hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.3 Test purpose | To verify that the terminal, during a call, increments the ACM every 5 s when e2 is less or equal to 5 s. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.4.1 Initial conditions | The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbers not ac... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.4.2 Procedure | a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.5 Test requirement | The MS shall, during a call, send INCREMENT commands to the SIM every 5 s. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3 Call terminated when ACM greater than ACMmax | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.1 Definition | ACMmax gives the maximum value of ACM, at which the current calls shall be terminated and no further outgoing calls and charged incoming calls may be made (except emergency calls). |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.2 Conformance requirement | ACM shall be incremented by the value of CCM.
If the ACMmax is valid, and the ACM becomes equal to or exceeds the value of the ACMmax, then all calls in progress, chargeable to the user, shall be terminated by the MS with cause value #68, once the chargeable interval determined by the CAI has elapsed, (except emergency... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.3 Test purpose | 1. To verify that the ME increments the ACM by the correct number of units, even though this may take ACM above ACMmax.
2. To verify that the ME terminates the call with cause value #68. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.4.1 Initial conditions | The ME shall be connected to a SIM or the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbe... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.4.2 Procedure | a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.3.5 Test requirement | 1) The MS shall terminate the call correctly 30 s after CAI was sent.
2) The value of ACM shall be 100 units. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4 Response codes of increase command | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.1 Definition | ACM has a maximum value in terms of coding, and an attempt by the ME to exceed that value by sending an INCREASE command shall result in an error message from the SIM. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.2 Conformance requirement | The ME shall perform the increasing procedure, sending the amount to be increased.
The running accumulated charge shall be stored in the ACM of the SIM.
Where this charge cannot be stored in the MS, use of the telecommunications service shall be prevented.
References:
3GPP TS 11.11, subclause 11.5.3; 3GPP TS 02.86, sub... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.3 Test purpose | To verify that the ME clears a charged call if the SIM indicates that the ACM cannot be increased. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.4.1 Initial conditions | The ME shall be connected to the SIM simulator, with all elementary files coded as default with the exception of:
EFSST (SIM Service Table)
Logically: CHV1 disable function allocated and activated.
Abbreviated dialling numbers allocated and activated.
PLMN selector allocated and activated.
Fixed dialling numbers not ac... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.4.2 Procedure | a) The MS is made to initiate a call. The call is established with AoCC e-parameters sent in a Facility IE in the CONNECT message, as given below. The MS returns the AoCC acknowledgement within 1 second of the CONNECT message. It is an implementation option whether the AoCC acknowledge is sent by the MS before or after... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.4.5 Test requirement | In each of the three cases, as described in steps b), c) and d) of the procedure, the MS shall terminate the call correctly when it receives an indication from the SIM that the ACM cannot be incremented. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28 Test of autocalling restrictions | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.1 General | It is essential that all autocalling apparatus is prevented from continuously dialling a given number, to avoid machines repeatedly disturbing PSTN subscribers in error, or numerous repeat attempts to unobtainable numbers which cause waste of valuable network resources. Therefore autocalling restrictions are defined by... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.2.1 Conformance requirement | A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in 3GPP TS 04.08 / 3GPP TS 24.008).
These reasons are classified in three major categories:
1. "Busy destination".
2. "Unobtainable destination - temporary".
3. "Unobtainable destination - permanent/long term"... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.2.2 Test purpose | To ensure the correct behaviour of the MS to 3GPP TS 02.07 Category 3. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.2.3 Method of test | Initial condition.
There shall be no numbers in the list of blacklisted numbers in the MS. The time set between the first re-attempt and the next re-attempt is set to the minimum value possible. The number of re-attempts is set to the lowest possible number greater than 1 that is supported by the MS. The autocalling fu... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.3.1 Conformance requirement | The MS must fulfil the requirements for category 1 and 2, see subclause 28.2.1
Reference:
3GPP TS 02.07, annex A. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.3.2 Test purpose | To ensure the correct behaviour of the MS to 3GPP TS 02.07 Categories 1 and 2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.3.3 Method of test | Initial condition.
There shall be no numbers in the list of blacklisted numbers in the MS. The re-try scheme is set to give the shortest possible intervals between re-tries. The number of re-attempts is set to the maximum possible number (N) that is supported by the MS. The autocalling function is invoked for the B-par... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.4 Behaviour of the MS when its list of blacklisted numbers is full | The number of B-party numbers that can be stored in the list of blacklisted numbers, as stated in the PIXIT statement (annex 3), is M. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.4.1 Conformance requirement | The number of B numbers that can be held in the blacklist is at the manufacturer’s discretion but there shall be at least 8. However, when the blacklist is full the MT shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the MT in respect of one or more B numbers.
... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.4.2 Test purpose | To ensure the correct behaviour of the MS when its list of blacklisted numbers is full. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.4.3 Method of test | Initial condition.
The list of blacklisted numbers, in the MS, shall be full. This may be achieved as described in the procedure in subclause 28.2, applied to M B-party numbers.
Specific PICS statements:
• Implementation of cause number 27 of busy autocalling in category 2 (TSPC_AddInfo_Impl_CNr27_Cat2)
• Implementatio... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 28.4.4 Test requirements | The MS must not initiate a call.
Step
Direction
Message
Comments
1
MS
"called number" entered
2
MS -> SS
CHANNEL REQUEST
Establishment cause indicates "originating call".
3
SS -> MS
IMMEDIATE ASSIGNMENT
4
MS -> SS
CM SERVICE REQUEST
Message is contained in SABM.
5
SS -> MS
AUTHENTICATION REQUEST
6
MS -> SS
AUTHENTICATI... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29 Testing of bearer services | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.1 General | In 3GPP TS 07.01, subclause 2 the reference configurations for access to the data services of a GSM PLMN are described. For testing purposes only the following classifications are used:
- MT2 configuration (Um- and R-interface available for testing).
- Configurations (only Um-interface available for testing) where it i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2 Testing of transparent data services | During all the tests the 3GPP TS 04.21 frames received as output of the channel coder in the SS shall be checked for correctness against 3GPP TS 04.21; this means checking that:
- S bits are coded as zeroes unless otherwise specified;
- the E bits have the correct value (for the synchronous services);
- the data bits c... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1 Verification of synchronization | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.1 Definition | -29.2.1.2 Conformance requirement
A Mobile Stations in MT2 configuration has to comply with all requirements whilst for other configurations some of the requirements are not relevant. These restrictions are explicitly indicated in subclause 29.2.1.5. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.3 Test purpose | This test verifies the correct synchronization procedure of user data and status information which are mapped on modified ITU-T Recommendation V.110 frames (as per 3GPP TS 04.21).
As V-series interfaces are supported in full duplex mode, it will test the capability to synchronize these frames in the direction from the ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.4 Method of test | The test shall be carried out under ideal radio conditions for all bearer services and user rates in transparent mode that are supported by the MS in case of mobile originated and terminated calls and in-call modification. The setting of Bearer Capability Information Elements in signalling messages sent to the MS by th... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.4.1 Procedure for Mobile Originated Calls | a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, the LTE shall set the signalling lines of the R interface Ct 105, Ct 108.2 for V-series interface to ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.4.2 Procedure for Mobile Terminated Calls | a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, The LTE shall set the signalling lines of the R interface Ct. 105, Ct 108.2 for V-series interface to... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.4.3 Procedure for In Call Modification | a) The MS is connected to the System Simulator at the Um interface and to the LTE using the appropriate R interface in case of MT2 only.
b) The MS is configured for data transmission. In the case of MT2 configurations, the LTE shall set the signalling lines of the R interface Ct. 105, Ct 108.2 for V-series interface to... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.5 Test requirements | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.5.1 Test requirements for Mobile Originated Calls | 1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.5.2 Test requirements for Mobile Terminated Calls | 1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.1.5.3 Test requirements for In Call Modification | 1) After step b) Cts 106, 107, 109 must be in the "OFF" condition, data line 104 shall be set to "1".
2) At t1 + 500 ms Ct 107 must still be in the "OFF" condition.
3) Between t1 + 500 ms and t1 + 1 000 ms Ct 107 must switch to the "ON" condition. This indicates successful synchronization of TAF towards IFE.
4) Between... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2 Filtering of channel control information for transparent BCs | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2.1 Definition | -29.2.2.2 Conformance requirement
An MS supporting data services shall decode and filter channel control information received over the Um-interface.
1. 3GPP TS 04.21, clause 7;
2. 3GPP TS 07.01, subclause 8.2.2;
3. 3GPP TS 07.02, subclause 3.2.1 (for asynchronous bearer services only);
4. 3GPP TS 07.03, subclauses 4.2.... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2.3 Test purpose | The purpose of this test is to verify the correct decoding and filtering of channel control information from the 3GPP TS 04.21 frames to the V.24/X.21 interface circuits. The tests apply after synchronization has been completed. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2.4 Method of test | The Test shall be carried out for all user data rates supported by the MS (see below) and the circuits CT106 (V.24) (interface circuit bit X) and CT109 (V.24) (interface circuit bit SB) and I (X.21) (S-bits). The test shall be carried out only for those frame formats and circuits which are supported by the MS. The test... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2.5 Test requirements | 1) After step a) the interface circuit at the R-interface shall be OFF.
2) During step b) the interface circuit at the R-interface shall not change.
3) During step c) the interface circuit at the R-interface shall change to ON and then again to OFF.
4) After step d) the interface circuit at the R-interface shall be ON.... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.2.6 BCIE | The following combinations shall be considered (ref. 3GPP TS 07.01, annex 2):
a) User Rate = 9,6 kbit/s;
b) User Rate = 4,8 kbit/s;
c) User Rate = 2,4 kbit/s;
d) User Rate = 1,2 kbit/s;
e) User Rate = 1 200/75 bit/s (only with asynchronous Bearer Services);
f) User Rate = 300 bit/s (only with asynchronous Bearer Servic... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3 Correct Terminal Compatibility Decision | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.1 Negotiation of Radio Channel Requirement (RCR) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.1.1 Test purpose | To verify that the MS ignores the RCR field in a mobile terminating setup and negotiates according to its capabilities and to the service requested. A Dual Rate support MS shall accept the channel rate chosen be the network in the ASSIGNMENT COMMAND message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.1.2 Initial conditions | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.1.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and with the RCR field set to "01".
b) The SS sends a ASSIGNMENT COMMAND message with a channel type set to "Full Rate" unless the CALL CONFIRM message indicates "dual rate mobile station/full rate preferred". In that cas... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.1.4 Test requirements | 1) After step a), the MS shall send a CALL CONFIRM message. If present, the BC-IE shall be coded according to 3GPP TS 07.01. If any other parameters than those listed below have different values than those of the BC-IE included in the SETUP, then the test shall be failed:
- Number of stop bits, number of data bits, par... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.2 Negotiation of Connection Element (CE) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.2.1 Test purpose | To verify that the MS accepts a CE equal to "Both, Transparent Preferred" or "Both Non Transparent Preferred" and indicates its choice in the CALL CONFIRM message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.2.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
•
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.2.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and with the CE field set to "Both Transparent Preferred". The RCR parameter shall be set to "Full Rate". The UIL2P is not included (i.e. octet 7 is absent). The NIRR is set to "no meaning" (i.e. 0). The IR is set to "16 ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.2.4 Test requirements | After step a), the MS shall send a CALL CONFIRM message. The BC-IE shall be present and shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. The CE shall be set to either "Transparent" or "Non Transparent" If any other parameters than those listed bellow... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.3 Negotiation of Number of Stop Bits, Number of Data bits, and Parity | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.3.1 Test purpose | To verify that the MS accepts any value for the parameters Number of Stop Bits, Number of Data bits, and Parity in a mobile terminating Setup and negotiates according to its capabilities and to the service requested. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.3.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.3.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to an asynchronous Bearer Service, and with the Number of Stop Bits (NSB) field set to "1 bit", the Number of Data Bits (NDB) field set to "8 bits", and the Parity field set to "none".
b) The call is rel... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.3.4 Test requirements | After steps a) and b), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the SETUP, then the ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.4 Negotiation of Modem Type | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.4.1 Test purpose | To verify that the MS accepts the value "autobauding type 1" for the parameter Modem Type in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
NOTE: It is not clear if the MS should also accept any possible value for the Modem Type field. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.4.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.4.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent"), and with the Modem Type field set to "autobauding type 1".
b) The call is released and step a) is repeated w... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.4.4 Test requirements | After steps a) and b), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included in the S... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.5 Negotiation of Intermediate Rate | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.5.1 Test purpose | To verify that the MS responds correctly to a request for a negotiation of the Intermediate Rate parameter in a mobile terminating Setup and negotiates according to its capabilities and to the service requested.
NOTE: The MS may support these services with a 6 Kbit/s or (non exclusive) 12 Kbit/s radio interface rate.
2... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.5.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent") with the user rate lower to or equal 4,8 kbit/s, and with the NIRR field set to "No meaning". The RCR field i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.5.4 Test requirements | 1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.6 Negotiation of User Information Layer 2 Protocol | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.6.1 Test purpose | To verify that the MS accepts any value (including the absence of) the UIL2P parameter in a mobile terminating Setup and negotiates according to its capabilities and to the service requested. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.6.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
-
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.6.3 Test method | a) The SS transmits a SETUP message containing a BC-IE among those declared as supported by the MS and corresponding to a non transparent Bearer Service (the Connection Element field is coded "Non transparent") and with no UIL2P parameter (i.e. octet 7 of the BC IE is absent).
b) The call is released and step a) is rep... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.6.4 Test requirements | 1) After steps a), b) and c), the MS shall send a CALL CONFIRMED message. If present, the BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to a Bearer Service or Teleservice supported by the MS. If any other parameters than those listed bellow have different values than those of the BC-IE included i... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.7 Negotiation between TS 61 and TS 62: Mobile Originated call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.7.1 Test purpose | To verify that the MS accepts a negotiation from TS 61 to TS 62. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.7.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully set up a call for TS 61.
Specific PICS statements:
-
PIXIT statements:
- Way to set up the call
- Features which must be activated by MMI before an outgoing call can be set up. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.7.3 Test method | a) The MS is made to set up a call for TS 61. If the MS supports it, the first phase of the call is speech.
b) The SS responds to the SETUP message with a CALL PROCEEDING message containing a BC-IE coded according to 3GPP TS 07.01 and corresponding to TS 62.
c) The SS sends an ALERTING message followed by a CONNECT mes... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.7.4 Test requirements | 1) After step b), the MS shall accept the call (i.e. it shall not reject the call with a DISCONNECT message).
2) After step c), the MS shall answer with a CONNECT ACKNOWLEDGE message. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.8 Negotiation between TS 61 and TS 62: Mobile Terminated call | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.8.1 Test purpose | To verify that an MS that does not support TS 61 accepts a Mobile Terminated call setup request for TS 61 and negotiates the demand to TS 62. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.8.2 Initial condition | For an MS with an external interface, the interface shall be setup in such a way that the MS is able to successfully receive the call for the service in question.
Specific PICS statements:
•
PIXIT statements:
- Way to receive the call
- Features which must be activated by MMI before an incoming call can be accepted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.8.3 Test method | a) The SS transmits a SETUP message containing two BC-IEs: the first BC shall indicate speech, the second BC shall indicate fax group 3.
b) The call is released, and the SS transmits a SETUP message containing two BC-IEs: the first BC shall indicate fax group 3, the second BC shall indicate speech. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.3.8.4 Test requirements | After steps a) and b), the MS shall send a CALL CONFIRMED message with one and only one BC-IE. The BC-IE shall be coded according to 3GPP TS 07.01 and shall correspond to TS 62. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4 Data Rate Adaptation for Synchronous Transparent Bearer Capabilities | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4.1 Definition | -29.2.4.2 Conformance requirement
An MS supporting synchronous transparent bearer capabilities shall perform data rate adaptation and support the frames at the Um-interface according to the following specifications:
1. 3GPP TS 04.21, clauses 5 and 7. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4.3 Test purpose | The purpose of these tests is to verify:
- that the format and the data bits of the 3GPP TS 04.21 frames sent by the MS are consistent with the data input and data rate at the R-interface; and
- that the data bits output by the MS at the R-interface are consistent with the received 3GPP TS 04.21 frames. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4.4 Method of test | The Test shall be carried out for all possible user data rates which are supported by the MS (see below). In case of an MT2 configuration, the interface circuits CT105 and CT108 shall be set to the ON condition from the start.
Procedure:
a) A data call shall be set up between the SS and the MS with a BCIE (see below) s... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4.5 Test requirements | 1) During the test no 3GPP TS 04.21 frame with incorrect format (i.e. format not compliant to 3GPP TS 04.21 (see conformance requirement) or not corresponding to the user data rate currently under test) shall have been received by the SS.
2) Only MT2 configuration: the user data stream input to the R-interface shall ma... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 29.2.4.6 BCIE | The following combinations shall be considered (ref. 3GPP TS 07.01, annex 2):
a) User Rate = 9,6 kbit/s;
b) User Rate = 4,8 kbit/s;
c) User Rate = 2,4 kbit/s;
d) User Rate = 1,2 kbit/s.
The remaining parameters of the BCIE and the channel type (FR/HR) shall be set to a value supported by the MS. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.