Southbound Rx Interface
|
|
- Norman Powers
- 6 years ago
- Views:
Transcription
1 Overview, page 1 Diameter Adaptor Connectivity, page 1 Protocol Support, page 2 Diameter Connection Establishment, page 2 Diameter Base RFC Compliance, page 2 Rx Protocol Message Formats, page 2 Cisco Rx Protocol Specific Attributes, page 9 Overview MOG provides a Diameter-based southbound Rx interface for interaction with PCRF. The Rx interface supports the modification of the following QoS updates: Default bearer Dedicated bearer Sponsored data MOG includes application ID in Auth-Application-Id AVP and the vendor ID in the Vendor-Id AVP of the Vendor-Specific-Application-Id AVP contained in the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. MOG creates a new Rx Session whenever a new API session is created for Update QoS API. All the commands on the Rx interface for the Rx Session include the session identifier of the Rx Session. The session-id AVP is populated with the session identifier. Diameter Adaptor Connectivity MOG supports two models for Diameter adaptor connectivity across Rx to PCRFs. 1
2 Protocol Support 1 Direct Connect. MOG establishes peer connections with the PCRFs. The Direct Connect model may be used when a DRA is not required to route the Rx session to a PCRF based on a binding. In this case, the PCRF to which MOG connects can locate the corresponding Gx session record for the UE, provided the Gx session exists in the network. 2 DRA Connect. MOG establishes peer connections with DRAs which route Rx messages to PCRFs based on UE bindings. DRA Connect is the more common model because bindings are typically required to route the Rx message to the same PCRF that handles the Gx sessions for the UE. Protocol Support The Cisco Enhanced Rx Policy Interface is based on the 3GPP Rx protocol. It uses both the Diameter Base (RFC 6733) and NASREQ Diameter Application (RFC 4005) messages. MOG acts as a Diameter client and PCRF acts as a Diameter server. The Diameter Application-ID used for the Cisco Enhanced Rx Policy Interface is , which is the Rx application IDas specified in 3GPP TS v12. Diameter Connection Establishment MOG supports diameter peer connections using TCP as the transport protocol. After establishing the peer connection, MOG and partner peer advertise the support of the appropriate diameter application using the Capability Exchange procedure. MOG advertises support for 3GPP (10415) and Cisco (9) vendor-specific attributes. MOG can be configured to establish multiple peer connections to a partner peer. This is sometimes useful to overcome performance limitations of a single peer connection. Each diameter peer connection will utilize the same IP address, but a different ephemeral port and a different Origin-Host. The value of the Session-Id AVP for each Rx session is unique to MOG. Diameter Base RFC Compliance The Cisco Enhanced Rx Policy Interface complies with RFC 6733 for Diameter Base. Restrictions on Diameter Base RFC Compliance MOG will not use the accounting messages defined in the Diameter Base protocol. The Session-Binding AVP is ignored by MOG. MOG uses the value of Origin-Host AVP received in the latest AAA or RAR as the Destination-Host AVP of the next request. Rx Protocol Message Formats The following sections describe the various messages used by the Rx Policy interface. 2
3 AA-Request (AAR) Note Some AVPs are Cisco vendor-specific AVPs that may appear in the message. Some AVPs are standard V12 AVPs, but are not expected to be exchanged between MOG and the PCRF for the mobility orchestration use cases. The AVPs should still be in the dictionary, and a PCRF is expected to support these other standard AVPs in order to successfully interoperate with other AFs. AA-Request (AAR) The AAR command, indicated by the Command-Code field set to 265 and the 'R' bit set in the Command Flags field, is sent by MOG to the PCRF. <AA-Request> ::= < Diameter Header: 265, REQ, PXY > { Auth-Application-Id } { Destination-Realm } [ Destination-Host ] [ IP-Domain-Id ] [ AF-Application-Identifier ] *[ Media-Component-Description ] [ Service-Info-Status ] [ AF-Charging-Identifier ] [ SIP-Forking-Indication ] *[ Specific-Action ] *[ Subscription-Id ] *[ Supported-Features ] [ Reservation-Priority ] [ Framed-IP-Address ] [ Framed-IPv6-Prefix ] [ Called-Station-Id ] [ Service-URN ] [ Sponsored-Connectivity-Data ] [ Dynamic-PCC-Requested-QoS ] [ MPS-Identifier ] [ Rx-Request-Type ] *[ Required-Access-Info ] *[ Route-Record ] 3
4 AA-Answer (AAA) Note 1 MOG identifies the UE to the PCRF via the Subscription-ID AVPs (1 as type IMSI and 1 as type E164) in the AAR message. 2 MOG populates the AF-Application-Identifier AVP have the value Dynamic-QoS i.e hex value of 44796e616d69632d516f53 in case of default bearer and will have the value OTT-Service-1 i.e hex value of 4f54542d d31 in case of dedicated bearer. 3 MOG populates the Application-Service-provider-Identifier AVP used for sponsored data connectivity with value UpdateQoS.<Tenant domain> where <Tenant domain> is the tenant domain of the subscriber who initated the request. For example, if the request is made by a subscriber of domain acme.com, the value is UpdateQoS.acme.com 4 MOG sends Specific-Action AVP in AAR message to arm event Triggers on PCRF: INDICATION_OF_LOSS_OF_BEARER (2) INDICATION_OF_RELEASE_OF_BEARER (4) INDICATION_OF_FAILED_RESOURCES_ALLOCATION (9) INDICATION_OF_SUCCESSFUL_RESOURCES_ALLOCATION (8) USAGE_REPORT (11), in case of Volume received in MOG API request. CUSTOM_DPCC_STATUS_REPORT (200), in case of MOG DPCC CRD configuration present. 5 MOG sends Dedicated-Bearer-QoS AVP in Dynamic-PCC-Requested-QoS AVP of AAR message when Service-Info-Status is FINAL_SERVICE_INFORMATION (0). For example: Dynamic-PCC-Requested-QoS: Dedicated-Bearer-QoS: QoS-Class-Identifier: Interactive (5) Allocation-Retention-Priority: Priority-Level: 3 Pre-emption-Capability: PRE-EMPTION_CAPABILITY_ENABLED (0) Pre-emption-Vulnerability: PRE-EMPTION_VULNERABILITY_DISABLED AA-Answer (AAA) The AAA command indicated by the Command-Code field set to 265 and the 'R' bit cleared in the Command Flags is sent by PCRF in response to an AAR command. 4
5 Re-Auth-Request (RAR) <AA-Answer> ::= < Diameter Header: 265, PXY > { Auth-Application-Id } [ Result-Code ] [ Experimental-Result ] *[ Access-Network-Charging-Identifier ] [ Access-Network-Charging-Address ] [ Acceptable-Service-Info ] [ IP-CAN-Type ] [ RAT-Type ] *[ Flows ] *[ Supported-Features ] *[ Class ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] *[ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] Note 1 Origin Host AVP received in the message is stored and used to populate the Destination Host AVP in the next outgoing message for the Rx Session. 2 An AAA with a Result-Code AVP value of 2001 (DIAMETER_SUCCESS) does not reflect the success or failure of the requested action of the Rx AAR. It indicates that the PCRF was able to initiate the action as indicated by the AAR. For example, the PCRF was able to find a corresponding Gx session and send a Gx RAR to the PGW to boost APN-AMBR or set up a dedicated bearer. If the AAA indicates success (Result-Code = 2001), an Rx RAR may be sent after the PCRF completes the Gx (or Sd) interaction with indication of the results of the AAR request. If the AAA is sent with a Result-Code AVP indicating an error or failure (i.e. 30xx, 40xx, 50xx) then the PCRF was not able to initiate the action indicated by the AAR. If the AAR was the first request for this Rx session, then MOG removes the Rx session from its session database and does not send an STR. Re-Auth-Request (RAR) The RAR command, indicated by the Command-Code field set to 258 and the 'R' bit set in the Command Flags field, is sent by PCRF to MOG. This command is used to indicate the results of a previous AAR or to notify MOG of some event. 5
6 Re-Auth-Answer (RAA) <RA-Request> ::= < Diameter Header: 258, REQ, PXY > { Destination-Realm } { Destination-Host } { Auth-Application-Id } *{ Specific-Action } *[ Access-Network-Charging-Identifier ] [ Access-Network-Charging-Address ] *[ Flows ] *[ Subscription-Id ] [ Abort-Cause ] [ IP-CAN-Type ] [ RAT-Type ] [ Sponsored-Connectivity-Data ] [ 3GPP-User-Location-Info ] [ User-Location-Info-Time ] [ 3GPP-MS-TimeZone ] [ 3GPP-SGSN-MCC-MNC ] *[ Class ] *[ Route-Record ] Note 1 Origin Host AVP received in the message is stored and used to populate the Destination Host AVP in the next outgoing message for the Rx session. 2 For sponsored-data with a volume or time threshold, the volume or time usage is reported to MOG in the Sponsored-Connectivity-Data AVP when the threshold is breached. 3 Specific-Action AVP received in the message may contain CUSTOM_DPCC_STATUS_REPORT (200) in case MOG armed the event in AAR message. In this case, Dynamic-PCC-Parameter AVP will have Status-Report in Parameter-Name and Parameter-Value AVPs received from PCRF. For example: Specific-Action: CUSTOM_DPCC_STATUS_REPORT (200) Dynamic-PCC-Result: Result-Code: DIAMETER_SUCCESS (2001) Dynamic-PCC-Parameter: Parameter-Name: QoS-Class-Identifier Parameter-Value: 0 Dynamic-PCC-Parameter: Parameter-Name: Allocation-Retention-Priority Parameter-Value: 0 Dynamic-PCC-Parameter: Parameter-Name: APN-Aggregate-Max-Bitrate-DL Parameter-Value: 0 Dynamic-PCC-Parameter: Parameter-Name: APN-Aggregate-Max-Bitrate-UL Parameter-Value: 0 Parameter-Value 0 is success, 1 is failure and 2 is ignored Re-Auth-Answer (RAA) The RAA command, indicated by the Command-Code field set to 258 and the 'R' bit cleared in the Command Flags field, is sent from MOG to PCRF in response to an RAR. 6
7 Session-Termination-Request (STR) <RA-Answer> ::= < Diameter Header: 258, PXY > [ Result-Code ] [ Experimental-Result ] *[ Media-Component-Description ] [ Service-URN ] *[ Class ] [ Error-Message ] [ Error-Reporting-Host ] *[ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] *[ Failed-AVP ] Session-Termination-Request (STR) The STR command, indicated by the Command-Code field set to 275 and the 'R' bit set in the Command Flags field, is sent by MOG to the PCRF. <ST-Request> ::= < Diameter Header: 275, REQ, PXY > { Destination-Realm } { Auth-Application-Id } { Termination-Cause } [ Destination-Host ] *[ Required-Access-Info ] *[ Class ] *[ Route-Record ] Note Destination Host AVP is populated with the value received in the Origin Host AVP from PCRF in AAA or RAR. Sesson-Termination-Answer (STA) The STA command indicated by the Command-Code field set to 275 and the 'R' bit cleared in the Command Flags is sent by PCRF in response to an STR command. 7
8 Abort-Sesson-Request (ASR) <ST-Answer> ::= < Diameter Header: 275, PXY > [ Result-Code ] [ Error-Message ] [ Error-Reporting-Host ] *[ Failed-AVP ] [ Sponsored-Connectivity-Data ] [ 3GPP-User-Location-Info ] [ User-Location-Info-Time ] [ 3GPP-MS-TimeZone ] [ 3GPP-SGSN-MCC-MNC ] *[ Class ] *[ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] Note 1 For sponsored-data with a volume or time threshold, the volume or time usage is reported to the MOG in the Sponsored-Connectivity-Data AVP. Abort-Sesson-Request (ASR) The Abort-Session-Request (ASR) command, indicated by the Command-Code set to 274 and the 'R' bit set in the Command Flags field, is sent by PCRF to request MOG to terminate the Rx session identified by the Session-Id AVP. The MOG sends an Rx STR command to the PCRF in order to terminate the Rx session. Message Format <AS-Request> ::= < Diameter Header: 274, REQ, PXY > { Destination-Realm } { Destination-Host } { Auth-Application-Id } [ User-Name ] *[ Route-Record ] Abort-Sesson-Answer (ASA) The Abort-Session-Answer (ASR) command, indicated by the Command-Code set to 274 and the 'R' bit cleared in the Command Flags field, is sent by MOG in response to an ASR command. 8
9 Cisco Rx Protocol Specific Attributes Message Format <AS-Answer> ::= < Diameter Header: 274, PXY > { Result-Code } [ User-Name ] [ Error-Message ] [ Error-Reporting-Host ] * [ Failed-AVP ] * [ Redirect-Host ] [ Redirect-Host-Usage ] [ Redirect-Max-Cache-Time ] * [ Proxy-Info ] * [ AVP ] Cisco Rx Protocol Specific Attributes The Cisco enhanced Rx protocol uses the AVPs defined in the 3GPP Rx specification. Please refer to 3GPP TS for detailed description of such AVPs. Cisco Vendor Id (9) is used for the following Cisco AVPs AVP Name Vendor-ID AVP Code AVP Flag (Must) AVP Flag (Must Not) AVP Type Dynamic-PCC-Request-QoS V M,P Grouped Intention V M,P Enumerated Dynamic-PCC-Requested-QoS AVP The Dynamic-PCC-Requested-QoS AVP is a grouped AVP used to request modification of the default/dedicated bearer QoS. Dynamic-PCC-Requested-QoS ::= < AVP Header: > [ APN-Aggregate-Max-Bitrate- UL ] [ APN-Aggregate-Max-Bitrate-DL ] [ Default-EPS-Bearer-QoS ] [ Dedicated-EPS-Bearer-QoS ] [ Intention ] [ Dynamic-PCC-Parameter ] Default-EPS-Bearer-QoS ::= < AVP Header: 1049 > [ QoS-Class-Identifier ] [ Allocation-Retention-Priority ] Dedicated-Bearer-QoS ::= < AVP Header: > [ QoS-Class-Identifier ] [ Allocation-Retention-Priority ] Allocation-Retention-Priority ::= < AVP Header: 1034 > [ Priority-Level ] [ Pre-emption-Capability ] [ Pre-emption-Vulnerability ] Intention ::= < AVP Header: > Dynamic-PCC-Parameter::= < AVP Header: > [Parameter-Name] [Parameter-Value] 9
10 Dynamic-PCC-Result Note If both the Predefined-QoS-Name and other attributes are specified in the Dynamic-PCC-Requested-QoS grouped AVP, the requested QoS is the QoS as defined in the Predefined-QoS-Name with overrides of the values of the individual attributes. If Service-Info-Status is PRELIMINARY SERVICE INFORMATION (1), Default-EPS-Bearer-QoS AVP is present in Dynamic-PCC-Requested-QoS AVP of AAR message and if Service-Info-Status is FINAL SERVICE INFORMATION (0), Dedicated-Bearer-QoS AVP is present in Dynamic-PCC-Requested-QoS AVP of AAR message. Dynamic-PCC-Result The Dynamic-PCC-Result AVP is a grouped AVP used to see the result of the default/dedicated bearer QoS modification. Dynamic-PCC-Result ::= < AVP Header: > [ Result-Code ] [ Error-Message ] [ Default-EPS-Bearer-QoS] [ APN-Aggregate-Max-Bitrate-UL ] [ APN-Aggregate-Max-Bitrate-DL ] [ Dynamic-PCC-Parameter ] Default-EPS-Bearer-QoS ::= < AVP Header: 1049 > [ QoS-Class-Identifier ] [ Allocation-Retention-Priority ] Allocation-Retention-Priority ::= < AVP Header: 1034 > [ Priority-Level ] [ Pre-emption-Capability ] [ Pre-emption-Vulnerability ] Dynamic-PCC-Parameter::= < AVP Header: > [Parameter-Name] [Parameter-Value] 10
CDRs. CDR Overview. CPS MOG Guide, Release
CDR Overview, page Auth, page Request, page Callback, page AAR, page 7 AAA, page 0 STR, page 0 STA, page RAR, page RAA, page ASR, page ASA, page Token, page Onboard, page ACRS Request, page 7 ACRS Response,
More informationRx Services. Overview
Overview, page 1 VoLTE, page 2 Dynamic Rule Naming (Multiple Dedicated Bearer QoS), page 16 QoS Selection, page 17 Dynamic QoS, page 17 SRVCC, page 30 NPLI (Access Network), page 30 Dynamic PCC (MOG),
More informationRx Services. Overview. VoLTE
Overview, on page 1 VoLTE, on page 1 Dynamic Rule Naming (Multiple Dedicated Bearer QoS), on page 15 QoS Selection, on page 16 Dynamic QoS, on page 16 SRVCC, on page 28 NPLI (Access Network), on page 28
More information3GPP TS V ( )
TS 29.214 V8.18.0 (2013-12) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Rx reference point (Release
More informationSupported Message Formats
APPENDIXA Revised: July 27, 2012, Supported Diameter Messages The messages sent and received by the diameter infrastructure are as follows: Capability Exchange Request (CER) Sent upon new connection establishment
More information3GPP TS V6.8.0 ( )
TS 29.209 V6.8.0 (2011-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy control over Gq interface (Release 6) GLOBAL SYSTEM
More informationETSI TS V ( )
TS 129 214 V11.6.0 (2012-10) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 11.6.0 Release 11)
More informationETSI TS V ( )
TS 129 214 V12.5.0 (2014-10) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 12.5.0 Release 12)
More informationETSI TS V8.5.0 ( ) Technical Specification
TS 129 214 V8.5.0 (2009-06) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 8.5.0 Release 8)
More informationAll-IP Core Network Multimedia Domain
GPP X.S00-0-0 Version.0 Date: December 0 All-IP Core Network Multimedia Domain Service Based Bearer Control Ty Interface Stage COPYRIGHT NOTICE GPP and its Organizational Partners claim copyright in this
More informationETSI TS V1.4.0 ( ) Technical Specification
TS 183 017 V1.4.0 (2007-08) Technical Specification Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol
More informationETSI TS V ( )
TS 129 214 V14.6.0 (2018-01) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx reference point (3GPP TS 29.214 version 14.6.0 Release 14)
More informationETSI TS V1.1.1 ( )
TS 183 017 V1.1.1 (2006-03) Technical Specification Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol
More information3GPP TS V ( )
TS 29.219 V11.2.0 (2012-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control: Spending Limit Reporting over
More informationGTP-based S2b Interface Support on the P-GW and SAEGW
GTP-based S2b Interface Support on the P-GW and SAEGW This chapter describes the GTP-based S2b interface support feature on the standalone P-GW and the SAEGW. Feature, page 1 How the S2b Architecture Works,
More information3GPP TS V9.3.0 ( )
TS 29.212 V9.3.0 (2010-06) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and Charging Control over Gx reference point (Release
More information3GPP TS V9.2.0 ( )
TS 29.273 V9.2.0 (2010-03) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); EPS AAA interfaces (Release
More informationETSI TS V3.1.1 ( ) Technical Specification
TS 183 026 V3.1.1 (2010-03) Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control; Protocol for QoS reservation
More informationETSI TS V9.3.0 ( ) Technical Specification
TS 129 212 V9.3.0 (2010-06) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Gx reference point (3GPP TS 29.212 version 9.3.0 Release 9)
More informationETSI TS V (201
TS 129 214 V13.6.0 (201 16-08) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control over Rx referencee point (3GPP TS 29.214 version 13.6.0 Release
More informationCPS Central Administration Guide, Release
CPS Central Administration Guide, Release 11.0.0 First Published: Nov 02, 2016 Last Modified: Nov 02, 2016 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com
More informationETSI TS V ( ) Technical Specification
TS 129 213 V10.2.0 (2011-06) Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling
More information3GPP TS V ( )
Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Policy and charging control signalling flows and Quality of Service (QoS) parameter
More information- Page 1 of 12 -
PGW Functional Tester 11.0.0 Release Notes - Page 1 of 12 - Introduction The PGW Functional Tester is an automated test suite for testing the correctness of an implementation of LTE PDN Gateway (PGW) according
More information- Page 1 of 8 -
PGW Functional Tester 10.0.0 Release Notes - Page 1 of 8 - Introduction The PGW Functional Tester is an automated test suit for testing the correctness of an implementation of LTE PDN Gateway (PGW) according
More informationGx Interface Support. Rel. 7 Gx Interface
This chapter provides information on configuring Gx interface to support policy and charging control for subscribers. The IMS service provides application support for transport of voice, video, and data
More informationETSI TS V ( ) Technical Specification
TS 129 273 V10.3.0 (2011-06) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Evolved Packet System (EPS); 3GPP EPS AAA interfaces (3GPP TS 29.273 version 10.3.0 Release
More informationETSI TS V6.2.0 ( )
Technical Specification Universal Mobile Telecommunications System (UMTS); Charging rule provisioning over Gx interface () 1 Reference RTS/TSGC-0329210v620 Keywords UMTS 650 Route des Lucioles F-06921
More informationETSI TS V ( )
Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC) over Gx/Sd reference point () 1 Reference RTS/TSGC-0329212vb60 Keywords LTE,UMTS 650 Route
More informationETSI TS V ( )
Technical Specification Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Policy and charging control signalling flows and Quality of Service
More informationshow ims-authorization
This chapter describes the outputs of the command. policy-control statistics, page 1 policy-gate status full, page 12 policy-gate counters all, page 13 servers, page 14 service name, page 15 service name
More informationSupported AVPs in DCCA Messages
CHAPTER B The following sections of this appendix list the vendor-specific attribute value pairs (AVPs) supported by the Cisco GGSN in Diameter Credit Control Application (DCCA) Credit-Control-Request
More informationThe URI of the northbound API is specified in the following format:
URI, on page 1 Session Identifier, on page 1 Update QoS Sessions and Methods, on page 1 Update QoS Request Fields, on page 3 Intent Parameter for Default Bearer, on page 9 /network/define/qostype/version
More informationDIAMETER Support in BNG
DIAMETER provides a base protocol that can be extended in order to provide authentication, authorization, and accounting (AAA) services to new access technologies. This chapter provides information about
More informationThis chapter describes StarOS support for the NetLoc for WiFi EPC feature on the P-GW and SAE-GW.
This chapter describes StarOS support for the feature on the P-GW and SAE-GW. Feature Description, page 1 How It Works, page 1 Configuring the Feature, page 3 Monitoring and Troubleshooting the Feature,
More information5G Non Standalone. Feature Summary and Revision History
This chapter describes the (NSA) feature in the following sections: Feature Summary and Revision History, on page 1 Feature Description, on page 2 Feature Summary and Revision History Summary Data Applicable
More informationMOG Installation, Configuration, and Upgrade
MOG Installation, page 1 Plugin Configuration, page 2 vpas Configuration, page 5 CDR Filter Configuration, page 9 Service Configuration, page 10 Administrator Database Configuration, page 14 Geographic
More information5G Non Standalone for SAEGW
This chapter describes the 5G Non Standalone (NSA) feature in the following sections: Feature Summary and Revision History, on page 1 Feature Description, on page 2 How It Works, on page 3 Configuring
More informationETSI TS V ( )
TS 129 201 V14.0.0 (2017-05) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Representational State Transfer (REST) reference point between Application Function (AF) and
More informationETSI TS V ( )
TS 129 215 V12.9.0 (2018-07) TECHNICAL SPECIFICATION Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC)
More informationDiameter Configuration
, page 1 Diameter Stack Configuration, page 18 Diameter Agents, page 28 Diameter Clients, page 32 Diameter Defaults, page 58 Rule Retry Profiles, page 80 The section allows for the configuration of the
More informationPolicy Control Configuration Mode Commands
Policy Control Configuration Mode Commands Policy Control Configuration mode is used to configure the Diameter dictionary, origin host, host table entry and host selection algorithm for IMS Authorization
More information5G NSA(Non-Standalone Architecture)
This chapter describes the following topics: Feature Summary and Revision History, page 1 Feature Description, page 2 How It Works, page 2 Configuring DCNR, page 5 Monitoring and Troubleshooting, page
More informationETSI TS V ( )
TS 129 273 V12.5.0 (2014-10) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Evolved Packet System (EPS); 3GPP EPS AAA interfaces (3GPP TS 29.273 version 12.5.0 Release
More informationPCC (Policy and Charging Control) In Mobile Data. EFORT
PCC (Policy and Charging Control) In Mobile Data EFORT http://www.efort.com By implementing policy and charging control (PCC) procedures in their mobile data network, mobile service providers are able
More informationHSS and PCRF Based P-CSCF Restoration Support
This feature enables support for HSS-based and PCRF-based P-CSCF restoration that helps to minimize the time a UE is unreachable for terminating calls after a P-CSCF failure. Feature Description, page
More informationIxLoad EPC Diameter Testing
IxLoad EPC Diameter Testing IxLoad is a full-featured layer 4-7 test application that provides real-world traffic emulation testing of voice, video, and data networks and components. IxLoad simultaneously
More informationTable of Contents. Diameter Base Protocol -- Pocket Guide 1
Table of Contents Diameter Protocol Definition............................... 3 Diameter to RADIUS Comparison...........................3 Diameter Sessions vs. Connections......................... 3 Diameter
More information5G NSA for MME. Feature Summary and Revision History
Feature Summary and Revision History, on page 1 Feature Description, on page 2 How It Works, on page 5 Configuring, on page 10 Monitoring and Troubleshooting, on page 13 Feature Summary and Revision History
More informationThis chapter provides configuration information for the HRPD Serving Gateway (HSGW).
This chapter provides configuration information for the HRPD Serving Gateway (HSGW). Important Information about all commands in this chapter can be found in the Command Line Interface Reference. Because
More informationThis chapter provides configuration information for the HRPD Serving Gateway (HSGW).
This chapter provides configuration information for the HRPD Serving Gateway (HSGW). Important Information about all commands in this chapter can be found in the Command Line Interface Reference. Because
More informationP-GW Service Configuration Mode Commands
Service Configuration Mode Commands The (PDN Gateway) Service Configuration Mode is used to create and manage the relationship between specified services used for either GTP or PMIP network traffic. Exec
More informationQuality of Service, Policy and Charging
Quality of Service, Policy and Charging Contents 1. Policy and Charging Control! 2. Session Management Procedures! 3. Charging and Billing 1. Policy and Charging Control 1.1 Introduction! 1.2 Quality of
More informationTest-king QA
Test-king.600-212.70.QA Number: 600-212 Passing Score: 800 Time Limit: 120 min File Version: 6.1 http://www.gratisexam.com/ Provide the highest amount of valid questions with correct answers. This VCE
More informationRequest for Comments: D. Spence Consultant D. Mitton Circular Networks August Diameter Network Access Server Application
Network Working Group Request for Comments: 4005 Category: Standards Track P. Calhoun G. Zorn Cisco Systems Inc. D. Spence Consultant D. Mitton Circular Networks August 2005 Status of This Memo Diameter
More informationPolicy Control Configuration Mode Commands
Policy Control Configuration Mode Commands Policy Control Configuration mode is used to configure the Diameter dictionary, origin host, host table entry and host selection algorithm for IMS Authorization
More informationResource authorization in IMS with known multimedia service adaptation capabilities
Resource authorization in IMS with known multimedia service adaptation capabilities Tomislav Grgic, Vedran Huskic, and Maja Matijasevic University of Zagreb, Faculty of Electrical Engineering and Computing,
More informationAAA Server-provided 3GPP-User-Location-Information Support
AAA Server-provided 3GPP-User-Location-Information Support The following topics are discussed: Feature Description, page 1 How AAA Server-provided 3GPP-User-Location-Information Works, page 2 Configuring
More informationCategory: Standards Track Cisco Systems Inc. David Spence Interlink Networks Inc. David Mitton Circular Networks. Feb 2004
AAA Working Group Internet-Draft Category: Standards Track Pat R. Calhoun Airespace Inc. Glen Zorn Cisco Systems Inc. David Spence Interlink Networks Inc. David Mitton Circular Networks Feb 2004 Diameter
More informationP-GW Service Configuration Mode Commands
P-GW Service Configuration Mode Commands The P-GW (PDN Gateway) Service Configuration Mode is used to create and manage the relationship between specified services used for either GTP or PMIP network traffic.
More informationETSI ES V2.2.0 ( ) ETSI Standard
ES 283 034 V2.2.0 (2008-07) Standard Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER
More informationIP Services Gateway Overview
This chapter provides an overview of the IP Services Gateway (IPSG) product. This chapter covers the following topics: Introduction, page 1 How it Works, page 2 In-line Services, page 4 Enhanced Feature
More informationETSI TS V ( )
TS 129 337 V11.0.0 (2012-10) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Diameter based T4 Interface for communications with packet data networks and applications (
More information5G NSA for SGSN. Feature Summary and Revision History
Feature Summary and Revision History, on page 1 Feature Description, on page 2 How It Works, on page 3 Configuring 5G Non Standalone in SGSN, on page 6 Monitoring and Troubleshooting, on page 7 Feature
More informationAAA Server Group Configuration Mode Commands
AAA Server Group Configuration Mode Commands The AAA Server Group Configuration Mode is used to create and manage the Diameter/RADIUS server groups within the context or system. AAA server group facilitates
More informationETSI TS V (201
TS 129 217 V13.2.0 (201 16-01) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Policy and Charging Control (PCC); Congestion reporting over Np reference point (3GPP TS 29.217
More informationETSI TS V ( )
TS 129 273 V14.4.0 (2017-10) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Evolved Packet System (EPS); 3GPP EPS AAA interfaces (3GPP TS 29.273 version 14.4.0 Release
More information3GPP TS V ( )
TS 29.272 V8.14.0 (2014-06) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity
More information4G Network Emulator. The Valid8 team will go above and beyond to get the job done. Jordan C., Network Integrity Lab & Certification Services, BoA
4G Network Emulator The Valid8 4G Network Emulator provides an all-in-one, cost-effective and ultra-portable 4G network for demonstration, testing and training purposes. There are options available to
More informationRequest for Comments: 4072 Category: Standards Track Lucent Technologies G. Zorn Cisco Systems August 2005
Network Working Group Request for Comments: 4072 Category: Standards Track P. Eronen, Ed. Nokia T. Hiller Lucent Technologies G. Zorn Cisco Systems August 2005 Diameter Extensible Authentication Protocol
More informationNon-IP Data Over SCEF
This chapter describes the transfer of Non-IP data over SCEF using Cellular Internet of Things (CIoT) technology. This feature is discussed in the following sections: Feature Summary and Revision History,
More informationETSI TS V6.1.0 ( )
TS 129 234 V6.1.0 (2004-12) Technical Specification Universal Mobile Telecommunications System (UMTS); 3GPP system to Wireless Local Area Network (WLAN) interworking; Stage 3 (3GPP TS 29.234 version 6.1.0
More informationDIAMETER Attributes. BNG DIAMETER Gx Application AVPs
DIAETER Attributes BNG Supports DIAETER Gx interface for Policy and Charging Provisioning with the PCRF, and DIAETER Gy interface for Online Charging Service with OCS. This Appendix lists the applicable
More informationMessage Priority Indication over GTPC
This chapter describes the following topics: Feature Summary and Revision History, page 1 Feature Description, page 2 How It Works, page 4 Configuring the Message Priority over GTP Feature, page 6 Monitoring
More informationE. The enodeb performs the compression and encryption of the user data stream.
Volume: 140 Questions Question No: 1 Which of the following statements is FALSE regarding the enodeb? A. The enodebs maybe interconnect TEID with each other via anx2 interface. B. The enodeb is an element
More informationETSI TS V ( )
TS 129 336 V11.1.0 (2013-01) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks
More informationETSI TS V ( )
TS 129 344 V12.1.0 (2015-01) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Proximity-services (ProSe) function to Home Subscriber Server (HSS) aspects; Stage 3 (3GPP TS
More informationCPS MOG API Reference, Release
CPS MOG API Reference, Release 13.1.0 First Published: 2017-08-18 Last Modified: 2017-08-18 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com
More informationCPS vdra Configuration Guide, Release (2)
First Published: 2017-08-18 Last Modified: 2018-04-02 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationREFERENCE ARCHITECTURE FOR END-TO-END QOS IN HETEROGENEOUS WIRELESS NETWORK ENVIRONMENTS
REFERENCE ARCHITECTURE FOR END-TO-END QOS IN HETEROGENEOUS WIRELESS NETWORK ENVIRONMENTS Sandra Frei 1, 2, Woldemar Fuhrmann 3, Andreas Rinkel 2 and Bogdan Ghita 1 1 Centre for Information Security and
More informationITU-T Q Recommendation ITU-T Q.3229 (08/2016) I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n
I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T Q.3229 TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (08/2016) SERIES Q: SWITCHING AND SIGNALLING Signalling requirements and
More informationCPS vdra Configuration Guide, Release
First Published: 2017-06-23 Last Modified: 2017-06-23 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387)
More informationRouting Behind the Mobile Station on an APN
Feature Description How It Works The routing behind the Mobile Station(MS) feature enables the routing of packets to IPv4 addresses that do not belong to the PDN Session (the MS), but exist behind it.
More informationDomains. Overview. Figure 1: APN Profile Rules. CPS Mobile Configuration Guide, Release
Overview, page 1 Strategies for Defining, page 2 Defining a Domain, page 2 Creating a Custom Reference Data (CRD) table for APN mapping, page 19 Validation Steps, page 23 Overview The Access Point Network
More information3GPP TS V9.2.0 ( )
TS 29.329 V9.2.0 (2010-06) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Sh Interface based on the Diameter protocol; Protocol details
More informationDiameter NASREQ Application. Status of this Memo. This document is an Internet-Draft and is subject to all provisions of Section 10 of RFC2026.
AAA Working Group Pat R. Calhoun Internet-Draft Black Storm Networks Category: Standards Track William Bulley Merit Network, Inc. Allan C. Rubens Tut Systems, Inc.
More informationOperator Policy. What Operator Policy Can Do. A Look at Operator Policy on an SGSN
The proprietary concept of an operator policy, originally architected for the exclusive use of an SGSN, is non-standard and currently unique to the ASR 5x00. This optional feature empowers the carrier
More informationGGSN CDR Field Descriptions
This chapter describes the CDR fields supported by the system for use in GGSN-CDRs (G-CDRs) and enhanced G-CDRs (eg-cdrs). The following information is provided for each field: Description: The field's
More informationETSI TS V ( )
TS 129 336 V11.0.0 (2012-10) Technical Specification Universal Mobile Telecommunications System (UMTS); LTE; Home Subscriber Server (HSS) diameter interfaces for interworking with packet data networks
More informationQuality-of-Service Option for Proxy Mobile IPv6
Internet Engineering Task Force (IETF) Request for Comments: 7222 Category: Standards Track ISSN: 2070-1721 M. Liebsch NEC P. Seite Orange H. Yokota KDDI Lab J. Korhonen Broadcom Communications S. Gundavelli
More informationDedicated Core Networks on MME
This chapter describes the Dedicated Core Networks feature in the following sections: Feature Summary and Revision History, on page 1 Feature Description, on page 2 How It Works, on page 4 Configuring
More information3GPP TS V9.1.0 ( )
TS 29.272 V9.1.0 (2009-12) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity
More informationCapturing and Reporting Subscriber Attributes
CHAPTER 6 Published: September 26, 2012 Introduction Vendor Specific Attributes (VSA) are RADIUS or Diameter attributes that are sent mostly in mobile environments. They can be captured from the traffic
More informationHSS-based P-CSCF Restoration
The home subscriber server-based (HSS) Proxy Call Session Control Function (P-CSCF) Restoration is an optional mechanism during a P-CSCF failure. It applies only when the UE is using 3GPP access technologies.
More informationDedicated Core Networks on MME
This chapter describes the Dedicated Core Networks feature in the following sections: Feature Summary and Revision History, page 1 Feature Description, page 2 How It Works, page 5 Configuring DECOR on
More informationS4 interface Support For Non-EPC Devices
This chapter describes the S4 interface support for Non-EPC capable devices. Feature Description, page 1 How it Works, page 2 Configuring S4 Interface Support for Non-EPC Capable Devices, page 4 Monitoring
More information3GPP TS V ( )
TS 29.368 V11.0.0 (2012-09) Technical Specification 3rd Generation Partnership Project; Technical Specification Group Core Network and Terminals; Tsp interface protocol between the MTC Interworking Function
More informationETSI TS V2.1.1 ( ) Technical Specification
TS 183 059-1 V2.1.1 (2009-08) Technical Specification Telecommunications and Internet converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); a2 interface
More informationETSI TS V ( )
TS 129 337 V12.3.0 (2014-10) TECHNICAL SPECIFICATION Universal Mobile Telecommunications System (UMTS); LTE; Diameter-based T4 Interface for communications with packet data networks and applications (3GPP
More informationSubscriber Data Management
Subscriber Data Management LTE S6a/S6d Interface Description 910-6720-001 Revision A June 2013 Copyright 2013 Tekelec All Rights Reserved Notice Information in this documentation is subject to change without
More information