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 should be directed to the 3GPP2 Secretariat Secretaria t at [email protected].. Requests to reproduce individual Organizational Partner's documents should be directed [email protected] to that Organizational Partner. See www.3gpp2.org for more information.

3GPP2 X.S0065 v1.0

Revision History Revision

Description of Changes

Date

Rev 0 v1.0

Initial publication

20 April 2012

3GPP2 X.S0065 v1.0

Revision History Revision

Description of Changes

Date

Rev 0 v1.0

Initial publication

20 April 2012

USSD

X.S0065 v1.0

Unstructured Supplementary Service Data (USSD)

1 2 3 4 5

TABLE OF CONTENTS

6 7

Table of Figures Figures ........................... .......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................ .......................iii .........iii

8 9

Table of Tables............................ ........................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................ ....................... ......... iv

10 11

Foreword Foreword ............................ ........................................... ............................ ........................... ............................ ............................. ............................. ............................ ............................ ............................ ................... ..... v

12 13 14

1

Introduction Introduction .......................... ......................................... ............................. ............................ ............................ ............................ ............................ ............................ ............................ ................. ... 1

15

1.1

Scope............... Scope............................. ............................. ............................. ............................ ............................ ............................ ............................ ............................ ........................ .......... 1

16

1.2

Requirements Language........... .......... ........... .......... ........... .......... ........... .......... ........... .......... .... 1

1.3

Normative References .......... ........... .......... ........... .......... ........... .......... ........... .......... .......... ........ 2

1.4

Informative References .............................................................................................................. 2

17 18 19 20 21

2

22

Definitions, Symbols and Abbreviations .................................................................................................. 3 2.1

23 24

Definitions Definitions ............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ ................. ... 3 2.1.1 Symbols and Abbreviations ......................................................................................... 3

25 26

3

27

MS registration registration............................ ........................................... ............................. ............................ ............................ ............................ ............................ ............................ ........................ .......... 4 3.1

28 29 30 31

4

32 33 34

Network initiated USSD.... .......... ........... .......... ........... .......... ........... .......... ........... .......... .......... ........... .... 6 4.1

Handling of network initiated USSD ......................................................................................... 6

4.2

Information flows and functions ................................................................................................ 6 4.2.1 Information 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

4.3

Handoff Handoff ............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ .................... ...... 11

35 36 37 38 39 40

Information flows and functions ................................................................................................ 4 3.1.1 MS initiated initiated registration registration ............................ .......................................... ............................ ............................ ............................ ........................ ..........4

41 42

5

43 44 45

MS initiated initiated USSD......................... ....................................... ............................ ............................ ............................ ............................ ............................ ............................ .................... ...... 12 5.1

Handling of an MS initiated USSD .......... .......... ........... .......... .......... ........... .......... ........... ....... 12

5.2

Information flows and functions .............................................................................................. 12 5.2.1 Information 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 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

5.3

Handoff Handoff ............................ .......................................... ............................ ............................ ............................ ............................ ............................ ............................ .................... ...... 20

46 47 48 49 50 51 52 53 54 55 56 57 58

6

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

59 60

i

Table of Contents

X.S0065 v1.0

6.1

USSD

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

1 2

7

Network Signaling Protocol ................. .................................................................................................. 21

3 4

7.1

Editorial Conventions .............................................................................................................. 21

7.2

MAP operations ....................................................................................................................... 21 7.2.1 Operation definitions ................................................................................................. 21 7.2.1.1 SMSDeliveryForward ..........................................................................21 7.2.1.2 SMSDeliveryBackward ........................................................................23

6

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

11

7.3

7.4

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

5

7 8 9 10

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 Contents

ii

USSD

1 2

X.S0065 v1.0

TABLE OF FIGURES

3 4 5 6 7 8 9

Figure 1 Figure 2 Figure 3 Figure 4 Figure 5

10 11

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

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

iii

Table of Figures

X.S0065 v1.0

USSD

1

TABLE OF TABLES

2 3

Table 1

HLR SMSRequest Response ............................................................................................ 53

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

FOREWORD

4 5

(This Foreword is not part of this Specification.)

6 7 8 9

This document was prepared by the Third Generation Partnership Project 2 (3GPP2) TSG-X Working Group. This document is a new specification.

10 11 12 13

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:

14 15 16 17

X.S0065-000-X-n where:

18 19



20

X: a numerical or uppercase alphabetic character [A, B, C, …] that indicates the revision level;

21 22



n: a numeric string [1, 2, 3, …] that indicates the point release level.

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

v

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

1

Introduction

4

This specification is for Unstructured Supplementary Service Data (USSD) Support.

5 6 7 8

1.1

Scope

9

The Unstructured Supplementary Service Data (USSD) mechanism enables a Mobile Station (MS) and Public Land Mobile Network (PLMN) operator defined application servers to communicate.

10 11 12 13 14

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.

15 16 17 18 19

Application Server

20 21 22 23 24

Applications Interface

25 26

MS

27

MSC USSD GW

28 29

USSD Client

30 31 32 33

Figure 1

34

Architecture for handling of USSD

35

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.

36 37 38 39 40

This document also defines architecture requirements (stage 2) and the protocol details (stage 3) of the USSD.

41 42 43 44 45

1.2

Requirements Language

46

“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.

47 48 49 50 51 52 53 54 55 56 57 58 59 60

1.1 Scope

1

1 Introduction

X.S0065 v1.0

1.3

USSD

1

Normative References

2

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.

3 4 5 6 7

[A.S0013]

3GPP2: A.S0013-D v3.0; 3GPP2 Interoperability Specification (IOS) for cdma2000 Access Network Interfaces – Part 3 Features; May 2011.

8 9 10

[C.S0105]

3GPP2: C.P0105 v0.02, Unstructured Supplementary Service Data (USSD) Service Options for Spread Spectrum Systems: Service Options 78 and 79; April 2012.

11 12 13

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 Editor’s Note is removed, the inclusion of the above document is for informational purposes only.

14 15 16 17

[X.S0002]

3GPP2: X.S0002-0 v2.0, MAP Location Services Enhancements; May 2006.

[X.S0004-520]

3GPP2: X.S0004-520-E v2.0, Mobile Application Part (MAP) – TCAP Application Signaling Protocols; July 2007.

19

3GPP2: X.S0004-540-E v2.0, Mobile Application Part (MAP) – Operations Signaling Protocols; July 2007.

22

[X.S0004-540]

18

20 21

23 24

[X.S0004-550]

3GPP2: X.S0004-550-E v4.0, Mobile Application Part (MAP) – Parameters Signaling Protocols; January 2010.

25 26 27

[X.S0004-551]

3GPP2: X.S0004-551-E v1.0, Mobile Application Part (MAP) – Parameter Type Signaling Protocols; March 2004.

28 29 30

[X.S0004-630] [X.S0004-640]

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.

31 32 33 34 35

[X.S0004-641]

3GPP2: X.S0004-641-E v2.0, Mobile Application Part (MAP) – SMS ; July 2007.

36

[X.S0004-691]

3GPP2: X.S0004-691-E v3.0, Mobile Application Part (MAP) – Annexes for the 6XX Series ; July 2007.

38

37

39 40

[TS24.080]

3GPP: TS 24.080, Mobile radio interface layer 3 supplementary services specification; format and encoding (Release 10); March 2011.

41 42 43

[TS22.030] [TS23.090] [TS24.010]

3GPP: TS 22.030, Man-Machine Interface (MMI) of the User Equipment (UE) (Relea se 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 l ayer 3 supplementary services specification; General aspects (Release 10); June 2011.

44 45 46 47 48 49 50 51 52

1.4

53

Informative References

54 55

None

56 57 58 59 60

1 Introduction

2

1.3 Normative References

USSD

1 2

X.S0065 v1.0

2

Definitions, Symbols and Abbreviations

2.1

Definitions

3 4 5 6 7

USSD Request

8 9

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.

10 11 12 13 14

USSD Response

15 16

A response to a USSD Request a USSD Notify.

17 18

USSD Notify

19 20

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.

21 22 23 24

USSD operation

25 26

A USSD Request or a USSD Notify, see [TS23.090].

27 28

USSD session

29 30

A set of USSD messages that all share the same session identifier.

31 32 33

USSD Release

34

A message that ends the USSD session. This message is equivalent to the RELEASE COMPLETE, see [TS24.080].

35 36 37 38 39

2.1.1

Symbols and Abbreviations

40

MMI USSD USSD GW ADDS DBM IOS

41 42 43 44 45 46 47

Man Machine Interface Unstructured Supplementary Service Data USSD Gateway Application Data Delivery Service Data Burst Message Interoperability Specification

48 49 50 51 52 53 54 55 56 57 58 59 60

2.1 Definitions

3

2 Definitions, Symbols and Abbreviations

X.S0065 v1.0

USSD

1

3

2

MS registration

3 4 5

3.1

6

Information flows and functions

7 8

3.1.1

9

MS initiated registration

10

The information flow in Figure 2 is for a mobile initiated registration on a Serving MSC that supports USSD functionality. Serving Network

11 12 13 14

Home Network

15 16 17 18

MS

BS

19

HLR/ AC

MSC

20 21 22 23

AIR: Registration Message

24

1

25 26

IOS: LOCATION UPDATING REQUEST

27

2

28 29

MAP: AUTHREQ (MIN, AUTHR, RAND )

30

3

31 32

MAP: authreq

33

4

34 35

MAP: REGNOT (MIN)

36

5

37 38 39

MAP: regnot (VLR Profile ) 6

40 41 42

IOS: LOCATION UPDATING ACCEPT 7

43 44 45

AIR: Registration Accepted Order 8

46 47 48

Figure 2

Information flow for MS initiated registration to MSC supporting USSD

49 50 51

1.

The MS initiates a registration operation by sending the Registration Message to the BS.

52 53 54

2.

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.

55 56 57 58 59 60

3 MS registration

4

3.1 Information flows and functions

USSD

1

X.S0065 v1.0

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).

4.

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.

5.

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.

6.

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.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23

If the HLR determines that authorization cannot be granted to the MS the RegistrationNotification RETURN RESULT will contain the AUTHDEN parameter.

24 25 26 27

7.

The MSC sends the Location Updating Accept message to the BS to indicate that the Location Updating Request message has been pr ocessed.

8.

The BS transmits a Registration Accepted Order to the MS to acknowledge the registration explicitly.

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

3 MS registration

X.S0065 v1.0

4

USSD

1

Network initiated USSD

2 3 4

4.1

Handling of network initiated USSD

5 6

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.

7 8 9 10 11 12 13 14

4.2

15


16 17

4.2.1

18

Information flows

19

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.

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

6

4.1 Handling of network initiated USSD

USSD

X.S0065 v1.0

1 2 3

Serving Network

4

Home Network

5 6

MS

BS

MSC

HLR

7

USSD GW

8

MAP: SMSREQUEST (MDN or IMSI)

9

1

10

MAP: smsrequest(SMS_Address )

11

2

12

MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request or USSD Notify) )

13

3

14 15

TRAFFIC CHANNEL ESTABLISHED 4

16 17

IOS: ADDS DELIVER (ADDS User Data=USSD DBM) 5

18 19

AIR: USSD Data Burst Message (USSD Request or USSD Notify)

20

22

6

SMT

21

AIR: Layer 2 Ack 7

23

IOS: ADDS DELIVER ACK

24

8

25 26

MAP: smdpp 9

27 28 29

AIR: USSD Data Burst Message (USSD Response) 10

30 31

AIR: Layer 2 Ack 11

32 33

IOS: ADDS DELIVER (ADDS User Data=USSD DBM)

12

34 35

MAP: SMDPP (SMS_BearData=USSD DBM (USSD Response) )

36 37

SMT

MAP: smdpp

38

13

14

39

MAP: SMDPP (SMS_BearData=USSD DBM (USSD Release) )

40

15

41 42

IOS: ADDS DELIVER (ADDS User Data=USSD Release) 16

43 44 45

AIR: USSD Data Burst Message (USSD Release) 17

46 47

SMT AIR: Layer 2 Ack

18

48 49


19

50 51

MAP: smdpp

20

52 53 54

TRAFFIC CHANNEL TORN DOWN 21

55 56 57 58

Figure 3

Information flow for network initiated USSD session

59 60


7


X.S0065 v1.0

USSD

1.

If the USSD GW does not have the address of the MSC currently serving the MS, it sends a SMSREQ toward the HLR.

1 2 3

2.

If the HLR has the current address of the indicated MS-based USSD Client, the HLR sends a smsreq to the requesting USSD GW.

4 5 6

3.

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.

7 8 9 10 11

4.

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 addr ess 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.

12 13 14 15 16 17

If the subscriber is not authorized, the MSC sends a cause code in the SMDPP (see step 9). 5.

6.

7.

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.

18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

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.

35

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.

42

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.

46

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.

52

8.

9.

36 37 38 39 40 41

43 44 45

47 48 49 50 51

53 54

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.

55 56 57 58 59 60


8


USSD

X.S0065 v1.0

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.

1 2 3 4 5

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.

6 7 8 9

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.

10 11 12 13

NOTE: If the USSD GW sends a USSD Noti fy (see step 3) then steps 4 through step 14 will not be repeated.

14 15 16

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.

17 18 19 20

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.

21 22 23 24 25 26

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.

27 28 29 30 31 32

18. The MS acknowledges delivery of the data burst message on the traffic channel with a Layer 2 Ack.

33 34 35

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.

36 37 38 39 40 41 42

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.

43 44 45

21. Anytime after step 17, the MS tears down the traffic channel.

46 47 48 49 50 51 52 53 54

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.

55 56 57 58

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

59 60


9


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.

1 2 3 4

If the application timer expires before a USSD Response has been received, the USSD GW shallend the USSD session.

5 6 7

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.

8 9 10 11

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.

12 13 14 15

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.

16 17 18 19 20

4.2.3

USSD operations at the MSC

21 22

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.

23 24 25 26 27 28 29

Upon receipt of a USSD Release the MSC shall send the USSD Release towards the MS.

30 31

4.2.4

32

USSD operations at the MS

33

An MS may receive a USSD operation (i.e., a USSD Request or a USSD Notify) from the USSD GW at any time.

34 35 36 37

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.

38 39 40

If a USSD operation requires MMI and MMI is not possible, the MS shall reject the USSD operation.

41 42 43 44

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].

45 46 47 48

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].

49 50 51 52

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.

53 54 55 56 57 58 59 60


10


USSD

X.S0065 v1.0

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.

1 2 3 4 5

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 TMB. 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.

6 7 8 9 10 11 12 13 14

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.

15 16 17 18

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.

19 20 21 22 23 24 25 26 27

4.3

Handoff

28

Inter-MSC handoff shall not have any impact on the USSD services.

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.3 Handoff

11


X.S0065 v1.0

5

USSD

1

MS initiated USSD

2 3 4

5.1

Handling of an MS initiated USSD

5 6

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.

7 8 9 10

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).

11 12 13

The USSD message may contain the USSD string, an alphabet indicator and a language indicator or may contain other data.

14 15 16 17

5.2

18


19 20

5.2.1

21

Information flows

22 23

5.2.1.1

MS initiated USSD Request

24 25

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.

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

Serving Network

4

Home Network

5 6

MS

BS

MSC

USSD

HLR

GW

7 8 9


10 11

AIR: USSD Data Burst Message (USSD Request) 2

12 13

AIR: Layer 2 Ack 3

14 15


16

MAP: SMDPP (SMS_BearData=USSD DBM (USSD Request) )

17

5

18

MAP: smdpp

19

SMT 6

20 21


22 23

7 IOS: ADDS DELIVER ACK (ADDS User Data=USSD DBM)

24 25 26

8 AIR: USSD Data Burst Message (USSD Release) 9

27 28

AIR: Layer 2 Ack

SMT 10

29


30

11

31

MAP: smdpp

32

12

33 34 35

TRAFFIC CHANNEL TORN DOWN

13

36 37 38

Figure 4

39

Information flow for MS initiated USSD session

40 41

1.

If the MS is not on a traffic channel, the MS sets up traffic channel as defined in [A.S0013].

2.

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].

3.

If a Layer 2 Ack was requested by the MS, the BS sends a Layer 2 Ack to the MS on the traffic channel.

4.

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.

5.

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

42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60


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.

1 2 3 4

NOTE: T here is no error message that i s sent back to the MS to infor m the USSD client that the USSD Request was rejected by the MSC.

5 6 7

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 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.

8 9 10 11 12 13

NOTE: The USSD GW can r equest further information from t he USSD client resulting in the USSD GW sending one or more USSD Requests within the same USSD session.

14 15 16

7.

8.

9.

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. 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.


17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34

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.

35

12. The MSC acknowledges the SMDPP INVOKE (step 7) by sending 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.

42

13. The MS releases the traffic channel. See the Call Clear via Clear Request (MS Initiated) informational flow in [A.S0013].

46

36 37 38 39 40 41

43 44 45

47 48

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

Serving Network

4

Home Network

5 6

MS

BS

MSC

USSD

HLR

GW

7 8

TRAFFIC CHANNEL ESTABLISHED

9

1

10 11

AIR: USSD Data Burst Message (USSD (USSD Request) 2

12 13

AIR: Layer 2 Ack 3

14 15


16


17

5

18

MAP: smdpp

19

SMT 6

20 21

AIR: USSD Data Burst Message (USSD (USSD Release)

22 23

7 AIR: Layer 2 Ack

24

8

25 26


9

27


28

10

29

MAP: smdpp

30

SMT 11

31 32

TRAFFIC CHANNEL TORN DOWN 12

33 34 35 36 37 38

Figure 5

Information flow for MS initiated USSD session which is immediately released by the MS

39 40

1.

If the MS is not on a traffic channel, the MS sets up traffic channel as defined in [A.S0013].

2.

The BS receives a traffic channel data burst message from an MS on the traffic channel with a burst type indicating USSD. USSD. The USSD DBM is constructed as defined in [C.S0105].

3.


4.

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. USSD.

5.

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

41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60


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.

1 2 3

6. NOTE: T here is no error message that i s sent back to the MS to infor m the th e USSD client that the USSD Request was rejected by the MSC.

4 5 6

7.

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 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.

7 8 9 10 11 12

8.

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].

13 14 15 16

9.


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. USSD.

17 18 19 20 21 22 23

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.

24

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.

30

13. The MS releases the traffic channel. See the Call Clear via Clear Request (MS Initiated) informational flow in [A.S0013].

34

25 26 27 28 29

31 32 33

35 36

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

Tandem Network

Serving Network

Anchor Network

2 3 4 5 6

MS

Serving MSC

BS

Tandem MSC

USSD GW

Anchor MSC

7 8 9


10 11

AIR: USSD Data Burst Message (USSD Request) 2

12 13

AIR: Layer 2 Ack

14

3 IOS: ADDS DELIVER (ADDS User Data=USSD DBM)

15

4 MAP: SMDBACK (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) )

16

5

17 18

MAP: SMDBACK (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) )

19 20

7

21

SMT

22 23

MAP: smdpp

9

25

MAP: smdback (ACK) 10

26

MAP: SMDPP (SMS_BearData=USSD DBM (USSD Response) )

27

11 MAP: SMDFWD (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) )

29 30

12 MAP: SMDFWD (ServiceIndicator=USSD, SMS_BearData=USSD DBM (USSD Request) ) 13

31


32

14

33 34 35

8

MAP: smdback (ACK)

24

28

6


AIR: USSD Data Burst Message (USSD Response) 15 SMT

AIR: Layer 2 Ack

36

16

37

IOS: ADDS DELIVER ACK 17

38 39

MAP: smdfwd (ACK) 18

40

MAP: smdfwd (ACK)

41

19

42

MAP: smdpp

43

20

44 45 46

Figure 6

Information flow for MS initiated USSD session after handoff

47 48

1.

MS is on a voice call and the traffic channel is established.

2.

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].

3.


4.

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

49 50 51 52 53 54 55 56 57 58 59 60


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.

1 2 3

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.

4 5 6 7 8

6.

The Tandem MSC forwards the SMDBACK INVOKE to the Anchor MSC.

7.

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.

9 10 11 12 13 14 15 16 17

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 r equest further information from t he 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.

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.

38 39

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.

40 41 42 43

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,

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

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.

1 2 3 4


5 6 7

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.

8 9 10 11 12 13 14

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.

15 16 17

19. The Tandem MSC forwards the SMDFWD RETURN RESULT to the Anchor MSC.

18 19

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.

20 21 22 23 24

5.2.2

Handling of USSD Request at the MS

25

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.

26 27 28 29 30 31 32 33 34 35

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.

36 37 38 39 40 41 42 43

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.

44 45 46 47 48 49 50 51 52 53 54 55 56 57

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.

58 59 60


19

5 MS initiated USSD

X.S0065 v1.0

5.2.4

USSD

1

Processing the USSD Request at the USSD Gateway

2

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.

3 4 5 6 7 8 9

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.

10 11 12 13

5.3

Handoff

14 15 16

Inter-MSC handoff shall not have any impact on the USSD services.

17 18

6

Protocol procedures

19 20 21

6.1

22

Requirements for mobile station and USSD Gateway

23 24

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].

25 26 27 28 29 30 31 32 33 34 35 36

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].

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

1 2

X.S0065 v1.0

7

Network Signaling Protocol

7.1

Editorial Conventions

3 4 5 6 7

The following editorial conventions are used for Section 7:

8 9



underline: is addition to pre-existing text from other specifications.



cross out: is deleted text to pre-existing text from other specifications.

10 11 12 13 14

7.2

MAP operations

15 16 17

7.2.1

Operation definitions

18 19 20 21 22 23 24 25 26

7.2.1.1

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.

27 28

The following table lists the valid combinations of invoking and responding FEs.

29

INVOKING FE

RESPONDING FE

Case 1

Anchor MSC

Serving MSC

Case 2

Anchor MSC

Tandem MSC

Case 3

Tandem MSC

Tandem MSC

Case 4

Tandem MSC

Serving MSC

30 31 32 33 34 35 36 37 38 39 40 41 42

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:

43 44 45

SMSDeliveryForward INVOKE Parameters

Timer: SFT

46 47

Field

Value

48

Identifier

SET [NATIONAL 18]

Length

variable octets

49 50 51

Type

Reference

M

[X.S0004520] 1.3.2.1

M

[X.S0004520] 1.3.2.1

52 53 54 55

Notes

Contents InterMSCCircuitID

M

[X.S0004540] 2.129

SMS_BearerData

M

[X.S0004540] 2.233

56 57 58 59 60

7.1 Editorial Conventions

21

7 Network Signaling Protocol

X.S0065 v1.0

USSD

1

SMS_TeleserviceIdentifier

M

[X.S0004540] 2.246

ElectronicSerialNumber

O

[X.S0004540] 2.112

b

[X.S0004540] 2.127

h

IMSI

O

2 3 4 5 6 7 8

MobileIdentificationNumber

O

[X.S0004540] 2.140

a, h

ServiceIndicator

O

6.3.1.1

i

11

SMS_ChargeIndicator

O

[X.S0004540] 2.235

c

12

[X.S0004540] 2.240

e

[X.S0004540] 2.241

b

9 10

13 14

SMS_OriginalDestinationAddress

O

SMS_OriginalDestinationSubaddress

O

16

O

[X.S0004540] 2.242

f

SMS_OriginalOriginatingSubaddress

O

[X.S0004540] 2.243

b

[X.S0004540] 2.244

g

O

17 18

SMS_OriginalOriginatingAddress

SMS_OriginatingAddress

15

19 20 21 22 23 24 25 26

Notes:

27 28

a.

Include to identify the destination MS.

b.

Include if applicable.

c.

Include if applicable. If not received, charge message originator.

d.

Intentionally left for future modifications.

e.

Include to identify the SME to which the short message is destined (e.g., the MDN, for termination to the MS-based SME).

29 30 31 32 33 34 35 36 37

Include to identify the SME from which the short message originated (e.g., the MDN, if originated by an MS-based SME).

38

g.

Include if the MC address may be sent to the MS.

41

h.

Include if available. At least one of these parameters should be present.

i.

Include for CDMA USSD. When ServiceIndicator is included, the length of the SMS_TeleserviceIdentifier is set to 0.

f.

39 40

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:

49 50 51 52 53

SMSDeliveryForward RETURN RESULT

54

Field

Value

Identifier

SET [NATIONAL 18]

Type

Reference

M

[X.S0004520]1.3.2.2

Notes

55 56 57 58 59 60


22

7.2 MAP operations

USSD

1

X.S0065 v1.0

Length

2

variable octets

[X.S0004520] 1.3.2.2

M

3 4

Contents

5

SMS_BearerData

M

[X.S0004540] 2.233

a

SMS_CauseCode

M

[X.S0004540] 2.234

b

6 7 8 9 10 11

Notes:

12 13 14 15

a.

Include for positive acknowledgments, when applicable.

b.

Include for all negative acknowledgments.

16 17 18 19 20 21 22 23 24 25 26

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.

27

INVOKING FE

RESPONDING FE

Case 1

Serving MSC

Anchor MSC

Case 2

Serving MSC

Tandem MSC

Case 3

Tandem MSC

Tandem MSC

Case 4

Tandem MSC

Anchor MSC

28 29 30 31 32 33 34 35 36 37 38 39 40

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:

41 42 43 44 45 46

SMSDeliveryBackward INVOKE Parameters Field

Value

Identifier

SET [NATIONAL 18]

Length

variable octets

47 48 49

Timer: SBT Type

Reference

M

[X.S0004520] 1.3.2.1

M

[X.S0004520] 1.3.2.1

50 51

Contents

52

InterMSCCircuitID

M

[X.S0004540] 2.129

MSID

M

[X.S0004540] 2.153

SMS_BearerData

M

[X.S0004540] 2.233

53 54 55 56 57 58

Notes

h

59 60

7.2 MAP operations

23


X.S0065 v1.0

USSD

1

SMS_TeleserviceIdentifier

M

[X.S0004540] 2.246

ElectronicSerialNumber

O

[X.S0004540] 2.112

a

2 3

5

ServiceIndicator

O

6.3.1.1

i

SMS_ChargeIndicator

O

[X.S0004540] 2.235

b

SMS_DestinationAddress

O

[X.S0004540] 2.236

c

[X.S0004540] 2.240

d

[X.S0004540] 2.241

a

[X.S0004540] 2.242

e

SMS_OriginalDestinationAddress

O

4

6 7 8 9 10 11 12 13 14

SMS_OriginalDestinationSubaddress SMS_OriginalOriginatingAddress

O O

15 16 17 18

SMS_OriginalOriginatingSubaddress

O

[X.S0004540] 2.243

a

SMS_TransactionID

O

[X.S0004540] 2.248

g

19 20 21 22 23 24 25 26

Notes:

27

a.

Include if applicable.

b.

Include if applicable. If not received, charge message originator.

c.

Include if an MC address is specified by the originating SME.

31

d.

Include to identify the SME to which the short message is destined (e.g., the MDN, for termination to an MS-based SME).

33

28 29 30

32

34 35

e.

Include to identify the SME from which the short message originated (e.g., the MDN, if originated by an MS-based SME).

36 37 38

f.

Intentionally left for future modifications.

g.

Include if TDMA to identify an MS based SMS originating SME.

h.

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.

42

Include for CDMA USSD. When ServiceIndicator is included, the length of the SMS_TeleserviceIdentifier is set to 0.

46

i.

39 40 41

43 44 45

47 48 49

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:

Value

Identifier

SET [NATIONAL 18]

51 52 53 54

SMSDeliveryBackward RETURN RESULT Field

50

55

Type

Reference

M

[X.S0004520] 1.3.2.2

Notes

56 57 58 59 60


24

7.2 MAP operations

USSD

X.S0065 v1.0

1

Length

2

variable octets

[X.S0004520] 1.3.2.2

M

3 4

Contents

5

SMS_BearerData

O

[X.S0004540] 2.233

a

SMS_CauseCode

O

[X.S0004540] 2.234

b

SMS_TransactionID

O

[X.S0004540] 2.248

c

6 7 8 9 10 11 12 13 14

Notes:

15 16 17 18 19 20

a.

Include for positive acknowledgments, when applicable.

b.

Include for all negative acknowledgments.

c.

Include if TDMA to identify an MS based SMS originating SME.

21 22 23

7.3

MAP parameters

24 25 26

7.3.1

Parameter definitions

27 28

7.3.1.1

ServiceIndicatior

29 30 31 32 33

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.

34 35

Field

36 37

Value

40 41

Reference

Identifer

ServiceIndicator IMPLICIT OCTET STRING

M

[X.S0004-550]

Length

variable octets

M

[X.S0004-550]

38 39

Type

Contents

42

H

43

G

44

F

E

D

C

B

A

46

48

Octet

Service

1

  

n

45

47

Notes

Notes

a

Notes: a.

49

Ignore extra octets, if received. Send only defined (or significant) octets

50 51 52 53 54

Service (octet 1)

55 56 57 58

Decimal Value

Meaning

0

Undefined Service.

59 60

7.3 MAP parameters

25


X.S0065 v1.0

USSD

1

1

CDMA OTASP Service.

2

TDMA OTASP Service.

3

CDMA OTAPA Service.

4

See [X.S0002]

5

See [X.S0002]

6

See [X.S0002]

7

USSD

values through 223

Reserved. Treat the same as value 0, Undefined Service.

224 through 255

Reserved for IS-41 protocol extension. If unknown, treat the same as value 0, Undefined Service.

2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17

7.3.1.2

18

TransactionCapability

19

Note: This parameter definition is a modification of the “TransactionCapability” parameter definition in [X.S0004-550]. The TransactionCapability (TRA NSCAP) parameter indicates a system’s transaction capability at the current time (i.e., this capability may change over time).

20 21 22 23 24 25 26

Field

Value

Identifer Length

Type

Reference

TransactionCapability IMPLICIT OCTET STRING

M

[X.S0004-550]

2 or more octets

M

Notes

27 28 29 30 31

[X.S0004-550]

32

Contents

33

H

G

F

E

D

C

B

A

Octet

Notes

34 35

NAMI

NDSS

UZCI

SPINI

OTAP A

S&R

WADD R

TL

RUI

ANN

BUSY

PROF

Multiple Terminations

1

36 37

2

38 39

Reserved

USSD

• • •

MX

ANCA P

Rsvd

3

a

40 41

N

b

42 43 44

Notes: a

45

Reserved bits shall be ignored on receipt and set to zero on sending.

46 47

b Ignore extra octets, if received. Send only defined (or significant) octets.

48 49 50

Profile (PROF) (octet 1, bit A) Value 0 1

51 52

Meaning

53

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.

54 55 56 57 58 59 60


26

7.3 MAP parameters

USSD

X.S0065 v1.0

1 2

Busy Detection (BUSY) (octet 1, bit B)

3

Value

4 5 6

0

The system is not capable of detecting a busy condition at the current time.

1

The system is capable of detecting a busy condition at the current time.

7 8

Meaning

9 10 11

Announcements (ANN) (octet 1, bit C)

12

Value

13

Meaning

14 15

0

The system is not capable of honoring the AnnouncementList parameter at the current time.

1

The system is capable of honoring the AnnouncementList parameter at the current time.

16 17 18 19 20

Remote User Interaction (RUI) (octet 1, bit D)

21 22

Value

Meaning

23 24 25 26 27 28

0

The system is not capable of interacting with the user.

1

The system is capable of interacting with the user.

Subscriber PIN Intercept (SPINI) (octet 1, bit E)

29

Value

30 31

Meaning

0

The system is not capable of supporting local SPINI operation at the current time.

1

The system is capable of supporting local SPINI operation.

32 33 34 35 36

UZCapabilityIndicator (UZCI) (octet 1, bit F)

37

Value

38 39 40 41

Meaning

0

The system is not User Zone capable at the current time.

1

The system is User Zone capable at the current time.

42 43

NDSS Capability (NDSS) (octet 1 bit G)

44 45

Value

Meaning

46 47 48 49 50 51

0

Serving System is not NDSS capable.

1

Serving System is NDSS capable.

NAME Capability Indicator (NAMI) (octet 1 bit H)

52

Value

53 54

Meaning

0

The system is not CNAP/CNAR capable.

1

The system is CNAP/CNAR capable.

55 56 57 58 59 60

7.3 MAP parameters

27


X.S0065 v1.0

USSD

1

Multiple Terminations (octet 2, bits A-D)

2 3

Value 0 1 through 15

Meaning

4

The system cannot accept a termination at this time (i.e., cannot accept routing information). The system supports the number of call legs indicated.

5 6 7 8 9

TerminationList (TL) (octet 2, bit E)

10 11

Value

12

Meaning

13

0 1

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.

0

15 16 17 18 19

WIN Addressing (WADDR) (octet 2, bit F) Value

14

20

Meaning

21

The system is not capable of supporting the TriggerAddressList parameter.

23

22

24 25

1

The system is capable of supporting the TriggerAddressList parameter.

Lower Layer Segmentation and Reassembly (S&R) (octet 2, bit G) Value

26 27 28 29 30

Meaning

31

0

The system is not capable of supporting lower layer segmentation and reassembly, (S&R)

1

The system is capable of supporting lower layer segmentation and reassembly, (S&R).

32 33 34 35 36 37

Over the Air Parameter Administration OTAPA (octet 2, bit H)

38 39

Value 0 1

Meaning

40

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.

41 42 43 44 45 46

Announcement Capabilities(ANCAP) (octet 3, bit B)

47 48

Value

Meaning

49 50

0

1

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.

51 52 53 54 55 56 57 58 59 60


28

7.3 MAP parameters

USSD

X.S0065 v1.0

1

MIN Extension(MX) (octet 3, bit C)

2 3

Value

4 5 6 7

Meaning

0

The system does not require the MIN Extension for this MS.

1

The system requires that the MIN Extension for this MS be transmitted.

8 9

Unstructured Supplementary Service Data (USSD) (octet 3, bit D)

10 11

Value

12

Meaning

13 14

0

The system is not capable of supporting the CDMA Unstructured Supplementary Service Data.

1

The system is capable of supporting the CDMA Unstructured Supplementary Service Data.

15 16 17 18 19 20 21 22 23 24 25 26 27 28 29

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 subscriber’s 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.

30 31

Profile

32

Type

Reference

Notes

AuthenticationCapability

O

[X.S0004550] 2.12

a

CallingFeaturesIndicator

O

[X.S0004550] 2.38

b

CarrierDigits

O

[X.S0004550] 2.47

c

CDMABandClass

O

[X.S0004550] 2.52

z

CDMABandClassList

O

[X.S0004550] 2.54

ad

CDMAServiceOptionList

O

[X.S0004550] 2.77

ab

DMH_AccountCodeDigits

O

[X.S0004550] 2.118

d

DMH_AlternateBillingDigits

O

[X.S0004550] 2.119

d

DMH_BillingDigits

O

[X.S0004550] 2.120

d

GeographicAuthorization

O

[X.S0004550] 2.132

e

33 34 35 36

Contents

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 MAP parameters

29


X.S0065 v1.0

USSD

MessageWaitingNotificationCount

O

[X.S0004550] 2.146

f

MessageWaitingNotificationType

O

[X.S0004550] 2.147

g

[X.S0004550] 2.149

x

[X.S0004550] 2.178

h

[X.S0004550] 2.179

I

MobileDirectoryNumber

O

OriginationIndicator

O

OriginationTriggers

O

8 9 10 11 12 13

PreferredLanguageIndicator

O

[X.S0004550] 2.189

k

[X.S0004550] 2.194

u, aa

14 15 16 17 18 19

QoSPriority

O

[X.S0004550] 2.196

y

RestrictionDigits

O

[X.S0004550] 2.216

l

[X.S0004550] 2.219

m

[X.S0004550] 2.255

n

[X.S0004550] 2.257

o

O

6 7

[X.S0004550] 2.181

RoutingDigits

4 5

O

O

2 3

PACAIndicator

PSID_RSIDList

1

20 21 22 23 24 25 26 27

SMS_OriginationRestrictions

O

SMS_TerminationRestrictions

O

29

O

[X.S0004550] 2.261

q

SPINITriggers

O

[X.S0004550] 2.262

r

[X.S0004550] 2.281

ac

O

30 31

SPINIPIN

TDMADataFeaturesIndicator

28

32 33 34 35 36 37 38

TerminationRestrictionCode

O

[X.S0004550] 2.291

s

TerminationTriggers

O

[X.S0004550] 2.293

T

39 40 41 42 43

TriggerAddressList

O

[X.S0004550] 2.296

w

UserGroup

O

[X.S0004550] 2.303

p

7.3.1.4

ae

44 45 46

USSDAddress

O

47 48 49 50 51 52

Notes:

53

a. Include if available. May not be received from systems that conform to revisions prior to IS-41-C.

54 55 56

b. Include to identify feature authorization and activity.

57 58

c. Include if preferred carrier is applicable and TransactionCapability supported.

59 60


30

7.3 MAP parameters

USSD

X.S0065 v1.0

d. Include if available for recording purposes (see DMH).

1 2

e. Include if available for certain authorization restricted areas.

3 4

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.

5 6 7

g. Include if Message Waiting Notification feature is active.

8 9

h. Include to indicate the type of calls allowed for origination service.

10

i. Include to indicate OriginationRequest triggers.

11 12

j. Include to identify the PACA feature.

13 14

k. Include to identify the Preferred Language feature.

15 16

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).

17 18 19 20 21 22

m. Include for special routing information.

23

n. Include for MS originated Short Message Service.

24 25

o. Include for MS terminated Short Message Service.

26 27

p. Include to specify the User Group allocation status.

28 29

q. Include if local SPINI operation supported.

30 31

r. Include to indicate SPINI triggers.

32

s. Include to indicate the type of call termination service.

33 34

t. Include to indicate the RedirectionRequest or TransferToNumberRequest triggers.

35 36

u. Include to indicate the list of acceptable PSIDs/RSIDs for the indicated MS.

37 38

v. Include to perform User Zone updates at the serving system.

39

w. Include to indicate active WIN triggers and associated addresses for service logic network elements.

40 41 42

x. Include if available.

43 44

y. Include if packet data services are applicable to indicate relative priority for purposes of radio resource allocation.

45 46 47

z. Include to indicate information for the current band in use.

48 49

aa. The PSID_RSIDList and UserZoneData parameters are mutually exclusive.

50

ab. Include to indicate preferred CDMA service options in descending order of preference.

51 52 53

ac. Include to indicate allowed TDMA data services.

54 55

ad. Include to indicate band classes supported.

56 57

ae. Include for USSD service.

58 59 60

7.3 MAP parameters

31


X.S0065 v1.0

7.3.1.4

USSD

1

USSDAddress

2

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.

3 4 5 6 7 8 9

7.3.1.4.1

USSDAddress parameter for BCD digits

10 11 12 13

Field

Value

Identifer Length

Type

Reference

Notes

USSDAddress IMPLICIT DigitsType

M

[X.S0004-550]

a

variable octets

M

14 15 16 17 18

[X.S0004-550]

19 20

Contents

21

H

G

F

E

D

C

B

A

22

Octet

Notes

Type of Digits

1

b

Nature of Number

2

c

3

d,e

27

4

f

29

23 24 25

Numbering Plan

Encoding Number of Digits

2nd BCD Digit

1st BCD Digit

5

4th BCD Digit

3rd BCD Digit

6

26

28

30 31 32 33

•

•

•

•

nth BCD Digit

•

•

•

n-1st BCD Digit

•

•

34 35

m

36 37

Notes: a.

38

Refer to the DigitsType parameter type see [X.S0004-551] Section 1.2 for notes and field encoding.

39 40 41

b.

Type of Digits is ignored on receipt.

42 43

c. Nature of Number shall be National .

44

d. Numbering Plan supported shall include include E.164, E.212, X.121, and Private numbering plan.

45

e.

Encoding shall be octet string for this parameter variant.

48

f.

The Number of Digits ranges from 0 to at least 15.

46 47

49

7.3.1.4.2

50 51

USSDAddress parameter for an IP address

52 53 54 55

Field Identifer

Value USSDAddress IMPLICIT DigitsType

Type

Reference

Notes

M

[X.S0004-550]

a

56 57 58 59 60


32

7.3 MAP parameters

USSD

1

X.S0065 v1.0

Length

2

variable octets

M

[X.S0004-550]

3

Contents

4 5

H

G

F

E

D

C

B

A

Octet

Notes

Type of Digits

1

b

Nature of Number

2

c

3

d,e

6 7 8 9 10

Numbering Plan

Encoding

11

MSB

12

4

13

5

IP Address

14

6

15 16

LSB

17

7

18

Notes:

19 20 21

a.


b.


22 23 24


25 26

d. Numbering Plan shall be SS7 PC and SSN for this parameter variant.

27 28

e.

29 30 31

7.3.1.4.3


USSDAddress Encoding for an ANSI SS7 Point Code Address

32 33 34

Field

35 36 37

Value

Reference

Notes a

Identifer


M

[X.S0004-550]

Length

variable octets

M

[X.S0004-550]

38 39

Type

40 41 42

Contents H

43

G

F

E

44 45 46

D

C

B

A

Octet

Notes

Type of Digits

1

b

Nature of Number

2

c

3

d,e

47

Numbering Plan

48 49 50 51 52 53 54

Encoding

Point code--Member Number

4

Point code--Cluster Number

5

Point code--Network Number

6

Subsystem Number

7

55 56 57

Notes: a.

58 59


60

7.3 MAP parameters

33


X.S0065 v1.0

USSD

b.

1


2


3 4

d. Numbering Plan shall be IP for this parameter variant. e.

5 6


7 8 9

7.3.1.4.4

USSDAddress Encoding for a Generic SS7 Point Code Address

10 11 12 13 14

Field

Value

Type

Reference

Notes a

Identifer


M

[X.S0004-550]

Length

variable octets

M

[X.S0004-550]

15 16 17 18 19 20 21

Contents

22

H

G

F

E

D

C

B

A

Octet

Notes

Type of Digits

1

b

Nature of Number

2

c

3

d,e

4

f

23 24 25

Numbering Plan

Encoding Point Code

27 28 29 30

5 6

Subsystem Number (SSN)

26

7

31 32 33 34 35

Notes: a. b.

36


37 38 39 40


41


42 43

d. Numbering Plan shall be SS7 PC and SSN for this parameter variant.

44 45

e.


f.

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 e nd of the point code up to and including bit H of Octet 6, should be set to 0.

46 47 48 49 50 51 52 53 54 55 56 57 58 59 60


34

7.3 MAP parameters

USSD

1 2

7.4

X.S0065 v1.0

MAP signaling procedures

3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18

7.4.1 7.4.1.1 7.4.1.1.1

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

IF the message can be processed:

1-1

19 20 21 22

IF the ServiceIndicator parameter set to either the CDMA OTASP Service or the CDMA OTAPA Service is received:

1-1-1 1-1-1-1

23 24 25

1-1-2

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:

26

1-1-2-1

CASE ActionCode OF:

27

1-1-2-2

Attach MSC to OTAF:

28 29

1-1-2-2-1

30 31

1-1-2-2-1-1

32 33 34

1-1-2-2-2

35 36

39

1-1-2-2-2-2

Send a RETURN RESULT.

1-1-2-2-3

41

1-1-2-3

43

1-1-2-3-1

44 45

1-1-2-4

46

1-1-2-4-1

47 48 49

1-1-2-4-1-1

50 51

ELSEIF the ServiceIndicator parameter is set to the CDMA OTAPA Service value: Include the SMS_CauseCode parameter set to indicate Unexpected parameter value.

40

42

Execute the “MSC Receiving SMDPP INVOKE to Attach with OTAF” task (see Part 640, sec. 43.3 [X.S0004-640], section. 43.3).

1-1-2-2-2-1

37 38

IF the ServiceIndicator parameter is set to the CDMA OTASP Service value:

1-1-2-4-2

52

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:

53 54

1-1-2-4-2-1

Include the SMS_CauseCode parameter set to indicate Unexpected parameter value.

1-1-2-4-2-2


55 56 57 58 59

1-1-2-4-3 1-1-2-5

ENDIF. Record NEWMSID:

60

7.4 MAP signaling procedures

35


X.S0065 v1.0

USSD

1-1-2-5-1

Execute the “MSC Receiving SMDPP INVOKE to Record NEW MSID” task (see Part 640, sec. 45.4 [X.S0004-640], section 45.4).

1 2 3

1-1-2-6

DEFAULT:

1-1-2-6-1

4

Include the SMS_CauseCode parameter set to indicate Unexpected parameter value.

1-1-2-6-2

8

ENDCASE.

1-1-3

ENDIF.

1-1-4

Exit this task.

9 10 11 12 13

1-2

ENDIF.

1-3

IF the ServiceIndicator parameter indicating USSD (Unstructured Supplementary Service Data) is received:

1-3-1

Execute the “MSC Receiving an SMDPP INVOKE for USSD Exchange” task (see Section 7.4.1.2.1).

1-3-2


1-3-3

Exit this task.

Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter.

1-6-2


1-6-3

Exit this task.

26

29 30 31 32 33

1-7

ENDIF.

1-8

IF the SMS_OriginatingAddress parameter is received:

34 35

Set the originatting address with the SMS_OriginatingAddress.

36 37

1-9

ENDIF.

1-10

IF the SMS_OriginalOriginatingAddress parameter is received:

38

Set the original originating address with the address in the received SMS_OriginalOriginatingAddressparameter. ELSE:

39 40 41 42 43

1-11-1

Include the SMS_CauseCode parameter set to Missing Expected Parameter.

1-11-2


1-11-3

Exit this task.

44 45 46 47 48

1-12

ENDIF.

1-13

IF the SMS_OriginalOriginatingSubaddress parameter is received:

49

Set the original originating subaddress with the address in the received SMS_OriginalOriginatingSubaddress parameter.

50 51 52 53

1-14

ENDIF

1-15

IF the BroadcastCategory parameter is received (indicating BTTC):

1-15-1-1

25

28


1-15-1

24

27

ELSE:

1-13-1

18

23

1-6-1

1-11

17

22

IF the SMS_OriginalDestinationAddress parameter is received:

1-10-1

16

21

1-5

1-8-1

15

20

ENDIF;

1-6

14

19

1-4 1-5-1

6 7


1-1-2-7

5

54

IF the BroadcastMessageStatus parameter indicates deletion is received: IF the BroadcastMessageIdentifier parameter is received:

55 56 57 58 59 60


36


USSD

X.S0065 v1.0

1-15-1-1-1

1

IF a broadcast message as indicated by the SMS_OriginalOriginatingAddress parameter and BroadcastMessageIdentifier parameter exists:

2 3 4 5

1-15-1-1-1-1

6

1-15-1-1-1-1-1

Wait for the broadcast process to be completed.

1-15-1-1-1-1-2

Delete the broadcast message.

7 8

IF the broadcasting process is ongoing at the MSC:

1-15-1-1-1-2

9 10

ELSE:

1-15-1-1-1-2-1

Delete the broadcast message immediately.

11

1-15-1-1-1-3

12

ENDIF.

1-15-1-1-2

13 14

ENDIF.

1-15-1-2

15

ELSE (deletion of a group of broadcast messages):

1-15-1-2-1

16

FOR each broadcast message that has matching SMS_OriginalOriginatingAddress and BroadcastCategory parameter values:

17 18 19

1-15-1-2-1-1

20

IF the broadcasting process is ongoing at MSC:

21

1-15-1-2-1-1-1

Wait for the broadcast process to be completed.

22

1-15-1-2-1-1-2

Delete the broadcast message.

23 24

1-15-1-2-1-2

25

1-15-1-2-1-2-1

26

ELSE: Delete the broadcast message immediately.

1-15-1-2-1-3

27

ENDIF.

1-15-1-2-2

28 29

ENDFOR.

1-15-1-3

ENDIF.

31

1-15-1-4


32

1-15-1-5

Exit this task.

30

33

1-15-2

ENDIF.

35

1-15-3

IF BroadcastMessageStatus parameter indicates replacement:

36

1-15-3-1

34

37 38 39

1-15-3-1-1

40

1-15-3-2

41 42

1-15-3-2-1

43

1-15-3-3

44

1-15-4

45 46

1-15-4-1

47 48

IF message as indicated by the SMS_OriginalOriginatingAddress parameter and BroadcastMessageIdentifier parameter exists: 1

Replace the old broadcast message with the received message . 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 br oadcast message.

1-15-5

ENDIF.

1-15-6

IF Broadcast Periodicity is requested for a new message and Broadcast Periodicity cannot be supported for this message by this MSC at this time:

49 50 51

1-15-6-1

52 53

Include the SMS_CauseCode parameter set to indicate Broadcast Periodicity Failure in MSC.

54 55 56 57 58 59

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 u nchanged if the BroadcastPeriodicity parameter is not received.

60


37


X.S0065 v1.0

USSD

1

1-15-7

ENDIF.

1-15-8


1-15-9

Process the broadcast message according to the B roadcastMessagePriority 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.

1-15-10

3

WHILE any additional broadcasts of this message are required (based on the BroadcastPeriodicity value for this message and the capabilities of the MSC):

1-15-10-1

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.

1-15-11

ENDWHILE.

1-15-12

Exit this task.


1-18-3

Exit this task.

1-20

IF an ElectronicSerialNumber parameter is received:

24 25 26

29 30

Set the ESN to the received ElectronicSerialNumberparameter.

31 32

1-21

ENDIF.

1-22

IF the destination MS is anchored by this MSC:

33 34

IF the MSC is allowed to terminate a short message to the destination MS according to the SMS_TerminationRestrictions parameter in the destination MS’s profile:

1-22-1-1-1-4-1

14

28

ENDIF.

1-22-1-1-1-4

13

27

1-19

1-22-1-1-1-3-1

12

23

1-18-2

1-22-1-1-1-3

11

22


1-22-1-1-1-2

10

21

1-18-1

1-22-1-1-1-1

9

20

ELSE:

1-22-1-1-1

8

19

Set the MSID to the received MSID parameter.

1-22-1-1

7

18

IF an MSID parameter is received:

1-22-1

6

17

1-17

1-20-1

5

16

ENDIF.

1-17-1

4

15

1-16

1-18

2

IF the MSC is currently the Serving MSC:

35 36 37 38 39

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).

40 41 42 43 44 45 46 47 48 49 50 51 52 53

ELSE:

54

Execute the “MSC Initiating SMD-REQUEST toward an MSBased SME” task (see Part 691, sec. 4 [X.S0004691], section 4).

55 56 57 58 59 60


38


USSD

1

X.S0065 v1.0

1-22-1-1-1-4-2

IF internal algorithms indicate that neighboring MSC(s) should be sent the SMS message:

2 3 4

1-22-1-1-1-4-2-1

FOR each applicable MSC:

5

1-20-1-1-1-4-2-1-1

Execute the “MSC Initiating InterSystem SMS Page” task (see Part 640, sec. 35.1 [X.S0004-640], section. 35.1).

6 7 8 9

1-22-1-1-1-4-2-2

10

1-22-1-1-1-4-3

11

1-22-1-1-1-5

12 13

1-22-1-1-2

14 15 16

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):

1-22-1-1-2-1

IF the SMS_NotificationIndicator parameter was present in the SMSDeliveryPointToPoint INVOKE and the SMS_NotificationIndicator indicates Do not notify when available:

17 18 19 20

1-22-1-1-2-1-1

Include the SMS_CauseCode parameter set to an appropriate value.

21 22 23

1-22-1-1-2-2

ELSE (notification was requested):

24

1-22-1-1-2-2-1

Set the SMS Delivery Pending Flag for this MS.

25

1-22-1-1-2-2-2

Include the SMS_CauseCode parameter set to SMS Delivery Postponed.

26 27 28 29 30

1-22-1-1-2-3 1-22-1-1-3

ENDIF. ELSE (the MS is not currently able receive an SMS message):

1-22-1-1-3-1

Include the SMS_CauseCode parameter set to Radio interface incompatibility.

31 32 33

1-22-1-1-4

34

1-22-1-2

35 36

Relay received parameters, except the SMS_ChargeIndicator parameter.

1-22-1-2-2

Execute the “MSC Initiating SMS Delivery Forward” task (see Part 641, sec. 2.1 [X.S0004-641], section 2.1).

39 40 41 42

ELSE (the MS has been handed off):

1-22-1-2-1

37 38

ENDIF.

1-22-1-3

ENDIF.

(At this point, message relaying had been postponed, denied, or attempted.)

43 44 45 46

1-22-1-4 1-22-1-4-1

47 48

1-22-1-4-1-1

49

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).

50 51 52 53 54

1-22-1-4-2 1-22-1-4-2-1 1-22-1-4-2-1-1

55 56

1-22-1-4-2-1-1-1

57 58 59

1-22-1-4-2-1-2

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):

60


39


X.S0065 v1.0

USSD

1-22-1-4-2-1-2-1

(Keep the MS awake for a while to receive another possible message.)

1 2 3

1-22-1-4-2-1-3

ENDIF.

4

1-22-1-4-2-2

ENDIF.

1-22-1-4-2-3

IF the SMS_MessageCount parameter was not received OR IF the received SMS_MessageCountparameter is zero:

1-22-1-4-2-3-1

5

Clear the SMS Delivery Pending Flag for this MS.

1-22-1-4-2-4

6 7 8 9 10

ENDIF.

11

1-22-1-4-3

ENDIF.

12

1-22-1-4-4

Relay the received parameters.

13

1-22-1-5

ELSE (an SMS_CauseCode has been included):

1-22-1-5-1

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):

1-22-1-5-1-1

Include the SMS_CauseCode parameter set to Network failure.

1-22-1-5-1-2

Relay the other received parameters.

1-22-1-5-2

14 15 16 17 18 19 20

ELSEIF the SMS_CauseCode was for a Destination resource shortage:

21 22

1-22-1-5-2-1

Relay all received parameters.

23

1-22-1-5-2-2

Clear the SMS Delivery Pending Flag for this MS.

24

1-22-1-5-3

ELSEIF the SMS_CauseCode was for a temporary condition:

1-22-1-5-3-1

IF the SMS_NotificationIndicator parameter was present in the SMSDeliveryPointToPoint INVOKE and the SMS_NotificationIndicator indicates Do not notify when available:

1-22-1-5-3-1-1


1-22-1-5-3-2-2

Include the SMS_CauseCode parameter set to SMS Delivery Postponed. Relay the other received parameters.

1-22-1-7


46

Include the SMS_CauseCode parameter indicating termination is SMS Termination Denied.

1-22-2-2


1-24

47 48 49 50 51 52

ENDIF.

53

ELSE (MS is not anchored by this MSC:

54

Include the SMS_CauseCode parameter set to Destination no longer at this address.

1-23-2

40

45

ELSE (MSC is not allowed to terminate a short message to the destination MS

1-23-1

37

44

1-22-2-1

1-23

36

43

ENDIF.

1-22-3

35

42

ENDIF.

1-22-1-6 1-22-2

34

41


1-22-1-5-5

33

39

ELSE (SMS_CauseCode is not for a temporary condition):

1-22-1-5-4-1

29

38

ENDIF.

1-22-1-5-4

28

32

1-22-1-5-3-2-1

1-22-1-5-3-3

27

31

ELSE (notification was requested):

1-22-1-5-3-2-3

26

30


1-22-1-5-3-2

25

55 56 57


58

ENDIF.

59 60


40


USSD

1

X.S0065 v1.0

2

2

ELSE (the received message cannot be p rocessed

3

2-1

Include the SMS_CauseCode parameter indicating the proper value.

4

2-2


5 6 7 8 9 10 11 12 13 14 15 16 17 18

7.4.1.1.2

3

ENDIF.

4

Exit this task.

Anchor MSC initiating SMS delivery Point-to-Point Note: This procedure i s a modification of the “Anchor MSC I nitiating 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:

19

1

20

1-1

21 22

IF the request can be processed: IF the SMS_TeleserviceIdentifier parameter is set to IMS Services Teleservice:

1-1-1

Include the SMS_DestinationAddress parameter set to the SMS_OriginalDestinationAddress.

23 24

1-2

25 26 27

1-2-1

28

1-2-1-1

29

1-2-2

30 31

ELSEIF the ServiceIndicator parameter is present and indicates USSD (Unstructured Supplementary Service Data) (i.e., MS has initiated a USSD request): IF subscriber’s profile contains a USSD Gateway address: Set the destination address to the USSD Gateway address. ELSE:

1-2-2-1

Include the SMS_CauseCode parameter indicating SMS Origination Restriction.

1-2-2-2

Return to the calling task indicating denied .

32 33 34 35 36

1-2-3 1-3

37 38

ENDIF. ELSEIF SMS originations are blocked (DEFAULT field of SMS_OriginationRestrictions set to Block all ):

1-3-1

Include the SMS_CauseCode parameter indicating SMS Origination Restriction.

40

1-3-2


41

1-4

39

42 43 44

1-4-1 1-5

45 46 47 48

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 subscriber’s MC (Force Message Center field of SMS_OriginationRestrictions set to Force Indirect ):

1-5-1

Include the SMS_DestinationAddress parameter set to the SMS_OriginalOriginatingAddress.

49 50

1-6

51 52 53

ELSEIF visited MSC network operator policy dictates that SMS originations shall use indirect routing:

1-6-1

Include the SMS_DestinationAddress parameter set to the SMS_OriginalOriginatingAddress.

54 55

1-7

56

1-7-1

ELSE: Include the SMS_DestinationAddress parameter set to the SMS_OriginalDestinationAddress.

57 58 59

1-8

ENDIF.

60


41


X.S0065 v1.0

USSD

1

1-9

Relay all included parameters.

1-10

Execute the “Initiating SMS Delivery Point-To-Point task (see Part 641, sec. 3.2 [X.S0004-641], section 3.2).

1-11 2

Return to the calling task with the received parameters and the returned indication.

2 3 4 5 6

ELSE (request cannot be processed):

7

2-1

Include the SMS_CauseCode parameter indicating the appropriate value.

8

2-2


9

3

ENDIF.

4

Exit this task.

10 11 12 13

7.4.1.2 7.4.1.2.1

14

SMS delivery point-to-point for USSD exchange

15

MSC receiving an SMDPP INVOKE for USSD exchange

16

1

18

IF the request can be processed:

1-1

19

IF the MS has performed an intersystem handoff forward:

1-1-1

Execute the “MSC Initiating SMSDeliveryForward” task (see [X.S0004 -641], section 2.1).

1-1-2 1-2 1-2-1

Page the MS and assign the MS to a traffic channel for USSD.

1-2-2

IF not successful:

Exit this task.

Execute “MSC Sending the USSD Message to the MS” (See Section 6.4.3.3).

Exit this task.

30 31

36 37 38


4

29

35

ELSE (request cannot be processed): ENDIF.

27

34

1-4

3

26

33

ENDIF. ENDIF.

2-1

25

32

1-3 2

22

28

Include the SMS_CauseCode parameter set to identify the failure appropriately.

1-2-3

21

24

ELSEIF the Target MS is not assigned to a traffic channel:

1-2-2-2

20

23

Exit this task.

1-2-2-1

17

39 40 41

7.4.1.2.2

42 43

MSC sending a USSD message to the MS 1

44 45

IF the Target MS is not assigned to a traffic channel:

46

1-1

Include the SMS_CauseCode parameter set to identify the failure appropriately.

1-2

Exit this task.

47 48 49

2

ENDIF.

50

3

IF the SMS_BearerData parameter has a non-zero length:

51

3-1 4

Extract the USSD Message from the SMS_BearerData parameter. ELSE (the SMS_BearerData has a zero length):

53 54

4-1


4-2

Exit this task.

5

52

55 56 57 58

ENDIF.

59 60


42


USSD

1

X.S0065 v1.0

6

Send the USSD Message to the MS.

3

7

IF the USSD Message could not be sent:

4

7-1

Include the SMS_CauseCode parameter set appropriately.

7-2

Exit this task.

2

5 6 7

8

ENDIF.

8

9

IF the MSC Request an acknowledgment from the BS:

9 10

9-1

11

9-1-1

12

WAIT for response from the BS: WHEN a BS response is received:

13

9-1-1-1

14

9-1-1-1-1

15

IF an error indication is included: Include the SMS_CauseCode parameter set appropriately.

9-1-1-2

16

9-2

17 18

ENDIF. ENDWAIT.

10 ENDIF.

19

11 Exit this task.

20 21 22 23 24 25 26 27 28 29 30

7.4.1.3 7.4.1.3.1

SMSDeliveryForward MSC receiving an SMSDeliveryForward INVOKE Note: This procedure is a mod ification of the “MSC Receiving an SMSDeliveryForward INVOKE” procedure in [X.S0004-641]. Upon receipt of an SMSDeliveryForward INVOKE, the MSC shall do the following:

31 32 33 34

1

IF the received message can be processed:

1-1

IF neither the MobileIdentificationNumber or IMSI parameter is received:

35

1-1-1

Include the SMS_CauseCode parameter set to Missing Expected Parameter .

36

1-1-2


1-1-3

Exit this task.

37 38 39

1-2

ENDIF.

1-3

IF the ServiceIndicator parameter indicating USSD (Unstructured Supplementary Service Data) is received:

40 41 42 43 44 45

1-3-1

IF the MSC is the Serving MSC:

1-3-1-1

Execute “MSC Sending the USSD Message to the MS” (See Section 6.4.1.2.2).

1-3-1-2


46 47 48 49 50

1-3-2

ELSE (this is a Tandem MSC):

1-3-2-1

Execute “MSC Initiating SMS Delivery Forward” (see [X.S0004 -641], section 2.1) toward the Serving MSC in the call.

1-3-2-2


51 52 53 54

1-3-3

ENDIF.

55

1-3-4

Exit this task.

56 57

1-4

ENDIF.

58

1-5


59 60


43


X.S0065 v1.0

USSD

1-5-1 1-6

Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter. ELSE:

1 2 3 4

1-6-1


1-6-2


1-6-3

Exit this task.

5 6

8 9

1-7

ENDIF.

1-8

IF the SMS_OriginatingAddress parameter is received:

1-8-1

7

10 11

Set the originating address with received SMS_OriginatingAddress.

1-9

ENDIF.

1-10


1-10-1 1-11

12 13 14

Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter.

15 16 17 18 19

ELSE:

20

1-11-1


21

1-11-2


22

1-11-3

Exit this task.

23 24 25

1-12

ENDIF.

1-13

IF the MSC is the Serving MSC:

26

1-13-1

IF the MS is currently able to receive SMS messages:

1-13-1-1

Execute the “MSC Initiating SMD-REQUEST toward an MS-Based SME” task (see Part 691, sec. 4 [X.S0004-691], section 4).

1-13-1-2

ELSE (the MS is unable to receive SMS messages):

1-13-2-1

Include the SMS_CauseCode parameter set to the appropriate value.

1-13-3

29 30 31

33 34 35 36

ENDIF.

37

ELSE (this is a Tandem MSC):

1-14-1

28

32


1-13-2

1-14

27

38

IF the next MSC in the handoff chain is known to support SMS:

39 40

1-14-1-1

Discard the InterMSCCircuitID parameter.

41

1-14-1-2

Relay all other received parameters.

42

1-14-1-3

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.

1-14-1-4


1-14-2


1-14-3 1-15 2 2-1

44 45 46

ELSE (the handed-off system does not support SMS):

1-14-2-1

43

47 48 49 50

ENDIF.

51

ENDIF.

52

ELSE (the received message cannot be processed)

53

Include the SMS_CauseCode parameter with the appropriate value.

54 55

3

ENDIF.

56

4

Send a RETURN RESULT

57

5

Exit this task.

58 59 60


44


USSD

X.S0065 v1.0

1 2 3 4 5 6 7 8 9 10

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:

11 12 13 14 15 16

1

IF the received message can be processed:

1-1

IF the SMS_DestinationAddress parameter is received:

1-1-1

Set the destination address with the address in the received SMS_DestinationAddress parameter.

17 18

1-2

ENDIF.

19

1-3


20 21

1-3-1

Set the original destination address with the address in the received SMS_OriginalDestinationAddress parameter.

22 23 24

1-4

ELSE:

25

1-4-1


26

1-4-2


1-4-3

Exit this task.

27 28 29 30

1-5

ENDIF.

1-6


31 32

1-6-1

Set the original originating address with the address in the received SMS_OriginalOriginatingAddress parameter.

33 34

1-7

ENDIF.

1-8

Relay all parameters received.

37

1-9

IF the MSC is the Anchor MSC:

38

1-9-1

Execute the “Anchor MSC Initiating SMS Delivery Point-To-Point” task (7.4.1.1.2).

1-9-2


35 36

39 40 41 42 43

1-10

ELSE (the MSC is a Tandem MSC):

44

1-10-1

45

1-10-1-1

Discard the InterMSCCircuitID parameter.

1-10-1-2


46 47 48 49

Execute the “MSC Initiating SMS Delivery Backward” task (7.4.1.4.2).

1-10-2

ELSE (the handing-off system does not support SMS):

1-10-2-1


50 51 52 53 54

1-10-3

ENDIF.

1-11

ENDIF.

1-12

Send a RETURN RESULT towards the Serving MSC.

55

2

56

2-1

Include the SMS_CauseCode parameter indicating t he proper value.

2-2


57 58

ELSE (the received message cannot be p rocessed):

59 60


45


X.S0065 v1.0

USSD

1

3

ENDIF.

4

Exit this task.

2

7.4.1.4.2

3 4

MSC initiating SMSDeliveryBackward

5

Note: This procedure is a modification of the “MSC Initiating SMS Delivery Backward” procedure in [X.S0004-641].

6 7 8

Upon request to send an MS-originated SMS point-to-point message up the handoff chain, the MSC shall do the following:

9

1

12

2

Include InterMSCCircuitID parameter set to the trunk used in the direction toward the Anchor MSC. IF the MSC is the Serving MSC:

2-1

13 14

16

Include the SMS_DestinationAddress parameter set to the destination address.

2-2

ENDIF.

2-3

Include the SMS_OriginalDestinationAddress parameter set to the original destination address (provided by the MS).

2-4

IF the original originating address was provided (by the MS):

2-4-1

11

15

IF the destination address was provided (by the MS):

2-1-1

10

17 18 19

Include the SMS_OriginalOriginatingAddress prameter set to the original originating address.

20 21 22 23 24 25 26

2-5

ENDIF.

27

2-6

Include other parameters as appropriate.

28

3

29

ELSE (the MSC is acting as a Tandem MSC for the MS):

3-1

30

Include all parameters received from the calling task (see Part 540 [X.S0004-540]).

31 32

4

ENDIF.

5

Send a SMSDeliveryBackward INVOKE message toward the Destination Address.

34

6

Start the Short Message Backward Timer (SBT).

35

7

WAIT for an SMS Delivery Backward response:

8

WHEN a RETURN RESULT is received:

33

8-1

Stop the timer (SBT).

8-2

IF the message can be pr ocessed:

8-2-1

36 37 38 39 40 41

IF the SMSDeliveryBackward INVOKE was initiated by an initial Serving MSC:

8-2-1-1

IF an intersystem handoff (handoff forward) has occurred:

8-2-1-1-1

Execute the “MSC Initiating SMS Delivery Point To Point Ack“ task (see Part 641, sec 4.1 [X.S0004-641], Section 4.1 ).

8-2-1-1-2

Exit this task.

8-2-1-2

42 43 44 45 46 47 48 49 50

ENDIF.

51

8-2-2

ENDIF.

52

8-2-3


53

8-2-4

Return to the calling task as accepted .

8-3

54 55

ELSE (the message cannot be pr ocessed):

8-3-1

56

Return to the calling task with the SMS_CauseCode indicating Other Network Problem.

57 58 59 60


46


USSD

X.S0065 v1.0

8-4

1 2

ENDIF.

3

9

4

9-1


9-2

Exit this task.

5 6

WHEN a FacilitiesRelease INVOKE is received :

10 WHEN a RETURN ERROR1 is received :

7 8

10-1


10-2

Return to the calling task with the SMS_CauseCode indicating Other Network Problem.

9 10 11 12

11 WHEN a REJECT is received:

13 14

11-1


15

11-2

CASE reject problem specifier OF:

11-3

Unrecognized component,

18

11-4

Incorrect component portion,

19

11-5

Badly structured component portion,

21

11-6

Incorrect parameter,

22

11-7

Unrecognized package type,

11-8

Incorrect transaction portion,

11-9

Badly structured transaction portion:

16 17

20

23 24 25 26

11-9-1

Return to the calling task with the SMS_CauseCode indicating Encoding Problem.

27 28

11-10

29

Unrecognized operation code:

11-10-1

30

Return to the calling task with the SMS_CauseCode indicating SMS not supported .

31 32 33

11-11

DEFAULT:

34

11-12

Return to the calling task with the SMS_CauseCode indicating Network failure.

11-13

ENDCASE:

35 36

12 WHEN the timer (SBT) expires:

37 38

12-1

Return to the calling task with the SMS_CauseCode indicating Network failure.

39

13 ENDWAIT.

40 41

7.4.1.5

42

SMS Notification

43

7.4.1.5.1

44

HLR initiating SMS Notification

45

Note: This procedure is a modification of the “HLR I nitiating SMS Notificati on” procedure in [X.S0004-641].

46 47 48

Upon request to send an SMSNotification message, the HLR shall do the following:

49 50 51 52 53 54 55

1

Include the ElectronicSerialNumber parameter set to the ESN of the desired MS.

2

Include the MSID parameter set to the MIN or IMSI of the desired MS.

3

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:

56 57 58

1

The sending of an SMS DeliveryBackward RETURN ERROR is not recommended and error tables are not supplied.

59 60


47


X.S0065 v1.0

USSD

3-1

Include the SMSTeleserviceIdentifier parameter set to the teleservice for which the notification is being made.

1 2 3

4

ENDIF.

5

IF MS is denied:

5-1 6

5

Include the SMS_AccessDeniedReason parameter set to Denied . ELSEIF MS is unavailable or the temporary SMS routing address is not current:

6-1 7

4

Include the SMS_AccessDeniedReason parameter set to Unavailable. ELSE:

7-1

6 7 8 9 10 11

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.

8

ENDIF.

9

Send an SMSNotification message toward the MS’s MC, for SMS, or toward the OTAF, for OTAPA or toward the USSD Gateway, for USSD.

12 13 14 15 16

10 Start the SMS Notification Timer (SNT).

17 18 19 20 21

11 WAIT for a SMS Notification response:

22

12 WHEN a RETURN RESULT is received:

23

12-1

Stop the timer (SNT).

24

12-2

IF the message cannot be processed:

12-2-1 12-3

25 26

Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1[X.S0004630], section 5.1).

27 28 29

ENDIF.

30

13 WHEN a RETURN ERROR or REJECT is received:

31

13-1

Stop the timer (SNT).

32

13-2

Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1 [X.S0004-630], section 5.1).

33

35 36

14 WHEN the timer (SNT) expires: 14-1

34

Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1[X.S0004-630], section 5.1).

15 ENDWAIT.

37 38 39 40 41

16 Exit this task.

42 43

7.4.1.6

SMS Request

44 45

7.4.1.6.1

HLR receiving an SMSRequest INVOKE

46 47

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

50 51

53

IF CDMA service:

1-1-1

49

52


1-1

48

54

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 .

55 56 57 58 59 60


48


USSD

1 2 3

X.S0065 v1.0

1-1-1-2


1-1-1-3

Exit this task.

4

1-1-2

ENDIF.

5

1-1-3

IF ServiceIndicator parameter is present and indicates CDMA OTAPA service:

6 7

1-1-3-1

8

1-1-3-1-1

9

IF the ElectronicSerialNumber parameter was not received: Include the ElectronicSerialNumber parameter set to identify the MS.

10

1-1-3-2

ENDIF.

11

1-1-3-3

IF either current serving MSC is not OTAPA capable OR is not secure to program the MS at its current locati on, OR IF the temporary routing address is not current, OR IF the MS is reported as inactive:

12 13 14 15

1-1-3-3-1

IF the SMSNotificationIndicator parameter was present in the SMSRequest INVOKE and the SMSNotificationIndicator indicates Do not notify when available:

16 17 18

1-1-3-3-1-1

Include the SMSAccessDeniedReason parameter set to Unavailable.

19 20 21 22 23

1-1-3-3-2

ELSE:

1-1-3-3-2-1

IF the OTA Delivery Pending Flag for this MS is not already set:

1-1-3-3-2-1-1

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.

24 25 26 27

1-1-3-3-2-2

ELSE:

28

1-1-3-3-2-2-1

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.

29 30 31 32 33

1-1-3-3-2-3

ENDIF.

34

1-1-3-3-2-4

Include the SMSAccessDeniedReason parameter set to Postponed .

35

1-1-3-3-3

ENDIF.

37

1-1-3-3-4


38

1-1-3-3-5

Exit this task.

36

39 40

1-1-3-4

ELSE:

41

1-1-3-4-1

Include the SMS_Address parameter set to the current address for the MS.

44

1-1-3-4-2


45

1-1-3-4-3

Exit this task.

42 43

46 47 48 49

1-1-3-5 1-1-4

ENDIF.

1-1-5

IF ServiceIndicator parameter is present and indicates USSD ( (Unstructured Supplementary Service Data):

50 51 52

1-1-5-1

53 54

ENDIF.

1-1-5-1-1

55 56

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:

57 58

1-1-5-1-1-1

59

Include the SMS_AccessDeniedReason parameter set to indicate Unavailable.

60


49


X.S0065 v1.0

USSD

1-1-5-1-2

1

ELSE:

1-1-5-1-2-1

IF the USSD Delivery Pending Flag for this MS is not already set:

1-1-5-1-2-1-1

Set the USSD Delivery Pending Flag for this MS, storing the routing address of the USSD Gateway from which the SMSRequest INVOKE was received.

1-1-5-1-2-2

ENDIF.

1-1-5-1-2-4

Include the SMS_AccessDeniedReason parameter set to indicate Postponed .

Include the SMS_Address parameter set to the current address for the MS. Send a RETURN RESULT.

1-1-5-5

Exit this task.

15 16

20 21

23 24 25 26

1-1-6

ENDIF.

1-1-7

IF the teleservice indicated by the SMS_TeleserviceIdentifier parameter is unknown or is not supported:

27

Include the SMS_AccessDeniedReason parameter indicating Invalid : ENDIF.

28 29 30 31 32 33

ELSEIF TDMA service:

34

IF the addressed MS is not known, OR IF the MS is known, but is not authorized for SMS:

35

Include the SMS_AccessDeniedReason parameter set to Denied .

37

1-2-1-1 1-2-2

12

22

1-1-5-4

1-2-1

11

19

ENDIF.

1-2

10

18

1-1-5-3

1-1-8

9

17

ELSE:

1-1-7-1

6

14

ENDIF.

1-1-5-2-1

5

13

1-1-5-1-2-3

1-1-5-2

4

8

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.

1-1-5-1-3

3

7

ELSE:

1-1-5-1-2-2-1

2

ELSEIF (the teleservice indicated by the SMS_TeleserviceIdentifier parameter is unknown or is not supported):

1-2-2-1

Include the SMS_AccessDeniedReason parameter set to Invalid .

36

38 39 40 41 42

1-2-3

ELSEIF the SMS_TeleserviceIdentifier is not supported:

1-2-3-1

Include the SMS_CauseCode parameter set to Invalid Teleservice ID.

1-2-4

43 44 45

ENDIF.

46

1-3

ENDIF.

47

1-4

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:

48 49 50

1-4-1

Include the SMS_Address parameter set to the current SMS address for the MS.

51

1-4-2

IF the ElectronicSerialNumber parameter was not received:

52

1-4-2-1

Include the ElectronicSerialNumber parameter set to identify the MS.

1-4-3 1-5

ENDIF.

53 54 55

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:

56 57 58 59 60


50


USSD

X.S0065 v1.0

1-5-1

Relay all parameters received in the SMSRequest INVOKE.

1-5-2

Include the ElectronicSerialNumber parameter for the addressed MS.

1-5-3

Send an SMSRequest INVOKE to the VLR that is currently serving the indicated MS.

1-5-4

Start the SMS Request Timer (SRT).

8

1-5-5

WAIT for an SMS Request Response.

9

1-5-6

WHEN a RETURN RESULT is received:

1 2 3 4 5 6 7

10 11

1-5-6-1

Stop timer (SRT).

12

1-5-6-2


13 14 15 16

1-5-6-2-1


1-5-6-3

ELSE (message cannot be processed):

1-5-6-3-1

Execute “Local Recovery Procedures” task (see Part 630, sec. 5.1 [X.S0004-630] Section 5.1).

1-5-6-3-2

Set the SMS Delivery Pending Flagfor this MS

1-5-6-3-3

Include the SMS_AccessDeniedReason parameter set to Postponed .

17 18 19 20 21 22

1-5-6-4

ENDIF.

23

1-5-7

24

1-5-7-1

Stop timer (SRT).

1-5-7-2


1-5-7-3


30

1-5-7-4


31

1-5-8

25 26

WHEN a RETURN ERROR or REJECT is received:

27 28 29

32

WHEN timer (SRT) expires:

1-5-8-1


35

1-5-8-2


36

1-5-8-3


33 34

37 38 39

1-5-9 1-6

ELSE (the MS is not registered to an SMS capable system or the MS is registered to an SMS incapable system):

40 41 42

ENDWAIT.

1-6-1

IF the SMS_NotificationIndicator parameter was present in the SMSRequest INVOKE and the SMS_NotificationIndicator indicates Do not notify when available

43 44 45 46 47

1-6-1-1

Include the SMS_AccessDeniedReason parameter set to Unavailable.

1-6-2

ELSE:

48

1-6-2-1

Set the SMS Delivery Pending Flag for this MS

49

1-6-2-2


50 51

1-6-3

52

1-7

ENDIF.

1-8


53 54 55 56 57 58

2

ENDIF.

ELSE (message cannot be processed):

2-1

Include the Error Code parameter set to the proper value (see the following table).

2-2

Send a RETURN ERROR.

59 60


51


X.S0065 v1.0

USSD

3

ENDIF.

4

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

1

X.S0065 v1.0

Table 1

HLR SMSRequest Response

2 3 4 5 6 7

Problem Detection and Recommended Response from the HLR towards the requesting MC RETURN ERROR Error Code UnrecognizedMIN

The supplied MobileIdentificationNumber parameter is within the HLR’s range of MINs, but no record exists.

UnrecognizedESN

An HLR record exists for the supplied MSID parameter, but the ElectronicSerialNumber parameter supplied does not match the stored value.

ID/HLRMismatch

The supplied MSID parameter is not in the HLR’s range of MSIDs or the supplied MDN parameter is not in the HLR’s range of MDNs. (suspect routing error).

ResourceShortage

A required HLR resource (e.g., internal memory record, HLR is fully occupied) is temporarily not available (e.g., congestion).

OperationNotSupported

The requested MAP operation is recognized, but not supported, by the receiving HLR, or the requesting functional entity is not authorized.

8 9 10 11 12 13

PROBLEM DEFINITION

14 15 16 17 18 19 20 21 22 23

Note: I t i s r ecommended that a H L R support SMSRequest tr ansaction s. T hi s response may have been ori gin ated by the ser vin g system.

24 25 26 27

ParameterError

28 29

A supplied parameter has an encoding problem (e.g., the supplied MobileIdentificationNumber parameter digit values do not meet the BCD specification).

30 31

Note: I nclude the Parameter I dentif ier i n question as the F aultyParameter parameter.

32 33 34

SystemFailure

35 36

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.

37 38

Note: Th is r esponse may have been or igi nated by the ser vin g system.

39 40 41 42

UnrecognizedParameterValu e

A supplied parameter value is unrecognized or has nonstandard values.

43 44


45 46 47

MissingParameter

48 49 50 51 52

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.

53 54


55 56 57

UnrecognizedIMSI/TMSI

58

The supplied IMSI parameter is within the HLR’s range of IMSIs, but no record exists

59 60


53


USSD Call Flow

Recommend Documents