15.9 USSD
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
15.9.1 ProcessUnstructuredSS-request/accepted
15.9.1.1 Definition
15.9.1.2 Conformance requirements
1) The MS invokes an USSD request by sending a REGISTER message to the network containing a ProcessUnstructuredSS‑Request invoke component.
…
When the application terminates the dialogue, the network shall clear the transaction by sending a RELEASE COMPLETE message containing a return result component. The MS may also clear the transaction at any time by sending a RELEASE COMPLETE message upon request of the user.
…
The MS shall not initiate USSD operations in parallel to any call independent supplementary service transaction. Only one transaction for USSD operations per user is allowed at a time. However, the MS is allowed to initiate USSD operations in parallel to call related transactions.
2) If the user enters an MMI string that, according to TS 22.030 [3], should be treated as USSD, the UE shall send this string to the network using the appropriate operation from TS 24.080 [5].
The mobile initiated operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the user.
The UE may initiate an USSD operation either during a call or out of call.
3) For supplementary service procedures independent of any call, the initiating side must establish a MM‑connection between the network and the MS according to the rules given in 3GPP TS 24.007 and 3GPP TS 24.008. The call independent supplementary service procedures shall apply to both CS and PS domain for some specific services. On PS domain, a PS-signalling connection shall be established between the network and the MS instead of a MM-connection. Throughout this specification, the term MM-connection is used to denote a MM-connection for CS domain or PS-signalling connection for PS domain, as appropriate. The MS or the network starts the transaction by transferring a REGISTER message across the radio interface. This transaction is identified by the transaction identifier associated with the REGISTER message, and the Invoke identifier present in the component part of the Facility information element. Following the REGISTER message one or more FACILITY messages may be transmitted, all of them related by the use of the same transaction identifier. If the transaction is no longer used, it shall be released by sending a RELEASE COMPLETE message. This procedure is specified in detail in clause 3, and the text in clause 3 takes precedence over this introduction.
To convey the supplementary service invocation, the Facility information element is used. The Facility information element present either in the REGISTER message or a subsequent message identifies the supplementary service involved and the type of component (i.e. Invoke, Return result, Return error or Reject component).
When the REGISTER or FACILITY message contains a Facility information element and the requested service is available, a FACILITY message containing a Facility information element may be returned. One or more exchanges of FACILITY messages may subsequently occur. To terminate the service interaction and release the transaction identifier value, a RELEASE COMPLETE message is sent as specified for the specific supplementary service procedure. The RELEASE COMPLETE message may also contain the Facility information element.
4) The following sequence of functions shall be used for the control of Supplementary Services:
SELECT: Entry of the procedure information (may be a digit or a sequence of characters).
SEND: Transmission of the information to the network.
INDICATION: Call progress indications.
The UE shall support the MMI procedure specified as:
Activation : *SC*SI#
Deactivation : #SC*SI#
Interrogation : *#SC*SI#
Registration : *SC*SI# and **SC*SI#
Erasure : ##SC*SI#
This structure consists of the following parts:
– Service Code, SC( (2 or 3 digits);
– Supplementary Information, SI (variable length).
The procedure always starts with *, #, **, ## or *# and is finished by #. Each part within the procedure is separated by *.
The service code uniquely specifies the Supplementary Service, either as a defined Supplementary Service or as a spare service code. All spare service codes shall be reserved for future use.
The UE shall determine from the context whether, an entry of a single *, activation or registration was intended.
For example, a call forwarding request with a single * would be interpreted as registration if containing a forwarded-to number, or an activation if not.
The supplementary information (SI) may comprise e.g. a PIN code or Directory Number. Where a particular service request does not require any SI, "*SI" is not entered, e.g. Activation becomes *SC#SEND. Where further supplementary information is required this is again entered as *SI, e.g. *SC*SIA*SIB#SEND. SIB may be used to specify the tele or bearer service expressed as a Basic Service Group to which this supplementary service request applies, SIC may be used to specify the value of the "No Reply Condition Timer".
Use of SIA, SIB, SIC for a particular procedure is optional. The procedure to be adopted where these are not all used is as follows:
*SI# shall be entered in any of the following formats:
* SIA * SIB * SIC #
* SIA * SIB #
* SIA * * SIC #
* SIA #
* * SIb * SIC #
* * SIB #
* * * SIC #
#
The denotation of the Supplementary Information and the order of entry are specified in annex B. Supplementary Information Codes for the Teleservices and Bearer Services are given in annex C.
The following procedures shall be used for application of supplementary services to the call set-up procedure:
*SCn*SI#DN SEND;
where SC is the service code defined in annex B and *SI is an optional field which may be applicable to service SC. The "n" is a single digit used to indicate the numbering plan, profile, priority, etc. according to the service being applied. For simplicity of presentation, the leading * is shown on the assumption that the action is to activate (switch on) the required service. However, for a deactivation (or switch off), this would become:
#SCn*SI#DN SEND;
It is assumed that the *# (interrogation) will not apply to call set-up.
Where more than one supplementary service is applicable to the call set-up, these shall be concatenated with any applicable supplementary information immediately following the applicable service code.
For example, if SCn and SI refer to one applicable supplementary service and scn and si to another, then the generic procedure becomes:
*SCn*SI#scn*si#DN SEND.
NOTE 1: The order of entry of SC and sc is a user option, provided that any supplementary information follows immediately after the relevant SC.
Where SI is not applicable according to the definition of the supplementary service, then *SI is omitted. Where its use is optional, but not selected for a particular call set-up, it may be omitted or entered as an extra * if this is necessary to avoid ambiguity of interpretation.
NOTE 2: By using the # as a separator, most cases are expected to be unambiguous.
5) When the user or the application in the MS makes a request which the MS determines is to make use of USSD, the MS shall set up a transaction to the network, send the request to the MSC and await a response. When the MS receives the response, it shall display the information contained to the user or relay the message to the application in the MS.
While awaiting the response, the MS may receive a network initiated USSD request or notification on the same transaction. If this occurs, the MS shall process that operation (see section 1) and continue to await the response to the mobile initiated request.
If, when the MS determines that a user request is to make use of USSD, the MS is already involved in a USSD or a non-call related supplementary service transaction, the MS shall reject the request.
References
TS 24.090 subclause 6.1
TS 22.090 subclause 4.1.1
TS 24.010 subclause 2.2.5.1
TS 22.030 subclause 6.5.2
TS 23.090 subclause 6.2.1
15.9.1.3 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 information included)
*NN(N)*SIA*SIB# (two fields of supplementary information 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 22.030
NN(N) features a set of service codes which have not yet been allocated for GSM supplementary services (see GSM 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 23.038 default alphabet followed by "SEND" shall be interpreted by the UE as an USSD request unless the UE is not engaged in a call and the first of the two character entry followed by "SEND" is a "1".
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 24.007 and 3GPP TS 24.008.
4) To verify that, within a call the UE shall transmit a USSD request if any. See 3GPP TS 24.007 and 3GPP TS 24.008 for the handling of multiple MM connections.
5) To check that upon receipt of the RELEASE COMPLETE message, the UE shall display the information contained to the user in a way described by the manufacturer.
15.9.1.4 Method of test
Related PICS/PIXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of USSD Yes/No.
Description of the user’s commands and of display of USSD.
Initial Conditions
System Simulator:
– 1 cell, default parameters.
User Equipment:
– The UE is in the MM-state "idle updated".
Test Procedure
By means of appropriate user action the mobile is made to initiate an Unstructured SS data operation. The mobile first establishes a MM-connection with the SS, and sends a REGISTER message. Upon receipt of this message, the system simulator answers with the RELEASE COMPLETE message.
The mobile station is triggered to originate a call. After the UE has sent a CONNECT ACKNOWLEDGE, the mobile is triggered 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 RELEASE COMPLETE message to the UE.
Expected Sequence
The sequence is executed for execution counters c=1,..,17.
Counter c determines the ussd-string selected by the user and sent by the UE (see specific message contents concerning the REGISTER message).
|
Step |
|
Message |
Comments |
||||
|
1 |
UE |
UE is triggered to initiate the unstructured SS data operation. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”. |
|||||
|
2 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
||||
|
3 |
<– |
AUTHENTICATION REQUEST |
|||||
|
4 |
–> |
AUTHENTICATION RESPONSE |
|||||
|
5 |
SS |
The SS starts integrity protection |
|||||
|
6 |
–> |
REGISTER |
|||||
|
7 |
<– |
RELEASE COMPLETE |
|||||
|
8 |
SS |
The SS releases the RRC connection |
|||||
|
9 |
SS |
It is checked that the ussd string is displayed by the UE using appropriate user action. |
|||||
|
10 |
Void |
||||||
|
11 |
UE |
The UE is made to trigger a MO Call |
|||||
|
12 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Conversational Call”. |
|||||
|
13 |
–> |
CM SERVICE REQUEST |
"mobile originating call" |
||||
|
14 |
<– |
AUTHENTICATION REQUEST |
|||||
|
15 |
–> |
AUTHENTICATION RESPONSE |
|||||
|
16 |
<– |
SECURITY MODE COMMAND |
|||||
|
17 |
–> |
SECURITY MODE COMPLETE |
The SS starts integrity protection |
||||
|
18 |
–> |
SETUP |
|||||
|
19 |
<– |
CALL PROCEEDING |
|||||
|
20 |
<– |
ALERTING |
|||||
|
21 |
<– |
CONNECT |
|||||
|
22 |
–> |
CONNECT ACKNOWLEDGE |
|||||
|
23 |
User action to initiate the desired undefined SS service operation. |
||||||
|
24 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
||||
|
25 |
<– |
CM SERVICE ACCEPT |
|||||
|
26 |
–> |
REGISTER |
The UE starts the transaction on the radio interface. |
||||
|
27 |
<– |
RELEASE COMPLETE |
|||||
|
28 |
SS |
The SS releases the RRC connection |
|||||
|
29 |
SS |
It is checked that the ussd string is displayed by the UE using appropriate user action |
|||||
|
30 |
<– |
DISCONNECT |
|||||
|
31 |
–> |
RELEASE |
|||||
|
32 |
<– |
RELEASE COMPLETE |
|||||
|
33 |
SS |
The SS releases the RRC connection. |
|||||
Specific message contents:
REGISTER (Steps 6 and 26)
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "Supplementary service (call independent)" |
|
Transaction identifier |
|
|
Register message type |
‘xx 111011’B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
|
Facility Information Element |
See below |
|
SS version indicator |
Not checked |
Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in GSM 04.80 section 3.6.1 table 3.3.
|
Contents |
Value/remark |
|
Facility IE identifier |
‘00011100’B |
|
Length of FIE contents |
|
|
Component type tag |
‘10100001’B |
|
Component length |
depending on the length of ussd-string |
|
InvokeID tag |
‘00000010’B |
|
Invoke ID length |
1 |
|
Invoke ID |
Arbitrary (1 octet) |
|
Operation Code tag |
‘00000010’B |
|
Operation Code length |
1 |
|
Operation Code |
ProcessUnstructuredSS-Request |
|
ussd-dataCodingScheme |
1 octet long. Alphabet indicator set to "default alphabet". |
|
ussd-string |
c=1, *60# (Activation with no supplementary information included) |
RELEASE COMPLETE (steps 7 and 27)
|
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 |
‘00101010’B |
|
Cause |
Omitted |
|
Facility Information Element |
See below |
Facility information element with Return Result = ProcessUnstructuredSS-Request component type as defined in GSM 04.80 section 3.6.1 table 3.4.
|
Contents |
Value/remark |
|
Facility IE identifier |
‘00011100’B |
|
Length of IE contents |
|
|
Component type tag |
‘10100001’B |
|
Component length |
depending on the length of the ussd-string |
|
Invoke ID tag |
‘00000010’B |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS-Request |
|
Operation Code tag |
‘00000010’B |
|
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 |
RELEASE COMPLETE (Step 32)
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "call control; call related SS messages" |
|
Transaction identifier |
Same as current call. |
|
Release Complete message type |
‘00101010’B |
15.9.1.5 Test requirements
1) At steps 6 and 26, the UE shall send a REGISTER message with the Invoke component ProcessUnstructuredSS-Request.
2) At steps 9 and 29, the UE shall send display the ussd string to the user.
3) At step 24, the UE shall send a CM SERVICE REQUEST message with the service type "Supplementary service activation".
15.9.2 ProcessUnstructuredSS-request/cross phase compatibility and error handling
15.9.2.1 Definition
15.9.2.2 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 MS shall assume that the network only supports protocol version 1 of USSD operations. The MS 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 UE 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 24.090 subclause 6.2.1.
Conformance requirement2: 3GPP TS 23.090.
15.9.2.3 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 UE 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).
15.9.2.4 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The UE is in the MM-state "idle updated".
Foreseen final state of the UE
MM-state "idle updated".
Related ICS/IXIT Statements
– Support of FDD Yes/No.
– Support of CS speech Yes/No.
– Support of USSD.
– Description of the user’s commands and of display of USSD.
– Full rate supported.
– Supported teleservices.
– Support of active state of the call control protocol (U10).
Test Procedure
With appropriate MMI or AT command, UE is triggered 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 RRC signalling connection is released. Then the SS checks that the UE 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 signalling link is released.
With appropriate MMI or AT command, UE is triggered 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 UE 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 signalling link is released.
The mobile station is forced to originate a call. After the UE has sent a CONNECT ACKNOWLEDGE, With appropriate MMI or AT command, UE is triggered 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 UE a RRC CONNECTION RELEASE message. This subtest is repeated with different errors and problems in the RELEASE COMPLETE message.
Expected Sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
UE |
Trigger UE to initiate the ProcessUnstructuredSS-Request undefined supplementary service operation using appropriate MMI or AT commands |
||
|
2 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”. |
||
|
3 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
|
|
3A |
<- |
AUTHENTICATION REQUEST |
||
|
3B |
-> |
AUTHENTICATION RESPONSE |
||
|
4 |
SS |
The SS starts integrity protection. |
||
|
5 |
–> |
REGISTER |
Operation code set to "ProcessUnstructuredSS-Request" |
|
|
6 |
<– |
RELEASE COMPLETE |
Reject – Unrecognized operation |
|
|
7 |
SS |
The SS releases the RRC connection. |
||
|
8 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”. |
||
|
9 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
|
|
10 |
SS |
The SS starts integrity protection. |
||
|
11 |
–> |
REGISTER |
Operation code set to "ProcessUnstructuredSS-Data" |
|
|
12 |
<– |
RELEASE COMPLETE |
normal release of the transaction |
|
|
13 |
SS |
The SS releases the RRC connection. |
||
|
14 |
SS |
It is checked that the ussd string is displayed by the UE using appropriate user action |
||
|
15 |
SS |
Trigger UE to initiate the ProcessUnstructuredSS-Request undefined supplementary service operation using appropriate MMI or AT commands |
||
|
16 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”. |
||
|
17 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
|
|
18 |
SS |
The SS starts integrity protection. |
||
|
19 |
–> |
REGISTER |
Operation code set to "ProcessUnstructuredSS-Request" |
|
|
20 |
<– |
RELEASE COMPLETE |
||
|
21 |
SS |
The SS releases the RRC connection. |
||
|
22 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating High Priority Signalling”. |
||
|
23 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
|
|
24 |
SS |
The SS starts integrity protection. |
||
|
25 |
–> |
REGISTER |
Operation code set to "ProcessUnstructuredSS-Data" |
|
|
26 |
<– |
RELEASE COMPLETE |
normal release of the transaction |
|
|
27 |
SS |
The SS releases the RRC connection. |
||
|
28 |
SS |
It is checked that the ussd string is displayed by the UE using appropriate user action |
||
|
29 |
For k=1 to 10, go through steps 30 to 39. Counter k deals with different kinds of general and invoke problems in step 35. |
|||
|
30 |
UE |
The UE is brought to CC state U10 by initiating a Mobile originating speech call |
||
|
31 |
Trigger UE to initiate the ProcessUnstructuredSS-Request undefined supplementary service operation using appropriate MMI or AT commands |
|||
|
32 |
–> |
CM SERVICE REQUEST |
"Supplementary service activation". |
|
|
33 |
<– |
CM SERVICE ACCEPT |
||
|
34 |
–> |
REGISTER |
The operation code is set to "ProcessUnstructuredSS-Request". |
|
|
35 |
<– |
RELEASE COMPLETE |
different errors and problems are sent. See specific message contents iiib) and iiic). |
|
|
36 |
<– |
DISCONNECT |
Disconnect CC call |
|
|
37 |
–> |
RELEASE |
CC |
|
|
38 |
<– |
RELEASE COMPLETE |
CC |
|
|
39 |
SS |
The SS releases the RRC connection |
||
Specific message contents.
REGISTER (steps 5, 11, 19, 25 and 34)
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "Supplementary service (call independent)" |
|
Transaction identifier |
|
|
Register message type |
As 3GPP TS 24.080 |
|
Facility Information Element |
See below |
|
SS version indicator |
As specified in 3GPP TS 24.080 for version 2 protocol Always omitted for version 1 protocol |
For steps 5, 19 and 34, Facility Information Element with Invoke = ProcessUnstructuredSS-Request (for version 2 protocol) component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.
For steps 11 and 25, Facility Information Element with Invoke = ProcessUnstructuredSS-Data (for version 1 protocol) as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.
|
Contents |
Value/remark |
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Invoke from 3GPP TS 24.080 |
|
Component length |
Depending on the length of ussd-string |
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
Arbitrary (1 octet) |
|
Operation Code tag |
From 3GPP TS 24.080 |
|
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# |
RELEASE COMPLETE (step 6)
|
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 24.080 |
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Reject |
|
Component length |
Depending on the length of ussd-string |
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
|
Problem Code tag |
As 3GPP TS 24.080 |
|
Problem Code length |
1 |
|
General Problem code |
Unrecognized operation |
RELEASE COMPLETE (Steps 12, 26)
|
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 24.080 |
|
Cause |
This field is omitted. |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Return Result from 3GPP TS 24.080 |
|
Component length |
|
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Data |
|
Sequence Tag |
As 3GPP TS 24.080 Table 3.4 |
|
Sequence length |
As 3GPP TS 24.080 Table 3.4 |
|
Operation Code Tag |
As 3GPP TS 24.080 Table 3.4 |
|
Operation Code Length |
As 3GPP TS 24.080 Table 3.4 |
|
Operation Code |
ProcessUnstructuredSS-Data |
|
Parameters |
As 3GPP TS 24.080 Table 3.4 |
RELEASE COMPLETE (Step 20)
|
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 24.080 |
|
Cause |
Coding standard is set to “11”B and cause value is set to "facility rejected" |
|
Facility Information Element |
omitted |
RELEASE COMPLETE (step 35, k=1, k=2, k=3, k=4)
|
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 24.080 |
|
Cause |
omitted. |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Return Error from 3GPP TS 24.080 |
|
Component length |
|
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
|
Error Code tag |
As 3GPP TS 24.080 |
|
Error Code length |
|
|
Error Code |
k=1, system failure k=2, data missing k=3, unknown alphabet k=4, unexpected data value |
RELEASE COMPLETE (step 35, k=5, k=6, k=7, k=8, k=9, k=10)
|
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 24.080 |
|
Cause |
omitted. |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Reject from 3GPP TS 24.080 |
|
Component length |
|
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the ProcessUnstructuredSS- Request |
|
Problem Code tag |
As 3GPP TS 24.080 |
|
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 |
15.9.2.5 Test requirements
1) At steps 11 and 25, the UE shall send a REGISTER message with the Invoke component “ProcessUnstructuredSS-Data”.
2) At step 34, the UE shall send a REGISTER message with the Invoke component operation code is set to "ProcessUnstructuredSS-Request".
15.9.3 UnstructuredSS-Notify/accepted
15.9.3.1 Definition
15.9.3.2 Conformance requirements
1) The network invokes an USSD notification by sending a REGISTER message to the MS containing a UnstructuredSS‑Notify invoke component.
The MS shall acknowledge the operation by sending a FACILITY message containing an empty result component to the network. The application may either continue or terminate the dialogue.
When the application continues the dialogue, it may initiate another USSD operation by sending a FACILITY message (see figure 5.4). The operation may either be an USSD request (see subclause 5.1.1) or notification.
When the application terminates the dialogue, the network shall clear the transaction by sending a RELEASE COMPLETE message. The MS may also clear the transaction at any time by sending a RELEASE COMPLETE message upon request of the user.
If the MS is unable to process the request received from the network, it shall return an error indication by sending a FACILITY message containing a return error component. Error values are specified in 3GPP TS 24.080.
When the MS receives an USSD operation in parallel to any call independent supplementary service transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD‑Busy" error as specified in 3GPP TS 24.080, to indicate the failure in handling a parallel USSD operation. However, the network is allowed to initiate USSD operations in parallel to call related transactions.
2) The UE shall include alphabet and language indicators in the response to the network (if any).
3) At any stage while the UE is registered with a network, the network may send an unstructured string to the UE. This string contains operator determined information that is relevant to the user. If the network is unable to successfully reach the UE, then an error shall be returned to the node that originated the operation.
The network initiated USSD operation shall contain an alphabet indicator and language indicator. The alphabet indicator shall indicate the alphabet used in the operation. The selection of values for these indicators is a matter for the network operator.
References
TS 24.090 subclause 5.2.1.
TS 22.090 subclause 5.2.2.
TS 22.090 subclause 5.2.1.
15.9.3.3 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.
15.9.3.4 Method of test
Initial Conditions
System Simulator:
1 cell, default parameters.
Use Equipment:
The UE is in the MM-state "idle updated".
Related PICS/PIXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of USSD Yes/No.
Test Procedure
– The UE 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 UE. The UE has to send a FACILITY message with an empty return result component.
– Then the SS originates a call to the UE. When the UE 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 UE. The UE has to send a FACILITY message with an empty return result component. Finally the SS releases both MM connections and the radio link.
Expected Sequence
|
Step |
|
Message |
Comments |
||||
|
1 |
Mobile terminated establishment of Radio Resource Connection |
See 3GPP TS 34.108. The IE “Paging cause” in the PAGING TYPE 1 message is set to “Terminating Low Priority Signalling”. The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Terminating Low Priority Signalling”. |
|||||
|
2 |
-> |
PAGING RESPONSE |
|||||
|
3 |
<– |
AUTHENTICATION REQUEST |
|||||
|
4 |
–> |
AUTHENTICATION RESPONSE |
|||||
|
5 |
SS |
The SS starts integrity protection |
|||||
|
6 |
<– |
REGISTER |
initiation of the transaction concerning the USSD notification operation |
||||
|
7 |
Void |
||||||
|
8 |
–> |
FACILITY |
signalling message sent by the UE as the response |
||||
|
8a |
UE |
Check that the UE displays the USSD string sent from the network |
|||||
|
9 |
<– |
SETUP |
Incoming call. |
||||
|
10 |
–> |
CALL CONFIRMED |
|||||
|
11 |
–> |
ALERTING |
|||||
|
11A |
UE |
Call is answered using suitable user action |
|||||
|
12 |
–> |
CONNECT |
|||||
|
13 |
<– |
CONNECT ACKNOWLEDGE |
|||||
|
14 |
<– |
RELEASE COMPLETE |
This message releases the transaction concerning the USSD operation. |
||||
|
15 |
<– |
REGISTER |
Initiation of a USSD request operation during a call. |
||||
|
16 |
Void |
||||||
|
17 |
–> |
FACILITY |
|||||
|
17a |
UE |
Check that the UE displays the USSD string received from the SS. |
|||||
|
18 |
<– |
RELEASE COMPLETE |
It releases the transaction identifier of the ussd operation. |
||||
|
19 |
<– |
DISCONNECT |
|||||
|
20 |
–> |
RELEASE |
|||||
|
21 |
<– |
RELEASE COMPLETE |
|||||
|
22 |
SS |
SS releases the RRC connection |
|||||
Specific message contents
REGISTER (steps 6 and 15).
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "Supplementary service (call independent)" |
|
Transaction identifier |
|
|
Register message type |
‘00111011’B |
|
Facility Information Element |
See below |
Facility Information Element with Invoke = UnstructuredSS-Notify component type as defined in GSM 04.90, clause 5.2.1.
|
Contents |
Value/remark |
|
Facility IE identifier |
‘00011100’B |
|
Length of FIE contents |
|
|
Component type tag |
‘10100001’B |
|
Component length |
depending on the length of ussd-string |
|
InvokeID tag |
‘00000010’B |
|
Invoke ID length |
1 |
|
Invoke ID |
Arbitrary (1 octet) |
|
Operation Code tag |
‘00000010’B |
|
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 |
FACILITY (steps 8 and 17).
|
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 |
‘xx 111010’B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
|
Facility Information Element |
See below |
Facility Information Element with Return Result = empty result component according to GSM 04.90, clause 5.2.1, figure 5.3.
|
Contents |
Value/remark |
|
Facility IE identifier |
‘00011100’B |
|
Length of FIE contents |
5 |
|
Component type tag |
Return Result ‘10100010’B |
|
Component length |
3 |
|
InvokeID tag |
‘00000010’B |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify |
RELEASE COMPLETE (step 14 and step 18)
|
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 |
‘00101010’B |
|
Facility Information Element |
omitted |
15.9.3.5 Test requirements
At steps 8 and 17 the UE shall send a FACILITY message with an empty return result.
15.9.4 UnstructuredSS-Notify/rejected on user busy
15.9.4.1 Definition
15.9.4.2 Conformance requirement
1) When the MS receives an USSD operation in parallel to any call independent supplementary service transaction, it shall respond with a return error component in a RELEASE COMPLETE message, containing the "USSD‑Busy" error as specified in 3GPP TS 24.080, to indicate the failure in handling a parallel USSD operation. However, the network is allowed to initiate USSD operations in parallel to call related transactions.
References
3GPP TS 24.090 subclause 5.1.1.
15.9.4.3 Test purpose
1) To verify that when the mobile 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.
15.9.4.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in MM-state "Idle, updated".
Related ICS/IXIT Statements
- Support of FDD Yes/No.
- Support of CS speech Yes/No
- Support of USSD.
- Description of the user’s commands and of display of USSD.
- Full rate supported.
- Supported teleservices.
- Support of active state of the call control protocol (U10).
Test procedure
The UE is paged and an RRC signalling 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 another USSD transaction by sending a REGISTER message with transaction identifier different form the previous one. The SS checks that the UE answers with a RELEASE COMPLETE message with an error component set to "USSD busy". Then the SS releases the signalling connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
<- |
PAGING TYPE 1 |
Mobile identity = TMSI-1 Paging order is for CS services. Paging cause = "terminatingLowPrioritySignalling" |
|
|
2 |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating Low Priority Signalling". |
||
|
3 |
-> |
PAGING RESPONSE |
||
|
3A |
<- |
AUTHENTICATION REQUEST |
||
|
3B |
-> |
AUTHENTICATION RESPONSE |
||
|
4 |
SS |
The SS starts integrity protection. |
||
|
5 |
<- |
REGISTER |
Initiation of the transaction concerning the USSD notification operation. |
|
|
6 |
Void |
|||
|
7 |
-> |
FACILITY |
||
|
7a |
UE |
Checks that the ussd-string sent by the SS is correctly displayed by the UE |
||
|
8 |
<- |
REGISTER |
Initiation of another USSD notification. The transaction identifier is different from that in step 5 |
|
|
9 |
-> |
RELEASE COMPLETE |
Return error set to "USSD busy". Transaction initiated in step 8 by the network is rejected by the UE. |
|
|
10 |
<- |
RELEASE COMPLETE |
normal release of transaction initiated in step 5. |
|
|
11 |
SS |
SS releases the RRC connection |
||
Specific message contents.
REGISTER (steps 5 and 8)
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "Supplementary service (call independent)" |
|
Transaction identifier |
|
|
Register message type |
As 3GPP TS 24.080 |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Invoke from 3GPP TS 24.080 |
|
Component length |
depending on the length of ussd-string |
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
Arbitrary (1 octet) |
|
Operation Code tag |
From 3GPP TS 24.080 |
|
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 |
Facility (step 7)
|
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 24.080 |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Return Result from 3GPP TS 24.080 |
|
Component length |
|
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify |
RELEASE COMPLETE (step 9)
|
Contents |
Value/remark |
|
Protocol Discriminator |
Set to "Supplementary service (call independent)" |
|
Transaction identifier |
Same as REGISTER (step 8) transaction value but the transaction flag is different. |
|
Release complete message type |
As 3GPP TS 24.080 |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 04.08 |
|
Length of FIE contents |
|
|
Component type tag |
Return Error from 3GPP TS 24.080 |
|
Component length |
|
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the UnstructuredSS-Notify in step 8 |
|
Error Code tag |
As 3GPP TS 24.080 |
|
Error Code length |
|
|
Error Code |
USSD Busy |
15.9.4.5 Test requirements
In step 9 the UE sends RELEASE COMPLETE with Return error set to "USSD busy".
15.9.5 UnstructuredSS-Request/accepted
15.9.5.1 Definition
15.9.5.2 Conformance requirement
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 23.090 subclause 5.2.5.
Conformance requirement 2: 3GPP TS 22.090 subclause 4.2.2.
Conformance requirement 3: 3GPP TS 22.090 subclause 4.2.1.
15.9.5.3 Test purpose
1) To test that, for a USSD request, the UE shall display the text provided and await user input. if the user enters a response, the UE shall return the response to the network, maintaining the transaction.
2) To verify that the UE 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 UE shall be able to process the operation during a call or out of a call.
15.9.5.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– the UE shall be in MM-state "Idle, updated".
Related ICS/IXIT Statements
- Support of FDD Yes/No.
- Support of CS speech Yes/No
- Support of USSD.
- Full rate supported.
- Supported teleservices.
- Support of active state of the call control protocol (U10).
Test procedure
– The UE is paged and the RRC 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 UE and answers the request using appropriate MMI/AT commands. Then the UE sends a FACILITY message with ussd string exactly containing the digits and symbols contained in AT/MMI commands.
– Then the SS originates a call to the UE. When the UE 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 UE and answers the request using appropriate MMI/AT commands. Then the UE 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.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
<- |
PAGING TYPE 1 |
Mobile identity = TMSI-1 Paging order is for CS services. Paging cause = "terminatingLowPrioritySignalling" |
|
|
2 |
SS |
SS checks that the IE "Establishment cause" in the received RRC CONNECTION REQUEST message is set to "Terminating Low Priority Signalling". |
||
|
3 |
-> |
PAGING RESPONSE |
||
|
3A |
<- |
AUTHENTICATION REQUEST |
||
|
3B |
-> |
AUTHENTICATION RESPONSE |
||
|
4 |
SS |
The SS starts integrity protection. |
||
|
5 |
<- |
REGISTER |
Initiation of the transaction concerning the USSD notification operation. |
|
|
6 |
SS |
The UE has to display the USSD string received from the SS. Trigger UE to answer using appropriate MMI/AT commands. |
||
|
7 |
-> |
FACILITY |
Return Result |
|
|
8 |
<- |
SETUP |
Incoming call |
|
|
9 |
–> |
CALL CONFIRMED |
||
|
10 |
–> |
ALERTING |
||
|
11 |
–> |
CONNECT |
||
|
12 |
<– |
CONNECT ACKNOWLEDGE |
||
|
13 |
<– |
RELEASE COMPLETE |
This message releases the transaction concerning the USSD operation. |
|
|
14 |
<– |
REGISTER |
initiation of a USSD request operation during a call. |
|
|
15 |
SS |
Check that the UE displays the USSD string received from the SS. Trigger UE to answer using appropriate MMI/AT commands. |
||
|
16 |
–> |
FACILITY |
Return Result |
|
|
17 |
<– |
RELEASE COMPLETE |
It releases the transaction identifier concerning the ussd operation. |
|
|
18 |
<– |
DISCONNECT |
CC call |
|
|
19 |
–> |
RELEASE |
CC call |
|
|
20 |
<– |
RELEASE COMPLETE |
||
|
21 |
SS |
SS releases the RRC connection |
||
Specific message contents.
REGISTER (steps 5 and 14)
|
Contents |
Value/remark |
|
Protocol Discriminator |
set to "Supplementary service (call independent)" |
|
Transaction identifier |
|
|
Register message type |
As 3GPP TS 24.080 |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.080 / 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Invoke from 3GPP TS 24.080 |
|
Component length |
depending on the length of ussd-string |
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
Arbitrary (1 octet) |
|
Operation Code tag |
From 3GPP TS 24.080 |
|
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 |
FACILITY (Steps 7 and 16)
|
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 24.080 |
|
Facility Information Element |
|
|
Facility IE identifier |
As 3GPP TS 24.080 / 3GPP TS 24.008 |
|
Length of FIE contents |
|
|
Component type tag |
Return Result from 3GPP TS 24.080 |
|
Component length |
depending on the length of ussd-string |
|
InvokeID tag |
From 3GPP TS 24.080 |
|
Invoke ID length |
1 |
|
Invoke ID |
The same as the invoke of the UnstructuredSS-Request |
|
Sequence tag |
|
|
Sequence length |
|
|
Operation Code tag |
From 3GPP TS 24.080 |
|
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. |
RELEASE COMPLETE (steps 13 and 17)
|
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 24.080 |
|
Facility Information Element |
omitted |
15.9.5.5 Test requirements
In steps 6 and 15, the UE shall display the received USSD string.
In steps 7 and 16, UE shall send the FACILITY message with the return result component.
15.9.6 MMI input for USSD
15.9.6.1 Definition
15.9.6.2 Conformance requirements
The UE shall act in accordance with figure 3.5.3.2 when digits are entered to the UE to determine whether to interpret these as call set-up requests or supplementary service control procedures etc. This may involve a mechanism, referred to as Unstructured SS Data, which allows the support of SS services which are not implemented by means of the specified functional signalling. See also 3GPP TS 22.090 [7].
…
The following definitions are applicable to the interpretation of figure 3.5.3.2:
1) In a call:
A UE is "in a call" from the time that signalling related to the establishment or attempted establishment of a MO or MT call commences and before the call or call attempt ends, and (if applicable) the ME has stopped generating tones related to this call to the user.
2) UE manufacturer defined procedure:
The term "UE manufacturer defined procedure" shall not include the following two cases:
(i) input which can be interpreted as being of the following form, whether or not in a call:
CX [string]# followed by SEND;
where
string is any combination of numeric digits, *, #;
and
C comprises 1, 2 or 3 digits from the set (*,#);
and
X comprises 1, 2 or 3 numeric digits or the fourth numeric digit is non-zero;
(ii) input of the following form in a call (as defined above):
"Entry of 1 or 2 characters defined in the 3GPP TS 23.038 [8] Default Alphabet followed by SEND".
3) #-string:
Input of the form.
"Entry of any characters defined in the 3GPP TS 23.038 [8] Default Alphabet (up to the maximum defined in 3GPP TS 24.080 [10]), followed by #SEND".
4) Short string:
"Entry of 1 or 2 characters defined in the 3GPP TS 23.038 [8] Default Alphabet followed by SEND".
5) Call setup string:
MMI input in accordance with the call set-up procedures as defined in 3GPP TS 24.008 [9] and terminated by SEND.
References
3GPP TS 22.030 subclause 6.5.3.2.
15.9.6.3 Test purpose
To check that the entry of 2 digits in the form 1X (X in the set 0,…9) followed by SEND is accepted by the mobile station in idle mode as a normal call establishment for the 1X number.
15.9.6.4 Method of test
Initial conditions
– System Simulator:
– one cell, default parameters.
– User Equipment:
– the UE has valid TMSI (= TMSI1), CKSN, CK, IK. It is "idle updated"
Related ICS/IXIT statement(s)
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of USSD Yes/No.
Support of MO circuit switched basic service Yes/No.
Test Procedure
The user requests call establishment with 2 digit phone number of the 1X form (X in the set 0,…9) followed by SEND. The UE request a MM-connection, sends CM SERVICE REQUEST message, the SS performs authentication and starts integrity. The UE then sends the SETUP message containing the ‘1X ‘phone number as called number (after having received the CM SERVICE ACCEPT message).
The procedure is executed 10 times with different phone number.
Expected Sequence
The following sequence is executed for execution counter k = 1 to 10.
|
Step |
|
Message |
Comments |
||||
|
1 |
UE |
The MS is made to initiate call establishment for phone number 1X (where X = k‑1) |
|||||
|
2 |
SS |
The SS verifies that the IE “Establishment cause” in the received RRC CONNECTION REQUEST message is set to “Originating Conversational Call” |
|||||
|
3 |
-> |
CM SEVICE REQUEST |
“Mobile originating call establishment” |
||||
|
4 |
<- |
AUTHENTICATION REQUEST |
|||||
|
5 |
-> |
AUTHENTICATION RESPONSE |
|||||
|
6 |
SS |
The SS starts integrity protection |
|||||
|
7 |
-> |
SETUP |
Called number set to ‘1X ‘ |
||||
|
8 |
<- |
RELEASE COMPLETE |
|||||
|
9 |
SS |
SS releases the RRC connection |
|||||
|
10 |
SS |
Wait for 10 seconds and repeat steps 1 to 10 until k=10 |
|||||
Specific message contents.
None.
15.9.6.5 Test requirements
At step 7 the UE shall send a SETUP message specifying the Called party BCD number that was entered into the UE.