hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17 Multi-party supplementary services, Process a call waiting request | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17.1 Definition | The MultiParty call is put on hold before the Call Waiting request is answered. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17.2 Conformance requirement | To answer the Call Waiting request, the UE places the existing MultiParty call on hold by sending a FACILITY message.
Reference(s)
3GPP TS 24.084 subclause 1.3.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17.3 Test purpose | To test that the UE can correctly process a Call Waiting request with a held MultiParty call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17.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 calls states shall be U10 "Active" with auxiliary state "Call in MPTY". The UE shall also have a Call A-D in state U7 "Call received". The... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.17.5 Test requirements | At step 7, step 9 and step 11, 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. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.18 Multi-party supplementary services, Terminate the held MultiParty call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.18.1 Definition | The operation of terminating the held 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.18.2 Conformance requirement | The held 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.3.1.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.18.3 Test purpose | To test that the UE correctly terminates a held MultiParty call by initiating call clearance for each party in turn. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.18.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.18.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.19 Multi-party, Managing a single call and a MultiParty call, Disconnect the single call, single call active | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.19.1 Definition | The operation of terminating the active single call besides a held MPTY call is performed by the UE sending a DISCONNECT message with the corresponding TI. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.19.2 Conformance requirement | The active single call, besides the held MultiParty call, is terminated by initiation of call clearing as defined in 3GPP TS 24.008 with the transaction identifier corresponding to the remote party.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.19.3 Test purpose | To test that the UE correctly clears the single call when the single call is active and the MultiParty call is held. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.19.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY, call held". The UE shall have in addition a single call (A-D) in state U10 "Active" with no auxili... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.19.5 Test requirements | At step A2, step A4 and step A6, or step B4, step B6 and step B8, the UE shall have the Call A-B entering state U10 with auxility 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 U0 (return a RELEASE COMPLETE message with cause #81 “... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20 Multi-party, Managing a single call and a MultiParty call, Disconnect the single call, single call held | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20.1 Definition | The operation of terminating the held single call besides an active MPTY call is performed by the UE sending a DISCONNECT message with the corresponding TI. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20.2 Conformance requirement | The held single call, besides an active MultiParty call, is terminated by initiation of call clearing as defined in 3GPP TS 24.008 with the transaction identifier corresponding to the remote party.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20.3 Test purpose | To test that the UE correctly clears the single call when the single call is held and the MultiParty call is active. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Cal... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.20.5 Test requirements | At step 6, step 8 and step 10, the UE shall have the Call A-B entering state U10 with auxility state "Call in MPTY", Call A-C entering state U10 with auxiliary state "Call in MPTY" and Call A-D entering State U0 (return a RELEASE COMPLETE message with cause #81 “invalid transaction identifier value” as the response of ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21 Clear all parties of held MultiParty call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21.1 Definition | The operation of terminating the entire held MPTY call is performed by the UE sending the DISCONNECT message with the corresponding TI of all remote parties consequently. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21.2 Conformance requirement | The held MultiParty call is terminated by initiation of call clearing as defined in 3GPP TS 24.008 with the transaction identifiers corresponding to the remote parties.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21.3 Test purpose | To test that the UE correctly clears the MultiParty call by clearing all remote parties to a held MultiParty call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21.4 Method of test | Initial conditions
• System Simulator:
- 1 cell, default parameters.
• User Equipment:
- The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY, Call held". The UE shall have in addition a single call (A-D) in state U10 "Active" with no auxili... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.21.5 Test requirements | At step 9, step 11 and step 13, 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 or A-C sent by the SS, and have Call A-D entering state U10 with no auxiliary state. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22 Clear all parties of active MultiParty call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22.1 Definition | The operation of terminating the entire active MPTY call is performed by the UE sending the DISCONNECT message with the corresponding TI of all remote parties consequently. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22.2 Conformance requirement | The active MultiParty call is terminated by initiation of call clearing as defined in 3GPP TS 24.008 with the transaction identifiers for all the remote parties.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22.3 Test purpose | To test that the UE correctly clears the MultiParty call by clearing all remote parties to an active MultiParty call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Cal... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.22.5 Test requirements | At step A10, step A12 and step A14, or step B12, step B14 and step B16, 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 or A-C sent by the SS, and have Call A-D entering state U10 with auxiliary state... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23 Multi-party supplementary services, Disconnect all calls | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23.1 Definition | The operation of terminating all calls is performed by the UE sending the DISCONNECT message with the corresponding TI of all remote parties consequently. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23.2 Conformance requirement | All calls are terminated by initiation of call clearing as defined in 3GPP TS 24.008 with the transaction identifiers for all the remote parties.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23.3 Test purpose | To test the UE correctly clears all calls, by clearing in turn each connected party. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23.4 Method of test | Initial conditions
• System Simulator:
• 1 cell, default parameters.
• User Equipment:
• The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Cal... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.23.5 Test requirements | At step 12, step 14 and step 16, 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, A-C or A-D sent by the SS. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24 Multi-party supplementary services, Add the single call to the MPTY, successful case | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24.1 Definition | The operation of adding a single held call into the active MPTY call is performed by the UE sending the FACILITY message with the TI of any remote party, and successfully accepted the network. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24.2 Conformance requirement | The UE may request the connection of all calls, held and active, into an active MultiParty call at any time by sending a FACILITY message with the transaction identifier corresponding to any remote party and containing the BuildMPTY invoke component.
Reference(s)
3GPP TS 24.084 subclause 1.4.1.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24.3 Test purpose | To test that the UE correctly adds a single held call to an active MultiParty call, and reacts correctly to a response from the SS indicating success. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24.4 Method of test | Initial conditions
- System Simulator:- 1 cell, default parameters.
- User Equipment:
- The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Call... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.24.5 Test requirements | At step 4, step 6 and step 8, the UE shall have Call A-B and A-C entering state U10 with auxiliary state "Call in MPTY", and have Call A-D entering state U10 with auxiliary state "MPTY request, Call held".
At step 11, step 13 and step 15, the UE shall have Call A-B, A-C or A-D all entering state U10 with auxiliary stat... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25 Multi-party supplementary services, Add the single call to the MPTY, maximum number of participants exceeded | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25.1 Definition | The operation of adding a single held call into the active MPTY call is performed by the UE sending the FACILITY message with the TI of any remote party, but rejected by the network with error as the maximum number of remote parties has already been reached. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25.2 Conformance requirement | The UE may request the connection of all calls, held and active, into an active MultiParty call at any time by sending a FACILITY message with the transaction identifier corresponding to any remote party and containing the BuildMPTY invoke component.
If the request is unsuccessful e.g. because the maximum number of rem... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25.3 Test purpose | To test that the UE correctly adds a single held call to an active MultiParty call, and reacts correctly to a response from the SS indicating maximum number of participants exceeded. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25.4 Method of test | Initial conditions
• System Simulator:
• 1 cell, default parameters.
• User Equipment:
• The UE shall have a MultiParty call to three destinations (A-B, A-C and A-D) all in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-E) in state U10 "Active" with auxiliary stat... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.25.5 Test requirements | At step 4, step 6, step 8 and step 10, the UE shall have Call A-B, A-C and A-D all entering state U10 with auxiliary state "Call in MPTY", and have Call A-E entering state U10 with auxiliary state "MPTY request, Call Held".
At step 13, step 15, step 17 and step 19, the UE shall have Call A-B, A-C and A-D all entering s... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26 Multi-party supplementary services, Alternate between the MPTY call and the single call | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26.1 Definition | The operation of alternating between a single call and a MPTY call is successfully accepted by the network. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26.2 Conformance requirement | The UE may request to alternate between a single held call and a active MPTY call is performed by the UE sending the FACILITY message with HoldMPTY component and a RETRIEVE message with the corresponding TI, then the network successfully accept the hold and retrieve operations.
The UE may request to alternate between a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26.3 Test purpose | To test that the UE correctly alternates between the single call and the MultiParty call, by proper use of the hold and retrieve procedures. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26.4 Method of test | • Initial conditionsSystem Simulator:
• - 1 cell, default parameters. User Equipment:
• The UE shall have a MultiParty call to two destinations (A-B and A-C) both in state U10 "Active" with auxiliary state "Call in MPTY". The UE shall have in addition a single call (A-D) in state U10 "Active" with auxiliary state "Cal... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.26.5 Test requirements | At step 5, step 7 and step 9, the UE shall have Call A-B and A-C entering state U10 with auxiliary state "Call in MPTY, Hold Request", and have Call A-D entering state U10 with auxiliary state "Retrieve request".
At step 13, step 15 and step 17, the UE shall have Call A-B and A-C entering state U10 with auxiliary state... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27 Multi-party supplementary services, Adding extra remote parties | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27.1 Definition | The operation of adding extra remote party into the MPTY call is successfully accepted by the network. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27.2 Conformance requirement | Extra remote parties are added by placing the MultiParty call on hold and setting up a new connection (either a new call or a waiting call) and then sending a FACILITY message to the network requesting that the active call be joined with the MPTY, using the same signalling as for invocation. This results in an active M... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27.3 Test purpose | To test that the UE adds extra remote parties to the MultiParty call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27.4 Method of test | Initial conditions
• System Simulator:
• 1 cell, default parameters.
• User Equipment:
• The UE 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 relevant to ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.7.27.5 Test requirements | At step 11, step 13 and step 15, the UE shall have Call A-B, A-C and A-D entering state U10 with auxiliary state "Call in MPTY". |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8 Call restriction | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1 Registration accepted | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1.1 Definition | To check that the UE correctly handles the successful password registration for all barring services. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1.2 Conformance requirement | If the served mobile subscriber is given the possibility to control the service by the use of a password, the service provider had to register a password at provision time. The served mobile subscriber can change the call barring password at any time.
If the entity that uses the supplementary support procedures wants t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1.3 Test purpose | 1) To check that the UE correctly requests a supplementary service transaction for registration of a password for all barring services in the CM SERVICE REQUEST message.
3) To check that the UE sends a REGISTER message containing an Invoke component of the operation “register password” with the expected parameter value... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1.4 Method of test | Related ICS/IXIT statements
Support of FDD Yes/No.
Support of one barring supplementary service Yes/No.
Support of CS speech Yes/No.
Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
The UE is in registered idle state on cell 1.
Test procedure
The UE is made to initiate the registration o... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.1.5 Test requirements | In Step 2 the UE sends the CM SERVICE REQUEST message with the CM service type ‘Supplementary service activation’.
In Steps 4, 6, 8 and 10 the UE populates the messages with the correct values.
In Step 14 the UE provides indication of successful password registration for all barring services. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2 Rejection after invoke of the operation “register password” with subscription violation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2.1 Definition | To check that the UE correctly handles the password change attempt for the Call Barring supplementary service when the new password registration fails as the subscription option “control of services” is set to “by the service provider”. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2.2 Conformance requirement | If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by the service provider" an attempt to register a password will be denied and the served mobile subscriber should receive a notification..
If the entity that uses the supplementary support procedures... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2.3 Test purpose | 1) To check that, when a CS call is already established, the UE correctly requests the establishment of a new MM transaction for supplementary services by sending a CM SERVICE REQUEST.
2) To check that the UE sends a REGISTER message containing the invoke of the operation “register password” with the expected parameter... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2.4 Method of test | Related ICS/IXIT statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of one barring supplementary service Yes/No.
Initial conditions
System Simulator:
- 1 cell, default parameters.
User Equipment:
- The UE is in call state U10 by using table 10.1.2/3.
Test procedure
The registration of a new password... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.2.5 Test requirements | In Step 2 the UE sends the CM SERVICE REQUEST message with the CM service type ‘Supplementary service activation’.
In steps 4 and 8 the UE sends the correct message.
In step 6 the mobile subscriber is notified about the subscription violation. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3 Rejection after password check with negative result | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3.1 Definition | To check that the UE correctly handles the password change attempt for the Call Barring supplementary service when the old password is rejected. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3.2 Conformance requirement | If the served mobile subscriber at provision time has selected the subscription option "control of supplementary service by subscriber using password", and if a wrong password is entered to activate the service the supplementary service will not be activated and the served mobile subscriber is notified.
If the entity t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3.3 Test purpose | 1) To check that, when a CS call is already established, the UE correctly requests the establishment of a new MM transaction for supplementary services by sending a CM SERVICE REQUEST.
2) To check that the UE sends a REGISTER message containing the invoke of the RegisterPassword operation with the expected parameter va... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3.4 Method of test | Related ICS/IXIT statements
Support of FDD Yes/No.
Support of CS speech Yes/No.
Support of one barring supplementary service Yes/No.
Initial conditions
System Simulator:
- 1 cell, default parameters.
User Equipment:
- The UE is brought into the CC state U10 by using table 10.1.2/3.
Test procedure
The registration of a ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.3.5 Test requirements | In Steps 2 the UE sends the CM SERVICE REQUEST message with the CM service type ‘Supplementary service activation’.
In steps 4, 6 and 10 the UE sends the correct message.
In step 8 the mobile subscriber is notified about the wrong password. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4 Activation accepted | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4.1 Definition | To check that the UE correctly handles the supplementary service activation for BAOC or BICRoam. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4.2 Conformance requirement | If the entity that uses the supplementary support procedures wants to send a REGISTER message, the supplementary service support entity shall first request the establishment of an MM‑connection.
...
The supplementary service support entity shall send the REGISTER message as the first CM‑message on the MM‑connection.
…
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4.3 Test purpose | 1) To check that the UE correctly requests a supplementary service transaction for activation of call restriction service in the subsequent CM SERVICE REQUEST.
2) To check that the UE sends a REGISTER message containing an Invoke component of the ActivateSS operation with the expected parameter values for activation of... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4.4 Method of test | Related ICS/IXIT statements
Support of FDD Yes/No.
Support of BAOC supplementary service Yes/No
Support of BICRoam supplementary service Yes/No
Support of CS speech Yes/No
Initial conditions
System Simulator:
- 1 cell, default parameters.
User Equipment:
- The UE is in registered idle state on cell 1.
Test procedure
Th... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.4.5 Test requirements | In Steps 2 and 11, the UE sends the CM SERVICE REQUEST message with the CM service type ‘Supplementary service activation’.
In Steps 4, 6, 13 and 15 the UE populates the messages with the correct values.
In steps 9a and 18a the UE provides the indications of successful activation of the relevant supplementary service (... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5 Rejection after invoke of ActivateSS operation | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5.1 Definition | To check that an attempt to activate a supplementary service with transgressing the subscription restrictions will be denied, the served mobile subscriber receives an error indication and the first call transaction remains unaffected. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5.2 Conformance requirement | If the entity that uses the supplementary support procedures wants to send a REGISTER message, the supplementary service support entity shall first request the establishment of an MM‑connection.
...
The supplementary service support entity shall send the REGISTER message as the first CM‑message on the MM‑connection.
…
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5.3 Test purpose | 1) To check that, when a call transaction is already established, the UE correctly requests the establishment of a parallel MM transaction for supplementary service transaction of specific call barring service, sending a CM SERVICE REQUEST.
2) To check that the UE sends a REGISTER message containing the invoke of the A... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5.4 Method of test | Related ICS/IXIT statements
Support of BOIC supplementary service Yes/No.
Support of FDD Yes/No.
Support of CS speech Yes/No.
Initial conditions
System Simulator:
- 1 cell, default parameters.
User Equipment:
- The UE is brought into the CC state U10 by using table 10.1.2/3.
Test procedure
The UE is made to initiate t... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.5.5 Test requirements | 1) In Steps 4 and 8 the UE populates the messages with the correct values.
2) In Steps 6 the UE provides an appropriate user indication about failure of the supplementary service deactivation. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.6 Deactivation accepted | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.6.1 Definition | To check that the UE correctly handles the supplementary service deactivation for all speech restrictions. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 15.8.6.2 Conformance requirement | If the entity that uses the supplementary support procedures wants to send a REGISTER message, the supplementary service support entity shall first request the establishment of an MM‑connection.
...
The supplementary service support entity shall send the REGISTER message as the first CM‑message on the MM‑connection.
..... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.