31.14 User-to-User Signalling (UUS)
3GPP51.010-1Mobile Station (MS) conformance specificationPart 1: Conformance specificationTS
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.
31.14.1 UUS / Implicit UUS1
31.14.1.1 UUS / Implicit UUS1 / CC MO call
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.
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.
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" |
31.14.1.2 UUS / Implicit UUS1 / CC MT call
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.
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.
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" |
31.14.1.3 UUS / Implicit UUS1 / Interactions with Call Waiting and call HOLD supplementary services
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.
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.
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" |