Nr V2x Uu-based Sidelink Control

Abstract

To provide sidelink (SL) resource configurations and allocation schemes controlled by a Uu interface or the like.SOLUTION: In radio resource control configurations, in the case of broadcast sidelink transmission, the scheduling DCI may indicate the time domain resources for PSCCH or PSSCH. The time domain resource for a PSCCH or PSSCHUu interface may be jointly assigned by the scheduling DCI, e.g., one time domain resource assignment may be used for PSCCH or PSSCH. For example, UE may receive one time domain resource assignment indicating the resources for PSCCH and PSSCH. When the PSCCH and PSSCH are FDM-ed, the UE may transmit the PSCCH and PSSCH on the allocated time resources using different frequency resources.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] Cross - reference to Related Applications This application claims priority to U.S. Provisional Patent Application No. 62 / 737,2 57, filed on September 27, 2018, and U.S. Provisional Patent Application No. 62 / 754,3 26, filed on November 1, 2018, the contents of which are hereby incorporated by reference in their entirety.

Background Art

[0002] The applications of Vehicle - To - Everything (V2X) have advanced significantly. As it progresses, the transmission of short messages about the status data of the vehicle itself for basic safety needs to be extended along with the transmission of larger - scale messages, which includes raw sensor data, vehicle intention data, cooperation, confirmation of future maneuvers, etc. The requirements expected to meet the data rate, latency, reliability, communication range, and speed for these latest applications are more stringent.

[0003]

[0004] Regarding enhanced V2X (eV2X) services, 3GPP (registered trademark) has clarified 25 use cases and related requirements in TR 22.886 (GPP TR 22.886 Study on enhancement of 3GPP Support for 5G V2X Services, Release 15, V15.2.0).

[0004] The set of regulatory requirements is classified into four use - case groups, namely, vehicle platooning, extended sensors, advanced driving, and remote driving use cases, along with TS 22.186 (GP ​P TS 22.186 Enhancement of 3GPP support for V2X scenarios (Stage 1), It is specified in Release 15, V15.3.0. The detailed description of the performance requirements for each use case group is specified in TS 22.186.

[0005] In LTE V2X of Release 14, for example, basic requirements for V2X services are supported with respect to road safety services, such as low-latency and high-reliability message exchange between vehicles, and support for infrastructure that enhances safety and efficiency.

[0006] In order to meet the latency requirements and adapt to the high Doppler spread and high density of vehicles for V2X communication, sidelink transmission modes 3 and 4 are specified in TS 36.213 (3GPP TS 36.213 Physical layer procedures, Release 15, V15.2.0).

[0007] Mode 3 uses a centrally centralized eNB scheduler. The vehicle user equipment (UE) and the eNB communicate using the Uu interface. The eNB uses downlink control information (DCI) format 5A to schedule the physical sidelink control channel (PSCCH) and the physical sidelink shared channel (PSSCH) of the vehicle UE for sidelink communication.

[0008] In NR V2X, sidelink resource allocation modes 1 and 2 have been agreed upon. In mode 1, the base station schedules the sidelink resources used by the UE for sidelink transmission. In mode 2, the UE determines the sidelink resources to be used for sidelink transmission from the sidelink resources configured by the base station or pre-configured sidelink resources.

[0009] Mode 1 supports the gNB to allocate sidelink resources to both the dedicated sidelink carrier and the shared license carrier between Uu and the sidelink through the Uu interface. The resources used for sidelink transmission can be dynamically allocated, pre-configured by RRC, or based on activation and deactivation.

SUMMARY OF THE INVENTION

[0010] Disclosed herein are various sidelink resource configurations and allocation schemes that may be controlled by an interface such as the Uu interface. For example, mechanisms related to resource allocation in the sidelink, namely, 1) RRC configuration, 2) DCI signaling, 3) sidelink transmission schedule, 4) groupcast sidelink design, or 5) sidelink measurement and reporting, which may be u-based.

[0011] RRC configured static resource allocation for IDRINK transmission, 3) Broadcast side Activation / deactivation (e.g., activation or deactivation) based semi-persistent resource allocation for link transmission, 4) Uni cast side link transmission activation / deactivation based semi-persistent resource allocation, or 5) Groupcast side link transmission activation / deactivation based semi-persistent resource allocation, etc. can be mentioned 。

[0012] In particular, DCI signaling, the case where the gNB schedules side link transmission, the design of the groupcast side link, and the mechanisms for side link measurement and reporting will be further disclosed.

[0013] This summary is presented in a simplified form to introduce a selection of concepts for implementing the inventions further described below. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited by limitations such as solving any or all of the disadvantages described in any part of this disclosure.

Brief Description of Drawings

[0014]

[0015]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9A

Figure 9B

Figure 9C

Figure 9D

Figure 9E

Figure 9F

Figure 9G

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15A

Figure 15B

Figure 16

Figure 17

Figure 18

Figure 19

Figure 20

Figure 21

Figure 22

[0016] Problem 1: In New Radio (NR) V2X Mode 1, the base station Schedules sidelink resources to be used by the UE for NR V 2X provides dynamic resource allocation, activation / deactivation, and Supports activation-based resource allocation, and RRC (pre)configured resource allocation To support the above mentioned NR V2X resource allocation techniques, Mechanisms need to be put in place.

[0017] In LTE mode 3, the time domain resources used for V2X sidelink transmission are determined in advance. The pool-based resource allocation should be based on the configured subframe resource pool. The granularity of the allocation is within a subframe. In NR V2X, the sidelink is aperiodic. Both intermittent and periodic traffic needs to be supported. The subframe-based resource allocation design may not meet the latency requirements. Therefore, in order to support low latency, an extension to the Uu-based resource allocation is necessary.

[0018] Problem 2: In NR V2X mode 1, broadcast, groupcast, or unicast sidelink communication needs to be supported as well. In LTE V2X, only broadcast sidelink communication is supported. Therefore, in NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer.

[0019] In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In NR V2X, a mechanism for allocating resources for groupcast or unicast sidelink communication needs to be introduced. The UE may be composed of multiple resources for broadcast, groupcast, or unicast sidelink communication. When the UE receives a scheduling grant, the UE needs to be able to determine which type of sidelink communication the received grant is used for. A mechanism to solve this problem needs to be introduced.

[0020] In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer. In LTE V2X, the receiving UE continues to attempt to decode the physical sidelink control channel (PSCCH) on each candidate PSCCH resource configured by the upper layer.​ That is, since V2X reception resources are relatively sparse in time, although it is acceptable in LTE, considering the NR V2X requirement where the density of V2X reception monitoring opportunities may be very high, in NR, the power efficiency may be very poor. For example, in NR V2X, UEs may be configured using multiple resources for broadcast, groupcast, and unicast sidelink communications. Furthermore, the NR V2X reception resource configuration needs to consider not only periodic traffic but also aperiodic traffic where the resource sets may need to be configured differently. Therefore, if the current LTE design for receiving PSCCH is applied to NR as it is, it may cause a huge power consumption problem in NR, and at the same time, the number of PSCCH blind decoding may increase significantly. This document discloses various sidelink resource configurations and allocation schemes that may be controlled by interfaces such as the Uu interface. Uu-based dynamic resource grant allocation for sidelink Broadcast sidelink transmission Broadcast sidelink transmission: In NR V2X, a node such as a gNB (e.g., gNB 201 in FIG. 3 or FIG. 9A) or a gNB may dynamically allocate resources used by UEs (e.g., UEs in FIG. 3 or FIG. 9A) for broadcast sidelink transmission. As disclosed in this document, UEs can, through RRC configuration and DCI signaling, obtain resources for broadcast sidelink transmission

[0021]

[0022] ​ A source may be allocated. When the UE receives scheduling DCI, the UE may broadcast control and data using the resources scheduled by the sidelink. The detailed resource allocation scheme is as follows. It may be used for control and data broadcast using the resources scheduled by the sidelink. The detailed resource allocation scheme is as follows.

[0023] Detailed design of RRC configuration: The UE may be configured using one or more Information Elements (IEs), where each IE indicates the configuration information of the NR V2X sidelink transmission resource. Different IEs are disclosed herein to support broadcast, groupcast, and unicast sidelink transmissions in NR V2X. For example, NR-SL-Resource-Broadcast, NR-SL-Resource-Groupcast, or NR-SL-Resource-Unicast may be used to configure the information of the sidelink transmission resource. Alternatively, the same IE (e.g., NR-SL-Resource) may be used, where the type of sidelink transmission (e.g., broadcast, groupcast, or unicast) is indicated by the IE. It may be configured using one or more Information Elements (IEs), where each IE indicates the configuration information of the NR V2X sidelink transmission resource. For broadcast, groupcast, and unicast sidelink transmissions in NR V2X, different IEs are disclosed herein. For example, NR-SL-Resource-Broadcast, NR-SL-Resource-Groupcast, or NR-SL-Resource-Unicast may be used to configure the information of the sidelink transmission resource. Alternatively, the same IE (e.g., NR-SL-Resource) may be used, where the type of sidelink transmission (e.g., broadcast, groupcast, or unicast) is indicated by the IE. icast may be used to configure the information of the sidelink transmission resource. Alternatively, the same IE (e.g., NR-SL-Resource) may be used, where the type of sidelink transmission (e.g., broadcast, groupcast, or unicast) is indicated by the IE. For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource- For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource- For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource-

[0024] For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource- For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource- For broadcast sidelink transmission, the IE NR-SL-Resource or NR-SL-Resource-Broadcast may carry the configuration information for sidelink control or sidelink data transmission. The UE may receive the broadcast signal, e.g., through the OSI or through the common or dedicated RRC configuration on the Uu interface, and obtain the NR-SL-Resource or NR-SL-Resource- It may be configured using ce-Broadcast. The IE NR-S disclosed in this specification L-Resource or NR-SL-Resource-Broadcast is 1 ) type of sidelink transmission, 2) type of carrier, 3) numerology of the resource , 4) UE transmitting the broadcast, 5) mask used for scrambling the scheduling DCI ing, 6) index of the candidate resources, 7) time domain resources at the time of candidate resource configuration , 8) number of repetitions and redundant versions, 9) frequency domain resources at the time of candidate resource configuration , or 10) beam sweeping, etc., and may carry the RRC configuration .

[0025] RRC configuration indicating the type of sidelink transmission. For example, if the same IE NR-SL-Res ource is used for all types of sidelink transmission, the RRC configuration NR-SL-Co mmuncationType may be Broadcast, G roupcast, or Unicast.

[0026] RRC configuration indicating the type of carrier. For example, the RRC configuration NR-SL-Carrier Type may be used. If NR-SL-CarrierType is configured as "shared", the UE determines that the sidelink resource allocation is for a shared license carrier between Uu and sidelink. If NR-SL-CarrierTyp e is configured as "dedicated", the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0027] RRC configuration indicating the numerology of the sidelink transmission resources. For example, 15, 3 ​​​0. RRC configuration NR-SL-Numerology that may be, for example, 60 KHz. Or, the numerology may be configured for each Bandwidth Part (BWP). Or, the numerology may be configured for each Bandwidth Part (BWP).

[0028] RRC configuration indicating the side-link ID of the UE that transmits broadcasts over the side link. In the case of broadcast side-link transmission, the UE may be configured using the UE ID in the side link, either as the source ID or the destination ID. For example, the UE may be configured using the Sidelink Broadcast Transmission RNTI (SL-BT-RNTI) that should be used as the source ID. The UE may be configured using the Sidelink Broadcast Reception RNTI (SL-BR-RNTI) that should be used as the destination ID, which may be associated with different services for each destination ID. In the case of broadcast side-link transmission, the UE may be configured using the UE ID in the side link, either as the source ID or the destination ID. For example, the UE may be configured using the Sidelink Broadcast Transmission RNTI (SL-BT-RNTI) that should be used as the source ID. For example, the UE may be configured using the Sidelink Broadcast Transmission RNTI (SL-BT-RNTI) that should be used as the source ID. The UE may be configured using the Sidelink Broadcast Transmission RNTI (SL-BT-RNTI) that should be used as the source ID. The UE may be configured using the Sidelink Broadcast Reception RNTI (SL-BR-RNTI) that should be used as the destination ID, which may be associated with different services for each destination ID. The UE may be configured using the Sidelink Broadcast Reception RNTI (SL-BR-RNTI) that should be used as the destination ID, which may be associated with different services for each destination ID. The UE may be configured using the Sidelink Broadcast Reception RNTI (SL-BR-RNTI) that should be used as the destination ID, which may be associated with different services for each destination ID.

[0029] When Sidelink Control Information (SCI) for broadcast side-link transmission is generated, the scrambling ring sequence for the SCI may be initialized jointly by the source ID and the destination ID. Alternatively, the scrambling ring sequence for the SCI may be initialized by one of the source ID and the destination ID, and the other of them may be indicated in the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. When Sidelink Control Information (SCI) for broadcast side-link transmission is generated, the scrambling ring sequence for the SCI may be initialized jointly by the source ID and the destination ID. When Sidelink Control Information (SCI) for broadcast side-link transmission is generated, the scrambling ring sequence for the SCI may be initialized jointly by the source ID and the destination ID. Alternatively, the scrambling ring sequence for the SCI may be initialized by one of the source ID and the destination ID, and the other of them may be indicated in the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload.

[0030] ​RRC configuration indicating the mask used for the scrambling ring of scheduling DCI. For example, the UE may be configured using the SLBroadcast-RNTI or the SL-RNTI. The gNB may generate and transmit scheduling DCI for the UE, together with the CRC scrambled by the configured SLBroadcast-RNTI or SL-RNTI. The UE may decode the DCI by using the configured SLBroadcast-RNTI or SL-RNTI.

[0031] RRC configuration indicating the index of candidate resources. The UE may be configured using multiple configurations of sidelink transmission resources, for example, multiple resource pools. Each configuration of resources may be associated with one dedicated resource index, for example, the RRC configuration NR-SL-Resource-Index. The UE may determine the configuration of resources to be used for sidelink transmission through the DCI that schedules the sidelink transmission.

[0032] RRC configuration indicating candidate time domain resources for resource configuration, for example, the time domain resources of each resource pool. As disclosed, the candidate time domain resources for broadcast sidelink transmission for each candidate resource may be configured using the following variations.

[0033] Variation 1 - Candidate time domain resources: The UE may be configured using one or more bitmaps indicating candidate time domain resources for sidelink transmission by the RRC configuration. The bitmap may indicate resources within a subframe, a slot, a mini-slot, or a symbol. For example, the bitmap may be used to indicate resources within a symbol. ​ When being, it may be mapped to symbols during a certain time interval. For example, {b s , b s- 1,..., b1, b0} is mapped to b s for the first symbol and b0 for the last symbol . When the bitmap is used to indicate resources within a minislot, it may be mapped to minislots during a certain time interval. For example, {b m , b m-1 ,..., b1, b0 } is mapped to b m for the first minislot and b0 for the last minislot. Alternatively , a two - level mapping may be used to save mapping bits. A 2 - bit sequence may be configured by the RRC configuration. For example, {a f , a f-1 ,...a1, a0 } is mapped to a f for the first subframe or slot during a certain time interval and a0 for the last subframe or slot, and is mapped to each subframe or each slot. {c s , c s-1 ,..., c1, c0} is mapped to symbols within a frame or slot or, {c m , c m-1 ,..., c1, c0} is mapped to mini slots within a frame or slot

[0034] When the UE receives DCI carrying a scheduling grant for sidelink transmission, the UE may start transmission from the next available time resource within the configured candidate time resources . A minimum time gap constraint may be applied for the UE to switch from the reception mode to the transmission mode , and the UE shall use the minimum time within the configured candidate time resources The transmission may be performed starting from the next available time resource after the gap.

[0035] Alternatively, the UE may determine whether the time resources to be used for sidelink transmission within the configured candidate time resources are available. The offset value may be configured to indicate the inter-scheduling resource. The offset value may be signaled by the DCI carrying the synchronization grant. Time resource for drink transmission and scheduling grant DCI are used to transmit or the offset value indicates the offset between the time resource The time resource for transmission and the next available one after the minimum time gap in the configured candidate time resources It may also indicate an offset between the available time resources.

[0036] Variation 2 - Candidate time domain resources: The UE may use The UE may be dynamically signaled by the DCI regarding the time resources to be used. It does not have to be configured with candidate time domain resources through RRC configuration. When the DCI carrying the ring grant is used for broadcast sidelink transmission, may indicate inter-resources.

[0037] RRC configuration showing beam sweeping information for broadcast sidelink transmission , the transmitting UE 202 broadcasts information in multiple directions using multiple beams. The UE may decide how many beam sweeps it needs to perform and the corresponding resources. You must be aware of the

[0038] Variation 1 - Beam Sweeping Information: The gNB determines the beam sweeping that the UE needs to perform. For example, the UE may determine the number of beam sweeps through RRC configuration. In another variation, the number of beam sweeps may be configured using the number or maximum number of beam sweeps. The UE may signal the beam sweeping configuration. To a Node B (e.g., a base station such as a gNB or eNB) to assist the NB in ​​making decisions. Such assistance information may be provided to the V2X service of interest, e.g. E is the UE capability, expressed as the number of beam sweeping directions that can be covered simultaneously, in power saving mode. The preference may include one or more of: UE scheduling preferences including UE call preferences, etc.

[0039] If a UE is configured to broadcast information through k directions / beams, Assuming that the UE is configured with k directions of beamforming through RRC configuration and DCI signaling, For band sweeping, we define k configurations of time and frequency resources, e.g. , k UEs may be assigned time and frequency resources for each direction / beam. If broadcasting in multiple directions is required, the UE will typically use a single beam with each beam pointing in one direction. The UE needs to form k beams (hence directions / beams) based on the k-th direction. To cover all directions, we may perform beam sweeping of the k shaped beams. stomach.

[0040] Alternatively, the UE may be assigned one configuration of time and frequency resources. Possibly, the allocated time and frequency resources are used for all beams. The UE may divide the allocated time resource equally into k parts and Each part may be used for one beam. Another possibility is that the allocated time and frequency resources may be used for one beam. For example, the UE may use time resources across all beam sweeping directions as follows. In Option 1 of the first variant of beam sweeping, the UE may use the time and frequency resources allocated for the first beam sweeping, and for the remaining beam sweepings, use the next available time resources in the resource pool configured with the same duration and the same frequency resources as those used for the first beam sweeping. For example, assume that the UE is configured to use time resources within a mini-slot and the UE is configured to use mini-slot n for the first beam sweeping. The UE may use mini-slots n + 1 to n + k - 1 in the configured resource pool for the remaining beam sweepings. The beams used for beam sweeping may be indicated by the gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. In Option 2 of the first variant of beam sweeping, the UE may evenly slice time resources in a round-robin basis across all beam sweeping directions and use the same one frequency resource in each direction. In Option 3 of the first variant of beam sweeping, the UE may autonomously determine the slicing method of time- frequency resources in both the time domain and the frequency domain across all beam sweeping directions.

[0041] Modification Example 2 - Beam Sweeping Information: The UE may determine the number of beam sweepings that the UE needs to perform for broadcast side link transmission. The UE may report k beam sweeping values to the gNB. The gNB may schedule time resources for the UE for broadcast side link transmission. For broadcast side link transmission, the UE may report k beam sweeping values to the gNB. The gNB may schedule time resources for the UE for broadcast side link transmission. For broadcast side link transmission, the UE may report k beam sweeping values to the gNB. The gNB may schedule time resources for the UE for broadcast side link transmission. For broadcast side link transmission, the UE may report k beam sweeping values to the gNB. The gNB may schedule time resources for the UE for broadcast side link transmission.

[0042] The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resources within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by the gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE 202 based on sensing or discovery. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. The beams used for beam sweeping may be indicated by the gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE 202 based on sensing or discovery. The beams used for beam sweeping may be indicated by the gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE 202 based on sensing or discovery. The beams used for beam sweeping may be indicated by the gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE 202 based on sensing or discovery.

[0043] Candidate frequency domain resources for resource configuration, for example, the frequency domain resources of each resource pool. RRC configuration indicating a cell. The UE may be configured using one or more SL-BWPs Alternatively, the UE may be configured using one or more candidate frequency resources for broadcast sidelink transmission. The candidate frequency resources may be configured using the following variations.

[0044] Variation 1 - Candidate frequency domain resources: The UE may be configured using contiguous frequency resources as candidate frequency resources for sidelink broadcast transmission. The frequency resources may be configured within an RB or within a subchannel, e.g., within an RBG. For example, the UE may be configured using parameters StartRB and LengthRB indicating the starting and length values (SLV) of the RB for candidate frequency resources through the RRC configuration. Alternatively, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The UE may be configured using one candidate frequency resource for both sidelink control information (SCI) transmission and sidelink data transmission. The UE may also be configured using two candidate frequency resources, e.g., StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH, respectively, for sidelink control information (SCI) transmission and sidelink data transmission. and LengthRBG-PSSCH for both sidelink control information (SCI) transmission and sidelink data transmission.

[0045] Variation 2 - Candidate frequency domain resources: The UE may be configured using ​As candidate frequency resources, non - contiguous frequency resources may be used. The frequency resources may be configured within an RB or within a sub - channel, e.g., within an RBG. The non - contiguous frequency resources may be composed of a plurality of SLVs, e.g., StartR BG_1 and LengthRBG_1, StartRBG_2 and LengthRB G_2, …, StartRBG_m and LengthRBG_m. Alternatively, the non - contiguous frequency resources may be composed of a start value and a bitmap, e.g., StartRBG and {b m-1 ,…, b1 ,b0}. Assuming that the UE is configured using the StartRBG set to k, b is mapped to RBG k and b0 is mapped to RBG k + m. m-1 is mapped to RB G k and b0 is mapped to RBG k + m.

[0046] In the case of the above - mentioned variations, the UE may provide assistance information, e.g., in a sidelink UE information message, in a UE assistance information message, or in a similar message, to assist the NB in properly configuring the UE. Such assistance information may include UE capabilities, whether the UE is interested in the transmission or reception of V2X communication or in the implementation of V2X discovery, the carrier frequency at that time, the V2X services in which the UE is interested, whether the UE is interested in the transmission or reception of V2X communication or in the implementation of V2X discovery, and a specific BWP within the carrier frequency at that time, etc. In LTE, procedures are used to obtain UE power - saving Physical Downlink Shared Channel / Physical Uplink Shared Channel:PDSCH (For PUSCH) may notify the E-UTRAN of, for example, the preferred bandwidth configuration, while receiving sidelink communication or discovery using the sidelink UE information message receiving V2X sidelink communication, and requesting allocation or release of transmission resources for V2X sidelink discovery gaps Note that the UE may notify the NB whether it is interested or no longer interested in any of the above.

[0047] The above RRC configuration may be configured through IE NR-SL-Resource or NR-SL-Re source-Broadcast, or note that some of the above RRC configuration may be configured by other IEs used for sidelink configuration

[0048] Detailed design of DCI signaling: The UE may be dynamically signaled a scheduling grant for broadcast sidelink transmission through DCI. For example a new DCI format, e.g., DCI format 3, may be used to schedule the Physical Sidelink Control Channel (PSCCH) and Physical Sidelink Shared Channel (PSSCH) for broadcast sidelink transmission. To support dynamic scheduling of resources for broadcast, groupcast, or unicast sidelink transmission the gNB may dynamically transmit scheduling DCI. To identify the scheduling DCI ​​​​To distinguish, different RNTIs may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. For example, SLBroadcast-RNTI, SLGroup-RNTI may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission, respectively. For example, SLBroadcast-RNTI, SLGroup-RNTI may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission, respectively. For example, SLBroadcast-RNTI, SLGroup-RNTI SLUnicast-RNTI may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission, respectively. For example, SLBroadcast-RNTI, SLGroup-RNTI SLUnicast-RNTI may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission, respectively. For example, SLBroadcast-RNTI, SLGroup-RNTI The UE may be configured through RRC with SLBroadcast-RNTI, SLGr oup-RNTI, SLUnicast-RNTI.

[0049] As a variant, one RNTI may be used to scramble the cyclic redundancy check (CRC) of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. For example, the same RNT I, for example, SL-RNTI, may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. The fields in the scheduling DCI may be used to indicate the DCI used for scheduling broadcast, groupcast, or unicast sidelink transmission. As a variant, one RNTI may be used to scramble the cyclic redundancy check (CRC) of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. For example, the same RNT I, for example, SL-RNTI, may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. The fields in the scheduling DCI may be used to indicate the DCI used for scheduling broadcast, groupcast, or unicast sidelink transmission. I, for example, SL-RNTI, may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. The fields in the scheduling DCI may be used to indicate the DCI used for scheduling broadcast, groupcast, or unicast sidelink transmission. I, for example, SL-RNTI, may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. The fields in the scheduling DCI may be used to indicate the DCI used for scheduling broadcast, groupcast, or unicast sidelink transmission. I, for example, SL-RNTI, may be used to scramble the CRC of DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. The fields in the scheduling DCI may be used to indicate the DCI used for scheduling broadcast, groupcast, or unicast sidelink transmission.

[0050] To schedule resources for broadcast sidelink transmission, the scheduling DCI includes: 1) a BWP indicator field, 2) a resource indicator field, 3) a sidelink type indicator field, 4) a carrier type indicator field, 5) a time domain resource management field, 6) a beam sweeping information field To schedule resources for broadcast sidelink transmission, the scheduling DCI includes: 1) a BWP indicator field, 2) a resource indicator field, 3) a sidelink type indicator field, 4) a carrier type indicator field, 5) a time domain resource management field, 6) a beam sweeping information field To schedule resources for broadcast sidelink transmission, the scheduling DCI includes: 1) a BWP indicator field, 2) a resource indicator field, 3) a sidelink type indicator field, 4) a carrier type indicator field, 5) a time domain resource management field, 6) a beam sweeping information field To schedule resources for broadcast sidelink transmission, the scheduling DCI includes: 1) a BWP indicator field, 2) a resource indicator field, 3) a sidelink type indicator field, 4) a carrier type indicator field, 5) a time domain resource management field, 6) a beam sweeping information field 7) frequency domain resource allocation field, or 8) slot format indicator It may carry information such as the Slot Format Indicator (SFI) field. Disclose that.

[0051] Bandwidth Part (BWP) indicator field. The UE shall, through RRC configuration, A scheduling DCI may be configured with multiple BWPs for drink communication. It may indicate the BWP to be used for broadcast sidelink transmissions. The Joule DCI indicates to the UE that it will switch from the current BWP to a new BWP. The BWP indicator field indicates that the UE is transmitting broadcast sidelink transmissions. Indicates the index of the BWP that needs to be implemented or to which the UE needs to switch. Assuming that the UE is configured with four BWPs, "00" is the first configuration. A 2-bit BWP with "01" indicating a configured BWP and "02" indicating a second configured BWP. WP indicator fields may be used. Some fields are bitmap-specific. It may also be used to indicate the initial BWP and the default BWP. For example, "00" may indicate the initial BWP used, for example, for discovery and synchronization. Alternatively, "00" may indicate the default BWP. In this example, "00" indicates the initial BWP, while "01" indicates the default BWP. There is a match.

[0052] Resource indicator field. The UE may, through RRC, For example, it may be configured using multiple resource pools. It is also possible to indicate the index of the configuration of the resources to be used for sidelink transmission in the loadcast. Assume that when the UE is configured using eight configurations of resources, for example, from configuration 0 to configuration 7, in a state where "000" indicates configuration 0 and "001" indicates configuration 1, a 3-bit resource indicator field may be used.

[0053] Sidelink type indicator field. The scheduling DCI may indicate the type of sidelink transmission. For example, in a state where "00" indicates that the DCI schedules broadcast sidelink transmission, "01" indicates that the DCI schedules groupcast sidelink transmission, and "10" indicates that the DCI schedules unicast sidelink transmission, a 2-bit sidelink type indicator field may be used. CI schedules, a 2-bit sidelink type indicator field may be used.

[0054] Carrier type indicator field. The UE may be dynamically informed of the type of carrier by 1 bit in the scheduling DCI. For example, when the carrier type indicator field is set to "0", the UE determines that the sidelink resource allocation is for a shared license carrier between Uu and sidelink, and when the carrier type indicator field is set to "1", the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0055] Time domain resource allocation field. The UE may signal the time domain resources scheduled using the following variants through the DCI.

[0056] Variant Example 1 - Time Domain Resource Allocation: The UE may be configured using one or more candidate resources through the RRC configuration. The scheduling DCI may indicate the time domain resources among the candidate resources to be used for broadcast sidelink transmission.

[0057] To determine the start of the time domain resources, the UE may be signaled with a time offset indicator. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for broadcast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may be informed of a slot / subframe (or, in other words, a slot or a subframe) offset to determine from which slot / subframe the time domain resources start. Then, the UE may be informed of the index of the start symbol / mini-slot (or, in other words, a slot or a mini-slot) within the slot / subframe to determine the start point within the slot / subframe. In one example, the two-level time offset may be indicated separately by two DCI fields, for example, through a slot-level offset indicator field and a start symbol indicator field. In another example, the two-level time offset is indicated by one DCI field.

[0058] In another example, the two-level time offset is indicated by one DCI field. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. To determine the duration of the time - domain resource, a bitmap or the length of the duration may be indicated by the scheduling DCI. In one example, the UE may be signaled a bitmap. The bitmap may indicate which time resources within the radio resource control (RRC) configured candidate resources are used for broadcast sidelink transmission. In another example, the UE may be signaled the length of the time - domain resource, for example, l. Then, the UE may use l consecutive resource units within the RRC configured candidate resources for broadcast sidelink transmission. The resource unit may be within a sub - frame, a slot, a mini - slot, or a symbol. The fields for indicating the start and duration of the time - domain resource may also be signaled through one DCI field. For example, it may be pre - determined or pre - configured. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission.

[0059] There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission.

[0060] There may be. For example, the table may include a combination of a slot level offset and a start symbol, and each combination may be pre - determined or (pre -)configured by the RRC configuration in a state associated with an index. The UE may signal one index by the scheduling DCI through the DCI field. The UE can determine the time domain start point by finding the corresponding two - level offset from the table. The examples shown in this specification may also be applicable to dynamic resource allocation for group - cast sidelink transmission or unicast sidelink transmission. configured. The configured table may include combinations of the start of a time-domain resource and its duration, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE may determine the time-domain resource by finding the corresponding start or duration value from the table. For example, the configured table may include combinations of the start of a time-domain resource and its duration, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE may determine the time-domain resource by finding the corresponding start or duration value from the table. For example, the configured table may include combinations of the start of a time-domain resource and its duration, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE may determine the time-domain resource by finding the corresponding start or duration value from the table. For example, the configured table may include combinations of the start of a time-domain resource and its duration, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE may determine the time-domain resource by finding the corresponding start or duration value from the table. For example, the configured table may include combinations of the start of a time-domain resource and its duration, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE may determine the time-domain resource by finding the corresponding start or duration value from the table.

[0061] Variant 2 - Time-domain resource allocation: The UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the UE may not be configured with candidate resources through the RRC. The UE may be dynamically informed of the time-domain resources for broadcast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, and duration of the time-domain resource. The slot / subframe offset may be related to the slot / subframe in which the DCI is received. Each of the above parameters may be indicated by different DCI fields or jointly indicated by DCI fields. For example, the time-domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI.

[0062] In the case of broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one time-domain resource and determine the time-domain resources for all directions according to some predefined rules. Alternatively, the UE may be informed of the time-domain resources for each direction respectively. For example, the UE may be informed of the time-domain resources for each direction respectively. In the case of broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one time-domain resource and determine the time-domain resources for all directions according to some predefined rules. Alternatively, the UE may be informed of the time-domain resources for each direction respectively. For example, the UE may be informed of the time-domain resources for each direction respectively. In the case of broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one time-domain resource and determine the time-domain resources for all directions according to some predefined rules. Alternatively, the UE may be informed of the time-domain resources for each direction respectively. For example, the UE may be informed of the time-domain resources for each direction respectively. In the case of broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one time-domain resource and determine the time-domain resources for all directions according to some predefined rules. Alternatively, the UE may be informed of the time-domain resources for each direction respectively. For example, the UE may be informed of the time-domain resources for each direction respectively. The UE may be informed of multiple start and duration values of the domain resources. Alternatively, the UE may be informed of the gap between the time domain resources for the first - direction transmission and the time domain resources for the remaining directions. For broadcast side - link transmission, the scheduling DCI may indicate the time domain resources for the PSCCH or PSSCH as shown in FIG. 1. The time domain resources for the PSCCH or PSSCH may be allocated together by the scheduling DCI. For example, one time domain resource allocation may be used for the PSCCH or PSSCH. For example, in one approach, the UE may receive one time domain resource allocation indicating the resources for the PSCCH and PSSCH. If the PSCCH and

[0063] PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are allocated together by the scheduling DCI. For example, one time domain resource allocation may be used for the PSCCH or PSSCH. For example, in one approach, the UE may receive one time domain resource allocation indicating the resources for the PSCCH and PSSCH. If the PSCCH and PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources. PSSCH are FDM, the UE may use different frequency resources to transmit the PSCCH and PSSCH on the allocated time resources.

[0064] If the PSCCH or PSSCH is TDM or transmitted on different time resources, the UE may determine the time resources for the PSCCH or PSSCH respectively from among the scheduled time resources. For example, the UE may use the number of symbols associated with the PSCCH, e.g., k symbols, which are statically configured by the RRC or the number of symbols may be dynamically indicated by the scheduling DCI. Next, if the PSCCH and PSSCH are TDM, the UE uses the first k symbols to transmit the PSCCH within the allocated time If the PSCCH or PSSCH is TDM or transmitted on different time resources, the UE may determine the time resources for the PSCCH or PSSCH respectively from among the scheduled time resources. For example, the UE may use the number of symbols associated with the PSCCH, e.g., k symbols, which are statically configured by the RRC or the number of symbols may be dynamically indicated by the scheduling DCI. Next, if the PSCCH and PSSCH are TDM, the UE uses the first k symbols to transmit the PSCCH within the allocated time associated with the PSCCH, e.g., k symbols, which are statically configured by the RRC or the number of symbols may be dynamically indicated by the scheduling DCI. Next, if the PSCCH and PSSCH are TDM, the UE uses the first k symbols to transmit the PSCCH within the allocated time associated with the PSCCH, e.g., k symbols, which are statically configured by the RRC or the number of symbols may be dynamically indicated by the scheduling DCI. Next, if the PSCCH and PSSCH are TDM, the UE uses the first k symbols to transmit the PSCCH within the allocated time associated with the PSCCH, e.g., k symbols, which are statically configured by the RRC or the number of symbols may be dynamically indicated by the scheduling DCI. Next, if the PSCCH and PSSCH are TDM, the UE uses the first k symbols to transmit the PSCCH within the allocated time The remaining symbols may be used to transmit the SSCH. Alternatively, if the bandwidth of the PSCCH is smaller than that of the PSSCH, the UE may use the first k symbols within the allocated time resource to transmit the PSCCH and the PSSCH according to the frequency-domain resource allocation, and further use the remaining symbols to transmit the PSSCH. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. The remaining symbols may be used to transmit the SSCH. Alternatively, if the bandwidth of the PSCCH is smaller than that of the PSSCH, the UE may use the first k symbols within the allocated time resource to transmit the PSCCH and the PSSCH according to the frequency-domain resource allocation, and further use the remaining symbols to transmit the PSSCH. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission.

[0065] In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In another approach, the UE may receive an allocation of one time-domain resource indicating the resource for the PSSCH, and the UE may correspondingly determine the time-domain resource for the PSCCH, and vice versa. The scheduled PSCCH and PSSCH may be in the same slot or in different slots. For example, the UE may be statically configured using the offset between the PSCCH and the PSSCH by the RRC configuration, where the RRC configuration may include both the slot-level offset and the symbol-level offset. The UE may be informed of the time-domain resource allocation for the PSSCH by the scheduling DCI and determine the time-domain resource for the associated PSCCH based on the configured offset. The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission.

[0066] Alternatively, the time-domain resources for the PSCCH and the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time-domain resources for the PSCCH and the PSSCH, respectively. Alternatively, the time-domain resources for the PSCCH and the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time-domain resources for the PSCCH and the PSSCH, respectively. Alternatively, the time-domain resources for the PSCCH and the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time-domain resources for the PSCCH and the PSSCH, respectively. For example, a DCI field for time domain resource allocation for PSCCH, and a DCI field for time domain resource allocation for PSS CH, and each field may indicate an index corresponding to an entry in the R RC configuration. For example, the UE may be RRC configured using the information element PSCCH_AllocationList and the information element PSSCH_Alloc ationList separately.

[0067] The information element PSCCH_AllocationList is a list of time domain resource allocation(s) configured for PSCCH, for example, a list of information elements PS CCH_TimeDomainResourceAllocation, and in this case, each indexed row constitutes a slot offset (e.g., kx), start and length indices between the scheduling DCI and the scheduled PSCCH SLIV, etc. An example of the information element PSCCH-TimeDomainReso urceAllocationList is shown in FIG. 17. Table 1 shows an example assuming 3 bits are used for the PSCCH time domain resource allocation field. The examples shown in this specification for PSCCH are also applicable to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission. In the scenario of groupcast sidelink transmission or unicast sidelink transmission, a two-stage SCI may be used. In the scenario where a two-stage SCI is used, the UE may, for example, use the DCI field first-stage PSCCH time domain resource allocation field and the information

[0068] In the scenario of groupcast sidelink transmission or unicast sidelink transmission, a two-stage SCI may be used. In the scenario where a two-stage SCI is used, the UE may, for example, use the DCI field first-stage PSCCH time domain resource allocation field, and the information ​​​​​​Report element First_Stage_PSCCH_TimeDomainResourceA Through the llocation, the time domain resource allocation for the transmission of the first-stage SCI is clearly known / it may be configured using it (in other words, known or configured). In this case, the slot offset kx represents the slot offset between the scheduling DCI and the scheduled first-stage PSCCH. The UE may be informed of the time domain resource allocations for the transmission of the second-stage SCI and PSSCH together, for example, through the DCI field PSSCH time domain resource allocation field. Then, the UE can derive the time domain resources used for the second-stage SCI transmission or the time domain resources used for the PSSCH transmission from the received PSSCH time domain resource allocation field, for example, using the method presented above. SCI and PSSCH transmissions. Next, the UE can derive, for example, the time domain resources used for the second-stage SCI transmission or the time domain resources used for the PSSCH transmission from the received PSSCH time domain resource allocation field, for example, using the method presented above. resource allocation field, for example, using the method presented above.

[0069]

Table 1

[0070] The information element PSSCH_AllocationList is a list of time domain resource allocations (one or more of them) configured for the PSSCH, for example, a list of information elements PS SCH_TimeDomainResourceAllocation. At this time, each indexed row may constitute a slot offset (for example, ky), start and length indicators, start and length indicator values (Start and Length In dicator Value: SLIV), etc. Regarding the slot offset ky, a single application start and length indicators, start and length indicator values (Start and Length In dicator Value: SLIV), etc. Regarding the slot offset ky, a single application In Loach, the slot offset ky may be the slot offset between the scheduling DCI and the scheduled PSSCH. In another approach, the slot offset ky may be the slot offset between the scheduled PSCCH and the scheduled PSSCH. An example of the information element PSSCH-TimeDomain ResourceAllocationList is shown in FIG. 18. Table 2 shows an example when it is assumed that 4 bits are used for the PSSCH time domain resource allocation field. The examples shown in this specification may also be applied to dynamic resource allocation for group cast sidelink transmission and unicast sidelink transmission. In the scenario of group cast sidelink transmission or unicast sidelink transmission,

[0071] a two-stage SCI may be used. In the scenario where a two-stage SCI is used, the slot offset ky may be the slot offset between the scheduled first-stage PSCCH transmission and the scheduled PSSCH transmission, or the slot offset between the scheduled first-stage PSCCH transmission and the transmissions of the scheduled second-stage PSCCH and PSSCH scheduled together.

[0072]

Table 2

[0073] Beam sweeping information field. The scheduling DCI may indicate the number of beam sweeping operations that the UE may need to perform. The UE may perform beam ​The value of the number of beam sweeps may be dynamically signaled by I. Alternatively, R RC is a multiple of the number of beam sweeps, with each value associated with an index A UE may configure a potential value. An index may be signaled to the UE to determine whether it should use the beamforming The beams used for beam sweeping may be determined by the gNB Alternatively, the beam used for beam sweeping may be represented by The determination may be made autonomously by the transmitting UE 202 based on routing or discovery.

[0074] Frequency domain resource allocation field. To determine the number of resource regions, the UE determines the minimum resource block to be used. Block (RB), Resource Block Group (RBG) or The UE may be informed of the subchannel information. The UE may select the minimum RB, RBG or subchannel. Alternatively, the UE may be signaled the index of the frequency domain resource allocation. The minimum RB, RBG or subchannel to be allocated and the RRC configuration formula of candidate frequency domain resources The offset between the minimum RB, RBG or subchannel may be signaled. The offset may be within an RB, an RBG, or a subchannel.

[0075] To determine the range of the frequency domain resource, use a bitmap or a frequency domain resource The width of the bitmap may be indicated by the scheduling DCI. The bitmap may be signaled based on the RRC configured candidate frequency resources. This indicates which frequency resources in the FREQ 0x10001 ... are used for broadcast sidelink transmissions. In another example, the UE may be signaled the width of the frequency domain resource, e.g., w. Then, the UE may use consecutive RBs, RBGs or sub-channels of w for broadcast sidelink transmission. For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions. For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions.

[0076] For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions. For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions. For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions. For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled different frequency domain resources for transmissions in different directions.

[0077] For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. For broadcast sidelink transmission, the scheduling DCI may indicate the frequency domain resources for both the PSCCH or the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are often allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively.

[0078] Slot format indicator (SFI) field. As shown in Figure 2, the SFI may be introduced to support sidelink transmission. The symbols used for sidelink transmission within a slot may be denoted as "S". It may be configured using dedicated sidelink carriers. Slot format indicator (SFI) field. As shown in Figure 2, the SFI may be introduced to support sidelink transmission. The symbols used for sidelink transmission within a slot may be denoted as "S". It may be configured using dedicated sidelink carriers. Slot format indicator (SFI) field. As shown in Figure 2, the SFI may be introduced to support sidelink transmission. The symbols used for sidelink transmission within a slot may be denoted as "S". It may be configured using dedicated sidelink carriers. In the case of a UE, the UE may perform sidelink transmission using only symbols designated as "S". Alternatively, the UE may perform sidelink transmission using symbols designated as "S" or "U". For a UE configured using a shared sidelink carrier between Uu and sidelink, the UE may perform sidelink transmission using only symbols designated as "S". The symbol designated as "X" may be used as a gap for switching between the transmission mode and reception mode of the UE.

[0079] If there is a mismatch between the RRC-configured candidate time resource and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and may not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE may not consider symbol k in slot m as a candidate time resource. When the UE determines the time resource for broadcast sidelink transmission, the UE may skip symbol k in slot m. If the candidate time resource is within a mini-slot and there is a mismatch in some of the symbols within the mini-slot, the UE may skip the entire mini-slot and may not perform sidelink transmission thereon. Alternatively, the UE may skip only the mismatched symbols and perform sidelink transmission using the matching symbols within the mini-slot.

[0080] Unicast Sidelink Transmission Unicast Sidelink Transmission: In NR V2X, a gNB or a node such as a gNB The RRC may dynamically allocate resources used by the UE for unicast sidelink communication. In the case of transmitting UE202, the UE may be allocated resources for unicast sidelink transmission through RRC configuration and DCI signaling. In the case of receiving UE203, the UE may be allocated resources for unicast sidelink reception through RRC configuration and DCI signaling. When the gNB schedules transmission on the sidelink, the transmitting UE202 or the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources or beams used for reception. A similar concept may also be applied to groupcast sidelink transmission. The detailed resource allocation scheme is as follows. In the case of the transmitting UE202, the UE may be allocated resources for unicast sidelink transmission through RRC configuration and DCI signaling. In the case of the receiving UE203, the UE may be allocated resources for unicast sidelink reception through RRC configuration and DCI signaling. When the gNB schedules transmission on the sidelink, the transmitting UE202 or the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources or beams used for reception. A similar concept may also be applied to groupcast sidelink transmission. The detailed resource allocation scheme is as follows. In the case of unicast sidelink transmission, IE NR-SL-Resource or NR-SL-Resource-Unicast may carry configuration information for both sidelink control and sidelink data transmission. The UE may be configured using NR-SL-Resource or NR-SL-Resource-Unicast through broadcast signals, such as OSI, or through common or dedicated RRC configurations via the Uu interface. IE NR-SL-Resource or NR-SL-Resource-Unicast may: 1) carry

[0081] Detailed design of RRC configuration: For unicast sidelink transmission, IE NR-SL-Resource or NR-SL-Resource-Unicast may carry configuration information for both sidelink control and sidelink data transmission. The UE may be configured using NR-SL-Resource or NR-SL-Resource-Unicast through broadcast signals, such as OSI, or through common or dedicated RRC configurations via the Uu interface. IE NR-SL-Resource or NR-SL-Resource-Unicast may carry configuration information for both sidelink control and sidelink data transmission. The UE may be configured using NR-SL-Resource or NR-SL-Resource-Unicast through broadcast signals, such as OSI, or through common or dedicated RRC configurations via the Uu interface. IE NR-SL-Resource or NR-SL-Resource-Unicast may carry configuration information for both sidelink control and sidelink data transmission. The UE may be configured using NR-SL-Resource or NR-SL-Resource-Unicast through broadcast signals, such as OSI, or through common or dedicated RRC configurations via the Uu interface. IE NR-SL-Resource or NR-SL-Resource-Unicast may: 1) carry Type of drink transmission, 2) Type of carrier, 3) Numerology of resources, 4) UE that transmits broadcasts, 5) Mask used in the scrambling ring of scheduling DCI 6) Index of candidate resources, 7) Candidate time domain of resource configuration Resources, 8) Number of repeated and redundant versions, or 9) Candidate frequency of resource configuration Number domain resources, etc., may carry RRC configurations.

[0082] RRC configuration indicating the type of sidelink transmission. For example, if the same IE NR-SL-Res ource is used for all sidelink transmission types, the RRC configuration NR-SL-Co mmuncationType may be Broadcast, G roupcast, or Unicast.

[0083] RRC configuration indicating the type of carrier. For example, the RRC configuration NR-SL-Carrier Type may be used. If NR-SL-CarrierType is configured as "shared", the UE determines that the sidelink resource allocation is for a shared license carrier between Uu and sidelink. If NR-SL-CarrierTyp e is configured as "dedicated", the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0084] RRC configuration indicating the numerology of sidelink transmission resources. For example, the RRC configuration NR-SL-Numerology may be 15, 3 0, 60KHz, etc.

[0085] RRC configuration indicating the unicast UE ID in sidelink. Unicast sidelink In the case of unicast sidelink communication, the UE may be configured using a UE ID, for example, a sidelink unicast RNTI (SL-U-RNTI). In the case of transmitting UE 202, the UE may use the SL-U-RNTI as the source ID. In the case of receiving UE 203, the UE may use the SL-U-RNTI as the destination ID. To perform unicast sidelink communication, the UE needs to know the information of the paired UE. In the case of transmitting UE 202, the ID of the paired UE is the destination ID. In the case of receiving UE 203, the ID of the paired UE is the source ID. The UE may be informed of the ID of the paired UE, for example, a sidelink unicast paired RNTI (SL-UP-RNTI), through the RRC configuration or through the scheduling DCI. When the SCI for unicast sidelink transmission is generated, the scrambling sequence for the SCI may be initialized jointly by the source ID and the destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by one of the source ID and the destination ID, and the other of them may be indicated in the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. RRC configuration indicating the mask used for the scrambling sequence of the scheduling DCI. For example, the UE may be configured using the SLUnicast-RNTI or the SL-RNTI.

[0086] To perform unicast sidelink communication, the UE needs to know the information of the paired UE. In the case of transmitting UE 202, the ID of the paired UE is the destination ID. In the case of receiving UE 203, the ID of the paired UE is the source ID. The UE may be informed of the ID of the paired UE, for example, a sidelink unicast paired RNTI (SL-UP-RNTI), through the RRC configuration or through the scheduling DCI. For example, the UE may be configured using the SLUnicast-RNTI or the SL-RNTI. When the SCI for unicast sidelink transmission is generated, the scrambling sequence for the SCI may be initialized jointly by the source ID and the destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by one of the source ID and the destination ID, and the other of them may be indicated in the SCI payload.

[0087] For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. When the SCI for unicast sidelink transmission is generated, the scrambling sequence for the SCI may be initialized jointly by the source ID and the destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by one of the source ID and the destination ID, and the other of them may be indicated in the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload. For example, the destination ID is used to scramble the SCI, and the source ID is carried by the SCI payload.

[0088] RRC configuration indicating the mask used for the scrambling sequence of the scheduling DCI. For example, the UE may be configured using the SLUnicast-RNTI or the SL-RNTI. It is okay. The gNB may generate and transmit scheduling DCI to the UE together with the CRC scrambled by the configured SL Unicast - RNTI or SL - RNTI. The DCI may be decoded by using the configured SL Unicast - RNTI or SL - RNTI.

[0089] An RRC configuration indicating the index of candidate resources. The UE may be configured using multiple configurations of sidelink transmission resources, e.g., multiple resource pools. Each configuration of the resources may be associated with one dedicated resource index, e.g., the RRC configuration NR - SL - Resource - Index. The UE may determine the configuration of the resources used for sidelink transmission through the DCI that schedules the sidelink transmission.

[0090] An RRC configuration indicating the candidate time - domain resources of the resource configuration, e.g., the time - domain resources of each resource pool. As disclosed, the candidate time - domain resources for unicast sidelink transmission for each candidate resource may be configured using the following variations.

[0091] Variation 1 - Candidate time - domain resources: The UE may be configured by one or more bitmaps indicating candidate time - domain resources for sidelink transmission according to the RRC configuration. The bitmaps may indicate resources within a subframe, a slot, a mini - slot, or a symbol. For example, when the bitmap is used to indicate resources within a symbol, it may be mapped to the symbols within a certain time interval, e.g., {b 1, b 1, …, b1, b0} may be mapped to b s 1 in the first symbol, b s- 1, …, b1, b0 in the first symbol, where b sis mapped to b0 for the last symbol . When the bitmap is used to indicate resources within a mini - slot, it may be mapped to mini - slots during a certain time interval . For example, {b m , b m-1 , …, b1, b0 } is mapped to b m for the first mini - slot and to b0 for the last mini - slot. Alternatively , a two - level mapping may be used to save mapping bits. A 2 - bit sequence may be configured by the RRC configuration. For example, {a , a f , …a1, a0 f-1} is mapped to a for the first sub - frame or slot during a certain time interval and to a0 for the last sub - frame f or slot, and is mapped to each sub - frame or each slot. {c , s , c s-1 , …, c1, c0} is mapped to symbols within a frame or slot or, {c m , c m-1 , …, c1, c0} is mapped to mini - slots within a frame or slot .

[0092] When the UE receives DCI that carries a scheduling grant for sidelink transmission , the UE may perform transmission starting from the next available time resource within the configured candidate time resources. A minimum time gap constraint may be applied for the UE to switch from the receiving mode to the transmitting mode , and the UE may perform transmission starting from the next available time resource after the minimum time gap within the configured candidate time resources.

[0093] Alternatively, the UE may use the time for sidelink transmission within the configured candidate time resources It may be configured using an offset value indicating an intermediate resource. The offset value may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources. It may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources. It may be configured using an offset value indicating an intermediate resource. The offset value may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources. It may be configured using an offset value indicating an intermediate resource. The offset value may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources. It may be configured using an offset value indicating an intermediate resource. The offset value may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources. It may be configured using an offset value indicating an intermediate resource. The offset value may be signaled by DCI carrying a scheduling grant. The offset value may indicate an offset between the time resource for sidelink transmission and the time resource used to transmit the scheduling grant DCI, or the offset value may indicate an offset between the time resource for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources.

[0094] Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources used for unicast sidelink transmission. The UE may not be configured using candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources used for unicast sidelink transmission. Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources used for unicast sidelink transmission. The UE may not be configured using candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources used for unicast sidelink transmission. Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources used for unicast sidelink transmission. The UE may not be configured using candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources used for unicast sidelink transmission. Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources used for unicast sidelink transmission. The UE may not be configured using candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources used for unicast sidelink transmission. Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources used for unicast sidelink transmission. The UE may not be configured using candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources used for unicast sidelink transmission.

[0095] The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k The RRC configuration indicating the number of repetitions and redundancy versions (RV). To improve reliability, the UE may repeat unicast sidelink transmission. The UE may be configured by the gNB through the RRC configuration using the number of repetitions and RV. In one example, the UE may be configured with one repetition number (e.g., k) in the RRC configuration. In another example, the UE may be configured with multiple repetition numbers (e.g., k1, k2,..., k i ) through RRC configuration. The repeating indicator field of log 2(i ) bits is used to indicate the number of repetitions of the scheduled transmission to the UE. The repeating indicator field of log may be signaled by scheduling DCI.

[0096] Table 3 shows an example of a repetition indicator when assuming i = 4. In the example shown in Table 3, when the repetition indicator field is set to "00", it indicates that the number of repetitions is k1. In another example, when the repetition indicator field is set to "00", it indicates that there is no repetition performed by the UE, and also, "01", "10 ", "11" indicate that the number of repetitions is k1, k2, k3 respectively. Similar concepts may be applied to groupcast sidelink transmission and broadcast sidelink transmission. When the UE repeats the initial transmission, inter-slot repetition or intra-slot repetition may be performed. The UE may use the same symbol or mini-slot in subsequent slots for repetition. Assuming that the initial transmission is scheduled in slot n, in one example, the UE may transmit k repetitions in slots n + 1, n + 2,..., n + k, and in another example, the UE may transmit k repetitions in slots n + m, n + 2*m,..., n + k*m. At this time, m is the gap between the initial transmission and the first repetition. In this example, m is within the unit of a slot. In another example, m may be within the unit of a mini-slot

[0097] or within the unit of a symbol. The value of m is constituted by the RRC configuration, for example, with the RRC configuration that constitutes the number of repetitions and redundant versions, or the value of m is dynamically signaled by scheduling DCI. Alternatively, the UE may use symbols or mini-symbols in the same slot for repetition. Slots may also be used.

[0098] [Table 3]

[0099] Candidate frequency domain resources for resource configuration, e.g., frequency domain resources for each resource pool RRC configuration indicating the UE's RRC base station. The UE may be configured with one or more SL-BWPs. Alternatively, the UE may select one or more candidate frequency resources for unicast sidelink transmission. The candidate frequency resources may be configured using the following variants: Disclose that there may be

[0100] Variation 1 - Candidate frequency domain resources: The UE selects candidate frequency domain resources for sidelink unicast transmission. The frequency resource may be configured using continuous frequency resources. The channels may be organized within RBs or within subchannels, e.g., within RBGs. For example, the UE may determine, through RRC configuration, the start and length of the RBs for the candidate frequency resources. It is configured using parameters StartRB and LengthRB that indicate the length value (SLV). Alternatively, the UE may determine, through RRC configuration, the RBG for the candidate frequency resource. It is configured with parameters StartRBG and LengthRBG that indicate the SLV. The UE may transmit both sidelink control information (SCI) and sidelink data. The UE may also be configured with one candidate frequency resource for the sidelink. Two candidate frequencies are selected for control information (SCI) transmission and sidelink data transmission. Several resources, such as StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH may be configured. It may be.

[0101] Modification Example 2 - Candidate Frequency Region Resources: The UE may be configured using non - contiguous frequency resources as candidate frequency resources for sidelink unicast transmission. The frequency resources may be configured within an RB or within a sub - channel, for example, within an RBG. The non - contiguous frequency resources may be composed of a plurality of SLVs, for example, StartRBG _1 and LengthRBG_1, StartRBG_2 and LengthRBG_ 2,..., StartRBG_m and LengthRBG_m. Alternatively, the non - contiguous frequency resources may be composed of a start value and a bitmap, for example, St artRBG and {b m-1 ,…, b1 ,b0}. Assuming that the UE is configured using the StartRBG set to k , b m-1 is mapped to RBG k, and b0 is mapped to RBG k + m.

[0102] In the case of the above - mentioned modification example, the UE may provide assistance information in, for example, a sidelink UE information message, a UE assistance information message, or a similar message, in order to assist the NB in properly configuring the UE. Such assistance information includes UE capabilities, whether the UE is interested in transmitting or receiving V2X communication , or the carrier frequency when the UE is interested in performing V2X discovery, the V2X services that the UE is interested in, whether the UE is interested in transmitting or receiving V2X communication transmission or reception, and when the UE is interested in performing V2X discovery, the carrier frequency, the V2X services that the UE is interested in, whether the UE is interested in transmitting or receiving V2X communication transmission or reception, or a specific BWP within the carrier frequency when interested in performing V2X discovery, etc. may include the information of. In LTE, procedures are used to notify the E-UTRAN of the UE's power saving preference and SPS support information, maximum PDSCH / PUSCH bandwidth configuration preference, etc. On the other hand, the sidelink UE information message is used to notify the NB whether the UE is interested in or no longer interested in receiving sidelink communication or discovery, receiving V2X sidelink communication, and also requesting allocation or release of transmission resources for V2X sidelink communication and V2X sidelink discovery gaps, etc. It should be noted that the above RRC configuration may be configured through IE NR-SL-Resource or NR-SL-Re source-Unicast, or it should be noted that a part of the above RRC configuration may be configured by other IEs used for sidelink configuration.

[0103]

[0104] Detailed design of DCI signaling: The UE may be dynamically signaled a scheduling grant for unicast sidelink transmission through DCI. For example, a new DCI format, for example, DCI format 3, may be used to schedule the PSCCH or PSSCH for unicast sidelink transmission. To schedule resources for unicast sidelink transmission, the scheduling DCI includes 1) a BWP indicator field, 2) a resource indicator field, 3) a s idelink type indicator field, and 4) a carrier type indicator field ​ , 5) Transmission / Reception Indicator Field, 6) Sidelink UE ID Field, 7 ) Pair UE ID Field, 8) Time Domain Resource Allocation Field, 9) Retransmission F ield, 10) HARQ Field, 11) CSI Acquisition and Reporting Field, 12) Frequency Domain Resource Allocation Field, or 13) Slot Format Indicator (SFI I) Field, etc. may carry information is disclosed.

[0105] BWP Indicator Field. The UE may be configured using a plurality of BWPs through the RRC configuration. The scheduling DCI may indicate the BWP to be used for unicast sidelink transmission. Alternatively, the scheduling DCI may indicate to the UE to switch from the current BWP to a new BWP. The BWP indicator field may indicate the index of the BWP that the UE needs to perform unicast sidelink transmission or the BWP that the UE needs to switch. Assuming that the UE is configured using 4 BWPs, a 2-bit BWP indicator field may be used in a state where "00" indicates the first configured BWP and "01" indicates the second configured BWP. Some fields may be dedicated in a bitmap and may also be used to indicate the initial BWP and the default BWP. For example, "00" may indicate the discovery of the initial BWP (e.g., used for discovery and synchronization). Alternatively, "00" may indicate the default BWP. In yet another variant, "00" may indicate the initial BWP, while "01" may indicate the default BWP.

[0106] ​​​​​Resource indicator field. The UE may, through RRC, have multiple configurations of resources, e.g., configured using multiple resource pools. The scheduling DCI may indicate an index of the configuration of resources to be used for unicast sidelink transmission . Assuming that the UE is configured using 8 configurations of resources, e.g., configurations 0 to 7, a 3-bit resource indicator field may be used such that "000" indicates configuration 0 and "001" indicates configuration 1.

[0107] Sidelink type indicator field: The scheduling DCI may indicate the type of sidelink transmission. For example, a 2-bit sidelink type indicator field may be used such that "00" indicates that the DCI schedules unicast sidelink transmission, "01" indicates that the DCI schedules unicast sidelink transmission, and "10" indicates that the DCI schedules unicast sidelink transmission.

[0108] Carrier type indicator field. The UE may be dynamically informed of the type of carrier by 1 bit in the scheduling DCI. For example, if the carrier type indicator field is set to "0", the UE determines that the sidelink resource allocation is for a shared license carrier between Uu and sidelink, and if the carrier type indicator field is set to "1", the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0109] Transmission / Reception Indicator Field. In unicast sidelink communication, both the transmitting UE2 02 and the receiving UE203 may receive scheduling DCI. The transmission / Reception Indicator Field may be signaled by the scheduling DCI to indicate whether the DCI schedules transmission or reception. For example, a 1-bit field may be used in a state where "0" indicates reception and "1" indicates transmission.

[0110] Sidelink UE ID Field: In the case of unicast sidelink communication, the UE may dynamically signal the sidelink UE ID, e.g., the SL-U-RNTI. For the transmitting UE202, the UE may use the SL-U-RNTI as the source ID. For the receiving UE203, the UE may use the SL-U-RNTI as the destination ID. The scheduling DCI may also explicitly indicate the UE ID, e.g., the SL-U-RNTI. Alternatively, the UE may be configured by the RRC with 2 UE IDs in a state where each UE ID is associated with an index. The scheduling DCI may indicate the index using an n-bit field for the UE to determine the ID. n E ID.

[0111] Paired UE ID Field: The UE may dynamically signal the ID of the paired UE. When the UE receives scheduling DCI with a transmission / reception indicator field set to "0", the paired UE ID field indicates the ID of the transmitting UE202. When the UE receives scheduling DCI with a transmission / reception indicator field set to "1", the paired UE ID field indicates the ID of the receiving UE203. When the UE receives scheduling DCI with a transmission / reception indicator field set to "1", the paired UE ID field indicates the ID of the receiving UE203. When receiving I, the paired UE ID field indicates the ID of the receiving UE203. Scheduling The DCI may clearly indicate the paired UE ID, e.g., the SL-UP-RNTI. Alternatively, the UE may be configured by RRC with paired UE IDs, where each paired UE ID is associated with an index. n The scheduling DCI may use an n-bit field to indicate the index for the UE to determine the paired UE ID. Time domain resource allocation field: The UE may be signaled, via DCI, the time domain resources scheduled using the following variants. Variant 1 - Time domain resource allocation: The UE may be configured via RRC with one or more candidate resources. The scheduling DCI may indicate the time domain resources among the candidate resources to be used for unicast sidelink transmission.

[0112] To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. Variant 1 - Time domain resource allocation: The UE may be configured via RRC with one or more candidate resources. The scheduling DCI may indicate the time domain resources among the candidate resources to be used for unicast sidelink transmission.

[0113] Variant 1 - Time domain resource allocation: The UE may be configured via RRC with one or more candidate resources. The scheduling DCI may indicate the time domain resources among the candidate resources to be used for unicast sidelink transmission. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. Variant 1 - Time domain resource allocation: The UE may be configured via RRC with one or more candidate resources. The scheduling DCI may indicate the time domain resources among the candidate resources to be used for unicast sidelink transmission.

[0114] To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine the start of the time domain resources, the UE may be signaled a time offset value. For example, the time offset value field may be carried by the scheduling DCI to indicate the number of time units between the scheduling DCI and the scheduled time domain resources for unicast sidelink transmission. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the start point of the time domain resources. For example, the UE may know from which slot / subframe the time domain resources start. To determine whether to start, the slot / subframe offset may be informed. Next, the UE may be informed of the start symbol / minislot index to determine the start point within the slot / subframe. To determine the duration of the time domain resource, a bitmap or the length of the duration may be indicated by the scheduling DCI. In one example, the UE may be signaled a bitmap. The bitmap may indicate which time resources within the RRC-configured candidate resources are used for unicast sidelink transmission. In another example, the UE may be signaled the length of the time domain resource, e.g., l. The UE may then use l consecutive resource units within the RRC-configured candidate resources for unicast sidelink transmission. The resource unit may be within a subframe, slot, minislot, or symbol. The fields indicating the start and duration of the time domain resource may also be signaled through one DCI field. For example, a pre-defined or pre-configured table may include combinations of the start and duration of the time domain resource, with each combination associated with an index. The UE may be signaled one index by the scheduling DCI through one DCI field. The UE determines the time domain resource by finding the corresponding start or duration value from the table. Variant 2 - Time domain resource allocation: The UE may configure candidate resources through the RRC.

[0115]

[0116] It does not have to be configured using. The UE may be dynamically informed of the time domain resources for unicast sidelink transmission by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, duration, etc. of the time domain resource source. Each of the above parameters may be indicated by different DCI fields or may be indicated together by the DCI field. For example, the time domain resource may be dynamically signaled by the slot / subframe offset value and the SLV only through the scheduling DCI. In the case of unicast sidelink transmission, the scheduling DCI may indicate the time domain resources for both the PSCCH and the PSSCH. The time domain resources for the PSCCH and the PSSCH may be allocated together by the scheduling DCI. For example,

[0117] one time domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the time domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time domain resources for the PSCCH or the PSSCH, respectively.

[0118] Retransmission field: HARQ feedback may be introduced in unicast sidelink. When the transmission is NACKed at the receiving UE203, the transmitting UE202 may perform retransmission.

[0119] The retransmission at the transmitting UE202 may be triggered by the receiving UE203 or by the gNB ​​​​​​​​It may be triggered by. Using one variant, the receiving UE 203 may feedback NACK to the gNB. The gNB can trigger the transmitting UE 202 to perform retransmission by sending another scheduling DCI for retransmission. For retransmission, the gNB may instruct the transmitting UE 202 to use the same MCS, or the gNB may instruct the transmitting UE 202 to use a different MCS. If retransmission is repeated, the UE may similarly signal different RVs for the retransmission repetitions. For example, the scheduling DCI may carry an MCS index field to indicate the row index of the corresponding MCS level to be used for sidelink transmission within a predefined modulation and coding scheme (MCS) table, or to indicate the row index of the corresponding MCS level to be used for sidelink transmission within an MCS table configured by the RRC configuration. The RRC-configured MCS table may be a subset of the predefined MCS table. For example, the RRC configuration NR-SL-MCS may include the start index and end index of the predefined MCS table to form the MCS table subset, or the RRC configuration NR-SL-MCS may include the start index of the predefined MCS table or the size of the subset. The start index or end index may be composed of a 5-bit bit string in the RRC configuration. The size of the subset may be, for example, 1, 2, 4, 8. The UE may, similarly, signal different RVs for the retransmission repetitions. For example, the scheduling DCI may carry an MCS index field to indicate the row index of the corresponding MCS level to be used for sidelink transmission within a predefined modulation and coding scheme (MCS) table, or to indicate the row index of the corresponding MCS level to be used for sidelink transmission within an MCS table configured by the RRC configuration. The MCS index field may be carried to indicate the row index of the corresponding MCS level to be used for sidelink transmission within a predefined modulation coding scheme (MCS) table, or to indicate the row index of the corresponding MCS level to be used for sidelink transmission within an MCS table configured by the RRC configuration. The RRC-configured MCS table may be a subset of the predefined MCS table. For example, the RRC configuration NR-SL-MCS may include the start index and end index of the predefined MCS table to form the MCS table subset, or the RRC configuration NR-SL-MCS may include the start index of the predefined MCS table or the size of the subset. The start index or end index may be composed of a 5-bit bit string in the RRC configuration.

[0120] The RRC-configured MCS table may be a subset of the predefined MCS table. For example, the RRC configuration NR-SL-MCS may include the start index and end index of the predefined MCS table to form the MCS table subset, or the RRC configuration NR-SL-MCS may include the start index of the predefined MCS table or the size of the subset. The start index or end index may be composed of a 5-bit bit string in the RRC configuration. The RRC-configured MCS table may be a subset of the predefined MCS table. For example, the RRC configuration NR-SL-MCS may include the start index and end index of the predefined MCS table to form the MCS table subset, or the RRC configuration NR-SL-MCS may include the start index of the predefined MCS table or the size of the subset. The start index or end index may be composed of a 5-bit bit string in the RRC configuration. The size of the subset may be, for example, 1, 2, 4, 8. with an integer such as may be configured by the RRC configuration.

[0121] Rows 10 to 17 of a predefined MCS table are a subset of the MCS table Assuming that it is configured by the RRC configuration as a The MCS index field is 3 bits, and an example is shown in Table 4. When the UE is informed of the MCS index field set to "001", the UE may use the second row of the configured subset of the MCS table (in this example, row 11 of the predefined MCS table). When the UE is informed of the MCS index field set to "001", the UE may use the second row of the configured subset of the MCS table (in this example, row 11 of the predefined MCS table). The examples shown in this specification may also be applied to dynamic resource allocation for groupcast sidelink transmission or broadcast sidelink transmission. In this case, the retransmission field may be 1 bit to indicate whether the scheduling is for initial transmission or retransmission. For example, "0" may indicate that the transmission is an initial transmission, and "1" may indicate that the transmission is a retransmission. An exemplary call flow is shown in FIG. 3. For this case, in order to indicate whether the scheduling is for initial transmission or retransmission, the retransmission field may be 1 bit. For example, "0" may indicate that the transmission is an initial transmission, and "1" may indicate that the transmission is a retransmission. An exemplary call flow is shown in FIG. 3. For this case, in order to indicate whether the scheduling is for initial transmission or retransmission, the retransmission field may be 1 bit. For example, "0" may indicate that the transmission is an initial transmission, and "1" may indicate that the transmission is a retransmission. An exemplary call flow is shown in FIG. 3. For example, "0" may indicate that the transmission is an initial transmission, and "1" may indicate that the transmission is a retransmission. An exemplary call flow is shown in FIG. 3. For example, "0" may indicate that the transmission is an initial transmission, and "1" may indicate that the transmission is a retransmission. An exemplary call flow is shown in FIG. 3. is shown in FIG. 3.

[0122]

Table 4

[0123] FIG. 3 shows an exemplary call flow of gNB-triggered retransmission for unicast sidelink. At step 211a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. At step 211b At step 211a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. At step 211b At step 211a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. At step 211b, the Rx UE203 obtains scheduling DCI for initial transmission through the Uu interface. At step 212, the Rx UE203 performs unicast sidelink communication At step 211b, the Rx UE203 obtains scheduling DCI for initial transmission through the Uu interface. At step 212, the Rx UE203 performs unicast sidelink communication At step 211b, the Rx UE203 obtains scheduling DCI for initial transmission through the Uu interface. At step 212, the Rx UE203 performs unicast sidelink communication Obtain s transmission. In step 213, based on step 212 or step 211b, Rx UE203 transmits HARQ feedback to gNB201 through the Uu interface. Steps 213 to 216 may be executed when a NACK is received. In step 214, scheduling DCI for retransmission through the Uu interface may be obtained by Tx UE202. Based on step 214, in step 215, unicast retransmission on the sidelink may be transmitted by Tx UE202. In step 216, based on step 215, Rx UE203 transmits HARQ feedback to the gNB through the Uu interface. Steps 217 to 219 may be executed when an ACK is received. In step 217, scheduling DCI for a new transmission through the Uu interface may be obtained by Tx UE202. Based on step 217, in step 218, unicast transmission on the sidelink may be transmitted by Tx UE202. In step 219, based on step 218, Rx UE203 transmits HARQ feedback to the gNB through the Uu interface. Alternatively, the receiving UE203 may feedback a NACK to the transmitting UE202. By receiving a NACK from the receiving UE203, the transmitting UE202 can perform retransmission. For retransmission, the transmitting UE202 may choose to use the same MCS as that used for the initial transmission, or the transmitting UE202 may use a different MCS.

[0124] ​​​​​​​​​​​​​​​​It may be autonomously selected for use. In one example, the transmitting UE 202 may autonomously select the MCS from a pre - defined MCS table. In another example, the transmitting UE 20 2 may autonomously select the MCS from a subset of a pre - defined MCS table. At this time, the subset may be configured by the RRC through the RRC configuration NR - SL - MCS. The details of the configuration disclosed above can also be applied in this case. The examples shown in this specification may also be applied to dynamic resource allocation for group - cast sidelink transmission or broadcast sidelink transmission. Resources for re - transmission may be pre - reserved by a re - transmission field in the scheduling DCI that carries the grant for the initial transmission. The re - transmission field may indicate the time or frequency resources allocated for re - transmission, such as symbol index, mini - slot index, RB index, etc. Alternatively, the re - transmission field may indicate the time or frequency offset between re - transmission and initial transmission, such as symbol offset, mini - slot offset, RB offset, etc.

[0125] When the transmitting UE 202 receives a NACK from the receiving UE 203, the transmitting UE 202 may use the resources pre - reserved for re - transmission. When the transmitting UE 202 receives an ACK from the receiving UE 20 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4. When the transmitting UE 202 receives a NACK from the receiving UE 203, the transmitting UE 202 may use the resources pre - reserved for re - transmission. When the transmitting UE 202 receives an ACK from the receiving UE 20 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4. When the transmitting UE 202 receives a NACK from the receiving UE 203, the transmitting UE 202 may use the resources pre - reserved for re - transmission. When the transmitting UE 202 receives an ACK from the receiving UE 20 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4.

[0126] When the transmitting UE 202 receives a NACK from the receiving UE 203, the transmitting UE 202 may use the resources pre - reserved for re - transmission. When the transmitting UE 202 receives an ACK from the receiving UE 20 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4. 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4. 3, the transmitting UE 202 may skip the resources pre - reserved for re - transmission. An exemplary call flow is shown in FIG. 4.

[0127] FIG. 4 shows an exemplary call flow for Rx UE 203 - triggered re - transmission for unicast sidelink. - A flow is shown. At step 221a, Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. At step 221b, Rx UE203 obtains scheduling DCI for initial transmission and retransmission through the Uu interface. At step 222, Rx UE203 obtains unicast transmission from Tx UE202 via the sidelink. At step 223, based on step 222, Rx UE203 transmits HARQ feedback to Tx UE202 via the sidelink. Steps 224 to 225 may be executed when a NACK is received. At step 224, unicast retransmission via the sidelink may be obtained by Rx UE203. Based on step 224, at step 225, Rx UE203 transmits HARQ feedback to Tx UE202 via the sidelink. For example, when an ACK is received at step 223, Tx UE202 may skip retransmission. The HARQ sent. The scheduling DCI may indicate a HARQ ID or a HARQ process number to the transmitting UE202 and the receiving UE203 . The scheduling DCI may also indicate a resource allocation for HARQ feedback. The scheduling DCI may indicate a time or frequency resource for HARQ feedback, e.g., a symbol index, a mini-slot index, an RB index, etc. Alternatively, the scheduling DCI may indicate a time or frequency offset between HARQ feedback and initial transmission, e.g., a symbol offset, a mini-slot offset, an RB offset, etc.

[0128] The HARQ sent. The scheduling DCI may indicate a HARQ ID or a HARQ process number to the transmitting UE202 and the receiving UE203 . The scheduling DCI may also indicate a resource allocation for HARQ feedback. The scheduling DCI may indicate a time or frequency resource for HARQ feedback, e.g., a symbol index, a mini-slot index, an RB index, etc. Alternatively, the scheduling DCI may indicate a time or frequency offset between HARQ feedback and initial transmission, e.g., a symbol offset, a mini-slot offset, an RB offset, etc. Or, the scheduling DCI may indicate a time or frequency offset between HARQ feedback and initial transmission, e.g., a symbol offset, a mini-slot offset, an RB offset, etc. may indicate a sidelink, etc. When retransmission is triggered by the receiving UE203, the receiving UE203 may use the allocated HARQ feedback resource to send HARQ feedback to the transmitting UE2 02. When retransmission is triggered by the gNB201, the receiving UE203 may use the allocated HARQ feedback resource to send HARQ feedback to the gNB201.

[0129] Channel State Information (CSI) acquisition and reporting fields. The gNB201 may schedule CSI acquisition and reporting on the sidelink. The scheduling DCI may indicate the CSI-RS configuration and resources used for reporting to the transmitting UE202 and the receiving UE203. The scheduling DCI may indicate the time or frequency resources for CSI feedback, e.g., symbol index, mini-slot index, RB index, etc. Multiple CSI-RS configurations may be configured by the RRC, and the scheduling DCI may signal an index indicating the CSI-RS configuration used.

[0130] Frequency domain resource allocation field. To determine the frequency domain resources for unicast sidelink transmission / reception, the UE may be informed of the minimum RB, RBG, or subchannel to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may compare the minimum RB, RBG, or subchannel of the frequency domain resource allocation with the minimum RB, RBG, or subchannel of the RRC-configured candidate frequency domain resources. subchannel of the RRC-configured candidate frequency domain resources. ​​​​An offset with respect to a subchannel may be signaled. The offset may be within an RB or within an RBG.

[0131] To determine the range of frequency-domain resources, a bitmap or the width of the frequency-domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled a bitmap. The bitmap indicates which frequency resources within the RRC-configured candidate frequency resources are used for unicast sidelink transmission. In another example, the UE may be signaled the width of the frequency-domain resources, e.g., w. The UE may then use consecutive RBs, RBGs, or subchannels of w for unicast sidelink transmission.

[0132] For unicast sidelink transmission, the scheduling DCI may indicate frequency-domain resources for both the PSCCH and the PSSCH. The frequency-domain resources for the PSCCH and the PSSCH may be allocated together by the scheduling DCI, e.g., one frequency-domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency-domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency-domain resources for the PSCCH or the PSSCH, respectively.

[0133] Slot format indicator field. For a UE configured with a dedicated sidelink carrier, the UE may perform sidelink transmission only with symbols marked as "S". Alternatively, the UE may perform sidelink transmission using symbols marked as "S" or "U". In the case of a UE configured using a shared sidelink carrier between Uu and sidelink, the UE may perform sidelink transmission using only symbols marked as "S".

[0134] If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and need not perform sidelink transmission thereon. For example, assume that symbol k within slot m is configured as a candidate time resource in the RRC configuration. If symbol k within slot m is marked as "D" in the SFI, the UE need not consider symbol k within slot m as a candidate time resource. When the UE determines the time resources for unicast sidelink transmission, the UE may skip symbol k within slot m. If the candidate time resource is within a mini-slot and there is a mismatch in some of the symbols within the mini-slot, the UE may skip the entire mini-slot and need not perform sidelink transmission thereon. Alternatively, the UE may skip only the mismatched symbols and perform sidelink transmission using the matching symbols within the mini-slot.

[0135] The symbols used for sidelink communication may be further divided into symbols used for sidelink transmission and symbols used for sidelink reception. As disclosed, symbols "ST" and "SR" may be incorporated for slot formats as shown in FIG. 5. FIG. 5 shows an example of a slot format for unicast sidelink. Transmission UE20 In the case of 2, the UE may use the symbols designated as "ST" by the SFI for sidelink transmission, and may also use the symbols designated as "SR" by the SFI for receiving feedback, e.g., HARQ feedback. In the case of the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE. In the case of 2, the UE may use the symbols designated as "ST" by the SFI for sidelink transmission, and may also use the symbols designated as "SR" by the SFI for receiving feedback, e.g., HARQ feedback. In the case of the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE. In the case of the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE. Similar concepts may be applied to groupcast sidelink as well. The symbols designated as "X" may be used as gaps for switching between the transmission mode and the reception mode of the UE.

[0136] Groupcast sidelink transmission Groupcast sidelink transmission: In NR V2X, nodes such as gNB201 or gNB may dynamically allocate the resources used by the UE for groupcast sidelink transmission. In the case of the transmitting UE202, the UE may be allocated the resources for groupcast sidelink transmission through RRC configuration and DCI signaling. In the case of the receiving UE203, the UE may be allocated the resources for reception through RRC configuration and DCI signaling. When gNB201 schedules transmission on the sidelink, both the transmitting UE202 and the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. Groupcast sidelink transmission: In NR V2X, nodes such as gNB201 or gNB may dynamically allocate the resources used by the UE for groupcast sidelink transmission. In the case of the transmitting UE202, the UE may be allocated the resources for groupcast sidelink transmission through RRC configuration and DCI signaling. In the case of the transmitting UE202, the UE may be allocated the resources for groupcast sidelink transmission through RRC configuration and DCI signaling. In the case of the receiving UE203, the UE may be allocated the resources for reception through RRC configuration and DCI signaling. When gNB201 schedules transmission on the sidelink, both the transmitting UE202 and the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. In the case of the receiving UE203, the UE may be allocated the resources for reception through RRC configuration and DCI signaling. When gNB201 schedules transmission on the sidelink, both the transmitting UE202 and the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. When gNB201 schedules transmission on the sidelink, both the transmitting UE202 and the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. When gNB201 schedules transmission on the sidelink, both the transmitting UE202 and the receiving UE203 may receive a scheduling grant. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. By receiving the scheduling grant, the transmitting side can determine the resources and beams used for transmission. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. By receiving the scheduling grant, the receiving UE203 can determine the resources used for reception. The beam can be determined. The detailed resource allocation scheme is as follows .

[0137] Detailed design of RRC configuration: In the case of groupcast sidelink transmission, IE NR-S L-Resource or NR-SL-Resource-Groupcast may carry configuration information for both sidelink control and sidelink data transmission . The UE may use NR-SL-Resource or NR-SL-Resource-Groupcast configured through broadcast signals, such as OSI, or through common or dedicated RRC configurations over the Uu interface . IE NR-SL-Resource or NR-SL-Resource-Groupcast may be configured using. IE NR-SL-Resource or NR-SL-Resource-Groupca st may carry RRC configurations such as 1) type of sidelink transmission, 2) type of carrier, 3) numerology of resources, 4) UEs transmitting groupcast, 5) mask used for scheduling DCI scrambling rings, 6) index of candidate resources, 7) candidate time domain resources of resource configuration, 8) number of repetitions and redundant versions, 9) candidate frequency domain resources of resource configuration, or 10) beam sweeping information, etc . . . . . .

[0138] RRC configuration indicating the type of sidelink transmission. For example, if the same IE NR-SL-Res ource is used for all types of sidelink transmission, the RRC configuration NR-SL-Co mmuncationType may be Broadcast, Groupcast, or Unicast .

[0139] RRC configuration indicating the type of carrier. For example, RRC configuration NR-SL-Carrier Type may be used. If NR-SL-CarrierType is configured as "shared", the UE shall determine that the sidelink resource allocation is for a shared licensed carrier between Uu and sidelink. If NR-SL-CarrierType is configured as "dedicated", the UE shall determine that the sidelink resource allocation is for a dedicated sidelink carrier.

[0140] RRC configuration indicating the numerology of the resources for sidelink transmission. For example, RRC configuration NR-SL-Numerology which may be 15, 30, 60 KHz, etc.

[0141] RRC configuration indicating the ID of the UE that transmits groupcast over sidelink. In the case of groupcast sidelink transmission, the UE may be configured using a UE ID, for example, a sidelink groupcast RNTI (Sidelink Groupcast RNTI: SL-G-RNTI). If the UE requires groupcast over sidelink, the UE may use the SL-G-RNTI as the source ID within the formed group.

[0142] To perform groupcast sidelink communication, the UE may need to be informed of the group ID. The UE may be configured using a group ID, for example, a sidelink groupcast destination RNTI (Sidelink Groupcast Destination RNTI: SL-GD-RNTI). The UE shall use the group ID configured as the destination group ID. ​​​​​​​​​​​It may be used. The group ID may also be dynamically signaled by the scheduling DCI. led.

[0143] The scrambling ring sequence for the SCI may be initialized jointly by the destination group ID and the source ID. Alternatively, the scrambling ring sequence for the SCI may be initialized by one of the destination group ID or the source ID, and the other of them may be indicated in the SCI payload. For example, the destination group ID is used to scramble the SCI, and the source ID is carried by the SCI payload. A RRC configuration indicating the mask used for the scrambling ring of the scheduling DCI. For example, the UE may be configured using the SLGroupcast-RNTI or the SL-RNTI. gNB201 may generate and transmit the scheduling DCI for the UE together with the CRC scrambled by the configured SLGroupcast-RNTI or the SL

[0144] -RNTI. The DCI may be decoded by using the configured SLGroupcast-RNTI or the SL -RNTI. A RRC configuration indicating the number of repetitions and the redundancy version (RV). To improve reliability, the UE may repeat the groupcast sidelink transmission. The UE may be configured by gNB201 through the RRC configuration with the number of repetitions and the RV. When the UE repeats the initial transmission, inter-slot repetition or intra-slot repetition may be performed. The UE may use the same symbol or mini- slot in the subsequent slot for repetition.

[0145] For the purpose of improving reliability, the UE may repeat the groupcast sidelink transmission. The UE may be configured by gNB201 through the RRC configuration with the number of repetitions and the RV. When the UE repeats the initial transmission, inter-slot repetition or intra-slot repetition may be performed. The UE may be configured by gNB201 through the RRC configuration with the number of repetitions and the RV. When the UE repeats the initial transmission, inter-slot repetition or intra-slot repetition may be performed. When the UE repeats the initial transmission, inter-slot repetition or intra-slot repetition may be performed. For repetition, the UE may use the same symbol or mini- ​​A nislot may be used. Alternatively, for repetition, the UE may use symbols or minislots within the same slot. When beam sweeping is applied to groupcast, the transmitting UE 202 may repeat all beam sweeping, e.g., beam 1, beam 2, …, beam k, beam 1, beam 2, …, beam k, …, beam 1, beam 2, …, beam k. Alternatively, the UE may repeat for each beam for beam sweeping, e.g., beam 1, beam 1, …, beam 1, beam 2, beam 2, …, beam 2, …, beam k, beam k, …, beam k. A RRC configuration indicating the index of candidate resources. The UE may be configured using a plurality of configurations of sidelink transmission resources, e.g., a plurality of resource pools. Each configuration of resources may be associated with one dedicated resource index, e.g., RRC configuration NR-SL-Resource-Index. The UE may determine the configuration of resources to be used for sidelink transmission through DCI for scheduling sidelink transmission. A RRC configuration indicating the candidate time domain resources of the resource configuration, e.g., the time domain resources of each resource pool. It is disclosed that the candidate time domain resources for groupcast sidelink transmission for each candidate resource may be configured using the following variations. Variation 1 - Candidate time domain resources: The UE may be configured using one or more bitmaps indicating candidate time domain resources for sidelink transmission by RRC configuration. The bitmap may be for resources within a subframe, slot, minislot, or symbol.

[0146]

[0147]

[0148] ​​​​​​​​​​​​​​ - A bitmap may be shown. For example, a bitmap may be used to indicate resources within a symbol and may be mapped to a symbol during a certain time interval. For example, {b s , b s- 1, …, b1, b0} may be mapped to b s in the first symbol and b0 in the last symbol . When a bitmap is used to indicate resources within a mini-slot, it may be mapped to a mini-slot during a certain time interval. For example, {b m , b m-1 , …, b1, b0 } may be mapped to b m in the first mini-slot and b0 in the last mini-slot. Alternatively , a two-level mapping may be used to save mapping bits. A 2-bit sequence may be configured by an RRC configuration. For example, {a f , a f-1 , …a1, a0 } may be mapped to a f in the first subframe or slot during a certain time interval and a0 in the last subframe or slot, and mapped to each subframe or each slot. {c s , c s-1 , …, c1, c0} may be mapped to symbols within a frame or slot or, {c m , c m-1 , …, c1, c0} may be mapped to mini slots within a frame or slot

[0149] When the UE receives DCI that carries a scheduling grant for sidelink transmission, the UE may start transmission from the next available time resource within the configured candidate time resources . A minimum time gap constraint is that the UE switches from the reception mode to the transmission mode ​ may be applied to switch thereto, and the UE may perform transmission starting from the next available time resource after the minimum time gap within the configured candidate time resources.

[0150] Alternatively, the UE may be configured using an offset indicator indicating the time resources to be used for sidelink transmission within the configured candidate time resources. The offset value may be signaled by DCI carrying the scheduling grant. The offset value may indicate the offset between the time resources for sidelink transmission and the time resources used to transmit the scheduling grant DCI, or the offset value may indicate the offset between the time resources for sidelink transmission and the next available time resource after the minimum time gap within the configured candidate time resources.

[0151] Variant 2 - Candidate time domain resources: The UE may be dynamically signaled by DCI regarding the time resources to be used for groupcast sidelink transmission. The UE may not be configured using the candidate time domain resources through RRC configuration. The DCI carrying the scheduling grant may indicate the time resources to be used for groupcast sidelink transmission.

[0152] RRC configuration indicating beam sweeping information. In the case of groupcast sidelink transmission, the transmitting UE 202 may transmit information in multiple directions through multiple beams. The UE needs to recognize the number of beam sweepings to be performed and the corresponding resources.

[0153] Modification Example 1 - Beam Sweeping Information: gNB 201 may determine the number of beam sweepings that the UE needs to perform. For example, the UE may be configured through RRC with the number or maximum number of beam sweepings. In another modification example, the number of beam sweepings may be signaled by DCI. The UE may provide support information to the NB to assist the NB in determining the beam sweeping configuration. Such support information may include one or more of the V2X services of interest, such as UE capabilities represented by the number of beam sweeping directions that the UE can cover simultaneously, UE scheduling preferences including power saving mode preferences, etc. Assuming that the UE is configured to transmit information through k directions / beams, the UE may, through RRC configuration and DCI signaling, configure k time and frequency resources for beam sweeping in k directions, respectively. For example, time and frequency resources may be allocated for each direction / beam. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In another modification example, the number of beam sweepings may be signaled by DCI. The UE may provide support information to the NB to assist the NB in determining the beam sweeping configuration. Such support information may include one or more of the V2X services of interest, such as UE capabilities represented by the number of beam sweeping directions that the UE can cover simultaneously, UE scheduling preferences including power saving mode preferences, etc. Assuming that the UE is configured to transmit information through k directions / beams, the UE may, through RRC configuration and DCI signaling, configure k time and frequency resources for beam sweeping in k directions, respectively. For example, time and frequency resources may be allocated for each direction / beam. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In another modification example, the number of beam sweepings may be signaled by DCI. The UE may provide support information to the NB to assist the NB in determining the beam sweeping configuration. Such support information may include one or more of the V2X services of interest, such as UE capabilities represented by the number of beam sweeping directions that the UE can cover simultaneously, UE scheduling preferences including power saving mode preferences, etc. Assuming that the UE is configured to transmit information through k directions / beams, the UE may, through RRC configuration and DCI signaling, configure k time and frequency resources for beam sweeping in k directions, respectively. For example, time and frequency resources may be allocated for each direction / beam.

[0154] Assuming that the UE is configured to transmit information through k directions / beams, the UE may, through RRC configuration and DCI signaling, configure k time and frequency resources for beam sweeping in k directions, respectively. For example, time and frequency resources may be allocated for each direction / beam. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. Assuming that the UE is configured to transmit information through k directions / beams, the UE may, through RRC configuration and DCI signaling, configure k time and frequency resources for beam sweeping in k directions, respectively. For example, time and frequency resources may be allocated for each direction / beam. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows.

[0155] Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resources into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. For example, the UE may use the time resources across all beam sweeping directions as follows. In the sweeping information option 1, the UE uses the assigned use the allocated time and frequency resources, and for the remaining beam sweeping, Use the same duration and same frequency resources as used for the first beam sweep. For each request, the next available time resource in the configured resource pool may be used. For example, the UE may be configured with time resources in a minislot, and the UE may Assume that we are configured to use minislot n for beam sweeping. E is the number of mini-slots in the configured resource pool for the remaining beam sweeping. The beams used for beam sweeping may be Alternatively, the beam sweeper may be represented by gNB201. may be determined autonomously by the transmitting UE 202 based on sensing or discovery. In this variant, option 2, the UE uses round robin over all beam sweeping directions. Slicing the time resource evenly on a per-channel basis and using the same frequency resource in each direction In this variant, option 3, the UE performs time-domain The system autonomously decides how to slice the time-frequency resources in both the time domain and the frequency domain. good.

[0156] Variation 2 - Beam Sweeping Information: The UE uses the Beam Sweeping Information for groupcast sidelink transmission. The UE may then determine how many beam sweeps it needs to perform to achieve the desired beamwidth. gNB201 may report the k beam sweeping values ​​to group B201. Schedule time resources to the UE for cast sidelink transmission.

[0157] The UE may be allocated k configurations of time and frequency resources for beam sweeping in k directions through RRC configuration and DCI signaling. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery. Alternatively, the UE may be allocated one configuration of time and frequency resources. In one possibility, the allocated time and frequency resources may be used for all beams. The UE may evenly divide the allocated time resource into k parts and use each part for one beam. In another possibility, the allocated time and frequency resources may be used for one beam. The UE may use the time and frequency resources allocated for the first beam sweeping and use the next available time resource within the configured resource pool with the same duration and the same frequency resources as those used for the first beam sweeping for the remaining beam sweepings. The beams used for beam sweeping may be indicated by gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery.

[0158] Candidate frequency domain resources for resource configuration, for example, RRC configuration indicating the frequency domain resources of each resource pool. The UE may be configured using one or more SL-BWPs. Alternatively, the UE may be configured using one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured using the following variations. Candidate frequency domain resources for resource configuration, for example, RRC configuration indicating the frequency domain resources of each resource pool. The UE may be configured using one or more SL-BWPs. Alternatively, the UE may be configured using one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured using the following variations. Candidate frequency domain resources for resource configuration, for example, RRC configuration indicating the frequency domain resources of each resource pool. The UE may be configured using one or more SL-BWPs. Alternatively, the UE may be configured using one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured using the following variations. Candidate frequency domain resources for resource configuration, for example, RRC configuration indicating the frequency domain resources of each resource pool. The UE may be configured using one or more SL-BWPs. Alternatively, the UE may be configured using one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured using the following variations. Candidate frequency domain resources for resource configuration, for example, RRC configuration indicating the frequency domain resources of each resource pool. The UE may be configured using one or more SL-BWPs. Alternatively, the UE may be configured using one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured using the following variations.

[0159] Modification Example 1 - Candidate Frequency Region Resource: The UE may be configured to use contiguous frequency resources as candidate frequency resources for sidelink groupcast transmission. The frequency resources may be configured within an RB or within a subchannel, e.g., within an RBG. For example, the UE may be configured using parameters StartRB and LengthRB indicating the start and length values (SLV) of the RB for candidate frequency resources through the RRC configuration. Alternatively, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The UE may be configured to use one candidate frequency resource for both sidelink control information (SCI) transmission and sidelink data transmission. The UE may also be configured to use two candidate frequency resources, e.g., StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH, respectively, for sidelink control information (SCI) transmission and sidelink data transmission. The frequency resources may be configured using contiguous frequency resources. The frequency resources may be configured within an RB or within a subchannel, e.g., within an RBG. For example, the UE may be configured using parameters StartRB and LengthRB indicating the start and length values (SLV) of the RB for candidate frequency resources through the RRC configuration. Alternatively, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The UE may be configured to use one candidate frequency resource for both sidelink control information (SCI) transmission and sidelink data transmission. The UE may also be configured to use two candidate frequency resources, e.g., StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH, respectively, for sidelink control information (SCI) transmission and sidelink data transmission. For example, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The UE may be configured to use one candidate frequency resource for both sidelink control information (SCI) transmission and sidelink data transmission. The UE may also be configured to use two candidate frequency resources, e.g., StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH, respectively, for sidelink control information (SCI) transmission and sidelink data transmission. For example, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The UE may be configured to use one candidate frequency resource for both sidelink control information (SCI) transmission and sidelink data transmission. The UE may also be configured to use two candidate frequency resources, e.g., StartRBG-PSCCH and LengthRBG-PSCCH, and StartRBG-PSSCH and LengthRBG-PSSCH, respectively, for sidelink control information (SCI) transmission and sidelink data transmission. For example, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration.

[0160] Modification Example 2 - Candidate Frequency Region Resource: The UE may be configured to use non-contiguous frequency resources as candidate frequency resources for sidelink groupcast transmission. The frequency resources may be configured within an RB or within a subchannel, e.g., within an RBG. The non-contiguous frequency resources may be configured by a plurality of SLVs, e.g., StartRBG_1 and LengthRBG_1, StartRBG_2 and LengthRBG_2,..., StartRBG_m and LengthRBG_m. The UE may be configured to use non-contiguous frequency resources as candidate frequency resources for sidelink groupcast transmission. The frequency resources may be configured within an RB or within a subchannel, e.g., within an RBG. The non-contiguous frequency resources may be configured by a plurality of SLVs, e.g., StartRBG_1 and LengthRBG_1, StartRBG_2 and LengthRBG_2,..., StartRBG_m and LengthRBG_m. For example, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. The non-contiguous frequency resources may be configured by a plurality of SLVs, e.g., StartRBG_1 and LengthRBG_1, StartRBG_2 and LengthRBG_2,..., StartRBG_m and LengthRBG_m. For example, the UE may be configured using parameters StartRBG and LengthRBG indicating the SLV of the RBG for candidate frequency resources through the RRC configuration. Alternatively, non-contiguous frequency resources may be assigned a start value and a bitmap, e.g. StartRBG and {b m-1 ,…, b1 , b0}. , k, then b m-1 RB G k and b0 maps to RBG k+m.

[0161] In the above variant, the UE may, for example, For example, in a Sidelink UE Information message, in a UE Assistance Information message, or in a similar message. Such assistance information may include information about UE capabilities, whether the UE is capable of V2X communication, Carrier Circumstances when interested in transmitting or receiving V2X signals or conducting V2X discovery The frequency, the V2X service that the UE is interested in, and whether the UE is interested in transmitting or receiving V2X communications. or a specific BWP within a carrier frequency when there is an interest in conducting V2X discovery, etc. In LTE, procedures are used to determine the UE's power saving preferences and and SPS support information, maximum PDSCH / PUSCH bandwidth configuration preference, etc. to E-UTRAN On the other hand, the sidelink UE may inform the sidelink UE of the sidelink information message. receiving V2X sidelink communications or discovery; receiving V2X sidelink communications; and In addition, the allocation of transmission resources for V2X sidelink communication and V2X sidelink discovery gaps is Indicates whether the UE is or is no longer interested in the It should be noted that the NB may be notified of the

[0162] The above RRC configuration is based on the IE NR-SL-Resource or NR-SL-Re It may be configured through source - Groupcast or, as for the above - mentioned RRC configuration It should be noted that a part of it may be configured by other IEs used for sidelink configuration.

[0163] Detailed design of DCI signaling: The UE may be dynamically signaled with a scheduling grant for groupcast sidelink transmission through DCI. For example, a new DCI format, e.g., DCI format 3, may be used to schedule the PSCCH or PSSCH for groupcast sidelink transmission. To schedule resources for groupcast sidelink transmission, the scheduling DCI may carry information such as 1) BWP indicator field, 2) resource indicator field, 3) sidelink type indicator field, 4) carrier type indicator field, 5) time - domain resource allocation field, 6) transmission / reception indicator field, 7) sidelink UE ID field, 8) group ID field, 9 ) re - transmission field, 10) HARQ field, 11) beam - sweeping information field, 12) frequency - domain resource allocation field, or 13) slot format indicator (SFI) field. ) It is disclosed that it may carry information such as the above. BWP indicator field. The UE may be configured with multiple BWPs through the RRC configuration. The scheduling DCI may indicate the BWP to be used for groupcast sidelink transmission. Alternatively, the scheduling DCI may be from the current BWP

[0164] and... The scheduling DCI may be used for groupcast sidelink transmission. ​The UE may be informed to switch to the new BWP. The BWP indicator field may indicate whether the UE needs to perform groupcast sidelink transmission or the index of the BWP that the UE needs to switch to. Assuming that the UE is configured with four BWPs, a 2-bit BWP indicator field may be used, with "00" indicating the first configured BWP and "01" indicating the second configured BWP. Some fields may be dedicated in the form of a bitmap and may also be used to indicate the initial BWP and the default BWP. For example, "00" may indicate the initial BWP (e.g., used for discovery and synchronization). Alternatively, "00" may indicate the default BWP. In yet another variant, "00" may indicate the initial BWP, while "01" may indicate the default BWP in some cases.

[0165] Resource indicator field. The UE may be configured through RRC with multiple configurations of resources, e.g., using multiple resource pools. The scheduling DCI may indicate the index of the resource configuration to be used for groupcast sidelink transmission. Assuming that the UE is configured with eight configurations of resources, e.g., from configuration 0 to configuration 7, a 3-bit resource indicator field may be used, with "000" indicating configuration 0 and "001" indicating configuration 1.

[0166] Sidelink type indicator field. The scheduling DCI may indicate the type of sidelink transmission. For example, "00" may indicate groupcast sidelink Indicates that the DCI schedules it, and "01" is for groupcast sidelink transmission Indicates that the DCI schedules it, and "10" is for unicast sidelink transmission D In a state indicating that the DCI schedules it, a 2-bit sidelink type indicator field may be used.

[0167] Carrier type indicator field. The UE may be dynamically informed of the type of the carrier by 1 bit in the scheduling DCI. For example, if the carrier type indicator field is set to "0", the UE determines that the sidelink resource allocation is for a shared license carrier between Uu and the sidelink, and if the carrier type indicator field is set to "1", the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0168] Transmission / reception indicator field. In unicast sidelink communication, both the transmitting UE2 02 and the receiving UE203 may receive the scheduling DCI. The transmission / reception indicator field may be signaled by the scheduling DCI to indicate whether the DCI schedules transmission or reception . For example, a 1-bit field may be used in a state where "0" indicates reception and "1" indicates transmission.

[0169] Sidelink UE ID field. The UE may be dynamically signaled with the UE ID within the sidelink group to indicate the source ID. The scheduling DCI may clearly indicate the UE ID, for example, the SL-G-RNTI. Alternatively, the UE ​is 2 with each candidate ID associated with an index n of candidate IDs, and may be configured by RR C. The scheduling DCI may indicate the index using an n-bit field in order for the UE to determine the source ID .

[0170] Group ID field. The UE may be signaled the group ID dynamically in order to indicate the destination group ID. The scheduling DCI may explicitly indicate the group ID, e.g., the SL-GD-RNTI. Alternatively, the UE is 2 with each candidate ID associated with an index of candidate IDs, and may be configured by RRC . The scheduling DCI may indicate the index using an n-bit field in order for the UE to determine the group ID n . .

[0171] Time domain resource allocation field. The UE may be signaled the time domain resources scheduled using the following variations through the DCI .

[0172] Variation 1 - Time domain resource allocation: The UE may be configured using one or more candidate resources through the RRC configuration. The scheduling DCI may indicate the time domain resources to be used for groupcast sidelink transmission among the candidate resources .

[0173] To determine the start of the time domain resources, the UE may be signaled a time offset value . For example, the time offset value field is the time between the scheduling DCI and the scheduled time domain resources for groupcast sidelink transmission . ​​To indicate the number of knits, it may be carried by scheduling DCI. The time unit may be within a subframe, a slot, a mini-slot, or a symbol. Alternatively, the UE may be informed of a two-level time offset to determine the starting point of the time domain resource. For example, the UE may be informed of a slot / subframe offset to determine from which slot / subframe the time domain resource starts. Then, the UE may be informed of the index of the starting symbol / mini-slot to determine the starting point within the slot / subframe.

[0174] To determine the duration of the time domain resource, a bitmap or the length of the duration may be indicated by the scheduling DCI. In one example, the UE may be signaled a bitmap. The bitmap may indicate which time resources within the RRC-configured candidate resources are used for groupcast sidelink transmission. In another example, the UE may be signaled the length of the time domain resource, e.g., l. Next, the UE may use l consecutive resource units within the RRC-configured candidate resources for groupcast sidelink transmission. The resource unit may be within a subframe, a slot, a mini-slot, or a symbol.

[0175] Fields for indicating the start and duration of the time domain resource may also be signaled through one DCI field. For example, a pre-defined or pre-configured table has each combination associated with an index, and the time domain ​​​​​​It may include a combination of the start of a resource and the duration. The UE may be signaled one index by the scheduling DCI through one DCI format. The UE determines the time domain resource by finding the corresponding start or duration value from the table. through one DCI format. The UE determines the time domain resource by finding the corresponding start or duration value from the table.

[0176] Variant 2 - Time domain resource allocation: The UE may not be configured using candidate resources through the RRC configuration. The UE may be informed of the time domain resources for groupcast sidelink transmission dynamically by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, duration, etc. of the time domain resource. Each of the above parameters may be indicated by different DCI fields or may be indicated together by the DCI field. For example, the time domain resource may be signaled dynamically by the slot / subframe offset value and the SLV only through the scheduling DCI. The UE may be informed of the time domain resources for groupcast sidelink transmission dynamically by the scheduling DCI. The DCI may carry information such as the slot / subframe offset, start point, duration, etc. of the time domain resource. The DCI may carry information such as the slot / subframe offset, start point, duration, etc. of the time domain resource. Each of the above parameters may be indicated by different DCI fields or may be indicated together by the DCI field. For example, the time domain resource may be signaled dynamically by the slot / subframe offset value and the SLV only through the scheduling DCI. For example, the time domain resource may be signaled dynamically by the slot / subframe offset value and the SLV only through the scheduling DCI.

[0177] In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions through, for example, k beams. The UE may be informed of one time domain resource and determine the time domain resources for all beams according to some predefined rules. For example, the UE may be informed of the mini-slot n. The UE may use that mini-slot n for the first beam and use the subsequent k - 1 mini-slots within the configured candidate time resources for the remaining beams. Alternatively, the UE may be informed of the time domain resources for each beam respectively. For example, the UE may be informed of k time domain resources. In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions through, for example, k beams. The UE may be informed of one time domain resource and determine the time domain resources for all beams according to some predefined rules. For example, the UE may be informed of the mini-slot n. The UE may use that mini-slot n for the first beam and use the subsequent k - 1 mini-slots within the configured candidate time resources for the remaining beams. Alternatively, the UE may be informed of the time domain resources for each beam respectively. For example, the UE may be informed of k time domain resources.​​ The start and duration values may be known. Alternatively, the UE may be informed of a gap between the time domain resources for transmission in the first direction and the time domain resources for transmission in the remaining directions. .

[0178] In the case of groupcast sidelink transmission, the scheduling DCI may indicate time domain resources for both the PSCCH and / or the PSSCH. The time domain resources for the PSCCH and PSSCH may be allocated together by the scheduling DCI, for example, one time domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the time domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time domain resources for the PSCCH or the PSSCH, respectively. .

[0179] Retransmission field. HARQ feedback may be introduced for groupcast sidelink. The transmitting UE 202 may groupcast a message to a plurality of receiving UEs through a plurality of beams, where each beam may cover one or more UEs. Retransmission may be triggered per beam. For a certain beam, retransmission may be triggered if any UE under that beam is NACKed, or retransmission may be triggered if all UEs under that beam are NACKed.

[0180] Retransmission at the transmitting UE 202 may be triggered by the receiving UE 203 or by the gNB 201. Using one variant, each receiving UE sends an N to the gNB 201 ​ ACK may be fed back. For retransmission, gNB201 may trigger the transmitting UE202 to retransmit by sending another scheduling DCI. For retransmission, gNB201 may instruct the transmitting UE202 to use the same MCS, or gNB201 may instruct the transmitting UE202 to use a different MCS. If retransmission is performed, the UE may similarly be signaled with different RVs for repeated retransmission. In this case, the retransmission field may be 1 bit to indicate whether the scheduling is for initial transmission or retransmission. For example, "0" indicates that the transmission is an initial transmission, and "1" indicates that the transmission is a retransmission. The bitmap may be signaled in the scheduling DCI to indicate which beams are required for retransmission. For example, {b ,..., b1, b0} is mapped to b for the first beam and b0 for the k-th beam. An exemplary call flow is shown in FIG. 6. FIG. 6 shows an exemplary call flow for gNB201-triggered retransmission for groupcast sidelink. In step 241a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. In step 241b, each Rx UE203 obtains scheduling DCI for initial transmission through the Uu interface. In step 242a, each Rx UE203 obtains groupcast transmission on beam 1 through the sidelink. In step 242b, each R x UE203 may feed back an ACK / NACK through the sidelink. If NACK is fed back, in step 243a, gNB201 may send another scheduling DCI for retransmission through the Uu interface to trigger the transmitting UE202 to retransmit. In step 243b, each Rx UE203 obtains the scheduling DCI for retransmission through the Uu interface. In step 244a, the transmitting UE202 retransmits on beam 1 through the sidelink. In step 244b, each Rx UE203 obtains the retransmitted data on beam 1 through the sidelink. If NACK is fed back again, steps 243a to 244b may be repeated. x UE203 may feed back an ACK / NACK through the sidelink. If NACK is fed back, in step 243a, gNB201 may send another scheduling DCI for retransmission through the Uu interface to trigger the transmitting UE202 to retransmit. In step 243b, each Rx UE203 obtains the scheduling DCI for retransmission through the Uu interface. In step 244a, the transmitting UE202 retransmits on beam 1 through the sidelink. In step 244b, each Rx UE203 obtains the retransmitted data on beam 1 through the sidelink. If NACK is fed back again, steps 243a to 244b may be repeated. x UE203 may feed back an ACK / NACK through the sidelink. If NACK is fed back, in step 243a, gNB201 may send another scheduling DCI for retransmission through the Uu interface to trigger the transmitting UE202 to retransmit. In step 243b, each Rx UE203 obtains the scheduling DCI for retransmission through the Uu interface. In step 244a, the transmitting UE202 retransmits on beam 1 through the sidelink. In step 244b, each Rx UE203 obtains the retransmitted data on beam 1 through the sidelink. If NACK is fed back again, steps 243a to 244b may be repeated. k-1 ,..., b1, b0} is mapped to b k-1 for the first beam and b0 for the k-th beam. An exemplary call flow is shown in FIG. 6. FIG. 6 shows an exemplary call flow for gNB201-triggered retransmission for groupcast sidelink. In step 241a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. In step

[0181] FIG. 6 shows an exemplary call flow for gNB201-triggered retransmission for groupcast sidelink. In step 241a, the Tx UE202 obtains (e.g., receives) scheduling DCI for initial transmission through the Uu interface. In step 241b, each Rx UE203 obtains scheduling DCI for initial transmission through the Uu interface. In step 242a, each Rx UE203 obtains groupcast transmission on beam 1 through the sidelink. In step 242b, each Rx UE203 may feed back an ACK / NACK through the sidelink. If NACK is fed back, in step 243a, gNB201 may send another scheduling DCI for retransmission through the Uu interface to trigger the transmitting UE202 to retransmit. UE203 obtains groupcast transmission on beam 2 via sidelink. In step 242c, each Rx UE203 obtains group cast transmission on beam k via sidelink. Based on steps 242a to 242c, steps 243a to step 243c may be executed. In step 243a, each Rx UE203 sends HARQ feedback to gNB201 on beam 1 via the Uu interface from UE1…UE i1 . In step 243b, each Rx UE203 sends HARQ feedback to gNB201 on beam 2 via the Uu interface from UE i1+1…UE i2. In step 243c, each Rx UE203 sends HARQ feedback to gNB201 on beam k via the Uu interface from UE i +1…UE i k-1 k to. In step 244a to step 246b, for example, may be executed when NACKs are received on beam 1 and beam 4. In step 2 44a, scheduling DCI for retransmission on beam 1 and beam 4 may be sent to Tx UE202 via the Uu interface. In step 244b, scheduling DCI for retransmission on beam 1 and beam 4 may be sent to each Rx UE203 via the Uu interface. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U E203 obtains groupcast retransmission on beam 4 via sidelink. Based on steps 245a to 245b, steps 246a to step 246c may be executed. In step 245a, obtain groupcast retransmission on beam 1 via sidelink. In step 245b, Rx U ​This may be done. In step 246a, each Rx UE 203 transmits HARQ feedback to gNB 201 on beam 1 from UEs UE1…UE i1 through the U u interface. In step 246b, each Rx UE 203 transmits HARQ feedback to gNB 201 on beam 4 from UEs UE i3+1…UE i4 through the U u interface. This may be done.

[0182] Using another variant, each receiving UE may feedback a NACK to the transmitting UE 202. For each beam, the transmitting UE 202 may determine whether to perform a retransmission based on the feedback. For retransmission, the transmitting UE 202 may choose to use the same MCS as that used for the initial transmission, or the transmitting UE 202 may autonomously choose to use a different MCS.

[0183] Resources for retransmission may be pre-reserved by a retransmission field in the scheduling DCI that carries the grant for the initial transmission. Similar to the resource allocation for the initial transmission, assuming that k beams are used for groupcast transmission, the retransmission field may indicate k time or frequency resources for retransmission, or the retransmission field may indicate one time or frequency resource, and the transmitting UE 202 may determine the resources for the remaining beams according to some predefined rules (for example, use the subsequent k-1 time resource units within the candidate time resources). The allocation of retransmission may be indicated by time resources, such as symbol index, mini-slot index ​​​​​​​​​​​​​The time or frequency offset from the initial transmission, e.g., symbol offset, mini-slot offset, RB offset, etc., may be indicated. If retransmission is triggered in any beam, the transmitting UE 202 may use the corresponding pre-reserved resources for the retransmission in that beam. An exemplary call flow is shown in FIG. 7. It may be indicated by, for example, symbol offset, mini-slot offset, RB offset, etc. If retransmission is triggered in any beam, the transmitting UE 202 may use the corresponding pre-reserved resources for the retransmission in that beam. An exemplary call flow is shown in FIG. 7. If retransmission is triggered in any beam, the transmitting UE 202 may use the corresponding pre-reserved resources for the retransmission in that beam. An exemplary call flow is shown in FIG. 7. It may be indicated by, for example, symbol offset, mini-slot offset, RB offset, etc. If retransmission is triggered in any beam, the transmitting UE 202 may use the corresponding pre-reserved resources for the retransmission in that beam. An exemplary call flow is shown in FIG. 7.

[0184] FIG. 7 shows an exemplary call flow for Rx UE 203-triggered retransmission for groupcast sidelink. At step 231a, the Tx UE 202 obtains (e.g., receives) scheduling DCI for initial transmission and retransmission through the Uu interface. At step 231a, the Tx UE 202 obtains (e.g., receives) scheduling DCI for initial transmission and retransmission through the Uu interface. At step 231a, the Tx UE 202 obtains (e.g., receives) scheduling DCI for initial transmission and retransmission through the Uu interface. At step 231b, each Rx UE 203 obtains scheduling DCI for initial transmission and retransmission through the Uu interface. At step 231b, each Rx UE 203 obtains scheduling DCI for initial transmission and retransmission through the Uu interface. At step 232a, each Rx UE 203 obtains groupcast transmission in beam 1 through the sidelink. At step 232b, each Rx UE 203 obtains groupcast transmission in beam 2 through the sidelink. At step 232b, each Rx UE 203 obtains groupcast transmission in beam 2 through the sidelink. At step 232c, each Rx UE 203 obtains groupcast transmission in beam k through the sidelink. Based on steps 232a to 232c (which may be received from the Tx UE 202), steps 233a to 233c may be executed and transmitted to the Tx UE 202. At step 232c, each Rx UE 203 obtains groupcast transmission in beam k through the sidelink. Based on steps 232a to 232c (which may be received from the Tx UE 202), steps 233a to 233c may be executed and transmitted to the Tx UE 202. At step 233a, each Rx UE 203 transmits HARQ feedback to the Tx UE 202 in beam 1 through the sidelink from UE1…UE i1. The communication between the Tx UE and the Rx UE occurs over the sidelink. The vehicle UE (e.g., the Tx UE or the Rx UE) and the g At step 233a, each Rx UE 203 transmits HARQ feedback to the Tx UE 202 in beam 1 through the sidelink from UE1…UE i1. The communication between the Tx UE and the Rx UE occurs over the sidelink. The vehicle UE (e.g., the Tx UE or the Rx UE) and the g At step 233a, each Rx UE 203 transmits HARQ feedback to the Tx UE 202 in beam 1 through the sidelink from UE1…UE i1. The communication between the Tx UE and the Rx UE occurs over the sidelink. The vehicle UE (e.g., the Tx UE or the Rx UE) and the g At step 233a, each Rx UE 203 transmits HARQ feedback to the Tx UE 202 in beam 1 through the sidelink from UE1…UE i1. The communication between the Tx UE and the Rx UE occurs over the sidelink. The vehicle UE (e.g., the Tx UE or the Rx UE) and the g Communication with the NB occurs over the Uu interface. In step 233b, each Rx U E203 transmits HARQ feedback to UE202 from UE i1+1…UE i2 via the sidelink on beam 2 for Tx In step 233c, each Rx UE2 03 transmits HARQ feedback to UE202 from UE i k-1 +1…UE i k via the sidelink on beam k for gTx In steps 234a to 23 5b may be executed, for example, when NACKs are received for beams 1 and 3. In step 234a, each Rx UE203 obtains groupcast retransmission via the sidelink on beam 1 In step 234b, each Rx UE203 obtains groupcast retransmission via the sidelink on beam 3. Based on steps 234a to 234b, steps 235a to 236b may be executed. In step 235a, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 1 from UE1…UE i1 via the sidelink In step 235b, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 3 from UE i2+1…UE i3 via the sidelink Based on steps 234a to 234b, steps 235a to 236b may be executed. In step 235a, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 1 from UE1…UE i1 via the sidelink In step 235b, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 3 from UE i2+1…UE i3 via the sidelink In step 235b, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 3 from UE i2+1…UE i3 via the sidelink In step 235b, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 3 from UE i2+1…UE i3 via the sidelink

[0185] HARQ field. The scheduling DCI may indicate the HARQ ID or HARQ process number to the transmitting UE202 and the receiving UE20 3. The scheduling D CI may also indicate the resource allocation for HARQ feedback. The resources used for HARQ feedback for different beams may be TDM and In step 235b, each Rx UE203 transmits HARQ feedback to Tx UE202 on beam 3 from UE i2+1…UE i3 via the sidelink The resources used for HARQ feedback for different UEs with the same beam may be F DM'd. The scheduling DCI may indicate the time or frequency resources for HARQ feedback, e.g., symbol index, mini-slot index, RB index, etc. Alternatively, the scheduling DCI may indicate the time or frequency offset between the HARQ feedback and the initial transmission, e.g., symbol offset, mini-slot offset, RB offset, etc. If the retransmission is triggered by the receiving UE203, the receiving UE203 may use the allocated HARQ feedback resource to send HARQ feedback to the transmitting UE202. If the retransmission is triggered by the gNB201, the receiving UE203 may use the allocated HARQ feedback resource to send HARQ feedback to the gNB201. .

[0186] Beam sweeping information field. The scheduling DCI may indicate the number of beam sweepings that the UE needs to perform. The UE may be dynamically signaled the value of the number of beam sweepings by the scheduling DCI. Alternatively, the RRC may configure multiple potential values of the number of beam sweepings with each value associated with an index. The UE may be signaled one index to determine the value of the number of beam sweepings. The beams used for beam sweeping may be indicated by the gNB201. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitting UE202 based on sensing or discovery.

[0187] Frequency domain resource allocation field. For groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG. To determine the frequency domain resources for groupcast sidelink transmission, the UE may be informed of the minimum RB, RBG or subchannel information to be used. The UE may be signaled with the index of the minimum RB or RBG. Alternatively, the UE may be signaled with the offset between the minimum RB, RBG or subchannel of the frequency domain resource allocation and the minimum RB, RBG or subchannel of the RRC configured candidate frequency domain resources. The offset may be within an RB or an RBG.

[0188] To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. In another example, the UE may be signaled with the width of the frequency domain resources, e.g., w. The UE may then use w consecutive RBs, RBGs or subchannels for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. In another example, the UE may be signaled with the width of the frequency domain resources, e.g., w. The UE may then use w consecutive RBs, RBGs or subchannels for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. In another example, the UE may be signaled with the width of the frequency domain resources, e.g., w. The UE may then use w consecutive RBs, RBGs or subchannels for groupcast sidelink transmission. To determine the range of frequency domain resources, a bitmap or the width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled with a bitmap. The bitmap may indicate which frequency resources within the RRC configured candidate frequency resources are used for groupcast sidelink transmission. In another example, the UE may be signaled with the width of the frequency domain resources, e.g., w. The UE may then use w consecutive RBs, RBGs or subchannels for groupcast sidelink transmission.

[0189] In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled with different frequency domain resources for transmission in different directions. In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled with different frequency domain resources for transmission in different directions. In the case of groupcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be informed of one frequency domain resource and use the same frequency domain resource for transmission in all directions. Alternatively, the UE may be signaled with different frequency domain resources for transmission in different directions.

[0190] In the case of group cast sidelink transmission, the scheduling DCI may indicate frequency domain resources for both the PSCCH and the PSSCH. The frequency domain resources for the PSCCH and the PSSCH are allocated together by the scheduling DCI. For example, one frequency domain resource allocation may be used for both the PSCCH and the PSSCH. Alternatively, the frequency domain resources for the PSCCH or the PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for the PSCCH or the PSSCH, respectively. Slot format indicator field. In the case of a UE configured with a dedicated sidelink carrier, the UE may perform sidelink transmission only in symbols designated as "S". Alternatively, the UE may perform sidelink transmission in symbols designated as "S" or "U". In the case of a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE may perform sidelink transmission only in symbols designated as "S". If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon.

[0191] Slot format indicator field. In the case of a UE configured with a dedicated sidelink carrier, the UE may perform sidelink transmission only in symbols designated as "S". Alternatively, the UE may perform sidelink transmission in symbols designated as "S" or "U". In the case of a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE may perform sidelink transmission only in symbols designated as "S". If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon.

[0192] If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. If there is a mismatch between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the mismatched symbols and not perform sidelink transmission thereon. For example, assume that symbol k in slot m is configured as a candidate time resource in the RRC configuration. If symbol k in slot m is designated as "D" in the SFI, the UE shall consider symbol k in slot m as a non-candidate time resource and not perform sidelink transmission thereon. It does not need to be regarded as an intermediate resource. When the UE determines the time resource for groupcast sidelink transmission, the UE may skip symbol k within slot m. If the candidate intermediate resource is within a mini-slot and there are mismatches in some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmission thereby. Alternatively, the UE may skip only the mismatched symbols and perform sidelink transmission using the matching symbols within the mini-slot. When determining the time resource for groupcast sidelink transmission, the UE may skip symbol k within slot m. If the candidate intermediate resource is within a mini-slot and there are mismatches in some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmission thereby. Alternatively, the UE may skip only the mismatched symbols and perform sidelink transmission using the matching symbols within the mini-slot.

[0193] The symbols used for sidelink communication may further be divided into symbols used for sidelink transmission and symbols used for sidelink reception. The notations "ST" and "SR" are disclosed as being potentially incorporated for slot formats. For the transmitting UE202, the UE may use the symbols designated as "ST" by the SFI for sidelink transmission, and may also use the symbols designated as "SR" by the SFI for receiving feedback, e.g., HARQ feedback. For the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. The symbols used for sidelink communication may further be divided into symbols used for sidelink transmission and symbols used for sidelink reception. The notations "ST" and "SR" are disclosed as being potentially incorporated for slot formats. For the transmitting UE202, the UE may use the symbols designated as "ST" by the SFI for sidelink transmission, and may also use the symbols designated as "SR" by the SFI for receiving feedback, e.g., HARQ feedback. For the transmitting UE202, the UE may use the symbols designated as "ST" by the SFI for sidelink transmission, and may also use the symbols designated as "SR" by the SFI for receiving feedback, e.g., HARQ feedback. For the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. For the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. For the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback. For the receiving UE203, the UE may use the symbols designated as "ST" by the SFI for receiving sidelink transmission, and may also use the symbols designated as "SR" by the SFI for transmitting feedback, e.g., HARQ feedback.

[0194] Dynamic resource allocation for unicast and groupcast Dynamic resource allocation for unicast and groupcast - Overall signaling design and UE operation in unicast or groupcast use cases: Dynamic Dynamic resource allocation for unicast and groupcast - Overall signaling design and UE operation in unicast or groupcast use cases: Dynamic ​​The subject matter disclosed herein with respect to resource allocation (e.g., FIGS. 10 through 16 and the accompanying description) may be for unicast or groupcast. In NR V2X mode 1, the gNB 201 may dynamically schedule unicast or groupcast transmissions on the sidelink through a scheduling grant. For unicast or groupcast, the Tx UE 202 or Rx UE 203 needs to recognize the resources used for transmission and reception. The transmission scheduling ring may be indicated by a scheduling DCI transmitted on the Uu interface with the following example.

[0195] Example 1 of scheduling DCI transmitted on the Uu interface: The gNB 201 may send the scheduling DCI to the Tx UE 202 or Rx UE 203. Shared resources may be used to transmit the scheduled DCI, e.g., SDM'd, to the Tx UE 202 or the Rx UE 203. In this case, the UE may be configured with 1 CORESET to monitor the scheduling DCI for the Tx UE 202 or Rx UE 203. Alternatively, dedicated resources may be used to transmit the scheduled DCI, e.g., TDM or FDM'd, to the Tx UE 202 and the Rx UE 203. In this case, the UE may be configured with 1 CORESET or 2 different CORESETS to monitor the scheduling DCI for the Tx UE 202 or the scheduling DCI for the Rx UE 203.

[0196] Example 2 of scheduling DCI transmitted over the Uu interface: gNB201 may transmit the scheduling DCI only to Tx UE202. By decoding the scheduling DCI, Tx UE202 can determine the scheduled grant for the feedback in the received DCI. Then, Tx UE202 may use the SCI to indicate to Rx UE203 the side-link transmission scheduling received, for example, PSSCH, for example, data transmission, or resource allocation for the transmission of a reference signal for measurement, and resource allocation feedback, for example, HARQ feedback or CSI feedback. Rx UE203 may be configured using a monitoring occasion to monitor for the SCI. By decoding the SCI, Rx UE203 can determine the resources used for the PSSCH and the feedback. When gNB201 transmits the scheduling DCI to both Tx UE202 and Rx UE203, gNB201 may schedule the side-link communication according to the following example. Example 1 of scheduling DCI for both to schedule side-link communication: gNB201 may transmit the scheduling DCI to Tx UE202 or Rx UE203, where the HARQ feedback is transmitted from Rx UE203 to gNB201 through the Uu interface. Figure 10 shows an example of a unicast use case.

[0197]

[0198]

[0199] ​​​​​​​​​​​​​​​​The scheduling DCI is for time and frequency resource allocation for sidelink transmission and may carry, for example, resource allocations for the SCI and PSSCH, and doing so allows both the Tx UE 202 and the Rx UE 203 to recognize the resources used for data transmission or reception on the sidelink.

[0200] The scheduling DCI may carry information on the resources used for HARQ feedback The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example in terms of time and frequency resources, or may be implicitly indicated by the scheduling DCI by, for example, an index of a HARQ feedback resource configuration configured by the RRC In the case of a UE scheduled for transmission on the sidelink, the UE may ignore the resource allocation for HARQ feedback. In the case of a UE scheduled for reception on the sidelink, the UE may use the allocated resources through the Uu interface to transmit HARQ feedback to the gNB 201.

[0201] Example 2 of scheduling DCI for both sides scheduling sidelink communication: The gNB 201 may transmit scheduling DCI to both the Tx UE 202 and the Rx UE 203, and in this case the HARQ feedback is transmitted from the Rx UE 20 3 to the Tx UE 202 through the sidelink. FIG. 11 shows an example of a unicast use case

[0202] The scheduling DCI is for time and frequency resource allocation for sidelink transmission ​​and, for example, may carry resource allocations for SCI and PSSCH, and by doing so the Tx UE202 or the Rx UE203 can recognize the resources used for data transmission or reception on the sidelink.

[0203] The scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, the RRC. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For example, the scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, the RRC. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For example, the scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, the RRC. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For example, the scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, the RRC. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For example, the scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, the RRC. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. For a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources.

[0204] Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case. Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case. Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case. Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case. Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case. Example 3 of scheduling DCI for both sides scheduling sidelink communication: The gNB201 may transmit scheduling DCI to both the Tx UE202 and the Rx UE203. In this case, the HARQ feedback is first transmitted from the Rx UE203 to the Tx UE202 on the sidelink, and then the Tx UE202 may feedback the information received from the gNB201 through the Uu interface. Fig. 12 shows an example of a unicast use case.

[0205] The Tx UE202 may transfer all of the HARQ feedback received from the gNB201 This is acceptable. Alternatively, to reduce overhead, Tx UE202 may feedback concise information to gNB20 1.

[0206] The scheduling DCI may carry time and frequency resource allocations for sidelink transmissions, for example, resource allocations for SCI and PSSCH, and by doing so the Tx UE202 or Rx UE203 can recognize the resources used for data transmission or reception on the sidelink.

[0207] The scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time or frequency resources, or may be implicitly indicated by an index of the HARQ feedback resource configuration configured by, for example, RRC in the scheduling DCI. In the case of a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE202 using the allocated resources on the sidelink. In the case of a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback using the allocated resources.

[0208] The scheduling DCI may carry time and frequency resource allocations for feedback from the Tx UE202 to the gNB201. In the case of a UE scheduled for reception on the sidelink, the UE may use the allocated resources on the sidelink to feedback from the Tx UE202 to the gNB201. Resource allocation for the UE may be ignored. For a UE scheduled for transmission on sidelink, the UE may use the allocated resources and send feedback to the gNB201 through the Uu interface. For a UE scheduled for transmission on sidelink, the UE may use the allocated resources and send feedback to the gNB201 through the Uu interface. For a UE scheduled for transmission on sidelink, the UE may use the allocated resources and send feedback to the gNB201 through the Uu interface.

[0209] When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203. When the gNB201 sends scheduling DCI to the Tx UE202 and the Rx UE203, the same DCI format may be used for the Tx UE202 and the Rx UE203. For example, the scheduling DCI for the Tx UE202 and the Rx UE203 may carry the same DCI fields. For example, the DCI for the Tx UE202 and the Rx UE203 may be scrambled with the same RNTI, such as the SLUnicast-RNTI, the SLGroupcast-RNTI. The UE may check the transmission / reception indicator field in the DCI to determine whether it is for the Tx UE202 or for the Rx UE203.

[0210] Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. Alternatively, the scheduling DCI for the Tx UE202 or the Rx UE203 may be transmitted in different DCI formats. For example, the scheduling DCI for the Tx UE202 or the Rx UE203 may carry different DCI fields. For example, the DCI for the Tx UE202 or the Rx UE203 may be scrambled with different RNTIs. The UE may have two RNTIs for unicast and groupcast respectively, such as the SLUnicastTx-RNTI or the SLUnicastRx-RNTI, the SLGroupcastTx-RNTI or the SLGroupcastRx-RNTI. It may be configured using tRx-RNTI. When the UE detects DCI scrambled with SLUnicastTx-RNTI or S LGroupcastTx-RNTI, the UE can determine that it is scheduled for transmission on the sidelink. When the UE detects DCI scrambled with SLUnicastRx-RNTI or SLGroupcastRx- RNTI, the UE can determine that it is scheduled for reception on the sidelink. When the UE detects DCI scrambled with SLUnicastRx-RNTI or SLGroupcastRx- RNTI, the UE can determine that it is scheduled for reception on the sidelink.

[0211] When gNB201 transmits scheduling DCI only to Tx UE202, g NB201 may schedule sidelink communication according to the following example. Example 1 of dedicated scheduling DCI for scheduling sidelink communication: gNB2 01 may transmit scheduling DCI only to Tx UE202. At this time, HA RQ feedback is transmitted from Rx UE203 to gNB2 01 through the Uu interface. FIG. 13 shows an example of a unicast use case.

[0212] The scheduling DCI may carry, for example, resource allocations for SCI and PSSCH, for time and frequency resource allocations for sidelink transmission. Tx U E202 indicates the resource allocation to Rx UE203 through the SCI. By doing so both Tx UE202 and Rx UE203 can recognize the resources used for data transmission and reception on the sidelink. The scheduling DCI may carry information on the resources used for HARQ feedback.

[0213] The scheduling DCI may carry information on the resources used for HARQ feedback. It may be sent. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, the time and frequency resources, or may be implicitly indicated by the scheduling DCI, for example, the index of the HARQ feedback resource configuration configured by the RRC. The Tx UE202 indicates the resource allocation to the Rx UE203 through the SCI. For a UE scheduled for transmission on the sidelink, the UE may ignore the resource allocation for HARQ feedback. For a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the gNB201 using the allocated resources through the Uu interface.

[0214] Example 2 of dedicated scheduling DCI for scheduling sidelink communication: The gNB2 01 may transmit the scheduling DCI only to the Tx UE202. At this time, the HA RQ feedback is transmitted from the Rx UE203 to the Tx UE202 on the sidelink. FIG. 14 shows an example of a unicast use case.

[0215] The scheduling DCI may carry, for example, the resource allocation for the SCI and the PSSCH, for the time and frequency resource allocation for sidelink transmission. The Tx U E202 indicates the resource allocation to the Rx UE203 through the SCI. By doing so, both the Tx UE202 and the Rx UE203 can recognize the resources used for data transmission and reception on the sidelink.

[0216] The scheduling DCI may carry information on the resources used for HARQ feedback. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or may be implicitly indicated by the scheduling DCI, for example, by an index into a HARQ feedback resource configuration configured by the RRC. The Tx UE 202 indicates the resource allocation to the Rx UE 203 through the SCI. In the case of a UE scheduled for reception on the sidelink, the UE may transmit HARQ feedback to the Tx UE 202 using the allocated resources on the sidelink. In the case of a UE scheduled for transmission on the sidelink, the UE may monitor or receive HARQ feedback on the allocated resources.

[0217] Example 3 of dedicated scheduling DCI for scheduling sidelink communication: gNB2 01 may transmit the scheduling DCI only to the Tx UE 202, whereupon the HA RQ feedback is first transmitted from the Rx UE 203 to the Tx UE 202 on the sidelink, and then the Tx UE 202 feeds back the information received from the gNB 201 through the Uu interface.

[0218] FIG. 15A shows an example of a use case. FIG. 15B shows an exemplary method flow. In summary, at step 251, the scheduling DCI may be obtained by the Tx UE 202, with the following further details. At step 252, the Tx UE 2 02 may transmit a transmission to the Rx UE 203 via the sidelink. At step 253 Based on step 252, Tx UE202 may receive a feedback from Rx UE203. Regarding FIG. 15 and other figures (e.g., FIGS. 20 to 22 or FIGS. 6 to 7, etc.), as presented in more detail herein, there are different scheduling rings and other approaches regarding scheduling DCI. Tx UE202 may transmit (forward) all of the HARQ feedback received by gNB201. Alternatively, to reduce overhead, Tx UE202 may feedback concise information. The scheduling DCI may carry time and frequency resource allocations for sidelink transmissions, e.g., resource allocations for SCI and PSSCH. Tx UE202 indicates the resource allocation to Rx UE203 through the SCI. By doing so, both Tx UE202 and Rx UE203 can recognize the resources used for data transmission and reception on the sidelink. Regarding FIG. 15 and other figures (e.g., FIGS. 20 to 22 or FIGS. 6 to 7, etc.), as presented in more detail herein, there are different scheduling rings and other approaches regarding scheduling DCI. There are other approaches regarding different scheduling rings and scheduling DCI, which will be presented in more detail herein with respect to FIG. 15 and other figures (e.g., FIGS. 20 to 22 or FIGS. 6 to 7, etc.).

[0219] Tx UE202 may transmit (forward) all of the HARQ feedback received by gNB201. Alternatively, to reduce overhead, Tx UE202 may feedback concise information. The scheduling DCI may carry time and frequency resource allocations for sidelink transmissions, e.g., resource allocations for SCI and PSSCH. The scheduling DCI may carry time and frequency resource allocations for sidelink transmissions, for example, resource allocations for SCI and PSSCH. Tx UE202 indicates the resource allocation to Rx UE203 through the SCI. By doing so, both Tx UE202 and Rx UE203 can recognize the resources used for data transmission and reception on the sidelink. By doing so, both Tx UE202 and Rx UE203 can recognize the resources used for data transmission and reception on the sidelink.

[0220] The scheduling DCI may carry information about the resources used for HARQ feedback transmitted from Rx UE203 to Tx UE202. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or implicitly indicated by the scheduling DCI, for example, through an index of the HARQ feedback resource configuration formed by, for example, RRC. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or implicitly indicated by the scheduling DCI, for example, through an index of the HARQ feedback resource configuration formed by, for example, RRC. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or implicitly indicated by the scheduling DCI, for example, through an index of the HARQ feedback resource configuration formed by, for example, RRC. The resources used for HARQ may be explicitly indicated by the scheduling DCI, for example, in terms of time and frequency resources, or implicitly indicated by the scheduling DCI, for example, through an index of the HARQ feedback resource configuration formed by, for example, RRC. Tx UE202 indicates the resource allocation to Rx UE203 through the SCI. For a UE whose reception on the sidelink is scheduled, the UE may, on the sidelink, be allocated​ Using the resources, HARQ feedback may be sent to the Tx UE 202. For the UE scheduled for transmission in sidelink, the UE may monitor or receive HARQ feedback on the allocated resources. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For the UE scheduled for transmission in sidelink, the UE may monitor or receive HARQ feedback on the allocated resources. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard. For example, the scheduling DCI may carry one DCI field indicating the resources used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202, for example, the PSFCH resource indicator field, where each value may be configured by the RRC configuration or associated with the indexed PSFCH resources predefined by the standard.

[0221] The UE may be configured using the common PSFCH resource configuration or the dedicated PSFCH resource configuration used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202 in sidelink. For example, the UE may be configured through broadcast signaling, for example, through RMSI or OSI, using the common RRC configuration psfch-ResourceCommon, or the UE may be configured using the dedicated RRC configuration PSFCH-ResourceSet. The PSFCH-ResourceSet may include one or more of the RRC configuration PSFCH-Resources, and an example of the RRC configuration PSFCH-Resource in this case is shown in FIG. 19. The UE may be configured using the common PSFCH resource configuration or the dedicated PSFCH resource configuration used for the transmission of HARQ feedback from the Rx UE 203 to the Tx UE 202 in sidelink. For example, the UE may be configured through broadcast signaling, for example, through RMSI or OSI, using the common RRC configuration psfch-ResourceCommon, or the UE may be configured using the dedicated RRC configuration PSFCH-ResourceSet. For example, the UE may be configured through broadcast signaling, for example, through RMSI or OSI, using the common RRC configuration psfch-ResourceCommon, or the UE may be configured using the dedicated RRC configuration PSFCH-ResourceSet. For example, the UE may be configured through broadcast signaling, for example, through RMSI or OSI, using the common RRC configuration psfch-ResourceCommon, or the UE may be configured using the dedicated RRC configuration PSFCH-ResourceSet. For example, the UE may be configured through broadcast signaling, for example, through RMSI or OSI, using the common RRC configuration psfch-ResourceCommon, or the UE may be configured using the dedicated RRC configuration PSFCH-ResourceSet. The PSFCH-ResourceSet may include one or more of the RRC configuration PSFCH-Resources, and an example of the RRC configuration PSFCH-Resource in this case is shown in FIG. 19. The PSFCH-ResourceSet may include one or more of the RRC configuration PSFCH-Resources, and an example of the RRC configuration PSFCH-Resource in this case is shown in FIG. 19.

[0222] In the case where only one of the common configuration and the dedicated configuration is supported, when the UE receives the scheduling DCI and decodes the PSFCH resource indicator field, In the case where only one of the common configuration and the dedicated configuration is supported, when the UE receives the scheduling DCI and decodes the PSFCH resource indicator field, The UE can determine the corresponding PSFCH resource through the configured psfch-ResourceCommon or the configured PSF CH-ResourceSet.

[0223] In a case where both common configuration and dedicated configuration are supported, when the UE receives the scheduling D CI and decodes the PSFCH resource indicator field, the UE can determine the corresponding PSFCH resource through the dedicated RRC configured PSFCH-ResourceSet or, if no dedicated RRC configuration is configured, through the common RRC configured psfch-ResourceCommon.

[0224] In another example, the scheduling DCI may carry one DCI field indicating the timing for transmitting HARQ feedback from the Rx UE203 to the Tx UE202, for example, the SL HARQ timing indicator field.

[0225] In one approach, the indicated timing may be the time offset between the HARQ feedback (from the Rx UE20 3 to the Tx UE202) and the initial transmission on the scheduled side link. For example, the UE may use the candidate time offset through the RRC parameter sl-I nitalDataToSL-ACK with the content of "SEQUENCE(SIZE(8) ) OF INTEGER(0..15)" to be RRC configured, where the time offset may be within a slot, a mini-slot, or a symbol. When the UE receives the scheduling DCI and the SL HARQ timing in dicator, ​​​​​​When decrypting the sidelink field, the UE can determine the timing offset by finding the corresponding entry in the configured RRC parameter sl-Init alDataToSL-ACK.

[0226] In another approach, the indicated timing may be the time offset between the HARQ feedback (from Rx UE2 03 to Tx UE202) and the last scheduled repetition / retransmission (or retransmission, in other words) of the transmission block (TB) on the sidelink. Assuming that k repetitions / retransmissions are scheduled by the scheduling DCI, the SL HARQ timing indicator field indicates the time offset between the HARQ feedback and the k-th scheduled repetition / retransmission. If there is no scheduled repetition, e.g., k = 0, the SL HARQ timing indicator field indicates the time offset between the HARQ feedback and the scheduled initial transmission. For example, the UE may be configured with RRC using candidate timing offsets through the RRC parameter sl-LastDataToSL-ACK with the content of "SEQUENCE(SIZE(8)) OF INTEGER(0..15)", where the timing offset may be within a slot, a mini-slot, or a symbol. When the UE receives the scheduling DCI or decrypts the SL HARQ timing indicator field, the UE can determine the timing offset by finding the corresponding entry in the configured RRC parameter sl-LastDataToSL-ACK.

[0227] The scheduling DCI may carry time and frequency resource allocations for feedback from Tx UE202 to gNB201. Tx UE202 may not indicate the resource allocation to Rx UE203 through the SCI. For a UE with scheduled transmission on the sidelink, the UE may send feedback to gNB201 using the allocated resources through the Uu interface. For example, the scheduling DCI may carry one DCI field indicating the resources used for transmission of HARQ feedback from a V2X UE (e.g., Tx UE202) to gNB201, e.g., a PUCCH resource indicator field, where each value is associated with a PUCCH resource configured by the RRC configuration or pre - indexed by the standard. The UE may be configured using a common PUCCH resource configuration or a dedicated PUCCH resource configuration for transmission of HARQ information for downlink transmission on the Uu interface. The UE may use the same set of common or dedicated configurations for transmission of HARQ information on the Uu interface for sidelink transmission on the sidelink. For example, when the UE receives the scheduling DCI or decodes the PUCCH resource indicator field, the UE may obtain the corresponding through the dedicated RRC - configured PUCCH - ResourceSet within PUCCH - Config, or through the common RRC - configured pucch - ResourceCommon within SIB1 if no dedicated RRC configuration is configured. For a UE with scheduled transmission on the sidelink, the UE may send feedback to gNB201 using the allocated resources through the Uu interface. For example, the scheduling DCI may carry one DCI field indicating the resources used for transmission of HARQ feedback from a V2X UE (e.g., Tx UE202) to gNB201, e.g., a PUCCH resource indicator field, where each value is associated with a PUCCH resource configured by the RRC configuration or pre - indexed by the standard. through the dedicated RRC - configured PUCCH - ResourceSet within PUCCH - Config, or through the common RRC - configured pucch - ResourceCommon within SIB1 if no dedicated RRC configuration is configured. For a UE with scheduled transmission on the sidelink, the UE may send feedback to gNB201 using the allocated resources through the Uu interface. For example, the scheduling DCI may carry one DCI field indicating the resources used for transmission of HARQ feedback from a V2X UE (e.g., Tx UE202) to gNB201, e.g., a PUCCH resource indicator field, where each value is associated with a PUCCH resource configured by the RRC configuration or pre - indexed by the standard. The UE may be configured using a common PUCCH resource configuration or a dedicated PUCCH resource configuration for transmission of HARQ information for downlink transmission on the Uu interface. The UE may use the same set of common or dedicated configurations for transmission of HARQ information on the Uu interface for sidelink transmission on the sidelink. For example, when the UE receives the scheduling DCI or decodes the PUCCH resource indicator field, the UE may obtain the corresponding

[0228] The UE may be configured using a common PUCCH resource configuration or a dedicated PUCCH resource configuration for transmission of HARQ information for downlink transmission on the Uu interface. The UE may use the same set of common or dedicated configurations for transmission of HARQ information on the Uu interface for sidelink transmission on the sidelink. For example, when the UE receives the scheduling DCI or decodes the PUCCH resource indicator field, the UE may obtain the corresponding through the dedicated RRC - configured PUCCH - ResourceSet within PUCCH - Config, or through the common RRC - configured pucch - ResourceCommon within SIB1 if no dedicated RRC configuration is configured. For a UE with scheduled transmission on the sidelink, the UE may send feedback to gNB201 using the allocated resources through the Uu interface. For example, the scheduling DCI may carry one DCI field indicating the resources used for transmission of HARQ feedback from a V2X UE (e.g., Tx UE202) to gNB201, e.g., a PUCCH resource indicator field, where each value is associated with a PUCCH resource configured by the RRC configuration or pre - indexed by the standard. The UE may be configured using a common PUCCH resource configuration or a dedicated PUCCH resource configuration for transmission of HARQ information for downlink transmission on the Uu interface. The UE may use the same set of common or dedicated configurations for transmission of HARQ information on the Uu interface for sidelink transmission on the sidelink. For example, when the UE receives the scheduling DCI or decodes the PUCCH resource indicator field, the UE may obtain the corresponding through the dedicated RRC - configured PUCCH - ResourceSet within PUCCH - Config, or through the common RRC - configured pucch - ResourceCommon within SIB1 if no dedicated RRC configuration is configured. For a UE with scheduled transmission on the sidelink, the UE may send feedback to gNB201 using the allocated resources through the Uu interface. For example, the scheduling DCI may carry one DCI field indicating the resources used for transmission of HARQ feedback from a V2X UE (e.g., Tx UE202) to gNB201, e.g., a PUCCH resource indicator field, where each value is associated with a PUCCH resource configured by the RRC configuration or pre - indexed by the standard. The PUCCH resources to be used can be determined.

[0229] Alternatively, for the transmission of HARQ information on the Uu interface for sidelink transmissions in the sidelink, the UE may be configured using different sets of common or dedicated configurations. For example, the UE may, through broadcast signaling, for example, through RMSI or OSI, be configured using the common RRC configuration pucch-sl-ResourceCommon or the UE may be configured using the dedicated RRC configuration SL-PUCCH-ResourceSet. In a case where only one of the common configuration and the dedicated configuration is supported, when the UE receives scheduling DCI and decodes the PUCCH resource indicator field, the UE can determine the corresponding PUCCH resources

[0230] through the configured pucch-sl-ResourceCommon or the configured SL-PUCCH-ResourceSet. When the UE receives scheduling DCI and decodes the PUCCH resource indicator field, the UE can determine the corresponding PUCCH resources through the configured pucch-sl-ResourceCommon or the configured SL-PUCCH-ResourceSet. In a case where both the common configuration and the dedicated configuration are supported, when the UE receives scheduling DCI

[0231] or decodes the PUCCH resource indicator field, the UE can determine the corresponding PUCCH resources through the dedicated RRC configuration SL-PUCCH-ResourceSet or, if the dedicated RRC configuration is not configured, through the common RRC configuration pucch-sl-ResourceCommon. In another example, the scheduling DCI is for a V2X UE (e.g., Tx UE202) through the dedicated RRC configuration SL-PUCCH-ResourceSet or, if the dedicated RRC configuration is not configured,

[0232] through the common RRC configuration pucch-sl-ResourceCommon. One DCI indicating the timing for transmitting HARQ feedback to gNB201 field, for example, when carrying a UL HARQ timing indicator field exists.

[0233] In one approach, the indicated timing may be the time offset between the HARQ feedback (from the V2X UE to gNB201) and the initial transmission on the scheduled sidelink. For example, the UE may be RRC configured using candidate time offsets through the RRC parameter sl-InitialDataToUL-ACK with the content of "SEQUENCE(SIZE(8))OF INTEGER(0..15)", where the time offset may be within a slot, a mini-slot, or a symbol. When the UE receives the scheduling DCI and decodes the UL HARQ timing indicator field, the UE can determine the time offset by finding the corresponding entry in the configured RRC parameter sl-InitialDataToUL-ACK.

[0234] In a second approach, the indicated timing may be the time offset between the HARQ feedback (from the V2X UE to gNB201) and the scheduled HARQ feedback transmitted on the sidelink (from the Rx UE203 to the Tx UE202). For example, the UE may be RRC configured using candidate time offsets through the RRC parameter sl-ACKToUL-ACK with the content of "SEQUENCE(SIZE(8))OF INTEGER(0..15)", where the time offset ​​​​​​​​​​T may be within a slot, a mini-slot, or a symbol. When the UE receives scheduling DCI or decodes the UL HARQ timing indicator field, the UE can determine the time offset by finding the corresponding entry in the configured RRC parameter sl-ACKToUL-ACK.

[0235] In a third approach, the indicated timing may be the time offset between the HARQ feedback (from the V2X UE to gNB201) and the scheduled last retransmission / repeat of the TB transmission on the sidelink. Assuming that k retransmissions / repeats are scheduled by the scheduling DCI, the UL HARQ timing indicator field indicates the time offset between the HARQ feedback and the scheduled k-th retransmission / repeat. If there is no scheduled retransmission, e.g., when k = 0, the UL HARQ timing indicator field indicates the time offset between the HARQ feedback and the scheduled initial transmission. For example, the UE may be configured through the RRC parameter sl-LastDataToUL-ACK with the content of "SEQUENCE(SIZE(8))OF INTEGER(0..15)" to use candidate time offsets, where the time offset may be within a slot, a mini-slot, or a symbol. When the UE receives the scheduling DCI and decodes the UL HARQ timing indicator field, the UE finds the corresponding entry in the configured RRC parameter By finding a bird, the time offset can be determined. When the gNB uses a dynamic s cheduling grant to schedule sidelink transmission, the gNB 201 may schedule the initial transmission of the TB when using one DCI and the multiple retransmissions / repetitions of the TB.

[0236] When the gNB 201 dynamically schedules the sidelink transmission of the TB using DCI, the gNB 201 may schedule one or more retransmissions / repetitions of the TB using the same scheduling DCI. Retransmission or HARQ feedback may be ) DCI-scheduled sidelink blind retransmission, 2) DCI-scheduled HA RQ feedback-based sidelink retransmission, or 3) DCI-scheduled HAR Q feedback-based Uu interface transmission type early termination with retransmission means, and may be performed by the Tx UE 202 or the Rx UE 203.

[0237] DCI-scheduled sidelink blind retransmission DCI-scheduled sidelink blind retransmission: In some cases, after receiving the scheduling DCI, the Tx UE 202 may blindly transmit all the scheduled transmissions. For example, the Tx UE 202 may perform all the scheduled initial transmissions and retransmissions / repetitions regardless of whether the Rx UE 203 has successfully decoded the data. In this case, for one HARQ feedback resource allocation, the DCI schedules the Rx UE 203 to transmit HARQ feedback to the Tx UE 202 via sidelink, and one HARQ feedback resource is allocated for the Rx UE 203 to transmit HARQ feedback to the Tx UE 202 via sidelink, and one HARQ feedback Resource allocation may be scheduled by DCI for the Tx UE202 to transmit HARQ feedback on the Uu interface to the gNB201. The scheduling DCI schedules the initial transmission in slot 0, and two retransmissions in slot 1 and slot 2 respectively, as shown in FIG. 20. The transmission of the SCI is scheduled in slot 0, and the HARQ feedback transmission from the Rx UE203 to the Tx UE202 is scheduled in slot 2, and the HARQ feedback transmission from the Tx UE202 to the gNB201 is scheduled in slot 3. In the example shown in the figure, the initial transmission and retransmissions are scheduled in consecutive slots. In another example, the initial transmission and retransmissions may be scheduled in non-consecutive slots. For

[0238] example, the initial transmission may be scheduled in slot 0, and the two retransmissions may be scheduled in slot 2 and slot 4 respectively. The Rx UE203 can determine the scheduled initial transmission and retransmissions by decoding the SCI. If the Rx UE203 fails to receive the uplink transmission after all repetitions, the Rx UE203 can use the scheduled HARQ

[0239] feedback resource, e.g., the HARQ feedback resource in slot 2 of FIG. 20, to send a NACK to the Tx UE202. If the Rx UE203 successfully receives the uplink transmission, the Rx UE203 can use the scheduled HARQ feedback resource to send an ACK to the Tx UE202, or the Rx UE203 may not use the scheduled HARQ feedback resource. If the Rx UE203 successfully receives the uplink transmission, the Rx UE203 can use the scheduled HARQ feedback resource to send an ACK to the Tx UE202, or the Rx UE203 may not use the scheduled HARQ feedback resource. UE203 may not need to transmit anything to Tx UE20 2 on the scheduled HARQ feedback resource. If Rx UE203 successfully receives a sidelink transmission before all scheduled retransmissions, for example, if Rx UE203 successfully receives a sidelink transmission after the initial transmission or after the first retransmission, Rx UE203 may skip the remaining scheduled retransmissions and may not attempt to decode the PSSCH.

[0240] After Tx UE202 receives HARQ feedback, such as ACK or NACK, from Rx UE203, Tx UE202 may use the scheduled HARQ feedback resource on the Uu interface, for example, the HARQ feedback resource in slot 3 of FIG. 20, to transmit HARQ feedback to gNB201.

[0241] DCI-Scheduled HARQ Feedback-Based Sidelink Retransmission DCI-Scheduled HARQ Feedback-Based Sidelink Retransmission: Another Case In another case, the scheduling DCI may schedule HARQ feedback-based sidelink retransmissions. FIG. 21 shows an example where the scheduling DCI schedules the initial transmission in slot 0 and two retransmissions in slots 1 and 2 respectively. The scheduling DCI schedules the transmission of HARQ feedback from Rx UE203 to Tx UE202 associated with the initial transmission and two retransmissions in slots 0, 1, and 2 respectively. The transmission of the SCI is scheduled in slot 0, and the transmission of HARQ feedback from Tx UE202 to gNB201 is scheduled. is scheduled in slot 3...

Claims

1. A first wireless transmit / receive unit (WTRU) including a processor, The processor, receiving a Radio Resource Control (RRC) message including an indication of a Sidelink Radio Network Temporary Identifier (SL-RNTI); receiving Downlink Control Information (DCI) from the base station using the SL-RNTI indicating resource allocation for a Physical Sidelink Shared Channel (PSSCH) transmission to at least a second WTRU, the DCI indicating a time and resources for the first WTRU to transmit Hybrid Automatic Repeat Request (HARQ) feedback associated with the PSSCH transmission to the base station; transmitting, to at least the second WTRU, sidelink control information (SCI) indicating a resource allocation for the PSSCH transmission according to the DCI; transmitting the PSSCH transmission to the second WTRU in accordance with the SCI; receiving HARQ feedback for the PSSCH transmission from the second WTRU; transmit the HARQ feedback received from the second WTRU to the base station according to the time and resources indicated in the DCI. A first WTRU configured to:

2. The first WTRU of claim 1, wherein resources for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station correspond to Physical Uplink Control Channel (PUCCH) resources indicated in the RRC message.

3. The first WTRU of claim 1, wherein the SCI includes a time resource allocation field and a frequency allocation field.

4. The first WTRU of claim 1, wherein the DCI includes an indication of a HARQ process for the PSSCH transmission.

5. The first WTRU of claim 1, wherein the RRC message indicates that the PSCCH transmission corresponds to a unicast transmission.

6. The first WTRU of claim 1, wherein the RRC message includes configuration information associated with a plurality of PUCCH resources used to feed back HARQ sidelink feedback to the base station, the configuration information indicating frequency information corresponding to each of the plurality of PUCCH resources, and the RRC message indicating an index corresponding to each of the plurality of PUCCH resources.

7. A first WTRU as described in claim 6, wherein a resource for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station is indicated in the DCI using an index corresponding to one of the multiple PUCCH resources.

8. A method performed by a first wireless transmit / receive unit (WTRU), comprising: receiving a Radio Resource Control (RRC) message including an indication of a Sidelink Radio Network Temporary Identifier (SL-RNTI); receiving Downlink Control Information (DCI) from the base station using the SL-RNTI indicating resource allocation for a Physical Sidelink Shared Channel (PSSCH) transmission to at least a second WTRU, the DCI indicating a time and resources for the first WTRU to transmit Hybrid Automatic Repeat Request (HARQ) feedback associated with the PSSCH transmission to the base station; transmitting, to at least the second WTRU, sidelink control information (SCI) indicating a resource allocation for the PSSCH transmission according to the DCI; transmitting the PSSCH transmission to the second WTRU in accordance with the SCI; receiving HARQ feedback for the PSSCH transmission from the second WTRU; transmit the HARQ feedback received from the second WTRU to the base station according to the time and resources indicated in the DCI. The method includes:

9. The method of claim 8, wherein resources for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station correspond to Physical Uplink Control Channel (PUCCH) resources indicated in the RRC message.

10. The method of claim 8, wherein the SCI includes a time resource allocation field and a frequency allocation field.

11. The method of claim 8, wherein the DCI includes an indication of a HARQ process for the PSSCH transmission.

12. The method of claim 8, wherein the RRC message indicates that the PSCCH transmission corresponds to a unicast transmission.

13. The method of claim 8, wherein the RRC message includes configuration information associated with a plurality of PUCCH resources used to feed back HARQ sidelink feedback to the base station, the configuration information indicating frequency information corresponding to each of the plurality of PUCCH resources, and the RRC message indicating an index corresponding to each of the plurality of PUCCH resources.

14. The method of claim 13, wherein a resource for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station is indicated in the DCI using an index corresponding to one of the plurality of PUCCH resources.

15. A base station including a processor, The processor, sending a Radio Resource Control (RRC) message to the first Wireless Transmit / Receive Unit (WTRU) including an indication of a Sidelink Radio Network Temporary Identifier (SL-RNTI); transmitting Downlink Control Information (DCI) indicating resource allocation for a Physical Sidelink Shared Channel (PSSCH) transmission from the first WTRU to at least a second WTRU, the DCI indicating a time and resources for the first WTRU to transmit Hybrid Automatic Repeat Request (HARQ) feedback associated with the PSSCH transmission to the base station using the SL-RNTI; receiving HARQ feedback from the first WTRU corresponding to HARQ feedback for the PSSCH transmission received by the first WTRU from the second WTRU according to the time and resources indicated in the DCI; A base station configured to 16. The base station of claim 15, wherein resources for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station correspond to Physical Uplink Control Channel (PUCCH) resources indicated in the RRC message.

17. The base station of claim 15, wherein the DCI includes an indication of a HARQ process for the PSSCH transmission.

18. The base station of claim 15, wherein the RRC message indicates that the PSCCH transmission corresponds to a unicast transmission.

19. The base station of claim 15, wherein the RRC message includes configuration information associated with a plurality of PUCCH resources used to feed back HARQ sidelink feedback to the base station, the configuration information indicating frequency information corresponding to each of the plurality of PUCCH resources, and the RRC message indicating an index corresponding to each of the plurality of PUCCH resources.

20. The base station of claim 19, wherein a resource for the first WTRU to transmit the HARQ feedback associated with the PSSCH transmission to the base station is indicated in the DCI using an index corresponding to one of the plurality of PUCCH resources.

Images