6 USSD operations – application mode
22.0903GPPStage 1TSUnstructured Supplementary Service Data (USSD)
6.1 General
USSD supports communication between an application (handler) in the UE and a corresponding application (handler) in the network by enabling transparent transfer of binary data between the network and the UE. The applications may use USSD either during a call or out of call.
Application-level addressing is out of scope of the present document.
6.2 Mobile initiated transfer
6.2.1 Initiating action at the UE
If the UE wishes to send data to the network, it can do so using USSD. It shall be possible for the UE to send data to nodes in the VPLMN and in the HPLMN, i.e. MSC, VLR, HLR, MExE servers, CSEs and proxy servers.
6.2.2 Action in the network
The serving network shall pass the received message to its destination node. If the VPLMN cannot route the message to the destination it shall forward the message to the HPLMN.
6.3 Network initiated transfer
6.3.1 Initiating action in the network
If a node in the network wishes to send data to an UE, it can do so using USSD.
If the network is unable successfully to reach the UE, then an error shall be returned to the node that originated the operation.
6.3.2 Action at the UE
The UE shall pass the message to the ME, to the SIM/USIM or to the TE as indicated in the message.
6.4 External addressing
The USSD dialogue exists inside the PLMN. However, it shall be possible to transport the address of an external node in the USSD message. The address format must be standardised and support at least E.164 and IP addresses.
When addressing of an UE from an external node the address shall be an MSISDN number. The return address shall be present and in the same format the UE uses to address an external node.
The mechanism for communication between the PLMN and the external node is out of scope of the present document.
6.5 Charging aspects
It shall be possible to charge for the use of application mode USSD based on e.g. the destination node.
Charging for the use of an application is out of scope of the present document.
6.6 Compatibility aspects
6.6.1 Mobile initiated transfer
If the network does not support application mode USSD, the mobile initiated operation will be rejected and the attempt will fail. The UE shall not attempt automatic fall back to phase 1 USSD or to MMI mode USSD in case of incompatibility. Application-level recovery is outside the scope of the present document.
If the network is unable to identify the destination node, it shall forward the message to the HLR.
6.6.2 Network initiated transfer
If the UE is unable to process the network initiated USSD operation, then an error indication shall be returned to the node that originated the operation.
6.7 Interaction with other services
The user or the network operator shall be able to prevent the use of application mode USSD during calls. The use of USSD in parallel with a circuit switched call may have a negative impact on the quality of the speech or data transmission.
6.8 Security
Application-level security is out of scope of the present document.
Annex A (informative):
Change history
|
Change history |
|||||||||||
|
TSG SA# |
SA Doc. |
SA1 Doc |
Spec |
CR |
Rev |
Rel |
Cat |
Subject/Comment |
Old |
New |
Work Item |
|
Jun 1999 |
02.90 |
Transferred to 3GPP SA1 |
8.0.0 |
||||||||
|
SA#04 |
22.090 |
R99 |
3.0.0 |
||||||||
|
SP-05 |
SP-99479 |
S1-99636 |
22.090 |
0001 |
R99 |
D |
Editorial changes for alignment for 3GPP |
3.0.0 |
3.0.1 |
||
|
SP-07 |
SP-000063 |
S1-000048 |
22.090 |
0002 |
R99 |
C |
UCS2 character set for MMI mode |
3.0.1 |
3.1.0 |
||
|
SP-11 |
SP-010065 |
S1-010258 |
22.090 |
Rel-4 |
Transferred to 3GPP Release 4 |
3.1.0 |
4.0.0 |
||||
|
SP-16 |
SP-020267 |
S1-021043 |
22.090 |
Rel-5 |
Updated from Rel-4 to Rel5 |
4.0.0 |
5.0.0 |
||||
|
SP-26 |
SP-040744 |
S1-040997 |
22.090 |
Rel-6 |
Updated from Rel-5 to Rel-6 |
5.0.0 |
6.0.0 |
||||
|
SP-32 |
SP-060445 |
– |
22.090 |
0003 |
2 |
Rel-7 |
F |
USSD – Corrections |
6.0.0 |
7.0.0 |
TEI7 |
|
SP-42 |
– |
– |
Rel-8 |
Updated from Rel-7 to Rel-8 |
7.0.0 |
8.0.0 |
|||||
|
SP-46 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-9 by MCC |
8.0.0 |
9.0.0 |
|
|
2011-03 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-10 version (MCC) |
9.0.0 |
10.0.0 |
|
|
2012-09 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-11 by MCC |
10.0.0 |
11.0.0 |
|
|
2014-10 |
– |
– |
– |
– |
– |
– |
– |
Update to Rel-12 version (MCC) |
11.0.0 |
12.0.0 |
|
|
2015-12 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-13 by MCC |
12.0.0 |
13.0.0 |
|
|
2017-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-14 by MCC |
13.0.0 |
14.0.0 |
|
|
2018-06 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-15 by MCC |
14.0.0 |
15.0.0 |
|
|
SA#88e |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
15.0.0 |
16.0.0 |
|
|
2022-03 |
– |
– |
– |
– |
– |
– |
– |
Updated to Rel-17 by MCC |
16.0.0 |
17.0.0 |
|