hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
|---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.1 TBF Release / Downlink / Normal / Network initiated / Acknowledged mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.1.1 Conformance requirements
|
If the mobile station receives an RLC data block with the FBI bit set the value '1' and with a valid RRBP field, the mobile station shall transmit a PACKET DOWNLINK ACK/NACK message in the specified uplink block. The mobile station shall continue to monitor all assigned PDCHs.
Whenever the mobile station receives an RLC data block with a valid RRBP and the mobile station has received all RLC data blocks of the TBF, the mobile station shall send the PACKET DOWNLINK ACK/NACK message with the Final Ack Indicator bit set to '1', stop timer T3190 and start or restart timer T3192.
If the mobile station receives more than one RLC data block with the FBI set to '1', it shall accept the data from only the first one of these blocks.
If the mobile station, after sending the PACKET DOWNLINK ACK/NACK message with the Final Ack Indicator bit set to '1', receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' while timer T3192 is running, the mobile station shall stop timer T3192, consider the previous downlink TBF released and act upon the new assignment.
When timer T3192 expires the mobile station shall stop monitoring its assigned downlink PDCHs. If the mobile station is operating in half duplex mode and received an uplink assignment during the TBF release procedure, the mobile station shall then immediately act upon the assignment. Otherwise, and if there is no ongoing uplink TBF, enter packet idle mode.
References
3GPP TS 04.60, subclause 9.3.2.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.1.2 Test purpose
|
To verify that in a downlink TBF of acknowledged mode:
1. The MS sends PACKET DOWNLINK ACK/NACK in the specified uplink block and continues monitoring all assigned PDCHs when it receives an RLC data block with a valid RRBP field and the Final Block Indicator (FBI) = '1'.
2. Whenever the MS receives an RLC data block with a valid RRBP and has received all RLC data blocks of the TBF, it sends PACKET DOWNLINK ACK/NACK with the Final Ack Indicator bit set to '1'.
3. If the MS receives more than one RLC data block with the FBI set to '1', it accepts the data from only the first one of these blocks.
4. While timer T3192 is running, if the MS receives, after sending PACKET DOWNLINK ACK/NACK with the Final Ack Indicator bit set to '1', PACKET DOWNLINK ASSIGNMENT with the Control Ack bit set to '1', the MS acts upon the new downlink assignment.
5. The MS stops monitoring its assigned downlink PDCHs and enters packet idle mode when timer T3192 expires if there is no ongoing uplink TBF.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, CCCH combined with SDCCH, BS_CV_MAX = 15, T3192 = 1,5 s.
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated and PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
1. The MS receives an IMMEDIATE ASSIGNMENT message containing packet downlink assignment on its PCH. The SS transmits 10 downlink RLC data blocks with consecutive BSN. The SS then transmits a downlink RLC data block with the highest BSN which is ten higher than the BSN of the last RLC data block. The SS sets FBI bit and polls the MS with a valid RRBP in the header of the RLC data block. The MS acknowledges the received data blocks and request a retransmission for the missing 9 data blocks in SSN and RBB fields.
2. The SS sends another 5 RLC data blocks and polls the MS with a valid RRBP. The MS acknowledges the received data blocks and request the retransmission of the missing 4 RLC data blocks. The SS transmits the last 4 RLC data blocks and polls the MS with RRBP=N+26. While the MS is waiting for transmission of the final Acknowledgement the SS transmits a RLC data block which sets FBI bit and has the same BSN value as the highest one in the test procedure 1. The MS ignores the downlink data and acknowledges the entire TBF with FINAL_ACK_INDICATION set. The SS transmits another data block with FBI set and polls the MS. The MS acknowledges the entire TBF with FINAL_ACK_INDICATION set. The SS waits 3 s.
3. The MS receives an IMMEDIATE ASSIGNMENT message containing packet downlink assignment on its PCH. The SS transmits a number of downlink RLC data blocks, sets FBI bit and polls the MS with a valid RRBP. The MS acknowledges the entire TBF with FINAL_ACK_INDICATION set.
4. The SS sends another PACKET DOWNLINK ASSIGNMENT on the assigned PACCH with Control ACK bit set. The SS transmits a number of downlink RLC data blocks on the new assigned PDTCH, sets FBI bit and polls the MS with a valid RRBP. The MS acknowledges the entire TBF with FINAL_ACK_INDICATION set.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group, including a packet downlink assignment, acknowledged mode.
2
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on downlink PDTCH assigned.
3
Repeat step 2 nine times, each time BSN is incremented by 1
4
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with valid RRBP, FBI bit is set.
BSN is incremented by 10. The MS has missed 9 consecutive RLC data blocks.
BSN of this data block =
(BSN of the last data block in step 3 + 10) mod 128
5
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 4.
Check that the Final Ack indicator = '0' and the SSN and RBB values for the 9 missing data blocks .
6
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN of the data block =
(BSN of the last data block in step 3 + 1) mod 128
7
Repeat step 6 three times, each time BSN is incremented by 1 on the basis of the last BSN in step 6
8
SS -> MS
DOWNLINK RLC DATA BLOCK
A valid RRBP, BSN is incremented by 1.
9
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 8.
Check that the Final Ack indicator = '0' and SSN and RBB values for the 4 missing data blocks.
10
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN is incremented by 1
11
Repeat step 10 twice
12
SS -> MS
DOWNLINK RLC DATA BLOCK
RRBP.= N+26, BSN is incremented by 1
13
SS -> MS
DOWNLINK RLC DATA BLOCK
FBI bit is set, BSN is same as in step 4, RRBP.= N+26, sent on next radio block from step 12.
14
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 12. Check that the Final Ack indicator = '1'.
15
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 13. Check that the Final Ack indicator = '1'.
16
SS
Wait 2s for expiry of T3192.
17
SS -> MS
DOWNLINK RLC DATA BLOCK
FBI bit is set, a valid RRBP. Sent on downlink PDTCH assigned in step 1.
18
SS
Check that the MS does not respond on RRBP in step 17, the MS is now in packet idle mode.
19
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group, including a packet downlink assignment, acknowledged mode.
20
SS -> MS
DOWNLINK RLC DATA BLOCK
21
Repeat step 20 ten times
22
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI = '1' and valid RRBP.
23
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 22. Check that the Final Ack indicator = '1'.
24
SS
Wait for 80% of expiry of T3192 (1.2s)
25
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Downlink Assignment, acknowledged mode. A different slot assigned. Control Ack Bit = 1. Sent on PACCH.
26
SS -> MS
DOWNLINK RLC DATA BLOCK
27
Repeat step 26 ten times
28
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI = '1' and valid RRBP.
29
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 28. Check that the Final Ack indicator = '1'.
Specific Message Contents
PACKET DOWNLINK ACK/NACK message in step 15:
Ack/Nack Description
- FINAL_ACK_INDICATION
1 (final ack)
- STARTING_SEQUENCE_NUMBER
V( R )
- RECEIVED_BLOCK_BITMAP
Acknowledges all data blocks transmitted by the MS
PACKET DOWNLINK ASSIGNMET message in step 25:
CONTROL_ACK
1
TIMESLOT_ALLOCATION
Single slot arbitrarily chosen but different from the value in step 19
{L|H<DOWNLINK_TFI_ASSIGNMENT>}
H (assign downlink TFI)
- DOWNLINK_TFI_ASSIGNMENT
Arbitrarily chosen but different from the value in step 19
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.2 TBF Release / Downlink / Normal / Network initiated / Unacknowledged mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.2.1 Conformance requirements
|
The network initiates release of a downlink TBF by sending an RLC data block with the Final Block Indicator (FBI) set to the value '1' and with a valid RRBP field. The RLC data block sent must have the highest BSN' (see 3GPP TS 04.60 subclause 9.3.1) of the downlink TBF. The network shall start timer T3191. The network may retransmit the last block with FBI set to the value '1' and with a valid RRBP field. For each retransmission the timer T3191 is restarted. For each RLC data block with the FBI bit set to '1' and with a valid RRBP field, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message in the uplink block specified by the RRBP field. The mobile station shall continue to read the assigned downlink PDCHs until the block period pointed to by the RRBP. If the mobile station receives more than one RLC data block with the FBI bit set to '1' and with valid RRBP fields that point the same uplink block period, the mobile station shall transmit the PACKET CONTROL ACKNOWLEDGEMENT message only once. The mobile station shall then stop timer T3190, start timer T3192 and continue to monitor all assigned downlink PDCHs. If the mobile station then receives a subsequent RLC data block with a valid RRBP and the FBI bit set to '1', the mobile station shall retransmit the PACKET CONTROL ACKNOWLEDGEMENT message and restart timer T3192.
If the mobile station receives more than one RLC data block with the FBI set to '1', it shall accept the data from only the first one of these blocks.
If the mobile station, after sending the PACKET CONTROL ACKNOWLEDGEMENT message, receives a PACKET DOWNLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message with the Control Ack bit set to '1' while timer T3192 is running, the mobile station shall stop timer T3192, consider the previous downlink TBF released and act upon the new assignment.
When timer T3192 expires the mobile station shall stop monitoring its assigned downlink PDCHs.
References
3GPP TS 04.60, subclauses 9.3.3.5 and 9.3.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.2.2 Test purpose
|
To verify that in a downlink TBF of unacknowledged mode:
1. The MS transmits PACKET CONTROL ACKNOWLEDGEMENT in the uplink block specified by the RRBP field whenever it receives an RLC data block with a valid RRBP field and the Final Block Indicator (FBI) set to the value '1'.
2. After sending PACKET CONTROL ACKNOWLEDGEMENT the MS continues to monitor all assigned downlink PDCHs.
3. While timer T3192 is running, if the MS receives, after sending PACKET CONTROL ACKNOWLEDGEMENT, a PACKET DOWNLINK ASSIGNMENT with the Control Ack bit set to '1', the MS acts upon the new downlink assignment.
4. The MS stops monitoring its assigned downlink PDCHs and enters packet idle mode when timer T3192 expires.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, CCCH combined with SDCCH, BS_CV_MAX = 15, T3192 = 1,5 s.
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated and PDP context3 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
1. The MS receives an IMMEDIATE ASSIGNMENT message containing packet downlink assignment on its PCH. The SS transmits 11 downlink RLC data blocks with consecutive BSN. The SS then transmits a downlink RLC data block with the BSN which is ten higher than the BSN of the last RLC data block. The SS polls the MS with a valid RRBP in the header of the RLC data block. The MS acknowledges the received data blocks.
2. The SS sends another RLC data block and polls the MS with a valid RRBP and with the FBI bit set. The MS sends PACKET CONTROL ACKNOWLEDGEMENT.
3. The SS resends the last RLC data block and polls the MS with a valid RRBP and with the FBI bit set. The MS sends PACKET CONTROL ACKNOWLEDGEMENT. The SS waits 1.2s and resends the RLC data block and polls the MS with a valid RRBP and with the FBI bit set. The MS responds with PACKET CONTROL ACKNOWLEDGEMENT. The SS waits till T3192 expires. The SS sends a RLC data block with FBI set and a valid RRBP and checks that the MS does not transmit any data block on RRBP block.
4. The MS receives an IMMEDIATE ASSIGNMENT message containing packet downlink assignment on its PCH. The SS transmits a number of downlink RLC data blocks, sets FBI bit and polls the MS with a valid RRBP. The MS responds with PACKET CONTROL ACKNOWLEDGEMENT.
5. The SS sends another PACKET DOWNLINK ASSIGNMENT on the assigned PACCH with Control ACK bit set. The SS transmits a number of downlink RLC data blocks on the new assigned PDTCH, sets FBI bit and polls the MS with a valid RRBP. The MS responds with PACKET CONTROL ACKNOWLEDGEMENT.
Expected Sequence
Step
Direction
Message
Comments
1
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group, including a packet downlink assignment, unacknowledged mode.
2
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on downlink PDTCH assigned.
3
Repeat step 2 ten times, each time BSN is incremented by 1
4
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with valid RRBP, BSN is incremented by 10. The MS has missed 9 consecutive RLC data blocks.
BSN of this data block =
(BSN of the last data block in step 3 + 10) mod 128
5
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 4.
Check that the Final Ack indicator = '0'
6
SS -> MS
DOWNLINK RLC DATA BLOCK
A valid RRBP, BSN is incremented by 1, FBI bit is set.
7
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP in step 6.
8
Repeat step 6 and 7 once Keeping BSN same.
9
SS
Wait 1.2 seconds (T3192 not expired).
10
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI ='1' and valid RRBP. BSN is same as the BSN of the data block sent in step 6.
11
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP in step 10.
12
SS
Wait for expiry of T3192
13
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI = '1' and valid RRBP. Sent on downlink PDTCH assigned in step 1. BSN is same as the BSN of the data block sent in step 6
14
SS
Check that the MS does not transmit any control block on the RRBP block.
15
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group, including a packet downlink assignment, unacknowledged mode.
16
SS -> MS
DOWNLINK RLC DATA BLOCK
17
Repeat step 16 ten times
18
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI = '1' and valid RRBP.
19
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Wait 1.2 seconds (T3192 not expired).
20
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Downlink Assignment, unacknowledged mode. A different timeslot assigned. Control Ack Bit = 1. Sent on PACCH.
21
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent 5 blocks from last block containing PACKET DOWNLINK ASSIGNMENT
22
Repeat step 21 ten times
23
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with FBI = '1' and valid RRBP.
24
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP in step 23.
PACKET DOWNLINK ASSIGNMENT message in step 20:
RLC_MODE
Unacknowledged mode
CONTROL_ACK
1
{L|H<DOWNLINK_TFI_ASSIGNMENT>}
H (assign downlink TFI)
- DOWNLINK_TFI_ASSIGNMENT
Arbitrarily chosen but different from the value in step 15
TIMESLOT_ALLOCATION
Single slot arbitrarily chosen but different from the values already assigned.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.3 TBF release / Downlink / Normal / Network initiated / Whilst in DTM
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.3.1 Conformance requirements
|
When timer T3192 expires the mobile station shall release the downlink TBF. If the mobile station is operating in half duplex mode and received an uplink assignment during the TBF release procedure, the mobile station shall then immediately act upon the uplink assignment. If there is no ongoing uplink TBF, the mobile station in packet transfer mode shall return to packet idle mode; the mobile station in dual transfer mode shall return to dedicated mode.
References
3GPP TS 04.60/44.060, sub-clauses 9.3.2.6
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.3.2 Test purpose
|
To verify that the network can successfully remove a downlink TBF, to a MS in DTM, returning the MS to dedicated mode.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.4.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported.
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is GPRS attached with a P-TMSI allocated and the PDP context 2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
Whilst in an active call on timeslot N, the MS receives a PACKET ASSIGNMENT message on the main DCCH, instructing the MS to switch to the designated timeslot. The SS waits a specified time and then starts to transmit to the newly allocated resources. After approximately 500 octets of data has been sent, the SS waits for the time period of T3192, before testing that the MS has dropped out of dual transfer mode by sending a DOWNLINK RLC DATA block with S/P=1 and verify that the MS does not respond.
Upon completion of the downlink TBF release, the SS verifies that the MS has correctly returned to dedicated mode.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in the active state (U10) of a call on Timeslot N of cell A. When:
k=1, Channel Type = TCH/F;
k=2, Channel Type = TCH/H.
2
SS->MS
PACKET ASSIGNMENT
See specific message contents.
3
SS<->MS
{ Downlink data transfer }
Macro – transmitting approximately 500 octets of data.
4
MS->SS
PACKET DL ACK/NACK
FAI = 1
5
SS
Wait for time period of T3192 + 10%.
6
SS->MS
RLC DOWNLINK DATA
S/P bit = 1
7
SS
Verifies that no PACKET DOWNLINK ACK/NACK message is received from MS and that the MS returns correctly to dedicated mode.
Specific Message Contents
PACKET ASSIGNMENT (Step 2):
k=1;
As default message contents except:
RR Packet Uplink Assignment IE
Not included
RR Packet Downlink Assignment IE
- TIMESLOT_ALLOCATION
(N 1) MOD 8
k=2;
As default message contents except:
RR Packet Uplink Assignment IE
Not included
RR Packet Downlink Assignment IE
- TIMESLOT_ALLOCATION
N
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5 PDCH Release
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5.1 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5.2 PDCH Release / With TIMESLOTS_AVAILABLE
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5.2.1 Conformance requirements
|
When a mobile station receives a PACKET PDCH RELEASE message containing a TIMESLOTS_AVAILABLE field, it shall immediately stop transmitting and receiving on all assigned PDCHs, which are indicated as not present in the TIMESLOTS_AVAILABLE field, remove those PDCHs from its list of assigned PDCHs.
If all of the mobile station's assigned PDCHs are removed from its list of assigned PDCH, and, if an uplink TBF was in progress, the mobile station shall perform an abnormal release with random access. If no uplink TBF was in progress, the mobile station shall perform an abnormal release with return to CCCH or PCCCH.
References
3GPP TS 04.60, subclause 8.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5.2.2 Test purpose
|
To verify that when the MS receives a PACKET PDCH RELEASE message with a TIMESLOTS_AVAILABLE field indicating that one or more timeslots is no longer available for packet data service:
1. it immediately stops transmitting and receiving on all assigned PDCHs which are not presented in the TIMESLOTS_AVAILABLE field.
2. it performs an abnormal release with random access when all of the MS's assigned PDCHs are removed, and an uplink TBF was in progress.
3. it performs an abnormal release with return to CCCH when all of the MS's assigned PDCHs are removed, and no uplink TBF was in progress.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.5.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, CCCH combined with SDCCH, BS_CV_MAX = 15.
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated, SPLIT PG CYCLE negotiated and PDP context2 activated.
Specific PICS Statements
- Multislotclass (TSPC_Type_GPRS_Multislot_ClassX where X = 1..45)
PIXIT Statements
-
Test Procedure
1. The MS is triggered to transfer user data. A TBF on one slot of dynamic allocation in acknowledged mode is assigned. After the MS transfers several RLC data blocks the SS sends PACKET PDCH RELEASE with TIMESLOTS_AVAILABLE indicating no timeslot available. It is checked that the MS initiates a random access for one or two phase access request. A TBF is assigned to the MS to allow it to complete the uplink data transferring.
2. The MS is triggered to transfer user data. A TBF on two consecutive slots of dynamic allocation in acknowledged mode is assigned. After the MS transfers several RLC data blocks the SS sends PACKET PDCH RELEASE with TIMESLOTS_AVAILABLE indicating that only a timeslot is available. The MS uses the available timeslot to complete the uplink data transferring.
3. The MS receives an IMMEDIATE ASSIGNMENT message containing packet downlink assignment on its PCH. A downlink TBF with a timeslot is assigned. The SS transmits several downlink RLC data blocks. Then SS sends PACKET PDCH RELEASE with TIMESLOTS_AVAILABLE indicating no timeslot available and polls the MS with a valid RRBP for acknowledgement. It is checked that the MS does not react upon the polling.
4. A downlink TBF with two timeslots is assigned. The SS transmits several downlink RLC data blocks. Then SS sends PACKET PDCH RELEASE with TIMESLOTS_AVAILABLE indicating only a timeslot available and polls the MS with a valid RRBP for acknowledgement. It is checked that the MS does not react upon the polling and continues receiving the downlink data on the available timeslot. The SS sends another PACKET PDCH RELEASE with TIMESLOTS_AVAILABLE indicating no timeslot available and polls the MS with a valid RRBP for acknowledgement. It is checked that the MS does not react upon the polling.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation one phase access with contention resolution}
or
{Uplink dynamic allocation two phase access}
n = 1000 octets in RLC acknowledged mode. (Test PDP context2)
CHANNEL_CODING_COMMAND = cs4.
2
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to MS
3
MS -> SS
UPLINK RLC DATA BLOCK
Received data block on the assigned PDTCH.
4
SS
Repeat steps 2 and 3 six times
5
SS -> MS
PACKET PDCH RELEASE
Sent on the PACCH of the PDCH assigned in step 1. With TIMESLOTS_AVAILABLE indicating no timeslot available, RRBP = N + 26.
6
SS
SS checks that no PACKET CONTROL ACKNOWLEDGEMENT is received.
7
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to MS
8
SS
Verify that no data block is received.
9
MS -> SS
CHANNEL REQUEST
Received on RACH.
10
SS -> MS
IMMEDIATE ASSIGNMENT
Single block assignment, to order the MS making two phase access procedure. Sent on AGCH.
11
MS -> SS
PACKET RESOURCE REQUEST
Two phase access procedure. Received on the single block assigned in step 10.
12
SS -> MS
PACKET UPLINK ASSIGNMENT
Open-ended uplink dynamic allocation with one time slot, USF_GRANULARITY = single block,
CHANNEL_CODING_COMMAND = cs4,
Sent on PACCH of the same PDCH assigned in step 10.
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned in step 12, containing USF assigned to the MS.
14
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
15
{Completion of uplink RLC data block transfer}
The MS of the GPRS multislot class 1, 2, 3, 4, 8, 30, 35 and 40 skips the steps 16 to 38.
16
{Uplink dynamic allocation one phase access with contention resolution}
or
{Uplink dynamic allocation two phase access}
n = 1100 octets in RLC acknowledged mode. (Test PDP context2),
CHANNEL_CODING_COMMAND = cs2
Two timeslots are assigned
17
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
USFs assigned to MS. Sent on PDTCH6 and PDTCH7.
18
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH6 and PDTCH7.
19
Repeat step 17 and 18 three times
20
SS -> MS
PACKET PDCH RELEASE
Sent on the PACCH of the PDCH6 assigned in step 16 RRBP=N+26 . With TIMESLOTS_AVAILABLE indicating no timeslot available.
21
SS
SS checks that no PACKET CONTROL ACKNOWLEDGEMENT is received.
22
SS-MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
USFs assigned to MS. Sent on PDTCH6 and PDTCH7.
23
SS
Verify that MS stop sending on both PDTCH6 and PDTCH7
24
MS -> SS
CHANNEL REQUEST
Received on RACH.
25
SS -> MS
IMMEDIATE ASSIGNMENT
Single block assignment, to order the MS making two phase access procedure. Sent on AGCH.
26
MS -> SS
PACKET RESOURCE REQUEST
Two phase access procedure. Received on the single block assigned in step 25.
27
SS -> MS
PACKET UPLINK ASSIGNMENT
Uplink dynamic allocation
CHANNEL_CODING_COMMAND = cs4
Two timeslots
28
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
USFs assigned to MS. Sent on PDTCH0 and PDTCH1.
29
MS -> SS
UPLINK RLC DATA BLOCKS
data blocks received on the assigned PDTCH1 and PDTCH0.
30
SS
Repeat steps 28 and 29 three times
31
SS -> MS
PACKET PDCH RELEASE
Sent on the PACCH of the PDCH1 assigned in step 27. With TIMESLOTS_AVAILABLE indicating only the timeslot corresponding to PDCH0 available.
32
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent after 6 radio blocks from step 31 on PDCH1,
USFs assigned to MS
33
SS
Verify that no data block was received
34
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on PDCH0,
USFs assigned to MS
35
MS -> SS
UPLINK RLC DATA BLOCK
data block received on PDCHo
36
SS
Repeat steps 34 and 35 until the countdown value CV=0,
37
SS -> MS
PACKET UPLINK ACK/NACK
Acknowledge all data blocks. The SS sets Final Ack Indicator = '1' containing a valid RRBP.
38
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PDCH0
39
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group, including a packet downlink assignment with one timeslot assigned, acknowledged mode.
40
SS -> MS
DOWNLINK RLC DATA BLOCK
A valid RRBP
41
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP in step 40.
42
SS -> MS
DOWNLINK RLC DATA BLOCK
Repeat the step three times.
43
SS -> MS
PACKET PDCH RELEASE
Sent on the next radio block from step 42 with TIMESLOTS_AVAILABLE indicating no timeslot available.
44
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on the next radio block from step 43 on PDTCH released, a valid RRBP = N + 21 or 22.
45
SS
Check that no PACKET DOWNLINK ACK/NACK received on the block specified in step 44.
The steps from 46 onwards are applicable to all GPRS multislot classes except the GPRS multislot class1.
46A
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on a PCH block corresponding to the MS's paging group with TBF starting time.
46B
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Timeslot1 and Timeslot0 assigned, acknowledged mode.
Sent on the PACCH assigned in step 46A.
47
SS -> MS
DOWNLINK RLC DATA BLOCK
Repeat the step five times. The RLC data blocks are received on PDTCH1 and PDTCH0.
The last data block on PDTCH1 containing a valid RRBP.
48
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block specified by RRBP on PDTCH1
Check whether all data blocks in step 47 are acknowledged.
49
SS -> MS
PACKET PDCH RELEASE
With TIMESLOTS_AVAILABLE indicating only timeslot0 available. Sent on the PACCH of PDCH1.
50
SS -> MS
DOWNLINK RLC DATA BLOCK
Repeat the step five times. The RLC data blocks are received on PDTCH0.
The last data block on PDTCH0 containing a valid RRBP.
51
MS -> SS
PACKET DOWNLINK ACK/NACK
On the block specified by RRBP on PDTCH0.
Check whether all data blocks sent in step 50 are acknowledged.
52
SS -> MS
DOWNLINK RLC DATA BLOCK
One data block with a valid RRBP = N + 26 on PDTCH1.
53
SS
Check that no PACKET DOWNLINK ACK/NACK received on the block specified.
54
SS -> MS
DOWNLINK RLC DATA BLOCK
Repeat the step five times on PDTCH0.
55
SS -> MS
PACKET PDCH RELEASE
With TIMESLOTS_AVAILABLE indicating no timeslot available sent on the next block from step 54.
56
SS -> MS
DOWNLINK RLC DATA BLOCK
Sent on the next radio block of step 55 on PDTCH0, a valid RRBP = N + 21 or 22.
57
SS
Check that no PACKET DOWNLINK ACK/NACK is received on the block specified in step 56.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6 TBF Release / Extended Uplink
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.1 TBF Release / Extended Uplink / Recalculation of CV before CV = 0
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.1.1 Conformance requirements
|
In an uplink TBF operating in extended uplink TBF mode, the CV shall indicate the current number of RLC data blocks that has not been transmitted in the uplink TBF. The mobile station shall update the TBC value and recalculate the CV for any untransmitted RLC data block in the following cases:
- The RLC entity of the mobile station receives new data from upper layers for transmission in the uplink TBF.
References
3GPP TS 44.060, subclause 9.3.1.3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.1.1.2 Test purpose
|
To verify that MS recalculates the CV when a new PDU is received from upper layers before MS has sent an RLC data block with CV=0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, BS_CV_MAX = 14
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF using dynamic allocation in acknowledged mode is assigned. The SS assigns an USF to MS until MS has sent CV = 14. Then MS is triggered to send more data. SS acknowledges all received data. A new USF is assigned to MS every 4th second. The CV is checked in the data block. If the CV becomes ‘0’ before having been recalculated, the test has failed. Otherwise the uplink TBF is continued and completed.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=14 (BS_CV_MAX).
5
MS
Trigger MS to send 400 octets of data.
6
SS -> MS
PACKET UPLINK ACK/NACK
Acknowledge all received data. USF assigned to the MS.
7
MS -> SS
RLC DATA BLOCK
Check CV
8
SS
Wait 4s
9
Repeat step 6 to 8 until CV (as received in step 7) > 14 (successful) or CV = 0 (failed)
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
11
MS -> SS
UPLINK RLC DATA BLOCK
12
Repeat step 10 and 11 until CV=0.
13
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
14
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.2 TBF Release / Extended Uplink / Recalculation of CV after CV = 0
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.2.1 Conformance requirements
|
[3GPP TS 44.060, 9.1.3.1]
In the extended uplink TBF mode, if V(S) = V(A) and there is no RLC data block with BSN = V(S) available, the mobile station shall stop sending RLC data blocks. The mobile station shall continue sending RLC data blocks when a RLC data block with BSN = V(S) is available.
[3GPP TS 44.060, 9.3.1.3]
In an uplink TBF operating in extended uplink TBF mode, the CV shall indicate the current number of RLC data blocks that has not been transmitted in the uplink TBF. The mobile station shall update the TBC value and recalculate the CV for any untransmitted RLC data block in the following cases:
• The RLC entity of the mobile station receives new data from upper layers for transmission in the uplink TBF.
[3GPP TS 44.060, 9.3.1b.2]
In extended uplink TBF mode, the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 9.1.3.1, 9.3.1.3, 9.3.1b.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.2.2 Test purpose
|
1 To verify that MS sends an RLC/MAC control block after fully acknowledgement of transmitted RLC data.
2 To verify that MS continues to send RLC data blocks on the current TBF when MS receives new data from upper layers when all RLC data have been fully acknowledged.
3 To verify that MS recalculates the CV when a new LLC PDU is received from upper layers after MS has sent a RLC data block with CV=0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, BS_CV_MAX = 15
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF of dynamic allocation in acknowledged mode is assigned. SS assigns an USF to MS until MS has sent CV = 0. SS acknowledges all received data with Final Ack Indicator bit set to ‘0’. SS continues to assigns USF to MS. MS shall send a PACKET UPLINK DUMMY CONTROL BLOCK every time. Then MS is triggered to send more data. After one second a new USF is assigned to MS. MS shall send a data block with a recalculated CV. Then the uplink TBF is continued and completed.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat step 6 and 7 five times.
9
MS
Trigger the MS to send 400 octets of data. SS should take care of allocating USF’s to the MS in order to prevent the MS from releasing the TBF. If SS receives PACKET UPLINK DUMMY CONTROL BLOCKs, these shall be discarded. If SS receives an UPLINK RLC DATA BLOCK, then verify that the MS has recalculated the CV.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
11
MS -> SS
UPLINK RLC DATA BLOCK
12
Repeat step 10 and 11 until CV=0
13
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
14
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.3 TBF Release / Extended Uplink / CS change order while CV=0
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.3.1 Conformance requirements
|
[3GPP TS 44.060, 9.1.3.1b2]
During a period when the network does not receive any RLC data blocks from the mobile station, the network may periodically send a PACKET UPLINK ACK/NACK message to the mobile station.
[3GPP TS 44.060, 9.1.12]
In the uplink direction the channel coding scheme shall be the commanded channel coding scheme.
[3GPP TS 44.060, 11.2.28]
The Channel Coding Indicator field indicates the channel coding scheme that the mobile station shall use when transmitting on the uplink.
References
3GPP TS 44.060, subclause 9.1.3.1b2,
3GPP TS 44.060, 9.1.12,
3GPP TS 44.060, 11.2.28
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.3.2 Test purpose
|
To verify that MS applies the new ordered CS whereas the CS change command has been received while CV = 0.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, BS_CV_MAX = 15
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF of dynamic allocation in acknowledged mode is assigned. SS assigns an USF to MS until MS has sent CV = 0. SS acknowledges all received data with Final Ack Indicator bit set to ‘0’. SS continues to assigns USF to MS. MS sends a PACKET UPLINK DUMMY CONTROL BLOCK every time. Then MS received a new Coding Scheme command while it transmits PACKET UPLINK DUMMY CONTROL BLOCKs. Last, it is triggered to send more data. After one second a new USF is assigned to MS. MS shall send a data block with a recalculated CV. Then the uplink TBF shall be continued and completed with the new commanded CS.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat step 6 and 7 five times.
9
SS -> MS
PACKET UPLINK ACK/NACK
CHANNEL_CODING_COMMAND: CS-3
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
12
MS
Trigger the MS to send 400 octets of data. SS should take care of allocating USF’s to the MS in order to prevent the MS from releasing the TBF. If SS receives PACKET UPLINK DUMMY CONTROL BLOCKs, these shall be discarded. If SS receives an UPLINK RLC DATA BLOCK, then verify that the MS has recalculated the CV.
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
14
MS -> SS
UPLINK RLC DATA BLOCK
Verify that the MS uses the new ordered CS.
15
Repeat step 13 and 14 until CV=0
16
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
17
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
PACKET UPLINK ACK NACK (Step 1):
As default message contents except:
CHANNEL_CODING_COMMAND
CS-2
PACKET UPLINK ACK NACK (Step 9):
As default message contents except:
CHANNEL_CODING_COMMAND
CS-3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.4 TBF Release / Extended Uplink / TBF reconfigure by PACKET TIMESLOT RECONFIGURE
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.4.1 Conformance requirements
|
The mobile station shall attempt to decode every downlink RLC/MAC block on all assigned PDCHs. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message.
The network may at any time during the uplink TBF initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message to the mobile station. During the reallocation TFI is allowed to be changed.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in sub-clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in sub-clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send for this TBF, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in sub-clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 9.3.1b.2
3GPP TS 44.060, subclause 8.1.1.1.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.4.2 Test purpose
|
To verify that if the MS receives a PACKET TIMESLOT RECONFIGURE while the Uplink TBF is extended, the MS switches to the new assigned channels and continues sending of PACKET DUMMY CONTROL BLOCKs in the uplink.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.4.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, GPRS supported, NW_EXT_UTBF = 1.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF using dynamic allocation in acknowledged mode is assigned. The SS assigns an USF to MS. SS receives data blocks till CV=0 and acknowledges all the blocks with an UPLINK ACK/NACK setting FAI=0. Then SS checks that if a USF is matched to the MS it sends a UPLINK DUMMY CONTROL BLOCK. SS sends a PACKET TIMESLOT RECONFIGURE, reassigning the timeslot given for Uplink and initiating a downlink TBF. SS checks that the MS is sending a UPLINK DUMMY CONTROL BLOCK on the new channels whenever the USF is matched. SS releases the downlink TBF. SS initiates a data transfer of 200 octets. SS checks that the MS is using the newly assigned channels for doing the data transfer. SS allows the MS to complete the data transfer and releases the TBF.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat step 6 and 7 five times.
9
SS -> MS
PACKET TIMESLOT RECONFIGURE
See Specific message content. Assigning different timeslot, starting a downlink TBF.
10
SS -> MS
DOWNLINK RLC DATA BLOCK
Containing RRBP= N+21 or +22 and USF assigned to the MS. FBI ='1'. Sent on the downlink PDTCH assigned on 3 blocks from the last radio block containing the TIMESLOT RECONFIGURE in step 9.
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
Received on the uplink PDTCH assigned in step 9.
12
MS -> SS
PACKET DOWNLINK ACK/NACK
Received on the block of frame number = N+21 or +22, N is the frame number of the first burst of the data block in step 10.
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
14
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
15
MS
Trigger the MS to send 200 octets of data. SS should take care of allocating USF’s to the MS in order to prevent the MS from releasing the TBF. If SS receives PACKET UPLINK DUMMY CONTROL BLOCKs, these shall be discarded. If SS receives an UPLINK RLC DATA BLOCK, then verify that the MS has recalculated the CV.
16
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
17
MS -> SS
UPLINK RLC DATA BLOCK
18
Repeat step 16 and 17 until CV=0
19
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
20
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents
PACKET TIMESLOT RECONFIGURE message in step 9:
PAGE_MODE
Normal
0, Global TFI as reference
- Global TFI
0, uplink TFI
same value as assigned in the uplink in step 1
CHANNEL_CODING_COMMAND
Arbitrarily chosen from valid values
Global packet Timing Advance
- {0|1<TIMING_ADVANCE_VALUE>}
1 (timing advance value)
- TIMING_ADVANCE_VALUE
30 bit periods
- {0|1<UPLINK_TIMING_ADVANCE_INDEX> <UPLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no uplink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
- {0|1<DOWNLINK_TIMING_ADVANCE_INDEX> <DOWNLINK_TIMING_ADVANCE_TIMESLOT_NUMBER>}
0 (no downlink timing advance index)
The MS stops the operation of the continuous timing advance procedure.
DOWNLINK_RLC_MODE
Acknowledged mode
CONTROL_ACK
0
{0|1<DOWNLINK_TFI_ASSIGNMENT>}
1
- GLOBAL_TFI_ASSIGNMENT
Arbitrarily chosen but different from the value for uplink TBF
{0|1<UPLINK_TFI_ASSIGNMENT>}
0
DOWNLINK_TIMESLOT_ALLOCATION
Timeslot 5 assigned
{0|1<Frequency parameters>}
0
Dynamic allocation
0
- Extended Dynamic Allocation
0 ( Dynamic allocation)
{0|1<P0>}
0
- USF GRANULARITY
0 (1 RLC block)
- {0|1<RLC_DATA_BLOCKS_GRANTED>}
0 (open-ended TBF)
- {0|1<TBF_STARTING_TIME>}
0 (no starting time)
-
1 (Timeslot Allocation with Power Control Parameters)
- ALPHA
0.5
- {0|1<USF_TNx><GAMMA_TNx>}
000001 (timeslot 5 assigned)
- USF_TN5
Arbitrarily chosen but different from current value
- GAMMA_TN5
For GSM 700, T-GSM 810, GSM 850 and GSM 900, +8 dBm
For DCS 1 800 and PCS 1 900, +6 dBm
00
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.5 TBF Release / Extended Uplink / TBF reconfigure by PACKET UPLINK ASSIGNMENT
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.5.1 Conformance requirements
|
The mobile station shall attempt to decode every downlink RLC/MAC block on all assigned PDCHs. Whenever the mobile station receives an RLC/MAC block containing an RLC/MAC control block, the mobile station shall attempt to interpret the message contained therein. If the message addresses the mobile station, the mobile station shall act on the message.
The network may at any time during the uplink TBF initiate a change of resources by sending on the downlink PACCH monitored by the MS, an unsolicited PACKET UPLINK ASSIGNMENT or PACKET TIMESLOT RECONFIGURE message to the mobile station. During the reallocation TFI is allowed to be changed.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in sub-clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in sub-clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send for this TBF, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in sub-clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 9.3.1b.2
3GPP TS 44.060, subclause 8.1.1.1.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.5.2 Test purpose
|
To verify that if the MS receives a PACKET UPLINK ASSIGNMENT while the Uplink TBF is extended, the MS switches to the new assigned channels and continues sending of PACKET DUMMY CONTROL BLOCKs in the uplink.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, GPRS supported, NW_EXT_UTBF = 1.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is triggered to transfer user data. A TBF using dynamic allocation in acknowledged mode is assigned. The SS assigns an USF to MS. SS receives data blocks till CV=0 and acknowledges all the blocks with an UPLINK ACK/NACK setting FAI=0. Then SS checks that if a USF is matched to the MS it sends a UPLINK DUMMY CONTROL BLOCK. SS sends a PACKET UPLINK ASSIGNMENT, reassigning the timeslot given for Uplink. SS checks that the MS is sending a UPLINK DUMMY CONTROL BLOCK on the new channels whenever the USF is matched. SS initiates a data transfer of 200 octets. SS checks that the MS is using the newly assigned channels for doing the data transfer. SS allows the MS to complete the data transfer and releases the TBF.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets,
USF_GRANULARITY = 1 block,
CHANNEL_CODING_COMMAND: CS-2,
RLC acknowledged mode (PDP context2)
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat step 6 and 7 five times.
9
SS -> MS
PACKET UPLINK ASSIGNMENT
See Specific message content. Assigning different timeslot.
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS. Sent after 3 blocks of sending the messages in step 9.
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
12
MS
Trigger the MS to send 200 octets of data. SS should take care of allocating USF’s to the MS in order to prevent the MS from releasing the TBF. If SS receives PACKET UPLINK DUMMY CONTROL BLOCKs, these shall be discarded. If SS receives an UPLINK RLC DATA BLOCK, then verify that the MS has recalculated the CV.
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
14
MS -> SS
UPLINK RLC DATA BLOCK
15
Repeat step 13 and 14 until CV=0
16
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
17
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific Message Contents :
PACKET UPLINK ASSIGNMENT message in step 9:
Information Element
value/ remark
Dynamic allocation
01
-
000000
-
1 (Timeslot Allocation with Power Control Parameters for 1 slot assigned)
- ALPHA
0.5
-
000001 (timeslot 5 assigned)
- USF_TN5
Arbitrarily chosen
- GAMMA_TN5
For GSM 900: +8 dBm
For GSM 400: +8 dBm
For GSM 850: +8 dBm
For GSM 700 and T-GSM 810: +8 dBm
For DCS 1 800: +6dBm
For PCS 1 900: +6 dBm
-
00000
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.6 Extended Uplink TBF / Cell Change while in Extended Uplink/ No Packet Neighbouring Cell Data
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.6.1 Conformance requirements
|
If CCN is enabled (see sub-clause 5.5.1.1a), the mobile station shall behave as in network control mode NC0 or NC1 up to the point when a new cell has been chosen. It shall then check the CCN_SUPPORTED parameter, if available, that was last received for that cell. This parameter can be sent on BCCH or PBCCH or individually in PACKET MEASUREMENT ORDER or in PACKET CELL CHANGE ORDER messages. If it is available and if it indicates that CCN mode shall be entered towards that cell or if it is not available, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, the MS shall then, when in CCN mode, inform the network about the proposed cell by sending a PACKET CELL CHANGE NOTIFICATION message, stop timer T3206, start timers T3208 and T3210. The PACKET CELL CHANGE NOTIFICATION message shall contain the ARFCN for the BCCH and the BSIC as identity of the proposed cell. The message shall also contain measurement reports for the proposed cell and for other neighbour cells if available. In CCN mode the mobile station shall continue the data transfer and store neighbour cell system information if received in instances of the PACKET NEIGHBOUR CELL DATA message, but not perform the cell change. At receipt of the first PACKET NEIGBOUR CELL DATA message or PACKET CELL CHANGE CONTINUE message or PACKET CELL CHANGE ORDER message, the mobile station shall stop the timer T3210.If a mobile station as response to a PACKET CELL CHANGE NOTIFICATION message receives a PACKET CELL CHANGE CONTINUE message without receiving any neighbour cell system information, the mobile station shall stop timer T3208, stop timer T3210 if still running, leave CCN mode and continue cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE CONTINUE message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE CONTINUE message is received, the mobile station shall stop timer T3208, leave CCN mode and continue the cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE ORDER message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE ORDER message is received, the mobile station shall stop timer T3208, leave CCN mode and follow the procedures as specified for the Packet Cell Change Order (sub-clause 8.4) and in sub-clause 8.8.1.
In extended uplink TBF mode, the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 8.8.3
3GPP TS 44.060, subclause 9.3.1b.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.6.2 Test purpose
|
To verify that an MS which is in Extended Uplink TBF, NACC active, changes to the proposed cell while in extending (sending uplink dummy control blocks).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.6.3 Method of test
|
Initial conditions
System Simulator:
2 cells, GPRS supported, CCN Active, RXLEV_ACCESS_MIN = -90dBm, NW_EXT_UTBF = 1.
Cell A: RLA_C = -50 dBm, is active.
Cell B: RLA_C = -60 dBm, is active.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate packet uplink transfer. SS assigns resources to the MS and it starts to send uplink data that the SS acknowledge. When MS reaches CV=0,it starts sending PACKET UPLINK DUMMY CONTROL BLOCKS During the uplink the signal strength of Cell A is lowered to – 80 dBm. The MS enters CCN mode and sends PACKET CELL CHANGE NOTIFICATION. The MS then continues to send PACKET UPLINK DUMMY CONTROL BLOCKS. While MS is sending PACKET ULINK DUMMY CONTROL BLOCKs, the SS then sends PACKET CELL CHANGE CONTINUE and the MS change to Cell B. The MS request resources for an uplink in the new cell and complete the uplink transfer in the new cell.
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets.
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: same as channel coding
CHANNEL_CODING_COMMAND: cs-1
No starting time present.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
3
MS -> SS
RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat steps 6 and 7 five times
9
SS
Lower signal strength of Cell A to –80 dBm.
10
SS -> MS
PACKET UPLINK ACK/NACK
USF assigned to the MS
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
Or
PACKET CELL CHANGE NOTIFICATION
12
Step 10 and 11 are repeated until a PACKET CELL CHANGE NOTIFICATION is received in step 11, but no longer than 15 sec.
The test has failed if no PACKET CELL CHANGE NOTIFICATION is received in Cell A within 15 sec from Step 9.
13
SS -> MS
PACKET CELL CHANGE CONTINUE
See specific message content.
The following messages are to be sent and received in Cell B.
14
MS ->SS
CHANNEL REQUEST
CHANNEL REQUEST with establishment cause = 'Single block packet access' or ‘one phase packet access’.
15
SS ->MS
IMMEDIATE ASSIGNMENT
Sent on the AGCH
16
MS ->SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 15. Access type = ’Cell Update’ or ‘Two Phase Access’.
17
SS ->MS
PACKET UPLINK ASSIGNMENT
Uplink dynamic allocation, no starting time Sent on PACCH of the same PDCH assigned in step 15.
18
{Completion of uplink RLC data block transfer}
MS performs a Cell Update.
Specific message contents
PACKET CELL CHANGE CONTINUE in Step 13
Information element
Value/remark
< PAGE_MODE : bit (2) >
00 (Normal Paging)
0
0
< GLOBAL_TFI : Global TFI IE >
0 <5 bit Uplink TFI>
0 | 1
1
< ARFCN : bit (10) >
ARFCN of Cell B.
< BSIC : bit (6) >
BSIC of Cell B.
<CONTAINER_ID>
01
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.7 Extended Uplink TBF / Cell Change failure while in Extended Uplink/ No Packet Neighbouring Cell Data
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.7.1 Conformance requirements
|
If CCN is enabled (see sub-clause 5.5.1.1a), the mobile station shall behave as in network control mode NC0 or NC1 up to the point when a new cell has been chosen. It shall then check the CCN_SUPPORTED parameter, if available, that was last received for that cell. This parameter can be sent on BCCH or PBCCH or individually in PACKET MEASUREMENT ORDER or in PACKET CELL CHANGE ORDER messages. If it is available and if it indicates that CCN mode shall be entered towards that cell or if it is not available, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, the MS shall then, when in CCN mode, inform the network about the proposed cell by sending a PACKET CELL CHANGE NOTIFICATION message, stop timer T3206, start timers T3208 and T3210. The PACKET CELL CHANGE NOTIFICATION message shall contain the ARFCN for the BCCH and the BSIC as identity of the proposed cell. The message shall also contain measurement reports for the proposed cell and for other neighbour cells if available. In CCN mode the mobile station shall continue the data transfer and store neighbour cell system information if received in instances of the PACKET NEIGHBOUR CELL DATA message, but not perform the cell change. At receipt of the first PACKET NEIGBOUR CELL DATA message or PACKET CELL CHANGE CONTINUE message or PACKET CELL CHANGE ORDER message, the mobile station shall stop the timer T3210.If a mobile station as response to a PACKET CELL CHANGE NOTIFICATION message receives a PACKET CELL CHANGE CONTINUE message without receiving any neighbour cell system information, the mobile station shall stop timer T3208, stop timer T3210 if still running, leave CCN mode and continue cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE CONTINUE message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE CONTINUE message is received, the mobile station shall stop timer T3208, leave CCN mode and continue the cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE ORDER message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE ORDER message is received, the mobile station shall stop timer T3208, leave CCN mode and follow the procedures as specified for the Packet Cell Change Order (sub-clause 8.4) and in sub-clause 8.8.1.
In extended uplink TBF mode, the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 8.8.3
3GPP TS 44.060, subclause 9.3.1b.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.7.2 Test purpose
|
To verify that an MS, which is in Extended Uplink TBF, NACC active, shall revert to the previous TBF, if selected cell disappears from the coverage and MS should still stay in Extended Uplink TBF
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.7.3 Method of test
|
Initial conditions
System Simulator:
2 cells, GPRS supported, CCN Active, RXLEV_ACCESS_MIN = -90dBm, NW_EXT_UTBF = 1.
Cell A: RLA_C = -50 dBm, is active.
Cell B: RLA_C = -60 dBm, is active.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established. Ready timer is deactivated
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate packet uplink transfer. SS assigns resources to the MS and it starts to send uplink data that the SS acknowledge. When MS reaches CV=0,it starts sending PACKET UPLINK DUMMY CONTROL BLOCKS During the uplink the signal strength of Cell A is lowered to – 80 dBm. The MS enters CCN mode and sends PACKET CELL CHANGE NOTIFICATION. The MS then continues to send PACKET UPLINK DUMMY CONTROL BLOCKS. While MS is sending PACKET ULINK DUMMY CONTROL BLOCKs, the SS then sends PACKET CELL CHANGE CONTINUE and the MS change to Cell B. MS tries to access Cell B. SS deactivates Cell B, The MS request resources for an uplink in the old cell.
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 500 octets.
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: same as channel coding
CHANNEL_CODING_COMMAND: cs-1
No starting time present.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
3
MS -> SS
RLC DATA BLOCK
4
Repeat step 2 and 3 until CV=0
5
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
8
Repeat steps 6 and 7 five times
9
SS
Lower signal strength of Cell A to –80 dBm.
10
SS -> MS
PACKET UPLINK ACK/NACK
USF assigned to the MS
11
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
Or
PACKET CELL CHANGE NOTIFICATION
12
Step 10 and 11 are repeated until a PACKET CELL CHANGE NOTIFICATION is received in step 11, but no longer than 15 sec.
The test has failed if no PACKET CELL CHANGE NOTIFICATION is received in Cell A within 15 sec from Step 9.
13
SS -> MS
PACKET CELL CHANGE CONTINUE
See specific message content.
14
MS -> SS
CHANNEL REQUEST
Allow the MS to try to access Cell B
15
Cell B is deactivated
The following messages are to be sent and received in Cell A.
16
MS -> SS
CHANNEL REQUEST
CHANNEL REQUEST with establishment cause = 'Single block packet access' or one phase packet access.
17
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on the AGCH.
18
MS -> SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 17.
19
SS -> MS
PACKET UPLINK ASSIGNMENT
uplink dynamic allocation, no starting time Sent on PACCH of the same PDCH assigned in step 17.
20
{Completion of uplink RLC data block transfer}
MS performs a Cell Update.
Specific message contents
PACKET CELL CHANGE CONTINUE in Step 13
Information element
Value/remark
< PAGE_MODE : bit (2) >
00 (Normal Paging)
0
0
< GLOBAL_TFI : Global TFI IE >
0 <5 bit Uplink TFI>
0 | 1
1
< ARFCN : bit (10) >
ARFCN of Cell B.
< BSIC : bit (6) >
BSIC of Cell B.
<CONTAINER_ID>
01
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.8 Extended Uplink TBF / Cell Change while in Extended Uplink/ With Packet Neighbouring Cell Data
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.8.1 Conformance requirements
|
If CCN is enabled (see sub-clause 5.5.1.1a), the mobile station shall behave as in network control mode NC0 or NC1 up to the point when a new cell has been chosen. It shall then check the CCN_SUPPORTED parameter, if available, that was last received for that cell. This parameter can be sent on BCCH or PBCCH or individually in PACKET MEASUREMENT ORDER or in PACKET CELL CHANGE ORDER messages. If it is available and if it indicates that CCN mode shall be entered towards that cell or if it is not available, then instead of performing the cell change, the mobile station shall start timer T3206 and enter the CCN mode. At the first possible opportunity, the MS shall then, when in CCN mode, inform the network about the proposed cell by sending a PACKET CELL CHANGE NOTIFICATION message, stop timer T3206, start timers T3208 and T3210. The PACKET CELL CHANGE NOTIFICATION message shall contain the ARFCN for the BCCH and the BSIC as identity of the proposed cell. The message shall also contain measurement reports for the proposed cell and for other neighbour cells if available. In CCN mode the mobile station shall continue the data transfer and store neighbour cell system information if received in instances of the PACKET NEIGHBOUR CELL DATA message, but not perform the cell change. At receipt of the first PACKET NEIGBOUR CELL DATA message or PACKET CELL CHANGE CONTINUE message or PACKET CELL CHANGE ORDER message, the mobile station shall stop the timer T3210.If a mobile station as response to a PACKET CELL CHANGE NOTIFICATION message receives a PACKET CELL CHANGE CONTINUE message without receiving any neighbour cell system information, the mobile station shall stop timer T3208, stop timer T3210 if still running, leave CCN mode and continue cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE CONTINUE message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE CONTINUE message is received, the mobile station shall stop timer T3208, leave CCN mode and continue the cell reselection in NC0/NC1 mode. The network sends first necessary system information for the cell proposed in the PACKET CELL CHANGE NOTIFICATION message, or for any other cell, in one or more instances of the PACKET NEIGHBOUR CELL DATA message and sends then a PACKET CELL CHANGE ORDER message. The mobile station shall store the received system information as specified in sub-clause 8.8.1. When the first instance of the PACKET NEIGHBOUR CELL DATA message is received, the mobile station shall stop timer T3210 if still running. When the PACKET CELL CHANGE ORDER message is received, the mobile station shall stop timer T3208, leave CCN mode and follow the procedures as specified for the Packet Cell Change Order (sub-clause 8.4) and in sub-clause 8.8.1.
In extended uplink TBF mode, the uplink TBF may be maintained during temporary inactive periods, where the mobile station has no RLC information to send.
During the temporary inactive periods, the mobile station may stop sending RLC data block, as defined in clause 9.1.3. The network shall continue allocating the mobile station uplink radio blocks during the inactivity period, using the procedures defined in clause 8.1.1 for each medium access mode. Uplink radio blocks shall be allocated as required allowing the mobile station to continue the transfer of RLC data blocks, when a new RLC data block becomes available.
When the mobile station is allocated an uplink radio block and there is no RLC data block ready to send, the mobile station shall send an RLC/MAC control block in each uplink radio block allocated by the network. The priority defined in clause 8.1.1 for different kinds of RLC/MAC blocks apply.
References
3GPP TS 44.060, subclause 8.8.3
3GPP TS 44.060, subclause 9.3.1b.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.8.2 Test purpose
|
To verify that: MS takes into consideration the change of parameter NW_EXT_UTBF in SI13 (sent in PACKET NEIGHBOUR CELL DATA) and operate in Extended Uplink TBF in the new cell.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.8.3 Method of test
|
Initial conditions
System Simulator:
2 cells, GPRS supported, CCN Active, RXLEV_ACCESS_MIN = -90dBm,.
Cell A: RLA_C = -50 dBm, is active and NW_EXT_UTBF = 0.
Cell B: Supports PACKET SI STATUS. No System Information is broadcast on the BCCH, except SI3. This is only made to make it possible to verify that the MS uses the information in Packet Neighbour Cell Data. RLA_C = -60 dBm, is active and NW_EXT_UTBF = 1.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate packet uplink transfer. SS assigns resources to the MS and it starts to send uplink data that the SS acknowledge. During the uplink the signal strength of Cell A is lowered to – 80 dBm. The MS enters CCN mode and sends PACKET CELL CHANGE NOTIFICATION. SS sends one or more PACKET NEIGHBOUR CELL DATA to the MS (with NW_EXT_UTBF in SI13 set to 1). The SS then sends PACKET CELL CHANGE CONTINUE and the MS change to Cell B. The MS requests resources for an uplink and asks for the SI2 and SI2bis messages by sending PACKET_SI_STATUS. In the new cell the MS completes the uplink transfer while operating in extended uplink TBF.
Maximum duration of the test
-
Expected sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 1200 octets.
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: same as channel coding
CHANNEL_CODING_COMMAND: cs-1
No starting time present.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
3
MS -> SS
RLC DATA BLOCK
4
Repeat step 2 and 3 five times
5
SS
Lower signal strength of Cell A to –80 dBm.
6
SS -> MS
PACKET UPLINK ACK/NACK
USF assigned to the MS
7
MS -> SS
RLC DATA BLOCK
Or
PACKET CELL CHANGE NOTIFICATION
8
Step 6 and 7 are repeated until a PACKET CELL CHANGE NOTIFICATION is received in step 7, but no longer than 15 sec.
The test has failed if no PACKET CELL CHANGE NOTIFICATION is received in Cell A within 15 sec from Step 5.
9
SS -> MS
PACKET NEIGHBOUR CELL DATA
USF assigned to the MS
10
MS -> SS
RLC DATA BLOCK
11
Step 9 and 10 are repeated until all instances of PACKET NEIGHBOUR CELL DATA are sent
(SI13 with NW_EXT_UTBF = 1 and SI_STATUS_IND = 1).
12
SS -> MS
PACKET CELL CHANGE CONTINUE
The following messages are to be sent and received in Cell B.
13
{Uplink dynamic allocation two phase access}
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end
TLLI_BLOCK_CHANNEL_CODING: same as channel coding
CHANNEL_CODING_COMMAND: cs-1
No starting time present.
14
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS.
15
MS -> SS
RLC DATA BLOCK or
PACKET SI STATUS or
PACKET RESOURCE REQUEST
Step 16 is performed only if a PACKET RESOURCE REQUEST is received in step 15.
16
SS -> MS
PACKET UPLINK ASSIGNMENT
Repeats the PDTCH assignment given in step 13.
17
Step 14 and 15 are repeated until a PACKET SI STATUS is received in step 15.
The PACKET SI STATUS shall be sent within 10 sec of accessing the cell. Verify that the MS does not request SI that was sent in step 9.
If the RLC DATA BLOCK with BSN = 0 received in Step 15 contains an empty LLC PDU as the first LLC PDU, Steps 14 and 15 are further repeated until a PACKET RESOURCE REQUEST is received in Step 15.
NOTE: The empty LLC PDU may be accompanied by another low priority RLC data block (with Packet Resource Request and Packet Uplink Assignment or Packet Timeslot Reconfigure as required), in order to ensure that the radio resources are used efficiently.
18
PACKET SERVING CELL DATA
SI2,SI4 and SI2bis messages are sent .
19
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
20(optional step)
MS -> SS
RLC DATA BLOCK or
PACKET RESOURCE REQUEST
21(conditional step)
SS->MS
PACKET UPLINK ASSIGNMENT
Step 21 is performed only PRR is sent step 20.
Contains the same frequency parameter as PUA in step 13.
22
Repeat step 19 and 20 until CV=0.
23
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 0. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
24
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS, sent after 6 blocks from step 23
A24 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B24.
B24(optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
25
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
26
Repeat step 24 and 25 five times.
27
MS
Trigger the MS to send 500 octets of data. SS should take care of allocating USF’s to the MS in order to prevent the MS from releasing the TBF
28
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
29
MS -> SS
UPLINK RLC DATA BLOCK
30
Repeat step 28 and 29 until CV=0
31
SS -> MS
PACKET UPLINK ACK/NACK
Final Ack Indication = 1 containing valid RRBP. Sent on PACCH of the assigned PDCH. Acknowledge all data blocks received.
32
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
Specific message contents
PACKET NEIGHBOUR CELL DATA in Step 9
The message contains the default SI13 with NW_EXT_UTBF = 1 and SI_STATUS_IND = 1, default SI1 and SI3 for Cell B.
Information element
Value/remark
< PAGE_MODE : bit (2) >
00 (Normal Paging)
0
0
< GLOBAL_TFI : Global TFI IE >
0 <5 bit Uplink TFI>
< CONTAINER_ID : bit (2) >
01 for SI belonging to Cell B
< SPARE :bit(1)>
0
< CONTAINER INDEX :bit (5)>
00000 to the index needed to send all SIs for each cell.
0 | 1
0 No ARFCN or BSIC
Container repetition struct
< PD : bit(3)>
000, BCCH
PACKET CELL CHANGE CONTINUE in Step 12
Information element
Value/remark
< PAGE_MODE : bit (2) >
00 (Normal Paging)
0
0
< GLOBAL_TFI : Global TFI IE >
0 <5 bit Uplink TFI>
0 | 1
1
< ARFCN : bit (10) >
ARFCN of Cell B.
< BSIC : bit (6) >
BSIC of Cell B.
<CONTAINER_ID>
01
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.9 TBF Release / Extended Uplink / Change of RLC mode / Normal release
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.9.1 Conformance requirements
|
During an uplink packet transfer, upper layer may request to transfer another LLC PDU. If the new LLC PDU does not have the same RLC mode as the current uplink TBF but has a higher radio priority, the mobile station shall complete the transmission of the current LLC PDU using the countdown procedure including acknowledgement from the network, if in acknowledged mode.
If the TBF is operated in extended uplink TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing RLC mode.
The mobile station shall send a PACKET RESOURCE REQUEST message on PACCH indicating the new RLC mode and start timer T3168.
If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and restart timer T3168.
On receipt of a PACKET RESOURCE REQUEST message, indicating a change of RLC mode, the network shall release the uplink TBF at a point determined by the network, using the procedure defined in sub-clause 9.5.
On receipt of PACKET UPLINK ACK/NACK with Final Ack Indicator set to '1' the mobile station shall stop timer T3168 and after sending the PACKET CONTROL ACK perform the change of RLC mode by establishing a new TBF.
References
3GPP TS 44.060, subclauses 8.1.1.6, 8.1.1.1.2, and 9.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.9.1.2 Test purpose
|
To verify that during extended uplink TBF the MS re-establishes the TBF and changes the RLC mode.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.9.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, BS_CV_MAX = 14, T3168 timeout value=7 (4s), N201-U=500 for SAPI 3, 5, 9, 11, N201-U=270 for SAPI 7.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 1 and context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
An uplink TBF is established and in progress. SS assigns USFs allowing the MS to transmit data blocks. The MS is triggered to transfer 220 octets user data with a different RLC mode and higher radio priority.
The mobile station shall complete the transmission of the current LLC PDU; SS will verify the complete reception of the LLC PDU.
SS acknowledges the LLC PDU with a Packet Uplink Ack/Nack with TBF Est field is set to '1' and Final Ack Indicator bit set to '1'.
The mobile station shall use the same procedures as are used for TBF establishment using two phase starting from the point where the mobile station transmits the PACKET RESOURCE REQUEST message
In case the MS ignores the TBF Est field in the PACKET UPLINK ACK/NACK , the mobile station shall transmit a PACKET CONTROL ACKNOWLEDGEMENT message, release the TBF and shall establish a new TBF using two phase access.
SS assigns a PDCH to the MS. SS assigns USFs allowing the MS to transmit data blocks until the countdown value CV=0.
SS sends a Packet Uplink Ack/Nack with TBF Est field set to '0' and Final Ack Indicator bit set to '1' and the MS is polled. The MS answers with a Packet Control Acknowledgement and the TBF is released.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
{Uplink dynamic allocation two phase access}
In PDP context2,
n = 220 octets, without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end,
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1,
RADIO_PRIORITY = 4
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH, the USF assigned to the MS, on 3 blocks from the last radio block containing the uplink assignment.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI, and BSN is correct.
4
Repeat step 2 and 3 three times
5
MS
To trigger the MS to transfer 220 octets: in test PDP context1, unacknowledged RLC mode and
Radio Priority = 1
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH, the USF assigned to the MS.
7
MS -> SS
UPLINK RLC DATA BLOCK
Or
Received on the assigned PDTCH.
Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI, and BSN is correct.
Send PACKET UPLINK ACK/NACK to acknowledge all received data blocks when CV=0 and PACKET RESOURCE REQUEST is not yet received.
(Note: MS may retransmit the block with BSN=0 once if it has already been scheduled while PACKET UPLINK ACK/NACK is being processed and the new LLC PDU is not ready for the transmission)
PACKET RESOURCE REQUEST
Or
Received on PACCH of the assigned PDCH indicating the change of RLC mode.
Check for radio priority level = 1 and RLC mode
Unacknowledged RLC mode.
PACKET UPLINK DUMMY CONTROL BLOCK
The MS is in extended TBF mode.
8
Repeat step 6 and 7 until CV = 0 and a PACKET RESOURCE REQUEST is received.
9
SS -> MS
PACKET UPLINK ACK/NACK
Sent on the PACCH of the PDCH assigned, acknowledging all blocks so far.
FINAL_ACK_INDICATION = '1',TBF Est = 1, Valid RRBP.
10
SS
Verify that only one complete LLC PDU has been received.
11
(optional)
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH. If not received continue with step 14.
12 (conditional)
MS -> SS
CHANNEL REQUEST
CHANNEL REQUEST with establishment cause = 'Single block packet access' or one phase packet access.
13 (conditional)
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on the AGCH
14
MS -> SS
PACKET RESOURCE REQUEST
Received on PACCH of the assigned PDCH
Check for radio priority level = 1 and RLC mode
Unacknowledged RLC mode. Received on the block specified by the single block assignment of step 13 or by the RRBP of step 9.
15
SS -> MS
PACKET UPLINK ASSIGNMENT
Open-ended uplink dynamic allocation, no starting time, USF_GRANULARITY = single block. Sent on PACCH of the assigned PDCH.
16
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS. Sent on PACCH of the assigned PDCH.
17
MS -> SS
UPLINK RLC DATA BLOCK
Received on the PDTCH assigned.
18
Repeat step 16 and 17 until countdown value CV=0.
19
SS -> MS
PACKET UPLINK ACK/NACK
FINAL_ACK_INDICATION = '1', TBF Est = 0, a valid RRBP, acknowledge all received data, sent on PACCH.
20
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.10 TBF Release / Extended Uplink / Change of RLC mode / Abnormal release
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.10.1 Conformance requirements
|
During an uplink packet transfer, upper layer may request to transfer another LLC PDU. If the new LLC PDU does not have the same RLC mode as the current uplink TBF but has a higher radio priority, the mobile station shall complete the transmission of the current LLC PDU using the countdown procedure including acknowledgement from the network, if in acknowledged mode. immediately request a resource reallocation for uplink according to the new Radio Priority of the new LLC PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and starting timer T3168.
If the TBF is operated in extended uplink TBF mode (see sub-clause 9.3.1b), the mobile station shall use the procedure in sub-clause 8.1.1.6 for changing RLC mode.
Then the mobile station shall complete the transmission of the current LLC PDU. If the TBF is operated in extended uplink TBF mode, the mobile station shall release the uplink TBF and re-establish a new uplink TBF in order to change the RLC mode
The mobile station shall send a PACKET RESOURCE REQUEST message on PACCH indicating the new RLC mode and start timer T3168.
If timer T3168 expires, the mobile station shall retransmit the PACKET RESOURCE REQUEST message and restart timer T3168.
If timer T3168 expires and the PACKET RESOURCE REQUEST message has already been transmitted four
times, the mobile station shall perform an abnormal release with access retry (see sub-clause 8.7.2).
On receipt of a PACKET RESOURCE REQUEST message, indicating a change of RLC mode, the network shall release the uplink TBF at a point determined by the network, using the procedure defined in sub-clause 9.5.
On receipt of PACKET UPLINK ACK/NACK with Final Ack Indicator set to '1' the mobile station shall stop timer T3168 and after sending the PACKET CONTROL ACK perform the change of RLC mode by establishing a new TBF.
References
3GPP TS 44.060, subclauses 8.1.1.6, subclauses 8.1.1.1.2, subclause 9.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.10.1.2 Test purpose
|
To verify that during extended uplink TBF the MS perform an abnormal release with access retry after timer T3168 expired and PACKET RESOURCE REQUEST message has been transmitted four times.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.6.10.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, NW_EXT_UTBF = 1, BS_CV_MAX = 14, T3168 timeout value=7 (4s), N201-U=500 for SAPI 3, 5, 9, 11, N201-U=270 for SAPI 7.
Mobile Station:
MS is in Packet Idle mode, GPRS attached with support of GERAN Feature Package 1 indicated in MS Radio Access Capabilities, and PDP context 1 and context 2 established.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
An uplink TBF is established and in progress. SS assigns USFs allowing the MS to transmit data blocks until the MS completes the countdown procedure. As soon as the MS is in extended UL TBF mode, the MS is triggered to transfer 220 octets user data with different RLC mode.
The mobile station shall immediately request a resource reallocation for uplink indicating the changed RLC mode applied to the new LLC PDU by sending a PACKET RESOURCE REQUEST message on the PACCH and start timer T3168.
SS keeps assigning USFs, the MS will send Packet Uplink Dummy Control Blocks till T3168 expire. The MS will send a PACKET RESOURCE REQUEST message again on the PACCH and restart timer T3168.
The SS keeps assigning USFs till the MS has transmitted the Packet Resource Request four times.
The MS shall perform an abnormal release with access retry.
The SS will assign new resources to the MS to complete the new TBF.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
SS
{Uplink dynamic allocation two phase access}
In PDP context2,
n = 220 octets, without starting time,
USF_GRANULARITY = 1 block,
RLC_DATA_BLOCKS_GRANTED = open-end,
TLLI_BLOCK_CHANNEL_CODING: cs1,
CHANNEL_CODING_COMMAND: cs1,
RADIO_PRIORITY = 4
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH, the USF assigned to the MS, on 3 blocks from the last radio block containing the uplink assignment.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH.
Check that the coding as specified by CHANNEL_CODING_COMMAND, the TFI is correct.
4
Repeat step 2 and 3 till CV = 0
5
SS -> MS
PACKET UPLINK ACK/NACK
Sent on the PACCH of the PDCH assigned, the USF not assigned to the MS, acknowledging all blocks.
FINAL_ACK_INDICATION = '0',TBF Est = 1
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS, sent after 6 blocks from step 5
A6 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit the block with BSN=0 once if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case go to step B6.
B6 (optional step)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
MS is in extended UL TBF mode.
8
MS
To trigger the MS to transfer 220 octets: in test PDP context1, unacknowledged RLC mode and
Radio Priority = 1
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
A10 (optional step)
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
MS may transmit while processing the uplink data trigger PACKET UPLINK DUMMY CONTROL BLOCK. In this case repeat step 9 until a PACKET RESOURCE REQUEST is received.
10
MS -> SS
PACKET RESOURCE REQUEST
MS starts T3168.
Received on the PACCH of the assigned PDCH, Indicating the change of RLC mode:
Check that radio priority level = 1 and
Unacknowledged RLC mode.
11
SS -> MS
PACKET UPLINK ACK/NACK
To prevent T3184 from expiring, sent on the PACCH of the PDCH assigned, the USF not assigned to the MS, acknowledging all Blocks.
FINAL_ACK_INDICATION = '0', TBF Est = 0
12
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
13
MS -> SS
PACKET UPLINK DUMMY CONTROL BLOCK
Or
MS is in extended UL TBF mode
PACKET RESOURCE REQUEST
Received on the PACCH of the assigned PDCH, Indicating the change of RLC mode:
Check that radio priority level = 1 and
Unacknowledged RLC mode.
14
Repeat step 12 and 13 until a PACKET RESOURCE REQUEST has been received. Check that the PACKET RESOURCE REQUEST is received within T3168 +/- 10% from the previous PACKET RESOURCE REQUEST.
15
Repeat Step 11 to Step 14 until the PACKET RESOURCE REQUEST has been received a total of 4 times.
MS shall perform an abnormal release with access retry
16
MS -> SS
CHANNEL REQUEST
CHANNEL REQUEST with establishment cause = 'Single block packet access' or one phase packet access.
17
SS -> MS
IMMEDIATE ASSIGNMENT
Sent on the AGCH
18
MS -> SS
PACKET RESOURCE REQUEST
Received on the single block assigned in step 17. Check that radio priority level = 1, peak throughput class = 5, unacknowledged RLC mode.
19
SS -> MS
PACKET UPLINK ASSIGNMENT
Open-ended uplink dynamic allocation, no starting time, USF_GRANULARITY = single block.
20
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
The USF assigned to the MS. Sent on PACCH of PDCH assigned in step 19.
21
MS -> SS
UPLINK RLC DATA BLOCK
Received on the PDTCH assigned.
22
Repeat step 20 and 21 until countdown value CV=0.
23
SS -> MS
PACKET UPLINK ACK/NACK
FINAL_ACK_INDICATION = '1', a valid RRBP, acknowledge all received data, sent on PACCH.
24
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Received on the block specified by RRBP on PACCH of the assigned PDCH.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.3.7 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.4 Void
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5 Dual transfer mode
|
To bring the MS into active state U10, macro 40.4.3.22 shall be used.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1 PS establishment whilst in dedicated mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1 Uplink TBF establishment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1 Uplink TBF establishment with no reallocation of CS resources
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.1 Uplink TBF establishment with no reallocation of CS resources / Successful case / Uplink resources assigned
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.1.1 Conformance requirements
|
While in dedicated mode, the establishment of an uplink packet resource may be initiated by the RR entity of the mobile station using the packet request procedure. The procedure is triggered by a request from upper layers to transfer an LLC PDU; see 3GPP TS 24.007.
On receipt of a DTM REQUEST message the network may allocate an uplink packet resource. The packet uplink resource is assigned to the mobile station in one of the DTM assignment messages:
- DTM ASSIGNMENT COMMAND or
- PACKET ASSIGNMENT.
The PACKET ASSIGNMENT message is only used when the packet resource is a PDCH and no reallocation of the RR connection is needed.
On receipt of:
- DTM ASSIGNMENT COMMAND message or
- PACKET ASSIGNMENT message,
the mobile station shall stop T3148.
- when the network sends a PACKET ASSIGNMENT message, the packet request procedure is completed for the network when assignment message is sent and for the mobile station when it is received.
When the packet request procedure is completed, the mobile station has entered the dual transfer mode.
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.1.2 Test purpose
|
To verify that the MS:
- decodes correctly the Cell’s System information, understanding that DTM access is allowed;
- requests an uplink TBF when it has something to send;
- acts upon the PACKET ASSIGNMENT message and then transmitting on the PDCH allocated.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is in packet idle mode with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink transfer data in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS assigns the MS PS resource. The SS accomplishes the resource assignment by passing a PACKET ASSIGNMENT message to the MS. On receipt of the PACKET ASSIGNMENT message, the MS starts to send RLC DATA BLOCKS to the SS on the assigned PDTCH.
The codec to be used in this test is chosen dependent on the capabilities of the MS.
MS supporting DTM shall complete testing for k=1and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in the active state (U10) of a call on Timeslot N. When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
PACKET ASSIGNMENT
SS sends this message such that it is received before Timer T3148 expiry. Includes information on the Radio resources provided to the MS. See specific message contents.
5
MS<->SS
{ Uplink data transfer }
Macro - Completion of the 1000 Octets of Data.
Specific Message Contents
PACKET ASSIGNMENT (Step 4):
k=1;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N 1) MOD 8
RR Packet Downlink Assignment IE
Not included
k=2;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
N
RR Packet Downlink Assignment IE
Not included
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.2 Uplink TBF establishment with no reallocation of CS resources / Successful case / Downlink resources assigned
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.2.1 Conformance requirements
|
While in dedicated mode, the establishment of an uplink packet resource may be initiated by the RR entity of the mobile station using the packet request procedure. The procedure is triggered by a request from upper layers to transfer an LLC PDU; see 3GPP TS 24.007.
On receipt of a DTM REQUEST message the network may allocate an uplink packet resource. The packet uplink resource is assigned to the mobile station in one of the DTM assignment messages:
- DTM ASSIGNMENT COMMAND or
- PACKET ASSIGNMENT.
The PACKET ASSIGNMENT message is only used when the packet resource is a PDCH and no reallocation of the RR connection is needed.
On receipt of:
- DTM ASSIGNMENT COMMAND message or
- PACKET ASSIGNMENT message,
the mobile station shall stop T3148.
If the received DTM ASSIGNMENT COMMAND or PACKET ASSIGNMENT message includes uplink packet resources, the mobile station shall proceed with the packet access. If the received message includes downlink packet resources and no uplink packet resources, the mobile station shall abort the packet access procedure and proceed with the procedure specified in clause 3.4.22.3, and then attempt an establishment of uplink TBF, using the applicable procedure specified in 3GPP TS 04.60.
- when the network sends a PACKET ASSIGNMENT message, the packet request procedure is completed for the network when assignment message is sent and for the mobile station when it is received.
When the packet request procedure is completed, the mobile station has entered the dual transfer mode.
If the received PACKET ASSIGNMENT message includes downlink packet resources and no uplink packet resources, the mobile station shall abort the packet access procedure and proceed with the downlink TBF establishment, and then attempt an establishment of uplink TBF.
References
3GPP TS 04.18/44.018 sub-clauses 3.4.22.1.1, 3.4.22.3
3GPP TS 04.60/44.060 sub-clause 8.1.2.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.2.2 Test purpose
|
To verify that the MS:
- decodes correctly the Cell’s System information, understanding that DTM access is allowed;
- requests an uplink TBF;
- acts upon the PACKET ASSIGNMENT message containing downlink resources.
- attempts uplink TBF establishment, once the downlink TBF establishment is complete.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported
Mobile Station:
The MS is in the active state (U10) of a call on cell A.
The MS is in packet idle mode with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink transfer data in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS assigns the MS downlink PS resources using the PACKET ASSIGNMENT message. The MS, upon receipt of the assignment message, aborts the packet access procedure and proceeds with the downlink assignment. When possible the MS requests the uplink TBF establishment. The SS upon receipt of the resource request allocates the MS uplink resources using the PACKET UPLINK ASSIGNMENT message. The MS then starts to send RLC DATA BLOCKS to the SS on the assigned PDTCH.
The codec to be used in this test is chosen dependent on the capabilities of the MS.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in the active state (U10) of a call on Timeslot N of cell A. When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
PACKET ASSIGNMENT
SS sends this message such that it is received before Timer T3148 expiry. See specific message contents.
5
SS<->MS
{ Downlink data }
Macro
6
MS->SS
PACKET DOWNLINK ACK/NACK
Channel Request Description IE indicating that uplink resources are required.
7
SS->MS
PACKET UPLINK ASSIGNMENT
When:
k=1, Timeslot = T;
k=2, Timeslot = N.
8
MS<->SS
{ Uplink data transfer }
Macro - Completion of the 10kB of Data.
Specific Message Contents
PACKET ASSIGNMENT (Step 4):
k=1;
As default message contents except:
RR Packet Uplink Assignment IE
Not included
RR Packet Downlink Assignment IE
- TIMESLOT_ALLOCATION
T = (N 1) MOD 8
k=2;
As default message contents except:
RR Packet Uplink Assignment IE
Not included
RR Packet Downlink Assignment IE
- TIMESLOT_ALLOCATION
N
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.3 Uplink TBF establishment with no reallocation of CS resources / Abnormal cases / DTM reject
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.3.1 Conformance requirements
|
On receipt of the DTM REJECT message, the mobile station stops T3148, notifies upper layers of a packet resource establishment failure and starts timer T3142 with the indicated value.
The mobile station is not allowed to make a new attempt for packet access in the same cell until T3142 expires
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1.3.3
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.3.2 Test purpose
|
To verify that when the MS receives a DTM REJECT message, the MS does not attempt to re-acquire uplink packet resources for a period specified by a wait indication (T3142), contained in the DTM REJECT message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported
Mobile Station:
The MS is in the active state (U10) of a call on cell A.
The MS is in packet idle mode with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink transfer data in RLC acknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, the SS returns a DTM REJECT message, simulating the inability to allocate the requested packet resource. The DTM REJECT message includes a wait indication (T3142) specifying that the MS is to wait 5 seconds before being allowed to re-request resources. The MS is again prompted to initiate an uplink TBF before the wait indication has expired, it is then tested that the MS does not try to access the network until the Wait Indication has expired. After the Wait Indication has expired, the MS initiates the packet access procedure and sends a DTM REQUEST message.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
2 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in state U10, utilising Timeslot N for CS connection (Timeslot chosen arbitrarily). When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
DTM REJECT
SS sends this message such that it is received before Timer T3148 expiry. The message contains the “Wait Indication” which is set to 10 seconds.
5
SS
Waits 2 seconds
6
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets. If triggering of data involves manual operation, this is to be finished within 5 seconds.
7
SS
Monitors the MS, checking that the MS does not try and establish an uplink TBF until at least 10 seconds after the DTM REJECT message was passed to the MS.
8
MS->SS
DTM REQUEST
Check that this message is sent after the Wait Indication has expired.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.4 Uplink TBF establishment with no reallocation of CS resources / Abnormal cases / Inter System to UTRAN Handover Command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.4.1 Conformance requirements
|
Only valid for a UTRAN capable MS. In dedicated mode or dual transfer mode, a change to UTRAN channel(s) can be requested by the network RR sublayer. This change is performed through the handover to UTRAN procedure.
If the mobile station receives an INTER SYSTEM TO UTRAN HANDOVER COMMAND message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the handover to UTRAN procedure as specified in clause 3.4.4a.
References
3GPP TS 04.18/44.018 sub-clauses 3.4.4a & 3.4.22.1.1.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.4.2 Test purpose
|
Verifying that the MS aborts the Packet Access procedure and proceed with the handover to UTRAN, upon reception of an INTER SYSTEM TO UTRAN HANDOVER COMMAND message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.4.3 Method of test
|
Initial Conditions
System Simulator:
2 cells - Cell 1 is GSM with DTM supported, Cell 2 is UTRAN. The present document sub-clause 26.6.5.1 shall be referenced for the default parameters of cell 1. 3GPP TS 34.108, sub-clause 6.1 shall be referenced for default parameters of Cell 2.
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is GPRS idle with a P-TMSI allocated and the PDP context 1 activated
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The SS starts the GSM cell and UTRAN cell with cell selection conditions in favour of GSM cell, the MS selects the GSM cell for camping on. The SS brings the MS into the call active state (CC state U10). The MS is then triggered to initiate packet uplink data transfer in RLC acknowledged mode and sends a DTM REQUEST message. On receiving the DTM REQUEST message, requesting uplink resources, the SS configures the dedicated channel corresponding to the pre-configuration in UTRAN cell, then sends INTERSYSTEM TO UTRAN HANDOVER COMMAND message indicating the dedicated channel of the target cell to the MS through the GSM serving cell. After the MS receives the command it shall configure itself accordingly and switch to the dedicated channel of the UTRAN cell. The SS checks whether the handover is performed by confirming the MS transmits a HANDOVER TO UTRAN COMPLETE message to the SS, on the DCCH of the UTRAN cell. To check that CS call is still active, SS Releases the CS call. To check that PDP context is active, SS sends MODIFY PDP CONTEXT REQUEST in UMTS cell. The MS may or may not accept the QoS and replies to the SS accordingly.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
SS
MS in state U10, utilising Timeslot N for CS connection (Timeslot chosen arbitrarily)
2
MEASUREMENT INFORMATION
3
MEASUREMENT REPORT
Including Measurement Results on the UTRAN cell
4
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
5
MS->SS
DTM REQUEST
6
SS->MS
INTER SYSTEM TO UTRAN HANDOVER COMMAND
The message is received before the timer T3148 expires. See specific message contents.
7
MS
The MS accepts the handover command and configures its lower layers using the parameters contained in the INTERSYSTEM TO UTRAN HANDOVER COMMAND
8
SS
The SS waits for uplink physical channel in synchronization
9
MS->SS
HANDOVER TO UTRAN COMPLETE
The SS receives this message on DCCH of cell 2 (UTRAN cell). It implies that the down link physical channel has synchronised with UTRAN.
10
SS
The SS starts integrity protection for CS domain
11
SS->MS
UTRAN MOBILITY INFORMATION
The SS conveys CN system information for the PS domain to the UE in connected mode. See specific message contents.
12
MS->SS
UTRAN MOBILITY_INFORMATION CONFIRM
13
MS->SS
ROUTING AREA UPDATE REQUEST
14
SS->MS
AUTHENTICATION AND CIPHERING REQUEST
15
MS->SS
AUTHENTICATION AND CIPHERING RESPONSE
16
SS
The SS starts integrity protection for PS domain
17
SS->MS
ROUTING AREA UPDATE ACCEPT
18
SS Releases the CS call.
19
SS->MS
MODIFY PDP CONTEXT REQUEST
SS requests the modification of a PDP context.
A20
MS->SS
MODIFY PDP CONTEXT ACCEPT
MS behaviour type A: Accept the PDP context modification
B20
MS->SS
DEACTIVATE PDP CONTEXT REQUEST
MS behaviour type B: Initiate the PDP context deactivation. Cause set to 'QoS not accepted'
B20a
SS->MS
DEACTIVATE PDP CONTEXT ACCEPT
MS behaviour type B: Accept the PDP context deactivation
B20b
MS->SS
DETACH REQUEST
MS behaviour type B: A non-auto attach MS may (optionally) send a Detach Request. The SS shall wait up to 'T3390' seconds for the Detach Request.
B20c
SS->MS
DETACH ACCEPT
If the MS transmitted a Detach Request message in step B20b then the SS responds with a Detach Accept message.
Specific message contents
MEASUREMENT INFORMATION
Information Element
Value/remark
< RR short PD : bit >
0
< Message type : bit (5) >
‘00101’B
< Short layer 2 header : bit (2) >
‘00’B
< BA_IND : bit >
0
< 3G_BA_IND : bit >
0
< MP_CHANGE_MARK : bit >
0
< MI_INDEX : bit (4) >
‘0000’B
< MI_COUNT : bit (4) >
‘0000’B
< PWRC : bit >
0
< REPORT_TYPE : bit >
1 (Measurement Reporting shall be used)
< REPORTING_RATE : bit >
0 (SACCH rate reporting)
< INVALID_BSIC_REPORTING : bit >
0 (Report on cells with invalid BSIC not allowed)
0 | 1 < Real Time Difference Description >
0
0 | 1 < BSIC Description >
0
0 | 1 < REPORT PRIORITY Description >
0
0 | 1 < MEASUREMENT Parameters Description >
0
0 | 1 < extension length >
0
0 | 1 < 3G Neighbour Cell Description >
1
0 | 1 < 3G_Wait : bit (3) >
0
0 | 1 < Index_Start_3G : bit (7) >
0
0 | 1 < Absolute_Index_Start_EMR : bit (7) >
0
0 | 1 < UTRAN FDD Description >
1
0 | 1 < Bandwidth_FDD : bit (3) >
0
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
1
0 < FDD-ARFCN : bit (14) >
0 See TS 34.108, clause 6.1.5, table 6.1.1
< FDD_Indic0 : bit >
0
< NR_OF_FDD_CELLS : bit (5) >
‘00001’B
< FDD_CELL_INFORMATION Field >
10 bits
Scrambling code according to TS 34.108, clause 6.1.4, Default settings for cell No.1
1 < Repeated UTRAN FDD Neighbour Cells > ** 0
0
0 | 1 < UTRAN TDD Description >
0
0 | 1 < CDMA2000 Description >
0
0 | 1 < 3G MEASUREMENT Parameters Description >
< Qsearch_C : bit (4) >
‘0111’B (Always)
< 3G_SEARCH_PRIO: bit (1) >
1
< FDD_REP_QUANT : bit (1) >
1 (Ec/No)
0 | 1 < FDD_MULTIRAT_REPORTING : bit (2) >
‘1 01’B (Report on 1 UTRAN cell)
0 | 1 < FDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < TDD_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < TDD_REPORTING_OFFSET : bit (3) >
0
0 | 1 < CDMA2000_MULTIRAT_REPORTING : bit (2) >
0
0 | 1 < CDMA2000_REPORTING_OFFSET : bit (3) >
0
INTERSYSTEM TO UTRAN HANDOVER COMMAND
Information Element
Value/remark
RR management Protocol Discriminator
‘0110'B
Skip Indicator
‘0000'B
Inter System to UTRAN Handover Command Message Type
‘01100011'B
Length of Handover to UTRAN Command contents
Octet length of the "Handover to UTRAN Command value part"
Handover to UTRAN Command value part
PER encoded ASN.1 value of type "HandoverToUTRANCommand-v1-IEs", the content is presented in the next table.
Content of "HandoverToUTRANCommand-v1-IEs"
Information Element
Value/remark
New U-RNTI
- SRNC Identity
‘000000000001'B
- S-RNTI-2
Set to arbitrary value corresponding to DPCH Offset value currently stored in SS
Activation time
now
Ciphering algorithm
The presence of this IE is dependent on IXIT statements in TS 34.123-2. If ciphering is indicated to be active, use UEA1. Else, this IE is omitted
CHOICE specificationMode
Preconfiguration
CHOICE preconfiguration mode
Default configuration
- Default configuration mode
FDD
- Default configuration identity
3 (12.2 kbps speech + 3.4 kbps signalling)
- RAB Info
- RAB identity
- GSM-MAP RAB identity
‘00000001'B
- CN domain identity
CS domain
- CHOICE Mode specific info
FDD
- UL DPCH info
- UL DPCH power control info
- DPCCH power offset
–-78dB (i.e. ASN.1 IE value of -20 ( 2 + ( IE Value * 4)) )
- PC Preamble
1 frame
- SRB delay
7 frames
- Scrambling code type
Long
- Reduced scrambling code number
0
- Spreading factor
64
- DL common information post
- DL DPCH info common
- DL DPCH power control info
- CHOICE Mode specific info
FDD
- DPC mode
Single TPC
- DL information perRL list
- Primary CPICH info
- Primary scrambling code
100
- DL DPCH info perRL
- pCPICH usage for channelEst
May be used
- DL channelisation code
- Secondary scrambling code
1
- SF and code number
SF = 128, code number = 0
- Scrambling code change
No code change
- TPC combination index
0
- Frequency info
- UARFCN uplink(Nu)
Not Present
Absence of this IE is equivalent to apply the default duplex distance defined for the operating frequency according to TS 25.101
- UARFCN downlink(Nd)
See TS 34.108, clause 6.1.5, table 6.1.1
Maximum allowed UL TX power
See TS 34.108, clause 6.1.5, table 6.1.1
Contents of UTRAN MOBILITY INFORMATION message:
The contents of the UTRAN MOBILITY INFORMATION message in this test case is identical to the default message in TS 34.108, with the following exceptions.
Information Element
Value/remark
Message Type
Integrity check info
As default
RRC transaction identifier
As default
Integrity protection mode info
As default
Ciphering mode info
As default
New U-RNTI
As default
New C-RNTI
As default
UE Timers and constants in connected mode
As default
CN information info
- PLMN identity
Not present
- CN common GSM-MAP NAS system information
Not present
- CN domain related information
- CN domain identity
CS domain
- CN domain specific GSM-MAP NAS system info
- T3212
30 (periodic updating every 3 hours)
- ATT
1 (MS shall apply IMSI attach and detach procedures)
- CN domain specific DRX cycle length coefficient
7
- CN domain related information
- CN domain identity
PS domain
- CN domain specific GSM-MAP NAS system info
- RAC
6 (GERAN and UTRAN cells use different RAC)
- NMO
0 (Network Mode of Operation I)
- CN domain specific DRX cycle length coefficient
7
URA identity
Not present
Downlink counter synchronization info
Not Present
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.5 Uplink TBF establishment with no reallocation of CS resources / Abnormal cases / Assignment Command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.5.1 Conformance requirements
|
If the mobile station receives an ASSIGNMENT COMMAND or HANDOVER COMMAND message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the channel assignment procedure as specified in clause 3.4.3 or the handover procedure as specified in clause 3.4.4. The mobile station shall then attempt an establishment of uplink TBF, using the procedure specified in clause 3.4.22.
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.5.2 Test purpose
|
To verify that the MS aborts the packet access procedure when the MS receives an ASSIGNMENT COMMAND message before the expiry of T3148, completing the channel assignment procedure before re-attempting the establishment of the uplink TBF.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is in packet idle mode, with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer in RLC unacknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS reallocates the MS’s CS resources using the ASSIGNMENT COMMAND. Once the MS changes to the newly allocated timeslot the MS re-requests PS resources with a DTM REQUEST message. Once the PS resources are allocated, the MS enters DTM.
The codec to be used in this test is chosen dependent on the capabilities of the MS.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
MS
MS in state U10, utilising Timeslot N for CS connection (Timeslot chosen arbitrarily)
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
ASSIGNMENT COMMAND
This message is sent such that it is received before timer T3148 expires. CS resources changed to (N + 4) MOD 8. When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
5
MS->SS
ASSIGNMENT COMPLETE
Sent on the correct channel after establishment of the main signalling link.
6
MS->SS
DTM REQUEST
7
SS->MS
PACKET ASSIGNMENT
Includes information on the Radio resources provided to the MS. See specific message contents.
8
MS<->SS
{ Uplink data transfer }
Macro - Completion of the 1000 octets of Data.
Specific Message Contents
PACKET ASSIGNMENT (Step 7):
k=1;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
((N + 4) 1) MOD 8
RR Packet Downlink Assignment IE
Not included
k=2;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N + 4) MOD 8
RR Packet Downlink Assignment IE
Not included
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.6 Uplink TBF establishment with no reallocation of CS resources / Abnormal cases / Handover Command
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.6.1 Conformance requirements
|
If the mobile station receives an ASSIGNMENT COMMAND or HANDOVER COMMAND message during the packet access procedure, the mobile station shall abort the packet access procedure, stop timer T3148 and proceed with the channel assignment procedure as specified in clause 3.4.3 or the handover procedure as specified in clause 3.4.4. The mobile station shall then attempt an establishment of uplink TBF, using the procedure specified in clause 3.4.22.
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1.3.2
41.5.1.1.1.6.2 Test purpose
To verify that the MS aborts the packet access procedure when the MS receives a HANDOVER COMMAND message before the expiry of T3148, completing the handover procedure before re-attempting the establishment of the uplink TBF.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.6.3 Method of test
|
Initial Conditions
System Simulator:
2 Cells, A and B, with same LAI/RAI and both supporting DTM.
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is in packet idle mode with a P-TMSI allocated and PDP context 2 activated
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer in RLC acknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS returns a HANDOVER COMMAND to the MS. The HANDOVER COMMAND instructs the switching of the MS to the newly assigned channel and the establishment of lower layer connections. Once the CS connection is established, the MS returns an HANDOVER COMPLETE message on the new main signalling link. The MS may perform Cell Update by sending the GPRS INFORMATION message containing an empty LLC PDU followed by DTM REQUEST to initiate packet uplink data transfer. If the Cell Update is not performed using GPRS INFORMATION, the MS again sends a DTM REQUEST message to initiate packet uplink data transfer, the SS allocates the MS PS resources and the MS enters DTM.
The codec to be used in this test is chosen dependent on the capabilities of the MS.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in state U10, utilising Timeslot N for CS connection (Timeslot chosen arbitrarily) When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
HANDOVER COMMAND
The message is sent such that it is received before the timer T3148 expires. See specific message contents.
5
MS->SS
HANDOVER ACCESS
Repeated on every burst of the uplink main DCCH (and optionally on the SACCH) until reception of PHYSICAL INFORMATION. Handover Reference as included in the HANDOVER COMMAND.
SS->MS
PHYSICAL INFORMATION
6
MS->SS
HANDOVER COMPLETE
Sent on the correct channel after establishment of the main signalling link.
7
SS->MS
DTM INFORMATION
The MS follows either branch A or B .
A8 (optional step)
MS->SS
GPRS INFORMATION
The MS sends an empty LLC PDU to indicate Cell Update.
A9
MS->SS
DTM REQUEST
A10
SS->MS
PACKET ASSIGNMENT
SS sends this message such that it is received before Timer T3148 expiry. See specific message contents.
A11
MS<->SS
{ Uplink data transfer }
Macro - Completion of the 1000 octets of Data.
B8
MS->SS
DTM REQUEST
Sent on main DCCH.
B9
SS->MS
PACKET ASSIGNMENT
See specific message contents.
B10
SS<->MS
{ Uplink data transfer }
Macro - Completion of the 1000 octets of Data. MS may commence sending of user data immediately after Step B9, or start by sending an empty LLC PDU.
Specific Message Contents
HANDOVER COMMAND (Step 4):
k=1;
As default message contents except:
Channel Description
- Channel Type and TDMA offset
TCH/F
- Timeslot Number
N’
Handover reference
Chosen arbitrarily
k=2;
As default message contents except:
Channel Description
- Channel Type and TDMA offset
TCH/H
- Timeslot Number
N’
Handover reference
Chosen arbitrarily
PACKET ASSIGNMENT (Step A10 and B9):
k=1;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N’ 1) MOD 8
RR Packet Downlink Assignment IE
Not included
k=2;
As default message contents except:
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
N’
RR Packet Downlink Assignment IE
Not included
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.7 Uplink TBF establishment with no reallocation of CS resources / Abnormal cases / Channel Release
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.7.1 Conformance requirements
|
If the MS receives a CHANNEL RELEASE message during the packet access procedure, the MS shall abort the packet access procedure, stop timer T3148 and proceed with the RR connection release procedure. The MS shall then attempt an establishment of the uplink TBF.
References
3GPP TS 04.18/44.018 sub-clauses 3.4.13 & 3.4.22.1.1.3.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.7.2 Test purpose
|
To verify that the MS aborts the packet access procedure when the MS receives a CHANNEL RELEASE message before the expiry of T3148, completing the release before re-attempting the establishment of the uplink TBF.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.1.7.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is in packet idle mode, with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer in RLC acknowledged mode and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS orders the MS to release the CS connection. The MS releases lower layer resources and then requests uplink packet transfer using normal dynamic allocation two phase access.
Maximum Duration of Test
5 minutes
Expected Sequence
Step
Direction
Message
Comments
1
MS
MS in state U10, utilising Timeslot N for CS connection (Timeslot chosen arbitrarily by test house)
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
4
SS->MS
CHANNEL RELEASE
This message is sent such that it is received before expiry of timer T3148.
5
{Uplink dynamic allocation two phase access}
Macro
6
MS<->SS
{ Uplink data transfer }
Macro - Completion of the 1000 octets of Data.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2 Uplink TBF establishment with reallocation of CS resources
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.1 Uplink TBF establishment with reallocation of CS resources / Successful case
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.1.1 Conformance requirements
|
Upon receipt of the DTM ASSIGNMENT COMMAND message, the mobile station initiates a local end release of link layer connections, disconnects the physical channels, commands the switching to the assigned channel and initiates the establishment of lower layer connection (this includes the activation of the channel, their connection and the establishment of the main signalling link).
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1.3.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.1.2 Test purpose
|
To verify that the MS allows reallocation of its CS resources during the request for PS resources. The resources can either be reallocated to a new timeslot within the same frequency or a new frequency.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, DTM supported.
Mobile Station:
The MS is in the active state (U10) of a call.
The MS is in packet idle mode, with a P-TMSI allocated and PDP context 1 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS, whilst in dedicated mode, is triggered to initiate packet uplink data transfer and sends a DTM REQUEST message. On receipt of the DTM REQUEST message, requesting uplink resources, the SS reallocates the MS’s CS resources and assigns PS resources to the MS. The SS accomplishes the resource assignment by passing a DTM ASSIGNMENT COMMAND message to the MS. Once the MS has received the assignment message, it moves to the new allocation, reconnects the CS resources, passes the ASSIGNMENT COMPLETE message to the SS on the main DCCH and starts to send RLC DATA BLOCKS to the SS on the assigned TBF.
The codec to be used in this test is chosen dependent on the capabilities of the MS.
MS supporting DTM shall complete testing for k=1 and MSs indicating support of single slot DTM shall additionally complete testing for k=2.
Maximum Duration of Test
5 minutes
Expected Sequence
The test sequence is repeated for k = 1,2.
Step
Direction
Message
Comments
1
SS
MS in the active state (U10) of a call on Timeslot N. When:
k=1, Channel Type=TCH/F;
k=2, Channel Type=TCH/H.
2
MS
Trigger the MS to initiate an uplink packet transfer containing 1000 octets.
3
MS->SS
DTM REQUEST
Sent on main DCCH
4
SS->MS
DTM ASSIGNMENT COMMAND
This message is sent such that it is received before expiry of timer T3148. See specific message contents.
5
MS->SS
ASSIGNMENT COMPLETE
Sent on new main DCCH.
6
MS->SS
{ Uplink Data Transfer }
Macro - Completion of the 1000 octets of Data.
Specific Message Contents
DTM ASSIGNMENT COMMAND (Step 4):
k=1;
As default message contents except:
Channel Description IE
- Timeslot Number
N’, chosen arbitrarily.
- Channel Type
TCH/F
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
(N’ 1) MOD 8
RR Packet Downlink Assignment IE
Not included
k=2;
As default message contents except:
Channel Description IE
- Timeslot Number
N’, chosen arbitrarily.
- Channel Type
TCH/H
RR Packet Uplink Assignment IE
- TIMESLOT_ALLOCATION
N’
RR Packet Downlink Assignment IE
Not included
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.2 Uplink TBF establishment with reallocation of CS resources / Abnormal case / Assignment Failure
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.2.1 Conformance requirements
|
If the network commands the mobile station to reallocate the RR connection and the establishment of the main DCCH fails, all the allocated packet resources are released; the mobile station shall revert to the old channel, trigger the establishment of the main DCCH and send a DTM ASSIGNMENT FAILURE message on the main DCCH with cause value "lower layer failure".
References
3GPP TS 04.18/44.018 sub-clause 3.4.22.1.1.5
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
41.5.1.1.2.2.2 Test purpose
|
To verify that, if the MS cannot complete the reallocation, then the MS shall revert back to the old resources and re-establish a connection.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.