hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.1 Definition | Fixed Dialling Number (FDN) is a service defined for the SIM. An activated FDN service results in call restrictions for the MS. The call restrictions are controlled by the ME. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.2 Conformance requirement | The MS allows call set-up to a directory number as stored in EFFDN and extended by digits added from an EFADN.
Reference:
3GPP TS 11.11, subclauses 9.3, 10.2.7, 10.3.2, 11.2.1 and 11.5.1, 3GPP TS 02.07, subclause 3.2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.3 Test purpose | To verify that the ME allows call set-up to a FDN number extended by digits from an EFADN. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.4.1 Initial conditions | The SS transmits on the BCCH, with the following network parameters
Attach/detach: disabled.
LAI-MCC: 246
LAI-MNC 81 or 813 (see Note 0)
LAI-LAC: 0001
LAI (MCC/MNC/LAC): 246/81/0001 or 246/813/0001 (see Note 0).
Access control: unrestricted.
The default FDN-SIM with FDN service enabled and EFADN invalidated but readabl... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.4.2 Procedure | a) The MS is powered on and PIN1 is entered.
b) Using the MMI a call set-up to the fixed dialling number 1 extended by the abbreviated dialling number 1 in the end is attempted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.1.2.5 Test requirement | 1) After step a) the MS is registered and in idle state.
2) After steps b) the MS shall allow call set-up and send the requested number across the air interface. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2 ME and SIM with FDN deactivated | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.1 Definition | Fixed Dialling Number (FDN) is a service defined for the SIM. An activated FDN service results in call restrictions for the MS. Only directory numbers which are stored in the EFFDN may be dialled by the MS. The call restrictions are controlled by the ME. To ascertain the type of SIM and state of FDN the MS runs the FDN... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.2 Conformance requirement | 1. Recognizing the state of the SIM (FDN disabled) the MS correctly performs the SIM initialization procedure.
2. The MS allows call set-up to a directory number as stored in EFFDN.
3. The MS allows call set-up to a directory number as stored in EFADN.
4. The MS allows call set-up to a directory number given in manuall... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.3 Test purpose | 1. To verify that the ME as a result of the state of the SIM correctly performs the SIM/ME initialization procedure.
2. To verify that the ME allows call set-up to a FDN number.
3. To verify that the ME allows call set-up to a ADN number.
4. To verify that the ME allows call set-up to manually given number. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.4.1 Initial conditions | The SS transmits on the BCCH, with the following network parameters
Attach/detach: disabled.
LAI-MCC: 246
LAI-MNC 81 or 813 (see Note 0)
LAI-LAC: 0001
LAI (MCC/MNC/LAC): 246/81/0001 or 246/813/0001 (see Note 0).
Access control: unrestricted.
The default FDN SIM with FDN service disabled is installed into the ME and the... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.4.2 Procedure | a) Using the MMI a call set-up to the fixed dialling number 1 is attempted.
b) Using the MMI a call set-up to the abbreviated dialling number 1 is attempted.
c) Using the MMI a call set-up to the number "1234567" is attempted. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.2.5 Test requirement | After steps a), b) and c) the MS shall allow call set-up and send the requested number across the air interface. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3 Enabling, disabling and updating of FDN | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.1 Definition | FDN may be enabled and disabled by the subscriber under control of PIN2. Fixed dialling numbers are read with PIN and updated under control of PIN2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.2 Conformance requirement | 1. Recognizing the state of the SIM (FDN enabled) the MS shall perform the SIM initialization procedure as specified.
2. The MS shall allow updating of EFFDN by the use of PIN2.
3. The MS provides means to disable the FDN service by the use of PIN2.
4. The MS shall allow the use of EFADN after disabling of FDN.
Referen... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.3 Test purpose | 1. To verify that the ME as a result of the state of the SIM rehabilitates EFIMSI and EFLOCI during SIM/ME initialization procedure.
2. To verify that the ME correctly performs the update of a number in EFFDN.
3. To verify that the ME correctly disables FDN service.
4. To verify that the ME recognizes disabling of FDN ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.4.1 Initial conditions | The SS transmits on the BCCH, with the following network parameters
Attach/detach: disabled.
LAI-MCC: 246
LAI-MNC 81 or 813 (see Note 0)
LAI-LAC: 0001
LAI (MCC/MNC/LAC): 246/81/0001 or 246/813/0001 (see Note 0).
Access control: unrestricted.
The default FDN SIM with FDN service enabled is installed into the ME and the ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.4.2 Procedure | a) The MS is powered on and PIN 1 is entered.
b) Using the MMI the directory number "+876543210" is stored in EFFDN as fixed dialling number 1 (The alpha identifier is not changed).
c) Using the MMI the FDN disabling procedure is performed. On request of the MS PIN2 is entered.
d) Using the MMI a call set-up to the abb... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.18.3.5 Test requirement | 1) After step a) the MS is registered and in idle state.
2) After step c) the MS shall indicate that the FDN disabling procedure has been successful.
3) After step d) the MS shall allow call set-up and send the requested number across the air interface.
4) After step e) the value of bit 1 of byte 12 in the response dat... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19 Phase identification | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.1 Definition | The phase of the SIM is indicated in the Elementary File EFPHASE. This allows the ME to identify the phase of the SIM and adapt its functionality accordingly. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.2 Conformance requirement | The phase of the card shall be determined as part of the initialization procedure.
Reference:
3GPP TS 11.11, subclauses 10.2.16 and 11.2.1. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.3 Test purpose | To verify that the ME requests the SIM phase as part of the initialization procedure. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.4.1 Initial conditions | The ME is connected to the SIM simulator, and powered off.
The default values are used. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.4.2 Procedure | a) The mobile is powered on.
b) The SIM simulator monitors the SIM initialization procedure. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.19.5 Test requirement | The ME shall request the phase of the SIM as part of the initialization procedure. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20 SIM presence detection | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.1 Definition | The presence of the SIM is an essential requirement for setting up and maintaining a call. The ME detects the presence of the SIM electronically. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.2 Conformance requirement | To ensure that the SIM has not been removed during a card session, the ME shall send STATUS commands within all 30 second periods of inactivity on the SIM‑ME interface during a call. Inactivity in this case is defined as starting at the end of the last communication or the last issued STATUS command. If the ME detects... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.3 Test purpose | 1. To verify that there are no periods of inactivity on the SIM‑ME interface greater than 30 seconds during a call.
2. To verify that the ME terminates a call within 5 s at the latest after having received a wrong response to the STATUS command. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.4.1 Initial conditions | The ME is connected to the SIM-simulator.
All elementary files are coded as default. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.4.2 Procedure | a) A call is set up using the generic call setup.
b) The SIM simulator monitors the periods of inactivity on the SIM-ME interface.
c) After 3 minutes, the call is cleared.
d) A call is set up using the generic call setup.
e) After one minute after the call was successfully set up, the SIM simulator responds to a STATUS... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.20.5 Test requirements | 1. During step b), the time periods of inactivity shall not be longer than 30 s.
2. After step e), the ME shall terminate the call within 5 s at the latest after having received the wrong response to the STATUS command. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21 Advice of Charge (AoC) | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1 AoC not supported by SIM | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.1 Definition | If the ME under test supports Advice of Charge Charging, it shall still look at the capability of the SIM, before responding to any AoCC information from the network. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.2 Conformance requirement | 1. An MS not supporting AoCC and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONNECT.
2. An MS not supporting AoCC and in the outgoing call / U4 call ... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.3 Test purpose | 1. To verify that an MS not supporting AoCC (where the ME does support AoCC but the SIM does not) and in the outgoing call / U4 call delivered state, on receipt of a CONNECT message containing AoCC information shall acknowledge the CONNECT message but ignore and not acknowledge the AoCC information sent within the CONN... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.4 Method of test | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.4.1 Initial conditions | The ME shall be installed with a SIM or SIM simulator, with all elementary files coded as for the default SIM, 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 dia... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.4.2 Procedure | a) For an MO call in the U4 state the SS transmits CONNECT containing AoCC information.
b) For an MO call in the U4 state the SS transmits FACILITY containing AoCC information.
c) For an MTcall in the U9 state the SS transmits FACILITY containing AoCC information.
d) For an MO call in the U10 state the SS transmits FAC... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.1.5 Test requirement | In all cases, the MS shall ignore the AoCC information sent to it in the Facility information elements as part of the CONNECT/FACILITY messages and not send any AoCC information acknowledgement. It shall be checked for 15 s that the MS does not transmit any AoCC information acknowledgement after the receipt of AoCC inf... |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2 Maximum frequency of ACM updating | |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.1 Definition | During a call, the ACM shall be updated at the end of every interval. The interval length is the greater of either 5 s or the value given by parameter e2. |
683b5b8a98f7b1390ddd5516ea9247a2 | 51.010-1 | 27.21.2.2 Conformance requirement | The ACM shall be incremented when the CCM is incremented or once every 5 s, whichever is the longer period.
Reference:
3GPP TS 02.24, subclause 4.3, part h. |
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 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.