hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.9.1 Mobile station initiated Unstructured supplementary service data operation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.9.2 Network initiated unstructured supplementary service operations | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 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).
for step10 see iiia).
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.10 MMI input for USSD | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.10.1 Conformance requirements | If the MS cannot interpret the MMI input as a defined GSM Supplementary Services, SIM control procedure or MS manufacturer-defined procedure, and if the MMI input is in the form:
- "entry of any characters defined in the 3GPP TS 03.38 Default Alphabet (up to the maximum defined in 3GPP TS 04.80) followed by #SEND"; or
- "entry of 1 or 2 characters defined in the 3GPP TS 03.38 Default Alphabet followed by SEND";
then it shall be interpreted by the MS as Unstructured SS Data and sent transparently towards the network, unless the MS is not engaged in a call and the first digit of the 2 character entry, followed by SEND, is a "1". In this case the MS shall transmit this as a call-setup request.
References
3GPP TS 02.30 subclause 4.5.3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.10.2 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. It is checked that the MS sends a CHANNEL REQUEST, sends CM SERVICE REQUEST message for mobile originated call (after having received an IMMEDIATE ASSIGNMENT), and then sends the SETUP message containing the 1X phone number as called number (after having received the CM SERVICE ACCEPT message). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.10.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station
The MS is "idle updated";
Specific PICS Statements
-
PIXIT Statements
-
Foreseen final state of the MS:
The MS is "idle updated.
Test procedure
The user requests call establishment successively for every 2 digit phone number of the 1X form (X in the set 0,...9) allowing ten seconds between each attempts.
Maximum duration of test
3 minutes.
Expected Sequence
The following sequence is executed for execution counter k = 1 to 10.
Step
Direction
Message
Comments
1
MS
The MS is made to initiate call establishment for phone number 1X (where X = k‑1)
2
MS -> SS
CHANNEL REQUEST
with establishment cause related to mobile originating call
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
"mobile originating call"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
SETUP
called BCD number is 1X
7
SS -> MS
RELEASE COMPLETE
8
Wait for 10 seconds
Specific message contents.
None. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.11 Specific message contents and ASN.1 codings | Introduction
In this subclause a mixed form of ASN.1 coding has been used in ASN.1 components within the messages.
Some components use the indefinite form of coding, and some use the short definite form.
An example of a FACILITY message using indefinite form of coding is described below.
The same message using short definite form of coding is described in Test 31.2.1.1.1 Step 7 of this subclause.
Contents
Value/remark
Coding
Length of FIE contents
43
2B
Component type tag
Return Result
A2
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30
Sequence length
indefinite
80
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
SS-Information
Forwarding Info tag
Tag=A0
A0
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRy
2A
Forwarding Feature List
Seq.
30
Length Indicator
indefinite
80
Forwarding Feature
Seq.
30
Forwarding Feature length
indefinite
80
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov., Registered, Active
07
Forwarded To Number identifier
Tag=85
85
ISDN-AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
NoReplyConditionTime
Tag=87
87
Length Indicator
1
01
NoReplyConditionTime
5
05
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.1.1. Registration accepted
MMI sequence: **61*00431234*11*5#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
26
1A
Component type tag
Invoke
A1 (note 1)
Component length
24
18
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
RegisterSS-Arg
Seq.
30 (note 1)
RegisterSS-Arg length
16
10
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRy
2A
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
Forwarded To Number identifier
Tag=84
84
AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
NoReplyConditionTime tag
Tag=85
85
NoReplyConditionTime length
1
01
NoReplyConditionTime
5
05
NOTE 1: This component may use the indefinite form.
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
35
23
Component type tag
Return Result
A2 (note 1)
Component length
33
21
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
28
1C
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
23
17
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRy
2A
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
18
12
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
16
10
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov., Registered, Active
07
Forwarded To Number identifier
Tag=85
85
ISDN-AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
NoReplyConditionTime
Tag=87
87
Length Indicator
1
01
NoReplyConditionTime
5
05
MMI sequence: **21*00431234*13#
Step 15: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
23
17
Component type tag
Invoke
A1 (note 1)
Component length
21
15
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
RegisterSS-Arg
Seq.
30 (note 1)
RegisterSS-Arg length
13
0D
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFU
21
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
Forwarded To Number identifier
Tag=84
84
AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
42
2A
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
indefinite
80
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFU
21
Forwarding Feature List
Seq.
30 (note 1)
Length indicator
indefinite
80
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
indefinite
80
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov., Registered, Active
07
Forwarded To Number identifier
Tag=85
85
ISDN-AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.1.2. Registration rejected
MMI sequence: **67*00431234*21#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
23
17
Component type tag
Invoke
A1 (note 1)
Component length
21
15
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
RegisterSS-Arg
Seq.
30 (note 1)
RegisterSS-Arg length
13
0D
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFB
29
Basic Service Code identifier
BearerserviceCode
82
Bearerservice length
1
01
Bearerservice code
AllAsynchronousServices
60
Forwarded To Number identifier
Tag=84
84
AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
02
Error Code length
1
01
Error Code
BearerServiceNot Provisioned
0A
MMI sequence: **002*00431234*13#
Step 11: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
23
1715
Component type tag
Invoke
A1 (note 1)
Component length
21
15
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterSS
0A
RegisterSS-Arg
30 (note 1)
RegisterSS-Arg length
13
0D
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CF
20
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
Forwarded To Number identifier
Tag=84
84
AddressString length
5
05
AddressString type
Unknown
81
AddressString
TBCD-String: 00431234
00 34 21 43
Step 12: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Reject
A4 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Invoke Problem tag
Tag=81
81
Invoke Problem length
1
01
Invoke Problem code
Resource limitation
03
Test 31.2.1.2.1. Erasure accepted
MMI sequence: ##004**13#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-ForBS
Seq.
30 (note 1)
SS-ForBS length
6
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFC
28
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
31
1F
Component type tag
Return Result
A2 (note 1)
Component length
29
1D
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
24
18
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFC
28
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
indefinite
80
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
indefinite
80
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Provisioned
04
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: ##62#
Step 15: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-ForBS
Seq.
30 (note 1)
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRc
2B
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
22
16
Component type tag
Return Result
A2 (note 1)
Component length
20
14
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
15
0F
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
10
0A
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRc
2B
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
5
05
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
3
03
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Provisioned
04
Test 31.2.1.2.2. Erasure rejected
MMI sequence: ##21**11#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-ForBS
30 (note 1)
SS-ForBS length
6
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFU
21
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
Tag=2
02
Error Code length
1
01
Error Code
TeleserviceNotProvisioned
0B
MMI sequence: ##61**13#
Step 11: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
EraseSS
0B
SS-ForBS
30 (note 1)
SS-ForBS length
6
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRy
2A
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
Step 12: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
10
0A
Component type tag
Reject
A4 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Invoke Problem tag
81
Invoke Problem length
1
01
Invoke Problem
Resource limitation
03
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.3. Activation
MMI sequence: *002**22#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
ActivateSS
0C
SS-ForBS
30 (note 1)
SS-ForBS length
6
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CF
20
Basic Service Code identifier
BearerserviceCode
82
Bearerservice length
1
01
Bearerservice code
AllSynchronousServices
68
Step 7:SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
29
1D
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
20
14
Operation Code tag
02
Operation Code length
1
01
Operation Code
ActivateSS
0C
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CF
20
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
8
08
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
6
06
Basic Service Code identifier
BearerserviceCode
82
Bearerservice length
1
01
Bearerservice code
AllSynchronousServices
68
SS-Status
Tag=4
84
SS-Status length
1
01
SS-Status code
Prov., Registered, Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: *21#
Step 15: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
ActivateSS
0C
SS-ForBS
Seq.
30 (note 1)
SS-ForBS length
3
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFU
21
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
26
1A
Component type tag
Return Result
A2 (note 1)
Component length
24
18
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
indefinite
80
Operation Code tag
02
Operation Code length
1
01
Operation Code
ActivateSS
0C
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFU
21
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
5
05
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
3
03
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered, Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.4. Deactivation
MMI sequence: #004**11#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
DeactivateSS
0D
SS-ForBS
Seq.
30 (note 1)
SS-ForBS length
6
06
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFC
28
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
29
1D
Component type tag
Return Result
A2 (note 1)
Component length
27
1B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
22
16
Operation Code tag
02
Operation Code length
1
01
Operation Code
DeactivateSS
0D
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
indefinite
80
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFC
28
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
indefinite
80
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
6
06
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Provisioned, Registered
06
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: #62**13#
Step 15: MS -> SS REGISTER
Contents
Value/remark
Coding
Same header as Step 6
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRc
2B
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
27
1B
Component type tag
Return Result
A2 (note 1)
Component length
25
19
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
20
14
Operation Code tag
02
Operation Code length
1
01
Operation Code
DeactivateSS
0D
SS-Information
Forwarding Info tag
Tag=A0
A0 (note 1)
Forwarding Info length
15
0F
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRc
2B
Forwarding Feature List
Seq.
30 (note 1)
Length Indicator
10
0A
Forwarding Feature
Seq.
30 (note 1)
Forwarding Feature length
indefinite
80
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
All Facsimile Services
60
SS-Status
Tag=4
84
SS-Status length
1
01
SS-Status code
Provisioned, Registered
06
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.6.1. Interrogation accepted
MMI sequence: *#67#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
SS-ForBS
30 (note 1)
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFB
29
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/Remark
Coding
Length of FIE contents
13
0D
Component type tag
Return Result
A2 (note 1)
Component length
11
0B
Invoke ID tag
Tag=02
02
Invoke ID length
1
01
Invoke ID
As received
03
Sequence tag
30 (note 1)
Sequence length
6
06
Operation code tag
Tag=02
02
Operation code length
1
01
Operation code
InterrogateSS
0E
InterrogateSS-Res
Choice
SS-Status
Tag=80
80
SS-Status length
1
01
SS-Status
Provisioned
04
MMI sequence: *#61**11#
Step 15: MS -> SS REGISTER
Contents
Value/Remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
InterrogateSS
0E
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
6
06
SS code tag
Tag=4
04
SS code length
1
01
SS code
CFNRy
2A
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/Remark
Coding
Length of FIE contents
26
1A
Component type tag
Return Result
A2 (note 1)
Component length
24
18
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
03
Sequence tag
30 (note 1)
Sequence length
19
13
Operation code tag
02
Operation code length
1
01
Operation code
InterrogateSS
0E
InterrogateSS-Res
Choice
Forwarding Feature List
Seq.
A3 (note 1)
length indicator
14
0E
Forwarding Feature tag
Seq.
30 (note 1)
Forwarding Feature length
12
0C
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmissionServices
10
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
Forwarded To Number Identifier
Tag=85
85
ISDN-AddressString length
4
04
AddressString type
International Number
91
AddressString
TBCD-String: 431234
34 21 43
Test 31.2.1.6.2. Interrogation rejected
MMI sequence: *#62#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
SS-ForBS
30 (note 1)
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
CFNRc
2B
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
02
Error Code length
1
01
Error Code
SS-NotAvailable
12
MMI sequence: *#67**13#
Step 11: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
InterrogateSS
0E
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
6
06
SS code tag
Tag=04
04
SS code length
1
01
SS code
CFB: CF on MS Busy
29
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllFacsimileServices
60
Step 12: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Reject
A4 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Problem code tag
Tag=81
81
Problem code length
1
01
Invoke problem
Resource limitation
03
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.7.1.1. Notification during an incoming call
Step 10 and 15: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
18
12
Component type tag
Invoke
A1 (note 1)
Component length
16
10
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
NotifySS
10
SS-ForBS
30 (note 1)
SS-ForBS length
indefinite
80
SS-Code tag
Tag=81
81
SS-Code length
1
01
SS-Code
CFB
29
SS-Notification tag
Tag=85
85
SS-Notification length
1
01
SS-Notification
Incoming call forwarded
02
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.7.1.2. Notification during an outgoing call
Step 9 : SS -> MS ALERTING
Contents
Value/remark
Coding
Length of FIE contents
18
12
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
00
Operation code tag
02
Operation code length
1
01
Operation code
NotifySS
10
NotifySS-Arg tag
Seq.
30 (note 1)
NotifyBS-Arg length
6
06
SS code tag
Tag=81
81
SS code length
1
01
SS code
CFU: Forw Unconditional
21
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
Step 10 : SS -> MS CONNECT
Contents
Value/remark
Coding
Length of FIE contents
18
12
Component type tag
Invoke
A1 (note 1)
Component length
16
10
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
01
Operation code tag
02
Operation code length
1
01
Operation code
NotifySS
10
NotifySS-Arg tag
Seq.
30 (note 1)
NotifyBS-Arg length
indefinite
80
SS code tag
Tag=81
81
SS code length
1
01
SS code
CFC: Conditional Forw.
28
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.2.1.7.2. Forwarded-to mobile subscriber side
Step 5 : SS -> MS SETUP
Contents
Value/remark
Coding
Length of FIE contents
18
12
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
00
Operation code tag
02
Operation code length
1
01
Operation code
NotifySS
10
NotifySS-Arg tag
Seq.
30 (note 1)
NotifyBS-Arg length
6
06
SS code tag
Tag=81
81
SS code length
1
01
SS code
CFNRc MS not reachable
2B
SS-Notification tag
Tag=85
85
SS-Notification length
1
01
SS-Notification
Forwarded call
01
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.6.1.1. AOC time related charging/MS originated call
k=1 Step 11: SS -> MS CONNECT
Contents
Value/remark
Coding
Length of FIE contents
41
29
Component type tag
Invoke
A1 (note 1)
Component length
39
27
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ForwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
indefinite
80
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
24
18
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 6,0
3C
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 14,0
00 8C
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
e4 tag
Tag=84
84
e4 length
2
02
e4
Value = 25,0
00 FA
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
2
02
e7
Value = 60,0
02 58
End-Of-Content Tag
0
00
Length Indicator
0
00
Step A13/B12: MS -> SS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
5
05
Component type tag
Return Result
A2 (note 1)
Component length
3
03
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
k=1...5: e-parameters
e-parameter values
k-value
e1
e2
e3
e4
e5
e6
e7
1
6
14
1
25
0
0
60
2
0
0
1
100
0
0
0
3
250
16
2
500
0
0
60
4
1
1
1
0
10
10
1
5
12,5
30
1
25
10
10
30
e-parameter coding
k-value
e1
e2
e3
e4
e5
e6
e7
1
3C
00 8C
64
00 FA
00
00
02 58
2
00
00
64
03 E8
00
00
00
3
09 C4
00 A0
00 C8
13 88
00
00
02 58
4
00 0A
00 0A
00 64
00 00
00 64
00 0A
00 0A
5
7D
01 2C
64
00 FA
64
0A
01 2C
Test 31.6.1.2. AOC time related charging/MS terminated call
k=1...5 Step 12: SS -> MS FACILITY e-parameters
e-parameter values
k-value
e1
e2
e3
e4
e5
e6
e7
1
0
0
0
0
0
0
0
2
0
0
1
100
0
0
0
3
6
14
1
25
0
0
60
4
1
1
1
0
0
0
1
5
12,5
30
1
25
0
0
30
e-parameter coding
k-value
e1
e2
e3
e4
e5
e6
e7
1
00
00
00
00
00
00
00
2
00
00
64
03 E8
00
00
00
3
3C
00 8C
64
00 FA
00
00
02 58
4
0A
0A
64
00
00
00
0A
5
7D
01 2C
00 64
FA
00
00
01 2C
Test 31.6.1.5. Change in charging information during a call
Step A12: SS -> MS FACILITY (initial CAI message)
Contents
Value/remark
Coding
CAI header element
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 10,0
64
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 28,0
01 18
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 10,0
64
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
2
02
e7
Value = 60,0
02 58
Step A12: SS -> MS FACILITY (subsequent CAI message)
Contents
Value/remark
Coding
CAI header element
e1
Value = 10,0
64
e2
Value = 14,0
00 8C
e3
Value = 1,0
64
e4
Value = 5,0
32
e5
Value = 0,0
00
e6
Value = 0,0
00
e7
Value = 60,0
02 58
Test 31.6.1.6. Different formats of charging information
k=1 SS -> MS FACILITY
Contents
Value/remark
Coding
CAI header element
e1
Value = 10,0
64
e2
Value = 40,0
01 90
e3
Value = 1,0
64
e4
Value = 0,0
00
e5
Value = 0,0
00
e6
Value = 0,0
00
e7
Value = 0,0
00 00
k=2 SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
27
1B
Component type tag
Invoke
A1 (note 1)
Component length
25
19
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
forwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
17
11
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
indefinite
80
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 10,0
64
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 40,0
01 90
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.6.1.7. AOC on a Call Hold call
Step 11: SS -> MS CONNECT
Contents
Value/remark
Coding
CAI header element
e1
Value = 7,0
46
e2
Value = 40,0
01 90
e3
Value = 1,0
64
e4
Value = 0,0
00
e5
Value = 0,0
00
e6
Value = 0,0
00
e7
Value = 0,0
00
Step 20: SS -> MS CONNECT
Contents
Value/remark
Coding
CAI header element
e1
Value = 13,0
00 82
e2
Value = 40,0
01 90
e3
Value = 1,0
64
e4
Value = 0,0
00
e5
Value = 0,0
00
e6
Value = 0,0
00
e7
Value = 0,0
00
Test 31.6.1.8. AOC on a Multi-party call
Step 11 & 20: SS -> MS CONNECT
e-parameter values
k-value
e1
e2
e3
e4
e5
e6
e7
1
19
40
1
0
0
0
0
2
29
40
1
0
0
0
0
e-parameter coding
k-value
e1
e2
e3
e4
e5
e6
e7
1
00 BE
01 90
64
00
00
00
00
2
01 22
01 90
64
00
00
00
00
Step 23: MS -> SS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Invoke
A1 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
BuildMPTY
7C
Step 24: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
7
07
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.6.2. Charge Storage
31.6.2.1 Removal of SIM during an active call
and 31.6.2.2 Interruption of power supply during an active call
and 31.6.2.3 MS going out of coverage during an active AoCC call
Step A11: SS -> MS CONNECT
Contents
Value/remark
Coding
Length of FIE contents
39
27
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
forwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
27
1B
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
22
16
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 10,0
64
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 55,0
02 26
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 10,0
64
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
1
01
e7
Value = 10,0
64
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.6.2.4. ACMmax operation/Mobile Originating
k=1 Step A11: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
41
29
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ForwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
27
1B
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
22
16
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 1,0
0A
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 30,0
01 2C
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 0,0
00
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
1
01
e7
Value = 0,0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
k=2 Step A11: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
40
28
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ForwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
26
1A
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
21
15
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 0,0
00
e2 tag
Tag=82
82
e2 length
1
01
e2
Value = 0,0
00
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 0,0
00
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 0,0
00
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
1
01
e7
Value = 0,0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.6.2.5 ACMmax operation/Mobile Terminating
k=1 Step A13: SS -> MS FACILITY, k=2 Step B13: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
41
29
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ForwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
27
1B
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
28
1C
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 1,0
00 0A
e2 tag
Tag=82
82
e2 length
2
02
e2
Value = 30,0
01 2C
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 1,0
64
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 0,0
00
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
1
01
e7
Value = 0,0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
k=3 Step A13: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
40
28
Component type tag
Invoke
A1 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ForwardChargeAdvice
7D
ForwardChargeAdviceArg
Seq.
30 (note 1)
ForwardChargeAdviceArg length
26
1A
SS code tag
Tag=80
80
SS code length
1
01
SS code
AoC-Charging
72
Charging Information
Tag=a1
A1 (note 1)
Charging Information length
21
15
e1 tag
Tag=81
81
e1 length
1
01
e1
Value = 0,0
00
e2 tag
Tag=82
82
e2 length
1
01
e2
Value = 0,0
00
e3 tag
Tag=83
83
e3 length
1
01
e3
Value = 0,0
00
e4 tag
Tag=84
84
e4 length
1
01
e4
Value = 0,0
00
e5 tag
Tag=85
85
e5 length
1
01
e5
Value = 0,0
00
e6 tag
Tag=86
86
e6 length
1
01
e6
Value = 0,0
00
e7 tag
Tag=87
87
e7 length
1
01
e7
Value = 0,0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.1.1. Registration of a password accepted
MMI sequence:**03*330*1234*9876*9876#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
11
0B
Component type tag
Invoke
A1 (note 1)
Component length
9
09
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterPasswordSS
11
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
B: All barring services
90
Step 7: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
14
0E
Component type tag
Invoke
A1 (note 1)
Component length
12
0C
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Linked ID tag
80
Linked ID length
1
01
Linked ID
As received
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
GetPasswordSS
12
Guidance information
Enumerated
0A
Guidance length
1
01
Guidance
enter password
00
Step 9: MS -> SS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Return Result
A2 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Contents
Value/remark
Coding
Sequence tag
30 (note 1)
Sequence length
9
09
Operation Code tag
02
Operation Code length
1
01
Operation Code
GetPasswordSS
12
Password tag
Numeric String
12
Password length
4
04
Password
Password = 1234
31 32 33 34
Step 10 & 12: FACILITY
Contents
Value/remark
Coding
Guidance
Enter New Password
01
Contents
Value/remark
Coding
Password
Password = 9876
39 38 37 36
Step 13 & 15: FACILITY
Contents
Value/remark
Coding
Guidance
EnterNewPasswordAgain
02
Contents
Value/remark
Coding
Password
Password = 9876
39 38 37 36
Step 16: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
20
14
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30 (note 1)
Sequence length
indefinite
80
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterPasswordSS
11
Password tag
Numeric String
12
Password length
4
04
Password
Password = 1234
31 32 33 34
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.1.2. Registration of a password rejected
MMI sequence:**03*330*1234*9876*987X#
Test 31.8.1.2.1. Rejection after invoke of the RegisterPassword operation
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
11
0B
Component type tag
Invoke
A1 (note 1)
Component length
9
09
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
RegisterPasswordSS
11
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
B: All barring services
90
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
Tag=2
02
Error Code length
1
01
Error Code
SS subscription violation
13
Test 31.8.1.2.2. Rejection after password check with negative result
Step 6: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
10
0A
Component type tag
Return Error
A3 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
Tag=2
02
Error Code length
1
01
Error Code
Negative Password Check
26
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.1.2.3. Rejection after new password mismatch
Step 14: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
11
0B
Component type tag
Return Error
A3 (note 1)
Component length
9
09
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error Code tag
Tag=2
02
Error Code length
1
01
Error Code
PW-Registration Failure
25
pw-Registration Failure cause
Tag=04
04 (note 2)
pw-Registration Failure length
1
01
pw-Registration Failure
New Password Mismatch
02
NOTE 2: This element is described in Rec. 3GPP TS 04.80 subclause 4.3.2.12, but there is no ASN.1 description in subclause 4.5. Description given in the informative annex A should be put at the end of subclause 4.5.
Test 31.8.3.1. Activation accepted
MMI sequence: *33*1234*22#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary (01)
--
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS-ForBS
Seq.
30 (note 1)
SS-ForBS length
6
06
SS code tag
Tag=04
04
SS code length
1
01
SS code
BAOC
92
Basic Service Code identifier
BearerserviceCode
82
BearerService length
1
01
BearerService code
AllSynchronousServices
68
Step 7: SS -> MS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
14
0E
Component type tag
Invoke
A1 (note 1)
Component length
12
0C
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary (02)
--
Linked ID tag
80
Linked ID length
1
01
Linked ID
As received (01)
--
Operation code tag
02
Operation code length
1
01
Operation code
Getpassword
12
Guidance tag
Enumerated
0a
Guidance length
1
01
Guidance
Enter Password
00
Step 8: MS -> SS FACILITY
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Return Result
A2 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received (02)
--
Sequence tag
30 (note 1)
Sequence length
9
09
Operation code tag
02
Operation code length
1
01
Operation code
Getpassword
12
Password tag
NumericString
12
Password length
4
04
Password
Password = 1234
31 32 33 34
Step 9: SS -> MS RELEASE COMPLETE
This message is coded to give a complete answer to the MS request. Shorter message can also be used (see last paragraph).
Contents
Value/remark
Coding
Length of FIE contents
29
1D
Component type tag
Return Result
A2 (note 1)
Component length
27
1B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received (01)
--
Sequence tag
30 (note 1)
Sequence length
indefinite
80
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS information
CallBarringInfo
Tag=a1
A1 (note 1)
CallBarringInfo length
indefinite
80
SS code tag
Tag=04
04
SS code length
1
01
SS code
BAOC
92
CallBarringFeature List
Seq.
30 (note 1)
Length indicator
8
08
CallBarring Feature tag
Seq.
30 (note 1)
CallBarring Feature length
6
06
Basic Service Code identifier
BearerserviceCode
82
BearerService length
1
01
BearerService code
AllSynchronousServices
68
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: *351*1234#
Step 17: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BICRoam
9B
Step 20: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
26
1A
Component type tag
Return Result
A2 (note 1)
Component length
24
18
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence identifier
30 (note 1)
Sequence length
19
13
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS-Information
CallBarringInfo
Tag=a1
A1 (note 1)
CallBarringInfo length
14
0E
SS code tag
Tag=04
04
SS code length
1
01
SS code
BICRoam
9B
CallBarringFeature List
Seq.
30 (note 1)
Length indicator
indefinite
80
CallBarring Feature tag
Seq.
30 (note 1)
CallBarring Feature length
indefinite
80
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
End-Of-Content Tag
0
00
Length Indicator
0
00
End-Of-Content Tag
0
00
Length Indicator
0
00
Step 9 & 20: short messages
Step 10 and 22 messages can be coded using this shorter form:
Message containing only the "Return result"
Contents
Value/remark
Coding
Length of FIE contents
5
05
Component type tag
Return Result
A2 (note 1)
Component length
3
03
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Message containing the "Return result" and the "Operation Code"
Contents
Value/remark
Coding
Length of FIE contents
12
0C
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence identifier
30 (note 1)
Sequence length
3
03
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.3.2.1. Rejection after invoke of ActivateSS operation
MMI sequence: *331*1234#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BOIC
93
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error code tag
02
Error code length
1
01
Error code
SS Subscription Violation
13
Test 31.8.3.2.2. Rejection after use of password procedure
MMI sequence: *35*1234#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
ActivateSS
0C
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BAIC
9A
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
10
0A
Component type tag
Return Error
A3 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error code tag
02
Error code length
1
01
Error code
NegativePasswordCheck
26
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.4.1. Deactivation accepted
MMI sequence: #330*1234*11#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0D
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
B: All barring services
90
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllSpeechTransmission
10
Step 10: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
21
15
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence identifier
30 (note 1)
Sequence length
12
0C
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-Information
CallBarringInfo
Tag=a1
A1 (note 1)
CallBarringInfo length
7
07
CallBarringFeature List
Seq.
30 (note 1)
Length indicator
5
05
CallBarring Feature tag
Seq.
30 (note 1)
CallBarring Feature length
3
03
Basic Service Code Identifier
TeleserviceCode
83
Teleservice Length
1
01
Teleservice code
AllSpeechTransmission
10
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: #333*1234*13#
Step 17: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
6
06
SS code tag
Tag=04
04
SS code length
1
01
SS code
BO
91
Basic Service Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
AllFacsimileServices
60
Step 21: MS -> SS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
21
15
Component type tag
Return Result
A2 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence identifier
30 (note 1)
Sequence length
12
0C
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-Information
CallBarringInfo
Tag=a1
A1 (note 1)
CallBarringInfo length
7
07
CallBarringFeature List
Seq.
30 (note 1)
Length indicator
5
05
CallBarring Feature tag
Seq.
30 (note 1)
CallBarring Feature length
3
03
Basic Service Code Identifier
TeleserviceCode
83
Teleservice Length
1
01
Teleservice code
AllFacsimileServices
60
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.4.2.1. Deactivation rejected after invoke operation
MMI sequence: *#353*1234#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BI
99
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
10
0A
Component type tag
Return Error
A3 (note 1)
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error code tag
02
Error code length
1
01
Error code
SS Subscription Violation
13
End-Of-Content Tag
0
00
Length Indicator
0
00
Test 31.8.4.2.2. Deactivation rejection after password operation
MMI sequence: *#332*1234#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
DeactivateSS
0D
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BOICExHome
94
Step 7: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
8
08
Component type tag
Return Error
A3 (note 1)
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error code tag
02
Error code length
1
01
Error code
NegativePasswordCheck
26
Test 31.8.6.1. Interrogation accepted
MMI sequence: *#35#
Step 6: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE contents
13
0D
Component type tag
Invoke
A1 (note 1)
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
InterrogateSS
0E
SS-ForBS
Seq
30 (note 1)
SS-ForBS length
3
03
SS code tag
Tag=04
04
SS code length
1
01
SS code
BAIC
9A
Step 10: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE Contents
15
0F
Component type tag
Return Result
A2
Component length
13
0D
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30
Sequence length
8
08
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
InterrogateSS-Res
Choice
BasicServiceGroupList tag
Seq.
A2
BasicServiceGroupList length
3
03
BasicService Code identifier
TeleserviceCode
83
Teleservice length
1
01
Teleservice code
Telephony
11
MMI sequence: *#332#
Step 17: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE Contents
13
0D
Component type tag
Invoke
A1
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
SS-ForBS
Seq
30
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
BOICExHome
94
Step 21: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE Contents
13
0D
Component type tag
Return Result
A2
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Sequence tag
30
Sequence length
6
06
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
InterrogateSS-Res
Choice
SS-Status
Tag=80
80
SS-Status length
1
01
SS-Status
Prov., Registered, Deactive
06
Test 31.8.6.2. Interrogation rejected
MMI sequence: *#351#
Step 4: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE Contents
13
0D
Component type tag
Invoke
A1
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
SS-ForBS
Seq
30
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
BICRoam
9B
Step 5: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE Contents
10
0A
Component type tag
Return Error
A3
Component length
indefinite
80
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Error code tag
02
Error code length
1
01
Error code
SS_NotAvailable
12
End-Of-Content Tag
0
00
Length Indicator
0
00
MMI sequence: *#331#
Step 11: MS -> SS REGISTER
Contents
Value/remark
Coding
Length of FIE Contents
13
0D
Component type tag
Invoke
A1
Component length
11
0B
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
InterrogateSS
0E
SS-ForBS
Seq
30
SS-ForBS length
3
03
SS-Code tag
Tag=4
04
SS-Code length
1
01
SS-Code
BOIC
93
Step 12: SS -> MS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE Contents
8
08
Component type tag
Reject
A4
Component length
6
06
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
As received
--
Problem code tag
Tag=81
81
Problem code length
1
01
Invoke problem code
Resource limitation
03
Test 31.8.7. Normal operation
Incoming call
Step 6: MS -> SS RELEASE COMPLETE
Contents
Value/remark
Coding
Length of FIE contents
16
10
Component type tag
Invoke
A1 (note 1)
Component length
14
0E
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation code tag
02
Operation code length
1
01
Operation code
NotifySS
10
NotifySS-Arg tag
Seq.
30 (note 1)
NotifySS-Arg length
6
06
SS code tag
Tag=81
81
SS code length
1
01
SS code
BI
99
SS-Status
Tag=84
84
SS-Status length
1
01
SS-Status code
Prov. Registered Active
07
Test 31.9. Registration accepted of a USSD
MMI sequence: **00#
Contents
Value/remark
Coding
Length of FIE contents
15
0F
Component type tag
Invoke
A1 (note 1)
Component length
13
0D
Invoke ID tag
02
Invoke ID length
1
01
Invoke ID
Arbitrary
--
Operation Code tag
02
Operation Code length
1
01
Operation Code
ProcessUSSDSS
0A
IA5 String tag
Tag=16
16
IA5 String length
5
05
Content
**00#
2A 2A 30 30 23
31.12 eMLPP Service
This subclause is applicable to the mobile stations supporting eMLPP service. The eMLPP is applicable to teleservices 1x, 6x, 9x and bearer services 2x, 3x, 4x, 5x.
For an MS supporting speech the test procedures in subclauses 31.12.1 and 31.12.2 are performed for full rate speech (teleservice 11, telephony). For an MS not supporting speech but supporting at least one of telecommunication services (TS6x, BS2x, BS3x, BS4x, BS5x), for each of the test procedures 31.12.1 and 31.12.2 a full rate service supported by the MS (see PICS/PIXIT statement) is chosen, and the test is performed corresponding to that service.
31.12.1 eMLPP Service / priority level of MO call |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.1.1 Conformance requirement | For the MS supporting MO calls:
1. Mobile stations indicate the priority of their call in the signalling that takes place during the call establishment process.
2. The MS shall verify the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level.
3. In case of no priority selection or use of a non-compatible Mobile Station the Mobile Station shall send a standard service request message.
4. Signalling information required for the prioritisation at mobile originating call establishment. (see figure 1 of 3GPP TS 04.67 subclause 4.1.1) and Signalling information between the network and the calling mobile station required for the prioritisation in case of a VGCS or VBS call (figure 4 of 3GPP TS 04.67 subclause 4.1.4).
5. The user or the network may wish to omit or postpone authentication and ciphering in order to provide for a faster call set-up.
Reference(s)
3GPP TS 03.67 subclauses 11.3.1.1, 11.3.1.2, 11.6 and 11.3.1.3.
3GPP TS 02.67 clause 4.
3GPP TS 04.67 subclauses 4.1.1 and 4.1.4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.1.2 Test purpose | For the MS supporting MO, to verify that:
1. When user selects priority level for normal MO call, the priority level is indicated in the signalling message.
2. The MS verifies the selected priority level against the priority levels stored in the SIM. If the selected priority is not allowed, then the priority of the call shall be modified to that of the nearest allowed priority level below the requested level.
3. If the user does not select a priority level, the priority level is not indicated in the signalling message.
4. If a priority selection is performed by the user the MS provides the priority level information element in L3-MM CM SERVICE REQUEST message when a group call is initiated.
5. The mobile is able to establish a normal MO call with a priority level or a group call with a priority level according to the procedure specified in 3GPP TS 04.67 subclause 4.1.1 and the procedure in 3GPP TS 04.67 subclause 4.1.4.
6. The mobile is able to initiate a fast call set-up without authentication and ciphering. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.1.3 Method of test | Initial Conditions
System Simulator:
1 cell with default parameters.
Mobile Station:
The MS is in idle mode with SIM in which the available priority levels are level 2, level 3, and level 4
Specific PICS Statements
- Support mobile originating call (TSPC_AddInfo_MOsvc)
- Support mobile emergency call (TSPC_Serv_TS12)
- Support VGCS originating (TSPC_AddInfo_VGCS_Originating)
- Support VBS originating (TSPC_AddInfo_VBS_Originating)
PIXIT Statements
- Way to select a priority level.
Foreseen Final State of the MS
"Idle, updated".
Test Procedure
The test steps 1 to 26 are repeated for k=1, 2, 3. After the repetition is finished the steps 27 to 71 are performed.
The test steps 1 to 7 are performed if the mobile station supports normal MO call. The steps 8 to 13 are executed if the MS supports TS12. The test steps 20 to step 26 are executed for k= 1, 2, 3, if the mobile station supports VGCS/VBS originating.
An allowed priority level (level 3) or a priority level (level 1) higher than allowed level or no priority level is selected by MMI action (for k=1, 2, 3 respectively). An MO call is attempted. It is checked that the MS indicates the selected priority level (for k=1) or the nearest allowed priority level below the selected level (for k=2) or no priority level (for k=3) in the signalling message.
A normal MO call is attempted with an allowed priority level (level 3). It is checked that the MS establishes completely this call.
If the mobile station supports VGCS/VBS originating a VGCS/VBS call is initiated via the MMI by using the SETUP procedure.
A MO VGCS/VBS call is attempted with the allowed priority level 0. It is checked that the MS establishes completely this call using the immediate setup procedure without authentication and ciphering.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
for k=1, MMI action to select a priority level 3
for k=2, MMI action to select a priority level 0
for k=3, no MMI action to select priority level
2
MS
to initiate a normal MO call
3
MS -> SS
CHANNEL REQUEST
4
SS -> MS
IMMEDIATE ASSIGNMENT
5
MS -> SS
CM SERVICE REQUEST
for k=1, containing priority IE with the selected priority
for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)
for k=3, containing no priority IE
6
SS -> MS
CM SERVICE REJECT
7
SS -> MS
CHANNEL RELEASE
8
MS
to initiate a normal MO emergency call
9
MS -> SS
CHANNEL REQUEST
10
SS -> MS
IMMEDIATE ASSIGNMENT
11
MS -> SS
CM SERVICE REQUEST
for k=1, containing priority IE with the selected priority
for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)
for k=3, containing no priority IE
12
SS -> MS
CM SERVICE REJECT
13
SS -> MS
CHANNEL RELEASE
20
MS
for k=1, MMI action to select a priority level 3
for k=2, MMI action to select a priority level 0
for k=3, no MMI action to select priority level
21
MS
to initiate a VGCS call by setup procedure, if supporting VGCS originating.
to initiate a VBS call by setup procedure, if supporting only VBS originating.
22
MS -> SS
CHANNEL REQUEST
23
SS -> MS
IMMEDIATE ASSIGNMENT
24
MS -> SS
CM SERVICE REQUEST
for k=1, containing priority IE with the selected priority
for k=2, containing priority IE with a priority level nearest allowed priority level below the requested one (level 2)
for k=3, containing no priority IE
25
SS -> MS
CM SERVICE REJECT
26
SS -> MS
CHANNEL RELEASE
27
MS
MMI action to select a priority level 3
28
MS
initiate a normal MO call
29
MS -> SS
CHANNEL REQUEST
30
SS -> MS
IMMEDIATE ASSIGNMENT
31
MS -> SS
CM SERVICE REQUEST
containing priority IE with a priority level nearest allowed priority level below the requested one (level 3)
32
SS -> MS
AUTHENTICATION REQUEST
33
MS -> SS
AUTHENTICATION RESPONSE
34
SS -> MS
CIPHERING MODE COMMAND
no ciphering
35
MS -> SS
CIPHERING MODE COMPLETE
36
MS -> SS
SETUP
37
SS -> MS
CALL PROCEEDING
38
SS -> MS
ASSIGNMENT COMMAND
39
MS -> SS
ASSIGNMENT COMPLETE
40
SS -> MS
ALERTING
41
SS -> MS
CONNECT
42
MS -> MS
CONNECT ACKNOWLEDGE
43
SS -> MS
DISCONNECT
44
MS -> SS
RELEASE
45
SS -> MS
RELEASE COMPLETE
46
SS -> MS
CHANNEL RELEASE
Steps 47 – 71 are performed if the MS supports VGCS/VBS originating
47
MS
MMI action to select a priority level 3 and initiate a VGCS/VBS call by setup procedure
49
MS -> SS
CHANNEL REQUEST
50
SS -> MS
IMMEDIATE ASSIGNMENT
51
MS -> SS
CM SERVICE REQUEST
containing priority IE with a priority level nearest allowed priority level below the requested one (level 3)
52
SS -> MS
AUTHENTICATION REQUEST
53
MS -> SS
AUTHENTICATION RESPONSE
54
SS -> MS
CIPHERING MODE COMMAND
no ciphering
55
MS -> SS
CIPHERING MODE COMPLETE
56
MS -> SS
SETUP
57
SS -> MS
CHANNEL MODE MODIFY
58
MS -> SS
CHANNEL MODE MODIFY ACKNOWLEDGE
59
SS -> MS
CONNECT
60
SS
Verify that TCH is through connected
61
SS -> MS
TERMINATION
62
SS -> MS
CHANNEL RELEASE
63
MS
MMI action to select a priority level 0, MMI action to initiate VGCS/VBS call.
64
MS -> SS
CHANNEL REQUEST
65
SS -> MS
IMMEDIATE ASSIGNMENT
TCH/F, single RF channel
GSM 450: 275
GSM 480: 322
GSM 900: 50
DCS 1800: 750
PCS 1 900: 650
GSM 710, GSM 750, T-GSM 810: 470
GSM 850: 177
66
MS -> SS
IMMEDIATE SETUP
L2: SABM / UA
67
SS -> MS
CHANNEL MODE MODIFY
very early assignment
68
MS -> SS
CHANNEL MODE MODIFY ACKNOWLEDGE
69
SS -> MS
CONNECT
verify that the TCH is through connected
70
SS
Verify that TCH is through connected
70
SS -> MS
TERMINATION
71
SS -> MS
CHANNEL RELEASE
Special Message Contents
CM SERVICE REQUEST in step 5 and step 24
for k=1, 2
Information Element
value/remark
as default except:
CM Service Type
not checked
Ciphering key sequence number
not checked
Mobile station classmark
not checked
Priority
Information element identifier
0001
Spare
0
Call priority
010 for k=1
011 for k=2
for k=3
Information Element
value/remark
as default except:
CM Service Type
not checked
Ciphering key sequence number
not checked
Mobile station classmark
not checked
Priority
not present
CM SERVICE REQUEST in step 11
for k=1, 2
Information Element
value/remark
as default except:
CM Service Type
"emergency call establishment"
Ciphering key sequence number
not checked
Mobile station classmark
not checked
Priority
Information element identifier
0001
Spare
0
Call priority
010 for k=1
for k=3
Information Element
value/remark
as default except:
CM Service Type
"emergency call establishment"
Ciphering key sequence number
not checked
Mobile station classmark
not checked
Priority
not present
31.12.2 eMLPP Service / automatic answering point-to-point MT call
31.12.2.1 Conformance requirement
For the MS supporting MT call:
1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following:
- point-to-point calls:
If the user is in idle mode, the Mobile Station shall automatically connect to an incoming call of a sufficient priority level. If the user is in dedicated mode and has a subscription to Call Waiting, a Call Waiting indication including the priority level of the call shall be given to the Mobile Station which automatically accepts the waiting call.
2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal.
3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the set-up message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically accept the waiting call and send a hold message to the network. If a hold acknowledge is received, the waiting call is accepted. If a hold reject is received for any reason, e.g. there is no subscription for hold, the other call shall be released and the waiting call accepted. If the ongoing call is not a TS11 call, the mobile station should not send a hold message to the network but release the call and accept the waiting call.
Reference(s)
3GPP TS 02.67 subclause 4, 5.9.
3GPP TS 03.67 clause 4, subclauses 11.3.2.4, 11.3.2.5 and 11.6.
3GPP TS 04.67 subclause 4.1.3.
3GPP TS 04.83 subclauses 1.1 and 1.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.2.2 Test purpose | For the MS supporting MT call, to verify that:
1. In idle mode the MS automatically accepts an incoming point-to-point call of priority level for which automatic answering is enabled.
2. In idle mode the MS alerts an incoming point-to-point call of a priority level for which automatic answering is disabled.
3. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a level for which automatic answering is enabled and the priority level is higher than the ongoing point-to-point call, the MS automatically confirms the waiting call and sends a hold message to the network. If a hold reject is received the other call is released and the waiting call is accepted.
4. In dedicated mode and supporting Call Waiting, when a Call Waiting indication includes a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call, the MS indicates the waiting call.
5. In group receive mode the MS automatically responds to the paging message containing a priority level for which automatic answering is enabled and the priority level is higher than the priority level of the ongoing call.
6. In group receive mode the MS indicates an incoming point-to-point call of a priority level for which automatic answering is enabled and the priority level is equal or lower than the priority level of the ongoing call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.2.3 Method of test | Initial Conditions
System Simulator:
1 cell with default parameters.
Mobile Station:
The MS is in idle mode.
The auto answering priority level is set to higher than priority level 2.
Specific PICS Statements
- Support VGCS listening (TSPC_AddInfo_VGCS_Listening)
- Support VBS listening (TSPC_AddInfo_VBS_Listening)
PIXIT Statements
- Way to configure automatic answering.
- Way to indicate a call has been automatically answered.
Foreseen Final State of the MS
"Idle, updated".
Test Procedure
The call waiting is activated. The MS is in idle mode and automatic answering for priority level 2 is disabled. A PAGING REQUEST message containing priority level 2 is sent. It is checked that the MS indicates the incoming call to the user. The automatic answering for level 1 is enabled. A PAGING REQUEST message with priority level 2 is sent. It is checked that the MS automatically accepts the incoming normal call. The call is released. A PAGING REQUEST message without priority level is sent, and during the call set-up the SETUP message contains priority level 1. It is checked that the MS automatically accepts the incoming normal call.
The MS is in dedicated mode (If the MS supports TS11, TS11service shall be selected for the dedicated mode testing). a SETUP message with priority level higher enough for auto answering is sent by the SS. It is checked that the MS automatically accepts the incoming normal call. A SETUP message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming call to the user.
The MS is in group receive mode, a NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message with priority level 0 are sent. It is checked that the MS automatically accepts the incoming normal call. The MS is brought into group receive mode. A NOTIFICATION/FACCH message containing paging information and a PAGING REQUEST message containing low priority level are sent. It is checked that the MS indicates the incoming call to the user.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
0
MS
the MS is in idle mode and auto answering for priority level 2 is disabled
1
SS -> MS
PAGING REQUEST TYPE 1
with priority level 2
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
4
MS -> SS
PAGING RESPONSE
5
SS -> MS
SETUP
containing priority level 2, but no signal IE
6
MS -> SS
CALL CONFIRMED
7
SS -> MS
ASSIGNMENT COMMAND
TCH
8
MS -> SS
ASSIGNMENT COMPLETE
9
MS -> SS
ALERTING
10
MS
An alerting indication as defined in a PICS/PIXIT statement is given by the MS
11
MS
The MS is made to accept the call in the way described in a PICS/PIXIT statement
12
MS -> SS
CONNECT
13
SS -> MS
CONNECT ACKNOWLEDGE
14
SS -> MS
DISCONNECT
15
MS -> SS
RELEASE
16
SS -> MS
RELEASE COMPLETE
17
SS -> MS
CHANNEL RELEASE
return to idle mode
21
SS -> MS
PAGING REQUEST TYPE 1
containing priority level 1
22
MS -> SS
CHANNEL REQUEST
23
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
24
MS -> SS
PAGING RESPONSE
25
SS -> MS
SETUP
containing priority level 1, but no signal IE
26
MS -> SS
CALL CONFIRMED
27
MS -> SS
CONNECT
automatic connection
28
SS -> MS
ASSIGNMENT COMMAND
TCH
29
MS -> SS
ASSIGNMENT COMPLETE
30
SS -> MS
CONNECT ACKNOWLEDGE
31
MS
to check that the MS gives an indication as defined in a PICS/PIXIT statement for call automatically answered
32
SS -> MS
DISCONNECT
33
MS -> SS
RELEASE
34
SS -> MS
RELEASE COMPLETE
35
SS -> MS
CHANNEL RELEASE
return to idle mode
36
SS -> MS
PAGING REQUEST TYPE 1
containing no priority level
37
MS -> SS
CHANNEL REQUEST
38
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
39
MS -> SS
PAGING RESPONSE
40
SS -> MS
SETUP
containing priority level 3, but no signal IE
41
MS -> SS
CALL CONFIRMED
42
MS -> SS
CONNECT
automatic connection
43
SS -> MS
ASSIGNMENT COMMAND
TCH
44
MS -> SS
ASSIGNMENT COMPLETE
45
SS -> MS
CONNECT ACKNOWLEDGE
51
SS -> MS
SETUP
new transaction, containing priority level 1 and Signal Information Element with value #7
52
MS -> SS
CALL CONFIRMED
on new transaction with cause #17
53a
MS -> SS
HOLD
on old transaction for service TS11
53b
no signalling for services other than TS11
54a
SS -> MS
HOLD REJECT
on old transaction for service TS11 with cause #69
54b
no signalling for services other than TS11
55
MS -> SS
DISCONNECT
on old transaction, cause = ‘Normal call clearing’
56
SS -> MS
RELEASE
on old transaction
57
MS -> SS
RELEASE COMPLETE
on old transaction
58
MS -> SS
CONNECT
on new transaction
59
SS -> MS
CONNECT ACKNOWLEDGE
on new transaction
60
SS -> MS
SETUP
another new transaction different from step 51, containing priority level 1 and Signal Information Element with value #7
61
MS -> SS
CALL CONFIRMED
on the same transaction as step 60, with cause #17
62
MS -> SS
ALERTING
on the same transaction as step 60
63
MS
to check that the MS gives incoming call indication
64
SS -> MS
DISCONNECT
on the same transaction as step 51
65
MS -> SS
RELEASE
on the same transaction as step 51
66
SS -> MS
RELEASE COMPLETE
on the same transaction as step 51
67
SS -> MS
CHANNEL RELEASE
70
MS
the MS is in group receive mode, the priority level of current call is level 3
72
SS -> MS
PAGING REQUEST TYPE 1
containing priority level 0
73
MS -> SS
CHANNEL REQUEST
74
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH
75
MS -> SS
PAGING RESPONSE
76
SS -> MS
SETUP
without priority level and signal IE
77
MS -> SS
CALL CONFIRMED
78
MS -> SS
CONNECT
automatic connection
79
SS -> MS
ASSIGNMENT COMMAND
TCH
80
MS -> SS
ASSIGNMENT COMPLETE
81
SS -> MS
CONNECT ACKNOWLEDGE
82
SS -> MS
DISCONNECT
83
MS -> SS
RELEASE
84
SS -> MS
RELEASE COMPLETE
85
SS -> MS
CHANNEL RELEASE
86
MS
the MS is brought into group receive mode with the priority level 3
88
SS -> MS
PAGING REQUEST TYPE 1
containing priority level 3
89
MS
to check that the MS gives incoming call indication
90
SS -> MS
CHANNEL RELEASE
UI format
31.12.3 eMLPP Service / automatic answering MT VGCS or VBS call
31.12.3.1 Conformance requirement
For the MS supporting VGCS/VBS listening:
1. Automatic answering or, if necessary, called-party pre-emption has to be performed by the Mobile Station as defined in the following:
- voice group calls and voice broadcast calls:
Notifications for other voice group calls, voice broadcast calls or information on paging for point-to-point calls shall be given to the Mobile Stations involved in on-going voice group calls or voice broadcast calls as defined in 3GPP TS 03.68 and 3GPP TS 03.69, respectively. The notifications include the related priority level of the call. In case of a notified call with higher priority where called-party pre-emption applies, the Mobile Station shall automatically leave the on-going voice group call or voice broadcast call and react according to the type of the notified call type.
2. In dedicated mode, in the case where the called subscriber has a subscription for eMLPP and for Call Waiting and is using a compatible Mobile Station, the Mobile Station shall be informed of the priority of the new call together with the call waiting indication. The Mobile Station will then consult the internal service configuration list stored on the SIM to establish whether it should automatically accept the waiting call without consulting the user, or whether the call waiting facility will be used as normal.
3. In the case where the called subscriber has a subscription for eMLPP and for CW, the mobile station shall be informed of the priority of the new call together with the CW indication. On reception of the notification message the compatible mobile station decides on called party pre-emption. If called party pre-emption applies, the mobile station shall automatically release the call and join the new call.
Reference(s)
3GPP TS 02.67 clause 4.
3GPP TS 03.68 clause 4, subclauses 11.3.1.3 and 11.3.1.4.
3GPP TS 03.67 clause 4.
3GPP TS 04.67 subclause 4.1.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.3.2 Test purpose | For the MS supporting VGCS/VBS listening, to verify that:
1. In idle mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.
2. In idle mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.
3. In dedicated mode, the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.
4. In dedicated mode, the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering.
5. In group receive mode the MS automatically accepts an incoming VGCS or VBS call of sufficient priority level.
6. In group receive mode the MS indicates an incoming VGCS or VBS call of priority level not high enough for automatic answering. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.3.3 Method of test | Initial Conditions
System Simulator:
1 cell with default parameters.
Mobile Station:
The MS is in idle mode.
The auto answering priority level is set to higher than priority level 2.
Specific PICS Statements
-
PIXIT Statements
- Way to configure automatic answering.
- Way to indicate that a VGCS/VBS call has been automatically accepted.
Foreseen Final State of the MS
"Idle, updated".
Test Procedure
The MS is in idle mode. a NOTIFICATION/NCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. The call is released. A NOTIFICATION/NCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.
The MS is in dedicated mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing low priority level without auto answering is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.
The MS is in group receive mode. a NOTIFICATION/FACCH message with priority level higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS automatically accepts the incoming VGCS/VBS call. A NOTIFICATION/FACCH message containing priority level not higher enough for auto answering and containing VGCS/VBS channel description is sent. It is checked that the MS indicates the incoming VGCS/VBS call to the user.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
the MS is in idle mode
2
SS -> MS
NOTIFICATION/NCH
containing priority level 1
3
MS
to check that the MS automatically accepts the VGCS/VBS call
4
SS
stop sending NOTIFICATION/NCH
5
SS -> MS
CHANNEL RELEASE
UI format, release VGCS/VBS channel
6
SS -> MS
NOTIFICATION/NCH
containing priority level 3
7
MS
to check that the MS indicates the VGCS/VBS call to the user
8
SS
stop sending NOTIFICATION/NCH
15
MS
the MS is in dedicated mode, the priority level of current call is level 3
16
SS -> MS
NOTIFICATION/FACCH
containing priority level 2
17
MS -> SS
DISCONNECT
18
SS -> MS
RELEASE
19
MS -> SS
RELEASE COMPLETE
20
SS -> MS
CHANNEL RELEASE
21
MS
to check that the MS automatically accepts the VGCS/VBS call
22
SS -> MS
CHANNEL RELEASE
UI format, release VGCS/VBS channel
23
MS
the MS is brought into dedicated mode, the priority level of current call is level 3
24
SS -> MS
NOTIFICATION/FACCH
containing priority level 4
25
MS
to check that the MS indicates the VGCS/VBS call to the user
26
SS
stop sending NOTIFICATION/FACCH
27
SS -> MS
DISCONNECT
28
MS -> SS
RELEASE
29
SS -> MS
RELEASE COMPLETE
30
SS -> MS
CHANNEL RELEASE
I format, release dedicated channel
31
MS
the MS is in group receive mode, the priority level of current call is level 3
32
SS -> MS
NOTIFICATION/FACCH
containing priority level 1 and with VGCS/VBS channel description
33
MS
to check the MS automatically accepts the incoming VGCS/VBS call
34
SS -> MS
NOTIFICATION/FACCH
containing priority level 4 and with VGCS/VBS channel description
35
MS
to check the MS indicates the incoming VGCS/VBS call to the user
36
SS -> MS
CHANNEL RELEASE
UI format, release VGCS/VBS channel
31.12.4 eMLPP Service / registration |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.4.1 Conformance requirement | For registration of eMLPP default priority level, the MS shall transmit successively:
1. A CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user".
2. A CM SERVICE REQUEST with CM service type indicating "supplementary service activation".
3. An eMLPP registration request from a mobile user shall include the SS-Code of the eMLPP service and the default priority level.
Reference(s)
3GPP TS 04.67 subclause 4.2 (figure 6).
3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.8.
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.4.2 Test purpose | To check that the MS:
1. Correctly requests a supplementary service transaction for registration of eMLPP in CHANNEL REQUEST message.
2. Correctly requests a supplementary service transaction for registration of eMLPP in the subsequent CM SERVICE REQUEST.
3. Then sends a REGISTER message containing the invoke of the RegisterSS operation with the expected parameter values for registration of eMLPP default priority level.
4. Provides the appropriate user indication (as described by the manufacturer) upon receipt of the result of the operation (in a RELEASE COMPLETE message). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.4.3 Method of test | Initial Conditions
System Simulator:
1 cell with default parameters.
Mobile Station:
the MS is in idle mode
Specific PICS Statements
-
PIXIT Statements
- Way to select a priority level.
- Way to initiate eMLPP registration.
- Way to indicate the result of the eMLPP registration.
Foreseen Final State of the MS
"Idle, updated".
Test Procedure
By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests registration of eMLPP for a default priority level DefaultPriorityLevel arbitrarily selected.
Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the RegisterSS operation.
The SS transaction is released and the dedicated channel is released.
Then check the MS provides a correct user indication.
Maximum Duration of Test
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a registration of eMLPP default priority level
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
RegisterSS(eMLPP, DefaultPriorityLevel)
7
SS -> MS
RELEASE COMPLETE
RegisterSS operation Return_result
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
Special Message Contents
REGISTER:
Information Element
value/remark
as default except:
Facility
invoke
RegisterSS
Supplementary service code
eMLPP
Default Priority
arbitrary
31.12.5 eMLPP Service / interrogation |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.5.1 Conformance requirement | For interrogation of eMLPP default priority level, the MS shall transmit successively:
1. A CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user".
2. A CM SERVICE REQUEST with CM service type indicating "supplementary service activation".
3. And then the REGISTER message containing a facility IE that includes an invoke of the InterrogateSS operation with parameter values eMLPP (MMI action) (see figure 7 of 3GPP TS 04.67 subclause 4.5).
Reference(s)
3GPP TS 04.67 subclause 4.5 (figure 7).
3GPP TS 04.08 / 3GPP TS 44.018 subclauses 3.3.1.2 and 9.1.9.
3GPP TS 04.08 / 3GPP TS 24.008 subclauses 4.5.1.1 and 9.2.9. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.5.2 Test purpose | To check that the MS:
1. Correctly requests a supplementary service transaction for interrogation of eMLPP in CHANNEL REQUEST message.
2. Correctly requests a supplementary service transaction for interrogation of eMLPP in the subsequent CM SERVICE REQUEST.
3. Then sends a REGISTER message containing the invoke of the InterrogateSS operation with the expected parameter values for interrogation of eMLPP default priority level.
4. Provides the appropriate user indication (as described by PIXIT) upon receipt of the result of the operation (in a RELEASE COMPLETE message). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.12.5.3 Method of test | Initial Conditions
System Simulator:
1 cell with default parameters.
Mobile Station:
the MS is in idle mode
Specific PICS Statements
-
PIXIT Statements
- Way to select a priority level.
- Way to initiate eMLPP interrogation.
- Way to indicate the result of the eMLPP interrogation.
Foreseen Final State of the MS
"Idle, updated".
Test Procedure
1. By means of appropriate MMI functions (using either 3GPP TS 02.30 or manufacturer defined MMI), the user requests interrogation of eMLPP.
2. Upon receipt of the operation (in a REGISTER message), the system simulator answers with a RELEASE COMPLETE message with the Facility information element containing the return result of the InterrogateSS operation.
3. The SS transaction is released and the dedicated channel is released.
4. Then check the MS provides a correct user indication.
Maximum Duration of Test
3 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is made to initiate a interrogation of eMLPP default priority level
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
InterrogateSS(eMLPP)
7
SS -> MS
RELEASE COMPLETE
InterrogateSS operation Return_result containing SS-Status, MaximumPriorityLevel, DefaultPriorityLevel
8
SS -> MS
CHANNEL RELEASE
9
MS
Provide correct MMI user indication after step 7
Special Message Contents
REGISTER:
Information Element
value/remark
as default except:
Facility
invoke
InterrogateSS
Supplementary service code
eMLPP |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13 Explicit Call Transfer (ECT) | NOTE: In this subclause, Subscriber A is the MS under test, and subscribers B and C are distant parties to the calls made during the tests. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1 Explicit Call Transfer invocation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.1 Explicit Call Transfer invocation, successful case, both calls active, clearing using DISCONNECT | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a DISCONNECT response from the network.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform and explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
7
SS -> MS
DISCONNECT
Transaction identifier of Call A-B
8
MS -> SS
RELEASE
Transaction identifier of Call A-B
9
SS -> MS
DISCONNECT
Transaction identifier of Call A-C
10
MS -> SS
RELEASE
Transaction identifier of Call A-C
11
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-B
12
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-C
13
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
14
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
15
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
16
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.2 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE response from the network.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a RELEASE message with respect to one of the calls containing a return result component, followed by a RELEASE message for the other call, the MS shall respond with a RELEASE COMPLETE message for each call and shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform and explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
7
SS -> MS
RELEASE
Transaction identifier of Call A-B
8
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B
9
SS -> MS
RELEASE
Transaction identifier of Call A-C
10
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-C
11
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
12
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
13
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
14
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.3 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE COMPLETE | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of a RELEASE COMPLETE response from the network.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a RELEASE COMPLETE message with respect to one of the calls containing a return result component, followed by a RELEASE COMPLETE message for the other call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform and explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
7
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-B
8
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-C
9
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
10
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
11
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
12
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.4 Explicit Call Transfer invocation, successful case, second call alerting | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and reacts correctly on receipt of clearing messages from the network.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on an active call and an alerting call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U4 "Call Delivered" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U0. Call A-C, state U0.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a DISCONNECT message with respect to one of the calls containing a return result component, followed by a DISCONNECT message for the other call, the MS shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the MS shall enter state U0 "Null". The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a RELEASE COMPLETE message with cause #81 "invalid transaction identifier value".
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform and explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U4
7
SS -> MS
DISCONNECT
Transaction identifier of Call A-B
8
MS -> SS
RELEASE
Transaction identifier of Call A-B
9
SS -> MS
DISCONNECT
Transaction identifier of Call A-C
10
MS -> SS
RELEASE
Transaction identifier of Call A-C
11
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-B
12
SS -> MS
RELEASE COMPLETE
Transaction identifier of Call A-C
13
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
14
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-B, with cause #81 "invalid transaction identifier value"
15
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
16
MS -> SS
RELEASE COMPLETE
Transaction identifier of Call A-C, with cause #81 "invalid transaction identifier value" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.5 Explicit Call Transfer invocation, unsuccessful case | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
1. To test that the MS invokes explicit call transfer between two active calls by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on receipt of an error or reject response.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active"with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state.
Maximum duration of test
30 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a FACILITY message using the same transaction identifier and including a return error component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Using suitable MMI commands, the MS shall again invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
On receipt of a FACILITY message using the same transaction identifier and including a reject component, the MS shall not send any further messages in respect of the transfer attempt, and shall remain in the same call state for both calls. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform an explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
7
SS -> MS
FACILITY
TI same as step 2, Return Error component
8
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
9
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
10
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
11
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
12
MS
Using MMI commands, perform an explicit call transfer
13
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
14
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
15
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
16
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
17
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
18
SS -> MS
FACILITY
TI same as step 2, Reject component
19
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
20
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
21
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
22
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.13.1.6 Explicit Call Transfer invocation, expiry of T(ECT) | Conformance requirement
3GPP TS 04.91 subclauses 4.1 and 4.2.
3GPP TS 04.80 subclause 4.2.
Applicability
MS supporting the Explicit Call Transfer supplementary service.
Test purpose
To test that the MS invokes explicit call transfer between an active held call and an alerting call by sending a FACILITY message with the correct invoke component, and returns both calls to their original states on expiry of T(ECT).
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of performing Explicit Call transfer on two active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have Call A-B in state U10 "Active" with auxiliary state "Call held" and Call A-C in state U10 "Active" with no auxiliary state. Both calls shall be of a basic service supported by the MS and applicable to the ECT supplementary service as described in 3GPP TS 02.04 table A.1.
Foreseen final state of the MS
Call A-B, state U10, auxiliary state "Call held". Call A-C, Call A-C, state U10, no auxiliary state.
Maximum duration of test
45 s.
Procedure
Using suitable MMI commands, the MS shall invoke an explicit call transfer between the two calls. The MS shall send a FACILITY message with a transaction identifier for either call A-B or call A-C and containing an ExplicitCT invoke component. The call state of both calls shall be unchanged. The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Between 5s and 15s after sending the FACILITY message, the MS shall either:
- remain in the same call states and indicate failure to the user; or
- send another FACILITY message with the same contents.
The call states shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of each call, and receiving a STATUS message indicating the appropriate call state.
Expected sequence
Step
Direction
Message
Comments
1
MS
Using MMI commands, perform an explicit call transfer
2
MS -> SS
FACILITY
TI for Call A-B or Call A-C, ExplicitCT Invoke component
3
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
4
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
5
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
6
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
7
SS
Wait 15 s from receiving FACILITY message
Take this branch if no message is received within 15 s
A8
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
A9
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
A10
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
A11
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state
Take this branch if a message is received within 15 s
B8
MS -> SS
FACILITY
Same as Step 2. Message shall not be received less than 5 s after the first FACILITY message
B9
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-B
B10
MS -> SS
STATUS
Transaction identifier of Call A-B, state U10, auxiliary state "Call held"
B11
SS -> MS
STATUS ENQUIRY
Transaction identifier of Call A-C
B12
MS -> SS
STATUS
Transaction identifier of Call A-C, state U10, no auxiliary state |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14 User-to-User Signalling (UUS) | This subclause applies to mobile station supporting User-to-User Signalling (UUS). The objective of this clause is to test UUS concerned procedures.
Unless indicated in individual sub-clauses, the default message contents in subclause 26.8.4 are applied for CC calls and default message contents in subclause 26.14.10 are applied for VGCS/VBS calls. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1 UUS / Implicit UUS1 | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.1 UUS / Implicit UUS1 / CC MO call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.1.1 Conformance requirement | The UUI service is activated implicitly by the presence of UUI in the set-up request from the mobile station.
To activate UUS1 implicitly, the MS shall include a User-user information element in the SETUP message as part of a normal call request.
The MS shall accept the presence of User-user information element in the ALERTING, CONNECT, DISCONNECT, RELEASE or RELEASE COMPLETE messages (as indicated in 3GPP TS 24.087, figure 1 in subclause 4.1.1).
References
3GPP TS 23.087 subclauses 4.1.1 and 5.2.1.2.1.
3GPP TS 24.087 subclause 4.1.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.1.2 Test purpose | 1. To verify that upon initiation of an outgoing basic call with implicit UUS1 by the user, the MS includes a User-user information element in the SETUP message.
2. To verify that inclusion of the User-user information element with different data length in either of the downlink messages ALERTING, CONNECT, DISCONNECT or RELEASE COMPLETE, causes no adverse effects on the operation of the MS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS Statements
- Support MO telephony (TSPC_AddInfo_MOsvc )
- Support UUS (TSPC_Serv_SS_UUS)
PIXIT Statements
- Way to activate implicit UUS1.
- Description of display of the User-user data received from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
By means of appropriate MMI function, the user requests implicit UUS1 and enters a string, which shall be included in the UUS1. Then MS is made to initiate a call. In the SETUP message, the User-user information element shall be present and shall include the requested string. Then, SS releases the call.
The MS is made to initiate a second call with implicit UUS1. In the SETUP message, the User-user information element shall be present with the requested string. SS releases the call, by sending a RELEASE COMPLETE message including a User-user information element with a long data value. It is checked that the MS is not disturbed by the optional User-user information element.
The MS is made to initiate a third call with implicit UUS1. In the SETUP message, the User-user information element shall be present with the requested string. Then SS shall include User-user information element in the ALERTING and in the CONNECT message with respectively short and long data value, it is checked that MS does not respond adversely to the inclusion of the optional User-user information element. After 10 seconds, SS initiates call clearing. SS sends DISCONNECT and RELEASE COMPLETE messages with User-user information element respectively without data and with a short data value, again the MS shall not respond adversely to the inclusion of the User-user information element, but shall continue to clear down the call normally.
Maximum Duration of Test
2 minutes.
Expected Sequence
Step
Direction
Message
Comments/actions/next state
0
MS
The MS is in idle mode.
MMI actions to initiate a CC call with implicit UUS1 including the string 'abc0123456'.
1
MS -> SS
CHANNEL REQUEST
2
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH4
3
MS -> SS
CM SERVICE REQUEST
4
MS -> SS
SETUP
Check User-user IE is included. See specific message contents
5
SS -> MS
RELEASE COMPLETE
6
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
10
MS
MMI actions to initiate a CC call with implicit UUS1 including the string 'abc'
11
MS -> SS
CHANNEL REQUEST
12
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH4
13
MS -> SS
CM SERVICE REQUEST
14
MS -> SS
SETUP
Check User-user IE is included. See specific message contents
15
SS -> MS
RELEASE COMPLETE
Message contains the User-user IE with a long data value, see Specific message contents
16
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
17
MS
Is is checked that the MS, in a way described by the manufacturer, displays user-user data after step 15
20
MS
MMI actions to initiate a CC call with implicit UUS1 including the string '123497'.
21
MS -> SS
CHANNEL REQUEST
22
SS -> MS
IMMEDIATE ASSIGNMENT
SDCCH4
23
MS -> SS
CM SERVICE REQUEST
24
MS -> SS
SETUP
Check User-user IE is included. See specific message contents
25
SS -> MS
AUTHENTICATION REQUEST
26
MS -> SS
AUTHENTICATION RESPONSE
27
SS -> MS
CALL PROCEEDING
28
SS -> MS
ASSIGNMENT COMMAND
TCH
29
MS -> SS
ASSIGNMENT COMPLETE
30
SS -> MS
ALERTING
Message contains the User-user IE with a short data value, see Specific message contents
31
MS
It is checked that the MS, in a way described by the manufacturer, displays user-user data.
32
SS -> MS
CONNECT
Message contains the User-user IE with a long data value, see Specific message contents
33
MS
It is checked that the MS, in a way described by the manufacturer, displays user-user data.
34
MS -> SS
CONNECT ACKNOWLEDGE
35
SS -> MS
DISCONNECT
Without Progress Indication IE
Including the User-user IE without data, see Specific message contents
36
MS
It is checked that the MS, in a way described by the manufacturer, displays no user-user data.
37
MS -> SS
RELEASE
38
SS-> MS
RELEASE COMPLETE
Message contains the User-user IE with a short data value, see Specific message contents
39
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
40
MS
It is checked that the MS, in a way described by the manufacturer, displays user-user data after step 38
Specific message contents:
SETUP
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1 + the entered string length
- PD
User specific protocol
- user-user
The string as entered coded in IA5 characters
ALERTING
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
2
- PD
User specific protocol
- user-user
The following string coded in IA5 characters: "A"
CONNECT
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
101
- PD
User specific protocol
- user-user
The following string with a length of 100 octets coded in IA5 characters: "abcdefghijklmnopqrstuvwxyz0123456789abc………."
DISCONNECT
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1
- PD
User specific protocol
- user-user
-
RELEASE COMPLETE – step 15
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
37
- PD
User specific protocol
- user-user
The following string coded in IA5 characters: "0123456789abcdefghijklmnopqrstuvwxyz"
RELEASE COMPLETE – step 38
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
17
- PD
User specific protocol
- user-user
The following string coded in IA5 characters: "RELEASE COMPLETE" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.2 UUS / Implicit UUS1 / CC MT call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.2.1 Conformance requirement | The MS shall accept the presence of User-user information element in the SETUP and DISCONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1).
The MS may include User-user information element in the ALERTING or CONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1).
References
3GPP TS 23.087 subclause 5.2.1.2.1.
3GPP TS 24.087. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.2.2 Test purpose | 1. To verify that, the receipt of SETUP message including user-user information element with a short or large data value causes no adverse effects on the call establishment operation of the MS.
2. To verify that MS could include User-user information element in either of the uplink messages ALERTING or CONNECT.
3. To verify that inclusion of the User-user information element with different data length in either of the downlink message DISCONNECT or RELEASE COMPLETE, causes no adverse effects on the operation of the MS. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS Statements
- Support MT telephony (TSPC_AddInfo_MTsvc)
- Support UUS (TSPC_Serv_SS_UUS)
PIXIT Statements
- Support the sending of UUS1 information element in ALERTING message
- Support the sending of UUS1 information element in CONNECT message
- Way to activate implicit UUS1.
- Description of display of the User-user data received from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
SS initiates a call. In the SETUP message, the User-user information element shall be present. It is checked that the MS, in a way described by the manufacturer, displays the user-user data. Then, SS releases the call immediately after the MS call confirmation.
The SS initiates a second call and in the SETUP message, the User-user information element shall contain a larger data value. It is checked that the MS, in a way described by the manufacturer, displays the user-user data. Then the SS releases the call immediately after the MS call confirmation. In the RELEASE COMPLETE message, the User-user information element shall also contain a large data value. It is checked that the MS is not disturbed by the User-user optional information element.
By means of appropriate MMI function and if MS supports User-user information element in ALERTING or CONNECT messages, the user enters a string, which shall be included in the UUS1. The SS initiates a third call and in the SETUP message, the User-user information element shall be included without data. After the MS call confirmation and depending on the MS capability, it is checked that the MS sends in the User-user information element of the ALERTING message the string as requested. When the TCH is allocated and depending on the MS capability, it is checked that the MS sends in the User-user information element of the CONNECT message the string as requested. When the call is established, the SS releases the call and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element.
Maximum Duration of Test
2 minutes.
Expected Sequence
Step
Direction
Message
Comments/actions/next state
0
MS
The MS is in idle mode.
1
SS -> MS
PAGING REQUEST
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
U0, SDCCH4
4
MS -> SS
PAGING RESPONSE
7
SS -> MS
SETUP
User-user IE included with a short data value, see Specific message contents
8
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
9
MS -> SS
CALL CONFIRMED
10
SS -> MS
RELEASE COMPLETE
11
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
15
SS -> MS
PAGING REQUEST
16
MS -> SS
CHANNEL REQUEST
17
SS -> MS
IMMEDIATE ASSIGNMENT
U0, SDCCH4
18
MS -> SS
PAGING RESPONSE
21
SS -> MS
SETUP
User-user IE included with a large data value, see Specific message contents
22
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
23
MS -> SS
CALL CONFIRMED
24
SS -> MS
RELEASE COMPLETE
Message contains the User-user IE with a long data value, see Specific message contents.
25
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
26
MS
Check that the MS, in a way described by the manufacturer, displays the user-user data value after step 24
If supported, MMI actions to initiate implicit UUS1 with the string '12346aA'
30
SS -> MS
PAGING REQUEST
31
MS -> SS
CHANNEL REQUEST
32
SS -> MS
IMMEDIATE ASSIGNMENT
U0, SDCCH4
33
MS -> SS
PAGING RESPONSE
34
SS -> MS
AUTHENTICATION REQUEST
35
MS -> SS
AUTHENTICATION RESPONSE
36
SS -> MS
SETUP
User-user IE included without data. See Specific message contents.
37
MS
Check that the MS, in a way described by the manufacturer, displays no User-user data value.
38
MS -> SS
CALL CONFIRMED
39
MS -> SS
ALERTING
If MS support User-user IE in ALERTING message, then check the presence of this IE. See specific message contents.
40
MS -> SS
CONNECT
If MS support User-user IE in CONNECT message, then check the presence of this IE. See specific message contents.
41
SS -> MS
ASSIGNMENT COMMAND
TCH
42
MS -> SS
ASSIGNMENT COMPLETE
43
SS -> MS
CONNECT ACKNOWLEDGE
44
SS -> MS
DISCONNECT
With the User-user IE with a long data value, see Specific message contents
45
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
46
MS -> SS
RELEASE
47
SS-> MS
RELEASE COMPLETE
Message contains the User-user IE with a short data value, see Specific message contents.
48
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
49
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value after step 47
Specific message contents:
SETUP – step 7
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
4
- PD
User specific protocol
- user-user
The following string coded in IA5 characters :"012"
SETUP – step 21
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
33
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz012345’"
SETUP – step 36
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1
- PD
User specific protocol
- user-user
-
RELEASE COMPLETE – step 24
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
37
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789"
RELEASE COMPLETE – step 47
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
2
- PD
User specific protocol
- user-user
The following string coded in IA5 characters: "A"
ALERTING
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
8
- PD
User specific protocol
- user-user
The string '12346aA' coded in IA5 characters
CONNECT
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
Value/remark
User-user
- IEI
'7E'O
- length
8
- PD
User specific protocol
- user-user
The string '12346aA ' coded in IA5 characters
DISCONNECT
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
Value/remark
User-user
- IEI
'7E'O
- length
37
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.3 UUS / Implicit UUS1 / Interactions with Call Waiting and call HOLD supplementary services | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.3.1 Conformance requirement | There are no interactions between UUS and the Call hold (HOLD) and Call waiting (CW) supplementary services.
To activate UUS1 implicitly, the MS shall include a User-user information element in the SETUP message as part of a normal call request.
The MS shall accept the presence of User-user information element in the SETUP and DISCONNECT messages (as indicated in 3GPP TS 23.087, figure 5.2.1.2.1.1).
References
3GPP TS 23.087 subclauses 4.1.1, 5.2.1.2.1.1 and 5.2.1.2.1.
3GPP TS 24.087 subclauses 4.1.1, 6.4 and 6.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.3.2 Test purpose | 1. To verify that when in active Call State and supporting Call Hold, to initiate a second call with implicit UUS1, the MS places the first call on hold and sends a SETUP message with the User-user information element. Verify that the second call is successfully established.
2. In call active state and supporting Call Waiting, when a Call Waiting indication includes a User-user information element, the MS accepts the waiting call and places the first call on hold and successfully establishes the second call. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.14.1.3.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS has a call ("Call A-B") in the active state. The SIM in the MS under test has Call Waiting enabled.
Specific PICS Statements
- Support MO telephony (TSPC_AddInfo_MOsvc)
- Support MT telephony (TSPC_AddInfo_MTsvc)
- Support UUS (TSPC_Serv_SS_UUS)
- Support hold (TSPC_Serv_SS_HOLD)
PIXIT Statements
- Way to activate implicit UUS1.
- Description of display of the User-user data received from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
A call is established between the MS and SS. This call is the active call named Call A-B.
Using suitable MMI commands, the MS shall request that the call A-B be placed on hold. The MS shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD ACKNOWLEDGE message from the SS, the MS is made to initiate a second call with implicit UUS1. It is checked that the MS includes the User-user information element in the SETUP message. Then the SS sends an ALERTING message including the optional User-user information. It is checked that the MS, in a way described by the manufacturer, displays the User-user data value. Then the SS sends a CONNECT message including the optional User-user information element. It is checked that the MS, in a way described by the manufacturer, displays the User-user data value. on receipt of a CONNECT ACKNOWLEDGE message, MS shall enter state U10 "Active". The SS releases the second call A-C and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element.
The Call A-B is still alive. By means of appropriate MMI function, the user enters a string, which shall be included in the UUS1 sent by the MS. The SS sends a SETUP message including a User-user information element and indicating the request of a new call, named Call C-A. It is checked with the appropriate MMI function, that the MS displays the contents of the User-user information element. Then the MS shall place Call A-B on hold, and answer Call C-A. The MS shall send a HOLD message to the SS using the transaction identifier of Call A-B. On receipt of a HOLD ACKNOWLEDGE from the SS, the MS shall send a CALL CONFIRMED message and an ALERTING message to the SS, using the transaction identifier of Call C-A, and depending on the MS capability including the optional User-user information element as requested by the user. Then the MS shall send a CONNECT message to the SS, using the transaction identifier of Call C-A, and depending on the MS capability including the optional User-user information element as entered by the user. on receipt of a CONNECT ACKNOWLEDGE message, MS shall enter state U10 "Active". The SS releases the call C-A and shall include in the DISCONNECT message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element. The SS shall also include in the RELEASE COMPLETE message the optional User-user information element. It is checked that the MS is not disturbed by the User-user information element.
Then SS releases the first call A-B.
Maximum Duration of Test
2 minutes.
Expected Sequence
Step
Direction
Message
Comments/actions/next state
0
MS
Active call state with call A-B.
1
MS
If supported, MMI actions to initiate implicit UUS1 with the string '12345'.
2
MS
Call A-C is requested using MMI commands and Call A-B is placed on hold using MMI commands
3
MS -> SS
CM SERVICE REQUEST
Transaction identifier of Call A-C
4
SS -> MS
CM SERVICE ACCEPT
Transaction identifier of Call A-C
5
MS -> SS
SETUP
Check User-user IE is included, transaction identifier of Call A-C, see Specific message contents.
6
SS -> MS
ALERTING
Message contains the User-user IE with a short data value, transaction identifier of Call A-C, see Specific message contents
7
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
8
MS -> SS
HOLD
Transaction identifier of Call A-B
9
SS -> MS
HOLD ACKNOWLEDGE
Transaction identifier of Call A-B
10
SS -> MS
CONNECT
Message contains the User-user IE with a long data value, transaction identifier of Call A-C, see Specific message contents
11
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
12
MS -> SS
CONNECT ACKNOWLEDGE
Transaction identifier of Call A-C
13
SS -> MS
DISCONNECT
Without Progress Indication IE, transaction identifier of Call A-C.
With the User-user IE without data, see Specific message contents
14
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
15
MS -> SS
RELEASE
16
SS-> MS
RELEASE COMPLETE
Message contains the User-user IE with a short data value, transaction identifier of Call A-C, see Specific message contents
17
SS
Call A-B is released
18
SS -> MS
CHANNEL RELEASE
The main signalling link shall be released by the MS (L2: DISC/UA).
19
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value after step 16
20
Active call state with call A-B.
21
MS
MMI actions to initiate implicit UUS1 with the string '201'.
22
SS -> MS
PAGING REQUEST
23
MS -> SS
PAGING RESPONSE
31
SS->MS
SETUP
User-user IE is included, see Specific message contents. Transaction identifier of Call C-A
32
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
Call A-B is placed on hold using MMI commands.
34
MS -> SS
HOLD
Transaction identifier of Call A-B
35
SS -> MS
HOLD ACKNOWLEDGE
Transaction identifier of Call A-B
36
MS
Call C-A is answered using MMI commands
37
MS -> SS
CALL CONFIRMED
Transaction identifier of Call C-A
38
MS -> SS
ALERTING
If MS support User-user IE in ALERTING message, then check the presence of this IE. Transaction identifier of Call C-A
39
MS -> SS
CONNECT
If MS supports User-user IE in CONNECT message, then check the presence of this IE. Transaction identifier of Call C-A
40
SS -> MS
CONNECT ACKNOWLEDGE
Transaction identifier of Call C-A
41
SS -> MS
DISCONNECT
With the User-user IE without data, transaction identifier of Call C-A, see Specific message contents.
42
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
43
MS -> SS
RELEASE
44
SS-> MS
RELEASE COMPLETE
Message contains the User-user IE with a short data value, see Specific message contents. Transaction identifier of Call C-A
45
MS
Check that the MS, in a way described by the manufacturer, displays the User-user data value.
Specific message contents:
SETUP – step 5
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1 + the entered string length
- PD
User specific protocol
- user-user
The string as entered, coded in IA5 characters
SETUP – step 31
As default message contents as defined in subclause 26.8.4 (network direction to mobile station), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
4
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "012"
ALERTING– step 6
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
4
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "012"
ALERTING– step 38
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1 + the entered string length
- PD
User specific protocol
- user-user
The string as entered, coded in IA5 characters
CONNECT– step 10
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
37
- PD
User specific protocol
- user-user
The following string coded in IA5 characters : "abcdefghijklmnopqrstuvwxyz0123456789"
CONNECT– step 39
As default message contents as defined in subclause 26.8.4 (mobile station to network direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1 + the entered string length
- PD
User specific protocol
- user-user
The string as entered in IA5 characters
DISCONNECT
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
1
- PD
User specific protocol
- user-user
-
RELEASE COMPLETE
As default message contents as defined in subclause 26.8.4 (network to mobile station direction), except:
Information Element
value/remark
User-user
- IEI
'7E'O
- length
2
- PD
User specific protocol
- user-user
The following string coded in IA5 characters: "A" |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15 Follow Me (FM) | This subclause applies to mobile station supporting Follow Me (FM). The objective of this clause is to test FM concerned procedures.
Unless indicated in individual sub-clauses, the default message contents in subclause 31.11 are applied. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.1 Follow Me (FM) / Registration | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.1.1 Conformance requirement | 1. The initiating subscriber registers the Follow Me feature with respect to a particular remote party. The initiating subscriber shall provide the following information to the network: the number of the remote party. The initiating subscriber shall receive an indication if the FM registration request was accepted or rejected by the network.
2. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.
3. As an operator's option additional information (such as passwords) for registration may be required from the initiating subscriber. This information shall be coded as a USSD string with a length not exceeding 30 characters.
4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.
5. 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 an SS version indicator if the unstructured data entered by the user can be coded as an IA5 string.
References
3GPP TS 22.094 subclause 6.3.
3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.
3GPP TS 24.090 subclause 6.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.1.2 Test purpose | 1. To check that the MS correctly requests a supplementary service transaction for registration of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.
2. To check that the MS sends a REGISTER message using USSD phase 2 and containing the FM-request control message for registration.
3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer).
4. To check that upon receipt of a rejection from the network with the problem code "unrecognized operation" or a cause "Facility rejected", the MS re-attempt the request by using USSD version 1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.1.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN.
Specific PICS Statements
-
PIXIT Statements
- Way to activate the registration of FM.
- Description of display of the FM answers from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
By means of appropriate MMI functions, the user requests registration of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (as described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.
The user requests registration of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.
Then user request again two registrations, upon receipt of the REGISTER message, SS answers with a RELEASE COMPLETE message including a rejection with respectively the problem code "unrecognized operation" or a cause "facility rejected". Check that MS re-attempt the request by using USSD version 1: without the SS version indicator information element included in the REGISTER message.
Maximum Duration of Test
2 minutes.
Expected Sequence
Test steps 1 to 10 are executed for k=1 to 13 with respectively the following error values:
1. Illegal interaction with incoming barring.
2. Unauthorised request.
3. Unknown remote party.
4. FM not subscribed.
5. Remote party already registered.
6. Unauthorised changes to remote party.
7. Illegal interaction with call forwarding.
8. Illegal interaction with call barring.
9. Request to own MSISDN not possible.
10. Forwarded-to number is invalid directory number.
11. Insufficient information.
12. Forwarded-to number is a special code.
13. Conflicting situation with other supplementary services.
Step
Direction
Message
Comments
0
MS
The MS is in idle mode.
1
MS
The MS is made to initiate a registration of FM
2
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
7
SS -> MS
RELEASE COMPLETE
With an unsuccessful FM-result info with the following error value:
k=1: Illegal interaction with incoming barring (code 21)
k=2: Unauthorised request (code 22)
k=3: Unknown remote party (code 41)
k=4: FM not subscribed (code 42)
k=5: Remote party already registered (code 61)
k=6: Unauthorised changes to remote party (code 64)
k=7: Illegal interaction with call forwarding (code 65)
k=8: Illegal interaction with call barring (code 66)
k=9: Request to own MSISDN not possible (code 67)
k=10: Forwarded-to number is invalid directory number (code 80)
k=11: Insufficient information (code 81)
k=12: Forwarded-to number is a special code (code 82)
k=13: Conflicting situation with other supplementary services (code 83)
See specific message contents.
8
SS -> MS
CHANNEL RELEASE
9
MS
Check that the MS, in a way described by the manufacturer, displays the error after step 7
15
MS
The MS is made to initiate a registration of FM
16
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
17
SS -> MS
IMMEDIATE ASSIGNMENT
18
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
19
SS -> MS
CM SERVICE ACCEPT
20
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
21
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
22
SS -> MS
CHANNEL RELEASE
23
MS
It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 21
30
MS
The MS is made to initiate a registration of FM
31
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
32
SS -> MS
IMMEDIATE ASSIGNMENT
33
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
34
SS -> MS
CM SERVICE ACCEPT
35
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
36
SS -> MS
RELEASE COMPLETE
Including a rejection with the problem code "unrecognized operation"
37
SS -> MS
CHANNEL RELEASE
38
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
39
SS -> MS
IMMEDIATE ASSIGNMENT
40
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
41
SS -> MS
CM SERVICE ACCEPT
42
MS -> SS
REGISTER
Check that SS version indicator IE is not included. See specific message contents.
43
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
44
SS -> MS
CHANNEL RELEASE
45
It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 43
50
MS
The MS is made to initiate a registration of FM
51
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
52
SS -> MS
IMMEDIATE ASSIGNMENT
53
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
54
SS -> MS
CM SERVICE ACCEPT
55
MS -> SS
REGISTER
The SS checks that the content of this message matches specific message contents.
56
SS -> MS
RELEASE COMPLETE
Including a rejection with the cause value Facility rejected. See specific message contents.
57
SS -> MS
CHANNEL RELEASE
58
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
59
SS -> MS
IMMEDIATE ASSIGNMENT
60
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
61
SS -> MS
CM SERVICE ACCEPT
62
MS -> SS
REGISTER
Check that SS version indicator IE is not included. See specific message contents.
63
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
64
SS -> MS
CHANNEL RELEASE
65
MS
It is checked that the MS, in a way described by the manufacturer, displays the positive result after step 63
Specific message contents:
REGISTER
Information Element
value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
'1011'B
Message type
As 3GPP TS 24.080
Facility 1C
See below
SS version indicator
As specified in 3GPP TS 24.080
For steps 42 and 62 omitted
For steps 6, 20, 35 and 55, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
Invoke CS/C/tag=1
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
For step 6 **214*04965878***#
For step 20 **214*04969***#
For steps 35 and 55 **214*31245688***#
RELEASE COMPLETE
Information Element
value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
the transaction value is the same as the REGISTER transaction value but the transaction flag is different
Message type
As 3GPP TS 24.080
Cause
For step 56, cause is set to "facility rejected" and FIE is omitted.
For steps 7,21,43,63,36 this field is omitted.
Facility Information Element
See below (omitted for step 56)
SS version indicator
As specified in 3GPP TS 24.080
For steps 7, 21, 43 and 63, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
Return result
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
Ussd-dataCodingScheme
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"
Ussd-string
For step 7: value of the error code
For steps 21 43 and 63: 01
For step 36, Facility Information Element with Reject = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
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 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.2 Follow Me (FM) / Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.2.1 Conformance requirement | 1. An initiating subscriber (also the FM service supervisor) shall be able to interrogate the Follow Me data of any remote party, for which she is authorised to become initiating subscriber.
2. In case the remote party corresponds to a subscriber the remote party shall be able to interrogate her own Follow Me data stored in the network.
3. As an operator's option additional information (such as passwords) for interrogation may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters.
4. All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.
5. MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.
References
3GPP TS 22.094 subclauses 6.8 and 7.3.
3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.
3GPP TS 24.090 subclause 6.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.2.2 Test purpose | 1. To check that the MS (as initiating subscriber or remote party) correctly requests a supplementary service transaction for interrogation of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.
2. To check that the MS sends a REGISTER message using USSD version 2 and containing the FM-request control message for interrogation.
3. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is registered to FM with respect to a remote party B.
Specific PICS Statements
-
PIXIT Statements
- Way to activate the interrogation of FM.
- Description of display of the FM answers from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
MS is registered to FM.
By means of appropriate MMI functions, the user requests interrogation of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result in a facility information element. Check that the MS provides the appropriate user indication (was described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.
The user requests interrogation of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.
Maximum Duration of Test
2 minutes.
Expected Sequence
Test steps 1 to 10 are executed for k=1 to 6 with respectively the following error values:
1. Illegal interaction with incoming barring.
2. Unauthorised request.
3. Unknown remote party.
4. FM not subscribed.
5. FM not registered to remote party.
6. Conflicting situation with other supplementary services.
Step
Direction
Message
Comments
0
MS
The MS is in idle mode. MS is registered to FM with respect to a remote party B.
1
MS
The MS is made to initiate an interrogation of FM of remote subscriber other than B.
2
MS -> SS
CHANNEL REQUEST
with establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
7
SS -> MS
RELEASE COMPLETE
With an unsuccessful FM-result info with the following error value:
k=1: Illegal interaction with incoming barring (code 21)
k=2: Unauthorised request (code 22)
k=3: Unknown remote party (code 41)
k=4: FM not subscribed (code 42)
k=5: FM not registered to remote party (code 62)
k=6: Conflicting situation with other supplementary services (code 83)
See specific message contents.
8
SS -> MS
CHANNEL RELEASE
9
MS
It is checked that the MS, in a way described by the manufacturer, displays the error after step 7
15
MS
The MS is made to initiate an interrogation of FM of remote party B.
16
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
17
SS -> MS
IMMEDIATE ASSIGNMENT
18
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
19
SS -> MS
CM SERVICE ACCEPT
20
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
21
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
22
SS -> MS
CHANNEL RELEASE
23
MS
Check that the MS, in a way described by the manufacturer, displays the positive result after step 21
Specific message contents:
REGISTER
Information Element
value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
‘1011’B
Message type
As 3GPP TS 24.080
Facility 1C
See below
SS version 7F
As 3GPP TS 24.080
For steps 6 and 20, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
CS/C/tag=1
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
Ussd-dataCodingScheme
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"
Ussd-string
For step 6: #21445896**#
For step 20: #21431245688**#
RELEASE COMPLETE
Information Element
value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
the transaction value is the same as the REGISTER transaction value but the transaction flag is different
Message type
As 3GPP TS 24.080
Cause
Omitted.
Facility Information Element
See below
SS version indicator
As specified in 3GPP TS 24.080
For steps 7 and 21, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
Return result
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
Ussd-dataCodingScheme
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"
Ussd-string
For step 7: value of the error code
For steps 21: 03 31245688 |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.3 Follow Me (FM) / Erasure | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.3.1 Conformance requirement | A previous FM registration can be erased in either of the following ways:
a) The initiating subscriber can specifically erase her previous registration with an appropriate control procedure.
b) In case the remote party corresponds to a subscriber the remote party can erase any previous registration with an appropriate control procedure.
c) The FM service supervisor can erase any previous registration to any remote party with an appropriate control procedure (forced erasure).
The subscriber who initiates the FM erase request shall be informed of the outcome of the request by the network.
As an operator's option additional information (such as passwords) for erasure may be required from the subscriber. The registration procedure shall transport this information from the subscriber to the network of the remote party. This information shall be coded as a USSD string with a length not exceeding 30 characters.
MS shall behave as indicated in the Information flow as indicated in 3GPP TS 23.094, figure 4.1.
All the messages between MS and the mobile network and internal to the mobile network, which are used for control of Follow Me, are USSD Phase 2 messages.
References
3GPP TS 22.094 subclause 6.4.
3GPP TS 23.094 subclauses 4.1, 4.2 and 4.4.
3GPP TS 24.090 subclause 6.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.3.2 Test purpose | 1. To check that the MS, acting as an initiating subscriber or as a remote party, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST.
2. To check that the MS as initiating subscriber or remote party sends a REGISTER message containing the FM-request control message for erasure.
3. To check that the MS, acting as a supervisor, correctly requests a supplementary service transaction for erasure of FM in CHANNEL REQUEST message and in the subsequent CM SERVICE REQUEST
4. To check that the MS as supervisor sends a REGISTER message containing the FM-request control message for forced-erasure.
5. To check that upon receipt of the result or the error of the operation (in a RELEASE COMPLETE message), the MS provides the appropriate user indication (as described by the manufacturer). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.15.3.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is in MM-state "idle, updated" with valid TMSI and CKSN. The MS is registered to FM with respect to a remote party B.
Specific PICS Statements
-
PIXIT Statements
- Way to activate the erasure of FM.
- Description of display of the FM answers from the network.
Foreseen final state of the MS
The MS is in MM-state "idle, updated" with valid TMSI.
Test procedure
MS is registered to FM.
By means of appropriate MMI functions, the user requests erasure of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (as described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.
The user requests erasure of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.
By means of appropriate MMI functions, the user requests forced-erasure of FM for a remote number. Upon receipt of the REGISTER message, SS answers with the RELEASE COMPLETE message with an unsuccessful FM-result information. Check that the MS provides the appropriate user indication (which is to be described by the manufacturer). Then SS transaction is released. This procedure is executed for all possible error values.
The user requests forced-erasure of FM for another remote subscriber. Upon receipt of the operation (in a REGISTER message), SS answers with a RELEASE COMPLETE message with a successful FM-response information. Check that the MS provides the appropriate user indication (as described by the manufacturer). The SS transaction is released.
Maximum Duration of Test
2 minutes.
Expected Sequence
Test steps 1 to 10 and 25 to 34 are executed for k=1 to 10 with respectively the following error values:
1. Illegal interaction with incoming barring.
2. Unauthorised request.
3. Unknown remote party.
4. FM not subscribed.
5. FM not registered to remote party.
6. Remote party not registered to this MSISDN.
7. Unauthorised changes to remote party.
8. Illegal interaction with call barring.
9. Insufficient information.
10. Inconsistent with registration.
Step
Direction
Message
Comments
0
MS
The MS is in idle mode. MS is registered to FM with respect to a remote party B.
1
MS
The MS is made to initiate erasure of FM for a remote subscriber other than B.
2
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
5
SS -> MS
CM SERVICE ACCEPT
6
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
7
SS -> MS
RELEASE COMPLETE
With an unsuccessful FM-result info with the following error value:
k=1: Illegal interaction with incoming barring (code 21)
k=2: Unauthorised request (code 22)
k=3: Unknown remote party (code 41)
k=4: FM not subscribed (code 42)
k=5: FM not registered to remote party (code 62)
k=6: Remote party not registered to this MSISDN (code 63)
k=7: Unauthorised changes to remote party (code 64)
k=8: Illegal interaction with call barring (code 66)
k=9: Insufficient information (code 81)
k=10: Inconsistent with registration (code 84)
See specific message contents.
8
SS -> MS
CHANNEL RELEASE
9
MS
Check that the MS, in a way described by the manufacturer, displays the error after step 7
15
MS
The MS is made to initiate erasure of FM for remote subscriber B
16
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
17
SS -> MS
IMMEDIATE ASSIGNMENT
18
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
19
SS -> MS
CM SERVICE ACCEPT
20
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
21
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
22
SS -> MS
CHANNEL RELEASE
23
MS
Check that the MS, in a way described by the manufacturer, displays the positive result after step 21
25
MS
The MS is made to initiate forced erasure
26
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
27
SS -> MS
IMMEDIATE ASSIGNMENT
28
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
29
SS -> MS
CM SERVICE ACCEPT
30
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
31
SS -> MS
RELEASE COMPLETE
With an unsuccessful FM-result info with the following error value:
k=1: Illegal interaction with incoming barring (code 21)
k=2: Unauthorised request (code 22)
k=3: Unknown remote party (code 41)
k=4: FM not subscribed (code 42)
k=5: FM not registered to remote party (code 62)
k=6: Remote party not registered to this MSISDN (code 63)
k=7: Unauthorised changes to remote party (code 64)
k=8: Illegal interaction with call barring (code 66)
k=9: Insufficient information (code 81)
k=10: Inconsistent with registration (code 84)
See specific message contents.
32
SS -> MS
CHANNEL RELEASE
33
MS
Check that the MS, in a way described by the manufacturer, displays the negative result after step 31
40
MS
The MS is made to initiate forced erasure
41
MS -> SS
CHANNEL REQUEST
With establishment cause "Other procedures which can be completed with an SDCCH"
42
SS -> MS
IMMEDIATE ASSIGNMENT
43
MS -> SS
CM SERVICE REQUEST
Cause: "supplementary service activation"
44
SS -> MS
CM SERVICE ACCEPT
45
MS -> SS
REGISTER
Check that the content of this message matches specific message contents.
46
SS -> MS
RELEASE COMPLETE
With a successful FM-result. See specific message contents.
47
SS -> MS
CHANNEL RELEASE
48
MS
Check that the MS, in a way described by the manufacturer, displays the positive result after step 46
Specific message contents:
REGISTER
Information Element
value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
'1011'B
Message type
As 3GPP TS 24.080
Facility 1C
See below
SS version 7F
As 3GPP TS 24.080
For steps 6, 20, 30 and 45, Facility Information Element with Invoke = ProcessUnstructuredSS-Request component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.3.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
CS/C/tag=1
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
Ussd-dataCodingScheme
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"
Ussd-string
For step 6: ##214*45896***#
For step 20: ##214*31245688***#
For steps 30 and 45: ##214*45896*88*0436987*#
RELEASE COMPLETE
Information Element
Value/remark
Supplementary service protocol discriminator
Supplementary service (call independent)
Transaction identifier
the transaction value is the same as the REGISTER transaction value but the transaction flag is different
Message type
As 3GPP TS 24.080
Cause
Omitted.
Facility Information Element
See below
SS version indicator
As specified in 3GPP TS 24.080
For steps 7, 21, 31 and 46, Facility Information Element with Return result = ProcessUnstructuredSS-Request return result component type as defined in 3GPP TS 24.080 subclause 3.6.1 table 3.6.
Contents
Value/remark
Facility IE identifier
As 3GPP TS 24.080
Length of FIE contents
depending on the length of ussd-string
Component type tag
Return result
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
Ussd-dataCodingScheme
1 octet long. Alphabet indicator set to "default alphabet". Language indicator set to "undefined"
Ussd-string
For steps 7 and 31: value of the error code
For steps 21 and 46: 02
32 Testing of speech transcoding functions
The test sequences for speech transcoding and DTX tests, both for input and required output, are defined in 3GPP TS 06.10, clause 5, and 3GPP TS 06.32, clause 4 for the full rate speech codec. For the half rate speech codec the test sequences are defined in 3GPP TS 06.20, clause 5 and 3GPP TS 06.42 clause 7. They are available on floppy disks in IBM/AT MS-DOS format from ETSI publications department.
The Digital Audio Interface (DAI) is described in subclause 36.4.
NOTE: For a definition of the term "traffic frame" used in this clause, refer to 3GPP TS 06.32 and 3GPP TS 06.42. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1 Full Rate Downlink speech transcoding | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.1 Definition | Downlink speech transcoding transforms the 13 kbit/s net bit stream obtained by channel decoding the incoming bit stream from the air interface to 13 bit linear PCM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.2 Conformance requirement | The output bit stream from the speech transcoder shall be continuous and bit by bit exactly the same as the predefined output sequence (SEQ01.OUT, SEQ03.OUT, SEQ04.OUT and SEQ05.OUT).
3GPP TS 06.01, clause2.
3GPP TS 06.10, subclauses 5.2 and 5.2.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.3 Test purpose | To verify that the speech transcoding of the MS can transform all predefined sequences (SEQ01.OUT, SEQ03.OUT, SEQ04.OUT and SEQ05.OUT) at 13 kbits/s level to 104 kbit/s (13 bit linear PCM at 8 kHz) level correctly. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.4.1 Initial conditions | DTX is off.
The DAI of the MS is connected to the SS and is set to the operating mode "Test of speech decoder/DTX functions (downlink)". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.4.2 Procedure | a) The SS resets the speech decoder of the MS via the DAI.
b) The SS sends test sequence SEQ01.COD at 13 kbit/s to the MS via the air interface after passing it through the SS channel encoder.
NOTE: These test sequence files contain 16 bit words for all speech encoded parameters and are justified as described in 3GPP TS 06.10 table 5.1. 76 words are used as input in a period of 20 ms.
c) The SS records the 104 kbit/s output bit stream from the MS on the digital audio interface.
d) The test is repeated using the test sequences SEQ03.COD, SEQ04.COD and SEQ05.COD. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.1.5 Test requirements | The bit stream output shall be continuous and bit by bit exactly the same as the sequence given in the files SEQ01.OUT, SEQ03.OUT, SEQ04.OUT and SEQ05.OUT.
NOTE: These files contain 16 bit words of 13 bit linear PCM left justified. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2 Full Rate Downlink receiver DTX functions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.1 Definition | The DTX receiver functions consist of a SID frame detector, comfort noise generator functions and lost frame substitution and muting functions. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.2 Conformance requirement | 1) The output level of the decoder has to be constant for an input signal consisting of identical speech frames.
3GPP TS 06.10.
2/3) When, after the first lost speech frame subsequent speech frames are lost, a muting technique shall be used that will gradually decrease the output level, resulting in the silencing of the output after a maximum of 320 ms. Speech frames with the FACCH flag set provoke a Bad Frame Indication (BFI = 1) and are hence regarded as lost speech frames.
3GPP TS 06.01, clause 6; 3GPP TS 06.11, subclauses 2.1 and 2.2, clause 3 for requirement 2 (first part).
3GPP TS 06.01, clause 6; 3GPP TS 06.11, subclauses 2.1 and 2.2, clause 3; 3GPP TS 06.31, subclauses 1.2.2 and 3.1.1 for requirement 3 (second part).
4/5) A valid SID-frame followed by a sequence of lost speech frames shall result in comfort noise generation with constant block amplitude parameters. Speech frames with the FACCH flag set provoke a Bad Frame Indication (BFI = 1) and are hence regarded as lost speech frames.
3GPP TS 06.01, clauses 3 and 5; 3GPP TS 06.12, clause 3 and subclause 3.1.
3GPP TS 06.31, subclauses 1.2.2, 3.1, 3.1.1 and 3.1.2 for requirement 4 (first part).
3GPP TS 06.01, clauses 3, 5 and 6; 3GPP TS 06.11, subclauses 2.1 and 2.2; 3GPP TS 06.12, clause 3 and subclause 3.1.
3GPP TS 06.31, subclauses 1.2.2, 3.1, 3.1.1 and 3.1.2 for requirement 5 (second part).
6/7) An invalid SID-frame followed by a sequence of lost speech frames shall result in comfort noise generation, using the set of parameters from the last valid SID-frame. Speech frames with the FACCH flag set provoke a Bad Frame Indication (BFI = 1) and are hence regarded as lost speech frames.
3GPP TS 06.01, clauses 3 and 5; 3GPP TS 06.12, clause 3 and subclause 3.1.
3GPP TS 06.31, subclauses 1.2.2, 3.1, 3.1.1 and 3.1.2 for requirement 6 (first part).
3GPP TS 06.01, clauses 3, 5 and 6; 3GPP TS 06.11, subclauses 2.1 and 2.2; 3GPP TS 06.12, clause 3 and subclause 3.1.
3GPP TS 06.31, subclauses 1.2.2, 3.1, 3.1.1 and 3.1.2 for requirement 7 (second part).
8) The energy of the output signal is controlled by the block amplitude parameter, xmaxc.
3GPP TS 06.10, subclauses 3.1.20, 3.1.21 and 3.2.1.
9/10) The first SID-frame that is expected and not received shall be substituted by the last valid SID-frame and the procedure for valid SID-frames shall be applied. For the second lost SID-frame, a muting technique shall be used that will gradually decrease the output level, resulting in silencing the output after a maximum of 320 ms. Speech frames with the FACCH flag set provoke a Bad Frame Indication (BFI = 1) and are hence regarded as lost speech frames.
3GPP TS 05.08, subclause 8.3; 3GPP TS 06.01, clause 6; 3GPP TS 06.11, subclauses 2.3 and 2.4.
3GPP TS 06.31, subclauses 1.2.2, 3.1.1 and 3.1.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.3 Test purpose | 1) To verify that the signal energy at the output of the decoder is constant with a tolerance of ±3 dB if a sequence of identical speech frames is applied at the receiver input.
2) To verify that the muting function of the receiver is within the required limits if a sequence of lost speech frames is applied at the receiver input.
3) To verify that the muting function of the receiver is within the required limits if a sequence of speech frames with the FACCH flag set is applied at the receiver input.
4) To verify the function of comfort noise generation when a valid SID-frame is received followed by a sequence of lost speech frames. The signal energy at the output of the decoder shall be constant with a tolerance of ±3 dB.
5) To verify the function of comfort noise generation when a valid SID-frame is received followed by a sequence of speech frames with the FACCH flag set. The signal energy at the output of the decoder shall be constant with a tolerance of ±3 dB.
6) To verify the function of comfort noise generation when an invalid SID-frame is received followed by a sequence of lost speech frames. The signal energy at the output of the decoder shall be constant with a tolerance of ±3 dB.
7) To verify the function of comfort noise generation when an invalid SID-frame is received followed by a sequence of speech frames with the FACCH flag set. The signal energy at the output of the decoder shall be constant with a tolerance of ±3 dB.
8) To verify that the signal energy at the output of the decoder depends on the block amplitude xmaxc of the input frames if a sequence of speech frames is applied to the decoder. The signal energy at the output of the decoder shall be constant with a tolerance of ±3 dB.
9) To verify the SID-frame substitution and muting functions on the comfort noise, if two consecutive expected SID-frames are lost with the other frames being lost speech frames.
10) To verify the SID-frame substitution and muting functions on the comfort noise, if two consecutive expected SID-frames are lost with the other frames being speech frames with the FACCH flag set. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.4.1 Initial conditions | Uplink DTX is off.
The DAI of the MS is connected to the SS and is set to the operating mode "Test of speech decoder/DTX functions (downlink)". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.4.2 Procedure | a) The SS transmits coded "speech" traffic frames on the air interface after passing them trough the SS channel encoder. They contain a special test signal at 13 kbit/s as defined below. All traffic frames are identical with the exception of some frames which are SID frames as defined in 3GPP TS 06.32.
b) The energy of the PCM signal is evaluated (as a mean square average) at the digital audio interface of the MS at 104 kbit/s level (13 bit, 8 kHz linear PCM) and recorded for each block of 20 ms synchronized to the 20 ms speech frame structure.
c) The SS transmission of the TDMA frames of the TCH/FS on the air interface is ramped "on" and "off" on a traffic frame by traffic frame basis, taking into account the block diagonal interleaving scheme defined in 3GPP TS 05.03. The first traffic frame in step 1 occurs one frame after the window of the SACCH multiframe (TDMA frame 60 modulo 104), allocated for the SID frame (see 3GPP TS 05.02 and 3GPP TS 05.08). The SACCH will also be transmitted.
NOTE 1: 8 timeslots in 8 consecutive TCH/FS TDMA frames are seen as one traffic frame, and the next traffic frame starts in the middle of the previous one (i.e. after 4 TDMA frames of the previous one) due to the block diagonal interleaving scheme defined in 3GPP TS 05.03.
d) The special test frame is an encoded "speech" traffic frame of 260 bits obtained from white Gaussian noise band limited to 300 Hz to 3 400 Hz. When repeated, the special test frame results in a humming sound with a fairly constant level when decoded, and is defined in table 32-1.
Table 32-1: Table of special test traffic frame for receiver DTX tests
Encoded parameter
Value
LARc(1)
38
LARc(2)
42
LARc(3)
24
LARc(4)
20
LARc(5)
10
LARc(6)
9
LARc(7)
5
LARc(8)
3
Sub-block no:
0
1
2
3
Grid position (Mc)
1
3
2
0
Block amplitude (xmaxc)
40
40
40
40
LTP gain (Bc)
0
0
0
0
LTP lag (Nc)
40
120
40
120
RPE pulses (xmc)
- pulse no 1
4
6
6
6
- pulse no 2
4
5
4
3
- pulse no 3
2
1
3
4
- pulse no 4
6
2
1
3
- pulse no 5
3
6
4
1
- pulse no 6
5
1
6
3
- pulse no 7
5
2
5
5
- pulse no 8
5
6
2
1
- pulse no 9
1
3
4
4
- pulse no 10
3
2
4
3
- pulse no 11
5
5
4
5
- pulse no 12
6
1
2
2
- pulse no 13
1
3
4
3
NOTE 2: The signal energy of the decoded special test frame is controlled with the block amplitude parameter (xmaxc). Reducing xmaxc from 40 to 32 reduces the signal energy by 6 dB, and reducing xmaxc from 40 to 24 reduces the signal energy by 12 dB.
e) The sequence of traffic frames on the air interface is as follows:
e.1) 23 test frames "on".
e.2) 20 frames "off".
e.3) 20 test frames "on".
e.4) 1 SID frame followed by 6 frames "off", another identical SID frame and 23 frames "off". Except for the SID codeword, the SID frames are identical to the test frame.
e.5) 1 different SID frame, however with 2 to 15 errors inserted in the SID codeword, followed by 23 frames "off".
e.6) 20 test frames "on", but with the block amplitude parameter xmaxc = 24.
e.7) 1 SID frame followed by 50 frames "off". Except for the SID codeword, the SID frames are identical to the test frame.
e.8) The whole test is repeated, but the frames "off" are replaced by frames "on" with the FACCH flag set. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.2.5 Test requirements | 1) In step e.1), the signal energy shall be fairly constant within ±3 dB.
2) In step e.2), the signal energy shall decrease to less than -60 dBm within 17 frames.
3) In step e.4), comfort noise shall be generated. The same requirements as in step e.1) apply.
4) In step e.5), the same requirements as in step e.4) apply.
5) In step e.6), the same requirements as in step e.1) apply. However, the signal energy shall be 12 dB lower.
6) In step e.7), the signal energy shall be fairly constant within ±3 dB for 28 frames. Then the signal energy shall decrease to less than -60 dBm within 16 frames.
7) In step e.8), the same requirements as in all previous steps apply. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3 Full Rate Uplink speech transcoding | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.1 Definition | Uplink speech transcoding transforms 13 bit linear PCM to the 13 kbit/s net bit stream. This net bit stream is to be channel encoded for transmission on the air interface. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.2 Conformance requirement | The output bit stream from the speech transcoder shall be bit by bit exactly the same as the predefined output sequence (SEQ01.OUT, SEQ02.OUT, SEQ03.OUT and SEQ04.OUT).
3GPP TS 06.01, clause 2.
3GPP TS 06.10, subclauses 5.2 and 5.2.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.3 Test purpose | To verify that the speech transcoder on the MS can transform all predefined sequences (SEQ01.INP, SEQ02.INP, SEQ03.INP and SEQ04.INP) at 104 kbit/s (13 bit linear PCM at 8 kHz) level to 13 kbit/s level correctly. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.4.1 Initial conditions | Uplink DTX is off.
The DAI of the MS is connected to the SS and is set to the operating mode "Test of speech encoder/DTX functions (uplink)". |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.4.2 Procedure | a) The SS resets the speech decoder on the MS (see subclause 36.4).
b) The SS sends a test sequence SEQ01.INP to the MS at 104 kbit/s level via the digital audio interface.
NOTE: These files contain 16 bit words for 13 bit linear PCM left justified. See also 3GPP TS 06.10 table 5.1.
c) The SS records the 13 kbit/s output bit stream obtained by channel decoding the incoming bit stream from the air interface.
d) The test is repeated using the test sequences SEQ02.INP, SEQ03.INP and SEQ04.INP. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.3.5 Test requirements | The bit stream output shall be bit by bit exactly the same as the sequence given in the files SEQ01.COD, SEQ02.COD, SEQ03.COD and SEQ04.COD.
NOTE: These files contain 16 bit words of all the 76 parameters in a speech frame justified as in 3GPP TS 06.10 table 5.1. 76 codewords shall occur in a frame of 20 ms. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4 Full Rate Uplink transmitter DTX functions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.1 Definition | The VAD/DTX transmitter functions consist of a Voice Activity Detector (VAD) and a surrounding Discontinuous Transmission (DTX) system introducing additional "speech" traffic frames on the air interface compared to those the VAD itself would classify as speech frames containing real speech. The additional traffic frames on the air are introduced due to:
1) A "hangover" period at the end of speech bursts in order to be certain that the traffic frames contain only noise and to evaluate the background acoustic noise characteristics when no real speech is present.
2) Special traffic frames (SID frames) added on the air at regular intervals containing only the evaluated background acoustic noise characteristics. These frames are used for generation of comfort noise in speaker silence periods on the receiving side. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.2 Conformance requirement | The MS VAD and DTX function allows only those frames to be transmitted that are either marked with SP = 1 or that are properly positioned SID-frames.
3GPP TS 05.08, subclause 8.3; 3GPP TS 06.01, clauses 3 and 4; 3GPP TS 06.31, subclauses 2.1, 2.1.1 and 2.1.2; 3GPP TS 06.32, clauses 1 and 2, subclauses 2.1 and 2.2.8. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.3 Test purpose | To verify that the combination of VAD and DTX operates correctly. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.4.1 Initial conditions | A call is set up on a TCH/FS according to the generic call set-up procedure.
Uplink DTX is on.
The DAI of the MS is connected to the SS and is set to the operating mode "Test of speech encoder/DTX functions (uplink)".
32.4.4.2 Procedure.
a) The SS sends a test sequence SPEC_A1.INP of PCM samples, which are grouped into frames of 20 ms synchronized to the TDMA and traffic frame structure on the air interface, on the digital audio interface in the MS at 104 kbits/s (13 bit, 8 kHz linear PCM).
The start of the test sequences is synchronized with the radio transmission on the air interface so that the first traffic frame on the air occurs just after the traffic frame allocated for the SID frame (TDMA frame 56 modulo 104, see 3GPP TS 05.02 and 3GPP TS 05.08).
NOTE: 8 timeslots in 8 consecutive TCH/FS TDMA frames are seen as one traffic frame and the next traffic frame starts in the middle of the previous one (i.e. after 4 TDMA frames of the previous one) due to the block diagonal interleaving scheme defined in 3GPP TS 05.03.
b) The SS detects whether or not there is any power transmitted over the radio path on a timeslot basis excluding SACCH frames. The speech frame by speech frame on/off transmission (on = 1) is recorded.
c) The test is repeated for all test sequences *.INP described in 3GPP TS 06.32 clause 4. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.4.5 Test requirements | 1) In step b), the traffic frame on/off sequence recorded shall be bit exact like the sequence of SP flags stored as bit 15 of LAR(2) on the respective reference files *.COD described in 3GPP TS 06.32, with the following exceptions:
1.1) The occurrence of a SID frame in its allowed window within the SACCH multiframe as defined in 3GPP TS 05.08.
1.2) The occurrence of a SID frame after 1 or more real speech frames consecutively transmitted on the air. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5 Full Rate Speech channel transmission delay | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.1 Definition | The total transmission delay within the various elements of a GSM system are specified as round trip delays. For the MS this would be equivalent to applying an RF equivalent of a speech signal to the MS receiver, closing an acoustic path from the ERP to the MRP, detecting the corresponding RF signal at the MS transmitter output and measuring the time interval between the signal originally fed to the MS receiver and that transmitted by the MS transmitter.
This simple approach cannot be demonstrated to be accurate due to the inherent non linear characteristic of the speech transcoder. The overall delay therefore is split into four identifiable and measurable delays. The delays are respectively:
- the downlink delay from RF input to DAI output;
- DAI output to ERP;
- MRP to DAI output; and
- DAI to uplink RF output.
Each delay is defined and its method of test described in the following subclauses. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.2 Conformance requirement | The overall speech channel transmission delay shall be less than 143,9 ms.
3GPP TS 03.50, subclause 3.3.6.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.3 Test purpose | To verify that the round trip delay, of a speech channel for a MS, which consists of the sum of:
- the downlink delay from RF input to DAI output;
- DAI output to ERP;
- MRP to DAI output; and
- DAI to uplink RF output;
meets the requirements when using the predefined test sequences SEQ01.COD, SEQ03.COD, SEQ04.COD and SEQ05.COD. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.4 Downlink processing delay | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.4.1 Definition | The downlink processing delay is the delay from the first bit of a speech block transmitted from the RF output of the SS up to the last bit of the corresponding speech block received at the DAI on the output of the speech transcoder. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.4.2 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 32.5.4.2.1 Initial conditions | DTX is off.
The DAI of the MS is connected to the SS and is set to the operating mode "Test of speech decoder/DTX functions (downlink)". |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.