1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelUnstructured Supp(3GPP TS 23.0floppy3TECHNICAL SPECIFICATION123 090 V13.0.0 (2016communications system (Phaelecommunications System (pplementary Service Data (USStage 2 .090 version 13.0.0 Release 13GLOBAL SYSTEMOBILE COMMUN16-01) hase 2+); (UMTS)
2、; USSD); 13) TEM FOR ICATIONSRETSI ETSI TS 123 090 V13.0.0 (2016-01)13GPP TS 23.090 version 13.0.0 Release 13Reference RTS/TSGC-0423090vd00 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 -
3、 NAF 742 C Association 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 electr
4、onic and/or print versions 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)
5、 version kept on a specific 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 http:/portal.etsi.org/tb/status/status
6、.asp If you 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 photocopyi
7、ng and microfilm 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 2016.
8、All rights 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 register
9、ed and owned by the GSM Association. ETSI ETSI TS 123 090 V13.0.0 (2016-01)23GPP TS 23.090 version 13.0.0 Release 13Intellectual 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,
10、 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 updates are available on
11、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 server) which are, or may
12、 be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced 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.
13、 These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between 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
14、 not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted as described in clause 3.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 1
15、23 090 V13.0.0 (2016-01)33GPP TS 23.090 version 13.0.0 Release 13Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 4g31 Scope 5g32 References 5g33 Abbreviations . 6g34 Cross phase compatibility 6g35 Network initiated unstructured supplementary service 6g35.
16、1 Handling of network initiated USSD 6g35.2 Functions and information flows 6g35.2.1 Invoking unstructured SS operation from the HLR 6g35.2.2 Invoking unstructured SS operation from the VLR 7g35.2.3 Invoking unstructured SS operation from the MSC 7g35.2.4 Forwarding USSD operations . 7g35.2.5 Handli
17、ng of unstructured SS operation at the MS 7g35.3 Information stored in the HLR . 15g35.4 Information stored in the VLR . 15g35.5 Handover 15g35.6 Cross-phase compatibility 16g36 Mobile initiated unstructured supplementary service data . 16g36.1 Handling of mobile initiated USSD 16g36.2 Functions and
18、 information flows 16g36.2.1 Handling of USSD request at MS . 16g36.2.2 Handling of USSD request at MSC 17g36.2.3 Handling of USSD request at VLR . 17g36.2.4 Handling of USSD request at HLR . 17g36.2.5 Processing the USSD request 17g36.3 Information stored in the HLR . 30g36.4 Information stored in
19、the VLR . 31g36.5 Handover 31g36.6 Cross-phase compatibility 31g3Annex A (informative): Change history . 32g3History 33g3ETSI ETSI TS 123 090 V13.0.0 (2016-01)43GPP TS 23.090 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3G
20、PP). 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 TSG with an identifying change of release date and an increase in version nu
21、mber 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 incremented for all changes of substance, i.e. technical enhancements, corrections, u
22、pdates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TS 123 090 V13.0.0 (2016-01)53GPP TS 23.090 version 13.0.0 Release 131 Scope The present document gives the stage 2 description of Unstructured Supplementary Service Data (USSD
23、). The unstructured supplementary service data (USSD) mechanism allows the Mobile Station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary ser
24、vices. The following diagram shows how handling of USSD is carried out, independently of the applications. Figure 1.1: Handling of USSD The present document defines the requirements for handling USSD at the MS and network entities. It does not include specification of particular applications, nor do
25、es it specify how a particular application is selected. Where more than one application exists at a network entity, routing of messages to the correct application is carried out by the USSD handler. The MMI for USSD is specified in TS 22.030 and TS 22.090. The alphabet indicator and the data coding
26、scheme are defined in TS 23.038. USSD may be initiated by the MS user, or by the network in the following ways: - Network initiated USSD (clause 1); - Mobile initiated USSD (clause 2). 2 References The following documents contain provisions which, through reference in this text, constitute provision
27、s of the present document. 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
28、3GPP document (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: “3G Vocabulary“. 2 3GPP TS 22.030: “Man-Machine Interface (MMI) of the User Equipment (UE)“. 3 3GPP TS 22.090: “U
29、nstructured Supplementary Service Data (USSD) - Stage 1“. 4 3GPP TS 23.038: “Alphabets and language-specific information“. ETSI ETSI TS 123 090 V13.0.0 (2016-01)63GPP TS 23.090 version 13.0.0 Release 133 Abbreviations In addition to those below, abbreviations used in the present document are listed
30、in TR 21.905 1. AI Application Initiated MI Mobile InitiatedUSSD Unstructured Supplementary Service Data 4 Cross phase compatibility The Phase 1 series of GSM specifications defined the signalling protocol which may be used, but they did not specify the operation of USSD as a service. The main body
31、of the present document assumes that the MS and all network entities comply with this phase of USSD. In order to minimize any possible problems between a Phase 1 implementation of USSD and this phase, subclauses 5.6 and 6.6 define the additional requirements for when one or more entity complies with
32、 the Phase 1 USSD specification for network initiated and mobile initiated USSD respectively. 5 Network initiated unstructured supplementary service 5.1 Handling of network initiated USSD The network (MSC, VLR or HLR) can at any time send a USSD operation towards an MS. This operation may be either
33、a request (asking the MS to provide information) or a notification (requiring no information in the response from the MS). No prior provision of USSD is required, although provision of services which make use of USSD may be required. All USSD requests, notifications and responses (except responses t
34、o notifications) contain the USSD string, an alphabet indicator and language indicator. 5.2 Functions and information flows The following text describes the handling of network initiated USSD. Diagrammatic representations are as follows: Figure 5.1 SDL for USSD invocation (HLR, VLR, MSC); Figure 5.2
35、 SDL for forwarding of USSD operations (VLR, MSC); Figure 5.3 SDL for MS; Figure 5.4 Information flow for successful single USSD request; Figure 5.5 Information flow for successful single USSD notification; Figure 5.6 Information flow for successful multiple USSD requests; Figure 5.7 Information flo
36、w for failed USSD request. 5.2.1 Invoking unstructured SS operation from the HLR When an application in the HLR is to send a USSD request or notification to an MS, it shall set up a transaction to the VLR where the subscriber is currently registered and send the operation to the VLR. It shall then a
37、wait a response. The HLR is responsible for controlling the transaction, and shall therefore normally release the transaction when it receives a response from the VLR. The HLR may also release the transaction before receiving a response if necessary (e.g. if an application timer expires). If an appl
38、ication in the HLR needs to send further operations to the same MS as part of the same application, it may continue to use the same transaction until all operations are completed (see figure 5.6). If a different transaction is to be used for a subsequent operation, the HLR shall release the first tr
39、ansaction before starting the next. ETSI ETSI TS 123 090 V13.0.0 (2016-01)73GPP TS 23.090 version 13.0.0 Release 13If the VLR releases the transaction at any time (e.g. due to user clearing), the HLR shall inform the application and terminate the USSD operation. See subclause 5.2.4 for forwarding of
40、 an HLR invoked operation by the VLR and MSC. 5.2.2 Invoking unstructured SS operation from the VLR When an application in the VLR is to send a USSD request or notification to an MS, it shall set up a transaction to the MSC where the subscriber is currently registered and send the operation to the M
41、SC. It shall then await a response. The VLR is responsible for controlling the transaction, and shall therefore normally release the transaction when it receives a response from the MSC. The VLR may also release the transaction before receiving a response if necessary (e.g. if an application timer e
42、xpires). If an application in the VLR needs to send further operations to the same MS as part of the same application, it may continue to use the same transaction until all operations are completed. If a different transaction is to be used for a subsequent operation, the VLR shall release the first
43、transaction before starting the next. See subclause 5.2.4 for forwarding of a VLR invoked operation by the MSC. If the MSC releases the transaction at any time (e.g. due to the user clearing), the VLR shall inform the application and terminate the USSD operation. 5.2.3 Invoking unstructured SS opera
44、tion from the MSC When an application in the MSC is to send a USSD request or notification to an MS, it shall set up a transaction to the MS where the subscriber is currently registered and send the operation to the MS. It shall then await a response. The MSC is responsible for controlling the trans
45、action, and shall therefore normally release the transaction when it receives a response from the MS. The MSC may also release the transaction before receiving a response if necessary (e.g. if an application timer expires). If an application in the MSC needs to send further operations to the same MS
46、 as part of the same application, it may continue to use the same transaction until all operations are completed. If a different transaction is to be used for a subsequent operation, the VLR shall release the first transaction before starting the next. If the MS releases the transaction at any time
47、(e.g. due to the user clearing), the MSC shall inform the application and terminate the USSD operation. NOTE: MSC invoked USSD is only likely to be used for call related operations, where the application is controlling a call to or from the MS. 5.2.4 Forwarding USSD operations The VLR may any time r
48、eceive a USSD operation from the HLR. If the subscriber can be contacted, the VLR shall set up a transaction to the MSC and forward the operation unchanged. Any further information exchange between the HLR and MSC shall be transparent to the VLR. When one transaction is released, the VLR shall relea
49、se the other. The MSC may at any time receive an USSD operation from the VLR. If the subscriber can be contacted, the MSC shall set up a transaction to the MS and forward the operation unchanged. Any further information exchange between the VLR and MS shall be transparent to the MSC. When one transaction is released, the MSC shall release the other. 5.2.5 Handling of unstructured SS operation at the MS The MS may at any time receive a USSD operation (request or notification) from the MSC. If the MS receives a USSD transaction while another USSD transaction (ne
