8 Sidelink transport channels and control information
38.2123GPPMultiplexing and channel codingNRRelease 17TS
8.1 Sidelink broadcast channel
The processing for SL-BCH transport channel follows the BCH according to clause 7.1, with the following changes:
– In Clause 7.1, ‘maximum of one transport block every 80ms’ is replaced with ‘maximum of one transport block’.
– Clause 7.1.1 for PBCH payload generation is not performed.
– Clause 7.1.2 for scrambling is not performed.
– In clause 7.1.5, the rate matching output sequence length E = 1386 when higher layer parameter cyclicPrefix is configured, otherwise, E = 1782.
8.1.1 (void)
8.2 Sidelink shared channel
The processing for SL-SCH transport channel follows the UL-SCH according to clause 6.2, with the following changes:
– Rate matching of SL-SCH follows the rate matching according to clause 6.2.5 by setting
– Clause 6.2.7 is replaced by clause 8.2.1
8.2.1 Data and control multiplexing
Denote the coded bits for SL-SCH as.
Denote the coded bits for the 2nd-stage SCI, as .
Denote the multiplexed data and control coded bit sequence as , where G is the total number of coded bits for transmission.
Assuming that is the number of layers onto which the SL-SCH transport block is mapped, the multiplexed data and control coded bit sequence is obtained as follows:
Denote is modulation order of the 2nd-stage SCI.
if ,
for to
if
end if
if
end if
end for
end if
if ,
let
set
for to
for to
for to
if
else
// placeholder bit
end if
end for
end for
end for
for to
end for
end if
8.3 Sidelink control information on PSCCH
SCI carried on PSCCH is a 1st-stage SCI, which transports sidelink scheduling information.
8.3.1 1st-stage SCI formats
The fields defined in each of the 1st-stage SCI formats below are mapped to the information bits to as follows:
Each field is mapped in the order in which it appears in the description, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to .
8.3.1.1 SCI format 1-A
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]. Value ‘000’ of Priority field corresponds to priority value ‘1’, value ‘001’ of Priority field corresponds to priority value ‘2’, and so on.
– 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 the following:
– bits as configured by higher layer parameter sl-NumReservedBits, with value set to zero, if higher layer parameter indicationUEBScheme2 is not configured, or if higher layer parameter indicationUEBScheme2 is configured to ‘Disabled’;
– bits otherwise, with value set to zero.
– Conflict information receiver flag – 0 or 1 bit
– 1 bit if higher layer parameter indicationUEBScheme2 is configured to ‘Enabled’, where the bit value of 0 indicates that the UE cannot be a UE to receive conflict information and the bit value of 1 indicates that the UE can be a UE to receive conflict information as defined in Clause 16.3.0 of [5, TS 38.213];
– 0 bit otherwise.
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 |
SCI format 2-C |
|
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 |
8.3.2 CRC attachment
CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed.
8.3.3 Channel coding
Channel coding is performed according to clause 7.3.3.
8.3.4 Rate Matching
Rate matching is performed according to clause 7.3.4.
8.4 Sidelink control information on PSSCH
SCI carried on PSSCH is a 2nd-stage SCI, which transports sidelink scheduling information, and/or inter-UE coordination related information.
8.4.1 2nd-stage SCI formats
The fields defined in each of the 2nd-stage SCI formats below are mapped to the information bits to as follows:
Each field is mapped in the order in which it appears in the description, with the first field mapped to the lowest order information bit and each successive field mapped to higher order information bits. The most significant bit of each field is mapped to the lowest order information bit for that field, e.g. the most significant bit of the first field is mapped to .
8.4.1.1 SCI format 2-A
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 |
8.4.1.2 SCI format 2-B
SCI format 2-B is used for the decoding of PSSCH, with HARQ operation 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-B:
– 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].
– Zone ID – 12 bits as defined in clause 5.8.11 of [9, TS 38.331].
– Communication range requirement – 4 bits determined by higher layer parameter sl-ZoneConfigMCR-Index.
8.4.1.3 SCI format 2-C
SCI format 2-C is used for the decoding of PSSCH, and providing inter-UE coordination information or requesting inter-UE coordination information. SCI format 2-C can be used only for unicast.
The following information is transmitted by means of the SCI format 2-C:
– HARQ process number – 4 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]
– 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]
– Providing/Requesting indicator – 1 bit, where value 0 indicates SCI format 2-C is used for providing inter-UE coordination information and value 1 indicates SCI format 2-C is used for requesting inter-UE coordination information
If the ‘Providing/Requesting indicator’ field is set to 0, all the remaining fields are set as follows:
– Resource combinations – bits as defined in Clause 8.1.5A of [6, TS 38.214], where
– and is the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; otherwise
– is the number of subchannels in a resource pool provided by the higher layer parameter sl-NumSubchannel
– First resource location – 8 bits as defined in Clause 8.1.5A of [6, TS 38.214].
– Reference slot location – ( bits as defined in Clause 8.1.5A of [6, TS 38.214], where is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211].
– Resource set type – 1 bit, where value 0 indicates preferred resource set and value 1 indicates non-preferred resource set.
– Lowest subChannel indices – bits as defined in Clause 8.1.5A of [6, TS 38.214].
If the ‘Providing/Requesting indicator’ field is set to 1, all the remaining fields are set as follows:
– 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]. Value ‘000’ of Priority field corresponds to priority value ‘1’, value ‘001’ of Priority field corresponds to priority value ‘2’, and so on.
– Number of subchannels – bits as defined in Clause 8.1.4A of [6, TS 38.214].
– Resource reservation period – bits as defined in Clause 8.1.4A of [6, TS 38.214], where is the number of entries in the higher layer parameter sl-ResourceReservePeriodList, if higher layer parameter sl-MultiReserveResource is configured; 0 bit otherwise.
– Resource selection window location – bits as defined in Clause 8.1.4A of [6, TS 38.214], where is defined in Table 4.2-1 of Clause 4.2 of [4, TS 38.211].
– Resource set type – 1 bit, where value 0 indicates a request for inter-UE coordination information providing preferred resource set and value 1 indicates a request for inter-UE coordination information providing non-preferred resource set, if higher layer parameter determineResourceSetTypeScheme1 is configured to ‘UE-B’s request’; otherwise, 0 bit.
– Padding bits.
For operation in a same resource pool, zeros shall be appended to SCI format 2-C of which ‘Providing/Requesting indicator’ field is set to 1 until the payload size equals that of SCI format 2-C of which ‘Providing/Requesting indicator’ field is set to 0.
8.4.2 CRC attachment
CRC attachment is performed according to clause 7.3.2 except that scrambling is not performed.
8.4.3 Channel coding
Channel coding is performed according to clause 7.3.3.
8.4.4 Rate Matching
For 2nd-stage SCI transmission on PSSCH with SL-SCH, the number of coded modulation symbols generated for 2nd-stage SCI transmission prior to duplication for the 2nd layer if present, denoted as , is determined as follows:
where
– is the number of the 2nd-stage SCI bits
– is the number of CRC bits for the 2nd-stage SCI, which is 24 bits.
– is indicated in the corresponding 1st-stage SCI.
– is the scheduled bandwidth of PSSCH transmission, expressed as a number of subcarriers.
– is the number of subcarriers in OFDM symbol that carry PSCCH and PSCCH DMRS associated with the PSSCH transmission.
– is the number of resource elements that can be used for transmission of the 2nd-stage SCI in OFDM symbol , for and for , in PSSCH transmission, where = sl-lengthSymbols – 2, where sl-lengthSymbols is the number of sidelink symbols within the slot provided by higher layers as defined in [6, TS 38.214]. If higher layer parameter sl-PSFCH-Period = 2 or 4, = 3 if "PSFCH overhead indication" field of SCI format 1-A indicates "1", and = 0 otherwise. If higher layer parameter sl-PSFCH-Period = 0, . If higher layer parameter sl-PSFCH-Period is 1, .
– = –
– is the number of vacant resource elements in the resource block to which the last coded symbol of the 2nd-stage SCI belongs.
– is the coding rate as indicated by "Modulation and coding scheme" field in SCI format 1-A.
– is configured by higher layer parameter sl-Scaling.
The input bit sequence to rate matching is , where is the number of coded bits.
Rate matching is performed according to Clause 5.4.1 by setting .
The output bit sequence after rate matching is denoted as , where and is modulation order of the 2nd-stage SCI. A UE is not expected to have.
8.4.5 Multiplexing of coded 2nd-stage SCI bits to PSSCH
The coded 2nd-stage SCI bits are multiplexed onto PSSCH according to the procedures in Clause 8.2.1.
Annex <A> (informative):
Change history
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-05 |
RAN1#89 |
R1-1707082 |
Draft skeleton |
0.0.0 |
|||
|
2017-07 |
AH_NR2 |
R1-1712014 |
Inclusion of LDPC related agreements |
0.0.1 |
|||
|
2017-08 |
RAN1#90 |
R1-1714564 |
Inclusion of Polar coding related agreements |
0.0.2 |
|||
|
2017-08 |
RAN1#90 |
R1-1714659 |
Endorsed version by RAN1#90 as basis for further updates |
0.1.0 |
|||
|
2017-09 |
RAN1#90 |
R1-1715322 |
Capturing additional agreements on LDPC and Polar code from RAN1 #90 |
0.1.1 |
|||
|
2017-09 |
RAN#77 |
RP-171991 |
For information to plenary |
1.0.0 |
|||
|
2017-09 |
RAN1#90b |
R1-1716928 |
Capturing additional agreements on LDPC and Polar code from RAN1 NR AH#3 |
1.0.1 |
|||
|
2017-10 |
RAN1#90b |
R1-1719106 |
Endorsed as v1.1.0 |
1.1.0 |
|||
|
2017-11 |
RAN1#91 |
R1-1719225 |
Capturing additional agreements on channel coding, etc. |
1.1.1 |
|||
|
2017-11 |
RAN1#91 |
R1-1719245 |
Capturing additional agreements on DCI format, channel coding, etc. |
1.1.2 |
|||
|
2017-11 |
RAN1#91 |
R1-1721049 |
Endorsed as v1.2.0 |
1.2.0 |
|||
|
2017-12 |
RAN1#91 |
R1-1721342 |
Capturing additional agreements on UCI, DCI, channel coding, etc. |
1.2.1 |
|||
|
2017-12 |
RAN#78 |
RP-172668 |
Endorsed version for approval by plenary. |
2.0.0 |
|||
|
2017-12 |
RAN#78 |
Approved by plenary – Rel-15 spec under change control |
15.0.0 |
||||
|
2018-03 |
RAN#79 |
RP-180200 |
0001 |
– |
F |
CR capturing the Jan18 ad-hoc and RAN1#92 meeting agreements |
15.1.0 |
|
2018-04 |
RAN#79 |
MCC: correction of typo in DCI format 0_1 (time domain resource assignment) – higher layer parameter should be pusch-AllocationList |
15.1.1 |
||||
|
2018-06 |
RAN#80 |
RP-181172 |
0002 |
1 |
F |
CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting agreements |
15.2.0 |
|
2018-06 |
RAN#80 |
RP-181257 |
0003 |
– |
B |
CR to 38.212 capturing the RAN1#92bis and RAN1#93 meeting agreements related to URLLC |
15.2.0 |
|
2018-09 |
RAN#81 |
RP-181789 |
0004 |
– |
F |
CR to 38.212 capturing the RAN1#94 meeting agreements |
15.3.0 |
|
2018-12 |
RAN#82 |
RP-182523 |
0005 |
3 |
F |
Combined CR of all essential corrections to 38.212 from RAN1#94bis and RAN1#95 |
15.4.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0006 |
– |
F |
Correction of wrong implementation on frequency domain resource assignment bitwidth |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0008 |
– |
F |
Correction to UCI multiplexing |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0009 |
– |
F |
Correction on DCI format 2_3 for SUL cell in TS 38.212 |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0010 |
– |
F |
Corrections to TS38.212 |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0011 |
– |
F |
On bitwidth calculation for DCI fields using RRC parameter indicating maximum number of MIMO layers per serving cell |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0012 |
– |
F |
CR on zero-padding of DCI 1_1 in cross-carrier scheduling case |
15.5.0 |
|
2019-03 |
RAN#83 |
RP-190448 |
0013 |
– |
F |
Clarification on UL_SUL indicator field and SRS request field |
15.5.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0014 |
– |
F |
CR on correction to bitwidth of NNZC indicator |
15.6.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0015 |
– |
F |
Correction on DCI size alignment in TS 38.212 |
15.6.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0016 |
– |
F |
Correction on UL/SUL indicator in DCI format 0_0 |
15.6.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0017 |
– |
F |
Corrections to 38.212 including alignment of terminology across specifications |
15.6.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0018 |
– |
F |
CR on maximum modulation order configured for serving cell |
15.6.0 |
|
2019-06 |
RAN#84 |
RP-191282 |
0019 |
1 |
F |
Corrections to 38.212 including alignment of terminology across specifications from RAN1#97 |
15.6.0 |
|
2019-09 |
RAN#85 |
RP-191941 |
0020 |
– |
F |
Corrections to 38.212 including alignment of terminology across specifications in RAN1#98 |
15.7.0 |
|
2019-12 |
RAN#86 |
RP-192625 |
0021 |
– |
F |
CR on UL/SUL indicator in DCI format 0_1 |
15.8.0 |
|
2019-12 |
RAN#86 |
RP-192625 |
0022 |
– |
F |
Corrections to 38.212 including alignment of terminology across specifications in RAN1#98bis and RAN1#99 |
15.8.0 |
|
2019-12 |
RAN#86 |
RP-192636 |
0023 |
– |
B |
Introduction of NR based access to unlicensed spectrum into 38.212 |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192637 |
0024 |
– |
B |
Introduction of IAB into 38.212 |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192638 |
0025 |
– |
B |
Introduction of 5G V2X sidelink features into TS 38.212 |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192639 |
0026 |
– |
B |
Introduction of Physical Layer Enhancements for NR URLLC |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192641 |
0027 |
– |
B |
Introduction of Enhancements on NR MIMO |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192642 |
0028 |
– |
B |
Introduction of power saving in 38.212 |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192645 |
0029 |
– |
B |
Introduction of MR DC/CA |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192643 |
0030 |
– |
B |
Introduction of NR positioning suppport |
16.0.0 |
|
2019-12 |
RAN#86 |
RP-192635 |
0031 |
– |
B |
Introduction of two-step RACH |
16.0.0 |
|
2020-03 |
RAN#87-e |
RP-200185 |
0032 |
– |
F |
Corrections for Rel-16 NR-U after RAN1#100-e |
16.1.0 |
|
2020-03 |
RAN#87-e |
RP-200190 |
0033 |
– |
F |
Corrections for NR MIMO after RAN1#100-e |
16.1.0 |
|
2020-03 |
RAN#87-e |
RP-200188 |
0034 |
– |
F |
Corrections for URLLC after RAN1#100-e |
16.1.0 |
|
2020-03 |
RAN#87-e |
RP-200191 |
0035 |
– |
F |
Corrections for power saving after RAN1#100-e |
16.1.0 |
|
2020-03 |
RAN#87-e |
RP-200187 |
0036 |
– |
F |
Corrections on 5G V2X sidelink features after RAN1#100-e |
16.1.0 |
|
2020-06 |
RAN#88-e |
RP-200683 |
0038 |
– |
A |
CR on L1-RSRP report on PUSCH |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200693 |
0039 |
1 |
F |
Corrections for power saving |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200689 |
0040 |
1 |
F |
Corrections on 5G V2X sidelink features after RAN1#100bis-e and RAN1#101-e |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200694 |
0041 |
1 |
F |
Corrections in TS 38.212 for NR postioning |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200692 |
0042 |
1 |
F |
Corrections in TS 38.212 for NR MIMO |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200696 |
0043 |
– |
F |
Corrections for Rel-16 MR-DC/CA after RAN1#100bis-e |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200690 |
0044 |
1 |
F |
Corrections on NR eURLLC |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200687 |
0045 |
1 |
F |
Corrections for Rel-16 NR-U |
16.2.0 |
|
2020-06 |
RAN#88-e |
RP-200688 |
0046 |
– |
F |
Corrections for NR IAB |
16.2.0 |
|
2020-09 |
RAN#89-e |
RP-201814 |
0047 |
– |
F |
Correction on UCI bit sequence generation |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201803 |
0049 |
– |
A |
CR on PTRS for TS 38.212 |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201810 |
0050 |
– |
F |
Alignment of RRC parameter ps-RNTI |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201813 |
0051 |
– |
F |
CR to 38.212 on RRC parameter alignment for SCell dormancy |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201807 |
0052 |
– |
F |
Corrections on 5G V2X sidelink features |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201809 |
0053 |
– |
F |
Corrections to MIMO enhancements |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201805 |
0054 |
– |
F |
Corrections to MIMO enhancements |
16.3.0 |
|
2020-09 |
RAN#89-e |
RP-201808 |
0055 |
– |
F |
Corrections on NR eURLLC |
16.3.0 |
|
2020-12 |
RAN#90-e |
RP-202390 |
0056 |
– |
F |
RRC IE name fix to dynamic frequency domain resource allocation type selection (Rel-15 origin) |
16.4.0 |
|
2020-12 |
RAN#90-e |
RP-202384 |
0057 |
– |
F |
Correction on Transmission configuration indication in DCI format 1_2 |
16.4.0 |
|
2020-12 |
RAN#90-e |
RP-202398 |
0058 |
– |
F |
Alignment CR for TS 38.212 |
16.4.0 |
|
2021-03 |
RAN#91-e |
RP-210052 |
0059 |
– |
F |
CR on DMRS |
16.5.0 |
|
2021-03 |
RAN#91-e |
RP-210049 |
0060 |
– |
F |
Correction to description of FDRA field size in DCI 0_0 |
16.5.0 |
|
2021-03 |
RAN#91-e |
RP-210049 |
0061 |
– |
F |
Correction to description of FDRA field interpretation in DCI 0_1 |
16.5.0 |
|
2021-03 |
RAN#91-e |
RP-210050 |
0062 |
– |
F |
Correction on Sidelink Broadcast channel |
16.5.0 |
|
2021-03 |
RAN#91-e |
RP-210049 |
0063 |
– |
F |
Correction on LBT Type and CP Extension Indication for Semi-Static Channel Occupancy |
16.5.0 |
|
2021-03 |
RAN#91-e |
RP-210059 |
0064 |
– |
F |
Alignment CR for TS 38.212 |
16.5.0 |
|
2021-06 |
RAN#92-e |
RP-211252 |
0066 |
– |
F |
38.212 CR on DAI size determination for DCI format 1_1/1-2 in CA |
16.6.0 |
|
2021-06 |
RAN#92-e |
RP-211236 |
0067 |
– |
F |
Corrections on parameter of MCS table set to qam256 |
16.6.0 |
|
2021-06 |
RAN#92-e |
RP-211234 |
0068 |
– |
D |
Alignment CR for TS 38.212 (post RAN1#104bis-e) |
16.6.0 |
|
2021-06 |
RAN#92-e |
RP-211234 |
0069 |
– |
F |
Correction on HARQ-ACK codebook RRC parameter |
16.6.0 |
|
2021-06 |
RAN#92-e |
RP-211236 |
0070 |
– |
F |
Correction on SRS resource set configuration in TS 38.212 |
16.6.0 |
|
2021-06 |
RAN#92-e |
RP-211243 |
0071 |
– |
F |
Alignment CR for TS 38.212 (post RAN1#105-e) |
16.6.0 |
|
2021-09 |
RAN#93-e |
RP-211843 |
0072 |
– |
F |
Correction on SRS resource set configuration for DCI format 0_2 in TS 38.212 |
16.7.0 |
|
2021-09 |
RAN#93-e |
RP-211841 |
0074 |
– |
A |
Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) |
16.7.0 |
|
2021-09 |
RAN#93-e |
RP-211850 |
0075 |
– |
F |
Alignment CR for TS 38.212 |
16.7.0 |
|
2021-12 |
RAN#94-e |
RP-212959 |
0076 |
– |
F |
Correction on mapping between priority field value and priority value in SCI format 1-A |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212961 |
0077 |
– |
F |
Changes of channel access types tables in TS 38.212 |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212961 |
0078 |
– |
F |
Corrections on CG-UCI multiplexing in TS38.212 |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212958 |
0080 |
– |
A |
Clarify UCI bitwidth and UCI mapping order for non-PMI based CSI feedback |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-213238 |
0081 |
– |
F |
Clarification on KNZ to codepoint mapping for eType II CSI |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212958 |
0083 |
– |
A |
Rel-15 editorial corrections for TS 38.212 (mirrored to Rel-16) |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212964 |
0084 |
– |
F |
Alignment CR for TS 38.212 |
16.8.0 |
|
2021-12 |
RAN#94-e |
RP-212967 |
0085 |
– |
B |
Introduction of features to extend current NR operation to 71 GHz |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212982 |
0086 |
– |
B |
Introduction of NR DL 1024QAM for FR1 |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212973 |
0087 |
– |
B |
Introduction of Coverage Enhancements |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212979 |
0088 |
– |
B |
Introduction of NR Multicast and Broadcast Services |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212966 |
0089 |
– |
B |
Introduction of Further enhancements on MIMO for NR |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212969 |
0090 |
– |
B |
Introduction of NR non-terrestrial networks (NTN) |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212972 |
0091 |
– |
B |
Introduction of Rel-17 UE power saving enhancements |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212968 |
0092 |
– |
B |
Introduction of Rel-17 enhanced IIoT and URLLC |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212980 |
0093 |
– |
B |
Introduction of NR dynamic spectrum sharing enhancements |
17.0.0 |
|
2021-12 |
RAN#94-e |
RP-212978 |
0094 |
– |
B |
Introduction of NR sidelink enhancement |
17.0.0 |
|
2022-03 |
RAN#95-e |
RP-220269 |
0096 |
– |
A |
Correction of NZC partitioning in eType II CSI |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220248 |
0098 |
– |
A |
Correction on Rel-16 UE dormancy adaptation |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220252 |
0099 |
– |
F |
Corrections on enhanced IIoT and URLLC in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220262 |
0100 |
– |
F |
Corrections on NR sidelink enhancement in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220257 |
0101 |
– |
F |
Corrections on coverage enhancements in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220263 |
0102 |
– |
F |
Corrections on NR Multicast and Broadcast Services in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220256 |
0103 |
– |
F |
Corrections on UE power saving enhancements in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220251 |
0104 |
– |
F |
Correction on extension of current NR operation to 71 GHz in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220264 |
0105 |
– |
F |
Corrections on NR dynamic spectrum sharing enhancements in 38.212 |
17.1.0 |
|
2022-03 |
RAN#95-e |
RP-220250 |
0106 |
– |
F |
Corrections on Further enhancements on MIMO for NR in TS 38.212 |
17.1.0 |
|
2022-06 |
RAN#96 |
RP-221617 |
0108 |
– |
A |
Clarification of TPMI indication for UL full power transmission |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221602 |
0109 |
– |
F |
Corrections on enhanced IIoT and URLLC in 38.212 |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221612 |
0110 |
– |
F |
Corrections on NR Multicast and Broadcast Services in 38.212 |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221606 |
0111 |
– |
F |
Corrections on UE power saving enhancements in 38.212 |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221601 |
0112 |
– |
F |
Correction on extension of current NR operation to 71 GHz in 38.212 |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221600 |
0113 |
– |
F |
Corrections on Further enhancements on MIMO for NR in TS 38.212 |
17.2.0 |
|
2022-06 |
RAN#96 |
RP-221599 |
0115 |
– |
A |
Rel-16 editorial corrections for TS 38.212 (mirrored to Rel-17) |
17.2.0 |
|
2022-09 |
RAN#97-e |
RP-222403 |
0116 |
1 |
F |
CR on DCI size for Rel-17 NTN HARQ in 38.212 |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222400 |
0117 |
– |
F |
CR on the description of the SRS resource set indication for PUSCH repetition |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222401 |
0118 |
– |
F |
CR on ChannelAccess-Cpext in Fallback DCI |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222413 |
0119 |
– |
F |
CR on DCI size alignment for Cross-carrier scheduling from SCell to PCell |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222406 |
0120 |
– |
F |
Corrections on UE Power Saving Enhancements for NR in TS 38.212 |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222412 |
0121 |
– |
F |
Corrections on NR Multicast and Broadcast Services in 38.212 |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222411 |
0122 |
– |
F |
Correction on NR sidelink enhancement |
17.3.0 |
|
2022-09 |
RAN#97-e |
RP-222422 |
0123 |
– |
F |
Rel-17 editorial corrections for TS 38.212 |
17.3.0 |