7.1.9 Activation/Deactivation of SCells
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.9.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer
7.1.9.1.1 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Intra-band Contiguous CA
7.1.9.1.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state with SCell configure }
ensure that {
when { the UE receives an Activation MAC Control Element activating the Scell }
then { the UE starts monitoring PDCCH on activated Scell }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with SCell activated }
ensure that {
when { the UE receives an UL grant on Scell PDCCH}
then { the UE restarts the sCellDeactivationTimer }
}
(3)
with { UE in E-UTRA RRC_CONNECTED state with SCell activated }
ensure that {
when { the UE sCellDeactivationTimer expires}
then { the UE deactivates the Scell and stops monitoring PDCCH on Scell }
}
(4)
with { UE in E-UTRA RRC_CONNECTED state with SCell Activated }
ensure that {
when { the UE receives a deactivation MAC Control Element deactivating the Scell }
then { the UE deactivates the Scell and stops monitoring PDCCH on Scell }
}
(5)
with { UE in E-UTRA RRC_CONNECTED state with SCell activated }
ensure that {
when { the UE receives a DL assignment on Scell PDCCH}
then { the UE restarts the sCellDeactivationTimer }
}
7.1.9.1.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.13 & 6.1.3.8.
[TS 36.321, clause 5.13]
If the UE is configured with one or more SCells, the network may activate and deactivate the configured SCells. The PCell is always activated. The network activates and deactivates the SCell(s) by sending the Activation/Deactivation MAC control element described in subclause 6.1.3.8. Furthermore, the UE maintains a sCellDeactivationTimer timer per configured SCell and deactivates the associated SCell upon its expiry. The same initial timer value applies to each instance of the sCellDeactivationTimer and it is configured by RRC. The configured SCells are initially deactivated upon addition and after a handover.
The UE shall for each TTI and for each configured SCell:
– if the UE receives an Activation/Deactivation MAC control element in this TTI activating the SCell, the UE shall in the TTI according to the timing defined in [2]:
– activate the SCell; i.e. apply normal SCell operation including:
– SRS transmissions on the SCell;
– CQI/PMI/RI/PTI reporting for the SCell;
– PDCCH monitoring on the SCell;
– PDCCH monitoring for the SCell
– start or restart the sCellDeactivationTimer associated with the SCell;
– else, if the UE receives an Activation/Deactivation MAC control element in this TTI deactivating the SCell; or
– if the sCellDeactivationTimer associated with the activated SCell expires in this TTI:
– in the TTI according to the timing defined in [2]:
– deactivate the SCell;
– stop the sCellDeactivationTimer associated with the SCell;
– flush all HARQ buffers associated with the SCell.
– if PDCCH on the activated SCell indicates an uplink grant or downlink assignment; or
– if PDCCH on the Serving Cell scheduling the activated SCell indicates an uplink grant or a downlink assignment for the activated SCell:
– restart the sCellDeactivationTimer associated with the SCell;
– if the SCell is deactivated:
– not transmit SRS on the SCell;
– not report CQI/PMI/RI/PTI for the SCell;
– not transmit on UL-SCH on the SCell;
– not monitor the PDCCH on the SCell;
– not monitor the PDCCH for the SCell.
[TS 36.321, clause 6.1.3.8]
The Activation/Deactivation MAC control element is identified by a MAC PDU subheader with LCID as specified in table 6.2.1-1. It has a fixed size and consists of a single octet containing seven C-fields and one R-field. The Activation/Deactivation MAC control element is defined as follows (figure 6.1.3.8-1).
– Ci: if there is an SCell configured with SCellIndex i as specified in [8], this field indicates the activation/deactivation status of the SCell with SCellIndex i , else the UE shall ignore the Ci field. The Ci field is set to "1" to indicate that the SCell with SCellIndex i shall be activated. The Ci field is set to "0" to indicate that the SCell with SCellIndex i shall be deactivated;
– R: Reserved bit, set to “0”.
Figure 6.1.3.8-1: Activation/Deactivation MAC control element
7.1.9.1.1.3 Test description
7.1.9.1.1.3.1 Pre-test conditions
System Simulator:
– Cell 1 (PCell) and Cell 3(SCell)
– Cell 3 is an Active SCell according to [18] cl. 6.3.4.
UE:
None.
Preamble:
– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18].
7.1.9.1.1.3.2 Test procedure sequence
Table 7.1.9.1.1.3.2-1: Time instances of cell power level and parameter changes
Parameter |
Unit |
Cell 1 |
Cell 3 |
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-85 |
Table 7.1.9.1.1.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on Cell 1 with SCell (Cell 3) addition. |
<– |
RRCConnectionReconfiguration |
– |
– |
2 |
The UE transmit an RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
3 |
The SS transmits Activation MAC control element to activate Scell (Cell 3). |
<– |
MAC PDU (Activation (C1=1)) |
– |
– |
4 |
200 ms after step 3, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
5 |
Check: Does the UE transmit a Scheduling Request on PUCCH? |
–> |
(SR) |
1 |
P |
6 |
The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1. |
<– |
(UL Grant) |
– |
– |
7 |
The UE transmit a MAC PDU containing the loop back PDU corresponding to step 4 |
–> |
MAC PDU |
– |
– |
7a |
The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 7 |
<– |
MAC PDU (CC1) |
– |
– |
8 |
200 ms after step 6, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
9 |
Check: Does the UE transmit a Scheduling Request on PUCCH? |
–> |
(SR) |
2 |
P |
10 |
The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1. |
<– |
(UL Grant) |
– |
– |
11 |
The UE transmit a MAC PDU containing the loop back PDU corresponding to step 8 |
–> |
MAC PDU |
– |
– |
12 |
The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 11 |
<– |
MAC PDU (CC1) |
– |
– |
13 |
400 ms after step 10, the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
14 |
Check: Does the UE transmit a Scheduling Request on PUCCH in next 1 second? |
–> |
(SR) |
3 |
F |
15 |
The SS transmits Activation MAC control element to activate Scell (Cell 3). |
<– |
MAC PDU (Activation (C1=1)) |
– |
– |
16 |
200 ms after step 15 The SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing just padding or RLC status PDU, but no RLC data PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
17 |
400 ms after step 15 the SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
18 |
Check: Does the UE transmit a Scheduling Request on PUCCH? |
–> |
(SR) |
1,5 |
P |
19 |
The SS sends an UL grant suitable for transmitting loop back PDU on Cell 1. |
<– |
(UL Grant) |
– |
– |
19 |
The UE transmit a MAC PDU containing the loop back PDU corresponding to step 17 |
–> |
MAC PDU |
– |
– |
20 |
The SS transmits a MAC PDU containing RLC status PDU acknowledging reception of RLC PDU in step 19 |
<– |
MAC PDU (CC1) |
– |
– |
21 |
The SS transmits Deactivation MAC control element to de-activate Scell (Cell 3). |
<– |
MAC PDU (Deactivation (C1=0)) |
– |
– |
22 |
The SS indicates a new transmission on PDCCH of CC2 and transmits a MAC PDU (containing an RLC PDU ) |
<– |
MAC PDU (CC2) |
– |
– |
23 |
Check: Does the UE transmit a Scheduling Request on PUCCH in next 1 second? |
–> |
(SR) |
4 |
F |
7.1.9.1.1.3.3 Specific message contents
Table 7.1.9.1.1.3.3-1: RRCConnectionReconfiguration (Table 7.1.9.1.1.3.2-1, step 1)
Derivation path: 36.508 table 4.6.1-8 condition SCell_AddMod |
|||
Information Element |
Value/Remark |
Comment |
Condition |
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE{ |
|||
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
RadioResourceConfigDedicated SEQUENCE { |
|||
mac-MainConfig CHOICE { |
|||
explicit |
MAC-MainConfig-RBC |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 7.1.9.1.1.3.3-2: MAC-MainConfig-RBC (Table 7.1.9.1.1.3.3-1)
Derivation path: 36.508 table 4.8.2.1.5-1 condition DRX_L |
|||
Information Element |
Value/Remark |
Comment |
Condition |
MAC-MainConfig-RBC SEQUENCE { |
|||
timeAlignmentTimerDedicated |
Infinity |
||
mac-MainConfig-v1020 SEQUENCE { |
|||
sCellDeactivationTimer-r10 |
rf32 |
320 milliseconds |
|
} |
|||
} |
Table 7.1.9.1.1.3.3-3: SCellToAddMod-r10 (Table 7.1.9.1.1.3.3-1)
Derivation Path: 36.508, Table 4.6.3-19D |
|||
Information Element |
Value/remark |
Comment |
Condition |
SCellToAddMod-r10 ::= SEQUENCE { |
|||
sCellIndex-r10 |
1 |
||
cellIdentification-r10 SEQUENCE { |
|||
physCellId-r10 |
PhysicalCellIdentity of Cell 3 |
||
dl-CarrierFreq-r10 |
Same downlink EARFCN as used for Cell 3 |
||
} |
|||
} |
7.1.9.1.2 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Inter-band CA
The scope and description of the present TC is the same as test case 7.1.9.1.1 with the following differences:
– CA configuration: Inter-band CA replaces Intra-band Contiguous CA.
– Cells configuration: Cell 10 replaces Cell 3.
– Cell 10 is an Active SCell according to [18] cl. 6.3.4.
7.1.9.1.3 CA / Activation/Deactivation of SCells / Activation/Deactivation MAC control element reception / sCellDeactivationTimer / Intra-band non-Contiguous CA
The scope and description of the present TC is the same as test case 7.1.9.1.1 with the following differences:
– CA configuration: Intra-band non-Contiguous CA replaces Intra-band Contiguous CA.
7.1.9.2 CA / PUCCH SCell / Activation/Deactivation of SCells
7.1.9.2.1 Test Purpose (TP)
(1)
with { UE in E-UTRA RRC_CONNECTED state with one SCell activated and configured as PUCCH SCell, and a second SCell activated and belongs to the second PUCCH group }
ensure that {
when { the PUCCH SCell is deactivated and UE receives a MAC PDU on the second SCell }
then { the UE transmits an ACK/NACK on the PCell }
}
7.1.9.2.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 36.321, clause 5.3.2.1.
[TS 36.213, clause 10 and 10.1]
If the UE is configured with a PUCCH-SCell, the UE shall apply the procedures described in this clause for both primary PUCCH group and secondary PUCCH group
– When the procedures are applied for the primary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’ , ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells, serving cell, serving cells belonging to the primary PUCCH group respectively.
- – When the procedures are applied for secondary PUCCH group, the terms ‘secondary cell’, ‘secondary cells’, ‘serving cell’, ‘serving cells’ in this clause refer to secondary cell, secondary cells (not including the PUCCH-SCell), serving cell, serving cells belonging to the secondary PUCCH group respectively. The term ‘primary cell’ in this clause refers to the PUCCH-SCell of the secondary PUCCH group.
…
A UE transmits PUCCH only on the primary cell.
[TS 36.321, clause 5.13]
The MAC entity shall for each TTI and for each configured SCell:
– if the MAC entity is configured with an activated SCell upon SCell configuration or receives MAC control element(s) in this TTI activating the SCell, the MAC entity shall in the TTI according to the timing defined in TS 36.213 [2]:
– activate the SCell; i.e. apply normal SCell operation including:
– SRS transmissions on the SCell;
– if cqi-ShortConfigSCell is configured:
– CQI/PMI/RI/PTI/CRI reporting for the SCell using the short period of the CSI (CQI/PMI/RI/PTI/CRI) reporting resource configured by cqi-ShortConfigSCell according to the timing defined in TS 36.213 [2].
– else:
– CQI/PMI/RI/PTI/CRI reporting for the SCell using the configuration in cqi-ReportConfigSCell.
– PDCCH monitoring on the SCell;
– PDCCH monitoring for the SCell;
– PUCCH/SPUCCH transmissions on the SCell, if configured.
…
– if the SCell is deactivated:
– not transmit SRS on the SCell;
– not report CQI/PMI/RI/PTI/CRI for the SCell;
– not transmit on UL-SCH on the SCell;
– not transmit on RACH on the SCell;
– not monitor the PDCCH on the SCell;
– not monitor the PDCCH for the SCell;
– not transmit PUCCH/SPUCCH on the SCell.
7.1.9.2.3 Test description
7.1.9.2.3.1 Pre-test conditions
System Simulator:
- Cell 1 (PCell), Cell 3(PUCCH SCell) and Cell 6(SCell)
- Cell 3 and Cell 6 are Active SCells according to [18] cl. 6.3.4
– RRC Connection Reconfiguration (preamble: Table 4.5.3.3-1, step 8) using parameters as specified in Table 7.1.9.2.3.3-1 and 7.1.9.2.3.3-2.
UE:
None.
Preamble:
– The UE is in state Loopback Activated (state 4) on Cell 1 according to [18].
7.1.9.2.3.2 Test procedure sequence
In Table 7.1.9.2.3.2-1, Row marked "T0" denotes the initial conditions which illustrates the downlink power levels and other changing parameters to be applied for the cells after preamble.
Table 7.1.9.2.3.2-1: Time instances of cell power level and parameter changes
Parameter |
Unit |
Cell 1 |
Cell 3 |
Cell6 |
|
T0 |
Cell-specific RS EPRE |
dBm/15kHz |
-85 |
-85 |
-85 |
Table 7.1.9.2.3.2-2: Main behaviour
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
U – S |
Message |
||||
1 |
The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on PCell (Cell 1) with SCell (Cell 3) addition and PUCCH configured on SCell (Cell 3). |
<– |
RRCConnectionReconfiguration |
– |
– |
2 |
The UE transmit an RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
3 |
The SS transmits an RRConnectionReconfiguration message containing a sCellToAddModList on PCell (Cell 1) with SCell (Cell 6) addition and configured to secondary PUCCH group. |
<– |
RRCConnectionReconfiguration |
– |
– |
4 |
The UE transmit an RRCConnectionReconfigurationComplete message. |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
5 |
The SS transmits Activation MAC control element to activate SCell (Cell 3). |
<– |
MAC PDU (Activation (C1=1)) |
– |
– |
6 |
The SS transmits Activation MAC control element to activate SCell (Cell 6). |
<– |
MAC PDU (Activation (C1=1)) |
– |
– |
7 |
Wait for 100ms to handle any UE messages related to the completion of the HARQ process |
– |
– |
– |
– |
8 |
The SS Transmits MAC PDU containing a RLC PDU on SCell (Cell 6) |
<– |
MAC PDU (SCell) |
– |
– |
9 |
Check: Does the UE transmit a HARQ ACK for the DL data corresponding SCell (Cell 6) on PUCCH SCell (Cell 3)? |
–> |
HARQ ACK (SCell) |
– |
– |
10 |
The SS transmits Activation MAC control element to deactivate SCell (Cell 3). |
<– |
MAC PDU (Activation (C1=0)) |
– |
– |
11 |
Wait for 100ms to handle any UE messages related to the completion of the HARQ process |
– |
– |
– |
– |
12 |
The SS Transmits MAC PDU containing a RLC PDU on SCell (Cell 6) |
<– |
MAC PDU (SCell) |
– |
– |
13 |
Check: Does the UE transmit a HARQ ACK for the DL data corresponding SCell (Cell 6) on PCell (Cell 1)? |
–> |
HARQ ACK (SCell) |
1 |
P |
7.1.9.2.3.3 Specific message contents
Table 7.1.9.2.3.3-1: RRCConnectionReconfiguration (preamble)
Derivation path: 36.508 Table 4.6.1-8 |
|||
Information Element |
Value/Remark |
Comment |
Condition |
RRCConnectionReconfiguration ::= SEQUENCE { |
|||
criticalExtensions CHOICE { |
|||
c1 CHOICE{ |
|||
rrcConnectionReconfiguration-r8 SEQUENCE { |
|||
RadioResourceConfigDedicated SEQUENCE { |
|||
mac-MainConfig SEQUENCE { |
|||
timeAlignmentTimerDedicated |
Infinity |
||
} |
|||
} |
|||
} |
|||
} |
|||
} |
|||
} |
Table 7.1.9.2.3.3-2: RRCConnectionReconfiguration (step 1, Table 7.1.9.2.3.2-2)
Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod |
Table 7.1.9.2.3.3-3: SCellToAddMod-r10 (Table 7.1.9.2.3.3-2)
Derivation Path: 36.508, Table 4.6.3-19D |
|||
Information Element |
Value/remark |
Comment |
Condition |
SCellToAddMod-r10 ::= SEQUENCE { |
|||
sCellIndex-r10 |
1 |
||
cellIdentification-r10 SEQUENCE { |
|||
physCellId-r10 |
PhysicalCellIdentity of Cell 3 |
||
dl-CarrierFreq-r10 |
Same downlink EARFCN as used for Cell 3 |
||
} |
|||
} |
Table 7.1.9.2.3.3-4: RadioResourceConfigCommonSCell-r10-DEFAULT (Table 7.1.9.2.3.3-3)
Derivation path: 36.508 Table 4.6.3-13A with condition PUCCH SCell |
Table 7.1.9.2.3.3-5: RRCConnectionReconfiguration (step 3, Table 7.1.9.2.3.2-2)
Derivation Path: 36.508 Table 4.6.1-8, condition SCell_AddMod |
Table 7.1.9.2.3.3-6: SCellToAddMod-r10 (Table 7.1.9.2.3.3-5)
Derivation Path: 36.508, Table 4.6.3-19D |
|||
Information Element |
Value/remark |
Comment |
Condition |
SCellToAddMod-r10 ::= SEQUENCE { |
|||
sCellIndex-r10 |
1 |
||
cellIdentification-r10 SEQUENCE { |
|||
physCellId-r10 |
PhysicalCellIdentity of Cell 6 |
||
dl-CarrierFreq-r10 |
Same downlink EARFCN as used for Cell 6 |
||
} |
|||
} |
Table 7.1.9.2.3.3-7: PhysicalConfigDedicatedSCell-r10-DEFAULT (Table 7.1.9.2.3.3-6)
Derivation Path: 36.508, Table 4.6.3-6A with condition PUCCH-SCell1 |