3GPP2 C.S0105-A v1.

01
4 April 4, 2013
Unstructured Supplementary Service Data
(USSD Service !pti"ns #"r Spread Spectrum
Systems$ Service !pti"ns %& and %'
2013 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 ecretariat at secretariat!3gpp2.org. Requests
to reproduce individual Organizational Partner's documents should be directed to that
Organizational Partner. ee """.3gpp2.org for more information.
1
2
3
1
2
3
4
5
6
7
3GPP2 C.P0105-A v0.01
Revision History
Revision Description of Changes Date
Rev 0 v1.0 Publication June, 2012
Rev 0 v2.0 Addition of capability of sending a USSD
message over an access channel.
xxx, 2013
1
2
1
3
3GPP2 C.P0105-A v0.01
Table of Contents
1 Introduction............................................................................................................1
1.1Scope................................................................................................................1
1.2Requirements Language.....................................................................................1
1.3Normative References........................................................................................2
1.4Informative References.......................................................................................3
1.5Terms and Abbreviations...................................................................................3
2 Mobile signaling protocol.........................................................................................4
2.1Operation..........................................................................................................4
2.2Parameters........................................................................................................4
2.2.1 Data Burst Type (BURST_TYPE).............................................................4
2.2.2 Service Options......................................................................................4
2.2.3 USSD Message Format...........................................................................4
2.3MS Signaling Procedures...................................................................................5
2.3.1 Negotiation for the USSD Service Option.................................................5
2.3.2 MS Sending USSD Message....................................................................5
2.3.3 MS Receiving USSD Message..................................................................6
2.3.4 USSD Client Actions...............................................................................6
i
1
2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
3
3GPP2 C.P0105-A v0.01
Table of Tables
Table 1 USSD Message Format...................................................................................4
ii
1
2
1
2
3
3
3GPP2 C.P0105-A v0.01
Foreword
This foreword is not part of this document.
This document is related to:
3GPP2 C.R1001-H v1.0, that provides service option number assignments.
3GPP2 X.S0065-0 v1.0, that provides core network support.
iii
1
2
1
2
3
4
5
3
3GPP2 C.P0105-A v0.01
1 Introduction
1.1 Scope
This document defnes radio interface support for USSD in cdma2000
1
Spread
Spectrum Systems.
Unstructured supplementary service data (USSD) allows the Mobile Station (MS)
user and a PLMN operator defned application to communicate in a way which is
transparent to the MS and to intermediate network entities. The mechanism
allows development of PLMN specifc supplementary services.
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.
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.
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: Pre-
paid balance Inquiry, Balance Transfer (payment from ones 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).
1.2 Requirements Language
Shall and shall not identify requirements to be followed strictly to conform to
this document and from which no deviation is permitted. Should and should
not indicate that one of several possibilities is recommended as particularly
suitable, without mentioning or excluding others, that a certain course of action
is preferred but not necessarily required, or that (in the negative form) a certain
possibility or course of action is discouraged but not prohibited. May and need
not indicate a course of action permissible within the limits of the document.
Can and cannot are used for statements of possibility and capability, whether
material, physical or causal.
1
cdma2000 is the trademark for the technical nomenclature for certain specifcations 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
1
2
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
3
4
5
6
7
3GPP2 C.P0105-A v0.01
1.3 Normative References
The following specifcations contain provisions which, through reference in this
text, constitute provisions of this specifcation. At the time of publication, the
editions indicated were valid. All specifcations are subject to revision, and
parties to agreements based on this specifcation are encouraged to investigate
the possibility of applying the most recent editions of the specifcations indicated
below.
Throughout this specifcation reference to a tag constitutes a reference to the
specifcation identifed 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 specifcation. Formats and coding.
[TS24.090] 3GPP TS 24.090. Unstructured Supplementary Service Data
(USSD); Stage 3.
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.
2
1
2
1
2
3
4
5
6
7
8
9
10
11
3
3GPP2 C.P0105-A v0.01
1.5 Terms and Abbreviations
Term Definition
DBM Data Burst Message [C.S0005]
GSM_USSD_MSG A tunneled GSM USSD message as defned in [TS24.080]
and explained in [TS24.090]
USSD_DBM_BURS
T
001001
USSD Unstructured Supplementary Service Data
3
1
2
1
2
3
3
3GPP2 C.P0105-A v0.01
2 Mobile signaling protocol
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.
2.2 Parameters
2.2.1 Data Burst Type (BURST_TYPE)
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
The format of a USSD message is a DBM using the format in the following table:
Tabe 1 !SSD "essage #ormat
#ie$ %ength &bits' (aue
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
1
2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
3
3GPP2 C.P0105-A v0.01
2.3 MS Signaling Procedures
2.3.1 Negotiation for the USSD Service Option
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
defnitions and contents for a GSM_USSD_MSG are defned in [TS24.090].
If the MS is to send the USSD message over an Access Channel, Enhanced
Access Channel, or Reverse Common Control Channel, the transmission of the
Origination Message shall follow the procedures defned in section 2.6.2.6 of
[C.S0005]. Authentication of the Origination Message may be conducted
according to the procedures defned in [C.S0004].
If the MS is to send the USSD message over a trafc channel, the 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 trafc channel to transmit the USSD message. Authentication of the
Origination Message may be conducted according to the procedure defned in
[C.S0004]. Call processing following the transmission of the Origination Message
shall follow the procedures defned in [C.S0005]. When the MS enters the
Conversation Substate, the MS may transmit the USSD message.
If the MS has already been assigned a trafc channel, the MS shall continue to
use the associated SO for that trafc channel.
The MS shall send the USSD message using the following procedures:
o The MS shall construct a DBM according to Table 1.
o The MS shall use the CHARi portion to construct the GSM_USSD_MSG
using the FACILITY, REGISTER, or RELEASE COMPLETE message type
defned in [TS24.080] and described in [TS24.090].
o The MS shall transmit the DBM on the Access Channel, Enhanced
Access Channel, Reverse Common Control Channel, or Trafc Channel.
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.
5
1
2
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
3
3GPP2 C.P0105-A v0.01
2.3.3 MS Receiving USSD Message
An MS supporting USSD shall process all DBMs addressed to the MS on the
Paging Channel, Forward Common Control Channel or Trafc 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:
MSG_NUMBER feld is set to a value other than 1;
NUM_MSGS feld is set to a value other than 1;
NUM_FIELDS feld is set to zero;
If the DBM is received on a paging channel.
Otherwise, the MS shall parse the CHARi felds 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
The actions taken by the USSD client are as follows:
When a USSD transaction is to be initiated:
The USSD Client shall send a USSD message as defned in section 2.3.1. The
GSM_USSD_MESSAGE feld shall be a REGISTER message containing a
ProcessUnstructuredSS-Request invoke component as defned 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 defned in
[TS24.080] and as explained in [TS24.090] section 6.2.
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].
After receiving a USSD request with a REGISTER message
containing the UnstructuredSS-Request invoke component as defned 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 users mobile
subscribers response in a return result component. The FACILITY message
is defned in [TS24.080] and explained in [TS24.090].
6
1
2
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
3
3GPP2 C.P0105-A v0.01
After receiving a USSD request with REGISTER message containing
the UnstructuredSS-Notify invoke component as defned in [TS24.080]:
If the USSD Client can process the USSD request, the USSD Client shall
acknowledge the USSD notifcation by sending a USSD message where
GSM_USSD_MSG contains a FACILITY message containing an empty return
result component.
After receiving a USSD operation while another USSD operation is
already in progress:
The USSD Client shall send a return error component in a RELEASE
COMPLETE message containing the "USSD Busy" error as defned in
[TS24.080].
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 defned in [TS24.080]. The USSD Client shall
clear the USSD transaction. Depending on the USSD application, either the
Trafc Channel, Access Channel, Enhanced Access Channel, or Reverse
Common Control Channel is used to terminate the USSD transaction. If the
trafc channel was used to send the RELEASE COMPLETE and it was
initiated with SO 78 or 79 then the MS shall enter the Release Substate with
an MS release indication (see [C.S0005]).
After receiving a RELEASE COMPLETE message containing a return
result, return error, or reject component as defned in [TS24.080].
The USSD Client shall clear the USSD transaction. Depending on the USSD
application, either the Trafc Channel, Access Channel, Enhanced Access
Channel, or Reverse Common Control Channel is used to terminate the
USSD transaction. If the trafc channel was used to receive the USSD
message and it was initiated with SO 78 or 79 then the MS shall enter the
Release Substate with an MS release indication (see [C.S0005]).
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
defned in [TS24.080].
7
1
2
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
3
3GPP2 C.P0105-A v0.01
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
defned in [TS24.080].
The USSD Client shall not initiate another USSD transaction while already in a
USSD transaction.
The MS shall not enter the Release Substate if a USSD transaction is cleared
when the trafc channel is being used for the transaction, but the trafc
channel was not initiated with SO 78 or 79.
The MS shall enter the Release Substate if a USSD transaction is cleared when
the trafc channel is being used for the transaction, but the trafc channel was
initiated with an SO other than SO 78 or SO 79 and the trafc 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 trafc
channel has been released, the MS shall may perform a service negotiation for a
new trafc 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 trafc channel.
The MS shall send a Layer 2 Ack upon receipt of any USSD DBM, if requested by
the network [C.S0005].
8
1
2
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
3