7.3.3 PDCP sequence numbering when lossless SRNS Relocation
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.3.3.1 Data transmission if lossless SRNS Relocation is supported
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
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 UE shall send to the UTRAN the next expected DL_Receive PDCP SN.
This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities.
Reference(s)
TS 25.323 clause 5.4.1.1
TS 25.323 clause 5.4.1.3.
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.
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 valid SRNS (Source SRNS). Usage of "PDCP Data" PDU, PDCP SeqNum PDU and no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of lossless SRNS Relocation – YES/NO
Support of PS – Yes/No
IXIT: Test_PDCP_TCP/IP_Packet1
IXIT: Test_PDCP_TCP/IP_Packet2
Test procedure
a) The SS setups a packet switched session including Radio Bearer and UE test loop mode 1 in RLC AM and in-sequence delivery using Common test procedures for mobile terminated PS switched sessions in Cell A. The RLC buffer discharge mode shall be set to "no discard". Usage of "PDCP Data" PDU, support of lossless SRNS relocation and no IP header compression has been configured by higher layers. The PDCP SN window size has been negotiated by RRC.
b) The SS sends a TCP/IP data packet (no compression packet type), PID=0.
c) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
d) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet shall be identical with the data as sent before.
e) The SS starts to broadcast BCCH messages on the primary CPICH in cell B with a power level higher than in cell A. The UE shall chose cell B to be more suitable for service and hence perform a cell reselection.
f) After completion of cell reselection, the UE transmits a CELL UPDATE message to the SS on the uplink CCCH of cell B with the Cell update cause "Cell Reselection".
g) The SS sends a TCP/IP data packet (no compression packet type), PID=0. The PDCP Data PDU is used during lossless SRNS relocation procedure.
h) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The UE shall increase its internal Sequence Number counter by 1.The received data shall be returned by the UE via its PDCP configuration using PDCP SeqNum PDU.
i) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet shall be identical with the data as sent before.
j) After having performed SRNS relocation (target RNC allocated with new S-RNTI for the UE), the Target SRNS is the valid SRNS and the SS sends a "CELL UPDATE CONFIRM" message with new RNC_ID to indicate the completion of the cell update.
k) The UE shall confirm the reallocation.
l) The SS sends the next TCP/IP data packet (no compression packet type), PID=0 using the PDCP SeqNum PDU to the UE.
m) After having received the TCP/IP data packet, the UE shall recognize the PID value and shall handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
n) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall be identical with the data as sent before.
o) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1) in Cell A |
||||
|
The SS creates a TCP/IP packet without IP header compression. The DL_Send PDCP SN is set to "0". |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet Afterwards the SS increments its counter value DL_Send PDCP SN by "1". |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression shall be applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
||||
|
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
3 |
The SS increases the RF power level of cell B and decreases the power level of Cell A such that the UE finds cell B more suitable for service. |
|||
|
4 |
The UE cell reselection is performed and Cell B are selected for service. |
|||
|
5 |
|
RRC CELL UPDATE |
Then, the UE shall inform the SS about the new cell selection by sending cell update with new parameters (parameter values as used in RRC testing). |
|
|
6 |
|
PDCP Data |
The SS sends a PDCP Data PDU with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet Afterwards the SS increments its counter value DL_Send PDCP SN by "1". |
|
|
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
7 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
8 |
|
RRC CELL UPDATE CONFIRM |
After having performed SRNS relocation, the Target SRNS is the valid SRNS and the SS sends a "CELL UPDATE CONFIRM" message See message content. |
|
|
9 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
The UE confirms the newly received information. |
|
|
10 |
|
PDCP SeqNum |
The SS sends the next PDCP SeqNum PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) SeqNum = current PDCP Sequence Number data: below described TCP/IP packet Afterwards the SS increments its counter value DL_Send PDCP SN by "1". |
|
|
After having received the PDCP SeqNum PDU, the UE shall set the received PDCP Sequence Number as its own valid value. It decodes the PDU, recognizes PID value = 0 applied for this TCP/IP data packet and shall decompress it with the appropriate method. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. The SN synchronisation shall be considered as successfully performed after acknowledgement of SeqNum PDU transmission by lower layer in the SS. |
||||
|
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
11 |
|
PDCP SeqNum |
The UE sends a PDCP SeqNum PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 SeqNum = current PDCP Sequence Number data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
RRC CONNECTION SETUP message
The contents of the RRC CONNECTION SETUP message applied in the preamble "Setup a UE terminated PS session using IP Header compression in AM RLC" of this test case are identical to those of the Default Message Contents for Signalling in TS 34.108 clause 9.1 (”UM (Transition to CELL_FACH)”) with the following exceptions:
|
Information Element |
Value/remark |
|
Capability update requirement – UE radio access capability update requirement |
TRUE NOTE: Value will be checked. Stated capability must be compatible with 34.123-2 (c.f. PICS/PIXIT statements in GSM) and the user settings |
RADIO BEARER SETUP message
The contents of the RADIO BEARER SETUP message applied in the preamble "Setup a UE terminated PS session using IP Header compression in AM RLC" of this test case are identical to those of the Default Message Contents for Signalling in TS 34.108 clause 9.1 ”AM (Packet to CELL_FACH from CELL_FACH in PS”) with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup |
|
|
– RAB info |
|
|
– RB information to setup |
|
|
– RB identity |
20 |
|
– PDCP info |
|
|
– Support of lossless SRNS relocation |
True |
|
– Max PDCP SN window size |
65535 |
|
– PDCP PDU header |
Present |
|
– CHOICE RLC info type |
RLC info |
|
– CHOICE Uplink RLC mode |
AM RLC |
|
– Transmission RLC Discard |
|
|
– CHOICE SDU Discard Mode |
No discard |
|
– CHOICE Downlink RLC mode |
AM RLC |
|
– In-sequence delivery |
True |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
1 (Note: next expected Sequence Number) |
Content of PDCP Data PDU (Step 1)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP SeqNum PDU (Step 6)
|
Information Element |
Value/remark |
|
PDU type PID Sequence number Data |
001 00000 (No header compression, PID = 0) (16 Bit value) valid Sequence Number of the SS PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
CELL UPDATE CONFIRM (Step 8)
Use the message sub-type in default message content defined in Annex A, with the following exceptions.
|
Information Element |
Value/Remarks |
|
New U-RNTI |
New value of U-RNTI different from the previous U-RNTI |
|
Receive PDCP sequence number |
IE is set to the value to be counted inside SS as next expected reception Sequence Number |
UTRAN MOBILITY INFORMATION CONFIRM (Step 9)
Only the message type is checked.
Content of PDCP Data PDU (Step 10)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
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 shall not be received by SS.
7.3.3.2 Synchronisation of PDCP sequence numbers
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.
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 UE shall send to the UTRAN the next expected DL_Receive PDCP SN.
This information exchange synchronises the Sequence Numbers at the UE and UTRAN PDCP entities.
2. For radio bearers that are configured to support lossless SRNS Relocation, the PDCP entity shall:
– if upper layer indicates to a PDCP entity that it should synchronise the PDCP SN following a RLC reset or RB reconfiguration; or
– if the UE/UTRAN PDCP entity receives an invalid "next expected UL/DL_Receive PDCP SN" from upper layer after Relocation:
– trigger the PDCP SN synchronisation procedure by submitting one PDCP SeqNum PDU to lower layer;
– consider that the synchronisation procedure is complete on confirmation by lower layer of the successful transmission of the PDCP SeqNum PDU.
Reference(s)
TS 25.323 clause 5.4.1.3
TS 25.323 clause 5.4.1.2
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.
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 valid SRNS (Source SRNS). Usage of "PDCP Data" PDU, "PDCP SeqNum" PDU and no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of lossless SRNS relocation – YES/NO
Support of RLC in-sequence delivery – YES/NO
Test procedure
a) The SS setups a packet switched session including Radio Bearer and UE test loop mode 1 in RLC AM and in-sequence delivery using Common test procedures for mobile terminated PS switched sessions in Cell A. The RLC buffer discharge mode shall be set to "no discard". Usage of "PDCP Data" PDU and "PDCP SeqNum" PDU, support of lossless SRNS relocation and no IP header compression has been configured by higher layers. The PDCP SN window size has been negotiated by RRC.
b) The SS sends a TCP/IP data packet (no compression packet type), PID=0.
c) After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PID value and shall handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
d) The SS receives and decodes the TCP/IP data packet according to the inserted PID. The decoded data packet shall be identical with the data as sent before.
e) The SS reconfigures (using RRC Radio Bearer Reconfiguration message) the PDCP entity by extending the PID value allocation table and therefore the applied optimisation method with the IP header compression protocol RFC 2507. The UE test loop mode 1 in RLC AM is still active.
f) The SS sends the next TCP/IP data packet (no compression packet type), PID=0 using the "PDCP SeqNum" PDU including the current PDCP Sequence Number value to the UE.
g) After having received the TCP/IP data packet, the UE shall recognize the PID value and shall handle the received data packet correctly. Afterwards it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE by using PDCP "SeqNum" PDU including its DL_Receive PDCP SN via its PDCP configuration.
h) The SS receives and decodes TCP/IP data packets according to the inserted PID. The decoded data packets shall be identical with the data as sent before.
i) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated PS session using IP Header compression in AM RLC (using UE test loop mode 1) in Cell A |
||||
|
The SS creates a TCP/IP packet without IP header compression. The DL_Send PDCP SN is set to "0". |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet Afterwards the SS increments its counter value DL_Send PDCP SN by "1". |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression shall be applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
||||
|
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
3 |
|
RRC RADIO BEARER RECONFIGURATION |
SS extends the "PID value allocation table" with IP header compression PID (RFC 2507) in the UE. |
|
|
4 |
|
RRC RADIO BEARER RECONFIGURATION COMPLETE |
UE acknowledges its new settings |
|
|
5 |
|
PDCP SeqNum |
The SS sends a PDCP SeqNum PDU including its current Sequence Number with the following content to the UE: PDU type = 001 (PDCP SeqNum PDU) PID = 0 (normal packet type [TCP/IP]) SeqNum = current PDCP Sequence Number data: below described TCP/IP packet Afterwards the SS increments its counter value DL_Send PDCP SN by "1". |
|
|
After having received the PDCP SeqNum PDU, the UE shall set the received PDCP Sequence Number as its own valid value. It decodes the PDU, recognizes PID value = 0 applied for this TCP/IP data packet and shall decompress it with the appropriate method. The UE shall set the value of DL_Receive PDCP SN to the value as received from SS. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. The SN synchronisation shall be considered as successfully performed after acknowledgement of SeqNum PDU transmission by lower layer in the SS. |
||||
|
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
6 |
|
PDCP PDU |
The UE sends a PDCP PDU with PDCP Header back to the SS. The content is as follows: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 SeqNum: current UE value, (optional parameter, depending on PDU used) data: previously received TCP/IP packet. |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
RRC RADIO BEARER RECONFIGURATION message
The contents of the RRC RADIO BEARER RECONFIGURATION message applied in the preamble "Setup a UE terminated PS session using IP Header compression in AM RLC" of this test case is identical to those of the default contents of layer 3 messages for RRC tests [TS 34.123-1] (PS connection for AM) with the following exceptions:
|
Information Element |
Value/remark |
|
RB information to reconfigure list RB information to reconfigure – PDCP info – Max PDCP SN window size – Support of lossless SRNS relocation – PDCP PDU header – Header compression information CHOICE algorithm type – RFC2507 – F_MAX_PERIOD – F_MAX_TIME – MAX_HEADER – TCP_SPACE – NON_TCP_SPACE – EXPECT_REORDERING |
1 65535 TRUE present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) |
|
Receive PDCP sequence number |
IE is set to the value to be counted inside SS as next expected reception Sequence Number |
|
U-RNTI |
New value of U-RNTI different from the previous U-RNTI |
RRC CONNECTION SETUP message
The contents of the RRC CONNECTION SETUP message applied in the preamble "Setup a UE terminated PS session using IP Header compression in AM RLC" of this test case is identical to those of the default contents of layer 3 messages for RRC tests [TS 34.123-1] (PS connection for AM) with the following exceptions:
|
Information Element |
Value/remark |
|
Capability update requirement – UE radio access capability update requirement |
TRUE NOTE: Value will be checked. Stated capability must be compatible with 34.123-2 (c.f. PICS/PIXIT statements in GSM) and the user settings |
RADIO BEARER SETUP message
The contents of the RADIO BEARER SETUP message applied in the preamble "Setup a UE terminated PS session using IP Header compression in AM RLC" of this test case is identical to those of the default contents of layer 3 messages for RRC tests [TS 34.123-1] (PS connection for AM) which fit to the here described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
– Downlink counter synchronisation info – RB with PDCP information list – RB identity – PDCP SN info – RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – Max PDCP SN window size – Support of lossless SRNS relocation – PDCP PDU header – RLC info – Downlink RLC mode – In-sequence delivery – Uplink RLC mode – Transmission RLC Discard |
20 1 (Note: next expected Sequence Number) No. # 23 as described in TS 34.108, Table 6.10.2.1.1 Prioritised RABs. QoS parameter: Traffic Class: Interactive or Background, max. UL: 64 kbps and max. DL: 64 kbps as described in TS 34.108, including described physical channel parameters, configuration for AM RLC Residual BER as described in TS 24.108, clause: 6.10 Related Signalling RB UL: 3.4 kbps, DL: 3.4 kbps DCCH, No. #2 (as described in TS 34.108) PS domain 20 65535 TRUE present (AM RLC) True (AM RLC) No Discard Note: Default value defined in TS 34.108, Annex B |
Content of PDCP Data PDU (Step 1)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP SeqNum PDU (Step 5)
|
Information Element |
Value/remark |
|
PDU type PID Sequence number Data |
001 00000 (No header compression, PID = 0) (16 Bit value) valid Sequence Number of the SS PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
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 Numbering and Data Forwarding – Reception of reserved PDU type
FFS
7.3.3.4 PDCP Sequence Number synchronization – Reception of invalid next expected receive Sequence Number
FFS
7.3.3.5 UTRAN MOBILITY INFORMATION: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
7.3.3.5.1 Definition
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> include the IE "RB with PDCP information list" in the UTRAN MOBILITY INFORMATION CONFIRM message and set it to the value of the variable PDCP_SN_INFO.
1> if the received UTRAN MOBILITY INFORMATION message included the IE "Downlink counter synchronisation info":
2> re-establish RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to TS 25.331 subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in the UTRAN MOBILITY INFORMATION CONFIRM message.
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM message on the uplink DCCH using AM RLC;
1> if the IE "Downlink counter synchronisation info" was included in the received UTRAN MOBILITY INFORMATION message:
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS.
1> if the variable PDCP_SN_INFO is non-empty:
2> when RLC has confirmed the successful transmission of the UTRAN MOBILITY INFORMATION CONFIRM message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> clear the variable PDCP_SN_INFO.
Reference
3GPP TS 25.331 clause 8.3.3
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 applied by the network, to confirm that the UE applies the new ciphering algorithm following a successful SRNS relocation.
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 |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Contents
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA0 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
The contents of RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4, use the message titled “Packet to CELL_FACH from CELL_FACH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
The UE is in the CELL_FACH state. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, a PDCP PDUs has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS then transmits a UTRAN MOBILITY INFORMATION message, which includes a valid IE “New C-RNTI” and “New U-RNTI”, IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”, to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. |
|||
|
3 |
|
UTRAN MOBILITY INFORMATION |
If IE “Ciphering mode info” is present in the SECURITY MODE COMMAND during initial condition set-up, this message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. New U-RNTI identities are assigned to the UE. IE “Downlink counter synchronisation info” includes the next PCDP sequence number that SS is expected to receive from the UE, otherwise only IE “Downlink counter synchronisation info” is included. New integrity protection configuration is applied on DL SRB1. |
|
|
4 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
New calculated START value is included, IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on UL SRB2 with the downlink and uplink values of the HFN component of COUNT-C for SRB2 incremented by one. |
|
|
5 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on DL SRB2 with the same START value as used in step 4. |
|
|
6 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on SRB2 by UE. |
|
|
7 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
8 |
Void |
|||
|
9 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
10 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
11 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
12 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
13 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
14 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
15 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
UTRAN MOBILITY INFORMATION (Step 3)
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
20 |
|
– RLC sequence number |
Current RLC SN+2 |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC Identity |
An arbitrary 12-bits string which is different from original SRNC |
|
– S-RNTI |
An arbitrary 20-bits string which is different from original S-RNTI |
|
New C-RNTI |
Not Present |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
– CN domain specific DRX cycle length coefficient |
7 |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is included |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE |
UTRAN MOBILITY INFORMATION CONFIRM for PS only UE (Step 4)
The same message sub-type found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH with the following exceptions:
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. (X) |
|
– START list |
Check that this IE is correct value |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20. .
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS and apply new ciphering configuration on UL SRB3.
After step 8, the UE shall respond with a IDENTITY RESPONSE message to SS
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the UTRAN MOBILITY INFORMATION CONFIRM message.
7.3.3.6 Cell Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
7.3.3.6.1 Definition
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 (refer to TS 25.331 subclause 8.5.9) with "START" in the IE "START list" for the CN domain as indicated by "CN domain identity" in the IE "START list";
3> if this procedure was triggered while the UE was not in CELL_DCH state, then for each CN domain as indicated by "CN domain identity" in the IE "START list":
4> set the 20 MSB of the MAC-d HFN with the corresponding START value in the IE "START list";
4> set the remaining LSB of the MAC-d HFN to zero.
3> transmit a CELL UPDATE CONFIRM message on the downlink DCCH or optionally on the CCCH but only if ciphering is not required; and
3> optionally include the IE "RLC re-establish indicator (RB5 and upwards)" to request a RLC re-establishment in the UE, in which case the corresponding RLC entities should also be re-established in UTRAN; or
If the UE after the state transition remains in CELL_FACH state; and
– a C-RNTI is stored in the variable C_RNTI;
the UE shall:
1> if the variable PDCP_SN_INFO is non-empty:
2> include the IE "RB with PDCP information list" in any response message transmitted below and set it to the value of the variable PDCP_SN_INFO.
1> if the received CELL UPDATE CONFIRM message included the IE "Downlink counter synchronisation info":
2> re-establish RB2;
2> set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2;
2> calculate the START value according to TS 25.331 subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in any response message transmitted below.
1> transmit a response message as specified in TS 25.331 subclause 8.3.1.7;
If the CELL UPDATE CONFIRM message:
– does not include "RB information elements"; and
– does not include "Transport channel information elements"; and
– does not include "Physical channel information elements"; and
– includes "CN information elements"; or
– includes the IE "Ciphering mode info"; or
– includes the IE "Integrity protection mode info"; or
– includes the IE "New C-RNTI"; or
– includes the IE "New U-RNTI":
the UE shall:
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition., and the UE shall:
1> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM message:
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].
1> if the variable PDCP_SN_INFO non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> continue with the remainder of the procedure.
Reference
3GPP TS 25.331 clause 8.3.1
7.3.3.6.3 Test purpose
- To confirm that the UE executes a cell update procedure after the successful reselection of another UTRA cell.
- 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.
- To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS relocation.
- 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.
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 |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4, uses the message titled “Packet to CELL_FACH from CELL_FACH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
Table 7.3.3.6
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.6 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the CELL_FACH state in cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, the number of a PDCP PDU has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.6. The UE shall find cell 2 to be more suitable for service and hence perform a cell reselection. After the completion of cell reselection, the UE shall transmits a CELL UPDATE message to the SS on the uplink CCCH of cell 2 and set IE "Cell update cause" to "Cell Reselection". SS then transmits a CELL UPDATE CONFIRM message, which includes a valid IE “New C-RNTI” and “New U-RNTI”, IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”, to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in CELL UPDATE CONFIRM message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. After last ciphering activation time has elapsed and there is no pending ciphering activation time, SS applies the downlink transmission power settings, according to the values in columns "T1" of table 7.3.3.6. The UE shall find that the cell 2 is better for service and perform a reselection. SS waits for the maximum duration required for the UE to camp to cell 2. |
||
|
3 |
|
CELL UPDATE |
Value "cell reselection" shall be indicated in IE "Cell update cause" |
|
|
4 |
|
CELL UPDATE CONFIRM |
IE "RRC State Indicator" is set to "CELL_FACH". New C-RNTI and U-RNTI identities are assigned to the UE. IE “Downlink counter synchronisation info” includes the next PCDP sequence number that SS is expected to receive from the UE, otherwise only IE “Downlink counter synchronisation info” is included. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
5 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. If IE “Ciphering mode info” is present in step 4, new ciphering configuration is applied on UL SRB2 with the downlink and uplink values of the HFN component of COUNT-C for SRB2 is incremented by one. |
|
|
6 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. If IE “Ciphering mode info” is present in step 4, new ciphering configuration is applied on DL SRB2 with the same value as used in step 5. |
|
|
7 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
8 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
9 |
Void |
|||
|
10 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
11 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
12 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
13 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
14 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
15 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
16 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
17 |
New ciphering configuration is applied on UL and DL RAB using the re-initialised COUNT-C HFN by the start value as stored in step 5. |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
CELL UPDATE (Step 3)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:
|
Information Element |
Value/remark |
|
Cell Update Cause |
Check to see if set to ‘Cell Re-selection’ |
CELL UPDATE CONFIRM (Step 4)
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA0 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
20 |
|
– RLC sequence number |
Current RLC SN+2 |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC Identity |
An arbitrary 12-bits string which is different from original SRNC |
|
– S-RNTI |
An arbitrary 20-bits string which is different from original S-RNTI |
|
New C-RNTI |
Not Present |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is included |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE.(X) |
UTRAN MOBILITY INFORMATION CONFIRM (Step 5)
The same message sub-type found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH with the following exceptions:
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE |
|
– START list |
Check that this IE is correct value |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 6)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 7)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 8)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 includes which includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, this message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 6, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 10, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the UTRAN MOBILITY INFORMATION CONFIRM message.
7.3.3.7 URA Update: Lossless SRNS relocation in CELL_FACH (without pending of ciphering)
7.3.3.7.1 Definition
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 stored in the variable C_RNTI;
the UE shall:
1> if the variable PDCP_SN_INFO is non-empty:
2> include the IE "RB with PDCP information list" in any response message transmitted below and set it to the value of the variable PDCP_SN_INFO.
1> if the received URA UPDATE CONFIRM message included the IE "Downlink counter synchronisation info":
2> re-establish RB2;
2> set the new uplink and downlink HFN component of the COUNT-C of RB2 to MAX(uplink HFN component of the COUNT-C of RB2, downlink HFN component of the COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of the COUNT-C for RB2;
2> calculate the START value according to TS 25.331 subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info" in any response message transmitted below.
If the URA UPDATE CONFIRM message:
– includes "CN information elements"; or
– includes the IE "Ciphering mode info"; or
– includes the IE "Integrity protection mode info"; or
– includes any one or both of the IEs "New C-RNTI" and "New U-RNTI":
the UE shall:
1> transmit a UTRAN MOBILITY INFORMATION CONFIRM as response message using AM RLC.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition., and the UE shall:
1> if the IE "Downlink counter synchronisation info" was included in the received CELL UPDATE CONFIRM or URA UPDATE CONFIRM message:
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of the COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS.
1> if the variable PDCP_SN_INFO non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
Reference
3GPP TS 25.331 clause 8.3.1
7.3.3.7.3 Test purpose
- To confirm that the UE executes a URA update procedure after the successful reselection of another UTRA cell.
- 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.
- To confirm that the UE sends calculated START values for each CN domain to SS after a successful SRNS relocation.
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 |
|||||
|
1 |
SS executes procedure P18 (clause 7.4.2.1.2 of TS 34.108) |
||||
|
2 |
UE enters state URA_PCH |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P14 as specified in TS 34.108 clause 7.4, uses the message titled “Packet to CELL_FACH from CELL_FACH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
Table 7.3.3.7
|
Parameter |
Unit |
Cell 1 |
Cell 3 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.7 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the URA_PCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDUs on the RAB. If ciphering is supported, a PDCP PDUs has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.7. The UE shall find cell 3 to be more suitable for service and hence perform a cell reselection. After the completion of cell reselection, the UE shall transmits a URA UPDATE message to the SS on the uplink CCCH of cell 3 and set IE "URA update cause" to "change of URA". After the SS receives this message, it transmits a URA UPDATE CONFIRM message, which includes a valid IE “New C-RNTI” and “New U-RNTI”, IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”, to the UE on the downlink DCCH using UM RLC. SS verifies that the UE sends UTRAN MOBILITY INFORMATION CONFIRM message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in CELL UPDATE CONFIRM message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. After last ciphering activation time has elapsed and there is no pending ciphering activation time, SS applies the downlink transmission power settings, according to the values in columns "T1" of table 7.3.3.7. The UE shall find that the cell 2 is better for service and perform a reselection. SS waits for the maximum duration required for the UE to camp to cell 3. |
||
|
3 |
|
URA UPDATE |
Value "change of URA" shall be indicated in IE "URA update cause" |
|
|
4 |
|
URA UPDATE CONFIRM |
IE "RRC State Indicator" is set to "CELL_FACH". New C-RNTI and U-RNTI identities are assigned to the UE. IE “Downlink counter synchronisation info” includes the next PCDP sequence number that SS is expected to receive from the UE, otherwise only IE “Downlink counter synchronisation info” is included. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
5 |
|
UTRAN MOBILITY INFORMATION CONFIRM |
New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. |
|
|
6 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. |
|
|
7 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
8 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
9 |
Void |
|||
|
10 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
11 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
12 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
13 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
14 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
15 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
16 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
17 |
Void |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
URA UPDATE (Step 3)
The same message found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink CCCH, with the exception of the following IEs:
|
Information Element |
Value/remark |
|
URA Update Cause |
Check to see if set to “change of URA” |
URA UPDATE CONFIRM (Step 4)
Use the same message sub-type found in TS 34.108, clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC Identity |
An arbitrary 12-bits string which is different from original SRNC |
|
– S-RNTI |
An arbitrary 20-bits string which is different from original S-RNTI |
|
New C-RNTI |
Not Present |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is included |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE.(X) |
UTRAN MOBILITY INFORMATION CONFIRM (Step 5)
The same message sub-type found in TS 34.108, clause 9 shall be transmitted by the UE on the uplink DCCH with the following exceptions:
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE.(X) |
|
– START list |
Check that this IE is correct value |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 6)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 7)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 8)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 includes which includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in UTRAN MOBILITY INFORMATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 6, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, the UE shall respond with an IDENTITY RESPONSE message to SS and apply new ciphering configuration on UL SRB3.
After step 10, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the UTRAN MOBILITY INFORMATION CONFIRM message.
7.3.3.8 Radio Bearer Establishment for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
7.3.3.8.1 Definition
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 IE "Downlink counter synchronisation info";
2> re-establish RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info".
1> if the variable PDCP_SN_INFO is not empty:
2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.
1> if the IE "Integrity protection mode info" was present in the received reconfiguration message:
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition, and the UE shall:
1> if the IE "Downlink counter synchronisation info" was included in the reconfiguration message;
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].
1> if the variable PDCP_SN_INFO is non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> perform the actions below.
Reference
3GPP TS 25.331 clause 8.2.2.
7.3.3.8.3 Test purpose
- 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.
- 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.
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 |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA0 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P13 as specified in TS 34.108 clause 7.4, use the message titled “Packet to CELL_DCH from CELL_DCH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
RAB information for setup |
|
|
– RAB info |
|
|
– RAB identity |
0000 0101B |
|
– CN domain identity |
PS domain |
|
– NAS Synchronization Indicator |
Not Present |
|
– Re-establishment timer |
UseT315 |
|
– RB information to setup |
|
|
– RB identity |
20 |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
|
– CHOICE RLC info type |
RLC info |
|
– CHOICE Uplink RLC mode |
AM RLC |
|
– Transmission RLC discard |
|
|
– SDU discard mode |
No discard |
|
– MAX_DAT |
15 |
|
– Transmission window size |
128 |
|
– Timer_RST |
500 |
|
– Max_RST |
4 |
|
– Polling info |
|
|
– Timer_poll_prohibit |
200 |
|
– Timer_poll |
200 |
|
– Poll_PDU |
Not Present |
|
– Poll_SDU |
1 |
|
– Last transmission PDU poll |
TRUE |
|
– Last retransmission PDU poll |
TRUE |
|
– Poll_Windows |
99 |
|
– Timer_poll_periodic |
Not Present |
|
– CHOICE Downlink RLC mode |
AM RLC |
|
– In-sequence delivery |
TRUE |
|
– Receiving window size |
128 |
|
– Downlink RLC status info |
|
|
– Timer_status_prohibit |
200 |
|
– Timer_EPC |
Not Present |
|
– Missing PDU indicator |
TRUE |
|
– Timer_STATUS_periodic |
Not Present |
|
– RB mapping info |
|
|
– Information for each multiplexing option |
2 RBMuxOptions |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
DCH |
|
– UL Transport channel identity |
1 |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Configured |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
DCH |
|
– DL DCH Transport channel identity |
6 |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Explicit List |
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
|
– MAC logical channel priority |
8 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
FACH |
|
– DL DCH Transport channel identity |
Not Present |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
Test Procedure
Table 7.3.3.8
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.8 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the CELL_DCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, the a PDCP PDUs has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.8. The SS sends a RADIO BEARER SETUP message on the downlink DCCH using AM RLC requesting the UE to do a handover combined with SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”. UE shall reselect to cell 2 and SS verifies that the UE sends RADIO BEARER SETUP COMPLETE message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in RADIO BEARER SETUP message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. SS applies the downlink transmission power settings, according to the values in columns "T1" of table 7.3.3.8. |
||
|
3 |
|
RADIO BEARER SETUP |
If IE “Ciphering mode info” is present in the SECURITY MODE COMMAND during initial condition set-up, this message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. IE “Downlink counter synchronisation info” includes the next PCDP sequence number that SS is expected to receive from the UE, otherwise only IE “Downlink counter synchronisation info” is included. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
4 |
|
RADIO BEARER SETUP COMPLETE |
The UE shall transmit this message after it reselects to cell 2. New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on UL SRB2 with the downlink and uplink values of the HFN component of COUNT-C for SRB2 is incremented by one. |
|
|
5 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on DL SRB2 with the same value as used in step 4. |
|
|
6 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
7 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
8 |
Void |
|||
|
9 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
10 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
11 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
12 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
13 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
14 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
15 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
16 |
If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on UL and DL RAB using the re-initialised COUNT-C HFN by the start value as stored in step 4. |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
RADIO BEARER SETUP for PS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Packet to CELL_DCH from CELL_DCH in PS”, with the following exception:
|
Information Element |
Value/remark |
||
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
||
|
– Ciphering mode command |
Start/restart |
||
|
– Ciphering algorithm |
UEA1 |
||
|
– Ciphering activation time for DPCH |
Not Present |
||
|
– Radio bearer downlink ciphering activation time info |
|||
|
– Radio bearer activation time |
|||
|
– RB identity |
1 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
2 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
3 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
4 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
20 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
Integrity protection mode info |
|||
|
– Integrity protection mode command |
Start |
||
|
– Downlink integrity protection activation info |
Not Present |
||
|
– Integrity protection algorithm |
UIA1 |
||
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
||
|
New U-RNTI |
|||
|
– SRNC identity |
0000 0000 0010B |
||
|
– S-RNTI |
0000 0000 0000 0000 0001B |
||
|
CN Information info |
|||
|
– PLMN identity |
Not present |
||
|
– CN common GSM-MAP NAS system information |
|||
|
– GSM-MAP NAS system information |
00 01H |
||
|
– CN domain related information |
|||
|
– CN domain identity |
PS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
05 00H |
||
|
– CN domain identity |
CS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
1E 01H |
||
|
RAB information for setup |
|||
|
– RAB info |
|||
|
– RAB identity |
0000 1100B |
||
|
– CN domain identity |
PS domain |
||
|
– NAS Synchronization Indicator |
Not Present |
||
|
– Re-establishment timer |
UseT315 |
||
|
– RB information to setup |
|||
|
– RB identity |
12 |
||
|
– PDCP info |
|||
|
– Support for lossless SRNS relocation |
FALSE |
||
|
– Max PDCP SN window size |
Not present |
||
|
– PDCP PDU header |
Absent |
||
|
– Header compression information |
Not present |
||
|
– CHOICE RLC info type |
RLC info |
||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
500 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
200 |
||
|
– Timer_poll |
200 |
||
|
– Poll_PDU |
Not Present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Windows |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not Present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
Not Present |
||
|
– RB mapping info |
|||
|
– Information for each multiplexing option |
2 RBMuxOptions |
||
|
– RLC logical channel mapping indicator |
Not Present |
||
|
– Number of uplink RLC logical channels |
1 |
||
|
– Uplink transport channel type |
DCH |
||
|
– UL Transport channel identity |
1 |
||
|
– Logical channel identity |
8 |
||
|
– CHOICE RLC size list |
Configured |
||
|
– MAC logical channel priority |
8 |
||
|
– Downlink RLC logical channel info |
|||
|
– Number of downlink RLC logical channels |
1 |
||
|
– Downlink transport channel type |
DCH |
||
|
– DL DCH Transport channel identity |
6 |
||
|
– DL DSCH Transport channel identity |
Not Present |
||
|
– Logical channel identity |
8 |
||
|
– RLC logical channel mapping indicator |
Not Present |
||
|
– Number of uplink RLC logical channels |
1 |
||
|
– Uplink transport channel type |
RACH |
||
|
– UL Transport channel identity |
Not Present |
||
|
– Logical channel identity |
8 |
||
|
– CHOICE RLC size list |
Explicit List |
||
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
||
|
– MAC logical channel priority |
8 |
||
|
– Downlink RLC logical channel info |
|||
|
– Number of downlink RLC logical channels |
1 |
||
|
– Downlink transport channel type |
FACH |
||
|
– DL DCH Transport channel identity |
Not Present |
||
|
– DL DSCH Transport channel identity |
Not Present |
||
|
– Logical channel identity |
8 |
||
|
Downlink counter synchronisation info |
|||
|
– RB with PDCP information list |
This IE is included |
||
|
– RB with PDCP information |
|||
|
– RB identity |
20 |
||
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE. |
||
|
Downlink information for each radio links |
|||
|
– Primary CPICH info |
|||
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
||
RADIO BEARER SETUP for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Non speech to CELL_DCH from CELL_DCH in CS”, with the following exception:
|
Information Element |
Value/remark |
||
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
||
|
– Ciphering mode command |
Start/restart |
||
|
– Ciphering algorithm |
UEA1 |
||
|
– Ciphering activation time for DPCH |
(256+CFN-(CFN MOD 8 + 8))MOD 256 |
||
|
– Radio bearer downlink ciphering activation time info |
|||
|
– Radio bearer activation time |
|||
|
– RB identity |
1 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
2 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
3 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
4 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
Integrity protection mode info |
|||
|
– Integrity protection mode command |
Start |
||
|
– Downlink integrity protection activation info |
Not Present |
||
|
– Integrity protection algorithm |
UIA1 |
||
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
||
|
New U-RNTI |
|||
|
– SRNC identity |
0000 0000 0010B |
||
|
– S-RNTI |
0000 0000 0000 0000 0001B |
||
|
CN Information info |
|||
|
– PLMN identity |
Not present |
||
|
– CN common GSM-MAP NAS system information |
|||
|
– GSM-MAP NAS system information |
00 01H |
||
|
– CN domain related information |
|||
|
– CN domain identity |
PS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
05 00H |
||
|
– CN domain identity |
CS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
1E 01H |
||
|
RAB information for setup |
|||
|
– RAB info |
|||
|
– RAB identity |
0000 1100B |
||
|
– CN domain identity |
CS domain |
||
|
– NAS Synchronization Indicator |
Not Present |
||
|
– Re-establishment timer |
UseT314 |
||
|
– RB information to setup |
|||
|
– RB identity |
13 |
||
|
– PDCP info |
Not Present |
||
|
– CHOICE RLC info type |
RLC info |
||
|
– CHOICE Uplink RLC mode |
TM RLC |
||
|
– Transmission RLC discard |
Not Present |
||
|
– Segmentation indication |
FALSE |
||
|
– CHOICE Downlink RLC mode |
TM RLC |
||
|
– Segmentation indication |
FALSE |
||
|
– RB mapping info |
|||
|
– Information for each multiplexing option |
|||
|
– RLC logical channel mapping indicator |
Not Present |
||
|
– Number of uplink RLC logical channels |
1 |
||
|
– Uplink transport channel type |
DCH |
||
|
– UL Transport channel identity |
1 |
||
|
– Logical channel identity |
Not Present |
||
|
– CHOICE RLC size list |
Configured |
||
|
– MAC logical channel priority |
8 |
||
|
– Downlink RLC logical channel info |
|||
|
– Number of downlink RLC logical channels |
1 |
||
|
– Downlink transport channel type |
DCH |
||
|
– DL DCH Transport channel identity |
6 |
||
|
– DL DSCH Transport channel identity |
Not Present |
||
|
– Logical channel identity |
Not Present |
||
|
Downlink counter synchronisation info |
|||
|
– RB with PDCP information list |
Not present |
||
|
Downlink information for each radio links |
|||
|
– Primary CPICH info |
|||
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
||
RADIO BEARER SETUP COMPLETE for PS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked. |
|
– RB with PDCP information |
|
|
– RB identity |
12 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. |
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. |
|
– START list |
Check that this IE is present. |
RADIO BEARER SETUP COMPLETE for CS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
– START list |
Check that this IE is present. |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in RADIO BEARER SETUP message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the RADIO BEARER RECONFIGURATION COMPLETE message.
7.3.3.9 Radio Bearer Reconfiguration for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
7.3.3.9.1 Definition
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 BEARER RECONFIGURATION and the IE "New U-RNTI" is included:
2> re-establish RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info".
1> if the variable PDCP_SN_INFO is not empty:
2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.
1> if the IE "Integrity protection mode info" was present in the received reconfiguration message:
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition, and the UE shall:
1> if the received reconfiguration message is a RADIO BEARER RECONFIGURATION and the IE "New U-RNTI" is included:
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].
1> if the variable PDCP_SN_INFO is non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> perform the actions below.
Reference
3GPP TS 25.331 clause 8.2.2.
7.3.3.9.3 Test purpose
- 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.
- 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.
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 as specified in clause 7.3.1.2.1.4 |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P13 as specified in TS 34.108 clause 7.4, use the message titled “Packet to CELL_DCH from CELL_DCH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
Table 7.3.3.9
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.9 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the CELL_DCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1. If ciphering is supported a PDCP PDU has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.9. The SS sends a RADIO BEARER RECONFIGURATION message on the downlink DCCH using AM RLC requesting the UE to do a handover combined with SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE “New U-RNTI” and IE “Integrity protection mode info”. UE shall reselect to cell 2 and SS verifies that the UE sends RADIO BEARER RECONFIGURATION COMPLETE message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in RADIO BEARER SETUP message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS responds with UE CAPABILITY INFORMATION CONFIRM message. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. SS applies the downlink transmission power settings, according to the values in columns "T1" of table 7.3.3.8. |
||
|
3 |
|
RADIO BEARER RECONFIGURATION |
If IE “Ciphering mode info” is present in the SECURITY MODE COMMAND during initial condition set-up, this message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. IE “RB information to reconfigure” includes the next PCDP sequence number that SS is expected to receive from the UE. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
4 |
|
RADIO BEARER RECONFIGURATION COMPLETE |
The UE shall transmit this message after it reselects to cell 2. New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on UL SRB2 with the downlink and uplink values of the HFN component of COUNT-C for SRB2 is incremented by one. |
|
|
5 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on DL SRB2 with the same value as used in step 4. |
|
|
6 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
7 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
8 |
Void |
|||
|
9 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
10 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
11 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
12 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
13 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
14 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
15 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
16 |
If IE “Ciphering mode info” is present in step 3, new ciphering configuration is applied on UL and DL RAB using the re-initialised COUNT-C HFN by the start value as stored in step 4. |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
RADIO BEARER RECONFIGURATION for PS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Packet to CELL_DCH from CELL_DCH in PS”, with the following exception:
|
Information Element |
Value/remark |
||
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
||
|
– Ciphering mode command |
Start/restart |
||
|
– Ciphering algorithm |
UEA0 |
||
|
– Ciphering activation time for DPCH |
Not Present |
||
|
– Radio bearer downlink ciphering activation time info |
|||
|
– Radio bearer activation time |
|||
|
– RB identity |
1 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
2 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
3 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
4 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
20 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
Integrity protection mode info |
|||
|
– Integrity protection mode command |
Start |
||
|
– Downlink integrity protection activation info |
Not Present |
||
|
– Integrity protection algorithm |
UIA1 |
||
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
||
|
New U-RNTI |
|||
|
– SRNC identity |
0000 0000 0010B |
||
|
– S-RNTI |
0000 0000 0000 0000 0001B |
||
|
CN Information info |
|||
|
– PLMN identity |
Not present |
||
|
– CN common GSM-MAP NAS system information |
|||
|
– GSM-MAP NAS system information |
00 01H |
||
|
– CN domain related information |
|||
|
– CN domain identity |
PS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
05 00H |
||
|
– CN domain identity |
CS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
1E 01H |
||
|
RB information to reconfigure list |
|||
|
– RB information to reconfigure |
(AM DCCH for RRC) |
||
|
– RB identity |
2 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
– RB information to reconfigure |
(AM DCCH for NAS_DT High priority) |
||
|
– RB identity |
3 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
– RB information to reconfigure |
(AM DCCH for NAS_DT Low priority) |
||
|
– RB identity |
4 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not Present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
– RB information to reconfigure |
(AM DTCH) |
||
|
– RB identity |
20 |
||
|
– PDCP info |
|||
|
– Support for lossless SRNS relocation |
TRUE |
||
|
– Max PDCP SN window size |
sn65535 |
||
|
– PDCP PDU header |
Present |
||
|
– Header compression information |
Not present |
||
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not Present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not Present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
Downlink information for each radio links |
|||
|
– Primary CPICH info |
|||
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
||
RADIO BEARER RECONFIGURATION for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Speech in CS” or “Non speech in CS”, with the following exception:
|
Information Element |
Value/remark |
||
|
Ciphering mode info |
If network does not apply ciphering, set this IE to “Not present”. If network applies ciphering, this IE present with the values of the sub IEs as stated below. |
||
|
– Ciphering mode command |
Start/restart |
||
|
– Ciphering algorithm |
UEA1 |
||
|
– Ciphering activation time for DPCH |
(256+CFN-(CFN MOD 8 + 8))MOD 256 |
||
|
– Radio bearer downlink ciphering activation time info |
|||
|
– Radio bearer activation time |
|||
|
– RB identity |
1 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
2 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
3 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
– RB identity |
4 |
||
|
– RLC sequence number |
Current RLC SN+2 |
||
|
Integrity protection mode info |
|||
|
– Integrity protection mode command |
Start |
||
|
– Downlink integrity protection activation info |
Not Present |
||
|
– Integrity protection algorithm |
UIA1 |
||
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
||
|
New U-RNTI |
|||
|
– SRNC identity |
0000 0000 0010B |
||
|
– S-RNTI |
0000 0000 0000 0000 0001B |
||
|
CN Information info |
|||
|
– PLMN identity |
Not present |
||
|
– CN common GSM-MAP NAS system information |
|||
|
– GSM-MAP NAS system information |
00 01H |
||
|
– CN domain related information |
|||
|
– CN domain identity |
PS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
05 00H |
||
|
– CN domain identity |
CS |
||
|
– CN domain specific NAS system information |
|||
|
– GSM-MAP NAS system information |
1E 01H |
||
|
RB information to reconfigure list |
|||
|
– RB information to reconfigure |
(AM DCCH for RRC) |
||
|
– RB identity |
2 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
– RB information to reconfigure |
(AM DCCH for NAS_DT High priority) |
||
|
– RB identity |
3 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
– RB information to reconfigure |
(AM DCCH for NAS_DT Low priority) |
||
|
– RB identity |
4 |
||
|
– PDCP info |
Not Present |
||
|
– PDCP SN info |
Not Present |
||
|
– RLC info |
|||
|
– CHOICE Uplink RLC mode |
AM RLC |
||
|
– Transmission RLC discard |
|||
|
– SDU discard mode |
No discard |
||
|
– MAX_DAT |
15 |
||
|
– Transmission window size |
128 |
||
|
– Timer_RST |
400 |
||
|
– Max_RST |
4 |
||
|
– Polling info |
|||
|
– Timer_poll_prohibit |
150 |
||
|
– Timer_poll |
150 |
||
|
– Poll_PDU |
Not present |
||
|
– Poll_SDU |
1 |
||
|
– Last transmission PDU poll |
TRUE |
||
|
– Last retransmission PDU poll |
TRUE |
||
|
– Poll_Window |
99 |
||
|
– Timer_poll_periodic |
Not Present |
||
|
– CHOICE Downlink RLC mode |
AM RLC |
||
|
– In-sequence delivery |
TRUE |
||
|
– Receiving window size |
128 |
||
|
– Downlink RLC status info |
|||
|
– Timer_status_prohibit |
200 |
||
|
– Timer_EPC |
Not Present |
||
|
– Missing PDU indicator |
TRUE |
||
|
– Timer_STATUS_periodic |
400 |
||
|
– RB mapping info |
Not Present |
||
|
– RB stop/continue |
Not Present |
||
|
Downlink information for each radio links |
|||
|
– Primary CPICH info |
|||
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
||
RADIO BEARER RECONFIGURATION COMPLETE for PS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. |
|
– START list |
Check that this IE is present. |
RADIO BEARER RECONFIGURATION COMPLETE for CS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
– START list |
Check that this IE is present. |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in RADIO BEARER RECONFIGURATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the RADIO BEARER RECONFIGURATION COMPLETE message.
7.3.3.10 Radio Bearer Release for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
7.3.3.10.1 Definition
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 IE "Downlink counter synchronisation info";
2> re-establish RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info".
1> if the variable PDCP_SN_INFO is not empty:
2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.
1> if the IE "Integrity protection mode info" was present in the received reconfiguration message:
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition, and the UE shall:
1> if the IE "Downlink counter synchronisation info" was included in the reconfiguration message;
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].
1> if the variable PDCP_SN_INFO is non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> perform the actions below.
Reference
3GPP TS 25.331 clause 8.2.2.
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.
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 loop mode 1 in CELL_DCH or CELL_FACH |
|||||
|
1a |
SS executes procedure P21 (clause 7.4.2.1.2 of TS 34.108) |
(PS+PS DCCH+DTCH_DCH) |
|||
|
1b |
SS executes procedure P23 (clause 7.4.2.1.2 of TS 34.108) |
(PS+CS DCCH+DTCH_DCH) |
|||
NOTE: depending on CN domain(s) supported, either step 1a or step 1b shall be executed in order to reach the final initial condition state for this test case.
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P13 as specified in TS 34.108 clause 7.4, use the message titled “Packet to CELL_DCH from CELL_DCH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
Table 7.3.3.10
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.10 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the CELL_DCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDUs on the RAB. If ciphering is supported, a PDCP PDU has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.10. The SS sends a RADIO BEARER RELEASE message on the downlink DCCH using AM RLC requesting the UE to do a handover combined with SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”. UE shall reselect to cell 2 and SS verifies that the UE sends RADIO BEARER RELEASE COMPLETE message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in RADIO BEARER RELEASE message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. SS applies the downlink transmission power settings, according to the values in columns "T1" of table 7.3.3.10 |
||
|
3 |
|
RADIO BEARER RELEASE |
This message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. IE “RB information to reconfigure” includes the next PCDP sequence number that SS is expected to receive from the UE. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
4 |
|
RADIO BEARER RELEASE COMPLETE |
The UE shall transmit this message after it reselects to cell 2. New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. |
|
|
5 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. |
|
|
6 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
7 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
8 |
Void |
|||
|
9 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression PDCP Data PDU). |
||||
|
10 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
11 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
12 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
13 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
14 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
15 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
16 |
Void |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
RADIO BEARER RELEASE for PS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Packet to CELL_DCH from CELL_DCH in PS”, with the following exception:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC identity |
0000 0000 0010B |
|
– S-RNTI |
0000 0000 0000 0000 0001B |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
RB information to release |
|
|
– RB identity |
18 |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is included |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE. |
|
Downlink information for each radio links |
|
|
– Primary CPICH info |
|
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
RADIO BEARER RELEASE for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Packet to CELL_DCH from CELL_DCH in PS”, with the following exception:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC identity |
0000 0000 0010B |
|
– S-RNTI |
0000 0000 0000 0000 0001B |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
RB information to release |
|
|
– RB identity |
13 |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
Downlink information for each radio links |
|
|
– Primary CPICH info |
|
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
RADIO BEARER RELEASE COMPLETE for PS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. |
|
– START list |
Check that this IE is present. |
RADIO BEARER RELEASE COMPLETE for CS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
– START list |
Check that this IE is present. |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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 bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in RADIO BEARER RELEASE message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the RADIO BEARER RELEASE COMPLETE message.
7.3.3.11 Transport Channel Reconfiguration for transition from CELL_DCH to CELL_DCH: Success (Lossless SRNS relocation) (without pending of ciphering)
7.3.3.11.1 Definition
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 IE "Downlink counter synchronisation info"; or
2> re-establish RB2;
2> set the new uplink and downlink HFN component of COUNT-C of RB2 to MAX(uplink HFN component of COUNT-C of RB2, downlink HFN component of COUNT-C of RB2);
2> increment by one the downlink and uplink values of the HFN component of COUNT-C for RB2;
2> calculate the START value according to subclause 8.5.9;
2> include the calculated START values for each CN domain in the IE "START list" in the IE "Uplink counter synchronisation info".
1> if the variable PDCP_SN_INFO is not empty:
2> include the IE "RB with PDCP information list" and set it to the value of the variable PDCP_SN_INFO.
1> if the IE "Integrity protection mode info" was present in the received reconfiguration message:
2> start applying the new integrity protection configuration in the uplink for signalling radio bearer RB2 from and including the transmitted response message.
If the new state is CELL_DCH or CELL_FACH, the response message shall be transmitted using the new configuration after the state transition, and the UE shall:
1> if the IE "Downlink counter synchronisation info" was included in the reconfiguration message; or
2> when RLC has confirmed the successful transmission of the response message:
3> re-establish all AM and UM RLC entities with RB identities larger than 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the corresponding CN domain;
3> re-establish the RLC entities with RB identities 1, 3 and 4 and set the first 20 bits of all the HFN component of the respective COUNT-C values to the START value included in the response message for the CN domain stored in the variable LATEST_CONFIGURED_CN_DOMAIN;
3> set the remaining bits of the HFN component of COUNT-C values of all UM RLC entities to zero;
3> re-initialise the PDCP header compression entities of each radio bearer in the variable ESTABLISHED_RABS as specified in [36].
1> if the variable PDCP_SN_INFO is non-empty:
2> when RLC has confirmed the successful transmission of the response message:
3> for each radio bearer in the variable PDCP_SN_INFO:
4> if the IE "RB started" in the variable ESTABLISHED_RABS is set to "started":
5> configure the RLC entity for that radio bearer to "continue".
3> perform the actions below.
Reference
3GPP TS 25.331 clause 8.2.2.
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.
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 as specified in clause 7.3.1.2.1.4 |
||||
Related ICS/IXIT statements
– Lossless SRNS relocation supported yes/no
– Support of RLC in-sequence delivery Yes/No
Specific Message Content
If network applies ciphering, the contents of SECURITY MODE COMMAND message in the initial condition set-up are identical to the same message sub-type found in [9] TS 34.108 clause 9, with the following exceptions:
|
Information Element |
Value/remark |
|
Ciphering mode info |
|
|
– Ciphering mode command |
Start/restart |
|
– Ciphering algorithm |
UEA1 |
|
– Ciphering activation time for DPCH |
Not Present |
|
– Radio bearer downlink ciphering activation time info |
|
|
– Radio bearer activation time |
|
|
– RB identity |
1 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
2 |
|
– RLC sequence number |
Current RLC SN+2 |
|
– RB identity |
3 |
|
– RLC sequence number |
Current RLC SN + 2 |
|
– RB identity |
4 |
|
– RLC sequence number |
Current RLC SN + 2 |
For RADIO BEARER SETUP message to be transmitted during P13 as specified in TS 34.108 clause 7.4, use the message titled “Packet to CELL_DCH from CELL_DCH in PS” as found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
– PDCP info |
|
|
– Support for lossless SRNS relocation |
TRUE |
|
– Max PDCP SN window size |
sn65535 |
|
– PDCP PDU header |
present |
Test Procedure
Table 7.3.3.11
|
Parameter |
Unit |
Cell 1 |
Cell 2 |
||
|
T0 |
T1 |
T0 |
T1 |
||
|
UTRA RF Channel Number |
Ch. 1 |
Ch. 1 |
|||
|
CPICH Ec (FDD) |
dBm/3.84MHz |
-60 |
-75 |
-75 |
-60 |
Table 7.3.3.11 illustrates the downlink power to be applied for the 2 cells at various time instants of the test execution. Columns marked "T0" denote the initial conditions.
The UE is in the CELL_DCH state, camping onto cell 1. If PS RAB has been established in the initial condition, SS initiates UE to enter loopback mode 1 and sends a PDCP PDU on the RAB. If ciphering is supported, a PDCP PDU has to be decided so that the ciphering activation time is elapsed. SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be send back by the UE and then note the next PDCP SN for the next PDCP PDU. SS configures its downlink transmission power settings according to columns "T1" in table 7.3.3.11. The SS sends a TRANSPORT CHANNEL RECONFIGURATION message requesting the UE to do a handover combined with SRNS relocation. This message includes IE "RRC State Indicator" set to "CELL_DCH", IE “Downlink counter synchronisation info” and IE “Integrity protection mode info”. UE shall reselect to cell 2 and SS verifies that the UE sends TRANSPORT CHANNEL RECONFIGURATION COMPLETE message. This message also includes a calculated new START value according to the formula “STARTX‘ = MSB20 (MAX {COUNT-C, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using a new FRESH value as included in IE “Integrity protection initialisation number” in IE “Integrity protection mode info” in TRANSPORT CHANNEL RECONFIGURATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration, and “Receive PDCP sequence number”.
SS transmits UE CAPABILITY ENQUIRY message on the downlink DCCH using RLC-AM. The UE shall respond to downlink message with a UE CAPABILITY INFORMATION message on the uplink DCCH using RLC-AM. SS resumes the transmission of PDCP PDUs and checks that all transmitted PDCP PDUs are sent back by the UE.
Expected sequence
|
Step |
Direction |
Message |
Comment |
|
|
UE |
SS |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
1a |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
1b |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
2 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
2a |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
2b |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
2c |
Void |
SS shall suspend the sending of PDCP PDUs and wait for the last PDCP PDU to be sent back by the UE and then note the next PDCP SN for the next PDCP PDU. SS applies the downlink transmission power settings, according to the values in columns "T1" of 7.3.3.11. |
||
|
3 |
|
TRANSPORT CHANNEL RECONFIGURATION |
This message is sent after last ciphering activation time has elapsed and there is no pending ciphering activation time. IE “RB information to reconfigure” includes the next PCDP sequence number that SS is expected to receive from the UE. New integrity protection configuration is applied on DL SRB1. LAI and RAI of cell 2 are given to the UE, and are the same as cell 1. |
|
|
4 |
|
TRANSPORT CHANNEL RECONFIGURATION COMPLETE |
The UE shall transmit this message after it reselects to cell 2. New calculated START value is included. IE “Receive PDCP sequence number” shall be included. New integrity protection configuration is applied on UL SRB2. |
|
|
5 |
|
UE CAPABILITY ENQUIRY |
New integrity protection configuration is applied on DL SRB2. |
|
|
6 |
|
UE CAPABILITY INFORMATION |
SS confirms that new integrity protection configuration is applied on UL SRB2 by UE. |
|
|
7 |
|
UE CAPABILITY INFORMATION CONFIRM |
||
|
8 |
Void |
|||
|
9 |
Void |
|||
|
The SS creates a TCP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
10 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
11 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 0 (no IP header compression) Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. |
|||
|
12 |
The RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
|||
|
13 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
14 |
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
|||
|
15 |
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
|||
|
16 |
Void |
|||
|
Deactivate a UE terminated PS session using IP Header compression (using UE test loop mode 1) |
||||
Specific Message Contents
TRANSPORT CHANNEL RECONFIGURATION for PS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Packet to CELL_DCH from CELL_DCH in PS”, with the following exception:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present. |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC identity |
0000 0000 0010B |
|
– S-RNTI |
0000 0000 0000 0000 0001B |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is included. |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
The next PCDP sequence number that SS is expected to receive from the UE. |
|
Downlink information for each radio links |
|
|
– Primary CPICH info |
|
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
TRANSPORT CHANNEL RECONFIGURATION for CS only UE (Step 3)
Use the same message sub-type found in [9] TS 34.108 clause 9, which is entitled “Speech in CS” or “Non speech in CS”, with the following exception:
|
Information Element |
Value/remark |
|
Ciphering mode info |
Not present. |
|
Integrity protection mode info |
|
|
– Integrity protection mode command |
Start |
|
– Downlink integrity protection activation info |
Not Present |
|
– Integrity protection algorithm |
UIA1 |
|
– Integrity protection initialisation number |
SS selects an arbitrary 32 bits number for FRESH |
|
New U-RNTI |
|
|
– SRNC identity |
0000 0000 0010B |
|
– S-RNTI |
0000 0000 0000 0000 0001B |
|
CN Information info |
|
|
– PLMN identity |
Not present |
|
– CN common GSM-MAP NAS system information |
|
|
– GSM-MAP NAS system information |
00 01H |
|
– CN domain related information |
|
|
– CN domain identity |
PS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
05 00H |
|
– CN domain identity |
CS |
|
– CN domain specific NAS system information |
|
|
– GSM-MAP NAS system information |
1E 01H |
|
Downlink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
Downlink information for each radio links |
|
|
– Primary CPICH info |
|
|
– Primary Scrambling Code |
Set to same code as used for cell 2 |
TRANSPORT CHANNEL RECONFIGURATION COMPLETE for PS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
This IE is checked |
|
– RB with PDCP information |
|
|
– RB identity |
20 |
|
– PDCP SN info |
Check that the PCDP sequence number is the next sequence number that SS would transmit to the UE. |
|
– START list |
Check that this IE is present. |
TRANSPORT CHANNEL RECONFIGURATION COMPLETE for CS only UE (Step 4)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9, with the following exception.
|
Information Element |
Value/remark |
|
Uplink counter synchronisation info |
|
|
– RB with PDCP information list |
Not present |
|
– START list |
Check that this IE is present. |
Content of PDCP Data PDUs used for entire test case
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #1: TCP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
UE CAPABILITY ENQUIRY (Step 5)
Use the same message sub-type found in [9] TS 34.108 clause 9.
UE CAPABILITY INFORMATION (Step 6)
Check that the UE uses the same message sub-type found in TS 34.108 clause 9.
UE CAPABILITY INFORMATION CONFIRM (Step 7)
Use the same message sub-type found in [9] TS 34.108 clause 9.
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, COUNT-I | radio bearers and signalling radio bearers using the most recently configured CKX and IKX}) + 2”, calculated IE ”Integrity Check Info” using the new FRESH value as included in IE ”Integrity protection initialisation number” in IE ”Integrity protection mode info” in TRANSPORT CHANNEL RECONFIGURATION message and COUNT-I that includes subsequent HFN as used in the old integrity protection configuration. This message shall also include IE “Receive PDCP sequence number” for RB#20.
After step 5, the UE shall respond with a UE CAPABILITY INFORMATION message to SS.
After step 9, UE shall start transmission on the RAB beginning with the PDCP SN equal to that included in the TRANSPORT CHANNEL RECONFIGURATION COMPLETE message.