1、 International Telecommunication Union ITU-T J.460.1TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (06/2008) SERIES J: CABLE NETWORKS AND TRANSMISSION OF TELEVISION, SOUND PROGRAMME AND OTHER MULTIMEDIA SIGNALS IPCablecom2 residential SIP telephony: Feature specification Recommendation ITU-T J.460.
2、1 Rec. ITU-T J.460.1 (06/2008) i Recommendation ITU-T J.460.1 IPCablecom2 residential SIP telephony: Feature specification Summary Recommendation ITU-T J.460.1 specifies an implementation of common residential telephony features in an IPCablecom2 network with SIP based User Equipment (UEs). These fe
3、atures include the most commonly used residential features and capabilities, including Caller ID features, call forwarding features, hold, transfer, three-way calling, emergency calling, and operator services. This Recommendation defines the Layer 3 and higher network requirements and signaling to e
4、nable User Equipment (UE) to establish services to emulate historical analog telephony services and features. Source Recommendation ITU-T J.460.1 was approved on 13 June 2008 by ITU-T Study Group 9 (2005-2008) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T J.460.1 (06/2008) FOREWORD The Int
5、ernational Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical,
6、operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in tur
7、n, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE
8、 In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.
9、g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not su
10、ggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the ev
11、idence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation development process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which
12、 may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may
13、 be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T J.460.1 (06/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative References 1 2.2 Informative References 3 2.3 Reference Acquisition 4 3 Terms and Definitions 4 4 Abbreviations, acronyms and c
14、onventions. 5 4.1 Abbreviations and Acronyms . 5 4.2 Conventions 7 5 Overview 8 5.1 IPCablecom2 Design Considerations for Residential SIP Telephony . 8 5.2 Residential SIP Telephony Specific Applications 8 5.3 Functional Components for Residential SIP Telephony 9 5.4 Protocol Interfaces for Resident
15、ial SIP Telephony 9 6 Normative Reference Application 9 7 Residential SIP telephony feature requirements. 9 7.1 Basic Calling Capabilities 9 Annex A Region A 58 Annex B Region B 59 Annex C Region C (Primarily Japan) . 60 Annex D Digit Map Syntax 61 Appendix I Service Descriptions Typically Used in N
16、orth America 63 I.1 Scope 63 I.2 References 63 I.3 Terms and Definitions 65 I.4 Abbreviations and Acronyms . 65 I.5 Overview 65 I.6 Normative Reference Application 65 I.7 Residential SIP Telephony Feature Requirements. 66 I.8 Emergency Services . 190 Rec. ITU-T J.460.1 (06/2008) 1 Recommendation ITU
17、-T J.460.1 IPCablecom2 residential SIP telephony: Feature specification 1 Scope This Recommendation specifies an implementation of common residential telephony features in an IPCablecom2 network with SIP based User Equipment (UEs). These features include the most commonly used residential features a
18、nd capabilities, including Caller ID features, call forwarding features, hold, transfer, three-way calling, emergency calling, and operator services. The IPCablecom2 network architecture uses the Session Initiation Protocol (SIP) as the basis for call setup and teardown. SIP was designed to permit d
19、istribution of feature logic to the network endpoints, requiring less processing in network elements, and theoretically permitting a reduction in cost of network infrastructure. Also, SIP was designed to support a wide range of interactive applications, including telephony, video conferencing, inter
20、active messaging, presence, wireless services, and many others. Lastly, SIP is the foundation of the IP Multimedia Subsystem (IMS) architecture, upon which the IPCablecom2 architecture is based. Many telecom equipment and software suppliers are focusing their investments in converged network solutio
21、ns on the IMS architecture, and the IPCablecom2 architecture leverages the IMS architecture, which should yield more rapid implementation timeframes. This initial Residential SIP Telephony Feature Specification defines the Layer 3 and higher network requirements and signaling to enable User Equipmen
22、t (UE) to establish services to emulate historical analog telephony services and features. This release of the Recommendation supports services described in Appendix II of RST TR. Future releases will support additional services that are described in Appendices I and III of RST TR as they are develo
23、ped. It is an important objective of this work that interoperability between IPCablecom 2.0 and 3GPP IMS is provided. IPCablecom 2.0 is based upon 3GPP IMS, but includes additional functionality necessary to meet the requirements of cable operators. Recognizing developing converged solutions for wir
24、eless, wireline, and cable, it is expected that further development of IPCablecom 2.0 will continue to monitor and contribute to IMS developments in 3GPP, with the aim of alignment of 3GPP IMS and IPCablecom 2.0. NOTE The structure and content of this Recommendation have been organized for ease of u
25、se by those familiar with the original source material; as such, the usual style of ITU-T recommendations has not been applied. 2 References 2.1 Normative References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisio
26、ns of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applying the most recent edition of the Recommendations
27、and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. CODEC-MEDIA Recommendation ITU-T J.361 (2006), IPCablecom
28、2 codec and media. ID SIP-ACR IETF RFC 5079, Rejecting Anonymous Requests in the Session Initiation Protocol (SIP), December 2007. 2 Rec. ITU-T J.460.1 (06/2008) ID SIP-URN IETF RFC 5031, A Uniform Resource Name (URN) for Emergency and other well-known Services, January 2008. PKT 24.229 Recommendati
29、on ITU-T J.366.4 (2006), IPCablecom2 IP Multimedia Subsystem (IMS): Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 specification. RFC 2543 IETF RFC 2543, SIP: Session Initiation Protocol, March 1999. RFC 3066 IETF RFC 3066, Tags for the Identification of Languages,
30、January 2001. RFC 3261 IETF RFC 3261, SIP: Session Initiation Protocol, June 2002. RFC 3262 IETF RFC 3262, Reliability of Provisional Responses in the Session Initiation Protocol (SIP), June 2002. RFC 3264 IETF RFC 3264, An Offer/Answer Model with the Session Description Protocol (SDP), June 2002. R
31、FC 3265 IETF RFC 3265, Session Initiation Protocol (SIP)-Specific Event Notification, June 2002. RFC 3323 IETF RFC 3323, A Privacy Mechanism for the Session Initiation Protocol (SIP), November 2002. RFC 3325 IETF RFC 3325, Private Extensions to the Session Initiation Protocol (SIP) for Asserted Iden
32、tity within Trusted Networks, November 2002. RFC 3389 IETF RFC 3389, Real-time Transport Protocol (RTP) Payload for Comfort Noise (CN), September 2002. RFC 3515 IETF RFC 3515, The Session Initiation Protocol (SIP) Refer Method, April 2003. RFC 3603 IETF RFC 3603, Private Session Initiation Protocol
33、(SIP) Proxy-to-Proxy Extensions for Supporting the PacketCable Distributed Call Signaling Architecture, October 2003. RFC 3825 IETF RFC 3825, Dynamic Host Configuration Protocol Option for Coordinate-based Location Configuration Information, July 2004. RFC 3842 IETF RFC 3842, A Message Summary and M
34、essage Waiting Indication Event Package for the Session Initiation Protocol (SIP), August 2004. RFC 3891 IETF RFC 3891, The Session Initiation Protocol (SIP) Replaces Header, September 2004. RFC 3892 IETF RFC 3892, The Session Initiation Protocol (SIP) Referred-By Mechanism, September 2004. RFC 3911
35、 IETF RFC 3911, The Session Initiation Protocol (SIP) Join Header, October 2004. RFC 3959 IETF RFC 3959, The Early Session Disposition Type for the Session Initiation Protocol (SIP), December 2004. RFC 3966 IETF RFC 3966, The tel URI for Telephone Numbers, December 2004. RFC 4119 IETF RFC 4119, A Pr
36、esence-based GEOPRIV Location Object Format, December 2005. RFC 4235 IETF RFC 4235, An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP), November 2005. RFC 4240 IETF RFC 4240, Basic Network Media Services with SIP, December 2005. Rec. ITU-T J.460.1 (06/2008) 3 RFC 4244
37、 IETF RFC 4244, An Extension to the Session Initiation Protocol (SIP) for Request History Information, November 2005. RFC 4330 IETF RFC 4330, Simple Network Time Protocol version 4 for IPv6, IPv4, and OSI, January 2006. RFC 4412 IETF RFC 4412, Communications Resource Priority for the Session Initiat
38、ion Protocol (SIP), February 2006. RFC 4458 IETF RFC 4458, Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR), April 2006. RFC 4538 IETF RFC 4538, Request Authorization through Dialog Identification in the Session Initiation Protocol (SIP),
39、 June 2006. RFC 4566 IETF RFC 4566, SDP: Session Description Protocol, July 2006. RFC 4676 IETF RFC 4676, Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Option for Civic Addresses Configuration Information, October 2006. 2.2 Informative References ARCH-FRM TR Recommendation ITU-T J.360: IPC
40、ablecom2 architecture framework. CMSS1.5 Recommendation ITU-T J.178: IPCablecom CMS to CMS signalling. ID LOST IETF Internet-Draft, Lost: A Location-to-Service Translation Protocol draft-ietf-ecrit-lost-01, September 2006, work in progress. ID ICE IETF Internet-Draft, Interactive Connectivity Establ
41、ishment (ICE): A Methodology for Network Address Translator (NAT) Traversal for Offer/Answer Protocols, draft-ietf-mmusic-ice-10, August 2006, work in progress. ID-BEHAVE- IETF Internet-Draft, Traversal Using Relay Network Address Translation TURN (NAT), draft-ietf-behave-turn-ipv6-00, February 2006
42、, work in progress. ID SIP-CONVEY IETF Internet-Draft, Session Initiation Protocol Location Conveyance, draft-ietf-sip-location-conveyance-10, February 2008, work in progress. ID SIP-GRUU IETF Internet-Draft, Obtaining and Using Globally Routable User Agent (UA) URIs (GRUU) in the Session Initiation
43、 Protocol (SIP), draft-ietf-sip-gruu-15, October 2007, work in progress. ID SIP- IETF Internet-Draft, Managing Client Initiated Connections in the Session OUTBOUND Initiation Protocol (SIP), draft-ietf-sip-outbound-12, February 2008, work in progress. PAMI Recommendation ITU-T J.365: IPCablecom2 app
44、lication manager interface. PKT 23.218 Recommendation ITU-T J.366.3 (2006): IPCablecom2 IP Multimedia Subsystem (IMS): Stage 2 specification. PKT 23.228 Recommendation ITU-T J.366.5: IP multimedia (IM) subsystem Cx and Dx interfaces; signalling flows and message contents specification (3GPP TS 29.22
45、8). PKT 33.203 Recommendation ITU-T J.366.7 (2006): IPCablecom2 IP Multimedia Subsystem (IMS): Access security for IP-Based services. PKT 33.210 Recommendation ITU-T J.366.8: IPCablecom2 IP Multimedia Subsystem (IMS): Network domain security specification. 4 Rec. ITU-T J.460.1 (06/2008) RFC 2396 IET
46、F RFC 2396, Uniform Resource Identifiers (URI): Generic Syntax, August 1998. RFC 2833 IETF RFC 2833, RTP Payload for DTMF Digits, Telephony Tones and Telephony signals, May 2000. RFC 3315 IETF RFC 3315, Dynamic Host Configuration Protocol for IPv6 (DHCPv6), July 2003. RFC 3761 IETF RFC 3761, The E.1
47、64 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM), April 2004. RFC 3960 IETF RFC 3960, Early Media and Ringing Tone Generation in the Session Initiation Protocol (SIP), December 2004. RFC 4234 IETF RFC 4234, Augmented BNF for Syntax Specifications
48、: ABNF, October 2005. RST TR Recommendation ITU-T J.460.0, IPCablecom2 Residential SIP Telephony: Feature: Definition. TGCP1.5 Recommendation ITU-T J.171.1: IPCablecom trunking gateway control protocol (TGCP): Profile 1. 2.3 Reference Acquisition Internet Engineering Task Force (IETF), Internet: htt
49、p:/www.ietf.org/ NOTE Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. The list of current Internet-Drafts can be accessed at http:/www.ietf.org/ietf/1id-abstracts.txt. National Emergency Number Association (NENA), http:/www.nena.org/9-1-1TechStandards/tech_info_docs.htm, http:/www.nena.org/9-1-1TechStandards/voip.htm Telcordia Technologies, http:/www.telcord
