hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.3 Traffic policy modification request | In order to modify traffic policies previously activated on transport resources described by Transport Resource Classifier(s), the RCEF sends a CC-Request Command with the CC-Request-Type AVP set to the value "UPDATE_REQUEST". During the modification procedure, a traffic policy previously activated for a set of Transport Resource Classifier(s) may be modified or deactivated. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 5.3.2.4 Traffic Policy Deactivation Request | In order to deactivate all traffic policies previously activated for given Transport Resource Classifier(s), the RCEF sends a CC-Request Command to the A-RACF, with the CC-Request-Type AVP set to "TERMINATION_REQUEST". On receipt of the CC-Answer, the RCEF will: • deactivate the traffic policy referenced by the Policy-Rule-Name AVP - if the Policy-Rule-Name AVP is included in the Policy-Rule-Remove AVP of the CC-Answer; • deactivate the traffic policies referenced by the Policy-Rule-Base-Name AVP - if the Policy-Rule-Base-Name AVP is included in the Policy-Rule-Remove AVP of the CC-Answer. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6 Use of the DIAMETER base protocol | The DIAMETER Base Protocol defined by RFC 3588 [3] shall apply, with the clarifications listed in the present document. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.1 Securing DIAMETER messages | For secure transport of DIAMETER messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found in RFC 3554 [5]. The RCEF may verify the identity of the A-RACF issuing during the Capabilities Exchange Request procedure. The RCEF may verify if the A-RACF that issues a PIR command is allowed to do so, based on: • The Identity of the A-RACF. • The Type of PIR Command. • The content of the PIR Command. • Any combination of the above. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the Re Reference Point. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 28 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.3 Use of sessions | DIAMETER sessions are implicitly terminated. As such, the Abort-Session-Request (ASR) and Session-Termination-Request (STR) defined in [3] are not used. NOTE: The A-RACF and RCEF obviously maintain state, but this state is not associated with the Session-Id. The A-RACF shall include in its Requests the Auth-Session-State AVPs set to the value NO_STATE_MAINTAINED (1) [3]. The Session-Id AVP is not meaningful on the Re interface. This means that the RCEF shall not maintain associations between the activated Policy Rules and the Session-Id AVP. For this reason, the RAR/RAA and STR/STA commands defined in the DIAMETER base protocol are not used in the context of the present document. Anyway, the Session-Id AVP shall be included in all DIAMETER commands that conform to the present document. The value of the Session-Id shall be chosen by the A-RACF. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.4 Transport protocol | DIAMETER messages over the Re interface shall make use of SCTP RFC 2960 [2] and shall utilize the new SCTP checksum method specified in RFC 3309 [4]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.5 Routing considerations | This clause specifies the use of the Destination-Realm and Destination-Host Routing AVPs. Both the Destination-Realm and Destination-Host AVPs shall be present in the Request from the A-RACF to the RCEF. The A-RACF may obtain the Destination-Host AVPs to use in Requests towards the RCEF from NASS user location information retrieved from the CLF or from configuration data. Requests initiated by the RCEF towards an A-RACF may include both Destination-Host and Destination-Realm AVPs. The RCEF may obtain the Destination-Host AVPs to use in Requests towards the A-RACF from Requests received earlier from the A-RACF, or from configuration data. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 6.6 Advertising Application support | The Capabilities-Exchange-Request (CER) and Capabilities-Exchange-Answer (CEA) are defined in RFC 3588 [3]. The A-RACF and RCEF shall advertise support of the Re specific application by including the following AVPs: • Vendor-Specific-Application-Id grouped AVPs containing the following AVPs: - Auth-Application-Id AVPs with the value (16777253); - Vendor-Id AVPs with the value AVPs (13019). • Supported-Vendor-Id AVP with the value ETSI (13019) to indicate support of ETSI AVPs. • Supported-Vendor-Id AVP with the value 3GPP (10415) to indicate support of 3GPP AVPs. • Supported-Vendor-Id AVP with the value ITU-T (11502) to indicate support of ITU-T AVPs. NOTE: The Vendor-Id AVPs included in CER and CEA commands that is not included in the Vendor-Specific-Application-Id AVPs as described above indicates the manufacturer of the DIAMETER node as per RFC 3588 [3]. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 29 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7 DIAMETER application | The DIAMETER Base Protocol as specified in RFC 3588 [3] is used to support information transfer on the Re interface. RFC 3588 [3] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 5. Unless otherwise specified, the procedures (including error handling and unrecognized information handling) are unmodified. The present document uses the DIAMETER application number (16777253). |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1 Commands | The following commands are used: Table 1: Command-Code values Command-Name Abbreviation Code Defined In See clause Policy-Install-Request PIR 315 [6], [13] 7.1.1 Policy-Install-Answer PIA 315 [6], [13] 7.1.2 Credit-Control-Request CCR 272 [8] 7.1.3 Credit-Control-Answer CCA 272 [8] 7.1.4 AVPs defined in [6] and not used in the present document are not represented in the below clauses. If received, these AVPs shall be ignored by the A-RACF and the RCEF. AVPs added in the ABNF of the commands are represented in bold. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.1 Policy-Install-Request (PIR) command | The Policy-Install-Request (PIR) command, indicated by the Command-Code field set to 315 and the "R" bit set in the Command Flags field, is sent by the A-RACF to the RCEF in order to install policies in the RCEF. This command is defined in [6] and used with additional AVPs defined in the present document. Message Format: < Policy-Install-Request > ::= < Diameter Header: 315, REQ, PXY> < Session-Id > { Auth-Application-Id } { Origin-Host } { Origin-Realm } { Destination-Realm } { Destination-Host } { PI-Request-Type } { PI-Request-Number } [ Origin-State-Id ] [ Auth-Session-State ] * [ Event-Trigger ] * [ Policy-Rule-Remove ] * [ Policy-Rule-Install ] [ User-Name ] [ Logical-Access-Id ] [ Framed-IP-Address ] [ Address-Realm ] [ Called-Station-ID ] [ ToS-Traffic-Class ] * [ Proxy-Info ] * [ Route-Record ] * [ AVP ] ETSI ETSI TS 183 060 V2.1.1 (2009-04) 30 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.2 Policy-Install-Answer (PIA) command | The Policy-Install-Answer (PIA) command, indicated by the Command-Code field set to 315 and the "R" bit cleared in the Command Flags field, is sent by a server in response to Policy-Install-Request command. This command is defined in [6] and used with additional AVPs defined in the present document. Message Format: <PI-Answer> ::= < Diameter Header: 315, PXY> < Session-Id > { Origin-Host } { Origin-Realm } { PI-Request-Type } { PI-Request-Number } [ Result-Code ] * [ Policy-Rule-Report ] [ Experimental-Result ] [ Origin-State-Id ] [ Error-Message ] [ Error-Reporting-Host ] * [ Policy-Rule-Name ] * [ Policy-Rule-Base-Name ] * [ Policy-Rule-Definition ] * [ Failed-AVP ] * [ Proxy-Info ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.3 CC-Request (CCR) command | The CCR command, indicated by the Command-Code field set to 272 and the 'R' bit set in the Command Flags field, is sent by the RCEF to the A-RACF in order to report the occurrence of particular event or to request activation, modification, or deactivation of traffic policies. If the Traffic-Flow AVP is used at the command level in the CCR command, the Flow-Description AVP, the Flow-Status AVP and the QoS-Information AVP shall not be used in the CCR command. Message Format: <CC-Request> ::= < Diameter Header: 272, REQ, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Destination-Realm } { Auth-Application-Id } { Service-Context-Id } { CC-Request-Type } { CC-Request-Number } [ Destination-Host ] [ User-Name ] [ Origin-State-Id ] [ Event-Timestamp ] [ Auth-Session-State ] [ Termination-Cause ] [ Called-Station-ID ] [ Logical-Access-Id ] [ Physical-Access-ID ] * [ Traffic-Flow ] * [ Flow-Description ] [ Flow-Status ] [ QoS-Information ] [ Framed-IP-Address ] [ Address-Realm ] * [ Policy-Rule-Report] ETSI ETSI TS 183 060 V2.1.1 (2009-04) 31 * [ Policy-Update-Request] * [ Event-Trigger] * [ Proxy-Info ] * [ Route-Record ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.1.4 CC-Answer (CCA) Command | The Credit-Control-Answer message (CCA) is indicated by the command-code field being set to 272 and the 'R' bit being cleared in the Command Flags field. It is sent by the A-RACF to the RCEF in answer to the CCR.. Message Format: <CC-Answer> ::= < Diameter Header: 272, PXY > < Session-Id > { Origin-Host } { Origin-Realm } { Auth-Application-Id } { Result-Code } { CC-Request-Type } { CC-Request-Number } [ User-Name ] [ Framed-IP-Address ] [ Address-Realm ] [ Called-Station-Id ] [ Logical-Access-Id ] [ ToS-Traffic-Class ] [ Origin-State-Id ] [ Event-Timestamp ] [ Auth-Session-State ] * [ Event-Trigger ] * [ Policy-Rule-Remove ] * [ Policy-Rule-Install ] * [ Failed-AVP ] * [ Proxy-Info ] * [ Route-Record ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2 Experimental-Result-Code AVP values | Clause 7.2 defines new Experimental-Result-Code values that shall be supported by all DIAMETER implementations that conform to the present document. When one of the Experimental Result Code defined in clause 7.2 is included in a response, it shall be inside an Experimental-Result AVP and the Result-Code AVP shall be absent. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.1 Success | Experimental Result Codes that fall within the Success category are used to inform a peer that a request has been successfully completed. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 32 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.2 Transient failures | Experimental Result Codes that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. The following values of the Experimental-Result-Code AVP defined in ES 283 026 [12] are reused: • COMMIT_FAILURE (4043). - The RCEF indicates that the Policy could not be committed. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.2.3 Permanent failures | Experimental Result Codes that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. The present document defines the following new values of the Experimental-Result-Code AVP: • UNKNOWN_POLICY_RULE (5061) - The RCEF indicates that the specified Policy-Rule-Name AVP in unknown. • UNKNOWN_POLICY_RULE_BASE_NAME (5062) - The RCEF indicates that the specified Policy-Rule-Base-Name AVP in unknown. • UNKNOWN_POLICY_RULE_FOR_TRANSPORT_RESOURCE (5063) - The RCEF indicates a mismatch between the specified combination of Policy-Rule-Name AVP and Transport Resource Classifier. • UNKNOWN_POLICY_RULE_BASE_NAME_FOR_TRANSPORT_RESOURCE (5064) - The RCEF indicates a mismatch between the specified combination of Policy-Rule-Base-Name AVP and Transport Resource Classifier. • UNKNOWN_TRANSPORT RESOURCE (5065) - The RCEF indicates that the specified Transport Resource Classifier(s) do not match with each others, or cannot be mapped to any Transport Resource. • POLICY_ACTIVATION_FAILURE (5066) - The RCEF indicates that a given Policy Rule could not be activated. • POLICY_MODIFICATION_FAILURE (5067) - The RCEF indicates that a given Policy Rule could not be updated. • AUTHORIZATION_REJECTED_FOR_TRANSPORT_RESOURCE (5068) - The RCEF denies the request because the requested operation is not allowed for the specified Transport Resource Classifier. • AUTHORIZATION_REJECTED_FOR_POLICY_RULE_NAME (5069) - The RCEF denies the request because the requested operation is not allowed for the specified Policy Rule. • AUTHORIZATION_REJECTED_FOR_POLICY_RULE_BASE_NAME (5070) - The RCEF denies the request because the requested operation is not allowed for the specified Policy Rule. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 33 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3 AVPs | Clause 7.3 summarizes the AVP used in the present document, beyond those defined in the DIAMETER Base Protocol. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1 AVPs Defined in the Present Document | Table 2 describes the new DIAMETER AVPs used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id field in the header for these AVPs shall be set to ETSI (13019). Table 2: New DIAMETER AVPs AVP flag rules Attribute name AVP Code Clause defined Value type Must May Should not Must not May encrypt Policy-Rule-Install 550 7.3.1.1 Grouped M,V P Y Policy-Rule-Remove 551 7.3.1.2 Grouped M,V P Y Policy-Rule-Definition 552 7.3.1.3 Grouped M,V P Y Policy-Rule-Base-Name 553 7.3.1.4 UTF8String M,V P Y Policy-Rule-Name 554 7.3.1.5 OctetString M,V P Y Policy-Rule-Report 555 7.3.1.6 Grouped M,V P Y Policy-Rule-Status 556 7.3.1.7 Enumerated M,V P Y Traffic-Flow 557 7.3.1.8 Grouped M,V P Y Policy-Update-Request 558 7.3.1.9 Grouped M,V P Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.1 Policy-Rule-Install AVP | The Policy-Rule-Install AVP (AVP code 550) is of type Grouped, and it is used to activate, install or modify Policy Rule as instructed from the A-RACF to the RCEF. AVP Format: Policy-Rule-Install ::= < AVP Header: 550 > * [ Policy-Rule-Definition ] * [ Policy-Rule-Name ] * [ Policy-Rule-Base-Name ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.2 Policy-Rule-Remove AVP | The Policy-Rule-Remove AVP (AVP code 551) is of type Grouped, and it is used to deactivate or remove Policy Rules. AVP Format: Policy-Rule-Remove ::= < AVP Header: 551 > * [ Policy-Rule-Name ] * [ Policy-Rule-Base-Name ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.3 Policy-Rule-Definition AVP | The Policy-Rule-Definition AVP (AVP code 552) is of type Grouped, and it describes a Policy Rule. The Policy-Rule-Name AVP uniquely identifies the Policy Rule and it is used to reference to a Policy Rule in communication between the RCEF and the A-RACF. The Flow-Description AVPs determines the traffic flows that belong to the service flow. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 34 If optional AVP(s) within a Policy-Rule-Definition AVP are omitted, but corresponding information has been provided in previous Re messages, the previous information remains valid. If Flow-Description AVP(s) are supplied, they replace all previous Flow-Description AVP(s). If Flows AVP(s) are supplied, they replace all previous Flows AVP(s). AVP Format: Policy-Rule-Definition ::= < AVP Header: 552 > { Policy-Rule-Name } [ Service-Identifier ] [ Rating-Group ] [ User-Name ] [ Logical-Access-Id ] [ Framed-IP-Address ] [ Address-Realm ] [ Called-Station-ID ] [ Physical-Access-Id ] * [ Flow-Description ] [ Flow-Status ] [ QoS-Information ] [ Reporting-Level ] [ Precedence ] * [ Flows ] * [ AVP ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.4 Policy-Rule-Base-Name AVP | The Policy-Rule-Base-Name AVP (AVP code 553) is of type UTF8String, and it indicates the name of a pre-defined group of Policy Rules residing at the RCEF. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.5 Policy-Rule-Name AVP | The Policy-Rule-Name AVP (AVP code 554) is of type OctetString, and it defines a name for Policy Rule. For Policy Rules provided by the A-RACF it uniquely identifies a Policy Rule. For Policy Rules pre-defined at the RCEF it uniquely identifies a Policy Rule within the RCEF. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.6 Policy-Rule-Report AVP | The Policy-Rule-Report AVP (AVP code 555) is of types Grouped, and it is used to report the status of a particular Policy Rule. Policy-Rule-Name AVP is a reference for a specific Policy. Policy-Rule-Base-Name AVP is a reference to a group of Policies. The Policy-Rule-Status AVP indicates the action being performed on the Policy rule. The Rule-Failure-Code indicates the reason that the Policy decisions cannot be successfully installed/activated or enforced. AVP Format: Policy-Rule-Report ::= < AVP Header: 555 > * [Policy-Rule-Name] * [Policy-Rule-Base-Name] [Policy-Rule-Status] [Rule-Failure-Code] * [AVP] ETSI ETSI TS 183 060 V2.1.1 (2009-04) 35 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.7 Policy-Rule-Status AVP | The Policy-Rule-Status AVP (AVP code 556) is of type Enumerated, and describes the status of one or a group of Policy Rules. The following values are defined: ACTIVE (0) This value is used to indicate that the Policy rule(s) are successfully installed (for those provisioned from A-RACF) or activated (for those pre-provisioned in RCEF). INACTIVE (1) This value is used to indicate that the Policy rule(s) are removed (for those provisioned from A-RACF) or inactive (for those pre-provisioned in RCEF). TEMPORARY INACTIVE (2) This value is used to indicate that, for some reason (e.g. loss of bearer), already installed or activated Policy rules are temporary disabled. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.8 Traffic-Flow AVP | The Traffic-Flow AVP (AVP code 557) is of type Grouped, and it describes the detailed information for a group of flows. AVP Format: Traffic-Flow ::= < AVP Header: 557 > * [ Flow-Description ] [ Flow-Status ] [ QoS-Information ] [ User-Name ] [ Called-Station-ID ] [Framed-IP-Address] [Framed-IPv6-Prefix] [Address-Realm] [ Logical-Access-Id ] [ Physical-Access-ID ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.1.9 Policy-Update-Request AVP | The Policy-Update-Request AVP (AVP code 558) is of types Grouped, and it is used to request the update the QoS of a particular Policy Rule. Policy-Rule-Name AVP is a reference for a specific Policy. Policy-Rule-Base-Name AVP is a reference to a group of Policies. AVP Format: Policy-Update-Request ::= < AVP Header: 558 > * [Policy-Rule-Name] * [Policy-Rule-Base-Name] [Policy-Rule-Status] [ QoS-Information ] * [AVP] ETSI ETSI TS 183 060 V2.1.1 (2009-04) 36 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2 AVPs imported from ITU-T NGN-GSI/DOC - 127 | The following table describes the DIAMETER AVPs imported from ITU-T NGN-GSI/DOC - 127 [6] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in [6] but noy listed in table 3 should not be sent by DIAMETER nodes conforming to the present document and shall be ignored by receiving entities. The Vendor-Id field in the header for these AVPs shall be set to ITU-T (11502). Table 3: DIAMETER AVPs imported from ITU-T NGN-GSI/DOC - 127 AVP flag rules Attribute name AVP Code Clause defined Value type Must May Should not Must not May encrypt Traffic-Descriptor-UL 1012 7.3.2.1 Grouped V P Y Traffic-Descriptor-DL 1013 7.3.2.2 Grouped V P Y Maximum-Burst-Size 1014 7.3.2.3 Unsigned32 V P Y Committed-Data-Rate 1015 7.3.2.4 Unsigned32 V P Y Committed-Burst-Size 1016 7.3.2.5 Unsigned32 V P Y Excess-Burst-Size 1017 7.3.2.6 Unsigned32 V P Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.1 Traffic-Descriptor-UL AVP (ITU-T NGN-GSI/DOC - 127) | The Traffic-Descriptor-UL AVP (AVP code 1012) is of type Grouped, and indicates traffic characteristics complementary to the maximum bandwidth. It is used to control the bandwidth of traffic flows in the uplink direction. AVP Format: Traffic-Descriptor-UL ::= < AVP Header: 1012 > [ Maximum-Burst-Size ] [ Committed-Data-Rate ] [ Committed-Burst-Size ] [ Excess-Burst-Size ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.2 Traffic-Descriptor-DL AVP (ITU-T NGN-GSI/DOC - 127) | The Traffic-Descriptor-DL AVP (AVP code 1013) is of type Grouped, and indicates traffic characteristics complementary to the maximum bandwidth. It is used to control the bandwidth of traffic flows in the downlink direction. AVP Format: Traffic-Descriptor-DL::= < AVP Header: 1013 > [ Maximum-Burst-Size ] [ Committed-Data-Rate ] [ Committed-Burst-Size ] [ Excess-Burst-Size ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.3 Maximum-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Maximum-Burst-Size AVP (AVP code 1014) is of type Unsigned32, and indicates the peak burst size in Octets. It is used to provision the peak burst size for the traffic policing. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.4 Committed-Data-Rate AVP (ITU-T NGN-GSI/DOC - 127) | The Committed-Data-Rate AVP (AVP code 1015) is of type Unsigned32, and indicates the average bandwidth in Octets per second. It is used to provision the average bandwidth for the traffic policing. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 37 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.5 Committed-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Committed-Burst Size AVP (AVP code 1016) is of type Unsigned32, and indicates the committed burst size in Octets. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.6 Excess-Burst-Size AVP (ITU-T NGN-GSI/DOC - 127) | The Excess-Burst Size AVP (AVP code 1017) is of type Unsigned32, and indicates the excess burst size in Octets. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.7 PI-Request-Type AVP (ITU-T NGN-GSI/DOC - 127) | The PI-Request-Type AVP (AVP Code 1010) is of type Enumerated and contains the reason for sending the Policy-Install-Request command. It shall be present in all Policy-Install-Request messages. The following values defined in [6] are reused: INITIAL_REQUEST 1 An Initial Request is used to activate Policy Rule(s) on a particular Transport Resource. UPDATE_REQUEST 2 An Update Request is used to update Policy Rules previously activated on a given Transport Resource, to add new Policy on a given Transport Resource, or to remove one or several Policy Rule(s) activated on a given Transport Resource. TERMINATION_REQUEST 3 Termination Request is used to deactivate and remove all Policy Rules previously activated on a given Transport Resource. The following values are added compared to [6]: QUERY_REQUEST 4 Query Request is used to query the RCEF about the supported or activated Policy Rules. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.2.8 PI-Request-Number AVP (ITU-T NGN-GSI/DOC - 127) | The PI-Request-Number AVP (AVP Code 1011) is of type Unsigned32 and identifies this request within one session. As Session-Id AVPs are globally unique, the combination of Session-Id and PI-Request-Number AVPs is also globally unique and can be used in matching policy-install messages with confirmations. An easy way to produce unique numbers is to set the value to 0 for a policy-install request of type INITIAL_REQUEST and EVENT_REQUEST and to set the value to 1 for the first UPDATE_REQUEST, to 2 for the second, and so on until the value for TERMINATION_REQUEST is the value of the last UPDATE_REQUEST + 1. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3 AVPs Imported From TS 129 212 | Table 4 describes the DIAMETER AVPs imported from [7] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in TS 129 212 [7] but no listed in the following table should not be sent by DIAMETER nodes conforming to the present document and shall be ignored by receiving entities. The Vendor-Id field in the header for these AVPs shall be set to 3GPP (10415). ETSI ETSI TS 183 060 V2.1.1 (2009-04) 38 Table 4: DIAMETER AVPs imported from TS 129 212 AVP flag rules Attribute name AVP Code Clause defined Value type Mu st May Should not Must not May encrypt QoS-Information 1016 7.3.3.1 Grouped M,V P Y ToS-Traffic-Class 1019 7.3.3.2 OctetString M,V P Y Event-Trigger 1006 7.3.3.3 Enumerated M,V P Y Precedence 1010 7.3.3.4 Unsigned32 M,V P Y Reporting-Level 1011 7.3.3.5 Enumerated M,V P Y Rule-Failure-Code 1031 7.3.3.6 Enumerated M,V P Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.1 QoS-Information AVP (TS 129 212) | The QoS-Information AVP (AVP code 1016) is of type Grouped, and it defines the maximum QoS that is authorized for the corresponding traffic flow(s): AVP Format: QoS-Information ::= < AVP Header: 1016> [ Max-Requested-Bandwidth-UL ] [ Max-Requested-Bandwidth-DL ] [ Traffic-Descriptor-UL ] [ Traffic-Descriptor-DL ] [ ToS-Traffic-Class ] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.2 ToS-Traffic-Class AVP (TS 129 212) | The ToS-Traffic-Class AVP (AVP code 1014) is of type OctetString, and it contains an identifier of the Traffic Class. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.3 Event-Trigger AVP (TS 129 212) | The Event-Trigger AVP (AVP code 1006) is of type Enumerated. When sent from the A-RACF to the RCEF the Event-Trigger AVP indicates that an event that shall trigger a CC-Request from the RCEF to the A-RACF. When sent from the RCEF to the A-RACF the Event-Trigger AVP indicates that the corresponding event has occurred on the RCEF. The following values defined in TS 129 212 [7] are reused: • LOSS_OF_BEARER (5) - This value shall be used in PIR commands by the A-RACF to indicate that upon loss of bearer, the RCEF shall inform the A-RACF. - When used in a CCR command, this value indicates that the RCEF generated the request because the bearer associated with the Policy indicated by the corresponding Policy-Rule-Report AVP was lost. The Policy-Rule-Status AVP within the Policy-Rule-Report AVP shall have the value INACTIVE or TEMPORARY INACTIVE. - The RCEF may provide the Logical-Access-Id AVP, Framed-IP-Address AVP, Framed-IP-Address and Address-Realm AVPs, User-Name AVP or Called-Station-Id AVP to indicate the resource that has been lost. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 39 • RECOVERY_OF_BEARER (6) - This value shall be used in PIR commands by the A-RACF to indicate that upon recovery of bearer, the RCEF shall inform A-RACF. - When used in a CCR command, this value indicates that the RCEF generated the request because the bearer associated with the Policy indicated by the corresponding Policy-Rule-Report AVP was recovered. The Policy-Rule-Status AVP within the Policy-Rule-Report AVP shall have the value ACTIVE. - The RCEF may provide the Logical-Access-Id AVP, Framed-IP-Address AVP, Framed-IP-Address and Address-Realm AVPs, User-Name AVP or Called-Station-Id AVP to indicate the resource that has been recovered. • RESOURCES_MODIFICATION (101) - When used in a CCR command, this value indicates that the RCEF generated the request because an event occurred that may affect resources requirements and require re-evaluation of these requirement by the RACS. The affected policy rules are provided in the Policy-Rule-Report AVP. Other values defined in TS 129 212 [7] are not used. The following values are added: • ANY_EVENT (11) - This value shall be used in PIR commands by the A-RACF to indicate that the RCEF shall inform the A- RACF of the occurrence of any event. • NO_EVENT (12) - This value shall be used in PIR commands by the A-RACF to indicate that the RCEF shall not inform the A-RACF anymore of the occurrence of any event. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.4 Precedence AVP (TS 129 212) | The Precedence AVP (AVP code 1010) is of type Unsigned32, and it defines the precedence of a Policy Rule in case of overlapping Policy Rules. A Policy Rule with the Precedence AVP with lower value shall take precedence over a Policy Rule with the Precedence AVP with higher value. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.3.5 Reporting-Level AVP (TS 129 212) | The Reporting-Level AVP (AVP code 1011) is of type Enumerated, and it defines on what level the RCEF reports the usage for the related Policy Rule. The following values are defined: • SERVICE_IDENTIFIER_LEVEL (0) - This value shall be used to indicate that the usage shall be reported on service id and rating group combination level. • RATING_GROUP_LEVEL (1) - This value shall be used to indicate that the usage shall be reported on rating group level. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 40 7.3.3.6 Rule-Failure-Code AVP The Rule-Failure-Code AVP (AVP code 1031) is of type Enumerated. It is sent by the RCEF to the A-RACF within a Policy-Rule-Report AVP to identify the reason a policy decision is being reported. The following values are defined: • UNKNOWN_RULE_NAME (1) - This value is used to indicate that the pre-provisioned policy decision could not be successfully activated because the Policy-Rule-Name or Policy-Rule-Base-Name is unknown to the RCEF. • RATING_GROUP_ERROR (2) - This value is used to indicate that the policy decision could not be successfully installed or enforced because the Rating-Group specified within the Policy-Rule-Definition AVP by the A-RACF is unknown or, invalid. • SERVICE_IDENTIFIER_ERROR (3) - This value is used to indicate that the policy decision could not be successfully installed or enforced because the Service-Identifier specified within the Policy-Rule-Definition AVP by the A-RACF is invalid, unknown, or not applicable to the service being charged. • GW/RCEF_MALFUNCTION (4) - This value is used to indicate that the policy decision could not be successfully installed (for those provisioned from the A-RACF) or activated (for those pre-provisioned in RCEF) or enforced (for those already successfully installed) due to GW/RCEF malfunction. • RESOURCES_LIMITATION (5) - This value is used to indicate that the policy decision could not be successfully installed (for those provisioned from A-RACF) or activated (for those pre-provisioned in RCEF) or enforced (for those already successfully installed) due to a limitation of resources at the RCEF. • MAX_NR_BEARERS_REACHED (6) - This value is used to indicate that the policy decision could not be successfully installed (for those provisioned from A-RACF) or activated (for those pre-provisioned in RCEF) or enforced (for those already successfully installed) due to the fact that the maximum number of bearers has been reached for the IP-CAN session. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.4 AVPs imported from RFC 4006 | Table 5 describes the DIAMETER AVPs imported from RFC 4006 [8] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in RFC 4006 [8] but no listed in the following table should not be sent by DIAMETER nodes conforming to the present document and shall be ignored by receiving entities. The Vendor-Id field in the header for these AVPs shall not be included. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 41 Table 5: DIAMETER AVPs imported from RFC 4006 AVP flag rules Attribute name AVP Code Clause defined Value type Mu st May Should not Must not May encrypt CC-Request-Number 415 Unsigned32 M P V Y CC-Request-Type 416 Enumerated M P V Y Rating-Group 432 Unsigned32 M P V Y Service-Identifier 439 Unsigned32 M P V Y Service-Context-Id 461 UTF8String M P V Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5 AVPs imported from TS 129 209 | Table 6 describes the DIAMETER AVPs imported from TS 129 209 [9] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in TS 129 209 [9] but no listed in the following table should not be sent by DIAMETER nodes conforming to the present document and shall be ignored by receiving entities. The Vendor-Id field in the header for these AVPs shall be set to 3GPP (10415). Table 6: DIAMETER AVPs imported from TS 129 209 AVP flag rules Attribute name AVP Code Clause defined Value type Mu st May Should not Must not May encrypt Flow-Description 507 7.3.5.1 IPFilterRule M,V P Y Flow-Number 509 7.3.5.2 Unsigned32 M,V P Y Flow 510 7.3.5.3 Grouped M,V P Y Flow-Status 511 7.3.5.4 Enumerated M,V P Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.1 Flow-Description AVP (TS 129 209) | The Flow-Description AVP (AVP code 507) is of type IPFilterRule, and defines a packet filter for an IP flow with the following information: • Direction (in or out). • Source and destination IP address (possibly masked). • Protocol. • Source and destination port (list or ranges). The following restrictions apply: • Only the Action "permit" shall be used. • No "options" shall be used. • The invert modifier "!" for addresses shall not be used. • The keyword "assigned" shall not be used. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 42 If any of these restrictions is not observed by the AF, the server shall send an error response to the AF containing the Experimental-Result-Code AVP with value FILTER_RESTRICTIONS. The Flow description AVP shall be used to describe a single IP flow. The direction "in" refers to uplink IP flows, and the direction "out" refers to downlink IP flows. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.2 Flow-Number AVP (TS 129 209) | The Flow-Number AVP (AVP code 509) is of type Unsigned32, and it contains the ordinal number of the IP flow(s), assigned according to the rules in annex C of TS 129 207 [14] (3GPP TS 29.207). |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.3 Flows AVP (TS 129 209) | The Flows AVP (AVP code 510) is of type Grouped, and it indicates IP flows via their flow identifiers. If no Flow-Number AVP(s) is supplied, the Flows AVP refers to all Flows matching the Media-Component-Number. AVP Format: Flows::= < AVP Header: 510 > { Media-Component-Number} * [ Flow-Number] |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.5.4 Flow-Status AVP (TS 129 209) | The Flow-Status AVP (AVP code 511) is of type Enumerated, and describes whether the Policy Rule needs to be activated or not. The following values are defined: • ENABLED-UPLINK (0) - This value shall be used to activate a Policy Rule relative to the outgoing direction on the RCEF. • ENABLED-DOWNLINK (1) - This value shall be used to activate a Policy Rule relative to the incoming direction on the RCEF. • REMOVED (4) - This value shall be used to deactivate and remove a Policy Rule. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.6 AVPs Imported From RFC 4005 | The following table describes the DIAMETER AVPs imported from RFC 4005 [10] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. AVPs defined in [10] but no listed in the following table should not be sent by DIAMETER nodes conforming to the present document and shall be ignored by receiving entities. The Vendor-Id field in the header for these AVPs shall not be included. Table 7: DIAMETER AVPs imported from RFC 4005 AVP flag rules Attribute name AVP Code Clause defined Value type Mu st May Should not Must not May encrypt Called-Station-Id 30 7.3.6.1 UTF8String M P V Y Framed-IP-Address 8 7.3.6.2 OctetString M P V Y NOTE: The AVP header bit denoted as "M" indicates whether support of the AVP is required. The AVP header bit denoted as "V" indicates whether the optional Vendor-ID field is present in the AVP header. The 'P' bit indicates the need for encryption for end-to-end security. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 43 |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.3.6.1 Called-Station-Id AVP (RFC 4005) | The Called-Station-Id AVP (AVP Code 30) is of type UTF8String and contains the ASCII string describing the layer 2 address of the Transport Resource on the RCEF. For use with IEEE 802 access, the Called-Station-Id MAY contain a MAC address. NOTE: Further clarification on the use of Called-Station-Id is required in the next release. 7.3.6.2 Framed-IP-Address The Framed-IP-Address AVP is defined in the NASREQ application RFC 4005 [10]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4 Use of namespaces | Clause 7.4 contains the namespaces that have either been created in the present document, or the values assigned to existing namespaces managed by IANA [11]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.1 AVP codes | The present document assigns the AVP values in the range 550 to 599 from the AVP Code namespace managed by ETSI for its DIAMETER vendor-specific applications. See clause 7.3 for the list of AVP values assigned in the present document. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.2 Experimental-Result-Code AVP values | This clause defines new Experimental-Result-Code values that shall be supported by all DIAMETER implementations that conform to the present document. When one of the Experimental-Result-Code values defined in this clause is included in a response, it shall be inside an Experimental-Result AVP. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.3 Command Code values | The present document does not assign command code values but uses existing command defined in ITU-T NGN-GSI/DOC-127 [6]. |
4cc63473e1390ddeb8fec0b111f7887f | 183 060 | 7.4.4 Application-ID value | The present document uses value 16777253. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 44 Annex A (informative): Differences compared to ITU-T Rw and 3GPP Gx specifications The protocol used over the Re reference point and defined in the present specification has strong similarities with the Diameter applications used over the 3GPP Gx reference point and ITU-T Rw reference points. Table A.1 provides a high-level comparison of the three specifications regarding the list of Diameter commands supported. Table A.1 TS 183 060 (Re) TS 129 210 [i.2] (Gx) ITU-T Recommendation Q.3303.3 [i.1] (Rw) CC-Request X X X CC-Answer X X X Re-Auth-Request X X Re-Auth-Answer X X Policy-Install-Request X X Policy-Install-Answer X X Although the same commands are used by the three specifications, it should be noted that there are significant differences between them regarding the list of AVPs supported. ETSI ETSI TS 183 060 V2.1.1 (2009-04) 45 History Document history V2.1.1 April 2009 Publication |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 1 Scope | The present document is applicable to the a2 interface between the Connectivity Session Location and Repository Function (CLF) and the Network Access Configuration Function (NACF). Whenever it is possible the present document specifies the requirements for this protocol by reference to specifications produced by the IETF within the scope of Diameter. Where this is not possible, extensions to Diameter are defined within the present document. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 004 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub- System (NASS)". NOTE: The latest version in the V2.y.z series applies. [2] ETSI ES 282 003 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". NOTE: The latest version in the V2.y.z series applies. [3] ETSI TS 129 229: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Cx and Dx interfaces based on the Diameter protocol; Protocol details (3GPP TS 29.229)". [4] ETSI TS 129 329: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Sh interface based on the Diameter protocol; Protocol details (3GPP TS 29.329)". [5] IETF RFC 2960: "Stream Control Transmission Protocol". [6] IETF RFC 3588: "Diameter Base Protocol". ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 7 [7] IETF RFC 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change". [8] draft-ietf-geopriv-radius-lo-24 (January 2008): "Carrying Location Objects in RADIUS and Diameter". [9] ETSI ES 283 034 (V2.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Network Attachment Sub-System (NASS); e4 interface based on the DIAMETER protocol". NOTE: The latest version in the V2.y.z series applies. [10] ETSI ES 283 035 (V2.y.z): Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Network Attachment Sub-System (NASS); e2 interface based on the DIAMETER protocol". NOTE: The latest version in the V2.y.z series applies. [11] DSL Forum TR-069 (May 2004): "CPE WAN Management Protocol". [12] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] IETF RFC 3554: "On the use of Stream Control Transmission Protocol (SCTP) with IPSec". |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3 Definitions and abbreviations | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access record: set of information stored in the CLF in relation to an IP address Application Function (AF): element of the network architecture offering - or providing access to - applications that require information about the characteristics of the IP-connectivity session used to access such applications attribute-value pair: corresponds to an Information Element in a Diameter message NOTE: See RFC 3588 [13]. nASS user: See definition in [1]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Application Function A-RACF Access RACF AVP Attribute-Value Pair CLF Connectivity session Location and repository Function CSCF Call Session Control Function FQDN Fully Qualified Domain Name IANA Internet Assigned Numbers Authority IETF Internet Engineering Task Force IPSec IP Security ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 8 NACF Network Access Configuration Function NASS Network Attachment SubSystem PNA Push-Notification-Answer PNR Push-Notification-Request RACF Resource and Admission Control Function RACS Resource and Admission Control Subsystem RFC Request For Comments SCTP Stream Control Transport Protocol UCS Universal Character Set UDA User-Data-Answer UDR User-Data-Request |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 4 Overview | The Network Attachment SubSystem (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity associated with NASS User connected to TISPAN networks. The a2 reference point allows the NACF to register in the CLF the association between the IP address allocated to a NASS User and information identifying the network access to which this equipment is connected. The following information flows are used on the a2 interface: • Bind Indication. • Bind Acknowledgment. • Unbind Indication. • Bind information query. • Bind information query acknowledgement. The present document specifies the protocol for the a2 Diameter interface. UE TE CNG ARF AMF CNGCF NACF UAAF PDBF CLF Service control subsystems and applications Resource Admission Control Subsystem e3 e1 e1 a1 a3 a2 a4 e4 e2 e2 e2 e5 Figure 4.1: a2 interface Scope of the present document ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 9 |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5 Procedure Descriptions | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.1 General | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.1.1 Information elements | The following clauses describe the realization of the functional procedures defined in the NASS [1] and RACS specifications [2] using Diameter commands described in clause 7. This involves describing a mapping between the information elements defined in the NASS specification [1] and Diameter AVPs. In the tables that describe this mapping, each Information Element is marked as (M) Mandatory, (C) Conditional or (O) Optional: - A mandatory Information Element (marked as (M) in the table) shall always be present in the command. If this Information Element is absent, an application error occurs at the receiver and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. - A conditional Information Element (marked as (C) in the table) shall be present in the command if certain conditions are fulfilled: - If the receiver detects that those conditions are fulfilled and the Information Element is absent, an application error occurs and an answer message shall be sent back to the originator of the request with the Result-Code set to DIAMETER_MISSING_AVP. This message shall also include a Failed-AVP AVP containing the missing Information Element i.e. the corresponding Diameter AVP defined by the AVP Code and the other fields set as expected for this Information Element. If multiple Information Elements are missing, all corresponding AVP codes shall be included in the Failed-AVP AVP. If those conditions are not fulfilled, the Information Element shall be absent. If however this Information Element appears in the message, it shall not cause an application error and it may be ignored by the receiver if this is not explicitly defined as an error case. Otherwise, an application error occurs at the receiver and an answer message with the Result-Code set to DIAMETER_AVP_NOT_ALLOWED shall be sent back to the originator of the request. A Failed-AVP AVP containing a copy of the corresponding Diameter AVP shall be included in this message. - An optional Information Element (marked as (O) in the table) may be present or absent in the command, at the discretion of the application at the sending entity. Absence or presence of this Information Element shall not cause an application error and may be ignored by the receiver. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2 Procedures on the CLF - NACF interface | 5.2.1 Bind indication/Acknowledgement |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.1 Overview | This procedure is used to report the binding between the IP address allocated to a user equipment and identity of the access to which this equipment is connected from the NACF to the CLF. This information flow occurs when an IP address has been allocated to a user equipment. The NACF should trigger this procedure as soon as an IP address has been allocated. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7. Tables 5.1 and 5.2 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their mapping to Diameter AVPs. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 10 Table 5.1: Bind indication (NACF -> CLF) Information element name Mapping to Diameter AVP Cat. Description Globally Unique IP Address Globally-Unique-Address M This information element contains: - The IP address of the NASS User. - The addressing domain in which the IP address is significant. Logical Access ID Logical-Access-Id M The identity of the logical access to which the user equipment is connected. Physical Access ID Physical-Access-Id O The identity of the physical access to which the user equipment is connected. Access Network Type Access-Network-Type O The type of access network providing IP connectivity to the NASS user. Terminal Type Terminal-Type O The type of user equipment. Table 5.2: Bind Acknowledgment (CLF -> NACF) Information element name Mapping to Diameter AVP Cat. Description CNGCF address CNGCF-Address O The address of the CNGCF entity from which configuration data may be retrieved by the user equipment. Geographic Location Information Location-Data O Geographic location information. P-CSCF Identity (optional) SIP-Outbound-Proxy O The Identity of the P-CSCF for accessing IMS services. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.2 Procedure at the NACF side | After allocating the IP address to a user equipment, or when a Renew is received from a different access line, the NACF shall send a Bind Indication with the following information to CLF: • The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. • The Logical-Access-ID AVP shall be present. • Physical Access ID and Terminal Type may be present if available. If the NACF is implemented as a DHCP v4 server, the Logical-Access-Id AVP shall be derived from the value of the DHCP option 82, sub-option 1 and 2 received from the ARF. The Physical-Access-ID may also be derived from the value of these sub-options. If the NACF is implemented as a DHCP v4 server, the Terminal-Type AVP shall be set from the value of the DHCP option 77 received from the user equipment. On receipt of a Bind Acknowledgement with a Result-Code AVP indicating DIAMETER_SUCCESS, the NACF shall process the received AVPs as follows: • If the NACF is implemented as a DHCP v4 server, the CNGCF-Address AVP shall be used to set the value of DHCP Option 43 (DSL Forum Autoconfiguration Server) or DHCP Option 66 (TFTP server). • If the NACF is implemented as a DHCP v4 server, the Location-Information AVP shall be mapped to the DHCP option 123 or 99. • If the NACF is implemented as a DHCP v4 server, the SIP-Outbound-Proxy AVP shall be mapped to the DHCP option 120. The behaviour when the NACF does not receive a Bind Acknowledgement, or when it arrives after the internal timer waiting for it has expires, or when it arrives with an indication that is different to DIAMETER_SUCCESS, is outside the scope of the present document. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 11 |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.3 Procedure at the CLF side | If at least one of the specified AVP(s) is invalid, the CLF shall return a Binding Acknowledgement with a Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE and a Failed-AVP AVP containing a copy of the invalid AVP(s). If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the CLF shall: • Create an internal record to store the received information for future use. If the globally unique identifier contained in the Globally-Unique-Address AVP is already known and the received Logical Access ID is different than the one stored in the internal record, the CLF shall: • interact with RACS entities (i.e. A-RACF) to remove transport policies associated with the existing record and clear associated resources; • replace the entire content of the internal record with the received information for future use. If the CLF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and return a Bind Acknowledgement with a Result-Code AVP value set to DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code AVP set to DIAMETER_SYSTEM_UNAVAILABLE. Otherwise, the requested operation shall take place and the CLF shall return a Bind Acknowledgement with the Result-Code AVP set to DIAMETER_SUCCESS and one or more of the AVPs identified in table 5.2. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2 Unbind indication | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.1 Overview | This procedure is used by the NACF to report the case the allocated IP address is released (e.g. DHCP leased timer expiry) or due to a release of the underlying layer 2 resources. This enables the CLF to remove the corresponding record from its internal database. This procedure is mapped to the commands Push-Notification-Request/Answer in the Diameter application specified in clause 7. Tables 5.3 and 5.4 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their mapping to Diameter AVPs. Table 5.3: Unbind indication (NACF -> CLF) Information element name Mapping to Diameter AVP Cat. Description Globally Unique IP Address Globally-Unique-Address M This information element contains: - The IP address of the NASS User. - The addressing domain in which the IP address is significant. Table 5.4: Unbind indication acknowledgement (CLF -> NACF) Information element name Mapping to Diameter AVP Cat. Description Result Result Code / Experimental_ Result M Result of the request. Result Code AVP shall be used for errors defined in the Diameter Base Protocol. Experimental Result AVP shall be used for other errors. This is a grouped AVP which contains a Vendor Id AVP, and the error code in the Experimental Result Code AVP. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 12 |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.2 Procedure at the NACF side | On receipt of release request for the allocated IP address from the user equipment or in case of expiry of the lease period or on receipt of an indication that the underlying layer 2 connection has been lost, the NACF shall clear all information stored against the IP address and issue a Push-Notification-Request representing a Globally-Unique-Address. The IP-Connectivity-Status AVP shall be set to IP CONNECTIVITY LOST. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.3 Procedure at the CLF side | If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the CLF shall stop processing the request and set the Experimental-Result-Code to DIAMETER_ERROR_USER_UNKNOWN in the Unbind Indication acknowledgement. If the globally unique identifier contained in the Globally-Unique-Address AVP is already known, the CLF shall: • remove the existing session record; • interact with RACS entities (i.e. A-RACF) to remove transport policies associated with the session and clear associated resources. If the CLF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code set to DIAMETER_SYSTEM_UNAVAILABLE. Otherwise, the requested operation shall take place and the CLF shall return an Unbind Indication response with the Result-Code AVP set to DIAMETER_SUCCESS. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3 Bind information query/acknowledgment | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3.1 Overview | This procedure is used by the CLF to request binding information from the NACF, in the context of recovery procedures. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in clause 7. Tables 5.5 and 5.6 detail the involved information elements as defined in the NASS specification ES 282 004 [1] and their mapping to Diameter AVPs. Table 5.5: Bind information query (CLF -> NACF) Information element name Mapping to Diameter AVP Cat. Description Globally Unique IP Address Globally-Unique-Address M This information element contains: - The IP address of the NASS User. - The addressing domain in which the IP address is significant. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 13 Table 5.6: Bind information query acknowledgement (NACF -> CLF) Information element name Mapping to Diameter AVP Cat. Description Result Result Code / Experimental_ Result M Result of the request. Result Code AVP shall be used for errors defined in the Diameter Base Protocol. Experimental Result AVP shall be used for other errors. This is a grouped AVP which contains a Vendor Id AVP, and the error code in the Experimental Result Code AVP. Globally Unique IP Address Globally-Unique-Address O This information element contains: - The IP address of the NASS User. - The addressing domain in which the IP address is significant. Logical Access ID Logical-Access-Id O The identity of the logical access to which the user equipment is connected. Physical Access ID Physical-Access-Id O The identity of the physical access to which the user equipment is connected. Access Network Type Access-Network-Type O The type of access network providing IP connectivity to the NASS user. Terminal Type Terminal-Type O The type of user equipment. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3.2 Procedure at the CLF side | The CLF may use this procedure after a restart, upon reception of the query request from AF associated with an IP-Address for which no record is stored. The CLF determines the NACF responsible for this IP address from the IP realm, and possibly the address range within this realm, it belongs to. In order to cope with network configurations where multiple NACF are associated with the same IP realm and are using overlapping address ranges, the CLF may apply one of the following procedures: • The CLF queries each of the NACF until it gets a Bind Information Query acknowledgement with the Result-Code AVP set to DIAMETER_SUCCESS. • The CLF sends the query to a Diameter Agent that has sufficient routing information to enable this query to be delivered to the appropriate NACF instance. If no successful answer is received, the CLF shall delete all information that may have been stored regarding this IP address and provides an appropriate response to the requesting AF. The CLF shall populate the Binding Information Query as follows: 1) The Globally-Unique-Address AVP shall be included. 2) The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3.3 Procedure at the NACF side | Upon reception of the Bind Information Query, the NACF shall, in the following order: 1) If the Globally-Unique-Address AVP is present, use this information as a key to retrieve the requested session information. 2) If no session record is stored for the Globally-Unique-Address AVP, return a Bind Information Query Acknowledgment with the Experimental-Result-Code AVP set to DIAMETER_ERROR_USER_UNKNOWN. If the NACF cannot fulfil the received request for reasons not stated in the above steps, e.g. due to database error, it shall stop processing the request and set Result-Code to DIAMETER_UNABLE_TO_COMPLY or an Experimental-Result-Code AVP set to DIAMETER_USER_DATA_NOT_AVAILABLE. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 14 Otherwise, the requested operation shall take place and the NACF shall return a Bind Information Query acknowledgement with the Result-Code AVP set to DIAMETER_SUCCESS and the session data described in table 5.6. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6 Use of the Diameter base protocol | With the clarifications listed in the following sub clauses the Diameter Base Protocol defined by RFC 3588 [6] shall apply. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.1 Securing Diameter Messages | For secure transport of Diameter messages, IPSec may be used. Guidelines on the use of SCTP with IPSec can be found in RFC 3554 [i.1]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.2 Accounting functionality | Accounting functionality (Accounting Session State Machine, related command codes and AVPs) is not used on the a2 interface. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.3 Use of sessions | Diameter sessions are implicitly terminated. An implicitly terminated session is one for which the server does not maintain state information. The client does not need to send any re-authorization or session termination requests to the server. The Diameter base protocol includes the Auth-Session-State AVP as the mechanism for the implementation of implicitly terminated sessions. The client (server) shall include in its requests (responses) the Auth-Session-State AVP set to the value NO_STATE_MAINTAINED (1), as described in RFC 3588 [6]. As a consequence, the server does not maintain any state information about this session and the client does not need to send any session termination request. Neither the Authorization-Lifetime AVP nor the Session-Timeout AVP shall be present in requests or responses. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.4 Transport protocol | Diameter messages over the a2 interface shall make use of SCTP as defined in RFC 2960 [5] and shall utilize the new SCTP checksum method specified in RFC 3309 [7]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.5 Routing considerations | This clause specifies the use of the Diameter routing AVPs Destination-Realm and Destination-Host. Requests initiated by the NACF towards the CLF shall include both Destination-Host and Destination-Realm AVPs. The NACF obtains the Destination-Host AVP to use in requests towards a CLF, from configuration data. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the NACF. Requests initiated by the CLF towards the NACF shall include both Destination-Host and Destination-Realm AVPs. The CLF obtains the Destination-Host AVP to use in requests towards a NACF, from the Origin-Host and Origin-Realm AVPs received in previous commands from the NACF related to the same IP realm. Consequently, the Destination-Host AVP is declared as mandatory in the ABNF for all requests initiated by the CLF. Destination-Realm AVP is declared as mandatory in the ABNF for all requests. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 15 |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 6.6 Advertising application support | The NACF and CLF shall advertise support of the e4 specific application by including the value of the application identifier in the Auth-Application-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. The vendor identifier value of ETSI (13019) shall be included in the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, and in the Vendor-Id AVP within the Vendor-Specific-Application-Id grouped AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands. Additionally, support of 3GPP AVPs shall be advertised by adding the vendor identifier value of 3GPP (10415) to the Supported-Vendor-Id AVP of the Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands, NOTE: The Vendor-Id AVP included in Capabilities-Exchange-Request and Capabilities-Exchange-Answer commands that is not included in the Vendor-Specific-Application-Id AVPs as described above indicate the manufacturer of the Diameter node as per RFC 3588 [6]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7 DIAMETER application | This clause specifies the use of the e4 a Diameter application that allows a Diameter server and a Diameter client exchange information related to IP-connectivity sessions. The Diameter application identifier assigned to this application is 16777231 (allocated by IANA for e4). The Diameter Base Protocol as specified in RFC 3588 [6] is used to support information transfer on both interfaces. RFC 3588 [6] shall apply except as modified by the defined support of the methods and the defined support of the commands and AVPs, result and event codes specified in clause 5. Unless otherwise specified, the procedures (including error handling and unrecognised information handling) are unmodified. 7.1 Commands The present document re-uses and modifies commands defined in ETSI e4 interface ES 283 034 [9] which itself re-uses and modifies commands defined in the 3GPP Sh specifications [4]. Only the following commands defined in TS 129 329 [4] are used. Any other command defined in TS 129 329 [4] shall be ignored. Table 7.1a: Command-code values Command-Name Abbreviation Code User-Data-Request UDR 306 User-Data-Answer UDA 306 Push-Notification-Request PNR 309 Push-Notification-Answer PNA 309 AVPs defined in TS 129 329 [4] and not used in the present document are not shown in the below clauses. If received, these AVPs shall be ignored by the NACF and the CLF. New AVPs are represented in bold. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.1.1 Push-Notification-Request command | The Push-Notification-Request (PNR) command, indicated by the Command-Code field set to 309 and the "R" bit set in the Command Flags field, is sent by a Diameter server to a Diameter client in order to notify changes in the NASS User data in the server. This command is defined in TS 129 329 [4] and used with additional AVPs defined in the present document. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 16 Message Format: < Push-Notification-Request > ::= < Diameter Header: 309, REQ, PXY, 16777231 > < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } { Destination-Host } { Destination-Realm } [Globally-Unique-Address] [Logical-Access-Id] [Physical-Access-Id] [Terminal-Type] [Access-Network-Type] [IP-Connectivity-Status] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.1.2 Push-Notification-Answer command | The Push-Notifications-Answer (PNA) command, indicated by the Command-Code field set to 309 and the "R" bit cleared in the Command Flags field, is sent by a client in response to the Push-Notification-Request command. This command is defined in TS 129 329 [4]. The Experimental-Result AVP may contain one of the values defined in clause 7.2 or in TS 129 229 [3] or in the present document. Message Format: < Push-Notification-Answer > ::= < Diameter Header: 309, PXY, 16777231 > < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [CNGCF-Address] [Location-Data] [SIP-Outbound-Proxy] *[ AVP ] *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ] |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.1.3 User-Data-Request command | The User-Data-Request (UDR) command, indicated by the Command-Code field set to 306 and the "R" bit set in the Command Flags field, is sent by a Diameter client to a Diameter server in order to request NASS User data. This command is defined in TS 129 329 [4] and used with additional AVPs defined in the present document. Message Format: < User-Data -Request > ::= < Diameter Header: 306, REQ, PXY, 16777231 > < Session-Id > { Vendor-Specific-Application-Id } { Auth-Session-State } { Origin-Host } { Origin-Realm } [ Destination-Host ] ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 17 { Destination-Realm } [Globally-Unique-Address] [Logical-Access-Id] *[ AVP ] *[ Proxy-Info ] *[ Route-Record ] |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.1.4 User-Data-Answer command | The User-Data-Answer (UDA) command, indicated by the Command-Code field set to 306 and the "R" bit cleared in the Command Flags field, is sent by a server in response to the User-Data-Request command. This command is defined in TS 129 329 [4] and used with additional AVPs defined in the present document. The Experimental-Result AVP may contain one of the values defined in clause 7.2 or in TS 129 229 [3] or in the present document. Message Format: < User-Data-Answer > ::= < Diameter Header: 306, PXY, 16777231 > < Session-Id > { Vendor-Specific-Application-Id } [ Result-Code ] [ Experimental-Result ] { Auth-Session-State } { Origin-Host } { Origin-Realm } [Globally-Unique-Address] [Logical-Access-Id] [Physical-Access-Id] [Terminal-Type] [Access-Network-Type] *[ AVP ] *[ Failed-AVP ] *[ Proxy-Info ] *[ Route-Record ] 7.2 Result-Code AVP values This clause defines new result code values that must be supported by all Diameter implementations that conform to the present document. When one of the result codes defined here is included in a response, it shall be inside an Experimental-Result AVP and Result-Code AVP shall be absent. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.2.1 Success | Result codes that fall within the Success category are used to inform a peer that a request has been successfully completed. No result codes within this category have been defined so far. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.2.2 Permanent Failures | Errors that fall within the Permanent Failures category are used to inform the peer that the request failed, and should not be attempted again. No errors within this category have been defined so far. However the following error defined in TS 129 229 [3] is used in the present document: DIAMETER_ERROR_USER_UNKNOWN (5001) When this result code is used, the 3GPP Vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 18 |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.2.3 Transient Failures | Errors that fall within the transient failures category are those used to inform a peer that the request could not be satisfied at the time that it was received. The request may be able to be satisfied in the future. The following error defined in ES 283 034 [9] is used in the present document: DIAMETER_SYSTEM_UNAVAILABLE (4001) This error is returned when a request could not be satisfied at the time that it was received due to a temporary internal failure or congestion. When this result code is used, the ETSI Vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. The following error defined in TS 129 229 [3] is also used in the present document: DIAMETER_USER_DATA_NOT_AVAILABLE (4100) When this result code is used, the 3GPP Vendor ID shall be included in the Vendor-Id AVP of the Experimental-Result AVP. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.3 AVPs | The following tables summarize the AVP used in the present document, beyond those defined in the Diameter Base Protocol. Table 7.1 describes the Diameter AVPs defined in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. The Vendor-Id header of all AVPs defined in the present document shall be set to ETSI (13019). Table 7.1: Diameter AVPs defined in the present document AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt SIP-Outbound-Proxy 601 13019 7.3 OctetString V M No CNGCF-Address 600 13019 7.3 Grouped V M No TFTP-Server 602 13019 7.3 UTF8String V M No ACS-Server 603 13019 7.3 UTF8String V M No NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. Table 7.2 describes the Diameter AVPs defined for the e2 interface protocol (ES 283 035 [10]) and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. Vendor-Id header for these AVPs shall be set to ETSI (13019). Table 7.2: Diameter AVPs imported from the e2 specification AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Terminal-Type 352 See ES 283 035 [10] OctetString V M No NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. Table 7.3 describes the Diameter AVPs defined for the e4 interface protocol (ES 283 034 [9]) and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. Vendor-Id header for these AVPs shall be set to ETSI (13019). ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 19 Table 7.3: Diameter AVPs imported from the e4 specification AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Logical-Access-Id 302 See ES 283 034 [9] OctetString V M No Physical-Access-Id 313 See ES 283 034 [9] UTF8String V M No Access-Network-Type 306 See ES 283 034 [9] Grouped V M No IP-Connectivity-Status 305 See ES 283 034 [9] Enumerated V M No NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. Table 7.4 describes the Diameter AVPs defined in IETF specifications other than RFC 3588 [6] and used in the present document, their AVP Code values, types, possible flag values and whether the AVP may or not be encrypted. Flags values are described in the context of the present document rather than in the context of the application where they are defined. Table 7.4: Diameter AVPs defined in IETF specifications AVP Flag rules Attribute Name AVP Code Clause defined Value Type Must May Should not Must not May Encrypt Location-Data 128 [8] OctetString M V No NOTE: The AVP header bit denoted as "M", indicates whether support of the AVP is required. The AVP header bit denoted as "V", indicates whether the optional Vendor-ID field is present in the AVP header. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.3.1 Logical-Access-ID AVP | See the definition in e4 ES 283 034 [9]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.3.2 Physical-Access-ID | See the definition in e4 ES 283 034 [9]. |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 7.3.3 Terminal-Type AVP | See the definition in e2 ES 283 035 [10]. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.