15.10 Explicit Call Transfer (ECT)
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
15.10.1 Explicit Call Transfer invocation, successful case, both calls active, clearing using DISCONNECT
15.10.1.1 Definition
15.10.1.2 Conformance requirement
The Mobile Station (MS) invokes the service by sending a FACILITY message to the network containing the ECT request (ECT request). This ECT request indicates to the network that the mobile subscriber wishes the two calls to be connected together. The MS shall not change the basic call state or the auxiliary state of either call when sending ECT request.
the call control entity of the network shall initiate clearing by: sending a DISCONNECT message; and entering the "disconnect indication" state. The DISCONNECT message is a local invitation to clear the call.
References:
3GPP TS 24.091 sub clauses 4.1 and 4.2.
3GPP TS 24.008 sub clause 5.4.4
15.10.1.3 Test purpose
To test that the UE 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.
15.10.1.4 Method of test
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Explicit Call Transfer service Yes/No.
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" with no auxiliary state as specified in TS 34.108 clause 7.2.3.3.1.4.
The CM Service Type used by the UE upon initiation of Call A-C shall be “MO Call or packet mode connection establishment”.
Test Procedure
The UE is triggered to invoke an explicit call transfer between the two calls. The UE 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 UE shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the UE 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 |
|
|
UE |
SS |
|||
|
1 |
SS |
UE is triggered to perform an explicit call transfer |
||
|
2 |
|
FACILITY |
TI for Call A-B or Call A-C |
|
|
3 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
4 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
5 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
6 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
7 |
|
DISCONNECT |
Transaction identifier of Call A-B (explicitCT operation Return result) |
|
|
8 |
|
RELEASE |
Transaction identifier of Call A-B |
|
|
9 |
|
DISCONNECT |
Transaction identifier of Call A-C |
|
|
10 |
|
RELEASE |
Transaction identifier of Call A-C |
|
|
11 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
12 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
|
13 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
14 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
15 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
16 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
Specific message contents
FACILITY with Invoke component (Step 2)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Facility |
|
|
Operation Code |
ExplicitCT |
STATUS (Step 4)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
|
Auxiliary states |
Call held |
STATUS (Step 6)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
DISCONNECT with Return result component with operation code (Step 7)
|
Information Element |
Value/remark |
|---|---|
|
Invoke ID |
the same Invoke ID as in the FACILITY in Step 2 |
|
Operation Code |
explicitCT |
RELEASE COMPLETE (Step 14)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
RELEASE COMPLETE (Step 16)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
15.10.1.5 Test requirement
In Step 2, UE sends the FACILITY message with correct Invoke component.
In Step 4, UE sends the STATUS message with the correct Call state and Auxiliary state.
In Step 6, UE sends the STATUS message with the correct Call state.
In Step 14, UE sends the RELEASE COMPLETE message with the correct Cause.
In Step 16, UE sends the RELEASE COMPLETE message with the correct Cause.
15.10.2 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE
15.10.2.1 Definition
15.10.2.2 Conformance requirement
The Mobile Station (MS) invokes the service by sending a FACILITY message to the network containing the ECT request (ECT request). This ECT request indicates to the network that the mobile subscriber wishes the two calls to be connected together. The MS shall not change the basic call state or the auxiliary state of either call when sending ECT request.
The call control entity of the mobile station in any state except the "null" state and the "release request" state, shall, upon receipt of a RELEASE message: stop all running call control timers; send a RELEASE COMPLETE message; release the MM connection; and return to the "null" state.
3GPP TS 24.091 subclauses 4.1 and 4.2.
3GPP TS 24.008 sub clause 5.4.3.3
15.10.2.3 Test purpose
To test that the UE 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.
15.10.2.4 Method of test
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Explicit Call Transfer service Yes/No.
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" with no auxiliary state as specified in TS 34.108 clause 7.2.3.3.1.4.
The CM Service Type used by the UE upon initiation of Call A-C shall be “MO Call or packet mode connection establishment”.
Test Procedure
The UE is triggered to invoke an explicit call transfer between the two calls. The UE 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 UE 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 |
|
|
UE |
SS |
|||
|
1 |
SS |
The UE is triggered to perform an explicit call transfer |
||
|
2 |
|
FACILITY |
TI for Call A-B or Call A-C |
|
|
3 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
4 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
5 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
6 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
7 |
|
RELEASE |
Transaction identifier of Call A-B |
|
|
8 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
9 |
|
RELEASE |
Transaction identifier of Call A-C |
|
|
10 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
|
11 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
12 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
13 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
14 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
Specific message contents:
FACILITY with Invoke component (Step 2)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Facility |
|
|
Operation Code |
ExplicitCT |
STATUS (Step 4)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
|
Auxiliary states |
Call held |
STATUS (Step 6)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
RELEASE COMPLETE (Step 12)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
RELEASE COMPLETE (Step 14)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
15.10.2.5 Test requirement
In Step 2, UE sends the FACILITY message with correct Invoke component.
In Step 4, UE sends the STATUS message with the correct Call state and Auxiliary state
In Step 6, UE sends the STATUS message with the correct Call state.
In Step 12, UE sends the RELEASE COMPLETE message with the correct Cause
In Step 14, UE sends the RELEASE COMPLETE message with the correct Cause
15.10.3 Explicit Call Transfer invocation, successful case, both calls active, clearing using RELEASE COMPLETE
15.10.3.1 Definition
15.10.3.2 Conformance requirements
The Mobile Station (MS) invokes the service by sending a FACILITY message to the network containing the ECT request (ECT request). This ECT request indicates to the network that the mobile subscriber wishes the two calls to be connected together. The MS shall not change the basic call state or the auxiliary state of either call when sending ECT request.
A call control entity of the network in any call control state shall, upon receipt of a RELEASE COMPLETE message from its peer entity in the mobile station: stop all running call control timers; release the MM connection; and return to the "null" state.
3GPP TS 24.091 subclauses 4.1 and 4.2.
3GPP TS 24.008 sub clause 5.4.3.4
15.10.3.3 Test purpose
To test that the UE 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.
15.10.3.4 Method of test
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Explicit Call Transfer service Yes/No.
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" with no auxiliary state as specified in TS 34.108 clause 7.2.3.3.1.4.
The CM Service Type used by the UE upon initiation of Call A-C shall be “MO Call or packet mode connection establishment”.
Test Procedure
The UE is triggered to invoke an explicit call transfer between the two calls. The UE 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 UE 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 |
|
|
UE |
SS |
|||
|
1 |
SS |
UE is triggered to perform an explicit call transfer |
||
|
2 |
|
FACILITY |
TI for Call A-B or Call A-C |
|
|
3 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B(explicitCT operation Return result) |
|
|
4 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
5 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
6 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
7 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
8 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
|
9 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
10 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
11 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
12 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
Specific message contents:
FACILITY with Invoke component (Step 2)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Facility |
|
|
Operation Code |
ExplicitCT |
STATUS (Step 4)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
|
Auxiliary states |
Call held |
STATUS (Step 6)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
RELEASE COMPLETE with Return result component with operation code (Step 7)
|
Information Element |
Value/remark |
|---|---|
|
Invoke ID |
the same Invoke ID as in the FACILITY in Step 2 |
|
Operation Code |
explicitCT |
RELEASE COMPLETE (Step 10)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
RELEASE COMPLETE (Step 12)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
15.10.3.5 Test Requirements
In Step 2, UE sends the FACILITY message with correct Invoke component.
In Step 4, UE sends the STATUS message with the correct Call state and Auxiliary state
In Step 6, UE sends the STATUS message with the correct Call state.
In Step 10, UE sends the RELEASE COMPLETE message with the correct Cause
In Step 12, UE sends the RELEASE COMPLETE message with the correct Cause
15.10.4 Explicit Call Transfer invocation, successful case, second call alerting
15.10.4.1 Definition
15.10.4.2 Conformance requirement
The Mobile Station (MS) invokes the service by sending a FACILITY message to the network containing the ECT request (ECT request). This ECT request indicates to the network that the mobile subscriber wishes the two calls to be connected together. The MS shall not change the basic call state or the auxiliary state of either call when sending ECT request.
The call control entity of the network shall initiate clearing by: sending a DISCONNECT message; and entering the "disconnect indication" state. The DISCONNECT message is a local invitation to clear the call.
3GPP TS 24.091 subclauses 4.1 and 4.2.
3GPP TS 24.008 subclause 5.4.4
15.10.4.3 Test purpose
To test that the UE 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
15.10.4.4 Method of test
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Explicit Call Transfer service Yes/No.
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 U4 "Call Delivered" with no auxiliary state as specified in TS 34.108 clause 7.2.3.3.1.3.
The CM Service Type used by the UE upon initiation of Call A-C shall be “MO Call or packet mode connection establishment”.
Test Procedure
The UE is triggered to invoke an explicit call transfer between the two calls. The UE 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 UE shall respond with a RELEASE message for each call. On receipt of a RELEASE COMPLETE message for each call, the UE 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 |
|
|
UE |
SS |
|||
|
1 |
SS |
The UE is triggered to perform an explicit call transfer |
||
|
2 |
|
FACILITY |
TI for Call A-B or Call A-C |
|
|
3 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B (explicitCT operation Return result) |
|
|
4 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
5 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
6 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
7 |
|
DISCONNECT |
Transaction identifier of Call A-B |
|
|
8 |
|
RELEASE |
Transaction identifier of Call A-B |
|
|
9 |
|
DISCONNECT |
Transaction identifier of Call A-C |
|
|
10 |
|
RELEASE |
Transaction identifier of Call A-C |
|
|
11 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
12 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
|
13 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
14 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-B |
|
|
15 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
16 |
|
RELEASE COMPLETE |
Transaction identifier of Call A-C |
|
Specific message contents:
FACILITY with Invoke component (Step 2)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Facility |
|
|
Operation Code |
ExplicitCT |
STATUS (Step 4)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
|
Auxiliary states |
Call held |
STATUS (Step 6)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U4 – call delivered |
DISCONNECT with Return result component with operation code (Step 7)
|
Information Element |
Value/remark |
|---|---|
|
Invoke ID |
the same Invoke ID as in the FACILITY in Step 2 |
|
Operation Code |
explicitCT |
RELEASE COMPLETE (Step 14)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
RELEASE COMPLETE (Step 16)
|
Information Element |
Value/remark |
|---|---|
|
Release complete |
|
|
Cause |
Invalid transaction identifier value |
15.10.4.5 Test requirement
In Step 2, UE sends the FACILITY message with correct Invoke component.
In Step 4, UE sends the STATUS message with the correct Call state and Auxiliary state.
In Step 6, UE sends the STATUS message with the correct Call state.
In Step 14, UE sends the RELEASE COMPLETE message with the correct Cause.
In Step 16, UE sends the RELEASE COMPLETE message with the correct Cause.
15.10.5 Explicit Call Transfer invocation, expiry of T(ECT)
15.10.5.1 Definition
15.10.5.2 Conformance requirement
The Mobile Station (MS) invokes the service by sending a FACILITY message to the network containing the ECT request (ECT request). This ECT request indicates to the network that the mobile subscriber wishes the two calls to be connected together. The MS shall not change the basic call state or the auxiliary state of either call when sending ECT request.
During the ECT operation the MS shall run a timer TECT. This timer is started when the operation is sent, and stopped when a response is received from the network. If this timer expires the MS shall assume that the operation has failed, locally release the invokeID, and may re‑attempt the operation or inform the user of the failure.
3GPP TS 24.091 subclauses 4.1 and 4.2.
3GPP TS 24.080 subclause 4.2.
15.10.5.3 Test purpose
To test that the UE 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
Related ICS/IXIT Statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of Explicit Call Transfer service Yes/No.
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" with no auxiliary state as specified in TS 34.108 clause 7.2.3.3.1.4.
The CM Service Type used by the UE upon initiation of Call A-C shall be “MO Call or packet mode connection establishment”.
15.10.5.4 Test Procedure
The UE is triggered to invoke an explicit call transfer between the two calls. The UE 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 UE 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 |
|
|
UE |
SS |
|||
|
1 |
SS |
The UE is triggered to perform an explicit call transfer |
||
|
2 |
|
FACILITY |
TI for Call A-B or Call A-C |
|
|
3 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
4 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
5 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
6 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
7 |
SS |
Wait 15 s from receiving FACILITY message |
||
|
Take this branch if no message is received within 15 s |
||||
|
A7 |
The UE provides indication of failure to the user |
|||
|
A8 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
A9 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
A10 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
A11 |
|
STATUS |
Transaction identifier of Call A-C |
|
|
Take this branch if a message is received within 15 s |
||||
|
B8 |
|
FACILITY |
Same as Step 2. Message shall not be received less than 5 s after the first FACILITY message |
|
|
B9 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-B |
|
|
B10 |
|
STATUS |
Transaction identifier of Call A-B |
|
|
B11 |
|
STATUS ENQUIRY |
Transaction identifier of Call A-C |
|
|
B12 |
|
STATUS |
Transaction identifier of Call A-C |
|
Specific message contents:
FACILITY with Invoke component (Step 2, Step B8)
|
Information Element |
Value/remark |
|---|---|
|
Protocol discriminator |
0011 B (call control; call related SS messages) |
|
Facility |
|
|
Operation Code |
ExplicitCT |
STATUS (Step 4, Step A9, Step B10)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10- active |
|
Auxiliary states |
Call held |
STATUS (Step 6, Step A11, Step B12)
|
Information Element |
Value/remark |
|---|---|
|
Status |
|
|
Cause |
Normal event |
|
Call State |
U10 – active |
15.10.5.5 Test Requirements
In Step 2, UE sends the FACILITY message with correct Invoke component.
In Step 4, UE sends the STATUS message with the correct Call state and Auxiliary state
In Step 6, UE sends the STATUS message with the correct Call state.
In Step A9, UE sends the STATUS message with the correct Call state and Auxiliary state
In Step A11, UE sends the STATUS message with the correct Call state.
In Step B10, UE sends the STATUS message with the correct Call state and Auxiliary state
In Step B12, UE sends the STATUS message with the correct Call state.