hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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].
|
223ebff1738b9aebce60fbd8ef406718
|
183 059-1
|
7.3.4 IP-Connectivity-Status
|
The IP Connectivity Status AVP (AVP code 305 13019) is defined in the e4 specification ES 283 034 [9].
|
223ebff1738b9aebce60fbd8ef406718
|
183 059-1
|
7.3.5 CNGCF-Address
|
The CNGCF-Address AVP (AVP code 600 13019) is of type Grouped and contains one or more CNGCF addresses, each of which identifying different types of CNGCF implementation. AVP Format: CNGCF-Address ::= < AVP Header: 600 13019 > [TFTP-Server] [ACS-Server]
|
223ebff1738b9aebce60fbd8ef406718
|
183 059-1
|
7.3.6 SIP-Outbound-Proxy
|
The SIP-Outbound-Proxy AVP (AVP code 601 13019) is of type OctetString and identifies a SIP outbound proxy (e.g. a P-CSCF when accessing to the IMS) in the form of an FQDN. ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 20
|
223ebff1738b9aebce60fbd8ef406718
|
183 059-1
|
7.3.7 Access-Network-Type AVP
|
The Access-Network-Type AVP (AVP code 306 13019) is defined in the e4 specification ES 283 034 [9].
|
223ebff1738b9aebce60fbd8ef406718
|
183 059-1
|
7.3.8 Location-Data AVP
|
The Location-Data AVP is defined in draft-ietf-geopriv-radius-lo-19 [8]. It contains location data in the form of either Civic Location or Geospatial Location. 7.3.9 TFTP-Server The TFTP-Server AVP (AVP code 602 13019) is of type UTF8String and identifies a TFTP server. 7.3.10 ACS-Server The ACS-Server AVP (AVP code 603 13019) is of type UTF8String and identifies an Autoconfiguration Server conforming to the DSL Forum specifications (TR-69 [11]) in the form of a URI (RFC 3986 [12]). ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 21 Annex A (informative): Mapping of a2 operations and terminology to Diameter TableA.1 defines the mapping between the information flows defined in ES 282 004 [1] and Diameter commands: Table A.1: a2 message to Diameter command mapping a2 message Source Destination Command-Name Abbreviation Bind Indication NACF CLF Push-Notification-Request PNR Bind Indication Acknowledgement CLF NACF Push-Notification-Answer PNA Unbind Indication NACF CLF Push-Notification-Request PNR Unbind Indication Acknowledgement CLF NACF Push-Notification-Answer PNA Bind Information Query CLF NACF User-Data-Request UDR Bind Information Query Acknowledgement NACF CLF User-Data-Answer UNA ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 22 Annex B (informative): Bibliography ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209) " IETF RFC 2234: "Augmented BNF for syntax specifications: ABNF". IETF RFC 4005: "Diameter Network Access Server application". ETSI ETSI TS 183 059-1 V2.1.1 (2009-08) 23 History Document history V2.1.1 August 2009 Publication
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
1 Scope
|
The present document specifies the Stage 3 of the real-time transfer of tariff information between a Charge Determination Point (CDP) and a Charge Generation Point (CGP) by means of the Session Initiation Protocol (SIP). ETSI ETSI TS 183 058 V2.1.0 (2008-06) 6
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
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. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
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] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] ETSI TS 129 458: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; SIP Transfer of IP Multimedia Service Tariff Information; Protocol specification (Release 8)".
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
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. Not applicable. ETSI ETSI TS 183 058 V2.1.0 (2008-06) 7
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
3 Definitions and abbreviations
| |
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 129 458 [7] apply.
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 129 458 [7] apply.
|
a29ebda6e1e5a166ae40ff84eabdbbf1
|
183 058
|
4 SIP Transfer of Charging Information
|
The provisions of the present document are contained in TS 129 458 [7]. ETSI ETSI TS 183 058 V2.1.0 (2008-06) 8 Annex A (informative): Signalling flows Information is contained in TS 129 458 [7]. ETSI ETSI TS 183 058 V2.1.0 (2008-06) 9 Annex B (informative): SIP Transfer of Charging Information parameters Information is contained in TS 129 458 [7]. ETSI ETSI TS 183 058 V2.1.0 (2008-06) 10 Annex C (normative): SIP Transfer of charging information XML schema The provisions of the present document are contained in TS 129 458 [7]. ETSI ETSI TS 183 058 V2.1.0 (2008-06) 11 History Document history V2.0.0 January 2008 Publication V2.1.0 June 2008 Publication
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
1 Scope
|
The present document provides an overview of the identifiers used within 3GPP which are considered applicable to NGN. It is intended that the information contained in the present document are not referred to any specific TISPAN Releases, and it shall be used as the basis for defining additional identifiers and related parameters to facilitate the implementation of TISPAN NGN standards.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • For a non-specific reference, the latest version applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. [1] ETSI TS 122 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Service requirements for the Internet Protocol (IP) multimedia core network subsystem (IMS); Stage 1 (3GPP TS 22.228 Release 6)". [2] IETF RFC 1035: "Domain names - implementation and specification". [3] IETF RFC 3966: "The tel URI for Telephone Numbers". [4] ETSI TS 131 102: "Universal Mobile Telecommunications System (UMTS); Characteristics of the Universal Subscriber Identity Module (USIM) application (3GPP TS 31.102 Release 6)". [5] ETSI TS 122 101: "Universal Mobile Telecommunications System (UMTS); Service aspects; Service principles (3GPP TS 22.101 Release 6)". [6] ETSI TS 123 003: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Numbering, addressing and identification (3GPP TS 23.003 Release 6)". [7] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS); Stage 2 (3GPP TS 23.228 Release 6)". [8] ETSI TS 129 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents (3GPP TS 29.228 Release 6)". [9] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users". [10] ITU-T Recommendation E.164: "The international public telecommunication numbering plan". [11] IETF RFC 3261: "SIP: Session Initiation Protocol". [12] IETF RFC 3761: "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)". [13] IETF RFC 1093: "The NSFNET routing architecture". ETSI ETSI TS 184 002 V1.1.1 (2006-10) 6 [14] ETSI ES 282 004: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [15] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". [16] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [17] ETSI ES 282 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); PSTN/ISDN Emulation Sub-system (PES); Functional architecture". [18] IETF RFC 4282: "The Network Access Identifier". [19] ETSI TS 182 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description (3GPP TS 23.228 v7.2.0, modified)". [20] ITU-T Recommendation E.164.1: "Criteria and procedures for the reservation, assignment and reclamation of E.164 country codes and associated identification codes (ICs)". [21] ITU-T Recommendation E.164.2: "E.164 numbering resources for trials". [22] ITU-T Recommendation E.164.3: "Principles, criteria and procedures for the assignment and reclamation of E.164 country codes and associated identification codes for groups of countries". [23] ITU-T Recommendation E.190: "Principles and responsibilities for the management, assignment and reclamation of E-series international numbering resources". [24] ITU-T Recommendation E.195: "ITU-T International numbering resource administration".
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
3 Definitions, symbols and abbreviations
| |
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 180 000 (see bibliography) and the following apply: address: identifier for a specific termination point and used for routeing to this termination point E.164 number: string of decimal digits that satisfies the three characteristics of structure, number length and uniqueness specified of ITU-T Recommendation E.164 [10] NOTE: The number contains the information necessary to route the call to the subscriber or to a point where a service is provided. The hierarchical structures of International E.164-numbers [10] are as follows: Figure 1 ETSI ETSI TS 184 002 V1.1.1 (2006-10) 7 identifier: a series of digits, characters and symbols used to identify uniquely subscriber(s), user(s), network element(s), function(s) or network entity(ies) providing services/applications NOTE 1: Identifiers can be used for registration or authorization. They can be either public to all networks or private to a specific network (private IDs are normally not disclosed to third parties). NOTE 2: In 3GPP the term 'Identity' or 'ID' is typically used instead. identity: identifier allocated to a particular entity, e.g. a particular end-user, provides an Identity for that entity NOTE: The definition currently provided in TR 180 000 (see bibliography): The attributes by which an entity or person is described, recognized or known. name: identifier of an entity (e.g. subscriber, network element) that may be resolved/translated into an address short code: string of digits in the national telephony numbering plan as defined by the national Numbering Plan Administration (NPA) which can be used as a complete dialling sequence on public networks to access a specific type of service/network NOTE: The short code is a non-E.164 number and its length does not exceed five digits, in exceptional cases six digits. An example is the emergency number 112 used in the EU. tel URI: representation of an international E.164 number or another number with the context defined (e.g. private number, short code) NOTE: RFC 3966 [3], which defines the use of the tel URI, also uses the term "local number" , but uses it in a totally different way from E.164. RFC 3966 [3] recognizes: "Global number" - which always start with +CC. "Local number" - which is anything that is not a "global number". Thus what E.164 refers to as national numbers, "local numbers" and short codes (as well as other types such as private numbers) would all be treated by RFC 3966 [3] as "local numbers". In the case of "local numbers", RFC 3966 [3] uses a context qualifier to distinguish the type of number. In the context of the present document, the term "local number" will be used in the E.164 sense and international/national format issues has to be defined in the SIP context.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project AESA ATM End System Address AS Application Service ATM Asynchronous Transfer Mode BGCF Breakout Gateway Control Function CC Country Code ccTLD country code Top Level Domain (e.g. .fr) CLF Connectivity session Location and repository Function CLI Calling Line Identity CN Core Network CPE Customer Premises Equipment CS Circuit Switched CS/GPRS Circuit Switched/General Packet Radio Service CSCF Call Session Control Function DHCP Dynamic Host Configuration Protocol DNS Domain Name System DSL Digital Subscriber Line EDGE Enhanced Data GSM Environment ENUM E.164 Number Mapping FFS For Further Study ETSI ETSI TS 184 002 V1.1.1 (2006-10) 8 GERAN GSM/EDGE Radio Access Network GPRS General Packet Radio Service GRX GPRS Roaming eXchange GSM Global System for Mobile Communication GSMA GSM Association gTLD generic Top Level Domain (e.g. .org) HPLMN Home PLMN HSS Home Subscriber Server ICANN Internet Corporation for Assigned Names and Numbers I-CSCF Interworking CSCF ID Identifier/Identity IIN Issuer Identifier Number IM CN IP Multimedia Core Network IM IP Multimedia IMPU IMS Public User Identity IMS IP Multimedia Subsystem IMSI International Mobile Subscriber Identity IP Internet Protocol ISDN Integrated Services Digital Network ISIM IM Services Identity Module I-WAN IP-Wide Area Network LIF Location Information Forum LIR Local Internet Registry MCC Mobile Country Code MGCF Media Gateway Control Function MNC Mobile Network Code MSIN Mobile Station Identification Number MSISDN Mobile Station ISDN Number NACF Network Access Configuration Function NAI Network Access Identifier NASS Network Attachment SubSystem NDC National Destination Code NGN Next Generation Network NIR National Internet Registry NPA Numbering Plan Administration NRA National Regulatory Authority PBX Private Branch Exchange P-CSCF Proxy CSCF PDBF Profile Data Base Function PDN Public Data Network PLMN Public Land Mobile Network PPP Point-to-Point Protocol PSI Public Service Identifier PSTN Public Switched Telephone Network QoS Quality of Service RACS Resource and Admission Control Subsystem RAN Radio Access Network RFC Request For Comments RIR Regional Internet Registry S-CSCF Serving CSCF SGSN Serving GPRS Support Node SIM Subscriber Identity Module SIP Session Initiation Protocol SLF Subscription Locator Function SN Subscriber Number SS7 Signalling System No. 7 TETRA Terrestrial European Trunked Radio TLD Top Level Domain TMSI Temporary Mobile Subscriber Identity UE User Equipment UICC Universal Integrated Circuit Card UML Unified Modelling Language ETSI ETSI TS 184 002 V1.1.1 (2006-10) 9 UMTS Universal Mobile Telecommunication System UPSF User Profile Server Function URI Universal Resource Identifier USIM UMTS Subscriber Identity Module UTRAN UMTS Radio Access Network VPLMN Visited PLMN WLAN Wireless Local Area Network WTSA World Telecommunication Standardization Assembly
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
4 Background on identifiers for NGN
|
NGN must be able to support the existing Naming, Numbering and Addressing plans for fixed and mobile networks. It is therefore important to have a full understanding of how these plans work. For networks like PSTN/ISDN, GSM-based PLMNs and the Internet there is a common terminology used concerning the present identifiers (IDs) used in these networks. The terms, which are defined in ITU-T Recommendation E.191 (see bibliography), are name, number and address. In the PSTN the ID is the E.164 number [10] and that number is used for identifying and routeing the call to the subscriber/user or services. With the introduction of services based on non-geographic numbers and number portability the function of the number has been split between a name role for identifying the user or service and an address role to indicate how to route the call to the subscriber's network termination point. In GSM-based PLMNs the E.164 number is often called an MSISDN to indicate that the E.164 number is used for mobile services. Another ID used in GSM networks is the IMSI, based on ITU-T Recommendation E.212 [9]. The IMSI provides a unique identifier of the mobile subscription for registration purposes. It is also used to identify the home PLMN (HPLMN) when the mobile subscriber/terminal is roaming in a visited mobile network (VPLMN). Most of the present SIM cards used in GSM networks are marked with another ID called the Issuer Identifier Number (IIN) according to ITU-T Recommendation E.118 (see bibliography). An introduction to different IDs used in PLMNs based on 3G systems can be found in clause 5.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
4.1 Circuit switch network identifiers
|
For circuit switched networks there are also some IDs used for different network functions. For example Signalling Point Codes for the ITU-T Signalling System No. 7 (SS7). Some of the signalling point codes are used in the international signalling network, ISPCs according to ITU-T Recommendation Q.708 (see bibliography), and some are used as NSPCs between national networks. These addresses can be seen as public IDs but there are also signalling point codes, with Network Indicator 2, used solely as a private ID inside one operator's network and therefore never disclosed to other operators.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
4.2 Packet switch network identifiers
|
For packet switched networks like the Internet and other IP based networks names in the form of Domain Names according to RFC 1035 [2] are well known and used. For the Internet the separation between a name and an address have been used from the early days of the Internet (from the beginning although only IP addresses was the major ID). The Domain Name is used to identify the user/host and the IP address used for routeing to the interface to which the host is connected (for IP address format IPv4 and IPv6, see clause 7.1.2). The IP address is received through a name resolution with the help of the Domain Name System (DNS). Before the growth and success of the Internet other public data networks (PDN) based on X.25 (see bibliography) and X.21 (see bibliography) was used and some are still in function. For these PDNs a numbering plan based on ITU-T Recommendation X.121 (see bibliography) is used. For ATM networks there exist specific address resources named ATM End System Addresses (AESA). Different AESAs are used and one (ITU-IND AESA) is administered by the ITU TSB and is based on ITU-T Recommendation E.191 (see bibliography). There are also IDs from other naming, numbering, addressing or identification plans, like the numbering plan (ITU-T Recommendation F.69, see bibliography) for the diminishing telex service, IDs for TETRA networks and more network specific IDs like NSAPs (Network Service Access Point), but this clause has no intention to cover all kind of IDs in present public networks. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 10 As mentioned in this clause, identifiers are used throughout the network to identify sources/destinations of traffic and also resources within the network and the E.164 number is for example used by PSTN users to identify the destination of a call. In the context of an NGN, E.164 numbers need to be translated into other kind of IDs (e.g. IP addresses) usable within the NGN. This will be further elaborated in the present document.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
5 3GPP concept on the use of IDs
|
In UMTS based PLMNs there are many specific IDs used and they are described in detail in TS 123 003 [6] . The following clauses will highlight some of these 3GPP IDs that also will be applicable in some form in the NGN. 5.1 An Introduction to UICC, USIM, ISIM, Public IDs, Private IDs, Home Domain IDs This clause provides an understanding to the Universal Integrated Circuit Card (UICC), the UMTS Subscribers Identity Module (USIM), and the IM Services Identity Module (ISIM) and the relationship between all three entities. With the introduction of the IMS Domain within 3GPP a single level of registration was found to be insufficient. To provide the necessary attributes for registration to IMS to be carried out, an ISIM application was added to the UICC. In summary the USIM application is used to gain access to the UMTS access network (CS/GPRS network) and the ISIM is used to gain access to the IMS Domain (3GPP Release 6 or greater). A subscriber may access the IMS Domain: • with the values of the ISIM identifiers derived from the USIM (in the absence of ISIM); • with the value of the ISIM identifiers provisioned independently from the USIM. It should be made clear from this clause that to access the IMS Domain an ISIM is required (note that the required private identifier provided and validated by the operator can be derived from the USIM if the ISIM is absent). As stated above, it is possible the ISIM resides or not on a UICC. 2G and 3G access Figure 2: Key 3GPP IDs The introduction of the SIM card introduced not only a method of uniquely identifying a subscription irrespective of the GSM device being used, but also a higher level of security that was absent from the previous analogue system where cloning the handset was common. Cloning a SIM card is much more complex. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 11 As with the SIM card the UICC resides inside the mobile device. However, whereas the SIM is seen as the physical card together with the software to authenticate, authorize, and identify the subscriber, the UICC merely defines the physical characteristics of the smart card. The USIM and ISIM are seen as software applications resident on the UICC. As previously stated a USIM must be present and an ISIM may be present. The UICC should remain the property of the mobile network operator who will need to have the authority to decide as to which applications can reside on it, e.g. USIM, ISIM. NOTE: When accessing IMS over GERAN/UTRAN or I-WAN using ISIM, a USIM needs also to be present to access the rest of the 3GPP system. The general requirements being that the subscriber can be uniquely identifiable by the network, the service network can authenticate the subscriber, and that if a subscriber is being served by a network other than its home network, the visiting network shall be able to identify the associated home network. Clause 13 from TS 122 101 [5] provides further clarification of the USIM module and the ISIM module in relationship to the UICC.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
5.2 USIM
|
USIM is an application and not an identifier, this application is to reside on the UICC module. The following is a summary of the requirements for the USIM application: - Every USIM has a unique identifier and is associated with one and only one home network. - It is possible for a home network to uniquely identify a subscription by the USIM. - The USIM is used to provide security features. - For access to services, provided by Packet Switched or Circuit Switched Core Networks, a valid USIM is required. - The USIM resides on a UICC. USIM specific information is protected against unauthorized access or alteration. - Access to the IMS services is possible using the USIM derived private identifier in the event of no ISIM being present on the UICC. If an ISIM is present on the UICC it is used to access the IMS. The specification does not preclude the support of more than one USIM per UICC associated with the same or different home networks so long as the security problems which arise from such coexistence are solved. However, only one USIM can be active at any given time. The USIM's private ID is based on the IMSI which contains the Mobile Network Code (MNC) allocated by the appropriate country's NRA. The IMSI (based on ITU-T Recommendation E.212 [9]) can be used for registering the user on Circuit Switched networks and Packet Switched networks.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
5.3 ISIM
|
ISIM is an application and not an identifier, this application is optional to the UICC module. The following is a summary of the requirements for the ISIM application: - Access to the IMS Domain is possible using an ISIM application. - The ISIM is sufficient for providing the necessary security features for the IMS. - The ISIM may reside on a UICC. ISIM specific information is protected against unauthorized access or alteration. It is recommended that the format of the identifier(s) stored in the ISIM are based on E.164 and/or E.212 resources. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 12 The ISIM consist of Public ID(s), Private ID and Home Domain ID. The Home Domain ID provides the means by which that IMS routes a users" registration request to the Home IMS Network. The Private ID is how the user is authenticated by the user's Home IMS Network and the Public ID is how the user is contactable by other users for IMS based services. If there is no ISIM application, a backward compatibility mechanism is in place to derive the Home Network Domain name (ID)from the IMSI as described in the following steps: 1) Take the first 5 or 6 digits, depending on whether a 2 or 3 digit MNC is used (see TS 131 102 [4] ) and separate them into MCC and MNC; if the MNC is 2 digits then a zero shall be added at the beginning. 2) Use the MCC and MNC derived in step 1 to create the "mnc<MNC>.mcc<MCC>.3gppnetwork.org" Domain Name. 3) Add the label "ims." to the beginning of the domain. An example of a Home Network Domain Name is: IMSI in use: 234150999999999; Where: MCC = 234; MNC = 15; MSIN = 0999999999, which gives the Home Network Domain Name: ims.mnc015.mcc234.3gppnetwork.org. NOTE 1: An MCC is assigned by the ITU-T to a member state. MNCs under this MCC are assigned by the NRA of this member state to an operator. MSINs are assigned by the operator to its customers. The use of the Home Domain Name works best in a globally agreed and unique domain name space which all operators (e.g. fixed and mobile) who need to use it can access directly. NOTE 2: Having to use the Domain Name '3gppnetwork.org' requires access to the 3GPP DNS system. The Domain Name 3gppnetwork.org is controlled by GSMA for registration in a private extranet. If there is no ISIM application, the private identifier is not known, in that case the private identifier could be derived from the IMSI (TS 123 003 [6] clause 13.3). However, this derived identifier is not visible for end-users and it is replaced by the actual public identifier obtained during the registration procedure (see GSMA IR.65 subclause 8.1, see bibliography) The following steps show how to build the Private Identifier out of the IMSI: 1) Use the whole string of digits as the username part of the private identifier. 2) Convert the leading digits of the IMSI, i.e. MNC and MCC, into a domain name, as described in clause 6.2.1.1. The result will be a Private User identifier of the form "<IMSI>@ims.mnc<MNC>.mcc<MCC>.3gppnetwork.org". For example: If the IMSI is 234150999999999 (MCC = 234, MNC = 15), the private user identifier then takes the form 234150999999999@ims.mnc015.mcc234.3gppnetwork.org The private ID is used only in the Home Domain operator's network. The approach for 3GPP UEs roaming into the NGN is specified ( TS 123 003 [6] clause 13.2). The realm can take a number format as defined by the Home Domain operator , except in the case where the Private ID (containing the realm) is derived from the IMSI. The whole of the username@realm needs to be unique in the Home Domain operator's network. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 13
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
5.4 Backward Compatibility
|
3GPP have provided backward-compatibility with the UMTS Services Identity Module (USIM) and thus with IMSIs and MSISDN numbers. There are other identifiers that ETSI will need to address in time, but these ones are critical to the whole NGN structure and so are focussed on initially. Interoperabiltiy betweeen operators who specify their networks by reference to different families of standards, e.g. ETSI TISPAN or 3GPP, is an important issue. Future work must consider compatibility of identifiers in an environment where such interoperability occurs as there will be an evolution to a fully encompassing NGN.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6 Concept on the use of IDs in NGN
|
In principle, it should be possible for any user of the ISDN, PSTN, PLMN or an IP-based NGN network to identify users in a global basis. That implies that Public IDs are globally unique.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.1 Introduction
|
Due to the ubiquitous use of identifiers, the list below should not be considered as providing a complete list. Table 1: Overview of Identifiers Public ID (User aware) Format of the Public ID within the network Private ID (Network Aware) NGN Layer Name(s) • SIP URI • ID stored in ISIM User/Service Identifier Number(s) • tel URI • SIP URI with domain operator- provided • ID stored in ISIM or derived from USIM Service Network Identifier Address • Number, and Routeing Number • IP Address • Network ID • Line ID Transport The format SIP URI and tel URI is a means to translate the identifiers used by the network in order to format E.164 numbers in coherence with SIP protocol requirements, as described in table 1. The NGN Layers are according to [16]: • Service Stratum/Layer The different services/applications are located here, together with the databases keeping the user related information and identifiers. • Transport Stratum/Layer This part provides for the transport of the media streams and also supports the users in gaining access to the applications and also control of resources and admissions. • Customer and Terminal functions This part covers the networking infrastructure at the user's premises. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 14 Figure 3 shows the NGN stratum/layer (more generic than the figure contained in [16]. R e so u r c e an d A d m i s s i o n C o n tr o l F u n c ti o n s R A CS Bas e d o n 3 G P P I MS I P C on n e c ti vi ty A c c e s s N e t wo r k A nd r e l at e d f un cti o n a l it y N e t w or k A c c es s A t t ach m e n t F u n cti o n s N A S S Ot h er Mu l t i m e d i a C o m p o n e n ts É S tr eam i n g S e r v i ce s ( R T S P b a s e d ) A p p licati o n F u n ctio n s C o r e tra n s p o rt F u n ctio ns 3G P P I P - CAN A cce ss T r a ns po r t F unc tio ns 3 G P P T er m in a l s NG N T e r m i na l s C u s to m er N e t w o r ks U s er P r of i l e F u n cti o n s Other Networks L e g a cy T e r m i n a l s G W P S T N / I S D N E m u l a t i o n ( S I P - I ba se d ) I P M u l t i m e d i a C o m p o n e n t ( C o r e I MS) ( S I P b a se d ) N N I T r a n s p o r t S tr a tu m S e r v i ce S tra tu m U N I N etw o r k E n t r y F u n c t io n s Customer and Terminal Functions Service and Control Functions Common Components Figure 3: Functional model of the TISPAN NGN Identifier required: • User and NGN Terminals IDs. • NASS IDs: see clause A.2.2. • RACS IDs: see clause A.2.3. • Use Data IDs: see clause A.2.1. • IMS/PES IDs. • Common components IDs (see [16] and [17]), are used by several subsystems, such as those required for accessing applications, charging functions, user profile management, security management, routeing data (e.g. ENUM), etc.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2 IDs used in TISPAN NGN
|
To enable access to NGN using the existing mobile subscriptions (that are based only on USIM) also a mechanism to derive these values from USIM could be evaluated. This results in the requirement to support Home Domain Names in the 3GPP format based on the use of MNC, MCC. NOTE: If MNC and MCC are to be used by fixed network operators, this might require changes to national regulations. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 15
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1 IDs for Users
|
An NGN operator can store User IDs in ISIMs provided to its subscribers or directly inside the terminals, if necessary. 3GPP specify that the ISIM itself is made up of various attributes. The main 3GPP attributes used for registration and authentication are the Home Domain Name, the Public and the Private Identifier. These identifiers are explained below.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.1 Home Domain Name
|
The Home Domain Name is used to identify the home domain of the user. This is used during authentication and registration. The format of the Home Domain Name is based on the Domain Name e.g. 'operator.com' as specified in RFC 1035 [2]. Note that there is no requirement for having the domain part of the private and public identifier being equal to this Domain Name since the two values are independent, but some operators may choose to link these two identifiers. The Home Network Domain Name is the parameter which is used to route the initial SIP registration requests to the home operator's IMS network. The Home Network Domain Name is stored in the ISIM. Upon receipt of the register information flow, the P-CSCF examines the Home Network Domain Name to discover the entry point to the home network (i.e. the I-CSCF). Note also that for the initial registration message routeing, the Domain Name resolution mechanism is made available to the user equipment at network attachment when the DHCP provides it with the domain name of a P-CSCF and the address of a Domain Name Server (DNS) that is capable of resolving that P-CSCF name: • e.g. if there is no ISIM application (i.e. when there is no IMS-specific module), the Home Domain Name must be derived from the data available "locally" to the UE.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.2 Private User Identifiers
|
Every NGN user has at least one private identifier. Private user identifiers are assigned by the home operator and are used to identify the IMS user's subscription. Its main role is to support the authentication procedure during registration/re-registration/de-registration, authorization, administration and accounting purposes at the home IMS. It is also used as the primary means of identifying the user within a dialog between network entities (e.g. UPSF or S-CSCF selection). The private user identifier is not used in SIP call routeing, but is conveyed in all registration requests. A private user identifier is "permanent" (i.e. not tied to a particular call instance/session.) and stored locally in the ISIM (IM Services Identity Module) that will be used to instantiate the registration message parameters. In some cases, the private user identifier may also be instantiated with default values when no ISIM is available. For its syntax, the private user identifier shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of RFC 4282 [18] in accordance with TS 123 003 [6] and TS 123 228 [7]. In case there is no ISIM on the UICC, the private user ID is derived from the IMSI. The username is replaced with the complete IMSI value. However for the realm the Home Domain Name value is used. Further, there is no functional requirement for mandating a single private ID structure for a given IMS network. In IMS, the Home Domain Name, which is part of the private identifier, is used to route from a P-CSCF to the home operator's I-CSCF.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.3 Public User Identifiers
|
Every IMS user has one or more public identifiers, which are primarily used for user-to-user communication. The public identifier serves as a basis for message routeing, possibly after a translation mechanism when appropriate, both for IMS session-based SIP messages (e.g. INVITE) or off-session SIP messages (e.g. NOTIFY). There is at least one public identifier stored in the ISIM, but like the private identifier, in some cases, it may also be instantiated with default values when no such ISIM is available. Note also that public identifiers are not authenticated during registration, but the correspondence between private identifier and public identifier can be checked by the UPSF. For its syntax, the public identifier shall take the form of either a SIP URI or a tel URI. A SIP URI shall take the form "sip:user@domain" (TS 23.003 or TS 23.228). Note that tel URIs public user identifiers (whether they are based on E.164 (i.e. public) or private number) can not be used for SIP call routeing in IMS and must be translated in SIP URI using ENUM. Every IM CN subsystem user must have one or more public identifier(s). This identifier is used between users who wish to communicate with each other. Hence this identifier may be found on such items such as business card, web sites etc. It is the equivalent to how a web site or number is used today. However it should be noted that the number is not used to authenticate the user during registration. Neither is it used to identify the user's information within the UPSF. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 16 A public user ID, e.g. stored on the ISIM, is needed by NGN to access ordinary services like e.g. E-mail, Instant messages. Access to e.g. emergency services may be possible without having a public user ID. The IMS Public User ID (IMPU) is in the format of a SIP URI. However both Internet naming and telephone numbering is supported, so technically the format is either a SIP URI, or a tel URI. At least one IMPU is stored on the ISIM and cannot be modified by the UE. However, additional IMPUs do not have to be stored on the ISIM, although it is recommended. The IMPU can be registered either explicitly or implicitly, but must be registered before the identifier can be used to originate IMS sessions and IMS session unrelated procedures. The identifier also has to be registered, either explicitly or implicitly, before terminating IMS sessions. If a UICC is used that does not contain an ISIM then a temporary IMPU can be derived from the USIM's IMSI and used for the initial SIP registration process only. The temporary IMPU takes the format of a SIP URI. The format is as follows: SIP:<private user identifier>; where <private user identifier> is derived as described in clause 6.2.1.2. NOTE: The ISIM does not need to reside on a UICC for ETSI NGN purposes. The UPSF provides a public user ID to the user which will be used in the subsequent messages in the 'FROM' field of the SIP INVITE message. As a consequence, the temporary IMPU will never be displayed at the called party's UE.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.4 Relationship of Private and Public IDs
|
An important starting point is to consider the main IDs used by 3GPP IMS and their relationships in the key IMS databases. These issues are considered in clause 4.3.3.4 of TS 123 228 [7] as endorsed by TISPAN in TS 182 006 [19], where object diagrams illustrate some of the required relationships. For ease of reference the figures 4.5 and 4.6 of TS 123 228 [7] are reproduced below. IMS Subscription Private User Identity Public User Identity Public User Identity Public User Identity Service Profile Service Profile Figure 4: Relationship between the Private User Identity and Public User Identities Public user identities may be shared across multiple Private User Identities within the same IMS subscription. Hence, a particular Public User Identity may be simultaneously registered from multiple UEs that use different Private User Identities and different contact addresses. If a Public User Identity is shared among the Private User Identities of a subscription, then it is assumed that all Private User Identities in the IMS subscription share the Public User Identity. The relationship for a shared Public User Identity with Private User Identities, and the resulting relationship with service profiles and IMS subscription, is depicted in figure 5. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 17 Private User Identity - 1 Private User Identity - 2 Public User Identity - 1 Public User Identity - 2 Public User Identity - 3 Service Profile - 1 Service Profile - 2 IMS Subscription Figure 5: The relation between a shared Public User Identity (Public-ID-2) and Private User Identities In particular, clause 4.3.3.4 of TS 123 228 [7] identifies that the combination of the Private ID and the Public ID is used to register the users" details to their allocated S-CSCF from their HSS User Profile. As well as the Public ID used for registration, more Public IDs can be registered and stored in the S-CSCF during this process. Each Public ID is associated with one and only one Service Profile (from clause 4.3.3.4 in TS 123 228 [7]), though a Service Profile can be associated with many public IDs. Another valuable, though different description of the object relationships is provided for when user data structures are passed from the HSS to the S-CSCF. These are described in the UML in TS 129 228 [8]. These descriptions are not necessarily incompatible, since the data structures passed from the HSS to the S-CSCF are a description of the IDs required for session/call processing, not of the full underlying structure of the database. These 3GPP descriptions are not necessarily incompatible, since the data structures passed from the HSS to the S-CSCF are a description of the IDs required for session/call processing, not of the full underlying structure of the database. The implication of the UML in TS 129 228 [8] is that at any one time, only one private ID represents the user for session/call processing. In 3GPP the private ID could only be used to register one single user equipment at one instance of time, whereas in NGN a multiplicity of user equipment should be allowed to use the same private ID for concurrent registration. Thus this conflicts with TISPAN requirements to use private IDs to represent different user roles or for registering from different equipment simultaneously and needs further investigation. It should be possible to change the private ID without changing the public ID allocated to a subscriber and vice versa.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.5 Handling of dialled number formats
|
The user may use E.164 numbers in local, national or international format. Whenever possible the dialling sequence must be converted into E.164 international numbering format to allow for ENUM lookup. When this is not possible the URI should specify the nature of the format of the sequence of digits that is being conveyed by the URI.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.1.6 Termination of session with the tel URI format Public User ID
|
If in a terminating session a tel URI is used, the UPSF and the SLF (in the case that more than one independently addressable UPSF is utilized by a network operator) shall support the tel URI format Public User Identifier.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.2 Access IDs in the NGN
|
The Access up to the User Entity is identified using: • Identifier for the Access Network. • Identifier for the Termination Point of the Physical Transport on the Access Network (e.g. Access Link). • Identifier(s)for the Logical Channel (possibly recursive). • Identifier(s) for the User Entities (UE) using the same Logical Channel. Figure 6 shows a simplified view of the above. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 18 Figure 6: Relation between Access Link, Logical Channel, User Equipment In later TISPAN Releases the above nested structure of identifiers needs to be supported. In TISPAN Release 1 Access network level registration involves the access authentication which is authentication and authorization procedures between the UE and the NASS to control the access to the access network. Two authentication types are considered for access networks: implicit authentication and explicit authentication. • Explicit authentication is an authentication procedure that is explicitly conducted between the UE and the NASS. It requires a signalling procedure to be performed between the UE and the NASS. • Implicit authentication does not require the NASS to explicitly conduct an authentication procedure directly with the UE, however the NASS performs the implicit authentication based on identification of the L2 connection the UE is connected to. It is a matter of operator policy whether implicit authentication or explicit authentication is applied. There shall be mutual authentication between the UE and the NASS [14] during access network level registration. Both implicit authentication and explicit authentication may be used independently as network level access authentication mechanism, notwithstanding the fact that implicit authentication may be a consequence of explicit authentication (e.g. the implicit line authentication used together with an explicit method such as Point-to-Point Protocol (PPP) RFC 1661 (see bibliography) in xDSL access). Authentication between users/subscribers and application/service providers shall be explicit or implicit (based on trust/security assertions). Through the Network Attachment Subsystem it is possible to: • Provide registration at access level and initialization of User Equipment (UE) for accessing to the TISPAN NGN services. • Provide dynamic provisioning of IP address and other user equipment configuration parameters (e.g. using DHCP). • Authenticate the user, prior or during the IP address allocation procedure. • Authorize of network access, based on user profile. • Access network configuration, based on user profile. • Location management. The Network Access Configuration Function (NACF) is responsible for the IP address allocation to the UE. It may also distribute other network configuration parameters such as address of DNS server(s), address of signalling proxies for specific protocols (e.g. address of the P-CSCF when accessing to the IMS). The NACF should be able to provide to the UE an access network identifier. This information uniquely identifies the access network to which the UE is attached. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 19 The Connectivity Session Location and Repository Function (CLF) registers the association between the IP address allocated to the UE and related network location information provided by the NACF, i.e.: access transport equipment characteristics, line identifier (Logical Access ID), IP Edge identity, etc. The CLF interfaces with the NACF to get the association between the IP address allocated by the NACF to the end user equipment and the Line ID. The CLF responds to location queries from service control subsystems and applications. The actual information delivered by the CLF may take various forms (e.g. network location, geographical coordinates, post mail address, etc.), depending on agreements with the requestor and on user preferences regarding the privacy of its location. The CLF holds a number of records representing active sessions. The definition of this format shall also be lined up with OCG EMTEL who has decided that the LIF (Location Information Forum) is required in certain environments according to regulatory requirements. Correct operation of a 3GPP IMS based network requires a number of different identifiers to be present in the IMS. The key identifiers, together with the role they fulfil in NGNs and how they come to be present in the system, are shown in table 2. Table 2: Overview showing the role of different identifiers and associated handling Identifier Role within 3GPP Method of provisioning 3GPP Method of provision for fixed line access IP address Used to support media and signalling stream Downloaded into terminal from DHCP in access network and uploaded to S-CSCF as part of registration process Associated with line card as part of service provision process Private identifier To identify terminal to system as part of registration / authentication process. Also used for billing Held in ISIM explicitly or derived from USIM, then loaded into S-CSCF via registration process. 'Pseudo IMSI' provided and held in UPSF as part of service provision process Public identifier Used to identify required terminal on incoming calls. Also used as CLI on outgoing calls Programmed into ISIM and loaded into HSS as part of service provision process. Programmed into UPSF as part of service provision process.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.3 Identification of Network Nodes
|
The CSCF, BGCF and MGCF nodes (functionalities I-BCF and IBGF) shall be identifiable using a valid SIP URI (Host Domain Name or Network Address) on those interfaces supporting the SIP protocol, (e.g. Gm, Mw, Mm, and Mg). These SIP URIs would be used when identifying these nodes in header fields of SIP messages. The names should be allocated in the public DNS system, however, this does not require that the nodes be reachable from the global Internet. These URIs will not be resolvable via the public DNS, they will only resolve from within the operators' network. Globally unique identifiers for certain network elements (e.g. x-CSCFs) will be required so that a shared interconnect model, e.g. a GRX/IPX type interconnect model can be supported. Element identifier can be left to the choice of the service provider since the operator identifier and root domain uniquely identify the service provider. However the element name should be compliant with RFC 1093 [13] and it is possible that further constraints, yet to be identified, may be required.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.4 IDs for Services
|
Public Service Identifiers shall take the form as defined in TS 123 003 [6]. All public service identifiers need to meet the specific requirements of services such as: • Voice. • Instant Messaging Service. • Presence Service. • Location Service. The public service identifier shall take the form of either a SIP URI (see RFC 3261 [11]) or a tel URI (see RFC 3966 [3]). ETSI ETSI TS 184 002 V1.1.1 (2006-10) 20 A public service identifier defines a service, or a specific resource created for a service. The domain part is pre-defined by the NGN operators and the IMS system provides the flexibility to dynamically create the user part of the PSIs. The SIP URI shall take the form of a distinct PSI "SIP:service@domain", where 'service' identifies a service. EXAMPLE: sip:conference@examplenetwork.com. Generally for SIP URIs three different contexts have to be differentiated: • international E.164 number; • private number which must include a context; • short codes.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.2.5 IDs for NGN operators
|
Proposals have been made for a naming scheme for NGN network elements. This takes the format <element id>.<service provider>.<root domain>. The nature of the root domain needs further consideration in the light of recent initiatives outside ETSI (e.g. GSMA). However there is general agreement that this needs to be allocated from within the public DNS name space. A name per operator/service provider will need to allocated, and this must be unique within the root domain if misrouteing is to be avoided. To ensure that uniqueness is achieved, the entity responsible for governance of the route domain will need to be responsible for allocation of SP identifiers. A user friendly name for the root domain is favourable. Additional requirements may occur in the situation, where same services are supplied to the user from different service providers. In such circumstances separate public service provider identifiers would be required and must be supported by the NGN.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.3 ID translation in NGN
|
Identifiers are used throughout the network to identify sources/destinations of traffic and also resources within the network. One special kind of identifier is an E.164 number that is used by PSTN users to identify the destination of a call. In the context of an NGN, E.164 numbers need to be translated into an identifier format usable within the NGN.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.3.1 E.164 to SIP URI translation for routeing (ENUM)
|
There is currently no decision that the public DNS/ENUM as specified in RFC 3761 [12] be used. This topic is for further study. In some cases when the subscriber provided an E.164 number only, 3GPP foresees an E.164 to SIP URI translation especially if the requested E.164 number is not under control of the IMS (e.g. in the case of Interconnection). Case 1: derived according to TS 123 228 [7] In the case where the Request-URI of the incoming INVITE request to S-CSCF contains a tel URI [3], it has to be translated to a globally routable SIP-URI before applying it as Request-URI of the outgoing INVITE request. For this address translation the S-CSCF uses the services of an ENUM-DNS protocol based on to RFC 3761 [12]. Database aspects of ENUM are outside the scope of this specification. Case 2: derived according to TS 122 228 [1] The S-CSCF shall support the ability to translate the E.164 number contained in a Request-URI in the non-SIP URI Tel: URI format RFC 3966 [3] to a SIP routable SIP URI using an ENUM DNS translation mechanism based on RFC 3761 [12]. If this translation fails, then the session may be routed to the PSTN or appropriate notification shall be sent to the mobile, depending on network operator configuration. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 21 Case 3: derived according to TS 123 228 [7] An Application Service (AS) is hosting Public Service IDs (PSI) and may originate requests with the PSI as the originating party. For such originating requests, the home IMS network shall be capable to perform the following function: - If the target identifier is a tel URI, ENUM translation needs to be performed, and the request shall be routed based on the translation result. Routeing from the Originating AS hosting the PSI can be performed as follows: a) The AS may forward the originating request to the destination network without involving an S-CSCF. If this option is applied where the target identifier is a tel URI, the AS shall perform an ENUM query and route the request based on the translation result. ENUM support for an AS is optional, therefore, if an AS does not support ENUM and the target identifier is a tel URI, it shall be configured to use b). b) If the PSI has an S-CSCF assigned, the AS forwards the originating request to this S-CSCF, which then processes the request as per regular originating S-CSCF procedures (including a possible DNS/ENUM query).
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
6.3.2 Accessibility of ID Translation
|
TISPAN NGN supports the E.164 number translation based on RFC 3966 [3] for routeing. 3GPP tackles the critical issue of how tel URIs should be used for IMPUs. In particular, for routeing, tel URIs are translated into SIP URIs. This highlights the importance of the location of such an Infrastructure ENUM DNS translation mechanism. This translation mechanism can be located in: 1) Publicly accessible DNS; or 2) Private DNS. In the first case this is based on RFC 3966 [3]. In the second case this routeing data tree will only be accessible by a single or a group of cooperating operators and needs only to be agreed between the participating operators.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
7 Administration of NGN IDs
|
Identifiers fall into 3 classes (not mutually exclusive): • Those generated automatically by network elements (e.g. call identifiers). For these, no human intervention is required (or possible). • Those that may be allocated by operators without reference to external bodies (e.g. customer account number). • Those for which operators must go to external bodies (e.g. NRA and others) to receive allocations (e.g. E.164 numbers, public IP addresses). Framework Directive, Article 10.1 (see bibliography) requires that National regulatory authorities control the assignment of all national numbering resources and the management of the national numbering plans. Adequate numbers and numbering ranges shall be provided for all publicly available electronic communications services. Framework Directive, Article 10.1 (see bibliography) also requires that National regulatory authorities establish objective, transparent and non-discriminatory assigning procedures for national numbering resources.
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
7.1 Overview on administration
| |
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
7.1.1 E.164 Numbers
|
According to the WTSA, ITU-T Study Group 2 ('SG2') is the lead ITU-T Study Group with regard to the Administration of International Numbering Resources. SG2's responsibilities, under this mandate, include overseeing the administration of all such resources in order to ensure uniformity and equity in their assignment, despite the technical responsibilities for these resources being dispersed across multiple ITU-T Study Groups. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 22 Specifically, ITU-T Recommendation E.164 [10], defines the number structure and functionality for four principal categories of numbers used for international public telecommunication – namely geographic areas, Global Services, Networks, and Groups of Countries ('GoCs'). For each of the categories, Recommendation E.164 details the components of the numbering structure and the digit analysis required to successfully route calls. Other specific Recommendation E.164-based global service applications (e.g. Universal International Freephone Numbers), which differ in usage, are defined in separate ITU-T Recommendations related to E.164, include, inter alia: • ITU-T Recommendation E.164.1 [20]: "Criteria and procedures for the reservation, assignment and reclamation of E.164 country codes and associated Identification Codes (ICs)"; • ITU-T Recommendation E.164.2 [21]: "E.164 numbering resources for trials"; • Determined ITU-T Recommendation E.164.3 [22]: "Principles, criteria and procedures for the assignment and reclamation of E.164 country codes and associated identification codes for Groups of Countries"; • ITU-T Recommendation E.190 [23]: "Principles and responsibilities for the management, assignment and reclamation of E-series international numbering resources"; • ITU-T Recommendation E.195 [24]: "ITU-T International numbering resource administration".
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
7.1.2 IP Addresses
|
Currently there are two types of Internet Protocol (IP) addresses in active use: IP version 4 (IPv4) and IP version 6 (IPv6). IPv4 was initially deployed on 1 January 1983 and is still the most commonly used version. IPv4 addresses are 32-bit numbers often expressed as 4 octets in "dotted decimal" notation (for example, 192.0.32.67). Deployment of the IPv6 protocol began in 1999. IPv6 addresses are 128-bit numbers and are conventionally expressed using hexadecimal strings (for example, 1080:0:0:0:8:800:200C:417A). Both IPv4 and IPv6 addresses are assigned in a delegated manner. Users are assigned IP addresses by Internet service providers (ISPs). ISPs obtain allocations of IP addresses from a local Internet registry (LIR) or national Internet registry (NIR), or from their appropriate Regional Internet Registry (RIR): • AfriNIC (African Network Information Centre) - Africa Region • APNIC (Asia Pacific Network Information Centre) - Asia/Pacific Region • ARIN (American Registry for Internet Numbers) - North America Region • LACNIC (Regional Latin-American and Caribbean IP Address Registry) - Latin America and some Caribbean Islands • RIPE NCC (Réseaux IP Européens) - Europe, the Middle East, and Central Asia The IANA's role is to allocate IP addresses from the pools of unallocated addresses to the RIRs according to their established needs. When an RIR requires more IP addresses for allocation or assignment within its region, the IANA makes an additional allocation to the RIR. Important links: • IPv4 Address Space (http://www.iana.org/assignments/ipv4-address-space) • IPv6 Address Allocation and Assignment Policy (http://www.iana.org/ipaddress/ipv6-allocation-policy-26jun02) • IPv6 Address Space (http://www.iana.org/assignments/ipv6-address-space) ETSI ETSI TS 184 002 V1.1.1 (2006-10) 23
|
eba5ee3fb4bd4ab7bb24d70d351c8271
|
184 002
|
7.1.3 Domain Names
|
The Domain Name System (DNS) helps users to find their way around the Internet. Every computer on the Internet has a unique address - just like a telephone number - which is a rather complicated string of numbers: the IP address. However IP addresses are hard to remember. The DNS makes using the Internet easier by allowing a familiar string of letters (the "Domain Name") to be used instead of the arcane IP address. The Internet Corporation for Assigned Names and Numbers (ICANN - www.icann.org) is an internationally organized, non-profit corporation that has responsibility for gTLD and ccTLD name system management. The responsibility for operating each TLD (including maintaining a registry of the Domain Names within the TLD) is delegated by ICANN to a particular organization. These organizations are referred to as 'registry operators'. Currently, the gTLD of .aero, .biz, .com, .coop, .info, .museum, .name, .net, .org and .pro are in use, and the corresponding registries are under contract with ICANN. Separate arrangements apply to .edu, .mil, .gov, under United States Government responsibility, and .int which is directly under ICANN's responsibility. Domain Names can be registered through many companies known as "registrars". The registrar collects various contact and technical information that makes up the user's registration. The registrar keeps then records of the contact information and submit the technical information to the registry operator. The latter provides other computers on the Internet the information necessary to resolve the Domain Name in the correct IP address. SIP addresses used as public user ID in NGN are based on Domain Names. A SIP address (or a SIP URI) is a type of Uniform Resource Identifier that identifies a communication resource in SIP. A SIP URI usually contains a user name and a host name and is similar in format to an email address (example: user@domain.foo). 7.1.4 International Mobile Subscriber Identity - IMSI (ITU-T Recommendation E.212) The IMSI is a string of decimal digits, up to a maximum of 15 digits, that identifies a unique mobile terminal or mobile subscriber internationally. IMSIs may also be used for terminal or subscriber identification within fixed or wireline networks that offer mobility services, or to achieve compatibility with networks that have mobility services. The IMSI consists of three fields: the MCC, the MNC, and the MSIN. The IMSI conforms to the ITU-T Recommendation for E.212 numbering. MCCs are assigned by the ITU in response to formal requests from national administrators of ITU Member States. Additional MCCs will be assigned only in anticipation of exhaust of assigned code(s). MNCs are administered by the designated administrator within each country or by the TSB in the case of shared MCCs. Additional MNCs are assigned to MNC assignees within a shared MCC only for exhaust of the assigned code(s). MSINs are administered by the MNC assignee. In principle, only one IMSI shall be assigned to each mobile terminal or mobile user. In case of multiple subscriptions (subscriptions to more than one mobility service from one or more service providers), a mobile terminal or mobile user may be assigned a different IMSI for each subscription. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 24 Annex A (normative): 3GPP and TISPAN IDs A.1 Identifiers already defined in 3GPP Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements 2 Identification of mobile subscribers IMSI 2.2 A unique International Mobile Subscriber Identity (IMSI) shall be allocated to each mobile subscriber in the GSM/UMTS system. Not used within NASS TMSI 2.4 In order to support the subscriber identity confidentiality service the VLRs and SGSNs may allocate Temporary Mobile Subscriber Identities (TMSI) to visiting mobile subscribers. The VLR and SGSNs must be capable of correlating an allocated TMSI with the IMSI of the MS to which it is allocated. Not used within NASS P-TMSI 2.1 Packet TMSI An MS may be allocated two TMSIs, one for services provided through the MSC, and the other for services provided through the SGSN (P-TMSI for short). Not used within NASS TLLI 2.6 For addressing on resources used for GPRS, a Temporary Logical Link Identity (TLLI) is used. The TLLI to use is built by the MS either on the basis of the P-TMSI (local or foreign TLLI), or directly (random TLLI). Access network type specific (ID specific to 3GPP networks) LMSI 2.5 In order to speed up the search for subscriber data in the VLR a supplementary Local Mobile Station Identity (LMSI) is defined. The LMSI may be allocated by the VLR at location updating and is sent to the HLR together with the IMSI. The HLR makes no use of it but includes it together with the IMSI in all messages sent to the VLR concerning that MS. Access network type specific (ID specific to 3GPP networks) NRI 2.4 Network Resource Identifier If intra domain connection of RAN nodes to multiple CN nodes as described in 3GPP TS 23.236 is applied in the MSC/VLR or SGSN, then the NRI shall be part of the TMSI. The NRI has a configurable length of 0 to 10 bits. A configurable length of 0 bits indicates that the NRI is not used and this feature is not applied in the MSC/VLR or SGSN. The NRI shall be coded in bits 23 to 14. An NRI shorter than 10 bits shall be encoded with the most significant bit of the NRI field in bit 23. Access network type specific (ID specific to 3GPP networks) 3 Numbering plan for mobile stations MSISDN 3.3 Mobile station international PSTN/ISDN number (E.164) The number consists of: - Country Code (CC) of the country in which the MS is registered, followed by: - National (significant) mobile number, which consists of: - National Destination Code (NDC); and - Subscriber Number (SN). A number of this format (i.e. an E.164 number) is required for NGNs, however, the term MSISDN is 3GPP specific MSRN 3.4 Mobile station roaming number for PSTN/ISDN routeing (E.164) The Mobile Station Roaming Number for PLMN/ISDN routing shall have the same structure as MSISDN numbers in the area in which the roaming number is allocated. Needed only in a circuit switched environment 3.5 Mobile station international data number The structure of MS international data numbers should comply with the data numbering plan of ITU-T Recommendation X.121 as applied in the home country of the mobile subscriber. Not needed, as all services can be provided using the same number 3.6 Handover number The structure of the handover number is the same as the structure of the MSRN. Handover implies "session continuity" which is for further study (ffs) in TISPAN ETSI ETSI TS 184 002 V1.1.1 (2006-10) 25 Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements 4 Identification of location areas and base stations LAI 4.1 Location Area Identity The LAI is composed of the following elements: - Mobile Country Code (MCC) identifies the country in which the GSM PLMN is located. The value of the MCC is the same as the three digit MCC contained in international mobile subscriber identity (IMSI); - Mobile Network Code (MNC) is a code identifying the GSM PLMN in that country. The MNC takes the same value as the two or three digit MNC contained in IMSI; - Location Area Code (LAC) is a fixed length code (of 2 octets) identifying a location area within a PLMN. This part of the location area identification can be coded using a full hexadecimal representation except for the following reserved hexadecimal values: - 0000, and - FFFE. These reserved values are used in some special cases when no valid LAI exists in the MS (see 3GPP TS 24.008 , 3GPP TS 31.102 and 3GPP TS 51.011 ). Access network type specific (ID specific to 3GPP networks). RAI 4.2 Routing Area Identity The RAI is composed of the following elements: - A valid Location Area Identity (LAI) as defined in clause 4.1. Invalid LAI values are used in some special cases when no valid RAI exists in the mobile station (see 3GPP TS 24.008 , 3GPP TS 31.102 and 3GPP TS 51.011). - Routeing Area Code (RAC) which is a fixed length code (of 1 octet) identifying a routeing area within a location area. Access network type specific (ID specific to 3GPP networks) CI 4.3.1 The BSS and cell within the BSS are identified within a location area or routeing area by adding a Cell Identity (CI) to the location area or routeing area identification, as shown in figure 5. The CI is of fixed length with 2 octets and it can be coded using a full hexadecimal representation. Access network type specific (ID specific to 3GPP networks) CGI 4.3.1 The Cell Global Identification is the concatenation of the Location Area Identification and the Cell Identity. Cell Identity shall be unique within a location area. Access network type specific (ID specific to 3GPP networks) BSIC 4.3.2 The Base Station Identity Code is a local colour code that allows an MS to distinguish between different neighbouring base stations. BSIC is a 6 bit code which is structured as shown in figure 6. Access network type specific (ID specific to 3GPP networks) RSZI 4.4 A PLMN-specific regional subscription defines unambiguously for the entire PLMN the regions in which roaming is allowed. It consists of one or more regional subscription zones. The regional subscription zone is identified by a Regional Subscription Zone Identity (RSZI). A regional subscription zone identity is composed as shown in figure 7. Access network type specific (ID specific to 3GPP networks) 5 Identification of MSCs, GSNs and location registers GSN address 5.1 GSN: GPRS Support Node address SGSN: Serving GPRS Support Node GGSN: Gateway GPRS Support Node MSCs, GSNs and location registers are identified by international PSTN/ISDN numbers and/or Signalling Point Codes ("entity number", i.e., "HLR number", "VLR number", "MSC number", "SGSN number" and "GGSN number") in each PLMN. Additionally SGSNs and GGSNs are identified by GSN Addresses. These are the SGSN Address and the GGSN Address. Access network type specific (ID specific to 3GPP networks) (similar functionalities required in TISPAN to identify the access to the NGN) HLR ID 5.2 Home Location Register HLR may also be identified by one or several "HLR id(s)", consisting of the leading digits of the IMSI (MCC + MNC + leading digits of MSIN). Not needed in TISPAN Release 1 ffs for later releases ETSI ETSI TS 184 002 V1.1.1 (2006-10) 26 Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements 6 International Mobile Station Equipment Identity and Software Version Number IMEI 6.2.1 International Mobile Equipment Identity The IMEI is composed of the following elements (each element shall consist of decimal digits only): - Type Allocation Code (TAC). Its length is 8 digits; - Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its length is 6 digits; - Spare digit: this digit shall be zero, when transmitted by the MS. Fixed network terminals need not to contain that ID ffs in later releases IMEISV 6.2.2 International Mobile Equipment Identity and Software Version Number The IMEISV is composed of the following elements (each element shall consist of decimal digits only): - Type Allocation Code (TAC). Its length is 8 digits; - Serial Number (SNR) is an individual serial number uniquely identifying each equipment within the TAC. Its length is 6 digits; - Software VErsion Number (SRV) identifies the software version number of the mobile equipment. Its length is 2 digits. Fixed network terminals need not to contain that ID ffs in later releases 7 Identification of Voice Group Call and Voice Broadcast Call Entities VGCS Group ID VBS Group ID 7.3 Logical groups of subscribers to the Voice Group Call Service or to the Voice Broadcast Service are identified by a Group Identity (Group ID). Group IDs for VGCS are unique within a PLMN. Likewise, Group IDs for VBS are unique within a PLMN. However, no uniqueness is required between the sets of Group IDs. These sets may be intersecting or even identical, at the option of the network operator. Access network type specific (ID specific to 3GPP networks) Group Call Area Identity 7.3 Grouping of cells into specific group call areas occurs in support of both the Voice Group Call Service and the Voice Broadcast Service. These service areas are known by a "Group Call Area Identity" (Group Call Area Id). No restrictions are placed on what cells may be grouped into a given group call area. Access network type specific (ID specific to 3GPP networks) 9 Definition of Access Point Name APN Network Identifier 9.1 Access Point Name The APN Network Identifier; this defines to which external network the GGSN is connected and optionally a requested service by the MS. This part of the APN is mandatory. Not needed in TISPAN Release 1 ffs in later releases APN Operator Identifier 9.1.2 The APN Operator Identifier; this defines in which PLMN GPRS backbone the GGSN is located. This part of the APN is optional. Not needed in TISPAN Release 1 ffs in later releases 10 Identification of Cordless Telephony System Entities FPBI 10.3 Every CTS-FP broadcasts a local identity - the Fixed Part Beacon Identity (FPBI) - which contains an Access Rights Identity. Every CTS-MS has both an Access Rights Key and a CTS Mobile Subscriber Identity (CTSMSI). These operate as a pair. A CTS-MS is allowed to access any CTS-FP which broadcasts an FPBI which can be identified by any of the CTS-MS Access Rights Keys of that CTS-MS. The CTS-MS Access Rights Key contains the FPBI and the FPBI Length Indicator (FLI) indicating the relevant part of the FPBI used to control access. Access network type specific (ID specific to Cordless Telephony Systems) CTSMSI 10.2 Each CTS-MS has one or more temporary identities which are used for paging and to request access. The structure and allocation principles of the CTS Mobile Subscriber Identities (CTSMSI) are defined below. Access network type specific (ID specific to Cordless Telephony Systems) ETSI ETSI TS 184 002 V1.1.1 (2006-10) 27 Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements IFPEI 10.4 The International Fixed Part Equipment Identity (IFPEI) is composed of the following elements (each element shall consist of decimal digits only): - Type Approval Code (TAC). Its length is 6 decimal digits; - Final Assembly Code (FAC). Its length is 2 decimal digits; - Serial NumbeR (SNR). Its length is 6 decimal digits; - Software Version Number (SVN) identifies the software version number of the fixed part equipment. Its length is 2 digits. Access network type specific (ID specific to Cordless Telephony Systems) IFPSI 10.5 The International Fixed Part Subscriber Identity (IFPSI) is composed of the following elements (each element shall consist of decimal digits only): - Mobile Country Code (MCC) consisting of three digits. The MCC identifies the country of the CTS-FP subscriber (e.g. 208 for France); - CTS Operator Number (CON). Its length is three digits; - Fixed Part Identification Number (FPIN) identifying the CTS-FP subscriber.. Access network type specific (ID specific to Cordless Telephony Systems) NFPSI 10.5 The National Fixed Part Subscriber Identity (NFPSI) consists of the CTS Operator Number and the Fixed Part Identification Number. Access network type specific (ID specific to Cordless Telephony Systems) 11 Identification of Localised Service Area LSAID 11 Cells may be grouped into specific localised service areas. Each localised service area is identified by a Localised Service Area IDentity (LSA ID). No restrictions are placed on what cells may be grouped into a given localised service area. The LSA ID can either be a PLMN significant number or a universal identity. This shall be known both in the networks and in the SIM. Access network type specific (ID specific to 3GPP networks) 12 Identification of PLMN, RNC, Service Area, CN domain and shared network Area PLMN-ID 12.1 A PLMN is uniquely identified by its Public Land Mobile Network Identifier. PLMN-Id consists of Mobile Country Code (MCC) and Mobile Network Code (MNC). PLMN-Id = MCC || MNC Operator network type specific CN Domain ID 12.2 Core Network Domain Identity A CN Domain Edge Node is identified within the UTRAN by its CN Domain Identifier. The CN Domain identifier is used over UTRAN interfaces to identify a particular CN Domain Edge Node for relocation purposes. The CN Domain identifier for Circuit Switching (CS) consists of the PLMN-Id and the LAC, whereas for Packet Switching (PS) it consists of the PLMN-Id, the LAC, and the RAC of the first accessed cell in the target RNS. The two following CN Domain Identifiers are defined: - CN CS Domain-Id = PLMN-Id || LAC - CN PS Domain-Id = PLMN-Id || LAC || RAC Access network type specific (ID specific to 3GPP networks) CN ID 12.3 Core Network Identity A CN node is uniquely identified within a PLMN by its CN Identifier (CN-Id). The CN-Id together with the PLMN identifier globally identifies the CN node. The CN-Id together with the PLMN-Id is used as the CN node identifier in RANAP signalling over the Iu interface. Global CN-Id = PLMN-Id || CN-Id The CN-Id is defined by the operator, and set in the nodes via O&M. Access network type specific (ID specific to 3GPP networks) ETSI ETSI TS 184 002 V1.1.1 (2006-10) 28 Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements RNC-Id 12.4 Radio Network Controller Identity An RNC node is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of an RNC is used in the UTRAN, in a GERAN which is operating in GERAN Iu mode and between them. A BSC which is part of a GERAN operating in Iu mode is uniquely identified by its RNC Identifier (RNC-Id). The RNC-Id of a BSC is used in a GERAN which is operating in GERAN Iu mode, in the UTRAN and between them. RNC-Id together with the PLMN identifier globally identifies the RNC. The RNC-Id on its own or the RNC-Id together with the PLMN-Id is used as the RNC identifier in the UTRAN Iub, Iur and Iu interfaces. The SRNC-Id is the RNC-Id of the SRNC. The C-RNC-Id is the RNC-Id of the controlling RNC. The D-RNC-Id is the RNC Id of the drift RNC. Global RNC-Id = PLMN-Id || RNC-Id The RNC-Id is defined by the operator, and set in the RNC via O&M. Access network type specific (ID specific to 3GPP networks) SAI 12.5 The Service Area Identifier (SAI) is used to identify an area consisting of one or more cells belonging to the same Location Area. Such an area is called a Service Area and can be used for indicating the location of a UE to the CN. The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier. - SAI = PLMN-Id || LAC || SAC The SAC is defined by the operator, and set in the RNC via O&M. Access network type specific (ID specific to 3GPP networks) SNA-Id 12.6 The Shared Network Area Identifier (SNA-Id) is used to identify an area consisting of one or more Location Areas. Such an area is called a Shared Network Area and can be used to grant access rights to parts of a Shared Network to a UE in connected mode (see 3GPP TS 25.401 ). The Shared Network Area Identifier consists of the PLMN-Id followed by the Shared Network Area Code (SNAC). - SNA-Id = PLMN-Id || SNAC The SNAC is defined by the operator. Access network type specific (ID specific to 3GPP networks) 13 Numbering, addressing and identification within the IP multimedia core network subsystem Private User ID 13.3 The private user identity shall take the form of an NAI, and shall have the form username@realm as specified in clause 2.1 of RFC 4282 Public User ID 13.4 The Public User Identity shall take the form of either a SIP URI (see RFC 3261 or a tel URL (see RFC 3966 ). A SIP URI for a Public User Identity shall take the form "sip:user@domain". SIP URI comparisions shall be performed as defined in RFC 3261 , section 19.1.4. PSI 13.5 The Public Service Identity (PSI) shall take the form of either a SIP URI (see RFC 3261 ) or a tel URL (see RFC 3966 ). A public service identity defines a service, or a specific resource created for a service. 14 Numbering, addressing and identification needed to access the 3GPP system supporting the WLAN interworking Home network realm 14.2 The home network realm shall be in the form of an Domain Name as specified in RFC1035 Root NAI 14.3 The Root NAI shall take the form of a NAI, and shall have the form 'username@realm' as specified in clause 2,1 of RFC 4282. Decorated NAI 14.4 The Decorated NAI shall take the form of a NAI, and shall have the form 'homerealm!username@otherrealm as specified in clause 2.73 of RFC 4282. Temporary Ids 14.5 The Temporary Identities (Pseudonyms and re-authentication identities) shall take the form of a Network Access Identifier (NAI) username as specified in clause 2,1 of the RFC 4282 Alternative NAI 14.6 The Alternative NAI shall take the form of a NAI, i.e. 'any_username@REALM' as specified in RFC 4282. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 29 Identifier name Clause in [6] Definition in TS 123 003 [6] TISPAN statements W-APN Network Identifier 14.7.1 A W-APN Network Identifier may be used to access a service associated with a PDG. This may be achieved by defining: - a W-APN Network Identifier consisting of 3 or more labels and starting with a Reserved Service Label, or a W-APN Network Identifier consisting of a Reserved Service Label alone, which indicates a PDG by the nature of the requested service. Reserved Service Labels and the corresponding services they stand for shall be agreed between operators who have WLAN roaming agreements. Access network type specific (ID specific to 3GPP networks) W-APN Operator Identifier 14.7.2 The W-APN Operator Identifier is composed of four labels. The last label shall be "pub.3gppnetwork.org". The second and third labels together shall uniquely identify the PLMN. The first label distinguishes the Domain Name as a W-APN. For each operator, there is a default W-APN Operator Identifier (i.e. Domain Name). This default W-APN Operator Identifier is derived from the IMSI as follows: "w-apn.mnc<MNC>.mcc<MCC>.pub.3gppnetwork.org" Access network type specific (ID specific to 3GPP networks) 15 Identification of Multimedia Broadcast/Multicast Service TMGI 15.2 Temporary Mobile Group Identity (TMGI) is used within MBMS to uniquely identify Multicast and Broadcast bearer services.. The TMGI is composed of three parts: 1) MBMS Service ID consisting of three octets. MBMS Service ID uniquely identifies an MBMS bearer service within a PLMN. 2) Mobile Country Code (MCC) consisting of three digits. The MCC identifies uniquely the country of domicile of the BM- SC; 3) Mobile Network Code (MNC) consisting of two or three digits. The MNC identifies the PLMN which the BM-SC belongs to. The length of the MNC (two or three digits) depends on the value of the MCC. Access network type specific (ID specific to 3GPP networks) 16 Numbering, addressing and identification within the GAA subsystem BSF address 16.2 The Bootstrapping Server Function (BSF) address is in the form of a Fully Qualified Domain Name as defined in RFC 1035. The UE shall discover the BSF address from the identity information related to the UICC application that is used during the bootstrapping procedure i.e. IMSI for USIM, or IMPI for ISIM. Not defined in TISPAN Release 1 ffs in later releases 17 Numbering, addressing and identification within the Generic Access Network Home network realm 17.2.1 The home network realm shall be in the form of an Internet domain name, e.g. operator.com, as specified in RFC 1035. Full Authentication NAI 17.2.2 The Full Authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of RFC 4282. Not defined in TISPAN Release 1 ffs in later releases Fast Re- Authentication NAI 17.2.3 The Fast Re-authentication NAI in both EAP-SIM and EAP-AKA shall take the form of an NAI as specified in clause 2.1 of RFC 4282. Not defined in TISPAN Release 1 ffs in later releases Home network Domain Name 17.3.1 The home network Domain Dame shall be in the form of a Domain Name, e.g. operator.com, as specified in RFC 1035. Provisioning GANC-SEGW ID 17.3.2 The Provisioning GANC-SEGW identifier shall take the form of a Fully Qualified Domain Name as specified in RFC 1035. Access network type specific (ID specific to 3GPP networks) Provisioning GANC ID 17.3.3 The Provisioning GANC identifier shall take the form of a fully qualified domain name (FQDN) as specified in RFC 1035. Access network type specific (ID specific to 3GPP networks) ETSI ETSI TS 184 002 V1.1.1 (2006-10) 30 A.2 Additional Identifiers necessary for TISPAN NGN A.2.1 Organization of User Data This table is taken from TR 182 005 (see bibliography) for TISPAN Release 1. Parameter Clause CLF PDBF Assigned IP Address 9.1.1.1 T Address Realm 9.1.1.2 T Subscriber Id 9.1.2 T P Default Subscriber ID 9.1.3 P Physical Access ID 9.2.1 T Logical Access ID 9.2.2 T Access Network Type 9.2.3 P Terminal Type 9.2.4 T Privacy Indicator 9.3.1 T P Location Information 9.3.2 P Geographic Location Information 9.3.3 T QoS Profile Information 9.4.1 T P Initial Gate Settings 9.4.2 T RACS Point of Contact 9.5.1 P CNCGF address 9.5.2 P P-CSCF Identity 9.5.3 P AF Identity 9.5.4 T A.2.2 Network Attachment Subsystem (NASS) Additional IDs in the NASS document ES 282 004 [14] for TISPAN Release 1. No new additional IDs are contained in the NASS document. A.2.3 Resource and Admission Control Subsystem (RACS) Additional ID's in the RACS document ES 282 003 [15] for TISPAN Release 1. Parameter Clause Charging Correlation identifier 5.2.2 RACF identification 5.2.3.1.2 Application function identifier 5.2.3.1.5 Resource Bundle Identifier 5.2.3.1.6 Media Session Identifier 5.2.3.3.2 Flow Identifier 5.3.1.3.1 A.3 Summarization of Access IDs Following are some access IDs derived from NASS document ES 282 004 [14] for TISPAN Release 1. • IP Address: The IP address of the attached user equipment. • Address Realm: The addressing domain in which the IP address is significant. • Physical Access ID: The identity of the physical access to which the user equipment is connected. • Logical Access ID: The identity of the logical access used by the attached user equipment. In the xDSL case, the Logical Access ID may explicitly contain the identity of the port, VP and/or VC carrying the traffic. • Subscriber ID: The identity of the attached user. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 31 • Static Information derived from the Physical access ID: - Location Information. - Default Subscriber ID. • Static Information Derived from the Logical Access ID: - RACS point of contact: The address of the RACS element where the subscriber profile should be pushed. - Access Network Type: The type of access network over which IP connectivity is provided to the user equipment. ETSI ETSI TS 184 002 V1.1.1 (2006-10) 32 Annex B (informative): Bibliography TISPAN 04bTD036r1: "Key Issues concerning user and network IDs in NGNs and TISPAN WGs". ITU-T Recommendation E.118 (2001): "The international telecommunication charge card". ITU-T Recommendation E.191 (2000): "B-ISDN addressing". ITU-T Recommendation Q.708 (1999): "Assignment procedures for international signalling point codes". ITU-T Recommendation X.121 (2000): "International numbering plan for public data networks". ITU-T Recommendation X.25 (1996): "Interface between Data Terminal Equipment (DTE) and Data Circuit- terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit". ITU-T Recommendation X.21 (1992): "Interface between Data Terminal Equipment and Data Circuit-terminating Equipment for synchronous operation on public data". ITU-T Recommendation F.69 (1994): "The International Telex Service - Service and operational provisions of Telex Destinations Codes and Telex Network Identification Codes". Directive 2002/19/EC of the European Parliament and of the Council of 7 March 2002 on access to, and interconnection of, electronic communications networks and associated facilities (Access Directive). Directive 2002/21/EC of the European Parliament and of the Council of 7 March 2002 on a common regulatory framework for electronic communications networks and services (Framework Directive). Directive 2002/22/EC of the European Parliament and of the Council of 7 March 2002 on universal service and users' rights relating to electronic communications networks and services (Universal Service Directive). The Convention on Mutual Assistance in Criminal Matters between the Member States of the European Union established by Council Act of 29th May 2000 (2000/C197/01). IETF RFC 1661: "Point-to-Point Protocol (PPP)". ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". ETSI TR 182 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Organization of user data". ITU-T Recommendation Y.2001: "General overview of NGN". GSMA IR.65: "IMS Roaming & Interworking Guidelines". ETSI ETSI TS 184 002 V1.1.1 (2006-10) 33 History Document history V1.1.1 October 2006 Publication
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
1 Scope
|
The present document describes the stage three protocol for basic communication procedures common to several services when at least one Application Server (AS) is included in the communication. The common procedures are based on stage three specifications for services.
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
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. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
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] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 6 [12] Void. [13] Void. [14] Void. [15] Void. [16] ETSI TS 124 528: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; Common Basic Communication procedures; Protocol specification (3GPP TS 24.528 Release 8)".
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
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] Void.
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
3 Definitions and abbreviations
| |
94043ccf0a585038ec575a17b426df3b
|
183 028
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TS 124 528 [16] apply.
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in TS 124 528 [16] apply.
|
94043ccf0a585038ec575a17b426df3b
|
183 028
|
4 Common basic communication procedures
|
The provisions of the present document are contained in TS 124 528 [16]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 7 Annex A (informative): Signalling flows for announcements Information is contained in TS 124 528 [16]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 8 Annex B (informative): Signalling flows for Network Determined User Busy (NDUB) Information is contained in TS 124 528 [16]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 9 Annex C (normative): Void ETSI ETSI TS 183 028 V2.5.0 (2008-06) 10 Annex D (normative): Application Server (AS) establishing multiple dialogs with originating UE The provisions of the present document are contained in TS 124 528 [16]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 11 Annex E (informative): Signalling flows for 3rd party call control Information is contained in TS 124 528 [16]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 12 Annex F (informative): Bibliography Information is contained in TS 124 528 [17]. ETSI ETSI TS 183 028 V2.5.0 (2008-06) 13 History Document history V2.4.0 January 2008 Publication V2.5.0 June 2008 Publication
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
1 Scope
|
The present document provides the stage 3 specification of the Rq interface. The functional requirements and the stage 2 specifications of the Rq interface are contained in ES 282 001 [1] and ES 282 003 [2]. The Rq interface is the interface between the Service Policy Decision Function (SPDF) and the Access - Resource and Admission Control Function (A-RACF) and is used for QoS resource reservation information exchange between the SPDF and the A-RACF. Via the Rq interface the SPDF issues requests for resources in the access network, indicating IP QoS characteristics. The A-RACF uses the IP QoS information to perform admission control and indicate to the SPDF via the Rq interface its admission control decisions. Due to the possible business roles in an access environment, the SPDF may be either in the same domain or in a different domain as the A-RACF. The present document defines: • The information to be exchanged between SPDF and A-RACF over the Rq interface. • An Rq interface definition based on the Diameter protocol. In situations where no generic overload control mechanism is used on the Rq interface, the interface shall only be capable of supporting a one-to-one relationship between the A-RACF and SPDF (i.e. one SPDF may only contact one A-RACF, and that A-RACF may only contact that same SPDF). Overload control need not be supported in this situation due to the fact that it should be possible to traffic engineer the capabilities of the two entities, so that the capacity of one entity matches the capacity of the other.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
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.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
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 001 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI ES 282 003 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". ETSI ETSI TS 183 026 V3.1.1 (2010-03) 7 [3] ETSI ES 282 004 (V3.y.z): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub- System (NASS)". [4] 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". [5] ETSI TS 183 017 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". [6] ETSI TS 129 207: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); Policy control over Go interface (3GPP TS 29.207)". [7] ETSI TS 129 209: "Universal Mobile Telecommunications System (UMTS); Policy control over Gq interface (3GPP TS 29.209)". [8] ETSI TS 133 210: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); 3G security; Network Domain Security (NDS); IP network layer security (3GPP TS 33.210)". [9] IETF RFC 2960: "Stream Control Transmission Protocol". [10] IETF RCF 3309: "Stream Control Transmission Protocol (SCTP) Checksum Change". [11] IETF RFC 3588: "Diameter Base Protocol". [12] IETF RFC 4005: "Diameter Network Access Server Application".
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
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. Not applicable.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
3 Definitions and abbreviations
| |
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: Attribute-Value Pair (AVP): corresponds to an Information Element in a Diameter message NOTE: See RFC 3588 [11]. hard-state reservation: type of reservation whereby the requested resources are reserved without time limit NOTE: Hard-state reservations are terminated if the DIAMETER session is terminated. soft-state reservation: type of reservation whereby the requested resources are reserved for a finite amount of time, soft-state reservations are terminated when the DIAMETER session is terminated ETSI ETSI TS 183 026 V3.1.1 (2010-03) 8
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: AAA AA-Answer AAR AA-Request AF Application Function A-RACF Access-Resource and Admission Control Function ASA Abort-Session-Answer ASP Application Service Provider ASR Abort-Session-Request ATM VC Asynchronous Transfer Mode Virtual Circuit AVP Attribute-Value Pair BGF Border Gateway Function BTF Basic Transport Functions IANA Internet Assigned Numbers Authority IP Internet Protocol IP-CAN IP-Connectivity Access Network NASREQ Network Access Server REQuirements RAA Re-Auth-Answer RACF Resource and Admission Control Function RACS Resource and Admission Control Subsystem RAR Re-Auth-Request RCEF Residual Code Excited Field RTCP Real-time Transport Control Protocol RTP Real-time Transport Protocol SDI Session Description Information SPDF Service-based Policy Decision Function STA Session-Termination-Answer STR Session-Termination-Request UDP User Datagram Protocol xDSL x Digital Subscriber Line
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4 Rq interface
| |
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4.1 Overview
|
In the following clause, the Rq interface is described in detail concerning what type of information that needs to be transported between the SPDF and the A-RACF. The functional requirements and the stage 2 specifications of the Rq interface are contained in ES 282 001 [1] and ES 282 003 [2]. Due to the possible business roles in an access environment, an SPDF instance may be either in the same domain or in a different domain as the A-RACF instance with which it interacts. This means that Rq reference point should support both the case when an SPDF instance and the A- RACF instance with which it interacts are located in the same domain, and when they are located in different domains. The Rq reference point is an open vendor interface and an open operator interface. One A-RACF instance shall be able to serve more than one SPDF instance and one given SPDF instance may interact with a number of A-RACF instances, although on a session basis, it shall interact with only a single A-RACF instance. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 9
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4.2 Rq reference model
|
The Rq interface is defined between the SPDF and the A-RACF. Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd ’ , Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Rr x - RACF AF SPDF BGF RCEF NASS Re Ia Gq ’ Rd ’ , Ri ’ Rq e4 Transport Processing Functions RACS BTF Rf Figure 1: Rq interface architecture model
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4.3 Functional elements and capabilities
| |
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4.3.1 Service Policy Decision Function (SPDF)
|
The SPDF is a functional element that coordinates the resource reservations requests received from by the AF. The SPDF makes policy decisions using policy rules and forwards the session and media related information obtained from the AF to the A-RACF via the Rq reference point for admission control purposes. The functionality of the SPDF is further detailed in ES 282 003 [2].
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
4.3.2 Access-Resource Admission Control Function (A-RACF)
|
The A-RACF is a functional element performing resource reservation admission control and network policy assembly. The A-RACF receives resource reservation requests from the SPDF via the Rq reference point. The functionality of the SPDF is further detailed in ES 282 003 [2].
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5 Resource control procedures
|
The resource control procedures are defined in seven interaction procedures: 1) Reservation. 2) Commit. 3) Reservation and commit. 4) Refresh. 5) Modification. 6) Release. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 10 7) Event notification. These interactions are described in the following clauses. During the interactions Diameter AVPs are passed between the SPDF and the A-RACF. Figure 2 describes the flow states as maintained by the A-RACF F according to the procedures. Annex A provides a table further clarifying how states change at different events and actions taken by the A-RACF. Reserved Committed Received STR Reservation Idle Commit Received STR or Release Request Modification or Refresh Reservation&Commit Modification or Refresh Reserved Reserved Committed Committed Received STR Reservation Reservation Idle Idle Commit Commit Received STR or Release Request Modification or Refresh Modification or Refresh Reservation&Commit Reservation&Commit Modification or Refresh Modification or Refresh Figure 2: Flow state The Flow-Status AVP (see clause 6.4.11) is used to define the action to be taken for each AA-Request made by the SPDF to the A-RACF. The rules for interpreting the Flow-Status AVP are the following: • Reservation: New Media-Description-Component AVP(s) and Media-Sub-Component AVP(s). Optional Flow-Status AVP(s) set to DISABLED (3). • Modification: Updated Media-Description-Component AVP(s) and/or Media-Sub-Component AVP(s). Flow-Status AVP not modified, unless the state needs to be modified (e.g. for committing a resource reservation, or for releasing a resource reservation). • Commit: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). • ReservationAndCommit: New Media-Component-Description AVP(s) and Media-Sub-Component AVP(s). Flow-Status AVP(s) set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). • Release: Media-Description-Component AVP(s) and optionally Media-Sub-Component AVP(s) of existing reservations with Flow-Status AVP(s) set to REMOVED (4). • Refresh: Existing reservation unchanged (Media-Component-Description AVP(s) not specified or unchanged), Flow-Status AVP unchanged. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 11
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.1 Procedures at the SPDF
| |
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.1.1 Initial Reservation for a Session
|
The SPDF may request the A-RACF to allocate resources for a new session (i.e. make an initial reservation request). The SPDF issues such request by sending an AA-Request message to the A-RACF. This message contains one or more Media-Component-Description Attribute-Value-Pair(s) (AVP(s)). Each Media-Component-Description AVP describes the set of flows of a particular media type (i.e. it contains one or more Media-Sub-Component AVP(s) and requirements for the flows (see clause 6.4.16)). The SPDF may in the AA-Request include the Flow-Grouping AVP(s) to request a particular way for how the IP Flows are to be distributed to IP-CAN bearers. The SPDF may also forward an AF-Charging-Identifier AVP from the AF in the message for charging correlation purposes between AF and RACS. An AA-Request issued to request an initial reservation contains a new Session-Id obtained by the SPDF. As specified in RFC 3588 [11], the Session-Id is globally unique and is meant to uniquely identify a user session without reference to any other information. The Session-Id begins with the sender's identity encoded in the DiameterIdentity type. The specific action that shall be performed by the A-RACF for each individual media and flow (i.e. the Reserve or the ReserveAndCommit operation) is defined by the Flow-Status AVP: • Reservation; the value of the Flow-Status AVP shall be set to DISABLED (3). • ReservationAndCommit; the value of the Flow-Status AVP shall be set to ENABLED-UPLINK (0), ENABLED-DOWNLINK (1) or ENABLED (2). • The Flow-Status AVP shall be specified in the Media-Component-Description AVP and in the Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to the same value in both these AVPs. Table 1: Initial Reservation operations Message Type Flow-Status AVP at the level of: Meaning Media Sub-Media AAR New Media, DISABLED New flow, DISABLED Reserve Resources for all the flows in the request. The media(s) and flow(s) descriptions MUST be new ones. AAR [New Media, ENABLE*] New flow, ENABLE* Reserve Resources. In addition, commit resources for some of the flows. The media(s) and flow(s) descriptions MUST be new ones. As specified in clause 8.9 of RFC 3588 [11], the SPDF may specify the Authorization-Lifetime AVP in the AA-Request to request a maximum lifetime for a session. To request a hard-state session the SPDF shall omit the Authorization-Lifetime AVP in the AA-Request. To request a soft-state session the SPDF shall specify this AVP in the AA-Request. The AA-Answer may contain the Authorization-Lifetime AVP. The AA-Answer may contain the Auth-Grace-Period AVP in addition to the Authorization-Lifetime AVP. The Authorization-Lifetime AVP specifies the maximum number of seconds before the Session must be refreshed by the SPDF. The Auth-Grace-Period AVP contains the number of seconds the A-RACF will wait for a Refresh following the expiration of the Authorization-Lifetime AVP. Whether the Authorization-Lifetime AVP and Auth-Grace-Period need to be included in the AA-Answer is a local decision of the A-RACF. This means that the SPDF may be offered a soft-state reservation although it asked for hard-state or a hard-state reservation although it asked for soft-state. Should the SPDF not accept what is offered by the A-RACF it must explicitly terminate the session. The SPDF may specify the Reservation-Priority AVP (see clause 6.4.23) as a main AVP of the AA-Request in order to assign a priority to the request. The SPDF may further specify the Reservation-Priority AVP in Media-Component-Description AVP(s) in order to assign priority to individual media. If the Reservation-Priority AVP is not specified the requested priority is DEFAULT. The SPDF may specify, in the Specific-Action AVP of the AA-Request through which the initial reservation request is made, the events of which it wants to be informed. The supported events are listed in clause 6.4.13. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 12 The SPDF may specify in the initial AAR the authorization context to be used for a media component or for the session by including one or more Media-Authorization-Context-Id AVP or Authorization-Package-Id AVPs respectively. In the case of a multicast reservation, the derived authorisation context stored in A-RACF may provide information on the multicast channels allowed or not allowed during the session and their respective QoS requirements. Should the AA-Answer contain one or more Session-Bundle-Id AVPs the SPDF shall store the association between the Session-Bundle-Id AVP(s) and the Session-ID AVP of the session in question. The behaviour when the SPDF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.1.2 Session Modification
|
The SPDF may modify an existing session by sending an AA-Request to the A-RACF with zero or more updated Media-Component-Description AVP(s) and/or Media-Sub-Component AVP(s). The Session-Id shall be an existing one and refer to the session that is to be modified. The Reservation-Priority may be specified as a main AVP and/or in Media-Component-Description AVP(s). If the Reservation-Priority AVP is not specified the requested priority is DEFAULT. The SPDF may perform the following operations: • Add a new flow within a media component by providing a new Media-Sub-Component AVP within the corresponding Media-Component-Description AVP. • Add a new flow within a new media component by providing a new Media-Component-Description AVP. • Modify a media component by updating the corresponding Media-Component-Description AVP (e.g. increase or decrease the allocated bandwidth). • Modify a flow within a media component by updating the corresponding Media-Sub-Component AVP. • Modify a media flow state from Reserved to Committed by providing a Flow-Status AVP of the corresponding Media-Component-Description AVP and/or Media-Sub-Component AVP(s). The Flow-Status AVP shall be set to one of the values ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, according to the direction in which the resources are to be committed. This operation requires that the media and flows are in the Reserved state prior to the AA-Request. • Release a media component by providing the corresponding Media-Component-Description AVP with the Flow-Status AVP set to the value REMOVED. • Release a flow within a media by providing the corresponding Media-Sub-Component AVP with the Flow-Status AVP set to the value REMOVED. • Refresh a soft-state session by providing an AA-Request message containing the Session-Id of the session that is to be refreshed. The AA-Request may contain the Authorization-Lifetime AVP to request a maximum lifetime of the refreshed session. If this AVP is not included, the refresh message requests the lifetime to be extended by a default value. The AA-Request may contain Media-Component-Description AVP(s) and Media-Sub-Component AVP(s) (e.g. to modify media, flows and/or commit status). • Modify the media level authorization context - provide new Media-Authorization-Context-Id AVP(s). The new Media-Authorization-Context-Id AVP(s) replace any authorization context previously associated to the media component. • Modify the session level authorization context - provide new Authorization-Package-Id AVP(s). The new Authorization-Package-Id AVP(s) replace any authorization context previously associated to the session. The Flow-Status AVP in the Media-Sub-Component AVP shall always be the same as the Flow-Status AVP in the Media-Component-Description AVP containing the Media-Sub-Component AVP. When providing new Media-Component-Description AVP(s) and/or Media-Sub-Component AVP(s) the SPDF may in the AA-Request include the Flow-Grouping AVP(s) to request a particular way for how the IP Flows are to be distributed to IP-CAN bearers. The SPDF SHALL NOT use the RAA to modify the session service information. As an option, the SPDF MAY send an AAR command following an RAA to update the session service information. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 13 Table 2: Modification operations Message Type Flow-Status AVP at the level of: Meaning Media Sub-Media AAR Existing Media Existing Flow, Unchanged Flow-Status Modify a media. In addition, modify a flow according to the new parameters specified in the Media-Sub-Component AVP. The Media and Flow must exist (see notes 1, 2 and 5). AAR Existing Media New flow. Same Flow-Status AVP as in the media (see note 3) Modify a media. In addition, add a new flow in a media. The Flow must be new (see notes 3 and 5). AAR Existing Media (see note 4) REMOVED Modify a media. In addition, release an existing flow within an existing media. If the flow does not exist, the request shall be ignored by the A-RACF (see notes 2 and 5). AAR Existing Media, Modified Flow-Status Existing Flow, Flow-Status AVP = REMOVED Modify the commit status (see note 5). AAR Existing Media Existing Flow (see note 5). NOTE 1: If the media is not an existing one, the AAR is interpreted as a reservation for a new media (see clause 5.1). NOTE 2: The parameters specified at flow-level (in the Media-Sub-Component AVP(s)) take precedence over the parameters specified at media-level (in the updated Media-Component-Description AVP). NOTE 3: The Flow-Status AVP of a new flow within a media shall be the same as the Flow-Status of the media. For example, it makes no sense to commit a flow within a media that is not yet committed. NOTE 4: As the Modify operation is also used for the Commit operation, the Flow-Status AVP of the Media-Component-Description AVP may actually be modified. NOTE 5: In case of a soft-state reservation, extend its lifetime. The behaviour when the SPDF does not receive an AA-Answer, or when it arrives after the internal timer waiting for it has expired, or when it arrives with an indication different than DIAMETER_SUCCESS, is outside the scope of the present document.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.1.3 Session Termination
|
The SPDF may issue a Session-Termination-Request (STR) command to the A-RACF, in order to terminate the session. This command releases all the resources associated with the session identified by the provided Session-Id AVP. Table 3: Termination operations Message Type Flow-Status AVP at the level of: Meaning Media Sub-Media STR Release a session: all the media(s) and flow(s) within that session are released When receiving an Abort-Session-Request (ASR) message from the A-RACF the SPDF shall if the session involves BGF resources release those resources and inform the AF of that the session identified by the Session-Id AVP is terminated. If the ASR message contains one or more Session-Bundle-Id AVPs the SPDF shall perform these procedures for all sessions associated with the Session-Bundle-Id AVP(s).
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.1.4 Event notification
|
Notifications for specific events may be implicitly requested through policies established in the A-RACF. The SPDF may further specify, in the Specific-Action AVP of an initial AA-Request command, the events of which it wants to be informed. The supported events are listed in clause 6.4. As an option, when the SPDF receives an RAR command from the A-RACF, this may result in the SPDF sending an AAR command to the A-RACF to update the service information. However, application-specific authentication and/or authorization messages are not mandated for the Rq application in response to an RAR command. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 14
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.2 Procedures at the A-RACF
| |
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.2.1 Initial Reservation for a Session
|
An initial AA-Request contains one or more Media-Component-Description AVP(s) including one or more Media-Sub-Component AVP(s). For initial reservation requests in which the Session-Id is new the Media-Component-Number(s) and Flow-Number(s) are interpreted by the A-RACF as new ones. The Reservation-Priority AVP may be specified (see clause 6.4.23) main AVP in the AA-Request. The AA-Answer from the A-RACF may echo the Reservation-Priority AVP. If the Reservation-Priority AVP is not specified in the AA-Request, the priority associated with the reservation shall be DEFAULT. If the A-RACF is not able to comply with the requested priority level, the entire reservation shall fail and the A-RACF shall include the Experimental-Result-Code AVP with the value PRIORITY_NOT_GRANTED. When provided as a main AVP in an AA-Request, the Reservation-Priority AVP indicates the priority of the message to the A-RACF. The A-RACF may use this indication when receiving and processing the message (e.g. high priority AA-Request messages may be assigned precedence over low priority AA-Request messages). Upon reception of an AF-Application-Identifier AVP in an initial AA-Request from the SPDF, the A-RACF shall store this identifier together with the states created and maintained for the new session for the purpose of charging correlation between AF and RACS. The identifier is opaque to the A-RACF. The A-RACF shall identify the access profile that applies to the AA-Request from an identifier. This identifier comes in the form of the Subscriber ID, the Globally Unique IP Address, or both (see clause 5.2.2.2.7 in ES 282 003 [2]). The mapping of these parameters to the Diameter AVPs is described in table 4. If the A-RACF does not receive at least one of these parameters, it shall return an AA-Answer that include a Result-Code AVP set to the value DIAMETER_MISSING_AVP. The Failed-AVP AVP should be included in the message. The Failed-AVP AVP must contain an example of the missing AVP. The value field of the missing AVP example should be of correct minimum length and contain zeroes. If the A-RACF cannot identify an access profile that applies to the AA-Request, it shall return an Experimental-Result-Code AVP to the SPDF set to ACCESS_PROFILE_FAILURE. Table 4: Mapping of information element names to Diameter AVPs Information element name Mapping to Diameter AVP Cat. AVP used in Subscriber ID in RACS [2] and in NASS [3] User-Name O Rq and e4 [4] Globally Unique IP Address in RACS [2] and in NASS [3] Globally-Unique-Address O Rq and e4 [4] QoS Profile in NASS [3] QoS-Profile O e4 [4] Requestor Name in RACS [2] AF-Application-Identifier O Rq Requestor Name in NASS [3] Application-Class-ID O e4 [4] Media Type in NASS [3] and in RACS [2] Media-Type O Rq and e4 [4] Reservation Class in RACS [2] Reservation-Class O Rq Transport Service Class in RACS [2] and in NASS [3] Transport-Class O Rq and e4 [4] Service Class in RACS [2] Service-Class O Rq Authorization package ID in RACS [2] Authorization-Package-Id O Rq and Gq’ [5] Media Authorization context ID Media-Authorization-Context-Id O Rq and Gq’ [5] If the identified access profile contains one or more QoS Profiles the A-RACF shall for each Media-Component-Description AVP in the AA-Request use the combined meaning of the AF-Application-Identifier AVP, the Transport-Class AVP and the Media-Type AVP to identify a QoS Profile to which the request applies. For this identification process the AF-Application-Identifier AVP, the Transport-Class AVP and the Media-Type AVP in the AA-Request received over Rq shall be matched with the information stored in the A-RACF that corresponds to the Application-Class-ID AVP, the Transport-Class AVP and the Media-Type AVP in the QoS Profile(s) obtained from NASS via e4 [3]. It should be noted that an access profile obtained from NASS via e4 ES 283 034 [4] may contain one or more QoS Profile AVPs with left out Application-Class-ID AVP, Transport-Class AVP and/or Media-Type AVP. The absence of these AVPs allows the A-RACF to apply default QoS Profiles to any Requestor Name, any Transport Service Class, and any Requestor Name and Transport Service Class. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 15 If the access profile does not contain any QoS Profile the A-RACF shall instead apply a default QoS Profile to the request. If the Reservation-Priority AVP is not specified in the Media-Component-Description AVP for which a QoS profile applies the requested priority is DEFAULT. The A-RACF shall return an Experimental-Result-Code AVP to the SPDF set to QOS_PROFILE_FAILURE if the request needs to be denied for any of the following reasons: • The User-Name AVP and/or the Globally-Unique-Address AVP do not match any access profile. • The AF-Application-Identifier AVP, Transport-Class AVP and Media-Type AVP do not match any QoS profile of the access profile (identified by the User-Name AVP and/or the Globally-Unique-Address AVP). • The Max-Requested-Bandwidth-UL AVP and/or the Max-Requested-Bandwidth-DL AVP are larger than what is allowed by the QoS Profile matching the request (i.e. the Maximum-Allowed-Bandwidth-UL AVP and/or the Maximum-Allowed-Bandwidth-DL AVP obtained via e4). • The Reservation-Priority AVP in the Media-Component-Description AVP is larger than the maximum priority allowed by the QoS profile matching the request (i.e. the maximum priority allowed by a QoS profile is received in the Reservation-Priority AVP obtained via e4). NOTE: Only the first failure reason is possible for access profiles that do not contain a QoS Profile. Any value of the Flow-Status AVP received in an initial AA-Request (in which the Session-Id is new) different from ENABLED-UPLINK, ENABLED-DOWNLINK, ENABLED or DISABLED shall result in an error. If the Flow-Status AVP has the value REMOVED the A-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. In case the operation fails due to lack of resources, the A-RACF shall include the Experimental-Result-Code AVP set to the value INSUFFICIENT_RESOURCES. An initial reservation request can be admitted by the A-RACF if for all media streams in the session, the resource requirements fit within the constraints of remaining envelopes of unused resources. The A-RACF is presumed to exhibit "atomic" reservation semantics (i.e. either all reservations are admitted, or none of them). Once a reservation is admitted, the corresponding amount of resources is removed from the pool of available resources. If the request is admitted the A-RACF must send an AA-Answer back to the SPDF and include the Result-Code AVP set to the value DIAMETER_SUCCESS. Upon successful reservation, the A-RACF shall store the Diameter base protocol Session-Id received in the AA-Request through which the initial reservation request was made, and the Media-Component-Number(s) and Flow-Number(s). It shall also create an instance of the state machine illustrated in figure 2 for each media in the session and store the state of each media of the session. The AA-Request may contain Authorization-Package-Id AVP(s) or Media-Authorization-Context-Id AVP(s). The A-RACF shall use these parameters to identify the authorization context for the session or media component. The parameters may be used to derive the appropriate policies to be passed to an RCEF through the Re reference point. Any Authorization-Package-Id AVP or Media-Authorization-Context-Id AVPs that cannot be correlated to a locally defined authorization context shall result in an error. The A-RACF shall return an AA-Answer containing a Failed-AVP AVP and Experimental-Result-Code AVP with the value INVALID_SERVICE_INFORMATION. The AA-Request may contain the Authorization-Lifetime AVP. The A-RACF shall interpret the presence of the Authorization-Lifetime AVP as a request for a soft-state reservation and the absence of this AVP as a request for a hard-state reservation. The A-RACF may however return the Authorization-Lifetime AVP or the pair of Authorization-Lifetime AVP and Auth-Grace-Period AVP although the AA-Request did not contain the Authorization-Lifetime AVP. The A-RACF thereby offers a soft-state reservation although the request was for hard-state. The A-RACF may also choose not to return the Authorization-Lifetime AVP and the Auth-Grace-Period AVP although the AA-Request contained the Authorization-Lifetime AVP. The A-RACF thereby offers a hard-state reservation although the request was for soft-state reservation. The Authorization-Lifetime indicates when the A-RACF expects a Refresh from the SPDF. The Auth-Grace-Period AVP can only be specified in addition to the Authorization-Lifetime AVP. As specified in clause 8.9 of RFC 3588 [11] the server (i.e. the A-RACF) may return the Authorization-Lifetime AVP set to a value equal to, or smaller, than the value of the Authorization-Lifetime AVP provided by the SPDF. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 16 The A-RACF may include one or more Session-Bundle-Id AVPs in the AA-Answer. The Session-Bundle-Id AVP identifies a group of sessions to which the session belongs. The value of this AVP and which sessions that belong to a certain such value are chosen by the A-RACF. The value if the Session-Bundle-Id AVP is meaningful only for the A-RACF. If the Specific-Action AVP is included in the initial AA-Request, notification for the given event(s) shall be activated by the A-RACF. The supported events are listed in clause 6.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.2.2 Session Modification
|
An AA-Request issued to modify an existing session may contain zero or more Media-Component-Description AVP(s) including one or more Media-Sub-Component AVP(s). For modification requests in which the Session-Id is an existing one the Media-Component-Number(s) and Flow-Number(s) of existing reservations shall be existing ones. Media-Component-Number(s) and Flow-Number(s) of new Media-Component-Description AVP(s) and Media-Sub-Component AVP(s) are interpreted by the A-RACF as new ones. For an AA-Request issuing a session modification operation the Flow-Status AVP must be set to a value representing a state to which the session is allowed to enter from its current state. The allowed state transitions are illustrated in figure 2. Should the Flow-Status AVP be set to a disallowed value the A-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. If the A-RACF is unable to modify the status of a reservation to ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, the A-RACF shall issue an error message to the SPDF with an Experimental-Result-Code AVP set to the value COMMIT_FAILURE. If the status of a reservation is one of the values ENABLED-UPLINK, ENABLED-DOWNLINK or ENABLED, the AA-Request should not contain a Flow-Status AVP set to DISABLED. If it does, the A-RACF shall return an AA-Answer to the SPDF with an Experimental-Result-Code AVP set to the value MODIFICATION_FAILURE. If the A-RACF is not able to re-initialize the lifetime of the reservation, it shall return an AA-Answer to the SPDF with an Experimental-Result-Code AVP set to the value REFRESH_FAILURE. If a flow-level operation fails, the entire Session Modification operation fails. In case the A-RACF determines that the request cannot be admitted due to insufficient resources, it shall return an Experimental-Result-Code AVP to the SPDF set to the value INSUFFICIENT_RESOURCES. The A-RACF shall return an Experimental-Result-Code AVP to the SPDF set to QOS_PROFILE_FAILURE if the request needs to be denied for any of the reasons listed in clause 5.2.1 associated with this value. In case the Specific-Action AVP, the AF-Charging-Identifier AVP, the Flow-Grouping AVP, the Service-Class AVP, the User-Name AVP or the Globally-Unique-Address AVP was provided in an initial AA-Request with a value different from the value of the AVP(s) in a modifying AA-Request, the A-RACF shall return an AA-Answer containing a Failed-AVP AVP and a Result-Code AVP with the value DIAMETER_INVALID_AVP_VALUE. Upon successful session modification, the A-RACF must send an AA-Answer back to the SPDF with the Result-Code AVP set to DIAMETER_SUCCESS. Upon a successful refresh operation, the A-RACF shall in the AA-Answer return the Authorization-Lifetime AVP with a value equal or smaller than the Authorization-Lifetime AVP of the AA-Request (if any). The Auth-Grace-Period AVP can only be specified in addition to the Authorization-Lifetime AVP. Whether Authorization-Lifetime AVP and Auth-Grace-Period AVP need to be specified in the AA-Answer is a local decision for the A-RACF. If a reference to a previously negotiated Media-Component-Description AVP and/or Media-Sub-Component AVP for the session in question is omitted in the AA-Request, the corresponding flow is not impacted by the Modification operation.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.2.3 Session Termination
|
If all IP flows within a SPDF session need to be terminated, the A-RACF shall inform the SPDF about this event by sending an Abort-Session-Request (ASR) message with the appropriate Abort-Cause AVP value. The A-RACF may include one or more Session-Bundle-Id AVPs in order to inform the SPDF of that several sessions identified by the provided Session-Bundle-Id AVP(s) are terminated. ETSI ETSI TS 183 026 V3.1.1 (2010-03) 17 Upon receipt of a Session-Termination-Request (STR) message from the SPDF the A-RACF shall release all the resources associated with the session identified through the provided Session-Id AVP. If an unknown Session-Id is provided in the STR the A-RACF shall return a STA message to the SPDF with the Result-Code AVP set to DIAMETER_UNKNOWN_SESSION_ID.
|
f8b36fc7978d66b44111bf90dcc70b85
|
183 026
|
5.2.4 Event Notification
|
If an event for which notification is requested occurs, the A-RACF shall send an unsolicited RAR message to the SPDF containing: • The value of the Specific-Action AVP, indicating the event that occurred. • Optionally, the appropriate Abort-Cause AVP value.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.