7.3.2 IP Header Compression and PID assignment
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.3.2.1 UE in RLC AM
7.3.2.1.1 Transmission of uncompressed Header
7.3.2.1.1.1 Definition and applicability
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences. The UE shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
7.3.2.1.1.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. This function is used for conveyance of data between users of PDCP services.
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
The mapping of the PID values shall follow the general rules listed below:
– PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver;
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
7.3.2.1.1.3 Test purpose
The test case consists of two test procedures:
The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers.
1. To verify, that the UE transmits and receives in acknowledged mode (RLC AM) TCP/IP and UDP/IP data packets without IP header compression as configured by higher layers.
2. To verify, that PID assignment rules are correctly applied, if usage of "PDCP Data" PDU are negotiated, i.e. the UE shall recognize PID value = 0 for a received TCP/IP and UDP/IP data packet and it shall use PID=0 to transmit IP data packets, if no IP header compression is negotiated. If usage of "PDCP No Header" PDU is negotiated, no PID assignment is used for transmitting and receiving TCP/IP and UDP/IP data packets.
7.3.2.1.1.4 Method of test
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108.
Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured.
Test procedure 2: No IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of PS – Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: Test_PDCP_UDP/IP_Packet1
Proc 1 Test procedure 1: Transmission of uncompressed IP header packets using PDCP Data PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC AM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data" PDU has been configured by higher layers.
- The SS sends a TCP/IP data packet with uncompressed IP Header.
- After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PDCP PDU type and shall handle the received data packet with the appropriate decoding method. Then it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration using PDCP Data PDU.
- The SS receives and decodes the TCP/IP data packet. The decoded data packet shall be identical with the data as sent before.
- Step b) to d) shall be repeated by using a UDP/IP data packet with uncompressed IP Header.
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) |
||||
|
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 |
|
|
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. |
||||
|
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 |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
||||
|
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
3 |
|
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 UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes with PID value = 0, there was no IP header compression applied for the UDP/IP packet. Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
4 |
|
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 UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS decodes the received data |
||||
|
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 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 fits to the below described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – Support of lossless SRNS relocation – PDCP PDU header – RLC info – Downlink RLC mode – Uplink RLC mode |
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 34.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 False (IE "Support of lossless SRNS relocation" only present, if RLC "In-sequence delivery" is TRUE and in AM) present (AM RLC) (AM RLC) |
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 Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Proc 2: Test procedure 2: Transmission of uncompressed IP header packets using No Header PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC AM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP No Header" PDU has been configured by higher layers.
- The SS sends a TCP/IP data packet with uncompressed IP Header.
- After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PDCP PDU type and shall handle the received data packet with the appropriate decoding method. Then it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration using PDCP No Header PDU.
- The SS receives and decodes the TCP/IP data packet. The decoded data packet shall be identical with the data as sent before.
- Step b) to d) shall be repeated by using a UDP/IP data packet with uncompressed IP Header.
- 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) |
||||
|
The SS creates a TCP/IP packet without IP header compression (PDCP No Header PDU). |
||||
|
1 |
|
PDCP No Header |
The SS sends a PDCP No Header PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: data: below described TCP/IP packet |
|
|
After having received the PDCP No Header PDU, the UE decodes the PDU and recognizes, there was no PID applied for the TCP/IP packet. Therefore, no IP header decompression shall be applied for this packet. Then, the data packet is forwarded via PDCP-SAP to the 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 No Header |
The UE sends a PDCP No Header PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
||||
|
The SS creates a UDP/IP packet without IP header compression (PDCP No Header PDU). |
||||
|
3 |
|
PDCP No Header |
The SS sends a PDCP No Header PDU using the RLC-AM-Data-Request Primitive with the following content to the UE: data: below described UDP/IP packet |
|
|
After having received the PDCP No Header PDU, the UE decodes the PDU and recognizes, there was no PID applied for the UDP/IP packet. Therefore, no IP header decompression shall be applied for this packet. Then, the data packet is forwarded via PDCP-SAP to the 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. |
||||
|
4 |
|
PDCP No Header |
The UE sends a PDCP No Header PDU using the RLC-AM-Data-Request Primitive with the following content back to the SS: data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS decodes the received data |
||||
|
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 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 fits to the below described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – Support of lossless SRNS relocation – PDCP PDU header – RLC info – Downlink RLC mode – Uplink RLC mode |
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 34.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 False (IE "Support of lossless SRNS relocation" only present, if RLC "In-sequence delivery" is TRUE and in AM) absent (AM RLC) (AM RLC) |
Content of PDCP No Header PDU (Step 1)
|
Information Element |
Value/remark |
|
Data |
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 No Header PDU (Step 3)
|
Information Element |
Value/remark |
|
Data |
PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
7.3.2.1.1.5 Test requirements
Test requirements 1 (Proc 1): Transmission of uncompressed IP header packets using PDCP Data PDU
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
Test requirements 2 (Proc 1): Transmission of uncompressed IP header packets using PDCP No Header PDU (Proc 2)
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP No Header PDU). This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.1.2 Transmission of compressed Header
7.3.2.1.2.1 Definition and applicability
Applicable for all UEs supporting RLC AM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol RFC 2507.
7.3.2.1.2.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. This function is used for conveyance of data between users of PDCP services.
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
7.3.2.1.2.3 Test purpose
1. To verify, that the UE transmits and receives in acknowledged mode (RLC AM) TCP/IP and UDP/IP data packets by using IP header compression protocol as described in RFC2507 as configured by higher layers.
2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID value for the applied optimisation method for transmitting and receiving TCP/IP and UDP/IP data packets.
7.3.2.1.2.4 Method of test
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of IP header compression protocol RFC 2507 – YES/NO.
Support of PS – Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: Test_PDCP_TCP/IP_Packet2
PIXIT: Test_PDCP_UDP/IP_Packet1
PIXIT: Test_PDCP_UDP/IP_Packet2
Test procedure
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC AM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data" PDU has been configured by higher layers.
b) The SS sends a "normal" 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 with the correct decompression protocol. Then, 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 sends a TCP/IP data packet with packet type: Full_Header, PID=1.
NOTE: According to the compression protocol RFC 2507, this is necessary to transmit the created CONTEXT and the assigned CID.
f) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
g) 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.
h) The SS sends a TCP/IP data packet with packet type: Compressed_TCP, PID=2.
i) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
j) 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.
k) Step b) to d) is repeated for a "normal" UDP/IP data packet, PID=0.
l) Step e) to g) is repeated for a UDP/IP data packet with packet type: Full_Header, PID=1.
m) The SS sends a UDP/IP data packet with packet type: Compressed_non_TCP, PID=4.
n) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
o) The SS receives and decodes the UDP/IP data packet according to the inserted PID. The decoded data packet shall be identical with the data as sent before.
p) The SS deactivates the UE tests loop mode 1 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) |
||||
|
The SS creates a TCP/IP packet without IP header compression. |
||||
|
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 |
|
|
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. |
||||
|
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 to 3 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 |
|
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 = 1 (Full_Header packet type [TCP/IP]) data: below described TCP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU, recognizes PID value = 1 applied for this TCP/IP data packet and decompresses it with the appropriate method. 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. |
||||
|
4 |
|
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 to 3 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. |
||||
|
5 |
|
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 = 2 (Compressed_TCP packet type) data: below described TCP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU, recognizes PID value = 2 applied for this TCP/IP data packet and decompress it with the appropriate method. 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. |
||||
|
6 |
|
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 to 3 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. |
||||
|
The SS creates a UDP/IP packet without compressed IP header compression. |
||||
|
7 |
|
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 UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes with PID value = 0, there was no IP header compression applied for the UDP/IP packet. Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
8 |
|
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 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
9 |
|
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 = 1 (Full_Header packet type) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 1 applied for this UDP/IP data packet and decompress it with the appropriate method. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
10 |
|
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 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
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 = 4 (Compressed _non-TCP packet type) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 4 applied for this UDP/IP data packet and decompress it with the appropriate method. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
12 |
|
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 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: previously received UDP/IP packet |
|
|
After reception of this UDP/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 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 |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – 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 – RLC info – Downlink RLC mode – Uplink RLC mode |
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 34.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 False (IE "Support of lossless SRNS relocation" only present, if RLC "In-sequence delivery" is TRUE and in AM) present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) (AM RLC) (AM RLC) |
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 Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) PDCP test data type #1: TCP/IP data packet with full TCP/IP header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 5)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00010 (Compressed_TCP, PID = 2) PDCP test data type #1: TCP/IP data packet with a compressed header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 7)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 9)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) PDCP test data type #2: UDP/IP data packet with full UDP/IP header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 11)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00100 (Compressed_non-TCP, PID = 4) PDCP test data type #2: UDP/IP data packet with a compressed header with any data content. The data shall be limited to 1500 bytes. |
7.3.2.1.2.5 Test requirements
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled with the correct compression protocol. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.2 UE in RLC UM
7.3.2.2.1 Transmission of uncompressed Header
7.3.2.2.1.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with TCP/IP and UDP/IP data packets with uncompressed IP header.
7.3.2.2.1.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. This function is used for conveyance of data between users of PDCP services
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
The mapping of the PID values shall follow the general rules listed below:
– PID value "0" shall indicate "no compression". PID value "0" shall be used in a PDCP PDU containing in its Data field a PDCP SDU that is unchanged by the Sender and that shall not be decompressed by the Receiver;
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
7.3.2.2.1.3 Test purpose
The test case consists of two test procedures:
The first test procedure verifies, that the "PDCP Data" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers. The second test procedure verifies, that the "PDCP No header" PDU is used for uncompressed IP header packets, if no IP header compression is configured by higher layers.
1. To verify, that the UE transmits and receives in unacknowledged mode (RLC UM) TCP/IP and UDP/IP data packets without IP header compression as configured by higher layers.
2. To verify, that PID assignment rules are correctly applied, if usage of "PDCP Data" PDU are negotiated, i.e. the UE shall recognize PID value = 0 for a received TCP/IP and UDP/IP data packet and it shall use PID=0 to transmit IP data packets, if no IP header compression is negotiated. If usage of "PDCP No Header" PDU is negotiated, no PID assignment is used for transmitting and receiving TCP/IP and UDP/IP data packets.
7.3.2.2.1.4 Method of test
Initial conditions
UE is in Idle mode.
Test procedure 1: Usage of "PDCP Data" PDU and no IP header compression is configured.
Test procedure 2: no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of PS – Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: Test_PDCP_UDP/IP_Packet1
Proc 1: Test procedure 1: Transmission of uncompressed IP header packets using PDCP Data PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC UM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data" PDU has been configured by higher layers.
- The SS sends a TCP/IP data packet with uncompressed IP Header.
- After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PDCP PDU type and shall handle the received data packet with the appropriate decoding method. Then it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration using PDCP Data PDU.
- The SS receives and decodes the TCP/IP data packet. The decoded data packet shall be identical with the data as sent before.
- Step b) to d) shall be repeated by using a UDP/IP data packet with uncompressed IP Header.
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 UM RLC (using UE test loop mode 1) |
||||
|
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-UM-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 |
|
|
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. |
||||
|
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-UM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
||||
|
The SS creates a UDP/IP packet without IP header compression (PDCP Data PDU). |
||||
|
3 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes with PID value = 0, there was no IP header compression applied for the UDP/IP packet. Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
4 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS decodes the received data |
||||
|
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 UM 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 UM) 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 UM 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 UM) which fits to the below described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – PDCP PDU header – RLC info – Downlink RLC mode |
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 UM RLC Residual BER as described in TS 34.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 21 present (UM RLC) |
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 Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Proc 2: Test procedure 2: Transmission of uncompressed IP header packets using No Header PDU
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC UM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP No Header" PDU has been configured by higher layers.
- The SS sends a TCP/IP data packet with uncompressed IP Header.
- After having received the TCP/IP data packet, the PDCP entity of the UE shall recognize the PDCP PDU type and shall handle the received data packet with the appropriate decoding method. Then it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration using PDCP No Header PDU.
- The SS receives and decodes the TCP/IP data packet. The decoded data packet shall be identical with the data as sent before.
- Step b) to d) shall be repeated by using a UDP/IP data packet with uncompressed IP Header.
- The SS deactivates the Loop back test mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated PS session using IP Header compression in UM RLC (using UE test loop mode 1) |
||||
|
The SS creates a TCP/IP packet without IP header compression (PDCP No Header PDU). |
||||
|
1 |
|
PDCP No Header |
The SS sends a PDCP No Header PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: data: below described TCP/IP packet |
|
|
After having received the PDCP No Header PDU, the UE decodes the PDU and recognizes, there was no PID applied for the TCP/IP packet. Therefore, no IP header decompression shall be applied for this packet. Then, the data packet is forwarded via PDCP-SAP to the 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 No Header |
The UE sends a PDCP No Header PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: data: previously received TCP/IP packet |
|
|
After reception of this TCP/IP data packet, the SS applies the appropriate decoding function for the received data |
||||
|
The SS creates a UDP/IP packet without IP header compression (PDCP No Header PDU). |
||||
|
3 |
|
PDCP No Header |
The SS sends a PDCP No Header PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: data: below described UDP/IP packet |
|
|
After having received the PDCP No Header PDU, the UE decodes the PDU and recognizes, there was no PID applied for the UDP/IP packet. Therefore, no IP header decompression shall be applied for this packet. Then, the data packet is forwarded via PDCP-SAP to the 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. |
||||
|
4 |
|
PDCP No Header |
The UE sends a PDCP No Header PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS decodes the received data |
||||
|
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 UM 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 UM) 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 UM 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 UM) which fits to the below described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – PDCP PDU header – RLC info – Downlink RLC mode – Uplink RLC mode |
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 UM RLC Residual BER as described in TS 34.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 21 False absent (UM RLC) (UM RLC) |
Content of PDCP No Header PDU (Step 1)
|
Information Element |
Value/remark |
|
Data |
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 No Header PDU (Step 3)
|
Information Element |
Value/remark |
|
Data |
PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
7.3.2.2.1.5 Test requirements
Test requirements 1 (Proc 1): Transmission of uncompressed IP header packets using PDCP Data PDU
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP Data PDU). This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
Test requirements 2 (Proc 2): Transmission of uncompressed IP header packets using PDCP No Header PDU
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled correctly (PDCP No Header PDU). This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.2.2 Transmission of compressed Header
7.3.2.2.2.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with compressed TCP/IP and UDP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol RFC 2507.
7.3.2.2.2.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. This function is used for conveyance of data between users of PDCP services.
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
7.3.2.2.2.3 Test purpose
1. To verify, that the UE transmits and receives in unacknowledged mode (RLC UM) TCP/IP and UDP/IP data packets by using IP header compression protocol as described in RFC2507 as configured by higher layers.
2. To verify, that the PID assignment rules are correctly applied by the UE. The UE as shall use the correct PID value for the applied optimisation method for transmitting and receiving TCP/IP and UDP/IP data packets.
7.3.2.2.2.4 Method of test
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of IP header compression protocol RFC 2507 – YES/NO
Support of PS – Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: Test_PDCP_TCP/IP_Packet2
PIXIT: Test_PDCP_UDP/IP_Packet1
PIXIT: Test_PDCP_UDP/IP_Packet2
Test procedure
a) The SS setups a packet switched session including radio bearer and UE test loop mode 1 in RLC UM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data" PDU has been configured by higher layers.
b) The SS sends a "normal" 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 with the correct decompression protocol. Then, 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 sends a TCP/IP data packet with packet type: Full_Header, PID=1.
NOTE: According to the compression protocol RFC 2507, this is necessary to transmit the created CONTEXT and the assigned CID.
f) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
g) 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.
h) The SS sends a TCP/IP data packet with packet type: Compressed_TCP, PID=2.
i) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
j) 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.
k) Step b) to d) is repeated for a "normal" UDP/IP data packet, PID=0.
l) Step e) to g) is repeated for a UDP/IP data packet with packet type: Full_Header, PID=1.
m) The SS sends a UDP/IP data packet with packet type: Compressed_non_TCP, PID=4.
n) 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 with the correct decompression protocol. Then, it forwards the data to its Radio Bearer Loop Back entity. The received data shall be returned by the UE via its PDCP configuration.
o) The SS receives and decodes the UDP/IP data packet according to the inserted PID. The decoded data packet shall be identical with the data as sent before.
p) The SS deactivates the UE test loop test mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated PS session using IP Header compression in UM RLC (using UE test loop mode 1) |
||||
|
The SS creates a TCP/IP packet without IP header compression. |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-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 |
|
|
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. |
||||
|
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-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 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 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 1 (Full_Header packet type [TCP/IP]) data: below described TCP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU, recognizes PID value = 1 applied for this TCP/IP data packet and decompresses it with the appropriate method. 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. |
||||
|
4 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 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. |
||||
|
5 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 2 (Compressed_TCP packet type) data: below described TCP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU, recognizes PID value = 2 applied for this TCP/IP data packet and decompress it with the appropriate method. 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. |
||||
|
6 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 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. |
||||
|
The SS creates a UDP/IP packet without compressed IP header compression. |
||||
|
7 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes with PID value = 0, there was no IP header compression applied for the UDP/IP packet. Therefore, no IP header decompression is applied for this packet. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
8 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: previously received UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
9 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 1 (Full_Header packet type) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 1 applied for this UDP/IP data packet and decompress it with the appropriate method. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
10 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: below described UDP/IP packet |
|
|
After reception of this UDP/IP data packet, the SS applies the appropriate decoding function depending on the assigned PID. |
||||
|
11 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 4 (Compressed _non-TCP packet type) data: below described UDP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 1 applied for this UDP/IP data packet and decompress it with the appropriate method. The data packet is forwarded via PDCP-SAP to the 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. |
||||
|
12 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (Data PDU with Header) PID value = 0,1 or 4 (depending on which UDP/IP header format is used by the UE) data: previously received UDP/IP packet |
|
|
After reception of this UDP/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 UM 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 UM) 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 UM 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 UM) which fit to the here described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – 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 – RLC info – Downlink RLC mode – Uplink RLC mode |
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 UM RLC Residual BER as described in TS 34.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 21 False present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) (UM RLC) (UM RLC) |
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 Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) PDCP test data type #1: TCP/IP data packet with full TCP/IP header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 5)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00010 (Compressed_TCP, PID = 2) PDCP test data type #1: TCP/IP data packet with a compressed header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 7)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00000 (No header compression, PID = 0) PDCP test data type #2: UDP/IP data packet without IP header compression with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 9)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) PDCP test data type #2: UDP/IP data packet with full UDP/IP header with any data content. The data shall be limited to 1500 bytes. |
Content of PDCP Data PDU (Step 11)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00100 (Compressed_non-TCP, PID = 4) PDCP test data type #2: UDP/IP data packet with a compressed header with any data content. The data shall be limited to 1500 bytes. |
7.3.2.2.2.5 Test requirements
The UE shall return the TCP/IP and UDP/IP data packets as indication, that the previous packets have been received and handled with the correct compression method. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.2.3 Extension of used compression methods
7.3.2.2.3.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity which applies IP header compression protocol: RFC 2507.
7.3.2.2.3.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. Transmission of user data means that PDCP receives PDCP SDU from the NAS and forwards it to the RLC layer and vice versa;
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
3. The mapping of the PID values shall follow the general rules listed below:
– PID values are re-mapped for the PDCP entity after any reconfiguration of the header compression protocols for that entity.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1
TS 25.323 clause 5.1.1.
7.3.2.2.3.3 Test purpose
1. To verify, that the UE is able to handle an extended PID value allocation table by header compression protocol IETF RFC 2507 after PDCP reconfiguration as configured by RRC.
7.3.2.2.3.4 Method of test
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of IP header compression protocol RFC 2507 – YES/NO
Support of PS – Yes/No
PIXIT: Test_PDCP_TCP/IP_Packet1
PIXIT: 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 UM using Common test procedures for mobile terminated PS switched sessions (with the UE test loop mode 1). Usage of "PDCP Data PDU" and no optimisation method has been configured by higher layers.
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 UM is still active.
f) The SS sends a TCP/IP data packet (no compression packet type), PID=0.
g) 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.
h) 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.
i) The SS sends a TCP/IP data packet with packet type: Full_Header, PID=1.
j) 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.
k) 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.
l) 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 UM RLC (using UE test loop mode 1) |
||||
|
The SS creates a TCP/IP packet without IP header compression. |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-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 |
|
|
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-UM-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 Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (normal packet type [TCP/IP]) data: below described TCP/IP packet. |
|
|
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. |
||||
|
6 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 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. |
||||
|
7 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 1 (Full_Header packet type [TCP/IP]) data: below described TCP/IP packet |
|
|
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes PID value = 1 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 RB LB entity in UE test loop mode 1 returns the received data packet and sends it back to its PDCP entity. |
||||
|
8 |
|
PDCP Data |
The UE sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 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 UM 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 UM) with the following exceptions:
|
Information Element |
Value/remark |
|
RB information to reconfigure list RB information to reconfigure – PDCP info – 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 present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) |
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 UM 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 UM) 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 UM 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 UM) which fit to the here described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – PDCP PDU header – RLC info – Downlink RLC mode – Uplink RLC mode |
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 UM RLC Residual BER as described in TS 34.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 21 present (UM RLC) (UM RLC) |
Content of PDCP Data PDU (Step 1 and 5)
|
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 Data PDU (Step 7)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) 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.2.2.3.5 Test requirements
After PDCP reconfiguration, the UE shall return the TCP/IP data packets as indication, that the extension of used optimisation method are applied by UE. This verifies, that the PDCP configuration on UE side works as negotiated by the RRC. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.2.4 Compression type used for different entities
7.3.2.2.4.1 Definition and applicability
Applicable only for an UE supporting the establishment of more than one PDCP entity in parallel, i.e. it shall be possible to configure more than one Radio Bearer Loop Back entities (each PDCP entity are assigned via PDCP-SAP to its own Radio Bearer Loop Back entity).
Applicable for all UEs supporting two Radio Bearers in RLC UM and RLC AM as described in this test case, clause 7.3.2.2.4.6 Combined PDCP Acknowledged and Unacknowledged mode configuration.
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore it shall apply IP header compression protocol RFC 2507.
7.3.2.2.4.2 Conformance requirement
1. The Packet Data Convergence Protocol shall perform the following functions:
– transfer of user data. This function is used for conveyance of data between users of PDCP services.
2. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
3. The mapping of the PID values shall follow the general rules listed below:
– PID values shall be mapped to the different packet types independently at each PDCP entity;
Several PDCP entities may be defined for a UE with each using the same or different protocol type. In this version of the specification, only one header compression protocol type, RFC 2507 [6], is supported.
Reference(s)
TS 25.323 clause 5.
TS 25.323 clause 5.1.1.
TS 25.323 clause 4.2.
7.3.2.2.4.3 Test purpose
1. To verify, that a configured IP header compression protocol are applied to compress and decompress TCP/IP data packets by several PDCP entities in parallel, if more than one entities are established, i.e. the UE uses the same PID to transmit two TCP/IP data packets with the same content in parallel using two Radio Bearer configurations.
7.3.2.2.4.4 Method of test
NOTE: For this test case, the SS shall be configured to handle more than one received PDCP messages.
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and IP header compression is configured for both PDCP entities.
Related ICS/IXIT Statement(s)
Establishment of more than one PDCP entities – YES/NO.
Support of IP header compression protocol RFC 2507 – YES/NO
Support of UM RB and AM RB
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 two radio bearer configurations in parallel in UE test loop mode 1 and in RLC UM and RLC UM using Common test procedures for mobile terminated PS switched sessions. Usage of IP header compression protocol RFC 2507 has been configured by higher layers.
b) The SS sends two successive "normal" TCP/IP data packet, PID=0 via both PDCP configurations to their peer entities.
c) After having received the TCP/IP data packets, the PDCP entities of the UE shall recognize the PID value and shall handle the received data packet independent of the used PID with the correct decompression method. Then they forward the data to their Radio Bearer Loop Back entity. Both received data shall be returned by each Radio Bearer Loop Back entity.
d) 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.
e) The SS sends two successive TCP/IP data packets with full header (PID=1) via both PDCP configurations to their peer entities.
f) After having received the TCP/IP data packets, the PDCP entities of the UE shall recognize the PID value and shall handle the received data packets independent of the used PID with the correct decompression method. Then they forward the data to their Radio Bearer Loop Back entity. Both received data shall be returned by each Radio Bearer Loop Back entity.
g) 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.
h) 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 UM RLC (using UE test loop mode 1) |
||||
|
1 |
|
PDCP Data |
The SS sends two successive PDCP Data PDUs using the RLC-UM-Data-Request Primitive via both PDCP entities with the following contents to the UE: PDU type = 000 (PDCP Data PDU) PID = 0 (uncompressed IP header) data: below described TCP/IP packet |
|
|
After having received both PDCP Data PDUs, the UE decodes each PDU and recognizes PID value = 0 (no IP header compression applied for both TCP/IP data packets). Although the same PID is used for both PDUs, the UE shall handle they with the correct method and it forwards both data packets via PDCP-SAPs to their Radio Bearer Loop Back (RB LB) entities. |
||||
|
The RB LB entities in UE test loop mode 1 return the received data packets and send they back to their PDCP entities. |
||||
|
2 |
|
PDCP Data |
The UE sends back for each PDCP configuration a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 data: previously received TCP/IP packet |
|
|
After reception of TCP/IP data packets, the SS applies the appropriate decoding function for both received messages depending on which PID was assigned to the received data |
||||
|
3 |
|
PDCP Data |
The SS sends two successive PDCP Data PDUs using the RLC-UM-Data-Request Primitive via both PDCP entities with the following contents to the UE: PDU type = 000 (PDCP Data PDU) PID = 1 (Full_Header packet type [TCP/IP]) data: below described TCP/IP packet |
|
|
After having received both PDCP Data PDUs, the UE decodes each PDU and recognizes PID value = 1 (Full_Header packet type applied for both TCP/IP data packets). Although the same PID is used for both PDUs, the UE shall handle they with the correct method and it forwards both data packets via PDCP-SAPs to their Radio Bearer Loop Back (RB LB) entities. |
||||
|
The RB LB entities in UE test loop mode 1 return the received data packets and send they back to their PDCP entities. |
||||
|
4 |
|
PDCP Data |
The UE sends back for each PDCP configuration a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 000 (PDCP Data PDU) PID value = 0 to 3 data: previously received TCP/IP packet |
|
|
After reception of TCP/IP data packets, the SS applies the appropriate decoding function for both received messages depending on which PID was assigned to the received data |
||||
|
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 UM 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 UM) 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 UM 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 UM) which fit to the here described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – 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 – RLC info – Downlink RLC mode – Uplink RLC mode – RB information to setup – RB identity – PDCP info – 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 – RLC info – Downlink RLC mode – Uplink RLC mode |
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 UM RLC configuration for UM RLC Residual BER as described in TS 34.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 present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) (AM RLC) (AM RLC) (NOTE: for RB ID 21, the same RAB configurations are used (No. # 23 as described in TS 34.108) as described for RB ID 20) 21 present 1 256 (Default) 5 (Default) 168 (Default) 15 (Default) 15 (Default) reordering not expected (Default) (UM RLC) (UM RLC) |
Content of both 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 both PDCP Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Full_Header, PID = 1) PDCP test data type #1: TCP/IP data packet with full TCP/IP header compression with any data content. The data shall be limited to 1500 bytes. |
7.3.2.2.4.5 Test requirements
The UE shall return both TCP/IP data packets as indication that the previous received data packets associated with the same PID value are handled in parallel with the same decompression protocol. This verifies, that more than one PDCP configuration on UE side using the same compression protocol is able to apply it in parallel. An invalid PDU type as well as unconfigured PID values shall not be received by SS.
7.3.2.2.4.6 Combined PDCP Acknowledged and Unacknowledged mode configuration
This configuration is based on the interactive or background / UL:64 DL 64 kbps / PS RAB. The SRB configurations are UL:3.4 DL:3.4 kbps for DCCH aligned to this combined RABs are described for SRB DL 3.4 kbps in TS 34.108, clause 6.10.2.4.1.2.2 and for SRB DL 3.4 kbps in TS 34.108, clause 6.10.2.4.1.2.1. The TFCS refer to TS34.108, clause 6.10.2.4.1.24.1.1.3 for UL and clause 6.10.2.4.1.25.2.1.3 for DL, the Physical channel parameters refer to TS 34.108, clause 6.10.2.4.1.24.1.2 for UL clause 6.10.2.4.1.25.2.2 and for DL accordingly. The configuration is applied to PDCP test cases using both the acknowledged and unacknowledged mode.
Table 7.3.2.2.4/1: Uplink Transport channel parameter for combined RABs PS AM_UM
|
Higher layer |
RAB/Signalling RB |
RAB #20 |
RAB #21 |
|
|
RLC |
Logical channel type |
DTCH |
DTCH |
|
|
RLC mode |
AM |
UM |
||
|
Payload sizes, bit |
316 |
324 |
||
|
Max data rate, bps |
63200 |
64800 |
||
|
TrD PDU header, bit |
16 |
8 |
||
|
MAC |
MAC header, bit |
4 |
||
|
MAC multiplexing |
2 logical channel multiplexing |
|||
|
Layer 1 |
TrCH type |
DCH |
||
|
TB sizes, bit |
336 |
|||
|
TFS |
TF0, bits |
0x336 |
||
|
TF1, bits |
1×336 |
|||
|
TF2, bits |
2×336 |
|||
|
TF3, bits |
3×336 |
|||
|
TF4, bits |
4×336 |
|||
|
TTI, ms |
20 |
|||
|
Coding type |
TC |
|||
|
CRC, bit |
16 |
|||
|
Max number of bits/TTI after channel coding |
4236 |
|||
|
Uplink: Max number of bits/radio frame before rate matching |
2118 |
|||
|
RM attribute |
130-170 |
|||
Table 7.3.2.2.4/2: Downlink Transport channel parameter for combined RABs PS AM_UM
|
Higher layer |
RAB/Signalling RB |
RAB #20 |
RAB #21 |
|
|
RLC |
Logical channel type |
DTCH |
DTCH |
|
|
RLC mode |
AM |
UM |
||
|
Payload sizes, bit |
316 |
324 |
||
|
Max data rate, bps |
63200 |
64800 |
||
|
TrD PDU header, bit |
16 |
8 |
||
|
MAC |
MAC header, bit |
4 |
||
|
MAC multiplexing |
2 logical channel multiplexing |
|||
|
Layer 1 |
TrCH type |
DCH |
||
|
TB sizes, bit |
336 |
|||
|
TFS |
TF0, bits |
0x336 |
||
|
TF1, bits |
1×336 |
|||
|
TF2, bits |
2×336 |
|||
|
TF3, bits |
3×336 |
|||
|
TF4, bits |
4×336 |
|||
|
TTI, ms |
20 |
|||
|
Coding type |
TC |
|||
|
CRC, bit |
16 |
|||
|
Max number of bits/TTI after channel coding |
4236 |
|||
|
RM attribute |
130-170 |
|||
7.3.2.2.5 Reception of not defined PID values
7.3.2.2.5.1 Definition and applicability
Applicable for all UEs supporting RLC UM and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with compressed TCP/IP data packets and furthermore to establish a PDCP entity, which applies PDCP Data PDU if no IP header compression protocol, is negotiated.
The UE shall not forward invalid PDCP PDU data contents to its Radio Bearer.
7.3.2.2.5.2 Conformance requirement
1. Depending on the configuration by upper layers (i.e. PDCP PDU type to be used and header compressor protocol), the PDCP sublayer shall be able to:
– identify the correct header compression protocol; and
– distinguish different types of header compression packets within a header compression protocol.
2. If a PDCP entity receives a PDCP PDU with a PID value that is not mapped with a valid packet type (see TS 25.323 subclause 5.1.1), it shall:
– discard the PDCP PDU.
Reference(s)
TS 25.323 clause 5.1.1.
TS 25.323 clause 9.2.
7.3.2.2.5.3 Test purpose
1. To verify, that a UE considers a received PDCP PDU message with not defined PID value as invalid, i.e. such an invalid PDCP PDU is not forwarded to the Radio Bearer entity on UE side. Therefore the UE using test loop mode 1 does not return such data packet to the SS.
7.3.2.2.5.4 Method of test
Initial conditions
UE is in Idle mode (state 3 or state 7) as specified in clause 7.4 of TS 34.108. Usage of "PDCP Data" PDU and no IP header compression is configured.
Related ICS/IXIT Statement(s)
Support of IP header compression protocol RFC 2507 – YES/NO
Support of PS – Yes/No
IXIT: Test_PDCP_TCP/IP_Packet1
IXIT: 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 UM using Common test procedures for mobile terminated PS switched sessions. Usage of "PDCP Data PDU" and no PDCP IP header compression protocol has been configured by higher layers.
b) The SS sends a "normal" 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 with the correct decoding method. 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 TCP/IP data packets according to the inserted PID. The decoded data packets shall be identical with the data as sent before.
e) The SS sends a TCP/IP data packet with PID=1. See note 1.
f) 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 with the correct decoding method.
g) The SS waits an amount of time to make sure, that no returned data packet was sent by UE.
h) The SS deactivates the UE test loop mode and terminates the connection.
NOTE 1 As no PDCP IP header compression protocol has been configured only PID=0 shall be recognised by the UE and PID=1 shall be considered as invalid PID value by the UE).
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated PS session using IP Header compression in UM RLC (using UE test loop mode 1) |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-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 |
|
|
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-UM-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 |
|
PDCP Data |
The SS sends a PDCP Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 000 (PDCP Data PDU) PID = 1 (Full_Header packet type [TCP/IP]) data: below described TCP/IP packet. |
|
|
After having received the PDCP Data PDU, the UE shall recognize, that a not defined PID value (as configured by higher layers) is inserted in the PDCP PDU. The UE shall consider this PDU as invalid, i.e. the data packet is not forwarded via PDCP-SAP to its Radio Bearer Loop Back (RB LB) entity. Therefore this data packet is not returned to the SS. |
||||
|
4 |
The SS waits a amount of time to make sure, that the previously sent data packet is not returned to the SS. |
|||
|
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 UM 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 UM) 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 UM 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 UM) which fit to the here described parameters with the following exceptions:
|
Information Element |
Value/remark |
|
RAB information for setup – RAB info – RAB identity – CN domain identity – RB information to setup – RB identity – PDCP info – PDCP PDU header – RLC info – Downlink RLC mode – Uplink RLC mode |
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 UM RLC Residual BER as described in TS 34.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 21 present (UM RLC) (UM RLC) |
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 Data PDU (Step 3)
|
Information Element |
Value/remark |
|
PDU type PID Data |
000 00001 (Invalid PID value, PID = 1) PDCP test data type #1: TCP/IP data packet with full TCP/IP header compression with any data content. The data shall be limited to 1500 bytes. |
7.3.2.2.5.5 Test requirements
The UE shall return the received TCP/IP data packet using the PDCP Data PDU with PID = 0.
The UE shall not return the TCP/IP data packet using the PDCP Data PDU with PID = 1.