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.2 IP Header Compression and PID assignment
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1 UE in RLC AM
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1 Transmission of uncompressed Header
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1.1 Definition and applicability
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. This function is used for conveyance of data between users of PDCP services. 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall b...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1.3 Test purpose
The test case consists of two test procedures: The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used for uncompressed IP header packets,...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1.4 Method of test
Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured. Test procedure 2: No IP header compression is configured. Related ICS/IXIT Statement(s) Support of PS – Yes/No PIXIT: Test_PDCP_TCP/I...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.1.5 Test requirements
Test requirements 1 (Proc 1): Transmission of uncompressed IP header packets using PDCP Data PDU The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negoti...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2 Transmission of compressed Header
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2.1 Definition and applicability
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol RFC 2507.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. This function is used for conveyance of data between users of PDCP services. 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall b...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2.3 Test purpose
1. To verify, that the UE transmits and receives in acknowledged mode (RLC AM) TCP/IP and UDP/IP data packets by using IP header compression protocol as described in RFC2507 as configured by higher layers. 2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID v...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2.4 Method of test
Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and IP header compression is configured. Related ICS/IXIT Statement(s) Support of IP header compression protocol RFC 2507 - YES/NO. Support of PS – Yes/No PIXIT: Test_PDCP_TCP/IP_Packet1 PIXIT: T...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.1.2.5 Test requirements
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled with the correct compression protocol. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2 UE in RLC UM
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1 Transmission of uncompressed Header
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. This function is used for conveyance of data between users of PDCP services 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1.3 Test purpose
The test case consists of two test procedures: The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used for uncompressed IP header packets,...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1.4 Method of test
Initial conditions UE is in Idle mode. Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured. Test procedure 2: no IP header compression is configured. Related ICS/IXIT Statement(s) Support of PS – Yes/No PIXIT: Test_PDCP_TCP/IP_Packet1 PIXIT: Test_PDCP_UDP/IP_Packet1 Proc 1: Test proced...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.1.5 Test requirements
Test requirements 1 (Proc 1): Transmission of uncompressed IP header packets using PDCP Data PDU The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negoti...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2 Transmission of compressed Header
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol RFC 2507.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. This function is used for conveyance of data between users of PDCP services. 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall b...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2.3 Test purpose
1. To verify, that the UE transmits and receives in unacknowledged mode (RLC UM) TCP/IP and UDP/IP data packets by using IP header compression protocol as described in RFC2507 as configured by higher layers. 2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2.4 Method of test
Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured. Related ICS/IXIT Statement(s) Support of IP header compression protocol RFC 2507 - YES/NO Support of PS – Yes/No PIXIT: Test_PDCP_TCP/IP_Packet1 PIXIT:...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.2.5 Test requirements
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled with the correct compression method. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be re...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3 Extension of used compression methods
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol: RFC 2507.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. Transmission of user data means that PDCP receives PDCP SDU from the NAS and forwards it to the RLC layer and vice versa; 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header co...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3.3 Test purpose
1. To verify, that the UE is able to handle an extended PID value allocation table by header compression protocol IETF RFC 2507 after PDCP reconfiguration as configured by RRC.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3.4 Method of test
Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured. Related ICS/IXIT Statement(s) Support of IP header compression protocol RFC 2507 - YES/NO Support of PS – Yes/No PIXIT: Test_PDCP_TCP/IP_Packet1 PIXIT:...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.3.5 Test requirements
After PDCP reconfiguration, the UE shall return the TCP/IP data packets as indication, that the extension of used optimisation method are applied by UE. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by S...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4 Compression type used for different entities
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.1 Definition and applicability
Applicable only for an UE supporting the establishment of more than one PDCP entity in parallel, i.e. it shall be possible to configure more than one Radio Bearer Loop Back entities (each PDCP entity are assigned via PDCP-SAP to its own Radio Bearer Loop Back entity). Applicable for all UEs supporting two Radio Bearers...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions: - transfer of user data. This function is used for conveyance of data between users of PDCP services. 2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall b...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.3 Test purpose
1. To verify, that a configured IP header compression protocol are applied to compress and decompress TCP/IP data packets by several PDCP entities in parallel, if more than one entities are established, i.e. the UE uses the same PID to transmit two TCP/IP data packets with the same content in parallel using two Radio B...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.4 Method of test
NOTE: For this test case, the SS shall be configured to handle more than one received PDCP messages. Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and IP header compression is configured for both PDCP entities. Related ICS/IXIT Statement(s) ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.5 Test requirements
The UE shall return both TCP/IP data packets as indication that the previous received data packets associated with the same PID value are handled in parallel with the same decompression protocol. This verifies, that more than one PDCP configuration on UE side using the same compression protocol is able to apply it in p...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.4.6 Combined PDCP Acknowledged and Unacknowledged mode configuration
This configuration is based on the interactive or background / UL:64 DL 64 kbps / PS RAB. The SRB configurations are UL:3.4 DL:3.4 kbps for DCCH aligned to this combined RABs are described for SRB DL 3.4 kbps in TS 34.108, clause 6.10.2.4.1.2.2 and for SRB DL 3.4 kbps in TS 34.108, clause 6.10.2.4.1.2.1. The TFCS refer...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5 Reception of not defined PID values
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity, which applies PDCP Data PDU if no IP header compression protocol, is negotiated. The UE shall not forward...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5.2 Conformance requirement
1. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to: - identify the correct header compression protocol; and - distinguish different types of header compression packets within a header compression protocol. 2. If a PDCP ent...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5.3 Test purpose
1. To verify, that a UE considers a received PDCP PDU message with not defined PID value as invalid, i.e. such an invalid PDCP PDU is not forwarded to the Radio Bearer entity on UE side. Therefore the UE using test loop mode 1 does not return such data packet to the SS.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5.4 Method of test
Initial conditions UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured. Related ICS/IXIT Statement(s) Support of IP header compression protocol RFC 2507 - YES/NO Support of PS – Yes/No IXIT: Test_PDCP_TCP/IP_Packet1 IXIT: T...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.2.2.5.5 Test requirements
The UE shall return the received TCP/IP data packet using the PDCP Data PDU with PID = 0. The UE shall not return the TCP/IP data packet using the PDCP Data PDU with PID = 1.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3 PDCP sequence numbering when lossless SRNS Relocation
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1 Data transmission if lossless SRNS Relocation is supported
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1.1 Definition and applicability
Applicable for all UEs supporting RLC AM, RLC in-sequence delivery, a Radio Bearer as described in the Common Test Sequences and lossless SRNS relocation. The UE shall be capable to deal with uncompressed TCP/IP data packets and furthermore to establish a PDCP entity which applies PDCP Sequence Numbering
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1.2 Conformance requirement
1. PDCP sequence numbering shall be applied when lossless SRNS Relocation is supported. PDCP Sequence Numbers serve to acknowledge previously transmitted PDCP SDUs prior to relocation. 2. In case of a lossless SRNS Relocation procedure: - the UTRAN should send to the UE the next expected UL_Receive PDCP SN; and - the U...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1.3 Test purpose
1. To verify, that a UE supporting lossless SRNS relocation is able to receive and to send IP data packets by using PDCP Sequence Numbering as configured by higher layers.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1.4 Method of test
Initial conditions SS: 2 cells - Cell A belonging to the valid SRNS (Source SRNS), Cell B belonging to the DRNS (Target SRNS). Both cells are neighbour cells. Cell A has a higher RF power level than Cell B such that an UE shall find Cell A more suitable for service. UE: It is in Idle mode and has selected cell A with v...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.1.5 Test requirements
After having completed lossless SRNS relocation, the UE shall return the received TCP/IP data packet by using PDCP SeqNum PDUs as indication, that it supports lossless SRNS relocation. This verifies, that Sequence Numbering is used for lossless SRNS relocation. An invalid PDU type as well as unconfigured PID values sha...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2 Synchronisation of PDCP sequence numbers
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2.1 Definition and applicability
Applicable for all UEs supporting RLC AM, RLC in-sequence delivery, a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore it shall be capable to use IP Header compression protocol RFC 2507.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2.2 Conformance requirement
The PDCP SeqNum PDU shall be sent by the peer PDCP entities when synchronisation of the PDCP SN is required. (...) Synchronisation of PDCP SN is required after (...) RB reconfiguration. 1. In case of a lossless SRNS Relocation procedure: - the UTRAN should send to the UE the next expected UL_Receive PDCP SN; and - the ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2.3 Test purpose
1. To verify, that the UE supporting lossless SRNS relocation as configured by higher layers is able to handle the "PDCP SeqNum" PDU to synchronize the used PDCP Sequence Number after reconfiguration of the Radio Bearer.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2.4 Method of test
Initial conditions SS: 2 cells - Cell A belonging to the valid SRNS (Source SRNS), Cell B belonging to the DRNS (Target SRNS). Both cells are neighbour cells. Cell A has a higher RF power level than Cell B such that an UE shall find Cell A more suitable for service. UE: It is in Idle mode and has selected cell A with v...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.2.5 Test requirements
After having received the TCP/IP data packet conveyed with the "PDCP SeqNum" PDU, the UE shall return the TCP/IP data packets as indication, that the UE is able to handle a Sequence Number synchronisation. An invalid PDU type as well as unconfigured PID values shall not be received by SS. 7.3.3.3 PDCP Sequence Numberin...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.4 PDCP Sequence Number synchronization – Reception of invalid next expected receive Sequence Number
FFS
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5 UTRAN MOBILITY INFORMATION: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5.2 Conformance requirement
To initiate the procedure UTRAN transmits a UTRAN MOBILITY INFORMATION message to the UE on the downlink DCCH using AM or UM RLC. In case of SRNS relocation, the message is sent using UM RLC only. When the UE receives a UTRAN MOBILITY INFORMATION message, it shall: 1> if the variable PDCP_SN_INFO is non-empty: 2> inclu...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5.3 Test purpose
1. To confirm that the UE that support lossless SRNS relocation, sends the correct expected downlink PDCP sequence number to SS after a successful SRNS relocation. 2. To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS relocation. 3. In the case that ciphering is applie...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5.4 Method of test
Initial Condition System Simulator: 1 cell. UE: PS-DCCH _FACH (state 6-8) as specified in clause 7.4 of TS 34.108. Initial conditions message sequence Step Direction Message Comment UE SS SS executes procedure Activate closed loop mode 1 in CELL_FACH case as specified in clause 7.3.1.2.1.4 Related ICS/IXIT statements -...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.5.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 UTRAN MOBILITY INFORMATION CONFIRM 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, COUNT-I | ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6 Cell Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6.2 Conformance requirement
When the UTRAN receives a CELL UPDATE message, the UTRAN should: 1> in case the procedure was triggered by reception of a CELL UPDATE: 2> if SRNS relocation was performed: 3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH. 2> otherwise: 3> update the START value for each CN domain as maintained in UTRAN (r...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6.3 Test purpose
1. To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell. 2. To confirm that the UE that support lossless SRNS relocation, sends the correct expected downlink PDCP sequence number to SS after a successful SRNS relocation. 3. To confirm that the UE sends calculated...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6.4 Method of test
Initial Condition System Simulator: 2 cells - Cell 1 and 2 are active. UE: PS-DCCH_FACH (state 6-8) as specified in clause 7.4 of TS 34.108. Initial conditions message sequence Step Direction Message Comment UE SS SS executes procedure Activate closed loop mode 1 inCELL_FACH case as specified in clause 7.3.1.2.1.4 Rela...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.6.5 Test requirement
After step 1, UE shall transmit back all the PDCP PDUs sent by the SS to the UE. After step 2, UE shall transmit CELL UPDATE message with the value of IE “Cell update cause” set to “cell reselection”. After step 4, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC which ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7 URA Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7.2 Conformance requirement
When the UTRAN receives a URA UPDATE message, the UTRAN should: 1> in case the procedure was triggered by reception of a URA UPDATE: 2> if SRNS relocation was performed: 3> transmit a URA UPDATE CONFIRM message on the downlink DCCH. If the UE after the state transition remains in CELL_FACH state; and - a C-RNTI is stor...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7.3 Test purpose
1. To confirm that the UE executes a URA update procedure after the successful reselection of another UTRA cell. 2. To confirm that the UE that support lossless SRNS relocation, sends the correct expected downlink PDCP sequence number to SS after a successful SRNS relocation. 3. To confirm that the UE sends calculated ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7.4 Method of test
Initial Condition System Simulator: 2 cells - Cell 1 and 3 are active. UE: PS-DCCH _DCH(state 6-7) in cell 1 as specified in clause 7.4 of TS 34.108. Initial conditions message sequence Step Direction Message Comment UE SS SS executes procedure Activate closed loop mode 1 in CELL_DCH case as specified in clause 7.3.1.2...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.7.5 Test requirement
After step 1, UE shall transmit back all the PDCP PDUs sent by the SS to the UE. After step 2, UE shall transmit URA UPDATE message with the value of IE “URA update cause” set to “change of URA”. After step 4, the UE shall transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC which inclu...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.8.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.8.2 Conformance requirement
1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure: 2> if the transmitted message is a RADIO BEARER RECONFIGURATION: 3> include the IE "New U-RNTI". 2> else: 3> include the IE "Downlink counter synchronisation info". The UE shall: 1> if the received reconfiguration message included the ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.8.3 Test purpose
1. To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a RADIO BEARER SETUP COMPLETE message in the new cell. 2. In the case that ciphering is applied by the network, to confirm that the UE applies the new ciphering algorithm following a successful SRNS relocation.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.8.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.8.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 RADIO BEARER SETUP 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, COUNT-I | radio b...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.9 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.9.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.9.2 Conformance requirement
1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure: 2> if the transmitted message is a RADIO BEARER RECONFIGURATION: 3> include the IE "New U-RNTI". 2> else: 3> include the IE "Downlink counter synchronisation info". The UE shall: 1> if the received reconfiguration message is a RADIO BE...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.9.3 Test purpose
1. To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a RADIO BEARER RECONFIGURATION COMPLETE message in the new cell. 2. In the case that ciphering is applied by the network, to confirm that the UE applies the new ciphering algorithm following a successful SRNS relocation.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.9.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.9.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 RADIO BEARER 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, COUNT-I...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10.2 Conformance requirement
1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure: 2> if the transmitted message is a RADIO BEARER RECONFIGURATION: 3> include the IE "New U-RNTI". 2> else: 3> include the IE "Downlink counter synchronisation info". The UE shall: 1> if the received reconfiguration message included the ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10.3 Test purpose
To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a RADIO BEARER RELEASE COMPLETE message in the new cell.
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10.4 Method of test
Initial Condition System Simulator: 2 cells – Cell 1 and 2 UE: PS -DCCH _DCH (state 6-7) or PS-DCCH_FACH (state 6-8) 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 ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.10.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 RADIO BEARER RELEASE 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, COUNT-I | radio...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11 Transport Channel Reconfiguration for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11.1 Definition
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11.2 Conformance requirement
1> if the reconfiguration procedure is simultaneous with SRNS relocation procedure: 2> if the transmitted message is a RADIO BEARER RECONFIGURATION: 3> include the IE "New U-RNTI". 2> else: 3> include the IE "Downlink counter synchronisation info". The UE shall: 1> if the received reconfiguration message included the ...
4251e2eb3ecde7c73983ce7a4175ddf3
34.123-1
7.3.3.11.3 Test purpose
To confirm that the UE performs a combined hard handover and SRNS relocation and then transmit a TRANSPORT CHANNEL RECONFIGURATION COMPLETE message in the new cell.