1、 TIA DOCUMENT All-IP Core Network Multimedia Domain IP Multimedia Subsystem IP Multimedia Call Model: Stage 2 TIA-873.003 DECEMBER 2003 TELECOMMUNICATIONS INDUSTRY ASSOCIATION The Telecommunications Industry Association represents the communications sector of Copyright Telecommunications Industry As
2、sociation 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 purchasers, f
3、acilitating 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 manufacturing
4、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 are pub
5、lished 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 Engineering
6、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. Suggest
7、ions for revision should be directed to: Standards Stage 2 3 4 Contents 5 6 Foreword iv 7 Revision History . iv 8 1 Scope .1 9 2 References.1 10 3 Definitions and abbreviations.2 11 3.1 Definitions .2 12 3.2 Abbreviations 3 13 4 Architecture and information flows for IM multimedia session.4 14 4.1 A
8、rchitecture for a mobile originated IP multimedia session4 15 4.2 Architecture for a mobile terminated IP multimedia session 4 16 4.3 Information flow for a mobile originated IP multimedia session .5 17 4.4 Information flow for retrieval of routing information for mobile terminated IP multimedia 18
9、session.5 19 4.5 Information flow for a mobile terminated IP multimedia session 5 20 5 Functional requirements of network entities 6 21 5.1 Architecture for service provision for IP multimedia subsystem .6 22 5.2 Service interaction with IP multimedia subsystem7 23 6 Functional requirements of servi
10、ng CSCF.9 24 6.1 Modes of operation of the S-CSCF.9 25 6.1.1 General overview of functional models and modes of operation of the S-CSCF9 26 6.2 Interfaces defined for S-CSCF10 27 6.2.1 S-CSCF CSCF (Mw) interface.10 28 6.2.2 S-CSCF Application Server (ISC) interface.10 29 6.2.3 S-CSCF HSS (Cx) interf
11、ace.10 30 6.2.4 S-CSCF MRFC (Mr) Interface.10 31 6.2.5 S-CSCF IP Multimedia Network (Mm) interface. .10 32 6.3 Handling of SIP registration 10 33 6.4 Handling of mobile originating requests .11 34 6.5 Handling of mobile terminating requests 12 35 6.5.1 Handling of mobile terminating requests, regist
12、ered user.12 36 6.5.2 Handling of mobile terminating requests, unregistered user.12 37 6.6 Handling of IP multimedia session release requests12 38 6.6.1 S-CSCF proxying release request12 39 6.6.2 S-CSCF initiating release request13 40 6.7 Handling of subscription and notification 13 41 6.8 S-CSCF ha
13、ndling IMS accounting14 42 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 ii 6.9 Description of subscriber data 14 1 6.9.1 Application Server subscription informati
14、on 14 2 6.9.2 Filter Criteria.14 3 6.9.3 Authentication data .15 4 7 Functional requirements of HSS15 5 7.1 Subscriber data related storage requirements for HSS15 6 7.2 Interfaces defined for HSS16 7 7.2.1 HSS CSCF (Cx) interface 16 8 7.2.2 HSS - Application Server (Sh) interface .16 9 7.2.3 Void16
15、10 7.2.4 Void.16 11 7.3 Procedures during IP multimedia registration.16 12 7.4 Procedures during IP multimedia sessions 16 13 8 Functional requirements of the MRFC.16 14 8.1 Functionality of the MRFC 16 15 8.1.1 Overview of MRFC Functionality 16 16 8.1.2 Tones and announcements 17 17 8.1.3 Ad hoc co
16、nferences (multiparty calls).17 18 8.1.4 Transcoding.17 19 8.2 Interfaces defined for MRFC.18 20 8.2.1 MRFC S-CSCF (Mr) interface.18 21 9 Generic IP multimedia session handling for SIP Application Servers .19 22 9.1 Architecture.19 23 9.1.1 Modes of operation between Application Server and S-CSCF .2
17、0 24 9.2 Interfaces defined for a SIP Application Server22 25 9.2.1 S-CSCF Application Server (ISC) interface.22 26 9.2.2 Application Server HSS (Sh) interface.22 27 9.3 Description of Application Server related subscriber data22 28 9.3.1 Application server subscription information .22 29 9.4 Proced
18、ures for multimedia session handling with a SIP based Application Server .23 30 9.4.1 Application Server handling of mobile originating requests.23 31 9.4.2 Application Server handling of mobile terminating requests23 32 9.4.3 Application Server handling of SIP registration23 33 9.4.4 Application Se
19、rver handling of IP multimedia session release requests .24 34 9.4.5 Application server handling of IP multimedia accounting25 35 10 Void 25 36 11 IP multimedia session handling with an OSA-Service Capability Server.25 37 12. IP multimedia session handling with an Charging Server26 38 Annex A (infor
20、mative): Scalability and deployment considerations for IP multimedia service provision39 .27 40 Annex B (informative): Information flows for example services 29 41 B.1 Call forwarding example.29 42 B.1.1 Call forwarding through Application Servers .29 43 B.1.1.1 Service activation and programming.30
21、 44 B.1.1.2 Service invocation and control30 45 B.1.2 Assumptions31 46 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 iii B.1.3 UE redirect based call flows31 1 B.1
22、.4 S-CSCF based redirect call flows32 2 B.2 Announcement, conferencing and transcoding examples using MRFC 34 3 B.2.1 Example information flow for a mobile originated IP multimedia session that results in playing 4 an announcement.34 5 B.2.2 Example information flow for a mobile originated IP multim
23、edia ad hoc conferencing session 6 (multiparty call).36 7 B.2.3 Example information flows for a mobile originated IP multimedia session that requires 8 transcoding38 9 B.3 Example information flows for a voicemail service.42 10 B.3.1 User out of coverage message recording .42 11 B.3.2 User IMS regis
24、ters voice mail service plays back messages .44 12 Annex C (informative): Example for Initial filter criteria triggering.47 13 14 15 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-
25、,-,-TIA-873-003 iv 1 2 Foreword 3 This document contains portions of material copied from 3GPP document number(s) TS 23.218. The copyright 4 on the 3GPP document is owned by the Organizational Partners of 3GPP (ARIB - Association of Radio 5 Industries and Businesses, Japan; CWTS China Wireless Telec
26、ommunications Standards group, China; ETSI 6 European Telecommunications Standards Institute; ATIS, USA; TTA - Telecommunications Technology 7 Association, Korea; and TTC Telecommunication Technology Committee, Japan), which have granted 8 license for reproduction and for use by 3GPP2 and its Organi
27、zational Partners. 9 10 Revision History 11 12 Revision Changes Date 0 Initial Publication December 2003 13 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 v 1 Copyr
28、ight Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 1 1 Scope 1 The present document specifies the IP Multimedia (IM) Call Model for handling of an IP multimedia 2 session or
29、igination and termination for an IP Multimedia subscriber. 3 The present document includes interactions between an Application Server and IP multimedia sessions. 4 The IP Multimedia (IM) Subsystem stage 2 is specified 3 and the stage 3 for the IP multimedia call 5 control based on SIP and SDP is spe
30、cified in 5. 6 2 References 7 The following documents contain provisions which, through reference in this text, constitute provisions of 8 the present document. 9 References are either specific (identified by date of publication, edition number, version number, 10 etc.) or non-specific. 11 For a spe
31、cific reference, subsequent revisions do not apply. 12 For a non-specific reference, the latest version applies. 13 14 1 Void. 15 2 TIA/TSB-151, IP Network Reference Model (NRM) for cdma20001Spread Spectrum Systems, 16 December 2003. 17 3GPP2 S.R0037-0, “IP Network Architecture Model for cdma2000 Sp
32、read Spectrum Systems”, 18 Version 3.0, September, 2003. 19 3 TIA-873-002, “ IP multimedia subsystem; Stage 2“. 20 3GPP2 X.S0013-002, “IP Multimedia Subsystem; Stage 2“ 21 4 Void 22 5 TIA-873-004, “IP multimedia call control protocol based on SIP and SDP; stage 3“. 23 3GPP2 X.S0013-004, “IP Multimed
33、ia Call Control Protocol Based on SIP and SDP Stage 3”. 24 6 IETF RFC 3261, “SIP: Session Initiation Protocol“. 25 7 TIA-937, “Open Service Access (OSA); Application Programming Interface (API) “, June 2003 26 3GPP2 X.S0017, “Open Service Access (OSA); Application Programming Interface (API) “ 27 8
34、TIA-873-005, “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and message 28 contents“. 29 3GPP2 X.S0013-005, “IP Multimedia (IM) Subsystem Cx Interface; Signalling flows and message 30 contents“. 31 9 Void 32 10 Void 33 11 3GPP2 S.S0086-0: “3GPP2 IMS Security Framework”. 34 1cdma2000 is
35、 the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. When applied to goods and services, the cdma2000mark certifies their compliance with cdma2000standards. Geographically (and as of the date of publication), cdma2000 i
36、s a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 2 12 Void 1 1
37、3 IETF RFC 3265, “Session Initiation Protocol (SIP) Event Notification“. 2 14 Void 3 15 IETF RFC 3264, “An Offer/Answer Model with Session Description Protocol“. 4 16 Void 5 17 TIA-873-006, “Cx Interface based on the Diameter protocol“. 6 3GPP2 X.S0013-006, “Cx Interface based on Diameter Protocol;
38、Protocol details”. 7 18 TIA-873-010, “IP Multimedia Subsystem (IMS) Sh Interface; Signalling flows and message 8 contents“. 9 3GPP2 X.S0013-010, “IP Multimedia Subsystem Sh interface; Signaling flows and message 10 contents Stage 2” 11 19 TIA-873-011, “Sh Interface based on the Diameter protocol“. 1
39、2 3GPP2 X.S0013-011, “Sh Interface based on the Diameter protocol; protocol details” 13 20 TIA-873-007, “ Accounting Architecture and stage 2 Description“. 14 3GPP2 X.S0013-007, “IP Multimedia Subsystem - Charging Architecture“. 15 21 TIA-873-008, “ IP Multimedia subsystem Accounting stage 3“. 16 3G
40、PP2 X.S0013-008, “IP Multimedia Subsystem - Accounting Information Flows and Protocol“. 17 3 Definitions and abbreviations 18 3.1 Definitions 19 For the purposes of the present document, the terms and definitions given in 2 and the following apply: 20 21 Application Server Incoming Leg Control Model
41、 (AS-ILCM): models AS behavior for handling SIP 22 information for an incoming leg. 23 24 Application Server information (AS-info): AS-info contains individualized information concerning one 25 particular Application Server entry. 26 This information contains e.g. Application Server Address (6.9.2.1
42、) and its corresponding Default IP 27 Multimedia Handling information (6.9.2.2). 28 29 Application Server Outgoing Leg Control Model (AS-OLCM): models AS behaviour for handling SIP 30 information for an outgoing leg. 31 32 Combined ILSM OLSM Incoming/outgoing Leg State Model: models the behaviour of
43、 an S-CSCF 33 for handling SIP messages on an incoming and outgoing session leg. 34 35 Filter Criteria (FC): the information which the S-CSCF receives from the HSS or the AS that defines the 36 relevant SPTs for a particular application. 37 They define the subset of SIP requests received by the S-CS
44、CF that should be sent or proxied to a particular 38 application. 39 40 Copyright Telecommunications Industry Association Provided by IHS under license with EIANot for ResaleNo reproduction or networking permitted without license from IHS-,-,-TIA-873-003 3 Incoming Leg Control Model (ILCM): models t
45、he behaviour of an S-CSCF for handling SIP information 1 sent to and received from an AS for an incoming session leg. 2 3 Initial Filter Criteria (iFC): filter criteria that are stored in the HSS as part of the user profile and are 4 downloaded to the S-CSCF upon user registration. 5 They represent
46、a provisioned subscription of a user to an application. 6 7 Initial Request: a SIP request that either initiates the creation of a new dialog or is part of a standalone 8 transaction. 9 10 IP Multimedia session: IP Multimedia session and IP Multimedia call are treated as equivalent in the 11 present
47、 document. 12 13 IP Transport Subsystem: refers to any collection of network entities that provides the underlying IP 14 transport for use to provide connectivity to or between IMS entities. 15 16 Outgoing Leg Control Model (OLCM): models the behavior of an S-CSCF for handling SIP information 17 rec
48、eived from and sent to an AS for an outgoing session leg. 18 19 Private User Identity: a unique global identity defined by the Home Network Operator, as defined in 3. 20 21 Public User Identity: the public user identity/identities are used by any user for requesting 22 communications to other users
49、and are in the form of a SIP URI or TEL URL as defined in 3. 23 24 Service Point Trigger (SPT): a point in the SIP signaling that may cause the S-CSCF to send/proxy the 25 SIP message to an SIP AS or an OSA SCS. 26 The subset of all possible SPTs which are relevant to a particular application are defined by means of Filter 27 Cr
