31.9 Handling of undefined (future) GSM supplementary services
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
31.9.1 Mobile station initiated Unstructured supplementary service data operation
31.9.1.1 ProcessUnstructuredSS-request/accepted
Conformance requirements
1) The mobile station shall invoke an USSD request by sending a REGISTER message to the network containing a ProcessUnstructuredSS-Request invoke component. This message will contain the alphabet indicator set to "SMS default alphabet" and the language indicator set to "language unspecified". The ussd-string parameter shall contain the following digits and symbols depending on the operation initiated:
Activation: *NN(N)# (no supplementary information included)
*NN(N)*SI# (one field of supplementary infor. included)
*NN(N)*SIA*SIB# (two fields of supplementary infor. included)
Deactivation: #NN(N)#
#NN(N)*SI#
#NN(N)*SIA*SIB#
Interrogation: *#NN(N)#
*#NN(N)*SI#
*#NN(N)*SIA*SIB#
Registration **NN(N)#
**NN(N)*SI#
**NN(N)*SIA*SIB#
Erasure ##NN(N)#
##NN(N)*SI#
##NN(N)*SIA*SIB#
Operations not yet: see conformance requirement 2).
defined in 3GPP TS 02.30.
NN(N) features a set of service codes which have not yet been allocated for GSM supplementary services (see 3GPP TS 02.30 for service codes already specified).
N is a digit within 1..9 and SI, SIA, SIB strings of characters.
2) Concerning operations which are not yet specified in 3GPP TS 02.30, the MS shall proceed as follows:
The entry of 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" shall be interpreted by the MS as an USSD request unless the MS is not engaged in a call and the first of the two character entry followed by "SEND" is a "1". Except if the 1 or 2 characters are MS manufacturer defined procedure in idle mode.
3) For supplementary service procedures independent of any call, the initiating side shall establish a MM-connection between the network and the mobile station according to the rules given in 3GPP TS 04.08 / 3GPP TS 24.008.
4) Within a call, the MS shall transmit a USSD request from the user if any. See 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008 for the handling of multiple MM connections.
5) Upon receipt of the RELEASE COMPLETE message, the MS shall display the information contained to the user in a way described by the manufacturer.
References
Conformance requirement 1: 3GPP TS 04.90 subclause 6.1,
3GPP TS 02.30 subclause 4.5.2, and
3GPP TS 02.90 subclause 4.1.1.
Conformance requirement 2: 3GPP TS 02.30 subclause 4.5.3.2.
Conformance requirement 3: 3GPP TS 04.10 subclause 3.2.1.
Conformance requirement 4: 3GPP TS 04.08 / 3GPP TS 24.008 subclause 4.5.1.1.
Conformance requirement 5: 3GPP TS 03.90 subclause 6.2.1.
Test Purpose
1) To verify that the mobile station invokes an USSD request by sending a REGISTER message to the network containing a ProcessUnstructuredSS-Request invoke component. This message will contain the alphabet indicator set to "SMS default alphabet" and the language indicator set to "language unspecified". The ussd-string parameter shall contain the following digits and symbols depending on the operation initiated:
Activation *NN(N)# (no supplementary information included)
*NN(N)*SI# (one field of supplementary infor. included)
*NN(N)*SIA*SIB# (two fields of supplementary infor. included)
Deactivation #NN(N)#
#NN(N)*SI#
#NN(N)*SIA*SIB#
Interrogation *#NN(N)#
*#NN(N)*SI#
*#NN(N)*SIA*SIB#
Registration **NN(N)#
**NN(N)*SI#
**NN(N)*SIA*SIB#
Erasure ##NN(N)#
##NN(N)*SI#
##NN(N)*SIA*SIB#
Operations not yet: see 2).
defined in 3GPP TS 02.30
NN(N) features a set of service codes which have not yet been allocated for GSM supplementary services (see 3GPP TS 02.30 for service codes already specified).
N is a digit within 1..9 and SI, SIA, SIB strings of characters.
2) To check that the entry of 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" shall be interpreted by the MS as an USSD request unless the MS is not engaged in a call and the first of the two character entry followed by "SEND" is a "1". Except if the 1 or 2 characters are MS manufacturer defined procedure in idle mode.
3) To verify that, for supplementary service procedures independent of any call, the initiating side must establish a MM-connection between the network and the mobile station according to the rules given in 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008.
4) To verify that, within a call the MS shall transmit a USSD request if any. See 3GPP TS 04.07 and 3GPP TS 04.08 / 3GPP TS 24.008 for the handling of multiple MM connections.
5) To check that upon receipt of the RELEASE COMPLETE message, the MS shall display the information contained to the user in a way described by the manufacturer.
Specific PICS Statements
–
PIXIT Statements
– Description of the user’s commands and of display of USSD.
– Identification of the short strings defining MS manufacturer defined procedure in idle mode (1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND").
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI) the mobile is made to initiate an Unstructured SS data operation. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message. Then a CHANNEL RELEASE message is sent to the MS to release the main signalling link.
The mobile station is forced to originate a call. After the MS has received a CONNECT ACKNOWLEDGE, MMI keys are depressed on the mobile in order to initiate an Unstructured SS data operation. Then a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message. Finally, the main signalling link is released by transferring a CHANNEL RELEASE message to the MS.
Expected Sequence
The sequence is executed for execution counters c=1,..,16.
The second part of the sequence, namely from step 9 to step 18, is executed for execution counter c=17.
Counter c determines the ussd-string selected by the user and sent by the MS (see specific message contents concerning the REGISTER message).
Step |
Direction |
Message |
Comments |
1 |
MS |
The user presses appropriate MMI keys to initiate the desired unstructured SS data operation. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
with establishment cause set to "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
5 |
SS -> MS |
CM SERVICE ACCEPT |
|
6 |
MS -> SS |
REGISTER |
The SS checks that the content of this message matches specific message content i). |
7 |
SS -> MS |
RELEASE COMPLETE |
It terminates the transaction used to initiate the desired unstructured SS data operation. |
8 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
MS |
During step 7 and 8 it is checked that the ussd string, if any, is displayed by the MS in a way described by the manufacturer. See ii). |
||
9 |
MS |
The MS is brought to state U10 by initiating a Mobile originating call |
|
10 |
Specific MMI keys are depressed to initiate the desired undefined SS service operation. DTMF signalling may occur. |
||
11 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
12 |
SS -> MS |
CM SERVICE ACCEPT |
|
13 |
MS -> SS |
REGISTER |
The MS starts the transaction on the radio interface. The SS checks that REGISTER matches i). |
14 |
SS -> MS |
RELEASE COMPLETE |
It terminates the transaction used to activate the desired undefined SS data operation. See specific message contents ii). |
15 |
SS -> MS |
DISCONNECT |
|
16 |
MS -> SS |
RELEASE |
|
17 |
SS -> MS |
RELEASE COMPLETE |
See message contents iii). |
18 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific message contents.
i) REGISTER message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
|
Register message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
SS version indicator |
As specified in 3GPP TS 04.80 |
Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Invoke from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
Arbitrary (1 octet) |
Operation Code tag |
From 3GPP TS 04.80 |
Operation Code length |
1 |
Operation Code |
ProcessUnstructuredSS-Request |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" |
ussd-string |
c=1, *60# (Activation with no supplementary information included) c=2, *201*35# (Activation with one field of supplementary information included) c=3, *70*635*562# (Activation with two fields of supplementary information included) c=4, #60# (Deactivation with no supplementary information included) c=5, #201*35# (Deactivation with one field of supplementary information included) c=6, #70*635*562# (Deactivation with two fields of supplementary information included) c=7, *#60# (Interrogation with no supplementary information included) c=8, *#201*35# (Interrogation with one field of supplementary information included) c=9, *#70*635*562# (Interrogation with two fields of supplementary information included) c=10, **60# (Registration with no supplementary information included) c=11, **201*35# (Registration with one field of supplementary information included) c=12, **70*635*562# (Registration with two fields of supplementary information included) c=13, ##60# (Erasure with no supplementary information included) c=14, ##201*35# (Erasure with one field of supplementary information included) c=15, ##70*635*562# (Erasure with two fields of supplementary information included) in idle mode : c=16, 1 or 2 characters defined in the 3GPP TS 03.38 default alphabet followed by "SEND" (related to conformance requirement 2). This short string shall not be a MS manufacturer defined procedure as identified in PIXIT statements and shall not be in the format 1x in active call : c=16, 36 ( related to conformance requirement 2) in active call : c=17, 7 (related to conformance requirement 2) |
ii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
the transaction value is the same as REGISTER transaction value but the transaction flag is different |
Release Complete message type |
As 3GPP TS 04.80 |
Cause |
omitted. |
Facility Information Element |
See below |
Facility information element with Return Result = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of IE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
depending on the length of the ussd-string |
Invoke ID tag |
|
From 3GPP TS 04.80 |
|
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS-Request |
Sequence Identifier |
From 3GPP TS 04.80 |
Operation Code tag |
From 3GPP TS 04.80 |
Operation Code length |
1 |
Operation Code |
ProcessUnstructuredSS-Request |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet" Language indicator set to "undefined" |
ussd-string |
chosen at random |
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call control)" |
Transaction identifier |
same as current call. |
Release Complete message type |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
31.9.1.2 ProcessUnstructuredSS-request/cross phase compatibility and error handling
Conformance requirements
1) If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "facility rejected", the mobile station shall assume that the network only supports protocol version 1 of USSD operations. The mobile station shall re-attempt the request by using the appropriate protocol version 1 USSD operation without a SS version indicator if the unstructured data entered by the user can be coded as an IA5 string.
2) Upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). If ussd-String information is included this shall be given to the user (in a way described by the manufacturer).
References
Conformance requirement1: 3GPP TS 04.90 subclause 6.2.1.
Conformance requirement2: 3GPP TS 03.90.
Test Purpose
1) To verify that If a mobile initiated USSD request using protocol version 2 is rejected by the network, and the reason for the rejection is indicated either by the problem code "unrecognized operation" or a cause "facility rejected", the mobile station shall assume that the network only supports protocol version 1 of USSD operations. The mobile station shall re-attempt the request by using the appropriate protocol version 1 USSD operation without a SS version indicator if the unstructured data entered by the user can be coded as an IA5 string.
2) To check that, upon receipt of the RELEASE COMPLETE message, the MS shall provide the appropriate user indication (which is to be described by the manufacturer). If ussd-String information is included this shall be given to the user (in a way described by the manufacturer).
Specific PICS Statements
–
PIXIT Statements
–
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
Appropriate MMI keys are pressed on the mobile in order to activate an USSD service. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message with the problem code set to "unrecognized operation", the main signalling link is released. Then the SS checks that the MS re-establishes a MM-connection and re-attempts the request by using a REGISTER message containing an invoke of the ProcessUnstructuredData operation. The SS answers with a normal RELEASE COMPLETE to terminate the transaction. Finally the main signalling link is released by transferring to the MS a CHANNEL RELEASE.
Appropriate MMI keys are pressed on the mobile in order to activate an USSD service. The mobile first establishes a MM-connection with the SS. Then, a REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message with the cause element set to "Facility rejected", the main signalling link is released. Then the SS checks that the MS re-establishes a MM-connection and re-attempts the request by using a REGISTER message containing an invoke of the ProcessUnstructuredData operation. Then the SS answers with a normal RELEASE COMPLETE to terminate the transaction. Finally the main signalling link is released by transferring to the MS a CHANNEL RELEASE.
The mobile station is forced to originate a call. After the SS has sent a CONNECT ACKNOWLEDGE, MMI keys are pressed on the mobile in order to activate an USSD service. A REGISTER message is sent to the SS. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message containing a return error with an error or a reject with a problem. Then the radio link is release by transferring to the MS a CHANNEL RELEASE message. This subtest is repeated with different errors and problems in the RELEASE COMPLETE message.
Expected Sequence
Step |
Direction |
Message |
Comments |
---|---|---|---|
1 |
MS |
The user presses appropriate MMI keys to initiate the desired undefined supplementary service operation. |
|
2 |
MS -> SS |
CHANNEL REQUEST |
with establishment cause set to "Other procedures which can be completed with an SDCCH". |
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
4 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
5 |
SS -> MS |
CM SERVICE ACCEPT |
|
6 |
MS -> SS |
REGISTER |
See specific message contents i).Operation code set to "ProcessUnstructuredSS-Request" |
7 |
SS -> MS |
RELEASE COMPLETE |
See specific message contents ii). |
8 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
9 |
MS -> SS |
CHANNEL REQUEST |
with establishment cause set to "Other procedures which can be completed with an SDCCH". |
10 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
11 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
12 |
SS -> MS |
CM SERVICE ACCEPT |
|
13 |
MS -> SS |
REGISTER |
Operation code is set to "ProcessUnstructuredSS-Data". See specific message content i). |
14 |
SS -> MS |
RELEASE COMPLETE |
normal release of the transaction. See iiia). |
15 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
16 |
MS |
The user presses appropriate MMI keys to initiate the desired undefined supplementary service. |
|
17 |
MS -> SS |
CHANNEL REQUEST |
with establishment cause set to "Other procedures which can be completed with an SDCCH". |
18 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
19 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
20 |
SS -> MS |
CM SERVICE ACCEPT |
|
21 |
MS -> SS |
REGISTER |
See specific message contents i).Operation code is set to "ProcessUnstructureSS- Request". See i). |
22 |
SS -> MS |
RELEASE COMPLETE |
see iii).cause is set to "facility rejected" |
23 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
24 |
MS -> SS |
CHANNEL REQUEST |
with establishment cause set to "Other procedures which can be completed with an SDCCH". |
25 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
|
26 |
MS -> SS |
CM SERVICE REQUEST |
"Supplementary service activation". |
27 |
SS -> MS |
CM SERVICE ACCEPT |
|
28 |
MS -> SS |
REGISTER |
Operation code is "ProcessUnstructuredSSdata". See specific message contents i). |
29 |
SS -> MS |
RELEASE COMPLETE |
normal release of the transaction. See iiia). |
30 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
For k=1 to 10, go through steps 31 to 40. Counter k deals with different kinds of general and invoke problems in step 36. |
|||
31 |
MS |
The MS is brought to state U10 by initiating a Mobile originating call |
|
32 |
Specific MMI keys are pressed to initiate the desired undefined supplementary service. DTMF signalling may occur. |
||
33 |
MS -> SS |
CM SERVICE REQUEST |
"supplementary service activation" |
34 |
SS -> MS |
CM SERVICE ACCEPT |
|
35 |
MS -> SS |
REGISTER |
The MS starts the transaction on the radio interface. See specific message contents i).The operation code is set to "ProcessUnstructuredSS-Request". |
36 |
SS -> MS |
RELEASE COMPLETE |
different errors and problems are sent. See specific message contents iiib) and iiic). |
37 |
SS -> MS |
DISCONNECT |
|
38 |
MS -> SS |
RELEASE |
|
39 |
SS -> MS |
RELEASE COMPLETE |
See message contents iv). |
40 |
SS -> MS |
CHANNEL RELEASE |
The main signalling link is released. |
Specific message contents.
i) REGISTER message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
|
Register message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
SS version indicator |
As specified in 3GPP TS 04.80 for version 2 protocol Always omitted for version 1 protocol |
For steps 6, 21 and 35, Facility Information Element with Invoke = ProcessUnstructuredSS-Request (for version 2 protocol) component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
For steps 13 and 28, Facility Information Element with Invoke = ProcessUnstructuredSS-Data (for version 1 protocol) as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Invoke from 3GPP TS 04.80 |
Component length |
Depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
Arbitrary (1 octet) |
Operation Code tag |
From 3GPP TS 04.80 |
Operation Code length |
1 |
Operation Code |
ProcessUnstructuredSS-Request (for version 2 protocol) ProcessUnstructuredSS-Data (for version 1 protocol) |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" |
ussd-string |
*70*635*562# |
ii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
Set to "Supplementary service (call independent)" |
Transaction identifier |
The transaction value is the same as the REGISTER transaction value but the transaction flag is different |
Facility message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
Facility Information Element with Reject = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.6.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Reject from 3GPP TS 04.80 |
Component length |
Depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
Problem Code tag |
As 3GPP TS 04.80 |
Problem Code length |
|
General Problem code |
Unrecognized operation |
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
Set to "Supplementary service (call independent)" |
Transaction identifier |
The transaction value is the same as the REGISTER transaction value but the transaction flag is different |
Release complete message type |
As 3GPP TS 04.80 |
Cause |
For step 22, cause is set to "facility rejected" and FIE is omitted. For steps 14, 29 and 36 this field is omitted. |
Facility Information Element |
For step 14 and 29 see iiia). For step 36 see iiib) and iiic). For step 22 this field is omitted. |
iiia) For steps 14 and 29, Facility Information Element with Return Result = ProcessUnstructuredSS-Data component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
ReturnResult from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Data |
Sequence Tag |
As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 |
Sequence length |
As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 |
Operation Code Tag |
As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 |
Operation Code Length |
As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 |
Operation Code |
ProcessUnstructuredSS-Data |
Parameters |
As 3GPP TS 04.80 / 3GPP TS 24.080 Table 3.4 |
iiib) Facility Information Element with Return Error = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Error from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
Error Code tag |
As 3GPP TS 04.80 |
Error Code length |
|
Error Code |
k=1, system failure k=2, data missing k=3, unknown alphabet k=4, unexpected data value |
iiic) Facility Information Element with Reject = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.6.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Reject from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
Problem Code tag |
As 3GPP TS 04.80 |
Problem Code length |
|
General Problem code Invoke Problem code |
k=5, Unrecognized component k=6, Mistyped component k=7, Badly structured component k=8, Mistyped parameter k=9, Resource limitation k=10, Initiating release |
iv) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
Set to "Supplementary service (call control)" |
Transaction identifier |
Same as current call. |
Release Complete message type |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
31.9.2 Network initiated unstructured supplementary service operations
31.9.2.1 UnstructuredSS-Notify/accepted
Conformance requirements
1) For a USSD notification, the MS shall display the text provided and await user input. The MS shall acknowledge the operation by sending a FACILITY message containing an empty result component to the network.
2) The MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified".
3) At any stage while the MS is registered with a network, the network may send an unstructured string to the MS. So, the MS shall be able to process the operation during a call or out of a call.
References
Conformance requirement 1: 3GPP TS 04.90 subclause 5.2.1.
Conformance requirement 2: 3GPP TS 02.90 subclause 4.2.2.
Conformance requirement 3: 3GPP TS 02.90 subclause 4.2.1.
Test Purpose
1) To verify that for a USSD notification, the MS shall display the text provided and await user input. If the user enters a response, the MS shall acknowledge the operation by sending a FACILITY message containing an empty result component to the network.
2) To verify that the MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified".
3) To check that the MS shall be able to process the operation during a call or out of a call.
Specific PICS Statements
–
PIXIT Statements
–
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
– The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to ProcessUnstructuredSS-Notify. The user checks that the ussd string sent by the SS is correctly displayed by the MS. The MS has to send a FACILITY message with an empty return result component.
– Then the SS originates a call to the MS. When the MS is in the U10 state, the SS releases the transaction identifier concerning USSD transaction by sending a RELEASE COMPLETE. The SS initiates a new ussd transaction by sending a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Notify. The user checks that the ussd string sent by the SS is correctly displayed by the MS. The MS has to send a FACILITY message with an empty return result component. Finally the SS releases both MM connections and the radio link.
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
a SDCCH is allocated to the MS. |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
REGISTER |
initiation of the transaction concerning the USSD notification operation. See i). |
6 |
The MS has to display the USSD string sent from the network. |
||
7 |
MS -> SS |
FACILITY |
signalling message sent by the MS as the response. The SS checks that it matches ii). |
8 |
SS -> MS |
SETUP |
incoming call. |
9 |
MS -> SS |
CALL CONFIRMED |
|
10 |
MS -> SS |
ALERTING |
|
11 |
MS -> SS |
CONNECT |
|
12 |
SS -> MS |
ASSIGNMENT COMMAND |
a TCH is allocated to the MS. |
13 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
14 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
15 |
SS -> MS |
RELEASE COMPLETE |
this message releases the transaction concerning the USSD operation. See iii). |
16 |
SS -> MS |
REGISTER |
initiation of a USS request operation during a call. See specific message contents i). |
17 |
The MS has to display the USSD string received from the SS. |
||
18 |
MS -> SS |
FACILITY |
The SS checks that this message matches ii). |
19 |
SS -> MS |
RELEASE COMPLETE |
It releases he transaction identifier concerning the ussd operation. |
20 |
SS -> MS |
DISCONNECT |
call release initiation. see iv). |
21 |
MS -> SS |
RELEASE |
|
22 |
SS -> MS |
RELEASE COMPLETE |
|
23 |
SS -> MS |
CHANNEL RELEASE |
Specific message contents.
i) REGISTER message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
|
Register message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
Facility Information Element with Invoke = UnstructuredSS-Notify component type as defined in 3GPP TS 04.90, subclause 5.2.1.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Invoke from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
Arbitrary (1 octet) |
Operation Code tag |
From 3GPP TS 04.80 |
Operation Code length |
1 |
Operation Code |
UnstructuredSS-Notify |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" |
ussd-string |
arbitrary chosen by the SS |
ii) Facility message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
the transaction value is the same as REGISTER transaction value but the transaction flag is different |
Facility message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
Facility Information Element with Return Result = empty result component according to 3GPP TS 04.90, subclause 5.2.1, figure 5.3.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify |
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
the transaction value is the same as REGISTER transaction flag is different |
Release Complete message type |
As 3GPP TS 04.80 |
Facility Information Element |
omitted |
iv) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call control)" |
Transaction identifier |
same as current call. |
Release Complete message type |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
31.9.2.2 UnstructuredSS-Notify/rejected on user busy
Conformance requirements
1) When the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error.
References
Conformance requirement 1: 3GPP TS 04.90 subclause 5.1.1.
Test Purpose
1) To verify that when the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it responds with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error.
Specific PICS Statements
–
PIXIT Statements
–
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
– The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Notify. The SS initiates an other USSD transaction by sending a REGISTER message with transaction identifier different form the previous one. The SS checks that the MS answers with a RELEASE COMPLETE message with an error component set to "USSD busy". Then the SS releases the radio link.
Test Procedure
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
a SDCCH is allocated to the MS. |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
REGISTER |
initiation of the transaction concerning the USSD notification operation. See i). |
6 |
The MS has to display the USSD string sent from the SS. |
||
7 |
MS -> SS |
FACILITY |
See ii). |
8 |
SS -> MS |
REGISTER |
initiation of an other USSD notification. The transaction identifier is different from that in step 5.See i). |
9 |
MS -> SS |
RELEASE COMPLETE |
error set to "USSD busy". Transaction initiated in step 6 by the network is rejected by the MS. See iii). |
10 |
SS -> MS |
RELEASE COMPLETE |
normal release of transaction initiated in step 5.See iii). |
11 |
SS -> MS |
CHANNEL RELEASE |
release of the main signalling link. |
Specific message contents.
i) REGISTER message.
See subclause 31.9.2.1.
ii) FACILITY message.
See subclause 31.9.2.1.
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
for step 10, same as REGISTER transaction identifier for step 9, the transaction value is the same as REGISTER transaction value but the transaction flag is different. |
Release complete message type |
As 3GPP TS 04.80 |
Facility Information Element |
for step 9 see iiib). for step 10, see iiia). |
iiia) Facility Information Element with Return Result = UnstructuredSS-Notify component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify in step 5 |
iiib) Facility Information Element with Return Error = UnstructuredSS-Notify component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 |
Length of FIE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
|
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify in step 8 |
Error Code tag |
As 3GPP TS 04.80 |
Error Code length |
|
Error Code |
USSD Busy |
31.9.2.3 UnstructuredSS-Request/accepted
Conformance requirements
1) For a USSD request, the MS shall display the text provided and await user input. if the user enters a response, the MS shall return the response to the network, maintaining the transaction.
2) The MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified".
3) At any stage while the MS is registered with a network, the network may send an unstructured string to the MS. So, the MS shall be able to process the operation during a call or out of a call.
References
Conformance requirement 1: 3GPP TS 03.90 subclause 5.2.5.
Conformance requirement 2: 3GPP TS 02.90 subclause 4.2.2.
Conformance requirement 3: 3GPP TS 02.90 subclause 4.2.1.
Test Purpose
1) To test that, for a USSD request, the MS shall display the text provided and await user input. if the user enters a response, the MS shall return the response to the network, maintaining the transaction.
2) To verify that the MS shall include alphabet and language indicators in the response to the network. The alphabet indicator shall indicate "SMS default alphabet". The language indicator shall indicate "language unspecified".
3) To check that the MS shall be able to process the operation during a call or out of a call.
Specific PICS Statements
–
PIXIT Statements
–
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
– The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to ProcessUnstructuredSS-Request. The user checks that the ussd string sent by the SS is correctly displayed by the MS and answers the request by depressing MMI keys. Then the MS has to send a FACILITY message with ussd string exactly containing the digits and symbols expressed on the mobile equipment keypad.
– Then the SS originates a call to the MS. When the MS is in the U10 state, the SS releases the transaction identifier concerning USSD transaction by sending a RELEASE COMPLETE. The SS initiates a new ussd transaction by sending a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Request. The user checks that the ussd string sent by the SS is correctly displayed by the MS and answers the request by depressing MMI keys. Then the MS has to send a FACILITY message with ussd string exactly containing the digits and symbols expressed on the mobile equipment keypad. Finally the SS releases both MM connections and the radio link.
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
a SDCCH is allocated to the MS. |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
REGISTER |
initiation of the transaction concerning the USSD Request operation. See i). |
6 |
The MS has to display the USSD string sent from the network and waits for the user response. By depressing MMI keys followed by SEND the user answers |
||
7 |
MS -> SS |
FACILITY |
signalling message sent by the MS as the response. See ii). |
8 |
SS -> MS |
SETUP |
incoming call. |
9 |
MS -> SS |
CALL CONFIRMED |
|
10 |
MS -> SS |
ALERTING |
|
11 |
MS -> SS |
CONNECT |
|
12 |
SS -> MS |
ASSIGNMENT COMMAND |
a TCH is allocated to the MS. |
13 |
MS -> SS |
ASSIGNMENT COMPLETE |
|
14 |
SS -> MS |
CONNECT ACKNOWLEDGE |
|
15 |
SS -> MS |
RELEASE COMPLETE |
this message releases the transaction concerning the USSD operation. See iii). |
16 |
SS -> MS |
REGISTER |
initiation of a USS request operation during a call. See specific message contents i). |
17 |
The MS has to display the USSD string received from the SS. By depressing MMI keys followed by SEND, the user answers. DTMF signalling may occur. |
||
18 |
MS -> SS |
FACILITY |
See ii). |
19 |
SS -> MS |
RELEASE COMPLETE |
It releases the transaction identifier concerning the ussd operation. |
20 |
SS -> MS |
DISCONNECT |
|
21 |
MS -> SS |
RELEASE |
|
22 |
SS -> MS |
RELEASE COMPLETE |
call release initiation. see iv). |
23 |
SS -> MS |
CHANNEL RELEASE |
Specific message contents
i) REGISTER message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
|
Register message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
Facility Information Element with Invoke = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.3.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Invoke from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
Arbitrary (1 octet) |
Operation Code tag |
From 3GPP TS 04.80 |
Operation Code length |
1 |
Operation Code |
UnstructuredSS-Request |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" |
ussd-string |
arbitrary chosen by the SS |
ii) Facility message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
the transaction identifier value is the same as REGISTER transaction value but the transaction flag is different. |
Facility message type |
As 3GPP TS 04.80 |
Facility Information Element |
See below |
Facility Information Element with Return Result = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Request |
Sequence Identifier |
|
Sequence length |
|
Operation Code tag |
1 |
Operation Code length |
1 |
Operation Code |
UnstructuredSS-Request |
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined" |
ussd-string |
contains exactly the digits and symbols expressed on the mobile equipment keypad. |
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
same as REGISTER transaction identifier |
Release Complete message type |
As 3GPP TS 04.80 |
Facility Information Element |
omitted |
iv) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call control)" |
Transaction identifier |
same as current call. |
Release Complete message type |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
31.9.2.4 UnstructuredSS-Request/rejected on user busy
Conformance requirements
1) When the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error.
References
Conformance requirement 1: 3GPP TS 04.90 subclause 5.1.1.
Test Purpose
1) To verify that when the mobile station receives an USSD operation in parallel to any call independent supplementary transaction, it responds with a return error component in a RELEASE COMPLETE message, containing the "USSD-Busy" error.
Specific PICS Statements
–
PIXIT Statements
–
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in the MM-state "idle updated".
Foreseen final state of the MS
MM-state "idle updated".
Test Procedure
– The MS is paged and a RR-connection is established. Then, the SS sends a REGISTER message containing a facility information element with operation code set to UnstructuredSS-Request. The SS initiates an other USSD transaction by sending a REGISTER message with transaction identifier different form the previous one. The SS checks that the MS answers with a RELEASE COMPLETE message with an error component set to "USSD busy". Then the SS releases the radio link.
Test Procedure
Step |
Direction |
Message |
Comments |
1 |
SS -> MS |
PAGING REQUEST TYPE 1 |
|
2 |
MS -> SS |
CHANNEL REQUEST |
|
3 |
SS -> MS |
IMMEDIATE ASSIGNMENT |
a SDCCH is allocated to the MS. |
4 |
MS -> SS |
PAGING RESPONSE |
|
5 |
SS -> MS |
REGISTER |
initiation of the transaction concerning the USSD Request operation. See i). |
6 |
The MS has to display the USSD string sent from the network and waits for the user response. By depressing MMI keys followed by SEND the user answers. |
||
7 |
MS -> SS |
FACILITY |
signalling message sent by the MS as the response to the request. See ii). |
8 |
SS -> MS |
REGISTER |
initiation of an other USSD request. The transaction identifier is different from that in step 5.See i). |
9 |
MS -> SS |
RELEASE COMPLETE |
error set to "USSD busy". Transaction initiated in step 6 by the network is rejected by the MS. See iii). |
10 |
SS -> MS |
RELEASE COMPLETE |
normal release of transaction initiated in step 5. See iii). |
11 |
SS -> MS |
CHANNEL RELEASE |
release of the main signalling link. |
Specific message contents
i) REGISTER message.
See subclause 31.9.2.3.
ii) FACILITY message.
See subclause 31.9.2.3.
iii) RELEASE COMPLETE message.
Contents |
Value/remark |
Protocol Discriminator |
set to "Supplementary service (call independent)" |
Transaction identifier |
the transaction identifier value is the same as REGISTER transaction value but the transaction flag is different. |
Release complete message type |
As 3GPP TS 04.80 |
Facility Information Element |
for step 9 see iiib). |
iiia) Facility Information Element with Return Result = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.4.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Result from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Request |
iiib) Facility Information Element with Return Error = UnstructuredSS-Request component type as defined in 3GPP TS 04.80 subclause 3.6.1 table 3.5.
Contents |
Value/remark |
Facility IE identifier |
As 3GPP TS 04.08 / 3GPP TS 24.008 |
Length of FIE contents |
|
Component type tag |
Return Error from 3GPP TS 04.80 |
Component length |
depending on the length of ussd-string |
InvokeID tag |
From 3GPP TS 04.80 |
Invoke ID length |
1 |
Invoke ID |
The same as the invoke of the UnstructuredSS-Request |
Error Code tag |
As 3GPP TS 04.80 |
Error Code length |
|
Error Code |
USSD Busy |