12.2.7 Inter-carrier concurrent operation / Sidelink CSI reporting
38.523-13GPP5GSPart 1: ProtocolRelease 17TSUser Equipment (UE) conformance specification
12.2.7.1 Inter-carrier concurrent operation / Sidelink CSI reporting / Configuration
12.2.7.1.1 Test Purpose (TP)
(1)
with { UE in NR RRC_CONNECTED state and having established PC5 RRC connection with peer UE }
ensure that {
when { UE is configured by upper layer to configure SL CSI-RS resource to peer UE }
then { UE sends an RRCReconfigurationSidelink message including sl-CSI-RS-Config and sl-LatencyBoundCSI-Report to peer UE and starts to transmit SL CSI-RS }
}
(2)
with { UE in NR RRC_CONNECTED and having established PC5 RRC connection with peer UE }
ensure that {
when { UE is configured by upper layer to trigger SL CSI report }
then { UE sends an SCI format 2-A to trigger SL CSI report and the ‘CSI request‘ field in the corresponding SCI format 2-A is set to 1 }
}
12.2.7.1.2 Conformance requirements
References: The conformance requirements covered in the current TC are specified in: TS 38.331 clause 5.8.9.1.1, 5.8.9.1.2, TS 38.214 clause 8.5.2.2, 8.2.1, TS 38.212 clause 8.3.1.1 and 8.4.1.1. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.8.9.1.1]
The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.
The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in sub-clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases:
…
– the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound.
In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.
[TS 38.331, clause 5.8.9.1.2]
The UE shall set the contents of RRCReconfigurationSidelink message as follows:
…
1> set the sl-CSI-RS-Config;
1> set the sl-LatencyBoundCSI-Report,
NOTE 1: How to set the parameters included in sl-CSI-RS-Config and sl-LatencyBoundCSI-Report is up to UE implementation.
The UE shall submit the RRCReconfigurationSidelink message to lower layers for transmission.
[TS 38.214, clause 8.5.2.2]
The UE can be configured with one CSI-RS pattern as indicated by the higher layer parameters sl-CSI-RS-FreqAllocation, sl-OneAntennaPort, sl-CSI-RS-FirstSymbol in SL-CSI-RS-Config.
Parameters for which the UE shall assume non-zero transmission power for CSI-RS are configured according to clause 8.2.1.
A UE is not expected to be configured such that a CSI-RS and the corresponding PSCCH can be mapped to the same resource element. A UE is not expected to receive sidelink CSI-RS and PSSCH DM-RS, nor CSI-RS and 2nd-stage SCI, on the same symbol.
Sidelink CSI-RS shall be transmitted according to [4, TS 38.211] in the resource blocks used for the PSSCH associated with the SCI format 2-A triggering a report.
[TS 38.214, clause 8.2.1]
A UE transmits sidelink CSI-RS within a unicast PSSCH transmission if the following conditions hold:
– CSI reporting is enabled by higher layer parameter sl-CSI-Acquisition; and
– the ‘CSI request‘ field in the corresponding SCI format 2-A is set to 1.
The following parameters for CSI-RS transmission are configured for each CSI-RS configuration:
– sl-CSI-RS-FirstSymbol indicates the first OFDM symbol in a PRB used for SL CSI-RS
– sl-CSI-RS-FreqAllocation indicates the number of antenna ports and the frequency domain allocation for SL CSI-RS.
When the UE is configured with Qp={1,2} CSI-RS port(s) in sidelink and the number of scheduled layers is ,
– The CSI-RS scaling factor specified in clause 8.4.1.5.3 of [4, TS 38.211] is given by where is the scaling factor for the corresponding PSSCH specified in clause 8.3.1.5 of [4, TS 38.211].
[TS 38.212, clause 8.3.1.1]
SCI format 1-A is used for the scheduling of PSSCH and 2nd-stage-SCI on PSSCH
The following information is transmitted by means of the SCI format 1-A:
– Priority – 3 bits as specified in clause 5.4.3.3 of [12, TS 23.287] and clause 5.22.1.3.1 of [8, TS 38.321].
– Frequency resource assignment – bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214].
– Time resource assignment – 5 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 2; otherwise 9 bits when the value of the higher layer parameter sl-MaxNumPerReserve is configured to 3, as defined in clause 8.1.5 of [6, TS 38.214].
– Resource reservation period – bits as defined in clause 16.4 of [5, TS 38.213], where is the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; 0 bit otherwise.
– DMRS pattern – bits as defined in clause 8.4.1.1.2 of [4, TS 38.211], where is the number of DMRS patterns configured by higher layer parameter sl-PSSCH-DMRS-TimePatternList.
– 2nd-stage SCI format – 2 bits as defined in Table 8.3.1.1-1.
– Beta_offset indicator – 2 bits as provided by higher layer parameter sl-BetaOffsets2ndSCI and Table 8.3.1.1-2.
– Number of DMRS port – 1 bit as defined in Table 8.3.1.1-3.
– Modulation and coding scheme – 5 bits as defined in clause 8.1.3 of [6, TS 38.214].
– Additional MCS table indicator – as defined in clause 8.1.3.1 of [6, TS 38.214]: 1 bit if one MCS table is configured by higher layer parameter sl-Additional-MCS-Table; 2 bits if two MCS tables are configured by higher layer parameter sl- Additional-MCS-Table; 0 bit otherwise.
– PSFCH overhead indication – 1 bit as defined clause 8.1.3.2 of [6, TS 38.214] if higher layer parameter sl-PSFCH-Period = 2 or 4; 0 bit otherwise.
– Reserved – a number of bits as determined by higher layer parameter sl-NumReservedBits, with value set to zero.
Table 8.3.1.1-1: 2nd-stage SCI formats
|
Value of 2nd-stage SCI format field |
2nd-stage SCI format |
|
00 |
SCI format 2-A |
|
01 |
SCI format 2-B |
|
10 |
Reserved |
|
11 |
Reserved |
Table 8.3.1.1-2: Mapping of Beta_offset indicator values to indexes in Table 9.3-2 of [5, TS38.213]
|
Value of Beta_offset indicator |
Beta_offset index in Table 9.3-2 of [5, TS38.213] |
|
00 |
1st index provided by higher layer parameter sl-BetaOffsets2ndSCI |
|
01 |
2nd index provided by higher layer parameter sl-BetaOffsets2ndSCI |
|
10 |
3rd index provided by higher layer parameter sl-BetaOffsets2ndSCI |
|
11 |
4th index provided by higher layer parameter sl-BetaOffsets2ndSCI |
Table 8.3.1.1-3: Number of DMRS port(s)
|
Value of the Number of DMRS port field |
Antenna ports |
|
0 |
1000 |
|
1 |
1000 and 1001 |
[TS 38.212, clause 8.4.1.1]
SCI format 2-A is used for the decoding of PSSCH, with HARQ operation when HARQ-ACK information includes ACK or NACK, when HARQ-ACK information includes only NACK, or when there is no feedback of HARQ-ACK information.
The following information is transmitted by means of the SCI format 2-A:
– HARQ process number – bits.
– New data indicator – 1 bit.
– Redundancy version – 2 bits as defined in Table 7.3.1.1.1-2.
– Source ID – 8 bits as defined in clause 8.1 of [6, TS 38.214].
– Destination ID – 16 bits as defined in clause 8.1 of [6, TS 38.214].
– HARQ feedback enabled/disabled indicator – 1 bit as defined in clause 16.3 of [5, TS 38.213].
– Cast type indicator – 2 bits as defined in Table 8.4.1.1-1 and in clause 8.1 of [6, TS 38.214].
– CSI request – 1 bit as defined in clause 8.2.1 of [6, TS 38.214] and in clause 8.1 of [6, TS 38.214].
Table 8.4.1.1-1: Cast type indicator
|
Value of Cast type indicator |
Cast type |
|
00 |
Broadcast |
|
01 |
Groupcast when HARQ-ACK information includes ACK or NACK |
|
10 |
Unicast |
|
11 |
Groupcast when HARQ-ACK information includes only NACK |
12.2.7.1.3 Test description
12.2.7.1.3.1 Pre-test conditions
System Simulator:
– SS-NW
– NR Cell 1
– System information combination 14 as defined in TS 38.508-1 [4] clause 4.4.3.1 is used in NR Cell 1.
– NR-SS-UE
– NR-SS-UE1: Operating as NR sidelink communication transmitting and receiving device and uses GNSS as the synchronization reference source.
– GNSS simulator
– The GNSS simulator is started and configured for Scenario #1.
UE:
– UE is authorised to perform NR sidelink communication.
– The UE is equipped with a USIM Configuration FFS as defined in TS 38.508 [4] Table FFS.
– The UE uses GNSS as the synchronization reference source.
Preamble:
– The UE is in state 3N-B RRC_CONNECTED_with_SL as defined in TS 38.508-1 [4] subclause 4.4A on NR Cell 1with parameters Sidelink (On), Cast Type (Unicast), GNSS Sync (On).
12.2.7.1.3.2 Test procedure sequence
Table 12.2.7.1.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
Cause the UE to request a Sidelink CSI Report. Note: This step is triggered by MMI or AT command |
– |
– |
– |
– |
|
2 |
Check: Does the UE transmit a RRCReconfigurationSidelink message including IEs sl-CSI-RS-Config and sl-LatencyBoundCSI-Report on SL-SRB3? |
–> |
PC5 RRC: RRCReconfigurationSidelink |
1 |
P |
|
3 |
The NR-SS-UE1 transmits a RRCReconfigurationCompleteSidelink message on SL-SRB3. |
<– |
PC5 RRC: RRCReconfigurationCompleteSidelink |
– |
– |
|
4 |
Check: Does the UE transmit an SCI format 2-A to trigger SL CSI report and the ‘CSI request‘ field in the corresponding SCI format 2-A is set to 1. |
–> |
PSSCH (SCI format 2-A) |
2 |
P |
|
5 |
The NR-SS-UE1 sends a Sidelink CSI Reporting MAC CE. |
<– |
MAC CE (Sidelink CSI Reporting) |
– |
– |
12.2.7.1.3.3 Specific message contents
Table 12.2.7.1.3.3-1: SIB12-IEs-r16 (preamble)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.2-14A |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
SIB12-IEs-r16 ::= SEQUENCE { |
|||
|
sl-ConfigCommonNR-r16 SEQUENCE { |
|||
|
sl-CSI-Acquisition-r16 |
enabled |
||
|
} |
|||
|
} |
|||
Table 12.2.7.1.3.3-2: RRCReconfigurationSidelink (step 2, Table 12.2.7.1.3.2-1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition SL_CSI |
|||
|
Information Element |
Value/remark |
Comment |
Condition |
|
RRCReconfigurationSidelink ::= SEQUENCE { |
|||
|
criticalExtensions CHOICE { |
|||
|
rrcReconfigurationSidelink-r16 SEQUENCE { |
|||
|
sl-CSI-RS-Config-r16 CHOICE { |
|||
|
setup SEQUENCE { |
|||
|
sl-CSI-RS-FreqAllocation-r16 |
Any value |
||
|
sl-CSI-RS-FirstSymbol-r16 |
(3..12) |
||
|
} |
|||
|
} |
|||
|
sl-LatencyBoundCSI-Report-r16 |
(3..160) |
||
|
} |
|||
|
} |
|||
|
} |
|||
Table 12.2.7.1.3.3-3: RRCReconfigurationCompleteSidelink (step 3, Table 12.2.7.1.3.2-1)
FFS
12.2.7.2 Inter-carrier concurrent operation / Sidelink CSI reporting / Reporting
12.2.7.2.1 Test Purpose (TP)
(1)
with { UE has established PC5 RRC connection with peer UE and is configured by peer UE to perform CSI measurement. }
ensure that {
when { UE receives a SCI format 2-A to trigger SL CSI report. }
then { UE sends an CSI reporting MAC-CE to peer UE within SL CSI report latency requirement. }
}
12.2.7.2.2 Conformance requirements
References: The conformance requirements covered in the present TC are specified in: TS 38.331 [22], subclause 5.8.9.1, 5.8.10.2, 5.8.10.3, 5.8.10.4 and 5.8.10.5. Unless otherwise stated these are Rel-16 requirements.
[TS 38.331, clause 5.8.9.1.1]
Figure 5.8.9.1.1-1: Sidelink RRC reconfiguration, successful
Figure 5.8.9.1.1-2: Sidelink RRC reconfiguration, failure
The purpose of this procedure is to modify a PC5-RRC connection, e.g. to establish/modify/release sidelink DRBs, to (re-)configure NR sidelink measurement and reporting, to (re-)configure sidelink CSI reference signal resources and CSI reporting latency bound.
The UE may initiate the sidelink RRC reconfiguration procedure and perform the operation in sub-clause 5.8.9.1.2 on the corresponding PC5-RRC connection in following cases:
…
– the (re-)configuration of the sidelink CSI reference signal resources and CSI reporting latency bound.
In RRC_CONNECTED, the UE applies the NR sidelink communications parameters provided in RRCReconfiguration (if any). In RRC_IDLE or RRC_INACTIVE, the UE applies the NR sidelink communications parameters provided in system information (if any). For other cases, UEs apply the NR sidelink communications parameters provided in SidelinkPreconfigNR (if any). When UE performs state transition between above three cases, the UE applies the NR sidelink communications parameters provided in the new state, after acquisition of the new configurations. Before acquisition of the new configurations, UE continues applying the NR sidelink communications parameters provided in the old state.
[TS 38.331, clause 5.8.9.1.3]
The UE shall perform the following actions upon reception of the RRCReconfigurationSidelink:
…
1> if the RRCReconfigurationSidelink message includes the sl-CSI-RS-Config:
2> apply the sidelink CSI-RS configuration;
1> if the RRCReconfigurationSidelink message includes the sl-LatencyBoundCSI-Report:
2> apply the configured sidelink CSI report latency bound;
…
1> else:
2> set the content of the RRCReconfigurationCompleteSidelink message;
3> submit the RRCReconfigurationCompleteSidelink message to lower layers for transmission;
[TS 38.214, clause 8.2.1]
A UE transmits sidelink CSI-RS within a unicast PSSCH transmission if the following conditions hold:
– CSI reporting is enabled by higher layer parameter sl-CSI-Acquisition; and
– the ‘CSI request‘ field in the corresponding SCI format 2-A is set to 1.
…
[TS 38.214, clause 8.5.1.1]
The UE shall calculate CSI parameters (if reported) assuming the following dependencies between CSI parameters (if reported)
– CQI shall be calculated conditioned on the reported RI
The CSI reporting can be aperiodic (using [10, TS 38.321]). Table 8.5.1.1-1 shows the supported combinations of CSI reporting configurations and CSI-RS configurations and how the CSI reporting is triggered for CSI-RS configuration. Aperiodic CSI-RS is configured and triggered/activated as described in Clause 8.5.1.2.
Table 8.5.1.1-1: Triggering/Activation of CSI reporting for the possible CSI-RS Configurations
|
CSI-RS Configuration |
Aperiodic CSI Reporting |
|
Aperiodic CSI-RS |
Triggered by SCI. |
For CSI reporting, wideband CQI reporting is supported. A wideband CQI is reported for a single codeword for the entire CSI reporting band.
[TS 38.214, clause 8.5.1.2]
The CSI-triggering UE is not allowed to trigger another aperiodic CSI report for the same UE before the last slot of the expected reception or completion of the ongoing aperiodic CSI report associated with the SCI format 2-A with the ‘CSI request‘ field set to 1, where the last slot of the expected reception of the ongoing aperiodic CSI report is given by [10, TS38.321].
An aperiodic CSI report is triggered by an SCI format 2-A with the ‘CSI request‘ field set to 1.
A UE is not expected to transmit a sidelink CSI-RS and a sidelink PT-RS which overlap.
[TS 38.321, clause 5.22.1.7]
The Sidelink Channel State Information (SL-CSI) reporting procedure is used to provide a peer UE with sidelink channel state information as specified in clause 8.5 of TS 38.214 [7].
RRC configures the following parameters to control the SL-CSI reporting procedure:
– sl-LatencyBoundCSI-Report, which is maintained for each PC5-RRC connection.
The MAC entity maintains an sl-CSI-ReportTimer for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection. sl-CSI-ReportTimer is used for an SL-CSI reporting UE to follow the latency requirement signalled from a CSI triggering UE. The value of sl-CSI-ReportTimer is the same as the latency requirement of the SL-CSI reporting in sl-LatencyBoundCSI-Report configured by RRC.
The MAC entity shall for each pair of the Source Layer-2 ID and the Destination Layer-2 ID corresponding to a PC5-RRC connection which has been established by upper layers:
1> if the SL-CSI reporting has been triggered by an SCI and not cancelled:
2> if the sl-CSI-ReportTimer for the triggered SL-CSI reporting is not running:
3> start the sl-CSI-ReportTimer.
2> if the sl-CSI-ReportTimer for the triggered SL-CSI reporting expires:
3> cancel the triggered SL-CSI reporting.
2> else if the MAC entity has SL resources allocated for new transmission and the SL-SCH resources can accommodate the SL-CSI reporting MAC CE and its subheader as a result of logical channel prioritization:
3> instruct the Multiplexing and Assembly procedure to generate a Sidelink CSI Reporting MAC CE as defined in clause 6.1.3.35;
3> stop the sl-CSI-ReportTimer for the triggered SL-CSI reporting;
3> cancel the triggered SL-CSI reporting.
2> else if the MAC entity has been configured with Sidelink resource allocation mode 1:
3> trigger a Scheduling Request.
NOTE: The MAC entity configured with Sidelink resource allocation mode 1 may trigger a Scheduling Request if transmission of a pending SL-CSI reporting with the sidelink grant(s) cannot fulfil the latency requirement associated to the SL-CSI reporting.
12.2.7.2.3 Test description
12.2.7.2.3.1 Pre-test conditions
System Simulator:
– NR Cell
– NR Cell 1 is the serving cell.
– System information combination NR-14 as defined in TS 38.508-1 [4] clause 4.4.3.1.2 is used in NR cell 1.
– NR-SS-UE
– NR-SS-UE 1 operating as NR sidelink communication device on the resources (i.e. the frequency included in pre-configuration) that UE is expected to use for transmission and reception via PC5 interface.
– NR-SS-UE 1 uses NR Cell 1 as its synchronization reference source.
UE:
– UE is authorised to perform NR sidelink communication.
– UE uses NR Cell 1 as its synchronization reference source.
– The UE is equipped with below information in UE or in a USIM containing default values (as per TS 38.508-1 [4]) except for those listed in Table 12.2.7.2.3.1-1.
Table 12.2.7.2.3.1-1: UE/ USIM configuration
|
USIM field |
Priority |
Value |
Access Technology Identifier |
|
EFUST |
As per TS 36.508 [18] clause 4.9.3.4 |
||
|
EFVST |
Service n°119 is "available" |
||
|
EFV2XP_PC5 |
As per TS 38.508-1[4] clause 4.8.3.3.3 SL-PreconfigurationNR included in V2X data policy over PC5 is defined in 38.508-1[4] Table 4.10.1-1 |
Preamble:
– The UE is in state 3N-B as defined in TS 38.508-1 [4], subclause 4.4A, using generic procedure parameter Sidelink (On), Unicast (On), and Test Mode (On) as defined in TS 38.508-1 [4], subclause 4.5.1 and using UE initiated unicast mode NR sidelink communication procedure as defined in TS 38.508-1 [4] subclause 4.9.22.
12.2.7.2.3.2 Test procedure sequence
Table 12.2.7.2.3.2-1: Main behaviour
|
St |
Procedure |
Message Sequence |
TP |
Verdict |
|
|
U – S |
Message |
||||
|
1 |
The SS transmits an RRCReconfiguration message to enable SL CSI reporting |
<– |
NR RRC: RRCReconfiguration |
– |
– |
|
2 |
The UE transmits an RRCReconfigurationComplete message |
–> |
NR RRC: RRCReconfigurationComplete |
– |
– |
|
3 |
The NR-SS-UE 1 transmits an RRCReconfigurationSidelink message to provide sidelink CSI-RS resource and reporting configuration. |
<– |
NR PC5 RRC: RRCReconfigurationSidelink |
– |
– |
|
4 |
The UE transmits an RRCReconfigurationCompleteSidelink message |
–> |
NR PC5 RRC: RRCReconfigurationCompleteSidelink |
– |
– |
|
5 |
The NR-SS-UE 1 transmits a SCI format 2-A with CSI request = 1 and starts transmitting SL CSI-RS according to the SL CSI-RS resource configuration included in RRCReconfigurationSidelink message. |
<– |
SCI format 2-A |
– |
– |
|
6 |
Check: Does the UE transmit a SL CSI reporting MAC-CE before slot n+k? NOTE: Slot n is the slot that UE receives SCI format 2-A with CSI request = 1. k is the SL CSI report latency requirement (in slots) indicated by sl-LatencyBoundCSI-Report. |
–> |
MAC CE (Sidelink CSI Reporting) |
1 |
P |
12.2.7.2.3.3 Specific message contents
Table 12.2.7.2.3.3-1: RRCReconfiguration (Table 12.2.7.2.3.2-1, Step 1)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1-13 with condition SIDELINK |
||||
|
Information Element |
Value/remark |
Comment |
Condition |
|
|
RRCReconfiguration ::= SEQUENCE { |
||||
|
criticalExtensions CHOICE { |
||||
|
rrcReconfiguration SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
nonCriticalExtension SEQUENCE { |
||||
|
sl-ConfigDedicatedNR-r16 CHOICE { |
||||
|
setup |
SL-ConfigDedicatedNR specified in 38.508-1 Table 4.6.6-7 with condition SELECTED and SL_CSI_REPORT |
|||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
|
} |
||||
Table 12.2.7.2.3.3-2: RRCReconfigurationSidelink (Table 12.2.7.2.3.2-1, Step 3)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-3 with condition RX and SL_CSI |
Table 12.2.7.2.3.3-3: RRCReconfigurationCompleteSidelink (Table 12.2.7.2.3.2-1, Step 4)
|
Derivation Path: TS 38.508-1 [4], Table 4.6.1A-4 with condition TX |