TIA-873 004-2003 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage-3《CDMA2000扩频系统的IP网－基于SIP和SDP进程3的-IP多媒体呼叫控制协议》.pdf

《TIA-873 004-2003 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage-3《CDMA2000扩频系统的IP网－基于SIP和SDP进程3的-IP多媒体呼叫控制协议》.pdf》由会员分享，可在线阅读，更多相关《TIA-873 004-2003 All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage-3《CDMA2000扩频系统的IP网－基于SIP和SDP进程3的-IP多媒体呼叫控制协议》.pdf（266页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA DOCUMENT All-IP Core Network Multimedia Domain IP Multimedia Call Control Protocol Based on SIP and SDP Stage-3 TIA-873.004 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Indu

2、stry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purcha

3、sers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Publications shall not in any respect preclude any member or non-member of TIA from manufac

4、turing or selling products not conforming to such Publications. Neither shall the existence of such Documents preclude their voluntary use by non-TIA members, either domestically or internationally. TIA DOCUMENTS TIA Documents contain information deemed to be of technical value to the industry, and

5、are published at the request of the originating Committee without necessarily following the rigorous public review and resolution of comments which is a procedural part of the development of a American National Standard (ANS). Further details of the development process are available in the TIA Engin

6、eering Manual, located at http:/www.tiaonline.org/standards/sfg/engineering_manual.cfm TIA Documents shall be reviewed on a five year cycle by the formulating Committee and a decision made on whether to reaffirm, revise, withdraw, or proceed to develop an American National Standard on this subject.

7、Suggestions for revision should be directed to: Standards CWTS China Wireless Telecommunications Standards group, China; ETSI 4 European Telecommunications Standards Institute; ATIS, USA; TTA - Telecommunications Technology 5 Association, Korea; and TTC Telecommunication Technology Committee, Japan)

8、, which have granted 6 license for reproduction and for use by 3GPP2 and its Organizational Partners.” 7 8 Revision History 9 Revision number Changes Date 0 Initial Publication December 2003 10 11 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleN

9、o reproduction or networking permitted without license from IHS-,-,-TIA-873-004 1 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-004 1 Scope 1 The present document defi

10、nes a call control protocol for use in the IP Multimedia (IM) Core Network (CN) 2 subsystem based on the Session Initiation Protocol (SIP), and the associated Session Description Protocol 3 (SDP). 4 The present document is applicable to: 5 - the interface between the User Equipment (UE) and the Call

11、 Session Control Function (CSCF); 6 - the interface between the CSCF and any other CSCF; 7 - the interface between the CSCF and an Application Server (AS); 8 - the interface between the CSCF and the Media Gateway Control Function (MGCF); 9 - the interface between the S-CSCF and the Media Resource Fu

12、nction Controller (MRFC) 10 - the interface between the CSCF and the Breakout Gateway Control Function (BGCF); 11 - the interface between the BGCF and the MGCF; 12 - the interface between the BGCF and any other BGCF; and 13 - the interface between the CSCF and an external Multimedia IP network. 14 W

13、here possible the present document specifies the requirements for this protocol by reference to specifications 15 produced by the IETF within the scope of SIP and SDP. Where this is not possible, extensions to SIP and SDP 16 are defined within the present document. The document has therefore been st

14、ructured in order to allow both 17 forms of specification. 18 NOTE 1: This document assumes the existence of the Go interface between the ICN Bearer Control Point 19 and the P-CSCF. However, since the Go interface is not supported in the MMD Revision 0, the 20 procedures that are dependent on the Go

15、 interface are not mandatory. This also pertains to the 21 Service Based Local Policy (SBLP) which is also not supported in the MMD Revision 0. 22 NOTE 2: The present document covers only the usage of SIP and SDP to communicate with the entities of 23 the IM CN subsystem. It is perfectly possible, a

16、nd not precluded, to use only the capabilities of 24 the IP Connectivity Network to allow a terminal containing a SIP UA to communicate with SIP 25 servers outside the IM CN subsystem, and therefore utilise the services provided by those SIP 26 servers. Such usage is outside the scope of the present

17、 document. 27 2 References 28 The following documents contain provisions which, through reference in this text, constitute provisions of the 29 present document. 30 For non-specific 3GPP references the latest Release 5 applies. 31 References are either specific (identified by date of publication, ed

18、ition number, version number, etc.) 32 or non-specific. 33 For a specific reference, subsequent revisions do not apply. 34 For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP2 document, 35 a non-specific reference implicitly refers to the latest version of

19、that document. 36 1 void 37 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-004 2 TIA-873-000, “All-IP Core Network Multimedia Domain - Overview“. 1 3GPP2 X.S0013-000, “

20、All-IP Core Network Multimedia Domain - Overview“. 2 3 void 3 4 void 4 5 TIA-873-003, “IP Multimedia (IM) Session Handling; IM call model“. 5 3GPP2 X.S0013-003, “IP Multimedia (IM) Session Handling; IM call model“. 6 6 void 7 7 TIA-873-002, “IP Multimedia Subsystem; Stage 2“ 8 3GPP2 X.S0013-002, “IP

21、 Multimedia Subsystem; Stage 2“ 9 8 void 10 9 void 11 10 void 12 10A TIA-835-C, “cdma20001Wireless IP Network Standard “. 13 3GPP2 X.S0011-C,: “cdma2000 Wireless IP Network Standard “. 14 11 void 15 12 void 16 13 void 17 14 TIA-873-005, “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows an

22、d message contents“. 18 3GPP2 X.S0013-005, “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and message 19 contents“. 20 15 TIA-873-006, “Cx Interface based on the Diameter protocol, Protocol details“. 21 3GPP2 X.S0013-006, “Cx Interface based on the Diameter protocol, Protocol details“.

23、 22 16 TIA-873-007, “IP Multimedia Subsystem - Charging Architecture“. 23 3GPP2 X.S0013-007, “IP Multimedia Subsystem - Charging Architecture“. 24 17 TIA-873-008, “IP Multimedia Subsystem - Accounting Information Flows and Protocol“. 25 3GPP2 X.S0013-008, “IP Multimedia Subsystem - Accounting Inform

24、ation Flows and Protocol“. 26 18 3GPP TS 33.102, “3G Security; Security architecture“. 27 19 3GPP2 S.S0086-0, “IMS Security Framework“. 28 20 void 29 1cdma2000 is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. When

25、 applied to goods and services, the cdma2000mark certifies their compliance with cdma2000standards. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. Copyright Telecommunications Indus

26、try Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-004 20A IETF RFC 2401 (November 1998), “Security Architecture for the Internet Protocol“. 1 20B IETF RFC 1594 (March 1994), “FYI on Questions and Answers t

27、o Commonly asked “New Internet 2 User“ Questions“. 3 20C IETF RFC 2403 (November 1998), “The Use of HMAC-MD5-96 within ESP and AH“. 4 20D IETF RFC 2404 (November 1998), “The Use of HMAC-SHA-1-96 within ESP and AH“. 5 20E IETF RFC 2462 (November 1998), “IPv6 Address Autoconfiguration“. 6 21 IETF RFC

28、2617 (June 1999), “HTTP Authentication: Basic and Digest Access Authentication“. 7 22 IETF RFC 2806 (April, 2000), “URLs for Telephone Calls“. 8 23 IETF RFC 2833 (May 2000), “RTP Payload for DTMF Digits, Telephony Tones and Telephony 9 Signals“. 10 24 IETF RFC 2916 (September 2000), “E.164 number an

29、d DNS“. 11 25 IETF RFC 2976 (October 2000), “The SIP INFO method“. 12 25A IETF RFC 3041 (January 2001), “Privacy Extensions for Stateless Address Autoconfiguration in IPv6“. 13 26 IETF RFC 3261 (June 2002), “SIP: Session Initiation Protocol“. 14 27 IETF RFC 3262 (June 2002), “Reliability of Provisio

30、nal Responses in Session Initiation Protocol“. 15 28 IETF RFC 3265 (June 2002), “Session Initiation Protocol (SIP) Specific Event Notification“. 16 29 IETF RFC 3311 (September 2002), “The Session Initiation Protocol (SIP) UPDATE method“. 17 30 IETF RFC 3312 (October 2002), “Integration of Resource M

31、anagement and Session Initiation Protocol 18 (SIP)“. 19 31 IETF RFC 3313 (January 2003), “Private Session Initiation Protocol (SIP) Extensions for Media 20 Authorization“. 21 32 IETF RFC 3320 (March 2002), “Signaling Compression (SigComp)“. 22 33 IETF RFC 3323 (November 2002), “A Privacy Mechanism f

32、or the Session Initiation Protocol (SIP)“. 23 34 IETF RFC 3325 (November 2002), “Private Extensions to the Session Initiation Protocol (SIP) for 24 Network Asserted Identity within Trusted Networks“. 25 35 IETF RFC 3327 (December 2002), “ Session Initiation Protocol Extension Header Field for Regist

33、ering 26 Non-Adjacent Contacts“. 27 36 IETF RFC 3515 (April 2003), “The Session Initiation Protocol (SIP) REFER method“. 28 37 IETF RFC 3420 (November 2002), “Internet Media Type message/sipfrag“. 29 38 IETF RFC 3608 (October 2003), “Session Initiation Protocol (SIP) Extension Header Field for Servi

34、ce 30 Route Discovery During Registration“. 31 39 IETF RFC 2327 (April 1998), “SDP: Session Description Protocol“. 32 39A IETF RFC 3266 (June 2002), “Support for IPv6 in Session Description Protocol (SDP)“. 33 40 IETF RFC 3315 (July 2003), “Dynamic Host Configuration Protocol for IPv6 (DHCPv6)“. 34

35、Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-004 41 IETF RFC 3319 (July 2003), “Dynamic Host Configuration Protocol (DHCPv6) Options for Session 1 Initiation Protocol

36、 (SIP) Servers“. 2 42 IETF RFC 3485 (February 2003), “The Session Initiation Protocol (SIP) and Session Description 3 Protocol (SDP) static dictionary for Signaling Compression (SigComp)“. 4 43 IETF RFC 3680 (December 2003), “A Session Initiation Protocol (SIP) Event Package for 5 Registrations“. 6

37、44 void 7 45 void 8 46 void 9 47 void 10 48 IETF RFC 3329 (January 2003), “Security Mechanism Agreement for the Session Initiation Protocol 11 (SIP)“. 12 49 IETF RFC 3310 (September 2002), “Hypertext Transfer Protocol (HTTP) Digest Authentication Using 13 Authentication and Key Agreement (AKA)“. 14

38、50 IETF RFC 3428 (December 2002), “Session Initiation Protocol (SIP) Extension for Instant Messaging“. 15 51 void 16 52 IETF RFC 3455 (December 2002), “ Private Header (P-Header) Extensions to the Session Initiation 17 Protocol (SIP) for the 3rd-Generation Partnership Project (3GPP)“. 18 53 IETF RFC

39、 3388 (December 2002), “Grouping of Media Lines in Session Description Protocol“. 19 54 IETF RFC 3524 (April 2003), “Mapping of Media Streams to Resource Reservation Flows“. 20 55 IETF RFC 3486 (February 2003), “Compressing the Session Initiation Protocol (SIP)“. 21 56 IETF RFC 3361 (August 2002), “

40、Dynamic Host Configuration Protocol (DHCP-for-IPv4)- Option for 22 Session Initiation Protocol (SIP) Servers”. 23 56A ITU-T Recommendation E.164 (May 1997), “The international public telecommunication numbering 24 plan”. 25 56B IETF RFC 3556 (July 2003), “ Session Description Protocol (SDP) Bandwidt

41、h Modifiers for RTP 26 Control Protocol (RTCP) Bandwidth“. 27 57 IETF RFC 2131 (March 1997), “Dynamic host configuration protocol”. 28 58 IETF RFC 3263 (June 2002), “SIP: Locating SIP Servers”. 29 3 Definitions and abbreviations 30 3.1 Definitions 31 For the purposes of the present document, the fol

42、lowing terms and definitions apply. 32 IP Connectivity Network: refers to any collection of network entities and interfaces that provides the 33 underlying IP transport connectivity to or between IMS entities. 34 IP Connectivity Network Bearer: a logical grouping of one or more IP flows that share a

43、 common QoS 35 allocation. Depending on the particular IP Connectivity Network, obtaining an IP Connectivity Network Bearer 36 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TI

44、A-873-004 may require the UE to specifically request access to specific IP Connectivity Network resources (e.g., Packet 1 Data Service Instance creation). In some IP Connectivity Networks, bearers may be available without a 2 specific access request. 3 ICN Bearer Control Point: refers to the entity

45、through which IP Connectivity Network flows pass, and which 4 controls the allocation of IP Connectivity network bearer resources to the UE (e.g., PDSN). 5 For the purposes of the present document, the following terms and definitions given in 20B. 6 Fully-Qualified Domain Name (FQDN) 7 For the purpo

46、ses of the present document, the following terms and definitions given in 26 apply (unless 8 otherwise specified see clause 6). 9 Back-to-Back User Agent (B2BUA) 10 Client 11 Dialog 12 Final response 13 Header 14 Header field 15 Loose routeing 16 Method 17 Option-tag (see 26 subclause 19.2) 18 Provi

47、sional response 19 Proxy, proxy server 20 Redirect server 21 Registrar 22 Request 23 Response 24 Server 25 Session 26 (SIP) transaction 27 Stateful proxy 28 Stateless proxy 29 Status-code (see 26 subclause 7.2) 30 Tag (see 26 subclause 19.3) 31 Target Refresh Request 32 User agent client (UAC) 33 Us

48、er agent server (UAS) 34 User agent (UA) 35 For the purposes of the present document, the following terms and definitions given in 2 subclause 4.1.1.1 36 and subclause 4a.7 apply: 37 Breakout Gateway Control Function (BGCF) 38 Call Session Control Function (CSCF) 39 Home Subscriber Server (HSS) 40 Media Gateway Control Function (MGCF) 41 Media Resource Function Controller (MRFC) 42 For the purposes of the present document, the following terms and definitions given in 5 subclause 3.1 apply: 43 Filter criteria 44 Initial filter criteria 45 Initial request 46 Standalone tran