7.1.2 RACH/FACH procedures
34.123-13GPPPart 1: Protocol conformance specificationRelease 15TSUser Equipment (UE) conformance specification
7.1.2.1 Selection and control of Power Level
7.1.2.1.1 Void
NOTE Test case "Selection and control of Power Level (FDD)" has been removed as the test purpose is implicitly tested by radio resource management test cases in TS 34.121 clause 8.4.2.1 and 8.4.2.2.
7.1.2.1.2 Selection and control of Power Level (3,84 Mcps TDD option)
(FFS)
7.1.2.1.3 Void
NOTE: Test case "Selection and control of Power Level (1.28Mcps TDD option)" has been removed as the test purpose is implicitly tested by radio resource management test cases in TS 34.1227.1.2.2. Correct application of Dynamic Persistence
7.1.2.2 Correct application of Dynamic Persistence
7.1.2.2.1 Void
NOTE Test case "Correct application of Dynamic Persistence (FDD)" has been removed as the test purpose is implicitly tested by radio resource management test cases in TS 34.121.
7.1.2.2.2 Correct application of Dynamic Persistence (3.84 Mcps TDD option)
(FFS)
7.1.2.2.3 Void
7.1.2.3 Correct Selection of RACH parameters
7.1.2.3.1 Correct Selection of RACH parameters (FDD)
7.1.2.3.1.1 Definition
The physical random access procedure described in this subclause is initiated upon request of a PHY-Data-REQ primitive from the MAC sublayer.
The UE selection of "PRACH system information" is described in TS 25.331 clause 8.5.17.
7.1.2.3.1.2 Conformance requirement
A. The physical random-access procedure shall be performed as follows:
1 Derive the available uplink access slots, in the next full access slot set, for the set of available RACH sub-channels within the given ASC with the help of TS 25.214, subclauses 6.1.1 and 6.1.2. Randomly select one access slot among the ones previously determined. If there is no access slot available in the selected set, randomly select one uplink access slot corresponding to the set of available RACH sub-channels within the given ASC from the next access slot set. The random function shall be such that each of the allowed selections is chosen with equal probability.
2 Randomly select a signature from the set of available signatures within the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability.
3 Set the Preamble Retransmission Counter to Preamble Retrans Max.
…
5 … Transmit a preamble using the selected uplink access slot, signature, and preamble transmission power.
6 If no positive or negative acquisition indicator (AI +1 nor –1) corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot:
6.1 Select the next available access slot in the set of available RACH sub-channels within the given ASC.
6.2 Randomly select a new signature from the set of available signatures within the given ASC. The random function shall be such that each of the allowed selections is chosen with equal probability.
…
6.4 Decrease the Preamble Retransmission Counter by one.
6.5 If the Preamble Retransmission Counter > 0 then repeat from step 5. Otherwise pass L1 status ("No ack on AICH") to the higher layers (MAC) and exit the physical random access procedure.
7 If a negative acquisition indicator corresponding to the selected signature is detected in the downlink access slot corresponding to the selected uplink access slot, pass L1 status ("Nack on AICH received") to the higher layers (MAC) and exit the physical random access procedure.
8 Transmit the random access message three or four uplink access slots after the uplink access slot of the last transmitted preamble depending on the AICH transmission timing parameter. Transmission power of the control part of the random access message should be P p-m [dB] higher than the power of the last transmitted preamble. Transmission power of the data part of the random access message is set according to subclause 5.1.1.2.
9 Pass L1 status "RACH message transmitted" to the higher layers and exit the physical random access procedure.
Reference(s)
TS 25.214 clause 6.1.
7.1.2.3.1.3 Test purpose
To verify that:
A1 the UE, initially:
– determines the ASC for the given Access Class (AC).
– derives the available uplink access slots, in the next full access slot set, for the set of available RACH sub-channels within the given ASC with the help of TS 25.214, subclauses 6.1.1. and 6.1.2. and randomly select one access slot among the ones previously determined.
– randomly select a new signature from the set of available signatures within the given ASC.
A2 the UE, when not receiving any reply from UTRAN:
– selects the next available access slot in the set of available RACH sub-channels within the given ASC.
– randomly select a new signature from the set of available signatures within the given ASC.
– does not transmit on the PRACH resources specified in the BCH message SIB 5/SIB 5bis after that the physical random access procedure is terminated.
A3 the UE, when detecting a negative acquisition indicator:
– does not transmit on the PRACH resources specified in the BCH message SIB 5/SIB 5bisafter that the physical random access procedure is terminated.
A4 the UE, when detecting a positive acquisition indicator:
– transmits the random access message three or four uplink access slots after the uplink access slot of the last transmitted preamble depending on the AICH transmission timing parameter.
– terminates the random access procedure.
7.1.2.3.1.4 Method of test
Initial conditions
The UE shall be attached to the network and in idle mode.
The UE shall use Access Class AC#0-9, which provides permission to use ASC#0 for the initial access.
Preamble Retrans Max parameter in SIB5/SIB5bis set to 5.
Maximum number of preamble retransmission cycles in SIB 5/SIB 5bis is set to Mmax = 1.
2 ASC settings (ASC#0 and ASC#1) are defined (with default parameters) in SIB5/SIB 5bis, except that the parameter assigned sub channel number is set as follows:
ASC#0 Assigned sub channel number = ‘0001’B
ASC#1 Assigned sub channel number = ‘0010’B
The available sub-channel number defined in SIB5/SIB 5bis is set to ‘1111 1111 1111’B.
NOTE: this value allows RACH transmission on all sub-channels defined by "Assigned sub channel number" above.
Related ICS/IXIT Statement(s)
TBD
Foreseen Final State of the UE
The same as the initial conditions.
Test procedure
a) The SS pages the UE until it performs a RACH access.
b) The SS measures the access slot and preamble signature used.
c) The SS does not acknowledge the RACH access, causing the UE to retry.
d) The SS again measures the access slot and preamble signature used.
e) The SS repeats the procedure from step c) until the maximum number of retries "Preamble Retrans Max" has been attempted, and monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
f) The SS pages the UE until it performs a RACH access.
g) The SS measures the access slot and preamble signature used.
h) The SS responds with a negative acquisition indicator on the AICH.
i) The SS monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
j) The SS pages the UE until it performs a RACH access.
k) The SS measures the access slot used.
l) The SS acknowledges the RACH access normally.
m) The SS measures the first access slot used in the PRACH message part.
n) The SS monitors the RACH channel for 10 seconds to ensure that no further RACH accesses occur.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
PAGE |
Preamble Retransmission Counter = 5 |
|
|
2 |
|
Access Preamble |
Access slot used = n, where n is defined by the table in clause 7.1.2.3.1.5 Signature used = any from {P0 .. P7} Preamble Retransmission Counter = 4 |
|
|
3 |
|
Access Preamble |
Access slot used = mod(n+3,15) Signature used = any from {P0 .. P7} Preamble Retransmission Counter = 3 |
|
|
4 |
|
Access Preamble |
Access slot used = mod(n+6,15) Signature used = any from {P0 .. P7} Preamble Retransmission Counter = 2 |
|
|
5 |
|
Access Preamble |
Access slot used = mod(n+9,15) Signature used = any from {P0 .. P7} Preamble Retransmission Counter = 1 |
|
|
6 |
|
Access Preamble |
Access slot used = mod(n+12,15) Signature used = any from {P0 .. P7} Preamble Retransmission Counter = 0 |
|
|
7 |
Wait for T = 10s |
SS monitors for RACH access attempts |
||
|
8 |
|
PAGE |
||
|
9 |
|
Access Preamble |
Access slot used = n, where n is defined by the table in clause 7.1.2.3.1.5 Signature used = any from {P0 .. P7} |
|
|
10 |
|
AICH = NEG ACQUISITION IND |
||
|
11 |
Wait for T = 10s |
SS monitors for RACH access attempts |
||
|
12 |
|
PAGE |
||
|
13 |
|
Access Preamble |
Access slot used = n, where n is defined by the table in clause 7.1.2.3.1.5 Signature used = any from {P0 .. P7} |
|
|
14 |
|
AICH = POS ACQUISITION IND |
||
|
15 |
|
RRC_CONNECTION_REQUEST |
Message part. Access slot used = mod(n+3, 15) |
|
|
16 |
Wait for T = 10s |
SS monitors for RACH access attempts |
||
Specific Message Contents
Use the default parameter values for the system information block with the same type specified in clause 6.1.0b of TS 34.108, with the following exceptions
Contents of System Information Block type 1
|
Information Element |
Value/Remark |
|
– UE Timers and constants in connected mode |
|
|
-N300 |
0 |
PRACH power offset info, PRACH info, and PRACH partitioning in System Information Block type 5/System Information Block type 5bis
|
Information Element |
Value/Remark |
|
PRACH info – CHOICE – Available Sub Channel number PRACH partitioning – Access Service Class – ASC Setting – CHOICE mode – Available signature Start Index – Available signature End Index – Assigned Sub-channel Number – ASC Setting – CHOICE mode – Available signature Start Index – Available signature End Index – Assigned Sub-channel Number PRACH power offset – Preamble Retrans Max |
FDD ‘1111 1111 1111’B FDD 0 (ASC#0) 7 (ASC#0) ‘0001’B FDD 0 (ASC#1) 7 (ASC#1) ‘0010’B 5 |
7.1.2.3.1.5 Test requirements
A1
At step 2
- the SS shall receive a PRACH preamble using an access slot as defined below and using a preamble signature from the set of preamble signatures {P0 .. P7}. See TS 25.213, clause 4.3.3.3 for a list of preamble codes.
- the access slot selected for the first access preamble can be any of the shaded table entries given below for ASC#0, depending on SFN.
NOTE: the table entries which are not shaded are not allowed for ASC#0.
|
SFN modulo 8 of corresponding P-CCPCH frame |
Sub-channel number |
|||||||||||
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
|
|
0 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
1 |
12 |
13 |
14 |
8 |
9 |
10 |
11 |
|||||
|
2 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
3 |
9 |
10 |
11 |
12 |
13 |
14 |
8 |
|||||
|
4 |
6 |
7 |
0 |
1 |
2 |
3 |
4 |
5 |
||||
|
5 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
|
6 |
3 |
4 |
5 |
6 |
7 |
0 |
1 |
2 |
||||
|
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
A2
At steps 3, 4, 5, and 6
– the SS shall receive a PRACH preamble using access slot mod(n + 3, 15), where n is the access slot used in the previous step, and using a preamble signature from the set of preamble signatures {P0 .. P7}. See TS 25.213, clause 4.3.3.3 for a list of preamble codes.
At step 7
– the SS shall not receive on the PRACH resources specified in the BCH message SIB 5/SIB 5bis after that the physical random access procedure is terminated.
A3
At step 11
– the SS shall not receive on the PRACH resources specified in the BCH message SIB 5/SIB 5bis after that the physical random access procedure is terminated.
A4
At step 15
– the SS shall receive the random access message three access slots after the uplink access slot of the preamble received in step 13.
At step 11
– the SS shall not receive on the PRACH resources specified in the BCH message SIB 5/SIB 5bis after that the physical random access procedure is terminated.
7.1.2.3.2 Correct Selection of RACH parameters (3.84 Mcps TDD option)
(FFS)
7.1.2.3.3 Correct Selection of RACH parameters (1.28 Mcps TDD option)
7.1.2.3.3.1 Definition and applicability
All TDD 1.28 Mcps UE
7.1.2.3.3.2 Conformance requirement
That the UE selects UpPCH codes and UpPCH sub-channels that are defined for the ASC that the UE should adopt based on its AC (when the RACH message to be transmitted is an ‘RRC Connection Request’). Parameters are defined in the SIB 5 messages received by the UE.
Reference(s)
TS25.224 clauses 4.7.1 and 5.6.
TS25.321 clause 11.2.3.
7.1.2.3.3.3 Test Purpose
To verify that the UE selects UpPCH codes and sub-channels that are allocated to the ASC that the UE should adopt based on its AC.
7.1.2.3.3.4 Method of test
Initial conditions
The UE is attached to the network and in idle mode. The Sim card should be configured so that the UE can adopt a known ASC based on its AC. The SS will broadcast SIB 5 messages that allocate to each ASC subsets of the total UpPCH codes and sub-channels.
Related ICS/IXT Statement(s)
TBD
Foreseen Final State of the UE
The same as the initial condition.
Test procedure
The test procedure is similar to that specified for test 7.1.2.1.3. In place of power level the test monitors the UpPCH codes that are used for the UE’s UpPCH transmissions and the sub-channels in which they are made.
a) The SS pages the UE to initiate the RACH access procedure;
b) The SS does not respond to UpPCH transmissions received from the UE;
c) The SS identifies the UpPCH codes on which the UE transmits;
d) The SS identifies the system frame numbers of the frames in which the UE’s UpPCH transmissions are received;
e) The procedure is continued until the maximum permitted power ramping cycles, and within each power ramping cycle, the maximum number of UpPCH transmissions have been made.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
PAGE |
||
|
2 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
|
3 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
|
4 |
……… |
|||
|
5 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
|
6 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
|
7 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
|
8 |
……… |
|||
|
9 |
-> |
UpPCH |
Code and sub-channel should be valid. |
|
7.1.2.3.3.5 Test Requirements
The UpPCH transmissions should be made in sub-channels and using codes that are allocated to the ASC that the UE should adopt based on its AC.
7.1.2.4 Correct Detection and Response to FPACH (1.28 Mcps TDD option)
7.1.2.4.1 Definition and applicability
All TDD 1,28 Mcps UE.
7.1.2.4.2 Conformance requirement
That the UE:
1. Receives and acts upon an FPACH message transmitted within WT sub-frames of the UE transmitting a UpPCH code, provided that:
– The FPACH was transmitted in the FPACH resource associated with the UpPCH code used by the UE; and
– The FPACH message correctly identifies the UpPCH codes identity and the number of sub-frames between the UpPCH and the FPACH transmissions.
2. Responds to the valid FPACH by transmitting an ‘RRC Connection Request’ message in the PRACH resources associated with the FPACH. The transmission should:
– Occupy the PRACH resource associated with the FPACH and the sub-channel in which the FPACH was received for the duration of the TTI;
– Be made with a timing correction and a transmission power that are based on information received in the FPACH.
3. Does not respond to FPACH messages that are transmitted, within WT sub-frames of the UE UpPCH transmission, in FPACH resources that are not associated with the UpPCH code that the UE used. Nor should it respond to FPACH messages that are received on the correct FPACH resources within WT sub-frames but which contain the incorrect UpPCH code identifier or an incorrect indication of the number of sub-frames elapsed between the UpPCH and FPACH transmissions.
Reference(s)
TS 25.224 clauses 4.7.1, 5.2.3, 5.6.
TS 25.331 clause 8.5.7.
TS 25.321 clause 11.2.3.
7.1.2.4.3 Test Purpose
To verify that:
– The UE does not respond to FPACH transmissions that are either, received on incorrect FPACH resources, or are received on correct resources and within WT sub-frames of the UpPCH transmission, but which do not contain the correct UpPCH identity or elapsed sub-frames.
– The UE does respond to an FPACH transmission that is received, within WT sub-frames of the UpPCH transmission, on the correct FPACH resources for the UpPCH code that was used, provided that the FPACH contains the identity of the UpPCH code and the number of sub-frames elapsed between the UpPCH and the FPACH transmissions.
– The UE response is to transmit an ‘RRC Connection Request’ message on the PRACH resources that are associated with the FPACH taking account of the timing correction and power adjustment parameters received in the FPACH.
7.1.2.4.4 Method of test
Initial conditions
The UE is attached to the network and in idle mode. The SS BCH SIB 5 message will specify that there are two or more FPACH associated with the UpPCH code set in a single PRACH system information. The UpPCH code set must include one or more odd and one or more even numbered codes.
Related ICS/IXT Statement(s)
TBD
Foreseen Final State of the UE
The same as the initial condition.
Test procedure
The test procedure consists of a number of stages:
a) The SS pages the UE to initiate RACH access.
b) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT sub-frames of each UpPCH transmission but on an incorrect FPACH resource for the UpPCH code used. It is noted that the UE may change the code used for each UpPCH transmission randomly amongst those available to its ASC.
c) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
d) The SS pages the UE to initiate RACH access.
e) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT sub‑frames of each UpPCH transmission on the correct FPACH resource for the UpPCH code used. The FPACH transmission should contain a signature reference number that is different from that of the UpPCH code that was used by the UE.
f) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
g) The SS pages the UE to initiate RACH access.
h) When UpPCH transmissions are received from the UE the SS should transmit FPACH responses within WT sub‑frames of each UpPCH transmission on the correct FPACH resource for the UpPCH code used. The FPACH transmission should contain a relative sub-frame number that is different from that defined by the elapsed number of frames between the UpPCH and the FPACH transmissions.
i) The PRACH resources associated with all of the FPACH should be monitored for a transmission from the UE.
j) The SS pages the UE to initiate RACH access.
k) When UpPCH transmissions are received from the UE the SS should transmit an FPACH response on the correct FPACH resources for the UpPCH code that was used by the UE. The FPACH response should include correct values for the signature reference and relative sub-frame number fields. The FPACH should also include known entries for the Received starting position of the UpPCH (UpPCHPOS) and the Transmit Power Level Command for RACH (PRXPRACHdes) fields.
l) The SS should monitor the PRACH resources associated with the FPACH commencing two or three sub-frames (depending upon the sub-frame in which the FPACH was transmitted and the length of the TTI) following the sub-frame in which the FPACH was transmitted and continuing for the number of sub-frames in the RACH TTI. The power level of the PRACH transmissions and the time of arrival of their mid-ambles should be measured. The SS should continue to monitor the UpPCH slot to ensure that the UE has ceased UpPCH transmissions.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
<- |
PAGE |
||
|
2 |
-> |
UpPCH |
||
|
3 |
<- |
FPACH |
Incorrect FPACH resources |
|
|
4 |
-> |
UpPCH |
||
|
5 |
………. |
|||
|
6 |
<- |
PAGE |
||
|
7 |
-> |
UpPCH |
||
|
8 |
<- |
FPACH |
Incorrect signature reference |
|
|
9 |
-> |
UpPCH |
||
|
10 |
……… |
|||
|
11 |
<- |
PAGE |
||
|
12 |
-> |
UpPCH |
||
|
13 |
<- |
FPACH |
Incorrect relative sub-frame number |
|
|
14 |
-> |
UpPCH |
||
|
15 |
………. |
|||
|
16 |
<- |
PAGE |
||
|
17 |
-> |
UpPCH |
||
|
18 |
<- |
FPACH |
Correct resources and information fields |
|
|
19 |
-> |
RRC Connection Request |
PPRACH = LPCCPCH + PRXPRACHdes +(i-1)*Pwrramp, UpPCHADV + UpPCHPOS– 8×16Tc |
|
7.1.2.4.5 Test Requirements
The UE should not respond to FPACH transmissions, which are made on the incorrect FPACH resources for the UpPCH code that the UE uses. The UE should continue to transmit UpPCH until the permitted maximum number of power ramping cycles is complete.
The UE should not respond to FPACH transmissions which are made within WT sub-frames of a UpPCH transmission and on the correct FPACH resources for the UpPCH code that it used if the FPACH contains either an incorrect signature reference number or an incorrect relative sub-frame number. The UE should continue to transmit UpPCH until the permitted maximum number of power ramping cycles is complete.
The UE should respond to an FPACH received within WT sub-frames of a UpPCH transmission if the FPACH is received on the correct FPACH resources for the UpPCH code used and if it contains valid information fields. The UE should cease transmitting UpPCH bursts and transmit an RRC Connection Request message using the PRACH resources that are associated with the FPACH and the sub-frame in which the FPACH was received. The transmission should commence two or three sub-frames after that containing the FPACH (dependent upon the sub-frame in which the FPACH was transmitted and the length of the TTI) and is made in all sub-frames within the TTI. Each PRACH burst should be made using the transmission power:
PPRACH = LPCCPCH + PRXPRACHdes + (i-1)*Pwrramp
Where i is the number of transmission attempts on UpPCH, i=1…Max SYNC_UL Transmissions. When the power used by the UE for the UpPCH transmission acknowledged by the FPACH was:
PUpPCH = LPCCPCH + PRXUpPCHdes +(i-1)*Pwrramp
And PRACHADV,i.e., the offset from the start of the PRACH slot of the UE’s transmission measured by SS shall be
UpPCHADV+UpPCHPOS – 8×16Tc chips, to an accuracy of 1/8 chip.
Where UpPCHADV denotes the offset from the start of the UpPCH slot of the UE’s transmission measured by SS and UpPCHPOS is the timing correction signalled to the UE in the FPACH.
7.1.2.4a Access Service class selection for RACH transmission
7.1.2.4a.1 Definition and applicability
All UE.
7.1.2.4a.2 Conformance requirement
The following ASC selection scheme shall be applied, where NumASC is the highest available ASC number and MinMLP the highest logical channel priority assigned to one logical channel:
– In case all TBs in the TB set have the same MLP, select ASC=min(NumASC, MLP).
– In case TBs in a TB set have different priority, determine the highest priority level MinMLP and select ASC=min(NumASC, MinMLP).
Reference(s)
TS 25.321 clause 11.2.1.
7.1.2.4a.3 Test purpose
To verify that MAC selects ASC correctly.
7.1.2.4a.4 Method of test
Initial conditions
System Simulator:
– SYSTEM INFORMATION BLOCK TYPE 7 (see specific message contents).
– 1 cell, default parameters, Ciphering Off.
User Equipment:
– The UE shall operate under normal test conditions, Ciphering Off.
– The Test-USIM shall be inserted
The SS starts broadcasting the System Information as specified in TS 34.108 clause 6.1, using the configuration for the PRACH and SCCPCH (signalled in SYSTEM INFORMATION BLOCK types 5 and 6) as follows:
1. The SCCPCH is configured as specified in TS 34.108 clause 6.10.2.4.3.3 (Interactive/Background 32 kbps RAB + SRB for PCCH + SRB for CCCH + SRB for DCCH + SRB for BCCH).
2. The PRACH is configured as specified in TS 34.108 clause 6.10.2.4.4.1.
The SS follows the procedure in TS 34.108 clause 7.4.2.6 (initiated by Mobile Terminated connection) so that the UE shall be in state BGP 6-11 (PS-DCCH+DTCH_FACH) with the following exceptions:
1. The MAC Logical channel Priority (MLP) of the user RB is set to 8.
2. The Timer Poll for RB20 will be Omitted in Radio Bearer Setup message to UE.
The user RB is placed into loop-back mode 1 each with the UL SDU size set to 39 bytes.
Related ICS/IXIT Statement(s)
TBD
Foreseen Final State of the UE
Test procedure
a) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
The SS waits to receive uplink data on RACH TrCH via the user RB.
NOTE 1: As all access slots are allowed, correct reception of loop backed PDU by SS, implicitly checks correct selection of ASC.
b) The SS reconfigures the transmitted system information as follows:
Only one ASC setting (ASC#0) is defined, with default parameters, except that the parameter "Assigned sub channel number" is set as follows:
ASC#0 Assigned sub channel number = ‘0010’B (FDD)
The available sub-channel number defined in system information is set to ‘1111 1111 1111’B (default parameter setting).
NOTE 2: this value allows RACH transmission on any sub-channel defined by "Assigned sub channel number" above.
ASC#0 sub channel size = Size1 : NULL (1.28Mcps TDD)
NOTE 3: "all available channelisation codes" and "all available subchannels" with "subchannel size=Size 1".The SS then updates System Information Block 6, sends a SYSTEM INFORMATION CHANGE INDICATION message to the UE and waits 10 s for the UE to take the system information change into account.
c) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
d) The SS waits to receive uplink data on RACH TrCH via the user RB, for FDD, then checks that the access slots and preamble signatures used correspond to ASC#0, i.e. the access slot selected for the first access preamble can be any of the shaded table entries given below for ASC#0, depending on SFN. The access slot used for the Message part shall be the access slot used for preamble (for which SS ACK’s) + 3.
NOTE 4: the table entries which are not shaded are not allowed for ASC#0 (FDD).
|
SFN modulo 8 of corresponding P-CCPCH frame |
Sub-channel number |
|||||||||||
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
|
|
0 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
1 |
12 |
13 |
14 |
8 |
9 |
10 |
11 |
|||||
|
2 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
3 |
9 |
10 |
11 |
12 |
13 |
14 |
8 |
|||||
|
4 |
6 |
7 |
0 |
1 |
2 |
3 |
4 |
5 |
||||
|
5 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
|
6 |
3 |
4 |
5 |
6 |
7 |
0 |
1 |
2 |
||||
|
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
e) The SS reconfigures the transmitted system information as follows:
Four ASC settings (ASC#0 to ASC#3) are defined (with default parameters), except that the parameter assigned sub channel number is set as follows (FDD):
ASC#0 Assigned sub channel number = ‘0100’B
ASC#1 Assigned sub channel number = ‘0001’B
ASC#2 Assigned sub channel number = ‘0010’B
ASC#3 Assigned sub channel number = ‘0000’B (i.e. no sub channel is assigned)
The available sub-channel number defined in system information is set to ‘1111 1111 1111’B (default parameter setting).
NOTE 5: this value allows RACH transmission on all sub-channels defined by "Assigned sub channel number" above.
Four ASC settings (ASC#0 to ASC#3) are defined (with default parameters), except that the parameter assigned sub channel number is set as follows (1.28Mcps TDD):
ASC#0 sub channel size = Size4 : ‘0100’B
ASC#1 sub channel size = Size4 : ‘0001’B
ASC#2 sub channel size = Size4 : ‘0010’B
ASC#3 sub channel size = Size4 : ‘0000’B (i.e. no sub channel is assigned)
NOTE 6: Each bit indicates availability of a subchannel, where the subchannels are numbered subchannel 0, subchannel 1 etc. The value 1 of a bit indicates that the subchannel is available for the ASC this IE is associated with. The value 0 of a bit indicates that the subchannel is not available for the ASC this IE is associated with. Default value of the IE is that all subchannels within the size are available for the ASC this IE is associated with.
The SS then updates System Information Block 6, sends a SYSTEM INFORMATION CHANGE INDICATION message to the UE and waits 10 s for the UE to take the system information change into account.
f) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
g) The SS waits 10 s to ensure no uplink data is received on RACH TrCH via the user RB.
h) The SS then reconfigures the uplink user RB to have a MAC Logical channel Priority of 1 by sending Radio Bearer Reconfiguration message on the DCCH using UM RLC.
i) The SS sends 1 RLC SDU of size 10 bytes on the downlink user RB.
j) The SS waits to receive uplink data on RACH TrCH via the user RB, for FDD, then checks that the access slots and preamble signatures used correspond to ASC#1, i.e. the access slot selected for the first access preamble can be any of the shaded table entries given below for ASC#1, depending on SFN. The access slot used for the Message part shall be the access slot used for preamble (for which SS ACK’s) + 3.SS will receive 2 loop backed PDU’s. One the loop backed PDU of step I, and the second one due to RLC layer transmission/retransmission of loop backed PDU of step f. As ‘In sequence Delivery’ will be enabled, the loop backed PDU of step f shall arrive before loop backed PDU of step i.
NOTE 7: the table entries which are not shaded are not allowed for ASC#1(FDD).
|
SFN modulo 8 of corresponding P-CCPCH frame |
Sub-channel number |
|||||||||||
|
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 |
|
|
0 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
1 |
12 |
13 |
14 |
8 |
9 |
10 |
11 |
|||||
|
2 |
0 |
1 |
2 |
3 |
4 |
5 |
6 |
7 |
||||
|
3 |
9 |
10 |
11 |
12 |
13 |
14 |
8 |
|||||
|
4 |
6 |
7 |
0 |
1 |
2 |
3 |
4 |
5 |
||||
|
5 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
|
6 |
3 |
4 |
5 |
6 |
7 |
0 |
1 |
2 |
||||
|
7 |
8 |
9 |
10 |
11 |
12 |
13 |
14 |
|||||
k) The SS may optionally release the radio bearer.
Expected sequence
|
Step |
Direction |
Message |
Comments |
|
|
UE |
SS |
|||
|
1 |
|
RLC PDU |
||
|
1a |
|
RLC PDU |
||
|
2 |
|
SYSTEM INFORMATION CHANGE INDICATION |
Modified system information |
|
|
3 |
|
RLC PDU |
||
|
4 |
|
RLC PDU |
SS checks ASC parameters (ASC#0) |
|
|
5 |
|
SYSTEM INFORMATION CHANGE INDICATION |
Modified system information |
|
|
6 |
|
RLC PDU |
||
|
6a |
SS waits to check no RLC PDUs are received |
|||
|
7 |
ß |
RB RECONFIGURATION |
User RB MLP = 1 |
|
|
7a |
|
RLC PDU |
Optional step, see note 1 SS checks ASC parameters (ASC#1)(transmission/retransmission of loop backed PDU of step 6) |
|
|
7b |
|
RB RCONFIGURATION COMPLETE |
||
|
7c |
|
RLC PDU |
Optional step, see note 1 SS checks ASC parameters (ASC#1)(transmission/retransmission of loop backed PDU of step 6) |
|
|
8 |
|
RLC PDU |
||
|
8a |
|
RLC PDU |
Optional step, see note 1 SS checks ASC parameters (ASC#1) (transmission/retransmission of loop backed PDU of step 6) |
|
|
9 |
|
RLC PDU |
SS checks ASC parameters (ASC#1) |
|
|
10 |
|
RB RELEASE |
optional |
|
|
Note 1: Loop backed RLC PDU of step 6 can be received either at step 7a or at step 7c or at step 8a |
||||
Specific Message Contents
System Information Block type 7
Use the same System Information Block Type 7 message as found in clause 6.1.0b of TS 34.108, with the following exceptions:
|
– PRACHs listed in system information block type6 |
|
|
– Dynamic persistence level |
2 |
System Information Block type 6 (Step 2) (FDD)
Use the same System Information Block Type 6 message as found in clause 6.1.0b of TS 34.108, with the following exceptions:
|
– PRACH system information list |
|
|
– PRACH system information |
|
|
– PRACH info |
|
|
– CHOICE mode |
FDD |
|
– Available Signature |
‘0000 0000 1111 1111’B |
|
– Available SF |
64 |
|
– Preamble scrambling code number |
0 |
|
– Puncturing Limit |
1.00 |
|
– Available Sub Channel number |
‘1111 1111 1111’B |
|
– Transport Channel Identity |
15 |
|
– RACH TFS |
|
|
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport format information |
|
|
– RLC size |
168 |
|
– Number of TB and TTI List |
|
|
– Number of Transport blocks |
1 |
|
– CHOICE Mode |
FDD |
|
– CHOICE Logical Channel List |
Configured |
|
– RLC size |
360 |
|
– Number of TB and TTI List |
|
|
– Number of Transport blocks |
1 |
|
– CHOICE Mode |
FDD |
|
– CHOICE Logical Channel List |
Configured |
|
– Semi-static Transport Format information |
|
|
– Transmission time interval |
20 ms |
|
– Type of channel coding |
Convolutional |
|
– Coding Rate |
1/2 |
|
– Rate matching attribute |
150 |
|
– CRC size |
16 |
|
– RACH TFCS |
|
|
– CHOICE TFCI signalling |
Normal |
|
– TFCI Field 1 information |
|
|
– CHOICE TFCS representation |
Complete reconfiguration |
|
– TFCS complete reconfiguration information |
|
|
– CHOICE CTFC Size |
2 bit |
|
– CTFC information |
0 |
|
– Power offset information |
|
|
– CHOICE Gain Factors |
Computed Gain Factor |
|
– Reference TFC ID |
0 |
|
– CHOICE Mode |
FDD |
|
– Power offset Pp-m |
0 dB |
|
– CTFC information |
1 |
|
– Power offset information |
|
|
– CHOICE Gain Factors |
Signalled Gain Factor |
|
– CHOICE mode |
FDD |
|
– Gain factor ßc |
11 |
|
– Gain factor ßd |
15 |
|
– Reference TFC ID |
0 |
|
– CHOICE Mode |
FDD |
|
– Power offset Pp-m |
0 dB |
|
– PRACH partitioning |
|
|
– Access Service Class |
|
|
– ASC Setting |
|
|
– CHOICE mode |
FDD |
|
– Available signature Start Index |
0 |
|
– Available signature End Index |
7 |
|
– Assigned Sub-Channel Number |
‘0010’B The first/ leftmost bit of the bit string contains the most significant bit of the Assigned Sub-Channel Number. |
|
– Persistence scaling factor |
Not Present |
|
– AC-to-ASC mapping table |
|
|
– AC-to-ASC mapping |
0 (AC0-9) |
|
– AC-to-ASC mapping |
0 (AC10) |
|
– AC-to-ASC mapping |
0 (AC11) |
|
– AC-to-ASC mapping |
0 (AC12) |
|
– AC-to-ASC mapping |
0 (AC13) |
|
– AC-to-ASC mapping |
0 (AC14) |
|
– AC-to-ASC mapping |
0 (AC15) |
|
– CHOICE mode |
FDD |
|
– Primary CPICH TX power |
31 |
|
– Constant value |
-10 |
|
– PRACH power offset |
|
|
– Power Ramp Step |
3dB |
|
– Preamble Retrans Max |
4 |
|
– RACH transmission parameters |
|
|
– Mmax |
2 |
|
– NB01min |
3 slot |
|
– NB01max |
10 slot |
|
– AICH info |
|
|
– Channelisation code |
3 |
|
– STTD indicator |
FALSE |
|
– AICH transmission timing |
0 |
System Information Block type 6 (Step 2)( 1.28Mcps TDD)
Use the same System Information Block Type 6 message as found in clause 6.1.0b of TS 34.108, with the following exceptions:
|
– PRACH system information list |
|
|
– PRACH system information |
|
|
– PRACH info |
|
|
– CHOICE mode |
TDD |
|
– CHOICE TDD option |
1.28 Mcps TDD |
|
– SYNC_UL info |
|
|
– SYNC_UL codes bitmap |
‘11111111’ |
|
– UL Target SIR |
10 dB |
|
– Power Ramping Step |
3 dB |
|
– Max SYNC_UL Transmissions |
8 |
|
– Mmax |
32 |
|
– Transport Channel Identity |
15 |
|
– RACH TFS |
|
|
– CHOICE Transport channel type |
Common transport channels |
|
– Dynamic Transport format information |
|
|
– RLC size |
Reference clause 6.11 "Parameter Set" |
|
– Number of TB and TTI List |
|
|
– Number of Transport blocks |
Reference clause 6.11 "Parameter Set" |
|
– CHOICE Mode |
TDD |
|
– CHOICE Logical Channel List |
Configured |
|
– Semi-static Transport Format information |
|
|
– Transmission time interval |
20 ms |
|
– Type of channel coding |
Convolutional |
|
– Coding Rate |
1/2 |
|
– Rate matching attribute |
150 |
|
– CRC size |
16 |
|
– RACH TFCS |
Not present |
|
– PRACH partitioning |
|
|
– Access Service Class |
|
|
– ASC Setting |
|
|
– CHOICE mode |
TDD |
|
– CHOICE TDD option |
1.28 Mcps TDD |
|
– Available SYNC_UL codes indices |
‘11111111’ |
|
– CHOICE subchannel size |
Size1 |
|
– Available Subchannels |
Null |
|
– Persistence scaling factor |
Not Present |
|
– AC-to-ASC mapping table |
|
|
– AC-to-ASC mapping |
0 (AC0-9) |
|
– AC-to-ASC mapping |
0 (AC10) |
|
– AC-to-ASC mapping |
0 (AC11) |
|
– AC-to-ASC mapping |
0 (AC12) |
|
– AC-to-ASC mapping |
0 (AC13) |
|
– AC-to-ASC mapping |
0 (AC14) |
|
– AC-to-ASC mapping |
0 (AC15) |
|
– CHOICE mode |
TDD (no data) |
RADIO BEARER RECONFIGURATION (FDD) (Step 7)
The contents of RADIO BEARER RECONFIGURATION message in this test case is identical to the message sub-type titled as "Packet to CELL_FACH from CELL_FACH in PS" as found in clause 9 of TS 34.108, with the following exceptions:
|
– RB mapping info |
|
|
– Information for each multiplexing option |
2 RBMuxOptions |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
DCH |
|
– UL Transport channel identity |
1 |
|
– Logical channel identity |
Not Present |
|
– CHOICE RLC size list |
Configured |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
DCH |
|
– DL DCH Transport channel identity |
6 |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
Not Present |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Explicit list |
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
FACH |
|
– DL DCH Transport channel identity |
Not Present |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
RADIO BEARER RECONFIGURATION (1.28Mcps TDD) (Step 7)
The contents of RADIO BEARER RECONFIGURATION message in this test case is identical to the message sub-type titled as "Packet to CELL_FACH from CELL_FACH in PS" as found in clause 9 of TS 34.108, with the following exceptions:
|
– RB mapping info |
|
|
– Information for each multiplexing option |
2 RBMuxOptions |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
DCH |
|
– UL Transport channel identity |
1 |
|
– Logical channel identity |
Not Present |
|
– CHOICE RLC size list |
Configured |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
DCH |
|
– DL DCH Transport channel identity |
6 |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
Not Present |
|
– RLC logical channel mapping indicator |
Not Present |
|
– Number of uplink RLC logical channels |
1 |
|
– Uplink transport channel type |
RACH |
|
– UL Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
|
– CHOICE RLC size list |
Explicit list |
|
– RLC size index |
Reference to TS34.108 clause 6 Parameter Set |
|
– MAC logical channel priority |
1 |
|
– Downlink RLC logical channel info |
|
|
– Number of downlink RLC logical channels |
1 |
|
– Downlink transport channel type |
FACH |
|
– DL DCH Transport channel identity |
Not Present |
|
– DL DSCH Transport channel identity |
Not Present |
|
– Logical channel identity |
7 |
7.1.2.4a.5 Test requirements
In step 1a, SS implicitly checks ASC parameters by receiving correctly the loop backed PDU.
In step 4, the access slots and preamble signatures used on the PRACH TrCH on which the RLC PDU was received shall correspond to configured legal values for the allowed ASC#0.
In step 6a, no PDUs shall be received on PRACH.
In step 9, the access slots and preamble signatures used on the PRACH TrCH on which the RLC PDU was received shall correspond to configured legal values for the allowed ASC#1.
7.1.2.5 Void
NOTE: Test case "Control of RACH transmissions for FDD mode" has been removed as the test purpose is implicitly tested by radio resource management test case in TS 34.121 clause 8.4.2.3.