15.6 Call Hold supplementary services
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
General
In this subclause, subscriber A is the UE under test, and subscribers B and C are distant parties in the calls used in the test cases.
15.6.1 Call completion supplementary services, Hold invocation
15.6.1.1 Definition
15.6.1.2 Conformance requirement
1) The served mobile subscriber indicates to the network that communication on the interface is to be interrupted.
The hold function should be invoked in association with an existing active call.
The invocation of the hold function does not affect the existing 3GPP TS 24.008 call states, but does affect the auxiliary state. The request for placing a call on hold places the auxiliary state in the hold request state. The responding entity will acknowledge this request with a HOLD ACKNOWLEDGE message if this operation was successful (see figure 2.1). This will result in the auxiliary state being put in the Call held state.
If the requested hold function cannot be obtained, then a HOLD REJECT message will be returned with the appropriate cause (see figure 2.1). This will result in the auxiliary state returning to the Idle state. The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B.
2) It is possible to place a call on hold in the Active state. The concept of dimensioned state space is being introduced to ensure state synchronization between the mobile station and the network. This concept suggests dimensioning the call state machine into two dimensions. In other words, there would be two states associated with each call. The first would be a 3GPP TS 24.008 call state and the second would be an auxiliary state associated with hold. Suppose the dimensioned state space is represented by two co-ordinates: one is a 3GPP TS 24.008 call state co-ordinate and the other is a hold co-ordinate. If a 3GPP TS 24.008 call state transition occurs, the former co-ordinate is updated. If a call is put on hold, the hold co-ordinate is updated. When the held call is reconnected, the hold co-ordinate is again updated.
There are four auxiliary states associated with the hold and retrieve functions:
– Idle;
– Hold request;
A request has been made for the hold function.
– Call held;
The call is held and the user information path has been reserved.
– Retrieve request;
A request has been made for the retrieve function.
Reference(s)
TS 24.083 clauses 2.1.2 and 2.1.5.
15.6.1.3 Test purpose
1) To verify the ability of a UE to invoke the Call Hold service when it has an active call.
2) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during an unsuccessful invocation of the Call Hold service when the response from the SS is a HOLD REJECT message.
3) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during a successful invocation of the Call Hold service when the response from the SS is a HOLD ACKNOWLEDGE message.
15.6.1.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– The UE shall have Call A-B in state U10 "Active". The call shall be of telecommunication service TS11. This state is achieved by the procedure in section 7.2.3.2 of TS 34.108.
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Call Hold Yes/No.
Method of placing an active call on hold.
Test procedure
Using suitable user action, the UE shall request that the call is placed on hold. The UE shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD REJECT message from the SS the UE shall return the call to the original call state U10 "Active". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of the call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. The SS verifies that the UE has through connected the DTCH in both directions.
Using suitable user action, the UE shall request that the call is placed on hold. The UE shall send a HOLD message and enter auxiliary state "hold request". On receipt of a HOLD ACKNOWLEDGE message from the SS the UE shall enter the state U10 "Active” with auxiliary state "Call held". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of the call, and receiving a STATUS message indicating the appropriate call state and auxiliary state.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
Make the UE to put Call A-B on hold |
||
|
2 |
–> |
HOLD |
||
|
3 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
4 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Hold request" |
|
|
5 |
<– |
HOLD REJECT |
||
|
6 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
7 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, no auxiliary state |
|
|
8 |
SS |
The DTCH is through connected in both directions. |
||
|
9 |
UE |
Make the UE to put Call A-B on hold |
||
|
10 |
–> |
HOLD |
||
|
11 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
12 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Hold request " |
|
|
13 |
<– |
HOLD ACKNOWLEDGE |
||
|
14 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
15 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
Specific Message Contents
HOLD (Step 2 and Step 10)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
xx01 1000 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
HOLD REJECT (Step 5)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1010 B |
|
Cause IE |
|
|
– Length of Cause IE contents |
2 |
|
– octet 3 |
|
|
– Extension bit |
1 B |
|
– coding standard |
11 B (GSM PLMNs) |
|
– spare |
0 B |
|
– location |
0010 B (public network serving the local user) |
|
– octet 4 |
|
|
– Extension bit |
1 B |
|
– cause value |
010 1001 B (Temporary failure) |
HOLD ACKNOWLEDGE (Step 13)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1001 B |
15.6.1.5 Test requirements
1) At step 2 and step 10 the UE shall send a HOLD message with the transaction identifier of Call A-B.
2) At step 4 and the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Hold request" and the multi party auxiliary state set to "Idle". At step 7 the UE shall send a STATUS message with the call state set to "U10 – active" and the auxiliary state IE is omitted.
3) At step 12 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Hold request" and the multi party auxiliary state set to "Idle". At step 15 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Call held" and the multi party auxiliary state set to "Idle".
15.6.2 Call completion supplementary services, Retrieve procedure
15.6.2.1 Definition
15.6.2.2 Conformance requirement
1) When the mobile subscriber that invoked the call hold service indicates that the call is to be retrieved, the network shall re establish communication and send an acknowledgement to the served mobile subscriber (see figure 2.3).
If the network received a non zero SS Screening indicator from the remote party’s mobile station the network shall send a notification to the remote party indicating that the call has been retrieved (see figure 2.4). If the network did not receive a non zero SS Screening indicator from the remote party’s mobile station it shall not send a notification.
The retrieve function is requested by sending a RETRIEVE message. This message may be sent while the auxiliary state is in the Call held state.
Upon the sending of the RETRIEVE message the auxiliary state of the initiator’s terminal would be the retrieve request state.
If the retrieve request is successful, the RETRIEVE ACKNOWLEDGE message will be returned. The initiator should not assume that call retrieval has occurred until it receives this message. The auxiliary state would then return to the Idle state.
If the retrieve request is not successful, the RETRIEVE REJECT message will be returned with an appropriate cause. The auxiliary state machine would then remain to the Call held state. The served mobile subscriber indicates to the network that communication on the interface is to be interrupted.
2) It is possible to place a call on hold in the Active state. The concept of dimensioned state space is being introduced to ensure state synchronization between the mobile station and the network. This concept suggests dimensioning the call state machine into two dimensions. In other words, there would be two states associated with each call. The first would be a 3GPP TS 24.008 call state and the second would be an auxiliary state associated with hold. Suppose the dimensioned state space is represented by two co-ordinates: one is a 3GPP TS 24.008 call state co-ordinate and the other is a hold co-ordinate. If a 3GPP TS 24.008 call state transition occurs, the former co-ordinate is updated. If a call is put on hold, the hold co-ordinate is updated. When the held call is reconnected, the hold co-ordinate is again updated.
There are four auxiliary states associated with the hold and retrieve functions:
– Idle;
– Hold request;
A request has been made for the hold function.
– Call held;
The call is held and the user information path has been reserved.
– Retrieve request;
A request has been made for the retrieve function.
Reference(s)
TS 24.083 clauses 2.1.3 and 2.1.5.
15.6.2.3 Test purpose
1) To verify the ability of a UE to retrieve a held call.
2) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during an unsuccessful retrieve procedure for a held call when the response from the SS is a RETRIEVE REJECT message.
3) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during a successful retrieve procedure for a held call when the response from the SS is a RETRIEVE ACKNOWLEDGE message.
15.6.2.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– The UE shall have Call A-B in state U10 "Active" with auxiliary state "Call held". The call shall be of telecommunication service TS11. This state is achieved by the procedure in section 7.2.3.3.1.2 of TS 34.108.
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Call Hold Yes/No.
Method of retrieving a held call.
Test procedure
Using suitable user action, the UE shall request that the held call is retrieved. The UE shall send a RETRIEVE message and enter auxiliary state "retrieve request". On receipt of a RETRIEVE REJECT message from the SS, the UE shall return the call to the original call state U10 "Active" with auxiliary state "Call held". The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of call, and receiving a STATUS message indicating the appropriate call state and auxiliary state.
Using suitable user action, the UE shall request that the held call is retrieved. The UE shall send a RETRIEVE message and enter auxiliary state "retrieve request". On receipt of a RETRIEVE ACKNOWLEDGE message from the SS, the UE shall enter the state U10 "Active”. The call state shall be verified by the SS sending a STATUS ENQUIRY message in respect of the transaction identifier of call, and receiving a STATUS message indicating the appropriate call state and auxiliary state. The SS verifies that the UE has through connected the DTCH in both directions.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
Make the UE to retrieve the held call |
||
|
2 |
–> |
RETRIEVE |
||
|
3 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
4 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Retrieve request" |
|
|
5 |
<– |
RETRIEVE REJECT |
||
|
6 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
7 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Call held" |
|
|
8 |
UE |
Make the UE to retrieve the held call |
||
|
9 |
–> |
RETRIEVE |
||
|
10 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
11 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Retrieve request" |
|
|
12 |
<– |
RETRIEVE ACKNOWLEDGE |
||
|
13 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
14 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, no auxiliary state |
|
|
15 |
SS |
The DTCH is through connected in both directions. |
||
Specific Message Contents
RETRIEVE (Step 2 and Step 9)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
xx01 1100 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
RETRIEVE REJECT (Step 5)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1110 B |
|
Cause IE |
|
|
– Length of Cause IE contents |
2 |
|
– octet 3 |
|
|
– Extension bit |
1 B |
|
– coding standard |
11 B (GSM PLMNs) |
|
– spare |
0 B |
|
– location |
0010 B (public network serving the local user) |
|
– octet 4 |
|
|
– Extension bit |
1 B |
|
– cause value |
010 1001 B (Temporary failure) |
RETRIEVE ACKNOWLEDGE (Step 12)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1101 B |
15.6.2.5 Test requirements
1) At step 2 and step 9 the UE shall send a RETRIEVE message with the transaction identifier of Call A-B.
2) At step 4 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Retrieve request" and the multi party auxiliary state set to "Idle". At step 7 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Call held" and the multi party auxiliary state set to "Idle".
3) At step 11 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Retrieve request" and the multi party auxiliary state set to "Idle". At step 14 the UE shall send a STATUS message with the call state set to "U10 – active" and the auxiliary state IE is omitted.
15.6.3 Call completion supplementary services, Alternate from one call to the other
15.6.3.1 Definition
15.6.3.2 Conformance requirement
1) If the served mobile subscriber is connected to an active call and a call on hold, he can alternate from one call to the other. This results in the previously active call being held and the previously held call becoming retrieved. This is achieved by sending a HOLD message for the active call, followed by a RETRIEVE message for the held call (see figure 2.5). These requests place the auxiliary state for the held and active calls in the retrieve request and hold request states respectively.
If this alternate procedure is successful the HOLD ACKNOWLEDGE message will be returned, followed by the RETRIEVE ACKNOWLEDGE message. The initiator should not assume that the held call is retrieved and the active call is held until it receives both these messages.
If the alternate procedure is not successful the HOLD REJECT message will be returned followed by the RETRIEVE REJECT message. This will result in the auxiliary state for the held and active calls returning to the previous states.
If the network received a non‑zero SS Screening indicator from the remote party’s mobile station the network shall send a notification towards the previously held party that the call has been retrieved (see figure 2.4) and towards the previously active party that the call has been on hold (see figure 2.2). If the network did not receive a non‑zero SS Screening indicator from the remote party’s mobile station it shall not send a notification.
2) It is possible to place a call on hold in the Active state. The concept of dimensioned state space is being introduced to ensure state synchronization between the mobile station and the network. This concept suggests dimensioning the call state machine into two dimensions. In other words, there would be two states associated with each call. The first would be a 3GPP TS 24.008 call state and the second would be an auxiliary state associated with hold. Suppose the dimensioned state space is represented by two co-ordinates: one is a 3GPP TS 24.008 call state co-ordinate and the other is a hold co-ordinate. If a 3GPP TS 24.008 call state transition occurs, the former co-ordinate is updated. If a call is put on hold, the hold co-ordinate is updated. When the held call is reconnected, the hold co-ordinate is again updated.
There are four auxiliary states associated with the hold and retrieve functions:
– Idle;
– Hold request;
A request has been made for the hold function.
– Call held;
The call is held and the user information path has been reserved.
– Retrieve request;
A request has been made for the retrieve function.
Reference(s)
TS 24.083 clauses 2.1.4 and 2.1.5.
15.6.3.3 Test purpose
1) To verify the ability of a UE to alternate between one call and the other, by placing the active call on hold, and retrieving the previously held call.
2) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during a successful alternation from one call to another when the response from the SS is a RETRIEVE ACKNOWLEDGE message.
3) To verify the ability of a UE to apply the auxiliary states for hold and retrieve correctly during an unsuccessful alternation from one call to another when the response from the SS is a RETRIEVE REJECT message.
15.6.3.4 Method of test
Initial Conditions
– System simulator:
– 1 cell, default parameters.
– User Equipment:
– The UE shall have Call A-B in state U10 "Active" with Auxiliary state "Call held" and Call A-C in state U10 "Active". Both calls shall be of telecommunication service TS11. This state is achieved by the procedure in section 7.2.3.3.1.4 of TS 34.108.
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Call Hold Yes/No.
Method of alternating between an active call and a held call.
Test procedure
Using suitable user action, the UE shall alternate between Call A-B and Call A-C. The UE shall send a HOLD message with the transaction identifier for Call A-C and enter auxiliary state "hold request", and send a RETRIEVE message with the transaction identifier for Call A-B and enter auxiliary state "retrieve request". On receipt of a HOLD ACKNOWLEDGE and RETRIEVE ACKNOWLEDGE message, the UE shall have Call A-B in state U10 "Active" and Call A-C in state U10 "Active" with auxiliary state "Call held". 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 and auxiliary state.
Using suitable user action, the UE shall alternate between Call A-B and Call A-C. The UE shall send a HOLD message with the transaction identifier for Call A-B and enter auxiliary state "hold request", and send a RETRIEVE message with the transaction identifier for Call A-C and enter auxiliary state "retrieve request". On receipt of a HOLD REJECT and RETRIEVE REJECT message, the UE shall have Call A-B in state U10 "Active" and Call A-C in state U10 "Active" with auxiliary state "Call held". 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 and auxiliary state.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
1 |
UE |
Make the UE to alternate between the active call and the held call |
||
|
2 |
–> |
HOLD |
||
|
3 |
–> |
RETRIEVE |
||
|
4 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
5 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Retrieve request" |
|
|
6 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
7 |
–> |
STATUS |
Transaction identifier of Call A-C, state U10, auxiliary state "Hold request" |
|
|
8 |
<– |
HOLD ACKNOWLEDGE |
||
|
9 |
<– |
RETRIEVE ACKNOWLEDGE |
||
|
10 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
11 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, no auxiliary state |
|
|
12 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
13 |
–> |
STATUS |
Transaction identifier of Call A-C, state U10, auxiliary state "Call held" |
|
|
14 |
UE |
Make the UE to alternate between the active call and the held call |
||
|
15 |
–> |
HOLD |
||
|
16 |
–> |
RETRIEVE |
||
|
17 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
18 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, auxiliary state "Hold request" |
|
|
19 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
20 |
–> |
STATUS |
Transaction identifier of Call A-C, state U10, auxiliary state "Retrieve request" |
|
|
21 |
<– |
HOLD REJECT |
||
|
22 |
<– |
RETRIEVE REJECT |
||
|
23 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
24 |
–> |
STATUS |
Transaction identifier of Call A-B, state U10, no auxiliary state |
|
|
25 |
<– |
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
26 |
–> |
STATUS |
Transaction identifier of Call A-C, state U10, auxiliary state "Call held" |
|
Specific Message Contents
HOLD (Step 2)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-C |
|
Message type |
xx01 1000 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
RETRIEVE (Step 3)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
xx01 1100 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
HOLD ACKNOWLEDGE (Step 8)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-C |
|
Message type |
0001 1001 B |
RETRIEVE ACKNOWLEDGE (Step 9)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1101 B |
HOLD (Step 15)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
xx01 1000 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
RETRIEVE (Step 16)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-C |
|
Message type |
xx01 1100 B (bits 7 and 8 are not checked, these bits are reserved for the send sequence number) |
HOLD REJECT (Step 21)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-B |
|
Message type |
0001 1010 B |
|
Cause IE |
|
|
– Length of Cause IE contents |
2 |
|
– octet 3 |
|
|
– Extension bit |
1 B |
|
– coding standard |
11 B (GSM PLMNs) |
|
– spare |
0 B |
|
– location |
0010 B (public network serving the local user) |
|
– octet 4 |
|
|
– Extension bit |
1 B |
|
– cause value |
010 1001 B (Temporary failure) |
RETRIEVE REJECT (Step 22)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Transaction identifier |
The same value that has been used in Call A-C |
|
Message type |
0001 1110 B |
|
Cause IE |
|
|
– Length of Cause IE contents |
2 |
|
– octet 3 |
|
|
– Extension bit |
1 B |
|
– coding standard |
11 B (GSM PLMNs) |
|
– spare |
0 B |
|
– location |
0010 B (public network serving the local user) |
|
– octet 4 |
|
|
– Extension bit |
1 B |
|
– cause value |
010 1001 B (Temporary failure) |
15.6.3.5 Test requirements
1) At step 2 the UE shall send a HOLD message with the transaction identifier of Call A-C. At step 3 the UE shall send a RETRIEVE message with the transaction identifier of Call A-B. At step 15 the UE shall send a HOLD message with the transaction identifier of Call A-B. At step 16 the UE shall send a RETRIEVE message with the transaction identifier of Call A-C.
2) At step 5 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Retrieve request" and the multi party auxiliary state set to "Idle". At step 7 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Hold request" and the multi party auxiliary state set to "Idle". At step 11 the UE shall send a STATUS message with the call state set to "U10 – active" and the auxiliary state IE is omitted. At step 13 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Call held" and the multi party auxiliary state set to "Idle".
3) At step 18 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Hold request" and the multi party auxiliary state set to "Idle". At step 20 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Retrieve request" and the multi party auxiliary state set to "Idle". At step 24 the UE shall send a STATUS message with the call state set to "U10 – active" and the auxiliary state IE is omitted. At step 26 the UE shall send a STATUS message with the call state set to "U10 – active", the hold auxiliary state set to "Call held" and the multi party auxiliary state set to "Idle".