hash
stringlengths 32
32
| doc_id
stringlengths 5
12
| section
stringlengths 4
595
| content
stringlengths 0
6.67M
|
---|---|---|---|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.1.1 Conformance requirements
|
When Shifted USF operation is used, PACCH operation shall be as described in sub-clause 8.1.1.2.2 except that the network shall transmit all PACCH messages on the PDCH carried on the second lowest numbered timeslot in the allocation, and the mobile station shall attempt to decode every downlink RLC/MAC block on the second lowest numbered timeslot in the PDCH allocation.
References
3GPP TS 44.060, sub-clause 8.1.1.2.4.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.1.2 Test purposes
|
To verify that when the MS is configured for a multi-slot uplink data transfer with shifted USF operation in use, it will decode a PACCH message sent to the MS on the second lowest numbered timeslot in the PDCH assignment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting,
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context 2 activated.
Specific PICS Statements
- The GPRS multislot class supported (TSPC_Type_GPRS_Multislot_ClassX, where X = 1..45)
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer in RLC acknowledged mode, with Extended Dynamic Allocation MAC mode. The SS orders the MS to use two-phase access procedure. The maximum number of UL timeslots is assigned, according to the mobile multislot class (TS 45.002 Annex B.1).
The SS sends to the MS a PACKET DOWNLINK ASSIGNMENT message on the second lowest numbered timeslot in the PDCH assignment, together with a valid RRBP and the TFI assigned to the uplink TBF. It is checked that the MS responds with a PACKET CONTROL ACKNOWLEDGEMENT on the same timeslot.
The SS completes the data transfer.
Maximum Duration of Test
1 minute.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 40 octets, without starting time,
Up to 6 consecutive timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1):
• USF1 on TN1,
• USF2 on TN2, (USF2 USF1)
• up to …
• USFN on TNN, where N = 5 or 6.
2
SS -> MS
PACKET DOWNLINK ASSIGNMENT
Sent on the PACCH of PDCH2, 3 blocks on from the last radio block containing the uplink assignment.
Includes the Polling bit set, and a valid RRBP field.
Includes the TFI assigned to the uplink TBF.
The timeslot assigned is TN2.
The USF is not addressing the MS.
3
MS-SS
PACKET CONTROL ACKNOWLEDGEMENT
Sent on the PACCH of PDCH2, and on the radio block specified by the RRBP.
4
{ Completion of uplink RLC data block transfer in extended dynamic mode }
Using all assigned PDTCHs.
Specific Message Contents
None
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.2 Extended Dynamic Allocation / Shifted USF / Normal / USF assignment on 2nd PDCH
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.2.1 Conformance requirements
|
When Shifted USF operation is used, the USF for the first assigned PDCH shall be sent on the second assigned PDCH. The MS shall monitor the second assigned PDCH for the USF corresponding to both the first assigned PDCH and the second assigned PDCH. If the USF corresponding to the first assigned PDCH is detected then the mobile station shall transmit on the first assigned PDCH and all higher numbered assigned PDCHs. Otherwise, operation shall be as described in sub-clause 8.1.1.2.1.
The USF value corresponding to the first assigned PDCH shall be different from the USF value corresponding to the second assigned PDCH.
References
3GPP TS 44.060, subclauses 8.1.1.2.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.2.2 Test purposes
|
To verify that the MS:
In a multi-slot uplink data transfer with shifted USF operation in use, the USF for the 1st and 2nd assigned PDCH’s are monitored and detected by the MS on the 2nd assigned PDCH, and otherwise operation is as for normal Extended Dynamic Allocation.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting,
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context 2 activated.
Specific PICS Statements
- The GPRS multislot class supported (TSPC_Type_GPRS_Multislot_ClassX, where X = 1..45)
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer in RLC acknowledged mode, and with Extended Dynamic Allocation MAC mode. The SS orders the MS to use two-phase access procedure. The maximum number of UL timeslots is assigned, according to the mobile multislot class (TS 45.002 Annex B.1).
For one block period, the SS allocates blocks on all but the two lowest-numbered assigned PDCHs, by signalling to the MS the USF assigned to the third PDTCH using the third PDCH. It is checked that the MS sends RLC data blocks on all but the two lowest-numbered assigned PDTCHs.
For the next block period, the SS increases the number of PDCHs allocated to the MS, and allocates blocks on all but the lowest PDCH, by signalling to the MS the USF assigned to the second PDTCH using the second PDCH. It is checked that the MS sends RLC data blocks on all but the lowest-numbered assigned PDTCH.
For the next block period, the SS increases the number of PDCHs again, and allocates blocks on all assigned PDCHs, by signalling to the MS the USF assigned to the first PDTCH, but using the second PDCH. It is checked that the MS sends RLC data blocks on all PDTCHs.
The MS completes the packet data transfer.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 1500 octets, without starting time,
Up to 6 consecutive timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1):
• USF1 on TN1,
• USF2 on TN2, (USF2 USF1)
• up to …
• USFN on TNN, where N = 5 or 6.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of PDCH3, 3 blocks on from the last radio block containing the uplink assignment; the assigned USF3 is addressing the MS.
3
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
Sent on the PACCH of PDCH1, PDCH2 and PDCH4 to PDCHN on the same block period as step 2; the USF is not addressing the MS.
4
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH3 to PDTCHN
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of PDCH2; the assigned USF2 is addressing the MS.
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
Sent on the PACCH of PDCH1 and PDCH3 to PDCHN on the same block period as step 5; the USF is not addressing the MS.
7
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH2 to PDTCHN
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of PDCH2; the assigned USF1 is addressing the MS.
9
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
Sent on the PACCH of PDCH1 and PDCH3 to PDCHN on the same block period as step 8; the USF is not addressing the MS.
10
MS -> SS
UPLINK RLC DATA BLOCKS
Received on all assigned PDTCH1 to PDTCHN
11
{ Completion of uplink RLC data block transfer in extended dynamic mode }
Using all assigned PDTCHs.
Specific Message Contents
None
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.3 Extended Dynamic Allocation / Shifted USF / Normal / Release of 2nd PDCH
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.3.1 Conformance requirements
|
1. If a PACKET PDCH RELEASE message releases the second PDCH in the current timeslot configuration of a mobile station using Shifted USF operation then the first timeslot shall be considered released. If any PDCHs remain in the new timeslot configuration then normal USF operation shall continue starting on the lowest available timeslot.
2. If the current timeslot configuration requires Shifted USF operation (see sub-clause 8.1.1.2.4) and the PACKET PDCH RELEASE message modifies the configuration in such a way that Shifted USF operation is no longer required then normal USF operation shall apply after a suitable reaction time as defined in 3GPP TS 45.010.
3. Upon a receipt of a commanding message or indication from the network requiring an action by the mobile station, if the reaction time for such action is not specified elsewhere, the mobile station shall begin to perform the required action no later than the next occurrence of block B((x+6) mod 12), where block B(x) is the radio block containing the commanding message or indication form the network.
References
3GPP TS 44.060, subclause 8.1.1.2.4
3GPP TS 44.060, clause 8.2
3GPP TS 45.010, clause 6.11.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.3.2 Test purposes
|
To verify that when the MS is performing a multi-slot uplink data transfer with shifted USF operation in use, and a PACKET PDCH RELEASE message is received that releases the second PDCH, then the MS will:
- stop transmitting on the first and second PDCH within the required reaction time, and
- continue data transfer using normal USF operation with Extended Dynamic Allocation and using the remaining available timeslots.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.9.3.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting,
Mobile Station:
The MS is GPRS attached with a P-TMSI allocated and the test PDP context 2 activated.
Specific PICS Statements
- The GPRS multislot class supported (TSPC_Type_GPRS_Multislot_ClassX, where X = 1..45)
PIXIT Statements
-
Test Procedure
The MS is triggered to initiate packet uplink transfer in RLC acknowledged mode. The SS orders the MS to use two-phase access procedure. The maximum number of UL timeslots is assigned, according to the mobile multislot class (TS 45.002 Annex B.1).
The SS signals to the MS the USF assigned to the lowest PDTCH on the second PDCH, and, in the next block period, it is checked that the MS sends RLC/MAC data blocks on all assigned PDTCH.
The SS sends a PACKET PDCH RELEASE message with TIMESLOTS_AVAILABLE indicating that the second lowest assigned PDCH timeslots is not available for packet data. For that block period, and the next five block periods, the SS continues signals to the MS the USF assigned to the lowest PDTCH on the second PDCH, and also the USF assigned to the third PDTCH on the corresponding PACCH.
On the sixth block period following the PACKET PDCH RELEASE message, it is checked that the MS has stopped transmitting on the two lowest timeslots, but continues to transmit on the remaining timeslots.
The SS completes the data transfer using the remaining timeslots.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Uplink dynamic allocation two phase access}
n = 2000 octets, without starting time,
Up to 6 consecutive timeslots are assigned according to MS multislot class (TS 45.002 Annex B.1):
• USF1 on TN1,
• USF2 on TN2, (USF2 USF1)
• up to …
• USFN on TNN, where N = 5 or 6.
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
Sent on the PACCH of PDCH1 to PDCHN, 3 blocks on from the last radio block containing the uplink assignment; the USF values are:
PACCH1 - USF is not addressing the MS.
PACCH2 - assigned USF1 is addressing the MS.
PACCH3 - USF is not addressing the MS.
up to …
PACCHN - USF is not addressing the MS.
3
MS -> SS
UPLINK RLC DATA BLOCKS
Received on all assigned PDTCH1 to PDTCHN
4
SS -> MS
PACKET PDCH RELEASE
Sent on the PACCH of PDCH2 on the same block period as step 3; the assigned USF1 is addressing the MS.
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCKS
Sent on the PACCH of PDCH1 and PDCH3 to PDCHN, on the same block period as step 3; the USF values are:
PACCH1 - USF is not addressing the MS.
PACCH3 - assigned USF3 is addressing the MS.
PACCH4 - USF is not addressing the MS.
up to …
PACCHN - USF is not addressing the MS.
6
MS -> SS
UPLINK RLC DATA BLOCKS
RLC data blocks may optionally be received on PDTCH1 and PDTCH2. RLC data blocks are mandatorily received on assigned PDTCH3 to PDTCHN
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of PDCH1 to PDCHN, on the same block period as step 6; the USF values are:
PACCH1 - USF is not addressing the MS.
PACCH2 - assigned USF1 is addressing the MS.
PACCH3 - assigned USF3 is addressing the MS.
PACCH4 - USF is not addressing the MS.
up to
PACCHN - USF is not addressing the MS.
8
SS,MS
Steps 6 and 7 are repeated four times more.
9
MS -> SS
UPLINK RLC DATA BLOCKS
RLC data blocks are received on assigned PDTCH3 to PDTCHN only.
No RLC data blocks are received on PDTCH1 and PDTCH2.
10
{ Completion of uplink RLC data block transfer in extended dynamic mode }
Using PDTCH3 to PDTCHN
Specific Message Contents
PACKET PDCH RELEASE (Step 4):
- PAGE MODE
Indicating “Same as before”
- TIMESLOTS_AVAILABLE
Indicating that TN1 and TN3 to TNN are available for GPRS. TN2 is not available.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10 EC-GSM-IoT
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1 EC-GSM-IoT / Packet Uplink Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.1 EC-GSM-IoT / Packet Uplink Assignment /Successful / CCCH
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.1.1 Conformance requirements
|
The establishment of an EC Temporary Block Flow (EC TBF), for a mobile station that has enabled EC operation, is performed on the EC-CCCH. It can be initiated by either the mobile station or the network. The establishment of an EC TBF can also be performed on the CCCH if the mobile station has selected Coverage Class 1 in both the uplink and downlink directions, see 3GPP TS 45.008 and 3GPP TS 44.018.
...
When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation.
...
This message may be sent by an EC capable mobile station attempting system access using the EC-RACH (see sub-clause 3.5.2.1.2a) in which the message format is as shown in Tables 9.1.65.1 and 9.1.65.2. This message can also be sent using the RACH (see sub-clause 3.5.2.1.2) in which the message format is as shown in Tables 9.1.65.3 and 9.1.65.4.
...
In case overlaid CDMA is used, see 3GPP TS 43.064 [6], up to four MS can be multiplexed on the same physical resource, simultaneously transmitting, using different orthogonal codes assigned by the network, see 3GPP TS 44.060 [11]. The codes are applied per burst over the assigned PDCHs for EC-PDTCH and EC-PACCH in each TDMA frame from the lowest to the highest numbered assigned TN, according to Table 6.3-2, and are only applied in case blind physical layer transmissions are used (i.e. for CC2, CC3 and CC4).
...
When EC operation is enabled the packet uplink resource is assigned to the mobile station in an EC IMMEDIATE ASSIGNMENT TYPE 1 message sent in unacknowledged mode on the same CCCH timeslot on which the network received the EC PACKET CHANNEL REQUEST message (see Table 3.5.2.1.2.3). Timer T3141 is started on the network side.
...
References
3GPP TS 44.060, subclauses 7a.1, 8.1.1.3b
3GPP TS 44.018, subclauses 3.5.1a, 3.5.1a.1, 3.5.2.1.3.1, 9.1.65
3GPP TS 45.002 subclause 6.3.2.2.6
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.1.2 Test purpose
|
1. The MS is triggered to initiate packet uplink transfer data in EC operation with FUA
2. Overlaid CDMA
3. Verify CCCH is used instead of EC-CCCH
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.1.3 Method of test
|
Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT. The MS is GPRS attached. RACH Access Control =1 in EC-SCH
Mobile Station:
- The MS is switched off.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
To verify that the MS:
1. Sends the EC-RACH on RACH channel due to RACH access control configured to 1
2. MS sends Overlaid CDMA using CC2 and code 1
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to send uplink data
2
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on RACH
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 1
Overlaid CDMA configured to be used Code 1
UL CC2 to be used
Fixed uplink assignment, sent on AGCH.
3 RLC Blocks to be sent
4
MS -> SS
UPLINK RLC DATA BLOCKS
Verify MS sends Overlaid Code 1
5
MS -> SS
UPLINK RLC DATA BLOCKS
Verify MS sends Overlaid Code 1
6
MS -> SS
UPLINK RLC DATA BLOCKS
Verify MS sends Overlaid Code 1
7
The messages in steps 4-6 are mapped according to UL CC2
8
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. UL CC1 to be used.
Sent on EC-PACCH.
9
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
acknowledge the RLC data. Received on EC-PACCH
Specific Message Contents
Step 2: EC IMMEDIATE ASSIGNMENT TYPE 1
TBD
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.2 EC-GSM-IoT / Packet Uplink Assignment /Successful / During Downlink ongoing
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.2.1 Conformance requirements
|
When the mobile station receives a Fixed Uplink Allocation, FUA, in e.g. the EC PACKET UPLINK ASSIGNMENT or EC PACKET UPLINK ACK/NACK message it shall perform uplink transmissions according to that allocation. The uplink resources are allocated with respect to a BTTI configuration, the mobile station uplink coverage class, the assigned MCS, the number of RLC data blocks required for the EC TBF as indicated by the mobile station and with respect to the latest ack/nack status as perceived by the network, if such exists, and transmitted to the mobile station in the message containing the FUA. The uplink resources will be allocated according to the coverage class dependent resource mapping (see 3GPP TS 45.002) and the mobile station shall transmit accordingly.
...
When the mobile station has an ongoing downlink EC TBF, it may initiate an uplink EC TBF by including the EC Channel Request Description information element in the EC PACKET DOWNLINK ACK/NACK message on the EC-PACCH and start timer T3168. The network may then establish an uplink EC TBF by sending an EC PACKET UPLINK ASSIGNMENT message to the mobile station, in which case the downlink EC TBF is released.
...
In EC operation, the downlink EC TBF is released at establishment of the uplink EC TBF.
...
In case overlaid CDMA is used, see 3GPP TS 43.064 [6], up to four MS can be multiplexed on the same physical resource, simultaneously transmitting, using different orthogonal codes assigned by the network, see 3GPP TS 44.060 [11]. The codes are applied per burst over the assigned PDCHs for EC-PDTCH and EC-PACCH in each TDMA frame from the lowest to the highest numbered assigned TN, according to Table 6.3-2, and are only applied in case blind physical layer transmissions are used (i.e. for CC2, CC3 and CC4).
...--
References
3GPP TS 44.060, subclauses 8.1.1.3b ,8.1.2.5
3GPP TS 45.002 subclause 6.3.2.2.6
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.2.2 Test purpose
|
1. The MS is triggered to initiate packet uplink transfer data in EC operation with FUA during an ongoing downlink TBF
2. Overlaid CDMA
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT. CC2 used.
Mobile Station:
The MS is GPRS attached.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
To verify that the MS:
1. Uplink is established during an ongoing downlink
2. Verify DL TBF terminates immediately after the UL TBF is requested
3. Overlaid CDMA used with code 1 during CC2
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1a
SS -> MS
EC IMMEDIATE ASSIGNMENT
For downlink TBF, Sent on EC-PCH.
1b
SS -> MS
EC PACKET DOWNLINK ASSIGNMENT
Triggers the MS to switch to the assigned PDCH. (no starting time)
With valid RRBP field
2
MS->SS
EC PACKET CONTROL ACK
4 access bursts. Sent in the block specified by RRBP field in step 1.
3
SS -> MS
RLC DATA BLOCK
2 blocks after the previous message, with valid RRBP field, on assigned PDCH, addressed to MS.
4
MS -> SS
EC PACKET DOWNLINK ACK/NACK
MS acknowledges on PACCH the RLC data block sent in step 3.
5
SS -> MS
X * RLC DATA BLOCK
Repeat sending data blocks and PDAN’s until step 7 occurs
6
MS -> SS
X * EC PACKET DOWNLINK ACK/NACK
Repeat sending data blocks and PDAN’s until step 7 occurs
7
MS
Trigger MS to send data
8
MS -> SS
EC PACKET DOWNLINK ACK/NACK
PDAN including a request for a Fixed Uplink Allocation
9
SS -> MS
EC PACKET UPLINK ASSIGNMENT
PUA including a Fixed Uplink Allocation
Overlaid CDMA configured to be used Code 1
UL CC2 to be used
3 RLC Blocks to be sent
10
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH.
Verify MS sends Overlaid Code 1
11
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH.
Verify MS sends Overlaid Code 1
12
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH.
Verify MS sends Overlaid Code 1
13
The messages in steps 10-12 are mapped according to UL CC2
14
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. UL CC1 to be used
Sent on EC-PACCH.
15
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
acknowledge the RLC data. Received on EC-PACCH.
Specific Message Contents
Step 9: EC PACKET UPLINK ASSIGNMENT
TBD
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.3 EC-GSM-IoT / Packet Uplink Assignment /Resource Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.3.1 Conformance requirements
|
STARTING_DL_TIMESLOT_OFFSET (2 bit field)
This field defines the timeslot number of the lowest timeslot included in the assignment that is used for transfer of downlink RLC/MAC control messages on the EC-PACCH during the UL EC TBF. The number of additional timeslots that are included in the downlink assignment depends on the assigned DL Coverage Class. The assigned timeslots are contiguous, starting with the timeslot number indicated in the STARTING_DL_TIMESLOT_OFFSET field. The STARTING_DL_TIMESLOT_OFFSET field is encoded as an offset to the timeslot assigned with the STARTING_UL_TIMESLOT field. The encoding of the field is dependent of the value of the UL_COVERAGE_CLASS and DL_COVERAGE_CLASS fields in the same message.
…
References
3GPP TS 44.018, table 9.1.60.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.3.2 Test purpose
|
To verify that the parameter STARTING_DL_TIMESLOT_OFFSET is properly used when uplink and downlink coverage classes are different and at least one of them is CC1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT
Mobile Station:
The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS triggers and uplink data transfer. A downlink data transfer is requested by the network and different type of coverage class combination and values of STARTING_DL_TIMESLOT_OFFSET are tested.
The EC PACKET UPLINK ACK/NACK requested a Packet control acknowledgement is sent according to the STARTING_DL_TIMESLOT_OFFSET. For DL CC2 where 4 slots are used for the transmission of this message, the last 3 blocks are corrupted.
The procedure is repeated different combination of coverage classes (k= 1 to 2).
Maximum duration of the test
5 min
Expected sequence
The test sequence is repeated for k = 1 … 2.
Step
Direction
Message
Comments
1
The NW is configured as follow:
k=1, Uplink CC1, DL CC2
k=2, Uplink CC2, DL CC1
2
TMS is triggered to send 50 Octets of data.
3
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on EC-RACH
X blocks requested
UL and DL CC1
4
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Fixed uplink assignment, sent on EC-AGCH
See specific message content
5
MS -> SS
UPLINK RLC DATA BLOCKS
6
MS
Step 4 is repeated X-1 times.
Branch A is done for k=1 (DL CC2)
Branch B is done for k=2 (DL CC1)
7- A
SS -> MS
EC PACKET UPLINK ACK/NACK
k=1
Acknowledge all the UL RLC data. Received on EC-PACCH on DL timeslot defined in step 4. Corrupted data sent of the next 3 DL TS allocated
EC Packet Control Ack requested with a valid RRBP.
7-B
SS -> MS
EC PACKET UPLINK ACK/NACK
k=2
Sent on EC-PACCH on TimeSlot = STARTING_UL_TIMESLOT.
No UL RLC Data block acknowledged
The MS shall not see this message.
7bis-B
SS -> MS
EC PACKET UPLINK ACK/NACK
Acknowledge all the UL RLC data. Received on EC-PACCH on DL timeslot defined in step 4.
EC Packet Control Ack requested with a valid RRBP.
8
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
Sent according to UL CC1
Specific Message Contents
EC IMMEDIATE ASSIGNMENT TYPE 2 message in step 4:
UL_COVERAGE_CLASS
00 UL CC1 for k=1
01 UL CC2 for k=2
DL_COVERAGE_CLASS
01 DL CC2 for k=1
00 DL CC1 for k=2
EC Fixed Uplink Allocation
STARTING_UL_TIMESLOT
Uplink_TFI_Assignment
STARTING_DL_TIMESLOT_OFFSET
011 Timeslot 3
00001
01 STARTING_UL_TIMESLOT - 1 for k=1
01 STARTING_UL_TIMESLOT + 1 for k=2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.4 EC-GSM-IoT / Packet Uplink Assignment /Resource Assignment / Gap
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.4.1 Conformance requirements
|
The mobile station in EC TBF mode may include an EC Channel Request Description in the EC PACKET DOWNLINK ACK/NACK message in order to request an uplink TBF. The network may then establish an uplink EC TBF for the mobile station by sending an EC PACKET UPLINK ASSIGNMENT message, in which case the downlink EC TBF is released.
…
TIMESLOT_MULTIPLICATOR (3 bit field)
This field defines how many UL timeslots that the assignment contains when the assigned UL Coverage Class, according to the UL_COVERAGE_CLASS field, is CC1.
…
Values other than ‘000’ can only be used if supported by the mobile station, as indicated by its multislot capability, see 3GPP TS 45.002. If the assigned uplink Coverage Class > CC1 (according to the UL_COVERAGE_CLASS field), the mobile station shall consider the TIMESLOT_MULTIPLICATOR field as not valid
START_FIRST_UL_RLC_DATA_BLOCK (4 bit field)
This field indicates the starting position of the resources for the first allocated RLC Data block in the fixed uplink allocation. The starting position is relative to the first TDMA frame (N) of the downlink block containing the last blind physical layer transmission of this EC PACKET UPLINK ASSIGNMENT message, according to the USED_DL_COVERAGE_CLASS field. The encoding of the field is dependent of the value of the UL_COVERAGE_CLASS and the TIMESLOT_MULTIPLICATOR fields in the same message.
…
DELAY_NEXT_UL_RLC_DATA_BLOCK (3 bit field)
This field indicates the position of the next allocated RLC Data block in the fixed uplink allocation. The position is calculated as the number of transmission opportunities from the previous uplink allocation, according to the UL_COVERAGE_CLASS and TIMESLOT_MULTIPLICATOR fields in the same assignment message, where the next uplink allocation for the mobile station is placed and where the mobile station thus shall transmit the next RLC data block. In the transmission opportunity/ies between the previous uplink allocation and this allocation the mobile station is not allocated any resource, and shall thus not transmit.
References
3GPP TS 44.060, subclauses 9.3.2.6 and table 11.2.58.2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.4.2 Test purpose
|
To verify that the Timeslot allocation and position in the TDMA Frame used to transmit the UL RLC data block are done according the defined parameters in the EC PACKET UPLINK ASSIGNMENT
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.4.3 Method of test
|
Initial Conditions
System Simulator:
- 1 cell, EC-GSM-IoT.
Mobile Station:
- The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
An uplink transfer is triggered during an EC DL TBF.
The SS sends an EC PACKET UPLINK ASSIGNMENT to handle the MS requests
The procedure is repeated different combination of parameters (k= 1 to 3).
Maximum duration of the test:
5 min
Expected sequence
The test sequence is repeated for k = 1 … 3.
Step
Direction
Message
Comments
1
SS -> MS
EC IMMEDIATE ASSIGNMENT
For downlink TBF, Sent on EC-PCH.
2
SS -> MS
EC PACKET DOWNLINK ASSIGNMENT
Triggers the MS to switch to the assigned EC-PDCH. Valid RRBP field
3
MS->SS
EC PACKET CONTROL ACK
4 access bursts. Sent in the block specified by RRBP field in step 2
4
SS -> MS
RLC DATA BLOCK
2 blocks after the previous message, with valid RRBP field, on assigned EC-PDCH, addressed to MS
5
MS -> SS
EC PACKET DOWNLINK ACK/NACK
MS acknowledges on EC-PACCH the RLC data block sent in step 4.
6
MS
The MS is triggered to send 50 Octets of Data
7
Steps 4 and 5 are repeated until an UL transfer Request is done in the EC PACKET DOWNLINK ACK/NACK
8
SS -> MS
EC PACKET UPLINK ASSIGNMENT
See specific message content for k=1,2 or 3
9
MS -> SS
UPLINK RLC DATA BLOCKS
Send on the EC-PDTCH defined in step 8 (according to UL_COVERAGE_CLASS , TIMESLOT_MULTIPLICATOR and START_FN_FIRST_UL_RLC_DATA_BLOCK)
10
MS -> SS
UPLINK RLC DATA BLOCKS
Sent on the EC-PDTCH defined in step 8 (according to DELAY_NEXT_UL_RLC_DATA_BLOCK)
Step 10 is repeated until the last block is transmitted
13
SS -> MS
EC PACKET UPLINK ACK/NACK
Acknowledges the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH
14
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
Specific Message Contents
EC IMMEDIATE ASSIGNMENT TYPE 2 message in step 4:
UL_COVERAGE_CLASS
TIMESLOT_MULTIPLICATOR
START_FN_FIRST_UL_RLC_DATA_BLOCK
DELAY_NEXT_UL_RLC_DATA_BLOCK
00 (CC1) for k=1 and k=2
10 (CC3) for k=3
0 0 0 1 timeslot assigned for k=1
0 1 0 3 timeslots assigned for k=2
1 1 0 7 timeslots assigned for k=3
1 1 0 0 for k=1
0 0 1 0 for k=2
0 1 0 1 for k=3
0 0 0 In the 2nd next transmission opportunity for k=1 and k=3
0 0 1 In the 3rd next transmission opportunity for k=2
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.5 EC-GSM-IoT / Packet Uplink Assignment /Downlink Coverage Class Adaptation/ T3248
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.5.1 Conformance requirements
|
When timer T3226 expires, the mobile station shall monitor the EC-PACCH according to its assigned downlink coverage class and, as long as T3228 is running, attempt to decode every downlink RLC/MAC block on the PDCHs corresponding to the downlink assigned EC-PACCH resources.
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.
If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires.
The assigned resources (timeslots) to be used for the downlink EC-PACCH according to the next higher DL Coverage Class are either the same as the assigned timeslots for the uplink EC-PDTCH or given in the assignment message. If no valid resources for the next higher Coverage Class are assigned, the mobile station shall continue to monitor the downlink EC-PACCH using the assigned DL Coverage Class while timer T3248 is running.
When the mobile station receives an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message addressing the mobile station with the TFI value associated with its uplink TBF it shall stop T3228, if running. If timer T3248 was running at reception of the EC PACKET UPLINK ACK/NACK message or the EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message (and thus not T3228), the timer T3248 shall be stopped.
References
3GPP TS 44.060, subclauses 8.1.1.3b.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.5.2 Test purpose
|
To verify that in EC operation, if T3248 is used and running, the MS will monitor the DL EC_PACCH using the next higher DL coverage Class (if any).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT. T3248 set to 3 secs
Mobile Station:
The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is set to trigger an UL data transfer.
Following the last radio block transmitted according to the fixed uplink allocation, the MS should then T3226 then T3228 and start to monitor the EC-PACCH according to its DL CC.
The SS does not send the corresponding EC PACKET UPLINK ACK/NACK.
At the expiry of T3228, the MS should start T3248 and monitor the EC-PACCH with DL CC2 configuration.
The SS then sends the expected EC PACKET UPLINK ACK/NACK.
The UL transfer is then complete and no retransmission is expected.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
The MS is triggered to send 50 Octets of data
2
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on EC-RACH
UL and DL CC1 should be requested.
X blocks requested
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Fixed uplink assignment, sent on EC-AGCH according to DL CC1
MCS1
STARTING_DL_TIMESLOT_OFFSET same as STARTING_UL_TIMESLOT
4
MS -> SS
UPLINK RLC DATA BLOCKS
5
MS
Step 4 is repeated X-1 times.
6
Wait for T3226 + T3228 + 1 sec
7
SS -> MS
EC PACKET UPLINK ACK/NACK
Acknowledge all the UL RLC data. Received on EC-PACCH during T3248. Mapped according to DL CC2 (see TS 45.002) on 4 slots.
EC Packet Control Ack requested with a valid RRBP.
8
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
Sent according to UL CC1
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.6 EC-GSM-IoT / Packet Uplink Assignment /Downlink Coverage Class Adaptation/ T3248 or T3228 Expiry
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.6.1 Conformance requirements
|
If timer T3228 expires, the mobile station shall release the ongoing uplink TBF and may perform an abnormal release with access retry, unless timer T3248 (sent in EC-SI) is used. If T3248 is used, i.e. it has a value > 0, the mobile station shall instead start timer T3248 and continue to monitor the DL EC-PACCH using the next higher DL Coverage Class, if such exists. If no higher DL CC than the assigned DL CC exists, the mobile station shall continue to monitor the DL EC-PACCH for reception of an EC PACKET UPLINK ACK/NACK message or an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message according to the last assigned DL CC until T3248 expires.
…
At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.
References
3GPP TS 44.060, subclauses 8.1.1.3b.1
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.6.2 Test purpose
|
To verify that in EC operation, if T3248 is used and running, the MS will monitor the DL EC_PACCH using the next higher DL coverage Class (if any).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.1.6.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT. T3248 set to 3 secs
Mobile Station:
The MS is GPRS attached. In EC Operation mode in CC1 (UL and DL)
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is set to trigger an UL data transfer.
Following the last radio block transmitted according to the fixed uplink allocation, the MS should then T3226 then T3228 and start to monitor the EC-PACCH according to its DL CC.
The SS does not send the corresponding EC PACKET UPLINK ACK/NACK.
At the expiry of T3228, the MS should start T3248 and monitor the EC-PACCH with DL CC2 configuration.
The SS then sends an EC PACKET UPLINK ACK/NACK not addressing the MS (i.e. wrong Uplink_TFI) during T3248. The Ms should not consider the acknowledgment.
The SS checks that no acknowledgement is sent by the MS.
At expiry of T3248, the mobile station shall release the ongoing uplink TBF. Abnormal release with access retry may be performed.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
The MS is triggered to send 50 Octets of data
2
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on EC-RACH
UL and DL CC1 should be requested.
X blocks requested
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Fixed uplink assignment, sent on EC-AGCH according to DL CC1
MCS1
STARTING_DL_TIMESLOT_OFFSET same as STARTING_UL_TIMESLOT
4
MS -> SS
UPLINK RLC DATA BLOCKS
5
MS
Step 4 is repeated X-1 times.
6
Wait for T3226 + T3228 + 1 sec
7
SS -> MS
EC PACKET UPLINK ACK/NACK
Received on EC-PACCH during T3248. Mapped according to DL CC2 (see TS 45.002) on 4 slots but not using the MS Uplink TFI (i.e. not addressing the MS).
A valid RRBP is indicated
8
SS
SS checks that no EC PACKET CONTROL ACK is received.
This is checked for 3 seconds.
9
SS
SS check that a new EC PACKET CHANNEL REQUEST might be sent as per T3248 expiry, the MS should abort the ongoing TBF and may trigger an abnormal release with access retry.
Specific Message Contents
-
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.2 EC-GSM-IoT / Packet Downlink Assignment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.2.1 EC-GSM-IoT / Packet Downlink Assignment / Successful / T3238
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.2.1.1 Conformance requirements
|
The purpose of network initiated TBF establishment is to establish a TBF to support the transfer of upper layer PDUs in the direction from the network to the mobile station. The procedure is triggered by a request from upper layers on the network side to transfer an upper layer PDU to a mobile station in packet idle mode that has enabled EC operation. Upon such a request, the network shall initiate a packet downlink assignment procedure on the EC-CCCH as described in 3GPP TS 44.018.
...
For a TBF in BTTI configuration, prior to the initiation of RLC data block transfer on the downlink, the network assigns the following parameters in a downlink assignment.
in case of a downlink EC TBF, the network also assigns the following parameters:
- uplink and downlink coverage classes;
- a set of PDCHs to be used for transmission of uplink RLC/MAC control messages.
...
If the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1’, has been indicated to continue monitoring the EC-PACCH, it shall start timer T3238. The mobile station shall then monitor the EC-PACCH, according to its assigned downlink Coverage Class of the TBF, after an initial waiting time as indicated in the EC PACKET UPLINK ACK/NACK message. The mobile station shall then monitor the EC-PACCH, using a monitoring pattern as indicated in the EC PACKET UPLINK ACK/NACK message, until timer T3238 expires or until a downlink RLC/MAC control message triggering the release of the TBF is received. When timer T3238 expires, the mobile station shall leave the TBF and return to packet idle mode.
...
If the mobile station receives an EC PACKET DOWNLINK ASSIGNMENT message addressing the mobile station while listening to the EC-PACCH, it shall stop timer T3238, release the uplink TBF and act on the assigned resources.
...
An uplink EC TBF is released when the network has received all RLC data blocks for a TBF, as indicated by the mobile station, and sent the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1'. An exception is when the mobile station, in the EC PACKET UPLINK ACK/NACK message with the Final Ack Indicator bit set to '1', is ordered to continue monitoring the EC-PACCH, see sub-clause 9.3.2.4.3
...
References
3GPP TS 44.060, subclauses 7a.3,8.1.2, 8.1.2.5, 9.3.2.4.3, 9.3.1.4
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.2.1.2 Test purpose
|
To verify that the MS:
1. Start a Uplink TBF
2. Send FAI for the Uplink with a value of the T3238
3. Establish a downlink TBF before expire of T3238
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.2.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, EC-GSM-IoT.
Mobile Station:
The MS is GPRS attached.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS triggers an UL data transfer in EC Operation mode. The SS acknowledges all the UL data blocks and activate T3238.
The MS shall monitor the DL EC-PACCH for a Downlink transfer when T3228 is used.
The SS then sends an EC DOWNLINK ASSIGNMENT before T3238 expiry.
The MS shall proceed with the DL transfer
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
MS -> SS
EC PACKET CHANNEL REQUEST
Verify received on RACH
2
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 1
Fixed uplink assignment, sent on EC-AGCH.
5 RLC Blocks to be sent
3
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH
4
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH
5
MS -> SS
UPLINK RLC DATA BLOCKS
Received on the assigned PDTCH
6
SS -> MS
EC PACKET UPLINK ACK/NACK
acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH.
T3238 set to 96s
7
SS
Wait 20s
12
SS -> MS
EC PACKET DOWNLINK ASSIGNMENT
Triggers the MS to switch to the assigned PDCH. (no starting time)
With valid RRBP field
Started before T3238 expired
Meaning verify EC-PACCH channel still monitored by MS as T3238 not expired
13
MS->SS
EC PACKET CONTROL ACK
4 access bursts. Sent in the block specified by RRBP field in step 1.
14
SS -> MS
RLC DATA BLOCK
2 blocks after the previous message, with valid RRBP field, on assigned PDCH, addressed to MS.
15
MS -> SS
EC PACKET DOWNLINK ACK/NACK
MS acknowledges on PACCH the RLC data block sent in step 3.
MS<->SS
Completion of macro {Downlink data transfer}
SS completes downlink transfer of 200 octets of data.
Specific Message Contents
Step 12: EC PACKET DOWNLINK ASSIGNMENT
TBD
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.3.1 EC-GSM-IoT / Contention resolution / Enhanced Access Burst procedure
|
The contention resolution is completed on the mobile station side when the mobile station receives a PACKET UPLINK ASSIGNMENT message with the same TLLI as the mobile station has included in the PACKET RESOURCE REQUEST message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.3.1.1 Conformance requirements
|
The TLLI is used to uniquely identify the mobile station when sending on the uplink. A mobile station, that has enabled EC operation, includes its TLLI in one or several of the uplink blocks that are transmitted during the establishment of an EC TBF, depending on what packet access procedure is used.
The contention resolution is described for the different packet access procedures in the following sub-clauses:
- using Access Burst procedure, with inclusion of the full TLLI in each RLC data block that is sent on the TBF until contention resolution is completed, described in 7a.2.1.1;
- using Enhanced Access Burst procedure, with inclusion of the full TLLI in only the first RLC data block that is sent on the TBF and then inclusion of a limited part of the TLLI in the subsequent RLC data blocks that are sent until contention resolution is completed, described in 7a.2.1.2.
The network indicates in the EC Immediate Assignment message which of the procedures that shall be used for the contention resolution, see 3GPP TS 44.018.
…
When the Enhanced Access Burst procedure is used, only the first RLC data block that is sent on the TBF shall include the TLLI of the mobile station. If MCS-7, MCS-8 or MCS-9 is used for the transmission of the TLLI (i.e. the RLC/MAC block is carrying two RLC data blocks), the TLLI shall be inserted in both RLC data blocks that are included in the first RLC/MAC block. Every RLC data block that is sent on the TBF, except the first one, shall include the reduced TLLI (rTLLI) of the mobile station until the mobile station receives an EC PACKET UPLINK ACK/NACK AND CONTENTION RESOLUTION message or an EC PACKET UPLINK ACK/NACK message addressing the mobile station with the TFI value associated with the uplink TBF and containing either the TLLI or the rTLLI of the mobile station. The reduced TLLI (rTLLI) consists of the 4 least significant bits of the TLLI of the mobile station. The rTLLI shall not be included in the RLC/MAC header if the TLLI is included in the RLC Data block. The rTLLI value shall thus not be included in the RLC/MAC header of the first RLC Data block of a TBF, with BSN=0 and, if MCS-7, MCS-8 or MCS-9 is used for the transmission, with BSN=1, since the TLLI of the mobile station is included in the RLC data block(s).
If the failure is due to a TLLI mismatch, or to the expiry of timers T3166 or T3168, or to the fact that the counter N3104 reached its maximum value in the contention resolution procedure, and repetition as described in subclause 7.1.3.3 has been performed, the mobile station shall remain in packet idle mode, notify higher layer (TBF establishment failure), transactions in progress shall be aborted and cell reselection continued.
Reference
3GPP TS 44.060 subclauses 7a.2.1, 7a.2.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.3.1.2 Test purpose
|
To verify that the MS uses the Enhanced Access Burst procedure when indicated by the network.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
42.10.3.1.3 Method of test
|
Initial conditions
System Simulator:
1 cell, EC-GSM-IoT supported
Mobile Station:
The MS is GPRS attached and in packet idle mode. PDP context 1 has been established.
Specific PICS Statements
-
PIXIT Statements
-
Test procedure
The MS is triggered to initiate uplink data transfer. The SS responds with EC IMMEDIATE ASSIGNMENT TYPE 2 message that request fixed link assignment, sent on EC-AGCH, with Enhanced Access Burst value set to 1..
The MS shall then send the first RLC data block including the TLLI. The SS responds with EC PACKET UPLINK ACK/NACK with the same TLLI.
The MS then sends two additional RLC data blocks with a reduced TLLI. The SS then acknowledge the received data blocks with the EC PACKET UPLINK ACK/NACK message. The MS acknowledge with the EC PACKET CONTROL ACKNOWLEDGEMENT message.
Maximum duration of the test
2 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is triggered to initiate packet uplink transfer of three RLC data blocks.
2
MS -> SS
EC PACKET CHANNEL REQUEST
Received on EC-RACH.
3
SS -> MS
EC IMMEDIATE ASSIGNMENT TYPE 2
Request Reference = pertaining to the message received in step 2. Fixed link assignment, sent on EC-AGCH
Enhanced Access Burst value: 1 (The Enhanced Access Burst procedure shall be used)
4
MS -> SS
UPLINK RLC DATA BLOCK
MS sends the 1st RLC data block including its TLLI
5
SS -> MS
EC PACKET UPLINK ACK/NACK
The SS transmits the MS TLLI in order to solve the contention and indicates that the 1st RLC data block has been received.
6
MS -> SS
UPLINK RLC DATA BLOCK
MS sends the 2nd RLC data block including its reduced TLLI (rTLLI) that is set to the 4 least significant bits of the TLLI of the mobile station
7
MS -> SS
UPLINK RLC DATA BLOCK
MS sends the 3rd RLC data block including its reduced TLLI (rTLLI) that is set to the 4 least significant bits of the TLLI of the mobile station
8
SS -> MS
EC PACKET UPLINK ACK/NACK
Acknowledge the received RLC data block, Final Ack Indicator = ‘1’ , a valid RRBP. Sent on EC-PACCH
9
MS -> SS
EC PACKET CONTROL ACKNOWLEDGEMENT
MS acknowledge the RLC data. Received on EC-PACCH
Specific message contents
None.
43 RLC Test Cases
Default conditions and messages
The default conditions, message contents and macros not specified in this subclause must be set as in clause 40.
Initial conditions
Unless otherwise indicated, the initial conditions for all acknowledged mode tests, as a minimum, are as follows. Other initial conditions may apply. In the event of conflict between initial conditions stated here and those stated in a test case, the test case shall take precedence.
- The MS is GPRS attached.
- A PDP context has been established with RLC acknowledged mode operation.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1 Acknowledged Mode
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1 Acknowledged mode / Uplink TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.1 Acknowledged mode / Uplink TBF / Send state variable V(S)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.1.1 Conformance requirements
|
1. The send state variable, V(S), can take on the values 0 through 127. Each RLC data block contains a block sequence number (BSN) field that is 7 bits in length. At the time that an in-sequence RLC data block is designated for transmission, the value of BSN is set equal to the value of the send state variable.
2. V(S) shall be set to the value 0 at the beginning of each TBF in which the RLC endpoint is the transmitter.
3. The value of V(S) shall be incremented by 1 after transmission of the RLC data block with BSN = V(S).
References
3GPP TS 04.60, subclause 9.1.1.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.1.2 Test purpose
|
1. To verify that the mobile station sets the V(S) to 0 at the beginning of each TBF.
2. To verify that the mobile station increases the V(S) by 1 after transmission of the RLC data block with BSN set to V(S).
3. To verify that the mobile station wraps the V(S) to 0 after 127.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is made to send RLC data blocks. SS checks that the BSN in the RLC data block:
1. is set to the value 0 at the beginning of each TBF in which the mobile station is the transmitter;
2. is incremented by 1 in each subsequent RLC data block in the TBF; and
3. takes on all values in the range 0 to 127 and then back to 0.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 3500 octets,
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, containing USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the BSN starts from 0.
4
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges each RLC data block, RBB set to 1, containing USF assigned to the MS
5
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the BSN is updated according to BSN(n) = (BSN(n-1) + 1 ) mod 128
6
-
Steps 4 & 5 are repeated at least 128 times
The PACCH of the PDCH assigned in step 2, containing USF assigned to the MS.
7
{ Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.2 Acknowledged mode / Uplink TBF / Transmit window size
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.2.1 Conformance requirements
|
1. V(S) shall not exceed V(A) modulo 128 by more than the maximum allowed number of outstanding RLC data blocks k (window size k is defined in 3GPP TS 04.60 subclause 9.1.9).
2. If V(S) = V(A) + k modulo 128 (i.e., the transmit window is stalled), the mobile station shall set the stall indicator to 1 in each RLC data block transmitted and transmit the oldest RLC data block whose corresponding element in V(B) has the value PENDING_ACK, then the next oldest RLC data block whose corresponding element in V(B) has the value PENDING_ACK, etc.
References
3GPP TS 04.60, subclauses 9.1.1, 9.1.3 and 9.1.9.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.2.2 Test purpose
|
1. To verify that the mobile station sets the stall indicator to 1 in each RLC data block transmitted once the transmit window is stalled.
2. To verify that the mobile station retransmits data blocks that are pending acknowledgment.
3. To verify that the mobile station retransmits unacknowledged RLC data blocks in correct order while the transmit window is stalled.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS transmits k (window size) blocks without acknowledgement from SS. Confirm that the MS:
a) sets the stall indicator bit once the window is stalled; and
b) retransmits blocks that are pending acknowledgement, oldest first.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 1500 octets
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SI=0
4
Repeat steps 2 and 3 for BSN=1 to 63. SS doesn't acknowledge any of the data blocks with BSN from 0 to 63
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SI=1
7
Repeat steps 5 & 6 for BSN = 1 to 63 until all unacknowledged blocks are retransmitted.
SS verifies that the unacknowledged data blocks are retransmitted with SI field set to 1. SS verifies that in the retransmitted blocks the BSN is from 0 to 63
8
SS->MS
Packet Uplink Ack/Nack
SS acknowledges all the data blocks
USF not assigned to the MS
9
Wait for 6 blocks with no assigned USF
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A11 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH, BSN = 0
Repeat step 10
11
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
12
SS
Verify that MS is not retransmitting any acknowledged blocks
Verify transmitted data blocks are BSNs 64 and higher
13
{ Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.3 Acknowledged mode / Uplink TBF / Acknowledge state variable V(A)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.3.1 Conformance requirements
|
1. The Acknowledge state variable V(A) contains the BSN value of the oldest RLC data block that has not been positively acknowledged by its peer. V(A) can take on the values 0 through 127.
2. V(A) shall be set to the value 0 at the beginning of each TBF in which the RLC endpoint is the transmitter.
3. The value of V(A) shall be updated from the values received from its peer in the received block bitmap (RBB) of the Packet Ack/Nack message (see subclause 9.1.8).
References
3GPP TS 04.60, subclauses 9.1.2 and 9.1.8.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.3.2 Test purpose
|
1. To verify that the mobile station correctly decodes the RBB and updates the values of V(A).
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
1. The mobile station transmits k (window size) blocks without acknowledgement from SS. SS then acknowledges the first N blocks. The MS retransmits the negatively acknowledged data blocks with BSN from N to 63 and then it transmits N more new data blocks (from 64 to N+63).
2. The test is performed for the values of N = 10,15 and 20.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 3000 octets
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SI=0
4
Repeat steps 2 and 3 for BSN=1 to 63. SS doesn't acknowledge any of the data blocks with BSN from 0 to 63
5
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
6
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SI=1
7
Repeat steps 5 and 6 until unacknowledged data blocks (BSN = 0 to 30) are retransmitted with SI field set to 1
8
Wait BS_CV_MAX periods without granting USF.
9
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges first N (=10) RLC data blocks, RBB set to 1 and negatively acknowledges all the other data blocks from BSN=N to BSN=63 with RBB set to 0
USF not assigned to the MS
10
Wait for 6 blocks with no USF
11
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A12 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit block BSN = 31 if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
A13 (optional step)
SS->MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
12
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = N & SI = 0
13
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
14
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
15
SS
Repeat steps 13 and 14 until all negatively acknowledged data blocks are retransmitted followed by new data blocks
SS verifies that the negatively acknowledged data blocks are retransmitted before new data blocks are sent, by verifying that RLC data blocks with BSN from N to 63 are received subsequently first, then RLC data blocks with BSN from 64 to 63+N are received.
16
{ Completion of uplink RLC data block transfer}
17
-
-
The procedure is repeated for different values of N
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.4 Acknowledged mode / Uplink TBF / Negatively acknowledged RLC data blocks
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.4.1 Conformance requirements
|
1. The transmitter shall transmit the oldest RLC data block whose corresponding element in V(B) indexed relative to V(A) has the value NACKED.
2. If [ V(S) < V(A) + k ] modulo 128 and no RLC data blocks have a corresponding element in V(B) with the value NACKED, the RLC data block with BSN = V(S) shall be transmitted.
3. As each RLC data block is transmitted the corresponding element in V(B) shall be set to the value PENDING_ACK.
References
3GPP TS 04.60, subclause 9.1.3.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.4.2 Test purpose
|
1. To verify that the mobile station retransmits Nacked data blocks before transmission of new information.
2. To verify that the mobile station retransmits Nacked blocks in order of age, older first.
3. To verify that the mobile station only retransmit Nacked blocks once per negative acknowledgment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.4.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, , PBCCH not present, BS_CV_MAX = 0.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is made to transmit RLC data blocks. The SS randomly negatively acknowledges RLC data blocks. The MS retransmits the negatively acknowledged RLC data blocks, oldest first before transmitting new RLC data blocks.
The SS does not send further acknowledgements. The MS does not retransmit the previously negatively acknowledged RLC data blocks.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 3000 octets
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
4
Repeat steps 2 and 3 until received data block BSN = 30
5
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges RLC data blocks with BSN 10 to 30, RBB set to 1 and negatively acknowledges the rest with RBB set to 0
USF not assigned to the MS
6
Wait for 6 blocks with no USF
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A8 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit block BSN = 31 if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case repeat step 7
8
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 0..9
9
SS
Repeat steps 7 & 8 ten (11 in case mobile sends BSN = 31 in step A8) times
SS verifies that the Nacked data blocks are received before new data block once per negative acknowledgment.
After these data blocks new data block BSN=31 (32 if MS sends BSN = 31 earlier in step A8) should be received
10
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges retransmitted (BSN 0..9) RLC data blocks, RBB set to 1
11
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
12
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
13
SS
Repeat steps 11 and 12 until the stall indication bit is set in the data block received in step 12.
SS verifies that acknowledged blocks are not retransmitted
14
SS -> MS
PACKET UPLINK ACK/NACK
SS negatively acknowledges RLC data blocks with BSN 55 to 60, RBB set to 0 and acknowledges the rest with RBB set to 1
USF not assigned to the MS
15
Wait for 6 blocks with no USF.
16
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A17
MS -> SS
UPLINK RLC DATA BLOCK
MS may retransmit block BSN = 32 (or 33) if it has already been scheduled while Packet Uplink Ack/Nack is being processed.
A18
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
17
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 55..60
18
SS
Repeat steps 16 & 17 until all Nacked blocks are received
SS verifies that the Nacked data blocks are received before new data blocks once per negative acknowledgment.
19
{Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.5 Acknowledged mode / Uplink TBF / Invalid Negative Acknowledgment
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.5.1 Conformance requirements
|
For a R97 and R98 MS only:
1. If the mobile station is the transmitter, it shall set an instance of timer T3198 for each RLC data block sent (subclause 9.1.3 3GPP TS 04.60).
2. The timer T3198 shall have the expiry value set to BS_CV_MAX block periods (subclause 9.1.3 3GPP TS 04.60).
3. The mobile station shall not modify the element in the acknowledge state array, V(B), corresponding to an RLC data block that cannot be validly negatively acknowledged (subclause 9.1.8 3GPP TS 04.60).
For a R99 or later MS only:
If the RLC transmitter is on the mobile station side, the bit contains the value '0' and the number of block periods between the end of the block period used for the last transmission of the corresponding RLC data block and the beginning of the block period containing the Packet Uplink Ack/Nack message is less than (max(BS_CV_MAX,1) – 1) (i.e., the RLC data block was recently (re)transmitted and thus can not be validly negatively acknowledged in this particular Packet Uplink Ack/Nack message), the element in V(B) shall not be modified.
References
3GPP TS 04.60, subclauses 9.1.3 and 9.1.8.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.5.2 Test purpose
|
To verify the correct response of the mobile station to an invalid negative acknowledgement.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.5.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, , PBCCH not present, BS_CV_MAX = 15.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
- GPRS Release (TSPC_MS_GPRS_RELEASE)
PIXIT Statements
-
Test Procedure
The MS is made to send RLC data blocks. The SS negatively acknowledges some RLC data blocks within BS_CV_MAX block periods. The MS shall not retransmit the RLC data blocks that were negatively acknowledged.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 440 octets
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 0
4
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
5
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 1
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
7
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN = 2
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
9
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN =3
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
11
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
BSN =4
Wait for BS_CV_MAX block period of Block BSN = 0 to expire
12
SS -> MS
PACKET UPLINK ACK/NACK
SS negatively acknowledges blocks BSN = 0 and BSN =3, RBB = 0 and acknowledges blocks BSN = 1, BSN = 2 and BSN = 4, RBB = 1, SSN = 5.
USF not assigned to the MS
13
Wait for 6 blocks with no USF.
14
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A15 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may transmit block BSN = 5 if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case repeat step 14
15
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that data block BSN = 0 is retransmitted
16
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
17
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that data block BSN = 3 is not retransmitted
New data block received with BSN = 5 (6 if mobile sends BSN=5 earlier in step A15)
18
{ Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.6 Acknowledged mode / Uplink TBF / Decoding of Received Block Bitmap
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.6.1 Conformance requirements
|
For each bit in the RBB whose corresponding BSN value is within the transmit window, if the bit contains the value '1', the corresponding element in V(B) indexed relative to SSN shall be set to the value ACKED. If the bit contains the value '0', the element in V(B) shall be set to the value NACKED. A bit within the RBB whose corresponding BSN is not within the transmit window, shall be ignored.
References
3GPP TS 04.60, subclause 9.1.8.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.6.2 Test purpose
|
1. To verify the decoding of the received block bitmap of the Packet Uplink Ack/Nack message.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.1.6.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is made to send RLC data blocks. The SS negatively acknowledges one or more RLC data blocks after BS_CV_MAX block periods. The MS retransmits these blocks.
The SS negatively acknowledges data blocks outside the transmit window. The MS ignores these negative acknowledgments.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{ Uplink dynamic allocation two phase access}
n = 4000 octets
USF_GRANULARITY = 1 block
CHANNEL_CODING_COMMAND: cs1
2
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
3
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
4
Repeat steps 2 and 3 until received data block BSN = 19
SS doesn't acknowledge any of the data blocks with BSN from 0 to 19
5
Wait BS_CV_MAX periods without granting USF.
6
SS -> MS
PACKET UPLINK ACK/NACK
SS negatively acknowledges RLC data block with BSN 0, RBB set to 0 and acknowledges data blocks with BSN from 1 to 19, RBB set to 1
USF not assigned to the MS
7
Wait for 6 blocks with no USF.
8
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A9 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may transmit block BSN = 20 if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case repeat step 8
9
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS verifies that the Nacked data block (BSN = 0) is received before new data blocks
10
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
11
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
12
Repeat steps 10 and 11 until BSN=63
SS doesn't acknowledge any of the data blocks until BSN = 63
13
SS -> MS
PACKET UPLINK ACK/NACK
SS acknowledges all RLC data blocks with RBB set to 1
14
Wait for 6 blocks with no USF.
15
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
A16 (optional step)
MS -> SS
UPLINK RLC DATA BLOCK
MS may transmit block BSN = 0 (or BSN = 20 if step A09 was performed) if it has already been scheduled while Packet Uplink Ack/Nack is being processed. In this case repeat step 15
16
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
SS receives new data block with BSN = 64
17
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
18
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
19
Repeat steps 17 and 18 until BSN=80
SS doesn't acknowledge any of the data blocks
20
Wait BS_CV_MAX periods without granting USF.
21
SS -> MS
PACKET UPLINK ACK/NACK
SS negatively acknowledges RLC data block with bit corresponding to BSN 50 in RBB set to 0 and all other bits set to 1
USF not assigned to the MS
22
Wait for 6 blocks with no USF.
23
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH, containing USF assigned to the MS.
24
MS -> SS
UPLINK RLC DATA BLOCK
Received on the assigned PDTCH
25
SS
Repeat steps 23 and 24 until BSN=127
SS verifies that the MS ignored negative acknowledgment outside the window and sends new data blocks BSN=81 to 127
26
{ Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2 Acknowledged mode / Downlink TBF
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.1 Acknowledged mode / Downlink TBF / Receive state variable V(R)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.1.1 Conformance requirements
|
1. In RLC acknowledged mode, each RLC endpoint receiver shall have an associated receive state variable V(R). The receive state variable denotes the BSN of the next in-sequence RLC data block expected to be received.
2. The mobile station shall set V(R) to the value 0 at the beginning of each TBF in which the RLC endpoint is the receiver.
References
3GPP TS 04.60, subclause 9.1.5.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.1.2 Test purpose
|
1. To verify correct initialisation of the receive state variable, V(R).
2. To verify the receive state variable, V(R) is set to the next in sequence RLC data block expected to be received.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
SS establishes a downlink TBF and sends RLC data blocks with BSN values between 0 to N in sequence. The MS is polled in each RLC data block by setting the S/P bit. SS verifies that the SSN in the Packet Downlink Ack/Nack messages sent by the MS are set to [BSN+1] modulo 128. SS then sends RLC data block with random BSN N1 that holds a value between [N+1] modulo 128 and [N+64] modulo 128. The MS is polled in the last RLC data block by setting the S/P bit. SS verifies that the SSN in the Packet Downlink Ack/Nack message sent by the MS is set to [N1+1] modulo 128.
The test is performed for the values of N = 1, 10, 63, 64, 126, 127.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Macro parameters:
Acknowledged mode
2
SS -> MS
DOWNLINK RLC DATA BLOCK
MS is polled S/P bit '1' RRBP 00
3
MS -> SS
Packet Downlink Ack/ Nack
SS verifies that SSN = [BSN + 1] modulo 128
4
Repeat steps 2 and 3 until BSN = N
5
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN = N1 a random number between [N+1] mod 128 and [N+64] modulo 128
MS is polled S/P bit '1' RRBP 00
6
MS -> SS
Packet Downlink Ack/ Nack
SS verifies that SSN = [N1+1] modulo 128.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.2 Acknowledged mode / Downlink TBF / Receive window state variable V(Q)
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.2.1 Conformance requirements
|
In RLC acknowledged mode, each RLC endpoint receiver shall have an associated receive window state variable, V(Q). The mobile station shall set V(Q) to the value 0 at the beginning of each TBF in which the RLC endpoint is the receiver.
The value of V(Q) shall be updated when the RLC receiver receives the RLC data block whose BSN is equal to V(Q).
References
3GPP TS 04.60, subclause 9.1.6.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.2.2 Test purpose
|
1. To verify that V(Q) is not updated when data blocks with BSN not equal to V(Q) are received.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.2.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and the test PDP Context2 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
SS establishes a downlink TBF and sends an RLC data block with BSN value N (N in the range 1..63) and polls the MS. The MS shall accept the block and sends a Packet Downlink Ack/Nack message. SS verifies that SSN is set to [N+1] and RBB bit corresponding to N is set to 1. SS sends another RLC data block to the MS with BSN value 64 and polls the MS. SS verifies that the SSN and RBB fields in the Packet Downlink Ack/Nack message sent by the MS are not updated.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Macro parameters:
Acknowledged mode
2
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN = N (N is in the range of [1..63]) polls the MS
3
MS -> SS
Packet Downlink Ack/ Nack
SSN value should be [N+1] RBB set for block N
4
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN = 64, polls the MS
5
MS -> SS
Packet Downlink Ack/ Nack
SSN value should be [N+1]. No change in RBB
6
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN = 0, polls the MS
7
MS -> SS
Packet Downlink Ack/ Nack
SSN value should be [N+1]. RBB updated
8
SS -> MS
DOWNLINK RLC DATA BLOCK
BSN = 64, polls the MS
9
MS -> SS
Packet Downlink Ack/ Nack
SSN value should be 65.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.3 Acknowledged mode / Downlink TBF / Re-assembly of RLC data blocks
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.3.1 Conformance requirements
|
RLC data blocks shall be collected at the receiver until all RLC data blocks comprising an LLC PDU have been received. The RLC headers shall be removed from each RLC data block at this time and the RLC data units re-assembled into an LLC PDU and passed to the next higher layer.
References
3GPP TS 04.60, subclause 9.1.11.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.3.2 Test purpose
|
To verify the correct re-assembly of the RLC data blocks.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.3.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and PDP Context 12 is activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
SS establishes a downlink TBF and sends several data blocks in random sequence , but within the range of transmit and receive window.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Macro parameters:
Acknowledged mode
2
SS -> MS
DOWNLINK RLC DATA BLOCK
A bit set (A=1) in LLC frame
SS sends data blocks in random sequence
3
Repeat step 2 until all the data blocks in one LLC frame is transmitted
4
MS -> SS
Packet Downlink Ack/ Nack
5
{Uplink dynamic allocation two phase access}
USF_GRANULARITY = 1 block
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
7
MS -> SS
UPLINK RLC DATA BLOCK
LLC Supervisory frame (RR) acknowledging a valid LLC frame
8
{ Completion of uplink RLC data block transfer}
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.4 Acknowledged mode / Downlink TBF / Re-assembly / Length Indicator
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.4.1 Conformance requirements
|
1. The Extension (E) bit is used to indicate the presence of an optional extension octet in the RLC data block header. The More (M) bit is used to indicate the presence of an LLC frame following the current LLC frame. The M bit, the E bit, and the Length Indicator, are used to delimit LLC frames within a TBF.
2. The Length Indicator (LI) field is six bits in length and shall be encoded as a binary number. The value 0 shall indicate that no LLC frame boundary does exist, that the M bit shall be ignored and that the E bit shall be interpreted as having the value 1.
3 A singular case occurs when the end of the LLC PDU would fit within the RLC data block but the addition of the Length Indicator octet (to indicate the LLC PDU boundary) causes the LLC PDU to extend into the next RLC data block. In this case, this additional LI field shall take the value 0 whatever is the length of the last but one LLC PDU segment.
References
3GPP TS 04.60, subclause 9.1.11 and clause B.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.4.2 Test purpose
|
To verify the correct decoding of RLC data block length indication, more(M) and extension(E) bit fields during reassembly of LLC frames into RLC data blocks.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.1.2.4.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is GPRS updated with a P-TMSI allocated, SPLIT PG CYCLE negotiated and PDP Context 12 activated.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
SS establishes a downlink TBF and sends data blocks containing two LLC frames (A bit set) with length indicator encoded. The MS is expected to decode these fields and re-assemble LLC frames correctly.
The size of the first LLC frame is 15 octets and second is 24 octets.
Maximum Duration of Test
5 minutes.
Expected Sequence
Step
Direction
Message
Comments
1
{Downlink TBF establishment}
Macro parameters:
Acknowledged mode
2
SS -> MS
DOWNLINK RLC DATA BLOCK
15 octets of first LLC frame and 4 octets of second LLC frame
Length Indicator = 15,M =1, E = 1
A bit set (A = 1) in both LLC frames
3
SS -> MS
DOWNLINK RLC DATA BLOCK
19 octets from second LLC frame Length indicator = 0, M = 0, E = 1
4
SS -> MS
DOWNLINK RLC DATA BLOCK
1 octet from second LLC frame Length indicator = 1, M = 0, E = 1, FBI = 1
5
MS -> SS
PACKET DOWNLINK ACK/NACK
Optionally Including channel request description
6
{Uplink dynamic allocation two phase access}
USF_GRANULARITY = 1 block
7
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
8
MS -> SS
UPLINK RLC DATA BLOCK
LLC Supervisory frame (RR) acknowledging first LLC frame. If this UPLINK RLC DATA BLOCK contains a second RR frame acknowledging the second LLC frame steps A9 and B9 should be skipped.
A9 (Optional)
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
Sent on the PACCH of the PDCH assigned, USF assigned to the MS.
B9
(Optional)
MS -> SS
UPLINK RLC DATA BLOCK
LLC Supervisory frame (RR) acknowledging second LLC frame
9
{Completion of uplink RLC data block transfer}
Note: If the negotiated window size is less than 2, the testcase ends at the PDP context activation and link establishment.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.2 Control Blocks
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.2.1 Control Blocks Re-assembly
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.2.1.1 Conformance requirements
|
The network may segment RLC/MAC control messages into one or two RLC/MAC control blocks depending on the length of the RLC/MAC control message.
RLC/MAC control blocks shall be collected at the receiver until all RLC/MAC control blocks comprising a RLC/MAC control message have been received. The receiving side shall determine the length of the RLC/MAC control message contents by interpreting the RLC/MAC control block contents.
References
3GPP TS 04.60, subclauses 9.1.11a, 9.1.11b and 9.1.2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.2.1.2 Test purpose
|
To verify that the MS re-assembles a RLC control message If it spans across more than one RLC control block.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.2.1.3 Method of test
|
Initial Conditions
System Simulator:
1 cell, default setting, PBCCH not present.
Mobile Station:
The MS is switched off.
Specific PICS Statements
-
PIXIT Statements
-
Test Procedure
The MS is switched on and triggered to perform a GPRS attach. The SS sends a PACKET UPLINK ASSIGNMENT message that spans more than one RLC control block. The PACKET UPLINK ASSIGNMENT message contains Dynamic Allocation struct (Timeslot allocation with power control parameters included) and frequency parameters with direct encoding 2 struct information fields. The SS verifies that RLC data blocks containing Attach Request message are received from the MS.. Switch off the MS.
Maximum Duration of Test
5 minutes.
Expected sequence
Step
Direction
Message
Comments
1
MS
The MS is switched on and triggered to perform a GPRS attach.
2
MS -> SS
CHANNEL REQUEST
3
SS -> MS
IMMEDIATE ASSIGNMENT
Indicating two phase access
4
MS -> SS
PACKET RESOURCE REQUEST
5
SS -> MS
PACKET UPLINK ASSIGNMENT
Frequency Parameter direct encoding 2 information element.
Dynamic Allocation struct information element (Timeslot allocation and Power Control parameters included)
Payload type = 10, Sent on PACCH.(See section below)
6
SS -> MS
PACKET DOWNLINK DUMMY CONTROL BLOCK
USF assigned to the MS
7
MS -> SS
UPLINK RLC DATA BLOCKS
Attach Request received on PDTCH assigned in step 5
Specific Message Contents
PACKET UPLINK ASSIGNMENT message in step 5:
MESSAGE_TYPE
001010
PAGE_MODE
Normal Paging
Referenced Address
-
10 (TLLI)
CHANNEL_CODING_COMMAND
CS-1 coding
TLLI_BLOCK_CHANNEL_CODING
use value indicated in CHANNEL_CODING_COMMAND
Packet Timing Advance
-
1 (timing advance value)
- TIMING_ADVANCE_VALUE
30 bit periods
-
0 (no timing advance index)
{L|H<Frequency Parameters>}
H (Frequency Parameters present)
- Frequency Parameters
- TSC
5
11 (Direct Encoding Struct 2)
Direct Encoding Struct 2
MAIO
arbitrarily chosen
HSN
arbitrarily chosen
Length of MA Frequency list contents
Length of frequency list chosen according to length of MA Frequency list contents
MA Frequency list contents
For GSM 900, in bitmap 0 format,
(10, 30, 40, 50, 60, 70)
For DCS 1800 and PCS 1900, in range 512,
(520, 530, 540, 550, 560, 570, 580, 600, 610)
For GSM 700, T-GSM 810 in Range 512,
(447, 462, 467,475, 477, 480,485, 492,498, 504)
For GSM 850, in Range 512,
(137, 157, 167, 177, 187, 197, 207, 217, 227)
0 (Dynamic Allocation)
Dynamic Allocation
- Extended_Dynamic_Allocation
0
P0 Bit
0 (off)
USF Granularity
0 (one block)
{L|H<UPLINK_TFI_ASSIGNMENT>}
1 (assign an uplink TFI)
- UPLINK_TFI_ASSIGNMENT
00000 (uplink TBF identifier)
{0|1 RLC Data Blocks Granted}
0
{0|1 TBF Starting time description}
1
TBF Starting time
arbitrarily chosen
TIMESLOT_ALLOCATION with Power Control Parameters
1
ALPHA
0.5
-{0|1 USF_TN0 GAMMA_TN0}
0 (timeslot 0 not assigned)
-{0|1 USF_TN1 GAMMA_TN0}
0 (timeslot 1 not assigned)
-{0|1 USF_TN2 GAMMA_TN0}
0 (timeslot 2 not assigned)
-{0|1 USF_TN3 GAMMA_TN0}
0 (timeslot 3 not assigned)
- USF_TN4
1 (timeslot 4 assigned)
USF_TN4
000
- GAMMA_TN4
00100
-{0|1 USF_TN5 GAMMA_TN0}
0 (timeslot 5 not assigned)
-{0|1 USF_TN6 GAMMA_TN0}
0 (timeslot 6 not assigned)
-{0|1 USF_TN7 GAMMA_TN0}
0 (timeslot 7 not assigned)
For R99 network simulation:
Additions for Rel.99
1
- Packet Extended TA flag
0 not present
spare padding
Spare Padding
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.3 Default Message Contents and Macros
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.3.1 Message Contents
|
none
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.3.2 Macros
| |
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.3.2.1 Macro for uplink dynamic allocation two phase access (PBCCH not present)
|
Step
Direction
Message
Comments
{Uplink dynamic allocation two phase access}
Macro parameters:
n: the number of data octets to be transferred,
USF_GRANULARITY: 1 or 4 blocks,
RLC_DATA_BLOCKS_GRANTED: 9-261 (close-end), or absent (open-end)
CHANNEL_CODING_COMMAND: CS-1, -2, -3, -4
TBF_STARTING_TIME
0
MS
Trigger the MS initiating uplink transfer n octets data according to the test PDP context activated
1
MS -> SS
CHANNEL REQUEST
Received on RACH.
2
SS -> MS
IMMEDIATE ASSIGNMENT
Single block assignment, to order the MS to follow the two phase access procedure. Sent on AGCH.
3
MS -> SS
PACKET RESOURCE REQUEST
Two phase access procedure. Received on the single block assigned in step 2.
Check that the PEAK_THROUGHPUT, RADIO_PRIORITY and RLC_MODE are compliant with the PDP context used.
4
SS -> MS
PACKET UPLINK ASSIGNMENT
uplink dynamic allocation, no starting time (as default, otherwise use TBF_STARTING_TIME), Sent on PACCH of the same PDCH assigned in step 2.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.3.2.2 Macro for downlink TBF establishment (PBCCH not present)
|
Step
Direction
Message
Comments
{Downlink TBF establishment}
Macro parameters:
TBF_STARTING_TIME
1
SS -> MS
PAGING REQUEST
Page info contains P-TMSI of the MS. Sent on PCH.
2
MS -> SS
CHANNEL REQUEST
Establishment cause = "One phase access". Received on RACH.
3
SS -> MS
IMMEDIATE ASSIGNMENT
Random Reference = pertaining to the message received in step 2. Dynamic allocation for RLC data blocks, Sent on AGCH.
4
MS -> SS
UPLINK RLC DATA BLOCK
LLC PDU implicitly indicating paging response, containing TLLI in the RLC/MAC header. Received on uplink PDTCH assigned in step 3.
5
SS -> MS
PACKET UPLINK ACK/NACK
Acknowledge the received RLC data block. Sent on uplink PACCH.
6
MS -> SS
PACKET CONTROL ACKNOWLEDGEMENT
Acknowledge the RLC control message. Received on uplink PACCH.
7
SS -> MS
IMMEDIATE ASSIGNMENT
Downlink Assignment, TLLI value as received. Sent on PCH. Macro parameter as assigned in the test case.
|
683b5b8a98f7b1390ddd5516ea9247a2
|
51.010-1
|
43.4 EC-GSM-IoT
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.