1、 ETSI TS 124 090 V14.0.0 (2017-03) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Unstructured Supplementary Service Data (USSD); Stage 3 (3GPP TS 24.090 version 14.0.0 Release 14) TECHNICAL SPECIFICATION GLOBAL SYSTEM FOR MOBILE COMMU
2、NICATIONSRETSI ETSI TS 124 090 V14.0.0 (2017-03)13GPP TS 24.090 version 14.0.0 Release 14Reference RTS/TSGC-0424090ve00 Keywords GSM,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Associati
3、on but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print ve
4、rsions of the present document shall not be modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a s
5、pecific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If yo
6、u find errors in the present document, please send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and mic
7、rofilm except as authorized by written permission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights
8、 reserved. DECTTM, PLUGTESTSTM, UMTSTMand the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and own
9、ed by the GSM Association. ETSI ETSI TS 124 090 V14.0.0 (2017-03)23GPP TS 24.090 version 14.0.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is public
10、ly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI W
11、eb server (https:/ipr.etsi.org/). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or ma
12、y become, essential to the present document. Foreword The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference betw
13、een GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.2
14、 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TS 124 090 V14.0.0 (2017-03)33GPP TS 24.090 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Forewor
15、d . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Abbreviations . 5g34 Cross phase compatibility 5g35 Network initiated unstructured supplementary service data operations . 5g35.1 Unstructured supplementary service data request 5g35.1.1 Normal operation 5g35.2 Unstructured
16、 supplementary service data notification 8g35.2.1 Normal operation 8g36 Mobile initiated unstructured supplementary service data operations . 10g36.1 Normal operation 10g36.2 Cross phase compatibility 12g36.2.1 Network only supports protocol version 1 of unstructured supplementary service data opera
17、tions . 12g36.2.2 Mobile station only supports protocol version 1 of unstructured supplementary service data operations 12g3Annex A (informative): Change history . 13g3History 14g3ETSI ETSI TS 124 090 V14.0.0 (2017-03)43GPP TS 24.090 version 14.0.0 Release 14Foreword This Technical Specification (TS
18、) has been produced by ETSI 3rd Generation Partnership Project (3GPP). This TS specifies the stage 3 description of the Unstructured Supplementary Service Data (USSD) operations within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change
19、following formal TSG approval. Should the TSG modify the contents of this TS, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version 3.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for
20、approval; 3 Indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the specification; ETSI ETS
21、I TS 124 090 V14.0.0 (2017-03)53GPP TS 24.090 version 14.0.0 Release 141 Scope The present document gives the stage 3 description of the Unstructured Supplementary Service Data (USSD) operations. The group of unstructured supplementary service data operations is divided into two different classes: -
22、 Network initiated unstructured supplementary service data operations (clause 5); - Mobile initiated unstructured supplementary service data operations (clause 6). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present docu
23、ment. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (
24、including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 24.008: “Mobile radio interface layer 3 specification“. 3 3GPP TS 24.080: “Mobil
25、e radio interface layer 3 supplementary services specification; Formats and coding“. 3 Abbreviations Abbreviations used in the present document are listed in 3GPP TR 21.905. 4 Cross phase compatibility For the mobile initiated USSD operations, a number of changes exist between the present document a
26、nd the protocol version 1 specification. For these operations the main body of the present document assumes that all network entities comply with this version of the service. In this case an additional subclause defines the additional requirements for when one or more network entities or the Mobile
27、Station (MS) complies with the protocol version 1 specifications for the USSD operations. 5 Network initiated unstructured supplementary service data operations 5.1 Unstructured supplementary service data request 5.1.1 Normal operation The network invokes an USSD request by sending a REGISTER messag
28、e containing a UnstructuredSS-Request invoke component to the MS. ETSI ETSI TS 124 090 V14.0.0 (2017-03)63GPP TS 24.090 version 14.0.0 Release 14The MS shall respond to the request by sending a FACILITY message containing the users mobile subscribers response in a return result component. The networ
29、k shall pass the data received in the response to the application handling USSD operations and shall wait for the response of the application. The application may either continue or terminate the dialogue. When the application continues the dialogue, it may initiate another USSD operation by sending
30、 a FACILITY message (see figure 5.2). The operation may either be an USSD request or notification (see subclause 5.1.2). When the application terminates the dialogue, the network shall clear the transaction by sending a RELEASE COMPLETE message. The MS may also clear the transaction at any time by s
31、ending a RELEASE COMPLETE message upon the request of the user. If the MS is unable to process the request received from the network, it shall return an error indication by sending a FACILITY message containing a return error component. Error values are specified in 3GPP TS 24.080. When the MS recei
32、ves an USSD operation in parallel to any call independent supplementary service transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the “USSD-Busy“ error as specified in 3GPP TS 24.080, to indicate the failure in handling a parallel USSD operation. H
33、owever, the network is allowed to initiate USSD operations in parallel to call related transactions. MS Network REGISTER Facility (Return result = UnstructuredSS-Request (ussd-DataCodingScheme, ussd-String) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
34、- - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem) RELEASE COMPLETE Facility (Return result = UnstructuredSS-Request (ussd-DataCodingScheme, ussd-String) FACILITY - - -
35、- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem) FACILITY Facility (Return result = Unstructu
36、redSS-Request (ussd-DataCodingScheme, ussd-String) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Reject
37、 (Invoke_problem) . . . RELEASE COMPLETE Facility (Return result) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
38、 - - - Facility (Reject (Invoke_problem) RELEASE COMPLETE Facility (Return result) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
39、- - - - - - - - - - - - Facility (Reject (Invoke_problem) FACILITY Facility (Return result) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
40、 - - - - - - - - - - - - - - - - Facility (Reject (Invoke_problem) . . . RELEASE COMPLETE Facility (Invoke = ProcessUnstructuredSS-Request (ussd-DataCodingScheme, ussd-String) RELEASE COMPLETE Facility (Invoke = ProcessUnstructuredSS-Request (ussd-DataCodingScheme, ussd-String) FACILITY Facility (Re
41、turn result = UnstructuredSS-Request (ussd-DataCodingScheme, ussd-String) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Facility (Return error (Error) FACILITY - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
42、 - - - - - Facility (Reject (Invoke_problem) . . . RELEASE COMPLETE New Version Subject/Comment Apr 1999 GSM 04.90 6.0.0 Transferred to 3GPP CN1 CN#03 24.090 R99 3.0.0 Approved at CN#03 CN#11 24.090 3.0.0 Rel-4 4.0.0 Approved at CN#11 CN#16 24.090 4.0.0 Rel-4 4.0.1 References updated CN#16 24.090 4.
43、0.1 Rel-5 5.0.0 Rel-5 created after CN#16 CN#26 24.090 5.0.0 Rel-6 6.0.0 Rel-6 created after CN#26 CT#36 24.090 6.0.0 Rel-7 7.0.0 Upgraded unchanged from Rel-6 CT#42 24.090 7.0.0 Rel-8 8.0.0 Upgraded unchanged from Rel-7 2009-12 24.090 8.0.0 - Rel-9 9.0.0 Update to Rel-9 version (MCC) 2011-03 24.090
44、 9.0.0 - Rel-10 10.0.0 Update to Rel-10 version (MCC) 2012-09 24.090 10.0.0 - Rel-11 11.0.0 Update to Rel-11 version (MCC) 2014-09 24.090 11.0.0 - Rel-12 12.0.0 Update to Rel-12 version (MCC) 2015-12 24.090 12.0.0 - Rel-13 13.0.0 Update to Rel-13 version (MCC) 2017-03 24.090 13.0.0 - Rel-14 14.0.0 Update to Rel-14 version (MCC) ETSI ETSI TS 124 090 V14.0.0 (2017-03)143GPP TS 24.090 version 14.0.0 Release 14History Document history V14.0.0 March 2017 Publication
