Uu-based sidelink control for NR V2X

Abstract

Different sidelink resource configurations and allocation methods may be controlled by an interface, such as the Uu interface. Radio resource control configurations may include dynamic allocation of broadcast sidelink transmission, unicast sidelink transmission, or group sidelink transmission. There may be static resource allocations configured by radio resource control for broadcast sidelink transmission, unicast sidelink transmission, or group sidelink transmission.

Description

Technology Field

[0001] Cross-reference regarding related applications

[0002] This application claims the benefit of U.S. Provisional Application No. 62 / 737,257 filed September 27, 2018 and U.S. Provisional Application No. 62 / 754,326 filed November 1, 2018, the contents of which are incorporated herein by reference in their entirety. Background Technology

[0003] As V2X (Vehicle-to-everything) applications are making significant progress, the transmission of short messages regarding the vehicles' own status data for basic safety needs to be expanded to the transmission of larger messages that include raw sensor data, vehicle intent data, coordination, and confirmation of future operations. For these advanced applications, the anticipated requirements to meet the necessary data rates, latency, reliability, communication range, and speed become more stringent.

[0004] For enhanced V2X (eV2X) services, 3GPP identified 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.).

[0005] A set of normative requirements is specified in TS 22.186 (GPP TS 22.186 Enhancement of 3GPP support for V2X scenarios (Stage 1), Release 15, V15.3.0), and the use cases are classified into four use case groups: vehicle platooning, extended sensors, advanced driving, and remote driving. There is a detailed description of the performance requirements for each use case group specified in TS 22.186.

[0006] In Release 14 LTE V2X, the basic requirements for V2X services were supported for road safety services, for example, to support low latency and reliable exchange of messages between vehicles and infrastructure to improve safety and efficiency.

[0007] To meet latency requirements and accommodate high Doppler spreads and high vehicle density for V2X communications, sidelink transmission modes 3 and 4 are specified in TS 36.213 (3GPP TS 36.213 Physical layer procedures, Release 15, V15.2.0).

[0008] Mode 3 uses a centralized eNB scheduler. The vehicle user equipment (UE) and the eNB use the Uu interface to communicate. The eNB schedules the vehicle UE's PSCCH and PSSCH for sidelink communication using Downlink Control Information (DCI) format 5A.

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

[0010] Mode 1 supports the gNB to allocate sidelink resources to both dedicated sidelink carriers and shared permission carriers between the Uu and the sidelink via the Uu interface. Resources used for sidelink transport can be dynamically allocated, pre-configured by RRC, or based on enabling and disabling.

[0011] Different sidelink resource configurations and allocation methods that can be controlled by an interface such as a Uu interface are disclosed herein. For example, the following mechanisms for resource allocation on a sidelink may be Uu-based: 1) RRC configurations; 2) DCI signaling; 3) scheduling sidelink transmissions; 4) designs of groupcast sidelinks; or 5) measurement and reporting on the sidelink.

[0012] RRC configurations may include, in particular, 1) dynamic resource allocation for broadcast, unicast, or group sidelink transmission; 2) RRC configuration static resource allocation for broadcast, unicast, or group sidelink transmission; 3) enable / disable (e.g., enable or disable) based semi-permanent resource allocation for broadcast sidelink transmission; 4) enable / disable based semi-permanent resource allocation for unicast sidelink transmission; or 5) enable / disable based semi-permanent resource allocation for groupcast sidelink transmission.

[0013] DCI signaling is additionally initiated, and the gNB can schedule, in particular, sidelink transmissions, groupcast sidelink designs, and mechanisms for measurement and reporting on the sidelink.

[0014] This summary is provided to introduce, in a simplified form, selected from the concepts further described in the following detailed description. This summary is not intended to identify the principal or essential features of the claimed subject matter, nor is it used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to any or all limitations addressing any of the disadvantages mentioned in any part of this disclosure. Brief explanation of the drawing

[0015] A more detailed understanding can be obtained from the following description, given as an example in relation to the attached drawings. Figure 1 illustrates an exemplary DCI for scheduling PSCCH and PSSCH. Figure 2 illustrates an exemplary slot format for a side link. Figure 3 illustrates an exemplary call flow of a gNB-triggered retransmission for a unicast sidelink. Figure 4 illustrates an exemplary call flow of an Rx UE-triggered retransmission for a unicast sidelink. Figure 5 illustrates an exemplary slot format for a unicast sidelink. Figure 6 illustrates an exemplary call flow of a gNB-triggered retransmission for a group cast sidelink. Figure 7 illustrates an exemplary call flow of an Rx UE-triggered retransmission for a group cast sidelink. FIG. 8 illustrates an exemplary display (e.g., a graphical user interface) that can be generated based on methods, systems, and devices for reducing mobility signaling load. FIG. 9a illustrates an exemplary communication system. FIG. 9b illustrates an exemplary system including RANs and core networks. FIG. 9c illustrates an exemplary system including RANs and core networks. FIG. 9c illustrates an exemplary system including RANs and core networks. FIG. 9e illustrates another exemplary communication system. FIG. 9f is a block diagram of an exemplary device or apparatus such as WTRU. Figure 9g is a block diagram of an exemplary computing system. FIG. 10 illustrates an exemplary transmission for scheduling DCIs for both Tx UE and Rx UE, along with HARQ feedback transmitted from Rx UE to gNB. FIG. 11 illustrates an exemplary transmission for scheduling DCIs for both Tx UE and Rx UE, along with HARQ feedback transmitted from Rx UE to Tx UE. FIG. 12 illustrates an exemplary transmission for scheduling DCIs for both Tx UE and Rx UE, along with HARQ feedback transmitted from Rx UE to Tx UE and feedback from Tx UE to gNB. FIG. 13 illustrates an exemplary transmission for scheduling a DCI for a Tx UE with HARQ feedback transmitted from the Rx UE to the gNB. FIG. 14 illustrates an exemplary transmission for scheduling a DCI for a Tx UE with HARQ feedback transmitted from an Rx UE to a Tx UE. FIG. 15a illustrates an exemplary transmission for scheduling a DCI for a Tx UE, along with HARQ feedback transmitted from the Rx UE to the Tx UE and feedback from the Tx UE to the gNB. FIG. 15b illustrates an exemplary method for scheduling DCI for a Tx UE with HARQ feedback transmitted from the Rx UE to the Tx UE and feedback from the Tx UE to the gNB. FIG. 16 illustrates an exemplary transmission for scheduling DCI for both Tx UE and Rx UE using a shared carrier for the Uu interface and sidelink. Fig. 17 is an exemplary PSCCH-TimeDomainResourceAllocationList Visualizes information elements. Fig. 18 is an exemplary PSSCH-TimeDomainResourceAllocationList Visualizes information elements. Fig. 19 shows an exemplary RRC configuration PSFCH-Resource City. FIG. 20 illustrates an exemplary DCI dynamically scheduled sidelink transmission with blind retransmission. FIG. 21 illustrates an exemplary DCI dynamically scheduled sidelink transmission with HARQ feedback-based retransmission. FIG. 22 illustrates an exemplary DCI dynamically scheduled sidelink transmission with HARQ feedback-based retransmission and early termination transmitted over the Uu interface. Specific details for implementing the invention

[0016] Problem 1: In new radio (NR) V2X mode 1, the base station schedules sidelink resources used by the UE for sidelink communication. NR V2X must support dynamic resource allocation for sidelinks, enable / disable-based resource allocation, and RRC (pre)configured resource allocation. Mechanisms to support the aforementioned NR V2X resource allocation technologies need to be introduced.

[0017] In LTE Mode 3, time-domain resources used for V2X sidelink transmission must be based on a pre-configured subframe resource pool. The granularity of pool-based resource allocation lies in the subframes. In NR V2X, both aperiodic and periodic traffic on the sidelink must be supported. This subframe-based resource allocation design may not meet latency requirements. Therefore, enhancements to Uu-based resource allocation are necessary to support lower latency.

[0018] Problem 2: In NR V2X Mode 1, broadcast, group cast, or unicast sidelink communication must also be supported. In LTE V2X, only broadcast sidelink communication is supported. Therefore, mechanisms for allocating resources for group cast or unicast sidelink communication in NR V2X need to be introduced. A UE may consist of multiple resources for broadcast, group cast, or unicast sidelink communication. When a UE receives a scheduling acknowledgment, the UE must be able to determine which type of sidelink communication the received acknowledgment is to be used for. Mechanisms to resolve this problem need to be introduced.

[0019] A UE may be composed of multiple resources for broadcast, group cast, or unicast sidelink communication. When a UE receives a scheduling acknowledgment, the UE must be able to determine which type of sidelink communication the received acknowledgment is intended for. Mechanisms need to be introduced to address this issue.

[0020] In LTE V2X, the receiver UE continuously attempts to decode the Physical Sidelink Control Channel (PSCCH) from each candidate PSCCH resource configured by the upper layers. While this is acceptable for LTE because V2X receiver resources are relatively sparse in terms of time, it can be very power-inefficient in NR, considering NR V2X requirements where the density of V2X receiver monitoring opportunities can be much higher. For example, in NR V2X, the UE may be configured with multiple resources for broadcast, groupcast, and unicast sidelink communication. In addition, the configuration of NR V2X receiver resources must be considered not only for periodic traffic but also for non-periodic traffic, which may require different sets of resources to be configured. Therefore, if applied directly to NR, the current design for receiving PSCCH in LTE can cause massive power consumption issues in NR because the number of PSCCH blind decodings can increase dramatically.

[0021] Different sidelink resource configurations and allocation methods that can be controlled by an interface such as the Uu interface are disclosed in this specification.

[0022] Uu-based dynamic resource approval allocation for sidelinks

[0023] Broadcast sidelink transmission

[0024] Broadcast Sidelink Transmission: In NR V2X, a gNB (e.g., gNB (201) of FIG. 3 or FIG. 9a) or a gNB-type node (e.g., a base station) may dynamically allocate resources used by a UE (e.g., UE of FIG. 3 or FIG. 9a) for broadcast sidelink transmission. As disclosed herein, the UE may be allocated resources for broadcast sidelink transmission through RRC configuration and DCI signaling. When the UE receives a scheduling DCI, the UE may broadcast control and data using the scheduled resources on the sidelink. A detailed resource allocation method is as follows.

[0025] Detailed design for RRC configuration: A UE may be composed of one or more information elements (IEs), wherein each IE specifies configuration information for resources for NR V2X sidelink transmission. Different IEs for supporting broadcast, group cast, and unicast sidelink transmission in NR V2X are disclosed herein, for example, NR-SL-Resource-Broadcast , NR-SL-Resource-Groupcast , or NR-SL-Resource-Unicast It can be used to configure information about resources for sidelink transmission, or if the type of sidelink transmission (e.g., broadcast, groupcast, or unicast) is specified in IE, the same IE (e.g., NR-SL-Resource ) can be used.

[0026] For broadcast sidelink transmission, IE NR-SL-Resource or NR-SL-Resource-Broadcast It can carry configuration information for sidelink control or sidelink data transmission. The UE can transmit via broadcasted signals, for example, via OSI or through common or dedicated RRC configurations on the Uu interface. NR-SL-Resource or NR-SL-Resource-Broadcast It may be composed of. The IE disclosed in this specification NR-SL-Resource or NR-SL-Resource-Broadcast It can specifically carry the following RRC configurations: 1) type of sidelink transmission; 2) type of carrier; 3) numerology of the resource; 4) broadcast transmission UE; 5) mask used to scramble the scheduling DCI; 6) index of candidate resource; 7) candidate time domain resources of the resource configuration; 8) number of iterations and duplicate versions; 9) candidate frequency domain resources of the resource configuration; or 10) beam sweeping.

[0027] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types NR-SL-Resource When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0028] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0029] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology is. Or, a numerology can be configured for each BWP.

[0030] This is an RRC configuration for indicating the UE sidelink ID for broadcast transmission on the sidelink. For broadcast sidelink transmission, the UE can be configured with a UE ID as either a source ID or a destination ID on the sidelink. For example, the UE is a sidelink broadcast transmission RNTI to be used as the source ID ( SL-BT-RNTI It can be composed of ). The UE is a sidelink broadcast receiving RNTI that is used as a destination ID where each destination ID can be associated with a different service ( SL-BR-RNTI It can be composed of ).

[0031] When generating Sidelink Control Information (SCI) for broadcast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, and the other is 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.

[0032] This is an RRC configuration to indicate the mask used to scramble the scheduling DCI. For example, the UE is SLBroadcast-RNTI or SL-RNTI It can be composed of. gNB is composed SLBroadcast-RNTI or SL-RNTI It can generate and transmit a scheduling DCI for a UE having a CRC scrambled by. The UE is configured SLBroadcast-RNTI or SL-RNTI DCI can be decoded using .

[0033] This is an RRC configuration for displaying an index of candidate resources. A UE may be composed of multiple configurations of resources for sidelink transport, for example, multiple resource pools. Each configuration of resources may be associated with a single dedicated resource index. For example, RRC configuration NR-SL-Resource-IndexThe UE can determine the configuration of resources to be used for sidelink transmission through the DCI that schedules sidelink transmission.

[0034] The RRC configuration is for indicating candidate time domain resources of a resource configuration, e.g., time domain resources of each resource pool. As disclosed, candidate time domain resources for broadcast sidelink transmission for each candidate resource may be configured with the following alternatives:

[0035] Alternative 1 - Candidate Time Domain Resources: The UE may be configured with one or more bitmaps by RRC configuration to represent candidate time domain resources for sidelink transmission. The bitmap may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0036] When the UE receives a DCI carrying a scheduling acknowledgment of a transmission on the sidelink, the UE may perform a transmission starting from the next available time resource within the configured candidate time resources. A minimum time gap constraint may be applied when the UE switches from receive mode to transmit mode, and the UE may perform a transmission starting from the next available time resource after a minimum time gap within the configured candidate time resources.

[0037] Alternatively, the UE may be configured with an offset value to indicate a time resource to be used for sidelink transmission within the configured candidate time resources. The offset value may be signaled by a DCI carrying a scheduling acknowledgment. The offset value may indicate an offset between a time resource for sidelink transmission and a time resource used to transmit the scheduling acknowledgment DCI; or the offset value may indicate an offset between a time resource for sidelink transmission after a minimum time gap within the configured candidate time resources and the next available time resource.

[0038] Alternative 2 - Candidate Time Domain Resources: The UE may be dynamically signaled by the DCI for time resources used for broadcast sidelink transmission. The UE may not be configured with candidate time domain resources through RRC configuration. The DCI carrying the scheduling acknowledgment may indicate the time resources used for broadcast sidelink transmission.

[0039] This is an RRC configuration for displaying beam sweeping information. For broadcast sidelink transmission, the transmitter UE (202) can broadcast information in multiple directions using multiple beams. The UE needs to recognize the number of beam sweeps that the UE needs to perform and the corresponding resources.

[0040] Alternative 1 - Beam Sweeping Information: The gNB can determine the number of beam sweeps that the UE must perform. For example, the UE may be configured with the number or maximum number of beam sweeps via RRC configuration. Alternatively, the number of beam sweeps may be signaled by the DCI. The UE may provide auxiliary information to Node B (e.g., a base station such as a gNB or eNB) to assist the NB in ​​determining the beam sweeping configuration. This auxiliary information may include one or more of the following: V2X services of interest, e.g., UE capabilities regarding the number of simultaneous beam sweeping directions the UE can cover, UE scheduling preferences including sleep mode preferences, etc.

[0041] UE k Assuming it is configured to broadcast information through several directions / beams, the UE k Time and frequency resources of the configuration, for example, k Time and frequency resources for each direction / beam can be allocated through RRC configuration for beam sweeping of each direction and DCI signaling. The UE k If it is necessary to broadcast in several directions, the UE typically k It is necessary to form beams (correspondingly, direction / beam), and each beam targets one direction. To cover all directions, the UE k Beam sweeping of the formed beam can be performed.

[0042] Alternatively, the UE may be assigned a single configuration of time and frequency resources. In one possibility, the assigned time and frequency resources may be used for all beams. The UE may use the assigned time resources k It can be uniformly divided into parts, and each part can be used for a single beam. In other possibilities, allocated time and frequency resources can be used for a single beam. For example, the UE can use time resources across beam sweeping directions as follows. In Option 1 of this Alternative 1 for beam sweeping, the UE uses the time and frequency resources allocated for the first beam sweeping, and can use the next available time resources from a configured resource pool in which the same time duration and the same frequency resources used for the first beam sweeping are used for the remainder of the beam sweeping. For example, the UE is configured with time resources in mini-slots, and the UE for the first beam sweeping mini-slot n Assume that it is configured to use. The UE uses mini-slots from the resource pool configured for the rest of the beam sweeping n+1 inside n+k-1 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 transmitter UE (202) based on sensing or discovery. In Option 2 of this alternative 1 for beam sweeping, the UE may slice time resources equally on a round-robin basis across the beam sweeping directions and use the same frequency resource in each direction. In Option 3 of this alternative 1 for beam sweeping, the UE may autonomously determine how to slice time-frequency resources in both the time domain and the frequency domain across the beam sweeping directions.

[0043] Alternative 2 - Beam Sweeping Information: The UE can determine the number of beam sweeps the UE needs to perform for broadcast sidelink transmission. The UE k The values ​​of beam sweeping can be reported to the gNB. The gNB can schedule time resources for the UE for broadcast sidelink transmission.

[0044] UE is, each, k k configurations of time and frequency resources may be allocated through RRC configuration and DCI signaling for beam sweeping of k directions. 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 divide the allocated time resources evenly 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 the next available time resources from the resource pool configured for the remainder of the beam sweeping, having the same time duration and frequency resources as those used for the first beam sweeping. The beams used for beam sweeping may be indicated by gNB. Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0045] It is an RRC configuration for representing candidate frequency domain resources of a resource configuration, e.g., frequency domain resources of each resource pool. A UE may be configured with one or more SL-BWPs. Alternatively, a UE may be configured with one or more candidate frequency resources for broadcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured with the following alternatives:

[0046] Alternative 1 - Candidate Frequency Domain Resources: The UE may be configured with adjacent frequency resources as candidate frequency resources for sidelink broadcast transmission. Frequency resources may be configured in RBs or subchannels, e.g., RBGs. For example, the UE may configure parameters via RRC configuration to indicate the Start and Length Value (SLV) of the RB for the candidate frequency resource. StartRB and LengthRB It can be configured as. Alternatively, the UE can use the parameters via RRC configuration to display the RBG's SLV for candidate frequency resources. StartRBG and LengthRBG It can be configured as follows. The UE may be configured with a single candidate frequency resource for both Sidelink Control Information (SCI) transmission and Sidelink Data transmission. The UE may have two candidate frequency resources for Sidelink Control Information (SCI) transmission and Sidelink Data transmission, respectively, e.g., StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can also be composed of.

[0047] Alternative 2 - Candidate Frequency Domain Resources: The UE may be composed of non-contiguous frequency resources as candidate frequency resources for sidelink broadcast transmission. The frequency resources may be composed of RBs or subchannels, e.g., RBGs. Non-contiguous frequency resources may be composed of multiple SLVs. For example, StartRBG_1 and LengthRBG_1 , StartRBG_2 and LengthRBG_2 , ..., StartRBG_m and LengthRBG_m is. Alternatively, non-adjacent frequency resources can be configured by a start value and a bitmap. For example, StartRBG and {b m-1 , ..., b1, b0}. UE is StartRBG go kIt is configured as set to, and b m-1 Assume that is mapped to RBG k and b0 is mapped to RBG k+m.

[0048] In the case of the above alternatives, the UE may provide auxiliary information, for example, in a sidelink UE information message or in a UE auxiliary information message or similar messages, to assist the NB in ​​properly configuring the UE. Such auxiliary information may include information such as UE capabilities, carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery; V2X services for which the UE is interested; and specific BWPs within the carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery. It should be noted that in LTE, this procedure can be used to notify the E-UTRAN of the UE’s power saving preference and SPS auxiliary information, maximum physical downlink shared channel / physical uplink shared channel (PDSCH / PUSCH) bandwidth configuration preference, etc., while the sidelink UE information message can be used to notify the NB that the UE is interested in or no longer interested in requesting the allocation or deallocation of transmission resources for V2X sidelink communication, V2X sidelink discovery gap, etc., as well as receiving sidelink communication or discovery, receiving V2X sidelink communication.

[0049] The previously mentioned RRC configurations are IE NR-SL-Resource or NR-SL-Resource-Broadcast Note that it can be configured through, or that some of the aforementioned RRC configurations can be configured by other IEs used for sidelink configuration.

[0050] Detailed Design for DCI Signaling: The UE can be dynamically signaled via a DCI for broadcast sidelink transmission as a scheduling acknowledgment. For example, a new DCI format, e.g., DCI Format 3, may be used to schedule PSCCH and PSSCH for broadcast sidelink transmission. To support the dynamic scheduling of resources for broadcast, groupcast, or unicast sidelink transmission, the gNB may dynamically transmit a scheduling DCI. To distinguish the scheduling DCI, different RNTIs may be used to scramble the CRC of the DCI for scheduling broadcast, groupcast, or unicast sidelink transmission. For example, SLBroadcast-RNTI , SLGroup-RNTI , SLUnicast-RNTI It can be used to scramble the DCI's CRC to schedule broadcast, group cast, or unicast, respectively. The UE, through RRC configuration SLBroadcast-RNTI , SLGroup-RNTI , SLUnicast-RNTI It can be composed of.

[0051] As an alternative, a single RNTI may be used to scramble the DCI's Cyclic Redundancy Check (CRC) to schedule broadcast, group cast, or unicast sidelink transmissions. For example, the same RNTI used to scramble the DCI's CRC to schedule broadcast, group cast, or unicast, e.g., SL-RNTI It may be used. Fields within the scheduling DCI may be used to indicate that the DCI is used to schedule broadcast, group cast, or unicast.

[0052] It is disclosed that, for scheduling resources for broadcast sidelink transmission, a scheduling DCI may carry, in particular, the following information: 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) a frequency domain resource allocation field; or 8) a slot format indicator (SFI) field.

[0053] This is a Bandwidth Part (BWP) indicator field. A UE may be configured with multiple BWPs via RRC configuration for sidelink communication. The scheduling DCI may indicate the BWP to be used for broadcast sidelink transmission. Alternatively, the scheduling DCI may indicate that the UE needs 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 broadcast sidelink transmission with or that the UE needs to switch to. Assuming the UE is configured with four BWPs, a 2-bit BWP indicator field may be used, such as '00' indicating the first configured BWP and '01' indicating the second configured BWP. Some fields may be dedicated from a bitmap and may be used to indicate the initial BWP and the default BWP. For example, '00' may indicate the initial BWP used, for instance, for discovery and synchronization. Alternatively, '00' may indicate the default BWP. In another alternative, '00' can display the initial BWP, while '01' can display the default BWP.

[0054] This is a resource indicator field. A UE may be composed of multiple resource configurations via RRC, for example, multiple resource pools. The scheduling DCI may indicate an index of the configuration of resources to be used for broadcast sidelink transmission. Assuming the UE is composed of eight resource configurations, for example, configurations 0 through 7, a 3-bit resource indicator field may be used, having '000' indicating configuration 0, '001' indicating configuration 1, etc.

[0055] This is a sidelink type indicator field. A scheduling DCI can indicate the type of sidelink transmission. For example, a 2-bit sidelink type indicator field may be used, having '00' to indicate that the DCI is scheduling a broadcast sidelink transmission, '01' to indicate that the DCI is scheduling a groupcast sidelink transmission, '10' to indicate that the DCI is scheduling a unicast sidelink transmission, etc.

[0056] This is the Carrier Type Indicator field. The UE can be dynamically indicated by a carrier type with 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 permission carrier between the UE and the sidelink; if the Carrier Type Indicator field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0057] This is a time domain resource allocation field. A UE can be signaled to a scheduled time domain resource via a DCI having the following alternatives.

[0058] Alternative 1 - Time Domain Resource Allocation: A UE can be configured with one or more candidate resources through RRC configuration. The scheduling DCI can designate a time domain resource among the candidate resources to be used for broadcast sidelink transmission.

[0059] To determine the start of a time domain resource, 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 resource for broadcast sidelink transmission. The time units may be in subframes, slots, mini-slots, or symbols. Alternatively, the UE may be signaled with a two-level time offset to determine the starting point of the time domain resource. For example, the UE may be signaled with a slot / subframe (i.e., slot or subframe) offset to determine which slot / subframe the time domain resource starts from. Subsequently, the UE may be signaled with an index of a start symbol / mini-slot (i.e., slot or mini-slot) to determine the starting point within the slot / subframe. In one example, the two-level time offset may be signaled separately by two DCI fields, for example, through the slot-level offset indicator field and the start symbol indicator field.

[0060] In another example, a 2-level time offset may be indicated by a single DCI field. For example, a table may include combinations of slot-level offsets and start symbols, each combination may be predefined or (pre-)configured by an RRC configuration associated with an index. A UE may be signaled by a scheduling DCI having a single index through the DCI field. The UE can determine the time domain start point by finding the corresponding 2-level offset from the table. The examples described herein may also apply to dynamic resource allocation for groupcast sidelink transmission or unicast sidelink transmission.

[0061] To determine the duration of time domain resources, a bitmap or the length of the duration may be indicated by the scheduling DCI. In an example, the UE may be signaled with a bitmap. The bitmap may indicate which time resources within the candidate resources configured by Radio Resource Control (RRC) are used for broadcast sidelink transmission. In another example, the UE indicates the length of the time domain resource, e.g., l It can be signaled as. Next, the UE within the RRC-configured candidate resources for broadcast sidelink transmission l Adjacent resource units may be available. Resource units may be in subframes, slots, mini-slots, or symbols.

[0062] Fields for indicating the start and duration of a time domain resource may also be signaled through a single DCI field. For example, a predefined or pre-configured table may contain combinations of the start and duration of a time domain resource, each having a combination associated with an index. A UE may be signaled by a scheduling DCI having a single index through a single DCI field. The UE can determine the time domain resource by finding the corresponding start or duration values ​​from the table.

[0063] Alternative 2 - Time Domain Resource Allocation: A UE may not be configured with candidate resources via RRC configuration. A UE may be dynamically indicated as a time domain resource for broadcast sidelink transmission by a scheduling DCI. The DCI may carry information such as slot / subframe offsets, start points, and durations of the time domain resource. The slot / subframe offset may relate to the slot / subframe used for receiving the DCI. The aforementioned parameters may be indicated by different DCI fields or jointly by DCI fields. For example, a time domain resource may be dynamically signaled by the slot / subframe offset value and the SLV through the scheduling DCI alone.

[0064] For broadcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE can be represented by a single time domain resource, and time domain resources for all directions can be determined by some predefined rules. Alternatively, the UE can be represented by a time domain resource for each direction. For example, the UE can be represented by multiple start and duration values ​​of time domain resources. Or, the UE can be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0065] For broadcast sidelink transmission, the scheduling DCI may designate time domain resources for PSCCH or PSSCH as illustrated in FIG. 1. Time domain resources for PSCCH or PSSCH may be jointly allocated by the scheduling DCI, for example, a single time domain resource allocation may be used for PSCCH or PSSCH. For example, in one approach, the UE may receive a single time domain resource allocation designating resources for PSCCH and PSSCH. When PSCCH and PSSCH are FDMed, the UE may transmit PSCCH and PSSCH over allocated time resources using different frequency resources.

[0066] When a PSCCH or PSSCH is TDMed or transmitted over different time resources, the UE can determine the time resources for the PSCCH or PSSCH, respectively, within the scheduled time resources. For example, the UE can statically configure the number of symbols spanned by the PSCCH, e.g., by the RRC. k It can be dynamically represented by scheduling DCI with dog symbols. Then, when PSCCH and PSSCH are TDMed, the UE is the first k PSCCH can be transmitted using symbols, and PSSCH can be transmitted in allocated time resources using the remaining symbols. Alternatively, if the bandwidth of PSCCH is smaller than the bandwidth of PSSCH, the UE can transmit the first k PSCCH and PSSCH can be transmitted using symbols according to frequency domain resource allocation, and PSSCH can be transmitted using the remaining symbols in the allocated time resources.

[0067] In another approach, the UE may receive a time-domain resource allocation indicating resources for a PSSCH, and the UE may determine time-domain resources for the PSCCH in response, or 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 with an offset between the PSCCH and PSSCH by an RRC configuration, where the RRC configuration may include both a slot-level offset and a symbol-level offset. The UE may be indicated by a scheduling DCI having a time-domain resource allocation for the PSSCH and determines time-domain resources for the associated PSCCH based on the configured offset(s). The examples described herein may also apply to dynamic resource allocation for groupcast sidelink transmission and unicast sidelink transmission.

[0068] Alternatively, time domain resources for PSCCH and PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time domain resources for PSCCH and PSSCH, respectively. For example, there is a DCI field for allocating time domain resources for PSCCH and a DCI field for allocating time domain resources for PSSCH, and each field may indicate an index corresponding to an entry in the RRC configuration. For example, the UE is an information element PSCCH_AllocationList and information elements PSSCH_AllocationList RRC can be configured separately.

[0069] Information elements PSCCH_AllocationList is a list of configured time domain resource allocations (one or more) for PSCCH, e.g., information element PSCCH_TimeDomainResourceAllocation It may include a list of, where each indexed row is the scheduling DCI and the scheduled PSCCH (e.g., kxConfigures the slot offset, start and length indicator SLIV, etc. between ). Information element PSCCH - TimeDomain ResourceAllocationList An example is illustrated in FIG. 17. Assuming that 3 bits are used in the PSCCH time domain resource allocation field, an example is illustrated in Table 1. The examples illustrated herein for PSCCH may also be applied to dynamic resource allocation for group cast sidelink transmission and unicast sidelink transmission.

[0070] In groupcast sidelink transmission or unicast sidelink transmission scenarios, a two-stage SCI may be used. In scenarios where a two-stage SCI is used, the UE, for example, DCI field, first stage PSCCH time domain resource allocation field and information element First_Stage_PSCCH_TimeDomainResourceAllocation Through this, it can be explicitly marked / configured (i.e., marked or configured) as a time domain resource allocation for the transmission of the first stage SCI. In this case, the slot offset kx represents a slot offset between the scheduling DCI and the scheduled first stage PSCCH. The UE may be jointly represented, for example, through the DCI field PSSCH time domain resource allocation field, as a time domain resource allocation for the transmission of the second stage SCI and PSSCH. Subsequently, the UE may derive the time domain resources used for the transmission of the second stage SCI or the time domain resources used for the transmission of PSSCH from the received PSSCH time domain resource allocation field, for example, using the methods provided above.

[0071]

[0072]

[0073] Information elements PSSCH_AllocationList is a list of configured time domain resource allocations (one or more) for PSSCH, e.g., information element PSSCH_TimeDomainResourceAllocationIt may contain a list of, where each indexed row is a slot offset (e.g., ky Configures the ), start and length indicator values ​​(SLIV), etc. slot offset ky Regarding this, in one approach, this can be the slot offset between the scheduling DCI and the scheduled PSSCH. In another approach, the slot offset ky can be a slot offset between a scheduled PSCCH and a scheduled PSSCH. Information element PSSCH-TimeDomainResourceAllocationList An example is illustrated in FIG. 18. Assuming that 4 bits are used in the PSSCH time domain resource allocation field, an example is illustrated in Table 2. The examples illustrated herein may also be applied to dynamic resource allocation for group cast sidelink transmission and unicast sidelink transmission.

[0074] In groupcast sidelink transmission or unicast sidelink transmission scenarios, a two-stage SCI may be used. In scenarios where a two-stage SCI is used, slot offset ky may be a slot offset between a scheduled first stage PSCCH transmission and a scheduled PSSCH transmission; or may be a slot offset between a scheduled first stage PSCCH transmission and a second stage PSCCH and PSSCH transmission jointly scheduled.

[0075] Table 2

[0076]

[0077] This is a beam sweeping information field. The scheduling DCI can indicate the number of beam sweeps that the UE may need to perform. The UE can be dynamically signaled by the scheduling DCI as a value for the number of beam sweeps. Alternatively, the RRC can configure multiple potential values ​​for the number of beam sweeps, each value associated with an index. The UE can be signaled by a single index and determine the values ​​for the number of beam sweeps. The beams used for beam sweeping can be indicated by the gNB. Alternatively, the beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0078] This is a frequency domain resource allocation field. To determine frequency domain resources for broadcast sidelink transmission, the UE may be represented by information regarding the lowest resource block (RB), resource block group (RBG), or subchannel to be utilized. The UE may be signaled by an index of the lowest RB, RBG, or subchannel. Alternatively, the UE may be signaled by an offset between the lowest RB, RBG, or subchannel of the frequency domain resource allocation and the lowest RB, RBG, or subchannel of the candidate frequency domain resources configured with RRC. The offset may be located on the RBs, RBGs, or subchannels.

[0079] To determine the range of frequency domain resources, a bitmap or width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled as a bitmap. The bitmap indicates which frequency resources within the RRC-configured candidate frequency resources are used for broadcast sidelink transmission. As another example, the UE indicates the width of the frequency domain resources, e.g., w It can be signaled as. Next, for broadcast sidelink transmission, the UE w Adjacent RB, RBG, or subchannels can be used.

[0080] For broadcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE can be represented by a single frequency domain resource and can use the same frequency domain resource for transmission in all directions. Alternatively, the UE can be signaled by different frequency domain resources for transmission in each different direction.

[0081] For broadcast sidelink transmission, the scheduling DCI may designate frequency domain resources for both PSCCH and PSSCH. Frequency domain resources for PSCCH and PSSCH may be allocated jointly by the scheduling DCI, for example, a single frequency domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH or PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for PSCCH or PSSCH, respectively.

[0082] This is a Slot Format Indicator (SFI) field. The SFI may be introduced to support sidelink transmission as illustrated in FIG. 2. Within the slot, symbols used for sidelink transmission may be labeled 'S'. In the case of a UE configured as a dedicated sidelink carrier, the UE may perform sidelink transmission only for symbols labeled 'S'. Alternatively, the UE may perform sidelink transmission for symbols labeled 'S' or 'U'. In the case of a UE configured as a shared sidelink carrier between Uu and the sidelink, the UE may perform sidelink transmission only for symbols labeled 'S'. Symbols labeled 'X' may be used as gaps for switching the transmit and receive modes for the UE.

[0083] If there is a conflict between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI can overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transports for them. For example, slots m internal symbol k It is assumed that it is configured as a candidate time resource in the RRC configuration. Slot m internal symbol k If it is labeled as 'D' in SFI, the UE slot m internal symbol k It may not be treated as a candidate time resource. When the UE determines a time resource for broadcast sidelink transmission, the UE slot m symbol in k ...can be skipped. If a candidate time resource is in a mini-slot and there is a conflict for some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform a sidelink transmission for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform a sidelink transmission for the non-conflicting symbol(s) within the mini-slot.

[0084] 유니캐스트 사이드링크 전송

[0085] Unicast Sidelink Transmission: In NR V2X, a gNB or gNB-type node can dynamically allocate resources used by the UE for unicast sidelink communication. In the case of a transmitter UE (202), the UE can be allocated resources for unicast sidelink transmission through RRC configuration and DCI signaling. In the case of a receiver UE (203), the UE can be allocated resources for unicast sidelink reception through RRC configuration and DCI signaling. When the gNB schedules transmission over the sidelink, the transmitter UE (202) or the receiver UE (203) can receive a scheduling acknowledgment. By receiving the scheduling acknowledgment, the transmitter can determine the resources and beams used for transmission. By receiving the scheduling acknowledgment, the receiver UE (203) can determine the resources or beams used for reception. A similar idea can be applied to groupcast sidelink transmission. The detailed resource allocation method is as follows.

[0086] Detailed Design for RRC Configuration: For Unicast Sidelink Transmission, IE NR-SL Resource or NR-SL-Resource-Unicast It can carry configuration information for both sidelink control and sidelink data transmission. The UE can do this via broadcasted signals, e.g., OSI; or via common or dedicated RRC configurations on the Uu interface. NR-SL Resource or NR-SL-Resource-Unicast It can be composed of. IE NR-SL Resource or NR-SL-Resource-Unicast It may specifically carry the following RRC configurations: 1) type of sidelink transmission; 2) type of carrier; 3) numerology of the resource; 4) broadcast transmission UE; 5) mask used to scramble the scheduling DCI; 6) index of the candidate resource; 7) candidate time domain resources of the resource configuration; 8) number of repeat and duplicate versions; or 9) candidate frequency domain resources of the resource configuration.

[0087] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types NR-SL Resource When used, Thanksgiving , ෸룹캐스트 , or 유니캐스트 Possible RRC configuration NR-SL-CommunicationType There is.

[0088] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL Carrier type If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL Carrier type If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0089] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0090] This is an RRC configuration for indicating the unicast UE ID on the sidelink. In the case of unicast sidelink communication, the UE has a UE ID, for example, the sidelink unicast RNTI ( SL-U-RNTI It can be composed of ). For the transmitter UE (202), the UE is as a source ID SL-U-RNTI It can be used. For the receiver UE (203), the UE SL-U-RNTI It can be used as the destination ID.

[0091] To perform unicast sidelink communication, the UE needs to know the information of the paired UE. In the case of the transmitter UE (202), the ID of the paired UE is the destination ID. In the case of the receiver UE (203), the ID of the paired UE is the source ID. The UE needs the ID of the paired UE, for example, the sidelink unicast paired RNTI ( SL-UP-RNTI It can be displayed as ) through RRC configuration or through scheduling DCI.

[0092] When generating an SCI for unicast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, while the other is 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.

[0093] This is an RRC configuration to indicate the mask used to scramble the scheduling DCI. For example, the UE is SLUnicast-RNTI or SL-RNTI It can be composed of. gNB is composed SLUnicast-RNTI or SL-RNTI It can generate and transmit a scheduling DCI for a UE with a scrambled CRC. This is configured SLUnicast-RNTI or SL-RNTI DCI can be decoded using .

[0094] This is an RRC configuration for displaying an index of candidate resources. A UE may be composed of multiple configurations of resources for sidelink transport, for example, multiple resource pools. Each configuration of resources may be associated with a single dedicated resource index. For example, RRC configuration NR-SL Resource Index The UE can determine the configuration of resources to be used for sidelink transmission through the DCI that schedules sidelink transmission.

[0095] The RRC configuration is for representing candidate time domain resources of a resource configuration, e.g., time domain resources of each resource pool. As disclosed, candidate time domain resources for unicast sidelink transmission for each candidate resource may be configured with the following alternatives:

[0096] Alternative 1 - Candidate Time Domain Resources: The UE may be configured with one or more bitmaps by RRC configuration to represent candidate time domain resources for sidelink transmission. The bitmap may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or slot. {c s , c s-1 , ..., c1, c0} is mapped to symbols within a frame or slot, or {cm , c m-1 {, ..., c1, c0} are mapped to mini-slots within a frame or slot.

[0097] When the UE receives a DCI carrying a scheduling acknowledgment of a transmission on the sidelink, the UE may perform a transmission starting from the next available time resource within the configured candidate time resources. A minimum time gap constraint may be applied when the UE switches from receive mode to transmit mode, and the UE may perform a transmission starting from the next available time resource after a minimum time gap within the configured candidate time resources.

[0098] Alternatively, the UE may be configured with an offset value to indicate a time resource to be used for sidelink transmission within the configured candidate time resources. The offset value may be signaled by a DCI carrying a scheduling acknowledgment. The offset value may indicate an offset between a time resource for sidelink transmission and a time resource used to transmit the scheduling acknowledgment DCI; or the offset value may indicate an offset between a time resource for sidelink transmission after a minimum time gap within the configured candidate time resources and the next available time resource.

[0099] Alternative 2 - Candidate Time Domain Resources: The UE can be dynamically signaled by the DCI for time resources used for unicast sidelink transmission. The UE may not be configured with candidate time domain resources through RRC configuration. The DCI carrying the scheduling acknowledgment can indicate the time resources used for unicast sidelink transmission.

[0100] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat unicast sidelink transmissions. The UE can be configured with the numbers of repeats and RVs by the gNB through the RRC configuration. In one example, the UE has one repeat number (e.g., in the RRC configuration) k It can be composed of ). In another example, the UE consists of multiple iteration numbers (e.g., in the RRC configuration) k 1 , k 2 , ..., k i It can be composed of ). log2( by the scheduling DCI to indicate to the UE the number of iterations for a scheduled transmission i ) A bit repeat indicator field can be signaled.

[0101] i Assuming =4, an example of the repeat indicator field is shown in Table 3. In the example shown in Table 3, when the repeat indicator field is set to '00', this means the repeat number is k 1 Indicates that. In another example, when the repeat indicator field is set to '00', this indicates that no repetitions are performed by the UE; '01', '10', and '11' indicate that the repetition numbers are respectively k 1 , k 2 , k 3 Indicates that it is. A similar idea can be applied to group cast sidelink transmission and broadcast sidelink transmission. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. The initial transmission is slot n Assuming scheduling is performed at, in one example, the UE is in a slot n+1 , slot n+2 , ..., slot n+k at k Iterations can be transferred; in another example, the UE slot n+m , slot n+2*m , ..., slot n+k*m at k Iterations can be transmitted, and here m is the gap between the initial transmission and the first iteration.

[0102] In this example, m It consists of slot units. In another example, m It can be in mini-slot units or in symbol units. m The value of can be configured by an RRC configuration, for example, with an RRC configuration that configures the number of repeat and duplicate versions; or m The value of can be dynamically signaled by the scheduling DCI. Alternatively, the UE can use symbols or mini-slots within the same slot for iteration.

[0103] Table 3

[0104]

[0105] It is an RRC configuration for representing candidate frequency domain resources of a resource configuration, e.g., frequency domain resources of each resource pool. A UE may be configured with one or more SL-BWPs. Alternatively, a UE may be configured with one or more candidate frequency resources for unicast sidelink transmission. It is disclosed that the candidate frequency resources may be configured with the following alternatives:

[0106] Alternative 1 - Candidate Frequency Domain Resources: The UE may be configured with adjacent frequency resources as candidate frequency resources for sidelink unicast transmission. The frequency resources may be configured in RBs or subchannels, e.g., RBGs. For example, the UE may configure parameters via RRC configuration to indicate the start and length values ​​(SLV) of the RB for the candidate frequency resources. StartRB and LengthRB It can be configured as. Alternatively, the UE can use the parameters via RRC configuration to display the RBG's SLV for candidate frequency resources. StartRBG and LengthRBG It can be configured as follows. The UE may be configured with a single candidate frequency resource for both Sidelink Control Information (SCI) transmission and Sidelink Data transmission. The UE may have two candidate frequency resources for Sidelink Control Information (SCI) transmission and Sidelink Data transmission, respectively, e.g., StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can also be composed of.

[0107] Alternative 2 - Candidate Frequency Domain Resources: The UE may be composed of non-contiguous frequency resources as candidate frequency resources for sidelink unicast transmission. The frequency resources may be composed of RBs or subchannels, e.g., RBGs. Non-contiguous frequency resources may be composed of multiple SLVs. For example, StartRBG_1 and LengthRBG_1 , StartRBG_2 and LengthRBG_2 , ..., StartRBG_m and LengthRBG_m is. Alternatively, non-adjacent frequency resources can be configured by a start value and a bitmap. For example, StartRBG and {b m-1 , ..., b1, b0}. UE is StartRBG go k It is configured as set to, and bm-1 is mapped to RBG k, and b0 is RBG k+m It is assumed that it maps to.

[0108] In the case of the above alternative, the UE may provide auxiliary information, for example, in a sidelink UE information message or in a UE auxiliary information message or similar messages, to assist the NB in ​​properly configuring the UE. Such auxiliary information may include information such as UE capabilities, carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery; V2X services for which the UE is interested; and specific BWPs within the carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery. In LTE, it should be noted that while this procedure may be used to notify the E-UTRAN of the UE's power saving preferences and SPS auxiliary information, maximum PDSCH / PUSCH bandwidth configuration preferences, etc., the sidelink UE information message may be used to notify the NB that the UE is interested in receiving sidelink communications or discovery, receiving V2X sidelink communications, or requesting the allocation or deallocation of transmission resources for V2X sidelink communications, V2X sidelink discovery gaps, etc., or is no longer interested in doing so.

[0109] The previously mentioned RRC configurations are IE NR-SL Resource or NR-SL-Resource-Unicast Note that it can be configured through, or that some of the aforementioned RRC configurations can be configured by other IEs used for sidelink configuration.

[0110] Detailed design for DCI signaling: A UE can be dynamically signaled via a DCI for unicast sidelink transmission as a scheduling acknowledgment. For example, a new DCI format, e.g., DCI format 3, may be used to schedule PSCCH or PSSCH for unicast sidelink transmission. It is disclosed that, for scheduling resources for unicast sidelink transmission, the scheduling DCI may carry, in particular, the following information: 1) BWP indicator field; 2) resource indicator field; 3) sidelink type indicator field; 4) carrier type indicator field; 5) transmit / receive indicator field; 6) sidelink UE ID field; 7) paired UE ID field; 8) time domain resource allocation field; 9) retransmission field; 10) HARQ field; 11) CSI acquisition and reporting field; 12) frequency domain resource allocation field; or 13) slot format indicator (SFI) field.

[0111] BWP Indicator Field: A UE may be configured with multiple BWPs via RRC configuration. The scheduling DCI may indicate the BWP to be used for unicast sidelink transmission. Alternatively, the scheduling DCI may indicate that the UE needs 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 with or that the UE needs to switch to. Assuming the UE is configured with four BWPs, a 2-bit BWP Indicator Field may be used, such as '00' indicating the first configured BWP and '01' indicating the second configured BWP. Some fields may be dedicated from a bitmap and may be used to indicate the initial BWP and the default BWP. For example, '00' may indicate the initial BWP (used, e.g., for discovery and synchronization). Alternatively, '00' may indicate the default BWP. In another alternative, '00' can display the initial BWP, while '01' can display the default BWP.

[0112] Resource indicator field: A UE may be composed of multiple resource configurations via RRC, for example, multiple resource pools. A scheduling DCI may indicate an index of the configurations of resources to be used for unicast sidelink transmission. Assuming that a UE is composed of eight resource configurations, for example, configurations 0 through 7, a 3-bit resource indicator field may be used, having '000' indicating configuration 0, '001' indicating configuration 1, etc.

[0113] Sidelink type indicator field: The scheduling DCI can indicate the type of sidelink transmission. For example, a 2-bit sidelink type indicator field may be used, having '00' indicating that the DCI is scheduling a unicast sidelink transmission, '01' indicating that the DCI is scheduling a unicast sidelink transmission, '10' indicating that the DCI is scheduling a unicast sidelink transmission, etc.

[0114] Carrier Type Indicator Field: The UE can be dynamically indicated by a carrier type with 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 permission carrier between Uu and the sidelink; if the Carrier Type Indicator Field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0115] Transmit / Receive Indicator Field: In unicast sidelink communication, both the transmitter UE (202) and the receiver UE (203) may receive a scheduling DCI. The transmit / receive indicator field may be signaled by the scheduling DCI to indicate whether the DCI is scheduling a transmit or a receive. For example, a 1-bit field having '0' indicating a receive and '1' indicating a transmit may be used.

[0116] Sidelink UE ID field: For unicast sidelink communication, the UE requires a sidelink UE ID, for example, SL-U-RNTI It can be dynamically signaled as. For the transmitter UE (202), the UE is as the source ID SL-U-RNTI It can be used. For the receiver UE (203), the UE SL-U-RNTI It can be used as the destination ID. The scheduling DCI is the UE ID, for example, SL-U-RNTIcan be explicitly indicated. Or, the UE is 2 by RRC n It can be composed of UE IDs, where each UE ID is associated with an index. The scheduling DCI may use an n-bit field to indicate the index for the UE to determine the UE ID.

[0117] Paired UE ID field: The UE can be dynamically signaled with the ID of the paired UE. When the UE receives a scheduling DCI with a transmit / receive indicator field set to '0', the paired UE ID field indicates the ID of the transmitter UE (202). When the UE receives a scheduling DCI with a transmit / receive indicator field set to '1', the paired UE ID field indicates the ID of the receiver UE (203). The scheduling DCI is the paired UE ID, for example, SL-UP-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can be composed of paired UE IDs, where each paired UE ID is associated with an index. The scheduling DCI indicates the index for determining the UE ID to which the UE is paired. n Bit fields can be used.

[0118] Time Domain Resource Allocation Field: A UE can be signaled to a time domain resource scheduled via DCI through the following alternatives:

[0119] Alternative 1 - Time Domain Resource Allocation: A UE can be configured with one or more candidate resources through RRC configuration. The scheduling DCI can designate a time domain resource among the candidate resources to be used for unicast sidelink transmission.

[0120] To determine the start of a time domain resource, the UE may be signaled by 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 for unicast sidelink transmission and the scheduled time domain resource. The time units may be in subframes, slots, mini-slots, or symbols. Alternatively, the UE may be indicated by a two-level time offset to determine the start point of the time domain resource. For example, the UE may be indicated by a slot / subframe offset to determine which slot / subframe the time domain resource starts from. Subsequently, the UE may be indicated by the index of a start symbol / mini-slot to determine the start point within the slot / subframe. To determine the duration of the time domain resources, the scheduling DCI may indicate a bitmap or the length of the duration. In the example, the UE may be signaled by 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 is the length of a time domain resource, for example, l It can be signaled. Subsequently, the UE within the RRC-configured candidate resources for unicast sidelink transmission l Adjacent resource units may be available. Resource units may be in subframes, slots, mini-slots, or symbols.

[0121] Fields for indicating the start and duration of a time domain resource can also be signaled through a single DCI field. For example, a predefined or pre-configured table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. A UE can be signaled by a scheduling DCI having a single index through a single DCI field. The UE determines the time domain resource by finding the corresponding start and duration values ​​from the table.

[0122] Alternative 2 - Time Domain Resource Allocation: A UE may not be configured with candidate resources via RRC configuration. A UE may be dynamically indicated as a time domain resource for unicast sidelink transmission by a scheduling DCI. The DCI may carry information such as slot / subframe offset, start point, and duration of the time domain resource. The aforementioned parameters may be indicated by different DCI fields or jointly by DCI fields. For example, a time domain resource may be dynamically signaled by the slot / subframe offset value and SLV through the scheduling DCI alone.

[0123] For unicast sidelink transmission, the scheduling DCI may designate time domain resources for both PSCCH and PSSCH. Time domain resources for PSCCH and PSSCH may be allocated jointly by the scheduling DCI, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH or PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time domain resources for PSCCH or PSSCH, respectively.

[0124] Retransmission field: HARQ feedback may be introduced for the unicast sidelink. When the transmission is NACKed at the receiver UE (203), the transmitter UE (202) may perform a retransmission.

[0125] Retransmission at the transmitter UE (202) can be triggered by the receiver UE (203) or by the gNB. Alternatively, the receiver UE (203) can feed back a NACK to the gNB. The gNB can trigger the transmitter UE (202) to perform retransmission by transmitting a different scheduling DCI for retransmission. For retransmission, the gNB can indicate to the transmitter UE (202) to use the same MCS; or the gNB can indicate to the transmitter UE (202) to use a different MCS. When a repetition is performed, the UE can also be signaled with a different RV for the repetition of the retransmission. 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 in a predefined modulation coding scheme (MCS) table, or to indicate the row index of the corresponding MCS level to be used for sidelink transmission in an MCS table configured by the RRC configuration.

[0126] The RRC-configured MCS table may be a subset of a predefined MCS table, for example, RRC configuration NR-SL-MCS It may include a predefined start index and end index of an MCS table to construct a subset of the MCS table; or an RRC configuration NR-SL-MCS It may include a predefined start index of the MCS table or the size of a subset to form a subset of the MCS table. The start index or end index may be composed of bit strings of 5 bits in length in the RRC configuration. The size of the subset may be composed of integers in the RRC configuration, e.g., 1, 2, 4, 8, etc.

[0127] Assuming that rows 10 through 17 of a predefined MCS table are configured as a subset of the MCS table by RRC configuration, the MCS index field will be 3 bits, and an example is shown in Table 4. When a UE is represented by an MCS index field set to '001', the UE can utilize the second row of the configured MCS table subset, which is row 11 of the predefined MCS table in this example. The examples shown herein 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 an initial transmission or a 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.

[0128] Table 4

[0129]

[0130] FIG. 3 illustrates an exemplary call flow of a gNB-triggered retransmission over a unicast sidelink. In step 211a, the Tx UE (202) obtains (e.g., receives) a scheduling DCI for an initial transmission over the Uu interface. In step 211b, the Rx UE (203) obtains a scheduling DCI for an initial transmission over the Uu interface. In step 212, the Rx UE (203) obtains a unicast transmission over the sidelink. In step 213, based on step 212 or step 211b, the Rx UE (203) transmits HARQ feedback to the gNB (201) over the Uu interface. Steps 213 through 216 may be executed when a NACK is received. In step 214, a scheduling DCI for a retransmission over the Uu interface may be obtained by the Tx UE (202). Based on step 214, at step 215, a unicast retransmission over the sidelink may be transmitted by the Tx UE (202). At step 216, based on step 215, the RX UE (203) transmits HARQ feedback to the gNB via the Uu interface. Steps 217 through 219 may be executed when an ACK is received. At step 217, a scheduling DCI for a new transmission via the Uu interface may be obtained by the Tx UE (202). Based on step 217, at step 218, a unicast transmission over the sidelink may be transmitted by the Tx UE (202). At step 219, based on step 218, the RX UE (203) transmits HARQ feedback to the gNB via the Uu interface.

[0131] As another alternative, the receiver UE (203) can feed back the NACK to the transmitter UE (202). Upon receiving the NACK from the receiver UE (203), the transmitter UE (202) can perform a retransmission. For the retransmission, the transmitter UE (202) may choose to use the same MCS as used for the initial transmission; or the transmitter UE (202) may autonomously select a different MCS to use. For example, the transmitter UE (202) may autonomously select an MCS from a predefined MCS table. As another example, the transmitter UE (202) may autonomously select an MCS from a subset of a predefined MCS table, where the subset is an RRC configuration NR-SL-MCS It can be configured by RRC through. The configuration details disclosed above may also be applied here. The examples illustrated in this specification may also be applied to dynamic resource allocation for group cast sidelink transmission or broadcast sidelink transmission.

[0132] Resources for retransmission may be reserved in advance by a retransmission field within a scheduling DCI that carries an acknowledgment for an initial transmission. The retransmission field may indicate time or frequency resources allocated for retransmission, e.g., a symbol index, a mini-slot index, an RB index, etc. Alternatively, the retransmission field may indicate a time or frequency offset between the retransmission and the initial transmission, e.g., a symbol offset, a mini-slot offset, an RB offset, etc.

[0133] When the transmitter UE (202) receives a NACK from the receiver UE (203), the transmitter UE (202) may use a resource reserved in advance for retransmission. When the transmitter UE (202) receives an ACK from the receiver UE (203), the transmitter UE (202) may skip the resource reserved in advance for retransmission. An exemplary call flow is illustrated in FIG. 4.

[0134] FIG. 4 illustrates an exemplary call flow of a retransmission triggered by an Rx UE (203) over a unicast sidelink. In step 221a, the Tx UE (202) obtains (e.g., receives) a scheduling DCI for an initial transmission over the Uu interface. In step 221b, the Rx UE (203) obtains a scheduling DCI for an initial transmission and a retransmission over the Uu interface. In step 222, the Rx UE (203) obtains a unicast transmission over the sidelink from the Tx UE (202). In step 223, based on step 222, the Rx UE (203) transmits HARQ feedback to the Tx UE (202) over the sidelink. Steps 224 through 225 may be executed when a NACK is received. In step 224, a unicast retransmission over the sidelink may be obtained by the Rx UE (203). Based on step 224, in step 225, the RX UE (203) transmits HARQ feedback to the Tx UE (202) via the sidelink. If an ACK is received in step 223, for example, the Tx UE (202) may skip the retransmission.

[0135] This is a HARQ field. The scheduling DCI may display a HARQ ID or HARQ process number to the transmitter UE (202) and the receiver UE (203). The scheduling DCI may also display resource allocations for HARQ feedback. The scheduling DCI may display time or frequency resources for HARQ feedback, such as a symbol index, mini-slot index, RB index, etc. Or the scheduling DCI may display a time or frequency offset between HARQ feedback and the initial transmission, such as a symbol offset, mini-slot offset, RB offset, etc. When retransmission is triggered by the receiver UE (203), the receiver UE (203) may transmit HARQ feedback to the transmitter UE (202) using the allocated HARQ feedback resources. When retransmission is triggered by the gNB (201), the receiver UE (203) may transmit HARQ feedback to the gNB (201) using the allocated HARQ feedback resources.

[0136] This is a Channel State Information (CSI) acquisition and reporting field. The gNB (201) can schedule CSI acquisition and reporting over the sidelink. The scheduling DCI can indicate the CSI-RS configuration and resources used to report to the transmitter UE (202) and the receiver UE (203). The scheduling DCI can indicate time or frequency resources for CSI feedback, such as symbol index, mini-slot index, RB index, etc. Multiple CSI-RS configurations can be configured by the RRC, and the scheduling DCI can signal an index indicating the CSI-RS configuration used.

[0137] This is a frequency domain resource allocation field. To determine frequency domain resources for unicast sidelink transmission / reception, the UE may be indicated by information on the lowest RB, RBG, or subchannel to be used. The UE may be signaled by an index of the lowest RB or RBG. Alternatively, the UE may be signaled by an offset between the lowest RB, RBG, or subchannel of the frequency domain resource allocation and the lowest RB, RBG, or subchannel of the RRC-configured candidate frequency domain resources. The offset may be on the RBs or RBGs.

[0138] To determine the range of frequency domain resources, a bitmap or width of the frequency domain resources may be indicated by the scheduling DCI. In one example, the UE may be signaled as a bitmap. The bitmap indicates which frequency resources within the RRC-configured candidate frequency resources are used for unicast sidelink transmission. As another example, the UE indicates the width of the frequency domain resources, e.g., w It can be signaled as. Next, for unicast sidelink transmission, the UE w Adjacent RB, RBG, or subchannels can be used.

[0139] For unicast sidelink transmission, the scheduling DCI may designate frequency domain resources for both PSCCH and PSSCH. Frequency domain resources for PSCCH and PSSCH may be jointly allocated by the scheduling DCI, for example, a single frequency domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH or PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for PSCCH or PSSCH, respectively.

[0140] This is the slot format indicator field. For a UE configured as a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured as a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0141] If there is a conflict between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI can overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transports for them. For example, slots m internal symbol k Assume that is configured as a candidate time resource in the RRC configuration. Slot m internal symbol k If it is labeled as 'D' in SFI, the UE slot m internal symbol k It may not be treated as a candidate time resource. When the UE determines a time resource for unicast sidelink transmission, the UE slot m internal symbol k ...can be skipped. If a candidate time resource is in a mini-slot and there is a conflict for some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform a sidelink transmission for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform a sidelink transmission for the non-conflicting symbol(s) within the mini-slot.

[0142] The symbols used for sidelink communication may be further subdivided into symbols used for sidelink transmission and symbols used for sidelink reception. As disclosed, labels 'ST' and 'SR' may be introduced for the slot format as illustrated in FIG. 5. FIG. 5 illustrates an example of a slot format for a unicast sidelink. For a transmitter UE (202), the UE may use symbols labeled by SFI as 'ST' for sidelink transmission and symbols labeled by SFI as 'SR' for receiving feedback, e.g., HARQ feedback. For a receiver UE (203), the UE may use symbols labeled by SFI as 'ST' for receiving sidelink transmission and symbols labeled by SFI as 'SR' for transmitting feedback, e.g., HARQ feedback. A similar idea may be applied to a groupcast sidelink. Symbols labeled 'X' can be used as gaps to switch the transmit and receive modes for the UE.

[0143] ෸룹캐스트 사이드링크 전송

[0144] Group Cast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node can dynamically allocate resources used by a UE for group cast sidelink transmission. In the case of a transmitter UE (202), the UE can be allocated resources for group cast sidelink transmission through RRC configuration and DCI signaling. In the case of a receiver UE (203), the UE can be allocated resources for reception through RRC configuration and DCI signaling. When the gNB (201) schedules transmission over the sidelink, both the transmitter UE (202) and the receiver UE (203) can receive a scheduling acknowledgment. By receiving the scheduling acknowledgment, the transmitter can determine the resources and beams used for transmission. By receiving the scheduling acknowledgment, the receiver UE (203) can determine the resources and beams used for reception. The detailed resource allocation method is as follows.

[0145] Detailed Design for RRC Configuration: For Group Cast Sidelink Transmission, IE NR-SL Resource or NR-SL-Resource-Groupcast It can carry configuration information for both sidelink control and sidelink data transmission. The UE can do this via broadcasted signals, e.g., OSI; or via common or dedicated RRC configurations on the Uu interface. NR-SL Resource or NR-SL-Resource-Groupcast It can be composed of. IE NR-SL Resource or NR-SL-Resource-Groupcast It can specifically carry the following RRC configurations: 1) type of sidelink transmission; 2) type of carrier; 3) numerology of the resource; 4) group cast transmission UE; 5) mask used to scramble the scheduling DCI; 6) index of the candidate resource; 7) candidate time domain resources of the resource configuration; 8) number of repeat and duplicate versions; 9) candidate frequency domain resources of the resource configuration; or 10) beam sweeping information.

[0146] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types NR-SL Resource When used, Thanksgiving , ෸룹캐스트 , or 유니캐스트 Possible RRC configuration NR-SL-CommunicationType am.

[0147] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL Carrier type If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL Carrier type If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0148] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0149] This is an RRC configuration for indicating the UE ID for group cast transmission over the sidelink. For group cast sidelink transmission, the UE uses the UE ID, for example, the sidelink group cast RNTI ( SL-G-RNTI It can be composed of ). If the UE needs to group cast on the sidelink, the UE as a source ID within the formed group SL-G-RNTI You can use .

[0150] To perform groupcast sidelink communication, the UE may need to be identified by a group ID. The UE is the group ID, for example, the sidelink groupcast destination RNTI ( SL-GD-RNTI It can be configured as ). The UE can use the configured group ID as the destination group ID. The group ID can also be dynamically signaled by the scheduling DCI.

[0151] The scrambling sequence for the SCI can be jointly initialized by the destination group ID and the source ID. Alternatively, the scrambling sequence for the SCI can be initialized by either the destination group ID or the source ID, and the other is 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.

[0152] This is an RRC configuration to indicate the mask used to scramble the scheduling DCI. For example, the UE is SLGroupcast-RNTI or SL-RNTI It can be composed of. gNB(201) is composed SLGroupcast-RNTI or SL-RNTI It can generate and transmit a scheduling DCI for a UE with a scrambled CRC. This is configured SLGroupcast-RNTI or SL-RNTI DCI can be decoded using .

[0153] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat groupcast sidelink transmissions. The UE can be configured with the numbers of repeats and RVs by the gNB (201) via the RRC configuration. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. Alternatively, the UE may use symbols or mini-slots within the same slot for repetition. If beam sweeping is applied in the groupcast, the transmitter UE (202) performs full beam sweeping, e.g., beam 1, beam 2, ..., beam k , beam 1, beam 2, ..., beam k , ..., Beam 1, Beam 2, ..., Beam k...can be repeated. Or, the UE repeats for each beam and then beam sweeping, e.g., Beam 1, Beam 1, ..., Beam 1, Beam 2, Beam 2, ..., Beam 2, ..., Beam k , beam k , ..., beam k It can perform.

[0154] This is an RRC configuration for displaying an index of candidate resources. A UE may be composed of multiple configurations of resources for sidelink transport, for example, multiple resource pools. Each resource configuration may be associated with a single dedicated resource index. For example, RRC configuration NR-SL Resource Index The UE can determine the configuration of resources to be used for sidelink transmission through the DCI that schedules sidelink transmission.

[0155] It is an RRC configuration for representing candidate time domain resources of a resource configuration, e.g., time domain resources of each resource pool. It discloses that candidate time domain resources for groupcast sidelink transmission for each candidate resource may be configured with the following alternatives:

[0156] Alternative 1 - Candidate Time Domain Resources: The UE may be configured with one or more bitmaps by RRC configuration to represent candidate time domain resources for sidelink transmission. The bitmap may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {bm , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0157] When the UE receives a DCI carrying a scheduling acknowledgment of a transmission on the sidelink, the UE may perform a transmission starting from the next available time resource within the configured candidate time resources. A minimum time gap constraint may be applied when the UE switches from receive mode to transmit mode, and the UE may perform a transmission starting from the next available time resource after a minimum time gap within the configured candidate time resources.

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

[0159] Alternative 2 - Candidate Time Domain Resources: The UE can be dynamically signaled by the DCI for time resources used for groupcast sidelink transmission. The UE may not be configured with candidate time domain resources through RRC configuration. The DCI carrying the scheduling acknowledgment can indicate the time resources used for groupcast sidelink transmission.

[0160] This is an RRC configuration for displaying beam sweeping information. For group cast sidelink transmission, the transmitter UE (202) can transmit information in multiple directions through multiple beams. The UE needs to recognize the number of beam sweeping operations the UE needs to perform and the corresponding resources.

[0161] Alternative 1 - Beam Sweeping Information: The gNB (201) can determine the number of beam sweeps that the UE needs to perform. For example, the UE may be configured with a number of beam sweeps or a maximum number through RRC configuration. Alternatively, the number of beam sweeps may be signaled by the DCI. The UE may provide auxiliary information to the NB to help the NB determine the beam sweeping configuration. This auxiliary information may include one or more of the following: V2X services of interest, e.g., UE capabilities regarding the number of concurrent beam sweeping directions the UE can cover, UE scheduling preferences including sleep mode preferences, etc.

[0162] UE k Assuming it is configured to transmit information through several directions / beams, the UE k configuration of time and frequency resources, for example, k Time and frequency resources for each direction / beam can be allocated through RRC configuration for beam sweeping of each of the directions and DCI signaling.

[0163] Alternatively, the UE may be assigned a single configuration of time and frequency resources. In one possibility, the assigned time and frequency resources may be used for all beams. The UE may use the assigned time resources kIt can be uniformly divided into parts, and each part can be utilized for a single beam. In another possibility, allocated time and frequency resources can be utilized for a single beam. For example, the UE can utilize time resources across beam sweeping directions as follows. In Option 1 of this alternative beam sweeping information, the UE utilizes the time and frequency resources allocated for the first beam sweeping, and can utilize the next available time resources from a configured resource pool where the same time duration and the same frequency resources used for the first beam sweeping are utilized for the remainder of the beam sweeping. For example, the UE is configured with time resources in mini-slots, and the UE for the first beam sweeping mini-slot n Assume that it is configured to use. The UE uses mini-slots from the resource pool configured for the rest of the beam sweeping n+1 inside n+k-1 The beams used for beam sweeping may be indicated by the gNB (201). Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery. In Option 2 of this alternative, the UE slices the time resources equally on a round-robin basis across the beam sweeping directions and uses the same frequency resources in each direction. In Option 3 of this alternative, the UE autonomously determines how to slice the time-frequency resources in both the time domain and the frequency domain across the beam sweeping directions.

[0164] Alternative 2 - Beam Sweeping Information: The UE can determine the number of beam sweeps the UE needs to perform for group cast sidelink transmission. The UE can report the value of k beam sweeps to the gNB (201). The gNB (201) schedules time resources for the UE for group cast sidelink transmission.

[0165] UE is, each,k Time and frequency resources through RRC configuration and DCI signaling for beam sweeping in several directions k A number of configurations may be assigned. Alternatively, the UE may be assigned a single configuration of time and frequency resources. In one possibility, the assigned time and frequency resources may be used for all beams. The UE may divide the assigned time resources evenly into k parts and use each part for one beam. In another possibility, the assigned time and frequency resources may be used for one beam. The UE may use the assigned time and frequency resources for the first beam sweeping and may use the next available time resources from the resource pool configured for the remainder of the beam sweeping, having the same time duration and frequency resources as those used for the first beam sweeping. The beams used for beam sweeping may be indicated by the gNB (201). Alternatively, the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0166] It is an RRC configuration for representing candidate frequency domain resources of a resource configuration, e.g., frequency domain resources of each resource pool. A UE may be configured with one or more SL-BWPs. Alternatively, a UE may be configured with one or more candidate frequency resources for groupcast sidelink transmission. It is disclosed that the candidate frequency resources may be configured with the following alternatives:

[0167] Alternative 1 - Candidate Frequency Domain Resources: The UE may be configured with adjacent frequency resources as candidate frequency resources for sidelink groupcast transmission. The frequency resources may be configured in RBs or subchannels, e.g., RBGs. For example, the UE may configure parameters via RRC configuration to indicate the start and length values ​​(SLV) of the RB for the candidate frequency resources. StartRB and LengthRB It can be configured as. Alternatively, the UE can use the parameters via RRC configuration to display the RBG's SLV for candidate frequency resources. StartRBG and LengthRBG It can be configured as follows. The UE may be configured with a single candidate frequency resource for both Sidelink Control Information (SCI) transmission and Sidelink Data transmission. The UE may have two candidate frequency resources for Sidelink Control Information (SCI) transmission and Sidelink Data transmission, respectively, e.g., StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can also be composed of.

[0168] Alternative 2 - Candidate Frequency Domain Resources: The UE may be composed of non-contiguous frequency resources as candidate frequency resources for sidelink groupcast transmission. The frequency resources may be composed of RBs or subchannels, e.g., RBGs. Non-contiguous frequency resources may be composed of multiple SLVs. For example, StartRBG_1 and LengthRBG_1 , StartRBG_2 and LengthRBG_2 , ..., StartRBG_m and LengthRBG_m is. Alternatively, non-adjacent frequency resources can be configured by a start value and a bitmap. For example, StartRBG and {b m-1 , ..., b1, b0}. UE is StartRBG go k It is configured as set to, and bm-1 Assume that is mapped to RBG k and b0 is mapped to RBG k+m.

[0169] In the case of the above alternatives, the UE may provide auxiliary information, for example, in a sidelink UE information message or in a UE auxiliary information message or similar messages, to assist the NB in ​​properly configuring the UE. Such auxiliary information may include information such as UE capabilities, carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery; V2X services for which the UE is interested; and specific BWPs within the carrier frequencies for which the UE is interested in transmitting or receiving V2X communications or performing V2X discovery. In LTE, it should be noted that while this procedure may be used to notify the E-UTRAN of the UE's power saving preferences and SPS auxiliary information, maximum PDSCH / PUSCH bandwidth configuration preferences, etc., the sidelink UE information message may be used to notify the NB that the UE is interested in receiving sidelink communications or discovery, receiving V2X sidelink communications, or requesting the allocation or deallocation of transmission resources for V2X sidelink communications, V2X sidelink discovery gaps, etc., or is no longer interested in doing so.

[0170] The previously mentioned RRC configurations are IE NR-SL Resource or NR-SL-Resource-Groupcast Note that it can be configured through, or that some of the aforementioned RRC configurations can be configured by other IEs used for sidelink configuration.

[0171] Detailed design for DCI signaling: A UE can be dynamically signaled via a DCI for group cast sidelink transmission as a scheduling acknowledgment. For example, a new DCI format, e.g., DCI format 3, may be used to schedule PSCCH or PSSCH for group cast sidelink transmission. To schedule resources for group cast sidelink transmission, the scheduling DCI may specifically carry the following information: 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) transmit / receive indicator field; 7) sidelink UE ID field; 8) group ID field; 9) retransmission field; 10) HARQ field; 11) beam sweeping information field; 12) frequency domain resource allocation field; or 13) slot format indicator (SFI) field.

[0172] This is the BWP indicator field. A UE can be configured with multiple BWPs via RRC configuration. The scheduling DCI can indicate the BWP to be used for groupcast sidelink transmission. Alternatively, the scheduling DCI can indicate that the UE needs to switch from the current BWP to a new BWP. The BWP indicator field can indicate the index of the BWP that the UE needs to perform groupcast sidelink transmission with or that the UE needs to switch to. Assuming the UE is configured with four BWPs, a 2-bit BWP indicator field may be used, such as '00' indicating the first configured BWP and '01' indicating the second configured BWP. Some fields may be dedicated from the bitmap and may be used to indicate the initial BWP and the default BWP. For example, '00' may indicate the initial BWP (used, e.g., for discovery and synchronization). Alternatively, '00' may indicate the default BWP. In another alternative, '00' can display the initial BWP, while '01' can display the default BWP.

[0173] This is a resource indicator field. A UE may be composed of multiple resource configurations via RRC, for example, multiple resource pools. The scheduling DCI may indicate an index of the configuration of resources to be used for group cast sidelink transmission. Assuming that the UE is composed of eight resource configurations, for example, configurations 0 through 7, a 3-bit resource indicator field may be used, having '000' indicating configuration 0, '001' indicating configuration 1, etc.

[0174] This is a sidelink type indicator field. A scheduling DCI can indicate the type of sidelink transmission. For example, a 2-bit sidelink type indicator field may be used, having '00' indicating that the DCI is scheduling a groupcast sidelink transmission, '01' indicating that the DCI is scheduling a groupcast sidelink transmission, '10' indicating that the DCI is scheduling a unicast sidelink transmission, etc.

[0175] This is the Carrier Type Indicator field. The UE can be dynamically indicated by a carrier type with 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 permission carrier between the UE and the sidelink; if the Carrier Type Indicator field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0176] This is a transmit / receive indicator field. In unicast sidelink communication, both the transmitter UE (202) and the receiver UE (203) may receive a scheduling DCI. The transmit / receive indicator field may be signaled by the scheduling DCI to indicate whether the DCI is scheduling a transmit or a receive. For example, a 1-bit field having '0' to indicate a receive and '1' to indicate a transmit may be used.

[0177] This is the sidelink UE ID field. The UE can be dynamically signaled by the UE ID in the sidelink group to indicate the source ID. The scheduling DCI is the UE ID, e.g., SL-G-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can consist of candidate IDs, where each candidate ID is associated with an index. The scheduling DCI indicates the index for the UE to determine the source ID.n Bit fields can be used.

[0178] This is the Group ID field. The UE can be dynamically signaled with the Group ID to indicate the destination group ID. The scheduling DCI is the Group ID, e.g., SL-GD-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can consist of candidate IDs, where each candidate ID is associated with an index. The scheduling DCI indicates the index for the UE to determine the group ID. n Bit fields can be used.

[0179] This is the time domain resource allocation field. The UE can be signaled to a time domain resource scheduled via DCI through the following alternatives:

[0180] Alternative 1 - Time Domain Resource Allocation: A UE can be configured with one or more candidate resources through RRC configuration. The scheduling DCI can indicate the time domain resource among the candidate resources to be used for group casting sidelink transports.

[0181] To determine the start of a time domain resource, the UE may be signaled by 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 for groupcast sidelink transmission and the scheduled time domain resource. The time units may be in subframes, slots, mini-slots, or symbols. Alternatively, the UE may be signaled by a two-level time offset to determine the start point of the time domain resource. For example, the UE may be signaled by a slot / subframe offset to determine from which slot / subframe the time domain resource starts. Subsequently, the UE may be signaled by the index of a start symbol / mini-slot to determine the start point within the slot / subframe.

[0182] To determine the duration of time domain resources, the length of the duration or a bitmap may be indicated by the scheduling DCI. In an example, the UE may be signaled by 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 indicates the length of the time domain resource, e.g., l It can be signaled. Subsequently, the UE within the RRC-configured candidate resources for groupcast sidelink transmission l Adjacent resource units may be available. Resource units may be in subframes, slots, mini-slots, or symbols.

[0183] Fields for indicating the start and duration of a time domain resource can also be signaled through a single DCI field. For example, a predefined or pre-configured table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. A UE can be signaled by a scheduling DCI having a single index through a single DCI field. The UE determines the time domain resource by finding the corresponding start and duration values ​​from the table.

[0184] Alternative 2 - Time Domain Resource Allocation: A UE may not be configured with candidate resources via RRC configuration. A UE may be dynamically indicated as a time domain resource for group cast sidelink transmission by a scheduling DCI. The DCI may carry information such as slot / subframe offset, start point, and duration of the time domain resource. The aforementioned parameters may be indicated by different DCI fields or jointly by DCI fields. For example, a time domain resource may be dynamically signaled by the slot / subframe offset value and SLV through the scheduling DCI alone.

[0185] For groupcast sidelink transmission, the UE, for example, k Through beams, the same information can be transmitted in multiple directions. A UE can be represented as a single time-domain resource, and time-domain resources for all beams can be determined by some predefined rules. For example, a UE is a mini-slot n It can be represented as, and the UE has a mini-slot for the first beam n Using and from the candidate time resources configured for the remaining beams, the following k-1 Several mini-slots may be available. Alternatively, the UE can be represented as a time-domain resource for each beam. For example, the UE is a time-domain resource of k It can be represented by start and duration values. Alternatively, the UE can be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0186] For groupcast sidelink transmission, the scheduling DCI may designate time domain resources for both PSCCH and PSSCH. Time domain resources for PSCCH and PSSCH may be jointly allocated by the scheduling DCI, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH or PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two time domain resources for PSCCH or PSSCH, respectively.

[0187] This is a retransmission field. HARQ feedback may be introduced for the groupcast sidelink. The transmitter UE (202) may groupcast a message to multiple receiver UEs through multiple beams, wherein each beam may cover one or more UEs. Retransmission may be triggered per beam. For a beam, retransmission may be triggered when any UE under that beam is NACKed, or when all UEs under that beam are NACKed.

[0188] Retransmission in the transmitter UE (202) can be triggered by the receiver UE (203) or by the gNB (201). Alternatively, the receiver UEs can feed back a NACK to the gNB (201). The gNB (201) can trigger the transmitter UE (202) to perform retransmission by transmitting a different scheduling DCI for retransmission. For retransmission, the gNB (201) can indicate to the transmitter UE (202) to use the same MCS; or the gNB (201) can indicate to the transmitter UE (202) to use a different MCS. When a repetition is performed, the UE can also be signaled with a different RV for the repetition of the retransmission. In this case, the retransmission field may be a 1 bit to indicate whether the scheduling is for the initial transmission or the retransmission. For example, '0' indicates that the transmission is an initial transmission, and '1' indicates that the transmission is a retransmission. A bitmap can be signaled in the scheduling DCI to indicate which beams need to be retransmitted, for example, {b k-1 , ..., b1, b0} is b k-1 This is mapped to the first beam, and b0 is mapped to the k-th beam. An exemplary arc flow is shown in FIG. 6.

[0189] FIG. 6 illustrates an exemplary call flow of a gNB (201)-triggered retransmission for a group cast sidelink. In step 241a, the Tx UE (202) obtains (e.g., receives) a scheduling DCI for an initial transmission over the Uu interface. In step 241b, the Rx UEs (203) obtain a scheduling DCI for an initial transmission over the Uu interface. In step 242a, the Rx UEs (203) obtain a group cast transmission on Beam 1 of the sidelink. In step 242b, the Rx UEs (203) obtain a group cast transmission on Beam 2 of the sidelink. In step 242c, the Rx UEs (203) [obtain] the beam of the sidelinkk Acquire the group cast transmission of the above. Based on steps 242a through 242c, steps 243a through 243c may be executed. In step 243a, the Rx UEs (203) transmit HARQ feedback from UE 1 ... UE i1 on Beam 1 to the gNB (201) via the Uu interface. In step 243b, the Rx UEs (203) transmit HARQ feedback from UE i1+1 ... UE i2 on Beam 2 to the gNB (201) via the Uu interface. In step 243c, the Rx UEs (203) transmit HARQ feedback from UE i on Beam k via the Uu interface. k-1 +1 ... UE i k HARQ feedback from is transmitted to the gNB (201). Steps 244a through 246b may be executed, for example, when a NACK is received for Beam 1 and Beam 4. In step 244a, a scheduling DCI for retransmission on Beam 1 and Beam 4 via the Uu interface may be transmitted to the Tx UE (202). In step 244b, a scheduling DCI for retransmission on Beam 1 and Beam 4 via the Uu interface may be transmitted to the Rx UEs (203). In step 245a, a group cast retransmission on Beam 1 of the sidelink is obtained. In step 245b, the Rx UE (203) obtains a group cast retransmission on Beam 4 of the sidelink. Based on steps 245a through 245b, steps 246a through 246c may be executed. In step 246a, the Rx UEs (203) transmit HARQ feedback from UE 1 ... UE i1 on Beam 1 to the gNB (201) via the Uu interface. In step 246b, the Rx UEs (203) transmit HARQ feedback from UE i3+1 ... UE i4 on Beam 4 to the gNB (201) via the Uu interface.

[0190] As another alternative, receiver UEs can feed back the NACK to the transmitter UE (202). For each beam, the transmitter UE (202) can decide whether to perform retransmission based on the feedback. For retransmission, the transmitter UE (202) can choose to use the same MCS used for the initial transmission; or the transmitter UE (202) can autonomously choose a different MCS to use.

[0191] Resources for retransmission can be reserved in advance by the retransmission field within the scheduling DCI that carries an acknowledgment for the initial transmission. k Assuming that beams are used for group cast transmission, similar to resource allocation for initial transmission, the retransmission field is for retransmission k Can indicate several time or frequency resources, or the retransmission field can indicate one time or frequency resource, and the transmitter UE (202) determines the resources for the remaining beams by some predefined rules, for example, from the candidate time resources the following k-1 Units of time resources are used. The allocation of retransmissions may be indicated by time resources, e.g., symbol index, mini-slot index, RB index, etc. Alternatively, the allocation of retransmissions may be indicated by a time or frequency offset between the retransmission and the initial transmission, e.g., symbol offset, mini-slot offset, RB offset, etc. When a retransmission is triggered on any beam, the transmitter UE (202) may use a corresponding pre-reserved resource for the retransmission on that beam. An exemplary call flow is illustrated in FIG. 7.

[0192] FIG. 7 illustrates an exemplary call flow of a triggered retransmission by an Rx UE (203) for a group cast sidelink. In step 231a, the Tx UE (202) obtains (e.g., receives) a scheduling DCI for an initial transmission and retransmission over the Uu interface. In step 231b, the Rx UEs (203) obtain a scheduling DCI for an initial transmission and retransmission over the Uu interface. In step 232a, the Rx UEs (203) obtain a group cast transmission on Beam 1 of the sidelink. In step 232b, the Rx UEs (203) obtain a group cast transmission on Beam 2 of the sidelink. In step 232c, the Rx UEs (203) [obtain] the beam of the sidelink k A group cast transmission is obtained. Based on steps 232a through 232c (which can be received from the Tx UE (202)), steps 233a through 233c are executed and can be transmitted to the Tx UE (202) (or gNB (201) in an alternative implementation). In step 233a, the Rx UEs (203) transmit HARQ feedback from UE 1 ... UE i1 on Beam 1 to the Tx UE (202) on the sidelink. Communication between the Tx UE and the Rx UE occurs on the sidelink. Communication between the vehicle UE (e.g., Tx UE or Rx UE) and the gNB occurs on the Uu interface. In step 233b, the Rx UEs (203) transmit HARQ feedback from UE i1+1 ... UE i2 on Beam 2 to the Tx UE (202) on the sidelink. In step 233c, the Rx UEs (203) are UE i on beam k k-1 +1 ... UE i kHARQ feedback is transmitted from to the Tx UE (202) on the sidelink. Steps 234a through 235b may be executed, for example, when a NACK is received for Beam 1 and Beam 3. In step 234a, the RX UEs (203) obtain a group cast retransmission on Beam 1 of the sidelink. In step 234b, the Rx UEs (203) obtain a group cast retransmission on Beam 3 of the sidelink. Based on steps 234a through 234b, steps 235a through 236b may be executed. In step 235a, the Rx UEs (203) transmit HARQ feedback from UE 1 ... UE i1 on Beam 1 to the Tx UE (202) on the sidelink. In step 235b, the Rx UEs (203) transmit HARQ feedback from UE i2+1 ... UE i3 on beam 3 to the Tx UE (202) on the sidelink.

[0193] This is a HARQ field. The scheduling DCI may display a HARQ ID or HARQ process number to the transmitter UE (202) and the receiver UE (203). The scheduling DCI may also display resource allocations for HARQ feedback. Resources used for HARQ feedback for different beams may be TDM, and resources used for HARQ feedback for different UEs on the same beam may be FDM. The scheduling DCI may display time or frequency resources for HARQ feedback, such as a symbol index, mini-slot index, RB index, etc. Or the scheduling DCI may display a time or frequency offset between HARQ feedback and the initial transmission, such as a symbol offset, mini-slot offset, RB offset, etc. When retransmission is triggered by the receiver UE (203), the receiver UE (203) may transmit HARQ feedback to the transmitter UE (202) using the allocated HARQ feedback resources. When retransmission is triggered by gNB (201), the receiver UE (203) can send HARQ feedback to gNB (201) using the allocated HARQ feedback resource.

[0194] This is a beam sweeping information field. The scheduling DCI can indicate the number of beam sweeps that the UE needs to perform. The UE can be dynamically signaled by the scheduling DCI as a value for the number of beam sweeps. Alternatively, the RRC can configure multiple potential values ​​for the number of beam sweeps, each value associated with an index. The UE can be signaled by a single index and determine the values ​​for the number of beam sweeps. The beams used for beam sweeping can be indicated by the gNB (201). Alternatively, the beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0195] This is a frequency domain resource allocation field. To determine frequency domain resources for group cast sidelink transmission, the UE may be indicated by information on the lowest RB, RBG, or subchannel to be used. The UE may be signaled by an index of the lowest RB or RBG. Alternatively, the UE may be signaled by an offset between the lowest RB, RBG, or subchannel of the frequency domain resource allocation and the lowest RB, RBG, or subchannel of the candidate frequency domain resources configured with RRC. The offset may be on the RBs or RBGs.

[0196] To determine the range of frequency domain resources, a bitmap or 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. As another example, the UE may indicate the width of the frequency domain resources, e.g., w It can be signaled as. Next, for group cast sidelink transmission, the UE w Adjacent RB, RBG, or subchannels can be used.

[0197] For groupcast sidelink transmission, a UE can transmit the same information in multiple directions. A UE can be represented by a single frequency domain resource and can utilize the same frequency domain resource for transmission in all directions. Alternatively, a UE can be signaled by different frequency domain resources for transmission in different directions.

[0198] For groupcast sidelink transmission, the scheduling DCI may designate frequency domain resources for both PSCCH and PSSCH. Frequency domain resources for PSCCH and PSSCH may be jointly allocated by the scheduling DCI, for example, a single frequency domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH or PSSCH may be allocated separately by the scheduling DCI. For example, the scheduling DCI may allocate two frequency domain resources for PSCCH or PSSCH, respectively.

[0199] This is the slot format indicator field. For a UE configured as a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured as a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0200] If there is a conflict between the RRC-configured candidate time resources and the DCI-signaled SFI, the DCI can overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transports for them. For example, slots m internal symbol k It is assumed that it is configured as a candidate time resource in the RRC configuration. Slot m internal symbol k If it is labeled as 'D' in SFI, the UE slot m internal symbol k It may not be treated as a candidate time resource. When the UE determines a time resource for groupcast sidelink transmission, the UE slot m symbol in k...can be skipped. If a candidate time resource is in a mini-slot and there is a conflict for some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform a sidelink transmission for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform a sidelink transmission for the non-conflicting symbol(s) within the mini-slot.

[0201] The symbols used for sidelink communication may be further divided into symbols used for sidelink transmission and symbols used for sidelink reception. It is disclosed that labels 'ST' and 'SR' may be introduced for the slot format. In the case of a transmitter UE (202), the UE may use symbols labeled by SFI as 'ST' for sidelink transmission and symbols labeled by SFI as 'SR' for receiving feedback, e.g., HARQ feedback. In the case of a receiver UE (203), the UE may use symbols labeled by SFI as 'ST' for receiving sidelink transmission and symbols labeled by SFI as 'SR' for transmitting feedback, e.g., HARQ feedback.

[0202] 유니캐스트 및 ط룹캐스트에 동적 리소스 할당

[0203] Dynamic Resource Allocation for Unicast and Groupcast - General Signaling Design and UE Behavior for Unicast or Groupcast Use Cases: Subjects disclosed herein regarding dynamic resource allocation (e.g., FIGS. 10 through 16 and associated descriptions) may relate to unicast or groupcast. In NR V2X mode 1, the gNB (201) may dynamically schedule unicast or groupcast transmissions over the sidelink via scheduling acknowledgment. For unicast or groupcast, the Tx UE (202) or Rx UE (203) must recognize the resources used for transmission and reception. Transmission scheduling may be indicated by scheduling DCI transmitted over the Uu interface in the following examples.

[0204] Example 1 of scheduling DCIs transmitted over the Uu interface: The gNB (201) can transmit scheduling DCIs to the Tx UE (202) or Rx UE (203). Shared resources can be used to transmit scheduling DCIs for the Tx UE (202) or Rx UE (203), for example, and may be SDM. In this case, the UE can be configured as a single CORESET to monitor scheduling DCIs for the Tx UE (202) or Rx UE (203). Alternatively, dedicated resources can be used to transmit scheduling DCIs for the Tx UE (202) and Rx UE (203), for example, TDM or FDM. In this case, the UE can be configured as a single CORESET or two different CORESETs to monitor scheduling DCIs for the Tx UE (202) or scheduling DCIs for the Rx UE (203).

[0205] Example 2 of a scheduling DCI transmitted over the Uu interface: The gNB (201) can transmit the scheduling DCI only to the Tx UE (202). By decoding the scheduling DCI, the Tx UE (202) can determine the scheduled acknowledgment for feedback from the received DCI. Subsequently, the Tx UE (202) can use the SCI to indicate the received sidelink transmission scheduling to the Rx UE (203). For example, there is resource allocation for the PSSCH for transmitting data or reference signals for measurement, and resource allocation feedback, such as HARQ feedback or CSI feedback. The Rx UE (203) may be composed of monitoring operations for monitoring the SCI. By decoding the SCI, the Rx UE (203) can determine the resources used for the PSSCH and feedback.

[0206] When gNB (201) sends scheduling DCIs to Tx UE (202) and Rx UE (203), gNB (201) can schedule sidelink communication through the following examples:

[0207] Scheduling DCIs for Both - Example 1 of Sidelink Communication Scheduling: gNB (201) can transmit scheduling DCIs to Tx UE (202) or Rx UE (203), where HARQ feedback is transmitted from Rx UE (203) to gNB (201) via the Uu interface. FIG. 10 illustrates an example of a unicast use case.

[0208] The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, such as resource allocations for SCI and PSSCH, so that both Tx UE (202) or Rx UE (203) can know the resources used to transmit or receive data on the sidelink.

[0209] The scheduling DCI can carry information about the resources used for HARQ feedback. The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time and frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, RRC. For a UE scheduled to transmit over a sidelink, the UE may ignore resource allocation for HARQ feedback. For a UE scheduled to receive over a sidelink, the UE may transmit HARQ feedback to the gNB (201) via the Uu interface using the allocated resources.

[0210] Scheduling DCIs for Both - Example 2 of Sidelink Communication Scheduling: The gNB (201) can send scheduling DCIs to both the Tx UE (202) and the Rx UE (203), where HARQ feedback is sent from the Rx UE (203) to the Tx UE (202) via the sidelink. FIG. 11 illustrates an example of a unicast use case.

[0211] The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, such as resource allocations for SCI and PSSCH, so that the Tx UE (202) or Rx UE (203) can know the resources used to transmit or receive data on the sidelink.

[0212] The scheduling DCI can carry information about the resources used for HARQ feedback. The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time and frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, the RRC. In the case of a UE scheduled to receive on a sidelink, the UE can transmit HARQ feedback to the Tx UE (202) using the allocated resources on the sidelink. In the case of a UE scheduled to transmit on a sidelink, the UE can monitor or receive HARQ feedback from the allocated resources.

[0213] Scheduling DCIs for Both - Example 3 of Sidelink Communication Scheduling: gNB (201) can transmit scheduling DCIs to both Tx UE (202) and Rx UE (203), where HARQ feedback is first transmitted from Rx UE (203) to Tx UE (202) over the sidelink, and then Tx UE (202) can feed back the received information to gNB (201) through the Uu interface. FIG. 12 illustrates an example of a unicast use case.

[0214] The Tx UE (202) can forward all received HARQ feedback to the gNB (201). Alternatively, to reduce overhead, the Tx UE (202) can feed back compressed information to the gNB (201).

[0215] The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, such as resource allocations for SCI and PSSCH, so that the Tx UE (202) or Rx UE (203) can know the resources used to transmit or receive data on the sidelink.

[0216] The scheduling DCI can carry information about the resources used for HARQ feedback. The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time or frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, RRC. In the case of a UE scheduled to receive on a sidelink, the UE can transmit HARQ feedback to the Tx UE (202) using the allocated resources on the sidelink. In the case of a UE scheduled to transmit on a sidelink, the UE can monitor or receive HARQ feedback from the allocated resources.

[0217] The scheduling DCI can carry time and frequency resource allocations for feedback from the Tx UE (202) to the gNB (201). For a UE scheduled to receive on the sidelink, the UE may ignore resource allocations for feedback from the Tx UE (202) to the gNB (201). For a UE scheduled to transmit on the sidelink, the UE may transmit feedback to the gNB (201) using resources allocated through the Uu interface.

[0218] When the gNB (201) transmits scheduling DCIs to the Tx UE (202) and Rx UE (203), the same DCI format may be used for the Tx UE (202) and Rx UE (203), for example, the scheduling DCIs for the Tx UE (202) and Rx UE (203) may carry the same DCI fields. For example, the DCIs for the Tx UE (202) and Rx UE (203) may have the same RNTI, for example, SLUnicast-RNTI , SLGroupcast-RNTI It can be scrambled. The UE can check the transmit / receive indicator field in the DCI to determine whether it is scheduled for the Tx UE (202) or Rx UE (203).

[0219] Alternatively, scheduling DCIs for the Tx UE (202) or Rx UE (203) may be transmitted in different DCI formats, for example, scheduling DCIs for the Tx UE (202) or Rx UE (203) may carry different DCI fields. For example, the DCI for the Tx UE (202) or Rx UE (203) may be scrambled into different RNTIs. The UE may each have two RNTIs for unicast and groupcast, for example, SLUnicastTx-RNTI or SLUnicastRx-RNTI ; or SLGroupcastTx-RNTI or SLGroupcastRx-RNTI It can be configured as. The UE DCI SLUnicastTx-RNTI or SLGroupcastTx-RNTI If the UE detects that it is scrambling, it can determine that it is scheduled for transmission over the sidelink. The UE DCI SLUnicastRx-RNTI or SLGroupcastRx-RNTI If scrambling is detected, the UE can determine that it is scheduled for reception on the sidelink.

[0220] When gNB (201) sends a scheduling DCI only to Tx UE (202), gNB (201) can schedule sidelink communication through the following examples:

[0221] Scheduling DCI only - Example 1 of sidelink communication scheduling: gNB (201) can transmit only the scheduling DCI to Tx UE (202), where HARQ feedback is transmitted from Rx UE (203) to gNB (201) via the Uu interface. FIG. 13 illustrates an example of a unicast use case.

[0222] The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, for example, resource allocations for SCI and PSSCH. The Tx UE (202) indicates resource allocations to the Rx UE (203) via SCI. Thus, both the Tx UE (202) and the Rx UE (203) can know the resources used to transmit and receive data over the sidelink.

[0223] The scheduling DCI can carry information about the resources used for HARQ feedback. The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time and frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, the RRC. The Tx UE (202) can indicate resource allocation to the Rx UE (203) via the SCI. For a UE scheduled to transmit over a sidelink, the UE can ignore resource allocation for HARQ feedback. For a UE scheduled to receive over a sidelink, the UE can transmit HARQ feedback to the gNB (201) via the Uu interface using the allocated resources.

[0224] Scheduling DCI only - Example 2 of sidelink communication scheduling: gNB (201) can transmit only the scheduling DCI to Tx UE (202), where HARQ feedback is transmitted from Rx UE (203) to Tx UE (202) over the sidelink. FIG. 14 illustrates an example of a unicast use case.

[0225] The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, for example, resource allocations for SCI and PSSCH. The Tx UE (202) indicates resource allocations to the Rx UE (203) via SCI. Thus, both the Tx UE (202) and the Rx UE (203) can know the resources used to transmit and receive data over the sidelink.

[0226] The scheduling DCI can carry information about the resources used for HARQ feedback. The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time and frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, the RRC. The Tx UE (202) indicates resource allocation to the Rx UE (203) via the SCI. In the case of a UE scheduled to receive on a sidelink, the UE can transmit HARQ feedback to the Tx UE (202) using the allocated resources on the sidelink. In the case of a UE scheduled to transmit on a sidelink, the UE can monitor or receive HARQ feedback from the allocated resources.

[0227] Scheduling DCI only - Example 3 of sidelink communication scheduling: gNB (201) can transmit only the scheduling DCI to Tx UE (202), where HARQ feedback is first transmitted from Rx UE (203) to Tx UE (202) over the sidelink, and then Tx UE (202) feeds back the received information to gNB (201) through the Uu interface.

[0228] FIG. 15a illustrates an example of a use case. FIG. 15b illustrates an exemplary method flow. In summary, as described in more detail below, at step 251, a scheduling DCI can be obtained by the Tx UE (202). At step 252, the Tx UE (202) can send a transmission to the Rx UE (203) via a side link. At step 253, based on step 252, the Tx UE (202) can receive feedback from the Rx UE (203). As provided in more detail herein, in relation to FIG. 15 and other figures (e.g., FIG. 20 through 22 or FIG. 6 through 7, etc.), there may be different scheduling and different approaches associated with the scheduling DCI.

[0229] The Tx UE (202) can transmit (e.g., forward) all received HARQ feedback to the gNB (201). Alternatively, to reduce overhead, the Tx UE (202) can provide compressed information. The scheduling DCI can carry time and frequency resource allocations for sidelink transmission, e.g., resource allocations for SCI and PSSCH. The Tx UE (202) indicates resource allocations to the Rx UE (203) via SCI. Thus, both the Tx UE (202) and the Rx UE (203) can know the resources used to transmit and receive data over the sidelink.

[0230] The scheduling DCI can carry information about the resources used for HARQ feedback transmitted from the Rx UE (203) to the Tx UE (202). The resources used for HARQ can be explicitly indicated by the scheduling DCI, for example, time and frequency resources; or they can be implicitly indicated by an index of the HARQ feedback resource configuration configured by the scheduling DCI, for example, the RRC. The Tx UE (202) indicates resource allocation to the Rx UE (203) via the SCI. In the case of a UE scheduled to receive on a sidelink, the UE can transmit HARQ feedback to the Tx UE (202) using the allocated resources on the sidelink. In the case of a UE scheduled to transmit on a sidelink, the UE can monitor or receive HARQ feedback from the allocated resources. For example, the scheduling DCI may carry a single DCI field, e.g., a PSFCH resource indicator field, that indicates the resources used to transmit HARQ feedback from the Rx UE (203)(s) to the Tx UE (202), each value of which may be configured by the RRC configuration or associated with an indexed PSFCH resource predefined in the specification.

[0231] The UE may be configured with a common PSFCH resource configuration or a dedicated PSFCH resource configuration used to transmit HARQ feedback from the Rx UE (203)(s) to the Tx UE (202) over the sidelink. For example, the UE may be configured with a common RRC configuration via broadcast signaling, e.g., via RMSI or OSI. psfch - ResourceCommon It can be configured as; or the UE has a dedicated RRC configuration PSFCH ResourceSet It can be composed of. PSFCH ResourceSet is one or more RRC configurations PSFCH-Resource It may include, where RRC configuration PSFCH-Resource An example of this is shown in Fig. 19.

[0232] If 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 is configured psfch - ResourceCommon or configured PSFCH ResourceSet You can determine the corresponding PSFCH resource through .

[0233] If both common configuration and private configuration are supported, when the UE receives the scheduling DCI and decodes the PSFCH resource indicator field, the UE private RRC configuration PSFCH ResourceSet via or if a dedicated RRC configuration is not configured, common RRC configuration psfch - ResourceCommon You can determine the corresponding PSFCH resource through this.

[0234] As another example, the scheduling DCI may carry one DCI field, for example, an SL HARQ timing indicator field, that indicates the timing for transmitting HARQ feedback from the Rx UE (203) to the Tx UE (202).

[0235] In one approach, the indicated timing may be a time offset between the HARQ feedback (from Rx UE (203) to Tx UE (202)) and the scheduled initial transmission on the sidelink. For example, the UE has an RRC parameter containing the contents of a sequence of integers (0.. 15) (size (8)). sl-InitialDataToSL-ACK It may be an RRC composed of candidate time offsets, where the time offsets may be in slots, mini-slots, or symbols. When the UE receives the scheduling DCI and decodes the SL HARQ timing indicator field, the UE has the configured RRC parameters sl-InitialDataToSL-ACK The time offset can be determined by finding the corresponding entry.

[0236] In another approach, the indicated timing may be the time offset between the HARQ feedback (from Rx UE (203) to Tx UE (202)) and the last scheduled iteration / retransmission (in other words, iteration or retransmission) for the transmission block (TB) on the sidelink. k Assuming that n iterations / retransmissions are scheduled by the scheduling DCI, the SL HARQ timing indicator field is scheduled with the HARQ feedback k Indicates the time offset between the nth iteration / retransmission. If no iteration is scheduled, for example, k If =0, the SL HARQ timing indicator field indicates the time offset between the HARQ feedback and the scheduled initial transmission. For example, the UE has an RRC parameter containing the contents of a sequence of integers (0.. 15) (size (8)). sl-LoadDataToSL-ACK It may be an RRC composed of candidate time offsets, where the time offsets may be in slots, mini-slots, or symbols. When the UE receives the scheduling DCI or decodes the UL HARQ timing indicator field, the UE [decodes] the configured RRC parameters sl-LoadDataToSL-ACK The time offset can be determined by finding the corresponding entry.

[0237] The scheduling DCI can carry time and frequency resource allocations for feedback from the Tx UE (202) to the gNB (201). The Tx UE (202) may not indicate resource allocations to the Rx UE (203) via the SCI. For a UE scheduled to transmit over a sidelink, the UE can transmit feedback to the gNB (201) using the allocated resources via the Uu interface. For example, the scheduling DCI can carry one DCI field, e.g., a PUCCH resource indicator field, indicating the resources used to transmit HARQ feedback from the V2X UE (e.g., Tx UE (202)) to the gNB (201), where each value is associated with an indexed PUCCH resource configured by the RRC configuration or predefined in the specification.

[0238] The UE may be configured with a common PUCCH resource configuration or a dedicated PUCCH resource configuration used for transmitting HARQ information for downlink transmissions on the Uu interface. The UE may use the same set of common or dedicated configurations for transmitting HARQ information on the Uu interface for sidelink transmissions on the sidelink. For example, when the UE receives a scheduling DCI or decodes the PUCCH resource indicator field, the UE PUCCH-Config Dedicated RRC configuration in PUCCH - ResourceSet Common RRC configuration on SIB1 via or if a dedicated RRC configuration is not configured pucch - ResourceCommon You can determine the corresponding PUCCH resource through this.

[0239] Alternatively, the UE may be configured with different sets of common or dedicated configurations for the transmission of HARQ information on the Uu interface for sidelink transmission on the sidelink. For example, the UE may have a common RRC configuration via broadcast signaling, e.g., RMSI or OSI. pucch - sl - ResourceCommonIt can be configured as; or the UE has a dedicated RRC configuration SL-PUCCH-ResourceSet It can be composed of.

[0240] In cases where only one of the common configuration and the dedicated configuration is supported, when the UE receives the scheduling DCI and decodes the PUCCH resource indicator field, the UE is configured pucch - sl - ResourceCommon or configured SL-PUCCH-ResourceSet You can determine the corresponding PUCCH resource through .

[0241] When both common and dedicated configurations are supported, when the UE receives the scheduling DCI or decodes the PUCCH resource indicator field, the UE uses the dedicated RRC configuration SL-PUCCH-ResourceSet via or if a dedicated RRC configuration is not configured, common RRC configuration pucch-sl-ResourceCommon You can determine the corresponding PUCCH resource through this.

[0242] As another example, the scheduling DCI may carry one DCI field, for example, a UL HARQ timing indicator field, that indicates the timing for transmitting HARQ feedback from the V2X UE (e.g., Tx UE (202)) to the gNB (201).

[0243] In one approach, the indicated timing may be a time offset between the HARQ feedback (from the V2X UE to the gNB (201)) and the scheduled initial transmission on the sidelink. For example, the UE has an RRC parameter containing the contents of a sequence of integers (0.. 15) (size (8)). sl-InitalDataToUL-ACK It may be an RRC composed of candidate time offsets, where the time offsets may be in slots, mini-slots, or symbols. When the UE receives the scheduling DCI and decodes the UL HARQ timing indicator field, the UE [describes] the configured RRC parameters sl-InitalDataToUL-ACK The time offset can be determined by finding the corresponding entry.

[0244] In the second approach, the indicated timing may be a time offset between the scheduled HARQ feedback transmitted over the sidelink (from Rx UE (203) to Tx UE (202)) and the HARQ feedback (from V2X UE to gNB (201)). For example, the UE has an RRC parameter containing the contents of a sequence of integers (0.. 15) (size (8)). sl-ACKToUL-ACK It may be an RRC composed of candidate time offsets, where the time offsets may be in slots, mini-slots, or symbols. When the UE receives the scheduling DCI or decodes the UL HARQ timing indicator field, the UE [decodes] the configured RRC parameters sl-ACKToUL-ACK The time offset can be determined by finding the corresponding entry.

[0245] In the third approach, the indicated timing may be the time offset between the HARQ feedback (from the V2X UE to the gNB (201)) and the last scheduled iteration / retransmission for the transmission of the TB on the sidelink. k Assuming that n iterations / retransmissions are scheduled by the scheduling DCI, the UL HARQ timing indicator field is scheduled with the HARQ feedback k Indicates the time offset between the nth iteration / retransmission. If no iteration is scheduled, for example, k If =0, the UL HARQ timing indicator field indicates the time offset between the HARQ feedback and the scheduled initial transmission. For example, the UE has an RRC parameter containing the contents of a sequence of integers (0.. 15) (size (8)). sl-LastDataToUL-ACK It may be an RRC composed of candidate time offsets, where the time offsets may be in slots, mini-slots, or symbols. When the UE receives the scheduling DCI and decodes the UL HARQ timing indicator field, the UE [deciphers] the configured RRC parameters sl-LastDataToUL-ACKThe time offset can be determined by finding the corresponding entry.

[0246] When the gNB schedules sidelink transmissions using dynamic scheduling acknowledgments, the gNB (201) can schedule multiple retransmissions / repetitions of the TB along with the scheduling of the initial transmission of the TB using a single DCI.

[0247] When the gNB (201) dynamically schedules the sidelink transmission of the TB using the DCI, the gNB (201) may schedule one or more retransmissions / repeats of the TB using the same scheduling DCI. Retransmissions or HARQ feedback may be performed by the Tx UE (202) or Rx UE (203) in particular in the following ways: 1) DCI-scheduled blind retransmission on the sidelink; 2) DCI-scheduled HARQ feedback-based retransmission on the sidelink; or 3) DCI-scheduled HARQ feedback-based retransmission with an early termination transmitted on the Uu interface.

[0248] DCI Scheduled Blind Retransmission on Sidelink

[0249] DCI-scheduled blind retransmission on the sidelink: In one case, after receiving the scheduling DCI, the Tx UE (202) may blind transmit all scheduled transmissions. For example, the Tx UE (202) may perform all scheduled initial transmissions and retransmissions / repetitions regardless of whether the Rx UE (203) successfully decodes the data. In this case, one HARQ feedback resource allocation may be scheduled by the DCI on the sidelink where the Rx UE (203)(s) transmit HARQ feedback to the Tx UE (202); and one HARQ feedback resource allocation may be scheduled by the DCI on the Uu interface where the Tx UE (202) transmits HARQ feedback to the gNB (201). An example in which the scheduling DCI schedules an initial transmission in slot 0 and two retransmissions in slots 1 and 2, respectively, is illustrated in FIG. 20. The transmission of SCI is scheduled in slot 0; the transmission of HARQ feedback from Rx UE (203) to Tx UE (202) is scheduled in slot 2; and the transmission of HARQ feedback from Tx UE (202) to gNB (201) is scheduled in slot 3.

[0250] In the example illustrated in the drawing, the initial transmission and retransmissions are scheduled in adjacent slots. In another example, the initial transmission and retransmissions may be scheduled in non-adjacent slots, for example, the initial transmission may be scheduled in slot 0, and two retransmissions may be scheduled in slots 2 and 4, respectively.

[0251] The Rx UE (203)(s) can determine the scheduled initial transmission and retransmission by decoding the SCI. If the Rx UE (203) fails to receive the sidelink transmission after all iterations, the Rx UE (203) can send a NACK to the Tx UE (202) using the scheduled HARQ feedback resources, for example, the HARQ feedback resources in slot 2 of FIG. 20. If the Rx UE (203) successfully receives the sidelink transmission, the Rx UE (203) can send an ACK to the Tx UE (202) using the scheduled HARQ feedback resources, or the Rx UE (203) can not send anything to the Tx UE (202) on the scheduled HARQ feedback resources. If the Rx UE (203) successfully receives a sidelink transmission before all scheduled retransmissions, for example, if the Rx UE (203) successfully receives a sidelink transmission after the initial transmission or after the first retransmission, the Rx UE (203) may skip the remaining scheduled retransmissions and not attempt to decode the PSSCH.

[0252] After the Tx UE (202) receives HARQ feedback, for example, an ACK or a NACK from the Rx UE (203), the Tx UE (202) can transmit HARQ feedback to the gNB (201) using scheduled HARQ feedback resources on the Uu interface, for example, the HARQ feedback resources in slot 3 of FIG. 20.

[0253] DCI scheduled HARQ feedback-based retransmission on the sidelink

[0254] DCI-Scheduled HARQ Feedback-Based Retransmission on Sidelink: In other cases, the scheduling DCI may schedule HARQ feedback-based retransmission on the sidelink. An example in which the scheduling DCI schedules an initial transmission in slot 0 and two retransmissions in slots 1 and 2, respectively, is illustrated in FIG. 21. The scheduling DCI schedules the transmission of HARQ feedback from the Rx UE (203) to the Tx UE (202) 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 the Tx UE (202) to the gNB (201) is scheduled in slot 3.

[0255] In the example illustrated in the drawing, the sidelink transmission and the associated HARQ feedback on the sidelink are scheduled in the same slot. In other examples, the sidelink transmission and the associated HARQ feedback may be scheduled in different slots, for example, the transmission of HARQ feedback from Rx UE (203) to Tx UE (202) may be scheduled in slots 1, 2, and 3, respectively. The initial transmission and retransmission may be scheduled in adjacent slots as illustrated in FIG. 20, or they may be scheduled in non-adjacent slots, for example, the initial transmission and the associated HARQ feedback may be scheduled in slots 0 and 1, respectively, the first retransmission and the associated HARQ feedback may be scheduled in slots 2 and 3, respectively, the second retransmission and the associated HARQ feedback may be scheduled in slots 4 and 5, respectively, and the same applies to others.

[0256] The Rx UE (203)(s) can determine scheduled initial transmissions and retransmissions by decoding the SCI. For each transmission, the Rx UE (203) can send HARQ feedback, e.g., ACK / NACK-based feedback or NACK-only-based feedback, to the Tx UE (202) using associated HARQ feedback resources. The Tx UE (202) can perform scheduled retransmissions for the TB until the Rx UE (203) successfully receives the TB. If the Tx UE (202) receives a NACK for all HARQ feedback on the sidelink, the sidelink transmission fails. The Tx UE (202) can send a NACK to the gNB (201) using scheduled HARQ feedback resources on the Uu interface. If the scheduled sidelink transmission is successful, the Tx UE (202) can send an ACK to the gNB (201) using the scheduled HARQ feedback resources.

[0257] If a scheduled sidelink transmission for a TB, e.g., TB 1, is successful before all scheduled retransmissions are performed, the Tx UE (202) can transmit another TB, e.g., TB 2, using resources for the remaining retransmissions. According to the example illustrated in FIG. 21, if the transmission of TB 1 is successful in slot 0, the Tx can transmit TB 2 using resources scheduled in slots 1 and 2. In the case of the Rx UE (203), after successfully receiving the scheduled TB, the Rx UE (203) can continue to monitor and decode the PSSCH transmitted over the resources for the remaining retransmissions and can transmit feedback to the Tx UE (202) using associated feedback resources. The Tx UE (202) can transmit HARQ feedback to the gNB (201) based on the transmission result for the scheduled TB. For example, if the transmission of TB 1 in slot 0 is successful and the transmission of TB 2 in slots 1 and 2 fails, the Tx UE (202) can still send an ACK to the gNB (201) using the resources in slot 3.

[0258] In another approach, if a scheduled sidelink transmission succeeds before all scheduled retransmissions are performed, unused resources, e.g., resources scheduled for retransmissions and associated HARQ feedback on the sidelink, may be released. The Tx UE (202) may not transmit data on the remaining scheduled retransmissions. The Rx UE (203) may skip decoding the remaining scheduled retransmissions and not transmit feedback on the associated resources. Once the resources are released, the Mode-2 V2X UE(s) may schedule sidelink transmissions on those resources.

[0259] The scheduling DCI may use one PSFCH resource indicator field and one SL HARQ timing indicator field to indicate multiple HARQ feedback resources on the sidelink. For example, the SL HARQ timing indicator field may indicate a time offset between each initial transmit / retransmission and its associated HARQ feedback resources. For example, the Tx UE (202) may first determine the resources for the initial transmit and retransmission. Then, the Tx UE (202) may apply the indicated time offset to them and determine the associated HARQ feedback resources on the sidelink. After decoding the PSFCH resource indicator field and the SL HARQ timing indicator field within the scheduling DCI, the Tx UE (202) may transmit information to the Rx UE (203)(s) by, for example, transmitting the same fields having the same values ​​within the SCI to the Rx UE (203). Similar to the Tx UE (202), based on whether the scheduled retransmission is a blind retransmission or a HARQ feedback-based retransmission, the Rx UE (203) can determine the scheduled HARQ feedback resources on the sidelink accordingly. When the 2-stage SCI is applied, the PSFCH resource indicator field and the SL HARQ timing indicator field can be carried by the 1-stage SCI.

[0260] DCI scheduled HARQ feedback-based retransmission with early termination transmitted over the Uu interface

[0261] DCI-scheduled HARQ feedback-based retransmission with early termination transmitted over the Uu interface: In another case, the scheduling DCI may schedule a HARQ feedback-based retransmission with early termination transmitted over the Uu interface. In FIG. 22, an SCI is scheduled in slot 0; an initial transmission, associated HARQ feedback resources on the sidelink (from Rx UE (203) to Tx UE (202)) or associated HARQ feedback resources on the Uu interface (from Tx UE (202) to gNB (201)) are scheduled in slots 0, 0, and 1, respectively; a first retransmission, associated HARQ feedback resources on the sidelink and associated HARQ feedback resources on the Uu interface are scheduled in slots 1, 1, and 2, respectively; An example is illustrated in which the second retransmission, associated HARQ feedback resources on the sidelink, and associated HARQ feedback resources on the Uu interface are scheduled in slots 2, 2, and 3, respectively.

[0262] In the example illustrated in the drawing, HARQ feedback resources on the Uu interface for the initial transmission and HARQ feedback resources for the first retransmission on the sidelink are scheduled in the same slot. In other examples, they may be scheduled in different slots. For example, the initial transmission, the associated HARQ feedback resources on the sidelink, and the associated HARQ feedback resources on the Uu interface are scheduled in slots 0, 0, and 1, respectively; the first retransmission, the associated HARQ feedback resources on the sidelink, and the associated HARQ feedback resources on the Uu interface are scheduled in slots 2, 2, and 3, respectively; and the second retransmission, the associated HARQ feedback resources on the sidelink, and the associated HARQ feedback resources on the Uu interface are scheduled in slots 4, 4, and 5, respectively. The sidelink transmission or the associated HARQ feedback on the sidelink may be scheduled in the same slot or in different slots.

[0263] The Rx UE (203)(s) can determine scheduled initial transmissions and retransmissions by decoding the SCI. For each transmission, the Rx UE (203) can transmit HARQ feedback, e.g., ACK / NACK-based feedback or NACK-only-based feedback, to the Tx UE (202) using scheduled HARQ feedback resources on the sidelink. The Tx UE (202) can be scheduled with dedicated HARQ feedback resources on the Uu interface for each initial transmission or retransmission.

[0264] If a scheduled transmission fails after a transmission that may be an initial transmission or a retransmission (excluding the final retransmission), the Tx UE (202) may not transmit any feedback on the HARQ feedback resource on the Uu interface and may skip it.

[0265] If a scheduled transmission succeeds before the last retransmission, the Tx UE (202) may send an early termination indication to the gNB (201) to release the reserved resources so that the gNB (201) can use the reserved resources for other purposes. Using FIG. 21 as an example, if the transmission succeeds after the first retransmission, the Tx UE (202) may not send the remaining scheduled retransmission(s), e.g., the second retransmission in the figure, and may send an ACK to the gNB (201) using the associated HARQ feedback resources on the Uu interface, e.g., the HARQ feedback resources on the Uu interface within slot 2 in the figure, to indicate that the remaining reserved resources are released. The Rx UE (203) may skip decoding the remaining scheduled retransmissions and may not send feedback on the associated resources on the sidelink.

[0266] Once the resources reserved by the gNB (201) are released, in one approach, only the gNB (201) can schedule other sidelink transmissions on the released resources. Or, in another approach, both the gNB (201) and the Mode-2 V2X UE(s) can schedule sidelink transmissions on the released resources. In this case, either of the above two approaches may be supported. In the other case, both of the above approaches may be supported. In this case, the Tx UE (202) may be signaled by the gNB (201) whether the released resources can be reused only by the gNB (201) or by both the gNB (201) and the Mode-2 V2X UE(s). Signaling may be done via DCI signaling, for example, by the resource reuse indicator field within the scheduling DCI. For example, when the field is set to '0', it indicates that the released resources can be reused only by the gNB (201); when the field is set to '1', it indicates that the released resources can be reused by the gNB (201) and the Mode-2 V2X UE(s). Signaling is also by RRC configuration, e.g., RRC parameters Released-Resource-Reuse It can be done through. For example, UE ' gNB only 'person Released-Resource-Reuse In the case where it is configured as such, the released resources can only be reused by the gNB (201); and the UE ' gNB and Mode-2 V2X UE 'person Released-Resource-Reuse In the case where it is configured as such, the released resources can be reused by both the gNB (201) and the Mode-2 V2X UE(s).

[0267] If the scheduled transmission fails before the last retransmission, the Tx UE (202) can send HARQ feedback to the gNB (201) based on the HARQ feedback result sent by the Rx UE (203) for the last retransmission.

[0268] The scheduling DCI may use one PUCCH resource indicator field and one UL HARQ timing indicator field to indicate multiple HARQ feedback resources on the Uu interface. For example, the UL HARQ timing indicator field may indicate a time offset between each initial transmission or retransmission and its associated HARQ feedback resources. For example, the Tx UE (202) may first determine the resources for the initial transmission or retransmission. Then, the Tx UE (202) may apply the indicated time offset to them and determine the associated HARQ feedback resources on the Uu interface. After decoding the PUCCH resource indicator field or the UL HARQ timing indicator field within the scheduling DCI, the Tx UE (202) may transmit information to the Rx UE (203)(s) by, for example, transmitting the same fields having the same values ​​within the SCI to the Rx UE (203). Similar to the Tx UE (202), based on whether the scheduled retransmission is a blind retransmission or a HARQ feedback-based retransmission, the Rx UE (203) can determine the scheduled HARQ feedback resources on the sidelink accordingly. When a 2-stage SCI is applied, the PUCCH resource indicator field or the UL HARQ timing indicator field may be carried by the 1-stage SCI.

[0269] As proposed in this specification, in some scenarios, both blind retransmission and HARQ feedback-based retransmission may be supported. In one approach, the A field within the scheduling DCI may be used to indicate which retransmission mode is being scheduled. For example, a retransmission mode indicator field (1 bit) may be carried by the scheduling DCI. When the retransmission mode indicator is set to '0', the retransmission scheduled with the initial transmission by the scheduling DCI is a blind retransmission; when the retransmission mode indicator is set to '1', the retransmission scheduled with the initial transmission by the scheduling DCI is a HARQ feedback-based retransmission.

[0270] In another approach, retransmission mode information can be statically configured by RRC. For example, RRC parameters SL-Retransmission-Mode It can be configured, and here the value is ' blind ' and ' HARQ-based It could be. UE is blind 'person SL-Retransmission-Mode When configured as such, the retransmission scheduled with the initial transmission by the scheduling DCI is a blind retransmission; and the UE ' HARQ-based 'person SL-Retransmission-Mode When configured as such, the retransmission scheduled along with the initial transmission by the scheduling DCI is a HARQ feedback-based retransmission.

[0271] After the Tx UE (202) determines the retransmission mode, the Tx UE (202) can use the SCI to convey information to the Rx UE (203)(s) by means of, for example, the retransmission mode indicator field (1 bit) in the SCI transmitted to the Rx UE (203). For example, if the Tx UE (202) is scheduled for blind retransmission, the Tx UE (202) can set the retransmission mode indicator of the SCI to '0'; and if the Tx UE (202) is scheduled for HARQ feedback-based retransmission, the Tx UE (202) can set the retransmission mode indicator of the SCI to '1'. In the case of the Rx UE (203), the Rx UE (203) can determine the retransmission mode by decoding the corresponding retransmission mode indicator field in the scheduling SCI.

[0272] For a V2X UE operating in Mode 2, the V2X UE can monitor SCIs from other V2X UEs before scheduling a sidelink transmission. When the V2X UE detects and decodes an SCI scheduling a sidelink transmission for another UE, it can determine whether a resource allocation for HARQ feedback and data transmission on the sidelink can be released and reused, for example, by decoding a resource reuse indicator field (1 bit) within the SCI. When a 2-stage SCI is applied, the resource reuse indicator field may be carried by a 1-stage SCI.

[0273] For example, if the detected resource reuse indicator field is set to '0', the V2X UE can determine that resource allocations in the SCI are reserved in advance and will not be released. The V2X UE can ignore the resources reserved in the SCI and search for other available resources.

[0274] If the detected resource reuse indicator field is set to '1', the V2X UE may determine that resource allocations in the SCI can be released. The V2X UE monitors release signaling and, if release signaling is detected, may reuse the reserved resources. For example, the V2X UE may monitor HARQ feedback on resources scheduled by the SCI. If the V2X UE detects that a scheduled transmission is successful before all scheduled transmissions are performed, for example by detecting ACK feedback from one of the scheduled HARQ feedback resources, or by detecting that no signaling is transmitted from one of the scheduled HARQ feedback resources, the V2X UE may treat the remaining resources originally reserved by the SCI for HARQ feedback and PSSCH transmissions as available resources on which the V2X UE can schedule sidelink transmissions.

[0275] For Tx UE (202), if resources within the SCI are released and can be reused by Mode-2 V2X UEs, Tx UE (202) can set the resource reuse indicator field within the SCI to '1'; if resources within the SCI are not released or resources within the SCI are released but cannot be reused by Mode-2 V2X UEs, Tx UE (202) can set the resource reuse indicator field within the SCI to '0'.

[0276] In one case, the retransmission mode indicator field and the resource reuse indicator field may be two different fields transmitted from the SCI. In some other cases, the value of the retransmission mode indicator field and the value of the resource reuse indicator field may have a one-to-one mapping, for example, both fields may be '0' or '1' at the same time. In these cases, only one of the retransmission mode indicator field and the resource reuse indicator field may be carried by the SCI.

[0277] For example, only the retransmission mode indicator field may be carried by the SCI. Then, Mode-2 V2X UEs can read the retransmission mode indicator field and determine information following the same method as reading the resource reuse indicator field disclosed herein, and vice versa.

[0278] In the SCI, the field may be used to indicate whether the transmission scheduled by the SCI is scheduled by the gNB (201) or by the Tx UE (202). For example, the resource allocation mode indicator field (1 bit) may be carried by the scheduling SCI. When the retransmission mode indicator is set to '0', it indicates that the sidelink transmission is scheduled by the gNB (201), e.g., mode 1 resource allocation; when the retransmission mode indicator is set to '1', it indicates that the sidelink transmission is scheduled by the V2X UE, e.g., mode 2 resource allocation. When a 2-stage SCI is applied, the resource allocation mode indicator field may be carried by the 1-stage SCI.

[0279] For example, when Mode-2 V2X UEs detect that a sidelink transmission is scheduled by the gNB (201), Mode-2 V2X UEs may assume that the reserved resources cannot be reused and may ignore the resource reuse indicator field in the SCI. Mode-2 V2X UEs may not monitor signals transmitted on the feedback resources scheduled by the SCI. When Mode-2 V2X UEs detect that a sidelink transmission is scheduled by another Mode-2 V2X UE, Mode-2 V2X UEs may read the resource reuse indicator field in the SCI and determine whether the reserved resources can be reused. If the reserved resources can be reused, Mode-2 V2X UEs may monitor signals transmitted on the feedback resources scheduled by the SCI. Also, in this example, the resource reuse indicator field may not be transmitted in the scheduling SCI. For example, Mode-2 V2X UEs can decode the retransmission mode indicator field in the SCI to determine whether reserved resources can be reused when a sidelink transmission is scheduled by another Mode-2 V2X UE. When the retransmission mode indicator field is set to '0', reserved resources cannot be reused; when the retransmission mode indicator field is set to '1', reserved resources can be reused. In this example, the resource allocation mode indicator field and the retransmission mode indicator field may be two different fields in the SCI; or the resource allocation mode indicator and the retransmission mode indicator may be two different bits in a single SCI field, for example, the resource allocation mode indicator may be the most significant bit and the retransmission mode indicator may be the least significant bit.

[0280] The subject disclosed above may apply when gNB (201) schedules CSI feedback over a sidelink, e.g., CSI reports, mobility measurements, beam management measurements, etc. For example, gNB (201) may transmit the scheduling of measurements and reports to both Tx UE (202) and Rx UE (203); or gNB (201) may transmit the scheduling of measurements and reports only to Tx UE (202), and then Tx UE (202) displays this to Rx UE (203) via SCI. Additionally, Rx UE (203) may transmit reports to gNB (201) via the Uu interface; or Rx UE (203) may transmit reports to Tx UE (202) over the sidelink; Alternatively, Rx UE (203) can first send a report to Tx UE (202), and then Tx UE (202) can send a report to gNB (201) through the Uu interface.

[0281] The subject disclosed above may be applied to a shared carrier scenario where the Uu interface and sidelink share a carrier. An example is illustrated in FIG. 16. In this example, scheduling is self-contained, which can reduce latency, but may require the UE to have sufficient capability for this. Scheduling may also be cross-slot. For example, scheduling DCI may occur in slot 0, and scheduled sidelink transmission in slot k It can occur in, and here k =1, 2, 3 etc.

[0282] Some special considerations for group cast use cases: In a group cast scenario, the gNB (201) can send scheduling DCIs to multiple Rx UEs (203). Dedicated resources may be used for scheduling DCIs for different Rx UEs (203). Alternatively, to reduce overhead, shared resources may be used for scheduling DCIs for different Rx UEs (203) in the following examples. When shared resources are used, a common search space having the same CORESET may be configured for all UEs in the group.

[0283] Example 1 of how shared resources can be used for scheduling DCIs for different Rx UEs: Scheduling DCIs can be SDM. The gNB (201) can form multiple beams to transmit scheduling DCIs to different Rx UEs (203) using the same time and frequency resources. When multiple Rx UEs (203) are QCLed for the same beam, scheduling DCIs between Rx UEs (203) QCLed for the same beam can be TDM or FDM, whereas scheduling DCIs for Rx UEs (203) on different beams are SDM.

[0284] Example 2 of shared resources being available for scheduling DCIs for different Rx UEs: gNB (201) can transmit the same scheduling DCI to multiple Rx UEs (203), for example, to all UEs in a proximity group when an omnidirectional antenna is used, or, for example, to RX UEs (203) QCLed to the same beam in a proximity group when scheduling DCIs for different beams are SDM, TDM, or FDM. The scheduling DCI can carry both a group / beam common DCI field (in other words, a group common DCI field or a beam common DCI) and UE-specific DCI fields. The group / beam common DCI field carries the DCI shared by Rx UEs (203) in a proximity group or by Rx UEs (203) QCLed to the same beam in a proximity group. For example, the group / beam common DCI field may carry time and frequency resource allocations for transmit / retransmit, a BWP indicator field, a resource indicator field, a transmit / receive indicator field, a slot format indicator field, etc. The UE-specific DCI fields are DCIs dedicated to each Rx UE (203), for example, a dedicated DCI field for Rx UE (203 1), a dedicated DCI field for Rx UE (203 2), ..., Rx UE (203 nIt carries a dedicated DCI field for the UE. For example, the UE-dedicated DCI field may carry time and frequency resource allocations for HARQ feedback, CSI feedback, etc. Each UE may be configured with a temporary ID within a proximity group or a temporary ID within a beam. The UE can obtain the full DCI signaled by the gNB (201) by checking the UE-dedicated DCI field and the group / beam common DCI field associated with the configured temporary ID. For example, in the case of a UE configured as UE 1 as the temporary ID, the UE may read the dedicated DCI field or the common DCI field for the Rx UE (203) (having ID UE 1) to obtain the full DCI information.

[0285] Example 3 where shared resources can be used for scheduling DCIs for different Rx UEs: While the gNB (201) can transmit the same scheduling DCI to all Rx UEs (203), the scheduling DCI may not carry UE-specific DCI fields. The scheduling DCI may carry only group / beam common DCI fields, and each UE may derive allocated UE-specific resources from the signaled scheduling DCI. For example, as an option, the DCI may carry a single allocation of time and frequency resources for HARQ feedback or CSI feedback for all UEs. The UE [receives] the allocated resources nIt may autonomously divide into parts and use associated parts, e.g., parts associated with configured temporary IDs, to transmit HARQ feedback, CSI reports, mobility measurements, beam management measurements, etc. As another option, the DCI may carry time and frequency resource allocations for HARQ feedback or CSI feedback for a single UE, e.g., a UE configured as a temporary ID (Rx UE (203) having ID UE 1). UEs configured with other temporary IDs may autonomously derive the resources to be used by the UEs from the resource allocation for the Rx UE (203) having ID UE 1. For example, the scheduling DCI may use RB 0 through RB 0 k It can indicate that -1 is assigned to the Rx UE (203) (having ID UE 1). The Rx UE (203) (another one having ID UE 2) is assigned RB in the same symbols as the allocated resources, etc. k To RB 2 k You can autonomously decide whether to use -1.

[0286] In a group cast scenario, when the Tx UE (202) is scheduled by the gNB (201) to transmit feedback via the Uu interface, the Tx UE (202) may transmit compressed feedback information derived from the feedback of the received Rx UEs (203) to reduce overhead. In the case of HARQ feedback, the Tx UE (202) may transmit a single HARQ feedback to the gNB (201) to indicate whether retransmission of the entire group cast transmission is required; or the Tx UE (202) may transmit HARQ feedback of each beam to the gNB (201) to indicate which beam(s) need to be retransmitted, where the bitmap is, for example, {b k-1 , ..., b1, b0} is b k-1 This is mapped to the first beam and b0 is kIt can be used in a manner that maps to the nth beam; or the Tx UE (202) can indicate to the gNB (201) the number of beams that need to be retransmitted. For measurement and reporting, the Tx UE (202) can transmit a proposed MCS level derived from a CSI report from the Rx UE (203) to assist the gNB (201) in determining the MCS level to be used for sidelink transmission.

[0287] In a group cast scenario, different Rx UEs (203) may have different QoS requirements. Based on the QoS requirements, the Rx UE (203) may be indicated whether the UE will send HARQ feedback to the gNB (201) / Tx UE (202). The Rx UE (203) may be statically configured by an RRC configuration, or may be semi-permanently enabled and disabled by an enable DCI, or may be dynamically signaled by a scheduling DCI having such information. For example, the UE RRC parameters SL-HARQ It can be configured by the gNB (201), where 'on' indicates that HARQ feedback is enabled and 'off' indicates that HARQ feedback is disabled. Alternatively, a 1-bit HARQ feedback enable field can be carried by the enable DCI, disable DCI, or scheduling DCI transmitted by the gNB (201), where '1' indicates that HARQ feedback is enabled and '0' indicates that HARQ feedback is disabled. A similar idea can be applied to CSI feedback, e.g., CSI reporting, beam management measurement reporting, mobility RSRP, or RSRQ measurement reporting. For example, the UE can be statically configured by the RRC configuration, can be semi-permanently enabled and disabled by the enable DCI, or can be dynamically signaled by the scheduling DCI when the UE needs to report channel status information by the gNB (201) or not.

[0288] In a group cast scenario, for a UE enabled to transmit HARQ feedback, the UE may transmit an ACK when the UE successfully decodes the data and a NACK when the UE fails to decode the data. Alternatively, in another option, the UE may transmit a NACK only when the UE fails to decode the data. When the UE successfully decodes the data, the UE must not transmit HARQ feedback on the allocated HARQ feedback resources. In this case, the Tx UE (202) or gNB (201) may assume that the data has been successfully received by the Rx UE (203) if no feedback is received on the allocated HARQ feedback resources.

[0289] In a group cast scenario, retransmission may be triggered based on the transmitter's QoS requirements or the data's QoS requirements, for example, high reliability data may request the Tx UE (202) not to receive ACKs from all Rx UEs (203s) or not to receive NACKs from any Rx UE (203). Thus, retransmission may be triggered if the Tx UE (202) does not receive all ACK feedback or receives a NACK from any Rx UE (203); low reliability data may request the Tx UE (202) to receive NACKs from the Rx UEs (203s) that are lower than the percentage of all Rx UEs (203s). The Tx UE (202) may be statically configured by an RRC configuration, may be semi-permanently enabled and disabled by an enable DCI, or may be dynamically signaled by a scheduling DCI having such information by the gNB (201). For example, Tx UE (202) is an RRC parameter for indicating the QoS requirements of the data Reliability-Type RRC parameters to indicate the threshold used to trigger and retransmission Reliability-PercentageIt can be configured by the gNB (201). Or, in another example, the Tx UE (202) may have an RRC parameter to indicate the threshold used to trigger a retransmission. Reliability-Percentage It can be configured by gNB (201). To indicate the reliability requirements of the data for each scheduling acceptance, a DCI field can be signaled by gNB (201) in the enabled / disabled DCI or scheduling DCI, and, for example, a 1-bit field having '1' indicating high reliability data and '0' indicating high reliability data can be used.

[0290] In a group cast scenario, once a retransmission is triggered, the Tx UE (202) can group cast a retransmission to all Rx UEs (203s) in the proximity group as in the initial transmission. Alternatively, the Tx UE (202) can send a retransmission only to NACKed Rx UEs (203s) or NACKed beams. The Tx UE (202) can be statically configured by an RRC configuration, semi-permanently enabled and disabled by an enable DCI, or dynamically signaled by a scheduling DCI containing such information by the gNB (201). For example, the Tx UE (202) RRC parameters SL-Retransmission-TypeIt may be configured by the gNB (201). Alternatively, the DCI field may be signaled by the gNB (201) in the enable / disable DCI or the scheduling DCI to indicate how retransmission is performed for each scheduling acknowledgment, for example, a 1-bit field may be used having '1' indicating group casting for retransmission for all Rx UEs (203s) and '0' indicating retransmission for NACKed UEs / beams. In the case of Rx UEs (203s), when receiving a retransmission, an Rx UE (203) that has ACKed the initial transmission may ignore the retransmission; an Rx UE (203) that has NACKed the initial transmission may decode the retransmission or decode the data by chasing the retransmission and the initial transmission together.

[0291] Measurement and reporting on the sidelink: Support for CSI feedback on the sidelink is disclosed herein. The Rx UE (203) may report channel status information, beam management measurement results, or mobility measurement results to the gNB (201) or the Tx UE (202). Periodic, semi-permanent, and non-periodic measurements or reporting may be supported in the NR V2X.

[0292] For periodic measurement or reporting, both the Tx UE (202) and the Rx UE (203) are RRC configured SL-CSI-ReportConfig It can be composed of. The UE is SL-CSI-ReportConfig It can be composed of multiple components, where each component is a single ID, e.g., config-ID It is associated with. Each configuration can carry information such as parameters that need to be reported; information on reference signals used to perform measurements; and resources used for reporting.

[0293] UE is RRC configured SL-CSI-ReportConfigIt may be configured to report a single parameter or a set of parameters, and the parameters may be Type I channel state information, e.g., CQI, RI, PMI; Type II channel state information, e.g., interference conditions, eigenvalues ​​and eigenvectors of the channel matrix, etc.; RSRP, RSRQ measurements for beam management; RSRP, RSRQ measurements for mobility. The UE configures the RRC to display the reference signal used to perform the measurement. SL-CSI-ReportConfig It can be configured by SSB indexes, DMRS ports, CSI-RS configurations, or SRS configurations. The UE uses RRC configuration to indicate the resources used for reporting. SL-CSI-ReportConfig By means of, time and frequency resources, e.g., slot index, start and length of symbol, time offset value, start RB index, bitmap of RB used, number of adjacent RBs used.

[0294] For semi-permanent measurement and reporting, both the Tx UE (202) and the Rx UE (203) have multiple RRC configurations SL-CSI-ReportConfig It can be configured as follows. gNB(201) can trigger semi-permanent measurements and reports using the CSI acquisition and reporting fields within the active DCI, for example, 0 indicates not triggering measurements and reports; other values ​​indicate triggered SL-CSI-ReportConfig Displays the index of. gNB (201) can trigger semi-permanent measurements and reporting by sending an activation DCI to both Tx UE (202) and Rx UE (203). Alternatively, gNB (201) can trigger semi-permanent measurements and reporting by sending an activation DCI to Tx UE (202), and Tx UE (202) can display the triggered semi-permanent measurements to Rx UR via SCI.

[0295] For non-periodic measurement and reporting, both the Tx UE (202) and the Rx UE (203) have multiple RRC configurations SL-CSI-ReportConfig It can be configured as follows. gNB(201) can schedule non-periodic measurements and reports using the CSI acquisition and reporting fields within the scheduling DCI, for example, 0 indicates that measurements and reports are not scheduled, and other values ​​indicate that they are scheduled. SL-CSI-ReportConfig Displays the index of. gNB (201) can schedule non-periodic measurements and reports by sending the scheduling DCI to Tx UE (202) or Rx UE (203). Alternatively, gNB (201) can schedule non-periodic measurements and reports by sending the scheduling DCI to Tx UE (202), and Tx UE (202) can display the scheduled non-periodic measurements and reports to Rx UR via SCI.

[0296] RRC configuration-based resource allocation on sidelinks

[0297] Broadcast sidelink transmission

[0298] Broadcast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node can statically configure the resources used by the UE for broadcast sidelink transmission. The UE can be statically configured with resources for broadcast sidelink transmission via RRC configuration. When the UE has data to transmit over the sidelink, the UE can broadcast control and data using the configured resources without dynamic acknowledgment.

[0299] A UE can be statically configured by RRC with broadcast occupations. A broadcast occupation (BO) can be defined as the allocation of sidelink resources in time, frequency, and space (e.g., directional antennas, panels, or directional beams) for broadcasting. RRC configurations can be configured via broadcasted signals, e.g., through OSI, or through common or dedicated RRC configurations on the Uu interface.

[0300] To support statically configuring occupations for broadcast, group cast, or unicast sidelink transmission in NR V2X, different IEs, e.g., SL-ConfigureGrantConfig-Broadcast, SL-ConfigureGrantConfig-Groupcast and SL-ConfigureGrantConfig-Unicast ...may be used; or if the type of sidelink transmission, e.g., broadcast, groupcast, or unicast, is specified in IE, the same IE, e.g., SL-ConfigureGrantConfig can be used. IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-Broadcast It can specifically carry the following RRC configurations: 1) type of sidelink transmission; 2) type of carrier; 3) numerology of the resource; 4) broadcast transmission UE sidelink ID on the sidelink; 5) periodicity of the BO; 6) frequency domain resource allocation; or 7) beam sweeping information.

[0301] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0302] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0303] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0304] This is an RRC configuration for indicating the UE sidelink ID for broadcast transmission on the sidelink. For broadcast sidelink transmission, the UE can be configured with the UE ID on the sidelink as the source ID or destination ID. For example, the UE is a sidelink broadcast transmission RNTI to be used as the source ID ( SL-BT-RNTI It can be composed of ). The UE is a sidelink broadcast receiving RNTI that is used as a destination ID where each destination ID can be associated with a different service ( SL-BR-RNTI It can be composed of ).

[0305] When generating an SCI for broadcast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, while the other is 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.

[0306] This is an RRC configuration to indicate the periodicity of BO.

[0307] This is an RRC configuration for indicating time domain resource allocation. It is disclosed that time domain resources for BO can be configured with the following alternatives:

[0308] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for the BO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b sis mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0309] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the BO. The UE may be composed of a slot / subframe offset of the BO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the BO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the BO. The aforementioned parameters may be composed of distinct configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the value of the start or duration.

[0310] For broadcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE may be composed of a single time domain resource and may determine time domain resources for all directions by some predefined rules. Alternatively, the UE may be composed of time domain resources for each direction. For example, the UE may be represented by multiple start and duration values ​​of time domain resources. Or, the UE may be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0311] For broadcast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH or PSSCH. Alternatively, time domain resources for PSCCH or PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH or PSSCH, respectively.

[0312] This is an RRC configuration for indicating frequency domain resource allocation. The UE can be configured with frequency resources adjacent to the BO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBG It can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0313] For broadcast sidelink transmission, the configured acknowledgment may configure frequency domain resources for both the PSCCH and PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH and PSSCH are TDMed and utilize the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH and PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0314] This is an RRC configuration for displaying beam sweeping information. For broadcast sidelink transmission, the transmitter UE (202) can broadcast information in multiple directions using multiple beams.

[0315] Alternative 1: gNB (201) can determine the number of beam sweeps that the UE needs to perform and can configure the determined value for the UE in the configured acknowledgments. The UE may provide auxiliary information to the NB to help the NB determine the beam sweeping configuration. This auxiliary information may include one or more of the following: V2X services of interest, e.g., UE capabilities regarding the number of concurrent beam sweeping directions the UE can cover, UE scheduling preferences including sleep mode preferences, etc.

[0316] UE k Assuming it is configured to broadcast information through several directions / beams, the UE, for each beam, kIt may be composed of BOs. Or the UE may be composed of one BO for all beams. The beams used for beam sweeping may be configured by gNB (201). Or the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0317] Alternative 2: The number of beam sweeps can be determined by the UE. The UE may be configured by the RRC into a single BO containing multiple symbols or mini-slots. The UE may autonomously utilize the configured symbols and mini-slots within the BO for beam sweeping. The beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0318] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0319] If there is a conflict between the RRC-configured BOs and the DCI-signaled SFI, the DCI may overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If the BO is configured in a mini-slot and there is a conflict for some of the symbols in the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0320] Unicast sidelink transmission

[0321] In NR V2X, a gNB (201) or a gNB-type node can statically configure resources used by a UE for unicast sidelink transmission. It is disclosed that a UE can statically configure resources for unicast sidelink transmission / reception through RRC configuration. When a UE has data to transmit over a sidelink, the UE can unicast control and data to a paired UE using the configured resources without dynamic acknowledgment.

[0322] It is disclosed that a UE can be statically configured by RRC with unicast occupations. A unicast occupation (UO) can be defined as an allocation of sidelink resources in time, frequency, and space for unicasting (e.g., directional antennas or panels or directional beams). RRC configurations can be configured via broadcasted signals, e.g., OSI, or via common or dedicated RRC configurations on the Uu interface. IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-Unicast It is disclosed that it can carry, in particular, the following RRC configurations: 1) type of sidelink transmission; 2) type of carrier; 3) numerology of resources; 4) unicast UE ID on the sidelink; 5) unicast paired UE ID; 6) periodicity of UO; 7) time domain resources; 8) number of repeat and duplicate versions; 9) frequency domain resources; 10) HARQ feedback information; or 11) retransmission related information.

[0323] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0324] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0325] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0326] This is an RRC configuration for displaying the unicast UE ID on the sidelink. For unicast sidelink communication, the UE uses a UE ID, for example, SL-U-RNTI It can be configured as follows. In the case of the transmitter UE (202), the UE may use SL-U-RNTI as the source ID. In the case of the receiver UE (203), the UE SL-U-RNTI It can be used as the destination ID.

[0327] This is an RRC configuration for displaying the unicast paired UE ID. To perform unicast sidelink communication, the UE needs to know the information of the paired UE. The UE uses the RRC from the configured acknowledgment to obtain the ID of the paired UE, for example, SL-UP-RNTI It can be configured as follows. In the case of the transmitter UE (202), the ID of the paired UE can be used as the destination ID. In the case of the receiver UE (203), the ID of the paired UE can be used as the source ID.

[0328] When generating an SCI for unicast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, while the other is 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.

[0329] This is an RRC configuration to indicate the periodicity of UO.

[0330] This is an RRC configuration for representing time domain resource allocations. It is disclosed that time domain resources for UO can be configured with the following alternatives.

[0331] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for the UO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1{, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0332] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the UO. The UE may be composed of a slot / subframe offset of the UO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the UO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the UO. The aforementioned parameters may be composed of distinct configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the values ​​of the start and duration.

[0333] For unicast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH or PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH or PSSCH, respectively.

[0334] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat unicast sidelink transmissions. The UE can be configured with the numbers of repeats and RVs by the gNB (201) through the RRC configuration. A similar idea can be applied to groupcast sidelink transmissions. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. Alternatively, the UE may use symbols or mini-slots within the same slot for repetition.

[0335] This is an RRC configuration for displaying information related to HARQ feedback. A UE can be configured with the number of the HARQ process. A UE can be configured with a single UO for both transmission and feedback. Resources used for feedback, for example, the time offset between transmission and feedback, can be indicated in the SCI in transmission. Alternatively, a UE can be configured with dedicated UOs for transmission and feedback, respectively. The UO for transmission and the UO for feedback can be configured with a one-to-one mapping. A receiver UE (203) can transmit feedback using the associated feedback UO when a transmission is received.

[0336] This is an RRC configuration for displaying retransmission-related information. When a NACK is received by the transmitter UE (202), retransmission can be performed. The UE may be configured with dedicated UOs for retransmission. The UO for transmission and the UO for feedback may be configured with a one-to-one mapping. The transmitter UE (202) may transmit a retransmission using the associated retransmission UO when the NACK is received. Alternatively, no dedicated retransmission UO may be configured. The UE may utilize resources within the UO configured for transmission and retransmission. Resources used for retransmission, for example, the time offset between transmission and retransmission, may be indicated in the SCI in transmission or in the feedback transmitted by the receiver UE (203).

[0337] This is an RRC configuration for indicating frequency domain resource allocation. A UE can be configured with adjacent frequency resources for a UO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBG It can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0338] For unicast sidelink transmission, the configured acknowledgment may configure frequency domain resources for the PSCCH or PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH or PSSCH is TDMed and uses the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH and PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0339] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0340] If there is a conflict between RRC-configured UOs and DCI-signaled SFIs, DCI may overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If a UO is configured in a mini-slot and there is a conflict with some of the symbols in the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0341] Groupcast Sidelink transmission

[0342] Group Cast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node may statically configure the resources used by the UE for group cast sidelink transmission. It is disclosed that the UE may statically configure the resources for group cast sidelink transmission / repeating via RRC configuration. When the UE has data to transmit over the sidelink, the UE may group cast the control and data to a group of UEs using the configured resources without dynamic acknowledgment.

[0343] It is disclosed that a UE can be statically configured by RRC with group cast operations. A group cast operation (GO) can be defined as an allocation of sidelink resources in time, frequency, and space for group casting (e.g., directional antennas or panels or directional beams). RRC configurations can be configured via broadcasted signals, e.g., OSI, or via common or dedicated RRC configurations on the Uu interface. The inventors [disclose] an IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-Groupcast It discloses that it can carry the following RRC configurations:

[0344] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0345] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-CarriertypeIf configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0346] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0347] This is an RRC configuration for indicating the group transport ID on the sidelink. For groupcast sidelink transmission, the UE can be configured with the UE ID on the sidelink. For example, the UE is the UE ID, e.g., SL-G-RNTI It can be composed of. If the UE needs to group cast on the sidelink, the UE as a source ID within the formed group SL-G-RNTI You can use .

[0348] This is an RRC configuration for displaying the group ID on the sidelink. The UE uses the group ID, for example, SL-GD-RNTI It can be configured as follows. The UE can use the configured group ID as the destination group ID.

[0349] When generating an SCI, the scrambling sequence for the SCI can be jointly initialized by the destination group ID and the source ID. Alternatively, the scrambling sequence for the SCI can be initialized by either the destination group ID or the source ID, while the other is 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.

[0350] This is an RRC configuration to indicate the periodicity of GO.

[0351] This is an RRC configuration for representing time domain resource allocations. It is disclosed that time domain resources for GO can be configured with the following alternatives:

[0352] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for GO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0353] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the GO. The UE may be composed of a slot / subframe offset of the GO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the GO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the GO. The aforementioned parameters may be composed of distinct configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the values ​​of the start and duration.

[0354] For groupcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE may be composed of a single time domain resource and may determine time domain resources for all directions by some predefined rules. Alternatively, the UE may be composed of time domain resources for each direction. For example, the UE may be represented by multiple start and duration values ​​of time domain resources. Or, the UE may be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0355] For groupcast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH and PSSCH, respectively.

[0356] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat groupcast sidelink transmissions. The UE can be configured with the numbers of repeats and RVs by the gNB (201) via the RRC configuration. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. Alternatively, the UE may use symbols or mini-slots within the same slot for repetition. If beam sweeping is applied in the groupcast, the transmitter UE (202) performs full beam sweeping, e.g., beam 1, beam 2, ..., beam k , beam 1, beam 2, ..., beam k , ..., Beam 1, Beam 2, ..., Beam k ...can be repeated. Or, the UE repeats for each beam and then beam sweeping, e.g., Beam 1, Beam 1, ..., Beam 1, Beam 2, Beam 2, ..., Beam 2, ..., Beam k , beam k , ..., beam k It can perform.

[0357] This is an RRC configuration for displaying information related to HARQ feedback. A UE can be configured with the number of the HARQ process. A UE can be configured with a single GO for both transmission and feedback. Resources used for feedback, for example, the time offset between transmission and feedback, can be indicated in the SCI in transmission. Alternatively, a UE can be configured with dedicated GOs for transmission and feedback, respectively. The GO for transmission and the GO for feedback can be configured with a one-to-one mapping. When a transmission is received, the receiver UE (203) can transmit feedback using the associated feedback GO.

[0358] This is an RRC configuration for displaying retransmission-related information. When a NACK is received by the transmitter UE (202), a retransmission can be performed. The UE may be configured with dedicated GOs for retransmission. The GOs for transmission and the GOs for feedback may be configured with a one-to-one mapping. The transmitter UE (202) may transmit a retransmission using the associated retransmission GO when a NACK is received. Alternatively, no dedicated retransmission GO may be configured. The UE may utilize resources within the GOs configured for transmission and retransmission. Resources used for retransmission, for example, the time offset between transmission and retransmission, may be indicated in the SCI in transmission or in the feedback transmitted by the receiver UE (203).

[0359] This is an RRC configuration for indicating frequency domain resource allocation. The UE can be configured with adjacent frequency resources for the GO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBGIt can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0360] For groupcast sidelink transmission, the configured acknowledgment may configure frequency domain resources for the PSCCH or PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH and PSSCH are TDMed and utilize the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH or PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0361] This is an RRC configuration for displaying beam sweeping information. For group cast sidelink transmission, the transmitter UE (202) can group cast information in multiple directions using multiple beams.

[0362] Alternative 1: gNB(201) can determine the number of beam sweeping operations the UE needs to perform and can configure the determined value for the UE in the configured acknowledgment. The UE k Assuming that it is configured to group-cast information through directions / beams, the UE for each beam kIt may be composed of GOs. Or the UE may be composed of one GO for all beams. The beams used for beam sweeping may be configured by the gNB (201). Or the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on detection or discovery.

[0363] Alternative 2: The number of beam sweeps can be determined by the UE. The UE may be configured by the RRC into a single GO containing multiple symbols or mini-slots. The UE may autonomously utilize the configured symbols and mini-slots within the GO for beam sweeping. The beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0364] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0365] If there is a conflict between the RRC-configured GOs and the DCI-signaled SFIs, the DCI may overwrite the RRC configuration. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If a GO is configured in a mini-slot and there is a conflict for some of the symbols in the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0366] Enable / Disable-based resource allocation on sidelinks

[0367] Broadcast sidelink transmission

[0368] Broadcast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node may permanently allocate resources used by a UE for broadcast sidelink transmission. It is disclosed that a UE may be permanently signaled to resources for broadcast sidelink transmission via RRC configuration and enable DCI. When a UE has data to transmit over the sidelink, the UE may broadcast control and data using the enabled resources without dynamic acknowledgment. The gNB (201) may disable the enabled resources using a disable DCI.

[0369] It is disclosed that a UE can be semi-permanently allocated by an active DCI and RRC having broadcast occupations. A broadcast occupation (BO) can be defined as an allocation of sidelink resources in time, frequency, and space for broadcasting (e.g., directional antennas or panels or directional beams). RRC configurations can be configured via a broadcasted signal, e.g., through OSI or through a common or dedicated RRC configuration on the Uu interface.

[0370] Detailed design for RRC configuration: To permanently allocate occupations for broadcast, group cast, or unicast sidelink transmissions in NR V2X, different IEs, e.g., SL-ConfigureGrantConfig-Broadcast, SL-ConfigureGrantConfig-Groupcast and SL-ConfigureGrantConfig-Unicast ...may be used; or if the type of sidelink transmission, e.g., broadcast, groupcast, or unicast, is specified in IE, the same IE, e.g., SL-ConfigureGrantConfig It is disclosed that [it] can be used. IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-BroadcastIt is disclosed that the following RRC configurations can be carried to convey information about the BO to be activated:

[0371] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0372] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0373] This is an RRC configuration for displaying indexes of candidate resources. A UE can be composed of multiple BOs to be activated. Each BO can be associated with a single dedicated resource index. For example, RRC configuration NR-BO-Index The UE can determine which BO is enabled / disabled through the enabled / disabled DCI.

[0374] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0375] This is an RRC configuration for indicating the UE sidelink ID for broadcast transmission on the sidelink. For broadcast sidelink transmission, the UE can be configured with the UE ID on the sidelink as the source ID or destination ID. For example, the UE is a sidelink broadcast transmission RNTI to be used as the source ID ( SL-BT-RNTI It can be composed of ). The UE is a sidelink broadcast receiving RNTI that is used as a destination ID where each destination ID can be associated with a different service ( SL-BR-RNTI It can be composed of ).

[0376] When generating an SCI for broadcast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, while the other is 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.

[0377] This is an RRC configuration to indicate the periodicity of BO.

[0378] This is an RRC configuration for indicating time domain resource allocation. It is disclosed that time domain resources for BO can be configured with the following alternatives:

[0379] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for the BO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b sis mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0380] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the BO. The UE may be composed of a slot / subframe offset of the BO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the BO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the BO. The aforementioned parameters may be composed of separate configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the values ​​of the start and duration.

[0381] For broadcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE may be composed of a single time domain resource and may determine time domain resources for all directions by some predefined rules. Alternatively, the UE may be composed of time domain resources for each direction. For example, the UE may be represented by multiple start and duration values ​​of time domain resources. Or, the UE may be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0382] For broadcast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH and PSSCH, respectively.

[0383] This is an RRC configuration for indicating frequency domain resource allocation. The UE can be configured with frequency resources adjacent to the BO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBG It can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0384] For broadcast sidelink transmission, the configured acknowledgment may configure frequency domain resources for both the PSCCH and PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH and PSSCH are TDMed and utilize the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH and PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0385] This is an RRC configuration for displaying beam sweeping information. For broadcast sidelink transmission, the transmitter UE (202) can broadcast information in multiple directions using multiple beams.

[0386] Alternative 1: gNB(201) can determine the number of beam sweeping operations the UE needs to perform and can configure the determined value for the UE in the configured acknowledgment. The UE k Assuming it is configured to broadcast information through several directions / beams, the UE, for each beam, k It may be composed of BOs. Or the UE may be composed of one BO for all beams. The beams used for beam sweeping may be configured by gNB (201). Or the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0387] Alternative 2: The number of beam sweeps can be determined by the UE. The UE may be configured by the RRC into a single BO containing multiple symbols or mini-slots. The UE may autonomously utilize the configured symbols and mini-slots within the BO for beam sweeping. The beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0388] Detailed Design for Enable / Deactivate DCI: Enable / Deactivate DCI can be used to semi-permanently enable / deactivate BO. To distinguish Enable / Deactivate DCI from other DCIs, a new RNTI, for example, SL-CS-RNTI It can be used to scramble the CRC of the enable / disable DCI. To distinguish the enable / disable DCI for BO, GO, and UO, the enable / disable DCI payload may carry a field indicating the type of sidelink communication being enabled / disabled. Or different RNTIs, e.g., SL-BO-CS-RNTI , SL-GO-CS-RNTI , SL-UO-CS-RNTI can be used to scramble the CRC of the enabled / disabled DCI for BO, GO, and UO, respectively. UE can be configured as an RNTI for the enabled DCI by RRC.

[0389] The enable / disable DCI may also carry information about the BO to be enabled / disabled. It is disclosed that the enable / disable DCI for the BO may carry the following information:

[0390] This is an enable / disable flag field. To indicate whether the DCI is used for enable or disable, 1 bit in the enable / disable DCI may be used, for example, '0' to indicate that the DCI is used for enable and '1' to indicate that the DCI is used for disable.

[0391] This is a resource indicator field. A UE may be composed of multiple BOs via RRCs to be enabled / disabled. The enable / disable DCI may indicate the index of the BO to be enabled / disabled for broadcast sidelink transmission. Assuming the UE is composed of 8 BOs, for example, BO 0 through BO 7, a 3-bit resource indicator field may be used, having '000' to indicate BO 0, '001' to indicate BO 1, etc.

[0392] This is a sidelink type indicator field. An enabled DCI can indicate the type of sidelink transport. For example, a 2-bit sidelink type indicator field may be used, having '00' indicating that the DCI is enabling broadcast sidelink transport, '01' indicating that the DCI is enabling groupcast sidelink transport, '10' indicating that the DCI is enabling unicast sidelink transport, etc., and '11' indicating that the DCI is enabling resources for all types of sidelink transport.

[0393] This is the Carrier Type Indicator field. A UE can be semi-permanently indicated by a carrier type having 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 permission carrier between the UE and the sidelink; if the Carrier Type Indicator field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0394] It is a time domain resource allocation field. The time domain resource allocation field can carry time domain resource allocations for BO with the following alternatives:

[0395] Alternative 1: The UE may be signaled with one or more bitmaps to represent time-domain resources for the BO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, 2-level mapping may be used. Two bit strings may be signaled by the enable DCI, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0396] Alternative 2: The UE may be signaled with a time offset, start point, and duration to indicate time domain resources for the BO. The UE may be signaled with a slot / subframe offset of the BO. The time offset may relate to a slot / subframe carrying an active DCI. The UE may be signaled with a start index to indicate the start point of the BO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be signaled with the number of symbols or the number of mini-slots to indicate the duration of the BO. The aforementioned parameters may be signaled as separate fields, or some of the parameters may be signaled together. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be signaled with an index of the table to indicate the values ​​of the start and duration.

[0397] For broadcast sidelink transmission, the UE may transmit the same information in multiple directions. The UE may be signaled by a single time domain resource and may determine time domain resources for all directions by some predefined rules. Alternatively, the UE may be signaled by time domain resources for each direction. For example, the UE may be represented by multiple start and duration values ​​of time domain resources. Or, the UE may be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0398] For broadcast sidelink transmission, the enabling DCI may signal time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be signaled jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be signaled separately, and the enabling DCI may signal two time domain resources for PSCCH and PSSCH, respectively.

[0399] This is a frequency domain resource allocation field. The frequency domain resource allocation field can carry frequency domain resource allocations for BO. The UE can be signaled to adjacent frequency resources for BO. Frequency resources can be signaled in RBs or subchannels, e.g., RBGs. Alternatively, the UE can be signaled by the index of the lowest RB and the number of allocated RBs, or the UE can be signaled by the index of the lowest RBG and the number of allocated RBGs. Alternatively, frequency resource allocations can be signaled by a bitmap. Each bit within the bitmap can represent one RB, one RBG, or one subchannel. The UE can be signaled by an index to represent the starting RB, RBG, or subchannel associated with the bitmap.

[0400] For broadcast sidelink transmission, the enabling DCI may signal frequency domain resources for PSCCH or PSSCH. Frequency domain resources for PSCCH and PSSCH may be signaled jointly, for example, if PSCCH and PSSCH are TDMed and use the same number of RBs, one frequency domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH and PSSCH may be signaled separately, and the enabling DCI may signal two frequency domain resources for PSCCH and PSSCH, respectively.

[0401] This is a beam sweeping information field. For group cast sidelink transmission, the transmitter UE (202) can group cast information in multiple directions using multiple beams in the following alternatives:

[0402] Alternative 1: gNB(201) can determine the number of beam sweeps the UE needs to perform and signal this to the UE via the enable DCI. The UE k Assuming that information is signaled to group cast through the directions / beams, the UE can be signaled with a single BO for all beams. The beams used for beam sweeping can be configured by the gNB (201). Alternatively, the beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0403] Alternative 2: The number of beam sweeps can be determined by the UE. The UE can be signaled by an activating DCI into a single BO containing multiple symbols or mini-slots. The UE can autonomously utilize the signaled symbols and mini-slots within the BO for beam sweeping. The beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0404] If part of the information in BO is represented by an active DCI, such as time domain resource allocation; frequency domain resource allocation, etc., gNB(201) does not configure the same information in the RRC configuration.

[0405] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0406] If there is a conflict between semi-permanently allocated BOs and DCI-signed SFIs, DCI may overwrite the allocation. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If a BO is allocated in a mini-slot and there is a conflict with some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0407] Unicast sidelink transmission

[0408] Unicast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node may permanently allocate resources used by a UE for unicast sidelink transmission. It is disclosed that a UE may be permanently signaled to resources for unicast sidelink transmission / reception via RRC configuration and enable DCI. When a UE has data to transmit over a sidelink, the UE may unicast control and data using the enabled resources without dynamic acknowledgment. The gNB (201) may disable the enabled resources using a disable DCI.

[0409] It is disclosed that a UE can be semi-permanently allocated by an active DCI and RRC having unicast occupations. A unicast occupation (UO) can be defined as an allocation of sidelink resources in time, frequency, and space for unicasting (e.g., directional antennas or panels or directional beams). RRC configurations can be configured via a broadcasted signal, e.g., through OSI, or through a common or dedicated RRC configuration on the Uu interface.

[0410] Detailed Design for RRC Configuration: IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-Unicast It is disclosed that it can carry the following RRC configurations to convey information about the UO to be activated:

[0411] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0412] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-CarriertypeIf configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0413] This is an RRC configuration for displaying the index of candidate resources. A UE can be composed of multiple UOs to be activated. Each UO can be associated with a single dedicated resource index. For example, RRC configuration NR-UO-Index The UE can determine which UO is enabled / disabled through the enabled / disabled DCI.

[0414] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0415] This is an RRC configuration for displaying the unicast UE ID on the sidelink. For unicast sidelink communication, the UE uses a UE ID, for example, SL-U-RNTI It can be configured as follows. In the case of the transmitter UE (202), the UE is as the source ID SL-U-RNTI It can be used. In the case of the receiver UE (203), the UE is SL-U-RNTI It can be used as the destination ID.

[0416] This is an RRC configuration for displaying the unicast paired UE ID. To perform unicast sidelink communication, the UE needs to know the information of the paired UE. The UE uses the RRC from the configured acknowledgment to obtain the ID of the paired UE, for example, SL-UP-RNTI It can be configured as follows. In the case of the transmitter UE (202), the ID of the paired UE can be used as the destination ID. In the case of the receiver UE (203), the ID of the paired UE can be used as the source ID.

[0417] When generating an SCI for unicast sidelink transmission, the scrambling sequence for the SCI may be jointly initialized by the source ID and destination ID. Alternatively, the scrambling sequence for the SCI may be initialized by either the source ID or the destination ID, while the other is 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.

[0418] This is an RRC configuration to indicate the periodicity of UO.

[0419] This is an RRC configuration for representing time domain resource allocations. It is disclosed that time domain resources for UO can be configured with the following alternatives:

[0420] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for the UO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1{, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0421] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the UO. The UE may be composed of a slot / subframe offset of the UO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the UO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the UO. The aforementioned parameters may be composed of distinct configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the values ​​of the start and duration.

[0422] For unicast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH and PSSCH, respectively.

[0423] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat unicast sidelink transmissions. The UE can be configured with the numbers of repeats and RVs by the gNB (201) through the RRC configuration. A similar idea can be applied to groupcast sidelink transmissions. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. Alternatively, the UE may use symbols or mini-slots within the same slot for repetition.

[0424] This is an RRC configuration for displaying information related to HARQ feedback. A UE can be configured with the number of the HARQ process. A UE can be configured with a single UO for both transmission and feedback. Resources used for feedback, for example, the time offset between transmission and feedback, can be indicated in the SCI in transmission. Alternatively, a UE can be configured with dedicated UOs for transmission and feedback, respectively. The UO for transmission and the UO for feedback can be configured with a one-to-one mapping. A receiver UE (203) can transmit feedback using the associated feedback UO when a transmission is received.

[0425] This is an RRC configuration for displaying retransmission-related information. When a NACK is received by the transmitter UE (202), retransmission can be performed. The UE may be configured with dedicated UOs for retransmission. The UO for transmission and the UO for feedback may be configured with a one-to-one mapping. The transmitter UE (202) may transmit a retransmission using the associated retransmission UO when the NACK is received. Alternatively, no dedicated retransmission UO may be configured. The UE may utilize resources within the UO configured for transmission and retransmission. Resources used for retransmission, for example, the time offset between transmission and retransmission, may be indicated in the SCI in transmission or in the feedback transmitted by the receiver UE (203).

[0426] This is an RRC configuration for indicating frequency domain resource allocation. A UE can be configured with adjacent frequency resources for a UO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBG It can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0427] For unicast sidelink transmission, the configured acknowledgment may configure frequency domain resources for the PSCCH or PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH and PSSCH are TDMed and utilize the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH and PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0428] Detailed Design for Enable / Deactivate DCI: Enable / Deactivate DCI can be used to semi-permanently enable / deactivate UO. To distinguish Enable / Deactivate DCI from other DCIs, a new RNTI, for example, SL-CS-RNTI It can be used to scramble the CRC of the enable / disable DCI. To distinguish the enable / disable DCI for BO, GO, and UO, the enable / disable DCI payload may carry a field indicating the type of sidelink communication being enabled / disabled. Or different RNTIs, e.g., SL-BO-CS-RNTI , SL-GO-CS-RNTI , SL-UO-CS-RNTI can be used to scramble the CRC of the enabled / disabled DCI for BO, GO, and UO, respectively. UE can be configured as an RNTI for the enabled DCI by RRC.

[0429] The enable / disable DCI may also carry information about the UO to be enabled / disabled. It is disclosed that the enable / disable DCI for the UO may carry the following information:

[0430] This is an enable / disable flag field. To indicate whether the DCI is used for enable or disable, 1 bit in the enable / disable DCI may be used, for example, '0' to indicate that the DCI is used for enable and '1' to indicate that the DCI is used for disable.

[0431] This is a resource indicator field. A UE may be composed of multiple UOs via RRCs to be enabled / disabled. The enable / disable DCI may indicate the index of the UO to be enabled / disabled for unicast sidelink transmission. Assuming the UE is composed of 8 UOs, for example, UO 0 through UO 7, a 3-bit resource indicator field may be used, having '000' to indicate UO 0, '001' to indicate UO 1, etc.

[0432] This is a sidelink type indicator field. An enabled DCI can indicate the type of sidelink transport. For example, a 2-bit sidelink type indicator field may be used, having '00' indicating that the DCI is enabling broadcast sidelink transport, '01' indicating that the DCI is enabling groupcast sidelink transport, '10' indicating that the DCI is enabling unicast sidelink transport, etc., and '11' indicating that the DCI is enabling resources for all types of sidelink transport.

[0433] This is the Carrier Type Indicator field. A UE can be semi-permanently indicated by a carrier type having 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 permission carrier between the UE and the sidelink; if the Carrier Type Indicator field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0434] This is the unicast sidelink UE ID field. In the case of unicast sidelink communication, the UE is the sidelink UE ID, for example, SL-U-RNTI It can be signaled semi-permanently. In the case of the transmitter UE (202), the UE is as the source ID SL-U-RNTI It can be used. In the case of the receiver UE (203), the UE is SL-U-RNTI It can be used as the destination ID. The activation DCI is the UE ID, e.g., SL-U-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can be composed of UE IDs, where each UE ID is associated with an index. The activation DCI indicates the index for the UE to determine the UE ID. n Bit fields can be used.

[0435] This is a unicast paired UE ID field. The UE can be signaled semi-permanently with the ID of the paired UE. When the UE needs to transmit over a unicast sidelink, the paired UE ID field indicates the ID of the receiver UE (203). When the UE is in receive mode, the paired UE ID field indicates the ID of the transmitter UE (202). The enable DCI is the paired UE ID, for example, SL-UP-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can be composed of paired UE IDs, where each paired UE ID is associated with an index. The activation DCI indicates the index for determining the UE ID to which the UE is paired. n Bit fields can be used.

[0436] It is a time domain resource allocation field. The time domain resource allocation field can carry time domain resource allocations for UO with the following alternatives:

[0437] Alternative 1: The UE may be signaled with one or more bitmaps to represent time-domain resources for the UO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b s is mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, 2-level mapping may be used. Two bit strings may be signaled by the enable DCI, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0438] Alternative 2: The UE may be signaled with a time offset, start point, and duration to indicate time domain resources for the UO. The UE may be signaled with a slot / subframe offset of the UO. The time offset may relate to a slot / subframe carrying an active DCI. The UE may be signaled with a start index to indicate the start point of the UO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be signaled with a number of symbols or a number of mini-slots to indicate the duration of the UO. The aforementioned parameters may be signaled as separate fields, or some of the parameters may be signaled together. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be signaled with an index of the table to indicate the values ​​of the start and duration.

[0439] For unicast sidelink transmission, the enabling DCI can signal time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH can be signaled jointly, for example, a single time domain resource allocation can be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH can be signaled separately, and the enabling DCI can signal two time domain resources for PSCCH and PSSCH, respectively.

[0440] This is a repeat indicator field. To improve reliability, the UE can repeat unicast sidelink transmissions. The UE can be signaled by the repeat number by the enable DCI. The UE can also be signaled by a pattern of RVs. For example, an RRC configuration can configure the UE with multiple candidate patterns of RVs, each having a pattern associated with a single index. The UE can be signaled by an index to indicate which pattern is used for the repeat. When the UE repeats the initial transmission, inter-slot or intra-slot repeats may be performed. The UE may use the same symbols or mini-slots in the following slots for the repeat. Alternatively, the UE may use symbols or mini-slots within the same slot for the repeat.

[0441] This is the HARQ process field. The UE can be signaled by the HARQ process number by the enable DCI.

[0442] This is a frequency domain resource allocation field. The frequency domain resource allocation field can carry frequency domain resource allocations for a UO. A UE can be signaled to adjacent frequency resources for a UO. Frequency resources can be signaled in RBs or subchannels, e.g., RGBs. Alternatively, a UE can be signaled by the index of the lowest RB and the number of allocated RBs, or a UE can be signaled by the index of the lowest RGB and the number of allocated RGBs. Alternatively, frequency resource allocations can be signaled by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. A UE can be signaled by an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0443] For unicast sidelink transmission, the enabling DCI may signal frequency domain resources for PSCCH or PSSCH. Frequency domain resources for PSCCH and PSSCH may be signaled jointly, for example, if PSCCH and PSSCH are TDMed and use the same number of RBs, one frequency domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH and PSSCH may be signaled separately, and the enabling DCI may signal two frequency domain resources for PSCCH and PSSCH, respectively.

[0444] If part of the information of the UO is represented by an active DCI, such as time domain resource allocation; frequency domain resource allocation, etc., the gNB (201) does not configure the same information in the RRC configuration.

[0445] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0446] If there is a conflict between semi-permanently allocated UOs and DCI-signed SFIs, DCI may overwrite the allocation. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If a UO is allocated in a mini-slot and there is a conflict with some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0447] Groupcast Sidelink transmission

[0448] Group Cast Sidelink Transmission: In NR V2X, a gNB (201) or a gNB-type node may permanently allocate resources used by a UE for group cast sidelink transmission. It is disclosed that a UE may be permanently signaled to resources for group cast sidelink transmission / reception via RRC configuration and enable DCI. When a UE has data to transmit over the sidelink, the UE may group cast control and data using the enabled resources without dynamic acknowledgment. The gNB (201) may disable the enabled resources using a disable DCI.

[0449] It is disclosed that a UE can be semi-permanently allocated by an active DCI and RRC having group cast occupations. A group cast occupation (GO) can be defined as an allocation of sidelink resources (e.g., directional antennas or panels or directional beams) in time, frequency, and space for group casting. RRC configurations can be configured via a broadcasted signal, e.g., through OSI, or through a common or dedicated RRC configuration on the Uu interface.

[0450] Detailed Design for RRC Configuration: IE SL-ConfigureGrantConfig or SL-ConfigureGrantConfig-Groupcast It is disclosed that it can carry the following RRC configurations to convey information about the GO to be activated:

[0451] This is an RRC configuration to indicate the type of sidelink transport. For example, the same IE for all sidelink transport types SL-ConfigureGrantConfig When used, Broadcast , groupcast , or Unicast Possible RRC configuration NR-SL-CommunicationType am.

[0452] This is an RRC configuration to indicate the carrier type. For example, RRC configuration NR-SL-CarrierType This can be used. NR-SL-Carriertype If configured to be 'shared', the UE determines that the sidelink resource allocation is for the sharing permission carrier between the Uu and the sidelink. NR-SL-Carriertype If configured to be 'dedicated', the UE determines that the sidelink resource allocation is for the dedicated sidelink carrier.

[0453] This is an RRC configuration for displaying indexes of candidate resources. A UE can be composed of multiple GOs to be activated. Each GO can be associated with a single dedicated resource index. For example, RRC configuration NR-G0-Index The UE can determine which GO is enabled / disabled through the enabled / disabled DCI.

[0454] This is an RRC configuration for indicating the numerology of resources for sidelink transmission. For example, an RRC configuration that could be 15, 30, 60KHz, etc. NR-SL-Numerology am.

[0455] This is an RRC configuration for indicating the groupcast transmission ID on the sidelink. For groupcast sidelink transmission, the UE can be configured with the UE ID on the sidelink. For example, the UE is the UE ID, e.g., SL-G-RNTIIt can be composed of. If the UE needs to group cast on the sidelink, the UE as a source ID within the formed group SL-G-RNTI You can use .

[0456] This is an RRC configuration for displaying the group ID on the sidelink. The UE uses the group ID, for example, SL-GD-RNTI It can be configured as follows. The UE can use the configured group ID as the destination group ID.

[0457] When generating an SCI, the scrambling sequence for the SCI can be jointly initialized by the destination group ID and the source ID. Alternatively, the scrambling sequence for the SCI can be initialized by either the destination group ID or the source ID, while the other is 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.

[0458] This is an RRC configuration to indicate the periodicity of GO.

[0459] This is an RRC configuration for representing time domain resource allocations. It is disclosed that time domain resources for GO can be configured with the following alternatives:

[0460] Alternative 1: The UE may consist of one or more bitmaps for representing time-domain resources for GO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b sis mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, a two-level mapping may be used. Two bit strings can be constructed by an RRC configuration, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0461] Alternative 2: The UE may be composed of a time offset, a start point, and a duration to represent time domain resources for the GO. The UE may be composed of a slot / subframe offset of the GO with respect to SFN=0. The UE may be composed of a start index to represent the start point of the GO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be composed of a number of symbols or a number of mini-slots to represent the duration of the GO. The aforementioned parameters may be composed of distinct configurations, or some of the parameters may be composed jointly. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be composed of an index of the table to represent the values ​​of the start and duration.

[0462] For groupcast sidelink transmission, the UE can transmit the same information in multiple directions. The UE may be composed of a single time domain resource and may determine time domain resources for all directions by some predefined rules. Alternatively, the UE may be composed of time domain resources for each direction. For example, the UE may be represented by multiple start and duration values ​​of time domain resources. Or, the UE may be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0463] For groupcast sidelink transmission, the configured acknowledgment may configure time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be configured jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be configured separately, and the configured acknowledgment may configure two time domain resources for PSCCH and PSSCH, respectively.

[0464] This is an RRC configuration for indicating the numbers of repeat and duplicate versions (RV). To improve reliability, the UE can repeat the groupcast sidelink transmission. The UE can be configured with the numbers of repeats and RVs by the gNB (201) via the RRC configuration. A similar idea can be applied to groupcast sidelink transmission. When the UE repeats the initial transmission, slot-to-slot or slot-to-slot repetition may be performed. The UE may use the same symbols or mini-slots in the following slots for repetition. Alternatively, the UE may use symbols or mini-slots within the same slot for repetition. If beam sweeping is applied in the groupcast, the transmitter UE (202) performs full beam sweeping, e.g., beam 1, beam 2, ..., beam k , beam 1, beam 2, ..., beam k , ..., Beam 1, Beam 2, ..., Beam k ...can be repeated. Or, the UE repeats for each beam and then beam sweeping, e.g., Beam 1, Beam 1, ..., Beam 1, Beam 2, Beam 2, ..., Beam 2, ..., Beam k , beam k , ..., beam k It can perform.

[0465] This is an RRC configuration for displaying information related to HARQ feedback. A UE can be configured with the number of the HARQ process. A UE can be configured with a single GO for both transmission and feedback. Resources used for feedback, for example, the time offset between transmission and feedback, can be indicated in the SCI in transmission. Alternatively, a UE can be configured with dedicated GOs for transmission and feedback, respectively. The GO for transmission and the GO for feedback can be configured with a one-to-one mapping. When a transmission is received, the receiver UE (203) can transmit feedback using the associated feedback GO.

[0466] This is an RRC configuration for displaying retransmission-related information. When a NACK is received by the transmitter UE (202), a retransmission can be performed. The UE may be configured with dedicated GOs for retransmission. The GOs for transmission and the GOs for feedback may be configured with a one-to-one mapping. The transmitter UE (202) may transmit a retransmission using the associated retransmission GO when a NACK is received. Alternatively, no dedicated retransmission GO may be configured. The UE may utilize resources within the GOs configured for transmission and retransmission. Resources used for retransmission, for example, the time offset between transmission and retransmission, may be indicated in the SCI in transmission or in the feedback transmitted by the receiver UE (203).

[0467] This is an RRC configuration for indicating frequency domain resource allocation. The UE can be configured with adjacent frequency resources for the GO. Frequency resources can be configured in RBs or subchannels, for example, in RBGs. Alternatively, the UE parameters StartRB and LengthRB It can be composed of, or the UE parameters StartRBG and LengthRBGIt can be configured as follows. Alternatively, frequency resources can be configured by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. The UE can be configured with an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0468] For groupcast sidelink transmission, the configured acknowledgment may configure frequency domain resources for the PSCCH or PSSCH. Frequency domain resources for the PSCCH and PSSCH may be configured jointly; for example, if the PSCCH and PSSCH are TDMed and utilize the same number of RBs, a single frequency domain resource allocation may be used for both the PSCCH and PSSCH. Alternatively, frequency domain resources for the PSCCH and PSSCH may be configured separately, and the configured acknowledgment may each have two frequency domain resources for the PSCCH and PSSCH, for example, StartRBG-PSCCH , LengthRBG-PSCCH and StartRBG-PSSCH , LengthRBG-PSSCH It can be composed of.

[0469] This is an RRC configuration for displaying beam sweeping information. For group cast sidelink transmission, the transmitter UE (202) can group cast information in multiple directions using multiple beams.

[0470] Alternative 1: gNB(201) can determine the number of beam sweeping operations the UE needs to perform and can configure the determined value for the UE in the configured acknowledgment. The UE k Assuming that it is configured to group-cast information through directions / beams, the UE for each beam kIt may be composed of GOs. Or the UE may be composed of one GO for all beams. The beams used for beam sweeping may be configured by the gNB (201). Or the beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on detection or discovery.

[0471] Alternative 2: The number of beam sweeps can be determined by the UE. The UE may be configured by the RRC into a single GO containing multiple symbols or mini-slots. The UE may autonomously utilize the configured symbols and mini-slots within the GO for beam sweeping. The beams used for beam sweeping may be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0472] Detailed Design for Enable / Deactivate DCI: Enable / Deactivate DCI can be used to semi-permanently enable / deactivate GO. To distinguish Enable / Deactivate DCI from other DCIs, a new RNTI, for example, SL-CS-RNTI It can be used to scramble the CRC of the enable / disable DCI. To distinguish the enable / disable DCI for BO, GO, and UO, the enable / disable DCI payload may carry a field indicating the type of sidelink communication being enabled / disabled. Or different RNTIs, e.g., SL-BO-CS-RNTI , SL-GO-CS-RNTI , SL-UO-CS-RNTI can be used to scramble the CRC of the enabled / disabled DCI for BO, GO, and UO, respectively. UE can be configured as an RNTI for the enabled DCI by RRC.

[0473] An enable / disable DCI may also carry information about the GO to be enabled / disabled. It is disclosed that an enable / disable DCI for a GO may carry the following information:

[0474] This is an enable / disable flag field. To indicate whether the DCI is used for enable or disable, 1 bit in the enable / disable DCI may be used, for example, '0' to indicate that the DCI is used for enable and '1' to indicate that the DCI is used for disable.

[0475] This is a resource indicator field. A UE can be composed of multiple GOs through RRCs to be enabled / disabled. The enabled / disabled DCI can indicate the index of the GO to be enabled / disabled for group cast sidelink transmission. Assuming the UE is composed of 8 GOs, for example, G0 0 to G0 7, a 3-bit resource indicator field can be used, having '000' indicating G0 0, '001' indicating G0 1, etc.

[0476] This is a sidelink type indicator field. An enabled DCI can indicate the type of sidelink transport. For example, a 2-bit sidelink type indicator field may be used, having '00' indicating that the DCI is enabling broadcast sidelink transport, '01' indicating that the DCI is enabling groupcast sidelink transport, '10' indicating that the DCI is enabling unicast sidelink transport, etc., and '11' indicating that the DCI is enabling resources for all types of sidelink transport.

[0477] This is the Carrier Type Indicator field. A UE can be semi-permanently indicated by a carrier type having 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 permission carrier between the UE and the sidelink; if the Carrier Type Indicator field is set to '1', the UE determines that the sidelink resource allocation is for a dedicated sidelink carrier.

[0478] This is the UE ID field for group cast transmission. The UE can be semi-permanently signaled with the UE ID within the group to indicate the source ID. The enabling DCI is the UE ID, e.g., SL-G-RNTI can be explicitly indicated. Or, the UE is 2 by RRC n It can consist of candidate IDs, where each candidate ID is associated with an index. The activation DCI is used by the UE to indicate an index for determining the source ID. n Bit fields can be used.

[0479] This is the Group ID field. The UE can be semi-permanently signaled with the Group ID to indicate the destination Group ID. The enabling DCI can explicitly indicate the Group ID, e.g., SL-GD-RNTI. Alternatively, the UE can be 2 by the RRC n It can consist of candidate IDs, where each candidate ID is associated with an index. The activation DCI is used by the UE to indicate the index for determining the group ID. n Bit fields can be used.

[0480] It is a time domain resource allocation field. The time domain resource allocation field can carry time domain resource allocations for GO with the following alternatives:

[0481] Alternative 1: The UE may be signaled with one or more bitmaps to represent time-domain resources for GO. The bitmaps may represent resources in subframes, slots, mini-slots, or symbols. For example, if the bitmap is used to represent resources in symbols, the bitmap may be mapped to symbols within a time interval, e.g., {b s , b s-1 , ..., b1, b0} is b sis mapped to the first symbol, and b0 is mapped to the last symbol. When a bitmap is used to display resources in mini-slots, it can be mapped to mini-slots within a time interval. For example, {b m , b m-1 , ..., b1, b0} is b m This is mapped to the first mini-slot, and b0 is mapped to the last mini-slot. Alternatively, to save mapping bits, 2-level mapping may be used. Two bit strings may be signaled by the enable DCI, for example, {a f , a f-1 {, ..., a1, a0} is a within the time interval f Subframes or slots are mapped in such a way that a is mapped to the first subframe or slot, and a0 is mapped to the last subframe or 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} are mapped to mini-slots within a frame or slot.

[0482] Alternative 2: The UE may be signaled with a time offset, start point, and duration to indicate time domain resources for the GO. The UE may be signaled with a slot / subframe offset of the GO. The time offset may relate to a slot / subframe carrying an active DCI. The UE may be signaled with a start index to indicate the start point of the GO, and the start index may be a symbol index within a slot or a mini-slot index. The UE may be signaled with the number of symbols or the number of mini-slots to indicate the duration of the GO. The aforementioned parameters may be signaled as separate fields, or some of the parameters may be signaled together. For example, a predefined table may contain combinations of start and duration of time domain resources, each having a combination associated with an index. The UE may be signaled with an index of the table to indicate the values ​​of the start and duration.

[0483] For groupcast sidelink transmission, a UE can transmit the same information in multiple directions. A UE can be signaled with a single time domain resource and can determine time domain resources for all directions by some predefined rules. Alternatively, a UE can be signaled with a time domain resource for each direction. For example, a UE can be represented by multiple start and duration values ​​of time domain resources. Or, a UE can be represented by gaps between time domain resources for transmission in the first direction and transmission in the remaining directions.

[0484] For groupcast sidelink transmission, the enabling DCI may signal time domain resources for PSCCH or PSSCH. Time domain resources for PSCCH and PSSCH may be signaled jointly, for example, a single time domain resource allocation may be used for both PSCCH and PSSCH. Alternatively, time domain resources for PSCCH and PSSCH may be signaled separately, and the enabling DCI may signal two time domain resources for PSCCH and PSSCH, respectively.

[0485] This is a repeat indicator field. To improve reliability, the UE can repeat groupcast sidelink transmissions. The UE can be signaled by the repeat number by the enable DCI. The UE can also be signaled by a pattern of RVs. For example, an RRC configuration can configure the UE with multiple candidate patterns of RVs, each having a pattern associated with a single index. The UE can be signaled by an index to indicate which pattern is used for the repeat. When the UE repeats the initial transmission, inter-slot or intra-slot repeats may be performed. The UE may use the same symbols or mini-slots in the following slots for the repeat. Alternatively, the UE may use symbols or mini-slots within the same slot for the repeat.

[0486] This is the HARQ process field. The UE can be signaled by the HARQ process number by the enable DCI.

[0487] This is a frequency domain resource allocation field. The frequency domain resource allocation field can carry frequency domain resource allocations for a GO. A UE can be signaled to adjacent frequency resources for a GO. Frequency resources can be signaled in RBs or subchannels, e.g., RGBs. Alternatively, a UE can be signaled by the index of the lowest RB and the number of allocated RBs, or a UE can be signaled by the index of the lowest RGB and the number of allocated RGBs. Alternatively, frequency resource allocations can be signaled by a bitmap. Each bit within the bitmap can represent one RB, one RGB, or one subchannel. A UE can be signaled by an index to represent the starting RB, RGB, or subchannel associated with the bitmap.

[0488] For groupcast sidelink transmission, the enabling DCI can signal frequency domain resources for both PSCCH and PSSCH. Frequency domain resources for PSCCH and PSSCH can be signaled jointly, for example, if PSCCH and PSSCH are TDMed and use the same number of RBs, one frequency domain resource allocation can be used for both PSCCH and PSSCH. Alternatively, frequency domain resources for PSCCH and PSSCH can be signaled separately, and the enabling DCI can signal two frequency domain resources for PSCCH and PSSCH, respectively.

[0489] This is a beam sweeping information field. For group cast sidelink transmission, the transmitter UE (202) can group cast information in multiple directions using multiple beams in the following alternatives:

[0490] Alternative 1: gNB(201) can determine the number of beam sweeps the UE needs to perform and signal this to the UE via the enable DCI. The UE k Assuming that information is signaled to group cast through the directions / beams, the UE can be signaled with a single BO for all beams. The beams used for beam sweeping can be configured by the gNB (201). Alternatively, the beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0491] Alternative 2: The number of beam sweeps can be determined by the UE. The UE can be signaled by an activating DCI into a single BO containing multiple symbols or mini-slots. The UE can autonomously utilize the signaled symbols and mini-slots within the BO for beam sweeping. The beams used for beam sweeping can be autonomously determined by the transmitter UE (202) based on sensing or discovery.

[0492] If part of the GO's information is represented by an active DCI, such as time domain resource allocation; frequency domain resource allocation, etc., the gNB (201) does not configure the same information in the RRC configuration.

[0493] A UE can be dynamically represented by an SFI. For a UE configured with a dedicated sidelink carrier, the UE can perform sidelink transmissions only for symbols labeled 'S'. Alternatively, the UE can perform sidelink transmissions for symbols labeled 'S' or 'U'. For a UE configured with a shared sidelink carrier between Uu and the sidelink, the UE can perform sidelink transmissions only for symbols labeled 'S'.

[0494] If there is a conflict between semi-permanently allocated GOs and DCI-signed SFIs, DCI may overwrite the allocation. The UE may skip the conflicting symbols and not perform sidelink transmissions for them. If a GO is allocated in a mini-slot and there is a conflict with some of the symbols within the mini-slot, the UE may skip the entire mini-slot and not perform sidelink transmissions for it. Alternatively, the UE may skip only the conflicting symbol(s) and perform sidelink transmissions for the non-conflicting symbol(s) within the mini-slot.

[0495] It is understood that entities (e.g., gNB, gNB-type node, or UE) performing the steps illustrated herein, such as those in FIG. 3, 4, 6, 7, and FIG. 10 through 20, may be logical entities. These steps may be stored in the memory of a device, server, or computer system, such as those illustrated in FIG. 9c or 9d, and executed on its processor. It is considered to skip steps, combine steps, or add steps between the exemplary methods disclosed herein (e.g., FIG. 3, 4, 6, and 7). Table 5 contains exemplary abbreviations and definitions as disclosed herein.

[0496] Table 5

[0497]

[0498]

[0499] FIG. 8 illustrates an exemplary display (e.g., a graphical user interface) that can be generated based on the methods, systems, and devices of Uu-based sidelink control for NR V2X as discussed herein. A display interface (901) (e.g., a touchscreen display) may provide text, such as RRC-related parameters, method flow, and RRC-associated current conditions, in a block (902) associated with Uu-based sidelink control for NR V2X. The progress of any step discussed herein (e.g., transmitting messages or success of steps) may be displayed in the block (902). In addition, a graphical output (902) may be displayed on the display interface (901). The graphical output may be a topology of devices implementing the methods, systems, and devices of Uu-based sidelink control for NR V2X, a graphical output of the progress of any method or system discussed herein, etc.

[0500] The 3rd Generation Partnership Project (3GPP) develops technical standards for cellular telecommunications network technologies, including radio access, core transport networks, and service capabilities—including work on codecs, security, and quality of service. Recent radio access technology (RAT) standards include WCDMA (commonly referred to as 3G), LTE (commonly referred to as 4G), LTE-Advanced standards, and New Radio (NR), also referred to as "5G." Development of 3GPP NR standards continues and is expected to include a definition of next-generation radio access technology (new RAT), which is expected to include the provision of new flexible radio access below 7 GHz and new ultra-mobile broadband radio access above 7 GHz. Flexible radio access is expected to consist of new non-backwards compatible radio access in the new spectrum below 6 GHz, which is expected to include different modes of operation that can be multiplexed together in the same spectrum to address a wide set of 3GPP NR use cases with diverging requirements. Ultra-mobile broadband is expected to include cmWave and mmWave spectrum to provide opportunities for ultra-mobile broadband access for, for example, indoor applications and hotspots. In particular, ultra-mobile broadband is expected to share a common design framework with flexible radio access below 7 GHz by utilizing cmWave and mmWave-specific design optimizations.

[0501] 3GPP has identified various use cases expected to be supported by NR, which result in extensive user experience requirements regarding data rates, latency, and mobility. These use cases include the following general categories: enhanced mobile broadband (eMBB) ultra-reliable low-latency communications (URLLC), massive machine type communications (mMTC), network operations (e.g., network slicing, routing, migration and interoperability, energy saving), and enhanced vehicle-to-everything (eV2X) communications, which may include any of Vehicle-to-Vehicle Communication (V2V), Vehicle-to-Infrastructure Communication (V2I), Vehicle-to-Network Communication (V2N), Vehicle-to-Pedestrian Communication (V2P), and vehicle communications with other entities. Specific services and applications in these categories include, for example, monitoring and sensor networks, device remote control, two-way remote control, personal cloud computing, video streaming, wireless cloud-based offices, first responder connectivity, vehicle erecall, disaster alerts, real-time games, multi-party video calls, autonomous driving, augmented reality, haptic internet, virtual reality, home automation, robotics, and aerial drones. All of these use cases and others are considered herein.

[0502] FIG. 9a illustrates an exemplary communication system (100) in which methods and apparatuses for Uu-based sidelink control for NR V2X, such as the systems and methods described and claimed herein, particularly those illustrated in FIG. 3, FIG. 4, FIG. 6, FIG. 7, and FIG. 10 through 20, may be utilized. The communication system (100) may include WTRUs (wireless transmit / receive units) (102a, 102b, 102c, 102d, 102e, 102f, or 102g) (which may be generally or collectively referred to as WTRU (102) or WTRUs (102). The communication system (100) may include a RAN (radio access network) (103 / 104 / 105 / 103b / 104b / 105b), a core network (106 / 107 / 109), a PSTN (public switched telephone network) (108), the Internet (110), other networks (112), and network services (113). Network services (113) may include, for example, a V2X server, V2X functions, a ProSe server, ProSe functions, IoT services, video streaming, or edge computing.

[0503] It will be understood that the concepts disclosed herein may be used with any number of WTRUs, base stations, networks, or network elements. Each of the WTRUs (102a, 102b, 102c, 102d, 102e, 102f, or 102g) may be any type of device or apparatus configured to operate or communicate in a wireless environment. Each WTRU (102a, 102b, 102c, 102d, 102e, 102f, or 102g) may be illustrated as a hand-held wireless communication device in FIG. 9a, 9b, 9c, 9d, 9e, or 9f, but for a wide range of use cases considered for 5G wireless communications, each WTRU may include any type of device or device configured to transmit or receive wireless signals, including, merely as an example, a user equipment (UE), a mobile station, a fixed or mobile subscriber unit, a pager, a cellular phone, a personal digital assistant (PDA), a smartphone, a laptop, a tablet, a netbook, a notebook computer, a personal computer, a wireless sensor, a consumer electronics device, a wearable device such as a smart watch or smart clothing, a medical or eHealth device, a robot, industrial equipment, a drone, a passenger car, a bus, a truck, a train, or an airplane, or a device to be implemented in such device or device. It is understood that it is possible.

[0504] The communication system (100) may also include a base station (114a) and a base station (114b). In the example of FIG. 9a, each base station (114a and 114b) is illustrated as a single element. In practice, the base stations (114a and 114b) may include any number of interconnected base stations or network elements. The base station (114a) may be any type of device configured to wirelessly interface with at least one of WTRUs (102a, 102b, 102c) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), network services (113), or other networks (112). Similarly, the base station (114b) may be any type of device configured to interface wired or wirelessly with at least one of Remote Radio Heads (RRHs) (118a, 118b), Transmission and Reception Points (TRPs) (119a, 119b) or RSUs (120a, 120b) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), other networks (112) or network services (113). RRHs (118a, 118b) may be any type of device configured to wirelessly interface with at least one of the WTRUs (102), for example, WTRU (102c), to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), network services (113), or other networks (112).

[0505] TRPs (119a, 119b) may be any type of device configured to wirelessly interface with at least one of WTRUs (102d) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), network services (113), or other networks (112). RSUs (120a and 120b) may be any type of device configured to wirelessly interface with at least one of WTRUs (102e or 102f) to facilitate access to one or more communication networks, such as a core network (106 / 107 / 109), the Internet (110), other networks (112), or network services (113). For example, base stations (114a, 114b) may be a Base Transceiver Station (BTS), Node-B, eNode B, Home Node B, Home eNode B, next-generation Node-B (gNode B), satellite, site controller, access point (AP), wireless router, etc.

[0506] A base station (114a) may be part of a RAN (103 / 104 / 105), which may also include other base stations or network elements (not shown), such as a Base Station Controller (BSC), a Radio Network Controller (RNC), relay nodes, etc. Similarly, a base station (114b) may be part of a RAN (103b / 104b / 105b), which may also include other base stations or network elements (not shown), such as a BSC, an RNC, relay nodes, etc. A base station (114a) may be configured to transmit or receive wireless signals within a specific geographical area that may be referred to as a cell (not shown). Similarly, a base station (114b) may be configured to transmit or receive wired or wireless signals within a specific geographical area that may be referred to as a cell (not shown) for methods, systems, and devices of Uu-based sidelink control for NR V2X as disclosed herein. Similarly, a base station (114b) may be configured to transmit or receive wired or wireless signals within a specific geographical area, which may be referred to as a cell (not shown). A cell may be further divided into cell sectors. For example, a cell associated with a base station (114a) may be divided into three sectors. Thus, in the example, the base station (114a) may include three transceivers, for example, one for each sector of the cell. In the example, the base station (114a) may utilize multiple-input multiple output (MIMO) technology and thus may utilize multiple transceivers for each sector of the cell.

[0507] Base stations (114a) can communicate with one or more of WTRUs (102a, 102b, 102c, or 102g) via an air interface (115 / 116 / 117) which may be any suitable radio communication link (e.g., RF (radio frequency), microwave, IR (infrared), UV (ultraviolet), visible light, cmWave, mmWave, etc.). The air interface (115 / 116 / 117) may be established using any suitable radio access technology (RAT).

[0508] Base stations (114b) may communicate with one or more of RRHs (118a, 118b), TRPs (119a, 119b), or RSUs (120a, 120b) via a wired or air interface (115b / 116b / 117b), which may be any suitable wired (e.g., cable, optical fiber, etc.) or wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115b / 116b / 117b) may be established using any suitable RAT.

[0509] RRHs (118a, 118b), TRPs (119a, 119b), or RSUs (120a, 120b) may communicate with one or more of WTRUs (102c, 102d, 102e, 102f) via an air interface (115c / 116c / 117c), which may be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115c / 116c / 117c) may be established using any suitable RAT.

[0510] WTRUs (102a, 102b, 102c, 102d, 102e, or 102f) can communicate with each other via an air interface (115d / 116d / 117d), such as a sidelink communication, which can be any suitable wireless communication link (e.g., RF, microwave, IR, UV, visible light, cmWave, mmWave, etc.). The air interface (115d / 116d / 117d) can be established using any suitable RAT.

[0511] The communication system (100) may be a multiple access system and may use one or more channel access methods such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, etc. For example, base stations (114a) and WTRUs (102a, 102b, 102c) in RAN (103 / 104 / 105), or RRHs (118a, 118b), TRPs (119a, 119b), and RSUs (120a, 120b) and WTRUs (102c, 102d, 102e, 102f) in RAN (103b / 104b / 105b) can implement radio technology such as UTRA (UMTS (Universal Mobile Telecommunications System) Terrestrial Radio Access), which can establish air interfaces (115 / 116 / 117 or 115c / 116c / 117c) respectively using WCDMA (wideband CDMA). WCDMA may include communication protocols such as HSPA (High-Speed ​​Packet Access) or HSPA+ (Evolved HSPA). HSPA may include HSDPA (High-Speed ​​Downlink Packet Access) or HSUPA (High-Speed ​​Uplink Packet Access).

[0512] In the example, the base station (114a) and WTRUs (102a, 102b, 102c), or RRHs (118a, 118b), TRPs (119a, 119b), or RSUs (120a, 120b) and WTRUs (102c, 102d) in the RAN (103b / 104b / 105b) can implement radio technology such as E-UTRA (Evolved UMTS Terrestrial Radio Access), which can establish air interfaces (115 / 116 / 117 or 115c / 116c / 117c) respectively using LTE (Long Term Evolution) or LTE-A (LTE-Advanced). In the future, the air interface (115 / 116 / 117 or 115c / 116c / 117c) may implement 3GPP NR technology. LTE and LTE-A technologies may include LTE D2D and V2X technologies and interfaces (such as sidelink communication). Similarly, 3GPP NR technology includes NR V2X technologies and interfaces (such as sidelink communication).

[0513] Base stations (114a) and WTRUs (102a, 102b, 102c, 102g) in RAN (103 / 104 / 105), or RRHs (118a, 118b), TRPs (119a, 119b) and / or RSUs (120a, 120b) and WTRUs (102c, 102d, 102e, 102f) in RAN (103b / 104b / 105b) are IEEE 802.16 (e.g., WiMAX (Worldwide Interoperability for Microwave Access)), CDMA2000, CDMA2000 1X, CDMA2000EV-DO, IS-2000 (Interim Standard 2000), IS-95 (Interim Standard 95), IS-856 (Interim Standard 856), Radio technologies such as GSM (Global System for Mobile communications), EDGE (Enhanced Data rates for GSM Evolution), and GERAN (GSM EDGE) can be implemented.

[0514] The base station (114c) in FIG. 9a may be, for example, a wireless router, a home Node B, a home eNode B, or an access point, and any suitable RAT may be used to facilitate wireless connectivity in a localized area such as a workplace, home, vehicle, train, aircraft, satellite, factory, campus, etc., to implement methods, systems, and devices of Uu-based sidelink control for NR V2X as disclosed herein. In example, the base station (114c) and WTRUs (102), for example, WTRU (102e), may implement radio technology such as IEEE 802.11 to establish a wireless local area network (WLAN). Similarly, the base station (114c) and WTRUs (102) may implement radio technology such as IEEE 802.15 to establish a wireless personal area network (WPAN). In another example, the base station (114c) and WTRUs (102), for example, the WTRU (102e), may use a cellular-based RAT (e.g., WCDMA, CDMA2000, GSM, LTE, LTE-A, NR, etc.) to establish a picocell or femtocell. As illustrated in FIG. 9a, the base station (114c) may have direct access to the Internet (110). Thus, the base station (114c) may not be required to access the Internet (110) through the core network (106 / 107 / 109).

[0515] A RAN (103 / 104 / 105) or a RAN (103b / 104b / 105b) may communicate with a core network (106 / 107 / 109), which may be any type of network configured to provide voice, data, messaging, authorization and authentication, applications, or VoIP (voice over internet protocol) services to one or more of WTRUs (102a, 102b, 102c, 102d). For example, the core network (106 / 107 / 109) may provide call control, billing services, mobile location-based services, prepaid calling, internet access, packet data network access, Ethernet access, video distribution, etc., or perform high-level security functions such as user authentication.

[0516] Although not illustrated in FIG. 9a, it will be understood that a RAN (103 / 104 / 105) or a RAN (103b / 104b / 105b) or a core network (106 / 107 / 109) may communicate directly or indirectly with other RANs using the same RAT or a different RAT as the RAN (103 / 104 / 105) or RAN (103b / 104b / 105b). For example, in addition to being connected to a RAN (103 / 104 / 105) or RAN (103b / 104b / 105b) capable of using E-UTRA radio technology, a core network (106 / 107 / 109) may also communicate with other RANs (not illustrated) using GSM or NR radio technology.

[0517] The core network (106 / 107 / 109) may also serve as a gateway for WTRUs (102a, 102b, 102c, 102d, 102e) to access the PSTN (108), the Internet (110), or other networks (112). The PSTN (108) may include circuit-switched telephone networks that provide plain old telephone service (POTS). The Internet (110) may include a global system of interconnected computer networks and devices that utilize common communication protocols such as the transmission control protocol (TCP), user datagram protocol (UDP), and Internet protocol (IP) in the TCP / IP Internet protocol set. The networks (112) may include wired or wireless communication networks owned or operated by other service providers. For example, networks (112) may include other core networks or any type of packet data network (e.g., IEEE 802.3 Ethernet network) connected to one or more RANs that can use the same RAT or a different RAT as RAN (103 / 104 / 105) or RAN (103b / 104b / 105b).

[0518] Some or all of the WTRUs (102a, 102b, 102c, 102d, 102e, 102f) in the communication system (100) may include multi-mode capabilities, for example, the WTRUs (102a, 102b, 102c, 102d, 102e, 102f) may include a plurality of transceivers for communicating with different wireless networks via different wireless links to implement methods, systems, and devices of Uu-based sidelink control for NR V2X as disclosed herein. For example, the WTRU (102g) illustrated in FIG. 9a may be configured to communicate with a base station (114a) capable of using cellular-based radio technology and to communicate with a base station (114c) capable of using IEEE 802 radio technology.

[0519] Although not illustrated in FIG. 9a, it will be understood that user equipment can make a wired connection to a gateway. The gateway may be a Residential Gateway (RG). The RG may provide access to the core network (106 / 107 / 109). It will be understood that many of the ideas contained herein are equally applicable to UEs and WTRUs that use wired connections to access the network. For example, the ideas applicable to wireless interfaces (115, 116, 117 and 115c / 116c / 117c) are equally applicable to wired connections.

[0520] FIG. 9b is a system diagram of an exemplary RAN (103) and a core network (106) capable of implementing methods, systems, and devices for Uu-based sidelink control for NR V2X as disclosed herein. As previously discussed, the RAN (103) may utilize UTRA radio technology to communicate with WTRUs (102a, 102b, 102c) via an air interface (115). The RAN (103) may also communicate with the core network (106). As illustrated in FIG. 9b, the RAN (103) may include Node-Bs (140a, 140b, 140c), each of which may include one or more transceivers for communicating with WTRUs (102a, 102b, 102c) via the air interface (115). Node-Bs (140a, 140b, 140c) may each be associated with a specific cell (not shown) within the RAN (103). The RAN (103) may also include RNCs (142a, 142b). It will be understood that the RAN (103) may include any number of Node-Bs and RNCs (Radio Network Controllers).

[0521] As illustrated in FIG. 9b, Node-Bs (140a, 140b) can communicate with RNC (142a). Additionally, Node-B (140c) can communicate with RNC (142b). Node-Bs (140a, 140b, 140c) can communicate with individual RNCs (142a, 142b) via an Iub interface. RNCs (142a, 142b) can communicate with each other via an Iur interface. Each of the RNCs (142a, 142b) can be configured to control individual Node-Bs (140a, 140b, 140c) connected to it. Additionally, each of the RNCs (142a, 142b) may be configured to perform or support other functions such as outer loop power control, load control, admission control, packet scheduling, handover control, macro-diversity, security functions, data encryption, etc.

[0522] The core network (106) illustrated in FIG. 9b may include a media gateway (MGW) (144), a mobile switching center (MSC) (146), a serving GPRS support node (SGSN) (148), or a gateway GPRS support node (GGSN) (150). Although each of the aforementioned elements is illustrated as part of the core network (106), it will be understood that any of these elements may be owned or operated by an entity other than the core network operator.

[0523] The RNC (142a) in the RAN (103) can be connected to the MSC (146) in the core network (106) via an IuCS interface. The MSC (146) can be connected to the MGW (144). The MSC (146) and the MGW (144) can provide the WTRUs (102a, 102b, 102c) with access to circuit-switched networks, such as the PSTN (108), to facilitate communication between the WTRUs (102a, 102b, 102c) and traditional land-line communication devices.

[0524] The RNC (142a) in the RAN (103) can also be connected to the SGSN (148) in the core network (106) via an IuPS interface. The SGSN (148) can be connected to the GGSN (150). The SGSN (148) and the GGSN (150) can provide the WTRUs (102a, 102b, 102c) with access to packet-switched networks, such as the Internet (110), to facilitate communication between the WTRUs (102a, 102b, 102c) and IP-enabled devices.

[0525] The core network (106) may also be connected to other networks (112) which may include other wired or wireless networks owned or operated by other service providers. [05...

Claims

Claim 1 As a device for performing wireless communication, a processor; and includes a memory coupled with the processor, wherein the memory includes stored executable instructions that, when executed by the processor, cause the processor to execute operations, the operations include: receiving a radio resource control (RRC) message from a base station—the RRC message includes an indication of a plurality of sidelink resource pools, an indication of a physical uplink control channel (PUCCH) resource for reporting sidelink hybrid automatic repeat request (HARQ) feedback information, and an indication of a sidelink radio network temporary identifier (SL-RNTI)—; obtaining scheduling downlink control information for a first transmission from the base station using the SL-RNTI—the scheduling downlink control information indicates an index of a sidelink resource pool among the plurality of sidelink resource pools to be used for the first transmission, the first transmission includes an initial transmission or a retransmission, and the scheduling downlink control information includes a field indicating timing information for transmitting HARQ feedback for the first transmission to the base station, the timing information is related to the time when the device receives the HARQ feedback from the receiving user equipment. -; based on the acquisition of the above-mentioned scheduling downlink control information, sending the first transmission to the receiving user equipment - the first transmission is transmitted via a sidelink -; based on sending the first transmission, receiving the HARQ feedback regarding the first transmission from the receiving user equipment - the HARQ feedback is received from the receiving user equipment via the sidelink -;A device comprising: transmitting the HARQ feedback to the base station—the HARQ feedback being transmitted to the base station via the Uu interface using the PUCCH resource indicated in the RRC message and according to the timing information indicated in the scheduling downlink control information; Claim 2 In paragraph 1, the device is a device that is a transmission user device. Claim 3 In claim 1, the device, wherein the scheduling downlink control information is used to schedule a physical sidelink control channel (PSCCH) or a physical sidelink shared channel (PSSCH). Claim 4 A device according to claim 1, wherein the scheduling downlink control information comprises separate fields for distinguishing scheduling for at least a combination of broadcast transmission, group cast transmission, or unicast transmission. Claim 5 A device according to claim 1, wherein the scheduling downlink control information obtained from the base station is scrambled using different radio network temporary identifiers for broadcast transmission, group cast transmission, or unicast transmission. Claim 6 A device according to claim 1, wherein the scheduling downlink control information comprises a first indication of a first feedback resource allocation scheduled on the sidelink to which the receiving user equipment transmits the feedback to the device, and a second indication of a second feedback resource allocation scheduled on the Uu interface to which the device transmits the feedback to the base station. Claim 7 A device according to claim 1, wherein the initial transmission and the retransmission are scheduled in the same slot as the feedback. Claim 8 As a method, the step of receiving a radio resource control (RRC) message from a base station, wherein the RRC message includes indications of a plurality of sidelink resource pools, indications of a physical uplink control channel (PUCCH) resource for reporting sidelink hybrid automatic repeat request (HARQ) feedback information, and indications of a sidelink radio network temporary identifier (SL-RNTI) -; the step of obtaining scheduling downlink control information for a first transmission from the base station using the SL-RNTI, wherein the scheduling downlink control information indicates an index of a sidelink resource pool among the plurality of sidelink resource pools to be used for the first transmission, and the first transmission includes an initial transmission or a retransmission, and the scheduling downlink control information includes a field indicating timing information for transmitting HARQ feedback for the first transmission to the base station, wherein the timing information relates to the time when the device receives the HARQ feedback from the receiving user equipment -; the step of sending the first transmission to the receiving user equipment based on the acquisition of the scheduling downlink control information, wherein the first transmission is transmitted over a sidelink. -; a step of receiving HARQ feedback for the first transmission from the receiving user equipment based on sending the first transmission - the HARQ feedback is received from the receiving user equipment via the side link -; and a step of transmitting the HARQ feedback to the base station - the HARQ feedback is transmitted to the base station via the Uu interface using the PUCCH resource indicated in the RRC message and according to the timing information indicated in the scheduling downlink control information - comprising. Claim 9 A method according to claim 8, wherein the scheduling downlink control information comprises separate fields for distinguishing scheduling for at least a combination of broadcast transmission, group cast transmission, or unicast transmission. Claim 10 A method according to claim 8, wherein the scheduling downlink control information is scrambled using different radio network temporary identifiers for broadcast transmission, group cast transmission, or unicast transmission. Claim 11 A method according to claim 8, wherein the scheduling downlink control information comprises a first indication of a first feedback resource allocation scheduled on the sidelink to which the receiving user equipment transmits the feedback, and a second indication of a second feedback resource allocation scheduled on the Uu interface to transmit the feedback to the base station. Claim 12 In claim 8, the method wherein the initial transmission and the retransmission are scheduled in the same slot as the feedback. Claim 13 A computer-readable storage medium storing computer-executable instructions, wherein, when executed by a computing device, the computer-executable instructions cause the computing device to perform operations, said operations include receiving a radio resource control (RRC) message from a base station—the RRC message includes an indication of a plurality of sidelink resource pools, an indication of a physical uplink control channel (PUCCH) resource for reporting sidelink hybrid automatic repeat request (HARQ) feedback information, and an indication of a sidelink radio network temporary identifier (SL-RNTI)—; obtaining scheduling downlink control information for a first transmission from the base station using the SL-RNTI—the scheduling downlink control information indicates an index of a sidelink resource pool among a plurality of sidelink resource pools to be used for the first transmission, said first transmission includes an initial transmission or a retransmission, said scheduling downlink control information includes a field indicating timing information for transmitting HARQ feedback for the first transmission to the base station, said timing information is the time at which the computing device receives the HARQ feedback from the receiving user equipment and A computer-readable storage medium comprising: receiving HARQ feedback for the first transmission from the receiving user equipment based on sending the first transmission; the HARQ feedback being received from the receiving user equipment via the sidelink; and transmitting the HARQ feedback to the base station; the HARQ feedback being transmitted to the base station via the Uu interface using the PUCCH resource indicated in the RRC message and according to the timing information indicated in the scheduling downlink control information. Claim 14 In paragraph 13, the computer-readable storage medium comprising separate fields for distinguishing scheduling for at least a combination of broadcast transmission, group cast transmission, or unicast transmission. Claim 15 A computer-readable storage medium according to claim 13, wherein the scheduling downlink control information obtained from the base station is scrambled using different radio network temporary identifiers for broadcast transmission, group cast transmission, or unicast transmission. Claim 16 A computer-readable storage medium according to claim 13, wherein the scheduling downlink control information comprises a first indication of a first feedback resource allocation scheduled on the sidelink to which the receiving user equipment transmits the feedback, and a second indication of a second feedback resource allocation scheduled on the Uu interface to which the feedback is transmitted to the base station. Claim 17 In paragraph 13, a computer-readable storage medium in which the initial transmission and the retransmission are scheduled in the same slot as the feedback.

Images