hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.1 Conformance requirements | 1) Upon receipt of the SETUP message containing a notification indication that the call is a forwarded one (with any SS code except CFC), the MS shall correctly continue call establishment and enter CC state U6.
2) Upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.2 Test purpose | 1) To check that, upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, the MS correctly continues call establishment and enters CC state U6.
2) To check that upon receipt of the SETUP message containing a notification indication that the call is a forwarded one, or af... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.1.7.2.3 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle updated".
Specific PICS Statements
-
PIXIT Statements
- Description of the user's commands and of display of the answers from the network for call forwarding.
Foreseen final state of the MS
The MS is "idle updated".
Test pr... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.2.2 Call transfer and mobile access hunting supplementary services | (Reserved). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3 Call completion supplementary services | NOTE: In this subclause, Subscriber B is the MS under test, and subscribers A, C and D are distant parties to the calls made during the tests. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1 Call Waiting | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.1 Waiting call indication and confirmation | Conformance requirement
3GPP TS 04.83 subclause 1.1.
Test purpose
With an active call, an MS receiving an MT call shall include Cause #17 "user busy" in the CALL CONFIRMED message sent to the SS, and indicate the waiting call to the subscriber.
Method of test
Specific PICS Statements
- Supported MT circuit switched bas... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2 Normal operation with successful outcome | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.1 Waiting call accepted; existing call released | Conformance requirement
3GPP TS 04.83 subclause 1.2.1.
Test purpose
The MS shall release the active call using the call clearing procedures of 3GPP TS 04.08 / 3GPP TS 24.008, and then accept the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIX... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.2 Waiting call accepted; existing call on hold | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.2.1 Waiting call accepted; existing call on hold, no additional calls | Conformance requirement
3GPP TS 04.83 subclause 1.2.2.
Test purpose
With one active call and one waiting call, the MS shall place the active call on hold, and then accept the waiting call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing an active call on hold and answering a waiting call.... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.2.3 Existing call released by user A; waiting call accepted | Conformance requirement
3GPP TS 04.83 subclause 1.2.3.
Test purpose
The MS, on receipt of a DISCONNECT message from the active call, shall complete the clearance of the active call, and accept the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
P... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3 Normal operation with unsuccessful outcome | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3.1 Waiting call released by subscriber B | Conformance requirement
3GPP TS 04.83 subclause 1.3.1.
Test purpose
To test that, using MMI commands, the MS shall clear the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
- Method of clearing a waiting call.
Initial conditions
... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.3.2 Waiting call released by calling user C | Conformance requirement
3GPP TS 04.83 subclause 1.3.2.
Test purpose
To test that the MS responds correctly to the receipt of a clearing message from the waiting call.
Method of test
Specific PICS Statements
- Supported MT circuit switched basic services (TSPC_AddInfo_MTsvc)
PIXIT Statements
-
Initial conditions
System ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.4 Activation | Conformance requirement
3GPP TS 04.83 subclause 1.4.
Test purpose
To test the correct operation of the activation procedure, and correctly display of the response from the SS in the following cases.
1) Successful activation.
2) Error response (reject).
3) Activation reject (Invoke problem).
Initial conditions
System Si... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.5 Deactivation | Conformance requirement
3GPP TS 04.83 subclause 1.5.
Test purpose
To test the correct operation of the deactivation procedure, and correct display of the response from the SS in the following cases.
1) Successful deactivation.
2) Error response (reject).
3) Activation reject (Invoke problem).
Initial conditions
System ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.6 Interrogation | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.6.1 Interrogation accepted | Conformance requirement
3GPP TS 04.83 subclause 1.6.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of successful interrogation.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS is "idle update... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.1.6.2 Interrogation rejected | Conformance requirement
3GPP TS 04.83 subclause 1.6.
Test purpose
To test the correct operation of the interrogation procedure, and correct display of the response from the SS in the case of an error response and an invoke problem
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.2 Call Hold | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.2.1 Hold invocation | Conformance requirement
3GPP TS 04.83 subclause 2.1.2.
Test purpose
To test the correct operation of the Hold procedure, and the MS reaction to the following messages sent in response to the HOLD message.
1. HOLD REJECT.
2. HOLD ACKNOWLEDGE.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.2.2 Retrieve procedure | Conformance requirement
3GPP TS 04.83 subclause 2.1.3.
Applicability
MS supporting the Call Hold supplementary service.
Test purpose
To test the correct operation of the retrieve procedure, and the MS reaction to the following messages sent in response to the RETRIEVE message.
1) RETRIEVE REJECT.
2) RETRIEVE ACKNOWLEDG... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.3.2.3 Alternate from one call to the other | Conformance requirement
3GPP TS 04.83 subclause 2.1.4.
Test purpose
To test that the MS correctly alternates between one call and the other, by placing the active call on hold, and retrieving the previously held call.
To test that the MS correctly returns to the original call states in the event of receipt of a HOLD RE... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4 Multi-party supplementary services | NOTE: In this subclause, subscriber A is the MS under test, and subscribers B to G are distant parties in the calls used in the tests. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.1 Beginning the MultiParty service | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.1.1 Beginning the MultiParty service, successful case | Conformance requirement
3GPP TS 04.84 subclause 1.1.
Test purpose
To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and reacts correctly to a response from the SS indicating success.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of joining two ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.1.2 Beginning the MultiParty service, unsuccessful case | Conformance requirement
3GPP TS 04.84 subclause 1.1.
Test purpose
To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and reacts correctly to the following responses from the SS.
1) Return error.
2) Reject.
Method of test
Specific PICS Statements
-
PIXIT Statements
- ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.1.3 Beginning the MultiParty service, expiry of timer T(BuildMPTY) | Conformance requirement
3GPP TS 04.84 subclause 1.1.
Test purpose
To test that the MS correctly starts the MultiParty service when it has an active call and a held call, and on expiry of timer T(BuildMPTY) returns both calls to their original states.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method o... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2 Managing an active MultiParty call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1 Served mobile subscriber | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.1 Put the MultiParty call on hold | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.1.1 Put the MultiParty call on hold, successful case | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.1.
Test purpose
To test that the MS correctly places an active MultiParty call on hold, and reacts correctly to a response from the SS indicating success.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing a MultiParty call on hold.
Initi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.1.2 Put the MultiParty call on hold, unsuccessful case | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.1.
Test purpose
To test that the MS correctly places an active MultiParty call on hold, and reacts correctly to a response from the SS indicating an error or a reject condition.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing a MultiPa... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.1.3 Put the MultiParty call on hold, expiry of timer T(HoldMPTY) | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.1.
Test purpose
To test that the MS correctly places an active MultiParty call on hold, and on expiry of T(HoldMPTY) returns the MultiParty call to the auxiliary state "Call in MPTY".
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of placing a M... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.2 Create a private communication with one of the remote parties | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.2.1 Create a private communication with one of the remote parties, successful case | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.2.
Test purpose
To test that the MS correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating success.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of creating a private communication with one party ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.2.2 Create a private communication with one of the remote parties, unsuccessful case | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.2.
Test purpose
To test that the MS correctly splits an active MultiParty call, and reacts correctly to a response from the SS indicating an error or reject condition.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of creating a private communic... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.2.3 Create a private communication with one of the remote parties, expiry of timer T(SplitMPTY) | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.2.
Test purpose
To test that the MS correctly splits an active MultiParty call, and on expiry of T(SplitMPTY) returns the call to the auxiliary state "Call in MPTY".
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of creating a private communicat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.3 Terminate the entire MultiParty call | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.3.
Test purpose
To test that the MS correctly terminates an entire MultiParty call by implementing the call clearance procedure for each call in turn.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of terminating a MultiParty call.
Initial condi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.1.4 Explicitly disconnect a remote party | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.4.
Test purpose
To test that the MS correctly disconnects a single remote party by implementing the call clearance procedure for that party.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of disconnecting one party of a MultiParty call.
Initial ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.2 Remote parties | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.2.2.1 Release from the MultiParty call | Conformance requirement
3GPP TS 04.84 subclause 1.2.1.4.
Test purpose
To test that the MS responds correctly to a call clearance from one of the remote parties.
Method of test
Specific PICS Statements
-
PIXIT Statements
-
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile Station:
The MS shall have... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3 Managing a held MultiParty call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.1 Retrieve the held MultiParty call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.1.1 Retrieve the held MultiParty call, successful case | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.1.
Test purpose
To test that the MS correctly retrieves a held MultiParty call, and reacts correctly to a response from the SS indicating success.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of retrieving a held MultiParty call.
Initial condi... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.1.2 Retrieve the held MultiParty call, unsuccessful case | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.1.
Test purpose
To test that the MS correctly retrieves a held MultiParty call, and reacts correctly to a response from the SS indicating an error or a reject condition.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of retrieving a held MultiPa... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.1.3 Retrieve the held MultiParty call, expiry of timer T(RetrieveMPTY) | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.1.
Test purpose
To test that the MS correctly retrieves a MultiParty call on hold, and on expiry of T(RetrieveMPTY) returns the MultiParty call to the auxiliary state "Call in MPTY, call held".
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of r... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.2 Initiate a new call | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.2.
Test purpose
To test that the MS can set up a new outgoing call with a held MultiParty call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of making a new outgoing call.
Initial conditions
System Simulator:
1 cell, default parameters.
Mobile... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.3 Process a call waiting request | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.3.
Test purpose
To test that the MS can correctly process a Call Waiting request with a held MultiParty call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of answering a waiting call.
Initial conditions
System Simulator:
1 cell, default parame... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.3.4 Terminate the held MultiParty call | Conformance requirement
3GPP TS 04.84 subclause 1.3.1.4.
Test purpose
To test that the MS correctly terminates a held MultiParty call by initiating call clearance for each party in turn.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of terminating a held MultiParty call.
Initial conditions
System ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4 Managing a single call and a MultiParty call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1 Served mobile subscriber | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.1 Disconnect the single call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.1.1 Disconnect active single call | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.1.
Test purpose
To test that the MS correctly clears the single call when the single call is active and the MultiParty call is held.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of clearing the single call.
Initial conditions
System Simulator:... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.1.2 Disconnect held single call | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.1.
Test purpose
To test that the MS correctly clears the single call when the single call is held and the MultiParty call is active.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of clearing the held single call.
Initial conditions
System Simul... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.2 Disconnect the MultiParty call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.2.1 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.2.2 Void | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.2.3 Clear all parties of held MultiParty call | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.2.
Test purpose
To test that the MS correctly clears the MultiParty call by clearing all remote parties to a held MultiParty call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of clearing a held MultiParty call.
Initial conditions
System Simul... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.1.2.4 Clear all parties of active MultiParty call | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.2.
Test purpose
To test that the MS correctly clears the MultiParty call by clearing all remote parties to an active MultiParty call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of clearing an active MultiParty call.
Initial conditions
System... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.2 Disconnect all calls | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.3.
Test purpose
To test the MS correctly clears all calls, by clearing in turn each connected party.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of clearing all active calls.
Initial conditions
System Simulator:
1 cell, default parameters.
Mo... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.3 Add the single call to the MPTY | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.3.1 Add the single call to the MPTY, successful case | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.4.
Test purpose
To test that the MS correctly adds a single held call to an active MultiParty call, and reacts correctly to a response from the SS indicating success.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of adding the single call to th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.3.2 Add the single call to the MPTY, maximum number of participants exceeded | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.4.
Test purpose
To test that the MS 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.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.4.4 Alternate between the MPTY call and the single call | Conformance requirement
3GPP TS 04.84 subclause 1.4.1.5.
Test purpose
To test that the MS correctly alternates between the single call and the MultiParty call, by proper use of the hold and retrieve procedures.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of alternating between the single call to... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.4.5 Adding extra remote parties | Conformance requirement
3GPP TS 04.84 subclause 1.5.
Test purpose
To test that the MS adds extra remote parties to the MultiParty call.
Method of test
Specific PICS Statements
-
PIXIT Statements
- Method of alternating between the single call to the MultiParty call.
Initial conditions
System Simulator:
1 cell, default ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.5 Community of interest supplementary services | (Reserved). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6 Charging supplementary services | The following Advice of Charge abbreviations are used in this subclause:
AoC Advice of Charge
AoCC Advice of Charge Charging
AoCI Advice of Charge Information
ACM Accumulated Charge Meter
ACMmax Accumulated Charge Meter Maximum
CCM Current Call Meter
CAI Charge Advice Information
CDUR Chargeable Duration
The following ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1 Advice of Charge Charging | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.1 AoCC time related charging / MS originated call | Purpose:
1) To verify that when the MS receives the AoCC parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives the AoCC parameters in a Facility I... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.2 AoCC time related charging / MS terminated call | Purpose:
1) To verify that when the MS receives certain AoCC e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.3 AoCC volume related charging / MS originated call | Future addition at GSM Phase 2+ stage. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.4 AoCC volume related charging / MS terminated call | Future addition at GSM Phase 2+ stage. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.5 Change in charging information during a call | Purpose:
1) To verify that when the MS receives new AoCC parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives new charging information mid-way through a call in ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.6 Different formats of charging information | Purpose:
1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE.
2) To verify the operation of a shortened channel release procedure where the SS does not s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.7 AoCC on a Call Hold call | Purpose:
1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS invokes a Call... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.1.8 AoCC on a Multi-party call | Purpose:
1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCC e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCC acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS originates a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2 Charge Storage | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2.1 Removal of SIM during an active call | Purpose:
1) To verify that when the SIM is removed from the ME during an active AoCC call the ME immediately terminates the call.
2) To verify that when the SIM is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM.
Conformance Requirement(s):... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2.2 Interruption of power supply during an active call | Purpose:
To verify that when the power supply of the MS is removed during an active AoCC call the ME has written the total charge up to that point in the call to the ACM field of the SIM.
Conformance Requirement(s):
When the power supply of the MS is removed during an active AoCC call midway through an AoC charging tim... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2.3 MS going out of coverage during an active AoCC call | NOTE: At present the core recommendations for AoCC in the case where the radio link is lost during an active call are vague. Does the mobile go on charging for a fixed period after radio link loss and continue as usual if radio link reestablishment occurs, or does charging stop? Input from people involved in charging f... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2.4 ACMmax operation / Mobile Originating | Purpose:
1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any outgoing calls in progress for which a non-zero CAI exists are terminated by the ME, with cause value #68 once the chargeable interval determined by the CAI has elapsed, with an appropriate indicat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.2.5 ACMmax operation / Mobile Terminating | Purpose:
1) To verify that when the value stored in the ACM becomes equal to or exceeds its maximum value, the ACMmax, any mobile terminating calls in progress for which a non-zero CAI exists are terminated by the ME with cause value #68, once the chargeable interval determined by the CAI has elapsed, with an appropria... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3 Advice of Charge Information | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.1 AoCI time related charging / MS originated call | Purpose:
1) To verify that when the MS receives the AoCI parameters in a Facility IE which is contained in the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that the when the call has no volume related component the MS... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.2 AoCI time related charging / MS terminated call | Purpose:
1) To verify that when the MS receives certain AoCI e-parameters in a Facility IE which is contained in a FACILITY message sent after the CONNECT message and when a TCH has already been assigned, the MS returns a FACILITY message containing the acknowledgement within 1 s.
Conformance Requirement(s):
1) When th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.3 AoCI volume related charging / MS originated call | Future addition at GSM Phase 2+ stage. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.4 AoCI volume related charging / MS terminated call | Future addition at GSM Phase 2+ stage. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.5 Change in charging information during a call | Purpose:
1) To verify that when the MS receives new AoCI parameters mid-way through a call in a Facility IE which is contained within a FACILITY message the MS returns a FACILITY message containing the acknowledgement within 1 s.
2) To verify that when the MS receives new charging information mid-way through a call in ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.6 Different formats of charging information | Purpose:
1) To verify that when the MS receives a Facility IE in which certain e-parameters are set to zero the total charge accumulated is the same as that when the same e-parameters are completely omitted from the Facility IE.
2) To verify the operation of a shortened channel release procedure where the SS does not s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.7 AoCI on a Call Hold call | Purpose:
1) To verify that when the MS invokes a Call Hold call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters.
Conformance Requirement(s):
1) When the MS i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.3.8 AoCI on a Multi-party call | Purpose:
1) To verify that when the MS invokes a Multi-party call and hence receives Facility IEs containing AoCI e-parameters for each chargeable call the MS returns a FACILITY message containing the AoCI acknowledgement within 1 s of transmission of each set of e-parameters.
2) To verify that when the MS originates a... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.6.4 Default contents of messages | As default message contents in 3GPP TS 11.10 subclause 26.8. These messages shall not contain SS version IEs.
Where indicated in specific tests CONNECT and FACILITY messages have Facility Information Elements as defined below.
Default contents of ForwardChargeAdvice Facility Information Elements
The following abbreviat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.7 Additional information transfer supplementary services | (Reserved). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.8 Call restriction supplementary services | The following abbreviations are used:
BO: Barring of Outgoing calls.
BAOC: Barring of All Outgoing Calls.
BOIC: Barring of Outgoing International Calls.
BOICExHC: Barring of Outgoing International Call EXcept those directed to the Home PLMN country.
BI: Barring of Incoming calls.
BAIC: Barring of All Incoming calls.
BI... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.8.1 Registration of a password | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.8.1.1 Registration accepted | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.8.1.1.1 Conformance requirements | 1) For registration of a password for all barring services, the MS shall transmit successively:
1.1) a CHANNEL REQUEST with establishment cause set to "other services requested by the mobile user";
1.2) a CM SERVICE REQUEST with CM service type indicating "supplementary service activation";
1.3) and then the REGISTER m... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 31.8.1.1.2 Test purpose | 1) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in CHANNEL REQUEST message.
2) To check that the MS correctly requests a supplementary service transaction for registration of a password for all barring services in the subsequent CM S... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.