hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.1.11 User to user signalling (UUS) | TP511001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.21 1.3.7.2/Q.737 TSS reference: SIP-ISUP/SS/UUS/ SIP selection criteria: ISUP selection criteria: PICS 11/1 AND PICS 11/2 Test purpose: Ensure that the SUT if a FAR is received with an user-to-user service 3 request (not essential) aft... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.1.12 Explicit call transfer (ECT) | TP512001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.8 TSS reference: SIP-ISUP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 Test purpose: Ensure that the SUT if a LOP(request) is received returns a LOP (response) with the indication "insufficient information" contin... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.1.13 Completion of Call to Busy Subscriber (CCBS) | TP513001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.11 TSS reference: SIP-ISUP/SS/CCBS/ SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if a REL is received contained a Diagnostic field and the CCBS indicator is coded as CCBS possible: • continue witho... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.1.14 Completion of Calls on No reply (CCNR) | TP514001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.12 TSS reference: SIP-ISUP/SS/CCNR/ SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if a ACM is received and a CCNR Possible Indicator is included: • continue without disrupting the SIP signalling pro... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.1.15 Anonymous Call Rejection (ACR) | TP515001 SIP reference: RFC 3261 [6] ISUP reference: ES 283 027 [14], clause 7.4.23 TSS reference: SIP-ISUP/SS/ACR/ SIP selection criteria: ISUP selection criteria: PICS 1/9 Test purpose: Ensure that the SUT, if a destination user has subscribed the ACR supplementary service: • the call attempt is rejected with a REL c... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2 Interworking from ISUP to SIP (Outgoing Call) | |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.1 Calling Line Identification (CLI) | TP601001 SIP reference: RFC 3261 [6] ISUP reference: EN 383 001 clause 7.1.3 [2] TSS reference: ISUP-SIP/SS/CLI/ SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that when the SUT has received an IAM message whereby Calling Party Number parameter and the Generic Number are not applicable: • Sends a... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.2 Call Hold (HOLD) | TP602001 SIP reference: RFC 3261 [6] ISUP reference: EN 383 001 [2], annex B.10 TSS reference: ISUP-SIP/SS/HOLD/ SIP selection criteria: Support the temporarily stops sending one or more unicast media streams ISUP selection criteria: Support the generic notification procedure for HOLD supplementary service Test purpose... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.3 Terminal portability (TP) | TP603001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.13 TSS reference: ISUP-SIP/SS/TP/ SIP selection criteria: ISUP selection criteria: PICS 5/6 Test purpose: Ensure that the SUT stop the temporarily sending one or more unicast media streams if a SUS message (ISDN subscriber initiated) w... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.4 Conference calling (CONF) | TP604001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [14], clause 7.4.14 TSS reference: ISUP-SIP/SS/CONF/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/10 Test purpose: Ensure that the SUT stop the temporarily sending one or more unicast media streams if a CPG message Generic notification i... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.5 Three Party service (3PTY) | TP605001 SIP reference: RFC 3261 [6] NGN reference: ES 283 027 [14], clause 7.4.15 TSS reference: ISUP-SIP/SS/3PTY/ SIP selection criteria: PICS 8/2 ISUP selection criteria: PICS 5/5 AND PICS 5/18 Test purpose: Ensure that the SUT stop the temporarily sending one or more unicast media streams if a CPG message Generic n... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.6 Connected line identification (COL) | TP606001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.2 TSS reference: ISUP-SIP/SS//COL / SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if the IAM is received with an optional forward call indicator, connected line requested, continue without disruptin... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.7 Sub-addressing (SUB) | TP607001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.5 TSS reference: ISUP-SIP/SS/ SUB / SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if the IAM is received with an ATP containing a calling sub-address, continue without disrupting the SIP or ISUP sig... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.8 Closed user group (CUG) | TP608001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.16 TSS reference: ISUP-SIP/SS/CUG/ SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if an IAM is received with Optional forward call indicator, CUG call indicator coded as "CUG call with outgoing acces... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.9 Call diversion (CDIV) | TP609001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annexes B.6 and B.7 TSS reference: ISUP-SIP/SS/ CDIV / SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if the IAM is received with Redirecting number, original called number and redirection information, conti... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.10 User to user signalling (UUS) | TP610001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.21 1.1.7/Q.737 TSS reference: ISUP-SIP/SS/ UUS / SIP selection criteria: ISUP selection criteria: Test purpose: Ensure that the SUT if the IAM is received with User-to-user information as an implicit service 1 request returns a User-to... |
09d0f941c2db9816d77f8c2b8c4b53e5 | 186 002-2 | 6.3.2.11 Explicit call transfer (ECT) | TP611001 SIP reference: RFC 3261 [6] ISUP reference: ITU-T Rec Q.1912.5 [1], annex B.8 TSS reference: ISUP-SIP/SS/ECT/ SIP selection criteria: ISUP selection criteria: PICS 12/1 Test purpose: Ensure that the SUT if a LOP(request) is received returns a LOP (response) with the indication "insufficient information" contin... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 1 Scope | The present document specifies the network PICS (Protocol Implementation Conformance Statement) of the Interworking between Session Initiation Protocol (SIP) and Bearer Independent Call Control Protocol or ISDN User Part. |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] Recommendations ITU-T Q.761 to Q.764 (1999): "Signalling System No.7 - ISDN User Part". [2] Recommendations ITU-T Q.1902.1 to Q.1902.4 (2001): "Bearer Independent Call Control protocol (Capability Set 2)". [3] Recommendati... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable. |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 3 Definitions and abbreviations | |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Abstract Test Case (ATC): complete and independent specification of the actions required to achieve a specific test purpose, defined at the level of abstraction of a particular Abstract Test Method, starting in a stable testing state a... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ACM Address Complete Message ACR Anonymous Call Rejection supplementary service AMR Adaptive Multi Rate (codec) ATC Abstract Test Case ATM Abstract Test Method ATS Abstract Test Suite BICC Bearer Independent Call Control protocol CCBS Call Com... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 4 Scenarios | 4.1 SIP Profile A and B for interworking between SIP and BICC/ISUP IP IP, ATM or TDM BICC or ISUP Profile scope SIP Proxy G/W Type 1 SIP Figure 1: Profile Scope for SIP Interworking with BICC/ISUP with a Type 1 Gateway ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 9 IP IP, ATM or TDM BICC or ISUP Profile scope SIP BICC CSF-T... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5 PICS proforma | |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.1 Instructions for completing the PICS proforma | |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.1.1 Other information | More detailed instructions are given at the beginning of the different clauses of the PICS proforma. The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5.4. ETSI ETSI TS 186 002-1 V1.1.5 (201... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.1.2 Purposes and structure | The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specification [1] to [10] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of i... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.1.3 Conventions | The PICS proforma is composed of information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [9]. Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives ref... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if ... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.1 Date of the statement | Date of the statement: |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 14 |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3 PICS proforma tables | |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? NOTE: Answering "No" to this question indicates non-conformance to the reference protocol specification. Non-supported mandatory capabilities are to be identified in the PICS, with an explanation of why the implementation is non-conforming. |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.2 Roles | Table 1: Roles Item Is the implementation ... Reference Status Support 1 Profile A? ITU-T TRQ.2815 [19] o.11 2 Profile B? ITU-T TRQ.2815 [19] o.11 3 Profile C? ITU-T TRQ.2815 [19] o.11 4 connected with a BICC Network? Rec. ITU-T Q.1902.2 [2] o.12 5 connected with a ISUP Network? Rec. ITU-T Q.764 [1] o.12 6 connected wi... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.3 Connection types | Table 2: Connection types Item Is the exchange able to ... Reference Status Support 1 support the media type "audio" and media format 0, 8? Clauses 6.1.3.5.1 and 7.1.1.1 of Rec. ITU-T Q.1912.5 [11] o.21 2 support the media type "audio" and media format 9? Clauses 6.1.3.5.1 and 7.1.1.1 of Rec. ITU-T Q.1912.5 [11] o.21 3... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.4 Forward address signalling | Table 3: Forward address signalling Item Is the exchange [role] able to ... Reference Status Support 1 SIP use the en bloc operation in the forward address signalling (sending)? Clause 7.1 of Rec. ITU-T Q.1912.5 [11] o.31 2 SIP use the overlap operation in the forward address signalling (sending)? Clause 7.1 of Rec. IT... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.5 Role independent capabilities | Table 4: Role independent capabilities Item Is the exchange able to ... Reference Status Support 1 use the Continuity check procedures during call setup? Clause 6.1.2 of Rec. ITU-T Q.1912.5 [11] o 2 support the Continuity check procedures during call setup? Clause 2.1.8 of Rec. ITU-T Q.764 [1] Clauses 7.2 and 7.3 of Re... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.6 Supplementary Services Major Capabilities | Table 5: Supplementary Services Major Capabilities Item Is the exchange able to ... Reference in Rec. ITU-T Q.1912.5 [11] Status Support 1 support the service Calling Line Identification Presentation (CLIP)? Annex B.1 m 2 support the service Calling Line Identification Restriction (CLIR)? Annex B.1 m 3 support the serv... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.3.7 Timers | Table 13: Timers Item Use of ... Reference Status Support Values in seconds allowed supported 1 Toiw1 Clause 7.8/Table 41 of Rec. ITU-T Q.1912.5 [11] m 4 - 6 2 Toiw2 Clause 7.8/Table 41 of Rec. ITU-T Q.1912.5 [11] m 4 - 14 3 Toiw3 Clause 7.8/Table 41 of Rec. ITU-T Q.1912.5 [11] m 4 - 6 4 ISUP T6 Annex A of Rec. ITU-T Q... |
5dce6be58c4cd456248c3b2190323681 | 186 002-1 | 5.4 Additional information for PICS | This clause contains all additional comments provided by the supplier of the implementation (see clause 5.1.1). ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 21 Annex A (informative): Bibliography • Recommendation ITU-T Q.732.3 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. ... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 1 Scope | The present document provides an alignment of definitions on E.164 numbers, based on ITU-T Recommendation E.101 [1]. It provides requirements and describes the manner the numbers will be used within NGN and NGCN environments. Naming issues related to NGCN are out of the scope for the moment. The support of national-onl... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ITU-T Recommendation E.101 (2009): "Definitions of terms used for identifiers (names, numbers, addresses and other identifiers) for public telecommunication services and networks in the E-Series Recommendation". [2] ITU-T ... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TR 184 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Naming/Numbering Address Resoluti... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 3 Definitions and abbreviations | |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ITU-T Recommendation E.101 [1] and the following apply: national-only number: As defined in ITU-T Recommendation E.101 [1]. global number: International E.164 number as defined in ITU-T Recommendation E.101 [1] and described in RFC 3966 [11]. ... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CC Country Code CSCF Call Session Control Function DDI Direct-Dial-In ENUM Telephone Number Mapping GSM Global System for Mobile Communications I-ENUM Infrastructure ENUM IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 4 Structure of Numbers | Each country defines its own national numbering and the national dialling plan, based on ITU-T Recommendation E.164 [2], as well as the prefixes and how the national formats (i.e. the local and national level) are used. Subscribers in other countries are always reached by dialling the international prefix and the inter... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 5 E.164 numbers formats and coding used in NGNs | 5.1 General From the technical point of view, an ETSI's NGN is an IP-based network with control/service and transport layers and SIP signalling. E.164 numbers can be used to identify the users and service entities. From the signalling protocol point of view, E.164 numbers are conveyed using tel URI and/or SIP URI forma... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 5.2 International E.164 number format | 5.2.1 Use of International E.164 number An international E.164 number is a globally unique public identity of a subscriber or a service entity independent of technologies and service context, for instance NGNs, PSTNs or PLMNs, etc. The use of international E.164 numbers is mandatory at international interfaces between ... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 5.2.2 Use of dialled digits for International E.164 number | In order to use international E.164 numbers, a user may be required to first enter the international prefix defined by the national or private dialling plan or another indication ("+" character) to indicate the format of the number. According to ITU-T Recommendation E.164 [2] it is recommended to use "00" as the intern... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 5.3 Use of National E.164 number format | The E.164 numbers in the national format are used for communications inside a country only. In addition the subscriber number format, if present in the specific national numbering plan, can be used for communications inside national local areas (for instance inside a district). The support of the subscriber number is a... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 5.4.2 Processing of the Request URI received over the UNI | The dialled digits carried on in the SIP Request URI at NGN UNI must be analysed using appropriate numbering analysis functions according to the national dialling plan rules. The processing of the Request URI is accomplished through the following steps: 1. Analysis of incoming digits and, if they are present, phone-con... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 6 E.164 numbers in NGCN | |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 6.1 General | Private/corporate numbers may exist for example at an NGCN within a company. These companies have their own private numbering plan and dialling plan. Normally, these numbers may be accessed from the public NGN using direct-dial-in (DDI) numbers. Typically these DDI numbers are E.164 numbers [2] where the first digits b... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 6.2 Use of E.164 numbers in the NGCN | NGCN users are identified by one or more of the following identifiers: • number based: - E.164 number - private number: out of the scope of the present document, but described in Annex A - name based (using aliases): out of the scope of present document. Number based identifiers can appear in form of SIP(S) URIs or of ... |
b8d7d6dfc8922bd984551ceaa3e039cb | 184 011 | 7 Numbering normative statements | The normative statements for numbering in ETSI NGN are: 1) E.164 numbering plan, being neutral with respect to the technologies and services, is the public numbering plan also for NGN: - "The "global" number coding for E.164 numbers shall be used at the national and international NNI. The number format coding of the na... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 1 Scope | The present document captures a set of assumptions that would help to define a set of ETSI requirements and a possible architecture for an IPX and in particular the ENUM & DNS aspects. It explains why an IPX may prove useful and provides guidelines which would apply to its use as a private, inter-operator IP backbone f... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IETF RFC 1035: "Domain Names - Implementation and Specification". [2] IETF RFC 6116: "The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)". [3] IETF RFC 3403: "Dyna... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 4282: "The Network Access Identifier". [i.2] GSMA IR67 version 3.1 (Jan 2009). [i.3] ETSI TR 184 003: "Telecommunications and Internet conver... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 3 Definitions and abbreviations | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: carrier of record: Service Provider to which the E.164 number was allocated for end user assignment, by the National Regulatory Authority (NRA) or the International Telecommunication Union (ITU), for instance, a code under "Internation... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ATM Asynchronous Transfer Mode BGCF Border Gateway Control Function BGF Border Gateway Function BGP Border Gateway Protocol CC Country Code CP Communications Provider CSCF Call Session Control Function D... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4 Description and Assumptions | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.1 Introduction | DNS/ENUM can be used in an ETSI TISPAN compliant environment to support E.164 number resolution and number portability. Due to TR 184 003 [i.3] DNS/ENUM can be used to support number portability between operators of NGNs by using a shared infrastructure or operator local infrastructure (non-root approach). The present ... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.2 DNS as used on an Interoperator IP backbone network | The proposed approach requires a specific a DNS architecture. The Master Root DNS node(s) that Interoperator IP backbone providers see are known as "Slave Roots". DNS Servers and are commonly provisioned by Communication provider. However, these Slave Root DNS Servers can be provisioned by operators themselves if they ... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4 Requirements for the Interoperator IP Backbone network | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.1 General Issues | Considered purely from a connectivity point of view the required IP network between different operators might take different forms via the public Internet (with VPN) or direct leased line such as Frame relay or ATM. However the preferred ETSI approach is similar to the model used by 3GPP networks, utilizing a dedicated... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.2 Top level requirements | NGNs will not emerge at the same rate in all countries due to market differences, economic drivers and technological differences. It's therefore essential that any proposal to establish an Interoperator IP backbone network takes full account of the variable timeframe for evolution from country to country. Whilst connec... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.3 IP Version Issues | IMS core systems & terminals can be either IPv6, IPv4 based or dual stack. General usage of IPv4 and IPv6 regarding IMS detailed in TS 129 421 [7]. |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.4 IP Addressing | Internet routers should not be able to route to the IP addresses advertised to the Inter-ServiceProvider IP Backbone. The IP Backbone Providers and Service Provider networks shall be totally separated from public Internet, from an IP routing and connectivity perspective. Currently, Inter-Service Provider IP Backbone ne... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.5 DNS data transport | Providers shall: • support the transport of DNS queries and responses require to facilitate routeing • provide transport of ENUM queries and responses to support any identified services [2] • support the transport of DNS and ENUM queries and responses via IPv4 and IPv6, UDP and TCP • support the differentiation between... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.6 DNS/ENUM client | An DNS/ENUM client which sends DNS/ENUM queries and receives DNS/ENUM answers (e.g. S-CSCF, BGF, DNS) resolver should be supported by the following requirements: • must support the DNS/ENUM basic functional standards RFC 1035 [1], RFC 6116 [2], RFC 3403 [3], RFC 2782 [6]; • in the case of using UDP as transport protoco... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.7 Security Issues | In order to maintain proper level of security within the Interoperator IP backbone network certain requirements for operators and backbone providers should be taken into account. It is strongly recommended that operators should implement firewalls adjacent to Border Gateways. Generally operators should allow only routi... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.8 Quality of Service | An SLA will define a service specification between a communications Provider and an IP backbone provider. The involved parties may agree an IP QoS profile that should be supported over the connection and this extends to whole Inter-Service Provider IP backbone network comprising IP backbone Providers maintained network... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 4.4.9 Service Related Issues | Different end-user services used in IMS have different requirements. The actual IMS based services and their requirements are not within the scope of the present document. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 16 5 DNS and ENUM for the Interoperator IP backbone network 5.1 Naming and Addressing within IP Multi-media co... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 5.2 E.164 Number Translation (ENUM) | E.164 numbers cannot be used on their own for addressing in IP based networks. The Internet Engineering Task Force has defined a mechanism for converting E.164 numbers to addresses relevant to services which the user wishes to use and which are accessible through means using IP. RFC 6116 [2] defines storing E.164 numbe... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 5.4 Non-root DNS/ENUM architecture | In some circumstances, where the DNS or ENUM database or parts of them are under a single administrative control there is no need for operating dedicated root, Top Level Domain, Second Level Domain, Third Level Domain etc. DNS server respectively Tier-0, Tier-1 and Tier-2 ENUM server. In such a case the whole DNS and/o... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 6 Addressing and Routeing | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 6.1 User Addressing | Every IMS user has at least one private user identity. Private user identity is assigned by the home operator, and used, for example, for Registration, Authorisation, Administration, and Accounting purposes. Private user identity is in the form of a Network Access Identifier (NAI) RFC 4282 [i.1], for example joe.doe@ca... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 6.2 Naming of home network | An operator can use any domain name that he has publicly registered as the name for his home network.(thereby providing uniqueness). The present document describe only the usage of RFC 1035 [1]. Therefore it is highlighted here that a TISPAN IPX supports only domain labels which consists of 7-bit ASCII characters as le... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7 ENUM and DNS Structure and Delegation Model | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.1 Introduction | There are three top level principles which the ENUM model should support. First, there should be a competitive environment. Second, equal accessibility is required, such that the ENUM data fill is available to all entities who need it. Third, accuracy is critical, which means that there exist authoritative databases wi... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.2 Model for the Interoperator IP backbone network | |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.2.1 Introduction | A strict hierarchy is followed as DNS is designed to have a hierarchical structure allowing different organisations to have control of different parts of the overall structure. E.164 numbers also have a hierarchical structure and this can be mapped onto the DNS structure on the Interoperator IP backbone network. When o... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.2.2 ENUM & DNS Architecture | The DNS architecture for this model is depicted in figure 3. Figure 3: ENUM DNS hierarchy It should be noted that what is represented in figure 3 are logical entities and thus one or more of those logical entities can be offered by one physical server. The physical realisation of this arrangement is not depicted in fig... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.2.3 Example resolution | Figure 4 depicts an example of ENUM resolution. Local Caching DNS Server Root DNS Server ENUM DNS Tier-0 Server ENUM DNS Tier-1 Server ENUM DNS Tier-2 Server 1 2 3 4 5 6 7 8 Figure 4: Example of ENUM resolution for an IMS session establishment ETSI ETSI TS 184 010 V3.1.1 (2011-08) 20 The numbers in the messages in figu... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 7.2.4 Access to ENUM servers | It is assumed that all operators connected to the Interoperator IP backbone network have access to all ENUM servers at all Tiers, and such servers service all queries sent to them by network operators. If any servers require commercial agreements and/or charge for access, then this will seriously hamper the ability for... |
38728eac46b7e848e574a5c1a5945388 | 184 010 | 8 Delegation and use of domains | The exact choice of domain names to be used for the inter-operator IP backbone network is for further study however some high level principles and guidelines on their control, administration and structure follow. At this stage all detailed references and use of domain names within the present document should be treated... |
0e06561ddbcf2651d8b229c2ed3e8620 | 184 009 | 1 Scope | The present document provides rules for the identification ("naming") of television channels using the TV URI identifier. |
0e06561ddbcf2651d8b229c2ed3e8620 | 184 009 | 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... |
0e06561ddbcf2651d8b229c2ed3e8620 | 184 009 | 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 TR 180 000: "Telecommunications and Internet con... |
0e06561ddbcf2651d8b229c2ed3e8620 | 184 009 | 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.