7.3.7 PDCP AMR Data PDU testing
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.3.7.1 PDCP AMR Data PDU testing
7.3.7.1.1 Definition and applicability
Applicable for all UEs supporting CS Voice over HSPA and a Radio Bearer as described in the Common Test Sequences.
The UE shall be capable to deal with AMR data PDU and to correctly set the value of the CS counter.
7.3.7.1.2 Conformance requirement
The Packet Data Convergence Protocol shall perform the following functions:
– header compression and decompression of IP data streams (e.g., TCP/IP and RTP/UDP/IP headers for IPv4 and IPv6) at the transmitting and receiving entity, respectively.
– transfer of user data. This function is used for conveyance of data between users of PDCP services.
– maintenance of PDCP sequence numbers for radio bearers that are configured to support lossless SRNS Relocation or lossless DL RLC PDU size change.
– transfer of CS counter if the radio bearer is configured to convey AMR and AMR WB frames.
– add and remove the padding in PDCP PDU for octet alignment.
PDCP uses the services provided by the Radio Link Control (RLC) sublayer.
(…)
If radio bearer is configured to convey AMR or AMR WB frames for every 20ms, the sender shall :
– if the PDCP SDU length is of 0 bit or no PDCP SDU is received by PDCP entity:
– discard the PDCP SDU if any and no PDCP PDU is submitted to the lower layer;
– if the PDCP SDU length is of 1 or more bits:
– include the CS counter in the PDCP AMR Data PDU as specified in subclause 5.6.1.4 of TS 25.323;
– indicate the PDCP AMR PDU type in the PDU type field;
– fill the data field of the PDCP AMR PDU type with the PDCP SDU and add padding bits as specified in subclause 8.2.4 of TS 25.323
– increment the CS counter;
When the PDCP entity at the Receiver receives the PDCP PDU from lower layers, it shall:
– if the received PDCP PDU is of type PDCP AMR Data PDU:
– the PDCP SDU is derived from the data field of the PDCP AMR Data PDU. The receiver determines the bit aligned data content and Frame Type from the PDU Data field length, as possible AMR and AMR WB payload has a unique size when being octet aligned;
– deliver the PDCP SDU and CS counter from the received PDCP header to the upper layer. (…)
In case the radio bearer is configured to convey AMR or AMR WB frames, the CS counter shall be included in the PDCP AMR Data PDU.
The value of the CS counter shall be set to the first to fifth LSBs of the CFN at which the packet has been received from higher layers.
(…)
The PDU type field indicates the PDCP Data PDU type.
|
Bit |
PDU Type |
|
000 |
PDCP Data PDU (Table 7) |
|
001 |
PDCP SeqNum PDU (Table 8) |
|
010 |
PDCP AMR Data PDU (Table 9) |
|
011-111 |
Reserved (PDUs with this encoding are invalid for this version of the protocol) |
(…)
The PDCP AMR Data PDU is used to convey:
– a PDCP SDU containing AMR or AMR WB frame
The format of the PDCP AMR Data PDU is shown in Table 9.
Table 9: PDCP AMR Data PDU format
|
PDU type |
CS counter |
|
Data |
|
The PDCP PDU is octet aligned but the actual PDCP SDU carrying the AMR or AMR WB frame may not be octet aligned. The AMR classes are always encoded in the order of class A, B and C, where the first bit of data follows immediately after the CS counter field and any padding for octet alignment is inserted at the end of the data field.
(…)
Length: 5 bits
CS counter field value indicates the timing of AMR or AMR WB frame.
Reference(s)
TS 25.323 clauses 5, 5.3, 5.6.1.4, 8.3.1, 8.2.4, 8.3.5
7.3.7.1.3 Test purpose
1. To verify that the UE transmits and receives AMR Data PDU in unacknowledged mode (RLC UM) as configured by higher layers.
2. To verify that the UE includes the CS counter and sets it to the first to fifth LSBs of the CFN at which the packet has been received from higher layers.
7.3.7.1.4 Method of test
Initial conditions
UE is in Idle mode (state 2 or state 7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT Statement(s)
Support of CS Voice over HSPA (Yes/No)
Test procedure
a) The SS setups a circuit switched session including radio bearer and UE test loop mode 1 in RLC UM using Common test procedures for mobile terminated CS switched sessions. Usage of "PDCP AMR Data" PDU has been configured by higher layers.
b) The SS sends an AMR data packet.
c) After having received the AMR data packet, the PDCP entity of the UE shall recognize the PDCP PDU type and shall handle the received AMR 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 AMR Data PDU. The CS counter field of the PDCP AMR Data PDU looped back shall be set to the first to fifth LSBs of the CFN at which the packet has been received from higher layers.
d) The SS receives and decodes the data packet. The decoded data packet shall be identical with the data as sent before. The SS verifies that the CS counter is set to the first to fifth LSBs of a CFN value comprised between (current CFN – 4) and (current CFN).
e) Steps b) through d) are repeated 10 times, with 500 ms between the sending of each AMR data packet in the downlink.
f) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated CS session (using UE test loop mode 1) |
||||
|
The SS creates an AMR data packet (PDCP AMR Data PDU). |
||||
|
1 |
|
PDCP Data |
The SS sends a PDCP AMR Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 010 (PDCP AMR Data PDU) CS counter = first to fifth LSBs of the CFN at which the packet has been received from higher layers data: below described AMR frames |
|
|
After having received the PDCP AMR Data PDU, the UE decodes the PDU and recognizes PDU type = 010 (PDCP AMR Data PDU) The AMR 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 AMR Data PDU using the RLC-UM-Data-Request Primitive with the following content back to the SS: PDU type = 010 (PDCP AMR Data PDU) CS counter = first to fifth LSBs of the CFN at which the packet has been received from higher layers data: previously received AMR frames |
|
|
After reception of this AMR data packet, the SS applies the appropriate decoding function for the received data and verifies that CS counter is set to the first to fifth LSBs of a CFN value comprised between (current CFN – 4) and (current CFN) |
||||
|
Steps 1-2 are repeated 10 times, with 500 ms between the sending of each AMR data packet in the downlink |
||||
|
Deactivate a UE terminated CS session (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 CS session in UM RLC" of this test case are identical to those of the default contents of layer 3 messages for RRC tests [TS 34.123-1] (CS connection) 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 are identical to “Speech to CELL_DCH / E-DCH / HS-DSCH CS RAB with DTX/DRX and enhanced data rate using one multiplexing option (1/1) and SRBs mapped on E-DCH/HS-DSCH (Condition A23) , with the following exceptions
|
Information Element |
Value/remark |
|
– CS-HSPA information |
|
|
– UL AMR rate |
Not Present |
|
– Max CS delay |
100 |
Content of PDCP Data PDU (Step 1)
|
Information Element |
Value/remark |
|
PDU type CS counter Data |
010 first to fifth LSBs of the CFN at which the packet has been received from higher layers 244 bits of AMR data + 4 bits of padding |
Content of PDCP Data PDU (Step 2)
|
Information Element |
Value/remark |
|
PDU type CS counter Data |
010 first to fifth LSBs of the CFN at which the packet has been received from higher layers Same content as Data from PDCP Data PDU at Step 1 |
7.3.7.1.5 Test requirements
After having received the AMR data packet conveyed with the "PDCP AMR Data" PDU, the UE shall return the data packets as indication that the previous packets have been received and handled correctly (PDCP AMR Data PDU).
The CS counter in the PDCP AMR Data PDUs received from the UE shall be set to the first to fifth LSBs of a CFN value comprised between (current CFN – 4) and (current CFN).
7.3.7.2 PDCP Unrecoverable Error Detection
7.3.7.2.1 Definition and applicability
Applicable for all UEs supporting CS Voice over HSPA and a Radio Bearer as described in the Common Test Sequences.
-
-
-
-
- Conformance requirement
-
-
-
Length: 3 bits.
The PDU type field indicates the PDCP Data PDU type.
|
Bit |
PDU Type |
|
000 |
PDCP Data PDU (Table 7) |
|
001 |
PDCP SeqNum PDU (Table 8) |
|
010 |
PDCP AMR Data PDU (Table 9) |
|
011-111 |
Reserved (PDUs with this encoding are invalid for this version of the protocol) |
(…)
The PDCP AMR Data PDU is used to convey:
– a PDCP SDU containing AMR or AMR WB frame
The format of the PDCP AMR Data PDU is shown in Table 9.
Table 9: PDCP AMR Data PDU format
|
PDU type |
CS counter |
|
Data |
|
The PDCP PDU is octet aligned but the actual PDCP SDU carrying the AMR or AMR WB frame may not be octet aligned. The AMR classes are always encoded in the order of class A, B and C, where the first bit of data follows immediately after the CS counter field and any padding for octet alignment is inserted at the end of the data field.
(…)
If a PDCP entity receives a PDCP PDU with a PDU Type set to Reserved (see subclause 8.3.1), it shall:
– discard the PDCP PDU.
If a PDCP entity is not configured for lossless SRNS Relocation or lossless DL RLC PDU size change and receives a PDCP SeqNum PDU, it shall:
– discard the PDCP SeqNum PDU.
…
If a PDCP entity receives a PDCP PDU with a PID value that is not mapped with a valid packet type (see subclause 5.1.1), it shall:
– discard the PDCP PDU.
(…)
For each radio bearer that is configured to perform PDCP Unrecoverable Error Detection:
– if the PDCP entity receives 2 or 3 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value:
– the UE PDCP entity may indicate PDCP Unrecoverable Error to upper layer [2].
– if the PDCP entity receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value:
– the UE PDCP entity shall indicate PDCP Unrecoverable Error to upper layer [2].
NOTE1: Until the UE receives 4 consecutive PDCP PDUs with an unexpected or invalid PDU Type or PID value, the UE may apply a self-recovery mechanism. For example, the UE PDCP entity may indicate to RLC layer that HFN can be incremented.
NOTE2: The PDCP unrecoverable error detection is performed before the invalid PDU type check specified in subclause 9.1.
NOTE3: PDCP unrecoverable error detection in the UE can only detect the problem in the downlink.
(…)
1> Radio link failure:
2> if none of the criteria for performing cell update with the causes specified above in the current subclause is met:
3> if the UE is in CELL_DCH state and the criteria for radio link failure are met as specified in subclause 8.5.6; or
3> if the transmission of the UE CAPABILITY INFORMATION message fails as specified in subclause 8.1.6.6; or
3> if the UE detects PDCP Unrecoverable Error [36] in a PDCP entity
4> perform cell update using the cause "radio link failure".
(…)
If IE "PDCP info" is included, the UE shall:
1> if the radio bearer is connected to a CS domain radio access bearer:
2> if the IE "PDCP info" is included in any other message than the RADIO BEARER SETUP, CELL UPDATE CONFIRM or the HANDOVER TO UTRAN COMMAND message; or
2> if the IE "PDCP PDU header" is set to the value "absent"; or
2> if the IE "Support for lossless SRNS relocation or for lossless DL RLC PDU size change" is set to TRUE; or
2> if the IE "Header compression information" is present; or
2> if the UE does not support CS voice service over HSDPA and EDCH:
3> set the variable INVALID_CONFIGURATION to TRUE.
2> else
3> include PDCP headers in both uplink and downlink PDCP PDUs.
3> configure "PDCP Unrecoverable Error Detection" in lower layer.
(…)
Reference(s)
TS 25.323 clauses 8.2.4, 8.3.1, 9.1, 9.2, 9.3
TS 25.331 clauses 8.3.1.2, 8.6.4.10
7.3.7.2.3 Test purpose
1. To verify that the UE discards PDCP PDUs with invalid header.
2. To verify that UE transmits CELL UPDATE with cause "radio link failure" when UE receives consecutive PDCP PDUs with the wrong header.
7.3.7.2.4 Method of test
Initial conditions
UE is in Idle mode (state 2 or state 7) as specified in clause 7.4 of TS 34.108.
Related ICS/IXIT Statement(s)
Support of CS Voice over HSPA
Test procedure
a) The SS setups a circuit switched session including radio bearer and UE test loop mode 1 in RLC UM using common test procedures for mobile terminated CS switched sessions. Usage of "PDCP AMR Data" PDU has been configured by higher layers.
b) The SS sends a PDCP AMR data packet with invalid header.
c) After having received the AMR data packet, the PDCP entity of the UE shall recognise the PDCP header is invalid and discard the data packet.
d) Step b shall be repeated and SS should verify the expected response in step c.
e) After 2 consecutive PDCP PDUs with invalid header are sent by SS, the UE may optionally send CELL UPDATE.
f) SS transmits another 2 consecutive PDCP PDUs with invalid header.
g) UE shall discard the data packets and may optionally transmit CELL UPDATE after the reception of the 3rd PCDP PDU with invalid header. The UE shall transmit CELL UPDATE after the reception of the 4th PDCP PDU with invalid header.
h) SS shall transmit CELL UPDATE CONFIRM in response to CELL UPDATE from the UE. The SS requests the UE to transit to CELL_DCH state and provides the physical channel configuration to resume the interrupted radio bearer mapped on E-DCH / HS-DSCH and configures UL DTX.
The UE sets up the physical channels associated to E-DCH / HS-DSCH, enters CELL_DCH state and sends a PHYSICAL CHANNEL RECONFIGURATION COMPLETE message.
i) The SS sends an AMR data packet with a valid header.
j) The received data shall be looped back by the UE via its PDCP configuration using PDCP AMR Data PDU.
k) The SS receives and decodes the data packet. The decoded data packet shall be identical with the data as sent before.
l) Steps i) through k) are repeated 10 times, with 500 ms between the sending of each AMR data packet in the downlink.
m) The SS deactivates the UE test loop mode and terminates the connection.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|---|---|---|---|---|
|
UE |
SS |
|||
|
Setup a UE terminated CS session (using UE test loop mode 1). Refer to section 7.3.1 of TS 34.123-1 for common test procedure sequence. |
||||
|
The SS creates an AMR data packet (PDCP AMR Data PDU). |
||||
|
1 |
|
PDCP Data with invalid PDU type |
The SS sends a PDCP AMR Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 011 (Invalid PDU type) CS counter = first to fifth LSBs of the CFN at which the packet has been received from higher layers |
|
|
2 |
After having received the PDCP Data PDU, the UE decodes the PDU and recognizes that the PDU type is an Invalid type. The data packet is discarded. SS checks that PDCP data is not looped back Repeat steps 1 and 2 once |
|||
|
3 |
|
CELL UPDATE |
Optional step, see note 1. If CELL_UPDATE is sent by UE then go to step 8 |
|
|
4 |
|
PDCP Data with invalid PDU type |
The SS sends a third PDCP AMR Data PDU with Invalid PDU type |
|
|
5 |
|
CELL UPDATE |
Optional step, see note 1. If CELL_UPDATE is sent by UE then go to step 8 |
|
|
6 |
|
PDCP Data with invalid PDU type |
The SS sends a fourth PDCP AMR Data PDU with invalid PDU type |
|
|
7 |
|
CELL UPDATE |
No data loop back. CELL UPDATE is mandatory if not already received in preceding steps 3 and 5. |
|
|
8 |
|
CELL UPDATE CONFIRM |
||
|
8a |
|
PHYSICAL CHANNEL RECONFIGURATION COMPLETE |
||
|
9 |
|
PDCP Data |
The SS sends a PDCP AMR Data PDU using the RLC-UM-Data-Request Primitive with the following content to the UE: PDU type = 010 (PDCP AMR Data PDU) CS counter = first to fifth LSBs of the CFN at which the packet has been received from higher layers |
|
|
10 |
|
PDCP Data |
The UE loops back PDCP AMR Data PDU with the following content back to the SS: PDU type = 010 (PDCP AMR Data PDU) CS counter = first to fifth LSBs of the CFN at which the packet has been received from higher layers data: previously received AMR frames |
|
|
Steps 9 and 10 are repeated 10 times, with 500 ms between the sending of each AMR data packet in the downlink |
||||
|
Deactivate a UE terminated CS session (using UE test loop mode 1). Refer to section 7.3.1 of TS 34.123-1 for common test procedure sequence. |
||||
|
Note 1: CELL UPDATE can optionally be transmitted by UE at steps 3 or 5. If CELL UPDATE is transmitted by the UE at either step then the expected test sequence goes direct to step 8. |
||||
Specific Message Contents
RADIO BEARER SETUP message
“Speech to CELL_DCH / E-DCH / HS-DSCH CS RAB with DTX/DRX and enhanced data rate using one multiplexing option (1/1) and SRBs mapped on E-DCH/HS-DSCH (Condition A23), with the following exceptions
|
Information Element |
Value/remark |
|
– RAB information for setup |
|
|
– CS-HSPA information |
|
|
– UL AMR rate |
Not Present |
|
– Max CS delay |
100 |
|
– RB information to be affected |
|
|
– RB identity |
1 (UM DCCH for RRC) |
|
– Information for each multiplexing option |
2 RBMuxOption |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
E-DCH |
|
– Logical channel identity |
1 |
|
– E-DCH MAC-d flow identity |
1 |
|
– CHOICE RLC PDU size |
Fixed size |
|
– DDI |
1 |
|
– RLC PDU size list |
1 RLC PDU size |
|
– RLC PDU size |
144 bits |
|
– Include in scheduling info |
FALSE |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of RLC logical channels |
1 |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL DCH Transport channel identity |
Not present |
|
– DL DSCH Transport channel identity |
Not present |
|
– CHOICE DL MAC header type |
MAC-ehs |
|
– DL HS-DSCH MAC-ehs Queue Id |
1 |
|
– Logical channel identity |
1 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
1 |
|
– CHOICE RLC size list |
Explicit List |
|
– RLC size index |
According to clause 6.10.2.4.1.3 (standalone 13.6 kbps signalling radio bearer) |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of 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 |
1 |
|
– RB identity |
2 (AM DCCH for RRC) |
|
– Information for each multiplexing option |
2 RBMuxOption |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
E-DCH |
|
– Logical channel identity |
2 |
|
– E-DCH MAC-d flow identity |
1 |
|
– CHOICE RLC PDU size |
Fixed size |
|
– DDI |
2 |
|
– RLC PDU size list |
1 RLC PDU size |
|
– RLC PDU size |
144 bits |
|
– Include in scheduling info |
FALSE |
|
– MAC logical channel priority |
2 |
|
– Downlink RLC logical channel info |
|
|
– Number of RLC logical channels |
1 |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL DCH Transport channel identity |
Not present |
|
– DL DSCH Transport channel identity |
Not present |
|
– CHOICE DL MAC header type |
MAC-ehs |
|
– DL HS-DSCH MAC-ehs Queue Id |
1 |
|
– Logical channel identity |
2 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
2 |
|
– CHOICE RLC size list |
Explicit List |
|
– RLC size index |
According to clause 6.10.2.4.1.3 (standalone 13.6 kbps signalling radio bearer) |
|
– MAC logical channel priority |
2 |
|
– Downlink RLC logical channel info |
|
|
– Number of 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 |
2 |
|
– RB identity |
3 (AM DCCH for RRC) |
|
– Information for each multiplexing option |
2 RBMuxOption |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
E-DCH |
|
– Logical channel identity |
3 |
|
– E-DCH MAC-d flow identity |
1 |
|
– CHOICE RLC PDU size |
Fixed size |
|
– DDI |
3 |
|
– RLC PDU size list |
1 RLC PDU size |
|
– RLC PDU size |
144 bits |
|
– Include in scheduling info |
FALSE |
|
– MAC logical channel priority |
3 |
|
– Downlink RLC logical channel info |
|
|
– Number of RLC logical channels |
1 |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL DCH Transport channel identity |
Not present |
|
– DL DSCH Transport channel identity |
Not present |
|
– CHOICE DL MAC header type |
MAC-ehs |
|
– DL HS-DSCH MAC-ehs Queue Id |
1 |
|
– Logical channel identity |
3 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
3 |
|
– CHOICE RLC size list |
Explicit List |
|
– RLC size index |
According to clause 6.10.2.4.1.3 (standalone 13.6 kbps signalling radio bearer) |
|
– MAC logical channel priority |
3 |
|
– Downlink RLC logical channel info |
|
|
– Number of 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 |
3 |
|
– RB identity |
4 (AM DCCH for RRC) |
|
– Information for each multiplexing option |
2 RBMuxOption |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
E-DCH |
|
– Logical channel identity |
4 |
|
– E-DCH MAC-d flow identity |
1 |
|
– CHOICE RLC PDU size |
Fixed size |
|
– DDI |
4 |
|
– RLC PDU size list |
1 RLC PDU size |
|
– RLC PDU size |
144 bits |
|
– Include in scheduling info |
FALSE |
|
– MAC logical channel priority |
4 |
|
– Downlink RLC logical channel info |
|
|
– Number of RLC logical channels |
1 |
|
– Downlink transport channel type |
HS-DSCH |
|
– DL DCH Transport channel identity |
Not present |
|
– DL DSCH Transport channel identity |
Not present |
|
– CHOICE DL MAC header type |
MAC-ehs |
|
– DL HS-DSCH MAC-ehs Queue Id |
1 |
|
– Logical channel identity |
4 |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
4 |
|
– CHOICE RLC size list |
Explicit List |
|
– RLC size index |
According to clause 6.10.2.4.1.3 (standalone 13.6 kbps signalling radio bearer) |
|
– MAC logical channel priority |
4 |
|
– Downlink RLC logical channel info |
|
|
– Number of 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 |
4 |
Content of PDCP Data PDU (Step 1, 4, 6)
|
Information Element |
Value/remark |
|
PDU type |
011 |
|
CS counter |
first to fifth LSBs of the CFN at which the packet has been received from higher layers |
|
Data |
244 bits of AMR data + 4 bits of padding |
Content of CELL UPDATE (step 3, 5, 7)
The same message found in TS 34.108 clause 9.1.1 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 ‘radio link failure’ |
CELL UPDATE CONFIRM (Step 8)
Use the same message content found in TS 34.108 clause 9.1.1 with the following exception:
|
Information Element |
Value/remark |
|
RRC State indicator |
CELL_DCH |
|
DTX-DRX timing information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A23. |
|
Uplink DPCH info |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A23. |
|
E-DCH Info |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A23. |
|
Downlink HS-PDSCH information |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A23. |
|
Downlink information common for all radio links |
|
|
– Timing Indication |
Initialise |
|
– Downlink F-DPCH power control information |
|
|
– DPC mode |
0 (single) |
|
– TPC command error rate target |
0.04 |
|
– CHOICE mode |
FDD |
|
– DPCH compressed mode info |
Not Present |
|
– TX Diversity mode |
None |
|
– Default DPCH Offset Value |
Arbitrary set to value 0..306688 by step of 512 |
|
– MAC-hs reset indicator |
TRUE |
|
Downlink information per radio link list |
Same as the set defined in RADIO BEARER SETUP message found in TS 34.108 clause 9 under condition A23. |
Content of PDCP Data PDU (Step 9)
|
Information Element |
Value/remark |
|
PDU type |
010 |
|
CS counter |
first to fifth LSBs of the CFN at which the packet has been received from higher layers |
|
Data |
244 bits of AMR data + 4 bits of padding |
Content of PDCP Data PDU (Step 10)
|
Information Element |
Value/remark |
|
PDU type |
010 |
|
CS counter |
first to fifth LSBs of the CFN at which the packet has been received from higher layers |
|
Data |
Same content as Data from PDCP Data PDU at Step 1 |
7.3.7.2.5 Test requirements
After receiving 2, 3 or 4 consecutive PDCP PDUs with invalid PDU type the UE shall transmit CELL UPDATE with cause value "radio link failure"
After receiving the AMR data packets conveyed with a valid header, the UE shall successfully loop back all the data packets