21.3.11 CA / Start SC-PTM reception on SCell / Continue SC-PTM reception on Non-Serving after SCell release
36.523-13GPPEvolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Packet Core (EPC)Part 1: Protocol conformance specificationRelease 17TSUser Equipment (UE) conformance specification
21.3.11.1 CA / Start SC-PTM reception on SCell / Continue SC-PTM reception on Non-Serving after SCell release / Intra-band Contiguous CA
21.3.11.1.1 Test Purpose (TP)
(1)
with { UE in E-UTRAN RRC CONNECTED state with PCell and SCell activate and both broadcasting SIB15 and UE is interested to receive a SC-PTM service}
ensure that {
when { SIB15 indicates that the MBMS service is available on the frequency of the SCell }
then { UE starts SC-PTM reception on the Scell }
}
(2)
with { UE in E-UTRA RRC_CONNECTED state with active PCell and SCell and ongoing SC-PTM reception on the SCell }
ensure that {
when { UE receives an RRCConnectionReconfiguration message containing sCellToReleaseList with a sCellIndex equalling to the current UE SCell configuration with ongoing SC-PTM reception and UE releases the SCell and sends an RRCConnectionReconfigurationComplete message }
then { UE continues SC-PTM reception on the former SCell (now Non-Serving cell) }
}
21.3.11.1.2 Conformance requirements
References: The conformance requirements covered in the current TC is specified in: TS 36.306, clause 4.3.5.2 and TS 36.331, clause 5.8.5.3 and 5.8.5.3a. Unless otherwise stated these are Rel-13 requirements.
[TS 36.306, clause 4.3.5.2]
This field defines the carrier aggregation, MIMO and MBMS reception capabilities (via MBSFN or SC-PTM) supported by the UE for configurations with inter-band, intra-band non-contiguous, intra-band contiguous carrier aggregation and without carrier aggregation. For each band in a band combination the UE provides the supported CA bandwidth classes and the corresponding MIMO capabilities for downlink. The UE also has to provide the supported uplink CA bandwidth class and the corresponding MIMO capability for at least one band in the band combination. Applicability of provisioning uplink CA bandwidth class for each band in the band combinations is defined in TS 36.101 [6]. A MIMO capability applies to all carriers of a bandwidth class of a band in a band combination. For bandwidth classes that include multiple component carriers (i.e. bandwidth classes B, C, D and so on), the UE may also indicate a separate MIMO capability that applies to each individual carrier of a bandwidth class of a band in a band combination.
(…)
The UE that supports MBMS reception via MBSFN shall support MBMS reception via MBSFN on the PCell of MCG, and it may indicate support for MBMS reception via MBSFN on configured SCells (mbms-SCell) and for any cell that may be additionally configured as an SCell (mbms-NonServingCell) according to this field. The UE that supports MBMS reception via SC-PTM shall support MBMS reception via SC-PTM on the PCell of MCG, and it may indicate support for MBMS reception via SC-PTM on configured SCells (scptm-SCell) and for any cell that may be additionally configured as an SCell (scptm-NonServingCell) according to this field. The UE shall apply the system information acquisition and change monitoring procedure relevant for MBMS operation for these cells.
The UE indicating more than one frequency in the MBMSInterestIndication message as specified in TS 36.331 [5] shall support simultaneous reception of MBMS (via MBSFN or SC-PTM) on the indicated frequencies when the frequencies of the configured serving cells and the indicated frequencies belong to at least one band combination.
(…)
[TS 36.331, clause 5.8.5.3]
The UE shall:
1> consider a frequency to be part of the MBMS frequencies of interest if the following conditions are met:
2> at least one MBMS session the UE is receiving or interested to receive via an MRB or SC-MRB is ongoing or about to start; and
NOTE 1: The UE may determine whether the session is ongoing from the start and stop time indicated in the User Service Description (USD), see 3GPP TS 36.300 [9] or 3GPP TS 26.346 [57].
2> for at least one of these MBMS sessions SystemInformationBlockType15 acquired from the PCell includes for the concerned frequency one or more MBMS SAIs as indicated in the USD for this session; and
NOTE 2: The UE considers a frequency to be part of the MBMS frequencies of interest even though E-UTRAN may (temporarily) not employ an MRB or SC-MRB for the concerned session. I.e. the UE does not verify if the session is indicated on (SC-)MCCH.
NOTE 3: The UE considers the frequencies of interest independently of any synchronization state, e.g. [9, Annex J.1]
2> the UE is capable of simultaneously receiving MRBs and/or is capable of simultaneously receiving SC-MRBs on the set of MBMS frequencies of interest, regardless of whether a serving cell is configured on each of these frequencies or not; and
2> the supportedBandCombination the UE included in UE-EUTRA-Capability contains at least one band combination including the set of MBMS frequencies of interest;
NOTE 4: Indicating a frequency implies that the UE supports SystemInformationBlockType13 acquisition for the concerned frequency i.e. the indication should be independent of whether a serving cell is configured on that frequency.
NOTE 5: When evaluating which frequencies it can receive simultaneously, the UE does not take into account the serving frequencies that are currently configured i.e. it only considers MBMS frequencies it is interested to receive.
NOTE 6: The set of MBMS frequencies of interest includes at most one frequency for a given physical frequency. The UE only considers a physical frequency to be part of the MBMS frequencies of interest if it supports at least one of the bands indicated for this physical frequency in SystemInformationBlockType1 (for serving frequency) or SystemInformationBlockType15 (for neighbouring frequencies). In this case, E-UTRAN may assume the UE supports MBMS reception on any of the bands supported by the UE (i.e. according to supportedBandCombination).
[TS 36.331, clause 5.8.5.3a]
The UE shall:
1> consider a MBMS service to be part of the MBMS services of interest if the following conditions are met:
2> the UE is SC-PTM capable; and
2> the UE is receiving or interested to receive this service via an SC-MRB; and
2> one session of this service is ongoing or about to start; and
2> one or more MBMS SAIs in the USD for this service is included in SystemInformationBlockType15 acquired from the PCell for a frequency belonging to the set of MBMS frequencies of interest, determined according to 5.8.5.3.
21.3.11.1.3 Test Description
21.3.11.1.3.1 Pre-test conditions
System Simulator:
– 2 E-UTRA cells. Cell 1 is the PCell, Cell3 is an inactive SCell to be added, according to [18] cl. 6.3.4.
– SCPTMConfiguration message as defined in TS 36.508 [18] Table 4.6.1-18a is transmitted on Cell 3.
– System information combination 3 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 1.
– System information combination 26 as defined in TS 36.508[18] clause 4.4.3.1 is used in Cell 3.
UE:
– The UE is configured to receive MBMS services.
– The UE has in the signalled IE “supportedBandCombination” indicated support of the CA configuration for the frequency of Cell 1.
– The UE is capable to receiving SCPTM on SCell.
– The UE is capable to receiving SCPTM on NonServingCell.
Preamble:
– UE is in state Loopback Activated (State 4) with UE TEST LOOP MODE F on Cell 1 according to [18].
– The UE is made interested in receiving SC-PTM service with MBMS Service ID=1 as broadcasted in SCPTMConfiguration.
– The UE is made aware that the MBMS service is active.
21.3.11.1.3.2 Test procedure sequence
Table 21.3.11.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCConnectionReconfiguration message containing a sCellToAddModList with Cell 3 as SCell addition. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCConnectionReconfigurationComplete message |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
3 |
The SS transmits a Paging message including a systemInfoModification for Cell1. |
<– |
Paging |
– |
– |
|
4 |
From the beginning of the next modification period the SS starts broadcast of SystemInformationBlockType15 according to system information combination 18 as defined in TS 36.508[18] clause 4.4.3.1 on Cell 1 and according to system information combination 28 as defined in TS 36.508[18] clause 4.4.3.1 on Cell 3. SystemInformationBlockType15 on Cell 1 is including mbms-SAI-InterFreqList-r11 list for the frequency of Cell 3 indicating MBMS SAI=1. SystemInformationBlockType15 on Cell 3 is including mbms-SAI-IntraFreq-r11 list indicating MBMS SAI=1. |
<– |
SystemInformationBlockType15 |
– |
– |
|
5 |
The UE transmits an MBMSInterestIndication message. |
–> |
MBMSInterestIndication |
– |
– |
|
6 |
Wait for a period equal to the SC-MCCH repetition period for the UE to receive SCPTMConfiguration message |
– |
– |
– |
– |
|
– |
Exception; Step 7 is repeated 5 times |
– |
– |
– |
– |
|
7 |
The SS transmits 2 MBMS Packets on the SC-MTCH |
<– |
MBMS Packets |
– |
– |
|
8 |
The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message on Cell 1. |
<– |
UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST |
– |
– |
|
9 |
UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE. |
–> |
UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE |
– |
– |
|
10 |
Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 9 greater than zero? (Note: This verifies that UE has received MBMS packets on the SCell providing the MBMS service and started SC-PTM reception) |
– |
– |
1 |
P |
|
11 |
The SS transmits an RRCConnectionReconfiguration message containing a sCellToReleaseList with SCell release of Cell 3. |
<– |
RRCConnectionReconfiguration |
– |
– |
|
12 |
The UE transmits an RRCConnectionReconfigurationComplete message |
–> |
RRCConnectionReconfigurationComplete |
– |
– |
|
– |
Exception; Step 13 is repeated 5 times |
– |
– |
– |
– |
|
13 |
The SS transmits 2 MBMS Packets on the SC-MTCH. |
<– |
MBMS Packets |
– |
– |
|
14 |
The SS transmits an UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST message on Cell 1 |
<– |
UE TEST LOOP MODE F SCPTM PACKET COUNTER REQUEST |
– |
– |
|
15 |
UE responds with UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE. |
–> |
UE TEST LOOP MODE F SCPTM PACKET COUNTER RESPONSE |
– |
– |
|
16 |
Check: Is the number of reported MBMS Packets received on the SC-MTCH in step 15 greater than the number reported in step 9? (Note: This verifies that UE continue to receive MBMS packets on Cell 3 after being released as SCell and becoming a Non-Serving cell) |
– |
– |
2 |
P |
21.3.11.1.3.3 Specific message contents
Table 21.3.11.1.3.3-0: Conditions for specific message contents
in Tables 21.3.11.1.3.3-5 and 21.3.11.1.3.3-6
|
Condition |
Explanation |
|
Uplink_CA |
The UE supports carrier aggregation in UL under the test band. |
Table 21.3.11.1.3.3-1: SystemInformationBlockType15 for Cell 1 (from step 4 and all subsequent steps, Table 21.3.11.1.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_interFreq. |
|||
|
SystemInformationBlockType15 ::= SEQUENCE { |
|||
|
mbms-SAI-IntraFreq-r11 SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) } |
Not present |
||
|
mbms-SAI-InterFreqList-r11[1] SEQUENCE (SIZE (1..maxFreq)) OF SEQUENCE { |
1 entry |
||
|
dl-CarrierFreq-r11 |
Downlink EARFCN for Cell 3, see [18] table 6.3.1.2-1. |
||
|
mbms-SAI-List-r11[1] SEQUENCE (SIZE (1..maxSAI-MBMS-r11)) OF { INTEGER (0..65535) } |
1 |
1 entry INTEGER (0..65535) |
|
|
} |
|||
|
} |
|||
Table 21.3.11.1.3.3-2: SystemInformationBlockType15 for Cell 3 (from step 4 and all subsequent steps, Table 21.3.11.1.3.2-1)
|
Derivation Path: 36.508 table 4.4.3.3-14, condition SCPTM_intraFreq. |
Table 21.3.11.1.3.3-3: RRCConnectionReconfiguration (step 1, Table 21.3.11.1.3.2-1)
|
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
sCellToReleaseList-r10 |
Not present |
|||
|
sCellToAddModList-r10 |
SCellToAddMod-r10-f2-Add |
SCell addition for Cell 3 |
||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 21.3.11.1.3.3-4: SCellToAddMod-r10-f2-Add (Table 21.3.11.1.3.3-3)
|
Derivation Path: 36.508 clause 4.6. 3 table 4.6.3-19D SCellToAddMod-r10-DEFAULT |
|||||
|
Information Element |
Value/remark |
Comment |
Condition |
||
|
SCellToAddMod-r10 ::= SEQUENCE { |
|||||
|
sCellIndex-r10 |
1 |
||||
|
cellIdentification-r10 SEQUENCE { |
|||||
|
physCellId-r10 |
Physical Cell Identity of Cell 3 |
||||
|
dl-CarrierFreq-r10 |
Same downlink EARFCN as used for Cell 3 |
||||
|
dl-CarrierFreq-r10 |
maxEARFCN |
Band > 64 |
|||
|
} |
|||||
|
dl-CarrierFreq-v1090 |
Same downlink EARFCN as used for Cell 3 |
Band > 64 |
|||
|
radioResourceConfigCommonSCell-r10 |
RadioResourceConfigCommonSCell-r10-f2 |
||||
|
radioResourceConfigDedicatedSCell-r10 |
RadioResourceConfigDedicatedSCell-r10-f2 |
||||
|
} |
|||||
Table 21.3.11.1.3.3-5: RadioResourceConfigCommonSCell-r10-f2 (Table 21.3.11.1.3.3-4)
|
Derivation Path: 36.508 clause 4.6.3 table 4.6.3-13A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigCommonSCell-r10 ::= SEQUENCE { |
|||
|
nonUL-Configuration-r10 SEQUENCE { |
|||
|
dl-Bandwidth-r10 |
Same downlink system bandwidth as used for Cell 3 |
||
|
} |
|||
|
ul-Configuration-r10 |
Not present |
||
|
ul-Configuration-r10 SEQUENCE { |
Uplink_CA |
||
|
ul-FreqInfo-r10 SEQUENCE { |
|||
|
ul-Bandwidth-r10 |
Same uplink system bandwidth as used for Cell 3 |
optional |
FDD |
|
Not present |
TDD |
||
|
additionalSpectrumEmissionSCell-r10 |
Same additionalSpectrumEmission as used for Cell 3 |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 21.3.11.1.3.3-6: RadioResourceConfigDedicatedSCell-r10-f2 (Table 21.3.11.1.3.3-4)
|
Derivation Path: 36.508 clause 4.6.3 table 4.6.3-19AA |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RadioResourceConfigDedicatedSCell-r10 ::= SEQUENCE { |
|||
|
physicalConfigDedicatedSCell-r10 SEQUENCE { |
|||
|
ul-Configuration-r10 |
Not present |
||
|
ul-Configuration-r10 SEQUENCE { |
Uplink_CA |
||
|
antennaInfoUL-r10 |
Not present |
||
|
pusch-ConfigDedicatedSCell-r10 |
Not present |
||
|
uplinkPowerControlDedicatedSCell-r10 |
UplinkPowerControlDedicatedSCell-r10-DEFAULT |
||
|
cqi-ReportConfigSCell-r10 |
CQI-ReportConfigSCell-r10-DEFAULT |
||
|
soundingRS-UL-ConfigDedicated-r10 |
Not present |
||
|
soundingRS-UL-ConfigDedicated-v1020 |
Not present |
||
|
soundingRS-UL-ConfigDedicatedAperiodic-r10 |
Not present |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 21.3.11.1.3.3-7: MBMSInterestIndication (step 4, Table 21.3.11.1.3.2-1)
|
Derivation Path: 36.508, Table 4.6.1-4AC condition SC-PTM |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE{ |
||||
|
mbms-FreqList-r11[1] SEQUENCE (SIZE (1..maxFreqMBMS-r11)) OF { INTEGER (0..maxEARFCN2) } |
Same EARFCN as used for Cell 3 |
INTEGER (0..maxEARFCN2) |
||
|
} |
||||
|
} |
||||
Table 21.3.11.1.3.3-8: RRCConnectionReconfiguration (step 11, Table 21.3.11.1.3.2-1)
|
Derivation Path: 36.508 clause 4.6.1 table 4.6.1-8 |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCConnectionReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
c1 CHOICE { |
||||
|
rrcConnectionReconfiguration-r8 SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
sCellToReleaseList-r10 SEQUENCE (SIZE (1..maxSCell-r10) OF SEQUENCE { |
1 entry |
|||
|
sCellIndex-r10[1] |
1 |
SCell release for Cell 3 |
||
|
} |
||||
|
sCellToAddModList-r10 |
Not present |
|||
|
nonCriticalExtension SEQUENCE {} |
Not present |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
21.3.11.2 CA / Start SC-PTM reception on SCell / Continue SC-PTM reception on Non-Serving after SCell release / Inter-band CA
21.3.11.2.1 Test Purpose (TP)
Same as TC 21.3.11.1 but applied to Inter-band CA case.
21.3.11.2.2 Conformance requirements
Same as TC 21.3.11.1.
21.3.11.2.3 Test description
21.3.11.2.3.1 Pre-test conditions
Same as test case 21.3.11.1 with the following differences:
– Cells configuration: Cell 10 replaces Cell 3
21.3.11.2.3.2 Test procedure sequence
Same as test case 21.3.11.1 with the following differences:
– Cells configuration: Cell 10 replaces Cell 3.
21.3.11.2.3.3 Specific message contents
Same as test case 21.3.11.1 with the following differences:
– Cells configuration: Cell 10 replaces Cell 3.