CN117501769A - Transmission of inter-UE coordinated feedback for V2X side link communication with collision avoidance - Google Patents

Abstract

Devices and systems for New Radio (NR) vehicle-to-everything (V2X) side link communications are described. UE procedures and content for transmission of coordinated feedback between independent and non-independent UEs, and resource selection using the coordinated feedback between UEs are described. The content and container of inter-UE coordination feedback is provided, as well as the ordering of the resource selection procedure carrying the inter-UE coordination feedback and the transmission priority and condition of the inter-UE coordination feedback. inter-UE coordination feedback requests, initial pre-processing of inter-UE coordination feedback, secondary UE selection and resource selection are presented.

Description

Transmission of inter-UE coordinated feedback for V2X side link communication with collision avoidance

Priority claim

The present application claims priority from U.S. provisional patent application Ser. No. 63/230,016, filed on 5 th 8 th 2021, and U.S. provisional patent application Ser. No. 63/230,557, filed on 6 th 8 th 2021, each of which is incorporated herein by reference in its entirety.

Technical Field

Embodiments relate to Next Generation (NG) wireless communications. In particular, some embodiments relate to New Radio (NR) vehicle-to-everything (V2X) side link communications.

Background

The use and complexity of Next Generation (NG) or New Radio (NR) wireless systems, including 5G networks and beginning to include sixth generation (6G) networks, has increased due to the increase in two: the type of devices that use network resources, such as User Equipment (UEs), and the amount of data and bandwidth used by various applications operating on these UEs, such as video streaming. With the substantial increase in the number and diversity of communication devices, the corresponding network environments including routers, switches, bridges, gateways, firewalls, and load balancers have become increasingly complex. As expected, with the advent of any new technology, problems arose, including complexity and vehicle communications.

Drawings

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. The accompanying drawings illustrate generally, by way of example, and not by way of limitation, various embodiments discussed in the present document.

Fig. 1A illustrates an architecture of a network in accordance with some aspects.

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 1C illustrates a non-roaming 5G system architecture in accordance with some aspects.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments.

Fig. 3A illustrates inter-independent UE coordination feedback in accordance with some embodiments.

Fig. 3B illustrates dependent inter-UE coordination feedback in accordance with some embodiments.

Fig. 4A illustrates ordering of priority-based resource selection procedures in accordance with some embodiments.

Fig. 4B illustrates ordering of a feedback type based resource selection process in accordance with some embodiments. Resource size alignment procedure

Fig. 5A illustrates a resource size alignment procedure according to some embodiments.

Fig. 5B illustrates another resource size alignment procedure in accordance with some embodiments.

Fig. 6 illustrates a block diagram of an NR V2X side chain resource allocation procedure according to some embodiments.

Fig. 7A illustrates a block diagram of a first option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

Fig. 7B illustrates a block diagram of a second option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

Fig. 7C illustrates a block diagram of a third option for an NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

Fig. 7D illustrates a block diagram of a fourth option for NR V2X side chain resource allocation with inter-UE coordination feedback according to some embodiments.

Fig. 7E illustrates a block diagram of a fifth option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

Fig. 7F illustrates a block diagram of a sixth option for NR V2X side chain resource allocation with inter-UE coordination feedback according to some embodiments.

Fig. 7G illustrates a block diagram of a seventh option of an NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

Fig. 8A illustrates a resource exclusion procedure that does not use inter-UE coordination resource sets, in accordance with some embodiments.

Fig. 8B illustrates a resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments.

Fig. 8C illustrates another resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments.

Fig. 8D illustrates another resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments.

Detailed Description

The following description and the drawings sufficiently illustrate specific embodiments to enable those skilled in the art to practice them. Other embodiments may incorporate structural, logical, electrical, process, and other changes. Portions and features of some embodiments may be included in, or substituted for, those of others. The embodiments recited in the claims encompass all available equivalents of those claims.

Fig. 1A illustrates an architecture of a network in accordance with some aspects. Network 140A includes 3GPP LTE/4G and NG network functions that can be extended to 6G and later generation functions. Thus, while reference will be made to 5G, it is understood that this can be extended to 6G (and later) structures, systems, and functions. The network functions may be implemented as discrete network elements on dedicated hardware, as software instances running on dedicated hardware, and/or as virtualized functions instantiated on an appropriate platform, e.g., dedicated hardware or cloud infrastructure.

Network 140A is shown to include User Equipment (UE) 101 and UE 102. The UEs 101 and 102 are illustrated as smart phones (e.g., handheld touch screen mobile computing devices connectable to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a portable (laptop) or desktop computer, a wireless handset, an unmanned aerial vehicle, or any other computing device that includes a wired and/or wireless communication interface. The UEs 101 and 102 may be collectively referred to herein as UE 101, and UE 101 may be configured to perform one or more of the techniques disclosed herein.

Any of the radio links described herein (e.g., for use in network 140A or any other illustrated network) may operate in accordance with any of the exemplary radio communication techniques and/or standards. Any spectrum management scheme including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed) shared spectrum (e.g., licensed shared access (Licensed Shared Access, LSA) in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz, and other frequencies, and spectrum access systems (Spectrum Access System, SAS) in 3.55-3.7GHz and other frequencies). Different single carrier or orthogonal frequency domain multiplexing (Orthogonal Frequency Domain Multiplexing, OFDM) modes (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier, FBMC), OFDMA, etc.), in particular 3GPP NR, may be used by allocating OFDM carrier data bit vectors to the corresponding symbol resources.

In some aspects, either of the UEs 101 and 102 may include an internet of things (Internet of Things, ioT) UE or a cellular IoT (CIoT) UE, which may include a network access layer designed for low power IoT applications that utilize short term UE connections. In some aspects, either of the UEs 101 and 102 may include Narrowband (NB) IoT UEs (e.g., enhanced NB-IoT (eNB-IoT) UEs and further enhanced (FeNB-IoT) UEs). IoT UEs may utilize technologies such as machine-to-machine (M2M) or machine-to-Machine (MTC) communication to exchange data with MTC servers or devices via public land mobile networks (public land mobile network, PLMNs), proximity-Based services (ProSe) or device-to-device (D2D) communication, sensor networks, or IoT networks. The M2M or MTC data exchange may be a machine initiated data exchange. IoT networks include interconnecting IoT UEs with short-term connections, which may include uniquely identifiable embedded computing devices (within the internet infrastructure). The IoT UE may execute a background application (e.g., keep-alive messages, status updates, etc.) to facilitate connection of the IoT network. In some aspects, either of the UEs 101 and 102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

The UEs 101 and 102 may be configured to connect, e.g., communicatively couple, with a radio access network (radio access network, RAN) 110. RAN 110 may be, for example, an evolved universal mobile telecommunications system (Evolved Universal Mobile Telecommunications System, UMTS) terrestrial radio access network (Evolved UMTS Terrestrial Radio Access Network, E-UTRAN), a next generation RAN (NextGen RAN, NG RAN), or some other type of RAN. RAN 110 may include one or more gnbs, one or more of which may be implemented by multiple units. Note that although a gNB may be mentioned herein, the same aspects may also be applied to other generation nodebs, e.g. generation 6 NodeB, and may thus be referred to as radio access network node (RAN node) instead.

Each gNB may implement protocol entities in a 3GPP protocol stack, the layers in the protocol stack being considered ordered, in the following order from low to high: physical (PHY), medium access control (Medium Access Control, MAC), radio link control (Radio Link Control, RLC), packet data convergence control (Packet Data Convergence Control, PDCP) and radio resource control (Radio Resource Control, RRC)/service data adaptation protocol (Service Data Adaptation Protocol, SDAP) (for control plane/user plane). The protocol layers in each gNB may be distributed in different units: a Central Unit (CU), at least one Distributed Unit (DU) and a remote radio head (Remote Radio Head, RRH). A CU may provide functions such as transmission control of user data and enable mobility control, radio access network sharing, positioning and session management, except for those functions specifically allocated to DUs.

The higher protocol layers (PDCP of control plane and PDCP and SDAP of RRC/user plane) may be implemented in the CU and RLC and MAC layers may be implemented in the DUs. The PHY layer may be partitioned, with higher PHY layers also implemented in DUs and lower PHY layers implemented in RRHs. The CUs, DUs and RRHs may be implemented by different manufacturers, but they may be connected by appropriate interfaces. A CU may be connected to a plurality of DUs.

Interfaces within the gNB include the E1 and Forward-have (F) F1 interfaces. The E1 interface may be between a CU control plane (gNB-CU-CP) and a CU user plane (gNB-CU-UP) such that the exchange of signaling information between the control plane and the user plane may be supported through E1AP services. The E1 interface may separate the radio network layer and the transport network layer and enable exchange of UE-associated information and non-UE-associated information. The E1AP service may be a non-UE associated service related to the entire E1 interface instance between the gNB-CU-CP and the gNB-CU-UP using a non-UE associated signaling connection, as well as a UE associated service related to a single UE and associated with a UE associated signaling connection maintained for the UE.

The F1 interface may be arranged between a CU and a DU. The CU may control the operation of the DU through the F1 interface. Since signaling in the gNB is split into control plane and user plane signaling, the F1 interface may be split into an F1-C interface for control plane signaling between the gNB-DU and gNB-CU-CP, and an F1-U interface for user plane signaling between the gNB-DU and gNB-CU-UP, which support control plane and user plane separation. The F1 interface may separate the radio network and transport network layers and enable exchange of UE-associated information and non-UE-associated information. Further, the F2 interface may be between a lower portion and an upper portion of the NR PHY layer. The F2 interface may also be separated into F2-C and F2-U interfaces based on control plane and user plane functions.

The UEs 101 and 102 utilize connections 103 and 104, respectively, each of which includes a physical communication interface or layer (discussed in more detail below); in this example, connections 103 and 104 are illustrated as air interfaces to enable communicative coupling and may conform to cellular communication protocols, such as the Global System for Mobile communications (Global System for Mobile Communications, GSM) protocol, code-division multiple Access (code-division multiple access, CDMA) network protocol, push-to-Talk (PTT) protocol, cellular PTT (PTT over Cellular, POC) protocol, universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS) protocol, 3GPP Long term evolution (Long Term Evolution, LTE) protocol, 5G protocol, 6G protocol, and so forth.

In an aspect, the UEs 101 and 102 may also exchange communication data directly via the ProSe interface 105. ProSe interface 105 may alternatively be referred to as a Side Link (SL) interface including one or more logical channels, including, but not limited to, a physical side link control channel (Physical Sidelink Control Channel, PSCCH), a physical side link shared channel (Physical Sidelink Shared Channel, PSSCH), a physical side link discovery channel (Physical Sidelink Discovery Channel, PSDCH), a physical side link broadcast channel (Physical Sidelink Broadcast Channel, PSBCH), and a physical side link feedback channel (PSFCH).

UE 102 is shown configured to access an Access Point (AP) 106 via a connection 107. Connection 107 may comprise a local wireless connection, such as a connection conforming to any IEEE 802.11 protocol, according to which AP 106 may comprise a wireless fidelity (wireless fidelity,) And a router. In this example, the AP 106 is shown connected to the internet, rather than to the core network of the wireless system (described in more detail below).

RAN 110 may include one or more access nodes that enable connections 103 and 104. These Access Nodes (ANs) may be referred to as Base Stations (BSs), nodebs, evolved nodebs (enbs), next generation nodebs (gnbs), RAN nodes, etc., and may include ground stations (e.g., ground access points) or satellite stations that provide coverage within a certain geographic area (e.g., cell). In some aspects, communication nodes 111 and 112 may be transmission/reception points (TRPs). In the case where the communication nodes 111 and 112 are nodebs (e.g., enbs or gnbs), one or more TRPs may operate within the communication cell of the NodeB. RAN 110 may include one or more RAN nodes, such as macro RAN node 111, for providing macro cells and one or more RAN nodes, such as Low Power (LP) RAN node 112, for providing femto cells or pico cells (e.g., cells having smaller coverage areas, smaller user capacity, or higher bandwidths than macro cells).

Either of the RAN nodes 111 and 112 may terminate the air interface protocol and may be the first point of contact for the UEs 101 and 102. In some aspects, any of RAN nodes 111 and 112 may perform various logical functions for RAN 110 including, but not limited to, radio network controller (radio network controller, RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management. In one example, any of nodes 111 and/or 112 may be a gNB, an eNB, or another type of RAN node.

RAN 110 is shown communicatively coupled to a Core Network (CN) 120 via an S1 interface 113. In an aspect, the CN 120 may be an evolved packet core (evolved packet core, EPC) network, a next generation packet core (NextGen Packet Core, NPC) network, or some other type of CN (e.g., as shown with reference to fig. 1B-1C). In this aspect, the S1 interface 113 is split into two parts: an S1-U interface 114 that carries traffic data between RAN nodes 111 and 112 and a serving gateway (S-GW) 122, and an S1 mobility management entity (mobility management entity, MME) interface 115 that is a signaling interface between RAN nodes 111 and 112 and MME 121.

In this aspect, the CN 120 includes an MME 121, an S-GW 122, a packet data network (Packet Data Network, PDN) gateway (P-GW) 123, and a home subscriber server (home subscriber server, HSS) 124.MME 121 may be similar in function to the control plane of a legacy serving general packet radio service (General Packet Radio Service, GPRS) support node (Serving GPRS Support Node, SGSN). MME 121 may manage mobility aspects in the access such as gateway selection and tracking area list management. HSS124 may include a database for network users including subscription-related information to support the handling of communication sessions by network entities. The CN 120 may include one or several HSS124 depending on the number of mobile subscribers, the capacity of the device, the organization of the network, etc. For example, HSS124 may provide support for routing/roaming, authentication, authorization, naming/addressing resolution, location compliance, and so on.

S-GW 122 may terminate S1 interface 110 towards RAN 113 and route data packets between RAN 110 and CN 120. Furthermore, S-GW 122 may be a local mobility anchor point for inter-RAN node handover and may also provide anchoring for inter-3 GPP mobility. Other responsibilities of S-GW 122 may include lawful interception, charging, and some policy enforcement.

The P-GW 123 may terminate the SGi interface towards the PDN. The P-GW 123 may route data packets between the CN 120 and external networks, such as a network including an application server 184 (or application function (application function, AF)) via an Internet Protocol (IP) interface 125. The P-GW 123 may also communicate data to other external networks 131A, which may include the internet, IP multimedia subsystem (IP multimedia subsystem, IPs) networks, and others. In general, the application server 184 may be an element that provides an application (e.g., a UMTS Packet Service (PS) domain, an LTE PS data Service, etc.) that uses IP bearer resources with the core network. In this aspect, P-GW 123 is shown communicatively coupled to application server 184 via IP interface 125. The application server 184 may also be configured to support one or more communication services (e.g., voice-over-Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UEs 101 and 102 via the CN 120.

The P-GW 123 may also be a node for policy enforcement and charging data collection. Policy and charging rules function (Policy and Charging Rules Function, PCRF) 126 is a policy and charging control element of CN 120. In a non-roaming scenario, in some aspects, there may be a single PCRF in the home public land mobile network (Home Public Land Mobile Network, HPLMN) associated with an internet protocol connectivity access network (Internet Protocol Connectivity Access Network, IP-CAN) session of the UE. In a roaming scenario with local bursts of traffic, there may be two PCRFs associated with the IP-CAN session of the UE: a Home PCRF (H-PCRF) within the HPLMN, and a Visited PCRF (V-PCRF) within the Visited public land mobile network (Visited Public Land Mobile Network, VPLMN). PCRF 126 may be communicatively coupled to application server 184 via P-GW 123.

In some aspects, the communication network 140A may be an IoT network or a 5G or 6G network, including a 5G new radio network that uses communication in licensed (5G NR) and unlicensed (5G NR-U) spectrum. One of the current contributors to IoT is the narrowband-IoT (NB-IoT). Operations in the unlicensed spectrum may include dual connectivity (dual connectivity, DC) operations and independent LTE systems in the unlicensed spectrum, according to which LTE-based techniques operate only in the unlicensed spectrum without using "anchors" in the licensed spectrum, known as multewire. Further enhanced operation of LTE systems in licensed spectrum as well as unlicensed spectrum is expected in future releases and 5G systems. Such enhanced operations may include techniques for NR side link resource allocation and UE processing behavior for NR side link V2X communications.

The NG system architecture (or 6G system architecture) may include RAN 110 and Core Network (CN) 120.NG-RAN 110 may include multiple nodes, such as a gNB and a NG-eNB. The CN 120 (e.g., 5G core network (5 GC)) may include access and mobility functions (access and mobility function, AMF) and/or user plane functions (user plane function, UPF). The AMF and UPF may be communicatively coupled to the gNB and the NG-eNB via an NG interface. More specifically, in some aspects, the gNB and NG-eNB may connect to the AMF over a NG-C interface and to the UPF over a NG-U interface. The gNB and NG-eNB may be coupled to each other via an Xn interface.

In some aspects, the NG system architecture may use reference points between various nodes. In some aspects, each of the gNB and NG-eNB may be implemented as a base station, a mobile edge server, a small cell, a home eNB, and so on. In some aspects, the gNB may be a Master Node (MN) in a 5G architecture, and the NG-eNB may be a Secondary Node (SN).

Fig. 1B illustrates a non-roaming 5G system architecture in accordance with some aspects. In particular, FIG. 1B illustrates a 5G system architecture 140B in reference point representation, which may be extended to a 6G system architecture. More specifically, UE 102 may communicate with RAN 110 and one or more other CN network entities. The 5G system architecture 140B includes a plurality of Network Functions (NF), such as AMF 132, session management function (session management function, SMF) 136, policy control function (policy control function, PCF) 148, application function (application function, AF) 150, UPF 134, network slice selection function (network slice selection function, NSSF) 142, authentication server function (authentication server function, AUSF) 144, and Unified Data Management (UDM)/home subscriber server (home subscriber server, HSS) 146.

The UPF 134 may provide a connection to a Data Network (DN) 152, which may include, for example, operator services, internet access, or third party services. The AMF 132 may be used to manage access control and mobility and may also include network slice selection functionality. The AMF 132 may provide UE-based authentication, authorization, mobility management, etc., and may be independent of access technology. The SMF 136 may be configured to set up and manage various sessions according to network policies. The SMF 136 may thus be responsible for session management and IP address assignment to the UE. The SMF 136 may also select and control the UPF 134 for data transfer. The SMF 136 may be associated with a single session of the UE 101 or multiple sessions of the UE 101. That is, the UE 101 may have multiple 5G sessions. Different SMFs may be assigned to each session. The use of different SMFs may allow each session to be managed separately. Thus, the functionality of each session may be independent of the other.

The UPF 134 can be deployed in one or more configurations and can be connected to a data network depending on the type of service desired. PCF 148 may be configured to provide a policy framework (similar to PCRF in 4G communication systems) with network slicing, mobility management, and roaming. The UDM may be configured to store subscriber profiles and data (similar to HSS in a 4G communication system).

The AF 150 may provide information about the packet flow to the PCF 148 responsible for policy control to support the desired QoS. PCF 148 may set mobility and session management policies for UE 101. To this end, PCF 148 may use the packet flow information to determine the appropriate policy for AMF 132 and SMF 136 to operate properly. The AUSF 144 may store data for UE authentication.

In some aspects, the 5G system architecture 140B includes an IP multimedia subsystem (IP multimedia subsystem, IMS) 168B and a plurality of IP multimedia core network subsystem entities, such as call session control functions (call session control functions, CSCFs). More specifically, the IMS168B includes a CSCF that may act as a proxy CSCF (P-CSCF) 162BE, a serving CSCF (S-CSCF) 164B, an emergency CSCF (E-CSCF) (not shown in FIG. 1B), or an interrogating CSCF (I-CSCF) 166B. P-CSCF 162B may be configured as a first point of contact for UE 102 within IM Subsystem (IMs) 168B. S-CSCF 164B may be configured to handle session states in the network and E-CSCF may be configured to handle certain aspects of emergency sessions, such as routing emergency requests to the correct emergency center or PSAP. I-CSCF 166B may be configured to act as a point of contact within an operator's network for all IMS connections intended for subscribers of the network operator or roaming subscribers currently located within the service area of the network operator. In some aspects, I-CSCF 166B may be connected to another IP multimedia network 170B, such as an IMS operated by a different network operator.

In some aspects, the UDM/HSS146 may be coupled to an application server (application server, AS) 160B, which may include a telephony application server (telephony application server, TAS) or another application server. AS160B may be coupled to IMS168B via S-CSCF 164B or I-CSCF 166B.

The reference point representation indicates that interactions may exist between corresponding NF services. For example, fig. 1B illustrates the following reference points: n1 (between UE 102 and AMF 132), N2 (between RAN 110 and AMF 132), N3 (between RAN 110 and UPF 134), N4 (between SMF136 and UPF 134), N5 (between PCF 148 and AF 150, not shown), N6 (between UPF 134 and DN 152), N7 (between SMF136 and PCF 148, not shown), N8 (between UDM146 and AMF132, not shown), N9 (between two UPF 134, not shown), N10 (between UDM146 and SMF136, not shown), N11 (between AMF132 and SMF 136), N12 (between AUSF144 and AMF132, not shown), N13 (between AUSF144 and UDM146, not shown), N14 (between PCF 132, not shown), N15 (between PCF 148 and AMF132 in a non-roaming scenario, or between AMF132 and N16, and nsf 142 (between AMF 142, not shown), and N15 (between AMF132, not shown) in a non-roaming scenario. Other reference point representations not shown in fig. 1B may also be used.

FIG. 1C illustrates a 5G system architecture 140C and service-based representation. In addition to the network entities shown in fig. 1B, the system architecture 140C may also include a network exposure function (network exposure function, NEF) 154 and a network warehouse function (network repository function, NRF) 156. In some aspects, the 5G system architecture may be service-based, and interactions between network functions may be represented by respective point-to-point reference points Ni or as service-based interfaces.

In some aspects, as shown in fig. 1C, the service-based representation may be used to represent network functions within the control plane that enable other authorized network functions to access their services. In this regard, 5G system architecture 140C may include the following service-based interfaces: namf158H (service-based interface presented by AMF 132), nspf 158I (service-based interface presented by SMF 136), nnef 158B (service-based interface presented by NEF 154), npcf 158D (service-based interface presented by PCF 148), nudm 158E (service-based interface presented by UDM 146), naf 158F (service-based interface presented by AF 150), nnrf 158C (service-based interface presented by NRF 156), nnssf 158A (service-based interface presented by NSSF 142), nausf 158G (service-based interface presented by AUSF 144). Other service-based interfaces not shown in fig. 1C (e.g., nudr, N5g-eir, and Nudsf) may also be used.

The NR-V2X architecture may support high reliability low latency side link communications with various traffic patterns, including periodic and aperiodic communications with random packet arrival times and sizes. The techniques disclosed herein may be used to support high reliability in distributed communication systems with dynamic topologies, including side-link NR V2X communication systems.

Fig. 2 illustrates a block diagram of a communication device in accordance with some embodiments. The communication device 200 may be a UE, such as a dedicated computer, a personal or laptop computer (PC), a tablet PC, or a smart phone, a dedicated network device, such as an eNB, a server running software to configure the server to operate as a network device, a virtual device, or any machine capable of executing instructions (sequential or otherwise) specifying actions to be taken by the machine. For example, the communication device 200 may be implemented as one or more of the devices shown in FIGS. 1A-1C. Note that the communications described herein may be encoded prior to transmission by a transmitting entity (e.g., UE, gNB) for receipt by a receiving entity (e.g., gNB, UE) and decoded after receipt by the receiving entity.

Examples as described herein may include or may operate on logic or several components, modules, or mechanisms. Modules and components are tangible entities (e.g., hardware) capable of performing specified operations and may be configured or arranged in a manner. In an example, the circuitry may be arranged as modules in a specified manner (e.g., internally or to an external entity, such as other circuitry). In an example, all or part of one or more computer systems (e.g., stand-alone, client, or server computer systems) or one or more hardware processors may be configured by firmware or software (e.g., instructions, application portions, or applications) as modules that operate to perform specified operations. In an example, the software may reside on a machine readable medium. In one example, the software, when executed by the underlying hardware of the module, causes the hardware to perform the specified operations.

Thus, the term "module" (and "component") is understood to encompass a tangible entity, whether physically constructed, specially configured (e.g., hardwired) or temporarily (e.g., transient) configured (e.g., programmed) to operate in a specified manner or to perform some or all of any of the operations described herein. Considering the example of temporarily configuring modules, it is not necessary to instantiate each module at any one time. For example, where a module includes a general-purpose hardware processor configured with software, the general-purpose hardware processor may be configured as each of the different modules at different times. The software may accordingly configure the hardware processor to constitute a particular module at one time and to constitute a different module at a different time, for example.

The communication device 200 may include a hardware processor (or equivalently, processing circuitry) 202 (e.g., a central processing unit (central processing unit, CPU), GPU, hardware processor core, or any combination of these), a main memory 204, and a static memory 206, some or all of which may communicate with each other via an interconnection link (e.g., bus) 208. Main memory 204 may include any or all of removable storage and non-removable storage, volatile memory, or nonvolatile memory. The communication device 200 may also include a display unit 210 (e.g., a video display), an alphanumeric input device 212 (e.g., a keyboard), and a User Interface (UI) navigation device 214 (e.g., a mouse). In an example, display unit 210, input device 212, and UI navigation device 214 may be touch screen displays. The communication device 200 may also include a storage device (e.g., a drive unit) 216, a signal generation device 218 (e.g., a speaker), a network interface device 220, and one or more sensors, such as a global positioning system (global positioning system, GPS) sensor, compass, accelerometer, or other sensor. The communication device 200 may also include an output controller 2128, such as a serial (e.g., universal serial bus (universal serial bus, USB)), parallel, or other wired or wireless (e.g., infrared (IR), near field communication (near field communication, NFC), etc.) connection to communicate with or control one or more peripheral devices (e.g., printer, card reader, etc.).

The storage device 216 may include a non-transitory machine-readable medium 222 (hereinafter referred to simply as machine-readable medium) on which is stored one or more sets of data structures or instructions 224 (e.g., software) embodying or utilized by any one or more of the techniques or functions described herein. The instructions 224 may also reside, completely or at least partially, within the main memory 204, within the static memory 206, and/or within the hardware processor 202 during execution thereof by the communication device 200. While the machine-readable medium 222 is illustrated as a single medium, the term "machine-readable medium" may include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) configured to store the one or more instructions 224.

The term "machine-readable medium" may include any of the following media: such media can store, encode, or carry instructions for execution by the communication device 200 and that cause the communication device 200 to perform any one or more of the techniques of this disclosure, or can store, encode, or carry data structures used by, or associated with, such instructions. Non-limiting examples of machine readable media may include solid state memory, as well as optical and magnetic media. Specific examples of machine-readable media may include: nonvolatile Memory such as semiconductor Memory devices (e.g., electrically programmable read-Only Memory (EPROM), electrically erasable programmable read-Only Memory (Electrically Erasable Programmable Read-Only Memory, EEPROM)), and flash Memory devices; magnetic disks, such as internal hard disks and removable disks; magneto-optical disk; random access memory (Random Access Memory, RAM); CD-ROM and DVD-ROM discs.

Several kinds of materials can also be utilizedAny of the wireless local area network (wireless local area network, WLAN) transport protocols (e.g., frame relay, internet protocol (internet protocol, IP), transmission control protocol (transmission control protocol, TCP), user datagram protocol (user datagram protocol, UDP), hypertext transfer protocol (hypertext transfer protocol, HTTP), etc.) sends or receives instructions 224 over a communication network via network interface device 220 using transmission medium 226. Example communication networks may include a local area network (local area network, LAN), a wide area network (wide area network, WAN), a packet data network (e.g., the internet), a mobile telephone network (e.g., a cellular network), a plain old telephone (Plain Old Telephone, POTS) network, and a wireless data network. The communications over the network may include one or more different protocols, such as the institute of Electrical and electronics Engineers (Institute of Electrical and Electronics Engineers, IEEE) 802.11 family of standards, referred to as Wi-Fi, the IEEE 802.16 family of standards, referred to as WiMax, the IEEE 802.15.4 family of standards, the Long term evolution (Long Term Evolution, LTE) family of standards, the universal mobile telecommunications system (Universal Mobile Telecommunications System, UMTS) family of standards, the peer-to-peer (eer-peer, P2P) network, the Next Generation (NG)/the 5 th generation (5) ^th generation, 5G) standard, and so forth. In an example, the network interface device 220 may include one or more physical jacks (e.g., ethernet, coaxial, or telephone jacks) or one or more antennas to connect to the transmission medium 226.

Note that the term "circuitry" refers to, is part of, or comprises, hardware components such as the following configured to provide the described functionality: electronic circuitry, logic circuitry, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group), an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), a field-programmable device (FPD) (e.g., field-programmable gate array, FPGA), a programmable logic device (programmable logic device, PLD), a Complex PLD (CPLD), a high-capacity PLD (hcpll), a structured ASIC, or programmable SoC), a digital signal processor (digital signal processor, DSP), and so forth. In some embodiments, circuitry may execute one or more software or firmware programs to provide at least some of the described functions. The term "circuitry" may also refer to a combination of one or more hardware elements (or circuitry for use in an electrical or electronic system) and program code for performing the functions of the program code. In these embodiments, the combination of hardware elements and program code may be referred to as a particular type of circuit.

The term "processor circuit" or "processor" as used herein thus refers to, is part of, or includes the following circuitry: the circuitry is capable of sequentially and automatically performing a sequence of operations or logic operations, or recording, storing, and/or transmitting digital data. The term "processor circuit" or "processor" may refer to one or more application processors, one or more baseband processors, a physical central processing unit (central processing unit, CPU), a single or multi-core processor, and/or any other device capable of executing or otherwise operating computer executable instructions, such as program code, software modules, and/or functional processes.

Any of the radio links described herein may operate in accordance with any one or more of the following radio communication technologies and/or standards, including, but not limited to: global System for Mobile communications (Global System for Mobile Communications, GSM) radio communications technology, general packet radio service (General Packet Radio Service, GPRS) radio communications technology, enhanced data rates for GSM evolution (Enhanced Data Rates for GSM Evolution, EDGE) radio communications technology, and/or third Generation partnership project (Third Generation Partnership Project,3 GPP) radio communications technology, such as Universal Mobile Telecommunications System (Universal Mobile Telecommunications System, UMTS), multimedia Access free (Freedom of Multimedia Access, FOMA), 3GPP Long term evolution (Long Term Evolution, LTE), 3GPP Long term evolution advanced (Long Term Evolution Advanced, LTE advanced), code division Multiple access 2000 (Code Division multiple access, CDMA 2000), cellular digital packet Data (Cellular Digital Packet Data, CDPD), mobitex, third Generation (3G), circuit Switched Data (Circuit Switched Data, CSD), high-Speed Circuit Switched Data (HSCSD), universal mobile telecommunications system (Third Generation) (Universal Mobile Telecommunications System, UMTS (3G)), wideband code Division multiple access (universal mobile telecommunications system) (Wideband Code Division Multiple Access (Universal Mobile Telecommunications System), W-CDMA (UMTS)), high-Speed packet access (High Speed Packet Access, HSPA), high-Speed downlink packet access (High-Speed Downlink Packet Access, HSDPA), high Speed uplink packet access (High-Speed Uplink Packet Access, HSUPA), high Speed packet access enhancements (High Speed Packet Access Plus, hspa+), universal mobile telecommunications system-Time Division Duplex (UMTS-TDD), time Division-code Division multiple access (Time Division-Code Division Multiple Access, TD-CDMA), time Division-synchronous code Division multiple access (Time Division-Synchronous Code Division Multiple Access, TD-CDMA), third Generation partnership project version 8 (before Generation 4) (3 gpp rel.8 (Pre-4G)), 3gpp rel.9 (Third Generation partnership project version 9), 3GPP Rel.10 (third Generation partnership project release 10), 3GPP Rel.11 (third Generation partnership project release 11), 3GPP Rel.12 (third Generation partnership project release 12), 3GPP Rel.13 (third Generation partnership project release 13), 3GPP Rel.14 (third Generation partnership project release 14), 3GPP Rel.15 (third Generation partnership project release 15), 3GPP Rel.16 (third Generation partnership project release 16), 3GPP Rel.17 (third Generation partnership project release 17) and subsequent releases (e.g., release 18, release 19, etc.), 3GPP 5G,5G new radio (5G New Radio,5G NR), 3GPP 5G new radio, 3GPP LTE Extra,LTE-Advanced Pro, LTE license Assisted Access (LTE Licens-UMTS Assisted Access, LAA), multefire, terrestrial radio Access (UMTS Terrestrial Radio Access UTRA), evolved terrestrial radio Access (Evolved UMTS Terrestrial Radio Access, E-UTRA), long term evolution terrestrial radio Access (Evolved UMTS Terrestrial Radio Access, E-UTRA) Evolution advanced (4 th Generation) (LTE advanced (4G)), cdmaOne (2G), code division multiple access 2000 (third Generation) (CDMA 2000 (3G)), evolution Data Optimized or Evolution-Only (EV-DO), advanced mobile phone system (1 st Generation) (Advanced Mobile Phone System (1 st Generation), AMPS (1G)), total access communication system/extended total access communication system (Total Access Communication System/Extended Total Access Communication System, TACS/ETACS), digital AMPS (2 nd Generation) (D-AMPS (2G)), push-to-talk (PTT), mobile phone system (Mobile Telephone System, MTS), improved mobile telephone systems (Improved Mobile Telephone System, IMTS), advanced mobile telephone systems (Advanced Mobile Telephone System, AMTS), OLT (norway, offentlig Landmobil Telefoni, public land mobile telephone), MTD (swedish abbreviation for Mobiltelefonisystem D, or mobile telephone system D), public automated land mobile (Public Automated Land Mobile, autotel/PALM), ARP (finnish, autoadiopuline, "car radiotelephone"), NMT (Nordic Mobile Telephony, northern european mobile telephone), high capacity versions (Hicap) of NTT (japanese telegram and telephone), cellular digital packet Data (Cellular Digital Packet Data, CDPD), mobitex, dataTAC, integrated digital enhanced network (Integrated Digital Enhanced Network, iDEN), personal digital cellular (Personal Digital Cellular, PDC), circuit switched data (Circuit Switched Data, CSD), personal Handyphone System (PHS), broadband integrated digital enhanced network (Wideband Integrated Digital Enhanced Network, wiDEN), iBurst, unlicensed mobile access (Unlicensed Mobile Access, UMA) (also known as 3GPP universal access network, or GAN standard), zigbee, The wireless gigabit alliance (Wireless Gigabit Alliance, wiGig) standard, the general mmWave standard (wireless systems operating at 10-300GHz and above, e.g., wiGig, IEEE 802.11ad,IEEE 802.11ay, etc.), techniques operating above 300GHz and THz bands (3 GPP/LTE based or IEEE 802.11p or IEEE 802.11bd and others) Vehicle-to-Vehicle (V2V) and Vehicle-to-X (V2X) and Vehicle-to-Infrastructure (V2I) and Infrastructure-to-Vehicle (I2V) communication technologies, 3GPP cellular V2X, DSRC (dedicated short range communication) communication systems, such as smart transportation systems and others (typically operating at or above 5850MHz to 5925MHz (typically up to 5935MHz after the change proposal of the CEPT report 71)), european ITS-G5 systems (i.e., DSRC based on IEEE 80211p, including ITS-G5A (i.e., operation in the european ITS band dedicated to security-related applications in the frequency range 5,875ghz to 5,905 ghz), s-G5B (i.e., operation in the frequency range 5,875ghz to the non-ITS band dedicated to security-5 MHz in the frequency range 5 ghz), s-G5B (i.e., operation in the frequency range 5,725 to the frequency range 5ghz to the frequency range 5MHz, and so on the like), DSRC-G5 systems (i.e., DSRC based on IEEE 80211p, i.e., operation in the frequency range of the frequency range 5,725 to the non-ITS band dedicated to security-5 MHz).

Aspects described herein may be used in the context of any spectrum management scheme, including private licensed spectrum, unlicensed spectrum, licensed exempt spectrum, (licensed) shared spectrum (e.g., lsa=licensed shared access in 2.3-2.4GHz, 3.4-3.6GHz, 3.6-3.8GHz and more frequencies and sas=spectrum access system/cbrs=national broadband radio system in 3.55-3.7GHz and more frequencies). Suitable portions of spectrum include IMT (international mobile telecommunications) spectrum and other types of spectrum/frequency bands, such as bands with national allocations (including 450-470MHz,902-928MHz (note: for example, in U.S. allocation (FCC part 15)), 863-868.6MHz (note: for example, in the european union allocation (ETSI EN 300 220)), 915.9-929.7MHz (note: for example, in japan), 917-923.5MHz (note: for example, in korea), 755-779MHz and 779-787MHz (note: for example, in china), 790-960MHz,1710-2025MHz,2110-2200MHz,2300-2400MHz,2.4-2.4835GHz (note: which is globally available ISM band, which is used by Wi-Fi technology family (11 b/g/n/ax) and also by bluetooth), 2500-2690MHz,698-790MHz,610-790MHz,3400-3600MHz,3400-3800MHz,3800-4200MHz,3.55-3.7GHz (note: for example, in the us assigned to public broadband radio service), 5.15-5.25GHz and 5.25-5.35GHz and 5.47-5.725GHz and 5.85GHz (note: for example, in the us assigned (FCC part 15), which is composed of four U-i, and also by bluetooth), and a total of the spectrum (note: for example, in the us assigned to the european community) and 5.725-5.725 MHz (note: the european community) is expected to operate as a system in the european community, which is the first generation of the spectrum (note: the european community) (note: the european system: for example, the european community: 25-15 th part), the spectrum: is assigned) and the frequency spectrum, 2500-60-peak (note: for example, the spectrum: 60-500 MHz: and the public. Is allocated in the european community, and the european spectrum: the public: spectrum: the spectrum: and the public. 25 and the public. Are each spectrum, and the spectrum, and each spectrum, and, 60 and, 5 and, and, it is noted that Wi-Fi systems have not been allowed in this band by 12 months of 2017. The intended supervision will be completed within the 2019-2020 time frame), IMT-advanced spectrum, IMT-2020 spectrum (intended to include the bands in the range of 3600-3800MHz, 3800-4200MHz,3.5 GHz band, 700MHz band, 24.25-86GHz band, etc.), ITS currently allocated bands to WiGig (e.g., wiGig 1 (57.24-59.40 GHz), wiGig band 2 (59.40-61.56 GHz) and wigg 3 (61.56-64 GHz) and the bands of (i.e., 55-858) according to the FCC "front-of-spectrum" 5G initiative (including 27.5-28.35GHz, 29.1-29.25GHz, 31-31.3GHz, 37-38.6GHz, 38.6-40GHz, 42-42.5GHz, 57-64GHz, 71-76GHz, 81-86GHz and 92-94GHz, etc.), ITS (intelligent transportation system) bands of 5.9GHz (typically 5.85-5.5 GHz), and 63-64GHz (intelligent transportation system) bands, currently allocated to WiGig (e.g., wiGig 1 (57.24-59.40 GHz): this band is almost universally designated for Multi-gigabit wireless systems (Multi-Gigabit Wireless Systems, MGWS)/WiGig. In the united states (FCC part 15), a total of 14GHz spectrum is allocated, whereas the european union (ETSI EN 302 567 and ETSI EN 301 217-2 for fixed P2P) allocates a total of 9GHz spectrum), 70.2GHz-71GHz band, any band between 65.88GHz and 71GHz, a band currently allocated to automotive radar applications, such as 76-81GHz, and future bands including 94-300GHz and above. Furthermore, this scheme may also be used as a secondary on bands such as the TV white space band (typically below 790 MHz), with 400MHz and 700MHz bands in particular being promising candidates. In addition to cellular applications, specific applications in the vertical market may be addressed, such as PMSE (Program Making and Special Events, programming and special events), medical, health, surgical, automotive, low latency, drone, etc. applications.

The aspects described herein may also enable hierarchical applications of the scheme, such as by introducing hierarchical prioritization (e.g., low/medium/high priority, etc.) for use by different types of users based on prioritized access to spectrum, such as highest priority to level 1 users, then level 2, then level 3, etc. users, etc.

Aspects described herein may also be applied to different single carrier or OFDM forms (CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multicarrier, FBMC), OFDMA, etc.) and in particular 3GPP NR (New Radio) by allocating OFDM carrier data bit vectors to corresponding symbol resources.

The 5G network expands beyond traditional mobile broadband services to provide a variety of new services, such as internet of things (internet of things, ioT), industrial control, autonomous driving, mission critical communications, etc., which may have ultra-low latency, ultra-high reliability, and high data capacity requirements for security and performance considerations. Some features in this document are defined for the network side, e.g. AP, eNB, NR or gnb—note that this term is commonly used in the context of 3gpp 5G and 6G communication systems and the like. Nonetheless, the UE may assume this role and act as an AP, eNB or gNB; that is, some or all of the features defined for the network device may be implemented by the UE.

As described above, NR V2X side link communication is a synchronous communication system with distributed resource allocation. The UE autonomously selects resources for side-chain transmission based on a predefined sensing and resource selection procedure implemented by a Transmitter (TX) UE. The sensing and resource selection procedures are designed to reduce potential side chain collisions (e.g., collisions or half duplex collisions) in transmissions or resource reservations. Whereas the sensing and resource selection procedure is performed by the TX UE only, irrespective of the environment on the Receiver (RX) side, the probability of side chain collisions (collisions) is not negligible. To address this problem, inter-UE coordination feedback from the RX UEs may be used to improve the resource allocation decisions made by the TX UEs and to improve the overall reliability of NR-V2X side-link communications.

In some embodiments, there are two types of transmissions that may be used to deliver inter-UE coordination feedback to TX UEs. This can be used to minimize co-channel and half-duplex problems in feedback delivery and keep feedback transmission overhead small without significantly affecting the overall system load.

There are two high-level inter-UE coordination solutions available to improve the NR V2X side-link performance: inter-UE coordination scheme #1 (side chain collision/collision avoidance) and inter-UE coordination scheme #2 (side chain collision resolution).

inter-UE coordination scheme #1 (side chain collision/collision avoidance) aims to avoid half duplex and collision problems of NR V2X communications using inter-UE coordination feedback. In this case, the UE providing inter-UE coordination feedback reports the preferred and/or non-preferred resource sets to surrounding side chain senders. The sidelink sender then applies a TX-based sensing procedure and uses the received inter-UE coordination feedback to select/reserve sidelink resources for transmission and avoid potential sidelink communication collisions.

inter-UE coordination scheme #2 (side link collision resolution) aims to resolve side link collisions that have occurred or potential future collisions detected based on resource reservation signaling using inter-UE coordination feedback. This is used to inform the sidelink sender of the detected sidelink collision through inter-UE coordination feedback so that the TX UE can perform additional retransmissions, either relinquish scheduled transmissions and reselect resources for transmission, or continue transmission on reserved resources.

Support for inter-UE coordination scheme #1 may include several aspects, including: the method includes a UE procedure/method for generation of inter-UE coordination feedback, a UE procedure/method for determining an inter-UE coordination feedback transmission type and a target UE, a UE procedure/method for transmission of inter-UE coordination feedback and content thereof, inter-UE coordination feedback reference time and aging information, reference parameters for generation of inter-UE coordination feedback, a UE procedure/method for resource selection using inter-UE coordination feedback, and inter-UE coordination signaling details.

UE behavior and content thereof for transmission of coordinated feedback between UEs

Coordinated feedback and content between independent/dependent UEs

One pending problem is whether the secondary UE (UE-a) can send independent inter-UE coordination feedback or can only send non-independent inter-UE coordination feedback (i.e., only side link transmission of inter-UE coordination payload-no other data/control signaling). In general, from a system perspective, the transmission of coordinated feedback between individual UEs may cause additional interference and half-duplex problems. However, if the TX UE requests feedback and the secondary UE has no data available for transmission, such transmission may be the only option. In a more general scenario, the secondary UE may send feedback to the TX UE along with other parallel data/traffic.

Thus, two options for coordinating feedback transmissions between UEs may be considered: coordination feedback between independent UEs and coordination feedback between non-independent UEs.

Option 1: inter-independent UE coordination feedback

In this case, feedback is sent even if the secondary UE has no other additional data for side link transmission/communication. Independent inter-UE coordination feedback may be supported and generated upon request from the TX UE, and may be applicable to both unicast and multicast communications (e.g., if the secondary UE provides inter-UE coordination feedback upon request by the TX UE, but does not have data itself to transmit to the target TX UE). The support for independent transport may not have a significant impact on the physical structure of the side link introduced in R16/R17. The ReQuest for feedback may be carried on side link control information (sidelink control information, SCI) format X (as, for example, a hybrid automatic repeat ReQuest (Hybrid Automatic Repeat ReQuest, HARQ)/channel state information (Channel State Information, CSI) feedback ReQuest) or using MAC control elements (MAC control element, MAC-CE)/RRC signaling as a physical side link shared channel (physical sidelink shared channel, PSSCH) payload.

For example, independent feedback may be used to deliver assistance information to TX UEs performing unicast or multicast semi-persistent transmissions. The TX UE may request inter-UE coordination feedback for a specific time interval (e.g., a resource selection window) in the future and provide parameters to the secondary UE to generate and receive feedback immediately before the next resource reselection for the semi-persistent procedure. Fig. 3A illustrates inter-independent UE coordination feedback in accordance with some embodiments.

Option 2: inter-dependent UE coordination feedback

In this case, inter-UE coordination feedback will be sent when the secondary UE has other/additional data for side link transmission/communication. The transmission of coordinated feedback between non-independent UEs does not have any impact on the physical structure. The feedback may be carried on the MAC CE multiplexed with other data and transmitted over the PSSCH. Fig. 3B illustrates dependent inter-UE coordination feedback in accordance with some embodiments.

Coordinated feedback between non-independent UEs may be a viable option from a system perspective, as it does not have the added problem of side chain half duplex and co-channel collisions. Meanwhile, if the TX UE requests inter-UE coordination feedback through a unicast connection, inter-UE coordination feedback may also be provided in an independent manner (e.g., using MAC CE signaling). It is also possible that the secondary UE is requested to provide unicast feedback, but only broadcast/multicast or unicast information to another UE (i.e. not intended for the TX UE). In this case, the secondary UE may use the broadcast transmission to provide inter-UE coordination feedback multiplexed with broadcast/multicast or unicast information to another UE.

The content of the inter-UE coordination feedback may depend on the type of communication used for the feedback transmission (referred to as the broadcast type), and whether the inter-UE coordination feedback is independent or dependent.

Content and container for coordinated feedback between UEs

The following containers may be considered to carry inter-UE coordination feedback to avoid side link collisions: SCI format 2 (phase 2), MAC CE, PC5 RRC signaling.

The use of MAC CEs may be desirable because MAC CEs may provide flexibility in terms of payload size and reasonable latency and may be able to multiplex coordinated feedback transmissions among multiple UEs in a single transmission along with other side link data.

The following table gives an overview of potential information fields that may be provided as part of inter-UE coordination feedback in scheme 1:

/>

/>

/>

table 1

Ordering of resource selection procedures with inter-UE coordination feedback

If the UE has multiple side-link sessions of different broadcast types, scheduling between broadcast types may be UE implementation dependent. The order of resource selection may be determined based on the priority of side-chain transmissions including coordinated feedback between associated UEs. In the case of equal transmission priorities, the following resource selection ordering rule may be applied:

Example 1: transmission with inter-UE coordination feedback > transmission without inter-UE coordination feedback (i.e., first/preferentially resource selection of transmission with inter-UE coordination feedback)

Example 2: unicast with inter-UE coordination feedback > multicast with inter-UE coordination feedback > broadcast with inter-UE coordination feedback > transmission without inter-UE coordination feedback

Example 3: broadcast with inter-UE coordination feedback > multicast with inter-UE coordination feedback > unicast with inter-UE coordination feedback > transmission without inter-UE coordination feedback

Fig. 4A illustrates ordering of priority-based resource selection procedures in accordance with some embodiments. Fig. 4B illustrates ordering of a feedback type based resource selection process in accordance with some embodiments. As shown in fig. 4B, the broadcast feedback has a higher priority than the multicast feedback, which has a higher priority than the unicast feedback, which has a higher priority than the transmission without feedback.

For subsequent selection procedures running in parallel (i.e., simultaneously) at the UE selecting the resource, the pre-selected/pre-reserved resource may be excluded from the resource selection.

Priority of coordinated feedback transmission between UEs

For inter-UE coordination scheme 1 (side chain collision avoidance), the assisting UE not only transmits or receives user/control plane data, but also transmits inter-UE coordination feedback. If the two transmissions cannot be multiplexed, the UE may decide what to send first. To address this situation, inter-UE coordination feedback may be associated with side link transmission priorities that are used to decide which transmission to make first, i.e., higher priority transmissions. In general, the following options are possible:

Option 1: conventional side link (user/control plane) transmissions take precedence over inter-UE coordinated feedback transmission/reception (which may be predefined or dependent on pre-configuration signaling).

Option 2: inter-UE coordinated feedback transmission/reception takes precedence over conventional side link transmission/reception (which may be predefined or dependent on pre-configuration signaling).

Option 3: inter-UE coordination feedback is associated with side chain transmission priority. The inter-UE coordination feedback and the side link transmission priority level of the regular side link transmission are used to determine whether transmission/reception of the inter-UE coordination feedback takes precedence over the regular side link transmission.

Option 4: inter-UE coordination feedback is multiplexed with conventional side link transmissions, and the highest priority level of the two is associated with multiplexed side link transmissions.

The priority of coordination feedback between UEs may take several different modes:

pre-configuration: in this mode, the gNB/network may use RRC signaling or an application layer to pre-configure the priority level of inter-UE coordination feedback (e.g., for broadcasting inter-UE coordination feedback).

Different broadcast types (broadcast/multicast/unicast) of inter-UE coordinated feedback may be associated with different priority levels.

Determined by the secondary UE.

Derived from the priority level of the secondary UE's side link transmission.

Derived from the priority of the transmission of the target TX UE.

The priority level of the sidelink transmission by the secondary UE based on the target TX UE requesting inter-UE coordination feedback (e.g., for unicast/multicast inter-UE coordination feedback).

Conditions for transmission of coordinated feedback between UEs

The following set of conditions may be used to enable generation and triggering of inter-UE coordination feedback for transmission:

condition 1: inter-UE coordination feedback is enabled for each side chain resource pool. Furthermore, the following configuration for a particular inter-UE coordination feedback type may be provided: configuration of coordinated feedback (if not predefined) between independent or non-independent UEs enabled in the resource pool; configuration of inter-UE coordination feedback enabled in the resource pool based on semi-persistent only/dynamic only or both semi-persistent and dynamic resource allocation (if not predefined); and a configuration (if not predefined) of the type/destination or format of coordinated feedback transmissions among the enabled UEs.

Condition 2: the UE receives a request from other UEs (e.g., UE group members) to provide inter-UE coordination feedback of a particular type.

Condition 3: the UEs are configured by higher layers to provide inter-UE coordination feedback and have available data for side link transmission (dependent inter-UE coordination feedback).

Condition 4: the higher layer triggers the transmission of coordinated feedback between UEs based on timer conditions. This condition may be that a pre-configured amount of time has elapsed since the previous trigger of transmission of coordination feedback between UEs.

Condition 5: the higher layer triggers inter-UE coordination feedback based on the distance travelled condition. This condition may be that a preconfigured distance has been travelled since the last trigger/transmission of inter-UE coordination feedback.

Condition 6: configuration settings for generating inter-UE coordination feedback, e.g., reference configuration (i.e., a set of sensing-based preferred/non-preferred resources for a side link resource selection procedure) for inter-UE coordination feedback are provided to the UE. Alternatively, the UE may use default settings.

Condition 7: such as side-chain transmissions configured by higher layer signaling or by UEs and/or gnbs and which activate inter-UE coordination feedback.

Condition 8: the status of congestion control indicates that the channel is not severely overloaded. In this case, inter-UE coordination feedback is generated based on a constant bit rate (constant bit rate, CBR) setting (i.e., if the CBR measurement is within a preconfigured range).

Condition 9: the UE has selected or reserved sidelink resources for its own potential sidelink transmissions and wishes to update other UEs to avoid potential sidelink collisions.

Condition 10: the UE generates inter-UE coordination feedback if 1) a side link reference signal received power (sidelink Reference Signal Received Power, SL-RSRP) threshold for constructing the set of resources (preferred/non-preferred) is above/below a preconfigured value of the SL-RSPR threshold configured to trigger inter-UE coordination feedback, and/or 2) the set size is within a preconfigured range [ X1, X2], which may be defined with respect to the number of resources in the selected time interval.

The above set of conditions may be applied in any possible combination to determine when a UE may generate inter-UE coordination feedback.

UE procedure/method for resource selection with inter-UE coordination feedback

Each TX UE may receive inter-UE coordination feedback from one or more UEs. Furthermore, the feedback may arrive at different time instances and may include auxiliary information with different delay/aging times and/or auxiliary information generated for different reference configuration settings for the feedback generation parameters. In order to optimize the TX-based resource selection procedure by considering inter-UE coordination feedback, TX UE behavior/procedure should be defined as to how to process feedback information.

In general, side-link communication based on TX UE sensing and coordinated feedback between UEs may include the following operations:

request for coordinated feedback between UEs

Initial pre-processing of feedback information at TX UE (feedback translation)

Selection of secondary UE(s) and inter-UE coordination report(s), including filtering of feedback information sources and filtering of feedback information

Feedback applications for TX UE resource selection, which include feedback aggregation/combining and resource selection based on TX UE sensing and inter-UE coordination feedback.

Depending on the implementation, some operations or sub-operations may be skipped, combined into a single processing step. Further, the order of operations may be changed.

Request for coordinated feedback between UEs

In the case of unicast or multicast transmissions, the TX UE may explicitly request the target RX UE to generate inter-UE coordination feedback. In this case, the TX UE generates an inter-UE coordination feedback request, which may include the following information:

the number of sub-channels L per side link preferred/non-preferred resources. These values may also be pre-configured in advance to the UE providing the feedback or default settings may be assigned.

The side link transmission priority value is used for assisting the UE side in resource selection. These values may also be pre-configured in advance to the UE providing the feedback or default settings may be assigned.

The resource selection window parameters (start time + duration or/end time) for feedback generation or the boundaries for resource selection window determination. This may be configured in a subframe/slot/transmission time index (transmission time index, TTI) or may be configured to a TX UE resource selection window.

The sensing window parameters (start time + duration or/end time) for feedback generation may include a minimum sensing window required.

The size of the resource set in% (e.g., the smallest size of the resource set(s) -5,10,20,30,40,50, … N <100% of the resources in the selection window).

Threshold type and value (e.g., SL-RSRP _preferred ，SL-RSRP _{non-preferred} ). This can be used to use SCI decoding and side link measurementPreferred and non-preferred resource sets are constructed.

A resource reservation period or a set of resource reservation periods for feedback generation.

Reference number of potential future collisions considered in feedback generation. This may be a fixed value, per cycle, or where each is below a threshold after the end of the window.

The type of feedback report is semi-persistent/dynamic transmission or both used for feedback generation.

The above values may also be pre-configured in advance to the UE providing the feedback, or default settings may be assigned. If the TX UE performs semi-persistent transmission, the secondary feedback request may be transmitted immediately prior to the impending resource reselection event. The TX UE knows this time instance so that the feedback provides up-to-date information.

Initial pre-processing of feedback information at TX UE (feedback translation)

Based on the information indicated in the feedback, information pre-processing at the TX UE may be used prior to feedback selection and further feedback information processing.

The information preprocessing may include:

feedback information translation

If the parameters transmitted by the TX UE are different from the parameters used by the secondary UE to generate the feedback, the feedback information may be preprocessed and aligned with the parameters used by the TX UE for sensing and resource selection (e.g., the resource size of the TX is different from the resource size used to generate the feedback). The TX UE may apply at least the following procedures:

1) Resource size alignment (translating reference resources in feedback to TX UE resources)

2) Resource selection window alignment (translating reference resources in feedback to resources from TX UE resource selection window)

3) SL-RSRP measurement alignment (if resources in feedback are associated with SL-RSRP measurements, additional filtering can be performed on the feedback resources to modify the set of resources)

Examples of resource size alignment procedure

The reference resource size of feedback < the resource size of TX UE. Fig. 5A illustrates a resource size alignment procedure according to some embodiments. Fig. 5A illustrates an example in which a reference resource for feedback is composed of L subchannels and a resource for transmission is composed of N subchannels, where n=2l. In this case, the TX resource contains two adjacent feedback resources. If two adjacent feedback resources belong to a set of resources, then the adjacent feedback resources can be considered as TX resources of the same set. Fig. 5B illustrates another resource size alignment procedure in accordance with some embodiments. In this case, if one of two adjacent feedback resources belongs to a resource set, the adjacent feedback resources may be regarded as TX resources of the same set.

The reference resource size of feedback > the resource size of TX UE. In this case, any combination of N adjacent subchannels among the L subchannels may be used as the TX resource.

Selection of a coordination report between auxiliary UE(s) and UE(s) by TX UE

The selection of the secondary UE(s) and inter-UE coordination report(s) may be accomplished in two operations: selection of UEs with feedback information (filtering feedback information sources) and filtering of feedback information. Depending on the implementation, these operations may be combined into a single operation.

Selection of UEs with feedback information

The following set of parameters may be configured to select UEs with feedback information for further processing:

radio range (e.g., SL-RSRP range) to a UE providing inter-UE coordinated feedback (applicable to sensing-based preferred/non-preferred resource sets)

Location information, which may include distance and/or angular ranges, as well as other location attributes (e.g., coordinates, altitude, street location, etc.)

Relative velocity/velocity vectors relative to the UEs providing inter-UE coordination feedback may include directions of travel, e.g., relative to directions of travel of the UEs providing inter-UE coordination feedback, or absolute directions (north/south/west/east)

Filtering feedback information

The feedback report may be selected using the following parameters:

feedback source/destination ID and broadcast type (unicast/multicast/broadcast)

Feedback type (dynamic/semi-persistent/both)

Feedback delay/aging time

Feedback aging information may be evaluated to decide whether to consider a given feedback or prioritize the most recent feedback. Option 1: feedback aging (one transmission per transport block (transmission block, TB)) is only evaluated at initial resource selection. In this case, the same set of feedback or feedback sources is used to determine the assistance information that may be further used in the resource selection. Option 2: the feedback aging value is evaluated at each resource (re) selection/(re) evaluation time. In this case, the auxiliary information source may change in time at each instant, as the most recent information from a different set of sources may be selected.

Resource indication window

A feedback resource selection window (start/end time). The following feedback may be selected for further processing: the feedback resource selection window overlaps with the TX UE resource selection window with at least N time resources or a portion of all time resources in the selection window.

Resource reservation period of feedback

Resource size for feedback generation

Reference threshold (type and value)

Feedback generated priority values

Feedback application of TX UE resource selection

Review of R16/R17 resource allocation procedure

Fig. 6 illustrates a block diagram of an NR V2X side chain resource allocation procedure according to some embodiments. In fig. 6, the sensed data is processed to exclude reserved resources in the resource selection window and form a TX-based candidate set of resources S for transmission SA _A . Then, N resources are selected for use by set R _S Potential transmission of the representation. These resources are re-evaluated with the most recent sensing information to finally determine the resources to be used for transmission and reservation.

Solution for considering R16/R17 resource allocation procedure

Fig. 7A illustrates a block diagram of a first option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments. Fig. 7B illustrates a block diagram of a second option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments. Fig. 7C illustrates a block diagram of a third option for an NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments. Fig. 7D illustrates a block diagram of a fourth option for NR V2X side chain resource allocation with inter-UE coordination feedback according to some embodiments. Fig. 7E illustrates a block diagram of a fifth option for NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments. Fig. 7F illustrates a block diagram of a sixth option for NR V2X side chain resource allocation with inter-UE coordination feedback according to some embodiments. Fig. 7G illustrates a block diagram of a seventh option of an NR V2X side chain resource allocation procedure with inter-UE coordination feedback according to some embodiments.

One difference between these options is in which procedure the set of resources provided by the inter-UE coordination feedback is considered for resource selection. Specifically, in option 1 (fig. 7A), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for resource exclusion and candidate resource set S _C Is formed by the steps of (a). In option 2 (fig. 7B), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for initial resource selection to produce resource set R _S . In option 3 (fig. 7C), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for resource exclusion and candidate resource set S _C And for initial resource selection to produce resource set R _S . In option 4 (fig. 7D), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for resource re-evaluation to produceResource set R _TX/RSV . In option 5 (fig. 7E), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for resource exclusion to form a candidate resource set S _C And is used for resource re-evaluation to produce a resource set R _TX/RSV . In option 6 (fig. 7F), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for initial resource selection to form a candidate resource set R _S And is used for resource re-evaluation to produce a resource set R _TX/RSV . In option 7 (fig. 7G), the inter-UE coordination feedback information ((set of resources S) S _B ) Is used for resource exclusion and candidate resource set S _C, For initial resource selection to form candidate resource set R _S And ultimately used for resource re-evaluation to produce resource set R _TX/RSV 。

inter-UE coordination feedback content

The assisting UE may report the following information in an inter-UE coordination feedback message to assist in resource selection at the TX UE:

identified preferred resource set-set S _B-P (time-frequency or time resources recommended from the RX UE perspective within the resource pool and time interval).

Identified non-preferred resource set-set S _B-NP (time-frequency or time resources not recommended from the RX UE perspective within the resource pool and time interval). Set S of non-preferred resources _B-NP Can be divided into two resource subsets: resource set S _B1-NP This is a resource determined by the assisting UE based on the radio sensing and resource exclusion/selection procedure, and may be constructed in accordance with the R16 sensing and resource exclusion procedure; resource set S _B2-NP This is a resource that assists the UE in selecting or reserving for potential side-link or uplink transmissions that affect the UE side-link reception capability.

A resource selection metric threshold (e.g., SL-RSRP threshold, distance threshold) value associated with each reported set of resources. If a fixed threshold is configured for the secondary UE (i.e., not updated by the secondary UE), then this information need not be reported. If the initial threshold is configured and further incremented/decremented by the secondary UE to identify the resource set, the updated threshold for the resource set used to generate the report may also be reported back to the TX UE.

Resource selection metrics (e.g., SL-RSRP measurements, distances) associated with the identified resources of each resource set. The resource selection metric becomes meaningful for the resource selection on the TX UE side if the secondary UE is the target receiver UE. The SL-RSRP of concurrent transmissions measured at the target RX UE has the concept of interference power, which may be used to estimate the communication link quality, decide the feasibility of transmissions at a particular resource, and may help adjust transmission parameters. If the assisting UE is not the target recipient UE, the resource selection metric from this UE may be implemented with additional information (e.g., distance, SL-RSRP measurements) that characterizes the proximity of the assisting UE to the target recipient. This additional information may be used to characterize the target recipient environment.

Once feedback with preferred and non-preferred resource sets is preprocessed, one of two alternatives may be used to use the feedback in the final resource selection procedure. Alternative 1: independent feedback processing for resource exclusion/(re) selection/(re) evaluation. In this case, the preferred (and/or non-preferred) resource sets indicated in each feedback may be processed independently. Alternative 2: feedback combining/aggregation for resource exclusion/(re) selection/(re) assessment. In this case, the preferred (and/or non-preferred) resource sets may be aggregated over a plurality of pre-selected feedback reports.

Feedback resource set combination/aggregation of resource sets

Scene 1: only the resources are reported without additional association metrics (e.g., SL-RSRP, distance).

In this case, multiple alternatives may be used to generate the combined resource set:

alternative 1: a combined resource set is an intersection of input resource sets:

S _Combined ＝S ₁ ∩S ₂ ∩…∩S _K-1 ∩S _K

alternative 2: the combined resource set is the union of the input resource sets:

S _Combined ＝S ₁ ∪S ₂ ∪…∪S _K-1 ∪S _K

alternative 3: a combined resource set is generated based on the resource occurrence. For each resource, the occurrence of the resource in the report may be estimated and used to decide whether a particular resource should be included in (or excluded from) the combined set of resources. For example, only the occurrence is above a preconfigured threshold value _B May be included into the combined set of resources. Here, thr _B Is a pre-configured threshold for determining whether resources are included in (or excluded from) the combined set of resources.

Scene 2: the reported resources are associated with additional metrics (e.g., SL-RSRP, distance).

In this case, if the reported additional resource metric is below (e.g., SL-RSRP of the preferred resource set) or above (e.g., SL-RSRP of the non-preferred resource set) (pre-configured threshold), the resource may be included in (or excluded from) the combined resource set.

In another embodiment, the TX UE may estimate and apply a threshold to estimate the resource occurrence for a given metric threshold.

Determining a preferred/non-preferred resource type based on processing multiple feedback received by a TX UE (combined feedback report Notice-resource set

Resource set based on inter-UE coordination feedback _SB The formation of (a) depends on the reported classification of the resource, i.e. whether the resource can be regarded as preferred or non-preferred.

In determining non-preferred resources based on processing of multiple feedback transmissions received by the TX UE, several options may be used:

for the case where the set of resources is reported without additional metrics (SL-RSRP, distance), the reported resource R is if the following occurs _x,y Is considered to be non-preferred:

scene 1: the resource sets from different sources (auxiliary UEs) are handled separately and R _x,y Is from the selected auxiliary UE _k Received non-preferred resource S _B-NP-k Is a member of R _x,y Is a slave to the auxiliary UE [ UE ] ₁ ..UE _K ]Received non-preferred resource set S _B-NP-1.. S _B-NP-K ]At least one set S of (a) _B-NP-k Is a member of R _x,y Is a slave to the auxiliary UE [ UE ] ₁ ..UE _K ]All non-preferred resource sets received S _B-NP-1.. S _B-NP-K ]And R is a member of the group _x,y Is a slave to the auxiliary UE [ UE ] ₁ ..UE _K ]Received K non-preferred resource sets S _B-NP-1.. S _B-NP-K ]Members of N groups in (a).

Scene 2: aggregation/combining of resource sets from different sources (secondary UEs). R is R _x,y Is to combine non-preferred resource sets S _{B-NP-Combined} Is a member of the group (a). For the case when reporting the set of resources and the corresponding additional metrics, the reported resource R is if _x,y Is considered to be non-preferred:

scene 1: sets of resources from different sources are handled separately. From the selected secondary UE _k Received non-preferred resource set S _B-NP-k And resource R _x,y Associated auxiliary measure M _Rx,y-k >M _Thr . From the auxiliary UE [ UE ] ₁ ..UE _K ]Received non-preferred resource set S _B-NP-1.. S _B-NP-K ]At least one set S of (a) _B-NP-k And resource R _x,y Associated auxiliary measure M _Rx,y-k >M _Thr . From the auxiliary UE [ UE ] ₁ ..UE _K ]Received non-preferred resource set S _B-NP-1.. S _B-NP-K ]Associated reporting auxiliary metric M in all sets of (a) _Rx,y-k >M _Thr . From the auxiliary UE [ UE ] ₁ ..UE _K ]Received K non-preferred resource sets S _B-NP-1.. S _B-NP-K ]Associated reporting assistance metrics M in N groups of _Rx,y-k >M _Thr 。

Scene 2: aggregating resource sets from different sources. From the auxiliary UE _k All non-preferred resource sets S received _B-NP-k In association reporting auxiliary metric M _{Rx,y-Combined} >M _Thr . The above procedure may also be applied to determine preferred resources based on the process of coordinating feedback among multiple UEs.

Resource exclusion and TX-based sensing based on non-preferred resource sets to form candidate resources for resource selection Source collection

In this section, modifications of the resource exclusion procedure that take into account inter-UE coordination feedback from the secondary UEs are discussed. In conventional operation, the UE generates a candidate set of resources S using the sensing results determined via the resource exclusion procedure _A The set is used to further select candidate resources for transmission. Fig. 8A illustrates a resource exclusion procedure that does not use inter-UE coordination resource sets, in accordance with some embodiments.

In providing feedback, the TX UE may generate two or more sets of resources (up to N): set S _A : a set of resources (a set of candidate resources) after the resource exclusion applied to the TX UE sensing data; set S _B : set of resource(s) from inter-UE coordination feedback; set S _B-k : from UE _k Resource sets of coordinated feedback between UEs (k=1 for single UE or aggregate reporting process); set S _C : resource set (set of candidate resources) and non-preferred resource set (S) (set S) after resource exclusion applied to TX UE sensing data _B-k ). Set S may be generated using a set of preferred and/or non-preferred resources _B-k . In one embodiment, if the resource R reported by the assisting UE(s) _x,y Classified as non-preferred, then the resource is added to the resource set S _B-k . Otherwise, if the resource is classified as preferred, the resource should not be added or should be added from set S _B-k Is removed.

The following options may be used to enhance the resource exclusion procedure:

option 1: regardless of the result of the resource exclusion procedure that handles the TX sense result, the data will be receivedSource candidate resource set S _A Excluding non-preferred resources from inter-UE coordination feedback-set S _B (or set S) _B-k ) As shown in fig. 8B. Fig. 8B illustrates a resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments.

Option 2: processing TX sensing results independently to generate candidate set of resources S _A . Fig. 8C illustrates another resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments. The candidate resource set is further selected from the non-preferred or preferred resource set S _B-k Combining to obtain a UE/feedback specific set of candidate resources S _C-k . Finally, as shown in FIG. 8C, all candidate resources S are aggregated _C-k Combined together (and optionally with a TX candidate resource set S _A Combined together) to generate a candidate set of resources S _C . Adding a set S at the final stage _A To ensure if S is combined _C-k Final set S thereafter _C Too small, set S _A As a backup option, or at least resources may be borrowed from the collection.

Option 3: processing TX sensing results independently to generate candidate set of resources S _A . Fig. 8D illustrates another resource exclusion procedure using inter-UE coordinated resource sets in accordance with some embodiments. The candidate resource set is further selected from the non-preferred or preferred resource set S _B Combining to obtain a UE/feedback specific set of candidate resources S _C As shown in fig. 8D. Set S _B By combining a set of resources S from multiple feedbacks _B-k And (3) generating. If during the final stage of combining, the combined set of resources S _C Too small, then the set of resources S may be used _A As a backup (i.e. set S _C Set S = _A ) Or at least can borrow from the set S _A Form a resource set S of resources of (1) _C 。

Although embodiments have been described with reference to specific example embodiments, it will be evident that various modifications and changes may be made to these embodiments without departing from the broader scope of the disclosure. The specification and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense. The accompanying drawings that form a part hereof show, by way of illustration and not of limitation, specific embodiments in which the subject matter may be practiced. The embodiments illustrated are described in sufficient detail to enable those skilled in the art to practice the teachings disclosed herein. Other embodiments may be utilized and derived therefrom, such that structural and logical substitutions and changes may be made without departing from the scope of this disclosure. This detailed description is, therefore, not to be taken in a limiting sense, and the scope of the various embodiments is defined only by the appended claims, along with the full range of equivalents to which such claims are entitled.

The subject matter may be referred to herein, individually and/or collectively, by the term "embodiment" merely for convenience and without intending to voluntarily limit the scope of this application to any single inventive concept if more than one is in fact disclosed. Thus, although specific embodiments have been illustrated and described herein, it should be appreciated that any arrangement calculated to achieve the same purpose may be substituted for the specific embodiments shown. This disclosure is intended to cover any and all adaptations or variations of various embodiments. Combinations of the above embodiments, and other embodiments not specifically described herein, will be apparent to those of skill in the art upon reviewing the above description.

In this document, the terms "a" or "an" are used, as is common in patent documents, to include one or more than one, independent of any other instance or use of "at least one" or "one or more". In this document, the term "or" is used to refer to a non-exclusive or, such that "a or B" includes "a, but no B", "B, but no a" and "a and B", unless otherwise indicated. In this document, the terms "comprise" and "wherein" are used as plain english equivalents of the respective terms "comprising" and "wherein. In addition, in the appended claims, the terms "including" and "comprising" are open-ended, that is, a system, UE, article, composition, formulation, or process that includes other elements in addition to those listed after such term in a claim is still considered to fall within the scope of that claim. In addition, in the appended claims, the terms "first", "second", and "third", etc. are used merely as labels, and are not intended to impose numerical requirements on their objects.

The abstract of the disclosure is provided to comply with 37c.f.r. ≡1.72 (b), which requires an abstract that will allow the reader to quickly ascertain the nature of the technical disclosure. It was submitted under the following understanding: it is submitted with the understanding that it will not be used to interpret or limit the scope or meaning of the claims. Furthermore, in the foregoing detailed description, it can be seen that various features are grouped together in a single embodiment for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed embodiments require more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive subject matter lies in less than all features of a single disclosed embodiment. Thus, the following claims are hereby incorporated into the detailed description, with each claim standing on its own as a separate embodiment.

Claims (20)

1. An apparatus for a User Equipment (UE), the apparatus comprising:

processing circuitry configured to configure the UE to:

receiving a request for inter-UE coordination feedback from another UE, the inter-UE coordination feedback including a preferred set of resources and a non-preferred set of resources for vehicle-to-everything (V2X) side link communication;

Determining whether the inter-UE coordination feedback is allowed to be transmitted to the other UE as independent inter-UE coordination feedback or is allowed to be transmitted to the other UE only as dependent inter-UE coordination feedback, in which case the inter-UE coordination feedback is allowed to be transmitted to the other UE separately from other side-chain transmissions to the other UE, in which case the inter-UE coordination feedback is transmitted to the other UE together with data; and is also provided with

Transmitting the inter-UE coordination feedback to the other UE depending on whether the inter-UE coordination feedback is allowed to be transmitted to the other UE as independent inter-UE coordination feedback or is only allowed to be transmitted to the other UE as dependent inter-UE coordination feedback; and

and a memory configured to store the inter-UE coordination feedback.

2. The apparatus of claim 1, wherein:

the request includes parameters for transmission of coordinated feedback between the UEs,

the parameters include a time interval after receiving the request, for transmitting the inter-UE coordination feedback,

The time interval after receiving the request is aligned in time with a resource reselection activity of the other UE, and

in response to receiving the request, the processing circuitry is further configured to configure the UE to send the inter-UE coordination feedback to the other UE at the time interval after receiving the request.

3. The apparatus of claim 1, wherein the processing circuitry is further configured to configure the UE to: the inter-UE coordination feedback is transmitted on a physical side link shared channel (PSSCH) using a Medium Access Control (MAC) control element (MAC-CE), the inter-UE coordination feedback being multiplexed with the data in response to determining that the inter-UE coordination feedback is non-independent inter-UE coordination feedback.

4. The apparatus of claim 1, wherein the processing circuitry is further configured to configure the UE to: transmitting content of the inter-UE coordination feedback that depends on a broadcast type selected from a group of broadcast types comprising: broadcast transmission, multicast transmission, and unicast transmission.

5. The apparatus of claim 4, wherein the processing circuitry is further configured to configure the UE to select the content from a set of content comprising: header information; preferred resource set (set 1); non-preferred resource set (set 2); reference to a resource size; the sizes of sets 1 and 2; reference signal received power (SL-RSRP), channel Quality Index (CQI), or range threshold and value of sets 1 and 2; a reference priority; a resource selection window or a starting slot index of a reporting resource set; the start and end of the sensing window; sensing a parameter; at least one of a side link transmit or receive pool Identifier (ID); dynamic transmission for feedback consideration; semi-persistent transmission for feedback consideration; a set of resource reservation periods; and at least one of a source or destination ID.

6. The apparatus of claim 1, wherein the processing circuitry is further configured to configure the UE to send the inter-UE coordination feedback for side link collision avoidance in at least one of: side link control information (SCI) format 2 (stage 2), medium Access Control (MAC) control element (MAC-CE), or PC5 Radio Resource Control (RRC) signaling, or distributed across multiple containers.

7. The apparatus of claim 1, wherein the processing circuitry is further configured to configure the UE to: side link transmissions are prioritized between different broadcast types including the inter-UE coordination feedback and side link transmissions with the inter-UE coordination feedback are set to a higher priority than side link transmissions without the inter-UE coordination feedback, including broadcast transmissions, multicast transmissions, and unicast transmissions.

8. An apparatus for a User Equipment (UE), the apparatus comprising:

processing circuitry configured to configure the UE to:

sending a request for inter-UE coordination feedback to another UE, the inter-UE coordination feedback including a preferred set of resources and a non-preferred set of resources for vehicle-to-everything (V2X) side link communication;

Receiving the inter-UE coordination feedback from the other UE;

determining that the parameters of V2X side chain transmissions are different from parameters used to generate the inter-UE coordination feedback;

responsive to determining that the parameters of the V2X side chain transmission are different from parameters used to generate the inter-UE coordination feedback, translating the inter-UE coordination feedback such that the inter-UE coordination feedback is aligned with parameters used for sensing and resource selection;

selecting an auxiliary UE and an inter-UE coordination report based on the inter-UE coordination feedback;

determining a resource selection based on the inter-UE coordination feedback; and is also provided with

Transmitting V2X side link transmissions using resources determined using the resource selection; and a memory configured to store the inter-UE coordination feedback.

9. The apparatus of claim 8, wherein the request for inter-UE coordination feedback comprises parameters to be used for the inter-UE coordination feedback, the parameters to be used for the inter-UE coordination feedback selected from a set of parameters comprising: the number of sub-channels per side chain preferred or non-preferred resources, the side chain transmission priority value for resource selection, the resource selection window parameters for feedback generation for resource selection window determination, the sensing window parameters for feedback generation, the size of the resource set, the threshold type and value, the resource reservation period for feedback generation, the reference number of potential future collisions considered in feedback generation, and the type of feedback report.

10. The apparatus of claim 8, wherein to translate the inter-UE coordination feedback such that the inter-UE coordination feedback is aligned with parameters for sensing and resource selection, the processing circuitry is configured to configure the UE to: the size of the reference resources in the inter-UE coordination feedback are translated to V2X side chain resources and the reference resources in the inter-UE coordination feedback are translated to resource selection window resources.

11. The apparatus of claim 10, wherein to translate the size of the reference resource in the inter-UE coordination feedback to a V2X side chain resource, the processing circuitry is configured to configure the UE to:

regarding a reference resource size that is less than a Transmit (TX) UE resource size resource, in response to determining that all neighboring reference resources that make up the TX UE resource or a predetermined number of resources that make up the TX UE resource have been reported, treating the TX UE resource as reported; and is also provided with

For a reference resource size that is greater than a TX UE resource size resource, in response to determining that the reference resource size that includes the TX UE resource is reported, the TX UE resource is considered as reported.

12. The apparatus of claim 10, wherein to translate reference resources in the inter-UE coordination feedback to the resource selection window resources, the processing circuitry is configured to configure the UE to select one of a starting slot, a subframe, or a Transmission Time Index (TTI) as a reference time.

13. The apparatus of claim 8, wherein:

to select the secondary UE, the processing circuitry is configured to configure the UE to use at least one of a radio range of the secondary UE, location information of the secondary UE, a relative speed of the secondary UE with respect to the UE, or a direction of travel of the secondary UE, and

to select the inter-UE coordination report, the processing circuitry is configured to configure the UE to filter the inter-UE coordination report with at least one reporting parameter from a group of reporting parameters comprising: the feedback source or destination identifies and broadcasts the type, feedback delay, resource indication window, feedback resource selection window, resource reservation period for feedback generation, resource size for feedback generation, type and value of reference threshold, and priority value for feedback generation.

14. The apparatus of claim 8, wherein the processing circuitry is configured to configure the UE to use the inter-UE coordination feedback for at least one of:

the resource exclusion and formation of the candidate resource set,

the initial resource selection used to generate the set of resources,

The resource exclusion and formation of the candidate resource set and the initial resource selection,

the resource re-assessment used to generate the resource collection,

the resource elimination used to form the candidate resource set and the resource re-evaluation used to generate the resource set,

initial resource selection to form a candidate resource set and resource re-evaluation to produce a resource set, or

The resource exclusion and formation of the candidate resource set, the initial resource selection used to form the candidate resource set, and the resource re-evaluation used to generate the resource set.

15. The apparatus of claim 8, wherein the processing circuitry is configured to configure the UE to receive and combine inter-UE coordination feedback from a plurality of UEs to form a combined set of resources that is one of:

an intersection or union of sets of resources for inter-UE coordinated feedback from the plurality of UEs, or

The occurrence of a resource in a set of resources of inter-UE coordination feedback from the plurality of UEs, wherein for each resource the number of occurrences of the resource in inter-UE coordination feedback from the plurality of UEs is used to decide whether the resource is included in the set of combined resources.

16. The apparatus of claim 8, wherein:

The processing circuitry is configured to configure the UE to determine a preferred set of resources and a non-preferred set of resources from inter-UE coordination feedback from a plurality of UEs,

the non-preferred set of resources includes:

for a set of non-preferred resources from the plurality of UEs processed individually by the processing circuitry, a predetermined number of occurrences of a particular non-preferred resource within the set of non-preferred resources, an

For non-preferred sets of resources from the plurality of UEs aggregated by the processing circuitry to a combined non-preferred set of resources and subsequently processed, a particular non-preferred resource within the combined non-preferred set of resources, and

the preferred set of resources includes:

for a set of preferred resources from the plurality of UEs that are individually processed by the processing circuitry, a predetermined number of occurrences of a particular preferred resource within the set of preferred resources, an

For a set of combined preferred resources and subsequently processed preferred resources from the plurality of UEs, aggregated by the processing circuitry, a particular preferred resource within the set of combined preferred resources.

17. The apparatus of claim 8, wherein:

the processing circuitry is configured to configure the UE to determine a resource type and an additional metric for resources received from coordination feedback among a plurality of UEs from the plurality of UEs,

The resource types are preferred resources and non-preferred resources,

the non-preferred resources include:

for a set of non-preferred resources from the plurality of UEs processed individually by the processing circuitry, a predetermined number of occurrences of a particular non-preferred resource within the set of non-preferred resources having a non-preferred metric greater than a non-preferred threshold metric, an

For a set of non-preferred resources from the plurality of UEs that are aggregated by the processing circuitry to be processed into a combined set of non-preferred resources and subsequently processed, the combined set of non-preferred resources having a non-preferred metric greater than the non-preferred threshold metric, and the preferred set of resources comprising:

for a set of preferred resources from the plurality of UEs processed individually by the processing circuitry, a predetermined number of occurrences of a particular preferred resource having a preferred metric less than a preferred threshold metric within the set of preferred resources, an

For a set of preferred resources from the plurality of UEs that are aggregated by the processing circuitry to process a set of combined preferred resources and subsequently processed, a particular preferred resource within the set of combined preferred resources that has a preferred metric that is less than the preferred threshold metric.

18. The apparatus of claim 8, wherein:

the processing circuitry is configured to configure the UE to:

forming a candidate set of resources for resource selection from a plurality of inter-UE coordination feedback from a plurality of UEs based on resource exclusion; and is also provided with

Sensing is performed based on the candidate set of resources.

19. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a User Equipment (UE), the one or more processors, when executed, configure the UE to:

receiving a request for inter-UE coordination feedback from another UE, the inter-UE coordination feedback including a preferred set of resources and a non-preferred set of resources for vehicle-to-everything (V2X) side link communication;

determining whether the inter-UE coordination feedback is allowed to be transmitted to the other UE as independent inter-UE coordination feedback or is allowed to be transmitted to the other UE only as dependent inter-UE coordination feedback, in which case the inter-UE coordination feedback is allowed to be transmitted to the other UE separately from other side-chain transmissions to the other UE, in which case the inter-UE coordination feedback is transmitted to the other UE together with data; and is also provided with

The inter-UE coordination feedback is sent to the other UE depending on whether the inter-UE coordination feedback is allowed to be transmitted to the other UE as independent inter-UE coordination feedback or is only allowed to be transmitted to the other UE as dependent inter-UE coordination feedback.

20. The non-transitory computer-readable storage medium of claim 19, wherein the request includes parameters for transmission of coordinated feedback between the UEs,

the parameters include a time interval after receiving the request, for transmitting the inter-UE coordination feedback,

the time interval after receiving the request is aligned in time with a resource reselection activity of the other UE, and

in response to receiving the request, the one or more processors further configure the UE to send the inter-UE coordination feedback to the other UE at the time interval after receiving the request when the instructions are executed.