1、GSM GSM 03.90 December 1996 Version 5.0.0 Source: ETSI TC-SMG Reference: TS/SMG-O30390Q ICs: 33.020 Key words: Digital cellular telecommunications system, Global System for Mobile communications (GSM) GLOBAL SYSTEM FOR MOBILE COMMJNICATIONS Digital cellular telecommunications system; Unstructured Su
2、pplementary Service Data (USSD) - Stage 2 (GSM 03.90) ETSI European Telecommunications Standards Institute ETSI Secretariat Postal address: F-O6921 Sophia Antipolis CEDEX - FRANCE Office address: 650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE X.400: c=fr, a=atlas, p=etsi, ssecretariat
3、 - Internet: secretariat Q etci.fr . Tel.: +33 4 92 94 42 O0 - Fax: +33 4 93 65 47 16 Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. O European Telecommunications Standards
4、 Institute 1996. All rights resewed. STD.ETS1 GSM 03.70-ENGL L77b 3400855 015283b 53b m Page 2 GSM 03.90 version 5.0.0: December 1996 Whilst every care has been taken in the preparation and publication of this document, errors in content, typographical or otherwise, may occur. If you have comments c
5、oncerning its accuracy, please write to “ETSI Editing and Committee Support Dept.“ at the address shown on the title page. . STDmETSI GSM 03-70-ENGL 177b 3q00855 0352837 q72 D Page 3 GSM 03.90 version 5.0.0: Decem ber 1996 Contents Foreword . 5 1 scope . 7 2 Normative references . 7 3 Abbreviations
6、8 4 Cross phase compatibility . 8 5 Network initiated unstructured supplementary service . 8 Handling of network initiated USSD . 8 Functions and information flows 8 5.1 5.2 5.2.1 5.2.2 5.2.3 5.2.4 Forwarding USSD operations 9 5.2.5 Information stored in the HLR . 18 Information stored in the VLR .
7、18 5.5 Handover 18 Invoking unstructured SS operation from the HLR 8 Invoking unstructured SS operation from the VLR 9 Invoking unstructured SS operation from the MSC . 9 Handling of unstructured SS operation at the MS . 1 0 5.3 5.4 5.6 Cross-phase compatibility 18 6 Mobile initiated unstructured su
8、pplementary service data 19 Handling of mobile initiated USSD . 19 Functions and information flows 19 6.2.1 Handling of USSD request at MS . 19 6.2.2 Handling of USSD request at MSC . 19 6.2.3 Handling of USSD request at VLR 20 6.2.4 Handling of USSD request at HLR 20 6.2.5 Processing the USSD reque
9、st 20 6.3 Information stored in the HLR . 34 6.4 Information stored in the VLR . 34 6.5 Handover 34 6.6 Cross-phase compatibility 34 6.1 6.2 History . 35 STDnETSI GSM 03-7U-ENGL L77b W 3400855 0352838 309 D Page 4 GSM 03.90 version 5.0.0: December 1996 Blank page STDmETSI GSM 03-90-ENGL L77b m 34008
10、55 0352837 2q5 m Page 5 GSM 03.90 version 5.0.0: December 1996 Foreword This Global System for Mobile communications Technical Specification (GTS) has been produced by the Special Mobile Group (SMG) Technical Committee (TC) of the European Telecommunications Standards Institute (ETSI). This GTS defi
11、nes the stage 2 description of Unstructured Supplementary Service Data (USSD) within the digital cellular telecommunications system. The contents of this GTS are subject to continuing work within TC-SMG and may change following formal TC-SMG approval. Should TC-SMG modify the contents of this GTS it
12、 will then be republished by ETSI with an identifying change of release date and an increase in version number as follows: Version 5.x.y where: y the third digit is incremented when editorial only changes have been incorporated in the specif ication; x the second digit is incremented for all other t
13、ypes of changes, .e. technical enhancements, corrections, updates, etc. The specification from which this GTS has been derived was originally based on CEPT documentation, hence the presentation of this GTS may not be entirely in accordance with the ETSVPNE rules. STD.ETSI GSM 03-70-ENGL L77b m 34008
14、55 OL5284L 7T3 m Page 7 GSM 03.90 version 5.0.0: December 1996 1 Scope This Global System for Mobile communications Technical Specification (GTS) gives the stage 2 description of Unstructured Supplementary Service Data (USSD). The unstructured supplementary seMce data (USSD) mechanism allows the Mob
15、ile 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 services. The following diagram shows how handling of USSD is carried out, indepe
16、ndently of the applications. USER Applica tions Handler App 1 i ca tions Handler Figure 1 .l: Handling of USSD This specification 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 particu
17、lar 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 GSM 02.30 and GSM 02.90. The alphabet indicator and the data coding scheme are defined in GSM 0
18、3.38. 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 Normative references This GTS incorporates by dated and undated reference, provisions from other publications. These normative references ar
19、e cited at the appropriate places in the text and the publications are listed hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply to this GTS only when incorporated in it by amendment or revision. For undated references, the latest edition of the
20、 publication referred to applies. 131 41 GSM O1 .O4 (ETR 350): “Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms“. GSM 02.30 (ETS 300 907): “Digital cellular telecommunications system (Phase 2+); Man-Machine Interface (MMI) of the Mobile Station (MS)“. GSM 02.90: “Di
21、gital cellular telecommunications system; Unstructured Supplementary Service Data (USSD) - Stage 1 II. GSM 03.38 (ETS 300 900): “Digital cellular telecommunications system (Phase 2+); Alphabets and language-specific information“. STD-ETSI GSM 03*90-ENGL L77b 3400855 0352842 83T Page 8 GSM 03.90 vers
22、ion 5.0.0: December 1996 3 Abbreviations In addition to those below, abbreviations used in this GTS are listed in GSM O1 .O4 l. AI MI USSD Application Initiated Mobile Initiated Unstructured Supplementary Service Data 4 Cross phase compatibility The Phase 1 series of GSM specifications defined the s
23、ignalling protocol which may be used, but they did not specify the operation of USSD as a service. The main body of this specification assumes that the MS and all network entities comply with this phase of USSD. In order to minimize any possible problems between a Phase i implementation of USSD and
24、this phase, subclauses 5.6 and 6.6 define the additional requirements for when one or more entity complies with 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 T
25、he network (MSC, VLR or HLR) can at any time send a USSD operation towards an MS. This operation may be either 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 serv
26、ices which make use of USSD may be required. All USSD requests, notifications and responses (except responses to 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 US
27、SD. Diagrammatic representations are as follows: Figure 5.1 Figure 5.2 Figure 5.3 SDL for MS; Figure 5.4 Figure 5.5 Figure 5.6 Figure 5.7 SDL for USSD invocation (HLR, VLR, MSC); SDL for forwarding of USSD operations (VLR, MSC); Information flow for successful single USSD request; Information flow f
28、or successful single USSD notification; Information flow for successful multiple USSD requests; Information flow 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 transac
29、tion to the VLR where the subscriber is currently registered and send the operation to the VLR. It shall then await 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 rele
30、ase the transaction before receiving a response if necessary (e.g. if an application timer expires). If an application 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 figur
31、e 5.6). If a different transaction is to be used for a subsequent operation, the HLR shall release the first transaction before starting the next. If 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 s
32、ubclause 5.2.4 for forwarding of an HLR invoked operation by the VLR and MSC. STD.ETS1 GSM 03g70-ENGL 199b 3400855 0352843 77b Page 9 GSM 03.90 version 5.0.0: December 1996 5.2.2 Invoking unstructured SS operation from the VLR When an application in the VLR is to send a USSD request or notification
33、to an MS, it shall set up a transaction to the MSC where the subscriber is currently registered and send the operation to the MSC. 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
34、from the MSC. The VLR may also release the transaction before receiving a response if necessary (e.9. if an application timer expires). 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
35、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. 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
36、the user clearing), the VLR shall inform the application and terminate the USSD operation. 5.2.3 Invoking unstructured SS operation 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 currentl
37、y registered and send the operation to the MS. It shall then await a response. The MSC is responsible for controlling the transaction, 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
38、 necessary (e.9. if an application timer expires). If an application in the MSC 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 o
39、peration, the VLR shall release the first transaction before starting the next. If the MS releases the transaction at any time (e.9. 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 ope
40、rations, where the application is controlling a call to or from the MS. 5.2.4 Forwarding USSD operations The VLR may any time receive 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 info
41、rmation exchange between the HLR and MSC shall be transparent to the VLR. When one transaction is released, the VLR shall release 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 th
42、e 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. - STD-ETSI GSM 3.90-ENGL 399b m 3400855 0352844 b02 m Page 10 GSM 03.90 version 5.0.0: December 1996 5.2.5 Handling of un
43、structured 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 (network or mobile initiated) or a non-call related supplementary service transaction is in progress, the MS
44、shall reject the new transaction. If the MS receives a USSD operation when t is in a state where the MMI required is not possible (e.g. during dialling) it shall reject the operation. If the MS does not support the alphabet indicated in the USSD operation, it shall inform the network. If the MS is i
45、n a state where it can handle the operation, it shall process the operation as follows: - For a USSD request, the MS shall display the text provided and await user input. If the user enters a response, the MS shall return the response to the MSC, maintaining the transaction. If the user requests rel
46、ease of the transaction, the MS shall release the transaction. See GSM 02.30 for details of the MMI. - For a USSD notification, the MS shall display the text provided and send back a response. After sending the response to a USSD operation, the MS shall wait for the network to release the transactio
47、n. If, while awaiting this release, the MS receives any further USSD operations, it shall process them in the normal way. STD.ETSI GSM 03.90-ENGL L77b = 3400855 0352845 547 Page 11 GSM 03.90 version 5.0.0: December 1996 USSD USSD release notify request / rocess USSD-NI1 Figure 5.1 release notify req
48、uest I I USSD notiy 390-5 1 (1) USSD release release request PUTS AND OUTPUTS Sourcddestination of messages shown tdfrom the right is the application. Sourcddestination of messages shown tdfrom the left depends on the entity being described, as follows: Entity To/From (, wE.r ,) ( idle 1 response er
49、ror wait user response idle i Figure 5.1: Network initiated USSD invoked at HLR, VLR or MSC STD-ETSI GSM 03.90-ENGL L77b = 3900855 015284b q85 Page 12 GSM 03.90 version 5.0.0: December 1996 error 1 Process-N2 390-52( 1) release release USSD Figure 5.2 idle / described, as follows: Entity Left Right notify request USSD reachable reachable release release USSD response error idle u / release USSD USSD notify request release Figure 5.2: Network initiated USSD forwarding at VLR or MSC STD*ETSI GSM 03*90-ENGL L99b 3400
