USSD Call Flow

3GPP2 X.S0065 v1.
0 April 2012
Unstructured Supplementary Service Data (USSD)
2012 3GPP2 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.
3GPP2 X.S0065 v1.0
Revision History
Revision Rev 0 v1.0 Description of Changes Initial publication Date 20 April 2012
USSD
X.S0065 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
Unstructured Supplementary Service Data (USSD)
TABLE OF CONTENTS
Table of Figures.....................................................................................................................................................iii Table of Tables ...................................................................................................................................................... iv Foreword ................................................................................................................................................................ v 1 Introduction .............................................................................................................................................. 1 1.1 1.2 1.3 1.4 2 Scope.......................................................................................................................................... 1 Requirements Language ............................................................................................................. 1 Normative References ................................................................................................................ 2 Informative References .............................................................................................................. 2
Definitions, Symbols and Abbreviations .................................................................................................. 3 2.1 Definitions ................................................................................................................................. 3 2.1.1 Symbols and Abbreviations ......................................................................................... 3
MS registration ......................................................................................................................................... 4 3.1 Information flows and functions ................................................................................................ 4 3.1.1 MS initiated registration .............................................................................................. 4
Network initiated USSD........................................................................................................................... 6 4.1 4.2 Handling of network initiated USSD ......................................................................................... 6 Information flows and functions ................................................................................................ 6 4.2.1 Information flows ........................................................................................................ 6 4.2.2 Invoking USSDoperation from the USSD Gateway .................................................... 9 4.2.3 USSD operations at the MSC .................................................................................... 10 4.2.4 USSD operations at the MS ....................................................................................... 10 Handoff .................................................................................................................................... 11
4.3 5
MS initiated USSD ................................................................................................................................. 12 5.1 5.2 Handling of an MS initiated USSD .......................................................................................... 12 Information flows and functions .............................................................................................. 12 5.2.1 Information flows ...................................................................................................... 12 5.2.1.1 MS initiated USSD Request ................................................................. 12 5.2.1.2 MS initiated USSD Request followed by an immediate USSD Release ................................................................................................. 14 5.2.1.3 MS initiated USSD Request after an intersystem handoff ................... 16 5.2.2 Handling of USSD Request at the MS....................................................................... 19 5.2.3 Handling of USSD request at the MSC ..................................................................... 19 5.2.4 Processing the USSD Request at the USSD Gateway ............................................... 20 Handoff .................................................................................................................................... 20
5.3 6
Protocol procedures ................................................................................................................................ 20
Table of Contents
X.S0065 v1.0
USSD
6.1 7
Requirements for mobile station and USSD Gateway ............................................................. 20
1 2
Network Signaling Protocol ................................................................................................................... 21 7.1 7.2 Editorial Conventions .............................................................................................................. 21 MAP operations ....................................................................................................................... 21 7.2.1 Operation definitions ................................................................................................. 21 7.2.1.1 SMSDeliveryForward ..........................................................................21 7.2.1.2 SMSDeliveryBackward ........................................................................23 MAP parameters ...................................................................................................................... 25 7.3.1 Parameter definitions ................................................................................................. 25 7.3.1.1 ServiceIndicatior ..................................................................................25 7.3.1.2 TransactionCapability ..........................................................................26 7.3.1.3 Profile ...................................................................................................29 7.3.1.4 USSDAddress.......................................................................................32 MAP signaling procedures ....................................................................................................... 35 7.4.1 Intersystem procedures .............................................................................................. 35 7.4.1.1 SMS delivery point-to-point .................................................................35 7.4.1.2 SMS delivery point-to-point for USSD exchange ................................42 7.4.1.3 SMSDeliveryForward ..........................................................................43 7.4.1.4 SMSDeliveryBackward ........................................................................45 7.4.1.5 SMS Notification..................................................................................47 7.4.1.6 SMS Request ........................................................................................48
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
7.3
7.4
Table of Contents
ii
USSD
X.S0065 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
TABLE OF FIGURES
Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Architecture for handling of USSD .................................................................................... 1 Information flow for MS initiated registration to MSC supporting USSD ......................... 4 Information flow for network initiated USSD session ........................................................ 7 Information flow for MS initiated USSD session ............................................................. 13 Information flow for MS initiated USSD session which is immediately released by the MS............................................................................................................................... 15 Information flow for MS initiated USSD session after handoff ....................................... 17
iii
Table of Figures
X.S0065 v1.0
USSD
TABLE OF TABLES
Table 1 HLR SMSRequest Response ............................................................................................ 53
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
Table of Tables
iv
USSD
X.S0065 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
FOREWORD
(This Foreword is not part of this Specification.) This document was prepared by the Third Generation Partnership 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 number as follows: X.S0065-000-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.
Foreword
X.S0065 v1.0
USSD
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
This page is intentionally left blank.
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
Foreword
vi
USSD
X.S0065 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
1.1
Introduction
This specification is for Unstructured Supplementary Service Data (USSD) Support.
Scope
The Unstructured Supplementary Service Data (USSD) mechanism enables a Mobile Station (MS) and Public Land Mobile 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 in the MS and the USSD Gateway (GW) via the MSC.
Application Server
Applications Interface MS USSD Client MSC USSD GW
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 selected. This document also defines architecture requirements (stage 2) and the protocol details (stage 3) of the USSD.
1.2
Requirements 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, 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 the document. Can and cannot are used for statements of possibility and capability, whether material, physical or causal.
1.1 Scope
1 Introduction
X.S0065 v1.0
USSD
1.3
Normative References
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.
1 2 3 4 5 6 7
[A.S0013] [C.S0105]
3GPP2: A.S0013-D v3.0; 3GPP2 Interoperability Specification (IOS) for cdma2000 Access Network Interfaces Part 3 Features; May 2011. 3GPP2: C.P0105 v0.02, Unstructured Supplementary Service Data (USSD) Service Options for Spread Spectrum Systems: Service Options 78 and 79 ; April 2012. NOTE: The above document is a work progress and should not be referenced unless and until it is approved and published. Until such time as this Editors Note is removed, the inclusion of the above document is for informational purposes only.
8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
[X.S0002] [X.S0004-520] [X.S0004-540] [X.S0004-550] [X.S0004-551] [X.S0004-630] [X.S0004-640] [X.S0004-641] [X.S0004-691] [TS24.080] [TS22.030] [TS23.090] [TS24.010]
3GPP2: X.S0002-0 v2.0, MAP Location Services Enhancements; May 2006. 3GPP2: X.S0004-520-E v2.0, Mobile Application Part (MAP) TCAP Application Signaling Protocols; July 2007. 3GPP2: X.S0004-540-E v2.0, Mobile Application Part (MAP) Operations Signaling Protocols; July 2007. 3GPP2: X.S0004-550-E v4.0, Mobile Application Part (MAP) Parameters Signaling Protocols; January 2010. 3GPP2: X.S0004-551-E v1.0, Mobile Application Part (MAP) Parameter Type Signaling Protocols; March 2004. 3GPP2: X.S0004-630-E v3.0, Mobile Application Part (MAP) Basic Call Processing; April 2008. 3GPP2: X.S0004-640-E v2.0, Mobile Application Part (MAP) Intersystem Operations; July 2007. 3GPP2: X.S0004-641-E v2.0, Mobile Application Part (MAP) SMS; July 2007. 3GPP2: X.S0004-691-E v3.0, Mobile Application Part (MAP) Annexes for the 6XX Series; July 2007. 3GPP: TS 24.080, Mobile radio interface layer 3 supplementary services specification; format and encoding (Release 10); March 2011. 3GPP: TS 22.030, Man-Machine Interface (MMI) of the User Equipment (UE) (Release 10); March 2011. 3GPP: TS 23.090, Unstructured Supplementary Service Data (USSD); Stage 2 (Release 10); March 2011. 3GPP: TS 24.010; 3GPP Mobile radio interface layer 3 supplementary services specification; General aspects (Release 10); June 2011.
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
1.4
Informative References
None
53 54 55 56 57 58 59 60
1 Introduction
1.3 Normative References
USSD
X.S0065 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
2
2.1
Definitions, Symbols and Abbreviations

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 a USSD Notify. USSD Notify A notification sent by a USSD GW to a USSD Client in the MS. The notification conveys information that the USSD Client may display to the user. USSD operation A USSD Request or a USSD Notify, see [TS23.090]. USSD session A set of USSD messages that all share the same session identifier. USSD Release A message that ends the USSD session. This message is equivalent to the RELEASE COMPLETE, see [TS24.080].
2.1.1
Symbols and Abbreviations

MMI USSD USSD GW ADDS DBM IOS Man Machine Interface Unstructured Supplementary Service Data USSD Gateway Application Data Delivery Service Data Burst Message Interoperability Specification
2.1 Definitions
2 Definitions, Symbols and Abbreviations
X.S0065 v1.0
USSD
3
3.1
3.1.1
MS registration
Information flows and functions
MS initiated registration
The information flow in Figure 2 is for a mobile initiated registration on a Serving MSC that supports USSD functionality.
Serving Network Home Network
2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18
MS
BS
MSC
HLR/ AC
19 20 21 22 23
AIR: Registration Message 1 IOS: LOCATION UPDATING REQUEST 2 MAP: AUTHREQ (MIN, AUTHR, RAND ) 3 MAP: authreq 4 MAP: REGNOT (MIN) 5 MAP: regnot (VLR Profile ) 6 IOS: LOCATION UPDATING ACCEPT 7 AIR: Registration Accepted Order 8
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
Figure 2
Information flow for MS initiated registration to MSC supporting USSD 1. The MS initiates a registration operation by sending the Registration Message to the BS. On reception of the Registration Message, the BS constructs the Location Updating Request message, places it in the Complete Layer 3 Information message, and sends it to the MSC.
49 50 51 52 53 54
2.
55 56 57 58 59 60
3 MS registration
3.1 Information flows and functions
USSD
X.S0065 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
3.
If authentication is required, the Serving MSC sends an AuthenticationRequest INVOKE to the HLR/AC with the CDMA authentication data provided by the MS (i.e., sent by the BS in the Location Updating Request message). If the Serving MSC has sent an AuthenticationRequest INVOKE in Step 3, the AC returns a response If authentication succeeds, the scenario continues. If authentication fails, the Serving MSC will signal a registration denied toward the MS. The Serving MSC constructs a RegistrationNotification message. The Serving MSC sets the USSD bit in the TransactionCapability parameter (see Section 7.3.1.2) to indicate to the HLR that the Serving MSC supports USSD functionality. The Serving MSC sends the RegistrationNotification INVOKE to the HLR. The HLR sends a RegistrationNotification RETURN RESULT to the Serving MSC. If the HLR determines that authorization can be granted to the MS the RegistrationNotification RETURN RESULT will contain the Profile parameter. If the Profile parameter contains a USSDAddress parameter (see Section 7.3.1.3) then the MS has subscribed to USSD services. If the HLR determines that authorization cannot be granted to the MS the RegistrationNotification RETURN RESULT will contain the AUTHDEN parameter.
4.
5.
6.
7.
The MSC sends the Location Updating Accept message to the BS to indicate that the Location Updating Request message has been processed. The BS transmits a Registration Accepted Order to the MS to acknowledge the registration explicitly.
8.
3 MS registration
X.S0065 v1.0
USSD
4
4.1
Network initiated USSD

Handling of network initiated USSD
The USSD GW may initiate a USSD operation (request or notification) to the MS at any time. The USSD operation may be a USSD request requesting the MS to provide information or may be a USSD notification to provide information to the MS (without a USSD response expected). The USSD operation may include a USSD string, an alphabet indicator and a language indicator. The USSD operation may contain other data when providing information for the MS or requesting information from the MS.
1 2 3 4 5 6 7 8 9 10 11 12 13 14
4.2
4.2.1

Information flows
The information flow for a network initiated USSD session is shown in Figure 3. The information flow assumes that a traffic channel is established at the time the network initiated the USSD request.
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
4 Network initiated USSD
4.1 Handling of network initiated USSD
USSD
X.S0065 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
Serving Network
Home Network
MS
BS
MSC
HLR
USSD GW
MAP: SMSREQUEST (MDN or IMSI) 1 MAP: smsrequest(SMS_Address ) 2 MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request or USSD Notify) ) 3 TRAFFIC CHANNEL ESTABLISHED 4 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 5 AIR: USSD Data Burst Message (USSD Request or USSD Notify) SMT AIR: Layer 2 Ack 7 IOS: ADDS DELIVER ACK 8 MAP: smdpp 9 AIR: USSD Data Burst Message (USSD Response) 10 AIR: Layer 2 Ack 11 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) MAP: SMDPP (SMS_BearData=USSD DBM (USSD Response) ) SMT 12 13 6
MAP: smdpp
14
MAP: SMDPP (SMS_BearData=USSD DBM (USSD Release) ) 15 IOS: ADDS DELIVER (ADDS User Data=USSD Release) 16 AIR: USSD Data Burst Message (USSD Release) 17 SMT AIR: Layer 2 Ack IOS: ADDS DELIVER ACK MAP: smdpp 18
19
20
TRAFFIC CHANNEL TORN DOWN 21
Figure 3
Information flow for network initiated USSD session
X.S0065 v1.0
USSD
1. 2. 3.
If the USSD GW does not have the address of the MSC currently serving the MS, it sends a SMSREQ toward the HLR. If the HLR has the current address of the indicated MS-based USSD Client, the HLR sends a smsreq to the requesting USSD GW. The USSD GW constructs a MAP SMDPP INVOKE message. The SMS_BearData parameter contains a USSD Request or a USSD Notify. The USSD Request or the USSD Notify is formatted as defined in [C.S0105]. The SMDPP INVOKE is sent to the MSC. The USSD Gateway starts timer SMT. Upon receipt of the SMDPP INVOKE message, the MSC determines if the subscriber is authorized to use USSD services by examining the subscriber profile. If the subscriber profile contains a USSDAddress parameter, the MSC caches the address which originated the SMDPP INVOKE until the USSD session is complete. If the MS is not on a traffic channel, the MSC pages the MS to establish a traffic channel. If the subscriber is not authorized, the MSC sends a cause code in the SMDPP (see step 9).
1 2 3 4 5 6 7 8 9 10 11
4.
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
5.
The MSC constructs an IOS ADDS Deliver message. The Data Burst Type of the ADDS User Data Informational Element is set to indicate USSD. The SMS_BearData parameter of the MAP SMDPP INVOKE is used to create the Application Data Message of the ADDS User Data Informational Element. The MSC sends the IOS ADDS Deliver message to the BS. The BS transmits the USSD Request message or USSD Notify message over the forward traffic channel. If the BS does not receive an acknowledgment after transmitting the USSD data burst message, it retransmits the message. The maximum number of the retransmissions is configurable. When the BS reaches the maximum number of retransmissions, the BS declares a Layer 2 Ack failure and initiates call clearing. The MS acknowledges receipt of the data burst message on the traffic channel with a Layer 2 Ack. If the MSC has requested a response by including the tag element in the ADDS Deliver message, the BS replies with an ADDS Deliver Ack message when it has received an acknowledgment from the MS that the USSD Request message or USSD Notify message was delivered. If a Tag element was included in the ADDS Deliver message, the BS shall include the Tag element in the ADDS Deliver Ack message, and set it to the same value as that received in the ADDS Deliver message. The MSC acknowledges the MAP SMDPP INVOKE (step 3) by sending an SMDPP RETURN RESULT to the USSD GW. Upon receiving the MAP SMDPP RETURN RESULT, the USSD GW stops timer SMT.
6.
7. 8.
9.
10. The BS receives a traffic channel data burst message from an MS on the traffic channel with a burst type indicating USSD. The traffic channel data burst message can contain either a USSD Response message or a USSD Release message. The USSD DBM is constructed as defined in [C.S0105]. If the MS sends a USSD Release, steps 15 through 20 are ignored. 11. If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel. 12. The BS sends an ADDS Deliver message to the MSC. The Application Data Message of the ADDS User Data Informational Element contains the USSD DBM received from the MS. The Data Burst Type of the ADDS User Data Informational Element is set to USSD.
52 53 54 55 56 57 58 59 60
USSD
X.S0065 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
13. The MSC constructs a MAP SMDPP INVOKE. The SMS_BearData is constructed from the ADDS User Part in the ADDS Deliver message containing the USSD response message as defined in [TS24.080]. The SMDPP INVOKE is sent to the cached address, see step 4.. The MSC starts timer SMT. 14. The USSD GW acknowledges the MAP SMDPP INVOKE (step 13) by sending an SMDPP RETURN RESULT to the MSC. Upon receiving the MAP SMDPP RETURN RESULT the MSC stops timer SMT. NOTE: The USSD GW can send several USSD Request messages which results in multiple transactions. In that case, steps 3 through 14 will be repeated for each USSD Request message sent by the USSD GW. NOTE: If the USSD GW sends a USSD Notify (see step 3) then steps 4 through step 14 will not be repeated. 15. To terminate the USSD transaction, the USSD GW constructs a MAP SMDPP INVOKE. The SMS_BearData contains a USSD Release. The SMDPP INVOKE is sent to the MSC. The USSD GW starts timer SMT. 16. Upon receipt of the SMDPP INVOKE, the MSC constructs an IOS ADDS Deliver message. The Data Burst Type of the ADDS User Data Informational Element is set to the USSD. The SMS_BearData parameter of the MAP SMDPP INVOKE is used to create the Application Data Message of the ADDS User Data Informational Element. The MSC sends the IOS ADDS Deliver message to the BS. 17. The BS transmits the USSD Release message over the forward traffic channel. If the BS does not receive an acknowledgment after transmitting the USSD data burst message, it shall retransmit the message. The maximum number of the retransmissions is configurable by the BS manufacturer. When the BS reaches the maximum number of retransmissions, it declares a Layer 2 Ack failure and initiate call clearing. 18. The MS acknowledges delivery of the data burst message on the traffic channel with a Layer 2 Ack. 19. If the MSC has requested a response by including the tag element in the ADDS Deliver message, the BS replies with an ADDS Deliver Ack message when it has received an acknowledgment from the MS that the USSD Release was delivered. If a Tag element was included in the ADDS Deliver message, the BS includes the Tag element in the ADDS Deliver Ack message, and set it to the same value as that received in the ADDS Deliver message. 20. The MSC acknowledges the MAP SMDPP INVOKE message (step 15) by sending an SMDPP RETURN RESULT to the USSD GW. Upon receiving the MAP SMDPP RETURN RESULT, the USSD GW stops timer SMT. 21. Anytime after step 17, the MS tears down the traffic channel.
4.2.2
Invoking USSDoperation from the USSD Gateway

If the USSD GW does not know the MSC address for which the USSD subscriber is currently registered, the USSD GW sends a location request to the HLR. The HLR response contains information as to whether the subscriber is registered and if registered what MSC is presently serving the USSD subscriber. If the subscriber is registered, the USSD GW may initiate a USSD session by sending a USSD operation (i.e., USSD Request or a USSD Notify) to the MSC serving the USSD
X.S0065 v1.0
USSD
subscriber starting an application timer. If a USSD Request was sent to the USSD subscriber, the USSD GW shall wait for a USSD Response. If the application timer expires before a USSD Response has been received, the USSD GW shallend the USSD session. If the USSD GW receives a USSD response, the USSD GW may end the USSD session or may use the same USSD session to send further USSD messages to the USSD subscriber. The USSD GW may initiate another USSD session with the USSD subscriber after an application dependent time interval has expired. The USSD GW shall end the first USSD session with the USSD subscriber before initiating a new USSD session. If the USSD subscriber ends the USSD session (e.g., the user ends the application), the USSD GW shall inform the application server and shall end the USSD session with the USSD subscriber.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
4.2.3
USSD operations at the MSC

Upon receipt of a USSD operation (i.e., a USSD Request or a USSD Notify) from the USSD GW, the MSC shall determine if the USSD subscriber addressed in the USSD operation is authorized to receive USSD services. If the USSD subscriber is authorized to receive USSD services, the MSC shall send the USSD operation to the MS. The MSC shall not modify the USSD application data. Upon receipt of a USSD Release the MSC shall send the USSD Release towards the MS.
21 22 23 24 25 26 27 28 29 30 31
4.2.4
USSD operations at the MS

An MS may receive a USSD operation (i.e., a USSD Request or a USSD Notify) from the USSD GW at any time. If a USSD session is active and the MS receives a USSD operation associated with a new USSD session, the MS shall reject the USSD operation. If a USSD operation requires MMI and MMI is not possible, the MS shall reject the USSD operation. If a USSD operation indicates an alphabet that is not supported by the MS, the MS shall reject the USSD operation and may inform the USSD GW of the alphabets supported by the MS, [TS24.080]. Upon receipt of a USSD operation, the USSD client in the MS shall determine whether the USSD operation is application mode or MMI mode as defined in [TS22.030]. If a USSD operation is MMI mode and the USSD operation is a USSD Request the USSD Client shall start timer TRooz . The USSD Client shall display the information and await an MMI response. Upon receipt of an MMI response, the MS may send a USSD Response to the USSD GW or terminate the USSD session by sending a USSD Release to the USSD GW. If timer TRooz expires, the USSD client in the MS shall terminate the USSD session by sending a USSD Release to the USSD GW.
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
10
USSD
X.S0065 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
If the USSD operation is a USSD Notify and the USSD operation is MMI mode, the USSD client in the MS shall display the information to the user. The USSD Client shall send a USSD Response back to the USSD GW. If a USSD operation is application mode and the USSD operation is a USSD Request, the USSD client shall pass the information to the addressed application client within the MS. The USSD client shall start timer T MB. The USSD Client awaits a response from the addressed application client. Upon receipt of an application client response, the USSD client may send a USSD response to the USSD GW or terminate the USSD session by sending a USSD Release to the USSD GW. If timer T MB expires, the USSD client in the MS shall terminate the USSD session by sending a USSD Release to the USSD GW. If a USSD operation is a USSD Notify and the USSD operation is application mode, the USSD client in the MS shall pass the information to the addressed application client within the MS. The USSD Client shall send a USSD Response back to the USSD GW. If the USSD client has sent a USSD Response within a USSD session, the USSD client in the MS shall wait for a USSD operation or a USSD Release from the USSD GW. The USSD client shall not terminate a USSD session if a USSD Response has been sent to the USSD GW. The USSD client shall wait for the USSD GW to terminate the USSD session. The USSD client shall handle successive USSD operations within the same USSD session.
4.3
Handoff
Inter-MSC handoff shall not have any impact on the USSD services.
4.3 Handoff
11
X.S0065 v1.0
USSD
5
5.1
MS initiated USSD
Handling of an MS initiated USSD
The USSD client in the MS may send a USSD request to an application server at any time. The application server may end the session or send a USSD request or USSD notification. Upon receipt of a USSD operation within the same transaction, the USSD client shall process the operation and send an appropriate response (e.g. USSD Response or Release). The USSD message may contain the USSD string, an alphabet indicator and a language indicator or may contain other data.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
5.2
5.2.1

Information flows
MS initiated USSD Request
The information flow for an MS initiated USSD session is shown in Figure 4. The information flow assumes that a traffic channel is established at the time of the MS initiated the USSD Request.
18 19 20 21 22 23
5.2.1.1
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
5 MS initiated USSD
12
5.1 Handling of an MS initiated USSD
USSD
X.S0065 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
Serving Network
Home Network
MS
BS
MSC
HLR
USSD GW
TRAFFIC CHANNEL ESTABLISHED 1 AIR: USSD Data Burst Message (USSD Request) 2 AIR: Layer 2 Ack 3 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 4 MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request) ) 5 MAP: smdpp SMT 6 MAP: SMDPP (SMS_BearData=USSD DBM (USSD Release) ) 7 IOS: ADDS DELIVER ACK (ADDS User Data=USSD DBM) 8 AIR: USSD Data Burst Message (USSD Release) 9 AIR: Layer 2 Ack SMT 10 IOS: ADDS DELIVER ACK 11 MAP: smdpp 12 TRAFFIC CHANNEL TORN DOWN 13
Figure 4 1. 2.
Information flow for MS initiated USSD session
If the MS is not on a traffic channel, the MS sets up traffic channel as defined in [A.S0013]. The BS receives a traffic channel data burst message from an MS on the traffic channel with a burst type indicating USSD. The USSD DBM is constructed as defined in [C.S0105]. If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel. The BS sends an ADDS Deliver message to the MSC. The Application Data Message of the ADDS User Data Informational Element contains the USSD DBM received from the MS. The Data Burst Type of the ADDS User Data Informational Element is set to indicate USSD. The MSC determines if the MS is authorized to use USSD services by examining the subscriber profile. If the subscriber profile contains a USSDAddress parameter, the MSC constructs an SMDPP INVOKE. The SMS_BearData is constructed from the ADDS User Part in the ADDS Deliver message. The SMDPP INVOKE is sent to the USSD Address
3. 4.
5.
13
5 MS initiated USSD
X.S0065 v1.0
USSD
identified by the USSD Address parameter in the Subscriber Profile. The MSC starts timer SMT. If the subscriber is not authorized to use USSD services the MSC rejects the USSD session setup. NOTE: There is no error message that is sent back to the MS to inform the USSD client that the USSD Request was rejected by the MSC. 6. The USSD GW caches the MSC address until the USSD session is complete. The USSD GW acknowledges the SMDPP INVOKE (step 5) by sending an SMDPP RETURN RESULT to the MSC. Upon receiving the SMDPP RETURN RESULT, the MSC stops timer SMT. The SMDPP RETURN RESULT can contain an error cause code indicating that the USSD GW has rejected the USSD Request. NOTE: The USSD GW can request further information from the USSD client resulting in the USSD GW sending one or more USSD Requests within the same USSD session. 7. The USSD GW constructs an SMDPP INVOKE. The SMS_BearData parameter contains a USSD Release. The USSD Release is constructed as defined in [C.S0105]. The SMDPP INVOKE is sent to the MSC. The USSD GW starts timer SMT. The MSC caches the address which originated the SMDPP INVOKE. The MSC constructs an IOS ADDS Deliver message. The Data Burst Type of the ADDS User Data Informational Element is set to indicate USSD. The SMS_BearData parameter of the SMDPP INVOKE is used to create the Application Data Message of the ADDS User Data Informational Element. The MSC sends the IOS ADDS Deliver message to the BS. The BS transmits the USSD message over the forward traffic channel to the MS. If the BS does not receive an acknowledgment after transmitting the USSD data burst message, it retransmits the message. The maximum number of the retransmissions is configurable. When the BS reaches the maximum number of retransmissions, the BS declares a Layer 2 Ack failure and initiates call clearing.
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
8.
9.
10. The MS acknowledges delivery of the data burst message on the traffic channel with a Layer 2 Ack. 11. If the MSC has requested a response by including the tag element in the ADDS Deliver message, the BS replies with an ADDS Deliver Ack message when it has received acknowledgment from the MS that the message was delivered. If a Tag element was included in the ADDS Deliver message, the BS shall include the Tag element in the ADDS Deliver Ack message, and set it to the same value as that received in the ADDS Deliver message. 12. The MSC acknowledges the SMDPP INVOKE (step 7) by sending an SMDPP RETURN RESULT to the address which originated the SMDPP INVOKE. Upon receiving the SMDPP RETURN RESULT, the USSD GW stops timer SMT. 13. The MS releases the traffic channel. See the Call Clear via Clear Request (MS Initiated) informational flow in [A.S0013].
5.2.1.2
MS initiated USSD Request followed by an immediate USSD Release

The information flow in Figure 5 is an example of when an MS initiates a USSD session and immediately sends a USSD Release before the USSD Request is acknowledged by the USSD Gateway. The information flow assumes that a traffic channel is established at the time of the MS initiated the USSD session.
49 50 51 52 53 54 55 56 57 58 59 60
5 MS initiated USSD
14
USSD
X.S0065 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
Serving Network
Home Network
MS
BS
MSC
HLR
USSD GW
TRAFFIC CHANNEL ESTABLISHED 1 AIR: USSD Data Burst Message (USSD Request) 2 AIR: Layer 2 Ack 3 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 4 MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request) ) 5 MAP: smdpp SMT 6 AIR: USSD Data Burst Message (USSD Release) 7 AIR: Layer 2 Ack 8 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) MAP: SMDPP (SMS_BearData=USSD DBM (USSD Release) ) 10 MAP: smdpp SMT 11 TRAFFIC CHANNEL TORN DOWN 12
Figure 5
Information flow for MS initiated USSD session which is immediately released by the MS 1. 2. If the MS is not on a traffic channel, the MS sets up traffic channel as defined in [A.S0013]. The BS receives a traffic channel data burst message from an MS on the traffic channel with a burst type indicating USSD. The USSD DBM is constructed as defined in [C.S0105]. If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel. The BS sends an ADDS Deliver message to the MSC. The Application Data Message of the ADDS User Data Informational Element contains the USSD DBM received from the MS. The Data Burst Type of the ADDS User Data Informational Element is set to indicate USSD. The MSC determines if the MS is authorized to use USSD services by examining the subscriber profile. If the subscriber profile contains a USSDAddress parameter, the MSC constructs an SMDPP INVOKE. The SMS_BearData is constructed from the ADDS User Part in the ADDS Deliver message. The SMDPP INVOKE is sent to the USSD Address identified by the USSDAddress parameter in the Subscriber Profile. The MSC starts
3. 4.
5.
15
5 MS initiated USSD
X.S0065 v1.0
USSD
timer SMT. If the subscriber is not authorized to use USSD services, the MSC rejects the USSD session setup. 6. 7. NOTE: There is no error message that is sent back to the MS to inform the USSD client that the USSD Request was rejected by the MSC. The USSD GW caches the MSC address until the USSD session is complete. The USSD GW acknowledges the SMDPP INVOKE (step 5) by sending an SMDPP RETURN RESULT to the MSC. Upon receiving the SMDPP RETURN RESULT, the MSC stops timer SMT. The SMDPP RETURN RESULT can contain an error cause code indicating that the USSD GW has rejected the USSD Request. The BS receives a traffic channel data burst message from an MS on the traffic channel with a burst type indicating USSD and containing a USSD Release. The USSD Release DBM is constructed as defined in [C.S0105]. If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel.
1 2 3 4 5 6 7 8 9 10 11 12
8.
13 14 15 16
9.
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36
10. The BS sends an ADDS Deliver message to the MSC. The Application Data Message of the ADDS User Data Informational Element contains the USSD DBM received from the MS. The Data Burst Type of the ADDS User Data Informational Element is set to indicate USSD. 11. The MSC constructs a MAP SMDPP INVOKE. The SMS_BearData is constructed from the ADDS User Part in the ADDS Deliver message containing the USSD Release message as defined in [TS24.080]. The SMDPP INVOKE is sent to the address given in the USSDAddress parameter (e.g., the USSD GW address) of the Subscriber Profile. The MSC starts timer SMT. 12. The USSD GW acknowledges the MAP SMDPP INVOKE (step 10) by sending an SMDPP RETURN RESULT to the MSC. Upon receiving the MAP SMDPP RETURN RESULT, the MSC stops timer SMT. 13. The MS releases the traffic channel. See the Call Clear via Clear Request (MS Initiated) informational flow in [A.S0013].
5.2.1.3
MS initiated USSD Request after an intersystem handoff

The information flow for a mobile initiated USSD Request after a voice call handoff is shown in Figure 6. The information flow illustrates the use of the SMSDeliveryBack and SMSDeliveryForward operations for passing USSD information between the Serving MSC and the Anchor MSC after a voice call handoff. It is assumed that there is a Tandem MSC between the Anchor MSC and the Serving MSC (e.g., the MS has handed off twice since establishing the voice call on the Anchor MSC).
37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
5 MS initiated USSD
16
USSD
X.S0065 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
Serving Network
Tandem Network
Anchor Network
MS
BS
Serving MSC
Tandem MSC
Anchor MSC
USSD GW
TRAFFIC CHANNEL ESTABLISHED 1 AIR: USSD Data Burst Message (USSD Request) 2 AIR: Layer 2 Ack 3 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 4 MAP: SMDBACK (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) ) 5 MAP: SMDBACK (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) ) MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request) ) 7 SMT MAP: smdback (ACK) 9 MAP: smdback (ACK) 10 MAP: SMDPP (SMS_BearData=USSD DBM (USSD Response) ) 11 MAP: SMDFWD (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) ) 12 MAP: SMDFWD (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) ) 13 IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 14 AIR: USSD Data Burst Message (USSD Response) 15 AIR: Layer 2 Ack IOS: ADDS DELIVER ACK 17 MAP: smdfwd (ACK) 18 MAP: smdfwd (ACK) 19 MAP: smdpp 20 SMT 16 MAP: smdpp 8 6
Figure 6 1. 2.
Information flow for MS initiated USSD session after handoff
MS is on a voice call and the traffic channel is established. The BS receives a traffic channel data burst message from the MS on the traffic channel with a burst type indicating USSD. The USSD DBM is constructed as defined in [C.S0105]. If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel. The BS sends an ADDS Deliver message to the Serving MSC. The Application Data Message of the ADDS User Data Informational Element contains the USSD DBM
3. 4.
17
5 MS initiated USSD
X.S0065 v1.0
USSD
received from the MS. The Data Burst Type of the ADDS User Data Informational Element is set to USSD. 5. The Serving MSC constructs an SMDBACK INVOKE (see Section 7.2.1.2). The Serving MSC sets the ServiceIndicator to the USSD value. The SMS_BearData is constructed from the ADDS User Data Informational Element in the ADDS Deliver message. The SMDBACK INVOKE is sent towards the Anchor MSC, via a Tandem MSC. The Tandem MSC forwards the SMDBACK INVOKE to the Anchor MSC. The Anchor MSC examines the subscriber profile to determine if the MS is authorized to use USSD services. If the subscriber profile contains a USSDAddress parameter, the Anchor MSC constructs a SMDPP INVOKE. The SMS_BearData is constructed from the SMS_BearData received in the SMDBACK INVOKE. The SMDPP INVOKE is sent to the USSD Address identified by the USSDAddress parameter in the Subscriber Profile. The Anchor MSC starts timer SMT. If the subscriber is not authorized to use USSD services, the Anchor MSC rejects the USSD session setup and sends a SMDBACK RETURN RESULT indicating a negative acknowledgment of the SMDBACK operation invocation via the inclusion of a SMS_CauseCode parameter to the Serving MSC. NOTE: There is no error message that is sent back from the Serving MSC to the MS to inform the USSD client that the USSD Request was rejected by the Anchor MSC. 8. The USSD GW caches the Anchor MSC address until the USSD session is complete. The USSD GW acknowledges the SMDPP INVOKE (step 7) by sending an SMDPP RETURN RESULT to the Anchor MSC. Upon receiving the SMDPP RETURN RESULT, the Anchor MSC stops timer SMT. The SMDPP RETURN RESULT can contain an error cause code indicating that the USSD GW has rejected the USSD Request. NOTE: The USSD GW can request further information from the USSD client resulting in the USSD GW sending one or more USSD Requests within the same USSD session. 9. The Anchor MSC constructs a SMDBACK RETURN RESULT indicating positive acknowledgment of the operation invocation and sends it to the Tandem MSC.
1 2 3 4 5 6 7 8
6. 7.
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
10. The Tandem MSC forwards the SMDBACK RETURN RESULT to the Serving MSC. 11. The USSD GW constructs a SMDPP INVOKE. The SMS_BearData parameter contains a USSD Response. The USSD Response is constructed as defined in [C.S0105]. The SMDPP INVOKE is sent to the Anchor MSC. The USSD GW starts timer SMT. 12. The Anchor MSC caches the address which originated the SMDPP INVOKE. The Anchor MSC constructs an SMDFWD INVOKE (see Section 7.2.1.1. The Anchor MSC sets the ServiceIndicator to the USSD value. The SMS_BearData is constructed from the SMS_BearData received in the SMDPP INVOKE. The SMDBACK INVOKE is sent towards the Anchor MSC, via a Tandem MSC. 13. The Tandem MSC forwards the SMDFWD INVOKE to the Serving MSC. 14. The Serving MSC constructs an IOS ADDS Deliver message. The Data Burst Type of the ADDS User Data Informational Element is set to USSD. The SMS_BearData parameter of the SMDFWD INVOKE is used to create the Application Data Message of the ADDS User Data Informational Element. The Serving MSC sends the IOS ADDS Deliver message to the BS. 15. The BS transmits the USSD message over the forward traffic channel to the MS. If the BS does not receive an acknowledgment after transmitting the USSD data burst message,
38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
5 MS initiated USSD
18
USSD
X.S0065 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
it retransmits the message. The maximum number of the retransmissions is configurable the BS manufacturer. When the BS reaches the maximum number of retransmissions, the BS declares a Layer 2 Ack failure and initiate call clearing. 16. The MS acknowledges delivery of the data burst message on the traffic channel with a Layer 2 Ack. 17. If the Serving MSC has requested a response by including the tag element in the ADDS Deliver message, the BS replies with an ADDS Deliver Ack message when it has received acknowledgment from the MS that the message was delivered. If a Tag element was included in the ADDS Deliver message, the BS shall include the Tag element in the ADDS Deliver Ack message, and set it to the same value as that received in the ADDS Deliver message. 18. The Serving MSC acknowledges the SMDFWD INVOKE (step 13) by sending an SMDFWD RETURN RESULT sent towards the Anchor MSC, via a Tandem MSC. 19. The Tandem MSC forwards the SMDFWD RETURN RESULT to the Anchor MSC. 20. The Anchor MSC acknowledges the SMDPP INVOKE (step 11) by sending an SMDPP RETURN RESULT to the address which originated the SMDPP INVOKE. Upon receiving the SMDPP RETURN RESULT, the USSD GW stops timer SMT.
5.2.2
Handling of USSD Request at the MS

When the user or an application in the MS is to initiate a USSD Request, the MS initiates a USSD session toward the USSD GW by constructing a USSD DBM as defined in [C.S0105]. If the MS is not assigned to a traffic channel, the MS shall establish a traffic channel as defined in [A.S0013]. After sending a USSD Request, the USSD client in the MS shall wait for a USSD operation from the USSD GW. If the USSD Response is MMI mode, the USSD client shall display the USSD Response to the user. If the USSD Response is application mode the USSD client shall relay the USSD Response to the appropriate application in the MS. The MS may receive a USSD Request or a USSD Notify from the USSD GW within the same USSD session while awaiting a USSD Response to the mobile initiated USSD Request. Upon receipt of an application mode USSD Request or USSD Notify within the same USSD session, the USSD client shall pass the information to the addressed application client within the MS. Upon receipt of an MMI mode USSD Request or USSD Notify within the same USSD session, the USSD client shall display the information and await an MMI response. If a USSD session is active and the MS receives a user or application request for a USSD Request for a new USSD session, the MS shall reject the user or application request. If a USSD session is active and the MS receives a USSD operation from the USSD GW associated with a new USSD session, the MS shall reject the USSD operation.
5.2.3
Handling of USSD request at the MSC

Upon receipt of a USSD Request from the USSD client in the MS, the MSC shall determine if the subscriber is authorized for USSD services. If the subscriber is authorized for USSD services the MSC shall send the USSD Request to the USSD Address identified by the USSDAddress parameter in the Subscriber Profile. The MSC shall not modify the USSD application data. If the subscriber is not authorized for USSD services the MSC rejects the USSD Request.
19
5 MS initiated USSD
X.S0065 v1.0
USSD
5.2.4
Processing the USSD Request at the USSD Gateway

The USSD GW may receive a USSD Request from a USSD client in the MS at any time. The USSD GW shall route the USSD Request to the appropriate application server. If the application server requires more information from the USSD client, the application server may request the USSD GW to send a USSD Request within the same USSD session to the USSD client. Upon completion of the session by the application server, the USSD GW shall send a USSD Response to the USSD client and shall release the USSD session.
1 2 3 4 5 6 7 8 9 10 11 12 13
5.3
Handoff
Inter-MSC handoff shall not have any impact on the USSD services.
14 15 16 17 18
6
6.1
Protocol procedures
Requirements for mobile station and USSD Gateway
The USSD GW and the MS shall support all the message types for the call independent supplementary services control, FACILITY, REGISTER, and RELEASE COMPLETE according to [TS24.080]. The USSD GW and the MS shall support all the USSD call related and USSD call independent operation types defined in [TS24.080]. According to [TS24.010], call related operations are supplementary service procedures occuring during the active state of a call while call independent operations occur independent of the active state of a call. The USSD GW and the MS shall support all the USSD related error responses defined in [TS24.080] and shall implement all the USSD operation types and USSD error responses defined in [TS24.080]. The USSD GW and the MS shall support all the USSD data types as defined in [TS24.080]. The USSD messages shall be embedded in the appropriate component (Invoke, Return Result or Return Error) of the Facility information element of the appropriate message (REGISTER, FACILITY or RELEASE COMPLETE), as specified in [TS24.090].
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
5 MS initiated USSD
20
5.3 Handoff
USSD
X.S0065 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
7
7.1
Network Signaling Protocol

Editorial Conventions
The following editorial conventions are used for Section 7: underline: is addition to pre-existing text from other specifications. cross out: is deleted text to pre-existing text from other specifications.
7.2
7.2.1
MAP operations
Operation definitions
SMSDeliveryForward
Note: This operation definition is a modification of the SMSDeliveryForward operation definition in [X.S0004-540]. The SMSDeliveryForward (SMDFWD) operation is a general purpose operation that is used to convey an MS-terminated short message or in general any other information or encapsulated data to the Serving MSC after handoff. The following table lists the valid combinations of invoking and responding FEs.
INVOKING FE Case 1 Case 2 Case 3 Case 4 Anchor MSC Anchor MSC Tandem MSC Tandem MSC RESPONDING FE Serving MSC Tandem MSC Tandem MSC Serving MSC
7.2.1.1
The SMSDeliveryForward operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
SMSDeliveryForward INVOKE Parameters Field Identifier Length Contents InterMSCCircuitID SMS_BearerData M M Value SET [NATIONAL 18] variable octets Type M M
Timer: SFT Reference [X.S0004520] 1.3.2.1 [X.S0004520] 1.3.2.1 Notes
[X.S0004540] 2.129 [X.S0004540] 2.233
7.1 Editorial Conventions
21
7 Network Signaling Protocol
X.S0065 v1.0
USSD
SMS_TeleserviceIdentifier ElectronicSerialNumber IMSI MobileIdentificationNumber ServiceIndicator SMS_ChargeIndicator SMS_OriginalDestinationAddress SMS_OriginalDestinationSubaddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubaddress SMS_OriginatingAddress
M O O O O O O O O O O
[X.S0004540] 2.246 [X.S0004540] 2.112 [X.S0004540] 2.127 [X.S0004540] 2.140 6.3.1.1 [X.S0004540] 2.235 [X.S0004540] 2.240 [X.S0004540] 2.241 [X.S0004540] 2.242 [X.S0004540] 2.243 [X.S0004540] 2.244 b h a, h i c e b f b g
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
Notes: a. b. c. d. e. f. g. h. i. Include to identify the destination MS. Include if applicable. Include if applicable. If not received, charge message originator. Intentionally left for future modifications. Include to identify the SME to which the short message is destined (e.g., the MDN, for termination to the MS-based SME). Include to identify the SME from which the short message originated (e.g., the MDN, if originated by an MS-based SME). Include if the MC address may be sent to the MS. Include if available. At least one of these parameters should be present. Include for CDMA USSD. When ServiceIndicator is included, the length of the SMS_TeleserviceIdentifier is set to 0.
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
The SMSDeliveryForward operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
SMSDeliveryForward RETURN RESULT Field Identifier Value SET [NATIONAL 18] Type M Reference [X.S0004520]1.3.2.2 Notes
49 50 51 52 53 54 55 56 57 58 59 60
22
7.2 MAP operations
USSD
X.S0065 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
Length Contents
variable octets
[X.S0004520] 1.3.2.2
SMS_BearerData SMS_CauseCode
M M
[X.S0004540] 2.233 [X.S0004540] 2.234
a b
Notes: a. b. Include for positive acknowledgments, when applicable. Include for all negative acknowledgments.
7.2.1.2
SMSDeliveryBackward
Note: This operation definition is a modification of the SMSDeliveryBackward operation definition in [X.S0004-540]. The SMSDeliveryBackward (SMDBACK) operation is a general purpose operation that is used to convey an MS-originated short message or in general any other information or encapsulated data to the Anchor MSC after handoff. The following table lists the valid combinations of invoking and responding FEs.
INVOKING FE Case 1 Case 2 Case 3 Case 4 Serving MSC Serving MSC Tandem MSC Tandem MSC RESPONDING FE Anchor MSC Tandem MSC Tandem MSC Anchor MSC
The SMSDeliveryBackward operation is initiated with a TCAP INVOKE (LAST). This is carried by a TCAP QUERY WITH PERMISSION package. The Parameter Set is encoded as follows:
SMSDeliveryBackward INVOKE Parameters Field Identifier Length Contents InterMSCCircuitID MSID SMS_BearerData M M M Value SET [NATIONAL 18] variable octets Type M M
Timer: SBT Reference [X.S0004520] 1.3.2.1 [X.S0004520] 1.3.2.1 Notes
[X.S0004540] 2.129 [X.S0004540] 2.153 [X.S0004540] 2.233 h
7.2 MAP operations
23
X.S0065 v1.0
USSD
SMS_TeleserviceIdentifier ElectronicSerialNumber ServiceIndicator SMS_ChargeIndicator SMS_DestinationAddress SMS_OriginalDestinationAddress SMS_OriginalDestinationSubaddress SMS_OriginalOriginatingAddress SMS_OriginalOriginatingSubaddress SMS_TransactionID
M O O O O O O O O O
[X.S0004540] 2.246 [X.S0004540] 2.112 6.3.1.1 [X.S0004540] 2.235 [X.S0004540] 2.236 [X.S0004540] 2.240 [X.S0004540] 2.241 [X.S0004540] 2.242 [X.S0004540] 2.243 [X.S0004540] 2.248 a i b c d a e a g
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
Notes: a. b. c. d. e. f. g. h. Include if applicable. Include if applicable. If not received, charge message originator. Include if an MC address is specified by the originating SME. Include to identify the SME to which the short message is destined (e.g., the MDN, for termination to an MS-based SME). Include to identify the SME from which the short message originated (e.g., the MDN, if originated by an MS-based SME). Intentionally left for future modifications. Include if TDMA to identify an MS based SMS originating SME. Include the identifier with which the MS last accessed the system, unless that identifier was a MIN-based IMSI, in which case the MobileIdentificationNumber (populated with the MIN derived from that IMSI) should be included. Include for CDMA USSD. When ServiceIndicator is included, the length of the SMS_TeleserviceIdentifier is set to 0.
26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49
i.
The SMSDeliveryBackward operation success is reported with a TCAP RETURN RESULT (LAST). This is carried by a TCAP RESPONSE package. The Parameter Set is encoded as follows:
SMSDeliveryBackward RETURN RESULT Field Identifier Value SET [NATIONAL 18] Type M Reference [X.S0004520] 1.3.2.2 Notes
50 51 52 53 54 55 56 57 58 59 60
24
7.2 MAP operations
USSD
X.S0065 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
Length Contents
variable octets
[X.S0004520] 1.3.2.2
SMS_BearerData SMS_CauseCode SMS_TransactionID
O O O
[X.S0004540] 2.233 [X.S0004540] 2.234 [X.S0004540] 2.248
a b c
Notes: a. b. c. Include for positive acknowledgments, when applicable. Include for all negative acknowledgments. Include if TDMA to identify an MS based SMS originating SME.
7.3
7.3.1
MAP parameters
Parameter definitions
ServiceIndicatior
Note: This parameter definition is a modification of the ServiceIndicator parameter definition in [X.S0004-550]. The ServiceIndicator (SRVIND) parameter indicates a type of service.
Field Identifer Length Contents H G F E D Service C B A Octet 1 n a Notes Value ServiceIndicator IMPLICIT OCTET STRING variable octets Type M M Reference [X.S0004-550] [X.S0004-550] Notes
7.3.1.1
Notes: a. Ignore extra octets, if received. Send only defined (or significant) octets
Service (octet 1)
Decimal Value 0 Meaning Undefined Service.
7.3 MAP parameters
25
X.S0065 v1.0
USSD
1 2 3 4 5 6 7 values through 223 224 through 255
CDMA OTASP Service. TDMA OTASP Service. CDMA OTAPA Service. See [X.S0002] See [X.S0002] See [X.S0002] USSD Reserved. Treat the same as value 0, Undefined Service. Reserved for IS-41 protocol extension. If unknown, treat the same as value 0, Undefined Service.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
7.3.1.2
TransactionCapability
Note: This parameter definition is a modification of the TransactionCapability parameter definition in [X.S0004-550]. The TransactionCapability (TRANSCAP) parameter indicates a systems transaction capability at the current time (i.e., this capability may change over time).
Field Identifer Length Contents H NAMI OTAP A G NDSS S&R F UZCI WADD R E SPINI TL D RUI C ANN B BUSY A PROF Octet 1 2 3 N a b Notes Value TransactionCapability IMPLICIT OCTET STRING 2 or more octets Type M M Reference [X.S0004-550] [X.S0004-550] Notes
18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39
Multiple Terminations USSD MX ANCA P Rsvd
Reserved
40 41 42 43 44
Notes: a Reserved bits shall be ignored on receipt and set to zero on sending.
45 46 47
b Ignore extra octets, if received. Send only defined (or significant) octets. Profile (PROF) (octet 1, bit A)
Value 0 1 Meaning The system is not capable of supporting the IS-41-C profile parameters. The system is capable of supporting the IS-41-C profile parameters.
48 49 50 51 52 53 54 55 56 57 58 59 60
26
7.3 MAP parameters
USSD
X.S0065 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
Busy Detection (BUSY) (octet 1, bit B)

Value 0 1 Meaning The system is not capable of detecting a busy condition at the current time. The system is capable of detecting a busy condition at the current time.
Announcements (ANN) (octet 1, bit C)

Value 0 1 Meaning The system is not capable of honoring the AnnouncementList parameter at the current time. The system is capable of honoring the AnnouncementList parameter at the current time.
Remote User Interaction (RUI) (octet 1, bit D)

Value 0 1 Meaning The system is not capable of interacting with the user. The system is capable of interacting with the user.
Subscriber PIN Intercept (SPINI) (octet 1, bit E)

Value 0 1 Meaning The system is not capable of supporting local SPINI operation at the current time. The system is capable of supporting local SPINI operation.
UZCapabilityIndicator (UZCI) (octet 1, bit F)

Value 0 1 Meaning The system is not User Zone capable at the current time. The system is User Zone capable at the current time.
NDSS Capability (NDSS) (octet 1 bit G)

Value 0 1 Meaning Serving System is not NDSS capable. Serving System is NDSS capable.
NAME Capability Indicator (NAMI) (octet 1 bit H)

Value 0 1 Meaning The system is not CNAP/CNAR capable. The system is CNAP/CNAR capable.
7.3 MAP parameters
27
X.S0065 v1.0
USSD
Multiple Terminations (octet 2, bits A-D)

Value 0 1 through 15 Meaning The system cannot accept a termination at this time (i.e., cannot accept routing information). The system supports the number of call legs indicated.
2 3 4 5 6 7 8 9
TerminationList (TL) (octet 2, bit E)

Value 0 1 Meaning The system is not capable of supporting the TerminationList parameter at the current time. The system is capable of supporting the TerminationList parameter at the current time.
10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
WIN Addressing (WADDR) (octet 2, bit F)

Value 0 1 Meaning The system is not capable of supporting the TriggerAddressList parameter. The system is capable of supporting the TriggerAddressList parameter.
26 27 28 29 30 31 32 33 34
Lower Layer Segmentation and Reassembly (S&R) (octet 2, bit G)

Value 0 1 Meaning The system is not capable of supporting lower layer segmentation and reassembly, (S&R) The system is capable of supporting lower layer segmentation and reassembly, (S&R).
35 36 37
Over the Air Parameter Administration OTAPA (octet 2, bit H)

Value 0 1 Meaning The system is not capable of supporting the CDMA Over the Air Parameter Administration. The system is capable of supporting the CDMA Over the Air Parameter Administration.
38 39 40 41 42 43 44 45 46
Announcement Capabilities(ANCAP) (octet 3, bit B)

Value 0 Meaning The system is not capable of supporting the enhanced call redirection (e.g., generating tones and announcements) at the current time. The system is capable of supporting the enhanced call redirection (e.g., generating tones and announcements) at the current time.
47 48 49 50 51 52 53 54 55 56 57 58 59 60
28
7.3 MAP parameters
USSD
X.S0065 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
MIN Extension(MX) (octet 3, bit C)

Value 0 1 Meaning The system does not require the MIN Extension for this MS. The system requires that the MIN Extension for this MS be transmitted.
Unstructured Supplementary Service Data (USSD) (octet 3, bit D)

Value 0 1 Meaning The system is not capable of supporting the CDMA Unstructured Supplementary Service Data. The system is capable of supporting the CDMA Unstructured Supplementary Service Data.
7.3.1.3
Profile
Note: This parameter definition is a modification of the Profile parameter definition in [X.S0004-550]. The Profile is a collection of the subscribers calling profile information. This information is a list of optional parameters. The Profile macro has been defined solely for editorial convenience, and does not affect the encoding in any way.
Profile Type Contents AuthenticationCapability CallingFeaturesIndicator CarrierDigits CDMABandClass CDMABandClassList CDMAServiceOptionList DMH_AccountCodeDigits DMH_AlternateBillingDigits DMH_BillingDigits GeographicAuthorization O O O O O O O O O O [X.S0004550] 2.12 [X.S0004550] 2.38 [X.S0004550] 2.47 [X.S0004550] 2.52 [X.S0004550] 2.54 [X.S0004550] 2.77 [X.S0004550] 2.118 [X.S0004550] 2.119 [X.S0004550] 2.120 [X.S0004550] 2.132 a b c z ad ab d d d e Reference Notes
7.3 MAP parameters
29
X.S0065 v1.0
USSD
MessageWaitingNotificationCount MessageWaitingNotificationType MobileDirectoryNumber OriginationIndicator OriginationTriggers PACAIndicator PreferredLanguageIndicator PSID_RSIDList QoSPriority RestrictionDigits RoutingDigits SMS_OriginationRestrictions SMS_TerminationRestrictions SPINIPIN SPINITriggers TDMADataFeaturesIndicator TerminationRestrictionCode TerminationTriggers TriggerAddressList UserGroup USSDAddress
O O O O O O O O O O O O O O O O O O O O O
[X.S0004550] 2.146 [X.S0004550] 2.147 [X.S0004550] 2.149 [X.S0004550] 2.178 [X.S0004550] 2.179 [X.S0004550] 2.181 [X.S0004550] 2.189 [X.S0004550] 2.194 [X.S0004550] 2.196 [X.S0004550] 2.216 [X.S0004550] 2.219 [X.S0004550] 2.255 [X.S0004550] 2.257 [X.S0004550] 2.261 [X.S0004550] 2.262 [X.S0004550] 2.281 [X.S0004550] 2.291 [X.S0004550] 2.293 [X.S0004550] 2.296 [X.S0004550] 2.303 7.3.1.4
f g x h I
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
k u, aa y l m n o q r ac s T w p ae
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
Notes: a. Include if available. May not be received from systems that conform to revisions prior to IS-41-C. b. Include to identify feature authorization and activity. c. Include if preferred carrier is applicable and TransactionCapability supported.
53 54 55 56 57 58 59 60
30
7.3 MAP parameters
USSD
X.S0065 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
d. Include if available for recording purposes (see DMH). e. Include if available for certain authorization restricted areas. f. Include if the MWI field of the MessageWaitingNotificationType parameter has the value MWI On. Include to indicate the type and number of messages waiting. g. Include if Message Waiting Notification feature is active. h. Include to indicate the type of calls allowed for origination service. i. Include to indicate OriginationRequest triggers. j. Include to identify the PACA feature. k. Include to identify the Preferred Language feature. l. Include if originations are restricted (e.g., to NPA-NXX or NPA-NXX-XXXX) and the TransactionCapability parameter is supported. Set nature of number to International if it is known that the destination network element for the profile can accept digits in this format (e.g., MSCIdentificationNumber parameter previously received). m. Include for special routing information. n. Include for MS originated Short Message Service. o. Include for MS terminated Short Message Service. p. Include to specify the User Group allocation status. q. Include if local SPINI operation supported. r. Include to indicate SPINI triggers. s. Include to indicate the type of call termination service. t. Include to indicate the RedirectionRequest or TransferToNumberRequest triggers. u. Include to indicate the list of acceptable PSIDs/RSIDs for the indicated MS. v. Include to perform User Zone updates at the serving system. w. Include to indicate active WIN triggers and associated addresses for service logic network elements. x. Include if available. y. Include if packet data services are applicable to indicate relative priority for purposes of radio resource allocation. z. Include to indicate information for the current band in use. aa. The PSID_RSIDList and UserZoneData parameters are mutually exclusive. ab. Include to indicate preferred CDMA service options in descending order of preference. ac. Include to indicate allowed TDMA data services. ad. Include to indicate band classes supported. ae. Include for USSD service.
7.3 MAP parameters
31
X.S0065 v1.0
USSD
7.3.1.4
USSDAddress
The USSDAddress (USSDADDR) parameter is used to convey the current routing address of the USSD Gateway for the purpose of sending USSD messaging from the MS USSD client to the USSD Gateway. If SS7 is used for international USSD message routing, this parameter should be formatted as an E.212 number. If SS7 is used for national message routing, this parameter may be formatted either as an SS7 point code address or as an E.212 number.
1 2 3 4 5 6 7 8 9
7.3.1.4.1
USSDAddress parameter for BCD digits
10 11 12 13 14
Field Identifer Length Contents H G F E
Value USSDAddress IMPLICIT DigitsType variable octets
Type M M
Reference [X.S0004-550] [X.S0004-550]
Notes a
15 16 17 18 19 20 21
Octet 1 2
Notes b c d,e f
22 23 24 25
Type of Digits Nature of Number Numbering Plan Number of Digits 2nd BCD Digit 4th BCD Digit nth BCD Digit 1st BCD Digit 3rd BCD Digit n-1st BCD Digit Encoding
26 27 28 29 30 31 32 33
3 4 5 6 m
34 35 36 37 38
Notes: a. b. c. d. e. f. 7.3.1.4.2 Refer to the DigitsType parameter type see [X.S0004-551] Section 1.2 for notes and field encoding. Type of Digits is ignored on receipt. Nature of Number shall be National. Numbering Plan supported shall include include E.164, E.212, X.121, and Private numbering plan. Encoding shall be octet string for this parameter variant. The Number of Digits ranges from 0 to at least 15.
39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55
USSDAddress parameter for an IP address
Field Identifer
Value USSDAddress IMPLICIT DigitsType
Type M
Reference [X.S0004-550]
Notes a
56 57 58 59 60
32
7.3 MAP parameters
USSD
X.S0065 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
Length Contents H G
variable octets
[X.S0004-550]
Octet 1 2
Notes b c d,e
Type of Digits Nature of Number Numbering Plan MSB IP Address Encoding
3 4 5 6 LSB 7
Notes: a. b. c. d. e. 7.3.1.4.3 Refer to the DigitsType parameter type see [X.S0004-551] Section 1.2 for notes and field encoding. Type of Digits is ignored on receipt. Nature of Number shall be National. Numbering Plan shall be SS7 PC and SSN for this parameter variant. Encoding shall be octet string for this parameter variant.
USSDAddress Encoding for an ANSI SS7 Point Code Address
Type M M
Reference [X.S0004-550] [X.S0004-550]
Notes a
Octet 1 2
Notes b c d,e
Type of Digits Nature of Number Numbering Plan Encoding
3 4 5 6 7
Point code--Member Number Point code--Cluster Number Point code--Network Number Subsystem Number
Notes: a. Refer to the DigitsType parameter type see [X.S0004-551] Section 1.2 for notes and field encoding.
7.3 MAP parameters
33
X.S0065 v1.0
USSD
b. c. d. e.
Type of Digits is ignored on receipt. Nature of Number shall be National. Numbering Plan shall be IP for this parameter variant. Encoding shall be octet string for this parameter variant.
1 2 3 4 5 6 7 8 9
7.3.1.4.4
USSDAddress Encoding for a Generic SS7 Point Code Address
10 11 12 13 14
Type M M
Reference [X.S0004-550] [X.S0004-550]
Notes a
15 16 17 18 19 20 21 22
Octet 1 2
Notes b c d,e f
23 24 25
Type of Digits Nature of Number Numbering Plan Point Code Encoding
26 27 28 29 30
3 4 5 6
31 32 33 34 35
Subsystem Number (SSN)
Notes: a. b. c. d. e. f. Refer to the DigitsType parameter type see [X.S0004-551] Section 1.2 for notes and field encoding. Type of Digits is ignored on receipt. Nature of Number shall be National. Numbering Plan shall be SS7 PC and SSN for this parameter variant. Encoding shall be octet string for this parameter variant. Bit A of Octet 4 is the first bit that would be emitted if the point code was transmitted by the MTP layer. If the point code is less than 24 bits in length, then all bits beyond the end of the point code up to and including bit H of Octet 6, should be set to 0.
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
34
7.3 MAP parameters
USSD
X.S0065 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
7.4
7.4.1
MAP signaling procedures

Intersystem procedures
SMS delivery point-to-point
MSC receiving an SMSDeliveryPointToPoint INVOKE Note: This procedure is a modification of the MSC Receiving an SMSDeliveryPointToPoint INVOKE procedure in [X.S0004-641]. Upon receipt of an SMSDeliveryPointToPoint INVOKE for an intended MS or for broadcast, the receiving MSC shall do the following: 1 1-1 1-1-1 1-1-1-1 1-1-2 1-1-2-1 1-1-2-2 1-1-2-2-1 1-1-2-2-1-1 1-1-2-2-2 1-1-2-2-2-1 1-1-2-2-2-2 1-1-2-2-3 1-1-2-3 1-1-2-3-1 1-1-2-4 1-1-2-4-1 1-1-2-4-1-1 1-1-2-4-2 1-1-2-4-2-1 1-1-2-4-2-2 1-1-2-4-3 1-1-2-5 IF the message can be processed: IF the ServiceIndicator parameter set to either the CDMA OTASP Service or the CDMA OTAPA Service is received: IF the SMS_BearerData parameter has a non-zero length: Execute the MSC Receiving SMDPP INVOKE for OTA Data Message Exchange task (see Part 640, sec. 44.2 [X.S0004-640], section. 44.2). ELSEIF the ActionCode parameter is received: CASE ActionCode OF: Attach MSC to OTAF: IF the ServiceIndicator parameter is set to the CDMA OTASP Service value: Execute the MSC Receiving SMDPP INVOKE to Attach with OTAF task (see Part 640, sec. 43.3 [X.S0004-640], section. 43.3). ELSEIF the ServiceIndicator parameter is set to the CDMA OTAPA Service value: Include the SMS_CauseCode parameter set to indicate Unexpected parameter value. Send a RETURN RESULT. ENDIF. Initiate RegistrationNotification:: Execute the MSC Receiving SMDPP INVOKE for Registration of MS task (see Part 640, sec. 45.2 [X.S0004-640], section 45.2). Release TRN: IF the ServiceIndicator parameter is set to the CDMA OTASP Service value: Execute the MSC Receiving SMDPP INVOKE to Release TRN task (see Part 640, sec. 43.5 [X.S0004-640], section 43.5). ELSEIF the ServiceIndicator parameter is set to the CDMA OTAPA Service value: Include the SMS_CauseCode parameter set to indicate Unexpected parameter value. Send a RETURN RESULT. ENDIF. Record NEWMSID:
7.4.1.1
7.4.1.1.1
7.4 MAP signaling procedures
35
X.S0065 v1.0
USSD
1-1-2-5-1 1-1-2-6 1-1-2-6-1 1-1-2-6-2 1-1-2-7 1-1-3 1-1-4 1-2 1-3 1-3-1 1-3-2 1-3-3 1-4 1-5 1-5-1 1-6 1-6-1 1-6-2 1-6-3 1-7 1-8 1-8-1 1-9 1-10 1-10-1 1-11 1-11-1 1-11-2 1-11-3 1-12 1-13 1-13-1 1-14 1-15 1-15-1 1-15-1-1 ENDIF.
Execute the MSC Receiving SMDPP INVOKE to Record NEW MSID task (see Part 640, sec. 45.4 [X.S0004-640], section 45.4). DEFAULT: Include the SMS_CauseCode parameter set to indicate Unexpected parameter value. Send a RETURN RESULT. ENDCASE. Exit this task.
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
ENDIF. IF the ServiceIndicator parameter indicating USSD (Unstructured Supplementary Service Data) is received: Execute the MSC Receiving an SMDPP INVOKE for USSD Exchange task (see Section 7.4.1.2.1). Send a RETURN RESULT. Exit this task. ENDIF; IF the SMS_OriginalDestinationAddress parameter is received: Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginatingAddress parameter is received: Set the originatting address with the SMS_OriginatingAddress. ENDIF. IF the SMS_OriginalOriginatingAddress parameter is received: Set the original originating address with the address in the received SMS_OriginalOriginatingAddressparameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginalOriginatingSubaddress parameter is received: Set the original originating subaddress with the address in the received SMS_OriginalOriginatingSubaddress parameter. ENDIF IF the BroadcastCategory parameter is received (indicating BTTC): IF the BroadcastMessageStatus parameter indicates deletion is received: IF the BroadcastMessageIdentifier parameter is received:
36
USSD
X.S0065 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
1-15-1-1-1
IF a broadcast message as indicated by the SMS_OriginalOriginatingAddress parameter and BroadcastMessageIdentifier parameter exists: IF the broadcasting process is ongoing at the MSC: Wait for the broadcast process to be completed. Delete the broadcast message. ELSE: Delete the broadcast message immediately. ENDIF. ENDIF. ELSE (deletion of a group of broadcast messages): FOR each broadcast message that has matching SMS_OriginalOriginatingAddress and BroadcastCategory parameter values: IF the broadcasting process is ongoing at MSC: Wait for the broadcast process to be completed. Delete the broadcast message. ELSE: Delete the broadcast message immediately. ENDIF. ENDFOR. ENDIF. Send a RETURN RESULT. Exit this task. ENDIF. IF BroadcastMessageStatus parameter indicates replacement: IF message as indicated by the SMS_OriginalOriginatingAddress parameter and BroadcastMessageIdentifier parameter exists: Replace the old broadcast message with the received message1. ELSE: Treat the received message as a new broadcast message. ENDIF. ELSE (BroadcastMessageStatus parameter either has not been received or, if received, indicates new): Treat the message as a new broadcast message. ENDIF. IF Broadcast Periodicity is requested for a new message and Broadcast Periodicity cannot be supported for this message by this MSC at this time: Include the SMS_CauseCode parameter set to indicate Broadcast Periodicity Failure in MSC.
1-15-1-1-1-1 1-15-1-1-1-1-1 1-15-1-1-1-1-2 1-15-1-1-1-2 1-15-1-1-1-2-1 1-15-1-1-1-3 1-15-1-1-2 1-15-1-2 1-15-1-2-1
1-15-1-2-1-1 1-15-1-2-1-1-1 1-15-1-2-1-1-2 1-15-1-2-1-2 1-15-1-2-1-2-1 1-15-1-2-1-3 1-15-1-2-2 1-15-1-3 1-15-1-4 1-15-1-5 1-15-2 1-15-3 1-15-3-1 1-15-3-1-1 1-15-3-2 1-15-3-2-1 1-15-3-3 1-15-4 1-15-4-1 1-15-5 1-15-6 1-15-6-1
As part of this replacement, the stored priority for this message is replaced by the priority associated to the received message (i.e., the priority indicated by the BroadcastMessagePriority parameter, if that parameter is received, or the default value of normal otherwise). Also, the stored broadcast periodicity for this message is replaced by the value of a received Broadcast-Periodicity parameter, but left unchanged if the BroadcastPeriodicity parameter is not received.
37
X.S0065 v1.0
USSD
1-15-7 1-15-8 1-15-9
ENDIF. Send a RETURN RESULT. Process the broadcast message according to the BroadcastMessagePriority value (if available) and BroadcastPeriodicity value (if available) and execute the MSC Initiating Broadcast SMD-Request Across the Air Interface task (see Part 691, sec. 4.7 [X.S0004-691], Section 4.7) when the initial broadcast of this message should occur. WHILE any additional broadcasts of this message are required (based on the BroadcastPeriodicity value for this message and the capabilities of the MSC): Execute the MSC Initiating Broadcast SMD-Request Across the Air Interface task (see Part 691, sec. 4.7 [X.S0004-691], Section 4.7) when the next broadcast of this message should occur. ENDWHILE. Exit this task. ENDIF. IF an MSID parameter is received: Set the MSID to the received MSID parameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF an ElectronicSerialNumber parameter is received: Set the ESN to the received ElectronicSerialNumberparameter. ENDIF. IF the destination MS is anchored by this MSC: IF the MSC is allowed to terminate a short message to the destination MS according to the SMS_TerminationRestrictions parameter in the destination MSs profile: IF the MSC is currently the Serving MSC: IF the MS is currently able to receive an SMS message: Optionally, take action to keep the MS in a state in which it can receive SMS messages (e.g., take the MS out of sleep mode). Relay received parameters, except the SMS_ChargeIndicator and SMS_NotificationIndicator parameters. IF the system is a CDMA System AND IF the MS last registered in an area close to the system border AND IF the MSC is configured to support border system SMS message delivery: Execute the MSC Attempt Border MSC SMS Message Delivery task (see Part 641, sec. 3.7 [X.S0004641], section 3.7). ELSE: Execute the MSC Initiating SMD-REQUEST toward an MSBased SME task (see Part 691, sec. 4 [X.S0004691], section 4).
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-15-10 1-15-10-1
1-15-11 1-15-12 1-16 1-17 1-17-1 1-18 1-18-1 1-18-2 1-18-3 1-19 1-20 1-20-1 1-21 1-22 1-22-1
1-22-1-1 1-22-1-1-1 1-22-1-1-1-1 1-22-1-1-1-2 1-22-1-1-1-3
1-22-1-1-1-3-1
1-22-1-1-1-4 1-22-1-1-1-4-1
38
USSD
X.S0065 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-22-1-1-1-4-2 1-22-1-1-1-4-2-1 1-20-1-1-1-4-2-1-1
IF internal algorithms indicate that neighboring MSC(s) should be sent the SMS message: FOR each applicable MSC: Execute the MSC Initiating InterSystem SMS Page task (see Part 640, sec. 35.1 [X.S0004-640], section. 35.1). ENDFOR. ENDIF. ENDIF. ELSEIF the MS is able to receive only a postponed SMS message (e.g., is busy, radio interface resource shortage, destination SME out of service, in a sleep mode or is inactive): IF the SMS_NotificationIndicator parameter was present in the SMSDeliveryPointToPoint INVOKE and the SMS_NotificationIndicator indicates Do not notify when available: Include the SMS_CauseCode parameter set to an appropriate value. ELSE (notification was requested): Set the SMS Delivery Pending Flag for this MS. Include the SMS_CauseCode parameter set to SMS Delivery Postponed. ENDIF. ELSE (the MS is not currently able receive an SMS message): Include the SMS_CauseCode parameter set to Radio interface incompatibility. ENDIF. ELSE (the MS has been handed off): Relay received parameters, except the SMS_ChargeIndicator parameter. Execute the MSC Initiating SMS Delivery Forward task (see Part 641, sec. 2.1 [X.S0004-641], section 2.1). ENDIF.
1-22-1-1-1-4-2-2 1-22-1-1-1-4-3 1-22-1-1-1-5 1-22-1-1-2
1-22-1-1-2-1
1-22-1-1-2-1-1 1-22-1-1-2-2 1-22-1-1-2-2-1 1-22-1-1-2-2-2 1-22-1-1-2-3 1-22-1-1-3 1-22-1-1-3-1 1-22-1-1-4 1-22-1-2 1-22-1-2-1 1-22-1-2-2 1-22-1-3
(At this point, message relaying had been postponed, denied, or attempted.) 1-22-1-4 1-22-1-4-1 1-22-1-4-1-1 1-22-1-4-2 1-22-1-4-2-1 1-22-1-4-2-1-1 1-22-1-4-2-1-1-1 1-22-1-4-2-1-2 IF an SMS_CauseCode has not been included (delivery was successful): IF the SMS_NotificationIndicator parameter was received and it indicates Do not notify when available: (Ignore the previously received SMS_MessageCount, if it is present). ELSE (notification was requested): IF the MSC is the Serving MSC: IF the SMS_MessageCount parameter was not received OR IF the received SMS_MessageCount parameter is zero: Optionally, restore the MS to its prior state (e.g., restore the MS to sleep mode). ELSE (SMS_MessageCount was non-zero):
39
X.S0065 v1.0
USSD
1-22-1-4-2-1-2-1 1-22-1-4-2-1-3 1-22-1-4-2-2 1-22-1-4-2-3 1-22-1-4-2-3-1 1-22-1-4-2-4 1-22-1-4-3 1-22-1-4-4 1-22-1-5 1-22-1-5-1 1-22-1-5-1-1 1-22-1-5-1-2 1-22-1-5-2 1-22-1-5-2-1 1-22-1-5-2-2 1-22-1-5-3 1-22-1-5-3-1 ENDIF.
(Keep the MS awake for a while to receive another possible message.) ENDIF. ENDIF. IF the SMS_MessageCount parameter was not received OR IF the received SMS_MessageCountparameter is zero: Clear the SMS Delivery Pending Flag for this MS. ENDIF. Relay the received parameters. ELSE (an SMS_CauseCode has been included): IF the SMS_CauseCode is from an MS, but it is not a legitimate SMS_CauseCode for an MS to send (e.g., SMS delivery postponed): Include the SMS_CauseCode parameter set to Network failure. Relay the other received parameters. ELSEIF the SMS_CauseCode was for a Destination resource shortage: Relay all received parameters. Clear the SMS Delivery Pending Flag for this MS. ELSEIF the SMS_CauseCode was for a temporary condition: IF the SMS_NotificationIndicator parameter was present in the SMSDeliveryPointToPoint INVOKE and the SMS_NotificationIndicator indicates Do not notify when available: Relay all received parameters. ELSE (notification was requested): Set the SMS Delivery Pending Flag for this MS. Include the SMS_CauseCode parameter set to SMS Delivery Postponed. Relay the other received parameters. ENDIF. ELSE (SMS_CauseCode is not for a temporary condition): Relay all received parameters. ENDIF. ENDIF. Send a RETURN RESULT.
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-22-1-5-3-1-1 1-22-1-5-3-2 1-22-1-5-3-2-1 1-22-1-5-3-2-2 1-22-1-5-3-2-3 1-22-1-5-3-3 1-22-1-5-4 1-22-1-5-4-1 1-22-1-5-5 1-22-1-6 1-22-1-7 1-22-2 1-22-2-1 1-22-2-2 1-22-3 1-23 1-23-1 1-23-2 1-24
ELSE (MSC is not allowed to terminate a short message to the destination MS Include the SMS_CauseCode parameter indicating termination is SMS Termination Denied. Send a RETURN RESULT. ENDIF. ELSE (MS is not anchored by this MSC: Include the SMS_CauseCode parameter set to Destination no longer at this address. Send a RETURN RESULT. ENDIF.
40
USSD
X.S0065 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
2 2-1 2-2 3 4 7.4.1.1.2
ELSE (the received message cannot be processed Include the SMS_CauseCode parameter indicating the proper value. Send a RETURN RESULT. ENDIF. Exit this task.
Anchor MSC initiating SMS delivery Point-to-Point Note: This procedure is a modification of the Anchor MSC Initiating SMS Delivery Point To Point procedure in [X.S0004-641]. This task assumes that it is called by a higher function capable of acting upon returned SMS_CauseCode appropriately. It sets the destination address, if not already set, based on the SMS_OriginationRestrictions from the MS profile. Upon request, the Anchor MSC shall do the following: 1 1-1 1-1-1 1-2 1-2-1 1-2-1-1 1-2-2 1-2-2-1 1-2-2-2 1-2-3 1-3 1-3-1 1-3-2 1-4 1-4-1 1-5 IF the request can be processed: IF the SMS_TeleserviceIdentifier parameter is set to IMS Services Teleservice: Include the SMS_DestinationAddress parameter set to the SMS_OriginalDestinationAddress. ELSEIF the ServiceIndicator parameter is present and indicates USSD (Unstructured Supplementary Service Data) (i.e., MS has initiated a USSD request): IF subscribers profile contains a USSD Gateway address: Set the destination address to the USSD Gateway address. ELSE: Include the SMS_CauseCode parameter indicating SMS Origination Restriction. Return to the calling task indicating denied. ENDIF. ELSEIF SMS originations are blocked (DEFAULT field of SMS_OriginationRestrictions set to Block all): Include the SMS_CauseCode parameter indicating SMS Origination Restriction. Return to the calling task indicating denied. ELSEIF the destination address was provided (by the MS): (do nothing, destination address is already set correctly) ELSEIF originations are forced to use indirect routing through the originating subscribers MC (Force Message Center field of SMS_OriginationRestrictions set to Force Indirect): Include the SMS_DestinationAddress parameter set to the SMS_OriginalOriginatingAddress. ELSEIF visited MSC network operator policy dictates that SMS originations shall use indirect routing: Include the SMS_DestinationAddress parameter set to the SMS_OriginalOriginatingAddress. ELSE: Include the SMS_DestinationAddress parameter set to the SMS_OriginalDestinationAddress. ENDIF.
1-5-1 1-6 1-6-1 1-7 1-7-1 1-8
41
X.S0065 v1.0
USSD
1-9 1-10 1-11 2 2-1 2-2 3 4
Relay all included parameters. Execute the Initiating SMS Delivery Point -To-Point task (see Part 641, sec. 3.2 [X.S0004-641], section 3.2). Return to the calling task with the received parameters and the returned indication. Include the SMS_CauseCode parameter indicating the appropriate value. Return to the calling task indicating denied. ENDIF. Exit this task.
1 2 3 4 5 6 7 8 9 10 11 12 13
ELSE (request cannot be processed):
7.4.1.2
7.4.1.2.1
SMS delivery point-to-point for USSD exchange

MSC receiving an SMDPP INVOKE for USSD exchange 1 1-1 1-1-1 1-1-2 1-2 1-2-1 1-2-2 1-2-2-1 1-2-2-2 1-2-3 1-3 1-4 2 2-1 3 4 ENDIF. Execute MSC Sending the USSD Message to the MS (See Section 6.4.3.3). ELSE (request cannot be processed): Include the SMS_CauseCode parameter indicating the appropriate value. ENDIF. Exit this task. IF the request can be processed: IF the MS has performed an intersystem handoff forward: Execute the MSC Initiating SMSDeliveryForward task (see [X.S0004 -641], section 2.1). Exit this task. ELSEIF the Target MS is not assigned to a traffic channel: Page the MS and assign the MS to a traffic channel for USSD. IF not successful: Include the SMS_CauseCode parameter set to identify the failure appropriately. Exit this task. ENDIF.
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
7.4.1.2.2
MSC sending a USSD message to the MS 1 1-1 1-2 2 3 3-1 4 4-1 4-2 5 IF the Target MS is not assigned to a traffic channel: Include the SMS_CauseCode parameter set to identify the failure appropriately. Exit this task. ENDIF. IF the SMS_BearerData parameter has a non-zero length: Extract the USSD Message from the SMS_BearerData parameter. ELSE (the SMS_BearerData has a zero length): Include the SMS_CauseCode parameter indicating the appropriate value. Exit this task. ENDIF.
50 51 52 53 54 55 56 57 58 59 60
42
USSD
X.S0065 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
6 7 7-1 7-2 8 9 9-1
Send the USSD Message to the MS. IF the USSD Message could not be sent: Include the SMS_CauseCode parameter set appropriately. Exit this task. ENDIF. IF the MSC Request an acknowledgment from the BS: WAIT for response from the BS: WHEN a BS response is received: IF an error indication is included: Include the SMS_CauseCode parameter set appropriately. ENDIF. ENDWAIT.
9-1-1 9-1-1-1 9-1-1-1-1 9-1-1-2 9-2 10 ENDIF.
11 Exit this task.
7.4.1.3
7.4.1.3.1
SMSDeliveryForward
MSC receiving an SMSDeliveryForward INVOKE Note: This procedure is a modification of the MSC Receiving an SMSDeliveryForward INVOKE procedure in [X.S0004-641]. Upon receipt of an SMSDeliveryForward INVOKE, the MSC shall do the following: 1 1-1 1-1-1 1-1-2 1-1-3 1-2 1-3 1-3-1 1-3-1-1 1-3-1-2 1-3-2 1-3-2-1 1-3-2-2 1-3-3 1-3-4 1-4 1-5 IF the received message can be processed: IF neither the MobileIdentificationNumber or IMSI parameter is received: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the ServiceIndicator parameter indicating USSD (Unstructured Supplementary Service Data) is received: IF the MSC is the Serving MSC: Execute MSC Sending the USSD Message to the MS (See Section 6.4.1.2.2). Send a RETURN RESULT. ELSE (this is a Tandem MSC): Execute MSC Initiating SMS Delivery Forward (see [X.S0004 -641], section 2.1) toward the Serving MSC in the call. Relay all received parameters. ENDIF. Exit this task. ENDIF. IF the SMS_OriginalDestinationAddress parameter is received:
43
X.S0065 v1.0
USSD
1-5-1 1-6 1-6-1 1-6-2 1-6-3 1-7 1-8 1-8-1 1-9 1-10 1-10-1 1-11 1-11-1 1-11-2 1-11-3 1-12 1-13 1-13-1 1-13-1-1 1-13-1-2 1-13-2 1-13-2-1 1-13-3 1-14 1-14-1 1-14-1-1 1-14-1-2 1-14-1-3 1-14-1-4 1-14-2 1-14-2-1 1-14-3 1-15 2 2-1 3 4 5
Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginatingAddress parameter is received: Set the originating address with received SMS_OriginatingAddress. ENDIF. IF the SMS_OriginalOriginatingAddress parameter is received: Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the MSC is the Serving MSC: IF the MS is currently able to receive SMS messages: Execute the MSC Initiating SMD-REQUEST toward an MS-Based SME task (see Part 691, sec. 4 [X.S0004-691], section 4). Relay all received parameters. ELSE (the MS is unable to receive SMS messages): Include the SMS_CauseCode parameter set to the appropriate value. ENDIF. ELSE (this is a Tandem MSC): IF the next MSC in the handoff chain is known to support SMS: Discard the InterMSCCircuitID parameter. Relay all other received parameters. Execute MSC Initiating SMS Delivery Forward (see Part 641, sec. 2.1 [X.S0004-641], Section. 2.1) toward the Serving MSC in the call. Relay all received parameters. ELSE (the handed-off system does not support SMS): Include the SMS_CauseCode parameter set to Network failure. ENDIF. ENDIF. Include the SMS_CauseCode parameter with the appropriate value.
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
ELSE (the received message cannot be processed) ENDIF. Send a RETURN RESULT Exit this task.
44
USSD
X.S0065 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
7.4.1.4
7.4.1.4.1
SMSDeliveryBackward
MSC receiving an SMSDeliveryBackward INVOKE Note: This procedure is a modification of the MSC Receiving an SMSDeliveryBackward INVOKE procedure in [X.S0004-641]. Upon receipt of an SMSDeliveryBackward INVOKE, the MSC shall do the following: 1 1-1 1-1-1 1-2 1-3 1-3-1 1-4 1-4-1 1-4-2 1-4-3 1-5 1-6 1-6-1 1-7 1-8 1-9 1-9-1 1-9-2 1-10 1-10-1 1-10-1-1 1-10-1-2 1-10-2 1-10-2-1 1-10-3 1-11 1-12 2 2-1 2-2 ENDIF. Send a RETURN RESULT towards the Serving MSC. Include the SMS_CauseCode parameter indicating the proper value. Send a RETURN RESULT. IF the received message can be processed: IF the SMS_DestinationAddress parameter is received: Set the destination address with the address in the received SMS_DestinationAddress parameter. ENDIF. IF the SMS_OriginalDestinationAddress parameter is received: Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. ELSE: Include the SMS_CauseCode parameter set to Missing Expected Parameter. Send a RETURN RESULT. Exit this task. ENDIF. IF the SMS_OriginalOriginatingAddress parameter is received: Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter. ENDIF. Relay all parameters received. IF the MSC is the Anchor MSC: Execute the Anchor MSC Initiating SMS Delivery Point -To-Point task (7.4.1.1.2). Relay all parameters received. ELSE (the MSC is a Tandem MSC): Execute the MSC Initiating SMS Delivery Backward task (7.4.1.4.2). Discard the InterMSCCircuitID parameter. Relay all parameters received. ELSE (the handing-off system does not support SMS): Include the SMS_CauseCode parameter set to Network failure. ENDIF.
ELSE (the received message cannot be processed):
45
X.S0065 v1.0
USSD
3 4 7.4.1.4.2
ENDIF. Exit this task.
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
MSC initiating SMSDeliveryBackward Note: This procedure is a modification of the MSC Initiating SMS Delivery Backward procedure in [X.S0004-641]. Upon request to send an MS-originated SMS point-to-point message up the handoff chain, the MSC shall do the following: 1 2 2-1 2-1-1 2-2 2-3 2-4 2-4-1 2-5 2-6 3 3-1 4 5 6 7 8 8-1 8-2 8-2-1 8-2-1-1 8-2-1-1-1 8-2-1-1-2 8-2-1-2 8-2-2 8-2-3 8-2-4 8-3 8-3-1 ENDIF. Relay all parameters received. Return to the calling task as accepted. ELSE (the message cannot be processed): Return to the calling task with the SMS_CauseCode indicating Other Network Problem. Include InterMSCCircuitID parameter set to the trunk used in the direction toward the Anchor MSC. IF the MSC is the Serving MSC: IF the destination address was provided (by the MS): Include the SMS_DestinationAddress parameter set to the destination address. ENDIF. Include the SMS_OriginalDestinationAddress parameter set to the original destination address (provided by the MS). IF the original originating address was provided (by the MS): Include the SMS_OriginalOriginatingAddress prameter set to the original originating address. ENDIF. Include other parameters as appropriate. ELSE (the MSC is acting as a Tandem MSC for the MS): Include all parameters received from the calling task (see Part 540 [X.S0004-540]). ENDIF. Send a SMSDeliveryBackward INVOKE message toward the Destination Address. Start the Short Message Backward Timer (SBT). WAIT for an SMS Delivery Backward response: WHEN a RETURN RESULT is received: Stop the timer (SBT). IF the message can be processed: IF the SMSDeliveryBackward INVOKE was initiated by an initial Serving MSC: IF an intersystem handoff (handoff forward) has occurred: Execute the MSC Initiating SMS Delivery Point To Point Ack task (see Part 641, sec 4.1 [X.S0004-641], Section 4.1 ). Exit this task. ENDIF.
46
USSD
X.S0065 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
8-4 9 9-1 9-2 10-1 10-2
ENDIF. WHEN a FacilitiesRelease INVOKE is received : Stop the timer (SBT). Exit this task. Stop the timer (SBT). Return to the calling task with the SMS_CauseCode indicating Other Network Problem. Stop the timer (SBT). CASE reject problem specifier OF: Unrecognized component, Incorrect component portion, Badly structured component portion, Incorrect parameter, Unrecognized package type, Incorrect transaction portion, Badly structured transaction portion: Return to the calling task with the SMS_CauseCode indicating Encoding Problem. Unrecognized operation code: Return to the calling task with the SMS_CauseCode indicating SMS not supported. DEFAULT: Return to the calling task with the SMS_CauseCode indicating Network failure. ENDCASE: Return to the calling task with the SMS_CauseCode indicating Network failure.
10 WHEN a RETURN ERROR1 is received :
11 WHEN a REJECT is received: 11-1 11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-9-1 11-10 11-10-1 11-11 11-12 11-13 12-1
12 WHEN the timer (SBT) expires: 13 ENDWAIT.
7.4.1.5
7.4.1.5.1
SMS Notification
HLR initiating SMS Notification Note: This procedure is a modification of the HLR Initiating SMS Notification procedure in [X.S0004-641]. Upon request to send an SMSNotification message, the HLR shall do the following: 1 2 3 Include the ElectronicSerialNumber parameter set to the ESN of the desired MS. Include the MSID parameter set to the MIN or IMSI of the desired MS. IF the notification is being issued, for any of the TDMA teleservices, independent of a postponed (previous) SMSRequest to initiate a SMS teleservice on an MS:
The sending of an SMS DeliveryBackward RETURN ERROR is not recommended and error tables are not supplied.
47
X.S0065 v1.0
USSD
3-1 4 5 5-1 6 6-1 7 7-1
Include the SMSTeleserviceIdentifier parameter set to the teleservice for which the notification is being made. ENDIF. IF MS is denied: Include the SMS_AccessDeniedReason parameter set to Denied. ELSEIF MS is unavailable or the temporary SMS routing address is not current: Include the SMS_AccessDeniedReason parameter set to Unavailable. ELSE: Include the SMS_Address parameter set to the temporary SMS routing address of the desired MS for SMS, or set to temporary MSC routing address for CDMA OTAPA, or set to temporary MSC routing address for USSD. ENDIF. Send an SMSNotification message toward the MSs MC, for SMS, or toward the OTAF, for OTAPA or toward the USSD Gateway, for USSD.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
8 9
10 Start the SMS Notification Timer (SNT). 11 WAIT for a SMS Notification response: 12 WHEN a RETURN RESULT is received: 12-1 12-2 12-2-1 12-3 13-1 13-2 Stop the timer (SNT). IF the message cannot be processed: Execute Local Recovery Procedures task (see Part 630, sec. 5.1[X.S0004630], section 5.1). ENDIF. Stop the timer (SNT). Execute Local Recovery Procedures task (see Part 630, sec. 5.1 [X.S0004-630], section 5.1). Execute Local Recovery Procedures task (see Part 630, sec. 5.1[X.S0004-630], section 5.1).
23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43
13 WHEN a RETURN ERROR or REJECT is received:
14 WHEN the timer (SNT) expires: 14-1
15 ENDWAIT. 16 Exit this task.
7.4.1.6
7.4.1.6.1
SMS Request
HLR receiving an SMSRequest INVOKE Note: This procedure is a modification of the HLR receiving an SMSRequest INVOKE procedure in [X.S0004-641]. Upon receipt of a SMSRequest INVOKE, the HLR shall do the following: 1 1-1 1-1-1 IF the message can be processed: IF CDMA service: IF the addressed MS is not known, OR IF the MS is known, but is not authorized for SMS, OR IF the ServiceIndicator parameter is present and its value is not supported by the HLR: Include the SMS_AccessDeniedReason parameter indicating Denied.
44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60
1-1-1-1
48
USSD
X.S0065 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-1-1-2 1-1-1-3 1-1-2 1-1-3 1-1-3-1 1-1-3-1-1 1-1-3-2 1-1-3-3
Send a RETURN RESULT. Exit this task. ENDIF. IF ServiceIndicator parameter is present and indicates CDMA OTAPA service: IF the ElectronicSerialNumber parameter was not received: Include the ElectronicSerialNumber parameter set to identify the MS. ENDIF. IF either current serving MSC is not OTAPA capable OR is not secure to program the MS at its current location, OR IF the temporary routing address is not current, OR IF the MS is reported as inactive: IF the SMSNotificationIndicator parameter was present in the SMSRequest INVOKE and the SMSNotificationIndicator indicates Do not notify when available: Include the SMSAccessDeniedReason parameter set to Unavailable. ELSE: IF the OTA Delivery Pending Flag for this MS is not already set: Set the OTA Delivery Pending Flag for this MS, storing the routing address of the OTAF from which the SMSRequest INVOKE was received with that flag. ELSE: Replace the routing address previously stored with the OTA Delivery Pending Flag for this MS with the routing address of the OTAF from which the SMSRequest INVOKE was received. ENDIF. Include the SMSAccessDeniedReason parameter set to Postponed. ENDIF. Send a RETURN RESULT. Exit this task. ELSE: Include the SMS_Address parameter set to the current address for the MS. Send a RETURN RESULT. Exit this task. ENDIF. ENDIF. IF ServiceIndicator parameter is present and indicates USSD ((Unstructured Supplementary Service Data): IF either current serving MSC is not USSD capable, OR IF the temporary routing address is not current, OR IF the MS is reported as inactive: IF the SMS_NotificationIndicator parameter was present in the SMSRequest INVOKE and the SMS_NotificationIndicator indicates Do not notify when available: Include the SMS_AccessDeniedReason parameter set to indicate Unavailable.
1-1-3-3-1
1-1-3-3-1-1 1-1-3-3-2 1-1-3-3-2-1 1-1-3-3-2-1-1
1-1-3-3-2-2 1-1-3-3-2-2-1
1-1-3-3-2-3 1-1-3-3-2-4 1-1-3-3-3 1-1-3-3-4 1-1-3-3-5 1-1-3-4 1-1-3-4-1 1-1-3-4-2 1-1-3-4-3 1-1-3-5 1-1-4 1-1-5 1-1-5-1 1-1-5-1-1
1-1-5-1-1-1
49
X.S0065 v1.0
USSD
1-1-5-1-2 1-1-5-1-2-1 1-1-5-1-2-1-1
ELSE: IF the USSD Delivery Pending Flag for this MS is not already set: Set the USSD Delivery Pending Flag for this MS, storing the routing address of the USSD Gateway from which the SMSRequest INVOKE was received. ELSE: Replace the routing address previously stored with the USSD Delivery Pending Flag for this MS with the routing address of the USSD Gateway from which the SMSRequest INVOKE was received. ENDIF. Include the SMS_AccessDeniedReason parameter set to indicate Postponed. ENDIF. ELSE: Include the SMS_Address parameter set to the current address for the MS. ENDIF. Send a RETURN RESULT. Exit this task. ENDIF. IF the teleservice indicated by the SMS_TeleserviceIdentifier parameter is unknown or is not supported: Include the SMS_AccessDeniedReason parameter indicating Invalid: ENDIF.
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-1-5-1-2-2 1-1-5-1-2-2-1
1-1-5-1-2-3 1-1-5-1-2-4 1-1-5-1-3 1-1-5-2 1-1-5-2-1 1-1-5-3 1-1-5-4 1-1-5-5 1-1-6 1-1-7 1-1-7-1 1-1-8 1-2 1-2-1 1-2-1-1 1-2-2 1-2-2-1 1-2-3 1-2-3-1 1-2-4 1-3 1-4 1-4-1 1-4-2 1-4-2-1 1-4-3 1-5 ENDIF.
ELSEIF TDMA service: IF the addressed MS is not known, OR IF the MS is known, but is not authorized for SMS: Include the SMS_AccessDeniedReason parameter set to Denied. ELSEIF (the teleservice indicated by the SMS_TeleserviceIdentifier parameter is unknown or is not supported): Include the SMS_AccessDeniedReason parameter set to Invalid. ELSEIF the SMS_TeleserviceIdentifier is not supported: Include the SMS_CauseCode parameter set to Invalid Teleservice ID. ENDIF. IF the temporary SMS routing address is current (as determined by the HLR, e.g., some time between never to until revoked) for the addressed MS: Include the SMS_Address parameter set to the current SMS address for the MS. IF the ElectronicSerialNumber parameter was not received: Include the ElectronicSerialNumber parameter set to identify the MS. ENDIF. ELSEIF the addressed MS is able to receive SMS messages (e.g., MS is registered to an SMS capable system), but the SMS address is not current or the MS is reported as inactive:
50
USSD
X.S0065 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-5-1 1-5-2 1-5-3 1-5-4 1-5-5 1-5-6 1-5-6-1 1-5-6-2 1-5-6-2-1 1-5-6-3 1-5-6-3-1 1-5-6-3-2 1-5-6-3-3 1-5-6-4 1-5-7 1-5-7-1 1-5-7-2 1-5-7-3 1-5-7-4 1-5-8 1-5-8-1 1-5-8-2 1-5-8-3 1-5-9 1-6 1-6-1
Relay all parameters received in the SMSRequest INVOKE. Include the ElectronicSerialNumber parameter for the addressed MS. Send an SMSRequest INVOKE to the VLR that is currently serving the indicated MS. Start the SMS Request Timer (SRT). WAIT for an SMS Request Response. WHEN a RETURN RESULT is received: Stop timer (SRT). IF the message can be processed: Relay all received parameters. ELSE (message cannot be processed): Execute Local Recovery Procedures task (see Part 630, sec. 5.1 [X.S0004-630] Section 5.1). Set the SMS Delivery Pending Flagfor this MS Include the SMS_AccessDeniedReason parameter set to Postponed. ENDIF. WHEN a RETURN ERROR or REJECT is received: Stop timer (SRT). Execute Local Recovery Procedures task (see Part 630, sec. 5.1 [X.S0004-630] Section 5.1). Set the SMS Delivery Pending Flag for this MS. Include the SMS_AccessDeniedReason parameter set to Postponed. WHEN timer (SRT) expires: Execute Local Recovery Procedures task (see Part 630, sec. 5.1 [X.S0004-630] Section 5.1). Set the SMS Delivery Pending Flag for this MS. Include the SMS_AccessDeniedReason parameter set to Postponed. ENDWAIT. ELSE (the MS is not registered to an SMS capable system or the MS is registered to an SMS incapable system): IF the SMS_NotificationIndicator parameter was present in the SMSRequest INVOKE and the SMS_NotificationIndicator indicates Do not notify when available Include the SMS_AccessDeniedReason parameter set to Unavailable. ELSE: Set the SMS Delivery Pending Flag for this MS Include the SMS_AccessDeniedReason parameter set to Postponed. ENDIF. ENDIF. Send a RETURN RESULT.
1-6-1-1 1-6-2 1-6-2-1 1-6-2-2 1-6-3 1-7 1-8 2 2-1 2-2
ELSE (message cannot be processed): Include the Error Code parameter set to the proper value (see the following table). Send a RETURN ERROR.
51
X.S0065 v1.0
USSD
3 4
ENDIF. Exit this task.
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
52
USSD
X.S0065 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
Table 1
HLR SMSRequest Response
Problem Detection and Recommended Response from the HLR towards the requesting MC RETURN ERROR Error Code UnrecognizedMIN UnrecognizedESN PROBLEM DEFINITION The supplied MobileIdentificationNumber parameter is within the HLRs range of MINs, but no record exists. An HLR record exists for the supplied MSID parameter, but the ElectronicSerialNumber parameter supplied does not match the stored value. The supplied MSID parameter is not in the HLRs range of MSIDs or the supplied MDN parameter is not in the HLRs range of MDNs. (suspect routing error). A required HLR resource (e.g., internal memory record, HLR is fully occupied) is temporarily not available (e.g., congestion). The requested MAP operation is recognized, but not supported, by the receiving HLR, or the requesting functional entity is not authorized. Note: It is recommended that a HLR support SMSRequest transactions. This response may have been originated by the serving system. ParameterError A supplied parameter has an encoding problem (e.g., the supplied MobileIdentificationNumber parameter digit values do not meet the BCD specification). Note: Include the Parameter Identifier in question as the FaultyParameter parameter. SystemFailure A required resource (e.g., data base access, functional entity) is not presently accessible due to a failure. Human intervention may be required for resolution. Note: This response may have been originated by the serving system. UnrecognizedParameterValu e A supplied parameter value is unrecognized or has nonstandard values. Note: Include the Parameter Identifier in question as the FaultyParameter parameter. MissingParameter An expected, or required, optional parameter (e.g., SMS_NotificationIndicator) was not received. The HLR has activity for the supplied MSID parameter that requires the ElectronicSerialNumber parameter to be supplied before a SMSRequest transaction can be successfully completed, the ElectronicSerialNumber parameter was not supplied. Note: Include the Parameter Identifier in question as the FaultyParameter parameter. UnrecognizedIMSI/TMSI The supplied IMSI parameter is within the HLRs range of IMSIs, but no record exists
ID/HLRMismatch
ResourceShortage OperationNotSupported
53
X.S0065 v1.0
USSD
RETURN RESULT SMS_AccessDeniedReason Denied
Note: Only RETURN RESULT clarification have been included.
operations
needing
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
An HLR record exists for the supplied MSID parameter, but a SMS routing address to the supplied MIN or IMSI has been permanently denied (e.g., Delinquent Account, Stolen Unit, Duplicate Unit, Invalid ESN, Unassigned directory number, Vacation disconnect); avoid future SMS transactions to the supplied MSID (ESN). An HLR record exists for the supplied MSID, but a SMS routing address to the supplied MIN or IMSI has been temporarily denied (e.g., no routing address, MS is busy, MS is not registered, No Page Response, MS is unavailable, MS is inactive, other temporary SMS delivery trouble). Also when the Serving VLR (or other functional entity) responded OperationNotSupported or did not respond. The HLR will notify the requesting MC when SMS delivery to the supplied MSID can be resumed. An HLR record exists for the supplied MSID parameter but a SMS routing address to the supplied MIN or IMSI has been temporarily denied (e.g., no routing address, MS is busy, MS is not registered, No Page Response, MS is unavailable, MS is inactive, other temporary SMS delivery trouble). Also when the Serving VLR (or other functional entity) responded OperationNotSupported or did not respond. The HLR will not notify the requesting MC when SMS delivery to the supplied MSID can be resumed. The teleservice indicated by the SMS_TeleserviceIdentifier parameter is unknown or is not supported.
Postponed
Unavailable
Invalid
54

USSD Call Flow

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

USSD Call Flow

Uploaded by

Copyright:

Available Formats

3GPP2 X.S0065 v1.

Unstructured Supplementary Service Data (USSD)

3GPP2 X.S0065 v1.0

Unstructured Supplementary Service Data (USSD)

Protocol procedures ................................................................................................................................ 20

Requirements for mobile station and USSD Gateway ............................................................. 20

This page is intentionally left blank.

Applications Interface MS USSD Client MSC USSD GW

Architecture for handling of USSD

1.3 Normative References

Definitions, Symbols and Abbreviations

Symbols and Abbreviations

2 Definitions, Symbols and Abbreviations

3.1 Information flows and functions

3.1 Information flows and functions

Network initiated USSD

Information flows and functions

4 Network initiated USSD

4.1 Handling of network initiated USSD

TRAFFIC CHANNEL TORN DOWN 21

Information flow for network initiated USSD session

4.2 Information flows and functions

4 Network initiated USSD

4 Network initiated USSD

4.2 Information flows and functions

Invoking USSDoperation from the USSD Gateway

4.2 Information flows and functions

4 Network initiated USSD

USSD operations at the MSC

USSD operations at the MS

4 Network initiated USSD

4.2 Information flows and functions

4 Network initiated USSD

Information flows and functions

5.1 Handling of an MS initiated USSD

Information flow for MS initiated USSD session

5.2 Information flows and functions

MS initiated USSD Request followed by an immediate USSD Release

5.2 Information flows and functions

5.2 Information flows and functions

MS initiated USSD Request after an intersystem handoff

5.2 Information flows and functions

Information flow for MS initiated USSD session after handoff

5.2 Information flows and functions

5.2 Information flows and functions

Handling of USSD Request at the MS

Handling of USSD request at the MSC

5.2 Information flows and functions

Processing the USSD Request at the USSD Gateway

Network Signaling Protocol

Timer: SFT Reference [X.S0004520] 1.3.2.1 [X.S0004520] 1.3.2.1 Notes

[X.S0004540] 2.129 [X.S0004540] 2.233

7.1 Editorial Conventions

7 Network Signaling Protocol

7 Network Signaling Protocol

7.2 MAP operations

[X.S0004540] 2.233 [X.S0004540] 2.234

Timer: SBT Reference [X.S0004520] 1.3.2.1 [X.S0004520] 1.3.2.1 Notes

[X.S0004540] 2.129 [X.S0004540] 2.153 [X.S0004540] 2.233 h

7.2 MAP operations

7 Network Signaling Protocol

7 Network Signaling Protocol

7.2 MAP operations