3GPP2 C.S0105-0 v1.0 June 2012

Unstructured Supplementary Service Data (USSD) Service Options for Spread Spectrum Systems: Service Options 78 and 79

© 2012 3GPP2 3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at [email protected]. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

3GPP2 C.P0105-0 v1.0

Revision History Revision

Description of Changes

Date

Rev 0 v1.0

Publication

June 2012

3GPP2 C.P0105-0 v1.0

1

Table of Contents

2

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

3

1.1  Scope ................................................................................................................ 1  

4

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

5

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

6

1.4  Informative References ...................................................................................... 3  

7

1.5  Terms and Abbreviations ................................................................................... 3  

8

2   Mobile signaling protocol ........................................................................................ 4  

9

2.1  Operation .......................................................................................................... 4  

10

2.2  Parameters........................................................................................................ 4  

11

2.2.1   Data Burst Type (BURST_TYPE) ............................................................. 4  

12

2.2.2   Service Options ...................................................................................... 4  

13

2.2.3   USSD Message Format ........................................................................... 4  

14

2.3  MS Signaling Procedures ................................................................................... 5  

15

2.3.1   Negotiation for the USSD Service Option ................................................ 5  

16

2.3.2   MS Sending USSD Message ................................................................... 5  

17

2.3.3   MS Receiving USSD Message ................................................................. 5  

18

2.3.4   USSD Client Actions .............................................................................. 6  

19

i

3GPP2 C.P0105-0 v1.0

1

Table of Tables

2

Table 1   USSD Message Format .................................................................................. 4  

3

ii

3GPP2 C.P0105-0 v1.0

1

Foreword

2

This foreword is not part of this document.

3

This document is related to:

4

•

3GPP2 C.R1001-H v1.0, that provides service option number assignments.

5

•

3GPP2 X.S0065-0 v1.0, that provides core network support.

iii

3GPP2 C.P0105-0 v1.0

1

1

Introduction

2

1.1

Scope

3 4

This document defines radio interface support for USSD in cdma2000®1 Spread Spectrum Systems.

5 6 7 8

Unstructured supplementary service data (USSD) allows the Mobile Station (MS) user and a PLMN operator defined application to communicate in a way which is transparent to the MS and to intermediate network entities. The mechanism allows development of PLMN specific supplementary services.

9 10 11 12

There are two modes of USSD: MMI-mode and application mode. MMI-mode USSD is for the transparent transport of MMI strings entered by the user to the network and for the transparent transport of text strings from the network that are displayed by the mobile for user information.

13 14 15

Application mode USSD is for the transparent transport of data between the network and the UE. Application mode USSD is intended to be used by applications in the network and their peer applications in the UE.

16 17 18 19 20 21 22 23

USSD may be initiated by the MS user, or by the network. Unlike Short Message Service (SMS) messages, USSD messages create a real-time connection during a USSD session. The connection remains open, allowing a two-way exchange of a sequence of data. Several examples of how USSD Services are used include: Prepaid balance Inquiry, Balance Transfer (payment from one’s balance to another balance), Voting (“Please rate our customer service: 1=Good, 2=OK, 3=Bad” after a call to a Customer Service Center), and Call Me (requesting another party to call you).

24 25

1.2

Requirements Language “Shall” and “shall not” identify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibility and capability, whether material, physical or causal.

26 27 28 29 30 31 32 33 34

1

cdma2000® is the trademark for the technical nomenclature for certain specifications and standards of the Organizational Partners (OPs) of 3GPP2. Geographically (and as of the date of publication), cdma2000® is a registered trademark of the Telecommunications Industry Association (TIA-USA) in the United States.

1

3GPP2 C.P0105-0 v1.0

1

1.3

Normative References

2 3 4 5 6 7

The following specifications contain provisions which, through reference in this text, constitute provisions of this specification. At the time of publication, the editions indicated were valid. All specifications are subject to revision, and parties to agreements based on this specification are encouraged to investigate the possibility of applying the most recent editions of the specifications indicated below.

8 9

Throughout this specification reference to a tag constitutes a reference to the specification identified below.

Tag

Specification Source

[C.S0004]

3GPP2 C.S0004-E v3.0. 3GPP2 Signaling Link Access Control (LAC) Standard for cdma2000 Spread Spectrum System. June 2011.

[C.S0005]

3GPP2 C.S0005-E v3.0. 3GPP2 Upper Layer (Layer 3) Signaling Standard for cdma2000 Spread Spectrum Systems. June 2011.

[C.S0015]

3GPP2 C.S0015-B v2.0. Short Message Service (SMS) for Wideband Spread Spectrum Systems. September 2005.

[TS24.080]

3GPP TS 24.080. 3GPP Mobile radio interface layer 3 supplementary services specification. Formats and coding.

[TS24.090]

3GPP TS 24.090. Unstructured Supplementary Service Data (USSD); Stage 3.

2

3GPP2 C.P0105-0 v1.0

1 2

1.4

Informative References Tag

Specification Source

[C.R1001]

3GPP2 C.R1001-G v1.0. 3GPP2 Administration of Parameter Value Assignments for cdma2000 Spread Spectrum Systems. June 2009.

3 4

1.5

Terms and Abbreviations Term

Definition

DBM

Data Burst Message [C.S0005]

GSM_USSD_MSG

A tunneled GSM USSD message as defined in [TS24.080] and explained in [TS24.090]

USSD_DBM_BURST

‘001001’

USSD

Unstructured Supplementary Service Data

5

3

3GPP2 C.P0105-0 v1.0

1

2

Mobile signaling protocol

2

2.1

Operation The MS operation is performed when the MS is to send a USSD message to the USSD Gateway or when the MS receives a USSD message from the USSD Gateway. The operation for the MS sending the USSD message is described in section 2.3.2. The operation for the MS receiving the USSD message is described in section 2.3.3.

3 4 5 6 7 8

2.2

9

2.2.1 Data Burst Type (BURST_TYPE)

10 11 12 13 14 15

Parameters

The BURST_TYPE for this DBM [C.S0005] is USSD_DBM_BURST which is also listed in [C.R1001].

2.2.2 Service Options Service options SO 78 for rate set 1 and SO 79 for rate set 2 are used for USSD, see [C.R1001].

2.2.3 USSD Message Format

16

The format of a USSD message is a DBM using the format in the following table:

17

Table 1

USSD Message Format

Field

Length (bits)

Value

MSG_NUMBER

8

1

BURST_TYPE

6

USSD_DBM_BURST

NUM_MSGS

8

1

NUM_FIELDS

8

The Length of the USSD message in octets.

CHARi

8 * NUM_FIELDS

GSM_USSD_MSG

4

3GPP2 C.P0105-0 v1.0

1

2.3

2

2.3.1 Negotiation for the USSD Service Option

3 4 5 6 7 8 9

MS Signaling Procedures

See [C.S0015] section 2.4.1.1.2.1. Treat SO 6 as SO 78, SO 14 as SO 79 and “SMS Service Option” as “USSD Service Option”.

2.3.2 MS Sending USSD Message If an MS is to send a USSD message, the USSD client within the MS shall construct the message according to Table 1. The GSM_USSD_MSG part of the USSD message is constructed according to [TS24.080]. The functional definitions and contents for a GSM_USSD_MSG are defined in [TS24.090].

10 11 12 13 14 15 16

The MS shall request Service Option 78 for rate set 1 or Service Option 79 for rate set 2 if the MS is in idle mode, using an Origination Message with no dialed digits to set up a traffic channel to transmit the USSD message. Authentication of the Origination Message may be conducted according to the procedure defined in [C.S0004]. Call processing following the transmission of the Origination Message shall follow the procedures defined in [C.S0005]. When the MS enters the Conversation Substate, the MS may transmit the USSD message.

17 18

If the MS has already been assigned a traffic channel, the MS shall continue to use the associated SO for that traffic channel.

19

The MS shall send the USSD message using the following procedures:

20

o

The MS shall construct a DBM according to Table 1.

21 22 23

o

The MS shall use the CHARi portion to construct the GSM_USSD_MSG using the FACILITY, REGISTER, or RELEASE COMPLETE message type defined in [TS24.080] and described in [TS24.090].

24

o

The MS shall transmit the DBM on the Traffic Channel.

25 26 27 28 29 30 31

If any SO other than SO 78 or SO 79 is connected, the MS shall remain in the Conversation Substate after acknowledgement of the DBM.

2.3.3 MS Receiving USSD Message An MS supporting USSD shall process all DBMs addressed to the MS on the Traffic Channel and having the BURST_TYPE USSD_DBM_BURST [C.R1001]. The MS shall discard the message without further processing if any of the following is true:

32

•

MSG_NUMBER field is set to a value other than 1;

33

•

NUM_MSGS field is set to a value other than 1;

34

•

NUM_FIELDS field is set to zero;

5

3GPP2 C.P0105-0 v1.0

•

1 2 3 4 5 6 7

If the DBM is received on a paging channel.

Otherwise, the MS shall parse the CHARi fields of the received DBM as a USSD message and shall send it to the USSD client. The USSD client shall process the USSD messages according to [TS24.080]. The signaling procedures for the received USSD DBM is as is any kind of DBM and shall be according to [C.S0005].

2.3.4 USSD Client Actions

8

The actions taken by the USSD client are as follows:

9

•

The USSD Client shall send a USSD message as defined in section 2.3.1. The GSM_USSD_MESSAGE field shall be a REGISTER message containing a ProcessUnstructuredSS-Request invoke component as defined in [TS24.080] and explained in [TS24.090]. The USSD request shall include SS version to indicate that it supports phase 2 or a higher protocol version as defined in [TS24.080] and as explained in [TS24.090] section 6.2.

10 11 12 13 14 15 16 17

•

•

30 31 32 33

After receiving a USSD request with a REGISTER message containing the UnstructuredSS-Request invoke component as defined in [TS24.080]: If the USSD Client can process the USSD request, the USSD Client shall acknowledge the REGISTER message by sending a USSD message where GSM_USSD_MSG contains a FACILITY message containing the user’s mobile subscriber’s response in a return result component. The FACILITY message is defined in [TS24.080] and explained in [TS24.090].

23 24 25 26 27 28 29

After receiving a USSD request with REGISTER message that cannot be processed: The USSD Client shall send a return error component in a FACILITY message with the appropriate error value [TS24.080].

18 19 20 21 22

When a USSD transaction is to be initiated:

•

After receiving a USSD request with REGISTER message containing the UnstructuredSS-Notify invoke component as defined in [TS24.080]: If the USSD Client can process the USSD request, the USSD Client shall acknowledge the USSD notification by sending a USSD message where GSM_USSD_MSG contains a FACILITY message containing an empty return result component.

6

3GPP2 C.P0105-0 v1.0

1 2

•

The USSD Client shall send a return error component in a RELEASE COMPLETE message containing the "USSD Busy" error as defined in [TS24.080].

3 4 5 6

•

•

•

25 26 27

After receiving a FACILITY message that the USSD Client is capable of processing. The USSD Client shall send a USSD message where GSM_USSD_MSG contains a FACILITY message containing a return result component, as defined in [TS24.080].

20 21 22 23 24

After receiving a RELEASE COMPLETE message containing a return result, return error, or reject component as defined in [TS24.080]. The USSD Client shall clear the USSD transaction. If the traffic channel was initiated with SO 78 or 79 then the MS shall enter the Release Substate with an MS release indication (see [C.S0005]).

15 16 17 18 19

If the USSD Client is to terminate the USSD transaction: The USSD Client shall send a USSD message where GSM_USSD_MSG contains a RELEASE COMPLETE message containing a return result, return error, or reject component as defined in [TS24.080]. The USSD Client shall clear the USSD transaction. If the traffic channel was initiated with SO 78 or 79 then the MS shall enter the Release Substate with an MS release indication (see [C.S0005]).

7 8 9 10 11 12 13 14

After receiving a USSD operation while another USSD operation is already in progress:

•

After receiving a FACILITY message that the USSD Client is not capable of processing. The USSD Client shall send a USSD message where GSM_USSD_MSG contains a FACILITY message containing a return error component as defined in [TS24.080].

7

3GPP2 C.P0105-0 v1.0

1 2

The USSD Client shall not initiate another USSD transaction while already in a USSD transaction.

3 4

The MS shall not enter the Release Substate if a USSD transaction is cleared when the traffic channel was not initiated with SO 78 or 79.

5 6 7 8 9 10 11 12

The MS shall enter the Release Substate if the traffic channel was initiated with an SO other than SO 78 or SO 79 and the traffic channel is released. If a USSD transaction is active then the USSD transaction shall remain active. If a USSD Client has a USSD message to send after a traffic channel has been released, the MS shall perform a service negotiation for a new traffic channel with SO 78 or SO 79 (see section 2.3.1). If the USSD Client is waiting for a USSD message from the USSD Gateway then it shall wait for the network to establish a new traffic channel.

13 14

The MS shall send a Layer 2 Ack upon receipt of any USSD DBM, if requested by the network [C.S0005].

15

8