hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.1.3 Test purpose | To verify that the UE will accept and indicate but not store a class 0 message, and that it will accept and indicate a class 0 message if its message store is full.
NOTE: failure of this test in a UE could cause it to reject a class 0 message when its SMS memory becomes full. This could lead to unwanted repetitions bet... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.1.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Whether SMS messages are stored in the USIM and/or the ME.
... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.1.5 Test requirements | After step 7 UE shall accept and indicate but not store a class 0 message.
After step 21 UE shall accept and indicate a class 0 message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2 Test of class 1 short messages | This test shall apply to UEs which support:
- storing of received Class 1 Short Messages; and
- indicating of stored Short Messages. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2.2 Conformance requirement | When a mobile terminated message is class 1, the UE shall send an acknowledgement to the SC when the message has successfully reached the UE and can be stored, either in the ME or in the USIM.
Reference
3GPP TS 23.038 clause 4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2.3 Test purpose | This procedure verifies that the UE acts correctly on receiving a class 1 message, i.e. that it stores the message in the ME or USIM and sends an acknowledgement (at RP and CP-Layer). |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the UE message store shall be empty;
- for storing of class 1 Short Messages, the UE shall be set up to store Short Messages in the ME memory (by way of MMI, as described in ICS/IXIT... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.2.5 Test requirements | After step 7 UE shall store the message in the ME or USIM and send an acknowledgement. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3 Test of class 2 short messages | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3.1 Definition | Class 2 Short Messages are defined as USIM specific, and the UE shall ensure that a message of this class is stored on the USIM. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3.2 Conformance requirement | When a mobile terminated message is Class 2, the UE shall ensure that the message has been correctly transferred to the SMS data field in the USIM before sending an acknowledgement to the SC. The UE shall return a "protocol error, unspecified" error message if the short message cannot be stored in the USIM and there is... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3.3 Test purpose | This procedure verifies that the UE acts correctly on receiving a class 2 message, i.e. that it stores the message correctly in the USIM, and if this is not possible, returns a protocol error message, with the correct error cause, to the network.
There are 2 cases:
1) if the UE supports storing of short messages in the... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the ME message store shall be empty;
- the ME shall be connected to the USIM simulator. The following shall be present in the USIM simulator:
- EFSMS with at least two free records a... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.3.5 Test requirements | After step 10 UE shall confirm that the short message is stored in the USIM and send CP-DATA containing RP-ACK RPDU.
After step 24 UE shall confirm that the short message cannot be stored in the USIM and send CP-DATA containing RP-ERROR RPDU. If UE supports storing of short message in the ME, the error cause of RP-ERRO... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.5.4 Test of class 3 short messages | For further study. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.6 Test of short message type 0 (R99 and REL-4 UE) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.6.1 Definition and applicability | This tests that the UE correctly acknowledges the receipt of the short message type 0 to the SC in Packet Switched mode. It is highly recommended that the UE discards the contents of the short message type 0.
This test shall apply to all R99 and REL-4 UEs supporting receipt of short messages in PS mode. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.6.2 Conformance requirement | When a mobile terminated message is type 0, the UE shall acknowledge receipt of the short message to the SC but may discard its contents.
Note: It is highly recommended that the UE discards the type 0 short message. This means that the UE is able to receive the type 0 short message irrespective of whether there is memo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.6.3 Test purpose | To verify that the UE will acknowledge receipt of the short message to the SC. The UE should discard its contents.
NOTE: failure of this test in a UE could cause it to reject a type 0 message when the network is trying to reach the UE. This could lead to unwanted repetitions between the UE and the service centre. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.6.4 Method of test | Initial conditions
System Simulator:
1 cell, default parameters.
User Equipment:
the UE shall be in GMM-state "GMM-REGISTERED";
Related ICS/IXIT Statements
Support for Short Message MT/PP.
The value of timer TC1M.
Foreseen Final State of UE
Idle, updated.
Test Procedure
The SS sends a type 0 message by using the method... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7 Test of the replace mechanism for SM type 1-7 | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7.2 Conformance requirement | On receipt of a short message, the UE shall check to see if the associated Protocol Identifier contains a Replace Short Message Type code. If such a code is present, then the UE will check the associated originating address (TP-OA) and replace any existing stored message having the same Protocol Identifier code and ori... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7.3 Test purpose | This procedure verifies the correct implementation of the replace mechanism for Replace Short Messages. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
The value of timer TC1M.
Test procedure
a) Two different numbers n and m are drawn r... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.7.5 Test requirements | After step 61 only the Short Messages delivered in step 7, 19 and 55 shall be retrieved and indicated. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8 Test of the reply path scheme | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8.2 Conformance requirement | When a replying UE receives an original mobile terminated short message it has:
- originating SME = TP-Originating Address in the SMS-DELIVER TPDU;
- original SC = RP-Originating Address in the RP-MT-DATA.
When submitting the reply mobile originated short message, the replying UE should use parameters as follows:
- TP-... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8.3 Test purpose | This procedure verifies that the UE is able to send a Reply Short Message back to the correct originating SME even if in the meantime it receives another Short Message. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the UE message store shall be empty.
Related ICS/IXIT Statements
Support for Short message MT/PP.
Support for Short message MO/PP.
The value of timer TC1M.
Test procedure
a) The SS d... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.8.5 Test requirements | After step 35 UE shall send the Reply Short Message corresponding to one of two previously received short messages.
After step 52 UE shall send the Reply Short Message corresponding to the other of two previously received short messages. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.9 Multiple SMS mobile originated | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.9.1 UE in idle mode | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.9.2 UE in active mode | This test is not applicable for R99. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10 Test of capabilities of simultaneously receiving a short message whilst sending a mobile originated short message | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10.2 Conformance requirements | An active UE shall be able to receive a short message TPDU (SMS-DELIVER) at any time, independently of whether or not there is an SMS mobile originated call (SMS-SUBMIT or SMS-COMMAND) in progress.
References
3GPP TS 23.040 clause 3.1, 9.2.3.16.
3GPP TS 24.011 clause 3.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10.3 Test purpose | The test verifies that the UE is capable of simultaneously receiving a network originated SM whilst sending a mobile originated SM. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10.4 Method of test | Initial Conditions
- System simulator:
- 1 cell, default parameters.
- User Equipment:
- the UE shall be in GMM-state "GMM-REGISTERED";
- the SMS message storage shall be empty.
Related ICS/IXIT Statements
Support for Short message MO/PP and MT/PP.
Support for state PDP-ACTIVE of session management.
The value of timer... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.2.10.5 Test requirements | After step 12 UE shall correctly receive the SM and indicate that a message has arrived. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3 Short message service cell broadcast | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3.1 Definition | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3.2 Conformance requirements | In idle mode, the UE has the ability to ignore repeated broadcasts of CBS messages already received (the message has not changed since it was last broadcast i.e. sequence number has not changed within the message's indicated geographical area);
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BM... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3.3 Test purpose | This test verifies that an UE supporting SMS-CB is able to receive SMS-CB messages and is able to ignore repeated broadcasts of CBS messages. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3.4 Method of test | Initial conditions
- System Simulator:
- 1 cell, default parameters;
- the SS provides a BCCH/CCCH to support the UE in idle mode;
- periodic location updating is disabled.
- User Equipment:
- the UE shall be in the idle updated state.
Related ICS/IXIT Statements
Support for short message transmission cell broadcast.
T... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.3.5 Test requirements | In consequence of test the UE shall ignore third message and store two messages.
16.3a Short message service cell broadcast Discontinuous Reception (DRX)
16.3a.1 Definition
16.3a.2 Conformance requirements
A UE supporting Cell Broadcast Service (CBS) shall be capable to receive BMC messages in the Idle mode.
In idle mo... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.4 Default message contents: | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.4.1 Default message contents for SM-CP protocol | CP-DATA
Information element
Comment Value
Protocol Discriminator
SMS messages ("1001"B)
Transaction Identifier
TIO
any value from the set {0, ..., 6}
TI flag
0
Message type
00000001
CP-User data
length indicator
RPDU
max 248 octets
CP-ACK
Information element
Comment Value
Transaction Identifier
TIO
TI flag
Message type... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.4.2 Default message contents for SM-RP protocol | RP-DATA
Information element
Comment Value
RP-Message Type
"001"B (SS->UE) or "000"B(UE->SS)
RP-Message Reference
see 3GPP TS 24.011, clause 8.2.3
RP-Originator Address
see 3GPP TS 24.011, clause 8.2.5.1
RP-Destination Address
see 3GPP TS 24.011, clause 8.2.5.2
RP-User Data
see 3GPP TS 24.011, clause 8.2.5.3
Length ind... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 16.4.3 Default message contents for SM-TP protocol | SMS DELIVER TPDU
Information element
Comment Value
TP-MTI
SMS DELIVER "00"B
TP-MMS
more messages are waiting in SC "0"B
TP-RP
no reply path "0"B
TP-UDHI
TP-UD contains only the SM "0"B
TP-SRI
no status report returned "0"B
TP-OA
an international number coded E.164
TP-PID
default "00000000"B
TP-DCS
default alphabet "00... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17 Specific features | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1 Test of autocalling restrictions | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.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... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2 Constraining the access to a single number (TS 22.001 category 3) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2.1 Definition | This test checks that when an auto-dialled call to a B-party number fails due to a category 3 cause, only one retry to that number is permitted.
During this test the SETUP messages shall contain the same B-party number.
No manual intervention shall be performed except to initiate and end the test. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2.2 Conformance requirement | A repeat call attempt may be made when a call attempt is unsuccessful for the reasons listed below (as defined in TS 24.008).
These reasons are classified in three major categories:
1. "Busy destination";
2. "Unobtainable destination - temporary";
3. "Unobtainable destination - permanent/long term".
NOTE: Cause values ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2.3 Test purpose | To ensure the correct behaviour of the UE to TS 22.001 Category 3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2.4 Method of test | Initial condition.
There shall be no numbers in the list of blacklisted numbers in the UE. 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 UE. The autocalling ... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.2.5 Test requirements | The time between step 4 and 7 must be minimum 5 s.
No further call attempt shall be made after step 9. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3 Constraining the access to a single number (TS 22.001 categories 1 and 2) | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3.1 Definition | This test checks that when an auto-dialled call to a B-party number fails due to a category 2 cause, the time between of retries complies with the requirements, and the number of retries does not exceed that declared by the UE manufacturer, and is never more than 10.
During this test the SETUP messages shall contain th... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3.2 Conformance requirement | The UE must fulfil the requirements for category 1 and 2, see clause 17.1.2.2.
Reference:
3GPP TS 22.001 annex E. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3.3 Test purpose | To ensure the correct behaviour of the UE to TS 22.001 Categories 1 and 2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3.4 Method of test | Initial condition
There shall be no numbers in the list of blacklisted numbers in the UE. 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 UE. The autocalling function is invoked for the B-par... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.3.5 Test requirements | 1: At the first re-attempt the time between step 4 and 7 must be minimum 5 sec. 2: At the 2nd, 3rd and 4th re-attempt the time between step 4 and 7 must be minimum 1 min. 3: At the 5th to 10th re-attempt the time between step 4 and 7 must be minimum 3 min.
The UE shall not make more than maximum 10 re-attempts. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4 Behaviour of the UE when its list of blacklisted numbers is full | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4.1 Definition and applicability | This tests that the UE does not allow autocalling 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 IXIT statement, is M.
This test shall only apply to UE that are capable of autocalling more than M B-party numbers. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4.2 Conformance requirement | The number of B numbers that can be held in the blacklist is at the manufacturers discretion but there shall be at least 8. However, when the blacklist is full the UE shall prohibit further automatic call attempts to any one number until the blacklist is manually cleared at the UE in respect of one or more B numbers.
R... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4.3 Test purpose | To ensure the correct behaviour of the UE when its list of blacklisted numbers is full. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4.4 Method of test | Initial condition
The list of blacklisted numbers, in the UE, shall be full. This may be achieved as described in the procedure in clause 17.1.2, applied to M B-party numbers.
Related ICS/IXIT Statement(s)
PICS: TBD.
PIXIT: Description of auto calling management:
- selection of the auto calling;
- indication that the c... |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.1.4.5 Test requirements | The UE must not initiate a call. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2 Location Services | The test cases for Location Services (LCS) are provided in 3GPP TS 37.571-2 [49], clause 6.. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.1 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.2 Assisted GPS Network Induced Tests | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.2.1 LCS Network Induced location request/ UE-Based GPS/ Emergency Call / with USIM | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.1.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.2.2 LCS Network Induced location request/ UE-Based GPS/ Emergency Call / without USIM | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.1.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.2.3 LCS Network induced location request/ UE-Assisted GPS/ Emergency call/ With USIM | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.1.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.2.4 LCS Network induced location request/ UE-Assisted GPS/ Emergency call/ Without USIM | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.1.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3 Assisted GPS Mobile Originated Tests | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.1 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.2 LCS Mobile originated location request/ UE-Based GPS/ Position estimate request/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.3 LCS Mobile originated location request/ UE-Based or UE-Assisted GPS/ Assistance data request/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.4 LCS Mobile originated location request/ UE-Assisted GPS/ Position Estimate/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.5 Void | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.6 LCS Mobile originated location request/ UE-Based GPS/ Transfer to third party/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.7 LCS Mobile originated location request/ UE-Assisted GPS/ Transfer to third party/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.5. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.8 LCS Mobile originated location request/ UE-Based or UE-Assisted GPS/ Assistance data request/ Failure | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.6. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.3.9 LCS Mobile originated location request/ UE-Based GPS/ Position estimate request/ Failure | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.2.7. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4 Assisted GPS Mobile Terminated Tests | |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.1 LCS Mobile terminated location request/ UE-Based GPS | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.1. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.2 LCS Mobile-terminated location request/UE-Based GPS/ Request for additional assistance data/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.2. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.3 LCS Mobile-terminated location request/UE-Based GPS/ Failure – Not Enough Satellites | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.3. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.4 LCS Mobile terminated location request/ UE-Assisted GPS/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.4. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.5 LCS Mobile terminated location request/ UE-Assisted GPS/ Request for additional assistance data/ Success | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.5. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.6 LCS Mobile terminated location request/ UE-Based GPS/ Privacy Verification/ Location Allowed if No Response | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.6. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.7 LCS Mobile terminated location request/ UE-Based GPS/ Privacy Verification/ Location Not Allowed if No Response | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.7. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.8 LCS Mobile terminated location request/ UE-Assisted GPS/ Privacy Verification/ Location Allowed if No Response | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.8. |
4251e2eb3ecde7c73983ce7a4175ddf3 | 34.123-1 | 17.2.4.9 LCS Mobile terminated location request/ UE-Assisted GPS/ Privacy Verification/ Location Not Allowed if No Response | This test case is provided in 3GPP TS 37.571-2 [49], sub-clause 6.1.3.9. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.