Scheduling sidelink resources for multiple unicast by a single downlink control information message

Abstract

The present disclosure provides systems, methods, and apparatus, including computer programs encoded on computer storage media, for wireless communications. In one aspect of the present disclosure, a method of wireless communication performed by a user equipment (UE) includes receiving, from a base station, a grant message indicating a set of sidelink resources. The method further includes transmitting a plurality of unicast messages via a plurality of subgroups of the set of sidelink resources.

Description

[0001] Cross-reference to related applications

[0002] This application claims the benefit of U.S. Patent Application No. 17 / 338,496, filed June 3, 2021, entitled “SCHEDULING SIDELINK RESOURCES FORMULTIPLE UNICASTS BY A SINGLE DOWNLINK CONTROL INFORMATION MESSAGE,” and U.S. Provisional Patent Application No. 63 / 045,526, filed June 29, 2020, entitled “SCHEDULING SIDELINK RESOURCES FOR MULTIPLE UNICASTS BY A SINGLE DOWNLINK CONTROL INFORMATION MESSAGE,” both of which are expressly incorporated herein by reference in their entirety. Technical Field

[0003] The various aspects of this disclosure generally relate to wireless communication systems, and more particularly to unicast scheduling side link resources.

[0004] introduction

[0005] Wireless communication networks are widely deployed to provide various communication services, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These wireless networks can be multiple-access networks capable of supporting multiple users by sharing available network resources. Typically, such multiple-access networks support communication for multiple users by sharing available network resources.

[0006] A wireless communication network may include several base stations or B-nodes capable of supporting communication between several user equipments (UEs). UEs may communicate with base stations via downlinks and uplinks. A downlink (or forward link) refers to the communication link from the base station to the UE, while an uplink (or reverse link) refers to the communication link from the UE to the base station.

[0007] The base station can transmit data and control information to the UE on the downlink and / or receive data and control information from the UE on the uplink. On the downlink, transmissions from the base station may encounter interference from neighboring base stations or other radio frequency (RF) transmitters. On the uplink, transmissions from the UE may encounter interference from uplink transmissions from other UEs communicating with neighboring base stations or from other RF transmitters. This interference can degrade the performance of both the downlink and uplink.

[0008] UEs can be used in various scenarios, such as in industrial environment control networks, where wireless links can, for example, reduce the time and cost required to reconfigure the control network on the factory floor. However, establishing and maintaining reliable wireless links between industrial controllers and one or more associated Industrial Internet of Things (IIoT) devices can be problematic. For example, these industrial controllers are typically located near machines, which can cause problems (e.g., shielding, electrical noise, etc.) in maintaining reliable and sufficient communication links with some of the many IIoT devices in the control network. Furthermore, the latency and reliability requirements of IIoT traffic can prove challenging to meet in wireless control network implementations. For example, latency and reliability requirements for Industrial Internet of Things (IIoT) traffic are very stringent (e.g., latency ≈ 1-2 ms and reliability ≈ 10). -5 -10 -6 Block Error Rate (BLER). Additionally, conventional wireless communication protocols require the base station to allocate resources to the transmitting (TX) device (such as a programmable logic controller (PLC) device) for sidelink communication. Sidelink communication can be unicast (to a single receiver), broadcast (to all UEs), or multicast (to a group of UEs). In IIoT, communication is often unicast messages. For each unicast message to be scheduled, the base station needs to send a separate control message, such as a downlink control information (DCI) message. Accordingly, to schedule multiple sidelink unicast resources for multiple unicast messages, multiple DCI control messages need to be sent to the TX device, which increases system overhead and traffic and reduces system efficiency.

[0009] Overview

[0010] The following outlines some aspects of this disclosure to provide a basic understanding of the techniques discussed. This overview is not an exhaustive summary of all conceived features of this disclosure, and is neither intended to identify all key or decisive elements of all aspects of this disclosure, nor to define the scope of any or all aspects of this disclosure. Its sole purpose is to provide, in an overview form, some concepts of one or more aspects of this disclosure as a prelude to the more detailed description that follows.

[0011] One innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication method performed by a user equipment (UE). The method includes receiving, from a base station, an authorization message indicating a sidelink resource set. The method further includes transmitting multiple unicast messages via multiple subgroups of the sidelink resource set.

[0012] Another innovative aspect of the subject matter described in this disclosure can be implemented in a UE. The UE includes at least one processor; and a memory coupled to the at least one processor and storing processor-readable instructions configured, when executed by the at least one processor, to: receive an approval message from a base station indicating a sidelink resource set. The at least one processor is further configured to: initiate the transmission of multiple unicast messages via multiple subgroups of the sidelink resource set.

[0013] Another innovative aspect of the subject matter described in this disclosure can be implemented in a device configured for wireless communication. The device includes means for receiving, from a base station, an authorization message indicating a set of sidelink resources. The device further includes means for transmitting multiple unicast messages via multiple subgroups of the sidelink resource set.

[0014] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transient computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: receiving an authorization message from a base station indicating a sidelink resource set; and initiating the transmission of multiple unicast messages via multiple subgroups of the sidelink resource set.

[0015] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication method performed by a UE. The method includes: determining a set of sidelink resources based on an approval message received from a base station. The method further includes: dividing the sidelink resource set into multiple subgroups; and transmitting multiple unicast messages via these subgroups.

[0016] Another innovative aspect of the subject matter described in this disclosure can be implemented in a UE. The UE includes at least one processor; and a memory coupled to the at least one processor and storing processor-readable instructions configured, when executed by the at least one processor, to determine a set of sidelink resources based on an approval message received from a base station. The at least one processor is further configured to divide the sidelink resource set into multiple subgroups; and to initiate the transmission of multiple unicast messages via these subgroups.

[0017] Another innovative aspect of the subject matter described in this disclosure can be implemented in a device configured for wireless communication. The device includes: means for determining a set of sidelink resources based on an permission message received from a base station. The device further includes: means for dividing the sidelink resource set into multiple subgroups; and means for transmitting multiple unicast messages via these subgroups.

[0018] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transient computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: determining a set of sidelink resources based on an approval message received from a base station; dividing the set of sidelink resources into multiple subgroups; and initiating the transmission of multiple unicast messages via these subgroups.

[0019] Another innovative aspect of the subject matter described in this disclosure can be implemented in a wireless communication method performed by a base station. The method includes: generating an authorization message configured to allocate a set of sidelink resources to a UE; and transmitting the authorization message to the UE for the UE to schedule unicast messages via different subgroups of the sidelink resource set.

[0020] Another innovative aspect of the subject matter described in this disclosure can be implemented in a base station. The base station includes at least one processor; and a memory coupled to the at least one processor and storing processor-readable instructions configured, when executed by the at least one processor, to: generate an approval message configured to allocate a set of sidelink resources to a UE. The at least one processor is further configured to: initiate the transmission of the approval message to the UE for the UE to schedule unicast messages via different subgroups of the sidelink resource set.

[0021] Another innovative aspect of the subject matter described in this disclosure can be implemented in a device configured for wireless communication. The device includes: means for generating an authorization message configured to allocate a set of sidelink resources to a UE; and means for transmitting the authorization message to the UE so that the UE can schedule unicast messages via different subgroups of the sidelink resource set.

[0022] Another innovative aspect of the subject matter described in this disclosure can be implemented in a non-transient computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations including: generating an authorization message configured to allocate a sidelink resource set to a UE; and initiating transmission of the authorization message to the UE for the UE to schedule unicast messages via different subgroups of the sidelink resource set.

[0023] Other aspects, features, and implementations of this disclosure will be apparent to those skilled in the art after reading the following description of specific example implementations of this disclosure in conjunction with the accompanying drawings. Although features of this disclosure may be described hereinafter with respect to certain implementations and drawings, all implementations of this disclosure may include one or more of the advantageous features described herein. In other words, although one or more implementations may be described having certain advantageous features, one or more such features may also be used according to various implementations of this disclosure described herein. Similarly, although example implementations may be described hereinafter as implementations of an apparatus, system, or method, such example implementations may be implemented in various apparatuses, systems, and methods. Brief description of the attached diagram

[0025] A further understanding of the nature and advantages of this disclosure can be obtained by referring to the following figures. In the figures, similar components or features may have the same reference numerals. Furthermore, components of the same type may be distinguished by a dash following the reference numeral and a second reference numeral used to differentiate between similar components. If only the first reference numeral is used in the description, the description may be applied to any of the similar components having the same first reference numeral regardless of the second reference numeral.

[0026] Figure 1 It is a block diagram illustrating the details of an example wireless communication system.

[0027] Figure 2 It is a block diagram that conceptually illustrates an example design for a base station and user equipment (UE).

[0028] Figure 3 This is a diagram illustrating the deterministic and periodic nature of Industrial Internet of Things (IIoT) traffic.

[0029] Figure 4 It is part of the wireless network that forms the industrial environmental control network.

[0030] Figure 5 It is a physical layer procedure flow for sidelink resource granting based on the Vehicle-to-Everything (V2X) interface Dynamic Grant (DG) / Configurable Grant (CG) Type 2 protocol.

[0031] Figure 6 This is a block diagram of an example wireless communication system that supports sidelink resource scheduling for unicast message transmission and reception, based on explanations from various aspects.

[0032] Figure 7 This is a flowchart illustrating an example process for sidelink resource scheduling for unicast message sending and receiving, based on explanations from various aspects.

[0033] Figure 8This is a flowchart illustrating an example process for sidelink resource scheduling for unicast message sending and receiving, based on explanations from various aspects.

[0034] Figure 9 This is a block diagram of an example UE that supports sidelink resource scheduling for unicast message transmission and reception, based on explanations from various aspects.

[0035] Figure 10 This is a flowchart illustrating an example process for sidelink resource scheduling for unicast message sending and receiving operations, based on explanations from various sources.

[0036] Figure 11 This is a block diagram of an example base station that supports sidelink resource scheduling for unicast message sending and receiving operations, based on explanations from various aspects.

[0037] Detailed description

[0038] Various aspects of this disclosure are described more fully below with reference to the accompanying drawings. However, this disclosure may be implemented in many different forms and is not to be construed as limited to any specific structure or function given throughout this disclosure. Rather, these aspects are provided so that this disclosure will be thorough and complete, and will fully convey the scope of this disclosure to those skilled in the art. Based on the teachings herein, those skilled in the art will appreciate that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, any number of aspects set forth herein may be used to implement an apparatus or method of practice. Furthermore, the scope of this disclosure is intended to cover such apparatus or methods practiced using additional structures, functionalities, or structures and functionalities that complement or supplement the various aspects of this disclosure set forth herein. Any aspect of this disclosure disclosed herein may be implemented by one or more elements of the claims.

[0039] This disclosure provides systems, apparatus, methods, and computer-readable media for supporting sidelink resource scheduling for unicast message transmission and reception operations. For example, sidelink resource scheduling for unicast message transmission and reception operations can be performed by a transmit (TX) user equipment (UE) based on an authorization message received from a base station (such as a gNB). To explain, the TX UE can receive an authorization message from the base station indicating a set of sidelink resources. In some implementations, the TX UE can be a programmable logic controller (PLC) device. The authorization message includes downlink control information (DCI) messages, such as a single DCI with DCI 3_0 format. In some implementations, the authorization message includes a dynamic authorization (DG) message or a configured authorization (CG) message. Based on the authorization message, the TX UE can determine a set of sidelink resources that can be subdivided into multiple subgroups for use in multiple unicast communications. For example, the TX UE can subdivide the sidelink resource set into multiple subgroups based on a receive (RX) UE buffer status report, channel state information of an RX UE channel, or a combination thereof. Resource allocation performed by the TX UE can be transparent to the base station, partially known to the base station, or instructed or controlled by the base station. The TX UE can also schedule multiple unicast messages and transmit them via subgroups (such as multiple subgroups of a sidelink resource set). For example, the TX UE can transmit a first unicast message of multiple unicast messages to a first receiving UE via a first subgroup of these subgroups, and a second unicast message of the same multiple unicast messages to a second receiving UE via a second subgroup of these subgroups.

[0040] In some implementations, the TX UE can generate a buffer state for each of one or more RX UEs. The TX UE can send one or more sidelink buffer state reports (BSRs) to the base station to request sidelink resources. For example, the TX UE can send a sidelink BSR for each RX UE. Additionally or alternatively, the TX UE can combine the buffer states of multiple RX UEs to generate a sidelink BSR and send sidelink BSRs for multiple RX UEs. The sidelink BSR can correspond to a resource request and enable the base station to allocate a resource set, determine the maximum number of subgroups, determine the number of subgroups of that resource set, or a combination thereof. The number of subgroups can be less than or equal to the maximum number of subgroups. For example, the number of subgroups can be a single subgroup. In some implementations, the base station can indicate the maximum number of subgroups, the number of subgroups, or a combination thereof in an authorization message, a radio resource control (RRC) message, or a combination thereof.

[0041] In some implementations, the TX UE can receive feedback, such as ACK / NACK, from the RX UE. Based on the received ACK / NACK, the TX UE can transmit a feedback message to the base station. The feedback message can be in response to an grant message. In some implementations, the feedback message can be used (e.g., by the base station) to determine additional resources requested by the TX UE. The feedback message can be a single feedback message (corresponding to multiple ACK / NACKs received by the TX UE) or multiple feedback messages (each corresponding to a different ACK / NACK). The feedback message can include ACK / NACK indicators, such as single-bit or multi-bit indicators. In some implementations, the feedback message includes an ACK / NACK indicator for each subgroup or for each subgroup out of a maximum number of subgroups. Additionally or alternatively, the feedback message can be configured to indicate the number of ACKs, the number of NACKs, or both, with respect to the number of subgroups. In some implementations, the ACK / NACK indicator includes multiple bits, and the value of the multiple bits indicates or corresponds to the amount of resources requested by the TX UE.

[0042] Specific implementations of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. In some aspects, this disclosure provides techniques for sidelink resource scheduling for unicast message transmission and reception operations. For example, a TX UE can receive a resource set from a base station and can partition and allocate portions of that resource set according to the needs of the TX UE. For example, the TX UE can use different portions to send unicast messages to different RX UEs. Accordingly, the techniques described herein enable a single grant message (such as a single DCI (e.g., a DCI with DCI 3_0 format)) to be used by the TX UE to schedule multiple unicast messages. By scheduling and transmitting multiple unicast messages in response to a single grant message, the amount of overhead messages is reduced compared to conventional techniques such as V2X messaging techniques.

[0043] This disclosure generally relates to providing or participating in sidelink resource scheduling for unicast message transmission and reception operations. In various implementations, the technologies and apparatus can be used in wireless communication networks such as Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single Carrier FDMA (SC-FDMA) networks, LTE networks, GSM networks, 5G or New Radio (NR) networks (sometimes referred to as "5G NR" networks, systems, or devices), and other communication networks. As described herein, the terms "network" and "system" can be used interchangeably.

[0044] CDMA networks enable radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. UTRA includes Wideband CDMA (W-CDMA) and Low Chip Rate (LCR). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards.

[0045] TDMA networks enable radio technologies such as the Global System for Mobile Communications (GSM). 3GPP defines the standard for the Radio Access Network (RAN) (also referred to as GERAN) for GSM EDGE (Enhanced Data Rate GSM Evolution). GERAN is the radio component of GSM or GSM EDGE, along with the network connecting base stations (e.g., Ater and Abis interfaces) to base station controllers (e.g., A interface). The radio access network represents the component of the GSM network through which telephone calls and packet data are routed from the Public Switched Telephone Network (PSTN) and the Internet to the subscriber's handset (also called the user terminal or user equipment (UE)) and from the subscriber's handset to the PSTN and the Internet. A mobile phone operator's network may include one or more GERANs, which may be coupled to the UTRAN in the case of UMTS / GSM networks. Additionally, the operator's network may include one or more LTE networks, or one or more other networks. Different network types may use different Radio Access Technologies (RATs) and Radio Access Networks (RANs).

[0046] OFDMA networks can implement radio technologies such as Evolved UTRA (E-UTRA), IEEE 802.11, IEEE 802.16, IEEE 802.20, and flash-OFDM. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long Term Evolution (LTE) is a UMTS version using E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents from an organization called the 3rd Generation Partnership Project (3GPP), while cdma2000 is described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). These various radio technologies and standards are known or under development. For example, 3GPP is a collaboration between various telecommunications association groups that aims to define globally applicable third-generation (3G) mobile phone specifications. 3GPP Long Term Evolution (LTE) is a 3GPP project aimed at improving the Universal Mobile Telecommunications System (UMTS) mobile phone standard. 3GPP defines specifications for next-generation mobile networks, mobile systems, and mobile devices. This disclosure may refer to LTE, 4G, 5G, or NR technologies to describe certain aspects; however, this description is not intended to be limited to any particular technology or application, and one or more aspects described with reference to one technology may be understood to be applicable to another technology. In fact, one or more aspects of this disclosure relate to shared access to radio spectrum between networks using different radio access technologies or radio air interfaces.

[0047] 5G networks envision a variety of deployments, spectrums, services, and devices that can be implemented using a unified OFDM-based air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage for: (1) ultra-high density (such as approximately 1 M nodes / km) 2 (1) A massive Internet of Things (IoT) with ultra-low complexity (e.g., approximately tens of bits per second), ultra-low energy consumption (e.g., approximately 10+ years of battery life), and deep coverage capable of reaching challenging locations; (2) A massive Internet of Things (IoT) with robust security (to protect sensitive personal, financial, or confidential information), ultra-high reliability (e.g., approximately 99.9999% reliability), ultra-low latency (e.g., approximately 1 millisecond (ms)), and mission-critical control for users with a wide range of mobility or lack of mobility; and (3) Enhanced mobile broadband, including extremely high capacity (e.g., approximately 10 Tbps / km). 2 Extreme data rates (such as multi-Gbps rates, 100+Mbps user experience rates), and deep insights with advanced discovery and optimization.

[0048] This enables 5G NR devices, networks, and systems to utilize optimized OFDM-based waveform characteristics. These characteristics can include: scalable parameter design and transmission time intervals (TTI); a shared, flexible framework for efficiently multiplexing services and features using dynamic, low-latency Time Division Duplex (TDD) / Frequency Division Duplex (FDD) designs; and advanced radio technologies such as massive MIMO, robust millimeter-wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of parameter design in 5G NR (and the scaling of subcarrier spacing) efficiently addresses the operation of diverse services across diverse spectrum and deployments. For example, in various outdoor and macro coverage deployments implemented with FDD or TDD below 3 GHz, subcarrier spacing can occur at 15 kHz over bandwidths such as 1, 5, 10, and 20 MHz. For other various outdoor and small-cell coverage deployments with TDD above 3 GHz, subcarrier spacing can occur at 30 kHz over an 80 / 100 MHz bandwidth. For various other indoor broadband implementations, by using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz over a 160 MHz bandwidth. Finally, for various deployments transmitting mmWave components under TDD at 28 GHz, the subcarrier spacing can occur at 120 kHz over a 500 MHz bandwidth.

[0049] 5G NR's scalable parameter design enables scalable TTIs to meet various latency and Quality of Service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. Efficient multiplexing of long and short TTIs allows transmissions to begin at symbol boundaries. 5G NR also envisions a self-contained integrated subframe design that incorporates uplink or downlink scheduling information, data, and acknowledgments within the same subframe. Self-contained integrated subframes support communication in unlicensed or contention-based shared spectrum, and support adaptive uplink or downlink that can be flexibly configured on a per-cell basis to dynamically switch between uplink and downlink to meet current traffic needs.

[0050] For clarity, aspects of the devices and technologies may be described below with reference to example 5G NR implementations or in a 5G-centric manner, and 5G terminology may be used in various sections of the following description as illustrative examples; however, this description is not intended to be limited to 5G applications.

[0051] Furthermore, it should be understood that in operation, wireless communication networks adapted according to the concepts herein can be operated using any combination of licensed or unlicensed spectrum, depending on load and availability. Accordingly, it will be apparent to those skilled in the art that the systems, apparatuses, and methods described herein can be applied to other communication systems and applications different from the specific examples provided.

[0052] Figure 1 This is a block diagram illustrating the details of an example wireless communication system. The wireless communication system may include a wireless network 100. For example, wireless network 100 may include a 5G wireless network. As those skilled in the art will appreciate, Figure 1 The components appearing in this network likely have corresponding parts in other network deployments (including, for example, cellular and non-cellular network deployments, such as device-to-device, peer-to-peer, or self-organizing network deployments, etc.).

[0053] Figure 1 The wireless network 100 described herein includes several base stations 105 and other network entities. Base stations can be stations that communicate with UEs and can be referred to as evolved B-nodes (eNBs), next-generation eNBs (gNBs), access points, etc. Each base station 105 can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to such a specific geographic coverage area of ​​a base station or a base station subsystem serving that coverage area, depending on the context in which the term is used. In the implementation of the wireless network 100 herein, base stations 105 can be associated with the same operator or different operators; for example, the wireless network 100 may include multiple operator wireless networks. Additionally, in the implementation of the wireless network 100 herein, base stations 105 can use one or more frequencies (such as licensed spectrum, unlicensed spectrum, or one or more bands of a combination thereof) from the same frequencies as adjacent cells to provide wireless communication. In some examples, an individual base station 105 or UE 115 can be operated by more than one network operating entity. In some other examples, each base station 105 and UE 115 can be operated by a single network operating entity.

[0054] Base stations can provide communication coverage for macrocells, small cells (such as picocells or femtocells), or other types of cells. Macrocells typically cover a relatively large geographic area (e.g., a radius of several kilometers) and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as picocells) typically cover a relatively small geographic area and allow unrestricted access by UEs with service subscriptions to a network provider. Small cells (such as femtocells) also typically cover a relatively small geographic area (such as a residential area) and, in addition to unrestricted access, allow restricted access by UEs associated with that femtocell (such as UEs in a Closed Subscriber Group (CSG), UEs of users in that residence, etc.). Base stations used for macrocells may be called macro base stations. Base stations for small cells may be called small cell base stations, pico base stations, femtocells, or home base stations. Figure 1 In the examples shown, base stations 105d and 105e are conventional macro base stations, while base stations 105a-105c are macro base stations enabled with one of 3D, full-dimensional (FD), or massive MIMO capabilities. Base stations 105a-105c utilize their higher-dimensional MIMO capabilities to increase coverage and capacity using 3D beamforming in both elevation and azimuth beamforming. Base station 105f is a small cell base station, which can be a home node or a portable access point. A base station can support one or more cells, such as two cells, three cells, four cells, etc.

[0055] Wireless network 100 can support synchronous or asynchronous operation. For synchronous operation, each base station can have similar frame timing, and transmissions from different base stations can be roughly aligned in time. For asynchronous operation, each base station can have different frame timing, and transmissions from different base stations can be misaligned in time. In some scenarios, the network can be implemented or configured to handle dynamic switching between synchronous and asynchronous operation.

[0056] UE 115 are distributed across the wireless network 100, and each UE may be stationary or mobile. It should be understood that although mobile devices are generally referred to as User Equipment (UE) in standards and specifications issued by 3GPP, such devices may be additionally or additionally referred to by those skilled in the art as mobile station (MS), subscriber station, mobile unit, subscriber unit, radio unit, remote unit, mobile device, radio device, wireless communication device, remote device, mobile subscriber station, access terminal (AT), mobile terminal, radio terminal, remote terminal, handheld device, terminal, user agent, mobile client, client, or any other suitable term. Within this document, a “mobile” device or UE need not be mobile and may be stationary. Some non-limiting examples of mobile devices may include implementations of one or more of the various UE 115, including mobile stations, cellular phones (mobile phones), smartphones, Session Initiation Protocol (SIP) phones, Wireless Local Loop (WLL) stations, laptops, personal computers (PCs), notebooks, netbooks, smartbooks, tablets, and personal digital assistants (PDAs). Mobile devices can also be “Internet of Things” (IoT) or “Internet of Everything” (IoE) devices, such as automobiles or other transportation vehicles, satellite radios, Global Positioning System (GPS) devices, logistics controllers, drones, multi-rotor aircraft, quadcopters, smart energy or security devices, solar panels or solar arrays, urban lighting, water supply or other infrastructure; industrial automation and enterprise equipment; consumer and wearable devices, such as glasses, wearable cameras, smartwatches, health or fitness trackers, mammalian implantable devices, posture tracking devices, medical devices, digital audio players (such as MP3 players), cameras, game consoles, etc.; and digital home or smart home devices, such as home audio, video and multimedia equipment, appliances, sensors, vending machines, smart lighting, home security systems, smart meters, etc. In one aspect, a UE can be a device that includes a Universal Integrated Circuit Card (UICC). In another aspect, a UE can be a device that does not include a UICC. In some aspects, a UE that does not include a UICC may be referred to as an IoE device. Figure 1 The UEs 115a-115d described in the text are examples of mobile smartphone-type devices accessing the wireless network 100. The UE can be a machine specifically configured for connected communications, including machine-type communication (MTC), enhanced MTC (eMTC), narrowband IoT (NB-IoT), etc. Figure 1 The UE 115e-115k described in the text is an example of various machines configured for accessing communications on a 5G network 100.

[0057] Mobile devices (such as UE 115) can communicate with any type of base station (whether macro base station, pico base station, femto base station, relay, etc.). Figure 1 In this context, a communication link (represented as a lightning bolt) indicates a radio transmission between the UE and a serving base station (a serving base station is a base station designated to serve the UE on a downlink or uplink), or a desired transmission between base stations, and a backhaul transmission between base stations. Backhaul communication between base stations of the wireless network 100 can occur using wired and / or wireless communication links.

[0058] In the operation of the 5G network 100, base stations 105a-105c use 3D beamforming and coordinated spatial technologies (such as Coordinated Multipoint (CoMP) or multi-connectivity) to serve UEs 115a and 115b. Macro base station 105d performs backhaul communication with base stations 105a-105c and small cell base station 105f. Macro base station 105d also transmits multicast services subscribed to and received by UEs 115c and 115d. Such multicast services may include mobile TV or streaming video, or may include other services for providing community information (such as weather emergencies or alerts, such as Amber Alerts or Grey Alerts).

[0059] Each implemented wireless network 100 supports mission-critical communication with highly reliable and redundant links for mission-critical equipment such as UE 115e, which is a drone. Redundant communication links with UE 115e include those from macro base stations 105d and 105e, and small cell base station 105f. Other machine-type devices (such as UE 115f (thermometer), UE 115g (smart meter), and UE 115h (wearable device)) can communicate directly with base stations (such as small cell base station 105f and macro base station 105e) via wireless network 100, or in a multi-hop configuration via wireless network 100 by communicating with another user equipment relaying its information to the network (e.g., UE 115f relaying temperature measurement information to smart meter UE 115g, which is then reported to the network via small cell base station 105f). 5G network 100 can provide additional network efficiency through dynamic low latency TDD or FDD communication (such as in vehicle-to-vehicle (V2V) mesh networks between UEs 115i-115k communicating with macro base station 105e).

[0060] Figure 2 This is a block diagram conceptually illustrating an example design for base station 105 and UE 115. Base station 105 and UE 115 can be... Figure 1 One of the base stations and one of the UEs. For restricted association scenarios (as mentioned above), base station 105 can be... Figure 1In the small cell base station 105f, UE 115 can be UE 115c or 115d operating within the service area of ​​base station 105f. To access small cell base station 105f, UE 115 will be included in the list of accessible UEs of small cell base station 105f. Additionally, base station 105 can be some other type of base station. Figure 2 As shown, base station 105 may be equipped with antennas 234a to 234t, and UE 115 may be equipped with antennas 252a to 252r for facilitating wireless communication.

[0061] At base station 105, transmitter processor 220 can receive data from data source 212 and control information from controller 240. The control information can be used for Physical Broadcast Channel (PBCH), Physical Control Format Indicator Channel (PCFICH), Physical Hybrid ARQ (Automatic Repeat Request) Indicator Channel (PHICH), Physical Downlink Control Channel (PDCCH), Enhanced Physical Downlink Control Channel (EPDCCH), or MTC Physical Downlink Control Channel (MPDCCH), etc. Data can be used for PDSCH, etc. Transmitter processor 220 can process (such as encoding and symbol mapping) data and control information to obtain data symbols and control symbols respectively. Additionally, transmitter processor 220 can generate reference symbols, such as reference symbols for primary synchronization signal (PSS) and secondary synchronization signal (SSS), and reference symbols that vary depending on the cell. The transmit (TX) multiple-input multiple-output (MIMO) processor 230 can perform spatial processing on data symbols, control symbols, or reference symbols where applicable, and can provide the output symbol stream to modulators (MODs) 232a to 232t. For example, the spatial processing performed on data symbols, control symbols, or reference symbols may include precoding. Each modulator 232 can process a corresponding output symbol stream (such as for OFDM) to obtain an output sample stream. Each modulator 232 can additionally or alternatively process the output sample stream to obtain a downlink signal. For example, to process the output sample stream, each modulator 232 can convert to analog, amplify, filter, and up-convert the output sample stream to obtain a downlink signal. The downlink signal from modulators 232a to 232t can be transmitted via antennas 234a to 234t, respectively.

[0062] At UE 115, antennas 252a to 252r can receive downlink signals from base station 105 and can respectively provide the received signals to demodulators (DEMODs) 254a to 254r. Each demodulator 254 can condition its own received signal to obtain an input sample. For example, to condition its own received signal, each demodulator 254 can filter, amplify, down-convert, and digitize its own received signal to obtain an input sample. Each demodulator 254 can further process the input sample (e.g., for OFDM) to obtain received symbols. MIMO detector 256 can obtain the received symbols from demodulators 254a to 254r, perform MIMO detection on these received symbols where applicable, and provide detected symbols. Receiver processor 258 can process these detected symbols, provide the decoded data for UE 115 to data sink 260, and provide the decoded control information to controller 280. For example, in order to process these detected symbols, the receiver processor 258 can demodulate, deinterleave, and decode these detected symbols.

[0063] On the uplink, at UE 115, transmit processor 264 can receive and process data from data source 262 (such as data for the Physical Uplink Shared Channel (PUSCH)) and control information from controller 280 (such as control information for the Physical Uplink Control Channel (PUCCH)). Additionally, transmit processor 264 can generate reference symbols for a reference signal. Symbols from transmit processor 264 can be pre-encoded by TX MIMO processor 266, further processed by modulators 254a to 254r (e.g., for SC-FDM), and transmitted to base station 105, where applicable. At base station 105, uplink signals from UE 115 can be received by antenna 234, processed by demodulator 232, detected by MIMO detector 236, and further processed by receive processor 238 to obtain decoded data and control information transmitted by UE 115. The receiver processor 238 can provide the decoded data to the data trap 239 and the decoded control information to the controller 240.

[0064] Controllers 240 and 280 can respectively direct operations at base station 105 and UE 115. Controller 240 or other processors and modules at base station 105, or controller 280 or other processors and modules at UE 115, can perform or direct the execution of various processes used in the techniques described herein, such as performing or directing... Figure 3-10 The execution of the techniques described herein, or other processes used in the techniques described herein. Memory 242 and 282 may store data and program code for base station 105 and UE 115, respectively. Scheduler 244 may schedule the UE for data transmission on the downlink or uplink.

[0065] In some scenarios, UE 115 and base station 105 may operate in a shared radio spectrum band, which may include licensed or unlicensed (e.g., contention-based) spectrum. In the unlicensed frequency portion of the shared radio spectrum band, UE 115 or base station 105 may conventionally perform media sensing procedures to contend for access to the spectrum. For example, UE 115 or base station 105 may perform Listen-Before-Speak or Listen-Before-Transmit (LBT) procedures (such as Open Channel Assessment (CCA)) before communication to determine if a shared channel is available. CCA may include energy detection procedures to determine if any other active transmissions exist. For example, the device may infer that a change in the Received Signal Strength Indicator (RSSI) of the power meter indicates that the channel is occupied. Specifically, signal power concentrated in a specific bandwidth and exceeding a predetermined noise floor may indicate another wireless transmitter. In some implementations, CCA may include the detection of a specific sequence indicating channel usage. For example, another device may transmit a specific preamble before transmitting a data sequence. In some cases, LBT procedures may include allowing a radio node to act as a collision-prone agent by adjusting its own backoff window based on the amount of energy detected on the channel or feedback on the acknowledgment or negation of packets it transmits (ACK or NACK).

[0066] In an example implementation of the wireless network 100, one or more of the UEs 115 may include various forms of Internet of Things (IoT) devices, such as Industrial Internet of Things (IIoT) devices, that communicate via the wireless link of the wireless network 100. For example, some deployed IIoT devices may include sensors (e.g., position sensors, temperature sensors, pressure sensors, power sensors, motion detectors, proximity detectors, accelerometers, scanners, cameras, probes, switches, etc.), actuators (e.g., linear actuators, rotary actuators, servo mechanisms, solenoids, stepper motors, motors, comb-driven actuators, etc.), or combinations thereof. A large number of IIoT devices may communicate with corresponding devices (e.g., industrial controllers (e.g., computers, programmable logic controllers (PLCs), supervisory control and data acquisition (SCADA) systems, etc.)) in an industrial environment (e.g., manufacturing facilities, material handling facilities, warehouses, etc.). For example, a PLC may communicate with 20-50 sensors and / or actuators, and 100-1000 such PLCs may be deployed throughout an industrial (e.g., manufacturing) facility.

[0067] Various IIoT devices in an industrial environment control network can periodically communicate information (e.g., measurements, status information, command confirmations, etc.) to or receive information (e.g., commands, parameters, settings, status information, etc.) from associated industrial controllers. For example, cyclical exchanges can be performed between industrial controllers and a large number of IIoT devices in the control network. Accordingly, IIoT traffic can be deterministic and periodic, such as... Figure 3 The diagram illustrates this.

[0068] The latency and reliability requirements for IIoT traffic are often stringent because the output must typically be generated within a finite timeframe in response to the input conditions to avoid unintended or even dangerous operations in industrial processes. For example, latency requirements for IIoT traffic can be on the order of 1-2 ms, and reliability requirements can be as high as 10^65. -5 -10 -6 The order of magnitude of the block error rate (BLER). Accordingly, both the data and control channels of industrial environment control networks can be designed to meet these overall requirements.

[0069] Control networks in industrial environments traditionally use wired communication links. For example, IIoT devices may use wired network links (such as 100 baseT Ethernet links) to communicate with corresponding industrial controllers. Such control networks can be quite complex in terms of establishing and maintaining network links, reconfiguring the network, etc. For example, reconfiguring a control network involves a large number of IIoT devices deployed on the factory floor, which can be costly in both time and money.

[0070] According to various aspects of this disclosure, one or more base stations are used in industrial environment control networks, such as to assist multi-hop communication links between corresponding IIoT devices of industrial controllers and / or control networks. For example, one or more base stations 105 of wireless network 100 may be ceiling-mounted or otherwise arranged (e.g., wall-mounted, mounted on top of marker poles or other structures, etc.) to provide a substantially unobstructed path to one or more industrial controllers, some or all of the IIoT devices of the control network. Figure 4 The example illustrates a portion of a wireless network 100 forming an industrial environment control network 400, wherein a base station 105f (e.g., a small cell base station) is arranged to assist communication links with multiple UEs (shown as UEs 115f, 115m, and 115n) of the control network.

[0071] although Figure 4The example described above is an industrial environment control network 400, in which base station 105f includes a small cell configuration, UE 115n includes a PLC configuration, UE 115f includes a thermometer sensor configuration, and UE 115m includes a robot actuator configuration. However, this example configuration is only to illustrate a control network to which the concepts of the present invention can be applied. It should be understood that the control network may include various configurations of dual base stations (e.g., macrocells, small cells, etc., or combinations thereof), industrial controllers UEs (e.g., computers, PLCs, SCADA, etc., or combinations thereof), and IIoT devices (e.g., position sensors, temperature sensors, pressure sensors, power sensors, motion detectors, proximity detectors, accelerometers, scanners, cameras, probes, switches, linear actuators, rotary actuators, servo mechanisms, solenoids, stepper motors, motors, comb-driven actuators, etc., or combinations thereof). Furthermore, although for simplicity, Figure 4 The examples illustrate a single instance of a base station, a single instance of an industrial controller, and two instances of IIoT devices, but the control environment in which the concepts of the present invention can be implemented may include any or all of the above in different numbers (e.g., multiple base stations, multiple industrial controllers, and tens, hundreds, or even thousands of IIoT devices).

[0072] exist Figure 4 In the example, UE 115n may include a PLC or other industrial controller that provides control functionality for multiple sensor and actuator IIoT devices (shown as UEs 115f and 115m, designated as sensor / actuator (S / A) 1 and S / A 2). UE 115n may communicate directly with base station 105f, such as using a UE-to-UMTS (Uu) interface. UE 115n (e.g., an industrial controller) may implement side links (i.e., direct communication links between UEs) with respect to UE 115f (e.g., a thermometer) and 115m (e.g., a robot actuator), such as using a UE-to-UE interface (e.g., a PC5 interface for a V2X mesh network). Multi-hop communication may be provided between UEs 115m and 115f and base station 105f via UE 115n. Base station 105f can additionally or alternatively establish direct communication links with some of the various IIoT devices in the control network (e.g., UE 115f, UE 115m, etc.), such as using the Uu interface.

[0073] Existing V2X interface protocols provide dynamic and configurable granting of sidelink resources (e.g., Physical Sidelink Control Channel (PSCCH) and / or Physical Sidelink Shared Channel) using the PC5 interface. A Dedicated Group (DG) can provide one-time granting of sidelink resources, such as in response to an instantaneous demand / need for sidelink communication. A Collector Group (CG) can provide granting of sidelink resources to enable continuous / periodic / repetitive sidelink communication. The first type of sidelink resource granting (Type 1) of the V2X interface protocol uses an Restricted Rate Control (RRC) to configure the UE with resources for a CG. The second type of sidelink resource granting (Type 2) of the V2X interface protocol uses a Dedicated Channel Control (DCI) on the PDCCH to configure the UE with resources for either a DG or a CG. For example, the DCI can be a DG, providing resource allocation for sidelink communication. Alternatively, the DCI can be a CG, activating / deactivating the CG for sidelink communication.

[0074] Figure 5 This section explains the physical layer procedure flow (procedure flow 500) for sidelink resource granting based on the V2X interface DG / CG Type 2 protocol mentioned above. It is described with reference to the V2X mesh network between UEs 115i and 115k communicating with macro base station 105e. Figure 5 The procedure flow 500, such as Figure 1 The wireless network 100 is shown. However, it should be understood that this procedure flow can be implemented with respect to various UEs and UE configurations.

[0075] exist Figure 5 In procedure flow 500, at procedure 501, base station 105a uses a DCI provided according to DCI format 3_0 and configured to correspond to UE 115k (e.g., sidelink TX UE) to deliver DG / CG type 2 to UE 115k. DCI format 3_0 provides fields for time slots, Hybrid Automatic Repeat Request (HARQ) procedure identifier, new data indicator, minimum index of subchannel allocation to initial transmission, Phase 1 Sidelink Control Information (SCI) format 0-1 fields (including frequency resource allocation and time resource allocation), Physical Sidelink Feedback Channel (PSFCH) to HARQ feedback timing indicator and PUCCH resource indicator, and configuration index in the CG case. In the case of DG, base station 105a prepares DCI using the sidelink-radio network temporary identifier (SL-RNTI) of UE 115, or in the case of CG, it prepares DCI using the sidelink-configured scheduled-radio network temporary identifier (SL-CS-RNTI) of UE 115k, to configure DCI to correspond to UE 115k. Specifically, the cyclic redundancy check (CRC) of DCI is scrambled by the SL-RNTI or SL-CS-RNTI of UE 115k to deliver DG / CG type 2 to the UE (e.g., sidelink TX UE).

[0076] In the case of CG, UE 115k (e.g., a sidelink TX UE) reports the activation (or deactivation) of the sidelink (not shown in procedure flow 500). Specifically, the activation / deactivation of the CG sidelink is reported via the Media Access Control-Control Element (MAC-CE). The MAC-CE report is also used by UE 115k to provide a sidelink buffer status report (BSR) to base station 105e. For example, UE 115k may have provided a BSR indicating that data for sidelink communication is included in the UE buffer, thereby causing sidelink resource granting to initiate procedure 501.

[0077] At procedure 502 of procedure flow 500, UE 115k (e.g., a sidelink TX UE) schedules the PSSCH using SCIs provided according to SCI format 0-1 (e.g., for scheduling the Physical Sidelink Shared Channel (PSSCH) and the second-stage SCI on the PSSCH) and SCI format 0-2 (e.g., for decoding the PSSCH), and transmits data to UE 115j (e.g., a sidelink receiver (RX) UE) via the PSSCH according to DG / CG type 2 (sidelink resource granting in procedure 501). SCI format 0-1 provides fields for priority, frequency resource allocation, time resource allocation, resource reservation period, demodulation reference signal (DMRS) mode, second-stage SCI format (broadcast, unicast, multicast), Beta_offset indicator, number of DMRS ports, modulation and coding scheme (MCS), and reserved fields. SCI format 0-2 provides fields for HARQ procedure identifier, new data indicator, redundancy version, source identifier, destination identifier, and channel state information (CSI) request. It also provides the field if the second-stage SCI format field in the corresponding SCI provided in SCI format 0-1 indicates the presence of a Type 1 multicast zone identifier and a communication range requirement field. MCS selection is performed by a sidelink TX UE (e.g., UE 115k in procedure flow 500) within the constraints set by the base station (e.g., base station 105e).

[0078] As can be seen from the above, the base station schedules node resources for the sidelink TX UE (Procedure 501), and the sidelink TX UE uses some or all of the scheduled resources to implement one or more sidelinks with the sidelink RX UE (Procedure 502). However, the base station does not control how the sidelink TX UE uses these resources or which UEs are selected by the sidelink TX UE as the sidelink RX UE. Existing V2X does not enable the base station to grant sidelink resource permission to the sidelink TX UE and schedule sidelink resources for a specific sidelink (e.g., a sidelink between the sidelink TX UE and a designated sidelink RX UE). Furthermore, existing V2X can provide a single permission for a single sidelink communication (such as a single sidelink unicast communication).

[0079] continue Figure 5 In procedure flow 500, in procedure 503, UE 115j (e.g., sidelink RX UE) provides sidelink feedback to UE 115k (e.g., sidelink TX UE). Specifically, UE 115j sends ACK / NACK on PSFCH upon receiving each transmission according to DG / CG type 2.

[0080] At procedure 504 of procedure flow 500, UE 115k (e.g., sidelink TX UE) forwards the sidelink feedback provided by UE 115j (e.g., sidelink RX UE) to base station 105e. Specifically, UE 115k forwards the ACK / NACK received from UE 115j to base station 105e on the PUCCH.

[0081] As referenced above Figure 3 The IIoT traffic exchanged between the industrial controller and its corresponding IIoT device is typically deterministic and periodic. As discussed above, low latency communication is desired for IIoT traffic. Accordingly, the V2X protocol for DG / CG implementing sidelink resources can be used for IIoT traffic between the IIoT device and its corresponding industrial controller in an attempt to achieve low latency communication. However, while the base station can utilize the V2X protocol to schedule resources for a first UE (e.g., a sidelink TX UE, such as UE 115k) to establish a sidelink with one or more other UEs (e.g., a sidelink RX UE, such as UE 115j), the base station needs to send separate control messages, such as downlink control information (DCI) messages. Consequently, to schedule multiple sidelink unicast resources for multiple unicast messages, multiple DCI control messages need to be sent to the TX device, which increases system overhead traffic and makes the system inefficient.

[0082] As described in this article, Figure 3The base station and TX UE can support sidelink resource scheduling for unicast message transmission and reception operations. For example, sidelink resource scheduling for unicast message transmission and reception operations can be performed by the TX UE based on a permission message received from the base station (such as a gNB). In some implementations, the TX UE can be a PLC device. The permission message includes DCI messages, such as a single DCI with DCI 3_0 format. In some implementations, the permission message includes DG messages or CG messages. Based on the permission message, the TX UE can determine a set of sidelink resources, which can be divided into multiple subgroups for multiple unicast communications. For example, the TX UE can divide the sidelink resource set into multiple subgroups based on RX UE buffer status reports, channel state information of the RX UE channel, or a combination thereof. The resource division performed by the TX UE can be transparent to the base station, partially known to the base station, or indicated or controlled by the base station. The TX UE can also schedule multiple unicast messages and transmit them via subgroups. For example, the TX UE can transmit the first unicast message of a plurality of unicast messages to the first receiving UE via the first subgroup of these subgroups, and transmit the second unicast message of the plurality of unicast messages to the second receiving UE via the second subgroup of these subgroups.

[0083] Specific implementations of the subject matter described herein can be implemented to achieve one or more of the following potential advantages. In some aspects, this disclosure provides techniques for sidelink resource scheduling for unicast message transmission and reception operations. For example, a TX UE can receive a resource set from a base station and can partition and allocate portions of that resource set according to the needs of the TX UE. For example, the TX UE can use different portions to send unicast messages to different RX UEs. Accordingly, the techniques described herein enable a single grant message (such as a single DCI (e.g., a DCI with DCI 3_0 format)) to be used by the TX UE to schedule multiple unicast messages. By scheduling and transmitting multiple unicast messages in response to a single grant message, the amount of overhead messages is reduced compared to conventional techniques such as V2X messaging techniques.

[0084] Figure 6This is a block diagram of an example wireless communication system 300 that supports scheduling sidelink resources for multiple unicast messages. In some examples, wireless communication system 300 may implement aspects of wireless network 100 or industrial environment control network 400. Wireless communication system 300 includes UE 115, base station 105, UE 360, and UE 370. Although three UEs and one base station are described, in some other implementations, wireless communication system 300 may generally include fewer than three UEs 115 and may include more than one base station. In some implementations, UE 115 may include or correspond to a TX UE, such as a PLC or PLC device. Additionally or alternatively, base station 105 may include or correspond to a gNB. Furthermore, UE 360 may include or correspond to a first RX UE, such as a first sensor / actuator (S / A) device, and UE 370 may include or correspond to a second RX UE, such as a second sensor / actuator (S / A) device.

[0085] UE 115 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 302 (hereinafter collectively referred to as “processor 302”), one or more memory devices 304 (hereinafter collectively referred to as “memory 304”), one or more transmitters 316 (hereinafter collectively referred to as “transmitter 316”), and one or more receivers 318 (hereinafter collectively referred to as “receiver 318”). Processor 302 may be configured to execute instructions stored in memory 304 to perform the operations described herein. In some implementations, processor 302 includes or corresponds to one or more of receive processor 258, transmit processor 264, and controller 280, and memory 304 includes or corresponds to memory 282.

[0086] In some implementations, memory 304 is configured to store side-link (SL) resource information 306 and buffer status report (BSR) information 308. UE 115 can generate and update SL resource information 306, channel surveillance information, ACK / NACK (A / N) information, or combinations thereof, based on permission messages received from base station 105. BSR information 308 can indicate BSR information corresponding to one or more RX UEs (such as UE 360, 370).

[0087] Transmitter 316 is configured to transmit reference signals, control information, and data to one or more other devices, and receiver 318 is configured to receive reference signals, synchronization signals, control information, and data from one or more other devices. For example, transmitter 316 may transmit signaling, control information, and data to base station 105, while receiver 318 may receive signaling, control information, and data from base station 105. In some implementations, transmitter 316 and receiver 318 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 316 or receiver 318 may include or correspond to reference signals. Figure 2 The described UE 115 includes one or more components. In some implementations, transmitter 316, receiver 318, or both may include or correspond to one or more interfaces. For example, the one or more interfaces may include a Uu interface configured to enable communication with base station 105 or a PC5 interface configured to enable communication with one or more UEs (such as UE 360, 370).

[0088] Base station 105 may include or correspond to a serving cell. Base station 105 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 352 (hereinafter collectively referred to as "processor 352"), one or more memory devices 354 (hereinafter collectively referred to as "memory 354"), one or more transmitters 356 (hereinafter collectively referred to as "transmitter 356"), and one or more receivers 358 (hereinafter collectively referred to as "receiver 358"). Processor 352 may be configured to execute instructions stored in memory 354 to perform the operations described herein. In some implementations, processor 352 includes or corresponds to one or more of receiver processor 238, transmitter processor 220, and controller 240, and memory 354 includes or corresponds to memory 242. In some implementations, memory 354 may store information such as SL resource information 306, BSR information 308, etc., or combinations thereof.

[0089] Transmitter 356 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 358 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 356 may transmit signaling, control information, and data to UE 115, while receiver 358 may receive signaling, control information, and data from UE 105. In some implementations, transmitter 356 and receiver 358 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 356 or receiver 358 may include or correspond to reference signals, synchronization signals, control information, and data. Figure 2The described base station 105 includes one or more components. In some implementations, transmitter 356, receiver 358, or both may include or correspond to one or more interfaces. For example, the one or more interfaces may include a Uu interface configured to enable communication with UE 115.

[0090] UE 360 may include or correspond to RX UE. UE 360 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 362 (hereinafter collectively referred to as "processor 362"), one or more memory devices 364 (hereinafter collectively referred to as "memory 364"), one or more transmitters 366 (hereinafter collectively referred to as "transmitter 366"), and one or more receivers 368 (hereinafter collectively referred to as "receiver 368"). Processor 362 may be configured to execute instructions stored in memory 364 to perform the operations described herein. In some implementations, processor 362 includes or corresponds to one or more of receive processor 258, transmit processor 264, and controller 280, and memory 364 includes or corresponds to memory 282.

[0091] Transmitter 366 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 368 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 366 may transmit signaling, control information, and data to UE 115, while receiver 368 may receive signaling, control information, and data from UE 105. In some implementations, transmitter 366 and receiver 368 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 366 or receiver 368 may include or correspond to reference signals, synchronization signals, control information, and data. Figure 2 The described UE 115 includes one or more components. In some implementations, transmitter 366, receiver 368, or both may include or correspond to one or more interfaces. For example, the one or more interfaces may include a Uu interface configured to enable communication with base station 105 or a PC5 interface configured to enable communication with one or more UEs (such as UE 115, 370).

[0092] UE 370 may include or correspond to RX UE. UE 370 may include various components (such as architecture, hardware components) for performing one or more of the functions described herein. For example, these components may include one or more processors 372 (hereinafter collectively referred to as "processor 372"), one or more memory devices 374 (hereinafter collectively referred to as "memory 374"), one or more transmitters 376 (hereinafter collectively referred to as "transmitter 376"), and one or more receivers 378 (hereinafter collectively referred to as "receiver 378"). Processor 372 may be configured to execute instructions stored in memory 374 to perform the operations described herein. In some implementations, processor 372 includes or corresponds to one or more of receive processor 258, transmit processor 264, and controller 280, and memory 374 includes or corresponds to memory 282.

[0093] Transmitter 376 is configured to transmit reference signals, synchronization signals, control information, and data to one or more other devices, and receiver 378 is configured to receive reference signals, control information, and data from one or more other devices. For example, transmitter 376 may transmit signaling, control information, and data to UE 115, while receiver 378 may receive signaling, control information, and data from UE 105. In some implementations, transmitter 376 and receiver 378 may be integrated into one or more transceivers. Additionally or alternatively, transmitter 376 or receiver 378 may include or correspond to reference signals, synchronization signals, control information, and data. Figure 2 The described UE 115 includes one or more components. In some implementations, transmitter 376, receiver 378, or both may include or correspond to one or more interfaces. For example, the one or more interfaces may include a Uu interface configured to enable communication with base station 105 or a PC5 interface configured to enable communication with one or more UEs (such as UE 115, 360).

[0094] In some implementations, the wireless communication system 300 implements a 5G New Radio (NR) network or a V2X network. For example, the wireless communication system 300 may include multiple 5G-capable UEs 115 and multiple 5G-capable base stations 105, such as UEs and base stations configured to operate according to 5G NR network protocols (such as those defined by 3GPP). Additionally, the wireless communication system 300 may include or implement aspects of a 4G network, a 3G network, a 2G network, or a combination thereof.

[0095] During operation of the wireless communication system 300, base station 105 (such as a gNB) sends an authorization message 386 to UE 115 (such as a PLC device). This authorization message includes a DCI message, such as a single DCI with DCI 3_0 format. In some implementations, the authorization message includes a DG message or a CG message. Based on the authorization message 386, UE 115 can determine a set of sidelink resources (such as sidelink resource information 306), which can be subdivided into multiple subgroups for use in multiple unicast communications. For example, UE 115 can subdivide the sidelink resource set into multiple subgroups based on BSR information 308. BSR information 308 may include or indicate an RX UE buffer status report, channel state information of an RX UE channel, or a combination thereof. The resource subdivision performed by UE 115 may be transparent to base station 105, partially known to base station 105, or indicated or controlled by base station 105.

[0096] UE 115 can schedule multiple unicast messages and transmit them via subgroups. For example, UE 115 can transmit the first message 390 of the multiple unicast messages to the first receiving UE 360 via the first subgroup. Additionally or alternatively, UE 115 can transmit the second message 392 of the multiple unicast messages to the second receiving UE 370 via the second subgroup.

[0097] In some implementations, UE 115 may receive feedback, such as ACK / NACK (A / N), from RX UE. For illustration, UE 115 may receive a first ACK / NACK message 394 from UE 360, a second ACK / NACK message from UE 370, or a combination thereof. Based on the received ACK / NACK messages, UE 115 may transmit a feedback message (such as A / N message 382) to base station 105. A / N message 382 may respond to an grant message 386. In some implementations, A / N message 382 may be used (e.g., by base station 105) to determine additional resources requested by UE 115. A / N message 382 may be a single feedback message (corresponding to multiple ACK / NACK messages received by UE 115) or multiple feedback messages (each feedback message corresponding to a different ACK / NACK message (394, 396)). A / N message 382 may include ACK / NACK indicators, such as one or more bits 383. The one or more bits 383 may include a single bit or multiple bits. In some implementations, the feedback message includes an ACK / NACK indicator for each subgroup or for each subgroup out of a maximum number of subgroups. Additionally or alternatively, the A / N message 382 may be configured to indicate the number of ACKs, the number of NACKs, or both, with respect to the number of subgroups. In some implementations, the ACK / NACK indicator includes multiple bits, and the value of these multiple bits indicates or corresponds to the amount of resources requested by UE 115.

[0098] In some implementations, UE 115 can generate a buffer state for each of one or more RX UEs. UE 115 can transmit one or more sidelink BSRs to base station 105 to request sidelink resources. For example, the UE can send a sidelink BSR for each RX UE. Additionally or alternatively, UE 115 can combine buffer states of multiple RX UEs to generate a sidelink BSR and send a sidelink BSR for multiple RX UEs. The sidelink BSR can correspond to a resource request and enable base station 105 to allocate a resource set, determine the maximum number of subgroups, determine the number of subgroups of the resource set, or a combination thereof. The number of subgroups can be less than or equal to the maximum number of subgroups. For example, the number of subgroups can be a single subgroup. In some implementations, base station 105 can indicate the maximum number of subgroups, the number of subgroups, or a combination thereof in an approval message 386, an RRC message 385, or a combination thereof.

[0099] In some implementations, base station 105 allocates a resource set to UE 115, and UE 115 partitions or splits the resource set into subgroups or channels according to its needs. Grant message 386 may be a single DCI, which is transmitted to UE 115 for UE 115 to schedule multiple unicast messages, such as multiple unicast messages for sidelink communication (e.g., sidelink communication to one or more sensor devices, actuator devices, or combinations thereof). In some implementations, grant message 386 may include a DCI 3_0 format and may grant a resource set.

[0100] In some implementations, resource splitting by UE 115 is transparent to base station 105. For example, base station 105 may be unaware that SL resources have been split by UE 115 and assume that UE 115 is using those resources to serve an RX UE. Base station 105 can grant SL resource sets to UE 115 using grant message 386 (such as DCI 3_0). To illustrate, base station 105 can grant resources via DCI 3_0 without knowing that UE 115 is splitting resources. UE 115 can then split the resources into smaller portions to serve multiple RX UEs, such as UEs 360 and 370.

[0101] UE 115 can perform BSR reporting by maintaining buffer states (such as BSR information 308) for each RX UE. When reporting a resource request to base station 105, UE 115 can combine the BSRs of multiple RX UEs into a combined SL BSR.

[0102] UE 115 can use PSCCH, PSSCH, or a combination thereof to allocate resources between its sidelinks and unicasts to its sidelinks. Resource allocation by UE 115 can be based on or per RX UE BSR, per RX UE channel, or a combination thereof. In some implementations, the allocation can be uneven or arbitrary. To illustrate, if UE 115 has two sidelinks and one channel has a better channel condition (and the other channel has a relatively worse channel condition), then UE 115 can allocate resources such that the majority of resources are allocated to the poor sidelink and less than the majority of resources are allocated to the good sidelink.

[0103] In some implementations, feedback reports (such as A / N message 382) may include a single bit, such as a single bit 838 (because the splitting is transparent to base station 105, so base station 105 expects only one bit). From the perspective of UE 115, each RX UE will report one A / N. UE 115 may use an OR operation on multiple received ACKs or multiple received NACKs to generate A / N message 382. In other words, if UE 115 receives a single NACK, UE 115 reports a NACK to base station 105 (indicating that at least one RX UE decoding failed) to request additional resources. In some implementations, feedback reports may include multi-bit A / N mechanisms, such as multi-bit 383.

[0104] In some implementations, UE 115 can use multiple bits for PUCCH reporting. For example, base station 105 can configure a variable number of bits (e.g., X) for the PUCCH, which can be used to request additional resources. The number of X bits can be any number of bits. The variable number of bits allows UE 115 to indicate more information than simply reporting A / N. UE 115 can determine the number of bits to be X and transmit it according to a format indicating a resource request (such as a resource request related to a previous resource allocation received from base station 105). As an illustrative and non-limiting example, if X = 2, the value "11" corresponds to reporting ACK, the value "00" corresponds to reporting NACK and requesting additional resources (e.g., 150% more resources), the value "01" requests the same resources, and the value "10" requests 50% more resources. As the number of bits X increases, the overhead may increase, but UE 115's resource requests may be more accurate and communication efficiency improved.

[0105] In some implementations, base station 105 is aware that resource partitioning is performed by UE 115. For example, base station 105 may know that UE 115 can partition the granted resources into N subgroups, where N is a positive integer, but may not know how many parts UE 115 divides each subgroup into, or how many subchannels exist in each part. The partitioning of the resource set into subgroups can be pre-configured or dynamically configured. To illustrate, base station 105 can inform UE 115 of the value of N. For example, base station 105 can provide N in RRC message 385. In some implementations, the value of N may also affect the feedback mechanism of UE 115, as further described herein. Base station 105 can use grant message 386 (such as DCI 3_0) to grant UE 115 an SL resource set partitioned into N. For example, base station 105 may pre-split the resources into groups of frequency bands, but UE 115 can partition each frequency band into smaller parts as needed. UE 115 is responsible for controlling the further splitting of different RX UEs into smaller parts.

[0106] In some implementations, for BSR reporting, the UE 115 maintains BSR information 308 for each RX UE (such as UE 360, 370), and reports multiple BSRs to the base station 105. The base station 105 combines the BSRs for resource allocation, assuming that the UE 115 will perform resource splitting. For illustration, the UE 115 may maintain BSR information 308 for each RX UE and report multiple BSRs to the base station 105, so that the base station 105 can combine the reports for resource allocation determination. In some implementations, the UE 115 maintains BSR information 308 for each RX UE, but combines the BSRs when reporting a resource request to generate a combined SL BSR. The base station 105 understands the combined BSR, and the UE 115 may further split the resources.

[0107] In some implementations, the base station 105 may configure the maximum number of subgroups into which a resource can be split to be equal to N, and the PUCCH will also include N bits. For illustration, each bit may correspond to a resource subgroup, and the A / N value of the PSFCH from the transmission may be assigned to that bit position. If any subgroup is not used by the UE 115 (e.g., the UE 115 only uses M of the N subgroups, where M < N), the UE 115 sets the corresponding bit(s) to indicate ACK. In another implementation, the N bits may be used to indicate the number of ACKs or NACKs in the total N. By providing the number of ACKs or NACKs - for example, by reporting a proportion of the total - the base station 105 can determine the additional amount of resources to be granted for retransmission. In some implementations, the N bits may be used by the UE 115 according to the format (as described above) indicating a resource request (such as a resource request related to a previous resource allocation received from the base station 105).

[0108] In some implementations, the resource splitting performed by the UE 115 may be controlled or directed by the base station 105. For illustration, the UE 115 may not be able to further split a resource into smaller subgroups. For example, the base station 105 may use a grant message 386 (such as DCI 3_0) to grant a SL resource set to the UE 115 and control how the resource is dynamically split into subgroups in the grant message 386 (e.g., DCI 3_0). The UE 115 is prohibited from further splitting the resources within each subgroup.

[0109] In some implementations, grant message 386 (such as DCI 3_0) may include a HARQ process ID field indicating the HARQ ID of the first subgroup. Remaining splits (e.g., remaining subgroups) can use a wrapper to increment the HARQ ID to determine the corresponding value. Regarding the wrapper, the first value could be "000", the value for the eighth subgroup would be "111", and based on the wrapper, the ninth subgroup would be "000".

[0110] In some implementations, the grant message 386 may indicate the number of splits, such as the number of subgroups. The number of splits may be less than or equal to the maximum number of splits (e.g., the maximum number of subgroups). The maximum number of subgroups may be a default value (such as a value set by a standard) or a dynamic value (such as a value set by UE 115 or base station 105). The maximum number of subgroups, the number of subgroups allocated, or both may be indicated in the grant message 386 or the RRC message 385, as explained by way of non-limiting example.

[0111] In some implementations, NDI control can be introduced for each of the subgroups, which allows for a hybrid NDI for each transmission. Alternatively, a shared NDI can be used for all subgroups. To illustrate NDI control, base station 105 can allocate resources and provide NDI control indications, such as those included in grant message 386 or RRC message 385, as illustrative rather than limiting examples. NDI control indications can be configured to force or cause UE 115 to transmit new packets / new messages. For example, NDI control indications can override existing scheduling mechanisms. If a shared NDI is used for multiple subgroups and base station 105 wants UE 115 to send a new message, then UE 115 discards all existing messages and sends the new message.

[0112] In some implementations, for BSR reporting, UE 115 maintains BSR information 308 for each RX UE and reports multiple BSRs to base station 105. The base station manages resources (e.g., for resource splitting) by taking into account the received BSRs.

[0113] In some implementations, UE 115 may perform feedback reporting, such as transmitting an A / N message 382 per split (e.g., per subgroup). UE 115 may provide feedback reporting using the same number of bits as the number of allocated subgroups or a different number of bits. When using the same number, UE 115 may map the PSFCH A / N to each of the bits. Base station 105 may be configured to determine feedback based on one or more bits and use the determined feedback for resource planning and NDI control.

[0114] In some implementations, UE 115 may receive an authorization message 386 indicating a sidelink resource set from base station 105. UE 115 may transmit multiple unicast messages via multiple subgroups of the sidelink resource set. For illustration, in some implementations, UE 115 may configure multiple subgroups of the sidelink resource set and may transmit multiple unicast messages via each of the multiple subgroups. Additionally or alternatively, UE 115 may determine the sidelink resource set based on the authorization message 386 and may divide the sidelink resource set into multiple subgroups.

[0115] For reference Figure 6 As described herein, this disclosure provides techniques for sidelink resource scheduling for unicast message transmission and reception operations. For example, UE 115 may receive a resource set from base station 105 and may partition and allocate portions of that resource set according to the needs of UE 115. For example, UE 115 may use different portions to send unicast messages to different RX UEs (such as UE 360, 370). Accordingly, the techniques described herein enable a single grant message (such as a single DCI (e.g., a DCI with DCI 3_0 format)) to be used by UE 115 to schedule multiple unicast messages. By scheduling and transmitting multiple unicast messages (such as messages 390, 392) in response to a single grant message (such as grant message 386), the overhead message volume is reduced compared to conventional techniques (such as V2X messaging techniques).

[0116] Figure 7 This is a flowchart of an example procedure 700 supporting sidelink resource scheduling for unicast message transmission and reception, based on explanations from various sources. The operation of procedure 700 can be performed by the UE, as described above. Figure 1 , 2 Or UE 115 as described in 6, refer to Figure 4 The UE 115n described, or refer to Figure 5 The UE 115k is described. For example, the example operation of procedure 700 (also referred to as the “box”) enables the UE to perform sidelink resource scheduling for unicast message reception and reception.

[0117] In block 702, the UE determines a sidelink resource set based on an authorization message received from the base station. In some implementations, the base station includes a gNB; the UE includes a programmable logic controller; or a combination thereof. The authorization message may include or correspond to authorization message 386. For example, the authorization message may be a single authorization message. The authorization message may include a DCI, such as a single DCI. The DCI may have a DCI 3_0 format. Additionally or alternatively, the authorization message may include a DG message or a CG message. The authorization message includes. The sidelink resource set may include or correspond to split information 387, SL resource information 306, or a combination thereof.

[0118] In box 704, the UE splits the sidelink resource set into multiple subgroups. The UE can split the sidelink resource set based on RX UE buffer state reports, channel state information of RX UE channels, or a combination thereof. In some implementations, after splitting the sidelink resource set, the UE can send multiple unicast messages to multiple RX UEs, such as... Figure 6 UE 360, 370.

[0119] In box 706, the UE transmits multiple unicast messages via these subgroups. The unicast messages may include or correspond to messages 390 and 392. For example, the UE may transmit a first unicast message of the multiple unicast messages to a first RX UE via a first subgroup of these subgroups, and a second unicast message of the multiple unicast messages to a second receiving UE via a second subgroup of these subgroups. X The first subgroup may include a different frequency band or channel than the second subgroup.

[0120] In some implementations, the UE may receive a first ACK / NACK message from a first RX UE in response to a first unicast message. Additionally or alternatively, the UE may receive a second ACK / NACK message from a second RX UE in response to a second unicast message. The first and second ACK / NACK messages may include or correspond to A / N messages 394 and 396.

[0121] In some implementations, the UE can generate a feedback message. The UE can transmit the feedback message to the base station. For example, the feedback message may include or correspond to ACK / NACK message 382. For example, the feedback message indicates the number of ACKs, the number of NACKs, or both regarding the number of subgroups. The feedback message may respond to an approval message and may be a single feedback message or a combination thereof. Additionally or alternatively, the feedback message may include several ACK / NACK indicators, such as one or more ACK / NACK indicators. ACK / NACK indicators may include single bits or multiple bits. One or more ACK / NACK indicators may include or correspond to bit 383. The feedback message may include ACK / NACK indicators for each subgroup. In some implementations, the feedback message includes ACK / NACK indicators for each subgroup in a maximum number of subgroups.

[0122] In some implementations, the feedback message includes an ACK / NACK indicator with multiple bits. The UE can request a certain amount of resources from the base station and determine the value of the multiple bits based on that amount.

[0123] In some implementations, the UE determines the maximum number of subgroups into which the resource set can be divided. For example, the UE may receive an RRC message indicating the maximum number of subgroups. Accordingly, the UE may determine the maximum number of subgroups based on the RRC message. The RRC message may include or correspond to RRC message 385. Additionally or alternatively, the UE may determine the number of subgroups into which the resource set is divided. The number of subgroups is less than or equal to the maximum number of subgroups. In some implementations, the number of subgroups is equal to one.

[0124] In some implementations, the UE can generate or maintain a buffer state for each of one or more RX UEs. The buffer state may include or correspond to BSR information 308. The UE can transmit a sidelink BSR to the base station to request sidelink resources. The sidelink BSR can be generated based on BSR information 308. In some implementations, the UE can combine the buffer states of multiple RX UEs to generate a sidelink BSR.

[0125] In some implementations, the UE can determine the HARQ ID of the first subgroup of the sidelink resource set based on the HARQ procedure ID field of the grant message. For example, the grant message indicates the number of one or more subgroups of the sidelink resource set. The number of one or more subgroups may be included in or indicated by the splitting information 387. The UE can determine the number of one or more subgroups of the sidelink resource set. The number of one or more subgroups of the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be split. Additionally or alternatively, the UE can identify the NDI control of the grant message. The NDI control can be applied to multiple subgroups. In some implementations, each subgroup is associated with the NDI control of the grant message.

[0126] thus, Figure 7 This paper describes techniques and potential advantages for sidelink resource scheduling for unicast message transmission. For example, the UE can receive a resource set from the base station and can partition and allocate portions of that resource set according to the UE's needs. For instance, the UE can use different portions to send unicast messages to different RX UEs. Accordingly, the techniques described herein enable a single grant message (such as a single DCI (e.g., a DCI with DCI 3_0 format)) to be used by the UE to schedule multiple unicast messages. By scheduling and transmitting multiple unicast messages in response to a single grant message, the overhead message volume is reduced compared to conventional techniques such as V2X messaging techniques.

[0127] Figure 8 This is a flowchart of an example procedure 800 supporting sidelink resource scheduling for unicast message transmission and reception, based on explanations from various aspects. The operation of procedure 800 can be performed by the UE, as described above. Figure 1 , 2Or UE 115 as described in 6, refer to Figure 4 The UE 115n described, or refer to Figure 5 The UE 115k is described. For example, the example operation of procedure 800 (also referred to as the “box”) enables the UE to perform sidelink resource scheduling for unicast message reception and reception.

[0128] In block 802, the UE receives an authorization message from a base station indicating a sidelink resource set. The base station may include or correspond to base station 105. The authorization message may include or correspond to authorization message 386. For example, the authorization message may be a single authorization message. The authorization message may include a DCI, such as a single DCI. The DCI may have a DCI 3_0 format. Additionally or alternatively, the authorization message may include a DG message or a CG message. The authorization message includes... The sidelink resource set may include or correspond to split information 387, SL resource information 306, or a combination thereof.

[0129] In block 804, the UE transmits multiple unicast messages via multiple subgroups of the sidelink resource set. Alternatively, to transmit multiple unicast messages, the UE may transmit multiple unicast messages via each of the multiple subgroups. In some implementations, the UE may send multiple unicast messages to multiple RX UEs, such as... Figure 6 UE 360, 370.

[0130] In some implementations, the UE can configure multiple subgroups of the sidelink resource set. Alternatively or additionally, the UE can determine the sidelink resource set based on an approval message and split the sidelink resource set into multiple subgroups.

[0131] Figure 9 This is a block diagram of an example UE900 that supports sidelink resource scheduling for unicast message transmission, based on explanations from various aspects. The UE900 can be configured to perform operations (including referencing...) Figure 7 and 8 The described process (either 700 or 800) is used to perform sidelink resource scheduling for unicast message transmission and reception. In some implementations, UE 900 includes references... Figure 1 , 2 Or UE 115 of 6 Figure 4 UE 115n, or Figure 5The UE 115k shows and describes the structure, hardware, and components. For example, UE 900 includes a controller 280 that operates to execute logical or computer instructions stored in memory 282, and various components that control UE 900 and provide the features and functionality of UE 900. Under the control of controller 280, UE 900 transmits and receives signals via wireless radio 901a-r and antenna 252a-r. Wireless radio 901a-r includes various components and hardware, such as those shown in… Figure 2 The components described in section UE 115 include modulators and demodulators 254a-r, MIMO detector 256, receiver processor 258, transmitter processor 264, and TX MIMO processor 266. In some implementations, the wireless radio 901a-r may include or correspond to one or more interfaces, such as a Uu interface, a PC5 interface, or a combination thereof.

[0132] As shown, memory 282 may include SL resource information 902 and BSR information 903. SL resource information 902 and BSR information 903 may respectively include or correspond to SL resource information 306 and BSR information 308. UE 900 may receive signals from or transmit signals to one or more network entities, such as... Figure 1 , 2 Or 6 base stations 105, Figure 4 Base station 105f, Figure 5 Base station 105e, Figure 1 , 2 Or UE 115 of 6 Figure 4 UE 115f, 115m, 115n Figure 5 UE 115k, 115j, Figure 6 UE 360, 370, or Figure 10 The base station explained in the text.

[0133] Figure 10 This is a flowchart of an example process 1000 supporting sidelink resource scheduling for unicast message transmission and reception, based on explanations from various aspects. The operations of process 1000 can be performed by the base station, such as... Figure 1 , 2 Or 6 base stations 105, Figure 4 Base station 105f, Figure 5 Base station 105e. For example, the example operation of procedure 1000 (also referred to as the “box”) can enable the base station to perform sidelink resource scheduling for unicast message transmission and reception.

[0134] In block 1002, the base station generates an authorization message configured to allocate a set of sidelink resources to the UE. In some implementations, the base station includes a gNB, the UE includes a programmable logic controller, or a combination thereof. The authorization message may include or correspond to authorization message 386. The authorization message may be a single authorization message. Additionally or alternatively, the authorization message may include a DCI, such as a single DCI—for example, a DCI 3_0 format. In some implementations, the authorization message includes a DG message or a CG message. The set of sidelink resources may include splitting information 387 or be indicated by splitting information 387.

[0135] In box 1004, the base station transmits the permission message to the UE to allow the UE to schedule unicast messages via different subgroups of the sidelink resource set. The UE may include or correspond to Figure 6 UE 115.

[0136] In some implementations, the base station may be unaware of the sidelink resource splitting implemented by the UE. The base station can receive feedback messages from the UE. Feedback messages may include or correspond to ACK / NACK messages 382. Feedback messages may respond to grant messages and may be a single feedback message or a combination thereof. Additionally or alternatively, feedback messages may include ACK / NACK indicators. ACK / NACK indicators may include or correspond to one or more bits 383, such as single bits or multiple bits. In some implementations, when the ACK / NACK indicator includes multiple bits, the base station can determine the value of the multiple bits and determine the amount of resources requested by the UE based on that value.

[0137] In some implementations, the base station is partially aware of the sidelink resource splitting implemented by the UE. The sidelink resource set includes one or more subgroups, and the base station may receive one or more feedback messages from the UE in response to an grant message. Additionally or alternatively, the base station may transmit an RRC message to the UE. An RRC may include or correspond to an RRC message 385. The RRC message may indicate the number of subgroups into which the sidelink resource set can be split. In some implementations, the base station may receive feedback messages from the UE, such as an ACK / NACK message 382. The feedback message may include several ACK / NACK indicators. For example, the feedback message may include an ACK / NACK indicator for each subgroup. Additionally or alternatively, the feedback message may indicate the number of ACKs, the number of NACKs, or both, with respect to the number of subgroups. In some implementations, the ACK / NACK indicator includes multiple bits, and the base station may determine the amount of resources requested by the UE based on the value of these multiple bits.

[0138] In some implementations, the partitioning of sidelink resources for the sidelink resource set is controlled by the base station. For example, the HARQ procedure ID field of the grant message may indicate the HARQ ID of the first subgroup of the sidelink resource set. Additionally or alternatively, the grant message may indicate the number of one or more subgroups of the sidelink resource set. The number of one or more subgroups of the sidelink resource set may be less than or equal to the maximum number of subgroups into which the sidelink resource set can be partitioned. In some implementations, the base station may transmit an RRC message to the UE. The RRC message (such as RRC message 385) may indicate the maximum number of subgroups. In some implementations, NDI control of the grant message (such as a single NDI control) may be used for multiple subgroups. Alternatively, NDI control of the grant message may be used for a single subgroup. In some implementations, the base station receives a feedback message from the UE, such as an ACK / NACK message 382. The feedback message may include several ACK / NACK indicators, such as one or more ACK / NACK indicators. For example, the feedback message may include an ACK / NACK indicator for each subgroup.

[0139] thus, Figure 10 This paper describes techniques and potential advantages for sidelink resource scheduling for unicast message transmission. For example, a base station can send an authorization message indicating a resource set (such as sidelink resources available for a UE to use for sidelink communication (such as unicast messages)). The authorization message allows the UE to split and allocate portions of the resource set according to its needs. For example, a TX UE can use different portions to send unicast messages to different RX UEs. Accordingly, the techniques described herein allow a single authorization message (such as a single DCI (e.g., a DCI with DCI 3_0 format)) to be used by the UE to schedule multiple unicast messages. By scheduling and transmitting multiple unicast messages in response to a single authorization message, the amount of overhead messages is reduced compared to conventional techniques (such as V2X messaging techniques).

[0140] Figure 11 This is a block diagram of an example base station 1100 that supports sidelink resource scheduling for unicast message transmission and reception, based on explanations from various aspects. In some implementations, base station 1100 includes references... Figure 1 , 2 Or 6 base stations 105, Figure 4 Base station 105f, Figure 5The base station 105e shows and describes its structure, hardware, and components. For example, base station 1100 may include a controller 240 that operates to execute logical or computer instructions stored in memory 242, and various components that control base station 1100 and provide the characteristics and functionality of base station 1100. Base station 1100 transmits and receives signals via wireless radio 1101a-t and antenna 234a-t under the control of controller 240. Wireless radio 1101a-t includes various components and hardware (such as those in…). Figure 2 (As explained in the text regarding base station 105), it includes modulators and demodulators 232a-t, a transmit processor 220, a TX MIMO processor 230, a MIMO detector 236, and a receive processor 238. In some implementations, the wireless radio 1101a-t may include or correspond to one or more interfaces, such as a Uu interface.

[0141] As shown, memory 242 may include SL resource information 1102 and BSR information 1103. SL resource information 1102 and BSR information 1103 may respectively include or correspond to SL resource information 306 and BSR information 308. Base station 1100 may receive signals from or transmit signals to one or more UEs, such as... Figure 1 , 2 Or UE 115 of 6 Figure 4 UE 115f, 115m, 115n Figure 5 UE115k, 115j, Figure 6 UE 360, 370.

[0142] Note that, refer to Figure 7 , 8 One or more boxes (or operations) described in or 10 may be combined with one or more boxes (or operations) described with reference to another figure. For example, Figure 7 One or more boxes (or operations) can be combined with Figure 10 A combination of one or more boxes (or actions). As another example, with... Figure 7 One or more associated boxes can be combined with Figure 8 A combination of one or more associated boxes (or actions). As another example, with... Figure 7 Or 8 associated with one or more boxes can be and with Figure 2 , 4 A combination of one or more boxes (or operations) associated with 5 or 6. As another example, with... Figure 10 One or more associated boxes can be combined with Figure 2 , 4 A combination of one or more boxes (or operations) associated with 5 or 6. Additionally or alternatively, refer to the above. Figure 1-11One or more operations described can be compared with the reference Figure 1-11 The other describes one or more combinations of operations.

[0143] In some aspects, techniques for implementing sidelink resource scheduling for unicast message transmission may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes or apparatuses described elsewhere herein. In a first aspect, performing sidelink resource scheduling for unicast message transmission may include: an apparatus configured to determine a set of sidelink resources based on permission messages received from a base station. The apparatus may also be configured to: divide the set of sidelink resources into multiple subgroups; and transmit multiple unicast messages via these subgroups. In some examples, the techniques of the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a UE or a component of a UE). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, configured, when executed by the processing unit, to cause the wireless communication device to perform the operations described herein.

[0144] In a second aspect, in conjunction with the first aspect, the sidelink resource set is split based on RX UE buffer status reports, RX UE channel channel state information, or a combination thereof.

[0145] In a third aspect, in conjunction with the first or second aspect, the device is configured to schedule multiple unicast messages.

[0146] In a fourth aspect, in conjunction with the third aspect, in order to transmit multiple unicast messages, the apparatus is further configured to transmit a first unicast message of the multiple unicast messages to a first receiving UE via a first subgroup of these subgroups, and in order to transmit multiple unicast messages, the apparatus is further configured to transmit a second unicast message of the multiple unicast messages to a second receiving UE via a second subgroup of these subgroups.

[0147] In a fifth aspect, in conjunction with one or more of the first to fourth aspects, the device is configured to receive a first ACK / NACK message from the first RX UE in response to a first unicast message.

[0148] In a sixth aspect, in conjunction with the fifth aspect, the device is configured to receive a second ACK / NACK message from the second RX UE in response to the second unicast message.

[0149] In the seventh aspect, in conjunction with one or more of the first to sixth aspects, the device is configured to generate a buffer state for each of one or more RX UEs.

[0150] In the eighth aspect, in conjunction with the seventh aspect, the device is configured to transmit a sidelink BSR to the base station to request sidelink resources.

[0151] In the ninth aspect, in conjunction with one or more of the first to eighth aspects, the device is configured to combine the buffer states of multiple RX UEs to generate a sidelink BSR.

[0152] In the tenth aspect, in conjunction with one or more of the first to ninth aspects, the device is configured to transmit a feedback message to the base station.

[0153] In the eleventh aspect, in conjunction with the tenth aspect, the feedback message responds to the grant message; the feedback message is a single feedback message; or a combination thereof.

[0154] In the twelfth aspect, in conjunction with one or more of the tenth or eleventh aspects, the feedback message includes an ACK / NACK indicator.

[0155] In the thirteenth aspect, in conjunction with the twelfth aspect, the ACK / NACK indicator is a single bit.

[0156] In the fourteenth aspect, in conjunction with the twelfth aspect, the ACK / NACK indicator includes multiple bits.

[0157] In the fifteenth aspect, in conjunction with the fourteenth aspect, the device is configured to determine the amount of resources to be requested from the base station.

[0158] In the sixteenth aspect, in conjunction with the fifteenth aspect, the device is configured to determine the value of the multi-bit based on the quantity.

[0159] In the seventeenth aspect, in conjunction with one or more of the first to sixteenth aspects, the device is configured to determine the maximum number of subgroups into which the resource collection can be divided.

[0160] In the eighteenth aspect, in conjunction with the seventeenth aspect, the device is configured to receive RRC messages.

[0161] In the nineteenth aspect, in conjunction with the eighteenth aspect, the maximum number of subgroups is determined based on RRC messages.

[0162] In the twentieth aspect, in conjunction with one or more of aspects seventeen to nineteen, the device is configured to determine the number of subgroups into which the resource set is divided.

[0163] In aspect 21, in combination with one or more of aspect 20, the number of subgroups is less than or equal to the number of the largest subgroup.

[0164] In the twenty-second aspect, in conjunction with one or more of the first to twenty-first aspects, the device is configured to generate a feedback message.

[0165] In the twenty-third aspect, in combination with one or more of the first to twenty-two aspects, the device is configured to transmit a feedback message to the base station.

[0166] In aspect 24, in conjunction with aspect 23, the feedback message includes several ACK / NACK indicators.

[0167] In aspect 25, in conjunction with one or more of aspects 22 to 24, the feedback message includes an ACK / NACK indicator for each subgroup.

[0168] In aspect 26, in conjunction with one or more of aspects 22 to 24, the feedback message includes an ACK / NACK indicator for each of the maximum number of subgroups.

[0169] In aspect 27, in conjunction with aspect 23, feedback messages indicate the number of ACKs, NACKs, or both regarding the number of subgroups.

[0170] In aspect 28, in conjunction with aspect 23, the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes multiple bits.

[0171] In the twenty-ninth aspect, in conjunction with the twenty-eighth aspect, the device is configured to determine the value of multiple bits.

[0172] In the thirtieth aspect, in conjunction with the twenty-ninth aspect, the device is configured to determine the amount of resources requested by the UE based on the value.

[0173] In the thirty-first aspect, in conjunction with one or more of the first to eighth aspects, the device is configured to determine the HARQ ID of the first subgroup of the sidelink resource set based on the HARQ process ID field of the grant message.

[0174] In aspect thirty-two, in conjunction with one or more of aspects one through eight or aspect fourteen, a message is permitted to indicate the number of one or more subgroups of the side link resource set.

[0175] In the thirty-third aspect, in conjunction with the thirty-second aspect, the device is configured to determine the number of one or more subgroups of the sidelink resource set.

[0176] In the thirty-fourth aspect, in conjunction with the thirty-third aspect, the number of one or more subgroups of the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided.

[0177] In aspect thirty-five, in conjunction with one or more of aspects thirty-three to thirty-four, the device is configured to receive RRC messages.

[0178] In the thirty-sixth aspect, in conjunction with the thirty-fifth aspect, the RRC message indicates the maximum number of subgroups.

[0179] In aspect thirty-seven, in conjunction with one or more of aspects one through eight or aspects fourteen through thirty-six, NDI control of the granted message is used for multiple subgroups.

[0180] In aspect thirty-eight, in conjunction with one or more of aspects one through eight or fourteen through thirty-six, each subgroup is associated with NDI control of the grant message.

[0181] In the thirty-ninth aspect, in conjunction with one or more of the first to eighth aspects or the fourteenth to thirty-eighth aspects, the device is configured to transmit a feedback message to the base station.

[0182] In aspect 40, in conjunction with aspect 39, the feedback message includes several ACK / NACK indicators, or the feedback message includes ACK / NACK indicators for each subgroup.

[0183] In the forty-first aspect, in combination with one or more of aspects one through forty, the granting message is a single granting message.

[0184] In aspect 42, in combination with one or more of aspects 1 to 41, permission is granted to include DCI.

[0185] In aspect 43, in conjunction with aspect 42, the permission message includes a single DCI.

[0186] In aspect 44, in combination with one or more of aspects 1 to 43, permitted messages include DG messages or CG messages.

[0187] In aspect 45, in combination with one or more of aspects 1 to 43, the permitted message includes the DCI 3_0 format.

[0188] In aspect 46, in combination with one or more of aspects 1 to 45, the base station includes a gNB; the UE includes a programmable logic controller; or a combination thereof.

[0189] In some aspects, techniques for implementing sidelink resource scheduling for unicast message reception may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes or apparatuses described elsewhere herein. In a forty-seventh aspect, techniques for implementing sidelink resource scheduling for unicast message reception may include an apparatus configured for wireless communication, such as a base station, configured to: generate an authorization message configured to allocate a set of sidelink resources to a UE; and transmit the authorization message to the UE for the UE to schedule unicast messages via different subgroups of the sidelink resource set. In some examples, the techniques of the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a base station or a component of a base station). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transient computer-readable medium on which program code is stored, which, when executed by the processing unit, is configured to cause a wireless communication device to perform the operations described herein.

[0190] In aspect 48, in conjunction with aspect 47, the base station is unaware of the sidelink resource splitting implemented by the UE.

[0191] In aspect 49, in conjunction with aspect 47 or 48, the device is configured to receive feedback messages from the UE.

[0192] In aspect 50, in conjunction with aspect 49, a feedback message responds to an grant message; the feedback message is a single feedback message; or a combination thereof.

[0193] In the fifty-first aspect, in conjunction with one or more of aspects forty-seven to forty-nine, the feedback message includes an ACK / NACK indicator.

[0194] In aspect 52, in conjunction with aspect 51, the ACK / NACK indicator is a single bit.

[0195] In aspect 53, in conjunction with aspect 51, the ACK / NACK indicator includes multiple bits.

[0196] In aspect 54, in conjunction with aspect 53, the device is configured to determine the value of multiple bits.

[0197] In aspect 55, in conjunction with aspect 53, the device is configured to determine the amount of resources requested by the UE based on the value.

[0198] In aspect 56, in conjunction with aspect 47, the base station is partially aware of the sidelink resource splitting implemented by the UE.

[0199] In aspect 57, in conjunction with aspect 56, the sidelink resource set includes one or more subgroups.

[0200] In aspect 58, in conjunction with one or more of 47 or 56 to 55, the device is configured to receive one or more feedback messages from the UE in response to an approval message.

[0201] In aspect 59, in combination with one or more of aspects 47 to 58, the device is configured to transmit an RRC message to the UE.

[0202] In the sixtieth aspect, in conjunction with the fifty-ninth aspect, the RRC message indicates the number of subgroups into which the sidelink resource set can be split.

[0203] In the sixty-first aspect, in conjunction with one or more of aspects fifty-nine to sixtieth, the device is configured to receive feedback messages from the UE.

[0204] In aspect sixty-two, in conjunction with aspect sixty-one, the feedback message includes several ACK / NACK indicators.

[0205] In aspect sixty-three, in conjunction with one or more of aspects sixty-one to sixty-two, the feedback message includes an ACK / NACK indicator for each subgroup.

[0206] In aspect sixty-four, in conjunction with aspect sixty-one, feedback messages indicate the number of ACKs, the number of NACKs, or both, regarding the number of subgroups.

[0207] In aspect sixty-five, in conjunction with aspect sixty-one, the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes multiple bits.

[0208] In the sixty-sixth aspect, in conjunction with the sixty-fifth aspect, the device is configured to determine the value of the multi-bits; and

[0209] In the sixty-seventh aspect, in conjunction with the sixty-sixth aspect, the device is configured to determine the amount of resources requested by the UE based on the value.

[0210] In aspect sixty-eight, in conjunction with aspect forty-seven, the splitting of sidelink resources for the sidelink resource set is controlled by the base station.

[0211] In aspect sixty-nine, in conjunction with aspect sixty-eight, the HARQ process ID field of the grant message indicates the HARQ ID of the first subgroup of the side link resource set.

[0212] In aspect 70, in combination with one or more of aspects 68 to 69, a message is permitted to indicate the number of one or more subgroups of the side link resource set.

[0213] In the seventy-first aspect, in conjunction with the seventy-second aspect, the number of one or more subgroups of the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided.

[0214] In aspect seventy-two, in combination with one or more of aspects seventy to seventy-one, the apparatus is configured to transmit radio resource control (RRC) messages to the UE.

[0215] In aspect seventy-three, in conjunction with one or more of aspects seventy to seventy-two, the RRC message indicates the maximum number of subgroups.

[0216] In aspect seventy-four, in conjunction with one or more of aspects seventy to seventy-three, NDI control of the granted message is used for multiple subgroups.

[0217] In aspect seventy-five, in conjunction with one or more of aspects seventy to seventy-three, NDI control for granting messages is applied to each subgroup.

[0218] In aspect seventy-six, in conjunction with one or more of aspects seventy to seventy-five, the device is configured to receive feedback messages from the UE.

[0219] In aspect seventy-seven, in conjunction with aspect seventy-six, the feedback message includes several ACK / NACK indicators.

[0220] In aspect seventy-eight, in conjunction with aspect seventy-six, the feedback message includes an ACK / NACK indicator for each subgroup.

[0221] In aspect seventy-nine, in combination with one or more of aspects forty-seven to seventy-eight, the base station includes a gNB, and the UE includes a programmable logic controller, or a combination thereof.

[0222] In aspect 80, in combination with one or more of aspects 47 to 79, the granting message is a single granting message.

[0223] In the eighty-first aspect, in combination with one or more of aspects forty-seven to eighty, permission is granted to include DCI.

[0224] In aspect 82, in conjunction with aspect 81, the grant message includes a single DCI.

[0225] In aspect 83, in combination with one or more of aspects 47 to 82, permitted messages include DG messages or CG messages.

[0226] In aspect 84, in combination with one or more of aspects 47 to 82, the permitted message includes the DCI 3_0 format.

[0227] In some aspects, techniques for implementing sidelink resource scheduling for unicast message transmission may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes or apparatuses described elsewhere herein. In aspect eighty-five, performing sidelink resource scheduling for unicast message transmission may include an apparatus configured to receive from a base station an permission message indicating a set of sidelink resources. The apparatus may also be configured to transmit multiple unicast messages via multiple subgroups of the sidelink resource set. In some examples, the techniques of the first aspect may be implemented in a method or process. In some other examples, the techniques of the first aspect may be implemented in a wireless communication device (such as a UE or a component of a UE). In some examples, the wireless communication device may include at least one processing unit or system (which may include an application processor, modem, or other component) and at least one memory device coupled to the processing unit. The processing unit may be configured to perform the operations described herein with respect to the wireless communication device. In some examples, the memory device includes a non-transitory computer-readable medium having program code stored thereon, configured, when executed by the processing unit, to cause the wireless communication device to perform the operations described herein.

[0228] In the 86th aspect, in conjunction with the 85th aspect, the device is configured to configure multiple subgroups of the sidelink resource set.

[0229] In aspect 87, in conjunction with one or more of aspects 85 or 86, in order to transmit multiple unicast messages via multiple subgroups, the apparatus is further configured to initiate the transmission of the multiple unicast messages via each of the multiple subgroups.

[0230] In aspect 88, in conjunction with one or more of aspects 85 to 87, the apparatus is configured to determine a set of sidelink resources based on an approval message; and to divide the set of sidelink resources into multiple subgroups.

[0231] In aspect 89, in conjunction with aspect 88, the sidelink resource set is split based on RX UE buffer status reports, RX UE channel channel state information, or a combination thereof.

[0232] In aspect ninety, in conjunction with one or more of aspects eighty-five to eighty-nine, the device is configured to schedule multiple unicast messages.

[0233] In aspect ninety-one, in conjunction with aspect ninety, in order to transmit multiple unicast messages, the apparatus is configured to transmit a first unicast message of the multiple unicast messages to a first receiving UE via a first subgroup of these subgroups, and to transmit a second unicast message of the multiple unicast messages to a second receiving UE via a second subgroup of these subgroups.

[0234] In aspect ninety-two, in combination with one or more of aspects eighty-five to ninety-one, the apparatus is configured to receive a first ACK / NACK message from a first RX UE in response to a first unicast message, and to receive a second ACK / NACK message from a second RX UE in response to a second unicast message.

[0235] In aspect ninety-three, in conjunction with one or more of aspects eighty-five to ninety-two, the apparatus is configured to generate a buffer state for each of one or more RX UEs, and to transmit a sidelink BSR to the base station to request sidelink resources.

[0236] In aspect ninety-four, in conjunction with aspect ninety-three, the apparatus is configured to combine the buffer states of multiple RX UEs to generate a sidelink BSR.

[0237] In aspect ninety-five, in combination with one or more of aspects eighty-five to ninety-four, the device is configured to transmit a feedback message to the base station.

[0238] In aspect ninety-six, in conjunction with aspect ninety-five, a feedback message responds to an grant message, and the feedback message is a single feedback message or a combination thereof.

[0239] In aspect ninety-seven, in conjunction with aspect ninety-five, the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes one or more bits.

[0240] In aspect ninety-eight, in conjunction with aspect ninety-seven, the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes multiple bits.

[0241] In aspect ninety-nine, in conjunction with one or more of aspects ninety-eight, the apparatus is configured to determine the amount of resources to be requested from the base station; and to determine the value of the multi-bits based on that amount.

[0242] In the first aspect, in conjunction with one or more of aspects 85 to 99, the device is configured to determine the maximum number of subgroups into which the resource collection can be divided, and to receive upper-layer messages; and

[0243] In the 101st aspect, in conjunction with the 100th aspect, the maximum number of subgroups is determined based on RRC messages.

[0244] In the 102nd aspect, in combination with one or more of aspects 85 to 101, the device is configured to generate a feedback message and transmit the feedback message to a base station.

[0245] In aspect 103, in conjunction with aspect 102, the feedback message includes several ACK / NACK indicators.

[0246] In aspect 104, in conjunction with aspect 102, the feedback message includes an ACK / NACK indicator for each subgroup.

[0247] In aspect 105, in conjunction with aspect 102, the feedback message includes an ACK / NACK indicator for each of the maximum number of subgroups.

[0248] In aspect 106, in conjunction with aspect 102, the feedback message indicates the number of ACKs, the number of NACKs, or both, regarding the number of subgroups.

[0249] In aspect 107, in conjunction with aspect 102, the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes multiple bits.

[0250] In the 108th aspect, in conjunction with the 107th aspect, the device is configured to determine the value of the multi-bit; and based on the value, to determine the amount of resources requested by the UE.

[0251] In aspect 109, in conjunction with one or more of aspects 85 to 93, the apparatus is configured to determine the HARQ ID of the first subgroup of the sidelink resource set based on the HARQ process ID field of the grant message.

[0252] In aspect 110, in combination with one or more of aspects 85 to 93 or aspect 109, a message is permitted to indicate the number of one or more subgroups of the side link resource set.

[0253] In the 111th aspect, in conjunction with the 110th aspect, the apparatus is configured to determine the number of one or more subgroups of a sidelink resource set, the number of one or more subgroups of the sidelink resource set being less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided.

[0254] In the 112th aspect, in conjunction with the 111th aspect, the device is configured to receive an RRC message indicating the maximum number of subgroups.

[0255] In aspect 113, in combination with one or more of aspects 85 to 93 or aspects 109 to 112, NDI control of the granted message is used for multiple subgroups.

[0256] In aspect 114, in conjunction with one or more of aspects 85 to 93 or aspects 109 to 112, each subgroup is associated with NDI control of the grant message.

[0257] In aspect 115, in combination with one or more of aspects 85 to 93 or aspects 109 to 114, the apparatus is configured to transmit a feedback message to a base station, and the feedback message includes a plurality of ACK / NACK indicators, or the feedback message includes ACK / NACK indicators for each subgroup.

[0258] In aspect 116, in combination with one or more of aspects 85 to 4, the grant message is a single grant message, or the grant message includes DCI.

[0259] In aspect 117, in conjunction with aspect 116, the permission message includes a single DCI.

[0260] Those skilled in the art will understand that information and signals can be represented using any of a variety of different techniques and skills. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referred to throughout the above description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or light particles, or any combination thereof.

[0261] The article about Figure 1-10 The components, functional blocks, and modules described herein may include processors, electronic devices, hardware devices, electronic components, logic circuits, memory, software code, firmware code, and any combination thereof. Furthermore, the features discussed herein may be implemented via dedicated processor circuitry, via executable instructions, or a combination thereof.

[0262] Those skilled in the art will further appreciate that the various illustrative logic blocks, modules, circuits, and algorithmic steps described in conjunction with the disclosure herein can be implemented as electronic hardware, computer software, or a combination of both. To clearly illustrate this interchangeability between hardware and software, the various illustrative components, blocks, modules, circuits, and steps are described above in a generalized form in terms of their functionality. Whether such functionality is implemented as hardware or software depends on the specific application and the design constraints imposed on the overall system. Those skilled in the art may implement the described functionality in different ways for each specific application, but such implementation decisions should not be construed as departing from the scope of this disclosure. Those skilled in the art will also readily recognize that the order or combination of components, methods, or interactions described herein are merely illustrative and that components, methods, or interactions of various aspects of this disclosure may be combined or performed in ways other than those explained and described herein.

[0263] The various illustrative logic blocks, modules, and circuits described herein can be implemented or executed using a general-purpose processor, digital signal processor (DSP), application-specific integrated circuit (ASIC), field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in alternatives, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors cooperating with a DSP core, or any other such configuration.

[0264] The steps of the methods or algorithms described herein can be implemented directly in hardware, in a software module executed by a processor, or a combination of both. The software module may reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, removable disk, CD-ROM, or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor so that the processor can read / write information from / to the storage medium. In an alternative, the storage medium may be integrated into the processor. The processor and storage medium may reside in an ASIC. The ASIC may reside in a user terminal. In an alternative, the processor and storage medium may reside as discrete components in the user terminal.

[0265] In one or more exemplary designs, the described functionality may be implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functionality may be stored or transmitted as one or more instructions or code on or through a computer-readable medium. A computer-readable medium includes both computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. A computer-readable storage medium may be any available medium accessible to a general-purpose or special-purpose computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and is accessible to a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor. Furthermore, a connection may also be appropriately referred to as a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, or digital subscriber line (DSL), then the coaxial cable, fiber optic cable, twisted pair, or DSL is included in the definition of a medium. As used in this article, disk and disc include compact discs (CDs), laser discs, optical discs, digital multi-purpose discs (DVDs), hard disks, solid-state drives (SSDs), and Blu-ray discs. Disks typically reproduce data magnetically, while discs reproduce data optically using lasers. Combinations of these should also be included within the scope of computer-readable media.

[0266] As used herein (including in the claims), the term “and / or” in a list of two or more items means that any one of the listed items may be used alone, or any combination of two or more listed items may be used. For example, if a composition is described as containing components A, B, and / or C, then the composition may contain only A; only B; only C; a combination of A and B; a combination of A and C; a combination of B and C; or a combination of A, B, and C. Moreover, as used herein (including in the claims), the word “or” in a list of items containing “at least one of” indicates a disjunctive list, such that a list such as “at least one of A, B, or C” means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) or any combination thereof.

[0267] The prior description of this disclosure is provided to enable any person skilled in the art to make or use this disclosure. Various modifications to this disclosure will be readily apparent to those skilled in the art, and the general principles defined herein can be applied to other variations without departing from the spirit or scope of this disclosure. Therefore, this disclosure is not intended to be limited to the examples and designs described herein, but should be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A wireless communication method performed by a user equipment (UE), the method comprising: Receive an authorization message indicating a set of sidelink resources, wherein the authorization message indicates the number of subgroups of sidelink resource subgroups in the set of sidelink resources; as well as Multiple unicast messages are transmitted via multiple subgroups of the sidelink resource subgroups in the sidelink resource set, wherein the multiple subgroups of the sidelink resource subgroups are determined based on the number of subgroups in the sidelink resource subgroups.

2. The method of claim 1, further comprising: Configure the multiple subgroups of the sidelink resource set; as well as Transmitting the plurality of unicast messages via the plurality of subgroups includes transmitting one unicast message of the plurality of unicast messages via each of the plurality of subgroups.

3. The method of claim 1, further comprising: The sidelink resource set is determined based on the permission message; as well as The sidelink resource set is split into the multiple subgroups.

4. The method of claim 3, further comprising: The sidelink resource set is divided into the multiple subgroups, wherein the sidelink resource set is divided based on the received (RX) UE buffer state report and the channel state information of the RX UE channel.

5. The method of claim 1, further comprising: Schedule the multiple unicast messages; and The transmission of the plurality of unicast messages includes: The first unicast message of the plurality of unicast messages is transmitted to the first receiving (RX) UE via the first subgroup of the plurality of subgroups; The second unicast message among the plurality of unicast messages is transmitted to the second RX UE via the second subgroup among the plurality of subgroups; In response to the first unicast message, a first ACK / NACK message is received from the first RX UE; and A second ACK / NACK message is received from the second RX UE in response to the second unicast message.

6. The method of claim 1, further comprising: Generate a buffer state for each of one or more receive (RX) UEs; as well as Transmit a sidelink buffer status report (BSR) to request sidelink resources.

7. The method of claim 6, further comprising: The buffer states of multiple RX UEs are combined to generate the sidelink BSR.

8. The method of claim 1, further comprising: Transmit feedback messages, wherein the feedback messages include ACK / NACK messages, and wherein the ACK / NAK messages include ACK / NACK indicators for each of the plurality of subgroups.

9. The method of claim 8, wherein: The feedback message is in response to the grant message; The feedback message is a single feedback message; or Its combination.

10. The method of claim 8, wherein the ACK / NACK indicator comprises one or more bits.

11. The method of claim 8, wherein the ACK / NACK indicator comprises multiple bits, the method further comprising: Determine the amount of the resource to be requested; as well as The value of the multi-bit is determined based on the quantity.

12. The method of claim 11, further comprising: Determine the maximum number of subgroups into which the sidelink resource set can be split; as well as Receive messages from the upper layer; The maximum number of subgroups is determined based on the upper-layer messages.

13. The method of claim 1, wherein the number of subgroups of the sidelink resource subgroups in the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided.

14. The method of claim 1, further comprising: Receive Radio Resource Control (RRC) messages indicating the maximum number of subgroups.

15. A user equipment (UE), comprising: At least one processor; as well as A memory coupled to the at least one processor and storing processor-readable code, which, when executed by the at least one processor, is configured to cause the UE to: Receive an authorization message indicating a set of sidelink resources, wherein the authorization message indicates the number of subgroups of sidelink resource subgroups in the set of sidelink resources; as well as Multiple unicast messages are transmitted via multiple subgroups of the sidelink resource subgroups in the sidelink resource set, wherein the multiple subgroups of the sidelink resource subgroups are determined based on the number of subgroups in the sidelink resource subgroups.

16. The UE of claim 15, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: Generate feedback messages; and The feedback message is transmitted.

17. The UE of claim 16, wherein the feedback message includes a plurality of ACK / NACK indicators.

18. The UE of claim 16, wherein the feedback message includes an ACK / NACK indicator for each of the plurality of subgroups.

19. The UE of claim 16, wherein the feedback message includes an ACK / NACK indicator for each of the maximum number of subgroups, and wherein the sidelink resource set can be split into the maximum number of subgroups.

20. The UE of claim 16, wherein the feedback message indicates the number of ACKs, the number of NACKs, or both for one or more subgroups of the number of subgroups.

21. The UE of claim 16, wherein the feedback message includes an ACK / NACK indicator, and the ACK / NACK indicator includes multiple bits.

22. The UE of claim 21, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: Determine the value of the multi-bit; and The amount of resources requested by the UE is determined based on the value.

23. The UE of claim 15, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: The HARQ ID of the first subgroup of the sidelink resource set is determined based on the Hybrid Automatic Repeat Request (HARQ) process identity (ID) field of the grant message.

24. The UE of claim 15, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: Determine the number of one or more subgroups of the sidelink resource set, wherein the number of one or more subgroups of the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided; and Receive a Radio Resource Control (RRC) message indicating the maximum number of subgroups.

25. The UE of claim 15, wherein the New Data Indicator (NDI) control of the grant message is used for multiple subgroups.

26. The UE of claim 15, wherein each subgroup is associated with the New Data Indicator (NDI) control of the grant message.

27. The UE of claim 15, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: Send feedback messages; and in: The feedback message includes several ACK / NACK indicators; or The feedback message includes ACK / NACK indicators for each subgroup.

28. The UE of claim 15, wherein the grant message is a single grant message and wherein the grant message includes a single downlink control information (DCI).

29. The UE of claim 15, wherein the number of subgroups of the sidelink resource subgroups in the sidelink resource set is less than or equal to the maximum number of subgroups into which the sidelink resource set can be divided.

30. The UE of claim 15, wherein the processor-readable code, when executed by the at least one processor, is further configured such that the UE: Receive Radio Resource Control (RRC) messages indicating the maximum number of subgroups.

Images