hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 resp... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 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 ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7 Multi-party supplementary services | General
In this subclause, subscriber A is the UE under test, and subscribers B, C, D and E are distant parties in the calls used in the test cases. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.1 Multi-party supplementary services, Beginning the MultiParty service, successful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.1.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.1.2 Conformance requirement | 1) The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B.
The mobile station invokes the service by sending a FACILITY message to the network containing the BuildMPTY request. This BuildMPTY request indicates to the network that the mobile subscriber wishes all hi... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.1.3 Test purpose | 1) To verify the ability of a UE to start the MultiParty service when it has an active call and a held call, and reacts correctly to a response from the SS indicating success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly during a successful beginning of the MultiParty service. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.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" 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.1.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "buildMPTY".
2) At step 4 the UE shall send a STATUS message with the call state set to "U10 - active", the hold auxili... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.2 Multi-party supplementary services, Beginning the MultiParty service, unsuccessful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.2.2 Conformance requirement | 1) The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B.
The mobile station invokes the service by sending a FACILITY message to the network containing the BuildMPTY request. This BuildMPTY request indicates to the network that the mobile subscriber wishes all hi... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.2.3 Test purpose | 1) To verify the ability of a UE to start the MultiParty service when it has an active call and a held call, and reacts correctly to the response from the SS indicating no success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly during an unsuccessful beginning of the MultiParty servic... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.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" 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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.2.5 Test requirements | 1) At step 2and step 13 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "buildMPTY".
2) At step 4 the UE shall send a STATUS message with the call state set to "U10 - active", the ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.3 Multi-party supplementary services, Beginning the MultiParty service, expiry of timer T(BuildMPTY) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.3.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.3.2 Conformance requirement | 1) The served mobile subscriber A may initiate an active MultiParty call from an active call C and a held call B.
The mobile station invokes the service by sending a FACILITY message to the network containing the BuildMPTY request. This BuildMPTY request indicates to the network that the mobile subscriber wishes all hi... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.3.3 Test purpose | 1) To verify the ability of a UE to start the MultiParty service when it has an active call and a held call.
2) To verify the ability of a UE to react correctly on expiry of timer T(BuildMPTY).
3) To verify the ability of a UE to apply the auxiliary states for MPTY correctly on expiry of timer T(BuildMPTY). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.3.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "buildMPTY". At step 4 the UE shall send a STATUS message with the call state set to "U10 - active", the hold auxiliary... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4 Multi-party, Managing an active MultiParty call, Put the MultiParty call on hold, successful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4.2 Conformance requirement | 1) Put the MultiParty call on hold
This is achieved by sending a FACILITY message to the network with any transaction identifier corresponding to a call within the MultiParty call. This requests the network to place the mobile subscriber's connection to the MultiParty call on hold. The network confirms with another mes... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4.3 Test purpose | 1) To verify the ability of a UE to put an active MultiParty call on hold and react correctly to a response from the SS indicating success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly after an active MultiParty call is put on hold successfully. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of telecommunication service TS11. This state is ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.4.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "holdMPTY".
2) At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 - active", the h... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5 Multi-party, Managing an active MultiParty call, Put the MultiParty call on hold, unsuccessful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5.2 Conformance requirement | 1) Put the MultiParty call on hold
This is achieved by sending a FACILITY message to the network with any transaction identifier corresponding to a call within the MultiParty call. This requests the network to place the mobile subscriber's connection to the MultiParty call on hold. The network confirms with another mes... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5.3 Test purpose | 1) To verify the ability of a UE to put an active MultiParty call on hold and react correctly to a response from the SS indicating no success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly during an unsuccessful attempt to put an active MultiParty call on hold when the response from ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of telecommunication service TS11. This state is ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.5.5 Test requirements | 1) At step 2 and step 13 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "holdMPTY".
2) At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 - ac... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6 Multi-party, Managing an active MultiParty call, Put the MultiParty call on hold, expiry of timer T(HoldMPTY) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6.2 Conformance requirement | 1) Put the MultiParty call on hold
This is achieved by sending a FACILITY message to the network with any transaction identifier corresponding to a call within the MultiParty call. This requests the network to place the mobile subscriber's connection to the MultiParty call on hold. The network confirms with another mes... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6.3 Test purpose | 1) To verify the ability of a UE to put an active MultiParty call on hold.
2) To verify the ability of a UE to react correctly on expiry of timer T(HoldMPTY).
3) To verify the ability of a UE to apply the auxiliary states for MPTY correctly on expiry of timer T(HoldMPTY). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of telecommunication service TS11. This state is ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.6.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "holdMPTY". At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 - active", the hold... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7 Multi-party, Managing an active MultiParty call, Create a private communication with one of the remote parties, successful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7.1 Definition | The operation of splitting a call from the active MPTY call is successfully accepted by the network. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7.2 Conformance requirement | To create a private communication with one of the remote parties, the served mobile will send a SplitMPTY within a FACILITY message to the network. Then the network returns a Return Result within a FACILITY message to accept the splitting operation. The call state with the prior remote parties are changed accordingly.
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7.3 Test purpose | To test that the UE correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating success. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.7.5 Test requirements | At step 9 and 11, the UE shall have Call A-B entering state U10 with no auxiliary state, and Call A-C entering state U10 with auxiliary state "Call Held". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8 Multi-party, Managing an active MultiParty call, Create a private communication with one of the remote parties, unsuccessful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8.1 Definition | The operation of splitting a call from the active MPTY call is rejected by the network. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8.2 Conformance requirement | To create a private communication with one of the remote parties, the served mobile will send a SplitMPTY within a FACILITY message to the network. Then the network returns a Return Error or Reject within a FACILITY message to reject the splitting operation. The call states with the prior remote parties are returned to... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8.3 Test purpose | To test that the UE correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating success. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.8.5 Test requirements | At step 9 and step 11, the UE shall have Call A-B entering state U10 with auxiliary state “Call in MPTY”, and Call A-C entering state U10 with auxiliary state "Call in MPTY". At step 20 and step 22, the UE shall have Call A-B entering state U10 with auxiliary state “Call in MPTY”, and Call A-C entering state U10 with a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9 Multi-party, Managing an active MultiParty call, Create a private communication with one of the remote parties, expiry of timer T(SplitMPTY) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9.1 Definition | The operation of splitting a call from the active MPTY call is not responded by the network until the timer T(SplitMPTY) expires. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9.2 Conformance requirement | To create a private communication with one of the remote parties, the served mobile will send a SplitMPTY within a FACILITY message to the network. Then the network does not response with any message until the timer T(SplitMPTY) expires. The call states with the prior remote parties are returned to their initial states... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9.3 Test purpose | To test that the UE correctly splits an active MultiParty call, and on expiry of T(SplitMPTY) returns the call to the auxiliary state "Call in MPTY". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.9.5 Test requirements | Branch A, at step A9 and step A11 the UE shall have Call A-B entering state U10 with auxiliary state "Call in MPTY", and Call A-C entering state U10 with auxiliary state "Call in MPTY".
Branch B, at step B10 and step B12 the UE shall have Call A-B entering state U10 with auxiliary state "Split request", and Call A-C en... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10 Multi-party supplementary services, Terminate the entire MultiParty call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10.1 Definition | The operation of terminating the entire MPTY call is performed by the UE sending a DISCONNECT message with each TI corresponding to the remote parties consequently. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10.2 Conformance requirement | The MultiParty call is terminated by disconnecting all individual parties by initiation of call clearing as defined in 3GPP TS 24.008 with each transaction identifier corresponding to the remote parties.
Reference(s)
3GPP TS 24.084 subclause 1.2.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10.3 Test purpose | To test that the UE correctly terminates an entire MultiParty call by implementing the call clearance procedure for each call in turn. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.10.5 Test requirements | At step 9 and step 11, the UE shall return a RELEASE COMPLETE message with cause #81 “invalid transaction identifier value” as the response of the STATUS ENQUIRY message sent by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11 Multi-party supplementary services, Explicitly disconnect a remote party | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11.1 Definition | The operation of terminating a remote party from the MPTY call is performed by the UE sending a DISCONNECT message with the corresponding TI of the remote party. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11.2 Conformance requirement | Any remote party may be individually disconnected by initiation of call clearing as defined in 3GPP TS 24.008 with the same transaction identifier corresponding to that party.
Reference(s)
3GPP TS 24.084 subclause 1.2.1.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11.3 Test purpose | To test that the UE correctly disconnects a single remote party by implementing the call clearance procedure for that party. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.11.5 Test requirements | At step 6, the UE shall return a RELEASE COMPLETE message with cause #81 “invalid transaction identifier value” as the response of the STATUS ENQUIRY message using TI of Call A-B.
At step 8, the UE shall return a STATUS message with call state U10 as the response of the STATUS ENQUIRY message using TI of Call A-C, and ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12 Multi-party supplementary services, Release from the MultiParty call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12.1 Definition | One of the remote parties release from the MPTY call by sending a DISCONNECT message with the corresponding TI. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12.2 Conformance requirement | Any remote party may be individually disconnected by initiation of call clearing as defined in 3GPP TS 24.008 with the same transaction identifier corresponding to that party.
Reference(s)
3GPP TS 24.084 subclause 1.2.1.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12.3 Test purpose | To test that the UE responds correctly to a call clearance from one of the remote parties. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (Call A-B and Call A-C) active. Both call states shall be U10 "Active" with auxiliary state "Call in MPTY". The call shall be of a basic service supported by the UE and releva... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.12.5 Test requirements | At step 5, the UE shall return a RELEASE COMPLETE message with cause #81 “invalid transaction identifier value” as the response of the STATUS ENQUIRY message using TI of Call A-B.
At step 7, the UE shall return a STATUS message with call state U10 as the response of the STATUS ENQUIRY message using TI of Call A-C, and ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13 Multi-party supplementary services, Retrieve the held MultiParty call, successful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13.2 Conformance requirement | 1) Retrieve the held MultiParty call
To retrieve the held MultiParty call, a FACILITY message is sent to the network with a transaction identifier corresponding to any call in the MPTY. The network confirms the retrieval with another message containing the same transaction identifier (see figure 1.6).
2) In the call ho... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13.3 Test purpose | 1) To verify the ability of a UE to retrieve a held MultiParty call and react correctly to a response from the SS indicating success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly after a held MultiParty call is retrieved successfully. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held". The call shall be of telecommunication service TS11. This ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.13.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "retrieveMPTY".
2) At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 - active", t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14 Multi-party supplementary services, Retrieve the held MultiParty call, unsuccessful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14.2 Conformance requirement | 1) Retrieve the held MultiParty call
To retrieve the held MultiParty call, a FACILITY message is sent to the network with a transaction identifier corresponding to any call in the MPTY. The network confirms the retrieval with another message containing the same transaction identifier (see figure 1.6).
2) In the call ho... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14.3 Test purpose | 1) To verify the ability of a UE to retrieve a held MultiParty call and react correctly to a response from the SS indicating no success.
2) To verify the ability of a UE to apply the auxiliary states for MPTY correctly during an unsuccessful attempt to retrieve a held MultiParty call when the response from the SS is a ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held". The call shall be of telecommunication service TS11. This ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.14.5 Test requirements | 1) At step 2 and step 13 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "retrieveMPTY".
2) At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15 Multi-party supplementary services, Retrieve the held MultiParty call, expiry of timer T(RetrieveMPTY) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15.2 Conformance requirement | 1) Retrieve the held MultiParty call
To retrieve the held MultiParty call, a FACILITY message is sent to the network with a transaction identifier corresponding to any call in the MPTY. The network confirms the retrieval with another message containing the same transaction identifier (see figure 1.6).
During the Retrie... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15.3 Test purpose | 1) To verify the ability of a UE to retrieve a held MultiParty call.
2) To verify the ability of a UE to react correctly on expiry of timer T(RetrieveMPTY).
3) To verify the ability of a UE to apply the auxiliary states for MPTY correctly on expiry of timer T(RetrieveMPTY). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held". The call shall be of telecommunication service TS11. This ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.15.5 Test requirements | 1) At step 2 the UE shall send a FACILITY message with the transaction identifier of either Call A-B or Call A-C, the Facility IE shall contain an invoke component wherein the operation code is set to "retrieveMPTY". At step 4 and step 6 the UE shall send a STATUS message with the call state set to "U10 - active", the ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16 Multi-party supplementary services, Initiate a new call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16.1 Definition | The initiation of a new call with a held MPTY call is achieved by a normal call set-up procedure. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16.2 Conformance requirement | To initiate a new call as there is already a held MultiParty call, the UE performs a normal MO call set-up procedure.
Reference(s)
3GPP TS 24.084 subclause 1.3.1.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16.3 Test purpose | To test that the UE can set up a new outgoing call with a held MultiParty call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a held MultiParty call to two destinations (Call A-B and Call A-C). Both call states shall be U10 "Active" with auxiliary state "Call in MPTY, call held". The call shall be of a basic service supported by the UE a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.16.5 Test requirements | At step 9, step 11 and step 13, the UE shall have the Call A-B entering state U10 with auxiliary state "Call in MPTY, call held", Call A-C entering state U10 with auxiliary state "Call in MPTY, call held" and Call A-D entering state U10 with no auxiliary state. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.