1、 ETSI TS 122 090 V15.0.0 (2018-07) Digital cellular telecommunications system (Phase 2+) (GSM); Universal Mobile Telecommunications System (UMTS); Unstructured Supplementary Service Data (USSD); Stage 1 (3GPP TS 22.090 version 15.0.0 Release 15) TECHNICAL SPECIFICATION GLOBAL SYSTEM FOR MOBILE COMMU
2、NICATIONSRETSI ETSI TS 122 090 V15.0.0 (2018-07)13GPP TS 22.090 version 15.0.0 Release 15Reference RTS/TSGS-0122090vf00 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. ETSI 2018. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand t
8、he ETSI logo are trademarks of ETSI registered for the benefit of its Members. 3GPPTM and LTETMare trademarks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. oneM2M logo is protected for the benefit of its Members. GSMand the GSM logo are trademarks registe
9、red and owned by the GSM Association. ETSI ETSI TS 122 090 V15.0.0 (2018-07)23GPP TS 22.090 version 15.0.0 Release 15Intellectual Property Rights Essential patents IPRs essential or potentially essential to normative deliverables may have been declared to ETSI. The information pertaining to these es
10、sential IPRs, if any, is publicly 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 upda
11、tes are available on the ETSI Web 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 serv
12、er) which are, or may be, or may become, essential to the present document. Trademarks The present document may include trademarks and/or tradenames which are asserted and/or registered by their owners. ETSI claims no ownership of these except for any which are indicated as being the property of ETS
13、I, and conveys no right to use or reproduce any trademark and/or tradename. Mention of those trademarks in the present document does not constitute an endorsement by ETSI of products, services or organizations associated with those trademarks. Foreword This Technical Specification (TS) has been prod
14、uced by ETSI 3rd Generation Partnership Project (3GPP). 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 be
15、tween 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
16、.2 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 122 090 V15.0.0 (2018-07)33GPP TS 22.090 version 15.0.0 Release 15Contents Intellectual Property Rights 2g3Forew
17、ord . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Abbreviations . 5g34 Description . 5g35 USSD operations MMI mode 5g35.1 Mobile initiated USSD operations 5g35.1.1 Initiating action at the User Equipment (UE) . 5g35.1.2 Action at the network 6g35.1.3 Mobile initiated USS
18、D cross phase compatibility 6g35.1.4 Allocation of service codes (to be noted by network operators) . 6g35.2 Network initiated USSD operation . 7g35.2.1 Initiating actions in the network . 7g35.2.2 Actions at the UE 7g35.3 Network aspects of USSD operation 7g36 USSD operations application mode 8g36.
19、1 General . 8g36.2 Mobile initiated transfer . 8g36.2.1 Initiating action at the UE . 8g36.2.2 Action in the network . 8g36.3 Network initiated transfer . 8g36.3.1 Initiating action in the network . 8g36.3.2 Action at the UE . 8g36.4 External addressing 8g36.5 Charging aspects 8g36.6 Compatibility a
20、spects . 8g36.6.1 Mobile initiated transfer 8g36.6.2 Network initiated transfer . 9g36.7 Interaction with other services 9g36.8 Security 9g3Annex A (informative): Change history . 10g3History 11g3ETSI ETSI TS 122 090 V15.0.0 (2018-07)43GPP TS 22.090 version 15.0.0 Release 15Foreword This Technical S
21、pecification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the T
22、SG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremente
23、d 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 document. ETSI ETSI TS 122 090 V15.0.0 (2018-07)53GPP TS 22.090 version 15.0.0 Release 151 Scope The present document def
24、ines the stage 1 description of Unstructured Supplementary Service Data (USSD) for use in one or a number of Public Land Mobile Networks (PLMNs). 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. References a
25、re 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 (including a GSM document
26、), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.004: “General on supplementary services“. 3 3GPP TS 22.030: “Man-Machine Interface (MMI) of the Mobil
27、e Station (MS)“. 4 3GPP TS 23.038: “Alphabets and language-specific information“. 5 3GPP TS 24.080: “Mobile radio interface layer 3 supplementary services specification Formats and coding“. 3 Abbreviations For the purposes of the present document, the abbreviations listed in TS 21.905 1 apply. 4 Des
28、cription There are two modes of USSD: MMI-mode and application mode. MMI-mode USSD is for the transparent transport of MMI strings entered by the user to the network and for the transparent transport of text strings from the network that are displayed by the mobile for user information. Application
29、mode USSD is for the transparent transport of data between the network and the UE. Application mode USSD is intended to be used by applications in the network and their peer applications in the UE. The communication over the radio interface takes place on the signalling channels using short dialogue
30、s with peak data throughput rate capabilities of up to approximately 600 bits/s outside of a call and 1 000 bits/s during a call. 5 USSD operations MMI mode 5.1 Mobile initiated USSD operations 5.1.1 Initiating action at the User Equipment (UE) If the user enters an MMI string that, according to TS
31、22.030 3, should be treated as USSD, the UE shall send this string to the network using the appropriate operation from TS 24.080 5. The mobile initiated operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The
32、 selection of values for these indicators is a matter for the user. ETSI ETSI TS 122 090 V15.0.0 (2018-07)63GPP TS 22.090 version 15.0.0 Release 15The UE may initiate an USSD operation either during a call or out of call. 5.1.2 Action at the network A network supporting USSD shall examine the alphab
33、et indicator. If the serving network does not recognize the alphabet indicated in the mobile initiated USSD operation, it shall send the operation to the HLR. On recognition of the alphabet, the network shall examine the contents of the string, and take appropriate action, according to the following
34、 rules, depending of the format of the message. Case a) 1, 2 or 3 digits from the set (*, #) followed by 1X(Y), where X=any number 0-4, Y=any number 0-9, then, optionally “* followed by any number of any characters“, and concluding with # SEND: This case is reserved for HPLMN use. When a serving net
35、work receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR. Case b) 1, 2 or 3 digits from the set (*, #) followed by 1X
36、(Y), where X=any number 5-9, Y=any number 0-9, then, optionally “* followed by any number of any characters“, and concluding with # SEND: This case is reserved for VPLMN use. It is up to the VPLMN to decide how to treat it. Case c) 7(Y) SEND, where Y=any number 0-9: This case is reserved for HPLMN u
37、se. When a serving network receives such a message from a visiting subscriber, it shall pass the USSD message directly to the HPLMN. If it receives it from a home subscriber, it is up to the network to decide whether to treat it locally or to pass it to the HLR. Case d) All other formats: The visite
38、d network examines the message. If it is able, it acts upon it. Failing that, it passes the message to the HLR. If the HLR does not support the alphabet indicated, it shall inform the UE. The network shall terminate the mobile initiated operation by responding to the request from the mobile with eit
39、her an error signal, or a text string indicating the outcome of the operation. The response string uses the characters available in the selected alphabet as defined in TS 23.038 4. If no indication to the user is required, the response string may be empty. The response to the mobile initiated USSD o
40、peration shall contain alphabet and language indicators. The selection of values for these indicators is a matter for the network operator. 5.1.3 Mobile initiated USSD cross phase compatibility In situations of incompatibility the mobile initiated USSD operation will be rejected by a non-supporting
41、network and the attempt will fail. In this situation, if it is possible to encode the content of the USSD message in the IA5 alphabet, the UE shall attempt the operation again using the IA5 format without the alphabet and language indicators. This procedure is not applicable if an operation failure
42、is due to alphabet support problems, services not supported or network failure problems. 5.1.4 Allocation of service codes (to be noted by network operators) Service codes for use in control of Supplementary Services are standardized by international agreement, so must not be used by PLMNs unless au
43、thorized, except for those codes allocated for PLMN use. If the message is of the format: 1, 2 or 3 digits from the set (*, #), followed by NN(N), where N=0-9, ETSI ETSI TS 122 090 V15.0.0 (2018-07)73GPP TS 22.090 version 15.0.0 Release 15optionally followed by “* and any number of any characters“,
44、and terminating in # SEND: then NN(N) is known as the service code. Only codes specified in TS 22.030 3 and those defined in cases a) and b) above may be used. All other values are reserved. Similarly, if the message is of the format: X(Y) SEND, where X=0-6 or 8-9 and Y=0-9: the codes X(Y) are stand
45、ardized. Only codes specified in TS 22.030 3 subclause 4.5.5 may be used. All other values are reserved. 5.2 Network initiated USSD operation 5.2.1 Initiating actions in the network At any stage while the UE is registered with a network, the network may send an unstructured string to the UE. This st
46、ring contains operator determined information that is relevant to the user. If the network is unable to successfully reach the UE, then an error shall be returned to the node that originated the operation. The network initiated USSD operation shall contain an alphabet indicator and language indicato
47、r. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the network operator. 5.2.2 Actions at the UE If the is unable to process the network initiated USSD operation (e.g. the feature is not supported or the user is e
48、ngaged in another MMI activity) then an error indication shall be returned to the node that originated the operation. If the alphabet indicated by the network is not supported by the UE, the UE shall inform the network. The network may explicitly indicate to the UE that a response from the user is r
49、equired. In this case, the next string entered by the user shall be used as the responseand this string is not interpreted according to normal MMI procedures stated in TS 22.030 3. An MMI command shall be provided to allow the user to terminate the dialogue with a null response. The response string uses the characters available in the selected alphabet as defined in TS 23.038 4. The response is sent to the node that originated the operation. If the network does not indicate that a response is required, then the normal MMI procedures on the
