7.1.11 Licensed Assisted Access
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
7.1.11.1 LAA transmits common control information in PDCCH scrambled with CC-RNTI
7.1.11.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state with nPUCCH-Identity-r11 configured and with a LAA Scell with frame structure type 3 activated }
ensure that {
when { LAA Scell transmits in PDCCH with DCI format 1C scrambled with CC-RNTI }
then { UE receives it and determines subframe configuration for LAA based on 4 bits }
}
7.1.11.1.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in TS 36.211 [44] clauses 4.3, , TS 36.213 [30] clause 13A and TS 36.321 [14] clause 7.1. Unless otherwise stated these are Rel-13 requirements.
…
[TS 36.211, clause 4.3]
Frame structure type 3 is applicable to LAA secondary cell operation with normal cyclic prefix only.
…
[TS 36.212, clause 5.3.3.1.4]
DCI format 1C is used for very compact scheduling of one PDSCH codeword, notifying MCCH change [6], notifying SC-MCCH change [6] , reconfiguring TDD, and LAA common information.
The following information is transmitted by means of the DCI format 1C:
If the format 1C is used for very compact scheduling of one PDSCH codeword
…
Else if the format 1C is used for notifying MCCH change
…
Else if the format 1C is used for notifying SC-MCCH change
…
Else if the format 1C is used for reconfiguring TDD
…
Else
– Subframe configuration for LAA – 4 bits as defined in section 13A of [3]
– UL duration and offset – 5 bits as defined in section 13A of [3]. The field only applies to a UE configured with uplink transmission on a LAA SCell
– PUSCH trigger B – 1 bit as defined in section 8.0 of [3]. The field only applies to a UE configured with uplink transmission on a LAA SCell
– Reserved information bits are added until the size is equal to that of format 1C used for very compact scheduling of one PDSCH codeword
…
[TS 36.213, clause 10]
If a UE is configured with a LAA Scell, the UE shall apply the procedures described in this clause assuming frame structure type 1 for the LAA Scell unless stated otherwise.
A UE is not expected to be configured with PUCCH on a LAA SCell.
[TS 36.213, clause 13A]
If a UE detects PDCCH with DCI CRC scrambled by CC-RNTI in subframe n-1 or subframe n of a LAA Scell, the UE may assume the configuration of occupied OFDM symbols in subframe n of the LAA Scell according to the ‘Subframe configuration for LAA’ field in the detected DCI in subframe n-1 or subframe n.
The ‘Subframe configuration for LAA’ field indicates the configuration of occupied OFDM symbols (i.e., OFDM symbols used for transmission of downlink physical channels and/or physical signals) in current and/or next subframe according to Table 13A-1.
If the configuration of occupied OFDM symbols for subframe n is indicated by the Subframe configuration for LAA field in both subframe n-1 and subframe n, the UE may assume that the same configuration of occupied OFDM symbols is indicated in both subframe n-1 and subframe n.
If a UE detects PDCCH with DCI CRC scrambled by CC-RNTI in subframe n, and the UE does not detect PDCCH with DCI CRC scrambled by CC-RNTI in subframe n-1, and if the number of occupied OFDM symbols for subframe n indicated by the Subframe configuration for LAA field in subframe n is less than 14, the UE is not required to receive any other physical channels in subframe n except for PDCCH with DCI format 0A/0B/4A/4B if configured.
If a UE does not detect PDCCH with DCI CRC scrambled by CC-RNTI containing ‘Subframe Configuration for LAA’ field set to other than ‘1110’ and ‘1111’ in subframe n and the UE does not detect PDCCH with DCI CRC scrambled by CC-RNTI containing ‘Subframe Configuration for LAA’ field set to other than ‘1110’ and ‘1111’ in subframe n-1, the UE is not required to use subframe n for updating CSI measurement.
The UE may detect PDCCH with DCI CRC scrambled by CC-RNTI by monitoring the following PDCCH candidates according to DCI Format 1C.
– one PDCCH candidate at aggregation level L=4 with the CCEs corresponding to the PDCCH candidate given by CCEs numbered 0,1,2,3
– one PDCCH candidate at aggregation level L=8 with the CCEs corresponding to the PDCCH candidate given by CCEs numbered 0,1,2,3,4,5,6,7
If a serving cell is a LAA Scell, and if the higher layer parameter subframeStartPosition for the Scell indicates ‘s07’, and if the UE detects PDCCH/EPDCCH intended for the UE starting in the second slot of a subframe, the UE may assume that OFDM symbols in the first slot of the subframe are not occupied, and all OFDM symbols in the second slot of the subframe are occupied,
If subframe n is a subframe in which OFDM symbols in the first slot are not occupied, the UE may assume that all the OFDM symbols are occupied in subframe n+1.
Table 13A-1: Subframe configuration for LAA in current and next subframe
Value of |
Configuration of occupied OFDM symbols (current subframe, next subframe) |
0000 |
(-,14) |
0001 |
(-,12) |
0010 |
(-,11) |
0011 |
(-,10) |
0100 |
(-,9) |
0101 |
(-,6) |
0110 |
(-,3) |
0111 |
(14,*) |
1000 |
(12,-) |
1001 |
(11,-) |
1010 |
(10,-) |
1011 |
(9,-) |
1100 |
(6,-) |
1101 |
(3,-) |
1110 |
reserved |
1111 |
reserved |
NOTE:
|
If a UE is configured with a LAA SCell for UL transmissions, and the UE detects PDCCH with DCI CRC scrambled by CC-RNTI in subframe n, the UE may be configured with a ‘UL duration’ and ‘UL offset’ for subframe n according to the ‘UL duration and offset’ field in the detected DCI. The ‘UL duration and offset’ field indicates the ‘UL duration’ and ‘UL offset’ according to TS 36.213 Table 13A-2.
If the ‘UL duration and offset’ field configures an ‘UL offset’ and an ‘UL duration’ for subframe n, the UE is not required to receive any downlink physical channels and/or physical signals in subframe(s) n+l+ i with i = 0, 1, …, d-1.
…
[TS 36.321, clause 7.1]
RNTI values are presented in Table 7.1-1 and their usage and associated Transport Channels and Logical Channels are presented in Table 7.1-2.
Table 7.1-1: RNTI values
Value (hexa-decimal) |
RNTI |
0000 |
N/A |
0001-0960 |
RA-RNTI, C-RNTI, Semi-Persistent Scheduling C-RNTI, Temporary C-RNTI, eIMTA-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SL-RNTI (see note), G-RNTI, SL-V-RNTI and SRS-TPC-RNTI |
0961-FFF3 |
C-RNTI, Semi-Persistent Scheduling C-RNTI, eIMTA-RNTI, Temporary C-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SL-RNTI, G-RNTI, SL-V-RNTI and SRS-TPC-RNTI |
FFF4-FFF9 |
Reserved for future use |
FFFA |
SC-N-RNTI |
FFFB |
SC-RNTI |
FFFC |
CC-RNTI |
FFFD |
M-RNTI |
FFFE |
P-RNTI |
FFFF |
SI-RNTI |
NOTE: A MAC entity uses the same C-RNTI on all Serving Cells.
Table 7.1-2: RNTI usage
RNTI |
Usage |
Transport Channel |
Logical Channel |
P-RNTI |
Paging and System Information change notification |
PCH |
PCCH |
SI-RNTI |
Broadcast of System Information |
DL-SCH |
BCCH, BR-BCCH |
M-RNTI |
MCCH Information change notification |
N/A |
N/A |
RA-RNTI |
Random Access Response |
DL-SCH |
N/A |
eIMTA-RNTI |
eIMTA TDD UL/DL configuration notification |
N/A |
N/A |
Temporary C-RNTI |
Contention Resolution (when no valid C-RNTI is available) |
DL-SCH |
CCCH |
Temporary C-RNTI |
Msg3 transmission |
UL-SCH |
CCCH, DCCH, DTCH |
C-RNTI |
Dynamically scheduled unicast transmission |
UL-SCH |
DCCH, DTCH |
C-RNTI |
Dynamically scheduled unicast transmission |
DL-SCH |
CCCH, DCCH, DTCH |
C-RNTI |
Triggering of PDCCH ordered random access |
N/A |
N/A |
Semi-Persistent Scheduling C-RNTI |
Semi-Persistently scheduled unicast transmission (activation, reactivation and retransmission) |
DL-SCH, UL-SCH |
DCCH, DTCH |
Semi-Persistent Scheduling C-RNTI |
Semi-Persistently scheduled unicast transmission (deactivation) |
N/A |
N/A |
TPC-PUCCH-RNTI |
Physical layer Uplink power control |
N/A |
N/A |
TPC-PUSCH-RNTI |
Physical layer Uplink power control |
N/A |
N/A |
SL-RNTI |
Dynamically scheduled sidelink transmission for sidelink communication |
SL-SCH |
STCH |
SC-RNTI |
Dynamically scheduled SC-PTM control information |
DL-SCH |
SC-MCCH |
G-RNTI |
Dynamically scheduled SC-PTM transmission |
DL-SCH |
SC-MTCH |
SC-N-RNTI |
SC-MCCH Information change notification |
N/A |
N/A |
CC-RNTI |
Providing common control PDCCH information |
N/A |
N/A |
SL-V-RNTI |
Dynamically scheduled sidelink transmission for V2X sidelink communication |
SL-SCH |
STCH |
SRS-TPC-RNTI |
SRS and TPC for the PUSCH-less SCells |
N/A |
N/A |
7.1.11.1.3 Test description
7.1.11.1.3.1 Pre-test conditions
System Simulator:
2 Cells
- Cell 1 (PCell) and Cell 10(SCell)
- Cell 10 is an Active SCell according to [18] cl. 6.3.4, configured with LAA Frame Structure 3.
UE:
None.
Preamble:
– The UE is in state Loopback Activated (state 4) in Cell 1 according to [18].
7.1.11.1.3.2 Test procedure sequence
Table 7.1.11.1.3.2-1shows the cell configurations used during the test. The configuration T0 indicates the initial conditions.
Table 7.1.11.1.3.2-1: Cell configuration
|
Parameter |
Unit |
Cell 1 |
Cell 10 |
Remarks |
T0 |
RS EPRE |
dBm/15kHz |
-85 |
-85 |
Table 7.1.11.1.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
0A |
The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 10) addition. |
<– |
– |
– |
– |
0B |
The UE transmits RRCConnectionReconfigurationComplete |
–> |
– |
– |
– |
1 |
The SS transmits Activation MAC control element to activate LAA Scell (Cell 10). |
<– |
(Activation) |
– |
– |
2 |
The SS indicates a new transmission on PDCCH and a DCI format 1C scrambled with CC-RNTI for common control information containing ‘Subframe Configuration for LAA’ field set to ‘0111’B and transmits a MAC PDU in Cell 10. |
<– |
MAC PDU |
– |
– |
3 |
60 ms after step 2he SS sends an UL grant suitable for the loop back PDU to be transmitted in Cell 1 |
<– |
(UL Grant) |
||
4 |
The UE transmits a MAC PDU containing the loop back PDU corresponding to step 2. |
–> |
MAC PDU |
1 |
P |
7.1.11.1.3.3 Specific message contents
Table 7.1.11.1.3.3-1: RRCConnectionReconfiguration (step 0A, Table 7.1.11.1.3.2-1)
Derivation Path: 36.331 clause 6.2.2 36.508, Table 4.6.1-8 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
rrc-TransactionIdentifier |
RRC-TransactionIdentifier-DL |
|||
criticalExtensions CHOICE { |
||||
c1 CHOICE{ |
||||
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
measConfig |
Not present |
|||
mobilityControlInfo |
Not present |
|||
dedicatedInfoNASList |
Not present |
|||
radioResourceConfigDedicated |
RadioResourceConfigDedicated-DEFAULT |
|||
securityConfigHO |
Not present |
|||
nonCriticalExtension |
SCellToAddMod-r10-DEFAULT |
|||
} |
||||
} |
||||
} |
||||
} |
Table 7.1.11.1.3.3-1A: RadioResourceConfigDedicated-DEFAULT (step 0A, Table 7.1.11.1.3.2-1)
Derivation Path: 36.331 clause 6.3.2 |
|||
Information Element |
Value/remark |
Comment |
Condition |
RadioResourceConfigDedicated-HO ::= SEQUENCE { |
|||
srb-ToAddModList |
Not present |
||
drb-ToAddModList |
Not present |
||
drb-ToReleaseList |
Not present |
||
mac-MainConfig |
Not present |
||
sps-Config |
Not present |
||
physicalConfigDedicated |
PhysicalConfigDedicated -DEFAULT |
||
} |
Table 7.1.11.1.3.3-1B: SCellToAddMod-r10-DEFAULT (step 0A, Table 7.1.11.1.3.2-1)
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-19D and Table 4.6.3-19AA |
|||
Information Element |
Value/remark |
Comment |
Condition |
SCellToAddMod-r10 ::= SEQUENCE { |
|||
sCellIndex-r10 |
1 |
||
radioResourceConfigDedicatedSCell-r10 SEQUENCE { |
|||
physicalConfigDedicatedScell-r10 |
PhysicalConfigDedicatedSCell-r10-DEFAULT |
||
} |
|||
} |
Table 7.1.11.1.3.3-2: PhysicalConfigDedicated-DEFAULT (Table 7.1.11.1.3.3-1A)
Derivation Path: 36.508, clause 4.6.3 table 4.8.2.1.6-1 |
|||||
Information Element |
Value/remark |
Comment |
Condition |
||
PhysicalConfigDedicated-DEFAULT ::= SEQUENCE { |
|||||
pucch-ConfigDedicated-v1020 |
PUCCH-ConfigDedicated-v1020-DEFAULT |
2TX AND FDD, TDD |
|||
pusch-ConfigDedicated-v1130 |
Not present |
||||
uplinkPowerControlDedicated-v1130 |
Not present |
||||
} |
|||||
Note: All other IE’s are not present |
Table 7.1.11.1.3.3-3: Void
Table 7.1.11.1.3.3-4: PhysicalConfigDedicatedScell-r10-DEFAULT (Table 7.1.11.1.3.3-4)
Derivation Path: 36.508 clause 4.6.3 Table 4.6.3-6A and 36.331 clause 6.3.2 |
||||
Information Element |
Value/remark |
Comment |
Condition |
|
PhysicalConfigDedicatedScell-r10 ::= SEQUENCE { |
||||
laa-SCellConfiguration-r13 SEQUENCE { |
||||
subframeStartPosition-r13 |
s0 |
|||
laa-SCellSubframeConfig-r13 |
00000000 |
LAA FS3 |
||
} |
||||
} |