hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 004 (V2.y.z): "Telecommunications and Int... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] IETF RFC 3554: "On the use of Stream Control Tra... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3 Definitions and abbreviations | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access record: set of information stored in the CLF in relation to an IP address Application Function (AF): element of the network architecture offering - or providing access to - applications that require information about the charact... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AF Application Function A-RACF Access RACF AVP Attribute-Value Pair CLF Connectivity session Location and repository Function CSCF Call Session Control Function FQDN Fully Qualified Domain Name IANA Internet Ass... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 4 Overview | The Network Attachment SubSystem (NASS), defined in ES 282 004 [1], maintains information about IP-connectivity associated with NASS User connected to TISPAN networks. The a2 reference point allows the NACF to register in the CLF the association between the IP address allocated to a NASS User and information identifyin... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5 Procedure Descriptions | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.1 General | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.1.1 Information elements | The following clauses describe the realization of the functional procedures defined in the NASS [1] and RACS specifications [2] using Diameter commands described in clause 7. This involves describing a mapping between the information elements defined in the NASS specification [1] and Diameter AVPs. In the tables that d... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2 Procedures on the CLF - NACF interface | 5.2.1 Bind indication/Acknowledgement |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.1 Overview | This procedure is used to report the binding between the IP address allocated to a user equipment and identity of the access to which this equipment is connected from the NACF to the CLF. This information flow occurs when an IP address has been allocated to a user equipment. The NACF should trigger this procedure as so... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.2 Procedure at the NACF side | After allocating the IP address to a user equipment, or when a Renew is received from a different access line, the NACF shall send a Bind Indication with the following information to CLF: • The Globally-Unique-Address AVP shall contain a Frame-IP-Address or Frame-IPv6-Prefix AVP value, and an Address-Realm AVP. • The L... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.1.3 Procedure at the CLF side | If at least one of the specified AVP(s) is invalid, the CLF shall return a Binding Acknowledgement with a Result-Code AVP value set to DIAMETER_INVALID_AVP_VALUE and a Failed-AVP AVP containing a copy of the invalid AVP(s). If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2 Unbind indication | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.1 Overview | This procedure is used by the NACF to report the case the allocated IP address is released (e.g. DHCP leased timer expiry) or due to a release of the underlying layer 2 resources. This enables the CLF to remove the corresponding record from its internal database. This procedure is mapped to the commands Push-Notificati... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.2 Procedure at the NACF side | On receipt of release request for the allocated IP address from the user equipment or in case of expiry of the lease period or on receipt of an indication that the underlying layer 2 connection has been lost, the NACF shall clear all information stored against the IP address and issue a Push-Notification-Request repres... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.2.3 Procedure at the CLF side | If the globally unique identifier contained in the Globally-Unique-Address AVP is not known, the CLF shall stop processing the request and set the Experimental-Result-Code to DIAMETER_ERROR_USER_UNKNOWN in the Unbind Indication acknowledgement. If the globally unique identifier contained in the Globally-Unique-Address ... |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3 Bind information query/acknowledgment | |
223ebff1738b9aebce60fbd8ef406718 | 183 059-1 | 5.2.3.1 Overview | This procedure is used by the CLF to request binding information from the NACF, in the context of recovery procedures. This procedure is mapped to the commands User-Data-Request/Answer in the Diameter application specified in clause 7. Tables 5.5 and 5.6 detail the involved information elements as defined in the NASS s... |
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 n... |
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 Ackn... |
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 mechan... |
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. Consequen... |
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... |
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... |
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... |
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 d... |
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 documen... |
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 Experiment... |
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 (500... |
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_UNAVAILA... |
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... |
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 60... |
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 accept... |
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] Voi... |
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) ... |
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 i... |
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 ... |
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. • ... |
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 stru... |
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 se... |
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 identifie... |
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... |
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 ... |
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 provid... |
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 s... |
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. - ... |
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... |
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) ... |
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 n... |
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. T... |
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 publ... |
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 ... |
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. NOTIF... |
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 ... |
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 conve... |
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 Log... |
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 nam... |
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... |
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 allo... |
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 identif... |
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... |
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... |
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 w... |
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, d... |
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... |
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 allo... |
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 accept... |
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] Voi... |
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 U... |
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 ... |
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 accept... |
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 Int... |
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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.