TIA-1165 400-2012 cdma2000 Femtocell Network 1x and IMS Supplementary Services Aspects《Cdma2000 Femtocell网络 1x和IMS补充性服务方面》.pdf

1、 TIA-1165.400 February 2012cdma2000 Femtocell Network: 1x and IMSSupplementary Services Aspects NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufacturers and purchasers, facilitating interchangeability and

2、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 Standards and Publications shall not in any respect preclude any member or non-member of TIA from manufacturing or selling products n

3、ot conforming to such Standards 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 I

4、nstitute (ANSI) patent 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 re

5、gulatory requirements. 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-0055.400, formulated under the cognizance of the TIA TR-45 Mobile (b) the

6、re is no assurance 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

7、 use of intellectual 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

8、 from the holder thereof 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,

9、 which are instead 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

10、 Document or its contents. 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), wheth

11、er such reference consists 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;

12、 (ii) TIAs policy of 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 identificatio

13、n to TIA of a claim 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

14、of the Document. ALL 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 INTELLECT

15、UAL PROPERTY RIGHTS. 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 S

16、ERVICE REFERRED TO 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

17、 CONSEQUENTIAL DAMAGES (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 NEGATIO

18、N OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. 3GPP2 X.S0059-400-0 v1.0 Revision History Revision Description of Changes Date Rev. 0 v1.0 Initial Publication December 2011 3GPP2 X.S0059-400-0 v1.0 1

19、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 57 58 59 400-i Contentscdma2000 Femtocell Network: 1x Supplementary Service Aspects CONTENTS List of Figures .iv List of Tablesv Foreword .vi 1

20、 Introduction1 1.1 Scope1 1.2 Document Conventions1 2 References2 2.1 Normative References2 3 Definitions, Abbreviations and Acronyms.3 3.1 Definitions .3 3.2 Abbreviations and Acronyms 3 4 Architectural Model and Reference Points.4 5 Informational Flows.5 5.1 Overview5 5.2 Line ID Services 5 5.2.1

21、Calling Number Identification Presentation (CNIP)5 5.2.1.1 CNIP Invocation to an Idle Subscriber.5 5.2.2 Calling Number Identification Restriction (CNIR) .6 5.2.2.1 CNIR Invocation 6 5.2.2.2 CNIR Temporary Activation or De-Activation with Call 7 5.3 Communication Diversion Service 8 5.3.1 Call Forwa

22、rdingBusy (CFB)8 5.3.1.1 CFB Invocation 8 5.3.1.2 CFB Invocation with Call Collision.8 5.3.2 Call ForwardingDefault (CFD)10 5.3.2.1 CFD Invocation with No Answer.10 5.3.2.2 CFD Invocation with No Response to Page.14 5.3.3 Call ForwardingNo Answer (CFNA) 16 5.3.4 Call ForwardingUnconditional (CFU).16

23、 5.4 Communication Barring.16 5.4.1 Incoming Call Barring (ICB) / Anonymous Call Rejection (ACR).16 5.4.2 Outgoing Call Barring (OCB) .16 5.5 Mid-Call Services 18 5.5.1 Call Hold (HOLD).18 5.5.1.1 HOLD Invocation OEP-initiated.18 5.5.2 Call Transfer (CT) .20 3GPP2 X.S0059-400-0 v1.0 1 2 3 4 5 6 7 8

24、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 57 58 59 Contents 400-ii 5.5.3 Call Waiting (CW).20 5.5.3.1 CW Invocation Mobile User Accepts Incoming Call. 20 5.5.3.2 CW Invocation Mobile User Rejects Inc

25、oming Call 23 5.5.4 Three-Way Calling (3WC) 26 5.5.4.1 3WC Invocation Establishment 26 5.5.4.2 3WC Invocation Connection 28 5.6 Other Services30 5.6.1 Message Waiting Notification (MWN) .30 5.6.1.1 MWN via an MS Indication MS Idle . 30 5.6.1.2 MWN via an MS Indication MS on an Active Call 31 5.6.1.3

26、 MWN After Handoff. 32 6 Procedures and Protocols .33 6.1 Overview33 6.1.1 Guidelines on use of IOS Messages.33 6.1.2 Guidelines on constructing a SIP MESSAGE request.33 6.1.3 Guidelines on sending a SIP MESSAGE request 33 6.1.4 Guidelines on constructing a SIP INFO request 33 6.1.4.1 Construction o

27、f SIP INFO request by FAP (sent toward FCS) . 33 6.1.4.2 Construction of SIP INFO request by FCS (sent toward FAP) . 34 6.1.5 Guidelines on sending a SIP INFO request .34 6.1.5.1 Sending a SIP INFO request by FAP (toward FCS) 34 6.1.5.2 Sending a SIP INFO request by FCS (toward FAP) 34 6.2 Line ID S

28、ervices 34 6.2.1 Calling Number Identification Presentation (CNIP)34 6.2.1.1 FAP procedures. 34 6.2.1.2 FCS procedures . 35 6.2.2 Calling Number Identification Restriction (CNIR)35 6.2.2.1 FCS procedures . 35 6.3 Communication Diversion Service 35 6.3.1 Call ForwardingBusy (CFB)35 6.3.1.1 FCS proced

29、ures . 35 6.3.2 Call ForwardingDefault (CFD)36 6.3.2.1 FCS procedures . 36 6.4 Communication Barring.37 6.4.1 Outgoing Call Barring (OCB)37 6.4.1.1 FCS procedures . 37 6.5 Mid-Call Services 37 6.5.1 Call Hold (HOLD).37 6.5.1.1 FAP procedures. 37 6.5.1.2 FCS procedures . 38 6.5.2 Call Waiting (CW).38

30、 6.5.2.1 FAP procedures. 38 6.5.2.2 FCS procedures . 38 6.5.3 Three-Way Calling (3WC) 41 6.5.3.1 FAP procedures. 41 6.5.3.2 FCS procedures . 41 3GPP2 X.S0059-400-0 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

31、 48 49 50 51 52 53 54 55 56 57 58 59 400-iii Contents6.6 Other Services46 6.6.1 Message Waiting Notification (MWN) .46 6.6.1.1 FAP procedures46 6.6.1.2 FCS procedures 47 7 Timer Definitions.49 3GPP2 X.S0059-400-0 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 3

32、1 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 57 58 59 List of Figures 400-iv LIST OF FIGURES Figure 1 CNIP Invocation to an Idle Subscriber .5 Figure 2 CNIR Invocation.7 Figure 3 Call Forwarding-Busy (CFB) Invocation8 Figure 4 Call Forwarding-Busy (CFB) Invocation wit

33、h Call Collision 9 Figure 5 Call Forwarding-Default (CFD) Invocation with No Answer 12 Figure 6 Call Forwarding-Default (CFD) Invocation with No Response to Page.14 Figure 7 Outgoing Call Barring (OCB).17 Figure 8 Call Hold (HOLD) OEP-initiated 19 Figure 9 CW Invocation Mobile User Accepts Incoming

34、Call 21 Figure 10 CW Invocation Mobile User Rejects Incoming Call .24 Figure 11 3WC Invocation Establishment .27 Figure 12 3WC Invocation Connection29 Figure 13 MWN Invocation MS Idle .31 Figure 14 MWN Invocation MS on an Active Call32 3GPP2 X.S0059-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

35、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 57 58 59 400-v List of TablesLIST OF TABLES Table 1 Timer Values 49 3GPP2 X.S0059-400-0 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

36、33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 Foreword 400-vi FOREWORD (This foreword is not part of this specification.) This document was prepared by the Third Generation Partnership Project 2 (3GPP2) TSG-X Working Group. This document is a new specification. Thi

37、s document is part of a multi-part document. The multiple parts together specify the cdma20001Femtocell Network. This document is subject to change following formal approval procedures. Should this document be modified in the future, it will be re-released with a change-of-release date and an identi

38、fying change in version number as follows: X.S0059-400-X-n where: X: a numerical or uppercase alphabetic character A, B, C, that indicates the revision level; n: a numeric string 1, 2, 3, that indicates the point release level. .1cdma2000 is the trademark for the technical nomenclature for certain s

39、pecifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000 is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States. 3GPP2 X.S0059-400-0 v1.0 4 8 9 10 11 12 13 14 15 16 17 20 2

40、1 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 57 58 59 400-1 1 Introduction1 2 3 1 Introduction 5 6 7 18 19 1.1 Scope This document defines the Stage 2 service descriptions, call flows and normative Stage 3 procedures that provide cdma2000

41、 1x circuit-switched Supplementary Services to the MS through the IMS core network when the MS is camped on a Femtocell Access Point (FAP). Specifically, 1x Supplementary Services are provided to an MS that is attached to a FAP using the cdma2000 1x radio interface. The MS is homed in the 1x circuit

42、-switched domain, and is registered in the 1x HLR. The system takes advantage of IMS functionality to provide subscribed services. 1.2 Document Conventions “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Sho

43、uld” 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 form) a certain possibility or course of action is dis

44、couraged 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. 3GPP2 X.S0059-400-0 v1.0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

45、 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 57 58 59 2 References 400-2 2 References 2.1 Normative References This section provides references to other specifications and standards that are necessary to implement this docum

46、ent. A.S0014 3GPP2 A.S0014-D v2.0, “Interoperability Specification (IOS) for cdma2000 Access Network Interfaces - Part 4 (A1, A1p, A2, and A5 Interfaces)”; August 2009. C.S0005 3GPP2 C.S0005-0 v3.0, “Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems”; June 2000. RFC 2976

47、IETF RFC 2976, “The SIP Info Method”; October 2000. 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 Sessi

48、on Description Protocol (SDP)”; June 2002. RFC 3326 IETF RFC 3326, “The Reason Header Field for the Session Initiation Protocol (SIP)”; December 2002. RFC 3966 IETF RFC 3966, “The tel URI for Telephone Numbers”; December 2004. RFC 4240 IETF RFC 4240, “Basic Network Media Services with SIP,”; Decembe

49、r 2005. TS 24.229 3GPP TS 24.229 v9.3.0, “Internet Protocol (IP) multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3”; March, 2010. TS 29.163 3GPP TS 29.163 v7.2.0, “Interworking between the IP Multimedia (IM) Core Network (CN) subsystem and Circuit Switched (CS) networks”; March, 2006. X.S0059-000 3GPP2 X.S0059-000-0 v1.0, “cdma2000 Femtocell Network: Overview and List of Parts”; January, 2010. X.S0059-200 3GPP2 X.S0059-200-0 v1.0, “cdma2000