- 1 - 12/12 Intended type of document

advertisement

- 1 -

Question(s): 12/12 Meeting, date:

Study Group: 12 Working Party: 3/12 Intended type of document (R-C-D-TD):

Source:

Title: A.5 justification information for draft new E.804 (ex E.MQoS)

Contact: <Name>

<Organization>

<Country>

Tel:

Fax:

Email:

Contact:

Please don't change the structure of this table, just insert the necessary information.

Tel:

Fax:

Email:

TD

1 Introduction

According to ITU procedures, as described in ITU-T Recommendation A.5

, any normative reference to documentation produced outside the ITU (other than ISO and IEC texts) needs to be evaluated by the study group or working party before a decision is made to incorporate the reference in an ITU-T Recommendation.

This TD contains the A.5 justification information for new E.804 (ex E.MQoS).

2 Referred documents and respective justifications

- ETSI EN 300 392-2 V3.4.1 (2010-08): Terrestrial Trunked Radio (TETRA);Voice plus Data

(V+D);Part 2: Air Interface (AI)

- Approved by ETSI.

- The referred document defines the Air Interface (AI) for the Terrestrial Trunked Radio

(TETRA) system supporting Voice plus Data (V+D) and contains the specifications of the physical layer, the data link layer and the network layer according to the ISO model. This reference is needed to specify the trigger points in Rec. E.804.

- Complete A.5 justification information can be found in Annex 1 .

- ETSI EN 300 392-5 V2.2.1 (2010-07): Terrestrial Trunked Radio (TETRA);Voice plus Data

(V+D) and Direct Mode Operation (DMO);Part 5: Peripheral Equipment Interface (PEI)

- Approved by ETSI.

- The referred document specifies the functional and technical aspects of TETRA Peripheral

Equipment Interface (PEI) that is the interface between a Terminal Equipment type 2 (TE2) and a Mobile Termination type 2 (MT2) at reference point RT. This reference is required in Rec.

E.804 to specify the test UE.

- Complete A.5 justification information can be found in Annex 2 .

- ETSI TR 102 493 V1.2.1 (2009-06): Speech and multimedia Transmission Quality

(STQ);Guidelines for the use of Video Quality Algorithms for Mobile Applications

- Approved by ETSI.

- 2 -

- The referred document gives guidelines for the use of video quality algorithms for the different services and scenarios applied in the mobile environment. This reference is neede in Rec. E.804 to define content integrity.

- Complete A.5 justification information can be found in Annex 3 .

- ETSI TR 102 581 V1.1.1 (2007-05): Speech Processing, Transmission and Quality Aspects

(STQ);A Study on the Minimum Additional Required Attenuation on the Antenna Path of the Field

Test Equipment

- Approved by ETSI.

- The referred document presents a theoretical model to be used for the estimation of the minimum required additional attenuation on the antenna path of the field test equipment in order for this to emulate the real life scenarios. This reference is needed in Rec. E.804 to specify requirements for Quality of Service measurement equipment.

- Complete A.5 justification information can be found in Annex 4 .

- ETSI TS 100 910 V8.20.0 (2005-11): Digital cellular telecommunications system (Phase

2+);Radio Transmission and Reception (3GPP TS 05.05 version 8.20.0 Release 1999)

- Approved by ETSI.

- The referred document defines the requirements for the transceiver of GSM. This reference is needed in Rec. E.804 to define antenna requirements for test UE.

- Complete A.5 justification information can be found in Annex 5 .

- ETSI TS 123 228 V11.10.0 (2013-12): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;IP Multimedia Subsystem

(IMS);Stage 2 (3GPP TS 23.228 version 11.10.0 Release 11)

- Approved by ETSI.

- This document defines the stage-2 service description for the IP Multimedia Core Network

Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services. This reference is needed in Rec. E.804 to describe the IMS Multimedia Telephony service.

- Complete A.5 justification information can be found in Annex 6 .

- ETSI TS 124 008 V11.8.0 (2013-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;Mobile radio interface Layer 3 specification;Core network protocols;Stage 3 (3GPP TS 24.008 version 11.8.0 Release 11)

- Approved by ETSI.

- The referred document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system. The reference is needed for Rec. E.804 to describe timeout values for data services.

- Complete A.5 justification information can be found in Annex 7 .

- ETSI TS 125 304 V11.4.0 (2013-09): Universal Mobile Telecommunications System

(UMTS);User Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode (3GPP TS 25.304 version 11.4.0 Release 11)

- Approved by ETSI.

- 3 -

- The referred document specifies the Access Stratum (AS) part of the Idle Mode procedures applicable to a UE. This reference is needed in Rec. E.804 for the definition of trigger points regarding radio network unavailabilty.

- Complete A.5 justification information can be found in Annex 8 .

- ETSI TS 127 005 V11.0.0 (2012-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;Use of Data Terminal Equipment

- Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and

Cell Broadcast Service (CBS) (3GPP TS 27.005 version 11.0.0 Release 11)

- Approved by ETSI.

- The referred document defines three interface protocols for control of SMS functions within a

GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.The reference is needed in Rec. E.804 to define the properties of the test UE.

- Complete A.5 justification information can be found in Annex 9 .

- ETSI TS 127 007 V11.8.0 (2013-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;AT command set for User

Equipment (UE) (3GPP TS 27.007 version 11.8.0 Release 11)

- Approved by ETSI.

- The referred document specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and GSM/UMTS network services from a Terminal Equipment (TE) through Terminal Adaptor (TA). This reference is needed in

Rec. E.804 to define test UE.

- Complete A.5 justification information can be found in Annex 10 .

- ETSI TS 129 002 V11.8.0 (2013-09): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);Mobile Application Part (MAP) specification (3GPP TS 29.002 version 11.8.0 Release 11)

- Approved by ETSI.

- The referred document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil GSM signalling needs.This reference is needed in Rec. E.804 to define trigger points for SMS and MMS.

- Complete A.5 justification information can be found in Annex 11 .

- ETSI TS 145 008 V11.5.0 (2013-09): Digital cellular telecommunications system (Phase

2+);Radio subsystem link control (3GPP TS 45.008 version 11.5.0 Release 11)

- Approved by ETSI.

- The referred document specifies the Radio sub system link control implemented in the Mobile

Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the digital cellular telecommunications systems GSM. This reference is needed in Rec. E.804 to describe network unavailabilty.

- Complete A.5 justification information can be found in Annex 12 .

- IETF RFC 1939 (1996): Post Office Protocol - Version 3, May 1996

- The referred RFCs were approved by IESG (Internet Engineering Steering Group).

- 4 -

- The reference to RFC 1939 is needed in Rec. E.804 to define the trigger points for e-mail transaction time.

- Complete A.5 justification information can be found in Annex 13 .

- IETF RFC 2177 (1997): IMAP4 IDLE command

- Normative

- This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. This refence is needed in Rec. E.804 for the definition of store-and-forward services measurements.

- Complete A.5 justification information can be found in Annex 14 .

- IETF RFC 2326 (1998): Real time Streaming protocol (RTSP)", H. Schulzrinne, A. Rao, R.

Lanphier, April 1998.

- Standards track, normative

- The reference to RFC 2326 is needed in Rec. E.804 to define the Real Time Streaming Protocol.

- Complete A.5 justification information can be found in Annex 15 .

- IETF RFC 2821 (2001): Mail Transfer Protocol, IETF RFC, April 2001

- The referred RFCs were approved by IESG (Internet Engineering Steering Group).

- The reference to RFC 2821 is needed in Rec. E.804 to define the trigger points for e-mail transaction time.

- Complete A.5 justification information can be found in Annex 16 .

- IETF RFC 3481 (2003): TCP over Second (2.5G) and Third (3G) Generation Wireless Networks

- Approved

- This document describes a profile for optimizing TCP to adapt so that it handles paths including second (2.5G) and third (3G) generation

wireless networks. It describes the relevant characteristics of 2.5G and 3G networks, and specific features of example deployments of such

networks. This reference is needed in Rec. E.804 to describe media downloads.

- Complete A.5 justification information can be found in Annex 17 .

- OMA-AD-PoC-V2_0-20110802-A: Push to talk over Cellular (PoC) - Architecture

- All of the documents are approved OMA specifications

- The scope of the Push to talk over Cellular (PoC) V2.0 architecture document is to define the architecture for the PoC Enabler V2.0. This reference is needed in Rec. E.804 to specify the

Push to talk over cellular trigger points.

- Complete A.5 justification information can be found in Annex 18 .

- OMA-ERELD-POC-V2_0-20110802-A: Enabler Release Definition for PoC

- All of the documents are approved OMA specifications

- The referred document defines the Enabler Release Definition of Push to talk over Cellular according to OMA Release process. This reference is needed for Rec. E.804 to define PoC trigger points.

- 5 -

- Complete A.5 justification information can be found in Annex 19 .

- OMA-TS-PoC_ControlPlane-V2_0-20110802-A: OMA PoC Control Plane

- All of the documents are approved OMA specifications

- The referred document defines the Control Plane signaling procedures of the PoC Client, the

PoC Box and the PoC Server for Push to talk over Cellular (PoC) service. Example detailed signaling flows for the reference points POC-1, POC-2, POC-9, POC-11 and IP-1 are also included in this specification. This reference is needed in Rec. E.804 for the definition of trigger points for PoC.

- Complete A.5 justification information can be found in Annex 20 .

- OMA-TS-PoC_UserPlane-V2_0-20110802-A: PoC User Plane

- All of the documents are approved OMA specifications

- The referred document describes the User Plane signalling procedures for the Push to talk over

Cellular (PoC) service over the POC-3, POC-4, POC-10 and POC-12 reference points. This reference is needed for Rec. E.804 to describe the PoC testing.

- Complete A.5 justification information can be found in Annex 21 .

- 6 -

Annex 1

A.5 justification information for the reference to ETSI EN 300 392-2 V3.4.1

(2010-08)

1 Clear description of the referenced document:

ETSI EN 300 392-2 V3.4.1 (2010-08): Terrestrial Trunked Radio (TETRA);Voice plus Data

(V+D);Part 2: Air Interface (AI)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document defines the Air Interface (AI) for the Terrestrial Trunked Radio (TETRA) system supporting Voice plus Data (V+D) and contains the specifications of the physical layer, the data link layer and the network layer according to the ISO model. This reference is needed to specify the trigger points in Rec. E.804.

4 Current information, if any, about IPR issues:

See: http://www.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] ETSI TS 100 900: "Digital cellular telecommunications system (Phase 2+) (GSM);

Alphabets and language-specific information (GSM 03.38 version 7.2.0 Release 1998)".

[2] ETSI TS 123 040: "Digital cellular telecommunications system (Phase 2+); Universal

Mobile Telecommunications System (UMTS); Technical realization of Short Message Service

(SMS) (3GPP TS 23.040)".

[3] ETSI ES 202 109: "Terrestrial Trunked Radio (TETRA); Security; Synchronization mechanism for end-to-end encryption".

[4] ETSI EN 300 113-1: "Electromagnetic compatibility and Radio spectrum Matters (ERM);

Land mobile service; Radio equipment intended for the transmission of data (and/or speech) using

- 7 - constant or non-constant envelope modulation and having an antenna connector; Part 1: Technical characteristics and methods of measurement".

[5] ETSI ETS 300 125: "Integrated Services Digital Network (ISDN); User-network interface data link layer specification; Application of CCITT Recommendations Q.920/I.440 and

Q.921/I.441".

[6] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 1:

General network design".

[7] ETSI EN 300 392-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 5:

Peripheral Equipment Interface (PEI)".

[8] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 7:

Security".

[9] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part 9:

General requirements for supplementary services".

[10] ETSI EN/ETSI ETS 300 392-12 (all subparts): "Terrestrial Trunked Radio (TETRA);

Voice plus Data (V+D); Part 12: Supplementary services stage 3".

[11] ETSI EN 300 392-12-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 1: Call Identification (CI)".

[12] ETSI EN 300 392-12-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 3: Talking Party Identification (TPI)".

[13] ETSI ETS 300 392-12-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 7: Short Number Addressing (SNA)".

[14] ETSI EN 300 392-12-8: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 8: Area Selection (AS)".

[15] ETSI EN 300 392-12-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 10: Priority Call (PC)".

[16] ETSI EN 300 392-12-16: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 16: Pre-emptive Priority Call (PPC)".

- 8 -

[17] ETSI EN 300 392-12-22: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 22: Dynamic Group Number Assignment

(DGNA)".

[18] ETSI TS 100 392-15: "Terrestrial Trunked Radio (TETRA) Voice plus DATA (V+D); Part

15: TETRA frequency bands, duplex spacings and channel numbering".

[19] ETSI TS 100 392-18-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and

Direct Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 1: Location

Information Protocol (LIP)".

[20] ETSI TS 100 392-18-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and

Direct Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 2: Net

Assist Protocol (NAP)".

[21] ETSI EN 300 395-2: "Terrestrial Trunked Radio (TETRA); Speech codec for full-rate traffic channel; Part 2: TETRA codec".

[22] ETSI EN 300 396-3: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile Station (MS-MS) Air Interface

(AI) protocol".

[23] ETSI EN 300 396-4: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 4: Type 1 repeater air interface".

[24] ETSI EN 300 396-5: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 5: Gateway air interface".

[25] ETSI EN 300 396-7: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 7: Type 2 repeater air interface".

[26] ETSI EN 300 396-10: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 10: Managed Direct Mode Operation (M-DMO)".

[27] ITU-T Recommendation V.42bis: "Data compression procedures for data circuitterminating equipment (DCE) using error correcting procedures".

- 9 -

[28] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and

Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".

[29] IETF RFC 1144: "Compressing TCP/IP Headers for Low-Speed Serial Links".

[30] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".

[31] IETF RFC 1662: "PPP in HDLC-like Framing".

[32] IETF RFC 1977: "PPP BSD Compression Protocol".

[33] IETF RFC 1978: "PPP Predictor Compression Protocol".

[34] IETF RFC 1994: "PPP Challenge Handshake Authentication Protocol (CHAP)".

[35] IETF RFC 2507: "IP Header Compression".

[36] IETF RFC 2508: "Compressing IP/UDP/RTP Headers for Low-Speed Serial Links".

[37] IETF RFC 2865: "Remote Authentication Dial In User Service (RADIUS)".

[38] IETF RFC 3232: "Assigned Numbers: RFC 1700 is Replaced by an On-line Database".

[39] IETF RFC 3344: "IP Mobility Support for IPv4".

NOTE: Obsoletes IETF RFC 3220.

[40] ISO/IEC 8859 (all parts): "Information technology - 8-bit single-byte coded graphic character sets".

[41] ISO/IEC 10646: "Information technology - Universal Multiple-Octet Coded Character Set

(UCS)".

[42] ITU-T Recommendation E.218: "Management of the allocation of terrestrial trunk radio

Mobile Country Codes".

- 10 -

[43] IETF RFC 2474 (December 1998): "Definition of the Differentiated Services Field (DS

Field) in the IPv4 and IPv6 Headers".

NOTE: Available at http://www.ietf.org/rfc/rfc2474.txt.

[44] IETF RFC 2475 (December 1998): "Architecture for Differentiated Services".

NOTE: Availeble at http://www.ietf.org/rfc/rfc2475.txt.

[45] IETF RFC 2597 (June 1999): "Assured Forwarding PHB Group".

NOTE: Available at http://www.ietf.org/rfc/rfc2597.txt.

[46] IETF RFC 3246 (March 2002): "An Expedited Forwarding PHB (Per-Hop Behavior)".

[47] IETF RFC 1456 (May 1993): "Conventions for Encoding the Vietnamese Language;

VISCII: VIetnamese Standard Code for Information Interchange; VIQR: VIetnamese Quoted-

Readable Specification".

NOTE: Available at http://www.ietf.org/rfc/rfc1456.txt.

[48] ETSI TS 100 392-18-3: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D) and

Direct Mode Operation (DMO); Part 18: Air interface optimized applications; Sub-part 3: Direct mode Over The Air Management protocol (DOTAM)".

[i.1] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Designers' guide; Part 5: Guidance on Numbering and addressing".

[i.2] ETSI TS 144 012: "Digital cellular telecommunications system (Phase 2+); Short Message

Service Cell Broadcast (SMSCB) support on the mobile radio interface; (3GPP TS 44.012 version

7.0.0 Release 7)".

[i.3] ETSI EN 300 392-3-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D); Part

3: Interworking at the Inter-System Interface (ISI); Sub-part 5: Additional Network Feature for

Mobility Management (ANF-ISIMM)".

[i.4] ETSI ETS 300 392-10-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 10: Supplementary services stage 1; Sub-part 7: Short number addressing".

- 11 -

[i.5] ETSI ETS 300 392-11-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 11: Supplementary services stage 2; Sub-part 7: Short Number Addressing (SNA)".

[i.6] ETSI EN 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation

(DMO); Part 6: Security".

[i.7] ISO/IEC 8348: "Information technology - Open Systems Interconnection - Network service definition".

[i.8] ISO/IEC 13239: "Information technology - Telecommunications and information exchange between systems - High-level data link control (HDLC) procedures".

[i.9] Open Mobile Alliance, Ltd. Technical-WAP2-0-20021106: "The WAP 2.0 conformance release".

NOTE: Available at http://www.openmobilealliance.org/tech/affiliates/wap/wapindex.html#wap20.

[i.10] ETSI TS 122 060: "Digital cellular telecommunications system (Phase 2+); Universal

Mobile Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service description; Stage 1 (3GPP TS 22.060)".

[i.11] ETSI EN 301 344: "Digital cellular telecommunications system (Phase 2+) (GSM); General

Packet Radio Service (GPRS); Service description; Stage 2 (GSM 03.60)".

[i.12] ETSI TR 102 021-8: "Terrestrial Trunked Radio (TETRA); User Requirement Specification

TETRA Release 2; Part 8: Air - Ground - Air services".

[i.13] ETSI EN 300 394-1: "Terrestrial Trunked Radio (TETRA); Conformance testing specification; Part 1: Radio".

[i.14] IETF RFC 792: "Internet Control Message Protocol".

[i.15] IETF RFC 1191: "Path MTU discovery".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

- 12 -

10

None

Other (for any supplementary information):

- 13 -

Annex 2

A.5 justification information for the reference to ETSI EN 300 392-5 V2.2.1

(2010-07)

1 Clear description of the referenced document:

ETSI EN 300 392-5 V2.2.1 (2010-07): Terrestrial Trunked Radio (TETRA);Voice plus Data (V+D) and Direct Mode Operation (DMO);Part 5: Peripheral Equipment Interface (PEI)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document specifies the functional and technical aspects of TETRA Peripheral

Equipment Interface (PEI) that is the interface between a Terminal Equipment type 2 (TE2) and a

Mobile Termination type 2 (MT2) at reference point RT. This reference is required in Rec. E.804 to specify the test UE.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] ETSI EN 300 392-1: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 1: General network design".

[2] ETSI TS 101 369: "Digital cellular telecommunications system (Phase 2+); Terminal

Equipment to Mobile Station (TE-MS) multiplexer protocol (3GPP TS 07.10 version 7.2.0 Release

1998)".

[3] ETSI EN 300 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 2: Air Interface (AI)".

- 14 -

[4] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)".

[5] ITU-T Recommendation V.250: "Serial asynchronous automatic dialling and control".

[6] ITU-T Recommendation V.28: "Electrical characteristics for unbalanced double-current interchange circuits".

[7] ETSI TS 100 916 (V7.8.0): "Digital cellular telecommunications system (Phase 2+); AT

Command set for GSM Mobile Equipment (ME) (3GPP TS 07.07 version 7.8.0 Release 1998)".

[8] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly

International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange".

[9] ETSI TS 127 007 (V3.3.0): "Digital cellular telecommunications system (Phase 2+)

(GSM); Universal Mobile Telecommunications System (UMTS); AT command set for 3GPP User

Equipment (UE) (3G TS 27.007 version 3.3.0 Release 1999)".

[10] IETF RFC 1661: "The Point-to-Point Protocol (PPP)".

[11] IETF RFC 1662: "PPP in HDLC-like Framing".

[12] ETSI EN 300 392-9: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 9: General requirements for supplementary services".

[13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".

[14] ETSI EN 300 812-3: "Terrestrial Trunked Radio (TETRA); Subscriber Identity Module to

Mobile Equipment (SIM-ME) interface; Part 3: Integrated Circuit (IC); Physical, logical and TSIM application characteristics".

[15] ETSI ES 200 812-2: "Terrestrial Trunked Radio (TETRA); Subscriber Identity Module to

Mobile Equipment (TSIM-ME) interface; Part 2: Universal Integrated Circuit Card (UICC);

Characteristics of the TSIM application".

[16] ETSI ETS 300 392-12-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

- 15 -

Part 12: Supplementary services stage 3; Sub-part 7: Short Number Addressing (SNA)".

[17] ETSI EN 300 392-12-16: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 16: Pre-emptive Priority Call (PPC)".

[18] ISO 8859-1: "Information technology - 8-bit single-byte coded graphic character sets -

Part 1: Latin alphabet No. 1".

[19] ITU-T Recommendation T.35: "Procedure for the allocation of ITU-T defined codes for non-standard facilities".

[20] ETSI EN 300 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 7: Security".

[21] ETSI EN 300 392-12-8: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 8: Area Selection (AS)".

[22] ETSI TS 100 392-2: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 2: Air Interface (AI)".

[23] ETSI TS 100 392-7: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 7: Security".

[24] ETSI TS 100 392-15: "Terrestrial Trunked Radio (TETRA) Voice plus Data (V+D);

Part 15: TETRA frequency bands, duplex spacings and channel numbering".

- 16 -

[25] ETSI EN 300 396-3: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 3: Mobile Station to Mobile Station (MS-MS) Air Interface

(AI) protocol".

[26] ETSI EN 300 396-6: "Terrestrial Trunked Radio (TETRA); Direct Mode Operation

(DMO); Part 6: Security".

[27] ITU-T Recommendation V.42bis: "Data compression procedures for data circuitterminating equipment (DCE) using error correction procedures".

[28] USB Implementers Forum, Inc: "Universal Serial Bus (USB) Specification, Revision 2.0".

NOTE: Available at: www.usb.org.

[29] USB Implementers Forum Inc: "On-The-Go Supplement to the USB 2.0 Specification,

Revision 1.2".

NOTE: Available at: http://www.usb.org/home.

[30] USB Implementers Forum Inc.: "Wireless Universal Serial Bus Specification, Revision

1.0".

NOTE: Available at: www.usb.org.

[31] WiMedia Alliance: "Multiband OFDM Physical Layer Specification, Revision 1".

NOTE: Available at: http://www.wimedia.org/en/index.asp.

[32] Bluetooth Special Interest Group (SIG): "BLUETOOTH SPECIFICATION Version 2.1 +

EDR; 26 July 2007".

NOTE: Available at: https://www.bluetooth.org/apps/content/.

[33] PCCA STD-101: "Data Transmission Systems and Equipment - Serial Asynchronous

Automatic Dialing and Control for Character Mode DCE on Wireless Data Services".

NOTE: Available at: http://www.pcca.org/standards/standards2.htm.

- 17 -

[i.1] ETSI EN 300 392-12-10: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Part 12: Supplementary services stage 3; Sub-part 10: Priority Call (PC)".

[i.2] ETSI TS 100 585 (V7.0.1): "Digital cellular telecommunications system (Phase 2+)

(GSM); Use of Data Terminal Equipment - Data Circuit terminating; Equipment (DTE - DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)

(GSM 07.05 version 7.0.1 Release 1998)".

[i.3] ETSI TS 101 356 (V7.2.0): "Digital cellular telecommunications system (Phase 2+);

General Packet Radio Service (GPRS); Mobile Station (MS) supporting GPRS

(GSM 07.60 version 7.2.0 Release 1998)".

[i.4] ETSI EN 300 396-10: "Terrestrial Trunked Radio (TETRA); Technical requirements for

Direct Mode Operation (DMO); Part 10: Managed Direct Mode Operation (M-DMO)".

[i.5] ITU-T Recommendation H.264: "Advanced video coding for generic audiovisual services".

[i.6] ETSI Drafting Rules (EDRs).

NOTE: Available at http://portal.etsi.org/edithelp/HowToStart/home.htm?page=DraftingRules.

[i.7] ETSI TR 102 300-5: "Terrestrial Trunked Radio (TETRA); Voice plus Data (V+D);

Designers' guide; Part 5: Guidance on numbering and addressing".

[i.8] ETSI EN 301 344: "Digital cellular telecommunications system (Phase 2+) (GSM); General

Packet Radio Service (GPRS); Service description; Stage 2 (GSM 03.60)".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 18 -

Annex 3

A.5 justification information for the reference to ETSI TR 102 493 V1.2.1 (2009-

06)

1 Clear description of the referenced document:

ETSI TR 102 493 V1.2.1 (2009-06): Speech and multimedia Transmission Quality

(STQ);Guidelines for the use of Video Quality Algorithms for Mobile Applications

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document gives guidelines for the use of video quality algorithms for the different services and scenarios applied in the mobile environment. This reference is neede in Rec. E.804 to define content integrity.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[i.1] ETSI TS 126 233: "Universal Mobile Telecommunications System (UMTS); LTE; End-toend transparent streaming service; General description (3GPP TS 26.233 version 8.0.0

Release 8)".

[i.2] VQEG: "Multimedia Group: Test Plan", Draft Version 1.5, March 2005.

[i.3] ETSI TS 122 960: "Universal Mobile Telecommunications System (UMTS); Mobile

Multimedia services including mobile Intranet and Internet services".

[i.4] Final Report from the Video Quality Experts Group on the validation of the objective models of multimedia quality assessment, Phase.

[i.5] ITU-T Recommendation J.247: Objective perceptual multimedia video quality measurement in presence of a full reference.

- 19 -

[i.6] ITU-T Recommendation J.246: Perceptual visual quality measurement techniques for multimedia services over digital cable television networks in the presence of a reduced bandwidth reference.

[i.7] ETSI TS 126 114: "Universal Mobile Telecommunications System (UMTS); LTE; IP

Multimedia Subsystem (IMS); Multimedia telephony; Media handling and interaction

(3GPP TS 26.114 Release 7)".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 20 -

Annex 4

A.5 justification information for the reference to ETSI TR 102 581 V1.1.1 (2007-

05)

1 Clear description of the referenced document:

ETSI TR 102 581 V1.1.1 (2007-05): Speech Processing, Transmission and Quality Aspects

(STQ);A Study on the Minimum Additional Required Attenuation on the Antenna Path of the Field

Test Equipment

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document presents a theoretical model to be used for the estimation of the minimum required additional attenuation on the antenna path of the field test equipment in order for this to emulate the real life scenarios. This reference is needed in Rec. E.804 to specify requirements for

Quality of Service measurement equipment.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] ETSI TS 102 250-4: "Speech Processing, Transmission and Quality Aspects (STQ); QoS aspects for popular services in GSM and 3G networks; Part 4: Requirements for Quality of

Service measurement equipment".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 21 -

Annex 5

A.5 justification information for the reference to ETSI TS 100 910 V8.20.0

(2005-11)

1 Clear description of the referenced document:

ETSI TS 100 910 V8.20.0 (2005-11): Digital cellular telecommunications system (Phase 2+);Radio

Transmission and Reception (3GPP TS 05.05 version 8.20.0 Release 1999)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document defines the requirements for the transceiver of GSM. This reference is needed in Rec. E.804 to define antenna requirements for test UE.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TR 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms".

[2] 3GPP TS 02.06: "Digital cellular telecommunications system (Phase 2+); Types of Mobile

Stations (MS)".

[3] 3GPP TS 03.64: "Digital cellular telecommunications system (Phase 2+); General Packet

Radio Service (GPRS); GPRS Radio Interface Stage 2".

[3a] 3GPP TS 03.71: "Digital cellular telecommunication system (Phase 2+); Location Services;

Functional description – Stage 2".

[4] 3GPP TS 05.01: "Digital cellular telecommunications system (Phase 2+); Physical layer on the radio path General description".

- 22 -

[5] 3GPP TS 05.04: "Digital cellular telecommunications system (Phase 2+); Modulation".

[6] 3GPP TS 05.08: "Digital cellular telecommunications system (Phase 2+); Radio subsystem link control".

[7] 3GPP TS 05.10: "Digital cellular telecommunications system (Phase 2+); Radio subsystem synchronization".

[8] 3GPP TS 11.10: "Digital cellular telecommunications system (Phase 2+); Mobile Station

(MS) conformity specification".

[9] 3GPP TS 11.11: "Digital cellular telecommunications system (Phase 2+); Specification of the Subscriber Identity Module Mobile Equipment (SIM ME) interface".

[10] ITU T Recommendation O.153: "Basic parameters for the measurement of error performance at bit rates below the primary rate".

[11] ETSI EN 300 019 1 3: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1 3: Classification of environmental conditions Stationary use at weather protected locations".

[12] ETSI EN 300 019 1 4: "Equipment Engineering (EE); Environmental conditions and environmental tests for telecommunications equipment; Part 1 4: Classification of environmental conditions Stationary use at non weather protected locations".

[13] 3GPP TS 04.14: "Digital cellular telecommunications system (Phase 2+); Individual equipment type requirements and interworking; Special conformance testing functions".

[14]

FCC Title 47 CFR Part 24: “Personal Communication Services”, Subpart E “Broadband services”.

[15] 3GPP TS 03.52: "Digital cellular telecommunications system (Phase 2+); GSM Cordless

Telephony System (CTS); Lower layers of the CTS radio interface; Stage 2".

[16] ITU T Recommendation O.151 (1992): "Error performance measuring equipment operating at the primary rate and above".

[17] TIA/EIA-136-C: “TDMA Third Generation Wireless”.

- 23 -

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 24 -

Annex 6

A.5 justification information for the reference to ETSI TS 123 228 V11.10.0

(2013-12)

1 Clear description of the referenced document:

ETSI TS 123 228 V11.10.0 (2013-12): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;IP Multimedia Subsystem

(IMS);Stage 2 (3GPP TS 23.228 version 11.10.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

This document defines the stage-2 service description for the IP Multimedia Core Network

Subsystem (IMS), which includes the elements necessary to support IP Multimedia (IM) services.

This reference is needed in Rec. E.804 to describe the IMS Multimedia Telephony service.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TS 23.002: "Network Architecture".

[2] CCITT Recommendation E.164: "Numbering plan for the ISDN era".

[3] CCITT Recommendation Q.65: "Methodology – Stage 2 of the method for the characterisation of services supported by an ISDN".

[4] ITU Recommendation I.130: "Method for the characterization of telecommunication services supported by an ISDN and network capabilities of an ISDN".

[5] Void.

[6] Void.

- 25 -

[7] 3GPP TS 23.221: "Architectural Requirements".

[8] 3GPP TS 22.228: "Service requirements for the IP multimedia core network subsystem".

[9] 3GPP TS 23.207: "End-to-end QoS concept and architecture".

[10] Void.

[10a] 3GPP TS 24.229: "IP Multimedia Call Control based on SIP and SDP; Stage 3".

[11] Void.

[11a] 3GPP TS 29.207: "Policy control over Go interface".

[12] IETF RFC 3261: "SIP: Session Initiation Protocol".

[13] IETF RFC 3986: "Uniform Resource Identifiers (URI): Generic Syntax".

[14] IETF RFC 4282: "The Network Access Identifier".

[15] IETF RFC 3966: "The tel URI for Telephone Numbers".

[16] IETF RFC 3761 (April 2004): "The E.164 to Uniform Resource Identifiers (URI) Dynamic

Delegation Discovery System (DDDS) Application (ENUM)".

[16a] IETF RFC 4941: "Privacy Extensions for Stateless Address Autoconfiguration in IPv6".

[17] ITU Recommendation G.711: "Pulse code modulation (PCM) of voice frequencies".

[18] ITU Recommendation H.248: "Gateway control protocol".

[19] 3GPP TS 33.203: "Access Security for IP-based services".

[20] 3GPP TS 33.210: "Network Domain Security: IP network layer security".

- 26 -

[21] Void.

[22] 3GPP TR 22.941: "IP Based Multimedia Services Framework".

[23] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service description; Stage 2".

[24] 3GPP TS 23.003: "Technical Specification Group Core Network; Numbering, addressing and identification".

[25] 3GPP TS 32.240: "Telecommunication management; Charging management; Charging architecture and principles".

[26] 3GPP TS 32.260: "Telecommunication Management; Charging Management; IP

Multimedia Subsystem (IMS) charging".

[27] 3GPP TS 22.071: "Technical Specification Group Services and System Aspects, Location

Services (LCS); Service description, Stage 1".

[28] 3GPP TS 23.271: "Technical Specification Group Services and System Aspects, Functional stage 2 description of LCS".

[29] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic

(CAMEL) Phase 3 - Stage 2".

[29a] 3GPP TS 22.340: "IMS Messaging; Stage 1".

[30] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx Interfaces; Signalling flows and message contents".

[31] 3GPP TS 23.240: "3GPP Generic User Profile - Architecture; Stage 2".

[32] 3GPP TS 22.250: "IP Multimedia Subsystem (IMS) group management"; Stage 1".

[33] IETF RFC 2766: "Network Address Translation-Protocol Translation (NAT-PT)".

[34] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and

Considerations".

- 27 -

[35] Void.

[36] 3GPP TS 23.141: "3rd Generation Partnership Project; Technical Specification Group

Services and System Aspects; Presence Service".

[37] Void.

[38] IETF RFC 3840: "Indicating User Agent Capabilities in the Session Initiation Protocol

(SIP)".

[39] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)".

[40] IETF RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Asserted

Identity within Trusted Network".

[41] IETF RFC 3312: "Integration of resource management and Session Initiation Protocol

(SIP)".

[42] IETF RFC 3841: "Caller Preferences for the Session Initiation Protocol (SIP)".

[43] IETF RFC 3428: "Session Initiation Protocol (SIP) Extension for Instant Messaging".

[44] IETF RFC 3263: "Session Initiation Protocol (SIP): Locating SIP Servers".

[45] IETF RFC 5245: "Interactive Connectivity Establishment (ICE): A Protocol for Network

Address Translator (NAT) Traversal for Offer/Answer Protocols".

[46] IETF RFC 5766: "Traversal Using Relays around NAT (TURN): Relay Extensions to

Session Traversal Utilities for NAT (STUN)".

[47] IETF RFC 5389: "Session Traversal Utilities for NAT (STUN)".

[48] IETF RFC 5626: "Managing Client Initiated Connections in the Session Initiation Protocol

(SIP)".

[49] IETF RFC 5627: "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)".

- 28 -

[50] IETF RFC 5628: "Registration Event Package Extension for Session Initiation Protocol

(SIP) Globally Routable User Agent URIs (GRUUs)".

[51] IETF RFC 4787: "Network Address Translation (NAT) Behavioural Requirements for

Unicast UDP".

[52] 3GPP TS 23.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services; Stage 2".

[53] 3GPP TS 22.173: "IMS Multimedia Telephony Service and supplementary services; Stage

1".

[54] 3GPP TS 23.203: "Policy and Charging Control architecture".

[55] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".

[56] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet

Protocol (IP) access".

[57] IETF RFC 4769: "IANA Registration for an Enumservice Containing Public Switched

Telephone Network (PSTN) Signaling Information".

[58] 3GPP TS 23.167: "IP Multimedia Subsystem (IMS) emergency sessions".

[59] 3GPP TS 29.333: "Multimedia Resource Function Controller (MRFC) - Multimedia

Resource Function Processor (MRFP) Mp Interface; Stage 3".

[60] 3GPP2 X.S0011: "cdma2000 Wireless IP Network Standard".

[61] 3GPP2 C.S0001-D: "Introduction to cdma2000 Spread Spectrum Systems - Revision D".

[62] 3GPP2 C.S0024-A: "cdma2000 High Rate Packet Data Air Interface Standard, April 2004".

[63] 3GPP2 C.S0084-000: "Overview for Ultra Mobile Broadband (UMB) Air Interface

Specification".

[64] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".

- 29 -

[65] IETF RFC 3022: "Traditional IP Network Address Translator (Traditional NAT)".

[66] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services".

[67] 3GPP TS 23.237: "IP Multimedia Subsystem (IMS) Service Continuity".

[68] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[69] 3GPP TS 31.103: "Characteristics of the IP Multimedia Services Identity Module (ISIM) application".

[70] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved

Universal Terrestrial Radio Access Network (E-UTRAN) access".

[71] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage 2".

[72] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol".

[73] 3GPP TS 23.333: "Multimedia Resource Function Controller (MRFC) - Multimedia

Resource Function Processor (MRFP) Mp interface: Procedures Descriptions".

[74] 3GPP TS 23.334: " IMS Application Level Gateway (IMS-ALG) - IMS Access Gateway

(IMS-AGW) interface: Procedures Descriptions".

[75] 3GPP TS 29.162: "Interworking between the IM CN subsystem and IP networks".

[76] 3GPP TS 26.114: "IP Multimedia Subsystem (IMS); Multimedia Telephony; Media handling and interaction".

[77] 3GPP TS 22.153: "Multimedia priority service".

[78] IETF Draft, draft-kaplan-enum-sip-routing-01 "Routing SIP Requests with ENUM".

Editor's Note: The above document cannot be formally referenced until it is published as an RFC.

- 30 -

[79] 3GPP TS 29.328: "IP Multimedia (IM) Subsystem Sh Interface; Signalling flows and message contents".

[80] 3GPP TS 23.380: "IP Multimedia Subsystem (IMS); IMS Restoration Procedures".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 31 -

Annex 7

A.5 justification information for the reference to ETSI TS 124 008 V11.8.0

(2013-10)

1 Clear description of the referenced document:

ETSI TS 124 008 V11.8.0 (2013-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;Mobile radio interface Layer 3 specification;Core network protocols;Stage 3 (3GPP TS 24.008 version 11.8.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document specifies the procedures used at the radio interface core network protocols within the 3rd generation mobile telecommunications system and the digital cellular telecommunications system. The reference is needed for Rec. E.804 to describe timeout values for data services.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] Void.

[2] Void.

[2a] 3GPP TR 21.905 "Vocabulary for 3GPP Specifications"

[3] 3GPP TS 22.002: "Circuit Bearer Services (BS) supported by a Public Land Mobile

Network (PLMN)".

[4] 3GPP TS 22.003: "Teleservices supported by a Public Land Mobile Network (PLMN)".

[5] 3GPP TS 42.009: "Security aspects".

- 32 -

[5a] 3GPP TS 33.102: "3G security; Security architecture".

[6] Void.

[7] 3GPP TS 42.017: "Subscriber Identity Modules (SIM); Functional characteristics".

[8] 3GPP TS 22.101: "Service aspects; Service principles".

[8a] 3GPP TS 22.001: "Principles of circuit telecommunication services supported by a Public

Land Mobile Network (PLMN)".

[8b] 3GPP TS 23.038: "Alphabets and language-specific information".

[9] 3GPP TS 23.101: "General UMTS Architecture".

[9a] 3GPP TS 23.108: "Mobile radio interface layer 3 specification core network protocols;

Stage 2 (structured procedures)".

[10] 3GPP TS 23.003: "Numbering, addressing and identification".

[11] Void.

[12] 3GPP TS 23.014: "Support of Dual Tone Multi-Frequency (DTMF) signalling".

[12a] ETSI ES 201 235-2, v1.2.1: "Specification of Dual Tone Multi-Frequency (DTMF);

Transmitters and Receivers; Part 2: Transmitters".

[13] 3GPP TS 43.020: "Security-related network functions".

[14] 3GPP TS 23.122: "Non-Access-Stratum functions related to Mobile Station (MS) in idle mode".

[15] 3GPP TS 24.002: "GSM-UMTS Public Land Mobile Network (PLMN) access reference configuration".

- 33 -

[16] 3GPP TS 44.003: "Mobile Station - Base Station System (MS - BSS) interface; Channel structures and access capabilities".

[17] Void.

[18] 3GPP TS 44.005: "Data Link (DL) layer; General aspects".

[19] 3GPP TS 44.006: "Mobile Station - Base Station System (MS - BSS) interface; Data Link

(DL) layer specification".

[19a] 3GPP TS 25.321: "Medium Access Control (MAC) protocol specification".

[19b] 3GPP TS 25.322: "Radio Link Control (RLC) protocol specification".

[19c] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[20] 3GPP TS 24.007: "Mobile radio interface signalling layer 3; General aspects".

[21] 3GPP TS 24.010: "Mobile radio interface layer 3; Supplementary services specification;

General aspects".

[22] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".

[23] 3GPP TS 24.012: "Short Message Service Cell Broadcast (SMSCB) support on the mobile radio interface".

[23a] 3GPP TS 44.071: "Location Services (LCS); Mobile radio interface layer 3 specification."

[23b] 3GPP TS 44.031 "Location Services LCS); Mobile Station (MS) - Serving Mobile Location

Centre (SMLC); Radio Resource LCS Protocol (RRLP)".

[23c] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification"

[24] 3GPP TS 24.080: "Mobile radio Layer 3 supplementary service specification; Formats and coding".

- 34 -

[25] 3GPP TS 24.081: "Line identification supplementary services; Stage 3".

[26] Void.

[27] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services;

Stage 3".

[28] 3GPP TS 24.084: "MultiParty (MPTY) supplementary services; Stage 3".

[29] Void.

[30] Void.

[31] Void.

[32] 3GPP TS 45.002: "Multiplexing and multiple access on the radio path".

[33] 3GPP TS 45.005: "Radio transmission and reception".

[34] 3GPP TS 45.008: "Radio subsystem link control".

[35] Void.

[36] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations

(MS)".

[36a] 3GPP TS 27.060: "Mobile Station (MS) supporting Packet Switched Services ".

[37] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[38] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile

Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched

Telephone Network (PSTN)".

[39] 3GPP TS 51.010: "Mobile Station (MS) conformance specification".

- 35 -

[40] Void.

[41] ISO/IEC 646 (1991): "Information technology - ISO 7-bit coded character set for information interchange".

[42] ISO/IEC 6429: "Information technology - Control functions for coded character sets".

[43] ISO 8348 (1987): "Information technology -- Open Systems Interconnection -- Network

Service Definition".

[44] ITU-T Recommendation E.163: "Numbering plan for the international telephone service".

[45] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".

[46] ITU-T Recommendation E.212: "The international identification plan for mobile terminals and mobile users".

[47] ITU-T Recommendation F.69 (1993): "The international telex service - Service and operational provisions of telex destination codes and telex network identification codes".

[48] ITU-T Recommendation I.330: "ISDN numbering and addressing principles".

[49] ITU-T Recommendation Q.920 (1993): "ISDN user-network interface data link layer -

General aspects".

[50] ITU-T Recommendation Q.930 (1993): "ISDN user-network interface layer 3 - General aspects".

[51] ITU-T Recommendation I.500 (1993): "General structure of the ISDN interworking recommendations".

[52] ITU-T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly

International Alphabet No. 5 or IA5) - Information technology - 7-bit coded character set for information interchange".

[53] ITU Recommendation Q.931: "ISDN user-network interface layer 3 specification for basic control".

- 36 -

[54] ITU-T Recommendation V.21: "300 bits per second duplex modem standardized for use in the general switched telephone network".

[55] ITU-T Recommendation V.22: "1200 bits per second duplex modem standardized for use in the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits".

[56] ITU-T Recommendation V.22bis: "2400 bits per second duplex modem using the frequency division technique standardized for use on the general switched telephone network and on point-topoint 2-wire leased telephone-type circuits".

[57] Void.

[58] ITU-T Recommendation V.26ter: "2400 bits per second duplex modem using the echo cancellation technique standardized for use on the general switched telephone network and on point-to-point 2-wire leased telephone-type circuits".

[59] ITU-T Recommendation V.32: "A family of 2-wire, duplex modems operating at data signalling rates of up to 9600 bit/s for use on the general switched telephone network and on leased telephone-type circuits".

[60] ITU-T Recommendation V.110: "Support by an ISDN of data terminal equipments with V-

Series type interfaces".

[61] ITU-T Recommendation V.120: "Support by an ISDN of data terminal equipment with V-

Series type interfaces with provision for statistical multiplexing".

[62] ITU-T Recommendation X.21: "Interface between Data Terminal Equipment (DTE) and

Data Circuit-terminating Equipment (DCE) for synchronous operation on public data networks".

[63] Void.

[64] Void.

[65] ITU-T Recommendation X.30: "Support of X.21, X.21 bis and X.20 bis based Data

Terminal Equipments (DTEs) by an Integrated Services Digital Network (ISDN)".

[66] ITU-T Recommendation X.31: "Support of packet mode terminal equipment by an ISDN".

- 37 -

[67] Void.

[68] Void.

[69] ITU-T Recommendation X.121: "International numbering plan for public data networks".

[70] ETSI ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network interface layer 3; Specifications for basic call control".

[71] Void.

[72] ISO/IEC 10646: "Information technology -- Universal Multiple-Octet Coded Character Set

(UCS)".

[73] 3GPP TS 22.060: "General Packet Radio Service (GPRS); Service Description; Stage 1".

[74] 3GPP TS 23.060: "General Packet Radio Service (GPRS); Service Description; Stage 2".

[75] Void.

[75a] 3GPP TS 43.318: "Generic Access Network (GAN); Stage 2".

[76] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base

Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".

[76b] 3GPP TS 44.318: "Generic Access Network (GAN); Mobile GAN interface layer 3 specification; Stage 3".

[77] Void.

[78] 3GPP TS 44.065: "Mobile Station (MS) - Serving GPRS Support Node (SGSN);

Subnetwork Dependent Convergence Protocol (SNDCP)".

[78a] 3GPP TS 44.064: "Mobile Station - Serving GPRS Support Node (MS-SGSN) Logical

Link Control (LLC) Layer Specification".

- 38 -

[79] ITU Recommendation I.460: "Multiplexing, rate adaption and support of existing interfaces".

[80] 3GPP TS 26.111: "Codec for Circuit Switched Multimedia Telephony Service;

Modifications to H.324".

[81] 3GPP TS 23.107: "Quality of Service (QoS) concept and architecture".

[82] 3GPP TS 43.022: "Functions related to Mobile Station (MS) in idle mode and group receive mode".

[83] 3GPP TS 26.103: "Speech Codec List for GSM and UMTS".

[84] 3GPP TS 44.018: "Mobile radio interface layer 3 specification, Radio Resource Control

Protocol".

[85] 3GPP TS 48.008: "Mobile-services Switching Centre – Base Station System (MSC – BSS) interface; layer 3 specification".

[86] 3GPP TS 48.018: "General Packet Radio Service (GPRS); Base Station System (BSS) -

Serving GPRS Support Node (SGSN); BSS GPRS Protocol (BSSGP)".

[87] 3GPP TS 43.055: "Dual Transfer Mode (DTM); Stage 2".

[88] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP);

Stage 2".

[88a] 3GPP TS 23.093: "Technical realization of Completion of Calls to Busy Subscriber

(CCBS); Stage 2".

[89] 3GPP TS 22.042: "Network Identity and Time Zone (NITZ), Stage 1".

[90] 3GPP TS 23.040: "Technical realization of Short Message Service (SMS)".

[91] 3GPP TS 44.056: "GSM Cordless Telephony System (CTS), (Phase 1) CTS Radio Interface

Layer 3 Specification".

[92] 3GPP TS 23.226: "Global Text Telephony; Stage 2 "

- 39 -

[93] 3GPP TS 26.226: "Cellular Text Telephone Modem (CTM), General Description"

[94] 3GPP TS 23.236: "Intra Domain Connection of RAN Nodes to Multiple CN Nodes"

[95] 3GPP TS 24.229: "IP Multimedia Call Control Protocol based on SIP and SDP"

[96] 3GPP TS 23.205: "Bearer-independent circuit-switched core network; Stage 2".

[97] 3GPP TS 23.172: "UDI/RDI Fallback and Service Modification; Stage 2".

[98] 3GPP TS 25.304: "UE Procedures in Idle Mode and Procedures for Cell Reselection in

Connected Mode"

[99] IETF RFC 4291 (February 2006): "Internet Protocol Version 6 (IPv6) Addressing

Architecture".

[100] 3GPP TS 29.207: "Policy control over Go interface".

[101] 3GPP TS 21.111: "USIM and IC card requirements".

[102] IETF RFC 1661 (July 1994): "The Point-to-Point Protocol (PPP)".

[103] IETF RFC 3232 (January 2002): "Assigned Numbers: RFC 1700 is Replaced by an On-line

Database".

[104] 3GPP TS 23.034: "High Speed Circuit Switched Data (HSCSD) – Stage 2".

[105] 3GPP TS 23.271: "Functional stage 2 description of Location Services (LCS)".

[106] 3GPP TS 23.246: "Multimedia Broadcast/Multicast Service (MBMS); Architecture and

Functional Description".

[107] IETF RFC 3376 (October 2002): "Internet Group Management Protocol, Version 3".

[108] IETF RFC 2710 (October 1999): "Multicast Listener Discovery (MLD) for IPv6".

- 40 -

[109] 3GPP TS 23.251: "Network Sharing; Architecture and Functional Description".

[110] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network"

[111] 3GPP TS 44.118: "Radio Resource Control (RRC) protocol; Iu mode".

[112] 3GPP TS 31.102: "Characteristics of the USIM Application".

[113] 3GPP TS 43.129: "Packet-switched handover for GERAN A/Gb mode; Stage 2".

[114] 3GPP TS 23.009: "Handover procedures".

[115] 3GPP TR 23.903: "Redial solution for voice-video switching".

[116] 3GPP TS 24.279: "Combining Circuit Switched (CS) and IP Multimedia Subsystem (IMS) services, stage 3"

[117] ITU-T Recommendation H.324 Amendment 1: "New Annex K "Media Oriented

Negotiation Acceleration Procedure" and associated changes to Annex".

[118] ITU-T Recommendation H.324 Amendment 2: "New Annex L on text conversation and associated changes; corrections and clarifications to Annex K".

[119] ITU-T Recommendation H.245: "Control protocol for multimedia communication"

[120] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);

Stage 3".

[121] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User

Equipment (UE) procedures in idle mode".

[122] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".

[123] 3GPP TS 33.401: "3GPP System Architecture Evolution; Security architecture".

- 41 -

[124] 3GPP TS 24.303: "Mobility management based on Dual-Stack Mobile IPv6; Stage 3".

[125] 3GPP TS 24.327: "Mobility between 3GPP WLAN Interworking and 3GPP systems; GPRS and 3GPP I-WLAN aspects; Stage 3".

[126] 3GPP TS 23.216: "Single Radio Voice Call Continuity (SRVCC); Stage 2".

[127] 3GPP TS 23.002: "Network architecture".

[128] 3GPP TS 25.301: "Radio interface protocol architecture".

[129] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource

Control (RRC); Protocol specification".

[130] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting packet based services and Packet Data Networks (PDN)".

[131] 3GPP TS 23.221: "Architectural requirements".

[132] 3GPP TS 23.090: "Unstructured Supplementary Service Data (USSD); Stage 2".

[133] 3GPP TS 23.272: "Circuit Switched Fallback in Evolved Packet System; Stage 2".

[134] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".

[135] 3GPP TS 24.368: "Non-Access Stratum (NAS) configuration Management Object (MO)".

[136] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity; Stage 3".

[137] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol".

[138] 3GPP TS 22.011: "Service accessibility".

[139] IETF RFC 3633 (December 2003): "IPv6 Prefix Options for Dynamic Host Configuration

Protocol (DHCP) version 6".

- 42 -

[140] 3GPP TS 23.012: "Location management procedures".

[141] 3GPP TS 24.022: "Radio Link Protocol (RLP) for circuit switched bearer and teleservices".

[142] ITU-T Recommendation X.1: "International user classes of service in, and categories of access to, public data networks and Integrated Services Digital Networks (ISDNs)".

[143] ITU-T Recommendation X.25: "Interface between Data Terminal Equipment (DTE) and

Data Circuit-terminating Equipment (DCE) for terminals operating in the packet mode and connected to public data networks by dedicated circuit".

[144] ITU-T Recommendation X.213: "Information technology – Open Systems Interconnection

– Network service definition".

[145] ITU-T Recommendation I.334: "Principles relating ISDN numbers/sub-addresses to the

OSI reference model network layer addresses".

[146] ITU-T Recommendation H.223: "Multiplexing protocol for low bit rate multimedia communication".

[147] ITU-T Recommendation V.34: "A modem operating at data signalling rates of up to 33 600 bit/s for use on the general switched telephone network and on leased point-to-point 2-wire telephone-type circuits".

[148] IETF RFC 3810 (June 2004): "Multicast Listener Discovery Version 2 (MLDv2) for IPv6".

[149] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node

(SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification".

[150] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node (SGSN) related interfaces based on Diameter protocol".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 43 -

Annex 8

A.5 justification information for the reference to ETSI TS 125 304 V11.4.0

(2013-09)

1 Clear description of the referenced document:

ETSI TS 125 304 V11.4.0 (2013-09): Universal Mobile Telecommunications System (UMTS);User

Equipment (UE) procedures in idle mode and procedures for cell reselection in connected mode

(3GPP TS 25.304 version 11.4.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document specifies the Access Stratum (AS) part of the Idle Mode procedures applicable to a UE. This reference is needed in Rec. E.804 for the definition of trigger points regarding radio network unavailabilty.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TS 43.022: "Functions related to Mobile Station in idle mode and group receive mode".

[2] 3GPP TS 25.301: "Radio Interface Protocol Architecture".

[3] 3GPP TS 25.303: "Interlayer Procedures in Connected Mode".

[4] 3GPP TS 25.331: "Radio Resource Control (RRC); protocol specification".

[5] 3GPP TS 23.122: "NAS functions related to Mobile Station (MS) in idle mode ".

[6] 3GPP TR 25.922: "Radio Resource Management Strategies".

- 44 -

[7] 3GPP TS 25.211: "Physical channels and mapping of transport channels onto physical channels (FDD)".

[8] 3GPP TS 25.221: "Physical channels and mapping of transport channels onto physical channels (TDD)".

[9] 3GPP TS 22.011: "Service accessibility".

[10] 3GPP TS 25.133: "Requirements for Support of Radio Resource Management (FDD)".

[11] 3GPP TS 25.123: "Requirements for Support of Radio Resource Management (TDD)".

[12] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[13] 3GPP TS 45.008: "Radio subsystem link control".

[14] 3GPP TS 25.214: "Physical layer procedures (FDD)".

[15] 3GPP TS 25.224: "Physical Layer Procedures (TDD)".

[16] 3GPP TS 24.008: "Mobile radio interface layer 3 specification, Core Network Protocols -

Stage 3".

[17] 3GPP TS 25.346: "Introduction of the Multimedia Broadcast Multicast Service (MBMS) in the Radio Access Network (Stage-2)".

[18] 3GPP TS 36.304: "Evolved Universal Terrestrial Radio Access (E-UTRA); User

Equipment (UE) procedures in idle mode".

[19] 3GPP TS 25.321: "MAC Protocol Specification".

[20] 3GPP TS 37.320: "Universal Terrestrial Radio Access (UTRA) and Evolved Universal

Terrestrial Radio Access (E-UTRA); Radio measurement collection for Minimization of Drive

Tests (MDT); Overall description; Stage 2".

- 45 -

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 46 -

Annex 9

A.5 justification information for the reference to ETSI TS 127 005 V11.0.0

(2012-10)

1 Clear description of the referenced document:

ETSI TS 127 005 V11.0.0 (2012-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;Use of Data Terminal Equipment

- Data Circuit terminating Equipment (DTE - DCE) interface for Short Message Service (SMS) and

Cell Broadcast Service (CBS) (3GPP TS 27.005 version 11.0.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document defines three interface protocols for control of SMS functions within a

GSM/UMTS mobile telephone from a remote terminal via an asynchronous interface.The reference is needed in Rec. E.804 to define the properties of the test UE.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] Void.

[2] 3GPP TS 23.038: "Alphabets and language specific information".

[3] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) ".

[4] 3GPP TS 23.041: "Technical realization of the Cell Broadcast Service (CBS)".

[5] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols;

Stage 3".

[6] 3GPP TS 24.011: "Short Message Service (SMS) support on mobile radio interface".

- 47 -

[7] 3GPP TS 24.012: "Cell Broadcast Service (CBS) support on the mobile radio interface".

[8] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations

(MS)".

[9] 3GPP TS 27.007: "AT command set for User Equipment (UE)".

[10] 3GPP TS 51.011: "Specification of the Subscriber Identity Module Mobile Equipment

(SIM ME) interface".

[11] ITU-T Recommendation V.25ter: "Serial asynchronous automatic dialling and control".

[12] ITU-T Recommendation V.24: "List of definitions for interchange circuits between data terminal equipment (DTE) and data circuit-terminating equipment (DCE)".

[13] ITU-T Recommendation E.164: "The international public telecommunication numbering plan".

[14] ITU-T Recommendation E.163: "Numbering plan for the international telephone service".

[15] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[16] 3GPP TS 31.102: "Characteristics of the USIM application".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10 none

Other (for any supplementary information):

- 48 -

Annex 10

A.5 justification information for the reference to ETSI TS 127 007 V11.8.0

(2013-10)

1 Clear description of the referenced document:

ETSI TS 127 007 V11.8.0 (2013-10): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);LTE;AT command set for User

Equipment (UE) (3GPP TS 27.007 version 11.8.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document specifies a profile of AT commands and recommends that this profile be used for controlling Mobile Termination (MT) functions and GSM/UMTS network services from a

Terminal Equipment (TE) through Terminal Adaptor (TA). This reference is needed in Rec. E.804 to define test UE.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TS 22.002: "Bearer Services (BS) supported by a GSM Public Land Mobile Network

(PLMN)".

[2] 3GPP TS 22.003: "Teleservices supported by a GSM Public Land Mobile Network

(PLMN)".

[3] 3GPP TS 22.081: "Line identification supplementary services Stage 1".

[4] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services Stage 1".

[5] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services

Stage 1".

- 49 -

[6] 3GPP TS 22.088: "Call Barring (CB) supplementary services Stage 1".

[7] 3GPP TS 23.003: "Numbering, addressing and identification".

[8] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols-

Stage 3".

[9] GSM MoU SE.13, GSM MoU Permanent Reference Document SE.13: "GSM Mobile

Network Codes and Names".

[10] ITU T Recommendation E.212: "Identification plan for land mobile stations".

[11] ITU T Recommendation T.31: "Asynchronous facsimile DCE control, service class 1".

[12] ITU T Recommendation T.32: "Asynchronous facsimile DCE control, service class 2".

[13] ITU T Recommendation T.50: "International Reference Alphabet (IRA) (Formerly

International Alphabet No. 5 or IA5) Information technology 7 bit coded character set for information exchange".

[14] ITU T Recommendation V.250: "Serial asynchronous automatic dialling and control".

[15] TIA IS 99: "Data Services Option Standard for Wideband Spread Spectrum Digital Cellular

System".

[16] TIA IS 135: "800 MHz Cellular Systems, TDMA Services, Async Data and Fax".

[17] PCCA STD 101 Data Transmission Systems and Equipment: "Serial Asynchronous

Automatic Dialling and Control for Character Mode DCE on Wireless Data Services".

[18] 3GPP TS 24.022: "Radio Link Protocol (RLP) for data and telematic services on the

Mobile Station Base Station System (MS BSS) interface and the Base Station System Mobile services Switching Centre (BSS MSC) interface".

[19] 3GPP TS 22.030: "Man Machine Interface (MMI) of the Mobile Station (MS)".

[20] 3GPP TS 45.008: "Radio subsystem link control".

- 50 -

[21] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services Stage 1".

[22] 3GPP TS 22.084: "MultiParty (MPTY) supplementary services Stage 1".

[23] 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD) Stage 1".

[24] 3GPP TS 27.005: "Use of Data Terminal Equipment Data Circuit terminating Equipment

(DTE DCE) interface for Short Message Service (SMS) and Cell Broadcast Service (CBS)".

[25] 3GPP TS 23.038: "Alphabet and language specific information".

[26] 3GPP TS 22.024: "Description of Charge Advice Information (CAI)".

[27] 3GPP TS 22.086: "Advice of Charge (AoC) supplementary services Stage 1".

[28] 3GPP TS 51.011: "Specification of the Subscriber Identity Module Mobile Equipment

(SIM ME) interface".

[29] 3GPP TS 22.034: "High Speed Circuit Switched Data (HSCSD) - Stage 1".

[30] 3GPP TS 22.091: "Explicit Call Transfer (ECT) supplementary service - Stage 1".

[31] 3GPP TS 22.072: "Call Deflection (CD) supplementary service - Stage 1".

[32] ISO/IEC 10646: "Universal Multiple-Octet Coded Character Set (UCS)"; UCS2, 16 bit coding.

[33] 3GPP TS 22.022: "Personalization of GSM Mobile Equipment (ME) Mobile functionality specification".

[34] 3GPP TS 27.060: "General requirements on Mobile Stations (MS) supporting General

Packet Radio Bearer Service (GPRS)".

[35] Void.

- 51 -

[36] CCITT Recommendation V.120: "Support by an ISDN of data terminal equipment with V-

Series type interfaces with provision for statistical multiplexing".

[37] Void.

[38] 3GPP TS 45.005: "Radio transmission and reception".

[39] 3GPP TS 29.061: "Interworking between the Public Land Mobile Network (PLMN) supporting GPRS and Packet Data Networks (PDN)".

[40] 3GPP TS 23.081: "Line identification supplementary services Stage 2".

[41] 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations

(MS)".

[42] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile

Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched

Telephone Network (PSTN)".

[43] Infrared Data Association; Specification of Ir Mobile Communications (IrMC).

[44] IrDA Object Exchange Protocol.

[45] 3GPP TS 27.010: "Terminal Equipment to User Equipment (TE-UE) multiplexer protocol

User Equipment (UE)".

[46] 3GPP TS 23.107: "Quality of Service, Concept and Architecture".

[47] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".

[48] Void.

[49] 3GPP TS 43.068: "Voice Group Call service (VGCS) - Stage 2".

[50] 3GPP TS 43.069: "Voice Broadcast Service (VBS) - Stage 2".

[51] Void.

- 52 -

[52] 3GPP TS 44.068: "Voice Group Call service (VGCS) - Stage 3".

[53] 3GPP TS 44.069: "Voice Broadcast Service (VBS) - Stage 3".

[54] 3GPP TS 22.067: "enhanced Multi Level Precedence and Pre emption service (eMLPP)

Stage 1".

[55] 3GPP TS 42.068: "Voice Group Call service (VGCS) - Stage 1".

[56] 3GPP TS 42.069: "Voice Broadcast Service (VBS) - Stage 1".

[57] Void.

[58] 3GPP TS 22.087: "User-to-User Signalling (UUS) - Stage 1".

[59] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM)

Application".

[60] ETSI TS 102 221 "Smart Cards; UICC-Terminal interface; Physical and logical characteristics (Release 1999)".

[61] 3GPP TS 44.065: "Mobile Station (MS) – Serving GPRS Support Node (SGSN);

Subnetwork Dependent Convergence Protocol (SNDCP)".

[62] 3GPP TS 25.323: "Packet Data Convergence Protocol (PDCP)".

[63] 3GPP TS 23.227 "Applications and User interaction in the UE-Principles and specific requirements".

[64] Void.

[65] 3GPP TS 31.101: "UICC-Terminal Interface; Physical and Logical Characteristics."

[66] ETSI TS 102 310: "Smart Cards; Extensible Authentication Protocol support in the UICC".

[67] Void.

- 53 -

[68] RFC 3748: "Extensible Authentication Protocol (EAP)".

[69] RFC 3629: "UTF-8, a transformation format of ISO 10646".

[70] 3GPP TS 44.318: "Generic Access (GA) to the A/Gb interface; Mobile GA interface layer

3 specification".

[71] 3GPP TS 44.060: "General Packet Radio Service (GPRS); Mobile Station (MS) - Base

Station System (BSS) interface; Radio Link Control/Medium Access Control (RLC/MAC) protocol".

[72] 3GPP TS 25.308: "High Speed Downlink Packet Access (HSDPA): Overall Description;

Stage 2".

[73] 3GPP TS 25.319: "Enhanced Uplink; Overall Description; Stage 2".

[74] 3GPP TS 25.331: "Radio Resource Control (RRC) protocol specification".

[75] 3GPP TS 24.216: "Communication Continuity Management Object (MO)".

[76] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".

[77] 3GPP TS 25.305 "User Equipment (UE) positioning in Universal Terrestrial Radio Access

Network (UTRAN); Stage 2".

[78] IEC 61162: "Maritime navigation and radio communication equipment and systems –

Digital interfaces".

[79] 3GPP TS 44.031: "Location Services (LCS); Mobile Station (MS) - Serving Mobile

Location Centre (SMLC), Radio Resource LCS Protocol (RRLP)".

[80] 3GPP TS 49.031: "Base Station System Application Part, LCS Extension (BSSAP-LE)".

[81] Void.

[82] 3GPP TS 23.401: "GPRS enhancements for E-UTRAN access".

- 54 -

[83] 3GPP TS 24.301: "Non-Access-Stratum (NAS) protocol for Evolved Packet System

(EPS)".

[84] Void.

[85] 3GPP TS 23.203: "Policy and charging control architecture".

[86] 3GPP TS 36.331: "Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource

Control (RRC); Protocol specification".

[87] 3GPP TS 24.173: "IMS multimedia telephony communication service and supplementary services; Stage 3".

[88] RFC 4291: "IP Version 6 Addressing Architecture".

[89] 3GPP TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol

(SIP) and Session Description Protocol (SDP)".

[90] 3GPP TS 23.221: "Architectural requirements".

[91] 3GPP TS 24.237: "IP Multimedia Subsystem (IMS) Service Continuity".

[92] 3GPP TS 31.111: "Universal Subscriber Identity Module (USIM) Application Toolkit

(USAT)".

[93] 3GPP TS 22.096: "Name identification supplementary services Stage 1".

[94] 3GPP TS 23.096: "Name identification supplementary services Stage 2".

[95] 3GPP TS 25.133: "Requirements for support of radio resource management (FDD)".

[96] 3GPP TS 25.123: "Requirements for support of radio resource management (TDD)".

[97] 3GPP TS 36.133: "Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management".

- 55 -

[98] 3GPP TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".

[99] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS)".

[100] 3GPP TS 23.041: "Technical realization of Cell Broadcast Service (CBS)".

[101] 3GPP TS 24.341: "Support of SMS over IP networks".

[102] 3GPP TS 24.167: "3GPP IMS Management Object (MO); Stage 3".

[103] IETF STD 5: "Internet Protocol".

[104] IETF STD 51: "The Point-to-Point Protocol (PPP)".

[105] RFC 1144: "Compressing TCP/IP Headers for Low-Speed Serial Links".

[106] RFC 2460: "Internet Protocol, Version 6 (IPv6) Specification".

[107] RFC 2507: "IP Header Compression".

[108] RFC 3095: "RObust Header Compression (ROHC): Framework and four profiles: RTP,

UDP, ESP, and uncompressed".

[109] 3GPP TS 24.080: "Mobile radio interface Layer 3 supplementary service specification;

Formats and coding".

[110] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[111] RFC 3261: "SIP: Session Initiation Protocol".

[112] RFC 3966: "The tel URI for Telephone Numbers".

[113] RFC 3969: "The Internet Assigned Number Authority (IANA) Uniform Resource Identifier

(URI) Parameter Registryfor the Session Initiation Protocol (SIP)".

- 56 -

[114] RFC 5341: "The Internet Assigned Number Authority (IANA) tel Uniform Resource

Identifier (URI) Parameter Registry".

[115] 3GPP TS 36.355: "Evolved Universal Terrestrial Radio Access (E-UTRA); LTE

Positioning Protocol (LPP)".

[116] RFC 2141: "URN Syntax".

[117] RFC 3406: "Uniform Resource Names (URN) Namespace Definition Mechanisms".

[118] RFC 5031: "A Uniform Resource Name (URN) for Emergency and Other Well-Known

Services".

[119] 3GPP TS 24.607: "Originating Identification Presentation (OIP) and Originating

Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[120] 3GPP TS 24.608: "Terminating Identification Presentation (TIP) and Terminating

Identification Restriction (TIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[121] 3GPP TS 24.654: "Closed User Group (CUG) using IP Multimedia (IM) Core Network

(CN) subsystem, Protocol Specification".

[122] RFC 4715: "The Integrated Services Digital Network (ISDN) Subaddress Encoding Type for tel URI".

[123] 3GPP TS 22.093: "Completion of Calls to Busy Subscriber (CCBS); Service description,

Stage 1".

[124] 3GPP TS 22.094: "Follow Me service description; Stage 1".

[125] 3GPP TS 22.097: "Multiple Subscriber Profile (MSP) Phase 2; Service description; Stage

1".

[126] 3GPP TS 22.135: "Multicall; Service description; Stage 1".

[127] 3GPP TS 24.182: "IP Multimedia Subsystem (IMS) Customized Alerting Tones (CAT);

Protocol specification".

- 57 -

[128] 3GPP TS 24.183: "IP Multimedia Subsystem (IMS) Customized Ringing Signal (CRS);

Protocol specification".

[129] 3GPP TS 24.239: "Flexible Alerting (FA) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[130] 3GPP TS 24.259: "Personal Network Management (PNM)".

[131] 3GPP TS 24.390: "Unstructured Supplementary Service Data (USSD) using IP Multimedia

(IM) Core Network (CN) subsystem IMS".

[132] 3GPP TS 24.604: "Communication Diversion (CDIV) using IP Multimedia (IM) Core

Network (CN) subsystem; Protocol specification".

[133] 3GPP TS 24.605: "Conference (CONF) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[134] 3GPP TS 24.606: "Message Waiting Indication (MWI) using IP Multimedia (IM) Core

Network (CN) subsystem; Protocol specification".

[135] 3GPP TS 24.610: "Communication HOLD (HOLD) using IP Multimedia (IM) Core

Network (CN) subsystem; Protocol specification".

[136] 3GPP TS 24.611: "Anonymous Communication Rejection (ACR) and Communication

Barring (CB) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".

[137] 3GPP TS 24.615: "Communication Waiting (CW) using IP Multimedia (IM) Core Network

(CN) subsystem; Protocol Specification".

[138] 3GPP TS 24.616: "Malicious Communication Identification (MCID) using IP Multimedia

(IM) Core Network (CN) subsystem; Protocol specification".

[139] 3GPP TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core

Network (CN) subsystem; Protocol specification".

[140] 3GPP TS 24.642: "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".

- 58 -

[141] 3GPP TS 24.647: "Advice Of Charge (AOC) using IP Multimedia (IM) Core Network

(CN) subsystem".

[142] 3GPP TS 36.509: "Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved

Packet Core (EPC); Special conformance testing functions for User Equipment (UE)".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 59 -

Annex 11

A.5 justification information for the reference to ETSI TS 129 002 V11.8.0

(2013-09)

1 Clear description of the referenced document:

ETSI TS 129 002 V11.8.0 (2013-09): Digital cellular telecommunications system (Phase

2+);Universal Mobile Telecommunications System (UMTS);Mobile Application Part (MAP) specification (3GPP TS 29.002 version 11.8.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document describes the requirements for the signalling system and the procedures needed at the application level in order to fulfil GSM signalling needs.This reference is needed in

Rec. E.804 to define trigger points for SMS and MMS.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications".

[2] 3GPP TS 22.001: "Digital cellular telecommunications system (Phase 2+); Principles of telecommunication services supported by a Public Land Mobile Network (PLMN)".

[3] 3GPP TS 22.002: "Bearer Services Supported by a Public Land Mobile Network (PLMN)".

[4] 3GPP TS 22.003: "Circuit Teleservices Supported by a Public Land Mobile Network

(PLMN)".

[5] 3GPP TS 22.004: "General on Supplementary Services".

- 60 -

[6] 3GPP TS 42.009: "Digital cellular telecommunications system (Phase 2+); Security aspects".

[7] 3GPP TS 22.016: "International Mobile station Equipment Identities (IMEI)".

[8] 3GPP TS 22.041: "Operator Determined Barring".

[9] 3GPP TS 22.081: "Line identification supplementary services - Stage 1".

[10] 3GPP TS 22.082: "Call Forwarding (CF) supplementary services - Stage 1".

[11] 3GPP TS 22.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services -

Stage 1".

[12] 3GPP TS 22.084: "Multi Party (MPTY) Supplementary Services - Stage 1".

[13] 3GPP TS 22.085: "Closed User Group (CUG) supplementary services - Stage 1".

[14] 3GPP TS 22.086: "Advice of charge (AoC) Supplementary Services - Stage 1".

[15] 3GPP TS 22.088: "Call Barring (CB) supplementary services - Stage 1".

[16] 3GPP TS 22.090: "Unstructured Supplementary Service Data (USSD); - Stage 1".

[17] 3GPP TS 23.003: "Numbering, addressing and identification".

[18] Void

[19] 3GPP TS 23.007: "Restoration procedures".

[20] 3GPP TS 23.008: "Organisation of subscriber data".

[21] 3GPP TS 23.009: "Handover procedures".

[22] 3GPP TS 23.011: "Technical realization of Supplementary Services - General Aspects".

- 61 -

[23] 3GPP TS 23.012: "Location management procedures".

[24] 3GPP TS 43.020: "Security related network functions".

[25] 3GPP TS 23.038: "Alphabets and language".

[25a] 3GPP TS 23.039: " Interface protocols for the connection of Short Message Service Centres

(SMSCs) to Short Message Entities (SMEs)".

[26] 3GPP TS 23.040: "Technical realization of the Short Message Service (SMS) Point to Point

(PP)".

[26a] 3GPP TS 23.271: "Functional stage2 description of LCS".

[27] 3GPP TS 23.081: "Line Identification Supplementary Services - Stage 2".

[28] 3GPP TS 23.082: "Call Forwarding (CF) Supplementary Services - Stage 2".

[29] 3GPP TS 23.083: "Call Waiting (CW) and Call Hold (HOLD) Supplementary Services -

Stage 2".

[30] 3GPP TS 23.084: "Multi Party (MPTY) Supplementary Services - Stage 2".

[31] 3GPP TS 23.085: "Closed User Group (CUG) Supplementary Services - Stage 2".

[32] 3GPP TS 23.086: "Advice of Charge (AoC) Supplementary Services - Stage 2".

[33] 3GPP TS 23.088: "Call Barring (CB) Supplementary Services - Stage 2".

[34] 3GPP TS 23.090: "Unstructured Supplementary Services Data (USSD) - Stage 2".

[34a] 3GPP TS 33.204: "3G Security; Network domain security; TCAP user security".

[35] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols -

Stage 3".

- 62 -

[36] 3GPP TS 24.010: "Mobile radio interface layer 3 Supplementary Services specification -

General aspects".

[37] 3GPP TS 24.011: "Point-to-Point (PP) Short Message Service (SMS) support on mobile radio interface".

[37a] 3GPP TS 44.071: "Location Services (LCS) – stage 3".

[38] 3GPP TS 24.080: "Mobile radio interface layer 3 supplementary services specification -

Formats and coding".

[39] 3GPP TS 24.081: "Line identification supplementary services - Stage 3".

[40] 3GPP TS 24.082: "Call Forwarding (CF) Supplementary Services - Stage 3".

[41] 3GPP TS 24.083: "Call Waiting (CW) and Call Hold (HOLD) supplementary services -

Stage 3".

[42] 3GPP TS 24.084: "Multi Party (MPTY) Supplementary Services - Stage 3".

[43] 3GPP TS 24.085: "Closed User Group (CUG) Supplementary Services - Stage 3".

[44] 3GPP TS 24.086: "Advice of Charge (AoC) Supplementary Services - Stage 3".

[45] 3GPP TS 24.088: "Call Barring (CB) Supplementary Services - Stage 3".

[46] 3GPP TS 24.090: "Unstructured Supplementary Services Data - Stage 3".

[47] 3GPP TS 48.002: " Base Station System - Mobile-services Switching Centre (BSS - MSC) interface principles".

[48] 3GPP TS 48.006: "Signalling transport mechanism specification for the Base Station

System - Mobile-services Switching Centre (BSS - MSC) interface".

[49] 3GPP TS 48.008: "Mobile Switching Centre - Base Station System (MSC - BSS) interface;

Layer 3 specification".

- 63 -

[49a1] 3GPP TS 48.031: "Location Services (LCS); Serving Mobile Location Centre (SMLC) –

Serving Mobile Location Centre (SMLC); SMLC Peer Protocol (SMLCPP)".

[49b] 3GPP TS 48.071: "Location Services (LCS); Serving Mobile Location Centre - Base

Station System (SMLC - BSS) interface Layer 3 specification".

[50] 3GPP TS 49.001: "General network interworking scenarios".

[51] 3GPP TS 29.002: "Mobile Application Part (MAP) specification".

[52] Void

[53] Void

[54] Void

[55] 3GPP TS 29.006: "Interworking between a Public Land Mobile Network (PLMN) and a

Packet Switched Public Data Network/Integrated Services Digital Network (PSPDN/ISDN) for the support of Packet Switched data transmission services".

[56] 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile

Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched

Telephone Network (PSTN)".

[57] 3GPP TS 29.008: "Application of the Base Station System Application Part (BSSAP) on the E-interface".

[58] 3GPP TS 29.010: "Information element mapping between Mobile Station - Base Station

System and BSS Mobile-services Switching Centre (MS - BSS - MSC) Signalling procedures and the Mobile Application Part (MAP)".

[59] 3GPP TS 29.011: "Signalling interworking for Supplementary Services".

[59a] 3GPP TS 49.031: "Digital cellular telecommunications system (Phase 2+); Location

Services (LCS); Base Station System Application Part LCS Extension (BSSAP-LE)".

[60] Void

- 64 -

[61] 3GPP TS 52.008: " GSM Subscriber and Equipment Trace".

[62] ETS 300 102-1 (1990): "Integrated Services Digital Network (ISDN); User-network interface layer 3 specifications for basic call control".

[63] ETS 300 136 (1992): "Integrated Services Digital Network (ISDN); Closed User Group

(CUG) supplementary service description".

[64] ETS 300 138 (1992): "Integrated Services Digital Network (ISDN); Closed User Group

(CUG) supplementary service Digital Subscriber Signalling System No.one (DSS1) protocol".

[65] ETS 300 287: "Integrated Services Digital Network (ISDN); Signalling System No.7;

Transaction Capabilities (TC) version 2".

[66] ETR 060: "Signalling Protocols and Switching (SPS); Guide-lines for using Abstract

Syntax Notation One (ASN.1) in telecommunication application protocols".

[66b] ETR 091: "ETSI object identifier tree; Common domain Mobile domain"

[67] ITU-T Recommendation E.164: " The international public telecommunication numbering plan".

[68] ITU-T Recommendation E.212: " The international identification plan for mobile terminals and mobile users".

[69] ITU-T Recommendation E.213: " Telephone and ISDN numbering plan for land mobile stations in public land mobile networks (PLMN) ".

[70] ITU-T Recommendation E.214: " Structure of the land mobile global title for the signalling connection control part (SCCP) ".

[71] ITU-T Recommendation Q.699: " Interworking between ISDN access and non-ISDN access over ISDN User Part of Signalling System No. 7 ".

[72] ITU-T Recommendation Q.711: "Specifications of Signalling System No.7; Functional description of the Signalling Connection Control Part".

[73] ITU-T Recommendation Q.712: "Definition and function of SCCP messages".

- 65 -

[74] ITU-T Recommendation Q.713: "Specifications of Signalling System No.7; SCCP formats and codes".

[75] ITU-T Recommendation Q.714: "Specifications of Signalling System No.7; Signalling

Connection Control Part procedures".

[76] ITU-T Recommendation Q.716: "Specifications of Signalling System No.7; Signalling connection control part (SCCP) performances".

[77] ITU-T Recommendation Q.721 (1988): "Specifications of Signalling System No.7;

Functional description of the Signalling System No.7 Telephone user part".

[78] ITU-T Recommendation Q.722 (1988): "Specifications of Signalling System No.7; General function of Telephone messages and signals".

[79] ITU-T Recommendation Q.723 (1988): "Specifications of Signalling System No.7; Formats and codes".

[80] ITU-T Recommendation Q.724 (1988): "Specifications of Signalling System No.7;

Signalling procedures".

[81] ITU-T Recommendation Q.725 (1988): "Specifications of Signalling System No.7;

Signalling performance in the telephone application".

[82] ITU-T Recommendation Q.761 (1988): "Specifications of Signalling System No.7;

Functional description of the ISDN user part of Signalling System No.7".

[83] ITU-T Recommendation Q.762 (1988): "Specifications of Signalling System No.7; General function of messages and signals".

[84] ITU-T Recommendation Q.763 (1988): "Specifications of Signalling System No.7; Formats and codes".

[85] ITU-T Recommendation Q.764 (1988): "Specifications of Signalling System No.7;

Signalling procedures".

[86] ITU-T Recommendation Q.767: "Specifications of Signalling System No.7; Application of the ISDN user part of CCITT signalling System No.7 for international ISDN interconnections".

- 66 -

[87] ITU-T Recommendation Q.771: "Specifications of Signalling System No.7; Functional description of transaction capabilities".

[88] ITU-T Recommendation Q.772: "Specifications of Signalling System No.7; Transaction capabilities information element definitions".

[89] ITU-T Recommendation Q.773: "Specifications of Signalling System No.7; Transaction capabilities formats and encoding".

[90] ITU-T Recommendation Q.774: "Specifications of Signalling System No.7; Transaction capabilities procedures".

[91] ITU-T Recommendation Q.775: "Specifications of Signalling System No.7; Guide-lines for using transaction capabilities".

[92] ITU-T Recommendation X.200: "Reference Model of Open systems interconnection for

CCITT Applications".

[93] ITU-T Recommendation X.680: "Information technology – Abstract Syntax Notation

One (ASN.1): Specification of basic notation".

[93b] ITU-T Recommendation X.681: "Information technology – Abstract Syntax Notation One

(ASN.1): Information object specification".

[94] ITU-T Recommendation X.690: "Information technology – ASN.1 encoding rules:

Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished

Encoding Rules (DER)".

[95] ITU-T Recommendation X.210: "Open systems interconnection layer service definition conventions".

[97] 3GPP TS 23.018: "Basic Call Handling".

[98] 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic

(CAMEL) Phase 4 - Stage 2".

[99] 3GPP TS 23.079: "Support of Optimal Routeing (SOR) - Stage 2".

[100] 3GPP TS 43.068: "Voice Group Call Service (VGCS) - Stage 2".

- 67 -

[101] 3GPP TS 43.069: "Voice Broadcast service (VBS) - Stage 2".

[102] ANSI T1.113: "Signaling System No. 7 (SS7) - ISDN User Part".

[103] Void

[104] 3GPP TS 23.060: "General Packet Radio Service (GPRS) Service description; Stage 2".

[105] 3GPP TS 29.060: "General Packet Radio Service (GPRS); GPRS Tunnelling Protocol

(GTP) across the Gn and Gp Interface".

[106] 3GPP TS 29.018: "General Packet Radio Service (GPRS); Serving GPRS Support Node

(SGSN) - Visitors Location Register (VLR); Gs interface layer 3 specification".

[107] 3GPP TS 23.093: "Technical Realization of Completion of Calls to Busy Subscriber

(CCBS); Stage 2".

[108] 3GPP TS 23.066: "Support of Mobile Number Portability (MNP); Technical Realisation

Stage 2".

[109] ANSI T1.112 (1996): "Telecommunication – Signalling No. 7 - Signaling Connection

Control Part (SCCP)".

[110] 3GPP TS 23.116: "Super-Charger Technical Realisation; Stage 2.".

[111] Void.

[112] Void

[113] Void

[114] Void

[115] Void

- 68 -

[116] ITU-T Recommendation Q.850 (May 1998): "Usage of cause and location in the Digital

Subscriber Signalling System No. 1 and the Signalling System No. 7 ISDN User Part".

[117] 3GPP TS 22.135: "Multicall; Service description; Stage 1".

[118] 3GPP TS 23.135: "Multicall supplementary service; Stage 2".

[119] 3GPP TS 24.135: "Multicall supplementary service; Stage 3".

[120] 3GPP TS 25.413: "UTRAN Iu interface Radio Access Network Application Part (RANAP) signalling".

[121] 3GPP TS 29.202: "SS7 signalling transport in core network".

[122] 3GPP TS 23.032: "Universal Geographical Area Description (GAD)".

[123] 3GPP TS 22.071: " Location Services (LCS); Service description, Stage 1".

[124] ITU-T Recommendation X.880: "Data networks and open system communication -

Open System Interconnection - Service definitions - Remote operations: Concepts, model and notation".

[125] 3GPP TS 23.278: "Customised Applications for Mobile Network Enhanced Logic

(CAMEL) Phase 4 – Stage 2 IM CN Interworking (Rel-5)".

[126] 3GPP TS 23.172: "Technical realization of Circuit Switched (CS) multimedia service;

UDI/RDI fallback and service modification".

[127] 3GPP TS 26.103: "Speech codec list for GSM and UMTS".

[128] 3GPP TS 23.141: "Presence Service; Architecture and Functional Description".

[129] 3GPP TS 23.094: "Follow Me (FM) – Stage 2".

[130] Void

[131] 3GPP TS 32.421: "Subscriber and equipment trace: Trace concepts and requirements".

- 69 -

[132] 3GPP TS 32.422: "Subscriber and equipment trace; Trace control and Configuration

Management".

[133] 3GPP TS 23.236: " Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core Network (CN) nodes".

[134] 3GPP TS 23.204: "Support of Short Message Service (SMS) over generic 3GPP Internet Protocol (IP) access".

[135] 3GPP TS 23.292: "IP Multimedia Subsystem (IMS) Centralized Services".

[136] 3GPP TS 23.067: "enhanced Multi-Level Precedence and Pre-emption service (eMLPP) -

Stage 2".

[137] 3GPP TS 24.067: "Enhanced Multi-Level Precedence and Pre-emption service (eMLPP);

Stage 3".

[138] 3GPP TS 22.011: "Service accessibility".

[139] IETF RFC 3588: "Diameter Base Protocol".

[140] Void

[141] 3GPP TS 29.173: "Locations Services; Diameter-based SLh interface for Control Plane

LCS".

[142] 3GPP TS 29.234: "3GPP system to Wireless Local Area Network (WLAN) Interworking;

Stage 3".

[143] 3GPP TS 23.272: "Circuit Switched (CS) fallback in Evolved Packet System (EPS); Stage

2".

[144] 3GPP TS 29.272: "Evolved Packet System (EPS); Mobility Management Entity (MME) and Service GPRS Support Node (SGSN) related interfaces based on Diameter protocol".

- 70 -

[145] 3GPP TS 23.401: "General Packet Radio Service (GPRS) enhancements for Evolved

Universal Terrestrial Radio Access Network (E-UTRAN) access".

[146] 3GPP TS 29.205: "Application of Q.1900 series to bearer independent Circuit Switched

(CS) core network architecture; Stage 3".

[147] 3GPP TS 36.413: "Evolved Universal Terrestrial Radio Access Network (E-UTRAN); S1

Application Protocol (S1AP)".

[148] 3GPP TS 23.682: "Architecture enhancements to facilitate communications with packet data networks and applications".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 71 -

Annex 12

A.5 justification information for the reference to ETSI TS 145 008 V11.5.0

(2013-09)

1 Clear description of the referenced document:

ETSI TS 145 008 V11.5.0 (2013-09): Digital cellular telecommunications system (Phase 2+);Radio subsystem link control (3GPP TS 45.008 version 11.5.0 Release 11)

2 Status of approval:

Approved by ETSI.

3 Justification for the specific reference:

The referred document specifies the Radio sub system link control implemented in the Mobile

Station (MS), Base Station System (BSS) and Mobile Switching Centre (MSC) of the digital cellular telecommunications systems GSM. This reference is needed in Rec. E.804 to describe network unavailabilty.

4 Current information, if any, about IPR issues:

See: http://ipr.etsi.org/.

5 Other useful information describing the "Quality" of the document:

The status of the referred ETSI document is "approved standards".

6 The degree of stability or maturity of the document:

The status of the referred ETSI document is published standard

7 none

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] 3GPP TR 21.905: 'Vocabulary for 3GPP Specifications'.

[2] 3GPP TS 23.003: 'Numbering, addressing and identification'.

[3] 3GPP TS 23.009: 'Handover procedures'.

[4] 3GPP TS 23.122: 'NAS Functions related to Mobile Station (MS) in idle mode'.

[5] 3GPP TS 25.101: 'UE Radio transmission and reception (FDD)'.

[6] 3GPP TS 25.123: 'Requirements for support of Radio Resource Management (TDD)'.

- 72 -

[7] 3GPP TS 25.133: 'Requirements for support of Radio Resource Management (FDD)'.

[8] 3GPP TS 25.304: 'UE Procedures in Idle Mode and Procedures for Cell Reselection in

Connected Mode'.

[9] 3GPP TS 25.331: 'Radio Resource Control (RRC); Protocol Specification'.

[10] 3GPP TS 26.093: 'AMR Speech Codec; Source Controlled Rate operation'.

[11] 3GPP TS 43.022: 'Functions related to Mobile Station (MS) in idle mode and group receive mode'.

[12] 3GPP TS 43.064: 'Overall description of the GPRS Radio Interface; Stage 2'.

[13] 3GPP TS 43.246: 'Multimedia Broadcast Multicast Service (MBMS) in the GERAN; Stage

2'.

[14] 3GPP TS 43.068: 'Voice Group Call Service (VGCS); Stage 2'.

[15] 3GPP TS 44.004: 'Layer 1; General requirements'.

[16] 3GPP TS 44.006: 'Mobile Station Base Station System (MS BSS) interface; Data Link

(DL) layer specification'.

[17] 3GPP TS 44.018: 'Mobile radio interface layer 3 specification; Radio Resource Control

Protocol'.

[18] 3GPP TS 44.056: 'GSM Cordless Telephony System (CTS), Phase 1; CTS radio interface layer 3 specification'.

[19] 3GPP TS 44.060: 'General Packet Radio Service (GPRS); Mobile Station (MS) - Base

Station System (BSS) interface; Radio Link Control (RLC) / Medium Access Control (MAC) protocol'.

[20] 3GPP TS 44.118: 'Mobile radio interface layer 3 specification, Radio Resource Control

(RRC) Protocol, Iu Mode'.

- 73 -

[21] 3GPP TS 44.160: 'Mobile Station (MS) - Base Station System (BSS) interface; Radio Link

Control/Medium Access Control (RLC/MAC) protocol; Iu mode'.

[22] 3GPP TS 45.002: 'Multiplexing and multiple access on the radio path'.

[23] 3GPP TS 45.003: 'Channel coding'

[24] 3GPP TS 45.005: 'Radio transmission and reception'.

[25] 3GPP TS 45.010: 'Radio subsystem synchronization'.

[26] 3GPP TS 45.056: 'CTS-FP radio subsystem'.

[27] 3GPP TR 45.902: 'Flexible Layer One'.

[28] 3GPP TS 46.011: 'Full rate speech; Substitution and muting of lost frames for full rate speech channels'.

[29] 3GPP TS 46.012: 'Full rate speech; Comfort noise aspect for full rate speech traffic channels'.

[30] 3GPP TS 46.031: 'Full rate speech; Discontinuous Transmission (DTX) for full rate speech traffic channels'.

[31] 3GPP TS 48.008: 'Mobile services Switching Centre Base Station System (MSC BSS) interface, Layer 3 specification'.

[32] 3GPP TS 48.058: 'Base Station Controller Base Transceiver Station (BSC BTS) interface; Layer 3 specification'.

[33] 3GPP TS 51.010: 'Mobile Station (MS) conformity specification'.

[34] 3GPP TS 51.011: 'Specification of the Subscriber Identity Module - Mobile Equipment

(SIM - ME) interface'.

[35] TIA/EIA/IS-2000-5-A: 'Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread

Spectrum Systems'.

- 74 -

[36] TIA/EIA/IS-833: 'Multi-Carrier Specification for Spread Spectrum Systems on GSM MAP

(MC-MAP) (Lower Layers Air Interface)'.

[37] 3GPP TS 36.101: 'Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment

(UE) radio transmission and reception'.

[38] 3GPP TS 36.104: 'Evolved Universal Terrestrial Radio Access (E-UTRA); Base Station

(BS) radio transmission and reception'.

[39] 3GPP TS 36.133: 'Evolved Universal Terrestrial Radio Access (E-UTRA); Requirements for support of radio resource management'.

[40] 3GPP TS 36.304: 'Evolved Universal Terrestrial Radio Access (E-UTRA); User Equipment

(UE) procedures in idle mode'.

[41] 3GPP TS 36.331: 'Evolved Universal Terrestrial Radio Access (E-UTRA); Radio Resource

Control (RRC); Protocol Specification'.

[42] 3GPP TS 31.102: 'Characteristics of the Universal Subscriber Identity Module (USIM) application'.

[43] 3GPP TS 24.301: 'Non-Access-Stratum (NAS) protocol for Evolved Packet System (EPS);

Stage 3'.

[44] 3GPP TS 22.268: 'Public Warning System (PWS) requirements; Stage 1'.

[45] 3GPP TS 23.251: "Network sharing; Architecture and functional description".

[46] 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core Network Protocols -

Stage 3".

9 Qualification of ETSI:

ETSI is recognized under the provisions of ITU-T Recommendations A.5 and A.6. Qualifying information is on file at TSB.

10

None

Other (for any supplementary information):

- 75 -

Annex 13

A.5 justification information for the reference to IETF RFC 1939 (1996)

1 Clear description of the referenced document:

IETF RFC 1939 (1996): Post Office Protocol - Version 3, May 1996

2 Status of approval:

The referred RFCs were approved by IESG (Internet Engineering Steering Group).

3 Justification for the specific reference:

The reference to RFC 1939 is needed in Rec. E.804 to define the trigger points for e-mail transaction time.

4 Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.

Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1939

5 Other useful information describing the "Quality" of the document:

The status of all the referred RFCs is "Proposed Standard".

6 The degree of stability or maturity of the document:

The status of all the referred RFCs is "Proposed Standard".

7 Relationship with other existing or emerging documents:

References within the referenced RFCs are listed under item (8).

8 Any explicit references within that referenced document should also be listed:

[1] Postel, J., "Simple Mail Transfer Protocol", STD 10, RFC 821, USC/Information Sciences

Institute, August 1982.

[2] Crocker, D., "Standard for the Format of ARPA-Internet Text Messages", STD 11, RFC 822,

University of Delaware, August 1982.

[3] Rivest, R., "The MD5 Message-Digest Algorithm", RFC 1321, MIT Laboratory for Computer

Science, April 1992.

[4] Crispin, M., "Internet Message Access Protocol - Version 4", RFC 1730, University of

Washington, December 1994.

[5] Myers, J., "POP3 AUTHentication command", RFC 1734, Carnegie Mellon, December 1994.

- 76 -

9 Qualification of ISOC/IETF:

9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).

9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.

9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All

RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10

None

Other (for any supplementary information):

- 77 -

Annex 14

A.5 justification information for the reference to IETF RFC 2177 (1997)

1 Clear description of the referenced document:

IETF RFC 2177 (1997): IMAP4 IDLE command

2 Status of approval:

Normative

3 Justification for the specific reference:

This document specifies the syntax of an IDLE command, which will allow a client to tell the server that it's ready to accept such real-time updates. This refence is needed in Rec. E.804 for the definition of store-and-forward services measurements.

4 Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.

5 Other useful information describing the "Quality" of the document:

It is a mature document..

6 The degree of stability or maturity of the document:

RFC 2177 has a status of STANDARD and was published in 1997. Since then it has been widely implemented and became one of the major components of Internet.

7 Relationship with other existing or emerging documents:

The following file is maintained by ISOC/IETF and has all the requested information: http://www.ietf.org/iesg/1rfc_index.txt .

8 Any explicit references within that referenced document should also be listed:

[IMAP4] Crispin, M., "Internet Message Access Protocol - Version

4rev1", RFC 2060, December 1996.

9 Qualification of ISOC/IETF:

9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).

9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.

- 78 -

9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All

RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10 none

Other (for any supplementary information):

- 79 -

Annex 15

A.5 justification information for the reference to IETF RFC 2326 (1998)

1 Clear description of the referenced document:

IETF RFC 2326 (1998): Real time Streaming protocol (RTSP)", H. Schulzrinne, A. Rao, R.

Lanphier, April 1998.

2 Status of approval:

Standards track, normative

3 Justification for the specific reference:

The reference to RFC 2326 is needed in Rec. E.804 to define the Real Time Streaming Protocol.

4 Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.

Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2326

5 Other useful information describing the "Quality" of the document:

This RFC has been in existence since April 1998 and is very widely used as video on demand control protocol.

6 The degree of stability or maturity of the document:

RFC 2326 was published in April 1998. It is a standards-track document and is currently in the

"Proposed Standard" state. Current standards status of this document can be found at ftp://ftp.ietf.org/rfc/rfc5000

7

None.

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[1] Schulzrinne, H., "RTP profile for audio and video conferences with minimal control", RFC

1890, January 1996.

[2] Fielding, R., Gettys, J., Mogul, J., Nielsen, H., and T. Berners-Lee, "Hypertext transfer protocol

- HTTP/1.1", RFC 2068, January 1997.

[3] Yergeau, F., Nicol, G., Adams, G., and M. Duerst, "Internationalization of the hypertext markup language", RFC 2070, January 1997.

[4] Bradner, S., "Key words for use in RFCs to indicate requirement levels", BCP 14, RFC 2119,

March 1997.

[5] ISO/IEC, "Information technology - generic coding of moving pictures and associated audio information - part 6: extension for digital storage media and control," Draft International Standard

- 80 -

ISO 13818-6, International Organization for Standardization ISO/IEC JTC1/SC29/WG11, Geneva,

Switzerland, Nov. 1995.

[6] Handley, M., and V. Jacobson, "SDP: Session Description Protocol", RFC 2327, April 1998.

[7] Franks, J., Hallam-Baker, P., and J. Hostetler, "An extension to HTTP: digest access authentication", RFC 2069, January 1997.

[8] Postel, J., "User Datagram Protocol", STD 6, RFC 768, August 1980.

[9] Hinden, B. and C. Partridge, "Version 2 of the reliable data protocol (RDP)", RFC 1151, April

1990.

[10] Postel, J., "Transmission control protocol", STD 7, RFC 793, September 1981.

[11] H. Schulzrinne, "A comprehensive multimedia control architecture for the Internet," in Proc.

International Workshop on Network and Operating System Support for Digital Audio and Video

(NOSSDAV), (St. Louis, Missouri), May 1997.

[12] International Telecommunication Union, "Visual telephone systems and equipment for local area networks which provide a non-guaranteed quality of service," Recommendation H.323,

Telecommunication Standardization Sector of ITU, Geneva, Switzerland, May 1996.

[13] McMahon, P., "GSS-API authentication method for SOCKS version 5", RFC 1961, June 1996.

[14] J. Miller, P. Resnick, and D. Singer, "Rating services and rating systems (and their machine readable descriptions)," Recommendation REC-PICS-services-961031, W3C (World Wide Web

Consortium), Boston, Massachusetts, Oct. 1996.

[15] J. Miller, T. Krauskopf, P. Resnick, and W. Treese, "PICS label distribution label syntax and communication protocols," Recommendation REC-PICS-labels-961031, W3C (World Wide Web

Consortium), Boston, Massachusetts, Oct. 1996.

[16] Crocker, D. and P. Overell, "Augmented BNF for syntax specifications: ABNF", RFC 2234,

November 1997.

[17] Braden, B., "Requirements for internet hosts - application and support", STD 3, RFC 1123,

October 1989.

- 81 -

[18] Elz, R., "A compact representation of IPv6 addresses", RFC 1924, April 1996.

[19] Berners-Lee, T., Masinter, L. and M. McCahill, "Uniform resource locators (URL)", RFC

1738, December 1994.

[20] Yergeau, F., "UTF-8, a transformation format of ISO 10646", RFC 2279, January 1998.

[21] Braden, B., "T/TCP - TCP extensions for transactions functional specification", RFC 1644,

July 1994.

[22] W. R. Stevens, TCP/IP illustrated: the implementation, vol. 2. Reading, Massachusetts:

Addison-Wesley, 1994.

[23] Schulzrinne, H., Casner, S., Frederick, R. and V. Jacobson, "RTP: a transport protocol for realtime applications", RFC 1889, January 1996.

[24] Fielding, R., "Relative uniform resource locators", RFC 1808, June 1995.

9 Qualification of ISOC/IETF:

9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).

9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.

9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All

RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10 Other (for any supplementary information):

References should always be made to RFC numbers (and not by other designations such as STD,

BCP, etc.). References not to be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic". Normative references should not be made to RFCs that are not standards, for example, "Informational" and "Experimental" RFCs.

- 82 -

Annex 16

A.5 justification information for the reference to IETF RFC 2821 (2001)

1 Clear description of the referenced document:

IETF RFC 2821 (2001): Mail Transfer Protocol, IETF RFC, April 2001

2 Status of approval:

The referred RFCs were approved by IESG (Internet Engineering Steering Group).

3 Justification for the specific reference:

The reference to RFC 2821 is needed in Rec. E.804 to define the trigger points for e-mail transaction time.

4 Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.

Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2821

5 Other useful information describing the "Quality" of the document:

The status of all the referred RFCs, is "Proposed Standard".

6 The degree of stability or maturity of the document:

The status of all the referred RFCs, is "Proposed Standard".

7 Relationship with other existing or emerging documents:

References within the referenced RFCs are listed under item (8).

8 Any explicit references within that referenced document should also be listed:

[1] American National Standards Institute (formerly United States of

America Standards Institute), X3.4, 1968, "USA Code for

Information Interchange". ANSI X3.4-1968 has been replaced by

newer versions with slight modifications, but the 1968 version

remains definitive for the Internet.

[2] Braden, R., "Requirements for Internet hosts - application and

- 83 -

support", STD 3, RFC 1123, October 1989.

[3] Butler, M., Chase, D., Goldberger, J., Postel, J. and J.

Reynolds, "Post Office Protocol - version 2", RFC 937, February

1985.

[4] Callas, J., Donnerhacke, L., Finney, H. and R. Thayer, "OpenPGP

Message Format", RFC 2440, November 1998.

[5] Crispin, M., "Interactive Mail Access Protocol - Version 2", RFC

1176, August 1990.

[6] Crispin, M., "Internet Message Access Protocol - Version 4", RFC

2060, December 1996.

[7] Crocker, D., "Standard for the Format of ARPA Internet Text

Messages", RFC 822, August 1982.

[8] Crocker, D. and P. Overell, Eds., "Augmented BNF for Syntax

- 84 -

Specifications: ABNF", RFC 2234, November 1997.

[9] De Winter, J., "SMTP Service Extension for Remote Message Queue

Starting", RFC 1985, August 1996.

[10] Fajman, R., "An Extensible Message Format for Message

Disposition Notifications", RFC 2298, March 1998.

[11] Freed, N, "Behavior of and Requirements for Internet Firewalls",

RFC 2979, October 2000.

[12] Freed, N. and N. Borenstein, "Multipurpose Internet Mail

Extensions (MIME) Part One: Format of Internet Message Bodies",

RFC 2045, December 1996.

[13] Freed, N., "SMTP Service Extension for Command Pipelining", RFC

2920, September 2000.

- 85 -

[14] Galvin, J., Murphy, S., Crocker, S. and N. Freed, "Security

Multiparts for MIME: Multipart/Signed and Multipart/Encrypted",

RFC 1847, October 1995.

[15] Gellens, R. and J. Klensin, "Message Submission", RFC 2476,

December 1998.

[16] Kille, S., "Mapping between X.400 and RFC822/MIME", RFC 2156,

January 1998.

[17] Hinden, R and S. Deering, Eds. "IP Version 6 Addressing

Architecture", RFC 2373, July 1998.

[18] Klensin, J., Freed, N. and K. Moore, "SMTP Service Extension for

Message Size Declaration", STD 10, RFC 1870, November 1995.

[19] Klensin, J., Freed, N., Rose, M., Stefferud, E. and D. Crocker,

"SMTP Service Extensions", STD 10, RFC 1869, November 1995.

- 86 -

[20] Klensin, J., Freed, N., Rose, M., Stefferud, E. and D. Crocker,

"SMTP Service Extension for 8bit-MIMEtransport", RFC 1652, July

1994.

[21] Lambert, M., "PCMAIL: A distributed mail system for personal

computers", RFC 1056, July 1988.

[22] Mockapetris, P., "Domain names - implementation and

specification", STD 13, RFC 1035, November 1987.

Mockapetris, P., "Domain names - concepts and facilities", STD

13, RFC 1034, November 1987.

[23] Moore, K., "MIME (Multipurpose Internet Mail Extensions) Part

Three: Message Header Extensions for Non-ASCII Text", RFC 2047,

December 1996.

- 87 -

[24] Moore, K., "SMTP Service Extension for Delivery Status

Notifications", RFC 1891, January 1996.

[25] Moore, K., and G. Vaudreuil, "An Extensible Message Format for

Delivery Status Notifications", RFC 1894, January 1996.

[26] Myers, J. and M. Rose, "Post Office Protocol - Version 3", STD

53, RFC 1939, May 1996.

[27] Partridge, C., "Mail routing and the domain system", RFC 974,

January 1986.

[28] Partridge, C., "Duplicate messages and SMTP", RFC 1047, February

1988.

[29] Postel, J., ed., "Transmission Control Protocol - DARPA Internet

Program Protocol Specification", STD 7, RFC 793, September 1981.

[30] Postel, J., "Simple Mail Transfer Protocol", RFC 821, August

- 88 -

1982.

[31] Ramsdell, B., Ed., "S/MIME Version 3 Message Specification", RFC

2633, June 1999.

[32] Resnick, P., Ed., "Internet Message Format", RFC 2822, April

2001.

[33] Vaudreuil, G., "SMTP Service Extensions for Transmission of

Large and Binary MIME Messages", RFC 1830, August 1995.

[34] Vaudreuil, G., "Enhanced Mail System Status Codes", RFC 1893,

January 1996.

9 Qualification of ISOC/IETF:

9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).

9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.

- 89 -

9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All

RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10

None

Other (for any supplementary information):

- 90 -

Annex 17

A.5 justification information for the reference to IETF RFC 3481 (2003)

1 Clear description of the referenced document:

IETF RFC 3481 (2003): TCP over Second (2.5G) and Third (3G) Generation Wireless Networks

2 Status of approval:

Approved

3 Justification for the specific reference:

This document describes a profile for optimizing TCP to adapt so that it handles paths including second (2.5G) and third (3G) generation

wireless networks. It describes the relevant characteristics of 2.5G and 3G networks, and specific features of example deployments of such

networks. This reference is needed in Rec. E.804 to describe media downloads.

4 Current information, if any, about IPR issues:

Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.

5 Other useful information describing the "Quality" of the document:

Proposed Standard

6 The degree of stability or maturity of the document:

Proposed Standard

7 Relationship with other existing or emerging documents:

References within the listed RFCs are listed under item (8).

8 Any explicit references within that referenced document should also be listed:

[1] Allman, M., Paxson, V. and W. Stevens, "TCP Congestion Control",

RFC 2581, April 1999.

[2] Jacobson, V., Braden, R. and D. Borman, "TCP Extensions for High

Performance", RFC 1323, May 1992.

- 91 -

[3] Mathis, M., Mahdavi, J., Floyd, S. and R. Romanow, "TCP

Selective Acknowledgment Options", RFC 2018, October 1996.

[4] Allman, M., Floyd, S. and C. Partridge, "Increasing TCP's

Initial Window", RFC 3390, October 2002.

Inamura, et al. Best Current Practice [Page 19]

RFC 3481 TCP over 2.5G/3G February 2003

[5] Dawkins, S., Montenegro, G., Kojo, M. and V. Magret, "End-to-end

Performance Implications of Slow Links", BCP 48, RFC 3150, July

2001.

[6] Mogul, J. and S. Deering, "Path MTU Discovery", RFC 1191,

November 1990.

[7] Knowles, S., "IESG Advice from Experience with Path MTU

Discovery", RFC 1435, March 1993.

- 92 -

[8] McCann, J., Deering, S. and J. Mogul, "Path MTU Discovery for IP

version 6", RFC 1981, August 1996.

[9] Ramakrishnan, K., Floyd, S. and D. Black, "The Addition of

Explicit Congestion Notification (ECN) to IP", RFC 3168,

September 2001.

[10] Allman, M., Balakrishnan, H. and S. Floyd, "Enhancing TCP's Loss

Recovery Using Limited Transmit", RFC 3042, January 2001.

[11] Paxson, V. and M. Allman, "Computing TCP's Retransmission

Timer", RFC 2988, November 2000.

[12] Bormann, C., Burmeister, C., Degermark, M., Fukushima, H.,

Hannu, H., Jonsson, L-E., Hakenberg, R., Koren, T., Le, K., Liu,

Z., Martensson, A., Miyazaki, A., Svanbro, K., Wiebke, T.,

- 93 -

Yoshimura, T. and H. Zheng, "RObust Header Compression (ROHC):

Framework and four profiles: RTP, UDP, ESP, and uncompressed",

RFC 3095, July 2001.

[13] Degermark, M., Nordgren, B. and S. Pink, "IP Header

Compression", RFC 2507, February 1999.

[14] Postel, J., "Transmission Control Protocol - DARPA Internet

Program Protocol Specification", STD 7, RFC 793, September 1981.

[15] Floyd, S. and T. Henderson, "The NewReno Modification to TCP's

Fast Recovery Algorithm", RFC 2582, April 1999.

[16] Bormann, C., "Robust Header Compression (ROHC) over PPP", RFC

3241, April 2002.

[17] Braden, R., "Requirements for Internet Hosts - Communication

Layers", STD 3, RFC 1122, October 1989.

- 94 -

[18] Deering, S. and R. Hinden, "Internet Protocol, Version 6 (IPv6)

Specification", RFC 2460, December 1998.

Inamura, et al. Best Current Practice [Page 20]

RFC 3481 TCP over 2.5G/3G February 2003

10. Informative References

[19] Montenegro, G., Dawkins, S., Kojo, M., Magret, V. and N.

Vaidya, "Long Thin Networks", RFC 2757, January 2000.

[20] Third Generation Partnership Project, "RLC Protocol

Specification (3G TS 25.322:)", 1999.

[21] Fall, K. and S. Floyd, "Simulation-based Comparisons of Tahoe,

Reno, and SACK TCP", Computer Communication Review, 26(3) , July

- 95 -

1996.

[22] Fairhurst, G. and L. Wood, "Advice to link designers on link

Automatic Repeat reQuest (ARQ)", BCP 62, RFC 3366, August 2002.

[23] Karn, P., "Advice for Internet Subnetwork Designers", Work in

Progress.

[24] Dawkins, S., Montenegro, G., Magret, V., Vaidya, N. and M.

Kojo, "End-to-end Performance Implications of Links with

Errors", BCP 50, RFC 3135, August 2001.

[25] Wireless Application Protocol, "WAP Specifications", 2002,

<http://www.wapforum.org>.

[26] Open Mobile Alliance, "Open Mobile Alliance", 2002,

<http://www.openmobilealliance.org/>.

- 96 -

[27] Braden, R., "T/TCP -- TCP Extensions for Transactions", RFC

1644, July 1994.

[28] Braden, R., Clark, D., Crowcroft, J., Davie, B., Deering, S.,

Estrin, D., Floyd, S., Jacobson, V., Minshall, G., Partridge,

C., Peterson, L., Ramakrishnan, K., Shenker, S., Wroclawski, J.

and L. Zhang, "Recommendations on Queue Management and

Congestion Avoidance in the Internet", RFC 2309, April 1998.

[29] IETF, "Robust Header Compression", 2001,

<http://www.ietf.org/html.charters/rohc-charter.html>.

[30] Ludwig, R. and R. H. Katz, "The Eifel Algorithm: Making TCP

Robust Against Spurious Retransmissions", ACM Computer

Communication Review 30(1), January 2000.

[31] Wireless Application Protocol, "WAP Wireless Profiled TCP",

- 97 -

WAP-225-TCP-20010331-a, April 2001,

<http://www.wapforum.com/what/technical.htm>.

Inamura, et al. Best Current Practice [Page 21]

RFC 3481 TCP over 2.5G/3G February 2003

[32] Hadi Salim, J. and U. Ahmed, "Performance Evaluation of Explicit

Congestion Notification (ECN) in IP Networks", RFC 2884, July

2000.

[33] NTT DoCoMo Technical Journal, "Special Issue on i-mode Service",

October 1999.

[34] NTT DoCoMo Technical Journal, "Special Article on IMT-2000

Services", September 2001.

[35] Floyd, S., Mahdavi, J., Mathis, M. and M. Podolsky, "An

Extension to the Selective Acknowledgement (SACK) Option for

- 98 -

TCP", RFC 2883, July 2000.

[36] Dierks, T. and C. Allen, "The TLS Protocol Version 1.0", RFC

2246, January 1999.

[37] Kent, S. and R. Atkinson, "Security Architecture for the

Internet Protocol", RFC 2401, November 1998.

[38] de Vivo, M., O. de Vivo, G., Koeneke, R. and G. Isern, "Internet

Vulnerabilities Related to TCP/IP and T/TCP", ACM Computer

Communication Review 29(1), January 1999.

[39] Third Generation Partnership Project, "RRC Protocol

Specification (3GPP TS 25.331:)", September 2001.

[40] Jacobson, V., "Compressing TCP/IP Headers for Low-Speed Serial

Links", RFC 1144, February 1990.

- 99 -

[41] Blanton, E. and M. Allman, "On Making TCP More Robust to Packet

Reordering", ACM Computer Communication Review 32(1), January

2002, <http://roland.grc.nasa.gov/~mallman/papers/tcp-reorder-

ccr.ps>.

[42] Karn, P. and C. Partridge, "Improving Round-Trip Time Estimates

in Reliable Transport Protocols", ACM SIGCOMM 87, 1987.

[43] Ludwig, R., Rathonyi, B., Konrad, A. and A. Joseph, "Multi-layer

tracing of TCP over a reliable wireless link", ACM SIGMETRICS

99, May 1999.

[44] Ludwig, R., Konrad, A., Joseph, A. and R. Katz, "Optimizing the

End-to-End Performance of Reliable Flows over Wireless Links",

Kluwer/ACM Wireless Networks Journal Vol. 8, Nos. 2/3, pp. 289-

299, March-May 2002.

- 100 -

Inamura, et al. Best Current Practice [Page 22]

RFC 3481 TCP over 2.5G/3G February 2003

[45] Gurtov, A., "Making TCP Robust Against Delay Spikes", University

of Helsinki, Department of Computer Science, Series of

Publications C, C-2001-53, Nov 2001,

<http://www.cs.helsinki.fi/u/gurtov/papers/report01.html>.

[46] Stevens, W., "TCP/IP Illustrated, Volume 1; The Protocols",

Addison Wesley, 1995.

[47] Braden, R., "TCP Extensions for High Performance: An Update",

Work in Progress.

[48] Allman, M., Dawkins, S., Glover, D., Griner, J., Tran, D.,

Henderson, T., Heidemann, J., Touch, J., Kruse, H., Ostermann,

S., Scott, K. and J. Semke, "Ongoing TCP Research Related to

- 101 -

Satellites", RFC 2760, February 2000.

[49] Allman, M., Glover, D. and L. Sanchez, "Enhancing TCP Over

Satellite Channels using Standard Mechanisms", BCP 28, RFC 2488,

January 1999.

[50] Balakrishnan, H., Padmanabhan, V., Fairhurst, G. and M.

Sooriyabandara, "TCP Performance Implications of Network

Asymmetry", RFC 3449, December 2002.

[51] Kempf, J., "Problem Description: Reasons For Performing Context

Transfers Between Nodes in an IP Access Network", RFC 3374,

September 2002.

[52] Khafizov, F. and M. Yavuz, "Running TCP over IS-2000", Proc. of

IEEE ICC, 2002.

[53] Khafizov, F. and M. Yavuz, "Analytical Model of RLP in IS-2000

- 102 -

CDMA Networks", Proc. of IEEE Vehicular Technology Conference,

September 2002.

[54] Yavuz, M. and F. Khafizov, "TCP over Wireless Links with

Variable Bandwidth", Proc. of IEEE Vehicular Technology

Conference, September 2002.

[55] TIA/EIA/cdma2000, "Mobile Station - Base Station Compatibility

Standard for Dual-Mode Wideband Spread Spectrum Cellular

Systems", Washington: Telecommunication Industry Association,

1999.

[56] TIA/EIA/IS-95 Rev A, "Mobile Station - Base Station

Compatibility Standard for Dual-Mode Wideband Spread Spectrum

Cellular Systems", Washington: Telecommunication Industry

Association, 1995.

- 103 -

Inamura, et al. Best Current Practice [Page 23]

RFC 3481 TCP over 2.5G/3G February 2003

[57] TIA/EIA/IS-707-A-2.10, "Data Service Options for Spread Spectrum

Systems: Radio Link Protocol Type 3", January 2000.

[58] Dahlman, E., Beming, P., Knutsson, J., Ovesjo, F., Persson, M.

and C. Roobol, "WCDMA - The Radio Interface for Future Mobile

Multimedia Communications", IEEE Trans. on Vehicular Technology,

vol. 47, no. 4, pp. 1105-1118, November 1998.

[59] Allman, M. and V. Paxson, "On Estimating End-to-End Network Path

Properties", ACM SIGCOMM 99, September 1999.

[60] Gurtov, A. and R. Ludwig, "Responding to Spurious Timeouts in

TCP", IEEE INFOCOM'03, March 2003

9 Qualification of ISOC/IETF:

9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).

- 104 -

9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.

9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All

RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.

10

None

Other (for any supplementary information):

- 105 -

Annex 18

A.5 justification information for the reference to OMA-AD-PoC-V2_0-

20110802-A

1 Clear description of the referenced document:

OMA-AD-PoC-V2_0-20110802-A: Push to talk over Cellular (PoC) - Architecture

2 Status of approval:

All of the documents are approved OMA specifications

3 Justification for the specific reference:

The scope of the Push to talk over Cellular (PoC) V2.0 architecture document is to define the architecture for the PoC Enabler V2.0. This reference is needed in Rec. E.804 to specify the Push to talk over cellular trigger points.

4 Current information, if any, about IPR issues: http://openmobilealliance.org/about-oma/policies-and-terms-of-use/intellectual-property-rights/

5 Other useful information describing the "Quality" of the document:

All of the documents are approved OMA specifications

6 The degree of stability or maturity of the document:

The documents are all approved OMA specifications that are undergoing continuing development

7

None

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[3GPP TS 23.002] 3GPP TS 23.002: "Network architecture". URL: http://www.3gpp.org/

[3GPP TS 23.228] 3GPP TS 23.228: "IP Multimedia Subsystem (IMS)", Stage 2. URL: http://www.3gpp.org/

[3GPP TS 32.272] 3GPP TS 32.272: "Push-to-Talk over Cellular (PoC) Charging". URL: http://www.3gpp.org/

[3GPP TS 33.203] 3GPP TS 33.203: "Access security for IP-based services". URL: http://www.3gpp.org/

[3GPP2 S.R0100-0] 3GPP2 S.R0100-0 Push-to-Talk over Cellular (PoC) System Requirements,

(v1.0). URL: http://www.3gpp2.org/

- 106 -

[3GPP2 X.S0013.2] 3GPP2 X.S0013.2: "IP Multimedia Subsystem (IMS)", Stage 2. URL: http://www.3gpp2.org/

[3GPP2 X.S0013-007] 3GPP2 X.S0013-007, All-IP Core Network Multimedia Domain: IP

Multimedia Subsystem - Charging Architecture. URL: http://www.3gpp2.org/ [OMA Charging

AD] "Charging Architecture", Version 1.0, Open Mobile Alliance™, OMA-AD-Charging-V1_0,

URL: http://www.openmobilealliance.org/

[OMA Client Provisioning] "OMA Client Provisioning", Version 1.1, Open Mobile Alliance™,

OMA-ERP-ClientProvisioning-V1_1, URL: http://www.openmobilealliance.org/

[OMA DM] "OMA Device Management Protocol", Version 1.2, Open Mobile Alliance™, OMA-

TS-DM_Protocol-V1_2, URL: http://www.openmobilealliance.org/

[OMA DM Bootstrap] "Device Management Bootstrap", Version 1.2, Open Mobile Alliance™,

OMA-TS-DM_Bootstrap-V1_2, URL: http://www.openmobilealliance.org/

[OMA IM AD] "Instant Messaging using SIMPLE Architecture", Version 1.0, Open Mobile

Alliance™, OMA-AD-SIMPLE_IM-V1_0, URL: http://www.openmobilealliance.org/

[OMA PoC V1.0 AD] "Push to Talk over Cellular (PoC) - Architecture", Version 1.0, Open Mobile

Alliance™, OMA-AD-PoC-V1_0_2, URL: http://www.openmobilealliance.org/

[OMA PoC V1.0 RD] "Push to Talk over Cellular Requirements", Version 1.0, Open Mobile

Alliance™, OMA-RD-PoC-V1_0, URL: http://www.openmobilealliance.org/

[OMA PoC V1.0 UP] "PoC User Plane", Version 1.0, Open Mobile Alliance™, OMA-TS-

PoC_UserPlane-V1_0_2, URL: http://www.openmobilealliance.org/

[OMA PoC V2.0 AD] "Push to Talk over Cellular (PoC) - Architecture", Version 2.0, Open

Mobile Alliance™, OMA-AD-PoC-V2_0, URL: http://www.openmobilealliance.org/

[OMA PoC V2.0 CP] "OMA PoC Control Plane", Version 2.0, Open Mobile Alliance™, OMA-TS-

PoC_ControlPlane-V2_0, URL: http://www.openmobilealliance.org/

[OMA PoC V2.0 Document-Mgmt] "OMA PoC Document Management", Version 2.0, Open

Mobile Alliance, OMA-TS-PoC_Document_Management-V2_0, URL: http://www.openmobilealliance.org/

- 107 -

[OMA PoC V2.0 RD] "Push to Talk over Cellular 2 Requirements", Version 2.0, Open Mobile

Alliance™, OMA-RD-PoC-V2_0, URL: http://www.openmobilealliance.org/

[OMA PoC V2.0 SD] "OMA PoC System Description", Version 2.0, Open Mobile Alliance,

OMA-TS-PoC_System_Description-V2_0, URL: http://www.openmobilealliance.org/

[OMA PoC V2.0 UP] "OMA PoC User Plane", Version 2.0, Open Mobile Alliance, OMA-TS-

PoC_UserPlane-V2_0, URL: http://www.openmobilealliance.org/

[OMA Presence V1.0 AD] "Presence SIMPLE Architecture Document", Version 1.0, Open Mobile

Alliance™, OMA-AD-Presence_SIMPLE-V1_0, URL: http://www.openmobilealliance.org/

[OMA XDM V2.0 AD] "XML Document Management Architecture", Version 2.0, Open Mobile

Alliance™, OMA-AD-XDM-V2_0, URL: http://www.openmobilealliance.org/

[RFC2119] IETF RFC 2119: "Key words for use in RFCs to Indicate Requirement Levels". S.

Bradner. March 1997. URL: http://www.ietf.org/rfc/rfc2119.txt [RFC2617] IETF RFC 2617:

"HTTP Authentication: Basic and Digest Access Authentication", J. Franks et al, June 1999. URL: http://www.ietf.org/rfc/rfc2617.txt

[RFC3261] IETF RFC 3261: "SIP: Session Initiation Protocol", J. Rosenberg et al, June 2002.

URL: http://www.ietf.org/rfc/rfc3261.txt

[RFC3265] IETF RFC 3265: "Session Initiation Protocol (SIP)-Specific Event Notification", A. B.

Roach, June 2002. URL: http://www.ietf.org/rfc/rfc3265.txt

[RFC4412] IETF RFC 4412: "Communications Resource Priority for the Session Initiation Protocol

(SIP)", H. Schulzrinne, J. Polk, February 2006. URL: http://www.ietf.org/rfc/rfc4412.txt

[3GPP TR 23.979] 3GPP: TS 23.979: "3GPP enablers for Open Mobile Alliance (OMA) Push-totalk over Cellular (PoC) services", Stage 2. URL: http://www.3gpp.org/

[3GPP TS 33.107] 3GPP: TS 33.107; "Lawful Interception architecture and functions". URL: http://www.3gpp.org/

[OMA-DICT] "Dictionary for OMA Specifications", Open Mobile Alliance™, OMA-Dictionary-

V2_4. URL: http://www.openmobilealliance.org/ [RFC3550] IETF RFC 3550: "RTP: A Transport

Protocol for Real-Time Applications", H. Schulzrinne, July 2003. URL: http://www.ietf.org/rfc/rfc3550.txt

- 108 -

[RFC4825] IETF RFC 4825: "The Extensible Markup Language (XML) Configuration Access

Protocol (XCAP)", J. Rosenberg, May 2007. URL: http://www.ietf.org/rfc/rfc4825.txt

[RFC4975] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)", September 2007,

URL: http://www.ietf.org/rfc/rfc4975.txt

9 Qualification of OMA:

Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5.

Qualifying information is on file in TSB.

10

None

Other (for any supplementary information):

- 109 -

Annex 19

A.5 justification information for the reference to OMA-ERELD-POC-V2_0-

20110802-A

1 Clear description of the referenced document:

OMA-ERELD-POC-V2_0-20110802-A: Enabler Release Definition for PoC

2 Status of approval:

All of the documents are approved OMA specifications

3 Justification for the specific reference:

The referred document defines the Enabler Release Definition of Push to talk over Cellular according to OMA Release process. This reference is needed for Rec. E.804 to define PoC trigger points.

4 Current information, if any, about IPR issues: http://openmobilealliance.org/about-oma/policies-and-terms-of-use/intellectual-property-rights/

5 Other useful information describing the "Quality" of the document:

All of the documents are approved OMA specifications

6 The degree of stability or maturity of the document:

The documents are all approved OMA specifications that are undergoing continuing development

7

None

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[OMA_SCR_Rules] “SCR Rules and Procedures”, Version 1.0, Open Mobile Alliance™, OMA-

ORG-SCR_Rules_and_Procedures-V1_0, URL: http://www.openmobilealliance.org/

[POC1_ERELD] “Enabler Release Definition for Push-to-Talk over Cellular”, Version 1.0.2, Open

Mobile Alliance, OMA-ERELD-PoC-V1_0_2, URL: http://www.openmobilealliance.org/

[POC1_GA] “Group Advertisement”, Version 1.0.1, Open Mobile Alliance, OMA-SUP-

XSD_poc_group_advertisement-V1_0_1, URL: http://www.openmobilealliance.org/

[POC1_LST] “List Service”, Version 1.0.2, Open Mobile Alliance, OMA-SUP-

XSD_poc_listService-V1_0_2, URL: http://www.openmobilealliance.org/

[POC1_RD] “Push to Talk over Cellular Requirements”, Version 1.0, Open Mobile Alliance™,

OMA-RD-PoC-V1_0, URL: http://www.openmobilealliance.org/

- 110 -

[POC1_UP] “PoC User Plane”, Version 1.0.1, Open Mobile Alliance, OMA-TS-PoC_User Plane-

V1_0_1, URL: http://www.openmobilealliance.org/ [POC1_USG] “PoC Usage”, Version 1.0.2,

Open Mobile Alliance, OMA-SUP-XSD_poc_pocusage-V1_0_2 URL: http://www.openmobilealliance.org/

[POC2_AC] “PoC Application Characteristics”, Version 2.0 , Open Mobile Alliance, OMA-SUP-

AC_ap0006_POC-V2_0,URL: http://www.openmobilealliance.org/

[POC2_AD] “Push to talk over Cellular (PoC) – Architecture”, Version 2.0, Open Mobile Alliance,

OMA-AD-PoC-V2_0, URL: http://www.openmobilealliance.org/

[POC2_CP] “OMA PoC Control Plane”, Version 2.0, Open Mobile Alliance, OMA-TS-PoC-

ControlPlane-V2_0, URL: http://www.openmobilealliance.org/

[POC2_Document_ Mgmt] “PoC Document Management”, Version 2.0, Open Mobile Alliance,

OMA-TS-PoC_Document_Management-V2_0, URL: http://www.openmobilealliance.org/

[POC2_DPR] “Detailed Discrete Media Transfer Progress Report”, Version 2.0, Open Mobile

Alliance, OMA-SUP-XSD_poc_detProgressRep-V2_0, URL: http://www.openmobilealliance.org/

[POC2_FDCFO] “Full Duplex Call Follow On Proceed postd Element”, Version 2.0, Open Mobile

Alliance, OMA-SUP-XSD_poc_FDCFO-V2_0, URL: http://www.openmobilealliance.org/

[POC2_FR] “Discrete Media Transfer Final Report”, Version 2.0, Open Mobile Alliance, OMA-

SUP-XSD_poc_finalReport-V2_0, URL: http://www.openmobilealliance.org/

[POC2_GAD] “Group Advertisement Dispatch Attribute”, Version 2.0, Open Mobile Alliance,

OMA-SUP-XSD_poc_dispatchInd-V2_0, URL: http://www.openmobilealliance.org/

[POC2_ID] “Invocation Descriptor”, Version 2.0, Open Mobile Alliance, OMA-SUP-

XSD_poc_sessionInvocationDescriptor-V2_0, URL: http://www.openmobilealliance.org/

[POC2_IM] “OMA PoC Endorsement of OMA IM TS”, Version 2.0, Open Mobile Alliance, OMA-

TS-PoC-Endorsement_OMA_IM_TS-V2_0,

URL: http://www.openmobilealliance.org/

[POC2_INV] “PoC Invocation Descriptor”, Version 2.0, Open Mobile Alliance, OMA-TS-

PoC_Invocation-Descriptor-V2_0,

URL: http://www.openmobilealliance.org/

- 111 -

[POC2_IWF] “PoC Interworking Service”, Version 2.0, Open Mobile Alliance, OMA-TS-PoC-

Interworking-Service-V2_0, URL: http://www.openmobilealliance.org/

[POC2_MO_DDF] “OMA PoC Management Object”, Version 2.0, Open Mobile Alliance, OMA-

SUP-MO_oma_poc-V2_0, URL: http://www.openmobilealliance.org/ [POC2_OPR]

“Optimized Discrete Media Transfer Progress Report”, Version 2.0, Open Mobile Alliance, OMA-

SUP-XSD_poc_optProgressRep-V2_0,

URL: http://www.openmobilealliance.org/

[POC2_PII] “Participant Information Indications”, Version 2.0, Open Mobile Alliance, OMA-

SUP-XSD_poc_participantInfoInd-V2_0,

URL: http://www.openmobilealliance.org/

[POC2_RD] “Push to talk over Cellular 2 Requirements”, Version 2.0, Open Mobile Alliance,

OMA-RD-PoC-V2_0,

URL: http://www.openmobilealliance.org/ [POC2_RUL] “PoC Rules”, Version 2.0, Open Mobile

Alliance, OMA-SUP-XSD_poc_poc2_0Rules-V2_0, URL: http://www.openmobilealliance.org/

[POC2_SD] “OMA PoC System Description”, Version 2.0, Open Mobile Alliance, OMA-TS-

PoC_System_Description-V2_0, URL: http://www.openmobilealliance.org/

[POC2_SET] “PoCv2.0 Service Settings”, Open Mobile Alliance, OMA-SUP-

XSD_poc_poc2_0Settings-V2_0,

URL: http://www.openmobilealliance.org/

[POC2_SGRP] “Shared Group Extensions”, Version 2.0, Open Mobile Alliance, OMA-SUP-

XSD_poc_poc2_0SharedGroupExt-V2_0,

URL: http://www.openmobilealliance.org/

[POC2_UP] “PoC User Plane”, Version 2.0, Open Mobile Alliance, OMA-TS-PoC_UserPlane-

V2_0, URL: http://www.openmobilealliance.org/

[RFC2119] “Key words for use in RFCs to Indicate Requirement Levels”, S. Bradner, March 1997,

URL: http://www.ietf.org/rfc/rfc2119.txt

[RFC3261] “SIP: Session Initiation Protocol”, June 2002,

URL: http://www.ietf.org/rfc/rfc3261.txt

- 112 -

[OMADICT] “Dictionary for OMA Specifications”, Version 2.5, Open Mobile Alliance™, OMA-

ORG-Dictionary-V2_5, URL: http://www.openmobilealliance.org/

9 Qualification of OMA:

Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5.

Qualifying information is on file in TSB.

10

None

Other (for any supplementary information):

- 113 -

Annex 20

A.5 justification information for the reference to OMA-TS-PoC_ControlPlane-

V2_0-20110802-A

1 Clear description of the referenced document:

OMA-TS-PoC_ControlPlane-V2_0-20110802-A: OMA PoC Control Plane

2 Status of approval:

All of the documents are approved OMA specifications

3 Justification for the specific reference:

The referred document defines the Control Plane signaling procedures of the PoC Client, the PoC

Box and the PoC Server for Push to talk over Cellular (PoC) service. Example detailed signaling flows for the reference points POC-1, POC-2, POC-9, POC-11 and IP-1 are also included in this specification. This reference is needed in Rec. E.804 for the definition of trigger points for PoC.

4 Current information, if any, about IPR issues: http://openmobilealliance.org/about-oma/policies-and-terms-of-use/intellectual-property-rights/

5 Other useful information describing the "Quality" of the document:

All of the documents are approved OMA specifications

6 The degree of stability or maturity of the document:

The documents are all approved OMA specifications that are undergoing continuing development

7

None

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[3GPP TS 24.229] 3GPP TS 24.229: "IP multimedia call control protocol based on Session

Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3, (Release 7),

URL: http://www.3gpp.org/ftp/Specs/latest/Rel-7/24_series/

[3GPP2 X.S0013.4] 3GPP2 X.S0013.4: "All-IP Core Network Multimedia Domain: IP Multimedia

Call Control Protocol Based on SIP and SDP Stage 3", URL: http://www.3gpp2.com/Public_html/specs/X.S0013-004-0_v1.0_022604.pdf

[DMSTDOBJ] "OMA Device Management Standardized Objects", Version 1.2, Open Mobile

Alliance, OMA-TS-DM_StdObj-V1_2 URL: http://www.openmobilealliance.org/ [DMTND]

"OMA Device Management Tree and Description", Version 1.2, Open Mobile Alliance, OMA-TS-

DM_TND-V1_2 URL: http://www.openmobilealliance.org/

[draft-uri-list-message] draft-ietf-sip-uri-list-message-03 (December 2007): "Multiple-Recipient

MESSAGE Requests in the Session Initiation Protocol (SIP)", expires June 2008. URL: http://www.ietf.org/internet-drafts/draft-ietf-sip-uri-list-message-03.txt NOTE: The referenced

- 114 -

IETF draft is a work in progress. [OMA Client Provisioning] OMA Client Provisioning, Version

1.1, Open Mobile Alliance™, OMA-ERP-ClientProvisioning-V1_1, URL: http://www.openmobilealliance.org/

[OMA DM] "OMA Device Management Protocol", Version 1.2, Open Mobile Alliance™, OMA-

TS-DM_Protocol-V1_2, URL: http://www.openmobilealliance.org/ [OMA IM TS] "Instant

Messaging using SIMPLE", Version 1.0, Open Mobile Alliance™, OMA-TS-SIMPLE_IM-V1_0,

URL: http://www.openmobilealliance.org/

[OMA_IM_TS_ Endorsement] "OMA PoC Endorsement of OMA IM TS", Version 2.0, Open

Mobile Alliance™, OMA-TS-PoC_Endorsement_OMA_IM_TS-V2_0, URL: http://www.openmobilealliance.org/ [OMA_SCR_Rules] "SCR Rules and Procedures", V1.0,

Open Mobile Alliance™, OMA-ORG-SCR_Rules_and_Procedures-V1_0, URL: http://www.openmobilealliance.org/

[OMA-DM-3GPPPS-CONNMO] "Standardized Connectivity Management Objects; 3GPP Packet

Switched Bearer Parameters", Version 1.0, Open Mobile Alliance™, OMA-TS-

DM_ConnMO_3GPPPS-V1_0, URL: http://www.openmobilealliance.org/

[OMA-POC-1-CP] "OMA PoC Control Plane", Version 1.0, Open Mobile Alliance™, OMA-TS-

PoC_ControlPlane-V1_0_1, URL: http://www.openmobilealliance.org/

[OMA-POC-1-UP] "PoC User Plane", Version 1.0, Open Mobile Alliance™, OMA-TS-

PoC_UserPlane-V1_0_1, URL: http://www.openmobilealliance.org/

[OMA-PoC-AC] "OMA Push to talk over Cellular (PoC) Application Characteristics File", Version

2.0, Open Mobile Alliance™, OMA-SUP-AC_ap0006_POC-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-Document-Mgmt] "OMA PoC Document Management", Version 2.0, Open Mobile

Alliance, OMA-TS-PoC_Document_Management-V2_0, URL: http://www.openmobilealliance.org/

[OMA-POC-FDCFO] "PoC - Full Duplex Call Follow On Proceed postd Element", Version 2.0,

Open Mobile Alliance, OMA-SUP-XSD_poc_FDCFO-V2_0, URL: http://www.openmobilealliance.org/

[OMA-POC-PARTICIPANTINFOIND] "PoC - Participant Information Indications", Version 2.0,

Open Mobile Alliance, OMA-SUP-XSD_poc_participant-info-ind, URL: http://www.openmobilealliance.org/

- 115 -

[OMA-POC-POC2.0-SETTINGS] "PoC - PoCv2.0 Service Settings", Version 2.0, Open Mobile

Alliance, OMA-SUP-XSD_poc_poc2_0Settings-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-SD] "OMA PoC System Description", Version 2.0, Open Mobile Alliance, OMA-TS-

PoC_System_Description-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-UP] "OMA PoC User Plane", Version 2.0, Open Mobile Alliance, OMA-TS-

PoC_UserPlane-V2_0, URL: http://www.openmobilealliance.org/

[OMA-Pres-Spec] "Presence SIMPLE Specification ",Version 1.0, Open Mobile Alliance, OMA-

TS-Presence_SIMPLE-V1_0, URL: http://www.openmobilealliance.org/

[RFC2046] IETF RFC 2046 (November 1996): "Multipurpose Internet Mail Extensions (MIME)

Part Two: Media Types", URL: http://www.ietf.org/rfc/rfc2046.txt

[RFC2119] IETF RFC 2119 (March 1997): "Key words for use in RFCs to Indicate Requirement

Levels", S. Bradner, March 1997, URL: http://www.ietf.org/rfc/rfc2119.txt

[RFC2396] IETF RFC 2396 (August 19998): "Uniform Resource Identifiers (URI): Generic

Syntax" URL: http://www.ietf.org/rfc/rfc2396.txt [RFC3108] IETF RFC 3108 (May 2001):

"Conventions For the Use of The Session Description Protocol (SDP) for ATM Bearer

Connections", URL: http://www.ietf.org/rfc/rfc3108.txt

[RFC3261] IETF RFC 3261 (June 2002): "SIP: Session Initiation Protocol", URL: http://www.ietf.org/rfc/rfc3261.txt

[RFC3262] IETF RFC 3262 (June 2002): "Reliability of Provisional Responses in the Session

Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc3262.txt

[RFC3264] IETF RFC 3264 (June 2002): "An Offer/Answer Model with the Session Description

Protocol (SDP)", URL: http://www.ietf.org/rfc/rfc3264.txt

[RFC3265] IETF RFC 3265 (June 2002): "Session Initiation Protocol (SIP)-Specific Event

Notification", URL: http://www.ietf.org/rfc/rfc3265.txt [RFC3311] IETF RFC 3311 (September

2002) "The Session Initiation Protocol (SIP) UPDATE Method", URL: http://www.ietf.org/rfc/rfc3311.txt [RFC3312] IETF RFC 3312 (October 2002): "Integration of

Resource Management and Session Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc3312.txt

- 116 -

[RFC3320] IETF RFC 3320 (January 2003): "Signaling Compression (SigComp)", URL: http://www.ietf.org/rfc/rfc3320.txt [RFC3321] IETF RFC 3321 (January 2003): "Signaling

Compression (SigComp) - Extended Operations", URL: http://www.ietf.org/rfc/rfc3321.txt

[RFC3323] IETF RFC 3323 (November 2002): "A Privacy Mechanism for the Session Initiation

Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc3323.txt

[RFC3325] IETF RFC 3325 (November 2002): "Private Extensions to the Session Initiation

Protocol (SIP) for Asserted Identity within Trusted Networks", URL: http://www.ietf.org/rfc/rfc3325.txt

[RFC3420] IETF RFC 3420 (November 2002): "Internet Media Type message/sipfrag",URL: http://www.ietf.org/rfc/rfc3420.txt

[RFC3428] IETF RFC 3428 (December 2002): "Session Initiation Protocol (SIP) Extension for

Instant Messaging", URL: http://www.ietf.org/rfc/rfc3428.txt

[RFC3485] IETF RFC 3485 (February 2003): "The Session Initiation Protocol (SIP) and Session

Description Protocol (SDP) Static Dictionary for Signaling Compression (SigComp)", URL: http://www.ietf.org/rfc/rfc3485.txt

[RFC3486] IETF RFC 3486 (February 2003): "Compressing the Session Initiation Protocol (SIP)",

URL: http://www.ietf.org/rfc/rfc3486.txt [RFC3515] IETF RFC 3515 (April 2003): "The Session

Initiation Protocol (SIP) REFER Method", URL: http://www.ietf.org/rfc/rfc3515.txt [RFC3550]

IETF RFC 3550 (July 2003): "RTP: A Transport Protocol for Real-Time Applications. URL: http://www.ietf.org/rfc/rfc3550.txt [RFC3605] IETF RFC 3605 (October 2003): "Real Time

Control Protocol (RTCP) attribute in Session Description Protocol (SDP)", URL: http://www.ietf.org/rfc/rfc3605.txt

[RFC3840] IETF RFC 3840 (August 2004): "Indicating User Agent Capabilities in the Session

Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc3840.txt

[RFC3680] IETF RFC 3680 (March 2004) "A Session Initiation Protocol (SIP) Event Package for

Registrations" URL: http://www.ietf.org/rfc/rfc3680.txt

[RFC3841] IETF RFC 3841 (August 2004): "Caller Preferences for the Session Initiation Protocol

(SIP)", URL: http://www.ietf.org/rfc/rfc3841.txt [RFC3892] IETF RFC 3892 (September 2004):

"The Session Initiation Protocol (SIP) Referred-By Mechanism", URL: http://www.ietf.org/rfc/rfc3892.txt

[RFC3903] IETF RFC 3903 (October 2004): "Session Initiation Protocol (SIP) Extension for Event

State Publication", URL: http://www.ietf.org/rfc/rfc3903.txt

- 117 -

[RFC4028] IETF RFC 4028 (April 2005): "Session Timers in the Session Initiation Protocol (SIP)",

URL: http://www.ietf.org/rfc/rfc4028.txt [RFC4145] IETF RFC 4145 (September 2005): "TCP-

Based Media Transport in the Session Description Protocol (SDP)". URL: http://www.ietf.org/rfc/rfc4145.txt

[RFC4244] IETF RFC 4244 (November 2005): "An Extension to the Session Initiation Protocol

(SIP) for Request History Information", URL: http://www.ietf.org/rfc/rfc4244.txt

[RFC4354] IETF RFC 4354 (January 2006): "A Session Initiation Protocol (SIP) Event Package and Data Format for Various Settings in Support for the Push-to-talk Over Cellular (PoC) Service",

URL: http://www.ietf.org/rfc/rfc4354.txt

[RFC4412] IETF RFC 4412 (February 2006): "Communications Resource Priority for the Session

Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc4412.txt

[RFC4458] IETF RFC 4458 (April 2006): "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)", URL: http://www.ietf.org/rfc/rfc4458.txt

[RFC4488] IETF RFC 4488 (May 2006): "Suppression of Session Initiation Protocol (SIP) REFER

Method Implicit Subscription", URL: http://www.ietf.org/rfc/rfc4488.txt

[RFC4538] IETF RFC 4538 (June 2006): "Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc4538.txt

[RFC4566] IETF RFC 4566 (July 2006): "SDP: Session Description Protocol", URL: http://www.ietf.org/rfc/rfc4566.txt

[RFC4574] IETF RFC 4574 (August 2006), "The Session Description Protocol (SDP) Label

Attribute", URL: http://www.ietf.org/rfc/rfc4574.txt [RFC4575] IETF RFC 4575 (August 2006):

"A Session Initiation Protocol (SIP) Event Package for Conference State", URL: http://www.ietf.org/rfc/rfc4575.txt

[RFC4583] IETF RFC 4583 (November 2006): "Session Description Protocol (SDP) Format for

Binary Floor Control Protocol (BFCP) Streams". URL: http://www.ietf.org/rfc/rfc4583.txt

[RFC4964] IETF RFC 4964 (October 2007): "The P-Answer-State Header Extension to the Session

Initiation Protocol for the Open Mobile Alliance Push-to-talk over Cellular". URL: http://www.ietf.org/rfc/rfc4964.txt

- 118 -

[RFC4975] IETF RFC 4975 (September 2007): "The Message Session Relay Protocol (MSRP)",

URL: http://www.ietf.org/rfc/rfc4975.txt

[RFC5079] IETF RFC 5079 (December 2007): "Rejecting Anonymous Requests in the Session

Initiation Protocol (SIP)", URI: http://www.ietf.org/rfc/rfc5079.txt

[RFC5234] IETF RFC 5234 (January 2008): "Augmented BNF for Syntax Specifications: ABNF",

URL: http://www.ietf.org/rfc/rfc5234.txt [RFC5318] IETF RFC5318: "The Session Initiation

Protocol (SIP) P-Refused-URI-List Private-Header (P-Header)", URL: http://www.ietf.org/rfc/rfc5318.txt

[RFC5364] IETF RFC5364: "Extensible Markup Language (XML) Format Extension for

Representing Capacity Attributes in Resource Lists", URL: http://www.ietf.org/rfc/rfc5364.txt

[RFC5365] IETF RFC5365: "Multiple-Recipient MESSAGE Requests in the Session Initiation

Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc5365.txt

[RFC5366] IETF RFC5366: "Conference Establishment Using Request-Contained Lists in the

Session Initiation Protocol (SIP)", URL:http://www.ietf.org/rfc/rfc5366.txt

[RFC5368] IETF RFC5368: "Refering to Multiple Resources in the Session Initiation Protocol

(SIP)", URL: http://www.ietf.org/rfc/rfc5368.txt

[RFC5373] IETF RFC 5373 (November 2008): "Requesting Answering Modes for the Session

Initiation Protocol (SIP)", URL: http://www.ietf.org/rfc/rfc5373.txt

[sip-outbound] draft-ietf-sip-outbound-10 (July 2007): "Managing Client Initiated Connections in the Session Initiation Protocol (SIP)", expires January, 2008, URL: http://www.ietf.org/internetdrafts/draft-ietf-sip-outbound-10.txt NOTE: The referenced IETF draft is a work in progress.

[XDM-Core] "XML Document Management (XDM) Specification", Version 2.0, Open Mobile

Alliance, OMA-TS-XDM_Core-V2_0, URL: http://www.openmobilealliance.org/

[XDM-Pres-EXT] "Presence SIMPLE Data Specification", Version 1.0, Open Mobile Alliance,

OMA-DDS-Presence_Data_Ext-V1_0, URL: http://www.openmobilealliance.org/

[XDM-Shared-Groups] "Shared Group XDM Specification", Version 1.0, Open Mobile Alliance,

OMA-TS-XDM_Shared_Group-V1_0, URL: http://www.openmobilealliance.org/

[XSD_XDM2_EXT] "XDM2 - Extensions", Version 1.0, Open Mobile Alliance, OMA-SUP-

XSD_xdm_extensions-V1_0, URL: http://www.openmobilealliance.org/

- 119 -

[3GPP TS 23.218] 3GPP TS 23.218: "IP Multimedia (IM) session handling; IM call model; Stage

2", (Release 5) URL: http://www.3gpp.org/ftp/Specs/latest/Rel-5/23_series/

[3GPP TS 29.228] 3GPP TS 29.228: "IP Multimedia (IM) Subsystem Cx and Dx interfaces;

Signalling flows and message contents", (Release 6) URL: http://www.3gpp.org/ftp/Specs/latest/Rel-6/29_series/

[OMA-PoC-AD] "OMA Push to talk over Cellular (PoC) – Architecture", Version 2.0, Open

Mobile Alliance, OMA-AD-PoC-V2_0, URL: http://www.openmobilealliance.org/

[Provisioning Content] "Provisioning Content", Version 1.1, Open Mobile Alliance, OMA-WAP-

TS-ProvCont-V1_1 URL: http://www.openmobilealliance.org/

9 Qualification of OMA:

Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5.

Qualifying information is on file in TSB.

10

None

Other (for any supplementary information):

- 120 -

Annex 21

A.5 justification information for the reference to OMA-TS-PoC_UserPlane-

V2_0-20110802-A

1 Clear description of the referenced document:

OMA-TS-PoC_UserPlane-V2_0-20110802-A: PoC User Plane

2 Status of approval:

All of the documents are approved OMA specifications

3 Justification for the specific reference:

The referred document describes the User Plane signalling procedures for the Push to talk over

Cellular (PoC) service over the POC-3, POC-4, POC-10 and POC-12 reference points. This reference is needed for Rec. E.804 to describe the PoC testing.

4 Current information, if any, about IPR issues: http://openmobilealliance.org/about-oma/policies-and-terms-of-use/intellectual-property-rights/

5 Other useful information describing the "Quality" of the document:

All of the documents are approved OMA specifications

6 The degree of stability or maturity of the document:

The documents are all approved OMA specifications that are undergoing continuing development

7

None

Relationship with other existing or emerging documents:

8 Any explicit references within that referenced document should also be listed:

[3GPP2 S.R0100-0] 3GPP2 S.R0100-0 Push-to-Talk over Cellular (PoC) System Requirements,

(v1.0). URL: http://www.3gpp2.org/

[OMA Dictionary] “Dictionary for OMA Specifications”, Version 2.3, Open Mobile Alliance™,

OMA-ORG-Dictionary-V2_3, URL: http://www.openmobilealliance.org/

[OMA_SCR_Rules] "SCR Rules and Procedures”, Version 1.0, Open Mobile Alliance™, OMA-

ORG-SCR_Rules_and_Procedures-V1_0, URL: http://www.openmobilealliance.org/

[OMA-IM-TS] "Instant Messaging using SIMPLE", Version 1.0, Open Mobile Alliance™, OMA-

TS-SIMPLE_IM-V1_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-1-UP] "PoC User Plane", Version 1.0, Open Mobile Alliance™, OMA-TS-

PoC_UserPlane-V1_0-20060609-A, URL: http://www.openmobilealliance.org/

- 121 -

[OMA-PoC-AD] "Push to talk over Cellular (PoC) - Architecture", Version 2.0, Open Mobile

Alliance™, OMA-AD_PoC-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-CP] "OMA PoC Control Plane", Version 2.0, Open Mobile Alliance™, OMA-TS-

PoC_ControlPlane-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-DET-PROG-REP] "PoC - PoCV2.0 detailed Discrete Media Transfer Progress

Report", Version 2.0, Open Mobile Alliance, OMA-SUP-XSD_poc_detProgressRep-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-Document-Mgmt] "OMA PoC Document Management", Version 2.0, Open Mobile

Alliance™, OMA-TS-PoC_Document_Management-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-FINAL-REP] "PoC - PoCV2.0 Discrete Media Transfer Final Report", Version 2.0,

Open Mobile Alliance, OMA-SUP-XSD_poc_finalReport-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-IM] "OMA PoC Endorsement of OMA IM TS", Version 2.0, Open Mobile Alliance,

OMA-TS-PoC_Endorsement_OMA_IM_TS-V2_0, URL: http://www.openmobilealliance.org/

[OMA-PoC-RD] “Push to talk over Cellular 2 Requirements”, Version 2.0, Open Mobile Alliance,

OMA-RD-PoC-V2_0, URL: http://www.openmobilealliance.org/

[RFC768] IETF RFC 768 (STD 0006): "User Datagram Protocol", August 1980, URL: http://www.ietf.org/rfc/rfc768.txt

[RFC1305] IETF RFC 1305: "Network Time Protocol (Version 3) Specification, Implementation and Analysis", March 1992. URL: http://www.ietf.org/rfc/rfc1305.txt

[RFC2119] IETF RFC 2119: "Key words for use in RFCs to Indicate Requirement Levels", S.

Bradner, March 1997, URL:http://www.ietf.org/rfc/rfc2119.txt

[RFC2396] IETF RFC 2396: "Uniform Resource Identifiers (URI): Generic Syntax", August 1998,

URL:http://www.ietf.org/rfc/rfc2396.txt [RFC3261] IETF RFC 3261: "SIP: Session Initiation

Protocol", June 2002, URL: http://www.ietf.org/rfc/rfc3261.txt

[RFC3267] IETF RFC 3267: "Real-Time Transport Protocol (RTP) Payload Format and File

Storage Format for the Adaptive Multi-Rate (AMR) and Adaptive Multi-Rate Wideband (AMR-

WB) Audio Codecs", June 2002, URL: http://www.ietf.org/rfc/rfc3267.txt

- 122 -

[RFC3323] IETF RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)",

URL: http://www.ietf.org/rfc/rfc3323.txt [RFC3489bis] IETF draft-ietf-behave-rfc3489bis (August

2007): "Session Traversal Utilities for (NAT) (STUN)", URL: http://www.ietf.org/internetdrafts/draft-ietf-behave-rfc3489bis-13.txt NOTE: The referenced IETF draft is a work in progress.

[RFC3550] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications", July 2003,

URL: http://www.ietf.org/rfc/rfc3550.txt [RFC3558] IETF RFC 3558: "RTP Payload Format for

Enhanced Variable Rate Codecs (EVRC) and Selectable Mode Vocoders (SMV)", June 2003, URL: http://www.ietf.org/rfc/rfc3558.txt

[RFC4566] IETF RFC 4566: "Session Description Protocol", July 2006, URL: http://www.ietf.org/rfc/rfc4566.txt

[RFC4975] IETF RFC 4975: "The Message Session Relay Protocol (MSRP)", September 2007,

URL: http://www.ietf.org/rfc/rfc4975.txt [TS26.235] 3GPP TS 26.235 "3rd Generation Partnership

Project; Technical Specification Group Services and System Aspects; Packet switched conversational multimedia applications; Default codecs (Release 6)", URL: http://www.3gpp.org/ftp/Specs/archive/26_series/26.235/

[TS26.236] 3GPP TS 26.236 "3rd Generation Partnership Project; Technical Specification Group

Services and System Aspects; Packet switched conversational multimedia applications; Transport protocols (Release 6)", URL: http://www.3gpp.org/ftp/Specs/archive/26_series/26.236/

[3GPP2 C.S0047-0] 3GPP2 C.S0047-0 Link-Layer Assisted Service Options for Voice-over-IP:

Header Removal (SO60) and Robust Header Compression (SO61), (v1.0). URL: http://www.3gpp2.org/Public_html/specs/index.cfm#tsgc/

[RFC2543] IETF RFC 2543: "SIP: Session Initiation Protocol", March 1999, URL: http://www.ietf.org/rfc/rfc2543.txt

9 Qualification of OMA:

Qualification of OMA: OMA is recognized under the provisions of ITU-T Recommendation A.5.

Qualifying information is on file in TSB.

10

None

Other (for any supplementary information):

Download