hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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 reference to the specification(s) [1] to [21], except where explicitly stated otherwise. Status column The following notations, defined in ISO/IEC 9646-7 [9], are used for the status column: m mandatory - the capability is required to be supported. n/a not applicable - in the given context, it is impossible to use the capability. No answer in the support column is required. o optional - the capability may be supported or not. o.i qualified optional - for mutually exclusive or selectable options from a set. "i" is an integer which identifies a unique group of related optional items and the logic of their selection which is defined immediately following the table. ci conditional - the requirement on the capability ("m", "o" or "n/a") depends on the support of other optional or conditional items. "i" is an integer identifying a unique conditional status expression that is defined immediately following the table. For nested conditional expressions, the syntax "IF ... THEN (IF ... THEN ... ELSE...) ELSE ..." shall be used to avoid ambiguities. If an ELSE clause is omitted, "ELSE n/a" shall be implied. NOTE: Support of a capability means that the capability is implemented in conformance to the specification(s) [1] to [21]. Support column The support column shall be filled in by the supplier of the implementation. The following common notations, defined in ISO/IEC 9646-7 [9], are used for the support column: • Y or y supported by the implementation. ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 13 • N or n not supported by the implementation. • N/A or n/a or "no answer required" (allowed only if the status is N/A, directly or after evaluation of a conditional status). Values allowed column This column contains the values or the ranges of values allowed. Values supported column The support column shall be filled in by the supplier of the implementation. In this column the values or the ranges of values supported by the implementation shall be indicated. References to items For each possible item answer (answer in the support column) within the PICS proforma, a unique reference exists. It is defined as the table identifier, followed by a slash character "/", followed by the item number in the table. If there is more than one support column in a table, the columns shall be discriminated by letters (a, b, etc.) respectively. EXAMPLE: 5/4 is the reference to the answer of item 4 in table 5.
|
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 they are different. A person who can answer queries regarding information supplied in the ICS should be named as the contact person.
|
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 with a µ-law network? Clauses 6.1 and 7.1 of ITU-T TRQ.2815 [19] o 7 an outgoing international exchange? Rec. ITU-T Q.764 [1] o 8 an incoming international exchange? Rec. ITU-T Q.764 [1] o 9 an implementation according ETSI EN 383 001 [10]? ETSI EN 383 001 [10] o NOTE: o.11: It is mandatory to support at least one of these items. o.12: It is mandatory to support one of these items. ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 15
|
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 support the media type "audio" and attribute value CLEARMODE? Clauses 6.1.3.5.1 and 7.1.1.1 of Rec. ITU-T Q.1912.5 [11] o.21 4 support the media type "image" and media format t38? Clauses 6.1.3.5.1 and 7.1.1.1 of Rec. ITU-T Q.1912.5 [11] o.21 5 support the dynamic assignment for codec? Clauses 6.1.3.5.1 and 7.1.1.1 of Rec. ITU-T Q.1912.5 [11] o.21 6 use the transport protocol udptl? RFC 768 [13] o 7 use the transport protocol tcptl? RFC 761 [14] o 8 support the transcoding of the AMR codec to G.711 PCM? RFC 4867 [21] o NOTE: o.21: It is mandatory to support at least one of these items.
|
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. ITU-T Q.1912.5 [11] o.31 3 SIP support the en bloc operation in the forward address signalling (receiving)? Clause 6.1 of Rec. ITU-T Q.1912.5 [11] o 4 SIP support the overlap operation in the forward address signalling (receiving)? Clause 6.1 of Rec. ITU-T Q.1912.5 [11] o 5 ISUP use the en bloc operation in the forward address signalling (sending)? Clause 6.1 of Rec. ITU-T Q.1912.5 [11] o.32 6 ISUP use the overlap operation in the forward address signalling (sending)? Clause 6.1 of Rec. ITU-T Q.1912.5 [11] o.32 7 ISUP support the en bloc operation in the forward address signalling (receiving)? Clause 7.1 of Rec. ITU-T Q.1912.5 [11] o 8 ISUP support the overlap operation in the forward address signalling (receiving)? Clause 7.1 of Rec. ITU-T Q.1912.5 [11] o NOTE: o.31: It is mandatory to support at least one of these items. o.32: It is mandatory to support one of these items.
|
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 Rec. ITU-T Q.1902.4 [2] m 3 support hop counter procedure? Clauses 6.1.3.9 and 7.1.4 of ETSI EN 383 001 [10] c41 4 support internal resource reservations (preconditions used)? Clause 6.1.2 2 of ETSI EN 383 001 [10] o 5 support the reliability of provisional responses? RFC 3262 [8] o ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 16 Item Is the exchange able to ... Reference Status Support 6 perform the automatic repeat attempt? Clause 2.8.1 of Rec. ITU-T Q.764 [1] Clause 12.4 of Rec. ITU-T Q.1902.4 [2] o 7 support the propagation delay determination procedure? Clause 2.6 of Rec. ITU-T Q.764 [1] Clause 8.5 of Rec. ITU-T Q.1902.4 [2] o 8 perform the automatic repeat attempt in case of dual seizure? Clause 2.9.1 of Rec. ITU-T Q.764 [1] Clause 13.2 of Rec. ITU-T Q.1902.4 [2] o 9 send ACM after determination of end of address signalling? Clause 7.1 1 of ETSI EN 383 001 [10] o 10 map the REL cause value into the reason header field of a SIP message (BYE, CANCEL or SIP final response)? Clauses 6.11.2 and 7.7.1 of ETSI EN 383 001 [10] c41 11 map a received reason header fields included in a SIP message (BYE, CANCEL or SIP final response) to the ISUP cause value in the sent REL? Clauses 6.11.1 and 7.7.2 of ETSI EN 383 001 [10] c41 12 interwork the SIP Failure response to ISUP? Note 1 of table 40 in Rec. ITU-T Q.1912.5 [11] o 13 derive the Display-name in the "From header field" from the "additional calling party number" or "calling party number"? Clause 7.1.3/Table 28 in Rec. ITU-T Q.1912.5 [11] c41 14 control exchange for the Suspend procedure? Clause 6.9 of ETSI EN 383 001 [10] o 15 use internal resource reservations (preconditions used)? Clause 6.1.1 1) b) and 7.1 B, D of ETSI EN 383 001 [10] o 16 control charging? Clause 2.1.4.2 of Rec. ITU-T Q.764 [1] o 17 satisfy the call using a new address provided in a Contact header field received in a 3xx response? Clause 13.2.2.2 of RFC 3261 [7] o 18 perform transcoding of media stream at the I-IWU? Clause 6.1.3.5.1 of ETSI EN 383 001 [10] c42 19 refuse an offer with a 415 Unsupported media type response if more than one media type is received in a SDP? Clause 6.1.3.5.4 of ETSI EN 383 001 [10] c41 20 derive the Display-name in the "P-Asserted-Identity header field" from the "calling party number" or "additional calling party number"? Clause 7.1.3/Table 29 of ETSI EN 383 001 [10] o 21 redirect to a new destination according the BICC/ISUP requirements if a REL is received with cause 23? Clause 6.11.2/Table 21 of ETSI EN 383 001 [10] o 22 support the ISDN User Part availability control? Clause 2.13 of Rec. ITU-T Q.764 [1] o 23 in case of a TMR 64 kBit/s was received in the IAM, in the Forward call indicator the Interworking indicator is set to no interworking encountered, the ISDN user part/BICC indicator is set to ISDN user part/BICC used all the way, the ISDN access indicator is set to originating access ISDN? Clause 6.1.3.4 of ETSI EN 383 001 [10] o 24 in case of a TMR 64 kBit/s was received in the IAM, in the Backward call indicator the Interworking indicator is set to no interworking encountered, ISDN user part/BICC indicator is set to ISDN user part/BICC used all the way, the ISDN access indicator is set to terminating access ISDN? Clause 7.3.1.1 of ETSI EN 383 001 [10] o NOTE: c41: IF 1/9 THEN m ELSE o. c42: IF 1/2 (THEN IF 1/9 THEN n/a ELSE o) ELSE n/a. ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 17
|
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 service Connected Line Identification Presentation (COLP)? Annex B.2 o 4 support the service Connected Line Identification Restriction (COLR)? Annex B.2 o 5 support the service Call Hold (HOLD)? Annex B.10 o 6 support the service Terminal Portability (TP)? Annex B.13 o 7 support the service Closed User Group (CUG)? Annex B.16 o 8 support the service Sub-addressing (SUB)? Annex B.5 o 9 support the service Malicious Call Identification (MCID)? Annex B.4 o 10 support the service Conference Call, add-on (CONF)? Annex B.14 o 11 support the service Explicit Call Transfer (ECT)? Annex B.8 o 12 support the service Call Forwarding Busy (CFB)? Annex B.6 o 13 support the service Call Forwarding No Reply (CFNR)? Annex B.6 o 14 support the service Call Forwarding Unconditional (CFU)? Annex B.6 o 15 support the service Call Deflection (CD)? Annex B.6 o 16 support the service Call Waiting (CW)? Annex B.9 o 17 support the service Completion Call to busy subscriber (CCBS)? Annex B.11 o 19 support the Three-Party (3PTY) service? Annex B.15 o 20 support the service Completion Call on No Reply (CCNR)? Annex B.12 o 21 support the service Anonymous Call Rejection (ACR)? Annex B.22 c.51 22 support the interworking of the Closed User Group (CUG) supplementary service? Annex B.16 o 23 support the interworking of the User-to-User Signalling (UUS) supplementary service? Annex B.21 o NOTE: c.51: IF 1/9 THEN o ELSE n/a. ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 18 Table 6: Calling Line Identification (CLI) Item Is the exchange [role] able to ... Reference Status Support 1 include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format '+'CC+NDC+SN; address signal: network provided? Table 7 o 2 include a network provided E.164 calling party number if the P-Asserted -Identity header field has not been received or not in the format '+'CC+NDC+SN, the From header field is in the format '+'CC+NDC+SN; address signal: derived from the From header field? Table 7 o 3 include an additional calling party number if a From header field has been received in the format '+'CC+NDC+SN; address signal: derived from the From header field? Table 7 o 4 discard the calling party number in case of bilateral agreements if it is "presentation restricted"? Clause 3.5.2.3.1 of Rec. ITU-T Q.731.1 [16] o 5 discard the additional calling party number in case of bilateral agreements if it is "presentation restricted"? Clause 3.5.2.3.1 of Rec. ITU-T Q.731.1 [16] o 6 discard the calling party number, if the address is marked not available? Clause 3.5.2.3.1 of Rec. ITU-T Q.731.1 [16] o 7 discard the additional calling party number in case of bilateral agreements if it is "presentation allowed"? Network option o 8 discard the calling party number in case of bilateral agreements if it is "presentation allowed"? Network option o 9 send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation allowed" if no P-Asserted -Identity header field has not been received or if received it is not in the format '+'CC+NDC+SN? Table 7 o 10 send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation restricted" if no P-Asserted -Identity header field has not been received or if received it is not in the format '+'CC+NDC+SN? Table 7 c.61 11 send a Calling Party Number with an Number Presentation restriction Indicator set to "address not available" if no P-Asserted -Identity header field has not been received or if received it is not in the format '+'CC+NDC+SN? Table 7 o 12 send a Calling Party Number with an Number Presentation restriction Indicator set to "presentation restricted by the network" if no P- Asserted -Identity header field has not been received or if received it is not in the format '+'CC+NDC+SN? Table 7 c.62 NOTE: c.61: IF 1/9 THEN n/a ELSE o. c.62: IF 1/9 THEN o ELSE n/a. Table 7: COnnected Line identification (COL) Item Is the exchange [role] able to ... Reference Status Support 1 discard the connected number in case of bilateral agreements if it is "presentation restricted"? Clause 5.5.2.4.1 of Rec. ITU-T Q.731.5 [17] o 2 discard the additional connected number in case of bilateral agreements if it is "presentation restricted"? Clause 5.5.2.4.1 of Rec. ITU-T Q.731.5 [17] o 3 discard the connected number in case of bilateral agreements if it is "presentation allowed"? Network option o 4 discard the additional connected number in case of bilateral agreements if it is "presentation allowed"? Network option o 5 add a prefix to an international connected number? Clause 5.5.2.3.1 of Rec. ITU-T Q.731.1 [16] o ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 19 Table 8: HOLD Item Is the exchange [role] able to ... Reference Status Support 1 support that a party can put the other party on hold after alerting has commenced? Annex B.10 of Rec. ITU-T Q.1912.5 [11] o 2 support that a party can put the other party on hold after the calling user has provided all of the information necessary for processing the call? Annex B.10 of Rec. ITU-T Q.1912.5 [11] o 3 does the network support the hold and resume of media streams using the UPDATE method in the confirmed dialogue? Clause 5.1 [10] o Table 9: Malicious Call Identification (MCID) Item Is the exchange [role] able to ... Reference Status Support 1 return an IRS with bit A of the MCID response indicator set to 0 "MCID not included", if the network does not support the MCID service? Clause 7.5.2.3.2 of Rec. ITU-T Q.731.7 [3] o 2 held the IP bearer after the release of the call? Annex B.4 of Rec. ITU-T Q.1912.5 [11] o Table 10: Call DIVersion service (CDIV) Item Is the exchange [role] able to ... Reference Status Support 1 discard the original called number if case of bilateral agreements? Clause 3.5.2.3.1 of Rec. ITU-T Q.732.2 [4] o 2 discard the redirecting number if case of bilateral agreements? Clause 3.5.2.3.1 of Rec. ITU-T Q.732.2 [4] o 3 add a prefix to an international original called number? Clause 3.5.2.4.1 of Rec. ITU-T Q.732.2 [4] o 4 add a prefix to an international redirecting number? o 5 discard the redirection number in case of bilateral agreements? Clause 3.5.2.3.1 of Rec. ITU-T Q.732.2 [4] o Table 11: User-to-user service Item Is the exchange [role] able to ... Reference Status Support 1 understand an explicit user-to-user request? Clauses 1.1.5.2.5.2.2, 1.2.5.2.5.2.1 and 1.3.5.2.5.2.1of Rec. ITU-T Q.737.1 [6] c.111 2 support the rejection procedure of an explicit service request or discarding of user-to-user information as described in clause 1.1.5.x.5.2 of Rec. ITU-T Q.737.1 [6]? Clause 1.1.5.2.2.2 of Rec. ITU-T Q.737.1 [6] c.111 3 reject an user-to-user request service 3 not essential after call set-up using the FRJ message? Clause 1.3.5.2.5.2.2 of Rec. ITU-T Q.737.1 [6] c.111 NOTE: c.111 IF 5/23 THEN o ELSE n/a. Table 12: ECT Item Is the exchange [role] able to ... Reference Status Support 1 return a LOP (response) message with the indication "insufficient information"? Clause 7.7 of Rec. ITU-T Q.732.7 [5] o ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 20
|
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.764 [1] o Rec. ITU-T Q.118 [18] 5 ISUP T7 Annex A of Rec. ITU-T Q.764 [1] o 20 - 30 6 ISUP T9 Annex A of Rec. ITU-T Q.764 [1] o Rec. ITU-T Q.118 [18]
|
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. 7: Call Forwarding No Reply (CFNR)". • Recommendation ITU-T Q.732.4 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Forwarding Unconditional (CFU)". • Recommendation ITU-T Q.732.5 (1999): "Stage 3 description for call offering supplementary services using Signalling System No. 7: Call Deflection (CD)". • Recommendation ITU-T Q.733.1 (1992): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call waiting (CW)". • Recommendation ITU-T Q.733.2 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Call hold (HOLD)". • Recommendation ITU-T Q.733.3 (1997): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls to busy subscriber (CCBS)". • Recommendation ITU-T Q.733.4 (1993): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Terminal portability (TP)". • Recommendation ITU-T Q.733.5 (1999): "Stage 3 description for call completion supplementary services using Signalling System No. 7: Completion of calls on no reply". • Recommendation ITU-T Q.734.1 (1993): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Conference calling". • Recommendation ITU-T Q.734.2 (1996): "Stage 3 description for multiparty supplementary services using Signalling System No. 7: Three-party service". • Recommendation ITU-T Q.735.1 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Closed user group (CUG)". • Recommendation ITU-T Q.735.3 (1993): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Multi-level precedence and pre-emption". • Recommendation ITU-T Q.735.6 (1996): "Stage 3 description for community of interest supplementary services using Signalling System No. 7: Global Virtual Network Service (GVNS)". • Recommendation ITU-T Q.736.1 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: International Telecommunication Charge Card (ITCC)". • Recommendation ITU-T Q.736.3 (1995): "Stage 3 description for charging supplementary services using Signalling System No. 7: Reverse charging (REV)". • Recommendation ITU-T Q.850 (1998): "Usage of cause and location in the Digital Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part". • IETF RFC 2046 (1996): "Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types". • IETF RFC 2327 (1998): "SDP: Session Description Protocol". • IETF RFC 2806 (2000): "URLs for Telephone Calls". • IETF RFC 3204 (2001): "MIME media types for ISUP and QSIG Objects". • IETF RFC 3264 (2002): "An Offer/Answer Model with the Session Description Protocol (SDP)". • IETF RFC 3311 (2002): "The Session Initiation Protocol UPDATE Method". ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 22 • IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". • IETF RFC 3323 (2002): "A Privacy Mechanism for the Session Initiation Protocol (SIP)". • IETF RFC 3326 (2002): "The Reason Header Field for the Session Initiation Protocol". • ISO/IEC 9646-1 (1994): "Conformance testing methodology and framework - Part 1: General Concepts". • ISO/IEC 9646-2 (1994): "Conformance testing methodology and framework - Part 2: Abstract Test Suite Specification". • ISO/IEC 9646-3 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation". • ISO/IEC 9646-3/DAM 1 (1992): "Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation; Amendment 1: TTCN extensions". • ISO/IEC 9646-5 (1994): "Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". • Recommendation ITU-T Q.767 (1991): "Application of the ISDN User Part of CCITT signalling system No. 7 for international ISDN interconnections". ETSI ETSI TS 186 002-1 V1.1.5 (2014-10) 23 History Document history V1.1.1 February 2006 Publication V1.1.4 May 2008 Publication V1.1.5 October 2014 Publication
|
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-only numbers is a national matter and is not addressed in the present document. The document deals with "geographic country codes" (i.e. geographic areas or groups of countries) and their associated dialling plans, not with the international E.164 numbering plan as a whole. Non geographic country codes (such as country codes for networks) are not addressed in the present document. Clause 7 defines the normative statements for numbering use in NGN.
|
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 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.
|
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 Recommendation E.164 (2010): "The international public telecommunication numbering plan". [3] ITU-T Recommendation E.123 (2001): "Notation for national and international telephone numbers, e-mail addresses and Web addresses". [4] ITU-T Recommendation Q.3401 (2007): "NGN NNI signalling profile (protocol set 1)". [5] ITU-T Recommendation Q.3402 (2008): "NGN UNI signalling profile (protocol set 1)". [6] ETSI TS 184 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interconnection and Routeing requirements related to Numbering and Naming for NGNs; NAR Interconnect". [7] ETSI TS 124 229(V8.7.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 8.7.0). [8] ETSI TS 123 228: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) Stage 2 (3GPP TS 23.228)". [9] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". ETSI ETSI TS 184 011 V3.1.1 (2011-02) 6 [10] ETSI TS 182 024: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Hosted Enterprise Services; Architecture, functional description and signalling". [11] IETF RFC 3966: "The tel URI for Telephone Numbers". [12] IETF RFC 3261: "SIP: Session Initiation Protocol". [13] IETF RFC 4967: "Dial String Parameter for the Session Initiation Protocol Uniform Resource Identifier".
|
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 Resolution (NAR)". [i.2] IETF RFC 1034: "Domain Names - Concepts and Facilities". [i.3] IETF RFC 1035: "Domain Names - Implementation and Specification".
|
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]. local number: National E.164 number or a national-only number as defined in ITU-T Recommendation E.101 [1] and described in RFC 3966 [11]. tel URI: As defined in RFC 3966 [11]. SIP URI: As defined in RFC 3261 [12] and reflected also in clause 4.2 TS 124 229 [7].
|
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 Services Digital Networks N(S)N National (Significant) Number NAR Naming and Addressing Resolution NDC National Destination Code NGCN Next Generation Corporate Network ETSI ETSI TS 184 011 V3.1.1 (2011-02) 7 NGN Next Generation Network NNI Network-Network-Interface NPA Numbering Plan Administrator PLMN Public Land Mobile Network PSTN Public Switched Telephone Network SIP Session Initiation Protocol SIPS SIP Secure SN Subscriber Number UE User Equipment UMTS Universal Mobile Telecommunications System UNI User-Network-Interface URI Uniform Resource Identifier
|
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 international E.164 number. International E.164 numbers are numbers based on ITU-T Recommendation E.164 [2] and are used in different network environments like PSTN, ISDN, and PLMNs based on GSM and UMTS, and are also used in NGNs as public identifiers. The international E.164 number uniquely identifies a subscriber or a point where a service is provided and satisfies the three characteristics of structure, number length and uniqueness as specified in E.164 [2]. The maximum number of digits for the E.164 number is 15 excluding the international prefix. International E.164 numbers are presently used in five different structures and these are described in detail in E.164 [2]: • International E.164-number for geographic areas. • International E.164-number for global services. • International E.164-number for Networks. • International E.164-number for Groups of Countries. • International E.164-number for Trials. The structure of the international E.164 number for geographic areas, as an example, is shown below taken from ITU-T Recommendation E.164 [2]: Figure 1: International E.164 number structure for geographic areas ETSI ETSI TS 184 011 V3.1.1 (2011-02) 8 An E.164 number of the own country can be used in different formats by the users and operators, the ones corresponding to: international level, national level and local level. Which of these formats are usable is dependant on the national E.164 numbering plan and the dialling plan. The following three notes describe the different formats which are national specifics: NOTE 1: International level: Some networks allow to dial the national E.164 numbers of the own country in the international format by using the international prefix. NOTE 2 National level: On the national level the number is used in the national (significant) number [N(S)N] format, i.e. the National Destination Code (NDC) and the Subscriber Number (SN), possibly together with the national (trunk) prefix. NOTE 3 Local level (Subscriber number): In some national dialling plans, using an open dialling plan, a user may also dial an E.164 number in the local format. This means dialling just the subscriber number (SN) without any national destination code. This dialling procedure might not be applicable in some countries and networks, using closed dialling plans. In this case, there is always an NDC required to access other national E.164 numbers in the same area. Countries with a closed dialling plan do not have a local format. This may also be the case for certain networks (mostly mobile networks). In some countries with a closed dialling plan there is no NDC required to be dialled.
|
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 formats and coding (see [4], [5] and [7]). As a consequence, for routeing purpose, tel URI and SIP URI have to be mapped to appropriate IP addresses, associated to control/service functional entities, for communication establishing. In the ETSI's NGN context, both tel URI and SIP URI are to be considered the "naming" schemes and SIP coding for E.164 numbers. The basic coding for E.164 numbers in SIP are the following: • tel: <telephone-subscriber> for the purpose of the present document the <telephone-subscriber> is addressed by a "global number" or "local number". • sip: <user info>@<domain>;user=phone For the purpose of the present document the <user info> is an E.164 number. The <domain> shall be a string that identifies the operator serving the end user identified by the E.164 number on a contractual basis, following the rules on Internet domain names for the domain administration (see [i.2] and [i.3]). Figure 2 describes the basic scenario that shows the exchange of E.164 format information at UNI and NNI in ETSI NGN functional architecture [9]. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 9 Figure 2: E.164 formats and SIP coding in NGN The basic formats which can be used at the UNI are the following: • International E.164 number: when the E.164 number is used in the international format, defined in Figure 1 (CC+NDC+SN), tel URI and SIP URI shall use the "global" coding defined in [11]. • National E.164 number: tel URI and SIP URI shall use the "local" coding defined in [11]. • Subscriber Number: tel URI and SIP URI shall use the "local" coding defined in [11]. For interconnection between NGNs (NNI) there exist two distinct cases: • National interconnection – interconnection between operator networks belonging to the same country; • International interconnection – interconnection between operator networks belonging to different countries. "The "global" number coding for E.164 numbers shall be used at the national and international NNI. The number format coding of the national interconnection NNI has also to take in account national requirements that are partially covered in the document. Based on a national common agreement by Numbering Plan Administrator (NPA) for national NNI other number coding formats (in particular local number coding) for E.164 numbers can be used."
|
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 networks. In case a number is delivered at NGN UNI, the NAR [i.1] translation function, realized inside the operator's domain, shall resolve such a number into a SIP URI or a tel URI coding, which enables the use of other steps of routeing process, also for interconnection scenarios. In case a number is delivered at the PSTN/ISDN or PLMN UNI, no new requirements are provided on PSTN/ISDN and, in the case of interworking with NGN, the numbering translation function at appropriate border gateways and interworking functional entities will provide tel URI or SIP URI coding on SIP. See the following clauses for normative requirements. The basic numbering format for interconnection of international NGN networks shall be compliant to the Q.3401 Recommendation [4] and compliant to the following coding: • tel: +<country code><national E.164 number> • sip: +<country code><national E.164 number>@<operator-domain>;user=phone NOTE 1: The "user=phone" parameter is a SIP URI parameter used coherently with [7]. UE NGN A NGN B UNI NNI E.164 Formats and SIP Coding between UE and NGN E.164 Formats and SIP Coding between NGNs ETSI ETSI TS 184 011 V3.1.1 (2011-02) 10 Both tel URI and SIP URI shall be adopted for the coding of international E.164 numbers for the international interconnection [6]. The operator-domain naming component identifies the operator serving the end user identified by the E.164 number on a contractual basis. In principle, both Originating and Terminating party identifiers shall be provided at interconnection NNI. They shall be coded in the SIP-header "P-Asserted-Identity" and in the "Request-URI", respectively. NOTE 2: The "P-Asserted-Identity" SIP header can be omitted in case of a not trusted relationship between networks. E.164 number identifiers based on tel URI and SIP URI codings are handled to address NAR [i.1] for routeing process and routable SIP URI determination [7], based on I-ENUM, as described in clause 4.3.5 of TS 123 228 [8], or on another translation mechanism or existing solutions.
|
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 international prefix, but some countries use a different international prefix. In ITU-T Recommendation E.123 [3] the "+" character is used as symbol for such international prefix. For dialling, if "+" character is used, it corresponds to the international prefix used in the applicable dialling plan. Also in RFC 3966 [11] the "+" character identifies the global number format (equivalent to international format basing on ITU-T terminology) and ITU-T Recommendation E.123 [3] meaning applies.
|
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 national matter; this format may be supported at NGN UNI, if it is required by national E.164 numbering and dialling plans. ETSI's NGN shall be compatible with national E.164 numbering plans and shall implement the necessary functionality using NAR numbering translation functions. Certain national numbering plans use only the national E.164 number format for any national communications, also inside local areas (for instance inside districts). In this case NDC does not exist. Other national numbering plans use both national and subscriber number formats. In this case a national (trunk) prefix exists. The structure of a national E.164 number is defined by ITU-T Recommendation E.164 [2] and typically consists of an area code and a subscriber number and, if it is required by the dialling plan, a national (trunk) prefix can be used. When it is defined in a specific national numbering plan coherently with ITU-T Recommendation E.164 [2], the subscriber number is unique only within a local area (generally inside a district). It becomes unique at the national level by inserting an appropriate area code in front of the subscriber number. If E.164 numbers in the national format need to be converted to international E.164 numbers, the ITU-T associated country code shall be inserted in front of the national E.164 number. As stated in ITU-T Recommendation E.164 [2] national and international prefix are never part of the number and they are only defined in the national dialling plan. The formats and the codings for national interconnection sum up to: 1. tel: <national E.164 number>;phone-context=+<country code> 2. sip: <national E.164 number>;phone-context=+<country code>@<operator-domain>;user=phone NOTE 1: The "user=phone" parameter is used coherently with [7]. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 11 NOTE 2: The "phone-context" is a tel URI parameter which is used coherently with [7]. The actual routeing of the call will be done basing upon the "national E.164 number" coding in a tel URI format, or basing upon the "national E.164 number" coding and the "operator domain" in a SIP URI format. Or 3. tel: +<country code><national E.164 number> 4. sip: +<country code><national E.164 number>@<operator-domain>;user=phone NOTE 3: The "user=phone" parameter is used coherently with [7]. It is required that: • The operator-domain name, coherently with Internet domain names administrative rules, identifies the operator serving the end user identified by the E.164 number on a contractual basis. NOTE 4: In certain cases on a bilateral agreement, e.g. when a transit network is used, the operator-domain can also be the domain of the transit network. • The value of <country code> shall be the ITU-T associated country code. • Both tel URI and SIP URI shall be adopted for the coding of national E.164 numbers at national interconnection. After numbering and addressing resolution through NAR functionalities, routable SIP-URI coding applies, and tel URI is mainly used to indicate to next hop network that further NAR numbering and addressing resolution is to be applied to identify final destination of the ongoing session/communication [i.1]. NOTE 5: The support of E.164 international and national formats at national NNI is a national matter. In principle, both Originating and Terminating party identifiers shall be provided at interconnection NNI. They shall be coded in the SIP-header "P-Asserted-Identity" and in the "Request-URI", respectively. NOTE 6: The "P-Asserted-Identity" SIP header can be omitted in case of a not trusted relationship between networks. National Interconnection NGN may support also routeing number formats, as a national option, included in both tel URI and SIP URI codings. The tel URI and SIP URI codings shall support the routeing number formats [6]. 5.4 Use of dialled digits for the determination of valid coding formats for E.164 number 5.4.1 Format of the Request URI at UNI The following UE capabilities are considered to determine the coding for the Request URI at UNI with regard to E.164 number format: • UE without dial string processing capabilities, that is the UE does not perform any analysis of the dialled string: in this case the dialled string is forwarded to the network at UNI using a tel URI or SIP URI, to be processed by the network. The URI content is in the RFC 3966 [11] local number format unless a "+" sign has been received in which case the RFC 3966 [11] global format is used. This is the "preferred" UE behaviour to assure global compatibility with networks in different countries. • UE with dial string processing capabilities, that is the UE is able to perform sufficient dialled string analysis, based also on possible explicit indication from the user regarding used number formats: in this case the UE recognizes the dialled number on the basis of national numbering plan rules and encodes the corresponding E.164 number in SIP, using tel URI or SIP URI, with the correct SIP header numbering format (i.e. local or global value, etc.). The UE shall remove prefix or escape codes for private network, following the national numbering and dialling plan rules. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 12 NOTE 1: If the UE detects that a local (private or public) dialling plan is being used, it may decide to send the dial string unchanged to the network or the UE may decide to alter it to comply with the national numbering plan (e.g. to remove all the dial string elements used for local numbering detection). The coding formats sent by the UE at the UNI in the case of called party identifier are the following: • If the output coding from the UE is a tel URI then: - UE without dial string processing capabilities: tel URI includes dialled digits and a phone-context provisioned at registration or by the operator. The required Request URI codings that may be supported are the following: tel: <dialled digits>;phone-context=<operator-provisioned-context> - UE with dial string processing capabilities and tel URI coding: the output is always a valid E.164 number and the required Request URI codings are the following: In case of international E.164 number: tel: +<CC><National E.164 number> (global format) In case of national E.164 number: tel: <National E.164 number>;phone-context=<context-value> (local format) NOTE 2: The <context-value> can be the string "+<CC>" where <CC> corresponds to the country where the UE is located or has a subscription or can be a value determined as specified in TS 124 229 [7], clause 5.1.2A.1.5 when the UE is connected to an IMS. Tel: +<CC><National E.164 number> (global format). In case of E.164 subscriber number: tel: <SN> (local format);phone-context=<context-value> where <CC> corresponds to the value of the ITU-T country code of the country where the UE is located or has a subscription. NOTE 3: The <context-value> can be the string "+<CC><NDC>" where <CC> corresponds to the country where the UE is located or has a subscription or can be a value determined as specified in TS 124 229 [7], clause 5.1.2A.1.5 when the UE is connected to an IMS. • If the output coding from the UE is a SIP URI: - UE without dial string processing capabilities: SIP URI coding contains the dialled digits, the phone context, the domain name of the originating operator or service provider and the user parameter "user=dialstring" [13]. The value of phone context and the home domain are provisioned at least at registration. Sip: <dialled digits>;phone-context=<operator-specific-context>@<operator- domain>;user=dialstring - UE with dial string processing capabilities: In case of international E.164 number, the required Request URI coding is the following: sip: +<CC><National E.164 number>@<operator-domain>;user=phone In case of national E.164 number: sip: <National E.164 number>;phone-context=<context-value>@<operator- domain>;user=phone (local format) sip: +<CC><National E.164 number>@<operator-domain>;user=phone (global format) with <CC> corresponding to the ITU-T country code of the country where the UE is located or has a subscription. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 13 NOTE 4: The <context-value> can be the string "+<CC>" where <CC> corresponds to the country where the UE is located or has a subscription or can be a value determined as specified in TS 124 229 [7], clause 5.1.2A.1.5 when the UE is connected to an IMS. In case of dialling an E.164 subscriber number: sip: <SN>;phone-context=<context-value>@<operator-domain>;user=phone (local format) NOTE 5: The <context-value> can be the string "+<CC><NDC>" where <CC> corresponds to the country where the UE is located or has a subscription or can be a value determined as specified in TS 124 229 [7], clause 5.1.2A.1.5 when the UE is connected to an IMS. In the case of Originating party identifier, the UE can be able to forward an E.164 number at UNI corresponding to the user subscription. When the UE forwards at UNI an Originating identifier, the UE uses tel URI or SIP URI coding, adhering to previously defined formats and codings. It is the task of the network at UNI to verify the received Originating identifier (if any), through appropriate screening functions, and to certify Originating identifier to be forwarded through the own network and towards other interconnected networks. There may be an UE sending URI without global context, such a case is not foreseen in RFC 3966 [11]. Based on operator policy, and national choices, in such cases the NGN has to add the phone-context. How to add the phone context is out of scope of this specification.
|
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-context parameters. 2. If a local number is used and the <CC> value of the phone-context parameter is recognized as not being equal to the ITU-T associated country code of the originating country, the call/session is considered an "International call/session", otherwise a "National call/session". If a global number is used and <CC> value is recognized as being equal to the ITU-T associated country code of the originating country, then the call/session is considered a "National call/session"; if not, then it is an "International call/session". 3. Look up the number in the own databases to determine, both for tel URI and SIP URI: 3.1 If the number is served by the own network of the operator domain, then the Request URI corresponds to the own domain (operator domain) and the user parameter is set to "user=phone". The output is a Routable SIP URI [6] and [7]. 3.2 If the number is served by another network, numbering and addressing resolution functionality is applied to determine an appropriate routable SIP URI (see [6]) towards next hop network or to the final destination. 5.5 Numbering and Addressing Resolution function for E.164 numbers Numbering and Addressing Resolution functions for tel URI and SIP URI are provided by TS 184 006 [6] and other NGN standards and specifications. NAR functions are in the responsibility of control function (CSCF), also located in Border Gateway functionalities in the case of inter-operators communication sessions. Different implementations of translation functions can be realized by operators, based on Naming and Addressing Resolution (NAR) process described in [i.1]. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 14
|
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 belong to the international and national E.164 numbering plan and the last digits correspond to the private numbering plan. This however does not apply to all private/corporate networks. In most of these private/corporate networks also the NGN can be accessed. To do so, a prefix (for instance "0" or "9") is defined. This prefix provides access to the national or international formats E.164 numbers. Private networks have to comply for their external communications with the rules of national and international E.164 numbering plans and no specific requirements are imposed by ETSI NGN. A private numbering plan is in principle defined to be used inside the private networks. As a general rule, only a private numbering plan integrated inside national E.164 numbering plan (i.e. direct dialling in) guarantees to be reachable by other national and international public networks. If NGCNs have their own (proxy) control function entity, it is assumed that numbers are delivered to the public NGN domain in a format coherent with national numbering plan rules. If an NGCN is handled through public NGN functions [10], the hosting NGN has to manage any private dialling plan. Appropriate SIP protocol coding for private calling and called identifiers, that guarantees to separate private numbering from public E.164 numbering plans, shall be used; specific SIP protocol coding could be defined but it is out of the scope of the present document.
|
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 tel URIs. Since all considerations here for SIP URIs apply equally to SIPS URIs, only SIP URIs and tel URIs are discussed in the rest of the present document. Number based SIP URIs where the user part represents a telephone subscriber string has global significance irrespective of the host part. This fact has led to the domain name being largely neglected when inspecting such a SIP URI, and modifying the domain name has become common practice in such circumstances. In the NGCN context this applies to E.164 number based SIP URIs and to those containing private numbers that are formatted as telephone subscriber string. The considerations below distinguish between URIs with an enterprise's own domain name and URIs where the domain name is that of the enterprise's trunking NGN provider. Table 1 summarizes the examples of usage of E.164 number formats in a NGCN. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 15 Table 1 Case Identifier SIP URI TEL URI 1 E.164 number tel: <National/ E.164 number>;phone-context= +<CC> or +<CC><NDC> 1a Private enterprise domain sip: <National number (including DDI digits)>;phone- context=+<CC>@example.com;user=phone 1b Public NGN sip: <National E.164 number>;phone- context=+<CC>@<operator- domain>;user=phone 1c Private enterprise domain sip: <international E.164 number>@example.com;user=phone tel: +<international E.164 number> 1d Public NGN sip: <international E.164 number>@<operator-domain>;user=phone The formats and coding rules for E.164 numbers are defined in clauses 5.4.1 and 5.4.2.
|
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 national interconnection NNI has also to take in account national requirements that are partially covered in the document. Based on a national common agreement by Numbering Plan Administrator (NPA) for national NNI other number coding formats (in particular local number coding) for E.164 numbers can be used." - NGN shall allow access to private/corporate networks using E.164 compatible numbering plans. 2) NGN shall support the internal functionality to differentiate alphanumerical identifiers, belonging to a recognized public naming scheme, that happen to be consisting of only digits from those which are numbers (e.g. E.164 numbers) and should be treated as necessary in routeing procedures. 3) In some service scenarios, e.g. interworking with PSTN/ISDN, the NGN shall support multimedia communication establishment (in both the originating and terminating case) using E.164 numbering with suited Numbering and Addressing Resolution (NAR) functions, including I-ENUM system or other equivalent Data Base based solutions where appropriate. 4) Originating and Terminating party identifiers shall be provided at interconnection NNI. They shall be coded in the SIP-header "P-Asserted-Identity" and in the "Request-URI", respectively. Note: The "P-Asserted-Identity" SIP header can be omitted in case of a not trusted relationship between networks. 5) If SIP URI coding is received on the NNI, then appropriate NAR resolution functionality may be applied by the network to determine the Routable SIP URI [6]. If tel URI coding is received on the NNI, then appropriate NAR resolution functionality shall be applied by the network to determine the Routable SIP URI [6]. 6) If SIP URI or tel URI coding is received on the UNI, it shall always be verified and handled for routeing and charging purposes by network control functions. An appropriate NAR resolution functionality shall be applied by the network to determinate the Routable SIP URI [6]. 7) The SIP parameter "user=dialstring" [13] coding can be used only at UNI. At interconnection NNI it shall not be used. ETSI ETSI TS 184 011 V3.1.1 (2011-02) 16 Annex A (informative): Use of private numbers in the NGCN A private numbering plan that does not overlap with an E.164 numbering plan can only be used inside a corporate network. Private numbers may appear at an NGN interface in the following two cases: • business trunking, where the NGN provides connectivity between NGCN sites; in this case private numbers are transparent to the NGN, there is no need to understand them; • hosted enterprise network, where the NGN provides private network services, including private numbering, to a company; in this case the use of private numbers is restricted to the hosted enterprise application, and the NGN has to prevent their use in any other context. In any case private numbers that appear in a SIP or tel URI can be distinguished from other (e.g. E.164) numbers by means of a domain name or a phone context identifying the enterprise that owns that private numbering plan. Table A.1 summarizes the examples of usage of private identifier formats in a NGCN. Table A.1 Case Identifier SIP URI TEL URI 1 Private number 1a Using private network functionalities. Sip: <dialled string>;phone- context=<enterprise number>@example.com;user=dialstring sip: <private number>;phone-context= <enterprise number>@example.com;user=phone sip: <dialled string>;phone-context= example.com @example.com;user=dialstring sip: <private number>; phone-context= example.com @example.com;user=phone sip:< dialled string or private number>@example.com tel: <dialled string or private number>; phone- context=<enterprise number> tel: <dialled string or private number>;phone- context=example.com 1b Using public NGN functionalities. Sip: <dialled string >;phone-context= <enterprise number>@<operator- domain>;user=dialstring sip: <private number>;phone-context= <enterprise number>@<operator- domain>;user=phone sip: <dialled string >;phone-context= example.com@<operator- domain>;user=dialstring sip: <private number>;phone-context= example.com@<operator- domain>;user=phone Definitions: <dialled string>: the string of digits dialled by the user <private number>: a number of the private numbering plan <enterprise number>: the (international) E.164 number assigned to the NGCN ETSI ETSI TS 184 011 V3.1.1 (2011-02) 17 Annex B (informative): Bibliography ETSI TS 184 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Identifiers (IDs) for NGN". ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". ETSI TR 184 005 (V1.1.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Types of numbers used in an NGN environment". ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". ETSI TS 129 165: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Inter-IMS Network to Network Interface (NNI) (3GPP TS 29.165)". ETSI ETSI TS 184 011 V3.1.1 (2011-02) 18 History Document history V3.1.1 February 2011 Publication
|
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 for ETSI TISPAN compliant networks. It is important that all potential Carriers' IPX implementations, ongoing in the market, should take account of ETSI NGN standards and specifications in order to ensure different "NGN implementations" may interoperate together. The present document analyses a particular case of numbering and naming resolution for use by NGN Communications Providers when providing indirect interconnection as specified in ES 282 001 [18] and covers the need for a standard solution to address numbering and naming resolution implemented through an ENUM/DNS solution for this particular case. A TISPAN IPX does not currently exist. It should not be assumed from the present document that ETSI would look to set in place an ETSI specific IPX, but the detailed requirements and approach set out within this document will ensure that ETSI is able to assess the options in moving forward. No decision on the way forward has yet been taken. However within ETSI there is strong recognition of the benefits that can be gained from adopting a combined approach with other parties providing the requirements specified by ETSI TISPAN can be accommodated. The present document would also allow an assessment to be made against the approach that is currently planned to introduce an IPX by the GSMA. Whilst the document details possible sub-domains that an operator may use they should only be viewed as possible examples. The present document does not put constraints on commercial models. The present document describes an Infrastructure ENUM that need not to be based on an Interoperator IP backbone, but it is managed by a confederation of operators also on the basis of a distributed architecture. As a consequence the applicability of the references to the Interoperator IP backbone network should be evaluated based on the operator's ENUM implementation.
|
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 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.
|
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: "Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database". [4] IETF RFC 3404: "Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)". [5] IETF RFC 3263: "Session Initiation Protocol (SIP): Locating SIP Servers". ETSI ETSI TS 184 010 V3.1.1 (2011-08) 7 [6] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)". [7] ETSI TS 129 421: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; NGN Release 1; Endorsement of 3GPP TS 29.162 Interworking between IM CN Sub-system and IP networks (3GPP TS 29.421)". [8] ETSI TS 184 011: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Requirements and usage of E.164 numbers in NGN and NGCN". [9] IETF RFC 3261: "SIP: Session Initiation Protocol". [10] IETF RFC 3966: "'The Tel URI for Telephone Numbers". [11] IETF RFC 4355: "IANA Registration for Enumservices email, fax, mms, ems, and sms". [12] IETF RFC 3764: "enumservice registration for Session Initiation Protocol (SIP) Addresses-of- Record". [13] IETF RFC 4769: "IANA registration for an ENUM service containing Public Switched Telephone Network (PSTN) Signalling Information". [14] ETSI TS 187 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements". [15] IETF RFC 2671: "Extension Mechanisms for DNS (EDNS0)". [16] IETF RFC 5358: "Preventing Use of Recursive Nameservers in Reflector Attacks". [17] IETF RFC 5452: "Measures for Making DNS More Resilient against Forged Answers". [18] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture".
|
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 converged Services and Protocols for Advanced Networking (TISPAN); Portability of telephone numbers between operators for Next Generation Networks (NGNs)". [i.4] IETF RFC 3824: "Using E.164 numbers with the Session Initiation Protocol (SIP)". [i.5] ETSI TR 184 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Types of numbers used in an NGN environment". [i.6] ETSI TR 184 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Infrastructure ENUM Options for a TISPAN IPX". [i.7] ETSI TR 187 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); TISPAN NGN Security (NGN-SEC); Threat, Vulnerability and Risk Analysis". [i.8] ETSI TR 187 010: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Report on issues related to security in identity imanagement and their resolution in the NGN". ETSI ETSI TS 184 010 V3.1.1 (2011-08) 8 [i.9] ETSI TS 184 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Interconnection and Routeing requirements related to Numbering and Naming for NGNs; NAR Interconnect".
|
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 "International Networks" (+882) or "Universal Personal Telecommunications (UPT)" (+878) NOTE: In the case that the number is ported the carrier of record maybe changed due the national number portability (NP) policies. It is understood that the definition of carrier-of-record within a given jurisdiction is subject to modification by national authorities. Communications Provider (CP): any entity providing communications services to 'End Users' and using a network to provide routeing capabilities delegation: when a part of a zone is maintained separately, it is delegated to a new nameserver that will have authority of that part of the domain namespace NOTE: The original zone will have the nameserver (NS) record for the delegated domain and the new sub-zone will have a new Start Of Authority (SOA) record. DNS Client: See "DNS Resolver". DNS Resolver: also known as a "DNS Client", this is an entity that is attempting to resolve a given domain name to an address or vice versa NOTE: Usually the DNS Resolver is connected to a local DNS caching server that performs the DNS look-ups on behalf of the DNS Resolver. Application programs use function calls, such as 'gethostbyname', to find the IP address representing a domain name. The name may be specified either as a Fully Qualified Domain Name (FQDN) or only partially. In the latter case, the DNS Resolver appends (a) configured local domain name(s) at the end of the name. DNS Server: can be a Nameserver, a Local Caching DNS Server or both domain name: consists of two or more labels separated with a dot ('.') character NOTE: It starts from the least significant domain on the left, and ends with the most significant domain (or top- level domain) on the right. This naming convention naturally defines a hierarchy. interoperator IP backbone provider: provider of a transit network or transit services that does not offer "services" to end users, but offers pure IP connectivity or session-based service interconnection to Communications Providers nameserver: takes care of DNS Queries sent by DNS Resolvers NOTE: The query is answered by using locally stored information (either configured locally or cached from a previous query result), by requesting the information from another DNS Server, or by providing the DNS Resolver with the details of another DNS Server to query. One Nameserver can serve (i.e. be authoritative for) several domains. There may also be several Nameservers serving one domain (Usually one Nameserver is the Primary and the other/rest are Secondaries. The Seconedary Namersever request authoritative DNS data from the Primary Nameserver due to a configured DNS data update process.). ETSI ETSI TS 184 010 V3.1.1 (2011-08) 9 Shared ENUM Infrastructure: Inter-operator infrastructure according to ENUM technology as defined in RFC 6116 [2], used by the originating or an intermediate network to map a specific E.164 number into a URI that identifies a specific entry point into the network actually serving that specific E.164 number NOTE: Carrier ENUM infrastructure is different from user ENUM infrastructure where the end-user may register his E.164 number to be associated with a URI of his desire. zone: DNS is a distributed database that contains information of each domain name NOTE: Each DNS server maintains a part of the database called a zone. Usually a zone contains information of one domain. However, one zone may contain information about many (sub)domains. Each information element is stored in a record that contains at least a domain name and type (which includes type specific information).
|
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 DNS Domain Name System ENUM Telephone Number Mapping FQDN Fully Qualified Domain Name GSMA Global System for Mobile Communications (GSM) Association GTP GPRS Tunnel Protocol HTTP Hyper Text Transfer Protocol IANA Internet Assigned Numbers Authority I-CSCF Interrogating - Call Server Control Function IDNA Internationalized Domain Names for Applications IMS IP Multimedia sub-system IP Internet Protocol IPSec Internet Protocol Security IPv4 Internet Protocol Version 4 IPv6 Internet Protocol Version 6 IPX IP Packet eXchange MGCF Media Gateway Control Function MMS Multimedia Messaging Service NAI Network Access Identifiers NAPTR Naming Authority PoinTeR NGN Next Generation Network NP Number Portability NS Name Server P-CSCF Proxy - Call Service Control Function PLMN Public Land Mobile Network QoS Quality of Service RTP Real-Time Transport Protocol S-CSCF Server - Call Session Control Function SEG Security gateway SIP Session Initiation Protocol SIP(S) Session Initiation Protocol (Secure) SLA Service Level Agreement SMTP Simple Mail Transfer Protocol SOA Start Of Authority TCP Transport Control Protocol UDP User Datagram Protocol UPSF User Profile Server Function ETSI ETSI TS 184 010 V3.1.1 (2011-08) 10 URI Uniform Resource Identifier VPN Virtual Private Network
|
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 document describes the usage of DNS/ENUM in a shared infrastructure. Nevertheless some general DNS/ENUM protocol requirements are also applicable in a provider local DNS/ENUM infrastructure. An inter-operator IP backbone network provides a method of supporting interconnectivity of IP based services and interconnection between different IMS based IP networks. Many, if not all, of these services rely upon DNS. Therefore, it is of utmost importance for the interworking and stability of such services that operators have all the necessary information to hand to ease configuration of their DNS servers that are connected to the Interoperator IP backbone network for each IP based service provided. The present document consists of an overview of DNS in relation to the successful interworking of fixed network services, the configuration of DNS servers, and procedures that would assist in the configuration and usage of domain names and DNS Servers within an inter-operator IP backbone network. This network is viewed as a key enabler for the support of full interconnectivity between communications providers. Whilst competing, Communications Providers deploying Next Generation Networks have the common objective of delivering traffic to each other in a profitable and cost effective manner. This will enable their customers to realise the full value of these services and comply with regulatory conditions that are applied to these services/networks. The common protocol for these networks is IP. Two basic possibilities exist for Interconnection between communication providers on the network layer as specified in ES 282 001 [18]: • Direct connection between two NGN Communication Providers on a bilateral basis (e.g. often using leased lines and VPN connectivity). • Indirect Connection via an Interoperator IP backbone network which facilitates interconnectivity for Communication Provider networks. Such indirect interconnection is isolated from the Internet. Security rules are defined to prevent unintended access to it. These two options are not mutually exclusive and it is a commercial decision which method Communications Providers use. The benefits of connectivity via an IPX include the ability to reach different interworking partners across the globe via one connection. These two options are not mutually exclusive and it is a commercial decision which method Communications Providers use. The benefits of connectivity or "session-based" services via an Interoperator IP backbone provider include the ability to reach different communication providers using a single network connectivity agreement. To ensure interoperability of all Communications Providers connected to the Interoperator IP backbone network will need to adhere to a set of common rules. These include rules regarding architecture functionalities, protocols, numbering and IP addressing resolution mechanisms, routeing, security, QoS, etc. The Interoperator IP backbone provider does not offer "services" to end users, but offers pure IP connectivity or session-based service interconnection to Communications Providers, and may provide transport functions required to enhance that interconnection, for example ENUM & DNS functionalities, numbering resolution mechanism, routeing capabilities and, if required, Triggering functionalities (see TS 184 006 [i.9]). Direct Connectivity between Communications Providers is a viable alternative defined in ETSI TISPAN NGN standards and specifications, but it is outside of the scope of the present document. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 11 The IPX is isolated from the Internet and security rules are defined to prevent unitended access from it. An interoperator IP Backbone network could be operated by any qualified party. The IP backbone network is expected to support Quality of Service features end to end, which requires parties involved in the transport of a service up to the terminating user equipment, to be bound by service level agreements.
|
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 so wish. Each Slave Root DNS Server is synchronised with a "back-end" Root DNS Server known as the "Master Root". This is known as a "Zone Transfer" and ensures that the data is the same in all interconnected Communication Providers. Figure 1 depicts this. Queries/Responses Communication Provider 1 Communication Provider 2 CShared ENUM Infrastructure Master Root Slave Root Master Zone File Zone Transfers NNI NNI Other Intermediate Network NNI NNI Slave Root Master/slave Root Other shared ENUM Infrastructure Intermediate Network(s ) Local DNS Figure 1: Backbone Architecture The ENUM&DNS is completely separate and autonomous from the DNS infrastructure of public Internet to be managed for QoS, availability, security, as required. Communication Providers will define a bilateral agreement with the Interoperator IP backbone network provider to manage access procedures to the ENUM&DNS servers for the numbering, naming and addressing resolution. The access to the Inter-operator IP Backbone network infrastructure and functionalities (for instance to ENUM/DNS, etc.) and related data population is limited to Communication Provider interconnected with specific Inter-operator IP backbone network eventually also in charge for NAR resolution and routeing determination. The data in the Master Root DNS Server is known as the Master Zone File. Access to the master Zone file will only be available to parties authorised to perform that role by the Interoperator IP backbone providers/Communications Providers. The population of the data that goes into the Master Zone File has a number of sources, mainly from Communications Providers, and Interoperator IP backbone providers acting on their behalf. It also needs to be policed and validated to ensure integrity of the sub-domain allocation and usage. Communications Providers can also query the root directly. Figure 2 showing the overall process architecture depicts the administration of the name server information that is required to populate the master root and slave servers. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 12 NO 3 Interoperator IP backbone Provider 1 Master Root DNS Server IPX Providers Interoperator IP backbone DNS Master Zone File Operators DNS Interface s Administration Interface s Problem Queries N S Info Slave Root DNS NO 1 Local DNS NO 2 Slave Root DNS & Local DNS Policing Operational Support Zone Transfers DNS Queries /Responses N S Info Zone Transfers Zone Transfers Zone Transfers Slave Root DNS & Local DNS Problem Queries Interoperator IP backbone Provider 1 Slave Root DNS Figure 2: Overall Process Architecture 4.3 IP Connectivity and Service-oriented interconnection services The Interoperator IP backbone network may permit three connectivity options: • Transport-Only Connectivity • Bilateral Service Transit Connectivity • Multilateral Service Transit for pure IP connectivity or "session-based" services Transport only connectivity Communication Providers interconnected indirectly using the Inter-operator IP backbone network with guaranteed QoS. This model is not service aware and it can be used to transport general IP traffic between two Communications Providers (provided compliance with security requirements is maintained). Bilateral Service Transit connectivity for pure IP connectivity or "session-based" services A bilateral agreement between Communications Providers interconnected indirectly for specific 'session based' services using as a transit operator the Interoperator IP backbone provider with guaranteed QoS. This model provides the opportunity to include service based interconnect charging in addition to the transport charging of the transport only model. Multilateral service transit for pure IP connectivity or "session-based" services Communications Providers interconnected indirectly for specific "session-based" services using as a transit operator the Inter-operator IP backbone network with guaranteed QoS. In this case the transit service is a multilateral one among Communication Providers. In order to support interworking of IP services, cascade interconnect billing and multilateral interconnect service hub (e.g. IP service Proxy) working would be required. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 13 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 Inter-operator IP backbone network shall be compliant with ETSI TISPAN standards for NGN architectures, protocols, interconnection, numbering, naming, addressing resolution and routing, etc., utilizing, to enable QoS, availability, reliability, security, etc., a dedicated inter-operator NGN "IP-based" network, that is totally separate from the public Internet. Communication providers should evaluate the alternatives for direct interconnection or indirect interconnection and choose the most appropriate. Issues such as QoS, security, control of interworking networks, overall reliability and issuing of new network features such as support for ENUM/DNS are easier handled within direct or indirect interconnections, being an operators' managed interconnection architecture. The benefits of this approach are more clearly assessed in TR 184 008 [i.6].
|
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 inter-operator IP network, that is totally separate from the public Internet. Using an inter-operator IP backbone network to carry IMS traffic would be less onerous than building direct connections between each and every IMS network in the world. As the number of operators increases, such an approach clearly does not scale without the introduction of 'transit IPX carriers' that would result in some form of carrier based IP backbone network. Communications Providers should evaluate the alternatives for IMS interworking and choose the most appropriate. One approach would be to use the inter-operator IP backbone network as the default routing choice but where traffic is high (typically between national carriers) a leased line or IP-VPN may be more cost effective. As the IP routing is separate from the physical topology, multiple physical connections may co-exist. In practice operators may have several physical interconnection links: leased line for national traffic, IP-VPN for medium volume and an inter-operator IP backbone network for all others. The DNS system will resolve the destination domain to an IP address that will be routed over the appropriate link. Issues such as QoS, security, control of interworking networks, overall reliability and issuing of new network features such as support for ENUM are easier handled inside an inter-operator IP backbone network than when using public internet to relay IMS traffic between operators. This is due to the fact that the inter-operator IP backbone network can be considered to be a closed operator controlled network unlike public Internet, which is totally open for everyone. The benefits of this approach are more clearly assessed in TR 184 008 [i.6].
|
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 connectivity at the IPX level can be facilitated in a number of ways, different countries are likely to require different connectivity implementations within their national environment, particularly as national databases will already be implemented or planned, closely coupled with different national number portability implementations. The rapid introduction of NGNs must not be hampered by the need to change such arrangements in order to facilitate connectivity at the Interoperator IP backbone level. There will also be an overriding need to ensure compliance with applicable national regulatory requirements and agreed processes, procedures and operating practices which are adopted at the national level in order to facilitate national number portability. Interoperator IP backbone network operators should: • Comply with any IP addressing guidelines set within ETSI, comply with DNS guidelines as specified in the present document • Have IPv4/IPv6 routing capability ETSI ETSI TS 184 010 V3.1.1 (2011-08) 14 • Distribute all valid known routes to Communications Providers • Control which routes a Communications Provider can advertise to the network • Offer interconnectivity to other inter-operator IP backbone networks (IPX peering) • Comply with agreed Service Level Agreements • Conform with security requirements laid out in TS 187 001 [14], TR 187 002 [i.7] and TR 187 010 [i.8] • Support end-to-end QoS requirements, described in any agreed SLA • Create the agreements required with other IPX Providers to fulfil the end to end SLA • Maintain required traffic separation e.g. invoke mechanisms to ensure the underlying IPX network is not reachable by end users
|
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 networks use IPv4 addressing but it is assumed that plans to introduce native IPv6 addressing will emerge in the foreseeable future. Support of IPv6 by native transport or tunnelling the IPv6 traffic over IPv4 between Communications Providers where required are options that could be considered. Both IP Backbone Providers and Service Providers who employ IPv6 in their network should assume full responsibility for Communication Providers that deploy IPv4. An IP Backbone Provider is responsible for the denial of IP spoofing attacks originated by its Service Provider customers, i.e. only traffic from valid IP address ranges is allowed to flow to other customers or other IP Backbone Providers.
|
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 different DNS domains and ENUM domains regarding the IPv4/IPv6 addresses of the DNS caching servers to provide advanced security as well as scalability measures
|
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 protocol the DNS/ENUM client must support RFC 2671 [15] to extend DNS the limitation of 512 octets in size when DNS protocol messages are sent over UDP; ETSI ETSI TS 184 010 V3.1.1 (2011-08) 15 • to ensure a basic level of security the DNS/ENUM client must support RFC 5358 [16] and RFC 5452 [17].
|
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 routing information (BGP), GTP traffic, signalling, DNS, SMTP and SIP(S) traffic. However, also traffic related to IMS user plane (such as RTP and HTTP) should be allowed due to IMS interworking. Therefore, due to potentially numerous new protocols introduced by IMS interworking, there should not be any kind of restrictions on the used protocols or port numbers with in the inter-operator IP backbone network. It is important to note that also firewalls must support IPv6 when IPv6 is used. Security gateways (SEGs) should be used at the border of an operator network. IPSec tunnels between CSCFs are not needed, if the Interoperator IP backbone network itself provides comparable level of security such as IPSec tunnel. SEG should be responsible for enforcing security policies for the inter-network traffic; all incoming & outgoing IP traffic would then need to pass through it. Usage of IPSec is mandatory if connectivity with the public Internet occurs, i.e. IMS connection must always be secured at some level. If IPSec is used in inter-PLMN IMS connections, it is recommend using the common IPSec parameter set in order to reduce the number of options. Above all, operators should realize that the actual security level of the whole IMS system depends on much more than just securing the transportation between CSCFs. This is done on an operational service level, where it is decided how these services are deployed and used. ETSI TISPAN IPX itself is nothing else than just IP bearer network, which does not provide any kind of actual security features besides the fact that no outsider should be able to access the a Interoperator IP backbone network. Consideration with TS 187 001 [14], TR 187 002 [i.7] and TR 187 010 [i.8]. Security issues related to IMS services, such as Peer-to-Peer traffic, are for further study.
|
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 networks and routers. Service guarantees should be defined and the backbone provider should take responsibility for providing measurements and also permit the Communications Provider to analyse the results.
|
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 core network Sub-system (IMS) IMS subscribers are addressed by SIP URIs and/or E.164 numbers represented as Tel URIs. For E.164 numbers, ENUM can be used in IMS as the means to convert an E.164 number into a SIP URI. TS 184 011 [8] provides requirements and describes the manner the E.164 numbers shall be used within NGN and NGCN environments. For resolving SIP URIs to SIP Servers (see RFC 3263 [5]), support of the SRV Resource Record functionality (as defined in RFC 2782 [6]) is needed in operator's DNS servers.
|
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 numbers and services related to a particular number using DNS. This mechanism is known as ENUM. 5.3 Shared ENUM Infrastructure for Inter-operator IP backbone Networks NGN architecture requires a name, number, addressing and routeing capability to be in place to facilitate the resolution of numbers, names and addresses to facilitate connectivity both within, and between networks. The ENUM protocol as defined within RFC 6116 [2] provides a method of achieving that. There is a need to process dialled digits that have been entered by the originating party in order to identify a called party or service, these digits are transmitted as a dial string to the NGN. To facilitate the routeing of calls the dial string is analysed and inserted in the ENUM application in the international format (an E.164 number) e.g. +44nnnnnnnnnn for processing within Shared ENUM Infrastructure. The output from the ENUM resolution process would be an address in the form of a SIP URI or tel URI, depending on whether then called part number can be reached on an IP based network or the PSTN. Within ETSI TISPAN Shared ENUM Infrastructure will be provided using a private DNS as set out in TR 184 008 [i.6] i.e. no direct connection to the public Internet. It will be transparent to users and not reachable by users of the Internet. Data can only be read by those that share that specific DNS architecture and related servers. The routeing data is populated by the communications service providers who are responsible for the numbers inserted. Amendments to the ENUM database can only be performed by the operators responsible for that specific set of number(s) e.g. numbers for which they are the carrier of record.
|
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/or ENUM data can be stored on one single device. This approach is called a Non-Root DNS architecture. Because there is no Name Server hierarchy a DNS/ENUM client can send DNS/ENUM queries direct to such an non-root DNS/ENUM server. The need for a caching NS is not applicable. The message flow is optimized, there is just one DNS query and response message needed for DNS resolution. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 17
|
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@carrier.com. Private user identity is not used for actual routing of SIP messages, but it is contained in all registration requests when S-CSCF stores the private user identity. Private user identity is permanently allocated to a user in order to identify the subscription and it is stored in home operator UPSF. In addition to private used identity, every IMS user has one or more public user identities. The public user identity is used in e.g. user-to-user communication. For example, it might be included on a business card. Public user identity is not authenticated by the network during registration, but it must be registered before the identity can be used in IMS activities. Public user identities can be used to identify the user's information within the UPSF. Format of public user identity is either SIP URI (RFC 3261 [9] or the "tel:"-URI format (RFC 3966 [10]), for example sip: tispan.support@etsi.org or tel: +33492944200. Routing of SIP signalling within the IMS uses SIP URIs. E.164 format public user identities are not used for direct routing within the IMS and session requests based upon E.164 format public user identities will require conversion into SIP URI format for internal IMS usage. This conversion is done using ENUM. In all roaming cases, visited network just forwards all requests to home network S-CSCF, which is then responsible for making ENUM query, if necessary. In case of interworking it is up to originating operator's S-CSCF to support this conversion mechanism. Details of conversion mechanisms other than ENUM are for further study. CSCF, BGCF and MGCF nodes are identifiable using a valid SIP URI (Host Domain Name or Network Address) on those interfaces supporting the SIP protocol. SIP URIs are used when identifying these nodes in header fields of SIP messages.
|
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 letters, digits, and hyphen. Mechanism and procedures to support Internationalized Domain Names for Applications (IDNA) are not part of the present document. DNS has an important role in IMS. During the session establishment an originating S-CSCF obtains the address of the I-CSCF for the network operator serving the destination user. Similarly during a registration a visited P-CSCF needs to resolve a home domain name to an address of I-CSCF in order to route SIP messages. DNS infrastructure is used for resolving an address of IMS contact point I-CSCF located in the home network. IMS typically uses multiple DNS queries, for example registration procedure requires at least 6 DNS queries, mobile originated call with E.164 numbers requires at least 3 DNS queries, and receiving a notification (SIP NOTIFY) from the AS requires approximately 4 DNS queries. Usage of cache, however, means that majority of these queries are transmitted only between resolver and the first configured/found DNS server. There are basically two major alternatives for IMS DNS deployment: 1) IMS domains are resolved using Internet DNS infrastructure (e.g. .com) 2) IMS domains are resolved using Interoperator DNS infrastructure, with three possible implementation models: - IMS Public User Identity (SIP URI) ends with (e.g. .3gppnetwork.org) - Subset of operator's global DNS infrastructure is duplicated in the Interoperator IP backbone network. Thus DNS server related to e.g. ims.operator.net can be found using the DNS service offered by the Interoperator IP backbone network - A mixture of Interoperator IP backbone DNS and operator internal mapping schemes is used ETSI ETSI TS 184 010 V3.1.1 (2011-08) 18
|
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 with the required information.
|
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 one country or a group of operators has solved the provisioning of their ENUM Tier-1 server provider and in certain cases operators have established their tier 2 information, all operators connected to the Interoperator IP backbone network are able to use data for interworking scenarios.
|
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 figure 3. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 19 Tier-0: Delegates E.164 numbers for a specific country code to a country-defined Tier-1 server. "Where can I get information about E.164 numbers for a given country code?". All slave root servers contain the same information; an exact copy of the master. Tier-1: Delegates a particular E.164 number or a block of numbers to a network operator-defined Tier-2 server. "Where can I get information about a particular E.164 number or block of numbers?" Tier-1 is basically country level i.e. every single country needs to have their own ENUM Tier-1 server. The ENUM Tier-1 server provider can be one operator in a country, or a designated third party, who has access to the Interoperator IP backbone network. The ENUM Tier-1 server could be shared between multiple network operators. In some instances the ENUM Tier-1 server provider can even be the same provider who provides the ENUM Tier-0 server. Tier-2: Returns NAPTR records for an E.164 number. "What services can this E.164 number support and what are the URIs to be able to contact it?". Tier-2 is basically operator level. The ENUM Tier-2 servers of operators under a country code could be combined with the ENUM Tier-1 server. Such a server could be "owned" by one network operator or shared between multiple network operators. Typically the ENUM Tier-2 server providers are either operators themselves or the same providers who offer Tier-0 or Tier-1 servers. It is also possible to run mixed mode, i.e. where part of the delegations are done in Tier-1 and rest is done in Tier-2. In practice there are many considerations relating to DNS delegation. Who has control of particular servers and number ranges is a matter of concern to telecomm carriers, especially in countries where numbers are portable between mobile and fixed carriers and there are potentially a large number of organisations involved. In the "real world" the delegation structure may not follow the model shown above and different Tiers may share the same server and delegation model. The present document does not attempt to describe arrangements for DNS & ENUM delegation, control and administration. The scope is restricted to describing technical details.
|
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 figure 4, refer to the below: 1 Service Provider's Local Caching DNS Server sends the DNS query to the Root DNS Server (which is essentially a DNS server that is authoritative for that delegation). 2 Root DNS Server replies with the NS record for the ENUM DNS Tier-0 Server. 3 Service Provider re-sends the DNS query, but to the ENUM DNS Tier-0 Server. 4 ENUM DNS Tier-0 Server replies with the NS record for the ENUM DNS Tier-1 Server. 5 Service Provider re-sends the DNS query, but to the ENUM DNS Tier-1 Server. 6 ENUM DNS Tier-1 Server replies with the NS record for the ENUM DNS Tier-2 Server. 7 Service Provider re-sends the DNS query, but to the ENUM DNS Tier-2 Server. 8 ENUM DNS Tier-2 Server replies with a list of URIs/URLs associated with the given E.164 number in NAPTR records, or an error of NXDOMAIN e.g. if the subscriber does not exist or if the Destination Communications Provider's optional policy check has decreed that there is no inter-working agreement with the originating Communications Provider. NOTE 1: As per normal DNS procedures, each reply an Communications Provider receives is cached for a certain amount of time, therefore, negating the need of every message shown always having to be sent. NOTE 2: Each ENUM DNS Tier Server may be combined e.g. combined Tier-1 and Tier2. NOTE 3: The Originating Communications Provider apply an optional policy check upon receiving any response. NOTE 4: A NS record contains normally FQDN. To reach the NS the FQDN has to be solved as an IPv4 or IPv6 address. In some cases the IP address is delivered in the answer packet of the NS record (glue record).
|
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 network operators to resolve queries and may lead to adverse resolution times due to DNS query timeouts. IP address Public addressing shall be applied in all Communications Provider IP Backbone network elements, which are advertised or visible to other Service Providers. Using public addressing means that each Communications Provider has a unique address space that is officially reserved from the Internet addressing authority. However, public addressing does not mean that these addresses should be visible to Internet. For security reasons, Communications Provider and inter-Service Provider backbone networks shall remain invisible and inaccessible to the public Internet. Internet routers should not be able to route to the IP addresses advertised to the Inter-Service Provider IP Backbone. In other words the IP Backbone Providers' and Communications Providers' networks shall be totally separated from public Internet, from an IP routing perspective.
|
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 as examples used merely to demonstrate the required structures. The choice of domain name to be used must: • to ensure there is no conflict with Public user ENUM • be registered on the Internet to ETSI TISPAN • have an appropriate suffix e.g. .net ETSI ETSI TS 184 010 V3.1.1 (2011-08) 21 • the chosen domain name must be available to be registered on the public internet for use by the inter-operator IP backbone network • neutral between mobile/fixed standards groups • has an indication of its purpose i.e. E164 and ENUM • can support future connection of both fixed & mobile services to an IPX common to ETSI TISPAN (and possibly GSMA) If a decision was taken to implement an ETSI TISPAN specific inter-operator IP backbone network appropriate control and oversight procedures would need to be determined but that study must remain dependent upon that event. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 22 Annex A (informative): Configuration Information for Services that Utilise DNS A.1 Introduction This clause describes the technical characteristics of each service that utilises DNS. Further detail can be found in the referenced specifications. If there are discrepancies between the description of the services in these clauses and the referenced specifications, what is stated in the referenced specifications prevail. A.2 ENUM FQDN Format Through translating E.164 numbers into DNS names, the ENUM mechanism can take advantage of existing DNS functionality such as infrastructure, delegation and caching. The algorithm for converting any E.164 number to an ENUM domain consists of the following: • Ensure that the E.164 number is written in its full form, including the country code. EXAMPLE 1: +44-7700-900123. • Remove all non-digit characters with the exception of the leading '+'. EXAMPLE 2: +447700900123. • Remove all characters with the exception of the digits. EXAMPLE 3: 447700900123. • Put dots (".") between each digit. EXAMPLE 4: 4.4.7.7.0.0.9.0.0.1.2.3. • Reverse the order of the digits. EXAMPLE 5: 3.2.1.0.0.9.0.0.7.7.4.4. • Append a top level domain name to the end (example: ".e164.arpa" for Public ENUM, or "e164enum.net" for Carrier ENUM on the GRX/IPX). For the inter-operator IP backbone network a top level domain name of the form .e164.tispan.foo is assumed. EXAMPLE 6: 3.2.1.0.0.9.0.0.7.7.4.4.e164.tispan.foo. The final answer identifies the destination operator for the given E.164 number. A.3 ENUM Tiers To ensure proper distribution and scalability of the DNS structures, ENUM uses a tier system. This is typically used in user ENUM as follows: Tier 0 - Global level - Under this domain are pointers to the Tier 1 authoritative servers. Tier 1 - Country level (CC) - Authoritative for country code (e.g. "4.4.e164.arpa" for country code +44). Under this domain are pointers to the Tier 2 authoritative servers. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 23 Tier 2 - User level - Authoritative for E.164 number ("6.5.4.3.2.1.0.0.7.7.4.4.e164.arpa"). Under this domain are the individual Subscriber Numbers each with one or more NAPTR records. In the case of shared ENUM infrastructure, the role of the user is taken by the operator (Carrier of Record). ENUM Tiers can be combined or even expanded. Further Tiers may be relevant in some networks and/or countries. ENUM is only for E.164 numbers. If the E.164 number is in a national format, as first step a conversion to an international format is needed. ENUM does not support non E.164 numbers (e.g. short codes). For further information see TR 184 005 [i.5]. Services that are related to particular E.164 numbers are stored and described in NAPTR records. NAPTR records are defined in RFC 3403 [3] and can be used for mechanisms other than ENUM. A.4 Technical Requirements for Interconnexion A.4.1 NAPTR formats The NAPTRs used in ENUM are defined in RFC 3404 [4]. An example of ENUM datafill in a DNS is as follows. This shows a part of an E.164 number which supports both IMS and MMS. Note that the $ORIGIN statement is used here to ensure correct syntax and would have limited use in a live DNS. $ORIGIN 3.2.1.0.0.9.0.0.7.7.4.4.e164enum.net. NAPTR 100 10 "u" "E2U+SIP". "!^.*$!sip:+447700900123@provider.net!". NAPTR 100 20 "u" "E2U+MMS:mailto". "!^.*$!mailto:+447700900123@provider.net!". A NAPTR contains the following fields: ORDER It is recommended to set the ORDER field in ENUM applications to 100. PREFERENCE The PREFERENCE field gives the preference by which the destination network wants the NAPTRs to be processed. FLAG The FLAG field may be "u" or blank "". In the inter-operator IP backbone network it is always "u", indicating that the regexp filed contains an URI. The "" is not used in inter-operator IP backbone network. ENUMservice The ENUMservice field contains E2U, indicating an ENUM application, plus one or more enumservices such as "sip", "mms:mailto" or "pstn:tel". The enumservices are defined in RFCs and registered via IANA. Regexp This field contains the URI in a regular expression. Replacement The replacement field is not used currently in the inter-operator IP backbone network. A.4.2 ENUMservice field The ENUMservice field appears in the NAPTR records for a particular E.164 number. It describes the services supported by that number. The following are recommended values to be used for different services defined by 3GPP. The ENUMservice to be used for IP-based services in IMS is "E2U+SIP" as defined in RFC 3764 [12]. The ENUMservice for services still on the PSTN/ISDN/PLMN on circuit-switched networks is "E2U+pstn:tel" as defined in RFC 4769 [13]. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 24 The ENUMservice to be used for MMS is "E2U+MMS:mailto" as defined in RFC 4355 [11]. A.4.3 URI Formats The information between the right side pair of "!" is known as an URI. For the inter-operator IP backbone network the user part contains the E.164 number in the international format, the domain name contains a unique indication to the destination network. EXAMPLE: sip:<+E.164 number>@provider.net add other examples: sip:<user>@example.com "sip:" indicates the protocol to be used which in this case is SIP. tel:<+E.164 number> The MMS ENUM URI domain format is not yet finalised (see GSMA PRD IR.67 [i.2]). A.4.4 SIP server configuration There are several IETF RFCs covering use of SIP in the DNS. These include RFC 3824 [i.4]. The reason this configuration is needed is as follows: When a SIP call is made by a user, he addresses the call to either a SIP URI (e.g. kim@provider.net) or an E.164 number. In both cases the IMS system needs to know the IP address of the SIP server to which it can route the call. The SIP server information contains the detail needed to provide the called network's SIP server IP address to the calling network based on the information in the SIP URI. If the call is to an E.164 number the ENUM system first translates that number to a SIP URI e.g. to: +447700900123@provider.net The approach described in this clause is compliant with these RFCs and consists of 4 separate steps. Step 1 This is the ENUM related step and is only performed for cases where the service has been addressed to an E.164 number. An IMS call to a user using the format bob@provider.net would not require this step. Example of DNS data for a particular SIP URI and its servers $ORIGIN 3.2.1.0.0.9.0.0.7.7.4.4.e164.foo. NAPTR 100 10 "u" "E2U+SIP" "!^.*$!sip:+447802345678@provider.net!" . NAPTR 100 10 "u" "E2U+MMS:mailto" "!^.*$!mailto:+447802345678@provider.net!" . The calling application asks the DNS for all the NAPTR records for the given E.164 number. There may be multiple NAPTR records returned as in this example. The calling application then selects the NAPTR record which contains the desired services which in this case are "E2U" and "SIP". "SIP" is called an enumservice. The "u" flag indicates the result of this lookup is a URI. The rest of the NAPTR is a Regular Expression. The calling application substitutes the relevant fields into the regular expression to get the result which is a SIP URI. The calling application then extracts the domain name from the URI. This is the domain name of the destination network to which the SIP call should be routed. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 25 Step 2 Having obtained the destination domain name the DNS is asked to provide matching SIP Server Location Information. One or more NAPTR records may be retrieved and the calling application examines these records to find the best match based on priorities and the desired SIP protocol variant: • provider.net. IN NAPTR 50 100 "s" "SIP+D2U" "" _sip._udp.provider.net. • provider.net. IN NAPTR 90 100 "s" "SIP+D2T" "" _sip._tcp. provider.net. • provider.net. IN NAPTR 90 100 "s" "SIPS+D2T" "" _sips._tcp. provider.net. In the above example, "D2U" indicates UDP-based SIP, "D2T" indicates TCP-based SIP, and "SIPS+D2T" indicates TCP-based encrypted SIP. The presence of these fields indicates what variations of SIP are supported on a given SIP server. The "s" flag means the next stage is to look up an "SRV" record Step 3 An example set of SIP server SRV records is as follows: • _sip._tcp.provider.net. SRV 0 1 5060 sipserv1.provider.net. • _sip._tcp.provider.net. SRV 0 2 5060 sipserv2.provider.net. • _sip._udp.provider.net. SRV 0 1 5060 sipserv1.provider.net. • _sip._udp.provider.net. SRV 0 2 5060 sipserv2.provider.net. • _sips._tcp.provider.net. SRV 0 1 5060 sipserv3.provider.net. • _sips._tcp.provider.net. SRV 0 2 5060 sipserv4.provider.net. For each of the variations of the SIP protocols supported the SRV records describe: • name of the server • which port number SIP uses • where there are multiple servers, the weights & priorities to allow rough load balancing The calling network asks the DNS for a SRV record for the host corresponding to the specific service/protocol/domain combination that was returned in Step 2. If there are multiple records with the same service/protocol/domain combination, the caller sort the records based on which has the lowest priority. If there is more than one record with the same priority, the record with the highest weight is chosen. From the SRV record get the corresponding server name. There is potential flexibility in this step for the destination operator to receive the SIP traffic on different servers depending on the desired variation of the SIP protocol - TCP, UDP, encrypted, unencrypted. Step 4 For the server name returned in Step 3, do a standard DNS lookup to finds its IP address. This is a normal "A" (address) record lookup for an IPv4 address or an "AAAA" (quad A) record lookup for an IPv6 address. • sipserv1.provider.net. IN A 10.1.2.3 • sipserv1.provider.net. IN AAAA 2001:db80:1234:5678:90ab:cdef:1234:5678 ETSI ETSI TS 184 010 V3.1.1 (2011-08) 26 • sipserv2.provider.net. IN A 10.1.2.4 • sipserv2.provider.net. IN AAAA 2001:db80:1234:5679:90ab:cdef:1234:5679 ETSI ETSI TS 184 010 V3.1.1 (2011-08) 27 Annex B (informative): General Configuration Information for Providers' DNS Servers B.1 Introduction This clause gives some general information on DNS server configuration for operators. B.2 Hardware It is recommended that operators have physically separate Primary and Secondary DNS servers. This helps provide the greatest service availability and allows for e.g. upgrading DNS Servers without any service interruption. B.3 Software Most commonly ISC BIND (usually version 4 or 9) is the chosen functional test reference software by operators and equipment vendors. This works for services which do not necessarily have a large data-fill but for services such as ENUM where the data-fill can run into millions of resource records, a commercial DNS server product may be used. Such commercial DNS server solutions can also support legacy DNS data-fill, thereby consolidating all operator DNS needs. B.4 Caching Since each service (e.g. MMS, etc.) has its own domain, a separate TTL value can be set per service respectively DNS resource record. When setting the TTL value for a zone, careful consideration is needed to ensure that the right trade-off is made between performance, consistency as well as operational, regulatory and process requirements. A small TTL value results in a greater signalling overhead, greater processing overhead for the authoritative name server(s) and greater time for a returning a result, but the data will be more up-to-date therefore allowing updates to propagate much more quickly. A large TTL value results in a smaller signalling overhead, smaller processor overhead for the authoritative name server(s) and usually shorter time for returning a result to the requesting entity, but the data will be more likely to be out of date and therefore resulting in updates taking longer to propagate. The TTL value for ENUM domains impact the time related requirements for number portability, in the case that ENUM is used to support number portability. It is highly recommended that negative caching is also used (available in ISC BIND versions 4.9, 8.x and 9.x and should be available in most commercial DNS solutions). Again, careful consideration should be taken, considering factors such as the frequency of updates, signalling overhead and processing overhead of the authoritative DNS server for the domain. B.5 Reverse Mapping Each operator is strongly recommended to provide reverse mapping of all FQDNs that they use (e.g. A or AAAA resource record resolution). This is not mandatory for interworking to be successful, but rather, it aids in trouble shooting/debugging activities such as performing a "traceroute". ETSI ETSI TS 184 010 V3.1.1 (2011-08) 28 B.6 Use of DNS Interrogation Modes Two interrogation modes are defined in the DNS specifications: iterative and recursive. In Recursive Mode, a DNS server interrogates only the next DNS server in the DNS hierarchy. That DNS Server then takes on responsibility for resolving the requested domain name and provides a final answer back to the original requesting DNS server. On the inter-operator IP backbone network DNS, this would look like the following. Root DNS Server Authoritative DNS Server Requesting DNS Server 1 4 2 3 Figure B.1: Recursive interrogation mode as seen by the owner of the authoritative DNS Server As can be seen above, the owner of the authoritative DNS server has no visibility of the source of the original request (i.e. the VPLMN address is not included in the request). In Iterative mode, a DNS server interrogates each DNS server in the hierarchy itself, in order to resolve the requested domain name. On the inter-operator IP backbone network DNS, this would look like the following. Root DNS Server Authoritative DNS Server Requesting DNS Server 1 2 3 4 4 Figure B.2: Iterative interrogation mode as would be seen on the DNS of the inter-operator IP backbone network As can be seen above, the owner of the authoritative DNS server has full visibility of the source of the original request. As a security measure it is recommended that on the inter-operator IP backbone network, Root DNS Servers deliberately do not service DNS requests sent in Recursive mode: only those issued in Iterative mode. This would enable owners of Authoritative DNS Servers to determine the true source of DNS requests and thus provide adequate security measures, such as access lists, at the edge of their networks. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 29 B.7 Use of the inter-operator IP backbone network Root DNS Server There are two possibilities to arrange DNS hierarchy. The first is for each Communications Provider to configure their Nameserver of each domain name individually for all inter-working and partner operators. The drawback of this approach is that it is not scalable as every time a new inter-working and/or partner operator agreement is made or any existing inter-working and/or partner Communications Provider Nameserver data changes, an data update of all DNS Server is needed. This potentially forms a likely source of operational inter-working and roaming problems. Another alternative is to use the common the inter-operator IP backbone network Root DNS Server, as provided for by the inter-operator IP backbone network provider Using the inter-operator IP backbone network Root DNS Server enables changed Nameserver data for an operator to be immediately active (subject to caching). B.8 Provisioning of Communications Providers DNS servers Inter-operator IP backbone network Service Providers may take the responsibility for the management of DNS on behalf of the operator subscribing to the IPX. Services require DNS information to be exchanged between all operators and the inter-operator IP backbone network providers (where those inter-operator IP backbone network providers are managing an operator's DNS service on their behalf). Communications Providers and the inter-operator IP backbone network providers should distribute all required DNS information between inter-working/roaming operators, or make available access to their authoritative DNS server(s) to service DNS requests. ETSI ETSI TS 184 010 V3.1.1 (2011-08) 30 Annex C (informative): Bibliography • IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". • IETF RFC 3401: "Dynamic Delegation Discovery System (DDDS) Part One:The Comprehensive DDDS". • IETF RFC 3402: "Dynamic Delegation Discovery System (DDDS) Part Two: The Algorithm". • ETSI TS 123 003: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Numbering, addressing and identification (3GPP TS 23.003 version 6.10.0 Release 6)". • GSMA PRD IR.65: "IMS Roaming and Interworking Guidelines". • IETF RFC 1032: "Domain administrators guide". ETSI ETSI TS 184 010 V3.1.1 (2011-08) 31 History Document history V3.1.1 August 2011 Publication
|
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 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.
|
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 converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". [2] ETSI TS 182 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional description (Endorsement of 3GPP TS 23.141 and OMA-AD-Presence-SIMPLE-V1-0)". [3] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [4] ETSI TS 182 027: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". [5] ETSI TS 182 028: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; Dedicated subsystem for IPTV functions". [6] ETSI TS 183 063: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based IPTV stage 3 specification". [7] IETF RFC 2838: "Uniform Resource Identifiers for Television Broadcasts". ETSI ETSI TS 184 009 V2.1.1 (2008-10) 6 [8] IETF RFC 3986: "Uniform Resource Identifier (URI): Generic Syntax". [9] ETSI TS 183 064: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Dedicated IPTV subsystem stage 3 specification".
|
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.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
3 Definitions and abbreviations
| |
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 180 000 [1], TS 181 016 [3] and the following apply: tv URI: identification of a broadcast television channel
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: BC Broadcast DNS Domain Name System EPG Electronic Program Guide IPTV Internet Protocol TeleVision TV Television URI Uniform Resource Identifier XML Extensible Markup Language
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
4 Requirements on the use of the TV URI
|
This clause sets requirements on the use of the TV URI for the identification of broadcast television channels for applications that require such identification.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
4.1 TV URI for IPTV presence
|
Presence TS 182 008 [2] is the application where one user (the "watcher") can see the status of another user (the "presentity"). In case of IPTV, an item in the presence information may be the television channel currently accessed. According to TS 181 016 [3]: "It shall be possible to define presence information related to the IPTV experience, e.g. channel currently accessed. The identification of the channel currently accessed shall be machine-readable. Language dependent information may also be made available to watchers." According to TS 182 027 [4]:"If the IPTV presence attribute "channel currently accessed" is supported, then the machine-readable part of the identification of the channel shall be globally unique. The term globally unique here means that there is no ambiguity in the identification of the channel if presentity and watcher (for terminology, see in TS 182 008 [2]) are with different network operators and/or in different countries." Document TS 183 063 [6] contains a stage-3 description of the IPTV presence service. The XML schema for presence information includes the "BCServiceID" parameter, which corresponds with the "channel currently accessed" in TS 181 016 [3] and TS 182 027 [4]. ETSI ETSI TS 184 009 V2.1.1 (2008-10) 7 Req. 4.1.1: If the "BCServiceID" parameter is used, then it shall be populated with a TV URI.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
4.2 TV URI for Electronic Program Guide
|
Electronic Program Guide (EPG) is "an assistance tool which helps users to locate the content they want and to facilitate the selection of IPTV services for watching, recording, etc." TS 181 016 [3], TS 182 027 [4], TS 182 028 [5], TS 183 063 [6] and TS 183 064 [9]. EPGs refer to television channels. Req. 4.2.1: If the IPTV provider and the provider of the EPG service are different parties, then the EPG shall use the TV URI to identify television channels. Req. 4.2.2: If the IPTV provider and the provider of the EPG service are the same party, then the EPG may use the TV URI to identify television channels. Req. 4.2.3: In an IMS-based IPTV system, the TV URI should be used in the EPG conforming to TS 183 063 [6], clause L.2.3. Req. 4.2.4: In a dedicated IPTV systems, the TV URI should be used in the EPG conforming to TS 183 064 [9], clause 9.2.1.1.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
4.3 TV URI for NNI for IPTV
|
NNI for IPTV is the interconnection between an IPTV Provider and another IPTV Provider or a content Provider to exchange content, like broadcast television channels (BC). If the broadcast television channels are exchanged on an on-demand basis then the identification of television channels is needed. Req. 4.3.1: If different parties exchange broadcast television channels on an on-demand basis, then the TV URI shall be used to identify those television channels.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5 Identification of television channels with TV URI
|
Identification of a TV channel is an answer to the question "What is the name of this TV channel?". Identification of TV channels is done by human, e.g. the end-user programming his set-top box, or an engineer at the IPTV provider filling in channel lists. Figure 1 illustrates the distinction between identification of television channels (this clause), and their resolution (see clause 6). Figure 1: Identification of TV channels is performed by humans ETSI ETSI TS 184 009 V2.1.1 (2008-10) 8
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5.1 TV URI syntax and semantics
|
Television channels are identified by a tv:URI as specified in RFC 2838 [7]. The basic structure of a television URI is: tv:<broadcast> where broadcast is a description of the data source. The description takes the form of a DNS-style identifier for a particular broadcaster or television network. EXAMPLE 1: tv:wqed.org the WQED station tv:nbc.com the NBC network In the simplest form, domain names themselves are used as broadcast identifiers. EXAMPLE 2: tv:abc.com the American Broadcast Company tv:abc.co.au the Australian Broadcast Corporation In some cases, networks have multiple broadcast streams that need to be distinguished. This is also handled in DNS style: tv:east.hbo.com HBO East tv:west.hbo.com HBO West
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5.2 Naming a television channel with a TV URI
|
The present document follows a so-called harmonization approach in the identification of television channels. This clause explains the harmonization approach and provides rules for the harmonization.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5.2.1 Harmonization of TV URIs
|
The purpose of standardization is to improve interoperability and hence and reduce identification ambiguity. The following approaches can be recognized in reducing the ambiguity in the identification of TV channels: Free-format text field. Harmonization. Registry. The first approach is the definition of a free-format text field. This would enable the identification. However, it leaves much ambiguity on how this text field should be used. The second approach is the specification of harmonized syntax and semantics rules. This is essentially what the tv:URI is. The syntax of the tv:URI is defined in RFC 2838 [7]: tv:<broadcast>, with <broadcast> being a DNS-style identifier. Examples of semantics rules are the following. The third approach is the establishment of a registry for tv:URIs. The registry would enforce rules like the above ones, and establish additional rules when needed. Notice that there will still remain ambiguity, as the registry can and will be incomplete. For example, the Showview channel lists maintained by Gemstar are incomplete, as it only covers TV channels in a limited set of countries and within those countries, various local and regional TV channels are missing in the lists. Figure 2 illustrates a view on how the different approaches compare to each other in reducing the ambiguity in the identification of TV channel. ETSI ETSI TS 184 009 V2.1.1 (2008-10) 9 Figure 2: Effectively of a harmonization approach to identify television channels with the TV URI So, the harmonization approach will quickly cover the majority of the TV channels. By adding harmonization rules when needed, the percentage of TV channels unambiguously identified can quickly become very high. In contrast, a registry approach will take much time, effort and cost. The registry has to be established, including funding, governance and policies. The registry will have to comply with various national and international regulations. Rules and procedures have to be made on which entities can populate the registry and how the creation, reading, updating and deletion of records is managed. So, the harmonized approach is most effective on the short term. Also, this approach does not preclude the evolution to a registry approach on the long term.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5.2.2 Rules for the harmonization of TV URIs
|
This clause provides rules for the harmonization to identify television channels with the TV URI. It is important to note that these DNS-style identifiers need not match real hostnames; they should not be resolved to IP addresses using DNS. Thus, using the terms as defined in RFC 3986 [8], the "tv:" scheme is a Uniform Resource Identifier and not a Uniform Resource Locator. Req 5.2.2.1: Domain names must be used as broadcast identifiers, with the applicable country top-level domain. EXAMPLE 1: - tv:abc.com the American Broadcast Company - tv:abc.co.au the Australian Broadcast Corporation Req 5.2.2.2: The tv:URI shall match with the registered domain name of the broadcaster or television network. EXAMPLE 2: - tv:cnn.com is the TV channel which has the website http://cnn.com Req 5.2.2.3: Networks may have multiple broadcast streams that need to be distinguished. This is also handled in DNS style. EXAMPLE 3: - tv:east.hbo.com HBO East - tv:west.hbo.com HBO West ETSI ETSI TS 184 009 V2.1.1 (2008-10) 10
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
5.2.3 Dispute resolution
|
In order to ensure uniqueness, the "tv:" scheme must use DNS-style identifiers for all broadcast streams. Because these build on the existing registration system for DNS hostname, all name collisions can be resolved through the existing DNS dispute resolution processes.
|
0e06561ddbcf2651d8b229c2ed3e8620
|
184 009
|
6 Resolution of TV URIs
|
Possible approaches to resolve a TV URI could be the following: 1) A user can read and understand the TV URI, and switches the channel manually. E.g. many people will understand which TV channel is identified by tv:bbc1.co.uk and know how to switch to that channel. 2) A user can look the TV URI in a list provided by his IPTV service provider. 3) A user can look the TV URI up in a list provided by a registry, if such a registry would exist. 4) The TV URI list can be (pre-)programmed in the user's end device. 5) The user can program the TV URI list in his end device herself. For example, users now have to reprogram their video recorder when a new TV channel becomes available. 6) The IPTV provider can decide to install a TV URI-resolution infrastructure to aid the resolution of TV-channel identifiers. 7) Other approaches. The present document does not preclude any approach for the resolution of TV URIs. ETSI ETSI TS 184 009 V2.1.1 (2008-10) 11 Annex A (informative): Bibliography ETSI TS 184 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Identifiers (IDs) for NGN". ETSI ETSI TS 184 009 V2.1.1 (2008-10) 12 Annex B (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version July 2008 17bTD078r1 CR001 - F Use of TV URI in TISPAN electronic program guides 2.0.0 2.1.1 ETSI ETSI TS 184 009 V2.1.1 (2008-10) 13 History Document history V2.0.0 June 2008 Publication V2.1.1 October 2008 Publication
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
1 Scope
|
The present document specifies the Test Suite Structure and Test Purposes (TSS&TP) for Network Integration Testing (NIT) to verify the overall compatibility of IMS networks. For IMS, SIP and SDP specific terminology, reference shall be made to ES 283 003 [1] and RFC 3261 [3] respectively.
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
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 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.
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
2.1 Normative references
|
The following referenced documents are necessary for the application of the present document. [1] ETSI ES 283 003 (V2.6.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". [2] ETSI TS 124 503 (V8.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 (Release 7), modified] (3GPP TS 24.503 version 8.5.0 Release 8)". [3] IETF RFC 3261 (2002): "SIP: Session Initiation Protocol". [4] ISO/IEC 9646-1 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 1: General concepts". [5] ISO/IEC 9646-2 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 2: Abstract Test Suite specification". [6] ISO/IEC 9646-3 (1998): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 3: The Tree and Tabular Combined Notation (TTCN)". [7] Void. [8] ISO/IEC 9646-5 (1994): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 5: Requirements on test laboratories and clients for the conformance assessment process". [9] ISO/IEC 9646-7 (1995): "Information technology - Open Systems Interconnection - Conformance testing methodology and framework - Part 7: Implementation Conformance Statements". [10] ETSI TS 124 229 (V7.15.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3 (3GPP TS 24.229 version 7.15.0 Release 7)". [11] Void. ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 7 [12] ETSI TS 124 504 (V8.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services: Communication Diversion (CDIV); Protocol specification (3GPP TS 24.504 version 8.5.0 Release 8)". [13] Void. [14] ETSI TS 124 407 (V7.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; PSTN/ISDN simulation services; Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR); Protocol specification (3GPP TS 24.407 version 7.0.0 Release 7)". [15] ETSI TS 124 410 (V7.0.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); TISPAN; NGN Signalling Control Protocol; Communication HOLD (HOLD) PSTN/ISDN simulation services; Protocol specification (3GPP TS 24.410 version 7.0.0 Release 7)". [16] IETF RFC 4566 (2006): "SDP: Session Description Protocol". [17] IETF RFC 3312 (2002): "Integration of Resource Management and Session Initiation Protocol (SIP)". [18] IETF RFC 3311 (2002): "The Session Initiation Protocol (SIP) UPDATE Method". [19] ETSI TS 124 147 (V8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3 (3GPP TS 24.147 version 8.2.0 Release 8)". [20] Void. [21] ETSI TS 124 615 (V8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specfication (3GPP TS 24.615 version 8.2.0 Release 8)". [22] ETSI TS 124 642 (V8.2.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Completion of Communications to Busy Subscriber (CCBS) and Completion of Communications by No Reply (CCNR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol Specification (3GPP TS 24.642 version 8.2.0 Release 8)". [23] ETSI TS 124 529 (V8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; TISPAN; PSTN/ISDN simulation services: Explicit Communication Transfer (ECT); Protocol specification (3GPP TS 24.529 version 8.1.0 Release 8)". [24] ETSI TS 124 508 (V8.1.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); PSTN/ISDN simulation services Terminating Identification Presentation (TIP) and Terminating Identification Restriction (TIR); Protocol specification (3GPP TS 24.508 version 8.1.0 Release 8)". [25] IETF RFC 5366: "Conference Establishment Using Request-Contained Lists in the Session Initiation Protocol (SIP)".
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
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. ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 8
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
3 Definitions and abbreviations
| |
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: For SIP and SDP specific terminology, reference shall be made to RFC 3261 [3] and RFC 4566 [16] respectively. SIP precondition: Indicates the support of the SIP "precondition procedure" as defined in RFC 3312 [17]. test purpose: non-formal test description, mainly using text NOTE: TSIs test description can be used as the basis for a formal test specification (e.g. Abstract Test Suite in TTCN). See ISO 9646 (all parts) [4] to [9]. The test purposes have been defined from the user's viewpoint and the abbreviation "UE" is used in the description. However, the detailed comments section uses the abbreviation "UA" for test system instances of the users.
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
3.2 Conventions for representation of SIP/SDP information
|
1) All letters of SIP method names are capitalised. EXAMPLE 1: INVITE, INFO. 2) SIP header fields are identified by the unabbreviated header field name as defined in the relevant RFC, including capitalization and enclosed hyphens but excluding the following colon. EXAMPLE 2: To, From, Call-ID. 3) Where it is necessary to refer with finer granularity to components of a SIP message, the component concerned is identified by the ABNF rule name used to designate it in the defining RFC (generally 25/RFC 3261 [3]), in plain text without surrounding angle brackets. EXAMPLE 3: Request-URI, the userinfo portion of a sip: URI. 4) URI types are represented by the lower-case type identifier followed by a colon and the abbreviation "URI". EXAMPLE 4: sip: URI, tel: URI. 5) SIP provisional responses and final responses other than 2XX are represented by the status code followed by the normal reason phrase for that status code, with initial letters capitalized. EXAMPLE 5: 100 Trying, 484 Address Incomplete. 6) Because of potential ambiguity within a call flow about which request a 200 OK final response answers, 200 OK is always followed by the method name of the request. EXAMPLE 6: 200 OK INVITE, 200 OK PRACK. 7) A particular line of an SDP session description is identified by the two initial characters of the line -- that is, the line type character followed by "=". EXAMPLE 7: m=line, a=line. 8) Where it is necessary to refer with finer granularity to components of a session description, the component concerned is identified by its rule name in the ABNF description of the SDP line concerned, delimited with angle brackets. EXAMPLE 8: The <media> and <fmt> components of the m= line. ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 9
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
3.3 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form ATS Abstract Test Suite CCBS Completion of Communications to Busy Subscriber CCNR Completion of Communications by No Reply CD Communication Deflection CDIV Communication DIVersion CDIVN Communication DIVersion Notification CFB Communication Forwarding Busy CFNL Communication Forwarding on Not Logged-in CFNR Communication Forwarding No Replay CFNRc Communication Forwarding on subscriber Not Reachable CFU Communication Forwarding Unconditional CONF CONFerence CW Call Waiting ECT Explicit Communication Transfer HOLD communication HOLD IUT Implementation Under Test NDUB Network Determined User Busy OIP Originating Identification Presentation OIR Originating Identification Restriction PIXIT Protocol Implementation eXtra Information for Testing SDP Session Description Protocol SIP Session Initiation Protocol SUT System Under Test TIP Terminating Identification Presentation TIR Terminating Identification Restriction TP Test Purpose TSI Test System Interface TSS Test Suite Structure TTCN Test and Test Control Notation UA User Agent UDUB User Determined User Busy UE User Equipment ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 10
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
4 Test Suite Structure (TSS)
| |
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
4.1 SIP-SIP
|
C - Plane / U - Plane Basic_Call Successful Normal call establishment SS___XX___xx Codec negotiation SS___CN___xx UPDATE SS___XX__UP__xx Unsuccessful SS___XX__Uxx Supplementary_Services OIP SS___XXSS_OIPxx OIR SS___XXSS_OIRxx TIP SS___XXSS_TIPxx TIR SS___XXSS_TIRxx HOLD SS___XXSS_CHxx CDIV CFU SS___XXSS_CFUxx CFB SS___XXSS_CFBxx CFNR SS___XXSS_CFNRxx CFNRc SS___XXSS_CFNRcxx CFNL SS___XXSS_CFNLxx CD SS___XXSS_CDxx CONF CONF_CRE SS___XXSS_CONF_CRExx CONF_IN SS___XXSS_CONF_INVxx CONF_LEAV SS___XXSS_CONF_LEAVxx CONF_REMOV SS___XXSS_CONF_REMOVxx CW SS___XXSS_CWxx CCBS SS___XXSS_CCBSxx CCNR SS___XXSS_CCNRxx ECT SS___XXSS_ECT
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
5 Numbering Scheme
| |
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
5.1 General description
|
Pos. 1: Network of the A-Subscriber Pos. 2: Network of the B-Subscriber Pos. 3: Network of the C-Subscriber Pos. 4: Network of the D-Subscriber Pos. 5: Network of the E-Subscriber The following Network Codes apply: _: No such network used (used e.g. for C-Subscriber in successful A to B Calls) (underscore makes it easier to read the name) P: PSTN I: ISDN ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 11 S: SIP (Extensions will be added when needed) Pos. 6 and 7: Bearer- or Teleservice involved XX: Defined per PIXIT value NOTE: TSIs may be appropriate for Test Purposes (provided the Test Purpose states for which Bearer- and/or Tele Services it should be tested). It is however NOT appropriate for Test Cases since it would be detrimental to Test Automation. SP: Speech AU: 3,1 kHz Audio UD: UDI UT: UDI/TA CN: Codec negotiation DT: DTMF UP: UPDATE Method Pos. 8 and 9: __: No Supplementary Services Involved / Successful _U: No Supplementary Services Involved / Unsuccessful SS: Supplementary Services Involved
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
5.2 Basic Call
|
Speech IS___XX__XX 1 2 3 4 5 6 7 8 9 10 11 I S _ _ _ S P _ _ x x
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
5.3 Supplementary Services
|
CLIP IS___XXSSCLIP XX 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 I S _ _ _ X X S S C L I P x X
|
3830b88c4707da898cf266974581f8bf
|
186 001-3
|
6 Test purposes
|
The registration and application usage procedures in the ATS shall be compliant to RFC 3261 [3] and ES 283 003 [1] (modified TS 124 229 [10] and TS 124 503 [2]). The validation of the registration procedure is out of scope of the present document and will be part of the preambles used in the abstract test cases. ETSI ETSI TS 186 001-3 V2.2.1 (2010-11) 12
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.