hash
stringlengths
32
32
doc_id
stringlengths
5
12
section
stringlengths
5
1.47k
content
stringlengths
0
6.67M
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11.4 Method of test
Initial Condition System Simulator: 2 cells – Cell 1 and 2 UE: PS-DCCH _DCH (state 6-7) as specified in clause 7.4 of TS 34.108, depending on the CN domain(s) supported by the UE. Initial conditions message sequence Step Direction Message Comment UE SS SS executes procedure Activate closed loop mode 1 in CELL_DCH case ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11.5 Test requirement
After step 1, UE shall transmit back all the PDCP PDUs sent by the SS to the UE. After step 3, the UE shall transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message on the uplink DCCH using AM RLC which includes which includes a calculated new START value according to the formula “STARTX' = MSB20 (MAX {COUNT-C, CO...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.4 PDCP configuration testing
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.4.1 PDCP configuration behaviour while RRC Radio bearer setup procedure
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.4.2 PDCP configuration behaviour while RRC Radio bearer release procedure
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.4.3 PDCP configuration behaviour while RRC Cell Update procedure
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.4.4 PDCP configuration behaviour for an invalid RRC configuration
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5 PDCP RoHC testing
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.1 General
These test cases are only applicable for UEs supporting PDCP Rel-4 RoHC functions (based on IETF RFC 3095) as defined in TS 25.323 Release 4 onwards.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.1.1 Preamble for extended RoHC conformance testing
If PDCP RoHC feature is supported, the following message contents are used if different from TS 34.108, clause 9 Contents of CONNECTION SETUP message: Information Element Value/remark Capability update requirement - UE radio access capability update requirement TRUE - System specific capability update requirement list ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2 Compression / Decompression of a UDP/RTP/IPv6 header flow
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.1 UDP/RTP/IPv6 Unacknowledged - unidirectional Mode (U-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.2 UDP/RTP/IPv6 Unacknowledged - Normal U-mode Transmission (without ack)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.3 UDP/RTP/IPv6 Unacknowledged - Bi-directional Optimistic Mode (O-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.4 UDP/RTP/IPv6 Unacknowledged - Bi-directional Reliable Mode (R-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.5 UDP/RTP/IPv6 Unacknowledged - Transition Mode
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.6 UDP/RTP/IPv6 Unacknowledged - Flow Parameters
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.7 UDP/RTP/IPv6 Acknowledged - unidirectional Mode (U-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.8 UDP/RTP/IPv6 Acknowledged - Normal U-mode Transmission (without ack) using the UE as compressor
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.9 UDP/RTP/IPv6 Acknowledged - Bi-directional Optimistic Mode (O-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.10 UDP/RTP/IPv6 Acknowledged - Bi-directional Reliable Mode (R-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.11 UDP/RTP/IPv6 Acknowledged - Transition Mode
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.2.12 UDP/RTP/IPv6 Acknowledged - Flow Parameters
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3 ROHC Profile 2,3 and 4. Compression / Decompression of a UDP/IPv6 or ESP/IPv6 or IPv6 header flow
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.1 UDP/IPv6 or ESP/IPv6 or IPv6 Unacknowledged - unidirectional Mode (U-Mode)
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2 UDP/IPv6 or ESP/IPv6 or IPv6 Unacknowledged - Normal U-mode Transmission (without ack)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2.1 Definition and applicability
Applicable for all UEs supporting PS PDCP ROHC header compression as describe in the RFC 3095. In this test case, compression unit of the UE and decompression unit of the UE is checked. The UE shall support Profile 2 (UDP/IPv6) streams.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2.2 Conformance requirement
Reference(s) TBD, refer to IETF RFC 3095 clause 5.3.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2.3 Test purpose
To verify the unidirectional mode in the UE Decompressor unit without using acknowledgements.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2.4 Method of test
Initial conditions Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1) and ROHC negotiation has been established. Compressor parameters as negotiated for UE and SS compression unit: Reset: Non L:3 K_1/n_1: 1 K_2/n_2: 1 Timer1: 256 packets Timer2: 256 packets M_1: 4 M_2: 4 ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.5.3.2.5 Test requirements
1. At step d), the UE has to loop back received IR packets to the SS decompressor in order to verify, that the decompression state was increased from No-Context state to Static-Context state (U-Mode). 2. At step f), the UE has to loop back received IR-DYN packets to the SS decompressor in order to verify, that the deco...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6 PDCP RoHC performance testing
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.1 General
IETF RFC3095 "RObust Header Compression (ROHC)" [40] and RFC 4815: "RObust Header Compression (ROHC): Corrections and Clarifications to RFC 3095” [41] is the IP header compression method specially designed for real time IP services over wireless links. ROHC is specified as part of the Rel-4 of UTRAN as one of the compr...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.1.1 Generic ROHC performance test procedure
Step Direction Message Comments UE SS 1 <-- SYSTEM INFORMATION (BCCH) Broadcast 2 <-- PAGING TYPE 1 (PCCH) Paging (PS domain, P-TMSI) 3 --> RRC CONNECTION REQUEST (CCCH) RRC 4 <-- RRC CONNECTION SETUP (CCCH) RRC 5 --> RRC CONNECTION SETUP COMPLETE (DCCH) RRC 6a --> SERVICE REQUEST (DCCH) GMM 6b <-- SECURITY MODE COMMA...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2 Base test of ROHC RTP O-mode compressor
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2.1 Definition and applicability
The purpose of the base test is to verify that the compressor implements an active and efficient compression for a regular IP/UDP/RTP packet stream, i.e. that it makes use of the most efficient compressed packet formats provided by ROHC RTP [40] for O-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2.2 Conformance requirement
This subclause defines performance test cases for ROHC. The ROHC profile within scope is profile 0x0001 for compression of RTP/UDP/IP headers only. This subclause is not meant to bring incoherent limitations to implementations, and is not meant to create a sub-specification of RFC 3095 [40] either, as a consequence of ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2.3 Test purpose
To verify that the ROHC compressor successfully transfers to O-mode operation and makes use of efficient compressed packet formats available to ROHC RTP.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.2.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.2. Table 7.3.6.2: Test Requirement for ROHC RTP O-mode compressor Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= N-1 44 octets 68 octets SN >= N 5 octets 5 octets With N value equal to 4 (which is sm...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3 Base test of ROHC RTP R-mode compressor
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3.1 Definition and applicability
The purpose of the base test case is to verify that the compressor properly implements compression for a well-behaved IP/UDP/RTP packet flow, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [40] when operating in R-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3.2 Conformance requirement
This subclause defines performance test cases for ROHC. The ROHC profile within scope is profile 0x0001 for compression of RTP/UDP/IP headers only. This subclause is not meant to bring incoherent limitations to implementations, and is not meant to create a sub-specification of RFC 3095 [40] either, as a consequence of ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3.3 Test purpose
To verify that the ROHC compressor successfully transfers to R-mode operation and makes use of efficient compressed packet formats available to ROHC RTP.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.3.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.3.2 Table 7.3.6.3.2: Test Requirement for ROHC RTP R-mode compressor Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= N-1 44 octets 68 octets N <= SN <= 5 5 octets 5 octets 6 <= SN <= x 9 octets 9 octe...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4 Re-establishment of TS function after DTX in O-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4.1 Definition and applicability
The purpose of the TS re-establishment test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it uses efficient header formats available to ROHC RTP [40] when operating in O-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4.2 Conformance requirement
The outline of each test case follows the same format with respect to the input sequences and the requirements Test 1a and 1b are base tests using a well-behaving flow of packets as one of the inputs. All subsequent tests are based on test 1a or test 1b, each with specific test events added to the packet flow of the ba...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4.3 Test purpose
To verify that the ROHC compressor re-establishes the proper TS value after a DTX period, i.e. that it uses efficient header formats available to ROHC RTP when operating in O-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.4.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.4. Table 7.3.6.4: Test Requirement for ROHC Test 7.3.6.4 Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= 19 See Test 1a (Test 7.3.6.2 in TS 34.123-1) 20 <= SN <= 19 + N 30 <= SN <= 29 + N 10 octets 10...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.5 Re-establishment of TS function after DTX in R-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.5.1 Definition and applicability
The purpose of the TS (Timestamp) re-establishment test case is to verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it uses the efficient header formats available to ROHC RTP [40] when operating in R-mode. 7.3.6.5.2 Conformance requirement This subclause defines performance te...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.5.3 Test purpose
To verify that the compressor re-establishes the proper TS value after a DTX period, i.e. that it uses the efficient header formats available to ROHC RTP when operating in R-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.5.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.5.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.5.1 Table 7.3.6.5.1: Test Requirement for Re-establishment of TS function after DTX in R-mode Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= 19 See Test 1b (Test case 7.3.6.3 in TS 34.123-1) 20 <= SN...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6 Compressor response to single lost packets in O-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6.1 Definition and applicability
Same as in 34.123-1 clause 7.3.6.2.1.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6.2 Conformance requirement
Same as in 34.123-1 clause 7.3.6.2.2.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6.3 Test purpose
The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6.4 Method of test
The method is the same as in 34.123-1 clause 7.3.6.2.4 except that test packets with SN 20, 30 and 40 are removed from the sequence.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.6.5 Test requirements
The maximal compressed header overhead shall be the same as in 34.123-1 clause 7.3.6.2.5.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7 Compressor response to single lost packets in R-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7.1 Definition and applicability
Same as in 34.123-1 clause 7.3.6.3.1.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7.2 Conformance requirement
Same as in 34.123-1 clause 7.3.6.3.2.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7.3 Test purpose
The purpose of this test is to verify that the compressor does not panic just because there is a single missing packet, i.e. the compressed packet size should not increase due to such events
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7.4 Method of test
The method is the same as in 34.123-1 clause 7.3.6.3.4 except that test packets with SN 20, 30 and 40 are removed from the sequence.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.7.5 Test requirements
The maximal compressed header overhead shall be the same as in 34.123-1 clause 7.3.6.3.5.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8 TS function during DTX with varying delta in O-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8.1 Definition and applicability
The purpose of this test case is to verify that the compressor properly handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses efficient header formats available to ROHC RTP [40] when operating in O-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8.2 Conformance requirement
The outline of each test case follows the same format with respect to the input sequences and the requirements Test 1a and 1b are base tests using a well-behaving flow of packets as one of the inputs. All subsequent tests are based on test 1a or test 1b, each with specific test events added to the packet flow of the ba...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8.3 Test purpose
To verify that the ROHC compressor properly handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses efficient header formats available to ROHC RTP when operating in O-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.8.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.8. Table 7.3.6.8: Test Requirement for ROHC Test 7.3.6.8 Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= 19 See Test 1a (Test 7.3.6.2 in TS 34.123-1) 20 <= SN <= 22 + N 30 <= SN <= 34 + N 40 <= SN <= ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.9 TS function during DTX with varying delta in R-mode
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.9.1 Definition and applicability
The purpose of this test case is to verify how efficiently the compressor handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses the efficient header formats available to ROHC RTP [40] when operating in R-mode. ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.9.3 Test purpose
To verify how efficiently the compressor handles variations in the function between the TS value and the SN during and after a DTX period, during which SID packets are sent periodically, i.e. that it uses the efficient header formats available to ROHC RTP when operating in R-mode.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.9.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.9.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.9.1 Table 7.3.6.9.1: Test Requirement for TS function during DTX with varying delta in R-mode Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= 19 See Test 1b (Test case 7.3.6.3 in TS 34.123-1) 20 <= SN...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10 SRNS relocation for ROHC RTP O-mode compressor
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10.1 Definition and applicability
The purpose of this test case is to verify that the compressor does not interrupt efficient header compression upon reception of the indication about SRNS relocation being performed, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [40] when operating in O-mode when data transmission ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10.2 Conformance requirement
The header compression context relocation is performed by the decision of upper layers in source RNC based on the UE radio capabilities. The decision is done independently every time the SRNS relocation occurs and is specific for each header compression protocol. It is indicated to UE as a part of the SRNS relocation s...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10.3 Test purpose
To verify that the compressor does not interrupt efficient header compression upon reception of the indication about SRNS relocation being performed, i.e. that it makes use of efficient compressed packet formats available to ROHC RTP [40] when operating in O-mode when data transmission is resumed after SRNS relocation....
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10.4 Method of test
Initial conditions User Equipment: The UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Execute the generic ROHC performance test procedure for a mobile terminating packet switched session according to clause 7.3.6.1.1. Profile 0x0001 for compression of RTP/UDP/IP headers only is used N=...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.6.10.5 Test requirements
The average compressed header size shall not exceed the limits specified in Table 7.3.6.10. Table 7.3.6.10: Test Requirement for SRNS relocation for ROHC RTP O-mode compressor Average Compressed Header Size, IPv4 Average Compressed Header size, IPv6 SN <= N-1 44 octets 68 octets N <= SN <= 9 5 octets 5 octets 60 <= SN ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7 PDCP AMR Data PDU testing
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1 PDCP AMR Data PDU testing
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1.1 Definition and applicability
Applicable for all UEs supporting CS Voice over HSPA and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with AMR data PDU and to correctly set the value of the CS counter.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1.2 Conformance requirement
The Packet Data Convergence Protocol shall perform the following functions: - header compression and decompression of IP data streams (e.g., TCP/IP and RTP/UDP/IP headers for IPv4 and IPv6) at the transmitting and receiving entity, respectively. - transfer of user data. This function is used for conveyance of data betw...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1.3 Test purpose
1. To verify that the UE transmits and receives AMR Data PDU in unacknowledged mode (RLC UM) as configured by higher layers. 2. To verify that the UE includes the CS counter and sets it to the first to fifth LSBs of the CFN at which the packet has been received from higher layers.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1.4 Method of test
Initial conditions UE is in Idle mode (state 2 or state 7) as specified in clause 7.4 of TS 34.108. Related ICS/IXIT Statement(s) Support of CS Voice over HSPA (Yes/No) Test procedure a) The SS setups a circuit switched session including radio bearer and UE test loop mode 1 in RLC UM using Common test procedures for mo...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.1.5 Test requirements
After having received the AMR data packet conveyed with the "PDCP AMR Data" PDU, the UE shall return the data packets as indication that the previous packets have been received and handled correctly (PDCP AMR Data PDU). The CS counter in the PDCP AMR Data PDUs received from the UE shall be set to the first to fifth LSB...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.2 PDCP Unrecoverable Error Detection
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.2.1 Definition and applicability
Applicable for all UEs supporting CS Voice over HSPA and a Radio Bearer as described in the Common Test Sequences. 7.3.7.2.2 Conformance requirement Length: 3 bits. The PDU type field indicates the PDCP Data PDU type. Bit PDU Type 000 PDCP Data PDU (Table 7) 001 PDCP SeqNum PDU (Table 8) 010 PDCP AMR Data PDU (Table 9)...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.2.3 Test purpose
1. To verify that the UE discards PDCP PDUs with invalid header. 2. To verify that UE transmits CELL UPDATE with cause "radio link failure" when UE receives consecutive PDCP PDUs with the wrong header.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.2.4 Method of test
Initial conditions UE is in Idle mode (state 2 or state 7) as specified in clause 7.4 of TS 34.108. Related ICS/IXIT Statement(s) Support of CS Voice over HSPA Test procedure a) The SS setups a circuit switched session including radio bearer and UE test loop mode 1 in RLC UM using common test procedures for mobile term...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.7.2.5 Test requirements
After receiving 2, 3 or 4 consecutive PDCP PDUs with invalid PDU type the UE shall transmit CELL UPDATE with cause value "radio link failure" After receiving the AMR data packets conveyed with a valid header, the UE shall successfully loop back all the data packets
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.4 BMC
General For BMC testing, the UE manufacturers shall define CB data as PIXIT (CB-Data 1 and 2) for different CB message types and for CB Data41 (ANSI-41 data) and it shall describe how the reception is indicated in a clear way on UE side. Only Cell Broadcast Services (CBS) as distributed BMC service is applied. For a UE...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.4.1 BMC RAB + SRBs for CCCH + SRB for DCCH + SRB for BCCH