TIA-4951-A-2012 cdma2000 Unstructured Supplementary Service Data (USSD).pdf

《TIA-4951-A-2012 cdma2000 Unstructured Supplementary Service Data (USSD).pdf》由会员分享，可在线阅读，更多相关《TIA-4951-A-2012 cdma2000 Unstructured Supplementary Service Data (USSD).pdf（74页珍藏版）》请在麦多课文档分享上搜索。

1、 TIA-4951-A April 2014cdma2000Unstructured Supplementary Service Data (USSD) 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 prod

2、ucts, 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 su

3、ch 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 Institute (ANSI) pat

4、ent 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 requiremen

5、ts. 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. Any use of trademarks in this document are for information purposes and do not constitute an endorsement by TIA

6、or this committee of the products or services of the company. (From Project No. TIA-PN-4951-A, formulated under the cognizance of the TIA TR-45 Mobile (b) there 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 Docu

7、ment 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 intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no s

8、earch 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 thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligatio

9、n 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 left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or

10、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 contents. If the Document contains one or more Normative References to a document published by another organization (“other S

11、SO”) engaged in the formulation, development or publication of standards (whether designated as a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA di

12、sclaims 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 of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending

13、 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 of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the conte

14、nts 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. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCUR

15、ACY 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. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WAR

16、RANTIES 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 IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIREC

17、T 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 DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRA

18、CT, 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 FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITAT

19、IONS. 3GPP2 S.X0065-A v1.0 Revision History Revision Description of Changes Date Rev 0 v1.0 Initial Publication April 2012 Rev A v1.0 Rev A Publication March 2014 X.S0065-A 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

20、 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i Unstructured Supplementary Service Data (USSD) Contents List of Figures iii List of Tables . iv Foreword 1 1 Introduction 2 1.1 Scope 2 1.2 Requirements Language . 2 1.3 Normative References 3 1.4 Informative References 3 1.5 Definitions, Symbols an

21、d Abbreviations . 4 1.5.1 Definitions . 4 1.5.2 Symbols and Abbreviations . 4 2 MS registration . 5 2.1 Information flows and functions 5 2.1.1 MS initiated registration 5 3 Network initiated USSD 7 3.1 Handling of network initiated USSD . 7 3.2 Information flows and functions 7 3.2.1 Information fl

22、ow for USSD on traffic channel 7 3.2.2 Information flows for USSD on common channel 10 3.2.2.1 Network initiated USSD Notify on common channel Option 1 11 3.2.2.2 Network initiated USSD Notify on common channel Option 2 12 3.2.3 Network element functions 15 3.2.3.1 Invoking USSD operation from the U

23、SSD Gateway . 15 3.2.3.2 USSD operations at the MSC . 15 3.2.3.3 USSD operations at the MS . 15 3.3 Handoff 16 4 MS initiated USSD . 17 4.1 Handling of an MS initiated USSD 17 4.2 Information flows and functions 17 4.2.1 Information flows 17 4.2.1.1 MS initiated USSD Request . 17 4.2.1.2 MS initiate

24、d USSD Request followed by an immediate USSD Release . 19 4.2.1.3 MS initiated USSD Request after an intersystem handoff . 21 4.2.2 Handling of USSD Request at the MS . 24 4.2.3 Handling of USSD request at the MSC . 24 X.S0065-A 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

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 60 ii 4.2.4 Processing the USSD Request at the USSD Gateway . 25 4.3 Handoff 25 5 Protocol procedures 25 5.1 Requirements for mobile station and USSD Gateway . 25 6 Network Signaling Protocol . 26 6

26、.1 Editorial Conventions 26 6.2 MAP operations . 26 6.2.1 Operation definitions . 26 6.2.1.1 SMSDeliveryForward . 26 6.2.1.2 SMSDeliveryBackward . 28 6.3 MAP Parameters 30 6.3.1 Parameter Identifiers 30 6.3.2 Parameter definitions . 30 6.3.2.1 ServiceIndicatior . 30 6.3.2.2 TransactionCapability . 3

27、1 6.3.2.3 Profile 34 6.3.2.4 USSDAddress 37 6.4 MAP signaling procedures . 40 6.4.1 Intersystem procedures 40 6.4.1.1 SMS delivery point-to-point 40 6.4.1.2 SMS delivery point-to-point for USSD exchange . 47 6.4.1.3 SMSDeliveryBackward . 49 6.4.1.4 SMS Notification . 50 6.4.1.5 SMS Request . 51 6.5

28、Basic Call Processing . 55 6.5.1 Loading of Profile Parameters . 55 6.6 Annexes for the 6xx Series 55 6.6.1 Annex D: SMS Air Interface Delivery Point-to-Point . 55 6.6.2 Serving MSC Receiving an SMD-REQUEST . 56 X.S0065-A 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 2

29、8 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 60 iii List of Figures Figure 1 Architecture for handling of USSD 2 Figure 2 Information flow for MS initiated registration to MSC supporting USSD . 5 Figure 3 Network initiated USSD session . 8 Figure 4 N

30、etwork initiated USSD Notify delivered on common channel Option 1 . 11 Figure 5 Network initiated USSD Notify delivered on common channel Option 2 . 13 Figure 6 MS initiated USSD session . 18 Figure 7 MS initiated USSD session which is immediately released by the MS 20 Figure 8 MS initiated USSD ses

31、sion after handoff . 22 X.S0065-A 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 57 58 59 60 iv List of Tables Table 1 MAP Parameter Identifiers . 30 Table 2 HLR SMSRequest Response 5

32、9 X.S0065-A 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 57 58 59 60 1 Foreword (This Foreword is not part of this document.) This document was prepared by the Third Generation Part

33、nership Project 2 (3GPP2) TSG-X Working Group. This document is a new specification. 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 identifying change in version numb

34、er as follows: X.S0065-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. X.S0065-A 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

35、 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 60 2 1 Introduction This specification is for Unstructured Supplementary Service Data (USSD) support. 1.1 Scope The Unstructured Supplementary Service Data (USSD) mechanism enables a Mobile Station (MS) and Public Land Mo

36、bile Network (PLMN) operator defined application servers to communicate. Figure 1 shows the architecture for handling of USSD sessions. The MSC retrieves the USSD information as part of the subscriber profile at the time of MS registration. The USSD transactions are carried between the USSD client i

37、n the MS and the USSD Gateway (GW) via the MSC. Figure 1 Architecture for handling of USSD This document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor does it specify how a particular application is select

38、ed. This document also defines architecture requirements (stage 2) and the protocol details (stage 3) of the USSD. The new features and enhancements supported in this revision are: USSD messages may be sent over a paging channel; and USSD messages may be sent over an access channel. 1.2 Requirements

39、 Language “Shall” and “shall not” identify requirements to be followed strictly to conform to this 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,

40、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 discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of X.S0065-A v1.0 1 2 3 4 5 6 7 8 9 10

41、 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 60 3 the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal. 1.3 Normative Referen

42、ces References are either specific (identified by date of publication, revision identifier, and version number) or non-specific. For a specific reference, subsequent revisions may not apply. For a non-specific reference, the latest revision applies. A.S0013 3GPP2: A.S0013-D v3.0; 3GPP2 Interoperabil

43、ity Specification (IOS) for cdma2000 Access Network Interfaces Part 3 Features; May 2011. C.S0105 3GPP2: C.S0105-A v1.0, Unstructured Supplementary Service Data (USSD) Service Options for Spread Spectrum Systems: Service Options 78 and 79; June 2013. X.S0002 3GPP2: X.S0002-0 v2.0, MAP Location Servi

44、ces Enhancements; May 2006. X.S0004-520 3GPP2: X.S0004-520-E v2.0, Mobile Application Part (MAP) TCAP Application Signaling Protocols; July 2007. X.S0004-540 3GPP2: X.S0004-540-E v2.0, Mobile Application Part (MAP) Operations Signaling Protocols; July 2007. X.S0004-550 3GPP2: X.S0004-550-E v4.0, Mob

45、ile Application Part (MAP) Parameters Signaling Protocols; January 2010. X.S0004-551 3GPP2: X.S0004-551-E v1.0, Mobile Application Part (MAP) Parameter Type Signaling Protocols; March 2004. X.S0004-630 3GPP2: X.S0004-630-E v3.0, Mobile Application Part (MAP) Basic Call Processing; April 2008. X.S000

46、4-640 3GPP2: X.S0004-640-E v2.0, Mobile Application Part (MAP) Intersystem Operations; July 2007. X.S0004-641 3GPP2: X.S0004-641-E v2.0, Mobile Application Part (MAP) SMS; July 2007. X.S0004-691 3GPP2: X.S0004-691-E v3.0, Mobile Application Part (MAP) Annexes for the 6XX Series; July 2007. TS24.080

47、3GPP: TS 24.080, Mobile radio interface layer 3 supplementary services specification; format and encoding (Release 10); March 2011. TS22.030 3GPP: TS 22.030, Man-Machine Interface (MMI) of the User Equipment (UE) (Release 10); March 2011. TS23.090 3GPP: TS 23.090, Unstructured Supplementary Service

48、Data (USSD); Stage 2 (Release 10); March 2011. TS24.010 3GPP: TS 24.010; 3GPP Mobile radio interface layer 3 supplementary services specification; General aspects (Release 10); June 2011. 1.4 Informative References None X.S0065-A 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

49、 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 60 4 1.5 Definitions, Symbols and Abbreviations 1.5.1 Definitions USSD Request A message requesting information sent by a USSD Client in the MS or a USSD GW. The USSD Request can be used to establish a new USSD session or can be sent in an already established USSD session. USSD Response A response to a USSD Request or to a USSD Notify. USSD Notify A notification sent by a USSD GW to a USSD Client in the MS. The n