5780 dsc integration guide

Alcatel-Lucent 5780DYNAMIC SERVICES CONTROLLER | RELEASE 5.1I N T E G R A T I O N G U I D E

Alcatel-Lucent ProprietaryThis document contains proprietary information of Alcatel-Lucent and is not to be disclosedor used except in accordance with applicable agreements.Copyright 2012-2013 © Alcatel-Lucent. All rights reserved.

I N T E G R A T I O N G U I D E

When printed by Alcatel-Lucent, this document is printed on recycled paper.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice.

Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, and TiMetra are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

Copyright 2012-2013 Alcatel-Lucent.All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

iii

Alcatel-Lucent License Agreement

SAMPLE END USER LICENSE AGREEMENT

1. LICENSE1.1 Subject to the terms and conditions of this Agreement, Alcatel-Lucent grants

to Customer and Customer accepts a nonexclusive, nontransferable license to use any software and related documentation provided by Alcatel-Lucent pursuant to this Agreement ("Licensed Program") for Customer's own internal use, solely in conjunction with hardware supplied or approved by Alcatel-Lucent. In case of equipment failure, Customer may use the Licensed Program on a backup system, but only for such limited time as is required to rectify the failure.

1.2 Customer acknowledges that Alcatel-Lucent may have encoded within the Licensed Program optional functionality and capacity (including, but not limited to, the number of equivalent nodes, delegate workstations, paths and partitions), which may be increased upon the purchase of the applicable license extensions.

1.3 Use of the Licensed Program may be subject to the issuance of an application key, which shall be conveyed to the Customer in the form of a Supplement to this End User License Agreement. The purchase of a license extension may require the issuance of a new application key.

2. PROTECTION AND SECURITY OF LICENSED PROGRAMS2.1 Customer acknowledges and agrees that the Licensed Program contains

proprietary and confidential information of Alcatel-Lucent and its third party suppliers, and agrees to keep such information confidential. Customer shall not disclose the Licensed Program except to its employees having a need to know, and only after they have been advised of its confidential and proprietary nature and have agreed to protect same.

2.2 All rights, title and interest in and to the Licensed Program, other than those expressly granted to Customer herein, shall remain vested in Alcatel-Lucent or its third party suppliers. Customer shall not, and shall prevent others from copying, translating, modifying, creating derivative works, reverse engineering, decompiling, encumbering or otherwise using the Licensed Program except as specifically authorized under this Agreement. Notwithstanding the foregoing, Customer is authorized to make one copy for its archival purposes only. All appropriate copyright and other proprietary notices and legends shall be placed on all Licensed Programs supplied by Alcatel-Lucent, and Customer shall maintain and reproduce such notices on any full or partial copies made by it.

3. TERM3.1 This Agreement shall become effective for each Licensed Program upon

delivery of the Licensed Program to Customer.

iv

3.2 Alcatel-Lucent may terminate this Agreement: (a) upon notice to Customer if any amount payable to Alcatel-Lucent is not paid within thirty (30) days of the date on which payment is due; (b) if Customer becomes bankrupt, makes an assignment for the benefit of its creditors, or if its assets vest or become subject to the rights of any trustee, receiver or other administrator; (c) if bankruptcy, reorganization or insolvency proceedings are instituted against Customer and not dismissed within 15 days; or (d) if Customer breaches a material provision of this Agreement and such breach is not rectified within 15 days of receipt of notice of the breach from Alcatel-Lucent.

3.3 Upon termination of this Agreement, Customer shall return or destroy all copies of the Licensed Program. All obligations of Customer arising prior to termination, and those obligations relating to confidentiality and nonuse, shall survive termination.

4. CHARGES4.1 Upon shipment of the Licensed Program, Alcatel-Lucent will invoice

Customer for all fees, and any taxes, duties and other charges. Customer will be invoiced for any license extensions upon delivery of the new software application key or, if a new application key is not required, upon delivery of the extension. All amounts shall be due and payable within thirty (30) days of receipt of invoice, and interest will be charged on any overdue amounts at the rate of 1 1/2% per month (19.6% per annum).

5. SUPPORT AND UPGRADES5.1 Customer shall receive software support and upgrades for the Licensed

Program only to the extent provided for in the applicable Alcatel-Lucent software support policy in effect from time to time, and upon payment of any applicable fees. Unless expressly excluded, this Agreement shall be deemed to apply to all updates, upgrades, revisions, enhancements and other software which may be supplied by Alcatel-Lucent to Customer from time to time.

6. WARRANTIES AND INDEMNIFICATION6.1 Alcatel-Lucent warrants that the Licensed Program as originally delivered to

Customer will function substantially in accordance with the functional description set out in the associated user documentation for a period of 90 days from the date of shipment, when used in accordance with the user documentation. Alcatel-Lucent's sole liability and Customer's sole remedy for a breach of this warranty shall be Alcatel-Lucent's good faith efforts to rectify the nonconformity or, if after repeated efforts Alcatel-Lucent is unable to rectify the nonconformity, Alcatel-Lucent shall accept return of the Licensed Program and shall refund to Customer all amounts paid in respect thereof. This warranty is available only once in respect of each Licensed Program, and is not renewed by the payment of an extension charge or upgrade fee.

v

6.2 ALCATEL-LUCENT EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES, REPRESENTATIONS, COVENANTS OR CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OR REPRESENTATIONS OF WORKMANSHIP, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, DURABILITY, OR THAT THE OPERATION OF THE LICENSED PROGRAM WILL BE ERROR FREE OR THAT THE LICENSED PROGRAMS WILL NOT INFRINGE UPON ANY THIRD PARTY RIGHTS.

6.3 Alcatel-Lucent shall defend and indemnify Customer in any action to the extent that it is based on a claim that the Licensed Program furnished by Alcatel-Lucent infringes any patent, copyright, trade secret or other intellectual property right, provided that Customer notifies Alcatel-Lucent within ten (10) days of the existence of the claim, gives Alcatel-Lucent sole control of the litigation or settlement of the claim, and provides all such assistance as Alcatel-Lucent may reasonably require. Notwithstanding the foregoing, Alcatel-Lucent shall have no liability if the claim results from any modification or unauthorized use of the Licensed Program by Customer, and Customer shall defend and indemnify Alcatel-Lucent against any such claim.

6.4 Alcatel-Lucent Products are intended for standard commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The Customer hereby agrees that the use, sale, license or other distribution of the Products for any such application without the prior written consent of Alcatel-Lucent, shall be at the Customer's sole risk. The Customer also agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the Products in such applications.

7. LIMITATION OF LIABILITY7.1 IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF

ALCATEL-LUCENT, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ANY CLAIM, REGARDLESS OF VALUE OR NATURE, EXCEED THE AMOUNT PAID UNDER THIS AGREEMENT FOR THE LICENSED PROGRAM THAT IS THE SUBJECT MATTER OF THE CLAIM. IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF ALCATEL-LUCENT, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ALL CLAIMS EXCEED THE TOTAL AMOUNT PAID BY CUSTOMER TO ALCATEL-LUCENT HEREUNDER. NO PARTY SHALL BE LIABLE FOR ANY INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES, WHETHER OR NOT SUCH DAMAGES ARE FORESEEABLE, AND/OR THE PARTY HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7.2 The foregoing provision limiting the liability of Alcatel-Lucent's employees, agents, officers and directors shall be deemed to be a trust provision, and shall be enforceable by such employees, agents, officers and directors as trust beneficiaries.

vi

8. GENERAL8.1 Under no circumstances shall either party be liable to the other for any failure

to perform its obligations (other than the payment of any monies owing) where such failure results from causes beyond that party's reasonable control.

8.2 This Agreement constitutes the entire agreement between Alcatel-Lucent and Customer and supersedes all prior oral and written communications. All amendments shall be in writing and signed by authorized representatives of both parties.

8.3 If any provision of this Agreement is held to be invalid, illegal or unenforceable, it shall be severed and the remaining provisions shall continue in full force and effect.

8.4 The Licensed Program may contain freeware or shareware obtained by Alcatel-Lucent from a third party source. No license fee has been paid by Alcatel-Lucent for the inclusion of any such freeware or shareware, and no license fee is charged to Customer for its use. The Customer agrees to be bound by any license agreement for such freeware or shareware. CUSTOMER ACKNOWLEDGES AND AGREES THAT THE THIRD PARTY SOURCE PROVIDES NO WARRANTIES AND SHALL HAVE NO LIABILITY WHATSOEVER IN RESPECT OF CUSTOMER'S POSSESSION AND/OR USE OF THE FREEWARE OR SHAREWARE.

8.5 Alcatel-Lucent shall have the right, at its own expense and upon reasonable written notice to Customer, to periodically inspect Customer's premises and such documents as it may reasonably require, for the exclusive purpose of verifying Customer's compliance with its obligations under this Agreement.

8.6 All notices shall be sent to the parties at the addresses listed above, or to any such address as may be specified from time to time. Notices shall be deemed to have been received five days after deposit with a post office when sent by registered or certified mail, postage prepaid and receipt requested.

8.7 If the Licensed Program is being acquired by or on behalf of any unit or agency of the United States Government, the following provision shall apply: If the Licensed Program is supplied to the Department of Defense, it shall be classified as "Commercial Computer Software" and the United States Government is acquiring only "restricted rights" in the Licensed Program as defined in DFARS 227-7202-1(a) and 227.7202-3(a), or equivalent. If the Licensed Program is supplied to any other unit or agency of the United States Government, rights will be defined in Clause 52.227-19 or 52.227-14 of the FAR, or if acquired by NASA, Clause 18-52.227-86(d) of the NASA Supplement to the FAR, or equivalent. If the software was acquired under a contract subject to the October 1988 Rights in Technical Data and Computer Software regulations, use, duplication and disclosure by the Government is subject to the restrictions set forth in DFARS 252-227.7013(c)(1)(ii) 1988, or equivalent.

8.8 Customer shall comply with all export regulations pertaining to the Licensed Program in effect from time to time. Without limiting the generality of the foregoing, Customer expressly warrants that it will not directly or indirectly export, reexport, or transship the Licensed Program in violation of any export laws, rules or regulations of Canada, the United States or the United Kingdom.

vii

8.9 No term or provision of this Agreement shall be deemed waived and no breach excused unless such waiver or consent is in writing and signed by the party claimed to have waived or consented. The waiver by either party of any right hereunder, or of the failure to perform or of a breach by the other party, shall not be deemed to be a waiver of any other right hereunder or of any other breach or failure by such other party, whether of a similar nature or otherwise.

8.10 This Agreement shall be governed by and construed in accordance with the laws of the Province of Ontario. The application of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded.

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 ix3HE 07630 AAAD TQZZA Edition 01Integration Guide

Preface

The preface provides general information about the 5780 Dynamic Services Controller (5780 DSC) documentation suite.

Audience

This document is intended for administrators, operators, and maintenance personnel involved with installing, operating, maintaining, or troubleshooting the 5780 DSC.

5780 DSC documentation suite

Table 1 describes the documents that comprise the 5780 DSC documentation suite.

Table 1 5780 DSC documentation set

Title Description Part number

5780 DSC Release Description General information about the platform, product, compatibility requirements, network element compatibility of the release, features and functions of the 5780 DSC, features that are no longer supported, and ordering information.

07RD0119

5780 DSC Release Notice Important late-breaking information including new features, design change requests, restrictions and limitations, closed and outstanding problems, technical alerts, and installation and upgrade notes.

3HE 07626 AAAD TQZZA

5780 DSC Planning Guide Information required to plan a successful deployment of the 5780 DSC including deployment scenarios, geo-redundant configurations, platform requirements and sizing, bandwidth requirements, and network and security considerations.


(1 of 2)

Preface

x May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

5780 DSC Installation and Upgrade Guide

Information that describes: • 5780 DSC software requirements and installation

prerequisites• how to install the 5780 DSC for the first time including pre-

and post-installation procedures• how to configure geo-redundant deployments• how to upgrade the 5780 DSC


5780 DSC User Guide Information about:• an overall description of the 5780 DSC, including the core

services and features, as well as the key benefits of using the product

• how to access and log in to the 5780 DSC web-based GUI, and an overview of the GUI components including menus and icons, how to view and manage information, and perform routine GUI tasks

• how to configure and manage the metering limits, 9900 WNG policies, RADIUS-based policy management, and the rules engine, including: rule sets, rule tables, QoS rules, internal and external SPR subscribers, and how to work with AF, IP-CAN, Gateway Control, NASREQ, S9, Sd, and Sy sessions

• how to configure and manage 5780 DSC VSA dictionaries, PCRF clusters, and view the parameters associated with 5780 DSC complex equipment

• routine administrator tasks such as how to create user accounts, view the 5780 DSC platform status, set up the collection of performance metrics, start and stop the database and application servers, back up the 5780 DSC database, and manage license keys

• how to troubleshoot 5780 DSC platform components (such as connections, sessions, interfaces, rules, and actions), how to manage logging functions, restore and replicate the database, and collect information for technical support

• how to use the Provisioning Server XML interface to automate provisioning operations and examples to help you write custom OSS applications that interface with the 5780 DSC database


5780 DSC Integration Guide Information about:• 3GPP Gx, Gxx, Rx, S9, Sy, and Sd Diameter interfaces

supported by the 5780 DSC • 5780 DSC compliance with the 3GPP PCC-related Release 7,

8, 9, and 10 specifications


5780 DSC Policy Management Use Cases Provides a number of use cases that demonstrate how the 5780 DSC provides flexible policy control and charging rules to address the requirements of service providers.


5780 DSC API Reference Manual Provides simplified APIs for the 5780 DSC to configure subscribers, provide types of billing identifiers, and configure metering limits.


5780 DSC Error Messages Reference Describes the error messages you may receive when you use the 5780 DSC.


5780 DSC Glossary Provides the 5780 DSC glossary terms and definitions. 3HE 07625 AAAD TQZZA

Title Description Part number

(2 of 2)

Preface

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 xi3HE 07630 AAAD TQZZA Edition 01Integration Guide

Procedure 1 To find the 5780 DSC user documentation

The user documentation is available from the following sources:

• the top level of the product DVD:• 5780_DSC_Integration_Guide.pdf• 5780_DSC_User_Guide.pdf• 5780_DSC_Installation_and_Upgrade_Guide.pdf• 5780_DSC_Planning_Guide.pdf• 5780_DSC_Use_Cases.pdf• 5780_DSC_API_Reference_Manual.pdf• 5780_DSC_Error_Messages.pdf• 5780_DSC_Glossary.pdf

• Help→5780 DSC User Documentation in the 5780 DSC client GUI main menu

The mibs directory in the product DVD contains all the .mib files packaged in the product.

Searching for information in this guide

You can use Adobe Reader, Release 6.0 or later, to search one or more PDF files for a term.

Procedure 2 To search for specific information in this guide

1 Open Adobe Acrobat Reader.

2 Choose Edit→Search from the Acrobat Reader main menu. The Search panel appears.

3 Enter the search criteria.

4 Click on the In the current PDF Document radio button.

Note � Users of Mozilla browsers may receive an error message when using the User Documentation Index page (index.html) to open the PDF files in the 5780 DSC documentation suite. The offline storage and default cache values used by the browsers are the cause of the error message.

Alcatel-Lucent recommends changing the offline storage (Mozilla Firefox) or cache (Mozilla 1.7) values to 100 Mbytes to eliminate the error message.

Preface

xii May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

5 Select the following search criteria, if required:

• Whole words only• Case-Sensitive• Include Bookmarks• Include Comments

6 Click on the Search button. Acrobat Reader displays the search results. The results are grouped by PDF file and you can expand the entry for each file. You can expand the entries by clicking on the + symbol.

Procedure 3 To search for specific information in multiple 5780 DSC user documents

1 Open the Adobe Reader.

2 Choose Edit→Search from the Adobe Reader main menu. The Search panel appears.

3 Enter the search criteria.

4 Click on the All PDF Documents in radio button.

5 Choose the folder in which to search using the drop-down menu.

Note � After you click on a hyperlink, you can right-click and choose Previous View from the contextual menu to return to the location of the previous hyperlink.

Note � The PDF files that you search must be in the same folder.

Preface

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 xiii3HE 07630 AAAD TQZZA Edition 01Integration Guide

6 Select the following search criteria, if required:

• Whole words only• Case-Sensitive• Include Bookmarks• Include Comments

7 Click on the Search button. Adobe Reader displays the search results. The results are grouped by PDF file and you can expand the entry for each file.You can expand the entries by clicking on the + symbol.

Prerequisites

To perform the tasks in this documentation set, you need sufficient technical knowledge about:

• 3GPP specifications, available at: http://www.3gpp.org/• general telecommunications principles• network requirements, recommended deployments, and administration• UNIX administration

Conventions

Table 2 describes the conventions that are used in this documentation set.

Table 2 Documentation conventions

Note � After you click on a hyperlink, you can right-click and choose Previous View from the contextual menu to return to the location of the previous hyperlink.

Convention Description Example

Key name Press a keyboard key. Delete

Italics Italics identifies a variable. hostname

Key+Key Type the appropriate consecutive keystroke sequence. CTRL+G

Key�Key Type the appropriate simultaneous keystroke sequence. CTRL�G

* An asterisk is a wildcard character, which means �any character� in a search argument. In addition, parameters that have an asterisk (*) beside them are mandatory.

log_file*.txtName*

↵ Press the Return key. ↵

� An em dash indicates there is no information. �

(1 of 2)

Preface

xiv May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

Procedures with options or substepsWhen there are options in a procedure, they are identified by letters. When there are substeps in a procedure, they are identified by Roman numerals.

Example of options in a procedure

At step 1, you can choose option a or b. At step 2, you must do what the step indicates.

1 This step offers two options. You must choose one of the following:

a This is one option.

b This is another option.

2 You must perform this step.

Example of substeps in a procedure

At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates.

1 Perform the following substeps:

i This is the first substep.

ii This is the second substep.

iii This is the third substep.

2 You must perform this step.

Measurement conventionsMeasurements in this document are expressed in metric units and follow the Système international d’unités (SI) standard for abbreviation of metric units. If imperial measurements are included, they appear in brackets following the metric unit.

Table 3 lists the measurement symbols used in this document.

→ A right arrow indicates that a cascading submenu opens when you choose a menu item.

Policies→Routing

User-defined parameters

Appears in examples of code to denote user-defined parameters. <password>password</password>

Convention Description Example

(2 of 2)

Preface

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 xv3HE 07630 AAAD TQZZA Edition 01Integration Guide

Table 3 Bits and bytes conventions

Glossary entries in this documentation setGlossary entries marked with an asterisk are reproduced with permission from LTE – The UMTS Long Term Evolution: A Pocket Dictionary of Acronyms, © 2009 Stefania Sesia, Issam Toufik and Matthew Baker, available at: http://www.wiley.com/go/sesia_theumts.

Important informationThe following conventions are used to indicate important information.

Contact information

If you have questions or comments about this documentation, contact:

[email protected]

Measurement Symbol

bit b

byte byte

kilobits per second kb/s

Warning � Warning indicates that the described activity or situation may, or will, cause equipment damage or serious performance problems.

Caution � Caution indicates that the described activity or situation may, or will, cause service interruption.

Note � Notes provide information that is, or may be, of special interest.

Preface

xvi May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

Contents

Preface ixAudience ............................................................................................... ix5780 DSC documentation suite ...................................................................... ix

Procedure 1 To find the 5780 DSC user documentation ......................... xiSearching for information in this guide............................................................. xi

Procedure 2 To search for specific information in this guide .................. xiProcedure 3 To search for specific information in multiple 5780 DSC

user documents.................................................................. xiiPrerequisites.......................................................................................... xiiiConventions........................................................................................... xiii

Procedures with options or substeps ...............................................xivMeasurement conventions ...........................................................xivGlossary entries in this documentation set ....................................... xvImportant information................................................................ xv

Contact information .................................................................................. xv

1 � 5780 DSC Integration Guide overview 1-11.1 Overview ................................................................................. 1-2

2 � 5780 DSC Diameter interface 2-12.1 Diameter interface overview.......................................................... 2-22.2 Diameter base procedures ............................................................. 2-2

Capabilities exchange ............................................................... 2-22.3 Message formats......................................................................... 2-3

Gx Common headers and AVPs ..................................................... 2-4Gxx common headers and AVPs .................................................... 2-6Rx Common headers and AVPs ..................................................... 2-8Sy common headers and AVPs..................................................... 2-11Gx, Gxx, Sy, and Rx error code reporting ....................................... 2-14

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 xvii3HE 07630 AAAD TQZZA Edition 01Integration Guide

Contents

2.4 Gateway scenarios ..................................................................... 2-16GTP-based EPC scenarios .......................................................... 2-17PMIP-based EPC scenarios.......................................................... 2-22GPRS-based scenarios .............................................................. 2-37

2.5 Network-initiated scenarios .......................................................... 2-42GTP-based EPC scenarios .......................................................... 2-42PMIP-based EPC scenarios.......................................................... 2-47GPRS scenarios ...................................................................... 2-53

2.6 UE-initiated scenarios ................................................................. 2-56GTP-based EPC scenarios .......................................................... 2-56PMIP-based EPC scenarios.......................................................... 2-59GPRS-initiated scenarios ........................................................... 2-63

2.7 PCRF-initiated scenarios .............................................................. 2-70PCRF Session Termination ......................................................... 2-70PCRF Session Modification ......................................................... 2-71

2.8 Rule installation failures .............................................................. 2-73Handling transient failures ........................................................ 2-73Handling permanent failure for network-initiated rule requirements ...... 2-74Handling permanent failure for UE-initiated rule requirements............. 2-76

2.9 Inactive IP-CAN session cleanups .................................................... 2-79Handling duplicate Session-Ids .................................................... 2-79Handling unknown Session-Ids..................................................... 2-80Handling duplicate session binding information................................ 2-80

2.10 Gx, Gxx, and Rx audits and session cleanups ...................................... 2-81IP-CAN session cleanup audit...................................................... 2-81AF session cleanup audit ........................................................... 2-82GW session cleanup audit .......................................................... 2-83

2.11 Diameter protocol over a Sy interface.............................................. 2-84User Attachment .................................................................... 2-84OCS-based charging scenarios..................................................... 2-90

3 � 5780 DSC compliance matrix for 3GPP technicalspecifications 3-1

3.1 5780 DSC compliancy overview ....................................................... 3-3Variance of Diameter Specification ............................................... 3-4Compliance statements ............................................................. 3-7

3.2 Statement of compliance information for 3GPP-23.203 .......................... 3-73GPP 23.203 compliancy ............................................................ 3-7

3.3 Statement of compliance information for 3GPP-23.335 ......................... 3-213.4 Statement of compliance information for 3GPP-29.212 ......................... 3-21

3GPP 29.212 compliancy ........................................................... 3-213GPP 29.212 compliancy-Release 11 ............................................. 3-38

3.5 Statement of compliance information for 3GPP-29.213 ......................... 3-393GPP 29.213 compliancy ........................................................... 3-39




xviii May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

Contents


3.10 Statement of compliance information for 3GPP 29.329 ......................... 3-593GPP 29.329 compliancy ........................................................... 3-59

3.11 Statement of compliance information for 3GPP 29.335 ......................... 3-623.12 Statement of compliance information for RFC 2865.............................. 3-633.13 Statement of compliance information for RFC 2866.............................. 3-653.14 Statement of compliance information for RFC 3588.............................. 3-663.15 Statement of compliance information for RFC 4006.............................. 3-713.16 Statement of compliance information for RFC 5176.............................. 3-753.17 Statement of compliance information for SMPP 3.4.............................. 3-76

A. Diameter Result Codes A-1A.1 Diameter result codes overview ...................................................... A-2

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 xix3HE 07630 AAAD TQZZA Edition 01Integration Guide

Contents

xx May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 1-13HE 07630 AAAD TQZZA Edition 01Integration Guide

1 � 5780 DSC Integration Guide overview

1.1 Overview 1-2

1 � 5780 DSC Integration Guide overview

1-2 May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

1.1 Overview

The 5780 DSC Integration Guide describes:

• 3GPP Gx, Gxx, S9, Sy, and the Rx Diameter interfaces supported by the 5780 DSC

• 5780 DSC compliance with the 3GPP PCC-related Release 7, 8, and 9 specifications

• Diameter error messages you may receive when using the 5780 DSC


2 � 5780 DSC Diameter interface

2.1 Diameter interface overview 2-2

2.2 Diameter base procedures 2-2

2.3 Message formats 2-3

2.4 Gateway scenarios 2-16

2.5 Network-initiated scenarios 2-42

2.6 UE-initiated scenarios 2-56

2.7 PCRF-initiated scenarios 2-70

2.8 Rule installation failures 2-73

2.9 Inactive IP-CAN session cleanups 2-79

2.10 Gx, Gxx, and Rx audits and session cleanups 2-81

2.11 Diameter protocol over a Sy interface 2-84



Integration Guide

2.1 Diameter interface overview

This chapter describes the 3GPP Gx, Gxx, and Rx Diameter interfaces supported by the 5780 DSC. In the context of an OCS interworking with the 5780 DSC, this chapter also describes Diameter Base protocol support as specified in RFC 3588, except as modified in Sy application-specific procedures and AVPs.

Diameter is the mandatory protocol for 3GPP interfaces. The Diameter infrastructure has an impact on scalability, security, and distribution transparency. The 3GPP mandates compliance with the base Diameter specifications IETF RFCs. The initialization and maintenance of the connection between each PCRF and PCEF pair is defined by the underlying protocol. The establishment, maintenance, and termination of connections between Diameter nodes is described in RFC 3588.

In order to support PULL and PUSH procedures, a Diameter session needs to be established for each IP-CAN session. For IP-CAN types that support multiple IP-CAN bearers (for example, GPRS), the Diameter session is established when the first IP-CAN bearer for the IP-CAN session is established. Therefore, the Diameter transport must be SCTP.

The architecture includes a Diameter Routing Agent (DRA) which provides distribution transparency The requesting entity is not aware of the selection of the Diameter peer that is handling the request. A route entry can have a different destination based on the application identification AVP of the message. Therefore, Diameter agents (relay, proxy, redirection, and translation agents) must be configured to identify the 3GPP Gx application in the Auth-Application-Id AVP in order to create appropriate routing tables.

2.2 Diameter base procedures

The Diameter base protocol provides the minimum requirements for an AAA protocol. Each Diameter packet contains a list of AVPs that are used to transfer information between Diameter peers. The attribute determines the type of information to be transferred; the values determine the contents.

Capabilities exchangeWhen two Diameter peers establish a transport connection, they send each other a capabilities exchange message. The message allows the discovery of the identity and capabilities of a peer.

Note � The AVP header format is defined in RFC 3588.



The Auth-Application-Id AVP indicates the interfaces that the PCRF supports for the authentication and authorization portion of the application. Table 2-1 lists the values of the application identifier that the PCRF includes in the Auth-Application-Id AVPs.

Table 2-1 Application identifiers

The AVP code, in combination with the Vendor-Id, uniquely identifies the AVP and is contained in the AVP header. Table 2-2 lists the values of the Vendor-Identifier that the PCRF includes in the Vendor-Id and Vendor-Specific-Application-Id AVPs.

Table 2-2 Vendor identifiers

2.3 Message formats

This section describes the common headers and AVPs that are in the Gx, Gxx, Sy, and Rx message, and any error codes. Table 2-3 describes the AVP qualifiers that are identified for the AVPs.

Note � The 5780 DSC supports variants of the Diameter specifications required to interoperate with:

• CISCO CSG2 R4, aligned to the features outlined in the Cisco CSG2 R4 Enhanced Gx Interface Specification

• Nokia-Siemens-Networks (NSN) aligned to the features outlined in the Nokia Siemens Networks Flexi ISN, Rel.5.0

Interface Application identifier

Rx 16777236

Gx 16777238

Gxx 16777266

Vendor name Vendor identifier

3GPP 10415

3GPP2 5535

ETSI 13019

Alcatel-Lucent 637

CISCO 9



Integration Guide

Table 2-3 AVP qualifiers

Gx Common headers and AVPsOn the Gx interface, the messages exchanged between GW and the PCRF are:

• Credit Control Request (CCR)• Credit Control Answer (CCA)• Re-Authorize Request (RAR)• Re-Authorize Answer (RAA)

Table 2-4 lists the common headers and AVPs that are in the Gx messages.

AVP qualifier Description

O This AVP is optional. You do not need to include this AVP if it is not required.

m This AVP is optional as per the protocol, but mandatory in that particular message.

M This AVP must be included in all the messages.

F This AVP must be included in all the messages and that its position is fixed.

* The repeated occurrences of the AVP.

Note � Diameter error codes are supported, as defined in RFC 3588.



Table 2-4 Common Gx headers and AVPs

Message Qualifier AVP Description

CCR F Diameter Header (Flags) REQ, PXY

F Diameter Header (Command Code) 272

F Session-Id Session-Id is generated by the PGW. See section 8.8 of RFC3588.

M Auth-Application-Id 16777238

M Origin-Host FQDN of the GW

M Origin-Realm FQDN of the GW realm

M Destination-Realm FQDN of the PCRF realm

M CC-Request-Number Request number of the request

M CC-Request-Type CC-Request-Type has one of the following values:INITIAL_REQUESTUPDATE_REQUESTTERMINATION_REQUEST

O Supported-Features As specified by 3GPP TS 29.212 section 5.4.1

CCA F Diameter Header (Flags) PXY


F Session-Id Session-Id provided by the PGW in the CCR request


M Origin-Host FQDN of the PCRF

M Origin-Realm FQDN of the PCRF realm

m Origin-State-Id As specified by RFC 3588 [3] section 8.16




m Result Code or Experimental-Result As specified by 3GPP TS 29.212 section 5.5

(1 of 2)



Integration Guide

Gxx common headers and AVPsOn the Gxx interface, the messages exchanged between GW and the PCRF are:

• CCR• CCA• RAR• RAA

Table 2-5 lists the common headers and AVPs that are in the Gxx messages.

RAR F Diameter Header (Flags) REQ, PXY


F Session-Id Session-Id for the session





M Destination-Realm FQDN of the PGW realm

M Destination-Host FQDN of the PGW

M Re-Auth-Request-Type AUTHORIZE_ONLY


RAA F Diameter Header (Flags) PXY







m Result Code or Experimental-Result As specified by 3GPP TS 29.212 section 5.a5


(2 of 2)



Table 2-5 Common Gxx headers and AVPs


CCR F Diameter Header (Flags) REQ, PXY


F Session-Id Session-Id is generated by the SGW/HSGW. See section 8.8 of RFC3588.







M CC-Request-Type CC-Request-Type has one of the following values:INITIAL_REQUEST

UPDATE_REQUESTTERMINATION_REQUEST


CCA F Diameter Header (Flags) PXY










m Result Code or Experimental-Result As specified by 3GPP TS 29.212 section 5.a5

(1 of 2)



Integration Guide

Rx Common headers and AVPsOn the Rx interface, the messages exchanged between the PCRF and the AF are:

Table 2-6 lists the common headers and AVPs that are in the Rx messages.



F Session-Id Session-Id for the session.





M Destination-Realm FQDN of the GW realm

M Destination-Host FQDN of the GW

M Re-Auth-Request-Type AUTHORIZE_ONLY

O Supported-Features As specified by 3GPP TS 29.212 section 5.4.1.



F Session-Id Session-Id for the session.



O Supported-Features As specified by 3GPP TS 29.212 section 5.4.1.

m Result Code or Experimental-Result As specified by 3GPP TS 29.212 section 5.a5.


(2 of 2)

• AA-Request (AAR)• AA-Answer (AAA)• Session-Termination-Request

(STR)• Session-Termination-Answer

(STA)

• Abort-Session-Request (ASR)• Abort-Session-Answer (ASA)• RAR• RAA



Table 2-6 Common Rx headers and AVPs


AAR F Diameter Header (Flags) REQ, PXY




M Origin-Host FQDN of the AF

M Origin-Realm FQDN of the AF realm



M Supported-Features As specified by 3GPP TS 29.214 section 5.4.1

AAA F Diameter Header (Flags) REQ, PXY






M Supported-Features As specified by 3GPP TS 29.214 section 5.4.1.


STR F Diameter Header (Flags) REQ, PXY








M Termination-Cause DIAMETER_LOGOUT


(1 of 3)



Integration Guide

STA F Diameter Header (Flags) REQ, PXY








ASR F Diameter Header (Flags) REQ, PXY






M Destination-Realm FQDN of the AF realm

M Destination-Host FQDN of the AF


M Abort-Cause BEARER_RELEASED

M Supported-Features As specified by 3GPP TS 29.214 section 5.4.1.

ASA F Diameter Header (Flags) REQ, PXY









(2 of 3)



Sy common headers and AVPsOn the Sy interface, the messages exchanged between the OCS and the PCRF are:

• AA-Request (AAR)• AA-Answer (AAA)• Session-Termination-Request (STR)• Session-Termination-Answer (STA)• RAR• RAA

Table 2-7 lists the common headers and AVPs that are in the Sy messages.

See section 2.11 for more information about Diameter messages and Sy-specific AVPs over the Sy interface.








M Specific-Action INDICATION_OF_LOSS_OF_BEARER










(3 of 3)



Integration Guide

Table 2-7 Common Sy headers and AVPs


AAR F Diameter Header (Flags) REQ, PXY

F Diameter Header (Command Code) 265, R-bit set in Command Flags field





m Subscription-Id As specified by RFC 3588 [3] section 8.16


M Proxy-Info As specified by RFC 3588 section 6.7.2

M Route-Record As specified by RFC 3588 [3] section 6.7.1

AAA F Diameter Header (Flags) REQ, PXY

F Diameter Header (Command Code) 265, R-bit cleared in Command Flags field




m Result-Code As specified by RFC 3588 section 7.1.4 and 7.1.5

M Charging-Policy-Report Policy charging information related to a subscriber

m Error-Message As specified by RFC 3588 section 7.3

M Error-Reporting-Host As specified by RFC 3588 section 7.4

m Failed-AVP As specified by RFC 3588 section 7.5


(1 of 3)



STR F Diameter Header (Flags) REQ, PXY








M Termination-Cause DIAMETER_LOGOUT

M Destination-Host As specified by 3GPP TS 29.214 section 5.4.1

Class As specified by RFC 3588 [3] section 8.20

Proxy-Info As specified by RFC 3588 section 6.7.2

Route-Record As specified by RFC 3588 [3] section 6.7.1

STA F Diameter Header (Flags) PXY







M Error-Message As specified by 3GPP TS 29.214 section 5.4.1

m Result Code As specified by 3GPP TS 29.214 section 5.5

M Error-Reporting-Host As specified by RFC 3588 [3] section 7.4

m Failed-AVP As specified by RFC 3588 [3] section 7.5



(2 of 3)



Integration Guide

Gx, Gxx, Sy, and Rx error code reportingThis sub-subsection describes the Gx, Gxx, Sy, and Rx error codes. Errors are reported in Diameter using the Result-Code AVP or Experimental-Result-Code AVP.

Gx-specific error codes

Table 2-8 lists the Gx-specific error codes used for reporting in the Experimental-Result-Code AVP.







Destination-Host FQDN of the AF


M Subscription-Id INDICATION_OF_LOSS_OF_BEARER

M Charging-Policy-Report As specified by 3GPP TS 29.214 section 5.4.1

Origin-state-Id As specified by RFC 3588 [3] section 8.16






Origin-state-Id As specified by RFC 3588 [3] section 8.16

m Error-Message As specified by RFC 3588 [3] section 7.3

m Result Code As specified by 3GPP TS 29.214 section 5.5

M Error-Reporting-Host As specified by 3GPP TS 29.214 section 5.4.1

m Failed-AVP As specified by RFC 3588 [3] section 7.5



(3 of 3)



Table 2-8 Gx-specific error codes

Gxx-specific error codes

Table 2-9 lists the Gxx-specific error codes used for reporting in the Experimental-Result-Code AVP.

Table 2-9 Gxx-specific error codes

Rx-specific error codes

Table 2-10 lists the Rx-specific error codes used for reporting in the Experimental-Result-Code AVP.

Table 2-10 Rx-specific error codes

Sy-specific error codes

Table 2-11 lists the Sy-specific error codes used for reporting in the Result-Code AVP.

Result code number Result code message Failure type

4141 DIAMETER_PCC_BEARER_EVENT Transient

5140 DIAMETER_ERROR_INITIAL_PARAMETERS Permanent

5141 DIAMETER_ERROR_TRIGGER_EVENT Permanent

5142 DIAMETER_PCC_RULE_EVENT Permanent

5143 DIAMETER_ERROR_BEARER_NOT_AUTHORIZED Permanent

5144 DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED Permanent

5147 DIAMETER_ERROR_CONFLICTING_REQUEST Permanent


5145 DIAMETER_QOS_RULE_EVENT Permanent

5146 DIAMETER _BEARER_EVENT Transient


5061 INVALID_SERVICE_INFORMATION Permanent

5062 FILTER_RESTRICTIONS Permanent

5063 REQUESTED_SERVICE_NOT_AUTHORIZED Permanent

5064 DUPLICATED_AF_SESSION Permanent

5065 IP-CAN_SESSION_NOT_AVAILABLE Permanent



Integration Guide

Table 2-11 Sy-specific error codes

2.4 Gateway scenarios

This section describes the following basic Gateway scenarios:

• GTP-based EPC• PMIP-based EPC• GPRS-based


4001 DIAMETER_AUTHENTICATION_REJECTED Transient

4002 DIAMETER_OUT_OF_SPACE Transient

4003 ELECTION_LOST Transient

4010 DIAMETER_END_USER_SERVICE_DENIED Transient

4011 DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE Transient

4012 DIAMETER_CREDIT_LIMIT_REACHED Transient

5001 DIAMETER_AVP_UNSUPPORTED Permanent

5002 DIAMETER_UNKNOWN_SESSION_ID Permanent

5003 DIAMETER_AUTHORIZATION_REJECTED Permanent

5004 DIAMETER_INVALID_AVP_VALUE Permanent

5005 DIAMETER_MISSING_AVP Permanent

5006 DIAMETER_RESOURCES_EXCEEDED Permanent

5007 DIAMETER_CONTRADICTING_AVPS Permanent

5008 DIAMETER_AVP_NOT_ALLOWED Permanent

5009 DIAMETER_AVP_OCCURS_TOO_MANY_TIMES Permanent

5010 DIAMETER_NO_COMMON_APPLICATION Permanent

5011 DIAMETER_UNSUPPORTED_VERSION Permanent

5012 DIAMETER_UNABLE_TO_COMPLY Permanent

5013 DIAMETER_INVALID_BIT_IN_HEADER Permanent

5014 DIAMETER_INVALID_AVP_LENGTH Permanent

5015 DIAMETER_INVALID_MESSAGE_LENGTH Permanent

5016 DIAMETER_INVALID_AVP_BIT_COMBO Permanent

5017 DIAMETER_NO_COMMON_SECURITY Permanent

5030 DIAMETER_USER_UNKNOWN Permanent

5031 DIAMETER_RATING_FAILED Permanent



GTP-based EPC scenariosThis subsection describes the following basic GTP-based EPC scenarios:

• Attach• Detach• GW-initiated Session Modification

Attach

Figure 2-1 shows how the PGW initiates an IP-CAN Session Establishment by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-1 Attach call flow (IP-CAN Session Establishment)

Table 2-12 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Establishment.

SGW

20534

CCR (Gx)

CCA (Gx)

Establish IP-CAN Session Request

Establish IP-CAN Session Response

PGW PCRF



Integration Guide

Table 2-12 IP-CAN Session Establishment AVPs

Event Interface Message AVPs

IP-CAN Session Establishment

Gx CCR M: CC-Request-Type=INITIAL_REQUEST

M: CC-Request-Number=0

m: Called-Station-Id {APN name}

m: Subscription-Id {IMSI, NAI}

m: IP-CAN-Type=3GPP-EPS

m: RAT-Type=EUTRAN

m: Framed-IP-Address/Framed-IPv6-Prefix

m: Default-EPS-Bearer-QoS

m: QoS-Information {APN-AMBR}

O: Network Requested Support=NETWORK_REQUEST SUPPORTED

m: AN-GW-Address

O: 3GPP-User-Location-Info=TAI/ECGI

O: User-Equipment-Info {IMEISV}

CCA M: CC-Request-Type=INITIAL_REQUEST


m: Result-Code=DIAMETER_SUCCESS

O: Bearer-Control-Mode=UE_NW



m: Charging-Information

(1 of 2)



Detach

Figure 2-2 shows how the PGW initiates an IP-CAN Session Termination by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

The PCRF then initiates a Session Termination by sending an ASR (Rx) to the AF. The AF responds by sending an ASA (Rx) to the PCRF. The AF indicates that the session is terminated by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.

Figure 2-2 Detach call flow (IP-CAN Session Termination and AF Session Termination)

IP-CAN Session Establishment (continued)

Gx CCA O: Charging-Rule-Install

O: Event-Trigger=QOS_CHANGE

O: Event-Trigger=RAT_CHANGE

O: Event-Trigger=LOSS_OF_BEARER

O: Event-Trigger=RECOVERY_OF_BEARER

O: Event-Trigger=IP-CAN_CHANGE

O: Event-Trigger=QOS_CHANGE_EXCEEDING_AUTHORIZATION

O: Event-Trigger=AN_GW_CHANGE

O: Event-Trigger=RESOURCE_MODIFICATION_REQUEST


(2 of 2)

PGW

20535

ASR (Rx)

ASA (Rx)

STR (Rx)

STA (Rx)

CCR (Gx)

CCA (Gx)

PCRF AF

Conditionto

Detach



Integration Guide

Table 2-13 lists the CCR (Gx) and CCA (Gx) attributes for an IP-CAN Session Termination, and the ASR (Rx), ASA (Rx), STR (Rx), and STA (Rx) attributes for a Session Termination.

Table 2-13 IP-CAN Session Termination and Session Termination AVPs

GW-initiated Session Modification

Figure 2-3 shows how the PGW initiates an IP-CAN Session Modification by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-3 IP-CAN Session Modification call flow (GW-initiated)

Table 2-14 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification.


IP-CAN Session Termination

Gx CCR M: CC-Request-Type=TERMINATION_REQUEST

M: CC-Request-Number=Previous + 1

m: Termination-Cause=DIAMETER_LOGOUT

CCA M: CC-Request-Type=TERMINATION_REQUEST



Session Termination

Rx ASR m: Abort-Cause=BEARER_RELEASED

ASA m: Result-Code=DIAMETER_SUCCESS

STR m: Termination-Cause=DIAMETER_LOGOUT

STA m: Result-Code=DIAMETER_SUCCESS

PGW

20536

CCR (Gx)

CCA (Gx)

PCRF

Triggerto modify

bearer



Table 2-14 IP-CAN Session Modification Gx AVPs

Table 2-15 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column describes any additional AVPs that are in the CCR (Gx) to report the indicated event from the PGW.

Table 2-15 Event Triggers on update


IP-CAN Session Modification

Gx CCR M: CC-Request-Type=UPDATE_REQUEST


*O: Event-Trigger=<Event Trigger>

*O: <Trigger Specific AVP>

CCA M: CC-Request-Type=UPDATE_REQUEST



*O: QoS-Information

*O: Charging-Rule-Install

*O: Charging-Rule-Remove

*O: Charging-Information

*O: Default-EPS-Bearer-QoS

Event trigger Trigger-specific AVPs

AN_GW_CHANGE AN-GW-Address

DEFAULT_EPS_BEARER_QOS_CHANGE Default-EPS-Bearer-QoS

IP-CAN_CHANGE IP-CAN-Type

NO_EVENT_TRIGGER �

OUT_OF_CREDIT Charging-Rule-Report

QOS_CHANGE QoS-Information

RAT_CHANGE RAT-Type

REALLOCATION_OF_CREDIT Charging-Rule-Report

RESOURCE_MODIFICATION_REQUEST Packet-Filter-OperationPacket-Filter-Information

USER_LOCATION_CHANGE 3GPP-User-Location-Info



Integration Guide

PMIP-based EPC scenariosThis subsection describes the following basic PMIP-based EPC scenarios:

• 3GPP access (GERAN/UTRAN/E-UTRAN)• e-HRPD

3GPP access (GERAN/UTRAN/E-UTRAN)

This subsection describes the following basic 3GPP access (GERAN/UTRAN/E-UTRAN) scenarios:

• Attach• Detach• GW-initiated Modification

Attach

Figure 2-4 shows how the SGW initiates a Gateway Control Session Establishment by sending a CCR (Gxc) to the PCRF. The PCRF responds by sending a CCA (Gxc) to the SGW.

The PGW initiates an IP-CAN Session Establishment by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-4 Attach call flow 3GPP access (GERAN/UTRAN/E-UTRAN)

Table 2-16 lists the CCR (Gxc) and CCA (Gxc) attributes for Gateway Control Session Establishment, as well as the CCR (Gx) and CCA (Gx) attributes for an IP-CAN Session Establishment.

Note � Only wildcard rules can be installed on Attach. QoS rules are typically installed after IP-CAN Session Establishment.

20537

PGWSGW

CCR (Gx)

CCA (Gx)

Binding Update

Binding Ack.

PCRF

Establish Gateway ControlSession Request

Establish Gateway ControlSession Response

CCR (Gxc)

CCA (Gxc)



Table 2-16 3GPP access (GERAN/UTRAN/E-UTRAN) Attach AVPs


Gateway Control Session Establishment

Gxc CCR M: CC-Request-Type=INITIAL_REQUEST





m: RAT-Type=EUTRAN




m: AN-GW-Address

O: 3GPP-User-Location-Info=TAI/ECGI








O: QoS-Rule-Install





O: Event-Trigger=USER_LOCATION_CHANGE

O: Event-Trigger=DEFAULT_EPS_BEARER_QOS_CHANGE


(1 of 2)



Integration Guide







m: RAT-Type=EUTRAN

m: AN-GW-Address









m: Online

m: Offline

O: Charging-Rule-Install

O: Charging-Information









(2 of 2)



Detach

Figure 2-5 shows how the SGW initiates a Gateway Control Session Termination by sending a CCR (Gxc) to the PCRF. The PCRF responds by sending a CCA (Gxc) to the SGW.


In Figures 2-5 and 2-6, the PCRF initiates a Session Termination by sending an ASR (Rx) to the AF. The PCRF responds by sending an ASA (Rx) to the PCRF. The AF then indicates that the session is terminated by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.

Figure 2-5 Detach call flow (SGW-initiated)

PGWSGW

Binding Update

Binding Ack.

CCR (Gxc)

CCA (Gxc)

ASR (Rx)

20538

ASA (Rx)

STR (Rx)

STA (Rx)

CCR (Gx)

CCA (Gx)

PCRF AF

Conditionto

Detach



Integration Guide

Figure 2-6 Detach call flow (PGW-initiated)

Table 2-17 lists the CCR (Gxc) and CCA (Gxc) attributes for Gateway Control Session Termination and Gateway Control Session Termination Ack, respectively. Table 2-17 also lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Termination, as well as the ASR (Rx), ASA (Rx), STR (Rx), and STA (Rx) attributes for Session Termination.

Table 2-17 Detach AVPs

PGWSGW

Binding Revocation Indication

Binding Revocation Ack.

CCR (Gxc)

CCA (Gxc)

ASR (Rx)

20539

ASA (Rx)

STR (Rx)

STA (Rx)

CCR (Gx)

CCA (Gx)

PCRF AF

Conditionto

Detach


Gateway Control Session Termination

Gxc CCR M: CC-Request-Type=TERMINATION_REQUEST






(1 of 2)



GW-initiated Modification

Figure 2-7 shows how the SGW initiates a Gateway Control and QoS Policy Rules Provisioning by sending a CCR (Gxc) to the PCRF. The PCRF responds by sending a CCA (Gxc) to the SGW.

The PGW can initiate an IP-CAN Session Modification by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-7 Modification call flow (SGW/PGW-initiated)

Table 2-18 lists the CCR (Gxc) and CCA (Gxc) attributes for Gateway Control and QoS Policy Rules Provisioning, as well as the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification.








Session Termination






(2 of 2)

SGW/PGW

20540

CCR (Gxc/Gx)

CCA (Gxc/Gx)

PCRF

Triggerto modify

bearer



Integration Guide

Table 2-18 3GPP access (GERAN/UTRAN/E-UTRAN) SGW/PGW-initiated AVP

Table 2-19 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column lists the additional AVPs that are in the CCR (Gxc) to report the indicated event from the SGW.

Table 2-19 Event Trigger codes on update


Gateway Control and QoS Policy Rules Provisioning

Gxc CCR M: CC-Request-Type=UPDATE_REQUEST




See Table 2-20 for a list of the <Event-trigger > Error codes.




*O: QoS-Rule-Install

*O: QoS-Rule-Remove

*O: QoS-Information

*O: Default-EPS-Bearer-QoS

IP-CAN Session Modification Gx CCR M: CC-Request-Type=UPDATE_REQUEST







m: Result-Code=DIAMETER_SUCCES


DEFAULT_EPS_BEARER_QOS_CHANGE Default-EPS-Bearer-QoS

LOSS_OF_BEARER QoS-Rule-Report


(1 of 2)



Table 2-20 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column describes the additional AVPs that are in the CCR (Gx) to report the indicated event from the PGW.

Table 2-20 Event Trigger codes on update

e-HRPD

This subsection describes the following basic e-HRPD scenarios:


Figure 2-8 shows how the HSGW initiates a Gateway Control Session Establishment by sending a CCR (Gxa) to the PCRF. The PCRF responds by sending a CCA (Gxa) to the HSGW.

The PGW initiates an IP-CAN Session Establishment by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

RAT_CHANGE RAT-Type

RECOVERY_OF_BEARER QoS-Rule-Report

RESOURCE_MODIFICATION_REQUEST Packet-Filter-OperationPacket-Filter-Information





RAT_CHANGE RAT-Type


(2 of 2)



Integration Guide

Figure 2-8 Session Establishment call flow (HSGW-initiated)

Table 2-21 lists the CCR (Gxa) and CCA (Gxa) attributes for Gateway Control Session Establishment, as well as the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Establishment.

20541

PGWHSGW

CCR (Gx)

CCA (Gx)

Binding Update

Binding Ack.

PCRF

Establish Gateway ControlSession Request

Establish Gateway ControlSession Response

CCR (Gxa)

CCA (Gxa)



Table 2-21 e-HRPD attach AVP


Gateway Control Session Establishment

Gxa CCR M: CC-Request-Type=INITIAL_REQUEST




m: IP-CAN-Type=3GPP2

m: RAT-Type=HRPD

O: QoS-Information {APN-AMBR}

m: AN-GW-Address

O: 3GPP2-BSID





O: QoS-Information {APN-AMBR}

O: QoS-Rule-Install







O: Event-Trigger=TFT_CHANGE

(1 of 2)



Integration Guide






m: IP-CAN-Type=3GPP2

m: RAT-Type=HRPD

m: AN-GW-Address









m: Online

m: Offline











(2 of 2)



Detach

Figure 2-9 shows how the HSGW initiates a Gateway Control Session Termination by sending a CCR (Gxa) to the PCRF. The PCRF responds by sending a CCA (Gxa) to the HSGW.


The PCRF initiates a Session Termination by sending an ASR (Rx) to the AF. The AF responds by sending an ASA (Rx) to the PCRF. The AF then indicates that the session is terminated by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.

Figure 2-9 Detach call flow (HSGW-initiated)

PGWHSGW

Binding Update

Binding Ack.

CCR (Gxa)

CCA (Gxa)

ASR (Rx)

20542

ASA (Rx)

STR (Rx)

STA (Rx)

CCR (Gx)

CCA (Gx)

PCRF AF

Conditionto

Detach



Integration Guide

Figure 2-10 Detach call flow (PGW-initiated)

Table 2-22 lists the CCR (Gxc) and CCA (Gxc) attributes for Gateway Control Session Termination and Gateway Control Session Termination Ack, respectively. The table also lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Termination, and the ASR (Rx), ASA (Rx), STR (Rx), and STA (Rx) attributes for Session Termination.

Table 2-22 e-HRPD Detach AVP

PGWHSGW

Binding Revocation Indication

Binding Revocation Ack.

CCR (Gxa)

CCA (Gxa)

ASR (Rx)

20543

ASA (Rx)

STR (Rx)

STA (Rx)

CCR (Gx)

CCA (Gx)

PCRF AF

Conditionto

Detach


Gateway Control Session Termination

Gxc CCR M: CC-Request-Type=TERMINATION_REQUEST






(1 of 2)



GW-initiated Modification

Figure 2-11 shows how the GW initiates Gateway Control and QoS Policy Rules Provisioning by sending a CCR (Gxa) to the PCRF. The PCRF responds by sending a CCA (Gxa) to the HSGW.

The GW initiates an IP-CAN Session Modification by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-11 Session Modification call flow (HSGW/PGW-initiated)

Table 2-23 lists the CCR (Gxa) and CCA (Gxa) attributes for Gateway Control and QoS Policy Rules Provisioning, as well as the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification.

IP-CAN Session Termination Gx CCR M: CC-Request-Type=TERMINATION_REQUEST






Session Termination Rx ASR m: Abort-Cause=BEARER_RELEASED





(2 of 2)

HSGW/PGW

20544

CCR (Gxa/Gx)

CCA (Gxa/Gx)

PCRF

Triggerto modify

bearer



Integration Guide

Table 2-23 GW-initiated AVP

Table 2-24 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column describes the additional AVPs that are in the CCR (Gxa) to report the indicated event from the PGW.

Table 2-24 Gxa-specific Event Triggers


Gateway Control and QoS Policy Rules Provisioning

Gxa CCR M: CC-Request-Type=UPDATE_REQUEST








*O: QoS-Rule-Install

*O: QoS-Rule-Remove

*O: QoS-Information






See Table 2-25 for a list of <Event-trigger > Error codes.

CCA M: CC-Request-Number=Previous + 1

M: CC-Request-Type=UPDATE_REQUEST




LOSS_OF_BEARER QoS-Rule-Report


RAT_CHANGE RAT-Type

RECOVERY_OF_BEARER QoS-Rule-Report

(1 of 2)



Table 2-25 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column describes the additional AVPs that are in the CCR (Gx) to report the indicated event from the PGW.

Table 2-25 Gx-specific Event Triggers

GPRS-based scenariosThis subsection describes the following basic GPRS-based scenarios:


Attach

Figure 2-12 shows how the GW initiates an IP-CAN Session Establishment by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.

Figure 2-12 Attach call flow (IP-CAN Session Establishment)

TFT_CHANGE TFT-Packet-Filter-InformationQoS-Resource-IdentifierQoS-Resource-Operation

USER_LOCATION_CHANGE 3GPP2-BSID




RAT_CHANGE RAT-Type


(2 of 2)

20727

CCR (Gx)

CCA (Gx)

Establish IP-CAN Session Request

Establish IP-CAN Session Response

GW PCRF



Integration Guide

Table 2-26 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Establishment.

Table 2-26 IP-CAN Session Establishment AVPs






O: Network-Requested-Support=NETWORK_REQUEST SUPPORTED

m: QoS-Information {QoS-Class-Identifier, Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Bearer-Identifier}


O: Event-Trigger=SGSN_CHANGE




O: Event-Trigger=PLMN_CHANGE





O: Event-Trigger=RAI_CHANGE



m: Bearer-Operation {ESTABLISHMENT}

(1 of 2)



Detach

Figure 2-13 shows how the GW initiates an IP-CAN Session Termination by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.

The PCRF then initiates a Session Termination by sending an ASR (Rx) to the AF. The AF responds by sending an ASA (Rx) to the PCRF. The AF then indicates that the session is terminated by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.

Gx CCA M: CC-Request-Type=INITIAL_REQUEST




m: QoS-Information {QoS-Class-Identifier, Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL, Bearer-Identifier}















(2 of 2)



Integration Guide

Figure 2-13 Detach call flow (IP-CAN Session Termination and Session Termination)

Table 2-27 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Termination, as well as the ASR (Rx), ASA (Rx), STR (Rx), and STA (Rx) attributes for Session Termination.


Modification

Figure 2-14 shows how the GW initiates a request for PCC rules by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.

GW

20728

RAR

CCA

ASA

STR

RAA

ASR

STA

CCR

Remove IP CANSession Request


PCRF AF

Detection that IP-CANSession termination

is required

For each affectedAF session (if any)





m: Termination-Cause=DIAMETER_LOGOUT(1)




Session Termination







Figure 2-14 Modification call flow (GW-initiated)

Table 2-28 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification.

Table 2-28 IP-CAN Session Modification

Table 2-29 lists the Event-Trigger values that are supported by the Event-Trigger AVP on an Update. The Trigger-specific AVP column describes the additional AVPs that are in the CCR (Gx) to report the indicated event from the GW.


GW

20743

CCR (Gx)

CCA (Gx)

PCRF

Triggerto modify

bearer


IP-CAN Session Modification Gx CCR M: CC-Request-Type=UPDATE_REQUEST



*O: Bearer-Identifier







SGSN_CHANGE 3GPP-SGSN-Address or 3GPP-SGSN-IPv6-Address

(1 of 2)



Integration Guide

2.5 Network-initiated scenarios

This section describes the following basic network-initiated scenarios:

• GTP-based EPC scenarios• PMIP-based EPC scenarios• GPRS-based scenarios


• Network-initiated Resource Request• Network-initiated Resource Release • Network-initiated Resource Modification

Network-initiated Resource Request

Figure 2-15 shows how the AF initiates a Resource Request by sending an AAR (Rx) to the PCRF. The PCRF responds by sending an AAA (Rx) to the AF.

The PCRF sends an RAR (Gx) to the PGW. The PGW responds by sending an RAA (Gx) to the PCRF.

QOS_CHANGE QoS-InformationBearer-Identifier

RAT_CHANGE RAT-type or 3GPP-RAT-Type

TFT_CHANGE TFT-Packet-Filter-InformationBearer-Identifier

PLMN_CHANGE 3GPP-SGSN-MCC-MNC

LOSS_OF_BEARER Charging-Rule-ReportBearer-IdentifierQoS-Information

RECOVERY_OF_BEARER Charging-Rule-ReportBearer-IdentifierQoS-Information

IP-CAN_CHANGE IP-CAN-Type, RAT-type or 3GPP-RAT-Type

QOS_CHANGE_EXCEEDING_AUTHORIZATION QoS-InformationBearer-Identifier

RAI_CHANGE RAI



(2 of 2)



Figure 2-15 Resource Request call flow (network-initiated)

Table 2-30 lists the AAR (Rx) and AAA (Rx) attributes for Resource Request, as well as the RAR (Gx) and RAA (Gx) attributes.

AF

20545

RAR (Gx)

RAA (Gx)

AAR (Rx)

AAA (Rx)

PCRF PGW



Integration Guide

Table 2-30 Resource request AVPs

Network-initiated Resource Release

Figure 2-16 shows how the AF initiates a Resource Release by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.


Resource Request

Rx AAR m: Subscription-Id=SIP URI/E.164


m: AF-Charging-Identifier

m: AF-Application-Identifier

m: Media-Component-Description

O: Specific-Action=SERVICE_INFORMATION_REQUEST

O: Specific-Action=INDICATION_OF_LOSS_OF_BEARER

O: Specific-Action=INDICATION_OF_RELEASE_OF_BEARER

O: Specific-Action=INDICATION_OF_ESTABLISHMENT_OF_BEARER

O: Specific-Action=CHARGING_CORRELATION_EXCHANGE

AAA m: Result-Code=DIAMETER_SUCCESS


m: RAT-Type=EUTRAN

Gx RAR M: Re-Auth-Request-Type=AUTHORIZE_ONLY

m: Charging-Rule-Install








RAA m: Result-Code=DIAMETER_SUCCESS




Figure 2-16 Resource Release call flow (network-initiated)

Table 2-31 lists the STR (Rx) and STA (Rx) attributes for Resource Release, as well as the RAR (Gx) and RAA (Gx) attributes.

Table 2-31 Resource release AVPs

Network-initiated Resource Modification

Figure 2-17 shows how the AF initiates a Resource Modification by sending an AAR (Rx) to the PCRF. The PCRF responds by sending an AAA (Rx) to the AF.


Note � When the PCRF receives an STR request and the associated Bearer-Control-Mode is UE_Only, an AF timer is started to delay the RAR and avoid a race condition from the Gx/Gxx interface.

AF

20546

RAR (Gx)

RAA (Gx)

STR (Rx)

STA (Rx)

PCRF PGW


Resource Release

Rx STR m: Termination-Cause=DIAMETER_LOGOUT



m: Charging-Rule-Remove




Integration Guide

Figure 2-17 Resource Modification call flow (AF-initiated)

Table 2-32 lists the AAR (Rx) and AAA (Rx) attributes for Resource Modification, as well as the RAR (Gx) and RAA (Gx) attributes.

Table 2-32 Resource Modification attributes (AF-initiated)

Figure 2-18 shows how the PGW initiates an IP-CAN Session Modification by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

The PCRF sends an RAR (Gx) to the AF. The AF responds by sending an RAA (Gx) to the PCRF.

Figure 2-18 IP-CAN Session Modification call flow (PGW-initiated)

AF

20545

RAR (Gx)

RAA (Gx)

AAR (Rx)

AAA (Rx)

PCRF PGW


Resource Modification

Rx AAR m: AF-Application-Identifier




m: Charging-Rule-Install and/or Charging-Rule-Remove


20547

RAR (Gx)

RAA (Gx)

CCR (Gx)

CCA (Gx)

PCRFPGW AF



Table 2-33 lists the CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification, as well as the RAR (Gx) and RAA (Gx) attributes.

Table 2-33 Session Modification attributes (PGW-initiated)


• Network-initiated Resource Request• Network-initiated Resource Release• Network-initiated Resource Modification


Figure 2-19 shows how the AF initiates a Resource Request by sending an AAR (Rx) to the PCRF. The PCRF responds by sending an AAA (Rx) to the AF.

The PCRF sends an RAR (Gxx) to the SGW/HSGW, and SGW/HSGW responds by sending an RAA (Gxx) to the PCRF.






O: QoS-Rule-Report




Rx RAR M: Re-Auth-Request-Type=AUTHORIZE_ONLY


O: Flows




Integration Guide

Figure 2-19 Resource Request call flow

Table 2-34 lists the AAR (Rx) and AAA (Rx) attributes for Resource Request, as well as the RAR (Gxx), RAA (Gxx), RAR (Gx) and RAA (Gx) attributes.

Table 2-34 Resource request attributes

AAR (Rx)

AAA (Rx)

20548

RAR (Gxx)

RAA (Gxx)

PCRFAF SGW/HSGW PGW

RAR (Gx)

RAA (Gx)


Resource Request












m: IP-CAN-Type

m: RAT-Type

(1 of 2)





The PCRF sends an RAR (Gxx) to the SGW/HSGW and SGW/HSGW responds by sending an RAA (Gxx) to the PCRF. The PCRF sends an RAR (Gx) to the PGW. The PGW responds by sending an RAA (Gx) to the PCRF.

Resource Request

Gxx RAR M: Re-Auth-Request-Type=AUTHORIZE_ONLY

m: QoS-Rule-Install






O: Event-Trigger=DEFAULT_EPS_BEARER_QOS_CHANGE















(2 of 2)

Note � When the PCRF receives an STR request and its associated Bearer-Control-Mode is UE_Only, an AF timer is started to delay the RAR and avoid a race condition from the Gx/Gxx interface.



Integration Guide

Figure 2-20 Resource Release call flow

Table 2-35 lists the STR (Rx) and STA (Rx) attributes for Resource Release, as well as the RAR (Gxx), RAA (Gxx), RAR (Gx) and RAA (Gx) attributes.




The PCRF sends an RAR (Gxx) to the SGW/HSGW and the SGW/HSGW responds by sending an RAA (Gxx) to the PCRF. The PCRF also sends an RAR (Gx) to the PGW. The PGW responds by sending an RAA (Gx) to the PCRF.

STR (Rx)

STA (Rx)

20549

RAR (Gxx)

RAA (Gxx)

PCRFAF SGW/HSGW PGW

RAR (Gx)

RAA (Gx)


Resource Release Rx STR m: Termination-Cause=DIAMETER_LOGOUT



m: QoS-Rule-Remove







Figure 2-21 Resource Modification call flow (AF-initiated)

Table 2-36 lists the AAR (Rx) and AAA (Rx) attributes for Resource Modification, as well as the RAR (Gxx), RAA (Gxx), RAR (Gx) and RAA (Gx) attributes.


Figure 2-22 shows how the HSGW/SGW initiates a Gateway Control Session Modification by sending a CCR (Gxx) to the PCRF. The PCRF responds by sending a CCA (Gxx) to the HSGW/SGW.

The PCRF sends an RAR (Rx) to the AF. The AF responds by sending an RAA (Rx) to the PCRF.

AAR (Rx)

AAA (Rx)

20548

RAR (Gxx)

RAA (Gxx)

PCRFAF SGW/HSGW PGW

RAR (Gx)

RAA (Gx)







m: QoS-Rule-Install and/or QoS-Rule-Remove



m: Charging-Rule-Install and/or Charging -Rule-Remove




Integration Guide

Figure 2-22 Gateway Control Session Modification call flow (HSGW/SGW-initiated)

Table 2-37 lists the CCR (Gxx) and CCA (Gxx) attributes for Gateway Control Session Modification, as well as the RAR (Rx) and RAA (Rx) attributes.

Table 2-37 Gateway Control Session Modification attributes (HSGW/SGW-initiated)

20550

RAR (Rx)

RAA (Rx)

CCR (Gxx/Gx)

CCA (Gxx/Gx)

PCRFHSGW/SGW/PGW AF

Triggerto modify

bearer



Gxx CCR M: CC-Request-Type=UPDATE_REQUEST



O: QoS-Rule-Report






O: Flows




GPRS scenariosThis subsection describes the following basic GPRS-based scenarios:

• Network-initiated Resource Request• Network-initiated Resource Release• Network-initiated Resource Modification


Figure 2-23 shows how the PCRF initiates a resource request by sending an RAR (Gx) to the GW. The GW responds by sending an RAA (Gx) to the PCRF.

Figure 2-23 Resource Request call flow (network-initiated)

Table 2-38 lists the RAR (Gx) and RAA (Gx) attributes, as well as the AAR (Rx) and AAA (Rx) attributes.

AF

20730

RAR (Gx)

RAA (Gx)

AAR (Rx)

AAA (Rx)

PCRF GW



Integration Guide

Table 2-38 Resource request AVPs


Resource Request












m: IP-CAN-Type

m: RAT-Type















m: Charging-Rule-Report






Figure 2-24 Resource Release call flow (network-initiated)

Table 2-39 lists the STR (Rx) and STA (Rx) attributes for Resource Release, as well as the RAR (Gx) and RAA (Gx) attributes.





AF

20731

RAR (Gx)

RAA (Gx)

STR (Rx)

STA (Rx)

PCRF GW


Resource Release

Rx STR m: Termination-Cause=DIAMETER_LOGOUT







Integration Guide

Figure 2-25 Resource Modification call flow (network-initiated)

Table 2-40 lists the AAR (Rx) and AAA (Rx) attributes for Resource Modification, as well as the RAR (Gx) and RAA (Gx) attributes.


2.6 UE-initiated scenarios

This section describes the following basic UE-initiated scenarios:

• GTP-based EPC scenarios• PMIP-based EPC scenarios• GPRS-based scenarios


• UE-initiated Resource Request• UE-initiated Resource Release• UE-initiated Resource Modification

AF

20732

RAR (Gx)

RAA (Gx)

AAR (Rx)

AAA (Rx)

PCRF GW







m: Charging-Rule-Install and/or Charging-Rule-Remove




UE-initiated Resource Request

Figure 2-26 shows how a UE-initiated Resource Request results in the PGW sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

Figure 2-26 Resource Request call flow (UE-initiated)

Table 2-41 lists the CCR (Gx) and CCA (Gx) attributes for UE-initiated Resource Request.

Table 2-41 Resource Request AVPs (UE-initiated)

UE-initiated Resource Release

Figure 2-27 shows how a UE-initiated Resource Release results in the PGW sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

20551

PCRFPGW

CCR (Gx)

CCA (Gx)

UE Requested BearerResource Modification





m: QoS-Information

m: Event-Trigger=RESOURCE_MODIFICATION_REQUEST

m: Packet-Filter-Operation=ADDITION

m: Packet-Filter-Information




m: Charging-Rule-Install/Charging-Rule-Remove



Integration Guide

Figure 2-27 Resource Release call flow (UE-initiated)

Table 2-42 lists the CCR (Gx) and CCA (Gx) attributes for UE-initiated Resource Release.

Table 2-42 Resource Release AVPs (UE-initiated)

UE-initiated Resource Modification

Figure 2-28 shows how a UE-initiated Resource Modification results in the PGW sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the PGW.

20551

PCRFPGW

CCR (Gx)

CCA (Gx)







m: Packet-Filter-Operation=DELETION








Figure 2-28 Resource Modification call flow (UE-initiated)

Table 2-43 lists the CCR (Gx) and CCA (Gxc) attributes for UE-initiated Resource Modification.

Table 2-43 Resource Modification attributes (UE-initiated)




Figure 2-29 shows how a UE-initiated Resource Request results in the SGW/HSGW sending a CCR (Gxx) to the PCRF. The PCRF responds by sending a CCA (Gxx) to the SGW/HSGW.

20551

PCRFPGW

CCR (Gx)

CCA (Gx)







m: Packet-Filter-Operation=MODIFICATION








Integration Guide



Table 2-44 lists the CCR (Gxx), CCA (Gxx), RAR (Gx) and RAA (Gx) attributes for UE-initiated Resource Request.

20552

PCRFSGW/HSGW

CCR (Gxx)

CCA (Gxx)


RAR (Gx)

RAA (Gx)

PGW



Table 2-44 Resource Request attributes (UE-initiated)


Figure 2-30 shows how a UE-initiated Resource Release results in the SGW/HSGW sending a CCR (Gxx) to the PCRF. The PCRF responds by sending a CCA. (Gxx) to the SGW/HSGW.







m: Packet-Filter-Operation=ADDITION





m: QoS-Rule-Install












Integration Guide


Table 2-45 lists the CCR (Gxx) and CCA (Gxx) attributes for UE-initiated Resource Release, as well as the RAR (Gx) and RAA (Gx) attributes.

Table 2-45 Resource release AVPs (UE-initiated)


Figure 2-31 shows how a UE-initiated Session Modification results in the SGW/HSGW sending a CCR (Gxx) to the PCRF. The PCRF responds by sending a CCA (Gxx) to the SGW/HSGW.


20552

PCRFSGW/HSGW

CCR (Gxx)

CCA (Gxx)


RAR (Gx)

RAA (Gx)

PGW






m: Packet-Filter-Operation=DELETION





m: QoS-Rule-Remove






Figure 2-31 Session Modification call flow (UE-initiated)

Table 2-46 lists the CCR (Gxx) and CCA (Gxx) attributes for UE-initiated Resource Modification, as well as the RAR (Gx) and RAA (Gx) attributes.

Table 2-46 Resource Modification AVPs (UE-initiated)

GPRS-initiated scenariosThis subsection describes the following basic GTP-based GPRS scenarios:


SGW/HSGW

20553

RAR (Gx)

RAA (Gx)

CCR (Gxx)

CCA (Gxx)

PCRF PGW







m: Packet-Filter-Operation=MODIFICATION





m: QoS-Rule-Install and/or QoS-Rule-Remove


m: Charging-Rule-Remove and/or Charging-Rule-Install




Integration Guide


Figure 2-32 shows a UE-initiated Resource Request. The GW initiates a resource request by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.

The PCRF sends an RAR (Rx) to the PGW. The PGW responds by sending an RAA (Rx) to the PCRF.


Table 2-47 lists the CCR (Gx) and CCA (Gx) attributes for UE-initiated Resource Request, as well as the RAR (Rx) and RAA (Rx) attributes.

20739

PCRFGW

CCR (Gx)

CCA (Gx)


RAR (Rx)

RAA (Rx)

AF



Table 2-47 Resource Request attributes (UE-initiated)


Figure 2-33 shows a UE-initiated Resource Release. The GW initiates a resource release by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.





m: Bearer-Identifier

m: Bearer-Operation {ESTABLISHMENT}

O: Bearer-Usage

m: QoS-Information

O: QoS-Upgrade

O: QoS-Negotiation

m: TFT-Packet-Filter-Information







O: Flows




Integration Guide


Table 2-48 lists the CCR (Gx) and CCA (Gx) attributes for UE-initiated Resource Release AVPs.

GW

20742

ASR (Rx)

ASA (Rx)

STR (Rx)

STA (Rx)

RAR (Rx)

RAA (Rx)

AAR (Rx)

AAA (Rx)

CCR (Gx)

Remove IP-CANBearer Request

Remove IP-CANBearer Response

CCA (Gx)

PCRF AF

If all the service dataflows within AFsessions are affected

If not all the service dataflows within AFsessions are affected



Table 2-48 Resource release AVPs (UE-initiated)


Figure 2-34 shows a UE-initiated Session Modification. The GW initiates a resource request by sending a CCR (Gx) to the PCRF and the PCRF responds by sending CCA (Gx) to the GW.

The PCRF sends an RAR (Rx) to the AF. The AF responds by sending an RAA (Rx) to the PCRF.





m: Bearer-Operation=TERMINATION








O: Flows






Session Termination





Note � The ASR/ASA and STR/STA (Rx) manages if all of the flows in the AF sessions are affected.

The RAR/RAA and AAR/AAA (Rx) manages if all of the flows in the AF sessions are not affected.



Integration Guide

Figure 2-34 Session Modification call flow (UE-initiated)

Table 2-49 lists the CCR (Gx) and CCA (Gx), as well as the RAR (Rx), RAA (Rx), attributes for UE-initiated Resource Modification.

Table 2-49 Resource Modification AVPs (UE-initiated)

20739

PCRFGW

CCR (Gx)

CCA (Gx)


RAR (Rx)

RAA (Rx)

AF





m: Bearer-Operation


O: QoS-Upgrade

O: QoS-Negotiation


*O: <Trigger Specific AVP>QoS-Information




*O: <Trigger Response AVP>



O: Flows





Table 2-50 Event Triggers on update

Table 2-51 lists the Trigger-Response AVPs that are sent in the CCA (Gx) from the PCRF to the GW after the Event-Trigger values are received.

Table 2-51 Event Trigger Responses


SGSN_CHANGE 3GPP-SGSN-Address/3GPP-SGSN-IPv6-Address

QOS_CHANGE Bearer-IdentifierQoS-Information

RAT_CHANGE 3GPP-RAT-Type

TFT_CHANGE Bearer-IdentifierTFT-Packet-Filter-Information


LOSS_OF_BEARER Charging-Rule-Report

RECOVERY_OF_BEARER Charging-Rule-Report


3GPP-RAT-Type

QOS_CHANGE_EXCEEDING_AUTHORIZATION Bearer-IdentifierQoS-Information

RAI_CHANGE RAI

USER_LOCATION_CHANGE 3GPP-User-Location


SGSN_CHANGE Charging-Rule-Install / Charging-Rule-Remove

QOS_CHANGE Charging-Rule-Install / Charging-Rule-RemoveQoS-Information

RAT_CHANGE Charging-Rule-Install / Charging-Rule-Remove

TFT_CHANGE Charging-Rule-Install / Charging-Rule-Remove

PLMN_CHANGE Charging-Rule-Install / Charging-Rule-Remove

IP-CAN_CHANGE Charging-Rule-Install / Charging-Rule-Remove

QOS_CHANGE_EXCEEDING_AUTHORIZATION Charging-Rule-Install / Charging-Rule-RemoveQoS-Information



Integration Guide

2.7 PCRF-initiated scenarios

This section describes the following basic UE/Gateway scenarios:

• PCRF Session Termination• PCRF Session Modification

PCRF Session TerminationFigure 2-35 shows how the PCRF initiates an IP-CAN Session Termination by sending an RAR (Gx) to the GW. The GW responds by sending an RAA (Gx) to the PCRF.

The GW terminates the IP-CAN session by sending a CCR (Gx) to the PCRF. The PCRF responds by sending a CCA (Gx) to the GW.

Figure 2-35 Detach call flow (IP-CAN Session Termination)

Table 2-52 lists the RAR (Gx), RAA (Gx), CCR (Gx), CCA (Gx) attributes for IP-CAN Session Termination, as well as the ASR (Rx), ASA (Rx), STR (Rx), and STA (Rx) attributes for Session Termination.

GW

20728

RAR

CCA

ASA

STR

RAA

ASR

STA

CCR



PCRF AF

Detection that IP-CANSession termination

is required

For each affectedAF session (if any)




PCRF Session ModificationFigure 2-36 shows how the PCRF initiates an IP-CAN Session Modification by sending an RAR (Gx) to the GW. The GW responds by sending an RAA (Gx) to the PCRF. For GPRS IP-CAN types, GW may also send a CCR (Gx) to the PCRF to indicate the change. The PCRF responds by sending a CCA (Gx).

Figure 2-36 PCRF-initiated Modification

Table 2-53 lists the RAR (Gx), RAA (Gx), CCR (Gx) and CCA (Gx) attributes for IP-CAN Session Modification




m: Session-Release-Cause=Unknown


CCR M: CC-Request-Type=TERMINATION_REQUEST

m: Termination-Cause=DIAMETER_LOGOUT(1)



Session Termination





20740

PCRFGW

CCR (Gx)

CCA (Gx)PDP context signalling

RAR (Gx)

RAA (Gx)



Integration Guide

Table 2-53 IP-CAN Session Modification






*O: <Modification-Specific AVP>


CCR M: CC-Request-Type=UPDATE_REQUEST



*O: Bearer-Identifier







SGSN_CHANGE 3GPP-SGSN-Address or 3GPP-SGSN-IPv6-Address

QOS_CHANGE QoS-InformationBearer-Identifier

RAT_CHANGE RAT-type or 3GPP-RAT-Type

TFT_CHANGE TFT-Packet-Filter-InformationBearer-Identifier


LOSS_OF_BEARER Charging-Rule-ReportBearer-IdentifierQoS-Information

RECOVERY_OF_BEARER Charging-Rule-ReportBearer-IdentifierQoS-Information

(1 of 2)



2.8 Rule installation failures

This section describes the basic failure handling for network-initiated and UE-initiated rule requirements. The failure types are:

• transient• partial• permanent

Handling transient failuresErrors in the transient failures category inform a peer that the request cannot be completed at the time the request was received, but may be completed in the future. The Result-Code AVP values defined in Diameter Base RFC 3588 [5], are applicable.

Figure 2-37 shows how the AF initiates a Resource Request by sending an AAR (Rx) to the PCRF containing two flows (F1 and F2) that map to two PCC rules (PCC1 and PCC2). F1 is a modification to an existing rule (PCC1); F2 is a new rule (PCC2). The PCRF responds by sending an AAA (Rx) to the AF.

The PCRF sends an RAR (Gxx) to install PCC1 and PCC2 in the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Gx) to install PCC1 and PCC2 in the PGW. The PGW responds with a transient failure by sending an RAA (Gx) to the PCRF.

The PCRF waits a small amount of time before resending the RAR (Gx) to the PGW. The PGW responds with success by sending an RAA (Gx).

The PCRF sends an RAR (Gxx) to the NP SGW. The NP SGW responds by sending an RAA (Gxx) transient failure to the PCRF. The PCRF waits a small amount of time and sends a second RAR (Gxx) to the NP SGW. The NP SGW responds by sending an RAA (Gxx) transient failure to the PCRF.

The PCRF waits a small amount of time and sends a third RAR (Gxx) to the NP SGW, and the NP SGW responds by sending an RAA (Gxx) transient failure to the PCRF. The request is treated as a permanent failure. The PCRF rolls back the new records of the NP SGW.

IP-CAN_CHANGE IP-CAN-TypeRAT-Type3GPP-RAT-Type

QOS_CHANGE_EXCEEDING_AUTHORIZATION QoS-InformationBearer-Identifier

RAI_CHANGE RAI



(2 of 2)



Integration Guide

Figure 2-37 Resource request call flow (Transient Failures)

Handling permanent failure for network-initiated rule requirementsThis subsection describes the following basic network-initiated rule failure handling scenarios:

• resource-request partial failure• resource-request full failure

Resource request partial failure


The PCRF sends an RAR (Gxx) to install PCC1 and PCC2 in the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Gx) to install PCC1 and PCC2 in the PGW. The PGW responds with one success, one failure (PCC2 failure) by sending an RAA (Gx) to the PCRF.

PGWAF PCRF

20909

P SGW NP SGW

Wait

Wait

AAA (Rx)

AAR (Rx)

RAA (Gxx) Success PCCI, PCC2

RAR (Gxx) Install PCCI, PCC2

RAA (Gx) Transient

RAR (Gxx)

Wait

RAA (Gx) Transient

RAR (Gxx)

Rollback NPSGW newrecords

RAA (Gx) Transient

RAR (Gxx)

RAA (Gx) Transient

RAR (Gx)Install PCC1, PCC2

RAA (Gx) Success

RAR (Gx)



The PCRF sends an RAR (Gxx) to uninstall PCC2 from the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Gx) to install PCC1 in the NP SGW, and the NP SGW responds with success by sending an RAA (Gx) to the PCRF. The PCRF sends an RAR with a failure to the AF.

Figure 2-38 Resource request partial failure call flow (network-initiated)

Resource request full failure


The PCRF sends an RAR (Gxx) to install the equivalent QoS1 and QoS2 in the PSGW. The PSGW responds by sending an RAA (Gxx) with Success to the PCRF. The PCRF sends an RAR (Gx) to install PCC1 and PCC2 in the PGW. The PGW responds with two failures (PCC1 and PCC2 failure) by sending an RAA (Gx) to the PCRF.

The PCRF sends an RAR (Gxx) to uninstall PCC2 and roll back PCC1 from the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Gx) to install QoS1 in NP SGW, and NP SGW responds with success by sending an RAA (Gx) to the PCRF. The PCRF sends an RAR with a failure to the AF.

PCRFAF

AAR (Rx) F1, F2

AAA (Rx)

RAR (Rx)F2 Failed (removed)

RAA (Rx) (Success)

20807

RAR (Gx) InstallPCC1, PCC2

RAA (Gx)PCC1 (success)

PCC2 (failed)

PGW P SGW NP SGW

RAR (Gxx) Install PCC1, PCC2

RAA (Gxx) success PCC1, PCC2

RAR (Gxx) uninstall PCC2

RAA (Gxx) success

RAA (Gxx) success

RAR (Gxx) Install PCC1



Integration Guide

Figure 2-39 Resource Request full failure call flow (network-initiated)

Handling permanent failure for UE-initiated rule requirementsThis subsection describes the following basic UE-initiated rule failure handling scenarios:

• resource-request partial failure• resource-request full failure

Resource request partial failure

Figure 2-40 shows how the PSGW initiates a Resource Request by sending a CCR (Gxx) to the PCRF containing two packet filter IDs (PCC1 and PCC2) that map to two QoS rules (QoS1 and QoS2). The PCRF responds by sending a CCA (Gxx) to the PSGW.

The PCRF sends an RAR (Gx) to install the equivalent PCC rules PCC1 and PCC2 in the PGW. The PGW responds by sending an RAA (Gx) with success to the PCRF. The PCRF sends an RAR (Gxx) to install QoS1 and QoS2 in the SGW, and the SGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF sends an RAR (Gxx) to uninstall PCC2 from the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Rx) to remove PCC2 in the AF. The AF responds with success by sending an RAA (Rx) to the PCRF.

The AF sends an AAR (Rx) with two flows (F1, F2) to the PCRF in the PCRF’s timer after servicing the UE request. The PCRF responds with success by sending an AAA (Rx) to the AF. The PCRF sends an RAR (Gxx) to the PSGW and updates QoS1 and QoS2. The PSGW responds with success by sending an RAA (Gxx) to the PCRF.

PCRFAF

AAR (Rx) F1, F2

AAA (Rx)

RAR (Rx)F2 Failed (removed)F1 Failed (rolled back)

20808

RAR (Gx) InstallPCC1, PCC2

RAA (Gx)PCC1 (failed)PCC2 (failed)

PGW P SGW NP SGW

RAR (Gxx) Install PCC1, PCC2

RAA (Gxx) success PCC1, PCC2

RAA (Gxx) success

RAR (Gxx)uninstall PCC2rollback PCC1



The PCRF responds with an update of PCC1 and PCC2 by sending an RAR (Gx) to the PGW. The PGW responds with one failure (PCC2) by sending an RAA (Gx) to the PCRF.

The PGW responds with an RAR (Gxx) to the PSGW with a request to roll back QoS2. The PSGW responds with success by sending an RAA (Gxx) to the PGW.

The PCRF responds with an RAR (Gx) to the PGW with a request to roll back PCC2. The PGW responds with success by sending an RAA (Gx) to the PCRF.

The PCRF responds with an RAR (Gxx) to the SGW with a request to roll back QoS2. The SGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF responds with an RAR (Rx) to the AF. The AF responds with an RAA (Rx) to the PCRF.

Figure 2-40 Resource request-partial failure call flow (UE-initiated)

PGWAF PCRF

20829

PSGW SGW

CCR (Gxx)

RAA (Gx) (Success)

RAR (Gx)(Install PCC1, PCC2)

RAA (Gx)(PCC1 Success,

PCC2 Fail)

RAR (Gx)(Update PCC1, PCC2)

RAR (Gx) PCC1

AAR (Rx) (F1, F2)

AAA (Rx) (Success)

RAR (Rx)

RAA (Rx)

RAA (Gx)

CCA (Gxx)(Install QoS1, QoS2)

RAA (Gxx) (Success)

RAA (Gxx) (Success)

RAR (Gxx) (Update QoS1, QoS2)

RAA (Gxx)(Success)

RAR (Gxx) (Install QoS1, QoS2)

RAA (Gxx)

RAR (Gxx)(Remove QoS2)

RAR (Gxx)

Timer



Integration Guide

Resource request-full failure

Figure 2-41 shows how the PSGW initiates a Resource Request by sending a CCR (Gxx) to the PCRF containing two flows (F1, F2) that map to two PCC rules (PCC1 and PCC2). The PCRF responds by sending a CCA (Gxx) to the PSGW.

The PCRF sends an RAR (Gx) to install PCC1 and PCC2 in the PGW. The PGW responds by sending an RAA (Gx) with success to the PCRF. The PCRF sends an RAR (Gxx) to install QoS1 and QoS2 in the SGW, and the SGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF sends an RAR (Gxx) to uninstall PCC2 from the PSGW. The PSGW responds by sending an RAA (Gxx) with success to the PCRF. The PCRF sends an RAR (Rx) to remove PCC2 in the AF. The AF responds with success by sending an RAA (Rx) to the PCRF.

The AF sends an AAR (Rx) with two flows (F1, F2) to the PCRF. The PCRF responds with success by sending an AAA (Rx) to the AF. The PCRF sends an RAR (Gxx) to the PSGW and updates QoS1 and QoS2. The PSGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF responds with an update of PCC1 and PCC2 by sending an RAR (Gx) to the PGW. The PGW responds with two failures (PCC1 and PCC2 failure) by sending an RAA (Gx) to the PCRF.

The PCRF responds with an RAR (Gxx) to the PSGW with a request to remove QoS1 and QoS2. The PSGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF responds with an RAR (Gx) to the PGW with a request to remove PCC1 and PCC2. The PGW responds with success by sending an RAA (Gx) to the PCRF.

The PCRF responds with an RAR (Gxx) to the SGW with a request to remove QoS1 and QoS2. The SGW responds with success by sending an RAA (Gxx) to the PCRF.

The PCRF responds with an ASR (Rx) to the AF wand the AF responds with an ASA (Rx) to the PCRF.



Figure 2-41 Resource Request full failure call flow (UE-initiated)

2.9 Inactive IP-CAN session cleanups

This section describes how the duplicate and unknown Session-Ids are handled.

Handling duplicate Session-IdsThe reuse of Session-Ids is not allowed. The Session-Id identifies the user session, and includes a mandatory portion and an implementation-defined portion. The Session-Id must be globally unique and is meant to uniquely identify a user session without a reference to any other information. If the PCRF receives a Session Update or Session Termination request from any interface with a Session-Id that is a duplicate of another Session-Id, the request is rejected with a Result Code= DIAMETER_UNABLE_TO_COMPLY (5012).

PGWAF PCRF

20828

PSGW SGW

CCR (Gxx)

RAA (Gx) (Success)

RAR (Gx)(Install PCC1, PCC2)

RAA (Gx)(PCC1, PCC2 Fail)

RAR (Gx)(Update PCC1, PCC2)

RAR (Gx)(Remove PCC1, PCC2)

AAA (Rx) (F1, F2)

AAA (Rx) (Success)

AAA (Rx)

AAA (Rx)

RAA (Gx)

CCA (Gxx)(Install PCC1, PCC2, QoS1, QoS2)

CCA (Gxx) (Success)

RAA (Gxx) (Success)

RAR (Gxx) (Update QoS1, QoS2)

RAA (Gxx)

CAR (Gxx) (Install QoS1, QoS2)

RAA (Gxx)

RAR (Gxx) (Remove PCC1, PCC2)

CAR (Gxx) (Remove QoS1, QoS2)

Timer



Integration Guide

Handling unknown Session-IdsIf the PCRF receives a Session Update or Session Termination request from any interface with a session that does not exist, it rejects the request with a Result Code= DIAMETER_UNKNOWN_SESSION_ID (5002).

Handling duplicate session binding informationIf the PCRF receives an IP-CAN Session Establishment with overlapping session binding information from an existing session, the new session is established. Termination requests are sent to all GWC sessions and all AF sessions that are bound to the old IP-CAN session that has the overlapping binding information. A termination request is then sent to the new IP-CAN session.

Figure 2-42 shows the PGW initiating an IP-CAN session using a unique Session-Id but it has overlapping session binding information. The PGW sends a CCR attach with session binding information (for example, a APN/IPv4 combination) that overlaps with an existing IP-CAN session. The 5780 DSC detects the overlap and session establishment continues as if no overlapping session binding information exists. That is, a CCA is sent to the PGW.

For each session with overlapping session binding information, the following occurs:

1 The session and all bound sessions are marked as termination pending.

2 Termination requests are sent (RAR to IP-CAN and GWC, ASR to AF).

Figure 2-42 Session cleanup call flow (IP-CAN session)

PGWSGW

CCR establish(sessID_2)

CCAASR

21304

ASA

STR

STA

RAR establish(SessID_1)

RAA

CCR

CCA

PCRF AF

RAA

CCR

CCA

RAR for session establish



2.10 Gx, Gxx, and Rx audits and session cleanups

This section describes the following basic Gx, Gxx, and Rx audit and session cleanup scenarios:

• IP-CAN session cleanup audit• AF session cleanup audit• GW session cleanup audit

IP-CAN sessions, AF sessions, and GWC sessions have configurable audit intervals. At each of these intervals, the sessions are examined and if the last activity on a session occurred before the value of the audit interval, the session is validated.

If the session validation determines that the session does not exist, the session and related sessions are terminated.

IP-CAN session cleanup auditFigure 2-43 shows an audit with a known session by sending an RAR (Gx) to the PGW. The PGW responds by sending an RAA (Gx) to the PCRF with a Result Code of DIAMETER_SUCCESS (2001).

Figure 2-43 RC=2001 cleanup audit call flow (IP-CAN session)

Figure 2-44 shows an audit with an unknown session. If the RAA (Gx) has a Result Code of DIAMETER_UNKNOWN_SESSION_ID (5002). The PCRF initiates an AF Session Termination by sending an ASR (Rx) to the AF.

PGWSGW

TimerExpiry

20820

PCRF AF

RAR (Gx) event trigger

RAA (Gx) RC = 2001



Integration Guide

Figure 2-44 RC=5002 cleanup audit call flow (IP-CAN session)

The AF responds by sending an ASA (Rx) to the PCRF. The AF then indicates that the session is terminated by sending an STR (Rx) to the PCRF. The PCRF responds by sending an STA (Rx) to the AF.

The PCRF also sends an RAR (Gxx) to the SGW containing a Session-Release-Cause to request termination. The SGW responds by sending an RAA (Gxx) to the PCRF. The SGW then indicates that the session is terminated by sending a CCR (Gxx) to the PCRF. The PCRF responds by sending a CCA (Gxx) to the SGW.

AF session cleanup auditFigure 2-45 shows how the PCRF initiates a successful AF Session Cleanup Audit by sending an RAR (Gx) to the AF. The AF responds by sending an RAA (Gx) to the PCRF with a Result Code of DIAMETER_SUCCESS (2001).

Figure 2-45 RC=2001 cleanup audit call flow (AF session)

If the RAA (Gx) has a Result Code of DIAMETER_UNKNOWN_SESSION_ID (5002), then the PCRF initiates a PGW Rule Update by sending an RAR (Gx) to the PGW, as shown in Figure 2-46.

PGWSGW


TimerExpiry

RAA (Gx) RC = 5002ASR (Rx)

20813

ASA (Rx)

STR (Rx)

STA (Rx)

PCRF AF

RAA (Gxx)

CCR (Gxx)

RAR (terminate)

CCA (Gxx)

PGWSGW

RAR (Rx)= Specific action

TimerExpiry

RAA = RC2001

20821

PCRF AF



The PGW responds by sending an RAA (Gx) to the PCRF. The PCRF then indicates that the rule is updated by sending an RAR (Gx) to the SGW. The SGW responds by sending an RAA (Gxx) to the PCRF.

Figure 2-46 RC=5002 cleanup audit call flow (AF session)

GW session cleanup auditFigure 2-47 shows how the PCRF initiates a successful GW Session Cleanup Audit by sending an RAR (Gx) to the SGW. The SGW responds by sending an RAA (Gx) to the PCRF with a Result Code of DIAMETER_SUCCESS (2001).

Figure 2-47 RC=2001 cleanup audit call flow (GW control session)

Figure 2-48 shows how the PCRF initiates a successful GW Session Cleanup Audit by sending an RAR (Gx) to the PSGW. The PSGW responds by sending an RAA (Gx) to the PCRF with a Result Code of DIAMETER_UNKNOWN_SESSION_ID (5002).

In most cases, the PCRF receives a message from the PGW indicating that a handover occurred. If this message is not received in a specified time frame, the PCRF initiates a handover because the PSGW has been lost. The PCRF sends the PGW an RAR (Gx). The PGW responds by sending an RAA (Gx) to the PCRF.

The PCRF then indicates that the rule is updated by sending an RAR (Gx) to the AF. The AF responds by sending an RAA (Gxx) to the PCRF.

PGWSGW

TimerExpiry

RAR (Gx)(Rule update)

RAA (Gx)

20822

PCRF AF

RAA (Gxx)

RAR (Rule update)

RAR (Rx)= Specific action

RAA = RC5002

PGWSGW

TimerExpiry

RAA (Gx) RC = 2001

20823

PCRF AF




Integration Guide

Figure 2-48 RC=5002 cleanup audit call flow (GW control session)

2.11 Diameter protocol over a Sy interface

The OCS acts as a Diameter server with Diameter defined over the Sy interface, such that it is the network element that handles requests of charging information relevant to policy. The 5780 DSC acts as the Diameter client, such that it is the network element that requests charging information to determine the correct policies for the IP-CAN session.

Existing Diameter command codes from the Diameter base protocol RFC 3588 and the NASREQ Diameter application (IETF RFC 4005) are used with the Sy-specific AVPs. A Sy-specific Auth-Application-Id AVP is used together with the command code to identify the Sy messages.

User AttachmentFigure 2-49 shows user attachment as establishment of a policy charging session. Before opening the Gy session, the 5780 DSC opens the Sy session if it is not already open. The OCS indicates the status of the subscriber counters (Charging-Policy-Report AVP) to the 5780 DSC. The 5780 DSC then sets the adequate PCC rules (including QoS and rating groups) for the start of the user data session and its associated Sy session.

PGWPSGW SGW

Handover

RAR (Rx)

20824

RAR (Gx)

RAA (Gx)

RAA (Rx)

PCRF AF

RAA (Gxx) RC = 5002

RAR (Gxx) Event trigger



Figure 2-49 User Attachment

At subscriber attachment, the PCEF interrogates the PCRF for QoS, Gating, or Charging policies in the Gx.CCR. The 5780 DSC validates the metering limits assigned to the subscriber to determine if Sy interaction is required. Some of the subscribers may not be controlled using a Sy session. The 5780 DSC supports Sy and Gx usage management simultaneously in the same deployment so the subscriber population can be split in the following ways for usage control:

• No usage management• Gx-based usage management• Sy-based usage management

The 5780 DSC maintains one Sy session per IMSI. The 5780 DSC can recycle an existing Sy session for the same subscriber across multiple bearers (same APN) and across multiple APNs provided that the same IMSI is present over Gx. This approach optimizes the Sy session management compared to Gx session management where the PCRF must maintain a separate Gx session per default bearer/primary PDP context.

The OCS returns managed counters to the 5780 DSC. The counters are reported in the Charging-Policy-Report, which includes multiple entries of the Policy-Counter. The counter value reported back to the 5780 DSC must be a “numeric” value so the 5780 DSC can map back to the metering limit cumulative usage that has been accumulating since the beginning of the billing cycle.

After receiving a list of counters per subscriber, the 5780 DSC selects one of the counters and associates it with the subscriber data session. For example, the OCS might return three counters (1. Blackberry. 2. Data. 3. Sponsored traffic). The 5780 DSC selects the counter to use based on the configured applicability in the metering limit; for example, if APN = blackberry then use “1.blackberry” counter”.

Another example can be where the OCS returns two counters:

• Data • Premium-Data

OCSPCEF

22063

5780DSC

SY.AAR

SY.AAA

GxCCA

Gx.CCRSy Required?

Sy Session exist?

Counter Binding

Policy Decision

PCEF - OCS Interaction as per 3GPP



Integration Guide

The 5780 DSC implements the applicability to select the “premium-data” if the subscriber SPR record is populated with a flag to reflect a premium service. In this case, the OCS embedded SPR must be maintained by the external OSS/BSS to ensure consistent handling across the two systems.

The same binding algorithm is implemented with PCC level counters, where the 5780 DSC selects certain counters based on the application session. The 5780 DSC ignores received data updates for counters that are not bound to a subscriber session or PCC rule (application session).

After binding the counter to the subscriber session, the 5780 DSC evaluates the associated business rules (for example, threshold value and threshold crossing policy) and based on the outcome can downgrade the subscriber QoS or reject the data session as configured by the service provider.

The 5780 DSC responds to the PCEF with the authorization for QoS, Gating, or Charging as defined in 3GPP 29.212. The Rating Group/Charging information must be consistent with the configuration on the OCS and the 5780 DSC so that the PCRF selected rating group (based on the metering limit) results in the OCS updating the counter that feeds into the metering limit selected by the 5780 DSC.

Threshold crossing

Based on the OCS configuration, the OCS may decide that the subscriber has crossed a specified limit and 5780 DSC intervention is required. This step is very specific to the OCS implementation. The OCS sends a RAR to communicate this new state information. The 5780 DSC deploys the changes to the network as defined in 3GPP 29.212. The PCEF installs the deployed PCC rules and acknowledges the RAR by sending a RAA.

Based on the new state of the subscriber counters, the 5780 DSC evaluates the associated business rules. For example, the threshold value and threshold crossing policy may be communicated and, based on the outcome, it can:

• downgrade the subscriber session QoS• redirect the data session to a captive portal• deploy DPI policy• or any other option that is available

Session termination

At some point the subscriber or network will decide to terminate the Gx session triggering the possibility of terminating the Sy session. In the case where the subscriber [identified by IMSI] has multiple Gx sessions, the Sy session will be terminated only when the final Gx session terminates as the 5780 DSC maintains a single Sy per multiple Gx sessions. Figure 2-50 shows the message flow for session termination.



Figure 2-50 Session termination

The 5780 DSC validates the Sy-Gx session correlation and depending on the number of Gx sessions posts the termination of the session in question. It may terminate the Sy session (because the number of Gx sessions is zero) or it might keep the Sy session (because the number of Gx sessions is greater than zero).

The OCS should also be notified by the gateway over the Gy interface that the UE session has been terminated. The OCS then acknowledges the removal of the Sy session and deletes any internal reference to it. The OCS is no longer expected to send updates of a user’s usage over Sy using the just deleted Sy Session-Id. If a RAR message is sent, it will be rejected and any reported usage will be ignored. If there is a new user attachment, the 5780 DSC will generate a new Sy Session-Id.

Summary of exchanged messages for Sy charging policy sessions

Table 2-55 summarizes the various messages exchanged between the PCEF, PCRF and OCS.

Table 2-55 Message summary for charging policy session

5780DSC

PCEF

22419

OCS

Gx CCA

Gx CCR

Sy.STA

Sy.STR

Terminate Sy Session?


The AAR messages is sent by the PCRF to the OCS in order to initiate a charging policy session and/or to request session information.The 5780 DSC interrogates the OCS for all subscriber active counters and registers for future changes. The OCS might be configured to expose a subset of the managed counters or it may be configured to expose abstract/aggregate counters. This is left to the OCS implementation. To relieve the complexity of maintaining the counters across systems, the 5780 DSC does not provide the names of the counters to the OCS.The 5780 DSC generates the unique Sy Session-Id.

Sy AAR Session-Id Auth-Application-Id Origin-Host Origin-Realm Destination-Realm *Subscription-ID *Proxy-Info *Route-Record

(1 of 3)



Integration Guide

The AAA command is sent by the OCS to the PCRF in response to the AAR command. The report must contain all policy charging information related to a subscriber; for example, all applicable policy counters must be present. The OCS is expected to return the managed counters to the 5780 DSC. The counters are reported in the Charging-Policy-Report, which includes multiple entries of Policy-Counter.Each policy-counter structure includes the Counter Id and Value.The counter-value reported back to the 5780 DSC must be a �numeric� value so that the 5780 DSC can map back to the metering limit cumulative usage that has been accumulating since the beginning of the billing cycle.The value of the counter is completely managed by the OCS. For example, on billing cycle reset, its expected that the OCS notifies the 5780 DSC that the counter value is set to zero.

Sy AAA Session-Id Auth-Application-Id Origin-Host Origin-Realm Result-Code Charging-Policy-Report Error-Message Error-Reporting-Host *Failed-AVP *Proxy-Info

The RAR command is sent by the OCS to the PCRF in order to indicate a charging policy report.The report contains information that has changed only; for example, only the policy counter that needs to be updated is present.

Sy RAR Session-Id Auth-Application-Id Origin-Host Origin-Realm Destination-Realm Destination-Host Subscription-ID Charging-Policy-ReportOrigin-State-Id *Proxy-Info *Route-Record

The RAA command is sent by the PCRF to the OCS to acknowledge a RAR command.

Sy RAA Session-Id Origin-Host Origin-Realm Result-Code Origin-State-Id Error-Message Error-Reporting-Host *Failed-AVP *Proxy-Info


(2 of 3)



Existing Diameter command codes from the Diameter base protocol IETF RFC 3588 and the NASREQ Diameter application (IETF RFC 4005) are used with the Sy-specific AVPs. A Sy-specific Auth-Application-Id is used together with the command code to identify the Sy messages. The Sy-specific AVPs include the following:

• Subscription-Id AVPThe Subscription-Id AVP (AVP Code 443) is used to identify the end user's subscription and is of type Grouped and includes a Subscription-Id-Data AVP that holds the identifier and a Subscription-Id-Type AVP that defines the identifier type. The Subscription-Id AVP is taken from the 3GPP TS32.299 specification and the rules for setting this AVP are the same as on Gy for a CCR in the IMS context.

• Charging-Policy-Report AVPThe Charging-Policy-Report AVP (AVP code to be defined) is of type Grouped, and holds policy charging information related to a subscriber. In the AAA, the report must contain all policy charging information related to a subscriber; for example, all applicable policy counters must be present. In the RAR, the report contains only information that has changed; for example, only the policy counter that needs to be updated is present.

• Policy-Counter AVPThe Policy-Counter AVP (Vendor 637: 1135) is of type Grouped and represents a counter associated to the subscriber and maintained by the OCS. The specific counter represented by this AVP is uniquely identified by the combination of the Policy-Counter-Id AVP and the Subscription-Id AVP. The value of the counter is defined by the Policy-Counter-Value AVP, which can hold an absolute value or percentage.

The STR command is sent by the PCRF to inform the OCS that an established session shall be terminated.

Sy STR Session-Id Auth-Application-Id Origin-Host Origin-Realm Destination-Realm Destination-Host Termination-CauseClassOrigin-State-Id *Proxy-Info *Route-Record

The STA command is sent by the OCS to the PCRF in response to the STR command.

Sy STA Session-Id Origin-Host Origin-Realm Result-Code Origin-State-Id Error-Message Error-Reporting-Host *Failed-AVP *Proxy-Info


(3 of 3)



Integration Guide

• Policy-Counter-Id AVPThe Policy-Counter-Id AVP (Vendor 637: 1137) is of type OctetString and contains the identifier of a policy counter.

• Policy-Counter-Value AVP The Policy-Counter-Value AVP (Vendor 637: 1137) is of type Unsigned32 and contains the value of the policy counter.

See section 2.3 for more information about Sy message formats.

See the 5780 DSC User Guide for more information about Sy usage.

OCS-based charging scenariosThis section describes the following basic OCS scenarios:

• Update of the policy charging session for a top-up• Restrict access asynchronous• Refresh of the policy charging session

Update of the policy charging session

Figure 2-51 shows how a Sy session is updated for a top-up when using the OCS. The update of the Sy session is initiated by the OCS which emits a RAR towards 5780 DSC. The RAR contains information about the counter state that has changed (new Policy-Counter-Value). The 5780 DSC then updates the PCC rules accordingly in the PCEF, which in turn performs credit reauthorization on Gy.

The OCS also allows the setting of validity dates on bundles and counter units. Validity is checked at session establishment only on Sy; therefore, when the units expire the session will continue as if the units continue to be valid. It is only in the next session or at the next refresh by the PCRF that the expiration will be detected.



Figure 2-51 User initiated session update

Restrict access asynchronous

Figure 2-52 shows how the OCS positions the Final Unit Action (FUA) to “restrict access” at the threshold crossing in an asynchronous situation. Before an update of the Gx session completes, the OCS immediately instructs the PCEF to apply restrictions for a short period of time (1 second).

During this time, the 5780 DSC can update the Gx session (set a new PCC rule with a new QoS and rating group). This solution is preferred when PCEF does not support validity-time = 0 or when optimization of the OCS response time is needed. This flow is enabled in OCS by setting a redirection rule of type “Limited free access” with a duration = 1 sec.

OCSPCEF

22967

PCRF

RAR (Charging-Policy-Report)

RAA (Result-Code)

If there are several Sy sessions opened for this subscriber(which is not recomended for performance reasons), the OCSshall emit a RAR for each session.

RAR (new PCC rule)

RAA

Update CCR (USU of previous RG RSU for new RG)

CAA (GSU for new RG)

1

top up



Integration Guide

Figure 2-52 Threshold reached (restricted mode async)

Refresh of the policy charging session

Figure 2-53 shows how the 5780 DSC refreshes the Sy session information regularly. For each Sy session that is alive, the 5780 DSC sends an AAR at regular intervals. The OCS replies with the complete PCC profile of the subscriber. If a change is detected, the 5780 DSC updates the corresponding Gx sessions with the PCEF.

OCSPCEF

22968

PCRF

RAR (Charging-Policy-Report)

RAA (Result-Code=2001)

The RESTRICT_ACCESS action specified in CCA is a“dummy” restriction, in the sense that no filter is defined.Its purpose is to allow continuation of the service for ashort period of time (1sec) while the PCRF installs the new PCC rule.

Policy 2(QoS 2)

Policy 1(QoS 1)

Restrictedmode with

policy 1(QoS1)

End user’sdata session

RAR (new PCC rule)

RAA

CCR (MSCC: RG=1, USU, RSU)

CCR (MSCC: RG=2, RSU)

CAA (MSCC: RG=2, GSU)

CCA (MSCC: RG=1, GSU, FUI,FUA=RESTRICT_ACCESS)

1

2

CCR (MSCC: RG=1, USU)

CCA (MSCC: RG=1, Validity-Time=1 sec)

1

After expiration of the validity-time, the service is supervised withthe newly installed policy (RG=2).

2

allocatedquota

consumed

Validitytime (1sec)expiration



Figure 2-53 Session refresh

OCSPCEF

22969

PCRF

AAR (Session-Id, Subscription-Id)

update Gx session (new PCC rules)

ack

AAA (Charging-Policy-Report)

CCR

CCA

Changedetected



Integration Guide


3 � 5780 DSC compliance matrix for 3GPP technical specifications

3.1 5780 DSC compliancy overview 3-3

3.2 Statement of compliance information for 3GPP-23.203 3-7







3.10 Statement of compliance information for 3GPP 29.329 3-59

3.11 Statement of compliance information for 3GPP 29.335 3-62

3.12 Statement of compliance information for RFC 2865 3-63






Integration Guide


3.17 Statement of compliance information for SMPP 3.4 3-76



3.1 5780 DSC compliancy overview

This chapter describes 5780 DSC compliance with the following versions of the 3GPP PCC-related specifications (the most recent minor version of each 3GPP specification release supported is listed below):

In addition to the specific versions mentioned above, the 5780 DSC supports the following minor versions of Releases 7, 8, 9, and 10, where applicable:

• DECEMBER 2009• SEPTEMBER 2010 • SEPTEMBER 2010 ALU • MARCH 2011• JUNE 2011 (Default)

The 5780 DSC must be configured to work in a specific minor version mode. If you want to use December 2011 support, or June 2011 support, select June 2011.

• 3GPP TS 23.203 v7.12.0• 3GPP TS 29.212 v7.11.0• 3GPP TS 29.213 v7.11.0• 3GPP TS 29.214 v7.9.0• 3GPP TS 29.230 v7.14.0• 3GPP TS 29.329 v7.8.0• 3GPP TS 23.203 v8.11.0• 3GPP TS 29.212 v8.11.1• 3GPP TS 29.213 v8.11.0• 3GPP TS 29.214 v8.9.1• 3GPP TS 29.215 v8.9.0• 3GPP TS 29.230 v8.5.0 • 3GPP TS 29.329 v8.7.0• 3GPP TS 23.203 v9.8.0• 3GPP TS 29.212 v9.6.1• 3GPP TS 29.213 v9.6.0• 3GPP TS 29.214 v9.6.0 • 3GPP TS 29.215 v9.6.0 • 3GPP TS 29.230 v9.6.0 • 3GPP TS 29.329 v9.3.0 • 3GPP TS 23.203 v10.3.0• 3GPP TS 23.203 v10.4.0• 3GPP TS 23.203 v10.5.0• 3GPP TS 23.335 v11.0.0• 3GPP TS 29.212 v10.2.1

• 3GPP TS 29.212 v10.3.0• 3GPP TS 29.212 v10.5.0• 3GPP TS 29.213 v10.1.0• 3GPP TS 29.213 v10.2.0• 3GPP TS 29.213 v10.4.0• 3GPP TS 29.214 v10.2.0 • 3GPP TS 29.214 v10.3.0 • 3GPP TS 29.214 v10.5.0• 3GPP TS 29.215 v10.1.0• 3GPP TS 29.215 v10.2.0• 3GPP TS 29.215 v10.4.0• 3GPP TS 29.219 v2.0.0 • 3GPP TS 29.230 v10.2.0 • 3GPP TS 29.230 v10.3.0 • 3GPP TS 29.230 v10.5.0 • 3GPP TS 29.329 v10.2.0 • 3GPP TS 29.329 v10.3.0 • 3GPP TS 29.329 v10.5.0 • 3GPP TS 29.335 v11.0.0 • RFC 2865• RFC 2866• RFC 3588• RFC 4006• RFC 5176• SMPP 3.4



Integration Guide

The 5780 DSC:

• Supports higher level Rx release sessions bound to a lower release Gx sessions; however, use of certain higher release AVPs may cause interworking issues. For example, using Rx release 8 specific actions with a Gx release 7 session may cause interworking issues.

• Diameter AVP flags for the AVPs that are supported by the 5780 DSC are pre-configured such that the correct flags are used by the 5780 DSC Diameter stack when operating with Diameter clients using different major and minor versions of the 3GPP standards.

• accepts a request with multiple versions to the PCRF, but chooses the highest version, storing it against the session and responding with that version in the CCA.

Variance of Diameter SpecificationThe 5780 DSC supports variants of the Diameter specifications required to interoperate with multiple vendors as follows:

FLASH NETWORKS

The 5780 DSC supports variants for Flash Networks:

• On Gx CCR establishment, there is no CC request number or Subscription Ids validation.

• Supports custom binding of Auxiliary Gx Host session to IP-CAN session with IPv4 / IPv6 addresses. It is assumed that there is no overlap of IP addresses in the APN.

• Supports custom establishment of CCA containing APN, SGSN MCC MNC, 3GPP RAT-Type, 3GPP-MS-TimeZone, User-Equipment-Info.

• Request message Bearer-Id is set to 1.• Request message IP-CAN-Type is set to 3GPP_GPRS.

SANDVINE

The 5780 DSC supports the following variants for Sandvine:

• Allows for missing QoS-Information in GPRS establishment scenarios.• Diameter_User_Unknown result for Auxiliary Gx Host establishment rejection

due to unknown subscriber• Diameter_User_Unknown result for IP-CAN Session establishment rejection due

to unknown subscriber• Indicates that default handling is based on the system default. The exceptions are

CCR messages are accepted without the QoS-Information. In addition, only the following event triggers are sent in CCA unless overwritten by the rule engine.

• SGSN_CHANGE• RAT_CHANGE• PLMN_CHANGE• RAI_CHANGE• USER_LOCATION_CHANGE



STARENT (Verizon specifications)

The 5780 DSC supports variants for Starent:

• Verizon vendor AVP support• Packet-Filter-Id in Flow-Information is generated by PCEF for the

Verizon-specific extension of Gxx• QoS Resource Operation AVP handling• QoS Resource Identifier AVP handling• Custom validation for QoS-Information for a UE-initiated request where

TFT-Packet-Filter-Information is involved• Updates contain TFT-Packet-Filter-Information• Event Trigger TFT-Change is allowed

CISCO CSG2

The 5780 DSC supports the following variants for CSG2:

• The 5780 DSC is aligned to the features outlined in the Cisco CSG2 R4 Enhanced Gx Interface Specification

• Supported features are set to Release 8.• Usage Management is supported as described in the Cisco CSG2 R4 Enhanced

Gx Interface Specification• The following QoS-Information validation is relaxed:

• GBR QCI:Not enforced: “GBR QCI requires either Guaranteed-Bitrate-UL or Guaranteed-Bitrate-DL)” and “must be non-GBR QCI” for establishment.Not enforced: “GBR QCI needs any of the following AVPs: Guaranteed-Bitrate-UL, Guaranteed-Bitrate-DL, Max-Requested-Bandwidth-UL, Max-Requested-Bandwidth-DL” during update.

• Non-GBR QCI:Not enforced: “non-GBR QCI requires Max-Requested-Bandwidth-UL or Max-Requested-Bandwidth-DL AVPs”.

• Unexpected GBR rates for non-GBR QCI are not ignored.• Relaxed validation “3GPP-RAT-Type is unexpected and will be ignored” on

establishment and update.• To terminate a session from the PCRF, the gateway expects the Terminate-Bearer

AVP from PCRF in RAR.• For Cisco eGGSN/CSG2 GPRS gateways, the Route-Record AVP should not be

included in diameter messages (CCR/CCA, RAR/RAA). You must modify the tpa.properties file to ensure that the Route-Record AVP is not included. See the 5780 DSC Installation and Upgrade Guide for information about changing the properties in the tpa.properties file.



Integration Guide

NSN

The 5780 DSC supports the following variants for NSN (Nokia-Siemens Networks):

• The 5780 DSC is aligned to the features outlined in the Nokia Siemens Networks Flexi Intelligent Service Node, Rel.5.0, CD, v. 5 Diameter Policy Control Application, Interface Description, including quota management

• IP-CAN-Type in CCR. The enumerated value is 3GPP-GPRS (0).• Supported-Features AVP. The PCRF will behave like Release 8 GPRS• Bearer-ID in CCR. Indicates the IP-CAN-bearer. When present within a CCR,

AVPs within the CCR refer to the bearer identified by this AVP. The Bearer-ID of an IP-CAN bearer is unique within the IP-CAN session and is selected by the PCEF.

• No network-initiated rule support for NSN.• Dynamic PCC rules are not supported.• The 5780 DSC supports only the following event triggers:

• SGSN_CHANGE (0)• QOS_CHANGE (1)• RAT_CHANGE (2)• RAI_CHANGE (12)• USER_LOCATION_CHANGE (13)• NO_EVENT_TRIGGERS (14) (in CCA only)• REVALIDATION_TIMEOUT (17)• USAGE_REPORT (26)

The USAGE_REPORT event trigger is set by default when UMI (GSU) is received by NSN.

The enumerated value NO_EVENT_TRIGGERS resets all event triggers, except for the USAGE_REPORT event trigger, which is reset when the accumulated usage is reported. Other event triggers, if any, are ignored and should be removed through rules.

• Several AVPs are not supported in CCR or ignored in CCA/RAR.• Since several AVPs are not supported in CCR, only basic validation is done on

the PCRF side.

HUAWEI/CISCO ASR5K GGSN

The 5780 DSC supports the following variants for Huawei/Cisco ASR5K GGSN:

• Pre-defined and provisioned PCC rules are installed with the Bearer-Identifier AVP contained within the Charging-Rule-Install AVP in CCA and/or RAR when the Bearer-Identifier is known to the 5780 DSC. This only applies to GPRS.

• Pre-defined and provisioned PCC rules are sent with the Bearer-Identifier AVP contained within Charging-Rule-Install AVP in CCA and/or RAR when the Bearer-Identifier is known to the 5780 DSC.

• The 5780 DSC allows changes to the session level Access-Network-Charging-Identifier



Compliance statementsIn order to provide information about the compliance of the Alcatel-Lucent 5780 DSC components with the 3GPP standards, Table 3-1 describes the types of compliance and associated codes. The codes are used in the following sections.

Table 3-1 Compliance statements

3.2 Statement of compliance information for 3GPP-23.203

A statement of compliance for the following specifications is described in this subsection:

• 3GPP 23.203 v7.12.0• 3GPP 23.203 v8.11.0• 3GPP 23.203 v9.8.0 • 3GPP 23.203 v10.3.0 • 3GPP 23.203 v10.4.0 • 3GPP 23.203 v10.5.0

3GPP 23.203 compliancyTable 3-2 lists compliancy information for Technical Specification Group Services and System Aspects; Policy and charging control architecture.

Type of Compliance Code Description

Fully compliant FC Implemented as specified in the section that includes the optional part of the specification.

Compliant C All mandatory parts of the functionality are implemented. Optional aspects may not be supported.

Partially compliant PC Some aspects of the mandatory part are not implemented.

Non-compliant NC The functionality is not implemented as specified. If applicable, proprietary implementations are described with a note.

Not applicable NA The section contains requirements, but they are not relevant to Alcatel-Lucent 5780 DSC core components.

No requirement NR The section does not contain requirements.

Header HD The section only contains the section header. For detailed compliance, see the corresponding subsections.



Integration Guide

Table 3-2 3GPP TS 23.203 compliancy

Section Requirement Compliancy v7.12.0 v8.11.0 v9.8.0 v10.3.0 v10.4.0/v10.5.0

Notes

Introduction � � ✓ ✓ ✓ ✓ ✓ �

1 Scope NA ✓ ✓ ✓ ✓ ✓ �

2 References NA ✓ ✓ ✓ ✓ ✓ �

3 Definitions, symbols and abbreviations

NA ✓ ✓ ✓ ✓ ✓ �

3.1 Definitions NA ✓ ✓ ✓ ✓ ✓ �

3.3 Abbreviations NA ✓ ✓ ✓ ✓ ✓ �

4 High level requirements HD ✓ ✓ ✓ ✓ ✓ �

4.1 General requirements PC ✓ ✓ ✓ ✓ ✓ Not all IP-CAN types supported.

4.2 Charging related requirements

NA ✓ ✓ ✓ ✓ ✓ �

4.2.1 General FC ✓ ✓ ✓ ✓ ✓ �

4.2.2 Charging models FC ✓ ✓ ✓ ✓ ✓ �

4.2.2a Charging requirements PC ✓ ✓ ✓ ✓ ✓ User CSG information not fully supported.

4.2.3 Examples of Service Data Flow Charging

NA ✓ ✓ ✓ ✓ ✓ �

4.3 Policy control requirements HD ✓ ✓ ✓ ✓ ✓ �

4.3.1 General FC ✓ ✓ ✓ ✓ ✓ �

4.3.2 Gating control FC ✓ ✓ ✓ ✓ ✓ �

4.3.3 QoS control FC ✓ ✓ ✓ ✓ ✓ �

4.3.3.1 QoS control at service data flow level

FC ✓ ✓ ✓ ✓ ✓ �

4.3.3.2 QoS control at IP-CAN bearer level

FC ✓ ✓ ✓ ✓ ✓ �

4.3.3.3 QoS Conflict Handling FC ✓ ✓ ✓ ✓ ✓ �

4.4 Usage Monitoring Control FC � � ✓ ✓ ✓ �

5 Architecture model and reference points

HD ✓ ✓ ✓ ✓ ✓ �

5.1 Reference architecture FC ✓ ✓ ✓ ✓ ✓ �

5.2 Reference points HD ✓ ✓ ✓ ✓ ✓ �

5.2.1 Rx reference point FC ✓ ✓ ✓ ✓ ✓ �

5.2.2 Gx reference point FC ✓ ✓ ✓ ✓ ✓ �

5.2.3 Reference points to subscriber databases

NC ✓ ✓ ✓ ✓ ✓ �

5.2.3.1 Sp reference point NC ✓ ✓ ✓ ✓ ✓ �

5.2.3.2 Ud reference point NC � � � ✓ ✓ �

(1 of 13)



5.2.4 Gy reference point NA ✓ ✓ ✓ ✓ ✓ �

5.2.5 Gz reference point NA ✓ ✓ ✓ ✓ ✓ �

5.2.6 S9 reference point PC � ✓ ✓ ✓ ✓ Server Rx authorizations and event subscriptions from an AF in the VPLMN not supported.

5.2.7 Gxx reference point FC � ✓ ✓ ✓ ✓ �

6 Functional description HD ✓ ✓ ✓ ✓ ✓ �

6.1 Overall description HD ✓ ✓ ✓ ✓ ✓ �

6.1.0 General HD ✓ ✓ ✓ ✓ ✓ �

6.1.1 Binding mechanism FC ✓ ✓ ✓ ✓ ✓ �

6.1.1.1 General FC ✓ ✓ ✓ ✓ ✓ �

6.1.1.2 Session binding FC ✓ ✓ ✓ ✓ ✓ �

6.1.1.3 PCC rule authorization and QoS rule generation

FC ✓ ✓ ✓ ✓ ✓ �

6.1.1.4 Bearer Binding FC ✓ ✓ ✓ ✓ ✓ �

6.1.2 Reporting FC ✓ ✓ ✓ ✓ ✓ �

6.1.3 Credit management FC ✓ ✓ ✓ ✓ ✓ �

6.1.4 Event Triggers FC ✓ ✓ ✓ ✓ ✓ �

6.1.5 Policy Control FC ✓ ✓ ✓ ✓ ✓ �

6.1.6 Service (data flow) Prioritization and Conflict Handling

FC ✓ ✓ ✓ ✓ ✓ �

6.1.7 Standardized QoS characteristics

HD � ✓ ✓ ✓ ✓ �

6.1.7.1 General FC � ✓ ✓ ✓ ✓ �

6.1.7.2 Standardized QCI characteristics

FC � ✓ ✓ ✓ ✓ �

6.1.7.3 Allocation and Retention Priority characteristics

FC � ✓ ✓ ✓ ✓ �

6.1.8 Termination Action NA � ✓ ✓ ✓ ✓ �

6.1.9 Handling of packet filters provided to the UE by PCEF/BBERF

FC � ✓ ✓ ✓ ✓ �

6.1.10 IMS Emergency Session Support

HD � ✓ ✓ ✓ ✓ �

6.1.10.1 Architecture model and Reference points

FC � � ✓ ✓ ✓ �

6.1.10.2 PCC Rule Authorization and QoS rule generation

FC � � ✓ ✓ ✓ �

6.1.10.3 Functional Entities HD � � ✓ ✓ ✓ �

6.1.10.3.1 PCRF FC � � ✓ ✓ ✓ �


Notes

(2 of 13)



Integration Guide

6.1.10.3.2 PCEF NA � � ✓ ✓ ✓ �

6.1.10.3.3 P-CSCF NA � � ✓ ✓ ✓ �

6.1.10.4 PCC Procedures and Flows FC � � ✓ ✓ ✓ �

6.1.11 Multimedia Priority Service Support

NC � � � ✓ ✓ MPS not supported

6.1.11.1 Architecture model and Reference points


6.1.11.2 PCC rule authorization and QoS rule generation


6.1.11.3 Priority EPS Bearer Service NC � � � ✓ ✓ MPS not supported

6.1.11.4 Bearer priority for IMS Multimedia Priority Services


6.2 Functional entities HD ✓ ✓ ✓ ✓ ✓ �

6.2.1 Policy Control and Charging Rules Function (PCRF)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.1.0 General FC ✓ ✓ ✓ ✓ ✓ �

6.2.1.1 Input for PCC decisions FC ✓ ✓ ✓ ✓ ✓ �

6.2.1.2 Subscription information management in the PCRF

FC ✓ ✓ ✓ ✓ ✓ �

6.2.1.3 V-PCRF HD � ✓ ✓ ✓ ✓ �

6.2.1.3.1 General FC � ✓ ✓ ✓ ✓ �

6.2.1.3.2 V-PCRF and Home Routed Access

NC � ✓ ✓ ✓ ✓ �

6.2.1.3.3 V-PCRF and Visited Access (local breakout)

NC � ✓ ✓ ✓ ✓ �

6.2.1.4 H-PCRF NC � ✓ ✓ ✓ ✓ �

6.2.1.4.1 General NC � ✓ ✓ ✓ ✓ �

6.2.1.4.2 H-PCRF and Home Routed Access

NC � ✓ ✓ ✓ ✓ �

6.2.1.4.3 H-PCRF and Visited Access (Local Breakout)

NC � ✓ ✓ ✓ ✓ �

6.2.1.5 Handling of Multiple BBFs associated with the same IP-CAN session

FC � ✓ ✓ ✓ ✓ �

6.2.1.5.1 Handling of two BBFs associated with the same IP-CAN session during handover

FC � ✓ ✓ ✓ ✓ �

6.2.1.5.2 Handling of multiple BBFs with IP-CAN session flow mobility

NC � � � �

6.2.2 Policy and Charging Enforcement Function (PCEF)

FC ✓ ✓ ✓ ✓ ✓ �


Notes

(3 of 13)



6.2.2.1 General FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.2 Service data flow detection FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.3 Measurement FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.4 QoS control FC ✓ ✓ ✓ ✓ ✓ �

6.2.3 Application Function (AF) FC ✓ ✓ ✓ ✓ ✓ �

6.2.4 Subscription Profile Repository (SPR)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.5 Service Data Flow Based Credit Control Function

FC ✓ ✓ ✓ ✓ ✓ �

6.2.6 Offline Charging System (OFCS)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.7 Bearer Binding and Event Reporting Function (BBERF)

HD � ✓ ✓ ✓ ✓ �

6.2.7.1 General FC � ✓ ✓ ✓ ✓ �

6.2.7.2 Service data flow detection FC � ✓ ✓ ✓ ✓ �

6.2.7.3 QoS Control FC � ✓ ✓ ✓ ✓ �

6.2.8 User Data Repository (UDR) NC � � � ✓ ✓ �

6.3 Policy and charging control rule

HD ✓ ✓ ✓ ✓ ✓ �

6.3.1 General FC ✓ ✓ ✓ ✓ ✓ �

6.3.2 Policy and charging control rule operations

FC ✓ ✓ ✓ ✓ ✓ �

6.4 IP-CAN bearer and IP-CAN session related policy information

FC ✓ ✓ ✓ ✓ ✓ �

6.5 Quality of Service Control rule

HD � ✓ ✓ ✓ ✓ �

6.5.1 General FC � ✓ ✓ ✓ ✓ �

6.5.2 Quality of Service control rule operations

FC � ✓ ✓ ✓ ✓ �

6.6 Usage Monitoring Control specific information

HD � � ✓ ✓ ✓ �

6.6.1 General FC � � ✓ ✓ ✓ �

6.6.2 Usage Monitoring Control operations

FC � � ✓ ✓ ✓ �

6.7 IP flow mobility Routing rule HD � � � ✓ ✓ �

6.7.1 General NC � � � ✓ ✓ �

6.7.2 Routing rule operations NC � � � ✓ ✓ �

7 PCC Procedures and flows HD ✓ ✓ ✓ ✓ ✓ �

7.1 Introduction FC ✓ ✓ ✓ ✓ ✓ �


Notes

(4 of 13)



Integration Guide

7.2 IP-CAN Session Establishment

FC ✓ ✓ ✓ ✓ ✓ �

7.3 IP-CAN Session Termination FC ✓ ✓ ✓ ✓ ✓ �

7.3.1 UE initiated IP-CAN Session termination

FC ✓ ✓ ✓ ✓ ✓ �

7.3.2 GW(PCEF) initiated IP-CAN Session termination

FC ✓ ✓ ✓ ✓ ✓ �

7.4 IP-CAN Session Modification FC ✓ ✓ ✓ ✓ ✓ �

7.4.1 IP-CAN Session Modification; GW(PCEF) initiated

FC ✓ ✓ ✓ ✓ ✓ �

7.4.2 IP-CAN Session Modification; PCRF initiated

FC ✓ ✓ ✓ ✓ ✓ �

7.4.3 Void NA � ✓ ✓ ✓ ✓ �

7.5 Update of the subscription information in the PCRF

FC ✓ ✓ ✓ ✓ ✓ �

7.6 PCRF Discovery and Selection

HD � ✓ ✓ ✓ ✓ �

7.6.1 General principles PC � ✓ ✓ ✓ ✓ �

7.6.2 Solution Principles NA � ✓ ✓ ✓ ✓ �

7.7 Gateway Control Session Procedures

HD � ✓ ✓ ✓ ✓ �

7.7.1 Gateway Control Session Establishment

HD � ✓ ✓ ✓ ✓ �

7.7.1.0 General FC � ✓ ✓ ✓ ✓ �

7.7.1.1 Gateway Control Session Establishment during Attach

FC � ✓ ✓ ✓ ✓ �

7.7.1.2 Gateway Control Session Establishment during BBERF Relocation

FC � ✓ ✓ ✓ ✓ �

7.7.2 Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

7.7.2.1 GW (BBERF)-Initiated Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

7.7.2.2 PCRF-Initiated Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

7.7.3 Gateway Control and QoS Rules Request

FC � ✓ ✓ ✓ ✓ �

7.7.3.1 General FC � ✓ ✓ ✓ ✓ �

7.7.3.2 Event reporting for PCEF in visited network and locally terminated Gxx interaction

NC � ✓ ✓ ✓ ✓ �

7.7.4 Gateway Control and QoS Rules Provision

FC � ✓ ✓ ✓ ✓ �


Notes

(5 of 13)



7.7.5 Void NA � ✓ ✓ ✓ ✓ �

7.8 Change in subscription for MPS priority services

NC � � � ✓ ✓ �

Annex A (normative):

Access specific aspects (3GPP)

NA ✓ ✓ ✓ ✓ ✓ �

A.1 GPRS FC ✓ ✓ ✓ ✓ ✓ �

A.1.0 General FC ✓ ✓ ✓ ✓ ✓ �

A.1.1 High level requirements FC ✓ ✓ ✓ ✓ ✓ �

A.1.1.1 General FC ✓ ✓ ✓ ✓ ✓ �

A.1.1.2 Charging related requirements

FC ✓ ✓ ✓ ✓ ✓ �

A.1.1.3 Policy control requirements FC ✓ ✓ ✓ ✓ ✓ �

A.1.1.4 QoS control FC � ✓ ✓ ✓ ✓ �

A.1.2 Architecture model and reference points

FC ✓ ✓ ✓ ✓ ✓ �

A.1.2.1 Reference points FC ✓ ✓ ✓ ✓ ✓ �

A.1.2.1.1 Gx reference point FC ✓ ✓ ✓ ✓ ✓ �

A.1.2.2 Reference architecture FC � ✓ ✓ ✓ ✓ �

A.1.3 Functional description FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1 Overall description FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.1 Binding mechanism FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.1.0 General FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.1.1 Bearer binding mechanism allocated to the PCEF

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.1.2 Bearer binding mechanism allocated to the PCRF

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.2 Reporting FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.3 Credit management FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.4 Event Triggers FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.1.5 Policy Control FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2 Functional entities FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.1 Policy Control and Charging Rules Function (PCRF)

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.1.1 Input for PCC decisions FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.2 Policy and Charging Enforcement Function (PCEF)

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.2.1 General FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.2.2 Service data flow detection FC ✓ ✓ ✓ ✓ ✓ �


Notes

(6 of 13)



Integration Guide

A.1.3.2.2.3 Packet Routing and Transfer Function

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.2.4 Measurement FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.2.3 Application Function (AF) FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.3 Policy and charging control rule

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.3.1 General FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.3.2 Policy and charging control rule operations

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.4 IP-CAN bearer and IP-CAN session related policy information

FC ✓ ✓ ✓ ✓ ✓ �

A.1.3.5 APN related policy information

FC � � ✓ ✓ ✓ �

A.1.4 PCC Procedures and flows FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.1 Introduction FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.2 IP-CAN Session Establishment

FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.3 IP-CAN Session Termination FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.3.1 UE initiated IP-CAN Session termination

FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.3.2 GW initiated IP-CAN Session termination

FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.4 IP-CAN Session Modification FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.4.1 IP-CAN Session Modification; GW (PCEF) initiated

FC ✓ ✓ ✓ ✓ ✓ �

A.1.4.4.2 IP-CAN Session Modification; PCRF initiated

FC ✓ ✓ ✓ ✓ ✓ �

A.2 I-WLAN (Void) NC ✓ ✓ ✓ ✓ ✓ This section is Void as of Release 8

A.2.1 High level requirements NC ✓ ✓ ✓ ✓ ✓ �

A.2.1.1 General NC ✓ ✓ ✓ ✓ ✓ �


NC ✓ ✓ ✓ ✓ ✓ �

A.2.1.3 Policy control requirements NC ✓ ✓ ✓ ✓ ✓ �

A.2.2 Architecture model and reference points

NC ✓ ✓ ✓ ✓ ✓ �

A.2.2.1 Reference points NC ✓ ✓ ✓ ✓ ✓ �

A.2.2.1.1 Rx reference point NC ✓ ✓ ✓ ✓ ✓ �

A.2.2.1.2 Gx reference point NC ✓ ✓ ✓ ✓ ✓ �

A.2.2.1.3 Sp reference point NC ✓ ✓ ✓ ✓ ✓ �

A.2.3 Functional description NC ✓ ✓ ✓ ✓ ✓ �


Notes

(7 of 13)



A.2.3.1 Overall description NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.1.1 Binding mechanism NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.2 Functional entities NC ✓ ✓ ✓ ✓ ✓ �


NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.2.1.1 Input for PCC decisions NC ✓ ✓ ✓ ✓ ✓ �


NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.2.3 Application Function (AF) NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.3 Policy and charging control rule

NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.3.1 General NC ✓ ✓ ✓ ✓ ✓ �

A.2.3.3.2 Policy and charging control rule operations

NC ✓ ✓ ✓ ✓ ✓ �

A.2.4 PCC Procedures and flows NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.1 Introduction NC ✓ ✓ ✓ ✓ ✓ �


NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.3 IP-CAN Session Termination NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.3.1 UE initiated IP-CAN Session termination

NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.3.2 GW (PCEF) initiated IP-CAN Session termination

NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.4 IP-CAN Session Modification NC ✓ ✓ ✓ ✓ ✓ �

A.2.4.4.1 IP-CAN Session Modification; GW (PCEF) initiated

NC ✓ ✓ ✓ ✓ ✓ �


NC ✓ ✓ ✓ ✓ ✓

A.3 Void NC ✓ ✓ ✓ ✓ ✓ �

A.4 3GPP Accesses (GERAN/UTRAN/E-UTRAN) - GTP-based EPC

HD � ✓ ✓ ✓ ✓ �

A.4.0 General HD � ✓ ✓ ✓ ✓ �

A.4.1 High Level Requirements HD � ✓ ✓ ✓ ✓ �


NA � ✓ ✓ ✓ ✓ �

A.4.1.2 QoS control FC � ✓ ✓ ✓ ✓ �

A.4.2 Architectural Model and Reference Points

HD � ✓ ✓ ✓ ✓ �


A.4.3 Functional Description HD � ✓ ✓ ✓ ✓ �


Notes

(8 of 13)



Integration Guide

A.4.3.1 Overall description HD � ✓ ✓ ✓ ✓ �

A.4.3.1.1 Credit management FC � ✓ ✓ ✓ ✓ �

A.4.3.1.2 Event Triggers FC � ✓ ✓ ✓ ✓ �

A.4.3.1.3 Binding mechanism FC � ✓ ✓ ✓ ✓ �

A.4.3.1.4 Policy Control FC � ✓ ✓ ✓ ✓ �

A.4.3.2 Functional Entities HD � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �


NC � � ✓ ✓ ✓ CSG not supported.

A.4.4 PCC Procedures and Flows HD � ✓ ✓ ✓ ✓ �

A.4.4.1 Introduction FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �

A.4.4.3 GW(PCEF) initiated IP-CAN Session termination

FC � ✓ ✓ ✓ ✓ �

A.4.4.4 IP-CAN Session Modification FC � ✓ ✓ ✓ ✓ �

A.4.4.4.1 IP-CAN Session Modification; GW(PCEF) initiated

FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �

A.5 3GPP Accesses (GERAN/UTRAN/E-UTRAN) - PMIP-based EPC

HD � ✓ ✓ ✓ ✓ �

A.5.0 General FC � ✓ ✓ ✓ ✓ �

A.5.1 High Level Requirements HD � ✓ ✓ ✓ ✓ �

A.5.1.0 General FC � ✓ ✓ ✓ ✓ �

A.5.1.1 QoS control FC � ✓ ✓ ✓ ✓ �

A.5.2 Architectural Model and Reference Points

HD � ✓ ✓ ✓ ✓ �


A.5.3 Functional Description HD � ✓ ✓ ✓ ✓ �

A.5.3.1 Overall Description HD � ✓ ✓ ✓ ✓ �

A.5.3.1.1 Binding mechanism FC � ✓ ✓ ✓ ✓ �

A.5.3.1.2 Credit management FC � ✓ ✓ ✓ ✓ �


Notes

(9 of 13)



A.5.3.1.3 Event triggers FC � ✓ ✓ ✓ ✓ �

A.5.3.2 Functional Entities HD � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �

A.5.3.2.3 Bearer Binding and Event Reporting Function (BBERF)

FC � ✓ ✓ ✓ ✓ �

A.5.3.3 Void NA � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �


NC � � ✓ ✓ ✓ CSG not supported.

A.5.4 PCC Procedures and Flows HD � ✓ ✓ ✓ ✓ �

A.5.4.1 Introduction FC � ✓ ✓ ✓ ✓ �

A.5.4.2 Gateway Control Session Establishment

FC � ✓ ✓ ✓ ✓ �

A.5.4.3 Gateway Control and QoS Rules Request

FC � ✓ ✓ ✓ ✓ �

A.5.4.4 Gateway Control and QoS Rules Provisioning

FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �

A.5.4.6 IP-CAN Session Modification HD � ✓ ✓ ✓ ✓ �

A.5.4.6.1 IP-CAN Session Modification; GW(PCEF) initiated

FC � ✓ ✓ ✓ ✓ �


FC � ✓ ✓ ✓ ✓ �

A.5.4.6.3 Void NA � ✓ ✓ ✓ ✓ �

Annex B (informative):

Usage of PCC in the visited network (Void)

HD ✓ ✓ ✓ ✓ ✓ This section is void as of Release 8

B.1 Introduction NC ✓ ✓ ✓ ✓ ✓ �

B.1.1 General aspects NC ✓ ✓ ✓ ✓ ✓ �

B.1.2 Charging related aspects NC ✓ ✓ ✓ ✓ ✓ �

B.1.2.1 Reporting NC ✓ ✓ ✓ ✓ ✓ �

B.1.2.2 Credit Control NC ✓ ✓ ✓ ✓ ✓ �

B.1.3 Policy control related aspects

NC ✓ ✓ ✓ ✓ ✓ �

B.1.4 Subscription related aspects NC ✓ ✓ ✓ ✓ ✓ �

B.1.5 Architectural aspects NC ✓ ✓ ✓ ✓ ✓ �


Notes

(10 of 13)



Integration Guide

B.1.5.1 Logical architecture of PCEF in the visited network

NC ✓ ✓ ✓ ✓ ✓ �

B.1.5.1.1 Functional Requirements for supporting PCC Rules in the visited network

NC ✓ ✓ ✓ ✓ ✓ �

B.1.5.1.2 Functional Requirements for Supporting On-line Charging in the visited network

NC ✓ ✓ ✓ ✓ ✓ �

B.1.6 Functional Entities NC ✓ ✓ ✓ ✓ ✓ �

B.1.6.1 Visited-PCEF NC ✓ ✓ ✓ ✓ ✓ �

B.1.6.2 SPR NC ✓ ✓ ✓ ✓ ✓ �

B.1.6.3 H-PCRF NC ✓ ✓ ✓ ✓ ✓ �

B.1.6.4 V-PCRF NC ✓ ✓ ✓ ✓ ✓ �

B.1.6.5 Proxy OCS NC ✓ ✓ ✓ ✓ ✓ �

B.2 Roaming Procedures and Flows

NC ✓ ✓ ✓ ✓ ✓ �

B.2.1 Introduction NC ✓ ✓ ✓ ✓ ✓ �

B2.2 V-PCEF to H-PCRF communication link establishment

NC ✓ ✓ ✓ ✓ ✓ �

B.2.3 V-PCRF rejection of a H-PCRF policy decision

NC ✓ ✓ ✓ ✓ ✓ �

Annex C (informative):

Void HD ✓ ✓ ✓ ✓ ✓ �

Annex D (informative):

Access specific aspects (Non-3GPP)

HD ✓ ✓ ✓ ✓ ✓ �

D.1 DOCSIS IP-CAN NC ✓ ✓ ✓ ✓ ✓ �

D.1.1 General NC ✓ ✓ ✓ ✓ ✓ �

D.1.1 High level requirements NC ✓ ✓ ✓ ✓ ✓ �

D.1.1.1 General NC ✓ ✓ ✓ ✓ ✓ �

D.1.1.2 Charging related requirements

NC ✓ ✓ ✓ ✓ ✓ �

D.1.1.3 Policy control requirements NC ✓ ✓ ✓ ✓ ✓ �

D.1.2 Architecture model and reference points

NC ✓ ✓ ✓ ✓ ✓ �

D.1.2.1 Reference points NC ✓ ✓ ✓ ✓ ✓ �

D.1.2.1.1 Rx reference point NC ✓ ✓ ✓ ✓ ✓ �

D.1.2.1.2 Gx reference point NC ✓ ✓ ✓ ✓ ✓ �

D.1.2.1.3 Void NC ✓ ✓ ✓ ✓ ✓ �

D.1.3 Functional description NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.1 Overall description NC ✓ ✓ ✓ ✓ ✓ �


Notes

(11 of 13)



D.1.3.1.1 Binding mechanism NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.2 Functional entities NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.2.1 Policy Control and Charging Rules Function (PCRF)

NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.2.1.1 Input for PCC decisions NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.2.2 Policy and Charging Enforcement Function (PCEF)

NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.2.3 Application Function (AF) NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.3 Policy and charging control rule

NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.3.1 General NC ✓ ✓ ✓ ✓ ✓ �

D.1.3.3.2 Policy and charging control rule operations

NC ✓ ✓ ✓ ✓ ✓ �

D.2 WiMAX IP-CAN NC ✓ ✓ ✓ ✓ ✓ �

D.2.1 High level requirements NC ✓ ✓ ✓ ✓ ✓ �

D.2.1.1 General NC ✓ ✓ ✓ ✓ ✓ �

D.2.1.2 Charging related requirements

NC ✓ ✓ ✓ ✓ ✓ �

D.2.1.3 Policy control requirements NC ✓ ✓ ✓ ✓ ✓ �

D.2.2 Architecture model and reference points

NC ✓ ✓ ✓ ✓ ✓ �

D.2.2.1 Reference points NC ✓ ✓ ✓ ✓ ✓ �

D.2.2.1.1 Rx reference point NC ✓ ✓ ✓ ✓ ✓ �

D.2.2.1.2 Gx reference point NC ✓ ✓ ✓ ✓ ✓ �

D.2.2.1.3 Sp reference point NC � ✓ ✓ ✓ ✓ This section was void in Release 7.

D.2.3 Functional description NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.1 Overall description NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.1.1 Binding mechanism NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.1.2 Credit management NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.1.3 Event triggers NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.2 Functional entities NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.2.1 Policy Control and Charging Rules Function (PCRF)

NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.2.2 Policy and Charging Enforcement Function (PCEF)

NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.2.3 Application Function (AF) NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.3 Policy and charging control rule

NC ✓ ✓ ✓ ✓ ✓ �


Notes

(12 of 13)



Integration Guide

D.2.3.3.1 General NC ✓ ✓ ✓ ✓ ✓ �

D.2.3.3.1 Policy and charging control rule operations

NC ✓ ✓ ✓ ✓ ✓ �

Annex E (informative)

Reference Scenario for the evolution of QoS control (Void)

NA ✓ ✓ ✓ ✓ ✓ Annex �Reference Scenario for the evolution of QoS control� removed in Release 10

Annex F (informative)

Co-existence between SBLP based (Release 6) and PCC based (Release 7 and later) policy control (Void)

HD ✓ ✓ ✓ ✓ ✓ Annex �Co-existence between SBLP based (Release 6) and PCC based (Release 7 and later) policy control� removed in Release 10

F.1 General NC ✓ ✓ ✓ ✓ ✓ Section �General� removed in Release 10

F.2 GPRS network scenario where the UE supports a previous Release

NA ✓ ✓ ✓ ✓ ✓ Section �GPRS network scenario where the UE supports a previous Release� removed in Release 10.

Annex G (informative)

PCC rule precedence configuration

NA ✓ ✓ ✓ ✓ ✓ �

Annex H (normative)

Access specific aspects (EPC-based Non-3GPP)

HD � ✓ ✓ ✓ ✓ �

H.1 General FC � ✓ ✓ ✓ ✓ �

H.2 EPC-based cdma2000 HRPD Access

NC � ✓ ✓ ✓ ✓ �

Annex I (informative)

Void NA � ✓ ✓ ✓ ✓ �

Annex J (informative)

Standardized QCI characteristics - rationale and principles

NA � ✓ ✓ ✓ ✓ �

Annex K (informative)

Limited PCC Deployment NA � ✓ ✓ ✓ ✓ �

Annex L (normative)

Limited PCC Deployment NC � ✓ ✓ ✓ ✓ �

Annex M (informative)

Handling of UE or network responsibility for the resource management of services

NA � ✓ ✓ ✓ ✓ �

Annex N (informative)

PCC usage for sponsored data connectivity

HD � � � ✓ ✓ �

N.1 General NC � � � ✓ ✓ �

N.2 Reporting for sponsored data connectivity

FC � � � ✓ ✓ �

Annex O (informative)

Change history NA ✓ ✓ ✓ ✓ ✓ �


Notes

(13 of 13)




The 5780 DSC has implemented a portion of 3GPP TS 29.335 User Data Convergence (UDC) v11.0.0 (2012-09);User Data Repository Access Protocol over the Ud interface; Stage 3 and User Data Convergence (UDC); Technical realization and information flows; Stage 2.

See section 3.11for more information.



• 3GPP 29.212 v7.11.0• 3GPP 29.212 v8.11.1 • 3GPP 29.212 v9.6.1 • 3GPP 29.212 v10.2.1 • 3GPP 29.212 v10.3.0 • 3GPP 29.212 v10.5.0 • 3GPP 29.212 v11.1.0 (See section 3GPP 29.212 compliancy-Release 11for

more information).

3GPP 29.212 compliancyTable 3-3 lists compliancy information for Technical Specification Group Core Network and Terminals Policy and Charging Control Over Gx Reference Point.

Table 3-3 3GPP 29.212 compliancy

Note � The 5780 DSC supports the TS 29.212 CR# 419 for Gn/Gp.


Notes

1 Scope NR ✓ ✓ ✓ ✓ ✓ �

2 References NR ✓ ✓ ✓ ✓ ✓ �

3 Definitions and abbreviations HD ✓ ✓ ✓ ✓ ✓ �

3.1 Definitions NR ✓ ✓ ✓ ✓ ✓ �

3.2 Abbreviations NR ✓ ✓ ✓ ✓ ✓ �

4 Gx reference point HD ✓ ✓ ✓ ✓ ✓ �

4.1 Overview NR ✓ ✓ ✓ ✓ ✓ �

4.2 Gx Reference model NR ✓ ✓ ✓ ✓ ✓ �

(1 of 18)



Integration Guide

4.3 PCC Rules HD ✓ ✓ ✓ ✓ ✓ �

4.3.1 PCC Rule Definition FC ✓ ✓ ✓ ✓ ✓ �

4.3.2 Operations on PCC Rules FC ✓ ✓ ✓ ✓ ✓ �

4.3.a IP flow mobility routing rules NC � � � ✓ ✓ �

4.3.a.1 Functional entities NC � � � ✓ ✓ �

4.3.a.2 IP flow mobility routing rule definition

NC � � � ✓ ✓ �

4.3.a.3 Operations on Routing rules NC � � � ✓ ✓ �

4.3.a.4 PCC procedures for IP flow mobility routing rule over Gx reference point

NC � � � ✓ ✓ �

4.3.a.4.1 Provisioning of IP flow mobility routing rules

NC � � � ✓ ✓ �

4.4 Functional elements HD ✓ ✓ ✓ ✓ ✓ �

4.4.1 PCRF FC ✓ ✓ ✓ ✓ ✓ �

4.4.2 PCEF NA ✓ ✓ ✓ ✓ ✓ �

4.5 PCC procedures over Gx reference point

HD ✓ ✓ ✓ ✓ ✓ �

4.5.1 Request for PCC rules PC ✓ ✓ ✓ ✓ ✓ xDSL IP-CAN Type handling not supported.

4.5.2 Provisioning of PCC rules FC ✓ ✓ ✓ ✓ ✓ �

4.5.2.1 Selecting a PCC rule for Uplink IP packets

PC ✓ ✓ ✓ ✓ ✓ CR 563 in Release 10 not supported. This CR indicates that a new RAR is not sent until an acknowledge for a previous RAR is returned

4.5.2.2 Selecting a PCC rule and IP-CAN Bearer for Downlink IP packets

NA ✓ ✓ ✓ ✓ ✓ �

4.5.2.3 Gate function FC ✓ ✓ ✓ ✓ ✓ �

4.5.2.4 Policy enforcement for Authorized QoS per PCC Rule

FC ✓ ✓ ✓ ✓ ✓ �

4.5.2.5 Usage Monitoring Control FC � � ✓ ✓ ✓ �

4.5.3 Provisioning of Event Triggers FC ✓ ✓ ✓ ✓ ✓ �

4.5.4 Provisioning of charging related information for the IP-CAN session

HD ✓ ✓ ✓ ✓ ✓ �

4.5.4.1 Provisioning of Charging Addresses

FC ✓ ✓ ✓ ✓ ✓ �

4.5.4.2 Provisioning of Default Charging Method

FC ✓ ✓ ✓ ✓ ✓ �

4.5.4.3 Void NA � � ✓ ✓ ✓ �

4.5.4.4 Provisioning of Access Network Charging Identifier

FC � ✓ ✓ ✓ ✓ �


Notes

(2 of 18)



4.5.5 Provisioning and Policy Enforcement of Authorized QoS

HD ✓ ✓ ✓ ✓ ✓ �

4.5.5.0 Overview FC ✓ ✓ ✓ ✓ ✓ �

4.5.5.0a Provisioning of authorized QoS per IP-CAN bearer

FC ✓ ✓ ✓ ✓ ✓ �

4.5.5.1 Policy enforcement for authorized QoS per IP-CAN bearer

NA ✓ ✓ ✓ ✓ ✓ �

4.5.5.2 Policy provisioning for authorized QoS per service data flow

FC ✓ ✓ ✓ ✓ ✓ �

4.5.5.3 Policy enforcement for authorized QoS per service data flow

NA ✓ ✓ ✓ ✓ ✓ �

4.5.5.4 Coordination of authorized QoS scopes in mixed mode

NR ✓ ✓ ✓ ✓ ✓ �

4.5.5.5 Provisioning of authorized QoS per QCI

FC ✓ ✓ ✓ ✓ ✓ �

4.5.5.6 Policy enforcement for authorized QoS per QCI

NA ✓ ✓ ✓ ✓ ✓ �

4.5.5.7 Provisioning of authorized QoS per APN

FC � ✓ ✓ ✓ ✓ �

4.5.5.8 Policy enforcement for authorized QoS per APN

NR � ✓ ✓ ✓ ✓ �

4.5.5.9 Provisioning of authorized QoS for the Default EPS Bearer

FC � ✓ ✓ ✓ ✓ �

4.5.5.10 Policy enforcement for authorized QoS of the Default EPS Bearer

NR � ✓ ✓ ✓ ✓ �

4.5.6 Indication of IP-CAN Bearer Termination Implications

FC ✓ ✓ ✓ ✓ ✓ �

4.5.7 Indication of IP-CAN Session Termination

FC ✓ ✓ ✓ ✓ ✓ �

4.5.8 Request for IP-CAN Bearer Termination

FC ✓ ✓ ✓ ✓ ✓ �

4.5.9 Request for IP-CAN Session Termination

FC ✓ ✓ ✓ ✓ ✓ �

4.5.10 Bearer Control Mode Selection FC ✓ ✓ ✓ ✓ ✓ �

4.5.11 Provisioning of Event Report Indication

FC � ✓ ✓ ✓ ✓ �

4.5.12 PCC Rule Error Handling FC ✓ ✓ ✓ ✓ ✓ �

4.5.13 Time of the day procedures FC ✓ ✓ ✓ ✓ ✓ �

4.5.14 Trace activation/deactivation NC � ✓ ✓ ✓ ✓ Trace activation/deactivation AVP is ignored.

4.5.15 IMS Emergency Session Support FC ✓ ✓ ✓ ✓ ✓ �

4.5.15.1 Functional Entities FC � � ✓ ✓ ✓ �


Notes

(3 of 18)



Integration Guide

4.5.15.2 PCC procedures for Emergency services over Gx reference point

FC � � ✓ ✓ ✓ �

4.5.15.2.1 Request for PCC Rules for Emergency services

FC � � ✓ ✓ ✓ �

4.5.15.2.2 Provisioning of PCC Rules for Emergency services

FC � � ✓ ✓ ✓ �

4.5.15.2.2.1 Provisioning of PCC Rules at Gx session establishment

FC � � ✓ ✓ ✓ �

4.5.15.2.2.2 Provisioning of PCC Rules for Emergency Services

FC � � ✓ ✓ ✓ �

4.5.15.2.3 Removal of PCC Rules for Emergency Services

FC � � ✓ ✓ ✓ �

4.5.15.2.4 Removal of PCC Rules at Gx session termination

FC � � ✓ ✓ ✓ �

4.5.16 Requesting Usage Monitoring Control

C � � ✓ ✓ ✓ The threshold level provided in the Granted-Service-Unit AVP does not support uplink and downlink volume.

4.5.17 Reporting Accumulated Usage FC � � ✓ ✓ ✓ �

4.5.17.1 Usage Threshold Reached FC � � ✓ ✓ ✓ �

4.5.17.2 PCC Rule Removal FC � � ✓ ✓ ✓ �

4.5.17.3 Usage Monitoring Disabled FC � � ✓ ✓ ✓ �

4.5.17.4 IP-CAN Session Termination FC � � ✓ ✓ ✓ �

4.5.17.5 PCRF Requested Usage Report FC � � ✓ ✓ ✓ �

4.5.18 IMS Restoration Support FC � � ✓ ✓ ✓ �

4.5.19 Multimedia Priority Support NC � � � ✓ ✓ �

4.5.19.1 PCC Procedures for Multimedia Priority services over Gx reference point

NC � � � ✓ ✓ �

4.5.19.1.1 Provisioning of PCC Rules for Multimedia Priority Services

NC � � � ✓ ✓ �

4.5.19.1.2 Invocation/Revocation of Priority EPS Bearer Services

NC � � � ✓ ✓ �

4.5.19.1.3 Invocation/Revocation of IMS Multimedia Priority Services

NC � � � ✓ ✓ �

4.5.20 Sponsored Data Connectivity FC � � � ✓ ✓ �

4.5.21 PCRF Failure and Restoration NA � � � ✓ ✓ �

4a Gxx reference points HD � ✓ ✓ ✓ ✓ �

4a.1 Overview NR � ✓ ✓ ✓ ✓ �

4a.2 Gxx Reference model NR � ✓ ✓ ✓ ✓ �

4a.3 Quality of Service Control Rules HD � ✓ ✓ ✓ ✓ �


Notes

(4 of 18)



4a.3.1 Quality of Service Control Rule Definition

FC � ✓ ✓ ✓ ✓ �

4a.3.2 Operations on QoS Rules FC � ✓ ✓ ✓ ✓ �

4a.4 Functional elements HD � ✓ ✓ ✓ ✓ �

4a.4.1 PCRF FC � ✓ ✓ ✓ ✓ �

4a.4.2 BBERF NA � ✓ ✓ ✓ ✓ �

4a.5 PCC procedures over Gxx reference points

HD � ✓ ✓ ✓ ✓ �

4a.5.1 Gateway control and QoS Rules Request

FC � ✓ ✓ ✓ ✓ �

4a.5.2 Gateway control and QoS Rules Provision

HD � ✓ ✓ ✓ ✓ �

4a.5.2.1 Overview PC � ✓ ✓ ✓ ✓ CR 563 in Release 10 not supported. This CR indicates to wait for an an answer of a previous RAR before sending out a new RAR

4a.5.3 Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

4a.5.4 Request for Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

4a.5.5 QoS Control Rule error handling FC � ✓ ✓ ✓ ✓ �

4a.5.6 Gateway Control session to Gx session linking

PC � ✓ ✓ ✓ ✓ The 5780 DSC ignores CoA-IP-Address.

4a.5.7 Multiple BBF support HD � ✓ ✓ ✓ ✓ �

4a.5.7.1 General PC � � � ✓ ✓ �

4a.5.7.2 Handling of two BBFs associated with the same IP-CAN session during handover

PC � � � ✓ ✓ �

4a.5.7.3 Handling of multiple BBFs with flow mobility within IP-CAN session

PC � � � ✓ ✓ �

4a.5.8 Provisioning of Event Triggers FC � ✓ ✓ ✓ ✓ �

4a.5.9 Bearer Control Mode Selection FC � ✓ ✓ ✓ ✓ �

4a.5.10 Provisioning and Policy Enforcement of Authorized QoS

HD � ✓ ✓ ✓ ✓ �

4a.5.10.1 Provisioning of authorized QoS for the Default EPS Bearer

FC � ✓ ✓ ✓ ✓ �

4a.5.10.2 Policy enforcement for authorized QoS of the Default EPS Bearer

NA � ✓ ✓ ✓ ✓ �

4a.5.10.3 Provisioning of authorized QoS per APN

FC � ✓ ✓ ✓ ✓ �

4a.5.10.4 Policy provisioning for authorized QoS per service data flow

FC � ✓ ✓ ✓ ✓ �


Notes

(5 of 18)



Integration Guide

4a.5.10.5 Policy enforcement for authorized QoS per service data flow

NA � ✓ ✓ ✓ ✓ �

4a.5.11 Trace activation/deactivation NC � ✓ ✓ ✓ ✓ Trace activation/deactivation AVP is ignored.

4a.5.12 IMS Emergency Session Support FC � � ✓ ✓ ✓ �

4a.5.12.1 PCC procedures for Emergency services over Gxx reference point

FC � � ✓ ✓ ✓ �

4a.5.12.1.1 Gateway control and QoS Rules request for Emergency services

FC � � ✓ ✓ ✓ �

4a.5.12.1.2 Provisioning of QoS Rules for Emergency services

FC � � ✓ ✓ ✓ �

4a.5.12.1.2.1 Provisioning of QoS Rules at Gxx session establishment

FC � � ✓ ✓ ✓ �

4a.5.12.1.2.2 Provisioning of QoS Rules for Emergency services

FC � � ✓ ✓ ✓ �

4a.5.12.1.2.1 Provisioning of QoS Rules at Gxx session establishment

FC � � ✓ ✓ ✓ �

4a.5.12.1.2.2 Provisioning of QoS Rules for Emergency services

FC � � ✓ ✓ ✓ �

4a.5.12.2 Gateway Control Session to Gx session linking

FC � � ✓ ✓ ✓ �

4a.5.12.3 Removal of QoS Rules for Emergency Services

FC � � ✓ ✓ ✓ �

4a.5.12.4 Termination of Gateway Control session for Emergency Services

FC � � ✓ ✓ ✓ �

4a.5.13 Time of the day procedures FC � ✓ ✓ ✓ ✓ �

4a.5.14 Multimedia Priority Support NC � � � ✓ ✓ �

4a.5.14.1 PCC Procedures for Multimedia Priority services over Gxx reference point

NC � � � ✓ ✓ �

4a.5.14.1.1 Provisioning of QoS Rules for Multimedia Priority Services

NC � � � ✓ ✓ �

4a.5.14.1.2 Invocation/Revocation of Priority EPS Bearer Services

NC � � � ✓ ✓ �

4a.5.14.1.3 Invocation/Revocation of IMS Multimedia Priority Services

NC � � � ✓ ✓ �

4a.5.15 PCRF Failure and Restoration NA � � � ✓ ✓ �

5 Gx protocol HD ✓ ✓ ✓ ✓ ✓ �

5.1 Protocol support FC ✓ ✓ ✓ ✓ ✓ �

5.2 Initialization, maintenance and termination of connection and session

FC ✓ ✓ ✓ ✓ ✓ �

5.3 Gx specific AVPs FC ✓ ✓ ✓ ✓ ✓ �


Notes

(6 of 18)



5.3.1 Bearer-Usage AVP (3GPP-GPRS and 3GPP-EPS access types)

PC ✓ ✓ ✓ ✓ ✓ Supported on Default-Bearer in 3GPP-GPRS and 3GPP-EPS access types.

5.3.2 Charging-Rule-Install AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.3 Charging-Rule-Remove AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.4 Charging-Rule-Definition AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.5 Charging-Rule-Base-Name AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.6 Charging-Rule-Name AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.7 Event-Trigger AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.8 Metering-Method AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.9 Offline AVP (All access types) FC ✓ ✓ ✓ ✓ ✓ �

5.3.10 Online AVP (All access types) FC ✓ ✓ ✓ ✓ ✓ �

5.3.11 Precedence AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.12 Reporting-Level AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.13 TFT-Filter AVP (3GPP-GPRS access type only)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.14 TFT-Packet-Filter-Information AVP (3GPP-GPRS access type only)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.15 ToS-Traffic-Class AVP (All access types)

C ✓ ✓ ✓ ✓ ✓ No support for substrings in this AVP.

5.3.16 QoS-Information AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.17 QoS-Class-Identifier AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.18 Charging-Rule-Report AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.19 PCC-Rule-Status AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.20 Bearer-Identifier AVP (Applicable access type 3GPP-GPRS)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.21 Bearer-Operation AVP (Applicable access type 3GPP-GPRS)

FC ✓ ✓ ✓ ✓ ✓ �


Notes

(7 of 18)



Integration Guide

5.3.22 Access-Network-Charging-Identifier-Gx AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ The 5780 DSC does not allow modification to Access-Network-Charging-Identifier.

5.3.23 Bearer-Control-Mode AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.24 Network-Request-Support AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.25 Guaranteed-Bitrate-DL AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.26 Guaranteed-Bitrate-UL AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.27 IP-CAN-Type AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.28 QoS-Negotiation AVP (3GPP-GPRS Access Type only)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.29 QoS-Upgrade AVP (3GPP-GPRS Access Type only)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.30 Event-Report-Indication AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5.3.31 RAT-Type AVP FC � ✓ ✓ ✓ ✓ �

5.3.32 Allocation-Retention-Priority AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5.3.33 CoA-IP-Address AVP (All access types)

NC � ✓ ✓ ✓ ✓ CoA-IP-Address AVP is ignored.

5.3.34 Tunnel-Header-Filter AVP (All access types)

NC � ✓ ✓ ✓ ✓ Tunnel-Header-Filter AVP is ignored.

5.3.35 Tunnel-Header-Length AVP (All access types)

NC � ✓ ✓ ✓ ✓ Tunnel-Header-Length AVP is ignored

5.3.36 Tunnel-Information AVP (All access types)

NC � ✓ ✓ ✓ ✓ Tunnel-Information AVP is ignored.

5.3.37 CoA-Information AVP (All access types)

NC � ✓ ✓ ✓ ✓ CoA-Information AVP is ignored.

5.3.38 Rule-Failure-Code AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.39 APN-Aggregate-Max-Bitrate-DL AVP

FC � ✓ ✓ ✓ ✓ �

5.3.40 APN-Aggregate-Max-Bitrate-UL AVP

FC � ✓ ✓ ✓ ✓ �

5.3.41 Revalidation-Time (ALL Access Types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.42 Rule-Activation-Time (ALL Access Types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.43 Rule-Deactivation-Time (ALL Access Types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.44 Session-Release-Cause (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.45 Priority-Level AVP (All access types)

FC � ✓ ✓ ✓ ✓ �


Notes

(8 of 18)



5.3.46 Pre-emption-Capability AVP FC � ✓ ✓ ✓ ✓ �

5.3.47 Pre-emption-Vulnerability AVP FC � ✓ ✓ ✓ ✓ �

5.3.48 Default-EPS-Bearer-QoS AVP FC � ✓ ✓ ✓ ✓ �

5.3.49 AN-GW-Address AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5.3.50 Resource-Allocation-Notification AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5.3.51 Security-Parameter-Index AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.52 Flow-Label AVP (All access types) FC ✓ ✓ ✓ ✓ ✓ �

5.3.53 Flow-Information AVP (All access types)

FC ✓ ✓ ✓ ✓ ✓ �

5.3.54 Packet-Filter-Content AVP FC � ✓ ✓ ✓ ✓ For uplink filters (direction IN), the source address must be the UE IP. For downlink filters (direction OUT), the destination address must be the UE IP.

5.3.55 Packet-Filter-Identifier AVP FC � ✓ ✓ ✓ ✓ �

5.3.56 Packet-Filter-Information AVP FC � ✓ ✓ ✓ ✓ �

5.3.57 Packet-Filter-Operation AVP FC � ✓ ✓ ✓ ✓ �

5.3.58 PDN-Connection-ID AVP NC � � ✓ ✓ ✓ �

5.3.59 Monitoring-Key AVP FC � � ✓ ✓ ✓ �

5.3.60 Usage-Monitoring-Information AVP

FC � � ✓ ✓ ✓ �

5.3.61 Usage-Monitoring-Level AVP FC � � ✓ ✓ ✓ �

5.3.62 Usage-Monitoring-Report AVP FC � � ✓ ✓ ✓ �

5.3.63 Usage-Monitoring-Support AVP FC � � ✓ ✓ ✓ �

5.3.64 CSG-Information-Reporting AVP NC � � ✓ ✓ ✓ �

5.3.65 Flow-Direction AVP FC � � ✓ ✓ ✓ �

5.3.66 Packet-Filter-Usage AVP (All access types)

FC � � ✓ ✓ ✓ �

5.3.67 Charging-Correlation-Indicator AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5.3.68 Routing-Rule-Install AVP NC � � � ✓ ✓ �

5.3.69 Routing-Rule-Remove AVP NC � � � ✓ ✓ �

5.3.70 Routing-Rule-Definition AVP NC � � � ✓ ✓ �

5.3.71 Routing-Rule-Identifier AVP NC � � � ✓ ✓ �

5.3.72 Routing-Filter AVP NC � � � ✓ ✓ �

5.3.73 Routing-IP-Address AVP NC � � � ✓ ✓ �


Notes

(9 of 18)



Integration Guide

5.3.74 Maximum-Bandwidth AVP (3GPP-GPRS and 3GPP-EPS access types)

NC � � � � ✓ �

5.3.75 Max-Supported-Bandwidth-DL AVP (3GPP-GPRS and 3GPP-EPS access types)

NC � � � � ✓ �

5.3.76 Max-Supported-Bandwidth-UL AVP (3GPP-GPRS and 3GPP-EPS access types)

NC � � � � ✓ �

5.4 Gx re-used AVPs HD ✓ ✓ ✓ ✓ ✓ �

3GPP-RAT-Type FC ✓ ✓ ✓ ✓ ✓ �

3GPP-SGSN-Address FC ✓ ✓ ✓ ✓ ✓ �

3GPP-SGSN-IPv6-Address FC ✓ ✓ ✓ ✓ ✓ �

3GPP-SGSN-MCC-MNC FC ✓ ✓ ✓ ✓ ✓ �

3GPP-User-Location-Info FC ✓ ✓ ✓ ✓ ✓ �

3GPP2-BSID FC ✓ ✓ ✓ ✓ ✓ �

Access-Network-Charging-Address

FC ✓ ✓ ✓ ✓ ✓ �

Access-Network-Charging-Identifier-Value

FC ✓ ✓ ✓ ✓ ✓ The 5780 DSC does not allow modification to Access-Network-Charging-Identifier.

AF-Charging-Identifier FC ✓ ✓ ✓ ✓ ✓ The AF-Charging-Identifier is set in the charging rule definition only if the Reporting-Level is set to SERVICE_IDENTIFIER_LEVEL.


Notes

(10 of 18)



5.4 (Continued)

Application-Service-Provider-Identity

NC � � � ✓ ✓ �

Called-Station-ID FC ✓ ✓ ✓ ✓ ✓ �

CC-Request-Number FC ✓ ✓ ✓ ✓ ✓ �

CC-Request-Type FC ✓ ✓ ✓ ✓ ✓ �

Charging-Information FC ✓ ✓ ✓ ✓ ✓ �

User-CSG-Information NC � � ✓ ✓ ✓ �

Final-Unit-Indication FC ✓ ✓ ✓ ✓ ✓ �

Flow-Description FC ✓ ✓ ✓ ✓ ✓ �

Flows FC ✓ ✓ ✓ ✓ ✓ �

Flow-Status FC ✓ ✓ ✓ ✓ ✓ �

Framed-IP-Address FC ✓ ✓ ✓ ✓ ✓ �

Framed-IPv6-Prefix FC ✓ ✓ ✓ ✓ ✓ �

Granted-Service-Unit NA � � ✓ ✓ ✓ �

Logical-Access-ID NC � � � ✓ ✓ �

Max-Requested-Bandwidth-UL FC ✓ ✓ ✓ ✓ ✓ �

Max-Requested-Bandwidth-DL FC � � � ✓ ✓ �

Physical-Access-ID NC ✓ ✓ �

RAI FC ✓ ✓ ✓ ✓ ✓ The 5780 DSC processes the RAI AVP as per the 3GPP specifications; however, you can only write 5780 DSC rules for the RAI AVP instead of the LAI and RAC encoded in the RAI AVP.

Rating-Group FC ✓ ✓ ✓ ✓ ✓ �

Service-Identifier FC ✓ ✓ ✓ ✓ ✓ �

Sponsor-Identity � � � ✓ ✓

Subscription-Id FC ✓ ✓ ✓ ✓ ✓ �

Supported-Features FC ✓ ✓ ✓ ✓ ✓ �

Used-Service-Unit NC � � ✓ ✓ ✓ �

Trace-Data NC ✓ ✓ ✓ ✓ ✓ Trace-Data AVP is ignored.

Trace-Reference NC ✓ ✓ ✓ ✓ ✓ Trace-Reference AVP is ignored.

User-Equipment-Info FC ✓ ✓ ✓ ✓ ✓ �

3GPP-MS-TimeZone PC ✓ ✓ ✓ ✓ ✓ �

AF-Signalling-Protocol FC � � ✓ ✓ ✓ �

5.4.1 Use of the Supported-Features AVP on the Gx reference point

FC � ✓ ✓ ✓ ✓ �


Notes

(11 of 18)



Integration Guide

5.5 Gx specific Experimental-Result-Code AVP values

HD ✓ ✓ ✓ ✓ ✓ �

5.5.1 General FC ✓ ✓ ✓ ✓ ✓ �

5.5.2 Success FC ✓ ✓ ✓ ✓ ✓ �

5.5.3 Permanent Failures FC ✓ ✓ ✓ ✓ ✓ �

5.5.4 Transient Failures FC ✓ ✓ ✓ ✓ ✓ �

5.6 Gx Messages HD ✓ ✓ ✓ ✓ ✓ �

5.6.1 Gx Application FC ✓ ✓ ✓ ✓ ✓ �

5.6.2 CC-Request (CCR) Command FC ✓ ✓ ✓ ✓ ✓ �

5.6.3 CC-Answer (CCA) Command FC ✓ ✓ ✓ ✓ ✓ �

5.6.4 Re-Auth-Request (RAR) Command

FC ✓ ✓ ✓ ✓ ✓ �

5.6.5 Re-Auth-Answer (RAA) Command FC ✓ ✓ ✓ ✓ ✓ �

5a Gxx protocols HD ✓ ✓ ✓ ✓ ✓ �

5a.1 Protocol support FC ✓ ✓ ✓ ✓ ✓ �

5a.2 Initialization, maintenance and termination of connection and session

FC ✓ ✓ ✓ ✓ ✓ �

5a.3 Gxx specific AVPs HD � ✓ ✓ ✓ ✓ �

5a.3.1 QoS-Rule-Install AVP (All access types)

C � ✓ ✓ ✓ ✓ Tunnel-Information in QoS-Rule-Install not supported.

5a.3.2 QoS-Rule-Remove AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5a.3.3 QoS-Rule-Definition AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5a.3.4 QoS-Rule-Name AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5a.3.5 QoS-Rule-Report AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5a.3.6 Session-Linking-Indicator AVP (All access types)

FC � ✓ ✓ ✓ ✓ �

5a.3.7 QoS-Rule-Base-Name AVP (All access types)

NC � � ✓ ✓ ✓ �

5a.4 Gxx re-used AVPs HD � ✓ ✓ ✓ ✓ �

3GPP-MS-TimeZone FC � ✓ ✓ ✓ ✓ �

3GPP-SGSN-Address NA � ✓ ✓ ✓ ✓ The 5780 DSC does not persist or make this AVP available in rules on Gxx.


Notes

(12 of 18)



5a.4 (continued)

3GPP-SGSN-IPv6-Address NA � ✓ ✓ ✓ ✓ The 5780 DSC does not persist or make this AVP available in rules on Gxx.

AN-GW-Address FC � ✓ ✓ ✓ ✓ �

3GPP-SGSN-MCC-MNC FC � ✓ ✓ ✓ ✓ �

3GPP-User-Location-Info FC � ✓ ✓ ✓ ✓ �

3GPP2-BSID FC � ✓ ✓ ✓ ✓ �

Access-Network-Charging-Identifier-Value

FC � ✓ ✓ ✓ ✓ �

Allocation-and-Retention-Priority

FC � ✓ ✓ ✓ ✓ �

APN-Aggregate-Max-Bitrate-DL FC � ✓ ✓ ✓ ✓ �

APN-Aggregate-Max-Bitrate-UL FC � ✓ ✓ ✓ ✓ �

Bearer-Control-Mode FC � ✓ ✓ ✓ ✓ �

Called-Station-ID FC � ✓ ✓ ✓ ✓ �

PDN-Connection-ID FC � � ✓ ✓ ✓ �

CC-Request-Number FC � ✓ ✓ ✓ ✓ �

CC-Request-Type FC � ✓ ✓ ✓ ✓ �

User-CSG-Information NC � � ✓ ✓ ✓ �

Event-Trigger FC � ✓ ✓ ✓ ✓ �

Flow-Description FC � ✓ ✓ ✓ ✓ Based on the operating mode of the 5780 DSC PCRF (that is, not March 2009 compliance).

Flow-Information FC � ✓ ✓ ✓ ✓ Based on the operating mode of the 5780 DSC PCRF (that is, not March 2009 compliance).

Flow-Label FC � ✓ ✓ ✓ ✓ �

Framed-IP-Address FC � ✓ ✓ ✓ ✓ �

Framed-IPv6-Prefix FC � ✓ ✓ ✓ ✓ �

Guaranteed-Bitrate-DL FC � ✓ ✓ ✓ ✓ �

Guaranteed-Bitrate-UL FC � ✓ ✓ ✓ ✓ �

IP-CAN-Type FC � ✓ ✓ ✓ ✓ �

Max-Requested-Bandwidth-UL FC � ✓ ✓ ✓ ✓ �

Max-Requested-Bandwidth-DL FC � ✓ ✓ ✓ ✓ �


Notes

(13 of 18)



Integration Guide

5a.4 (continued)

Packet-Filter-Content FC � ✓ ✓ ✓ ✓ For uplink filters (direction IN), the source address must be the UE IP. For downlink filters (direction OUT), the destination address must be the UE IP.

Packet-Filter-Identifier FC � ✓ ✓ ✓ ✓ �

Packet-Filter-Information FC � ✓ ✓ ✓ ✓ �

Packet-Filter-Operation FC � ✓ ✓ ✓ ✓ �

Packet-Filter-Usage FC � � ✓ ✓ ✓ �

Network-Request-Support FC � ✓ ✓ ✓ ✓ �

Precedence FC � ✓ ✓ ✓ ✓ �

PCC-Rule-Status FC � ✓ ✓ ✓ ✓ �

QoS-Class-Identifier FC � ✓ ✓ ✓ ✓ �

QoS-Information FC � ✓ ✓ ✓ ✓ �

Default-EPS-Bearer-QoS FC � ✓ ✓ ✓ ✓ �

RAI FC � ✓ ✓ ✓ ✓ The 5780 DSC processes the RAI AVP as per the 3GPP specifications; however, you can only write 5780 DSC rules for the RAI AVP instead of the LAI and RAC encoded in the RAI AVP.

RAT-Type FC � ✓ ✓ ✓ ✓ �

Resource-Allocation-Notification FC � ✓ ✓ ✓ ✓ �

Rule-Failure-Code FC � ✓ ✓ ✓ ✓ �

Security-Parameter-Index FC � ✓ ✓ ✓ ✓ �

Session-Release-Cause FC � ✓ ✓ ✓ ✓ �

Subscription-Id FC � ✓ ✓ ✓ ✓ �

Supported-Features FC � ✓ ✓ ✓ ✓ �

ToS-Traffic-Class C � ✓ ✓ ✓ ✓ No support for substrings in this AVP.

Trace-Data NC � ✓ ✓ ✓ ✓ Trace-Data AVP is ignored

Trace-Reference NC � ✓ ✓ ✓ ✓ Trace-Reference AVP is ignored

Tunnel-Header-Filter NC � ✓ ✓ ✓ ✓ Tunnel-Header-Filter is ignored

Tunnel-Header-Length NC � ✓ ✓ ✓ ✓ Tunnel-Header-Length is ignored

Tunnel-Information NC � ✓ ✓ ✓ ✓ Tunnel-Information is ignored


Notes

(14 of 18)



5a.4 (continued)

User-Equipment-Info FC � ✓ ✓ ✓ ✓ �

5a.4.1 Use of the Supported-Features AVP on the Gxx reference point

FC � ✓ ✓ ✓ ✓ �

5a.5 Gxx specific Experimental-Result-Code AVP values

FC � ✓ ✓ ✓ ✓ �

5a.6 Gxx Messages HD � ✓ ✓ ✓ ✓ �

5a.6.1 Gxx Application FC � ✓ ✓ ✓ ✓ �

5a.6.2 CC-Request (CCR) Command PC � ✓ ✓ ✓ ✓ Logical-access-id / physical-access-id not supported.

5a.6.3 CC-Answer (CCA) Command FC � ✓ ✓ ✓ ✓ �

5a.6.4 Re-Auth-Request (RAR) Command

FC � ✓ ✓ ✓ ✓ �

5a.6.5 Re-Auth-Answer (RAA) Command FC � ✓ ✓ ✓ ✓ �

Annex A (normative):

Access specific aspects (GPRS) HD � ✓ ✓ ✓ ✓ �

A.1 Scope NR � ✓ ✓ ✓ ✓ �

A.2 Reference Model NR � ✓ ✓ ✓ ✓ �

A.2 Functional Elements HD � ✓ ✓ ✓ ✓ �

A.2.1 PCRF NR � ✓ ✓ ✓ ✓ �

A.3 PCC procedures HD � ✓ ✓ ✓ ✓ �

A.3.1 Request for PCC rules FC � ✓ ✓ ✓ ✓ �

A.3.2 Provisioning of PCC rules FC � ✓ ✓ ✓ ✓ �

A.3.2.1 PCC rule request for services not known the PCRF

FC � ✓ ✓ ✓ ✓ �

A.3.2.2 Selecting a PCC rule and IP-CAN Bearer for Downlink IP packets

NA � ✓ ✓ ✓ ✓ �

A.3.3 Provisioning and Policy Enforcement of Authorized QoS

FC � ✓ ✓ ✓ ✓ �

A.3.3.0 Overview FC � ✓ ✓ ✓ ✓ �

A.3.3.1 Provisioning of authorized QoS per IP-CAN bearer

FC � ✓ ✓ ✓ ✓ �

A.3.3.2 Policy enforcement for authorized QoS per IP-CAN bearer

NA � ✓ ✓ ✓ ✓ �

A.3.3.2a Policy provisioning for authorized QoS per service data flow

FC � ✓ ✓ ✓ ✓ �

A.3.3.3 Policy enforcement for authorized QoS per service data flow

NA � ✓ ✓ ✓ ✓ �

A.3.3.3a Coordination of authorized QoS scopes in mixed mode

FC � ✓ ✓ ✓ ✓ �


Notes

(15 of 18)



Integration Guide

A.3.3.3b Provisioning of authorized QoS per QCI

FC � ✓ ✓ ✓ ✓ �

A.3.3.4 Policy enforcement for authorized QoS per QCI

NA � ✓ ✓ ✓ ✓ �

A.3.3.5 Handling of maximum QoS support

NA � � � � ✓ �

A.3.4 Indication of IP-CAN Bearer Termination Implications

FC � ✓ ✓ ✓ ✓ �

A.3.5 FC � ✓ ✓ ✓ ✓ �

A.3.6 Request for IP-CAN Bearer Termination

FC � ✓ ✓ ✓ ✓ �

A.3.7 Request for IP-CAN Session Termination

FC � ✓ ✓ ✓ ✓ �

A.3.8 Bearer Control Mode Selection FC � ✓ ✓ ✓ ✓ The 5780 DSC PCRF provides flexible framework to define the Bearer-Control-Mode (for example, based on APN, Network-Request-Support)

A.3.9 Bearer Binding Mechanism FC � ✓ ✓ ✓ ✓ �

A.3.10 Void NR � ✓ ✓ ✓ ✓ �

A.3.11 PCC Rule Error Handling FC � ✓ ✓ ✓ ✓ �

A.3.12 IMS Emergency Session Support FC � � ✓ ✓ ✓ The 5780 DSC does not support emergency calls when the subscriber identification is not provided.

A.3.12.1 Request of PCC Rules for an Emergency services

FC � � ✓ ✓ ✓ �

A.3.12.2 Provisioning of PCC Rules for an Emergency services

FC � � ✓ ✓ ✓ �

A.3.13 Removal of PCC Rules for Emergency Services

FC � � ✓ ✓ ✓ �

A.3.14 Removal of PCC Rules at Gx session termination

FC � � ✓ ✓ ✓ �

A.3.15 IMS Restoration Support FC � � ✓ ✓ ✓ �

A.3.16 Provisioning of CSG information reporting indication

NC � � ✓ ✓ ✓ �

A.3.17 Packet-Filter-Usage AVP PC � � ✓ ✓ ✓ �

A.4 QoS Mapping HD � ✓ ✓ ✓ ✓ �

A.4.1 QCI to QoS parameter mapping FC � ✓ ✓ ✓ ✓ �

A.4.2 GPRS ARP to UMTS ARP parameter mapping

NA � � ✓ ✓ ✓ �

Annex B (normative):

Access specific aspects, 3GPP (GERAN/UTRAN/E-UTRAN) EPS

HD � ✓ ✓ ✓ ✓ �


Notes

(16 of 18)



B.1 Scope NR � ✓ ✓ ✓ ✓ �

B.2 Functional Elements HD � ✓ ✓ ✓ ✓ �

B.2.1 PCRF NA � ✓ ✓ ✓ ✓ �

B.2.2 PCEF NA � ✓ ✓ ✓ ✓ �

B.2.3 BBERF NA � ✓ ✓ ✓ ✓ �

B.3 PCC procedures FC � ✓ ✓ ✓ ✓ �

B.3.1 Request for PCC and/or QoS rules NR � ✓ ✓ ✓ ✓ �

B.3.2 Provisioning of PCC and/or QoS rules

C � ✓ ✓ ✓ ✓ Only supported on Default-Bearer in EPS.

B.3.3 Provisioning and Policy Enforcement of Authorized QoS

HD � ✓ ✓ ✓ ✓ �

B.3.3.1 Provisioning of authorized QoS per APN

NR � ✓ ✓ ✓ ✓ �

B.3.3.2 Policy enforcement for authorized QoS per APN

NR � ✓ ✓ ✓ ✓ �

B.3.3.3 QoS handling for interoperation with Gn/Gp SGSN

FC � ✓ ✓ ✓ ✓ �

B.3.3.4 Handling of maximum QoS support

FC � ✓ ✓ ✓ ✓ �

B.3.4 Packet-Filter-Information AVP NA � ✓ ✓ ✓ ✓ �

B.3.5 Bearer Control Mode Selection FC � ✓ ✓ ✓ ✓ �

B.3.6 Trace activation/deactivation at P-GW

NC � ✓ ✓ ✓ ✓ Trace activation/deactivation AVP is ignored.

B.3.7 IMS Restoration Support FC � � ✓ ✓ ✓ �

B.3.8 Void NA � � ✓ ✓ ✓ �

B.3.9 Packet-Filter-Usage AVP PC � � ✓ ✓ ✓ �

B.3.10 User CSG Information Reporting NC � � ✓ ✓ ✓ �

B.3.11 Request of IP-CAN Bearer Termination

FC � � ✓ ✓ ✓ �

Annex C (informative):

Mapping table for type of access networks

HD � ✓ ✓ ✓ ✓ �

Annex D (normative):

Access specific aspects (EPC-based Non-3GPP)

HD � ✓ ✓ ✓ ✓ �

D.1 Scope NA � ✓ ✓ ✓ ✓ �

D.2 EPC-based e-HRPD Access HD � ✓ ✓ ✓ ✓ �

D.2.1 General NA � ✓ ✓ ✓ ✓ �

D.2.2 Gxa procedures HD � ✓ ✓ ✓ ✓ �

D.2.2.1 Request for QoS rules FC � ✓ ✓ ✓ ✓ �

D.2.2.2 Provisioning of QoS rules HD � ✓ ✓ ✓ ✓ �


Notes

(17 of 18)



Integration Guide

3GPP 29.212 compliancy-Release 11The 5780 DSC has implemented a portion of 3GPP TS 29.212 V11.1.0 (2011-06), Policy and Charging Control over Gx/Sd reference point, including the following Sd-specific Diameter AVPs:

• ADC-Rule-Install• ADC-Rule-Base-Name• ADC-Rule-Remove

ADC-Rule-Install AVP

The ADC-Rule-Install AVP (AVP code 1092) is of type Grouped, and it is used to activate, install or modify ADC rules as instructed from the PCRF to the TDF. The ADC-Rule-Base-Name AVP is a reference that may be used for activating a group of ADC rules predefined at the TDF.

AVP Format:

ADC-Rule-Install ::= < AVP Header: 1092 >

*[ ADC-Rule-Base-Name ]

*[ AVP ]

D.2.2.2.1 QoS rule request for services not known the PCRF

FC � ✓ ✓ ✓ ✓ �

D.2.2.3 Provisioning and Policy Enforcement of Authorized QoS

HD � ✓ ✓ ✓ ✓ �

D.2.2.3.1 Provisioning of authorized QoS FC � ✓ ✓ ✓ ✓ �

D.2.2.3.2 Policy enforcement for authorized QoS

NA � ✓ ✓ ✓ ✓ �

D.2.3 Bearer Control Mode Selection FC � ✓ ✓ ✓ ✓ �

D.2.4 QoS Mapping HD � ✓ ✓ ✓ ✓ �

D.2.4.1 QCI to e-HRPD QoS parameter mapping

FC � ✓ ✓ ✓ ✓ The user can write 5780 DSC rules.

Annex E (informative):

Change history NR ✓ ✓ ✓ ✓ ✓ �


Notes

(18 of 18)

Note 1 � The 5780 DSC has only implemented the PUSH mechanism. The 5780 DSC installs one or more ADC rules on the TDF (Traffic Detection Function).

Note 2 � The 5780 DSC has not implemented the ADC-specific Event trigger. There is one for Application Start/Stop.

Note 3 � The 5780 DSC current operation is only binds to NASREQ sessions.



ADC-Rule-Base-Name AVP

The ADC-Rule-Base-Name AVP (AVP code 1095) is of type UTF8String, and it indicates the name of a pre defined group of ADC rules residing at the TDF.

ADC-Rule-Remove AVP

The ADC-Rule-Remove AVP (AVP code 1093) is of type Grouped, and it is used to deactivate or remove ADC rules from an TDF session. The ADC-Rule-Base-Name AVP is a reference for a group of ADC rules predefined at the TDF to be deactivated.

AVP Format:

ADC-Rule-Remove ::= < AVP Header: 1093 >

*[ ADC-Rule-Base-Name ]

*[ AVP ]



• 3GPP 29.213 v7.11.0• 3GPP 29.213 v8.11.0• 3GPP 29.213 v9.6.0 • 3GPP 29.213 v10.1.0 • 3GPP 29.213 v10.2.0 • 3GPP 29.213 v10.4.0

3GPP 29.213 compliancyTable 3-4 lists compliancy information for Technical Specification Group Core Network and Terminals Policy and Charging Control signaling flows and QoS parameter mapping.

Table 3-4 3GPP 29.213 v10.1.0 compliancy


Notes

1 Scope NR ✓ ✓ ✓ ✓ ✓ �





4 Signaling Flows over Gx, Gxx, Rx and S9

HD ✓ ✓ ✓ ✓ ✓ �

(1 of 8)



Integration Guide

4.0 General C � ✓ ✓ ✓ ✓ Case 2a not supported. See 29.215 compliancy for details about roaming support.

4.1 IP-CAN Session Establishment C ✓ ✓ ✓ ✓ ✓ Case 2a not supported. Roaming scenario not supported.

4.2 IP-CAN Session Termination HD ✓ ✓ ✓ ✓ ✓ �

4.2.1 UE-Initiated HD ✓ ✓ ✓ ✓ ✓ �

4.2.1.1 AF located in the HPLMN C � ✓ ✓ ✓ ✓ Case 2a not supported. Roaming scenario not supported.

4.2.1.2 AF located in the VPLMN C � ✓ ✓ ✓ ✓ Case 2a not supported. Roaming scenario not supported.

4.2.2 PCEF-Initiated HD � ✓ ✓ ✓ ✓ �

4.2.2.1 AF located in the HPLMN FC � ✓ ✓ ✓ ✓ �

4.2.2.2 AF located in the VPLMN FC � ✓ ✓ ✓ ✓ �

4.2.3 PCRF-Initiated HD ✓ ✓ ✓ ✓ ✓ �

4.2.3.1 AF located in the HPLMN C � ✓ ✓ ✓ ✓ Case 2a not supported. Roaming scenario not supported.

4.2.3.2 AF located in the VPLMN FC � ✓ ✓ ✓ ✓ �

4.3 IP-CAN Session Modification HD ✓ ✓ ✓ ✓ ✓ �

4.3.1 Network-Initiated IP-CAN Session Modification

HD ✓ ✓ ✓ ✓ ✓ �

4.3.1.1 Interactions between BBERF, PCEF and the PCRF (PCC/QoS Rule Provisioning in PUSH mode)

FC ✓ ✓ ✓ ✓ ✓ �

4.3.1.2 Interactions between PCRF, AF and SPR

HD ✓ ✓ ✓ ✓ ✓ �

4.3.1.2.1 AF Session Establishment HD ✓ ✓ ✓ ✓ ✓ �

4.3.1.2.1.1 AF located in the HPLMN FC � ✓ ✓ ✓ ✓ �

4.3.1.2.1.2 AF located in the VPLMN FC � ✓ ✓ ✓ ✓ �

4.3.1.2.2 AF session modification HD ✓ ✓ ✓ ✓ ✓ �



4.3.1.2.3 AF session termination HD ✓ ✓ ✓ ✓ ✓ �




Notes

(2 of 8)



4.3.2 PCEF-Initiated IP-CAN Session Modification (PCC Rule Provisioning in PULL Mode)

HD ✓ ✓ ✓ ✓ ✓ �

4.3.2.1 PCEF-initiated IP-CAN Session Modification. AF located in HPLMN.

FC ✓ ✓ ✓ ✓ ✓ �

4.3.2.2 PCEF-initiated IP-CAN Session Modification, AF located in the VPLMN

FC ✓ ✓ ✓ ✓ ✓ �

4.4 Gateway Control Session Procedures

C � ✓ ✓ ✓ ✓ Case 2a not supported. Roaming scenario not supported.

4.4.1 Gateway Control Session Establishment


4.4.2 Gateway Control and QoS Rules Request

C � ✓ ✓ ✓ ✓ CoA not supported

4.4.2.1 Non-Roaming and Home Routed cases

PC � ✓ ✓ ✓ ✓ Home Routed cases not supported.

4.4.2.2 Visited access cases NC � ✓ ✓ ✓ ✓ Visited access cases not supported

4.4.3 Gateway Control and QoS Rules Provision

FC � ✓ ✓ ✓ ✓ �

4.4.4 Gateway Control Session Termination

HD � ✓ ✓ ✓ ✓ �

4.4.4.1 BBERF-Initiated Gateway Control Session Termination


4.4.4.2 PCRF-Initiated Gateway Control Session Termination

FC � ✓ ✓ ✓ ✓ �

4.5 Multiple BBERF Signaling Flows HD � ✓ ✓ ✓ ✓ �

4.5.1 Non-Roaming and Home Routed cases

HD � ✓ ✓ ✓ ✓ �

4.5.1.1 New Gateway Control Session Establishment

FC � ✓ ✓ ✓ ✓ �

4.5.1.2 PCEF IP-CAN session modification - Handover

FC � ✓ ✓ ✓ ✓ �

4.5.1.3 PCEF IP-CAN session modification - IP flow mobility

NC � � � ✓ ✓ IP flow mobility not supported

4.5.1.4 Gateway Control Session Establishment and PCEF IP-CAN session modification - IP flow mobility


4.5.2 Visited access case NC � ✓ ✓ ✓ ✓ Visited access case not supported


Notes

(3 of 8)



Integration Guide

4.5.2.1 New Gateway Control Session Establishment

NC � ✓ ✓ ✓ ✓ Visited access case not supported

4.5.2.2 PCEF-Initiated IP-CAN session modification-Handover

NC � ✓ ✓ ✓ ✓ PCEF-Initiated IP-CAN session modification-Handover not supported

4.5.2.3 PCEF-Initiated IP-CAN session modification-IP flow mobility


4.5.2.4 Gateway Control Session Establishment and PCEF IP-CAN session modification - IP flow mobility


5 Binding Mechanism HD ✓ ✓ ✓ ✓ ✓ �

5.1 Overview FC ✓ ✓ ✓ ✓ ✓ �

5.2 Session Binding FC ✓ ✓ ✓ ✓ ✓ �

5.3 PCC Rule Authorization and QoS Rule Generation

FC ✓ ✓ ✓ ✓ ✓ �

5.4 Bearer Binding FC ✓ ✓ ✓ ✓ ✓ �

6 QoS Parameters Mapping HD ✓ ✓ ✓ ✓ ✓ �

6.1 Overview FC ✓ ✓ ✓ ✓ ✓ �

6.1.1 UE-Initiated IP-CAN bearers FC ✓ ✓ ✓ ✓ ✓ �

6.1.2 Network-Initiated IP-CAN bearers FC ✓ ✓ ✓ ✓ ✓ �

6.2 QoS parameter mapping Functions at AF

NA ✓ ✓ ✓ ✓ ✓ �

6.3 QoS parameter mapping Functions at PCRF

FC ✓ ✓ ✓ ✓ ✓ �

6.4 QoS parameter mapping Functions at PCEF

HD ✓ ✓ ✓ ✓ ✓ �

6.4.1 GPRS HD ✓ ✓ ✓ ✓ ✓ �

6.4.2 3GPP- EPS HD ✓ ✓ ✓ ✓ ✓ �

6.4.2.1 Authorized IP QoS parameters per PDP Context to Authorized UMTS QoS parameters mapping in GGSN

NA ✓ ✓ ✓ ✓ ✓ �

6.4.2.2 Comparing UMTS QoS Parameters against the Authorized UMTS QoS parameters in GGSN for UE initiated PDP context

NA ✓ ✓ ✓ ✓ ✓ �

6.5 QoS parameter mapping Functions at UE for a UE-initiated GPRS PDP Context

NA ✓ ✓ ✓ ✓ ✓ �

6.5.1 SDP to UMTS QoS parameter mapping in UE

NA ✓ ✓ ✓ ✓ ✓ �

6.5.2 SDP parameters to Authorized UMTS QoS parameters mapping in UE

NA ✓ ✓ ✓ ✓ ✓ �


Notes

(4 of 8)



7 PCRF addressing HD � ✓ ✓ ✓ ✓ �

7.1 General NA � ✓ ✓ ✓ ✓ �

7.2 DRA Definition NA � ✓ ✓ ✓ ✓ �

7.3 DRA Procedures NA � ✓ ✓ ✓ ✓ �

7.3.1 General NA � ✓ ✓ ✓ ✓ �

7.3.2 DRA Information Storage NA � ✓ ✓ ✓ ✓ �

7.3.3 Capabilities Exchange NA � ✓ ✓ ✓ ✓ �

7.3.4 Redirect DRA HD � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.3.4.1 Redirecting Diameter Requests NA � ✓ ✓ ✓ ✓ �

7.3.4.2 DRA binding removal NA � ✓ ✓ ✓ ✓ �

7.3.5 Proxy DRA NA � ✓ ✓ ✓ ✓ �

7.3.6 PCRF selection by BBERF/PCEF (non-roaming case)

NA � ✓ ✓ ✓ ✓ �

7.3.7 PCRF selection by AF NA � ✓ ✓ ✓ ✓ �

7.3.8 PCRF selection in a roaming scenario

FC � ✓ ✓ ✓ ✓ �

7.4 DRA flows FC � ✓ ✓ ✓ ✓ �

7.4.1 Proxy DRA FC � ✓ ✓ ✓ ✓ �

7.4.1.1 Establishment of Diameter Sessions

FC � ✓ ✓ ✓ ✓ �

7.4.1.1.1 Non-roaming cases FC � ✓ ✓ ✓ ✓ �

7.4.1.1.2 Roaming cases PC � ✓ ✓ ✓ ✓ See 29.215 compliancy for details about roaming support.

7.4.1.2 Modification of Diameter Sessions FC � ✓ ✓ ✓ ✓ �

7.4.1.2.1 Non-roaming cases FC � ✓ ✓ ✓ ✓ �

7.4.1.2.1.1 Client-initiated FC � ✓ ✓ ✓ ✓ �

7.4.1.2.1.2 PCRF-initiated NA � ✓ ✓ ✓ ✓ �

7.4.1.2.2 Roaming cases NA � ✓ ✓ ✓ ✓ �

7.4.1.2.2.1 V-PCRF initiated NA � ✓ ✓ ✓ ✓ �

7.4.1.2.2.2 H-PCRF initiated NA � ✓ ✓ ✓ ✓ �

7.4.1.3 Termination of Diameter Sessions NA � ✓ ✓ ✓ ✓ �

7.4.1.3.1 Non-roaming cases NA � ✓ ✓ ✓ ✓ �

7.4.1.3.2 Roaming cases NA � ✓ ✓ ✓ ✓ �

7.4.2 Redirect DRA NC � ✓ ✓ ✓ ✓ �

7.4.2.1 Establishment of Diameter Sessions

NC � ✓ ✓ ✓ ✓ �


Notes

(5 of 8)



Integration Guide

7.4.2.1.1 Non-roaming cases NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.4.2.1.2 Roaming cases NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.4.2.2 Modification of Diameter Sessions NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.4.2.3 Termination of Diameter Sessions NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.4.2.3.1 Non-roaming cases NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

7.4.2.3.2 Roaming cases NC � ✓ ✓ ✓ ✓ Redirect DRA not supported

Annex A (informative)

Examples of deriving the Maximum Authorized parameters from the SDP parameters

NR ✓ ✓ ✓ ✓ ✓ �

Annex B (normative)

Signaling Flows for IMS NR ✓ ✓ ✓ ✓ ✓ �

B.0 General PC � � ✓ ✓ ✓ Configured using rules to specify the APN for unknown subscribers. See the section that describes unknown subscribers in the 5780 DSC User Guide for more information.

B.1 Subscription to Notification of Signaling Path Status at IMS Registration

FC ✓ ✓ ✓ ✓ ✓ �

B.1a Subscription to Notification of Change of IP-CAN Type at IMS Registration

FC ✓ ✓ ✓ ✓ ✓ �

B.1b Provisioning of SIP signalling flow information at IMS Registration

FC � � ✓ ✓ ✓ �

B.2 IMS Session Establishment HD ✓ ✓ ✓ ✓ ✓ �

B.2.1 Provisioning of service information at Originating P-CSCF and the PCRF

FC ✓ ✓ ✓ ✓ ✓ �

B.2.2 Provisioning of service information at terminating P-CSCF and the PCRF

FC ✓ ✓ ✓ ✓ ✓ �

B.3 IMS Session Modification HD ✓ ✓ ✓ ✓ ✓ �

B.3.1 Provisioning of service information FC ✓ ✓ ✓ ✓ ✓ �

B.3.2 Enabling of IP Flows FC ✓ ✓ ✓ ✓ ✓ �

B.3.3 Disabling of IP Flows FC ✓ ✓ ✓ ✓ ✓ �

B.3.4 Media Component Removal FC ✓ ✓ ✓ ✓ ✓ �

B.4 IMS Session Termination HD ✓ ✓ ✓ ✓ ✓ �


Notes

(6 of 8)



B.4.1 Mobile initiated session release / Network initiated session release

FC ✓ ✓ ✓ ✓ ✓ �

B.4.2 IP-CAN Bearer Release/Loss FC ✓ ✓ ✓ ✓ ✓ �

Annex C (normative)

NAT Related Procedures HD ✓ ✓ ✓ ✓ ✓ EPS and GPRS use default bearer; therefore, the procedures in this section do not apply.

C.1 Support for media traversal of NATs using ICE

NC ✓ ✓ ✓ ✓ ✓ Dynamic Rule procedure is not supported.

C.2 P-CSCF procedures HD ✓ ✓ ✓ ✓ ✓ �

C.2.1 General NA ✓ ✓ ✓ ✓ ✓ �

C.2.2 Deriving the UEs IP address NA ✓ ✓ ✓ ✓ ✓ �

C.2.3 Deriving flow descriptions NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

C.2.4 Gating control NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

C.2.5 Bandwidth impacts NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

C.3 PCRF procedures HD ✓ ✓ ✓ ✓ ✓ �

C.3.1 General NR ✓ ✓ ✓ ✓ ✓ �

C.3.2 Deriving additional flow descriptions

NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

C.3.3 Gating control NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

C.3.4 Bandwidth impacts NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored

Annex D (normative)

Access specific procedures for GPRS

HD ✓ ✓ ✓ ✓ ✓ �

D.1 General FC � ✓ ✓ ✓ ✓ �

D.2 Binding Mechanisms FC � ✓ ✓ ✓ ✓ �

D.3 PCC Procedures FC � ✓ ✓ ✓ ✓ �

D.3.1 IP-CAN Session Modification FC � ✓ ✓ ✓ ✓ �

D.3.1.1 Network-initiated IP-CAN Session Modification

FC � ✓ ✓ ✓ ✓ �

D.3.1.2 PCEF-initiated IP-CAN Session Modification

FC � ✓ ✓ ✓ ✓ �

D.3.1.2.1 UE-initiated IP-CAN Bearer Establishment or IP-CAN Bearer Modification

FC � ✓ ✓ ✓ ✓ �

D.3.1.2.2 UE-initiated IP-CAN Bearer Termination

FC � ✓ ✓ ✓ ✓ �


Notes

(7 of 8)



Integration Guide



• 3GPP 29.214 v7.9.0• 3GPP 29.214 v8.9.1• 3GPP 29.214 v9.6.0 • 3GPP 29.214 v10.2.0• 3GPP 29.214 v10.3.0• 3GPP 29.214 v10.5.0

3GPP 29.214 compliancyTable 3-5 lists compliancy information for Technical Specification Group Core Network and Terminals Policy and Charging Control over Rx reference point.


Annex E (informative)



Notes

(8 of 8)


Notes

Forward NR ✓ ✓ ✓ ✓ ✓ �

1 Scope NR ✓ ✓ ✓ ✓ ✓ �





4 Rx reference point HD ✓ ✓ ✓ ✓ ✓ �

4.1 Overview NR ✓ ✓ ✓ ✓ ✓ �

4.2 Rx reference model NR ✓ ✓ ✓ ✓ ✓ �

4.3 Functional elements HD ✓ ✓ ✓ ✓ ✓ �

4.3.1 AF FC ✓ ✓ ✓ ✓ ✓ �

4.3.2 PCRF FC ✓ ✓ ✓ ✓ ✓ �

4.4 PCC procedures over Rx reference point

HD ✓ ✓ ✓ ✓ ✓ �

4.4.1 Initial Provisioning of Session Information

FC ✓ ✓ ✓ ✓ ✓ �

(1 of 6)



4.4.2 Modification of Session Information FC ✓ ✓ ✓ ✓ ✓ �

4.4.3 Gate Related Procedures FC ✓ ✓ ✓ ✓ ✓ �

4.4.4 AF Session Termination FC ✓ ✓ ✓ ✓ ✓ �

4.4.5 Subscription to Notification of Signaling Path Status

FC ✓ ✓ ✓ ✓ ✓ �

4.4.5a Provisioning of AF Signalling Flow Information

PC � ✓ ✓ ✓ ✓ The 5780 DSC does not support the AF-Signaling-Protocol AVP.

4.4.6 Traffic Plane Events HD ✓ ✓ ✓ ✓ ✓ �

4.4.6.1 IP-CAN Session Termination FC ✓ ✓ ✓ ✓ ✓ �

4.4.6.2 Service Data Flow Deactivation FC ✓ ✓ ✓ ✓ ✓ �

4.4.6.3 Notification of Signaling Path Status

FC ✓ ✓ ✓ ✓ ✓ �

4.4.6.4 IP-CAN type change Notification FC ✓ ✓ ✓ ✓ ✓ �

4.4.6.5 Access Network Charging Information Notification

FC ✓ ✓ ✓ ✓ ✓ �

4.4.6.6 Reporting Usage for Sponsored Data Connectivity

FC � � � ✓ ✓

5 Rx protocol HD ✓ ✓ ✓ ✓ ✓ �

5.1 Protocol support FC ✓ ✓ ✓ ✓ ✓ �


FC ✓ ✓ ✓ ✓ ✓ �

5.3 Rx specific AVPs PC ✓ ✓ ✓ ✓ ✓ SIP-Forking-Indication is ignored

5.3.1 Abort-Cause AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.2 Access-Network-Charging-Address AVP

FC ✓ ✓ ✓ ✓ ✓ No specific check done for interoperator interface forwarding.

5.3.3 Access-Network-Charging-Identifier AVP

FC ✓ ✓ ✓ ✓ ✓ �

5.3.4 Access-Network-Charging-Identifier-Value AVP

FC ✓ ✓ ✓ ✓ ✓ �

5.3.5 AF-Application-Identifier AVP PC ✓ ✓ ✓ ✓ ✓ AF-Application-Identifier in Media-Component-Description is ignored.

5.3.6 AF-ChargingIdentifier AVP PC ✓ ✓ ✓ ✓ ✓ �

5.3.7 Codec-Data AVP NC ✓ ✓ ✓ ✓ ✓ Codec-Data AVP is ignored. Maximum size is 1024 bytes.


Notes

(2 of 6)



Integration Guide

5.3.8 Flow-Description AVP PC ✓ ✓ ✓ ✓ ✓ The modification of Flow-Description is supported for Network-only and UE-only requests.Note: Source, destination IP address in the flow description can be wildcarded using �any� keyword. The 5780 DSC does not match these wildcarded flow descriptions to another flow description with a specific IP address.For uplink filters (direction IN), the source address must be the UE IP. For downlink filters (direction OUT), the destination address must be the UE IP.

5.3.9 Flow-Number AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.10 Flows AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.11 Flow-Status AVP PC ✓ ✓ ✓ ✓ ✓ Media-Component-Description level is supported and can be used in the 5780 DSC rules. Media-Sub-Component level is ignored and is not supported in 5780 DSC rules.

5.3.12 Flow-Usage AVP FC ✓ ✓ ✓ ✓ ✓ Not supported in the 5780 DSC rules.

5.3.13 Specific-Action AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.14 Max-Requested-Bandwidth-DL AVP PC ✓ ✓ ✓ ✓ ✓ Media-Component-Description level is supported and can be used in the 5780 DSC rules. Media-Sub-Component level is ignored and is not supported in 5780 DSC rules.

5.3.15 Max-Requested-Bandwidth-UL AVP PC ✓ ✓ ✓ ✓ ✓ Media-Component-Description level is supported and can be used in the 5780 DSC rules. Media-Sub-Component level is ignored and is not supported in 5780 DSC rules.


Notes

(3 of 6)



5.3.16 Media-Component-Description AVP PC ✓ ✓ ✓ ✓ ✓ Command level Reservation-Priority is supported. Media-Component-Description level Reservation-Priority is ignored.Media-Sub-Components cannot be added after a media component is established.

5.3.17 Media-Component-Number AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.18 Media-Sub-Component AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.19 Media-Type AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.20 RR-Bandwidth AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.21 RS-Bandwidth AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.22 SIP-Forking-Indication AVP NC ✓ ✓ ✓ ✓ ✓ SIP-Forking-Indication is ignored.

5.3.23 Service-URN AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.24 Acceptable-Service-Info AVP PC ✓ ✓ ✓ ✓ ✓ Acceptable-Service-Info in Media-Component-Description is ignored.

5.3.25 Service-Info-Status-AVP FC ✓ ✓ ✓ ✓ ✓ �

5.3.26 AF-Signalling-Protocol-AVP FC � � ✓ ✓ ✓ �

5.3.27 Sponsored-Connectivity-Data AVP NC � � � ✓ ✓ �

5.3.28 Sponsor-Identity AVP NC � � � ✓ ✓ �

5.3.29 Application-Service-Provider-Identity AVP

NC � � � ✓ ✓ �

5.3.30 MPS-Identifier AVP NC � � � ✓ ✓ �

5.4 Rx re-used AVPs FC ✓ ✓ ✓ ✓ ✓ �

5.4.1 Use of the Supported-Features AVP on the Rx reference point

FC � ✓ ✓ ✓ ✓ �

5.5 Rx specific Experimental-Result-Code AVP values

FC ✓ ✓ ✓ ✓ ✓ �

5.6 Rx messages FC ✓ ✓ ✓ ✓ ✓ �

5.6.1 AA-Request (AAR) command PC ✓ ✓ ✓ ✓ ✓ SIP-Forking-Indication is ignored

5.6.2 AA-Answer (AAA) command FC ✓ ✓ ✓ ✓ ✓ �

5.6.3 Re-Auth-Request (RAR) command FC ✓ ✓ ✓ ✓ ✓ �

5.6.4 Re-Auth-Answer (RAA) command FC ✓ ✓ ✓ ✓ ✓ �

5.6.5 Session-Termination-Request (STR) command

FC ✓ ✓ ✓ ✓ ✓ �

5.6.6 Session-Termination-Answer (STA) command

FC ✓ ✓ ✓ ✓ ✓ �


Notes

(4 of 6)



Integration Guide

5.6.7 Abort-Session-Request (ASR) command

FC ✓ ✓ ✓ ✓ ✓ �

5.6.8 Abort-Session-Answer (ASA) command

FC ✓ ✓ ✓ ✓ ✓ �

Annex A (normative)

IMS Related P-CSCF Procedures over Rx

HD ✓ ✓ ✓ ✓ ✓ �

A.1 Provision of Service Information at P-CSCF

NA ✓ ✓ ✓ ✓ ✓ �

A.2 Enabling of IP Flows NA ✓ ✓ ✓ ✓ ✓ �

A.3 Support for SIP forking NR ✓ ✓ ✓ ✓ ✓ �

A.3.1 PCC rule provisioning for early media for forked responses

NC ✓ ✓ ✓ ✓ ✓ SIP-Forking is not supported.

A.3.2 Updating the provisioned PCC rules at the final answer

NC ✓ ✓ ✓ ✓ ✓ SIP-Forking is not supported.

A.4 Notification of AF Signaling Transmission Path Status

FC ✓ ✓ ✓ ✓ ✓ �

A.5 Indication of Emergency Session FC ✓ ✓ ✓ ✓ ✓ �

A.6 Notification IP-CAN Type Change FC � ✓ ✓ ✓ ✓ �

A.7 Support for Early Session disposition SDP

HD � � ✓ ✓ ✓ �

A.7.1 General NC � � ✓ ✓ ✓ �

A.7.2 Service Information Provisioning for Early Media

NC � � ✓ ✓ ✓ �

A.7.3 Updating the Provisioned Service Information when Dialogue is established

NC � � ✓ ✓ ✓ �

A.8 Provision of Signalling Flow Information at P-CSCF

NC � � ✓ ✓ ✓ �

A.9 Handling of MPS Session NC � � � ✓ ✓ �

Annex B (normative)

Flow identifiers: Format definition and examples

HD ✓ ✓ ✓ ✓ ✓ �

B.1 Format of a flow identifier HD ✓ ✓ ✓ ✓ ✓ �

B.1.1 General NA � � ✓ ✓ ✓ �

B.1.2 Derivation of Flow Identifiers from SDP

NA � � ✓ ✓ ✓ �

B.1.2.1 Standard Procedure NA � � ✓ ✓ ✓ �

B.1.2.2 SDP with "early session" disposition type

NA � � ✓ ✓ ✓ �

B.2 Example 1 NR ✓ ✓ ✓ ✓ ✓ �

B.3 Example 2 NR ✓ ✓ ✓ ✓ ✓ �

B.4 Example 3 without media components

NR ✓ ✓ ✓ ✓ ✓ �

B.5 Example 4 NR ✓ ✓ ✓ ✓ ✓ �


Notes

(5 of 6)





• 3GPP 29.215 v8.9.0• 3GPP 29.215 v9.6.0• 3GPP 29.215 v10.1.0• 3GPP 29.215 v10.2.0• 3GPP 29.215 v10.4.0

3GPP 29.215 compliancyTable 3-6 lists compliancy information for Technical Specification Group Core Network and Terminals Policy and Charging Control (PCC) over S9 reference point; (Stage 3).


Annex C (normative)

void HD ✓ ✓ ✓ ✓ ✓ �

Annex D (normative)



Notes

(6 of 6)

Note 1 � The 5780 DSC supports visited access in PCEF in V-PLMN and AF only in H-PLMN.

Note 2 � The 5780 DSC does not support PMIPv6-based S9 scenarios

Note 3 � In section 4.5.1 of Technical Specification Group Core Network and Terminals Policy and Charging Control (PCC) over S9 reference point; (Stage 3) (Release 10) ,Scenario 2a) and Scenario 2b) are not supported.

Section Requirement Compliancy v8.9.0 v9.6.0 v10.1.0 v10.2.0/ v10.4.0

Notes

1 Scope HD ✓ ✓ ✓ ✓ �

2 References NR ✓ ✓ ✓ ✓ �

3 Definitions and abbreviations

NR ✓ ✓ ✓ ✓ �

3.1 Definitions NR ✓ ✓ ✓ ✓ �

3.2 Abbreviations NR ✓ ✓ ✓ ✓ �

4. S9 Reference Point HD ✓ ✓ ✓ ✓ �

(1 of 5)



Integration Guide

4.1 Overview PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.2 Reference model PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.3 Functional elements HD ✓ ✓ ✓ ✓ �

4.3.1 H-PCRF PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.3.1.1 Home routed access NC ✓ ✓ ✓ ✓ �

4.3.1.2 Visited Access PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.3.2 V-PCRF PC ✓ ✓ ✓ ✓ See notes 1 and 3 for more information.

4.3.2.1 Home routed access NC ✓ ✓ ✓ ✓ �

4.3.2.2 Visited access PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.4 PCC Rules and QoS Rules HD ✓ ✓ ✓ ✓ �

4.4.1 PCC Rule definition FC ✓ ✓ ✓ ✓ �

4.4.2 QoS Rule definition NC ✓ ✓ ✓ ✓ �

4.4.2a IP flow mobility routing Rule definition

NC � � ✓ ✓

4.4.3 Operations on PCC rules FC ✓ ✓ ✓ ✓ �

4.4.4 Operations on QoS Rules NC ✓ ✓ ✓ ✓ �

4.4.5 Operations on IP flow mobility routing Rules

NC � � ✓ ✓ �

4.5 PCC procedures over S9 Reference Point

HD ✓ ✓ ✓ ✓ �

4.5.1 General PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.5.1.1 S9 Session Establishment PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.5.1.2 S9 Session Termination FC ✓ ✓ ✓ ✓ �

4.5.1.3 Event Triggers HD ✓ ✓ ✓ ✓ �

4.5.1.3.1 Provisioning of Event Triggers

PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

4.5.1.3.2 Reporting of deployed Event Triggers


4.5.1.4 Multiple BBERF scenarios NC ✓ ✓ ✓ ✓ �

4.5.1.5 Provisioning and validation of Default EPS Bearer authorized QoS

PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.In addition, QoS validation is not supported.


Notes

(2 of 5)



4.5.1.6 Provisioning of Authorized QoS per APN


4.5.1.7 Bearer Control Mode Selection

FC ✓ ✓ ✓ ✓ �

4.5.1.8 Access Network Information Reporting

PC � � ✓ ✓ see note 2

4.5.2 Home-Routed access HD ✓ ✓ ✓ ✓ �

4.5.2.1 S9 Session/Subsession establishment/modification

NC ✓ ✓ ✓ ✓ �

4.5.2.2 Provision of QoS Rules by the H-PCRF

NC ✓ ✓ ✓ ✓ �

4.5.2.3 S9 Session/Subsession Termination Initiated by the V-PCRF

NC ✓ ✓ ✓ ✓ �

4.5.2.4 S9 Session/Subsession Termination Initiated by the H-PCRF

NC ✓ ✓ ✓ ✓ �

4.5.2.5 Multiple BBERF Handling HD ✓ ✓ ✓ ✓ �

4.5.2.5.1 General NC � � ✓ ✓ see note 2

4.5.2.5.2 Handling of multiple BBERFs associated with the same IP-CAN session during handover

NC � � ✓ ✓ see note 2

4.5.2.5.3 Handling of two BBERFs with flow mobility within the same IP-CAN session

NC � � ✓ ✓ see note 2

4.5.2.6 Deferred Session Linking Handling

NC ✓ ✓ ✓ ✓ �

4.5.2.7 Session Linking Handling When Multiple PDN Connection to a single APN is supported

NC � ✓ ✓ ✓ �

4.5.3 Visited Access HD ✓ ✓ ✓ ✓ �

4.5.3.1 Request PCC and QoS Rules


4.5.3.2 PCC and QoS Rules Provisioning


4.5.3.3 S9 Session/Subsession Termination Initiated by V-PCRF.



Notes

(3 of 5)



Integration Guide

4.5.3.4 S9 Session/Subsession Termination Initiated by the H-PCRF.

FC ✓ ✓ ✓ ✓ �

4.5.3.5 Multiple BBERF Handling NC ✓ ✓ ✓ ✓ �

4.5.3.6 Rx Over S9 NC ✓ ✓ ✓ ✓ �

4.5.3.6.1 General NC ✓ ✓ ✓ ✓ �

4.5.3.6.2 Event Handling NC ✓ ✓ ✓ ✓ �

4.5.3.6.2.1 V-AF Subscription to Notification of Signalling Path Status

NC ✓ ✓ ✓ ✓ �

4.5.3.6.2.2 Reporting of Signalling Path Status

NC ✓ ✓ ✓ ✓ �

4.5.3.6.2.3 Reporting IP-CAN Type Change Notification

NC ✓ ✓ ✓ ✓ �

4.5.3.7 Deferred Session Linking Handling

NC ✓ ✓ ✓ ✓ �

4.5.3.8 Session Linking Handling When Multiple PDN Connection to a single APN is supported

NC � ✓ ✓ ✓ �

4.5.3.9 IP flow mobility support NC � � ✓ ✓ �

4.5.4 IMS Emergency services FC � ✓ ✓ ✓ �

5. S9 Protocol HD ✓ ✓ ✓ ✓ �

5.1 Protocol Support PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.In addition, QoS validation is not supported.



5.3 S9 specific AVPs PC ✓ ✓ ✓ ✓ Multiple BBERF actions are not supported.

5.3.1 Subsession-Decision-Info PC ✓ ✓ ✓ ✓ See notes 1, 2 and 3 for more information.

5.3.2 Subsession-Enforcement-Info


5.3.3 Subsession-Id FC ✓ ✓ ✓ ✓ �

5.3.4 Subsession-Operation FC ✓ ✓ ✓ ✓ �

5.3.5 Void NA ✓ ✓ ✓ ✓ �

5.3.6 Multiple-BBERF-Action NC ✓ ✓ ✓ ✓ �

5.4 S9 re-used AVPs PC ✓ ✓ ✓ ✓ See note 2 for more information.


Notes

(4 of 5)




A statement of compliance for the following specification is described in this subsection:

• 3GPP 29.219 V2.0.0

3GPP 29.219 compliancyTable 3-7 lists compliancy information for 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control: Spending Limit Reporting over Sy reference point.


5.4.1 Use of the Supported-Features AVP on the S9 reference point

FC ✓ ✓ ✓ ✓ �

5.5 S9 Messages HD ✓ ✓ ✓ ✓ �

5.5.1 S9 Application FC ✓ ✓ ✓ ✓ �

5.5.2 CC-Request (CCR) Command

PC ✓ ✓ ✓ ✓ See note 2 for more information.

5.5.3 CC-Answer (CCA) Command


5.5.4 Re-Auth-Request (RAR) Command


5.5.5 Re-Auth-Answer (RAA) Command


5.6 S9 specific Experimental-Result-Code AVP values

HD ✓ ✓ ✓ ✓ �

5.6.1 General FC ✓ ✓ ✓ ✓ �

5.6.2 Success FC ✓ ✓ ✓ ✓ �

5.6.3 Permanent Failures FC ✓ ✓ ✓ ✓ �

Annex A (informative):

Change history NR ✓ ✓ ✓ ✓ �


Notes

(5 of 5)

Section Requirement Compliancy V1.0.0 Notes

Foreword � NR ✓ �

1 Scope NR ✓ �

2 References NR ✓ �

(1 of 3)



Integration Guide

3 Definitions, symbols and abbreviations

NR ✓ �

3.1 Definitions NR ✓ �

3.2 Symbols NR ✓ �

3.3 Abbreviations NR ✓ �

4 Sy reference point HD ✓ �

4.1 Overview PC ✓ The 5780 DSC does not support roaming scenarios.

4.2 Sy Reference model FC ✓ �

4.3 Subscriber Spending Limits FC ✓ �

4.4 Functional elements HD ✓ �

4.4.1 PCRF FC ✓ �

4.4.2 OCS NA ✓ �

4.5 Spending Limits procedures over Sy reference point

HD ✓ �

4.5.1 Initial/Intermediate Spending Limit Report Request

FC ✓ �

4.5.1.1 General FC ✓ �

4.5.1.2 Detailed behaviour of the PCRF

FC ✓ �

4.5.1.3 Detailed behaviour of the OCS NA ✓ �

4.5.2 Spending Limit Report FC ✓ �




FC ✓ �

4.5.3 Final Spending Limit Report Request

FC ✓ �



FC ✓ �


5 Sy protocol HD ✓ �

5.1 Protocol support FC ✓ �

5.1.1 Use of Diameter base protocol FC ✓ �

5.1.2 Void NA ✓ �

5.1.3 Accounting functionality FC ✓ �

5.1.4 Transport protocol FC ✓ �

5.1.5 Advertising Application Support

FC ✓ �


(2 of 3)



5.1.6 Use of the Supported-Features AVP

FC ✓ The feature bits have not yet been defined by the standard.

5.2 Initialization and maintenance of connection and session

FC ✓ �

5.3 Sy specific AVPs FC ✓ AVP code bits have not yet been defined by the standard.

5.3.1 Policy-Counter-Identifier AVP FC ✓ AVP code bits have not yet been defined by the standard.

5.3.2 Policy-Counter-Status AVP FC ✓ AVP code bits have not yet been defined by the standard.

5.3.3 Policy-Counter-Status-Report AVP

FC ✓ AVP code bits have not yet been defined by the standard.

5.3.4 SL-Request-Type AVP FC ✓ AVP code bits have not yet been defined by the standard.

5.4 Sy re-used AVPs FC ✓ �

5.5 Void NA ✓ �

5.6 Sy Messages HD ✓ �

5.6.1 Command-Code Values FC ✓ For command code bits, the standard has not as yet been defined.

5.6.2 Spending Limit Request (SLR) command

FC ✓ For command code bits, the standard has not as yet been defined.

5.6.3 Spending Limit Answer (SLA) command


5.6.4 Spending-Status Notification Request (SNR) command


5.6.5 Spending-Status Notification Answer (SNA) command


5.6.6 Session-Termination-Request (STR) command


5.6.7 Session-Termination-Answer (STA) command


Annex <X> (informative):

Change history NA ✓ �


(3 of 3)



Integration Guide



• 3GPP 29.230 v7.14.0 • 3GPP 29.230 v8.5.0 • 3GPP 29.230 v9.6.0 • 3GPP 29.230 v10.2.0 • 3GPP 29.230 v10.3.0 • 3GPP 29.230 v10.5.0

3GPP 29.230 compliancyTable 3-8 lists compliancy information for Technical Specification Group Core Network and Terminals Diameter applications; 3GPP specific codes and identifiers.



Notes

� Foreword NR ✓ ✓ ✓ ✓ ✓ �

1 Scope NR ✓ ✓ ✓ ✓ ✓ �


3 Definitions and abbreviations NR ✓ ✓ ✓ ✓ ✓ �



4 Application identifiers NR ✓ ✓ ✓ ✓ ✓ �

4.1 3GPP specific application identifiers

FC ✓ ✓ ✓ ✓ ✓ �

5 Command codes NR ✓ ✓ ✓ ✓ ✓ Not applicable to the PCRF

5.1 Command codes allocated for 3GPP

NR ✓ ✓ ✓ ✓ ✓ Not applicable to the PCRF.

6 Vendor identifier NR ✓ ✓ ✓ ✓ ✓ �

6.1 3GPP�s vendor identifier NR ✓ ✓ ✓ ✓ ✓ �

7 Attribute-Value-Pair codes NR ✓ ✓ ✓ ✓ ✓ �

7.1 3GPP specific AVP codes PC ✓ ✓ ✓ ✓ ✓ See Rx and Gx compliance documents for details .

8 Experimental result codes FC ✓ ✓ ✓ ✓ ✓ �

8.1 3GPP specific result codes FC ✓ ✓ ✓ ✓ ✓ �

(1 of 2)



3.10 Statement of compliance information for 3GPP 29.329


• 3GPP 29.329 v7.8.0 • 3GPP 29.329 v8.7.0 • 3GPP 29.329 v9.3.0 • 3GPP 29.329 v10.2.0 • 3GPP 29.329 v10.3.0 • 3GPP 29.329 v10.5.0

3GPP 29.329 compliancyTable 3-9 lists compliancy information for Technical Specification Group Core Network and Terminals Sh Interface base on the Diameter Protocol: Protocol Details.


8.1.1 Informational NR ✓ ✓ ✓ ✓ ✓ Not applicable to the PCRF.

8.1.2 Success FC ✓ ✓ ✓ ✓ ✓ �

8.1.3 Transient Failures FC ✓ ✓ ✓ ✓ ✓ �

8.1.4 Permanent Failures FC ✓ ✓ ✓ ✓ ✓ �


Assignment of the Diameter codes and identifiers in 3GPP

NR ✓ ✓ ✓ ✓ ✓ �

A.1 Application identifiers NR ✓ ✓ ✓ ✓ ✓ �

A.2 Command codes NR ✓ ✓ ✓ ✓ ✓ �

A.3 AVP codes NR ✓ ✓ ✓ ✓ ✓ �

A.4 Result codes NR ✓ ✓ ✓ ✓ ✓ �

Annex B (informative)



Notes

(2 of 2)

Section Requirement Compliancy v7.8.0 v8.7.0 v9.3.0 v10.2.0 v10.3.0 /v10.5.0

Notes

Forward NR ✓ ✓ ✓ ✓ ✓ �

1 Scope NR ✓ ✓ ✓ ✓ ✓ �


(1 of 4)



Integration Guide

3 Definitions, symbols and abbreviations HD ✓ ✓ ✓ ✓ ✓ �



4 General HD ✓ ✓ ✓ ✓ ✓ �

5 Use of the Diameter base protocol FC ✓ ✓ ✓ ✓ ✓ �

6 Diameter application for Sh interface FC ✓ ✓ ✓ ✓ ✓ �

6.1 Command-Code values FC ✓ ✓ ✓ ✓ ✓ �

6.1.1 User-Data-Request (UDR) Command FC ✓ ✓ ✓ ✓ ✓ �

6.1.2 User-Data-Answer (UDA) Command FC ✓ ✓ ✓ ✓ ✓ �

6.1.3 Profile-Update-Request (PUR) Command

NC ✓ ✓ ✓ ✓ ✓ �

6.1.4 Profile-Update-Answer (PUA) Command

NC ✓ ✓ ✓ ✓ ✓ �

6.1.5 Subscribe-Notifications-Request (SNR) Command

FC ✓ ✓ ✓ ✓ ✓ �

6.1.6 Subscribe-Notifications-Answer (SNA) Command

FC ✓ ✓ ✓ ✓ ✓ �

6.1.7 Push-Notification-Request (PNR) Command

FC ✓ ✓ ✓ ✓ ✓ �

6.1.8 Push-Notifications-Answer (PNA) Command

FC ✓ ✓ ✓ ✓ ✓ �

6.2 Result-Code AVP values FC ✓ ✓ ✓ ✓ ✓ �

6.2.1 Success FC ✓ ✓ ✓ ✓ ✓ �

6.2.2 Permanent Failures HD ✓ ✓ ✓ ✓ ✓ �

6.2.2.1 DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED (5100)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.2 DIAMETER_ERROR_OPERATION_NOT_ALLOWED (5101)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.3 DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ (5102)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.4 DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED (5103)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.5 DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED (5104)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.6 DIAMETER_ERROR_TOO_MUCH_DATA (5008)

NA ✓ ✓ ✓ ✓ ✓ Not used

6.2.2.7 DIAMETER_ERROR_TRANSPARENT_DATA OUT_OF_SYNC (5105)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.8 DIAMETER_ERROR_FEATURE_UNSUPPORTED (5011)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.9 DIAMETER_ERROR_SUBS_DATA_ABSENT (5106)

FC ✓ ✓ ✓ ✓ ✓ �


Notes

(2 of 4)



6.2.2.10 DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA (5107)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.11 DIAMETER_ERROR_DSAI_NOT_AVAILABLE (5108)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.2.12 DIAMETER_ERROR_IDENTITIES_DONT_MATCH (5002)

NA � � � ✓ ✓ �

6.2.3 Transient Failures HD ✓ ✓ ✓ ✓ ✓ �

6.2.3.1 DIAMETER_USER_DATA_NOT_AVAILABLE (4100)

FC ✓ ✓ ✓ ✓ ✓ �

6.2.3.2 DIAMETER_PRIOR_UPDATE_IN_PROGRESS (4101)

FC ✓ ✓ ✓ ✓ ✓ �

6.3 AVPs HD ✓ ✓ ✓ ✓ ✓ �

6.3.1 User-Identity AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.2 MSISDN AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.3 User-Data AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.4 Data-Reference AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.5 Service-Indication AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.6 Subs-Req-Type AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.7 Requested-Domain AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Conditional field

6.3.7A Requested-Nodes AVP NC � � ✓ ✓ ✓ �

6.3.8 Current-Location AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Conditional field

6.3.9 Server-Name AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Conditional field

6.3.10 Identity-Set AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.11 Supported-Features AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.12 Feature-List-ID AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.13 Feature-List AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.14 Supported-Applications AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.15 Public-Identity AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.16 Expiry-Time AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.17 Send-Data-Indication AVP FC ✓ ✓ ✓ ✓ ✓ �

6.3.18 DSAI-Tag AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Conditional field


Notes

(3 of 4)



Integration Guide

3.11 Statement of compliance information for 3GPP 29.335

The 5780 DSC has implemented a portion of 3GPP TS 29.335 User Data Convergence (UDC) v11.0.0 (2012-09);User Data Repository Access Protocol over the Ud interface; Stage 3 and User Data Convergence (UDC); Technical realization and information flows; Stage 2.

The 5780 DSC supports the Ud notification interface to allow customers who are using an external SPR to notify the 5780 DSC of any changes to the SPR objects.

6.3.19 Wildcarded-PSI AVP NC ✓ ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.20 Wildcarded-IMPU AVP NC � ✓ ✓ ✓ ✓ Not provided - Optional field

6.3.21 Session-Priority AVP NC � ✓ ✓ ✓ ✓ �

6.3.22 One-Time-Notification AVP NC � ✓ ✓ ✓ ✓ �

6.3.23 Serving-Node-Indication AVP NC � � � ✓ ✓ �

6.3.24 Repository-Data-ID AVP NC � � � ✓ ✓ �

6.3.25 Sequence-Number AVP NC � � � ✓ ✓ �

6.3.26 Pre-paging-Supported AVP NC � � � ✓ ✓ �

6.4 Use of namespaces NR ✓ ✓ ✓ ✓ ✓ �

6.4.1 AVP codes NR ✓ ✓ ✓ ✓ ✓ �

6.4.2 Experimental-Result-Code AVP values NR ✓ ✓ ✓ ✓ ✓ �

6.4.3 Command Code values FC ✓ ✓ ✓ ✓ ✓ �

6.4.4 Application-ID value FC ✓ ✓ ✓ ✓ ✓ �

7 Special Requirements HD ✓ ✓ ✓ ✓ ✓ �

7.1 Version Control FC ✓ ✓ ✓ ✓ ✓ �




Notes

(4 of 4)

Note � The 5780 DSC Ud implementation in Release 5.1 R2 is limited to implementation of the notification interface.

• All Ud message content is ignored with the exception of the parameters used to identify the subscriber object that has changed.

• Upon receiving notification, the 5780 DSC will trigger a reload of the identified subscriber and account objects.

• Subscription procedure is not supported.

See the 5780 DSC API Reference Manual for more information about Ud.



3.12 Statement of compliance information for RFC 2865

Table 3-10 lists compliancy information for RFC 2865 Remote Authentication Dial In User Service (RADIUS).

Table 3-10 RFC 2865 compliancy

Section Requirement Compliancy Notes

1. Introduction NR �

1.1 Specification Requirements NR �

1.2 Terminology NR �

2. Operation FC �

2.1 Challenge/Response NC �

2.2 Interoperation with PAP and CHAP PC CHAP not supported

2.3 Proxy FC �

2.4 Why UDP? NR �

2.5 Retransmission Hints NA �

2.6 Keep-Alives Considered Harmful NR �

3. Packet Format FC �

4. Packet Types NR �

4.1 Access-Request FC �

4.2 Access-Accept FC �

4.3 Access-Reject FC �

4.4 Access-Challenge NC �

5. Attributes FC �

5.1 User-Name FC �

5.2 User-Password FC �

5.3 CHAP-Password NC �

5.4 NAS-IP-Address FC �

5.5 NAS-Port FC �

5.6 Service-Type FC �

5.7 Framed-Protocol C �

5.8 Framed-IP-Address FC �

5.9 Framed-IP-Netmask C �

5.10 Framed-Routing PC �

5.11 Filter-Id FC �

5.12 Framed-MTU C �

5.13 Framed-Compression C �

5.14 Login-IP-Host C �

(1 of 3)



Integration Guide

5.15 Login-Service FC �

5.16 Login-TCP-Port FC �

5.17 (unassigned) NR �

5.18 Reply-Message FC �

5.19 Callback-Number C �

5.20 Callback-Id FC �

5.21 (unassigned) NR �

5.22 Framed-Route FC �

5.23 Framed-IPX-Network FC �

5.24 State C �

5.25 Class C �

5.26 Vendor-Specific FC �

5.27 Session-Timeout FC �

5.28 Idle-Timeout FC �

5.29 Termination-Action FC �

5.30 Called-Station-Id FC �

5.31 Calling-Station-Id NC �

5.32 NAS-Identifier C �

5.33 Proxy-State FC �

5.34 Login-LAT-Service C �

5.35 Login-LAT-Node C �

5.36 Login-LAT-Group C �

5.37 Framed-AppleTalk-Link FC �

5.38 Framed-AppleTalk-Network FC �

5.39 Framed-AppleTalk-Zone FC �

5.40 CHAP-Challenge NC �

5.41 NAS-Port-Type FC �

5.42 Port-Limit C �

5.43 Login-LAT-Port C �

5.44 TableofAttributes FC �

6. IANAConsiderations NR �

6.1 DefinitionofTerms NR �

6.2 RecommendedRegistrationPolicies NR �

7. Examples NR �

7.1 UserTelnettoSpecifiedHost NR �

7.2 FramedUserAuthenticatingwithCHAP NR �

7.3 UserwithChallenge-Responsecard NR �


(2 of 3)




Table 3-11 lists compliancy information for RFC 2866 RADIUS Accounting.


8. SecurityConsiderations NR �

9. ChangeLog NR �

10. References NR �

11. Acknowledgements NR �

12. Chair'sAddress NR �

13. Authors'Addresses NR �

14. FullCopyrightStatement NR �


(3 of 3)



1.1 SpecificationofRequirements NR �

1.2 Terminology NR �

2. Operation FC �

2.1 Proxy FC �

3. PacketFormat FC �

4. PacketTypes NR �

4.1 Accounting-Request FC �

4.2 Accounting-Response FC �


5.1 Acct-Status-Type FC �

5.2 Acct-Delay-Time NC �

5.3 Acct-Input-Octets NC �

5.4 Acct-Output-Octets NC �

5.5 Acct-Session-Id FC �

5.6 Acct-Authentic NC �

5.7 Acct-Session-Time NC �

5.8 Acct-Input-Packets NC �

5.9 Acct-Output-Packets NC �

5.10 Acct-Terminate-Cause NC �

5.11 Acct-Multi-Session-Id NC �

(1 of 2)



Integration Guide


Table 3-12 lists compliancy information for RFC 3588 Diameter Base Protocol.


5.12 Acct-Link-Count NC �

5.13 TableofAttributes FC �

6. IANAConsiderations NR �

7. SecurityConsiderations NR �

8. ChangeLog NR �



11. Chair'sAddress NR �

12. Author'sAddress NR �

13. FullCopyrightStatement NR �


(2 of 2)



1.1. Diameter Protocol NR �

1.1.1. Description of the Document Set NR �

1.2. Approach to Extensibility NR �

1.2.1. Defining New AVP Values NR �

1.2.2. Creating New AVPs NR �

1.2.3. Creating New Authentication Applications NR �

1.2.4. Creating New Accounting Applications NR �

1.2.5. Application Authentication Procedures NR �

1.3. Terminology NR �

2. Protocol Overview FC �

2.1. Transport PC SCTP not supported

2.1.1. SCTP Guidelines NR SCTP not supported

2.2. Securing Diameter Messages NR �

2.3. Diameter Application Compliance NR �

2.4. Application Identifiers FC �

2.5. Connections vs. Sessions NR �

2.6. Peer Table NR �

(1 of 6)



2.7. Realm-Based Routing Table NR �

2.8. Role of Diameter Agents NR �

2.8.1. Relay Agents FC �

2.8.2. Proxy Agents FC �

2.8.3. Redirect Agents NC See Section 7.4.2 of 3GPP 29.213 compliancy for more information.

2.8.4. Translation Agents NA The 5780 DSC supports RADIUS to DIAMETER translation. See the 5780 DSC User Guide for more information.

2.9. End-to-End Security Framework NR �

2.10. Diameter Path Authorization FC �

3. Diameter Header FC �

3.1. Command Codes NR �

3.2. Command Code ABNF specification FC �

3.3. Diameter Command Naming Conventions NR �

4. Diameter AVPs FC �

4.1. AVP Header FC �

4.1.1. Optional Header Elements NR �

4.2. Basic AVP Data Formats FC �

4.3. Derived AVP Data Formats FC �

4.4. Grouped AVP Values FC �

4.4.1. Example AVP with a Grouped Data Type NR �

4.5. Diameter Base Protocol AVPs FC �

5. Diameter Peers NR �

5.1. Peer Connections FC �

5.2. Diameter Peer Discovery FC �

5.3. Capabilities Exchange FC �

5.3.1. Capabilities-Exchange-Request NR �

5.3.2. Capabilities-Exchange-Answer NR �

5.3.3. Vendor-Id AVP NR �

5.3.4. Firmware-Revision AVP NR �

5.3.5. Host-IP-Address AVP NR �

5.3.6. Supported-Vendor-Id AVP NR �

5.3.7. Product-Name AVP NR �

5.4. Disconnecting Peer Connections FC �

5.4.1. Disconnect-Peer-Request NR �

5.4.2. Disconnect-Peer-Answer NR �


(2 of 6)



Integration Guide

5.4.3. Disconnect-Cause AVP NR �

5.5. Transport Failure Detection NR �

5.5.1. Device-Watchdog-Request NR �

5.5.2. Device-Watchdog-Answer NR �

5.5.3. Transport Failure Algorithm FC �

5.5.4. Failover and Failback Procedures FC �

5.6. Peer State Machine FC �

5.6.1. Incoming connections FC �

5.6.2. Events NR �

5.6.3. Actions NR �

5.6.4. The Election Process FC �

6. Diameter Message Processing NR �

6.1. Diameter Request Routing Overview FC �

6.1.1. Originating a Request FC �

6.1.2. Sending a Request FC �

6.1.3. Receiving Requests FC �

6.1.4. Processing Local Requests FC �

6.1.5. Request Forwarding FC �

6.1.6. Request Routing FC �

6.1.7. Redirecting Requests NC See Section 7.4.2 of 3GPP 29.213 compliancy for more information.

6.1.8. Relaying and Proxying Requests FC �

6.2. Diameter Answer Processing FC �

6.2.1. Processing Received Answers FC �

6.2.2. Relaying and Proxying Answers FC �

6.3. Origin-Host AVP FC �

6.4. Origin-Realm AVP FC �

6.5. Destination-Host AVP FC �

6.6. Destination-Realm AVP FC �

6.7. Routing AVPs NR �

6.7.1. Route-Record AVP NR �

6.7.2. Proxy-Info AVP NR �

6.7.3. Proxy-Host AVP NR �

6.7.4. Proxy-State AVP NR �

6.8. Auth-Application-Id AVP FC �

6.9. Acct-Application-Id AVP FC �

6.10. Inband-Security-Id AVP NR �


(3 of 6)



6.11. Vendor-Specific-Application-Id AVP FC �

6.12. Redirect-Host AVP NR �

6.13. Redirect-Host-Usage AVP NR �

6.14. Redirect-Max-Cache-Time AVP NR �

6.15. E2E-Sequence AVP NR �

7. Error Handling NR �

7.1. Result-Code AVP NR �

7.1.1. Informational NR �

7.1.2. Success NR �

7.1.3. Protocol Errors NR �

7.1.4. Transient Failures NR �

7.1.5. Permanent Failures NR �

7.2. Error Bit NR �

7.3. Error-Message AVP NR �

7.4. Error-Reporting-Host AVP NR �

7.5. Failed-AVP NR �

7.6. Experimental-Result AVP NR �

7.7. Experimental-Result-Code AVP NR �

8. Diameter User Sessions NR �

8.1. Authorization Session State Machine NR �

8.2. Accounting Session State Machine NR �

8.3. Server-Initiated Re-Auth NR �

8.3.1. Re-Auth-Request NR �

8.3.2. Re-Auth-Answer NR �

8.4. Session Termination FC �

8.4.1. Session-Termination-Request FC �

8.4.2. Session-Termination-Answer FC �

8.5. Aborting a Session FC �

8.5.1. Abort-Session-Request FC �

8.5.2. Abort-Session-Answer FC �

8.6. Inferring Session Termination from Origin-State-Id

PC In a distributed installation, 5780 DSC components (DPA, PCRF) detect and correctly handle Origin-State-Id changes of other components in the same complex.Change of Origin-State-Id by 5780 DSC clients is not handled.

8.7. Auth-Request-Type AVP NR �

8.8. Session-Id AVP NR �


(4 of 6)



Integration Guide

8.9. Authorization-Lifetime AVP NR �

8.10. Auth-Grace-Period AVP NR �

8.11. Auth-Session-State AVP NR �

8.12. Re-Auth-Request-Type AVP NR �

8.13. Session-Timeout AVP NR �

8.14. User-Name AVP NR �

8.15. Termination-Cause AVP NR �

8.16. Origin-State-Id AVP NR �

8.17. Session-Binding AVP NR �

8.18. Session-Server-Failover AVP NR �

8.19. Multi-Round-Time-Out AVP NR �

8.20. Class AVP NR �

8.21. Event-Timestamp AVP NR �

9. Accounting NR �

9.1. Server Directed Model NR �

9.2. Protocol Messages NR �

9.3. Application Document Requirements NR �

9.4. Fault Resilience NR �

9.5. Accounting Records NR �

9.6. Correlation of Accounting Records NR �

9.7. Accounting Command-Codes NR �

9.7.1. Accounting-Request NR �

9.7.2. Accounting-Answer NR �

9.8. Accounting AVPs NR �

9.8.1. Accounting-Record-Type AVP NR �

9.8.2. Acct-Interim-Interval AVP NR �

9.8.3. Accounting-Record-Number AVP NR �

9.8.4. Acct-Session-Id AVP NR �

9.8.5. Acct-Multi-Session-Id AVP NR �

9.8.6. Accounting-Sub-Session-Id AVP NR �

9.8.7. Accounting-Realtime-Required AVP NR �

10. AVP Occurrence Table NR �

10.1. Base Protocol Command AVP Table NR �

10.2. Accounting AVP Table NR �

11. IANA Considerations NR �

11.1. AVP Header NR �

11.1.1. AVP Code NR �


(5 of 6)




Table 3-13 lists compliancy information for RFC 4006 Diameter Credit Control Application.

11.1.2. AVP Flags NR �

11.2. Diameter Header NR �

11.2.1. Command Codes NR �

11.2.2. Command Flags NR �

11.3. Application Identifiers NR �

11.4. AVP Values NR �

11.4.1. Result-Code AVP Values NR �

11.4.2. Accounting-Record-Type AVP Values NR �

11.4.3. Termination-Cause AVP Values NR �

11.4.4. Redirect-Host-Usage AVP Values NR �

11.4.5. Session-Server-Failover AVP Values NR �

11.4.6. Session-Binding AVP Values NR �

11.4.7. Disconnect-Cause AVP Values NR �

11.4.8. Auth-Request-Type AVP Values NR �

11.4.9. Auth-Session-State AVP Values NR �

11.4.10. Re-Auth-Request-Type AVP Values NR �

11.4.11. Accounting-Realtime-Required AVP Values NR �

11.5. Diameter TCP/SCTP Port Numbers NR �

11.6. NAPTR Service Fields NR �

12. Diameter Protocol Related Configurable Parameters

NR �

13. Security Considerations NC �

13.1. IPsec Usage NC �

13.2. TLS Usage NC �

13.3. Peer-to-Peer Considerations NC �


14.1. Normative References NR �

14.2. Informative References NR �


Appendix A. Diameter Service Template NR �

Appendix B. NAPTR Example NR �

Appendix C. Duplicate Detection NR �

Appendix D. Intellectual Property Statement NR �


(6 of 6)



Integration Guide



1. Introduction NA �

1.1 Requirements Language NA �

1.2 Terminology NA �

1.3 Advertising Application Support NA �

2. Architecture Models NA �

3. Credit-Control Messages NA �

3.1 Credit-Control-Request (CCR) Command FC �

3.2 Credit-Control-Answer (CCA) Command FC �

4. Credit-Control Application Overview NA �

4.1 Service-Specific Rating Input and Interoperability

NA �

5. Session Based Credit-Control NA �

5.1 General Principles NA �

5.2 First Interrogation NA �

5.3 Intermediate Interrogation NA �

5.4 Final Interrogation NA �

5.5 Server-Initiated Credit Re-Authorization NA �

5.6 Graceful Service Termination NA �

5.7 Failure Procedures NA �

6 One Time Event NA �

6.1 Service Price Enquiry NA �

6.2 Balance Check NA �

6.3 Direct Debiting NA �

6.4 Refund NA �

6.5 Failure Procedure NA �

7 Credit-Control Application State Machine NA �

8 Credit-Control AVPs NA �

8.1 CC-Correlation-Id AVP NA �

8.2 CC-Request-Number AVP FC �

8.3 CC-Request-Type AVP FC �

8.4 CC-Session-Failover AVP NA �

8.5 CC-Sub-Session-Id AVP NA �

8.6 Check-Balance-Result AVP NA �

8.7 Cost-Information AVP NA �

8.8 Unit-Value AVP NA �

8.9 Exponent AVP NA �

(1 of 4)



8.10 Value-Digits AVP NA �

8.11 Currency-Code AVP NA �

8.12 Cost-Unit AVP NA �

8.13 Credit-Control AVP NA �

8.14 Credit-Control-Failure-Handling AVP NA �

8.15 Direct-Debiting-Failure-Handling AVP NA �

8.16 Multiple-Services-Credit-Control AVP NA �

8.17 Granted-Service-Unit AVP NA �

8.18 Requested-Service-Unit AVP NA �

8.19 Used-Service-Unit AVP NA �

8.20 Tariff-Time-Change AVP NA �

8.21 CC-Time AVP FC �

8.22 CC-Money AVP FC �

8.23 CC-Total-Octets AVP FC �

8.24 CC-Input-Octets AVP FC �

8.25 CC-Output-Octets AVP FC �

8.26 CC-Service-Specific-Units AVP FC �

8.27 Tariff-Change-Usage AVP NA �

8.28 Service-Identifier AVP FC �

8.29 Rating-Group AVP FC �

8.30 G-S-U-Pool-Reference AVP NA �

8.31 G-S-U-Pool-Identifier AVP NA �

8.32 CC-Unit-Type AVP NA �

8.33 Validity-Time AVP NA �

8.34 Final-Unit-Indication AVP FC �

8.35 Final-Unit-Action AVP FC �

8.36 Restriction-Filter-Rule AVP FC �

8.37 Redirect-Server AVP FC �

8.38 Redirect-Address-Type AVP FC �

8.39 Redirect-Server-Address AVP FC �

8.40 Multiple-Services-Indicator AVP NA �

8.41 Service-Context-Id AVP NA �

8.42 Service-Context-Id AVP NA �

8.43 Service-Parameter-Info AVP NA �

8.44 Service-Parameter-Type AVP NA �

8.45 Service-Parameter-Value AVP NA �

8.46 Subscription-Id AVP FC �


(2 of 4)



Integration Guide

8.47 Subscription-Id-Type AVP FC �

8.48 Subscription-Id-Data AVP FC �

8.49 User-Equipment-Info AVP FC �

8.50 User-Equipment-Info-Type AVP FC �

8.51 User-Equipment-Info-Value AVP FC �

9 Result Code AVP Values FC �

9.1 Transient Failures NA �

9.2 Permanent Failures NA �

10 AVP Occurrence Table NA �

10.1 Credit-Control AVP Table NA �

10.2 Re-Auth-Request/Answer AVP Table NA �

11 RADIUS/Diameter Credit-Control Interworking

NA �

12 IANA Considerations NA �

12.1 Application Identifier NA �

12.2 Command Codes NA �

12.3 AVP Codes NA �

12.4 Result-Code AVP Values FC �

12.5 CC-Request-Type AVP FC �

12.6 CC-Session-Failover AVP FC �

12.7 CC-Unit-Type AVP NA �

12.8 Check-Balance-Result AVP NA �

12.9 Credit-Control AVP NA �

12.10 Credit-Control-Failure-Handling AVP NA �

12.11 Direct-Debiting-Failure-Handling AVP NA �

12.12 Final-Unit-Action AVP FC �

12.13 Multiple-Services-Indicator AVP NA �

12.14 Redirect-Address-Type AVP FC �

12.15 Requested-Action AVP NA �

12.16 Subscription-Id-Type AVP FC �

12.17 Tariff-Change-Usage AVP NA �

12.18 User-Equipment-Info-Type AVP FC �

13 Credit-Control Application Related Parameters

NA �

14 Security Considerations NA �

14.1 Direct Connection with Redirects NA �

15 References NA �

15.1 Normative References NA �


(3 of 4)




Table 3-14 lists compliancy information for RFC 5176 Dynamic Authorization Extensions to Remote Authentication Dial In User Service (RADIUS).


15.2 Informative References NA �

Appendix A Credit-Control Sequences NA �

A.1 Flow I NA �

A.2 Flow II NA �

A.3 Flow III NA �

A.4 Flow IV NA �

A.5 Flow V NA �

A.6 Flow VI NA �

A.7 Flow VII NA �

A.8 Flow VIII NA �

A.9 Flow IX NA �


(4 of 4)



1.1. Applicability NR �

1.2. Requirements Language NR �

1.3. Terminology NR �

2. Overview NR �

2.1. Disconnect Messages (DMs) FC �

2.2. Change-of-Authorization (CoA) Messages

FC �

2.3. Packet Format FC �


3.1. Proxy State FC �

3.2. Authorize Only FC �

3.3. State FC �

3.4. Message-Authenticator NC �

3.5. Error-Cause FC �

3.6. Table of Attributes FC �

4. Diameter Considerations NR �

(1 of 2)



Integration Guide

3.17 Statement of compliance information for SMPP 3.4

Table 3-15 lists compliancy information for Short Message Peer to Peer Protocol Specification v3.4.

Table 3-15 SMPP 3.4 compliancy

5. IANA Considerations NR �

6. Security Considerations HD �

6.1. Authorization Issues NA �

6.2. IPsec Usage Guidelines NR �

6.3. Replay Protection NA �

7. Example Traces NR �

8. References HD �

8.1. Normative References NR �

8.2. Informative References NR �

9. Acknowledgments NR �

Appendix A � NR �


(2 of 2)


1.0 Introduction HD �

1.1 SMPP Overview NA �

1.2 Scope NA �

1.3 Glossary NA �

1.4 References NA �

2. SMPP Protocol Overview HD �

2.1 SMPP Protocol Definition PC Support Transceiver

2.2 SMPP Session Description PC Support OPEN, BOUND_TRX, CLOSED

2.2.1 Outbind NC �

2.3 SMPP PDUs PC Support bind_transceiver, bind_transceiver_resp, unbind, unbind_resp, submit_sm, submit_sm_resp,

2.4 SMPP Network Layer Connections

HD �

2.5 SMPP messages sent from ESME to SMSC

PC Support submit_sm

(1 of 7)



2.5.1 SMPP Message Response from SMSC to ESME

PC Support submit_sm_resp

2.5.2 Typical SMPP session sequence - ESME Transmitter

FC �

2.6 SMPP messages sent from SMSC to ESME

HD �

2.6.1 SMPP Message Response from ESME to SMSC

NA �

2.6.2 Typical SMPP session sequence - ESME Receiver

NA �

2.7 Duplex message exchange between an SMSC and an ESME

PC Support submit_sm

2.7.1 Typical SMPP session sequence - ESME Transceiver

FC �

2.8 SMPP Error Handling FC �

2.9 SMPP Timers FC �

2.10 Message Modes HD �

2.10.1 Store and Forward Message Mode

FC �

2.10.2 Datagram Message Mode NA �

2.10.3 Transaction Message Mode NA �

2.11 Message Types NC �

3. SMPP PDU Type and Format Definitions

HD �

3.1 SMPP PDU - Type Definitions FC �

3.1.1 SMPP Parameter Field Size Notation

FC �

3.2 SMPP PDU Format - Overview

FC �

3.2.1 SMPP PDU Layout FC �

3.2.2 SMPP PDU Length FC �

3.2.3 SMPP Message length and extended message length

FC �

3.2.4 Optional Parameters FC �

3.2.4.1 Optional Parameter Format FC �

3.3 Guidelines for SMPP Forward Compatibility

NC �

3.4 Guidelines for SMPP Backward Compatibility

FC �

4. SMPP PDU Definition HD �

4.1 �BIND� Operation PC �


(2 of 7)



Integration Guide

4.1.1 �BIND_TRANSMITTER� Syntax

NA �

4.1.2 �BIND_TRANSMITTER_RESP� Syntax

NA �

4.1.3 �BIND_RECEIVER� Syntax NA �

4.1.4 �BIND_RECEIVER_RESP� NA �

4.1.5 �BIND_TRANSCEIVER� Syntax

FC �

4.1.6 �BIND_TRANSCEIVER_RESP� FC �

4.1.7 �OUTBIND� Operation. NC �

4.1.7.1 �OUTBIND� Syntax NC �

4.2 �UNBIND� Operation HD �

4.2.1 �UNBIND� FC �

4.2.2 �UNBIND_RESP FC �

4.3 �GENERIC_NACK� PDU NC �

4.3.1 �GENERIC_NACK� Syntax NC �

4.4 �SUBMIT_SM� Operation NA �

4.4.1 �SUBMIT_SM� Syntax NA �

4.4.1.1 Source and Destination Addressing

NA �

4.4.1.2 Message Replace operation in �SUBMIT_SM

NA �

4.4.2 �SUBMIT_SM_RESP NA �

4.5 �SUBMIT_MULTI� Operation NA �

4.5.1 �SUBMIT_MULTI� Syntax NA �

4.5.1.1 Destination Address definition

NA �

4.5.1.2 Distribution List (DL) definition

NA �

4.5.2 �SUBMIT_MULTI_RESP� Syntax

NA �

4.5.2.1 Unsuccessful deliveries NA �

4.6 �DELIVER_SM� Operation NA �

4.6.1 �DELIVER_SM� Syntax NA �

4.6.2 �DELIVER_SM_RESP� Syntax NA �

4.7 �DATA_SM� Operation NA �

4.7.1 �DATA_SM� Syntax NA �

4.7.2 �DATA_SM_RESP� Syntax NA �

4.8 �QUERY_SM� Operation NA �

4.8.1 �QUERY_SM� Syntax NA �


(3 of 7)



4.8.2 �QUERY_SM_RESP� Syntax NA �

4.9 �CANCEL_SM� Operation NA �

4.9.1 �CANCEL_SM� Syntax NA �

4.9.2 �CANCEL_SM_RESP� Syntax NA �

4.10 �REPLACE_SM� Operation NA �

4.10.1 �REPLACE_SM� Syntax NA �

4.10.2 �REPLACE_SM_RESP� Syntax NA �

4.11 �ENQUIRE_LINK� Operation HD �

4.11.1 �ENQUIRE_LINK� Syntax FC �

4.11.2 �ENQUIRE_LINK_RESP� Syntax

FC �

4.12 �ALERT_NOTIFICATION� Operation

NA �

4.12.1 �ALERT_NOTIFICATION� Syntax

NA �

5. SMPP Parameter Definition FC �

5.1 Command Header Parameters

FC �

5.1.1 command_length FC �

5.1.2 command_id FC �

5.1.2.1 SMPP Command set FC �

5.1.3 command_status FC �

5.1.4 sequence_number FC �

5.2 Mandatory SMPP Parameters FC �

5.2.1 system_id FC �

5.2.2 password FC �

5.2.3 system_type FC �

5.2.4 interface_version FC �

5.2.5 addr_ton, source_addr_ton, dest_addr_ton, esme_addr_ton

FC �

5.2.6 addr_npi, source_addr_npi, dest_addr_npi, esme_addr_npi

FC �

5.2.7 address_range NA �

5.2.8 source_addr FC �

5.2.9 destination_addr FC �

5.2.10 esme_addr NA �

5.2.11 service_type NA �

5.2.12 esm_class FC �


(4 of 7)



Integration Guide

5.2.13 protocol_id FC �

5.2.14 priority_flag FC �

5.2.15 schedule_delivery_time FC �

5.2.16 registered_delivery FC �

5.2.18 replace_if_present_flag FC �

5.2.19 data_coding FC �

5.2.20 sm_default_msg_id FC �

5.2.21 sm_length FC �

5.2.22 short_message FC �

5.2.23 message_id FC �

5.2.24 number_of_dests NA �

5.2.25 dest_flag NA �

5.2.26 no_unsuccess NA �

5.2.27 dl_name NA �

5.2.28 message_state NA �

5.3 SMPP Optional Parameter Description

FC �

5.3.1 Optional Parameter Tag Identifiers

FC �

5.3.2 SMPP Optional Parameter Tag definitions

FC �

5.3.2.1 dest_addr_subunit FC �

5.3.2.2 source_addr_subunit FC �

5.3.2.3 dest_network_type FC �

5.3.2.4 source_network_type FC �

5.3.2.5 dest_bearer_type FC �

5.3.2.6 source_bearer_type FC �

5.3.2.7 dest_telematics_id FC �

5.3.2.8 source_telematics_id FC �

5.3.2.9 qos_time_to_live FC �

5.3.2.10 payload_type FC �

5.3.2.11 additional_status_info_text FC �

5.3.2.12 receipted_message_id FC �

5.3.2.13 ms_msg_wait_facilities FC �

5.3.2.14 privacy_indicator FC �

5.3.2.15 source_subaddress FC �

5.3.2.16 dest_subaddress FC �

5.3.2.17 user_message_reference FC �


(5 of 7)



5.3.2.18 user_response_code FC �

5.3.2.19 language_indicator FC �

5.3.2.20 source_port FC �

5.3.2.21 destination_port FC �

5.3.2.22 sar_msg_ref_num FC �

5.3.2.23 sar_total_segments FC �

5.3.2.24 sar_segment_seqnum FC �

5.3.2.25 sc_interface_version FC �

5.3.2.26 display_time FC �

5.3.2.27 ms_validity FC �

5.3.2.28 dpf_result FC �

5.3.2.29 set_dpf FC �

5.3.2.30 ms_availability_status FC �

5.3.2.31 network_error_code FC �

5.3.2.32 message_payload FC �

5.3.2.33 delivery_failure_reason FC �

5.3.2.34 more_messages_to_send FC �

5.3.2.35 message_state FC �

5.3.2.36 callback_num FC �

5.3.2.37 callback_num_pres_ind FC �

5.3.2.38 callback_num_atag FC �

5.3.2.39 number_of_messages FC �

5.3.2.40 sms_signal FC �

5.3.2.41 alert_on_message_delivery FC �

5.3.2.42 its_reply_type FC �

5.3.2.43 its_session_info FC �

5.3.2.44 ussd_service_op FC �

6. Network Implementation HD �

6.1 Network Error Codes NA �

6.2 Maximum Message Length NA �

7. General Definitions HD �

7.1 Time Definitions HD �

7.1.1 Time Format NA �

7.1.1.1 Absolute Time format NA �

7.1.1.2 Relative Time Format NA �

7.2 Timer Definitions FC �

Appendix A UNIX Regular Expressions HD �


(6 of 7)



Integration Guide

Appendix B Delivery Receipt Format NA �

Appendix C SMPP and Year 2000 Conformance

FC �


(7 of 7)

Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R4 May 2013 A-13HE 07630 AAAD TQZZA Edition 01Integration Guide

A. Diameter Result Codes

A.1 Diameter result codes overview A-2


A-2 May 2013 Alcatel-Lucent 5780 Dynamic Services Controller, Release 5.1 R43HE 07630 AAAD TQZZA Edition 01

Integration Guide

A.1 Diameter result codes overview

This appendix describes the Diameter result codes you may receive when using the 5780 DSC.

Table A-1 lists the 3GPP result codes you may receive when using the 5780 DSC.

Table A-1 3GPP Result Codes

Note � Where there are duplicate Result Code Names, the 5780 DSC uses the Result Code/Vendor ID based on the context relevant to the message it is processing.

For example, if you are using Result Code 2001 in Gx, the Vendor ID IETF_IANA is used. If you are using Result Code 2001 in Sh, the Vendor ID is 3GPP is used.

Result Code

Vendor ID Result Code Name 29.230 V8.5.0

29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

1001 IETF_IANA DIAMETER_MULTI_ROUND_AUTH

2001 3GPP DIAMETER_FIRST_REGISTRATION

x x

2001 IETF_IANA DIAMETER_SUCCESS

2002 IETF_IANA DIAMETER_LIMITED_SUCCESS

2002 3GPP DIAMETER_SUBSEQUENT_REGISTRATION

x x

2003 IETF_IANA DIAMETER_FIRST_REGISTRATION

2003 3GPP DIAMETER_UNREGISTERED_SERVICE

x x

2004 3GPP DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED

x x

2004 IETF_IANA DIAMETER_SUBSEQUENT_REGISTRATION

2005 IETF_IANA DIAMETER_UNREGISTERED_SERVICE

2006 IETF_IANA DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED

2007 IETF_IANA DIAMETER_SERVER_SELECTION

2008 IETF_IANA DIAMETER_SUCCESS_AUTH_SENT_SERVER_NOT_STORED

3001 IETF_IANA DIAMETER_COMMAND_UNSUPPORTED

(1 of 6)



3002 IETF_IANA DIAMETER_UNABLE_TO_DELIVER

3003 IETF_IANA DIAMETER_REALM_NOT_SERVED

3004 IETF_IANA DIAMETER_TOO_BUSY

3005 IETF_IANA DIAMETER_LOOP_DETECTED

3006 IETF_IANA DIAMETER_REDIRECT_INDICATION

3007 IETF_IANA DIAMETER_APPLICATION_UNSUPPORTED

3008 IETF_IANA DIAMETER_INVALID_HDR_BITS

3009 IETF_IANA DIAMETER_INVALID_AVP_BITS

3010 IETF_IANA DIAMETER_UNKNOWN_PEER

4001 IETF_IANA DIAMETER_AUTHENTICATION_REJECTED

4101 3GPP DIAMETER_PRIOR_UPDATE_INPROGRESS

x

4002 IETF_IANA DIAMETER_OUT_OF_SPACE

4003 IETF_IANA ELECTION_LOST

4005 IETF_IANA DIAMETER_ERROR_MIP_REPLY_FAILURE

4006 IETF_IANA DIAMETER_ERROR_HA_NOT_AVAILABLE

4007 IETF_IANA DIAMETER_ERROR_BAD_KEY

4008 IETF_IANA DIAMETER_ERROR_MIP_FILTER_NOT_SUPPORTED

4010 IETF_IANA DIAMETER_END_USER_SERVICE_DENIED

4011 IETF_IANA DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE

4012 IETF_IANA DIAMETER_CREDIT_LIMIT_REACHED

4013 IETF_IANA DIAMETER_USER_NAME_REQUIRED

4041 ETSI DIAMETER_INSUFFICIENT_RESOURCES

4043 ETSI DIAMETER_COMMIT_FAILURE

Result Code


29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

(2 of 6)



Integration Guide

4045 ETSI DIAMETER_QOS_PROFILE_FAILURE

4046 ETSI DIAMETER_ACCESS_PROFILE_FAILURE

4100 3GPP DIAMETER_USER_DATA_NOT_AVAILABLE

x x

4141 3GPP DIAMETER_PCC_BEARER_EVENT

x x

4142 3GPP DIAMETER_BEARER_EVENT x x x

5001 IETF_IANA DIAMETER_AVP_UNSUPPORTED

5001 3GPP DIAMETER_ERROR_USER_UNKNOWN

x x

5002 3GPP DIAMETER_ERROR_IDENTITIES_DONT_MATCH

x x

5002 IETF_IANA DIAMETER_UNKNOWN_SESSION_ID

5003 IETF_IANA DIAMETER_AUTHORIZATION_REJECTED

5003 3GPP DIAMETER_ERROR_IDENTITY_NOT_REGISTERED

x x

5004 3GPP DIAMETER_ERROR_ROAMING_NOT_ALLOWED

x x

5004 IETF_IANA DIAMETER_INVALID_AVP_VALUE

5005 3GPP DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED

x x

5005 IETF_IANA DIAMETER_MISSING_AVP

5006 3GPP DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED

x x

5006 IETF_IANA DIAMETER_RESOURCES_EXCEEDED

5007 IETF_IANA DIAMETER_CONTRADICTING_AVPS

5007 3GPP DIAMETER_ERROR_IN_ASSIGNMENT_TYPE

x x

5008 IETF_IANA DIAMETER_AVP_NOT_ALLOWED

5008 3GPP DIAMETER_ERROR_TOO_MUCH_DATA

x x

5009 IETF_IANA DIAMETER_AVP_OCCURS_TOO_MANY_TIMES

5009 3GPP DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA

x x

Result Code


29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

(3 of 6)



5010 IETF_IANA DIAMETER_NO_COMMON_APPLICATION

5011 3GPP DIAMETER_ERROR_FEATURE_UNSUPPORTED

x x

5011 IETF_IANA DIAMETER_UNSUPPORTED_VERSION

5012 IETF_IANA DIAMETER_UNABLE_TO_COMPLY

5013 IETF_IANA DIAMETER_INVALID_BIT_IN_HEADER

5014 IETF_IANA DIAMETER_INVALID_AVP_LENGTH

5015 IETF_IANA DIAMETER_INVALID_MESSAGE_LENGTH

5016 IETF_IANA DIAMETER_INVALID_AVP_BIT_COMBO

5017 IETF_IANA DIAMETER_NO_COMMON_SECURITY

5018 IETF_IANA DIAMETER_RADIUS_AVP_UNTRANSLATABLE

5024 IETF_IANA DIAMETER_ERROR_NO_FOREIGN_HA_SERVICE

5025 IETF_IANA DIAMETER_ERROR_END_TO_END_MIP_KEY_ENCRYPTION

5030 IETF_IANA DIAMETER_USER_UNKNOWN

5031 IETF_IANA DIAMETER_RATING_FAILED

5032 IETF_IANA DIAMETER_ERROR_USER_UNKNOWN

5033 IETF_IANA DIAMETER_ERROR_IDENTITIES_DONT_MATCH

5034 IETF_IANA DIAMETER_ERROR_IDENTITY_NOT_REGISTERED

5035 IETF_IANA DIAMETER_ERROR_ROAMING_NOT_ALLOWED

5036 IETF_IANA DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED

5037 IETF_IANA DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED

5038 IETF_IANA DIAMETER_ERROR_IN_ASSIGNMENT_TYPE

5039 IETF_IANA DIAMETER_ERROR_TOO_MUCH_DATA

Result Code


29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

(4 of 6)



Integration Guide

5040 IETF_IANA DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA

5041 ETSI DIAMETER_MODIFICATION_FAILURE

5061 3GPP INVALID_SERVICE_INFORMATION

x x x x x

5062 3GPP FILTER_RESTRICTIONS x x x x x

5063 3GPP REQUESTED_SERVICE_NOT_AUTHORIZED

x x x

5064 3GPP DUPLICATED_AF_SESSION x x x

5065 3GPP IP_CAN_SESSION_NOT_AVAILABLE

x x x

5066 3GPP UNAUTHORIZED_NON_EMERGENCY_SESSION

x x

5067 3GPP UNAUTHORIZED_SPONSORED_DATA_CONNECTIVITY

x

5100 3GPP DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED

x x x

5101 3GPP DIAMETER_ERROR_OPERATION_NOT_ALLOWED

x x x

5102 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ

x x x

5103 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED

x x x

5104 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED

x x x

5105 3GPP DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC

x x x

5106 3GPP DIAMETER_ERROR_SUBS_DATA_ABSENT

x x x

5107 3GPP DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA

x x x

5108 3GPP DIAMETER_ERROR_DSAI_NOT_AVAILABLE

x x x

5131 IETF_IANA DIAMETER_RATING_FAILED

5140 3GPP DIAMETER_ERROR_INITIAL_PARAMETERS

x x x x x

5141 3GPP DIAMETER_ERROR_TRIGGER_EVENT

x x x x x

5142 3GPP DIAMETER_PCC_RULE_EVENT

x x x x x

Result Code


29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

(5 of 6)



Table A-2 lists the ETSI result codes you may receive when using the 5780 DSC.

Table A-2 ETSI Result Codes

Table A-3 lists the RFC result codes you may receive when using the 5780 DSC.

Table A-3 RFC result codes

5143 3GPP DIAMETER_ERROR_BEARER_NOT_AUTHORIZED

x x x x x

5143 3GPP DIAMETER_ERROR_TRAFFIC_MAPPING_INFO_REJECTED

x x x x x


x x x

5145 3GPP DIAMETER_QOS_RULE_EVENT

x x x

5147 3GPP DIAMETER_ERROR_CONFLICTING_REQUEST

x x x

Result Code


29.230 V9.6.0

29.212 V8.11.1

29.212 v9.6.1

29.212 v10.2.1

29.214 V8.9.1

29.214 v9.6.0

29.214 v10.2.1

29.329 V8.7.0

(6 of 6)

Result Code

Vendor ID Result Code Name ETSI TS183026 V 3.0.1

4041 ETSI DIAMETER_INSUFFICIENT_RESOURCES x

4043 ETSI DIAMETER_COMMIT_FAILURE x

4045 ETSI DIAMETER_QOS_PROFILE_FAILURE x

4046 ETSI DIAMETER_ACCESS_PROFILE_FAILURE x

5041 ETSI DIAMETER_MODIFICATION_FAILURE x

Result Code

Vendor ID Result Code Name RFC 4004

RFC 4849

RFC 4006

RFC 4740

RFC 3588

1001 IETF_IANA DIAMETER_MULTI_ROUND_AUTH x

2001 3GPP DIAMETER_FIRST_REGISTRATION

2001 IETF_IANA DIAMETER_SUCCESS x

2002 IETF_IANA DIAMETER_LIMITED_SUCCESS x

2002 3GPP DIAMETER_SUBSEQUENT_REGISTRATION

2003 IETF_IANA DIAMETER_FIRST_REGISTRATION x

2003 3GPP DIAMETER_UNREGISTERED_SERVICE

2004 3GPP DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED

(1 of 4)



Integration Guide

2004 IETF_IANA DIAMETER_SUBSEQUENT_REGISTRATION x

2005 IETF_IANA DIAMETER_UNREGISTERED_SERVICE x

2006 IETF_IANA DIAMETER_SUCCESS_SERVER_NAME_NOT_STORED

x

2007 IETF_IANA DIAMETER_SERVER_SELECTION x

2008 IETF_IANA DIAMETER_SUCCESS_AUTH_SENT_SERVER_NOT_STORED

x

3001 IETF_IANA DIAMETER_COMMAND_UNSUPPORTED x

3002 IETF_IANA DIAMETER_UNABLE_TO_DELIVER x

3003 IETF_IANA DIAMETER_REALM_NOT_SERVED x

3004 IETF_IANA DIAMETER_TOO_BUSY x

3005 IETF_IANA DIAMETER_LOOP_DETECTED x

3006 IETF_IANA DIAMETER_REDIRECT_INDICATION x

3007 IETF_IANA DIAMETER_APPLICATION_UNSUPPORTED x

3008 IETF_IANA DIAMETER_INVALID_HDR_BITS x

3009 IETF_IANA DIAMETER_INVALID_AVP_BITS x

3010 IETF_IANA DIAMETER_UNKNOWN_PEER x

4001 IETF_IANA DIAMETER_AUTHENTICATION_REJECTED x

4101 3GPP DIAMETER_PRIOR_UPDATE_IN_PROGRESS

4002 IETF_IANA DIAMETER_OUT_OF_SPACE x

4003 IETF_IANA ELECTION_LOST x

4005 IETF_IANA DIAMETER_ERROR_MIP_REPLY_FAILURE x

4006 IETF_IANA DIAMETER_ERROR_HA_NOT_AVAILABLE x

4007 IETF_IANA DIAMETER_ERROR_BAD_KEY x

4008 IETF_IANA DIAMETER_ERROR_MIP_FILTER_NOT_SUPPORTED x

4010 IETF_IANA DIAMETER_END_USER_ SERVICE_DENIED x

4011 IETF_IANA DIAMETER_CREDIT_CONTROL_NOT_APPLICABLE x

4012 IETF_IANA DIAMETER_CREDIT_LIMIT_REACHED x

4013 IETF_IANA DIAMETER_USER_NAME_REQUIRED x

4041 ETSI DIAMETER_INSUFFICIENT_RESOURCES

4043 ETSI DIAMETER_COMMIT_FAILURE

4045 ETSI DIAMETER_QOS_PROFILE_FAILURE

4046 ETSI DIAMETER_ACCESS_PROFILE_FAILURE

4100 3GPP DIAMETER_USER_DATA_NOT_AVAILABLE

4141 3GPP DIAMETER_PCC_BEARER_EVENT

4142 3GPP DIAMETER_BEARER_EVENT

5001 IETF_IANA DIAMETER_AVP_UNSUPPORTED x

Result Code


RFC 4849

RFC 4006

RFC 4740

RFC 3588

(2 of 4)



5001 3GPP DIAMETER_ERROR_USER_UNKNOWN

5002 3GPP DIAMETER_ERROR_IDENTITIES_DONT_MATCH

5002 IETF_IANA DIAMETER_UNKNOWN_SESSION_ID x

5003 IETF_IANA DIAMETER_AUTHORIZATION_REJECTED x

5003 3GPP DIAMETER_ERROR_IDENTITY_NOT_REGISTERED

5004 3GPP DIAMETER_ERROR_ROAMING_NOT_ALLOWED

5004 IETF_IANA DIAMETER_INVALID_AVP_VALUE x

5005 3GPP DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED

5005 IETF_IANA DIAMETER_MISSING_AVP x

5006 3GPP DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED

5006 IETF_IANA DIAMETER_RESOURCES_EXCEEDED x

5007 IETF_IANA DIAMETER_CONTRADICTING_AVPS x

5007 3GPP DIAMETER_ERROR_IN_ASSIGNMENT_TYPE

5008 IETF_IANA DIAMETER_AVP_NOT_ALLOWED x

5008 3GPP DIAMETER_ERROR_TOO_MUCH_DATA

5009 IETF_IANA DIAMETER_AVP_OCCURS_TOO_MANY_TIMES x

5009 3GPP DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA

5010 IETF_IANA DIAMETER_NO_COMMON_APPLICATION x

5011 3GPP DIAMETER_ERROR_FEATURE_UNSUPPORTED

5011 IETF_IANA DIAMETER_UNSUPPORTED_VERSION x

5012 IETF_IANA DIAMETER_UNABLE_TO_COMPLY x

5013 IETF_IANA DIAMETER_INVALID_BIT_IN_HEADER x

5014 IETF_IANA DIAMETER_INVALID_AVP_LENGTH x

5015 IETF_IANA DIAMETER_INVALID_MESSAGE_LENGTH x

5016 IETF_IANA DIAMETER_INVALID_AVP_BIT_COMBO x

5017 IETF_IANA DIAMETER_NO_COMMON_SECURITY x

5018 IETF_IANA DIAMETER_RADIUS_AVP_UNTRANSLATABLE x

5024 IETF_IANA DIAMETER_ERROR_NO_FOREIGN_HA_SERVICE x

5025 IETF_IANA DIAMETER_ERROR_END_TO_END_MIP_KEY_ENCRYPTION

x

5030 IETF_IANA DIAMETER_USER_UNKNOWN x

5031 IETF_IANA DIAMETER_RATING_FAILED x

5032 IETF_IANA DIAMETER_ERROR_USER_UNKNOWN x

5033 IETF_IANA DIAMETER_ERROR_IDENTITIES_DONT_MATCH x

5034 IETF_IANA DIAMETER_ERROR_IDENTITY_NOT_REGISTERED x

Result Code


RFC 4849

RFC 4006

RFC 4740

RFC 3588

(3 of 4)



Integration Guide

5035 IETF_IANA DIAMETER_ERROR_ROAMING_NOT_ALLOWED x

5036 IETF_IANA DIAMETER_ERROR_IDENTITY_ALREADY_REGISTERED

x

5037 IETF_IANA DIAMETER_ERROR_AUTH_SCHEME_NOT_SUPPORTED

x

5038 IETF_IANA DIAMETER_ERROR_IN_ASSIGNMENT_TYPE x

5039 IETF_IANA DIAMETER_ERROR_TOO_MUCH_DATA x

5040 IETF_IANA DIAMETER_ERROR_NOT_SUPPORTED_USER_DATA x

5041 ETSI DIAMETER_MODIFICATION_FAILURE

5061 3GPP INVALID_SERVICE_INFORMATION

5062 3GPP FILTER_RESTRICTIONS

5063 3GPP REQUESTED_SERVICE_NOT_AUTHORIZED

5064 3GPP DUPLICATED_AF_SESSION

5065 3GPP IP_CAN_SESSION_NOT_AVAILABLE

5100 3GPP DIAMETER_ERROR_USER_DATA_NOT_RECOGNIZED

5101 3GPP DIAMETER_ERROR_OPERATION_NOT_ALLOWED

5102 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_READ

5103 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_MODIFIED

5104 3GPP DIAMETER_ERROR_USER_DATA_CANNOT_BE_NOTIFIED

5105 3GPP DIAMETER_ERROR_TRANSPARENT_DATA_OUT_OF_SYNC

5106 3GPP DIAMETER_ERROR_SUBS_DATA_ABSENT

5107 3GPP DIAMETER_ERROR_NO_SUBSCRIPTION_TO_DATA

5108 3GPP DIAMETER_ERROR_DSAI_NOT_AVAILABLE

5131 IETF_IANA DIAMETER_RATING_FAILED x

5140 3GPP DIAMETER_ERROR_INITIAL_PARAMETERS

5141 3GPP DIAMETER_ERROR_TRIGGER_EVENT

5142 3GPP DIAMETER_PCC_RULE_EVENT

5143 3GPP DIAMETER_ERROR_BEARER_NOT_AUTHORIZED



5145 3GPP DIAMETER_QOS_RULE_EVENT

5147 3GPP DIAMETER_ERROR_CONFLICTING_REQUEST

Result Code


RFC 4849

RFC 4006

RFC 4740

RFC 3588

(4 of 4)

Customer documentation and product support

Customer documentationhttp://www.alcatel-lucent.com/myaccessProduct manuals and documentation updates are available at alcatel-lucent.com. If you are a new user and require access to this service, please contact your Alcatel-Lucent sales representative.

Technical Supporthttp://support.alcatel-lucent.com

Documentation [email protected]

http://www.alcatel-lucent.com/myaccess

http://support.alcatel-lucent.com

mailto:[email protected]

5780 dsc integration guide

Documents

alcatellucent logo

alcatellucent pursuant

alcatellucent grants

alcatellucent harmless

incomplete information

failure of products

t i o n g u i d ewhen

internal use