TIA-873-B SERIES-2009 ALL-IP CORE NETWORK MULTIMEDIA DOMAIN - OVERVIEW (INCLUDES STANDARDS TIA-873 000 TIA-873 002 TIA-873 003 TIA-873 004 TIA-873 005 TIA-873 006 TIA-873 007 TIA-8.pdf

《TIA-873-B SERIES-2009 ALL-IP CORE NETWORK MULTIMEDIA DOMAIN - OVERVIEW (INCLUDES STANDARDS TIA-873 000 TIA-873 002 TIA-873 003 TIA-873 004 TIA-873 005 TIA-873 006 TIA-873 007 TIA-8.pdf》由会员分享，可在线阅读，更多相关《TIA-873-B SERIES-2009 ALL-IP CORE NETWORK MULTIMEDIA DOMAIN - OVERVIEW (INCLUDES STANDARDS TIA-873 000 TIA-873 002 TIA-873 003 TIA-873 004 TIA-873 005 TIA-873 006 TIA-873 007 TIA-8.pdf（866页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-873.000-B June 2009 ALL-IP CORE NETWORK MULTIMEDIADOMAIN - OVERVIEW NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and improvement of products

2、, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products not conforming to such S

3、tandards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted by TIA in accordance with the American National Standards Institute (ANSI) patent

4、policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all safety problems associated with its use or all applicable regulatory requirements.

5、It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-4935.000-RV2, formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance

6、that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. The use or practice of contents of this Document may involve the use of intellectua

7、l property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent applications are claimed and called to TIAs attention, a statement from the holder th

8、ereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither be a party to discussions of any licensing terms or conditions, which are instead

9、left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or provided in the Manual have been complied with as respects the Document or its co

10、ntents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference c

11、onsists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or letters of assurance relating to any such Normative Reference; (ii) TIAs policy o

12、f encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or publications of the other SSO shall not constitute identification to TIA of a claim

13、 of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, designs or services or any claims of compliance with the contents of the Document. AL

14、L WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHANTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS

15、. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR THE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO

16、IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMA

17、GES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A F

18、UNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54

19、 55 56 58 59 60 iALL-IP CORE NETWORK MULTIMEDIA DOMAIN - OVERVIEW CONTENTS 1 Introduction1 2 Scope2 3 Reference .3 3.1 Normative References3 3.2 Informative References3 4 Terminology.4 5 Assumptions.5 6 Definitions6 6.1 Quality of Service (QoS) .6 6.2 Home Subscriber Server (HSS) .6 7 Abbreviations.

20、7 8 MMD Core Network Architecture .9 8.1 Network Entities 13 8.2 Reference Points 13 9 Documents for the core network packet data subsystem14 10 Documents for the core network IP Multimedia subsystem.15 11 Documents for the core network service capability subsystem16 X.P0013-000-B v1.0 1 2 3 4 5 6 7

21、 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 ii LIST OF FIGURES Figure 1 HSS Collective 6 Figure 2 MMD Core Network Architecture Model. 9 Figure 3 Packet Data Subsystem Core Network Architec

22、ture Model . 10 Figure 4 IMS Core Network Architecture Model 11 Figure 5 Session Control Reference Model. 12 Figure 6 Multimedia Application Server Control Plane 12 X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42

23、 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 iiiLIST OF TABLES Table 1. Abbreviations.8 X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 iv FOREWORD (This

24、foreword is not part of this document) This document was prepared by 3GPP2 TSG-X. This document contains major modifications from the previous revision. This document is part of the series of documents X.S0013. “Shall“ and “shall not“ identify requirements to be followed strictly to conform to this

25、document and from which no deviation is permitted. “Should“ and “should not“ indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative

26、 form) a certain possibility or course of action is discouraged but not prohibited. “May“ and “need not“ indicate a course of action permissible within the limits of the document. “Can“ and “cannot“ are used for statements of possibility and capability, whether material, physical or causal. REVISION

27、 HISTORY Revision Changes Date 0 v1.0 Initial Publication December 2003 0 v2.0 Version 2 July 2005 A. v1.0 Release A November 2005 B. v1.0 Release B December 2007 X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 4

28、3 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 1 1 Introduction The Multimedia Domain (MMD) is a collection of core network entities providing 3rdgeneration capabilities and based on IP protocols, elements and principles. This document provides an introduction to the core network elements and int

29、erfaces that make up a portion of the MMD. This document also introduces the series of documents that provide the complete specification of the core network interfaces and protocols that provide this part of the MMD capabilities. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

30、21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 2 2 Scope This document contains the introduction of the Stage-1, Stage-2 and Stage-3 recommendations for the Multimedia Domain. It includes an overview of the system elements and int

31、erfaces and lists the series of documents that provide the complete specifications for the core network portions of the MMD. Not all MMD entities and interfaces may be covered by this version of this series of specifications. The specific entities and interfaces covered by a particular version are i

32、dentified in each of the individual specifications. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 3 3 Reference 3.1 Normative References The following standard

33、s and documents contain provisions which, through reference in this text, constitute provisions of this document. At the time of publication, the editions indicated were valid. 2 3GPP2 X.S0011-D v1.0, “cdma2000 Wireless IP Network Standard” 3 3GPP2 X.S0013-002-B v1.0, “IP Multimedia Subsystem (IMS);

34、 Stage-2” 4 3GPP2 X.S0013-003-B v1.0, “IP Multimedia (IM) session handling; IM call model” 5 3GPP2 X.S0013-004-B v1.0, “IP Multimedia Call Control Protocol based on SIP and SDP; Stage-3” 6 3GPP2 X.S0013-005-B v1.0, “IP Multimedia (IM) Subsystem Cx Interface; Signaling flows and message contents” 7 3

35、GPP2 X.S0013-006-B v1.0, “Cx Interface based on the Diameter protocol; Protocol details” 8 3GPP2 X.S0013-007-A v1.0, “IP Multimedia Subsystem; Charging Architecture” 9 3GPP2 X.S0013-008-A v1.0, “IP Multimedia Subsystem; Offline Accounting, Information Flows and Protocol” 10 3GPP2 X.S0013-009-0 v1.0,

36、 “MMD Call Flow Examples” 11 3GPP2 X.S0013-010-B v1.0, “IP Multimedia Subsystem (IMS) Sh Interface signaling flows and message contents” 12 3GPP2 X.S0013-011-B v1.0, “Sh interface based on the Diameter protocol” 13 3GPP2 X.S0013-012-0 v1.0, “Service Based Bearer Control Stage 2” 14 3GPP2 X.S0013-013

37、-0 v1.0, “Service Based Bearer Control Tx Interface Stage-3” 15 3GPP2 X.S0013-014-0 v1.0, “Service Based Bearer Control Ty Interface Stage 3” 16 3GPP2 X.S0013-016-0 v1.0, “Messaging service using the IP Multimedia (IM) Subsystem (IMS)” 3.2 Informative References 1 3GPP2 S.R0037-0, “IP Network Archit

38、ecture Model for cdma2000 Spread Spectrum Systems”, Version 3.0, August, 2003. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 4 4 Terminology This document uses

39、 the following “verbal forms” and “verbal form definitions”: a. “shall” and “shall not” identify items of interest that are to be strictly followed and from which no deviation is recommended, b. “should” and “should not” indicate items of interest that are highly desirable and particularly suitable,

40、 without identifying or excluding other items; or (in the negative form) indicate items of interest that are not desirable, are not particularly suitable, or are not recommended but not prohibited, and c. “may” and “may not” indicate items of interest that are optional but permissible within the lim

41、its of this recommendation. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 5 5 Assumptions a. The architecture described in this document assumes the following

42、protocols: I. SIP (Session Initiation Protocol), II. DIAMETER, and III. MOBILE IP. b. The use, support, and interoperation of IPv4 and IPv6 in the All-IP network are currently assumed in this document. c. There are known bearer paths not shown in Figure 2 (e.g., bearer paths between the Application

43、Servers and the Border Router, the Application Servers and the Media Resource Function Processor). Some of these interfaces are shown in additional diagrams in this document, but not numerically labeled, see Section 2. d. There are known signaling paths not shown in Figure 2 (e.g., signaling paths b

44、etween two Call Session Control Function (CSCF), two AAA, an external SIP entity beyond the Border Router and the CSCF). Some of these interfaces are shown in additional diagrams in this document, but not numerically labeled, see Section 2. X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1

45、7 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59 60 6 6 Definitions This section provides definitions of some terms used within this document. 6.1 Quality of Service (QoS) QoS refers to a set of capabilities that a network m

46、ay provide to a communications session. These capabilities can be specified so that particular applications (e.g., conversational voice, video, streaming audio) fulfill human factors or other requirements with respect to fidelity and performance. 6.2 Home Subscriber Server (HSS) For the documents re

47、lated to the IP Multimedia Subsystem (IMS) elements and the Sh and Cx interfaces (see “11/Sh” and “16/Cx” in Figures 2, 3, 4 and 6), the term “HSS” is used to represent the Home AAA entity plus the Databases to which it interfaces. When used to define interfaces, the term HSS implies interfaces to t

48、he AAA component of the collective. The functionalities of the HSS collective and its interfaces are solely defined by the MMD documents and their normative references. The use of this term does not imply the support of any additional functionality. Other functionalities and interfaces supported by

49、the AAA and Databases (e.g., Packet Data Subsystem Authentication, Authorization, Accounting) defined in other documents are not changed by the use of the HSS term in the MMD series of documents. Figure 1 shows the HSS collective. For the purposes of the IMS elements and interfaces, the AAA plus the Databases are equivalent to the HSS: 4AAADatabasesFigure 1 HSS Collective X.P0013-000-B v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 58 59