Determination of Collisions and Contention in Sidelink Communication

Abstract

A computer-readable storage medium stores instructions for configuring a UE for sidelink operation in a 5G NR network and causing the UE to perform operations including encoding a first SCI for transmission. The first SCI includes a first resource reservation for a subsequent sidelink transmission by the UE in a preselected slot. A second SCI received from a second UE is decoded. The second SCI includes a second resource reservation for a subsequent sidelink transmission by the second UE in the preselected slot. A reservation conflict is detected based on the first resource reservation and the second resource reservation using the preselected slot. A third SCI is encoded for transmission based on the detection of the reservation conflict. The third SCI includes a modified version of the first resource reservation for a subsequent sidelink transmission by the UE.

Description

Technical Field

[0001] [Cross - Reference to Related Applications] This application claims the benefit of priority under 35 U.S.C. § 119(e) to the following U.S. provisional patent applications.

[0002] One of those U.S. provisional patent applications is U.S. Provisional Patent Application No. 63 / 169,711, filed on April 1, 2021, entitled "Method for Determining Sidelink Collisions and Half - Duplex Contention for Reliable Sidelink Communication Using Cooperative Feedback between UEs".

[0003] Another of those U.S. provisional patent applications is U.S. Provisional Patent Application No. 63 / 169,759, filed on April 1, 2021, entitled "Method for Determining Sidelink Collisions and Half - Duplex Contention with Multiple Transmitting UEs and Enhanced Resource (Re) - Selection Procedures".

[0004] Each of the two above - mentioned U.S. provisional patent applications is hereby incorporated by reference in its entirety.

[0005] [Technical Field] A plurality of aspects relate to wireless communication. Some of those aspects relate to 3GPP (Registered Trademark) (3rd Generation Partnership Project) networks, 3GPP LTE (Long Term Evolution) networks, 3GPP LTE-A (LTE Advanced) networks, (MulteFire, LTE-U), and 5th Generation (5G) networks, and 5G New Radio (NR) (or, 5G-NR) networks, 5G NR license-exempt spectrum (NR-U) networks and other license-exempt networks such as Wi-Fi, 5G-LTE networks including CBRS (OnGo), Beyond 5G networks including CBRS (OnGo), etc. Other aspects are related to mechanisms for determining sidelink (SL) collisions and half-duplex conflicts for reliable SL communication using inter-UE coordination feedback. Additional aspects are related to mechanisms for determining SL collisions and half-duplex conflicts by a plurality of transmitting UEs and enhanced resource (re-)selection procedures.

Background Art

[0006] Mobile communication has evolved remarkably from the early voice systems to today's highly sophisticated and integrated communication platforms. With the increasing number of different types of devices communicating with various network devices, the usage of 3GPP LTE systems is on the rise. The penetration of mobile devices (such as user equipment or UE) in modern society continuously evokes the demand for a wide variety of network devices in many different environments. The fifth-generation (5G) wireless system is about to emerge and is expected to enable even greater speeds, connectivity, and user usability. The next-generation 5G network (or NR network) is expected to improve throughput, coverage, and robustness, while reducing latency, as well as operating and capital expenditures. The 5G-NR network is continuously evolving based on 3GPP LTE-Advanced with additional and potential new radio access technologies (RAT), and as a result, it will enrich people's lives with seamless wireless connectivity solutions that deliver high-speed and rich content and services. Since the current cellular network frequencies are saturated, higher frequencies such as millimeter-wave (mmWave) frequencies may be beneficial due to their large bandwidths.

[0007] Potential LTE operations in unlicensed spectrum include, but are not limited to, LTE operations in unlicensed spectrum by or based on dual connectivity (DC) and independent LTE systems in unlicensed spectrum. LTE-based technologies operate only in unlicensed spectrum according to those potential LTE operations, referred to as MulteFire, without the need for an "anchor" in licensed spectrum. The operation of LTE systems and NR systems not only in unlicensed spectrum but also in licensed spectrum is expected to be further enhanced in future release systems and 5G systems (and Beyond 5G systems). Such enhanced operations may include mechanisms for determining sidelink (SL) collisions and half-duplex conflicts for reliable SL communication using inter-UE coordination feedback. Additional aspects relate to mechanisms for determining SL collisions and half-duplex conflicts by multiple transmitting UEs and enhanced resource (re)selection procedures.

Brief Description of the Drawings

[0008] In the several figures, which are not necessarily drawn to scale, like numerals may represent like components in different views. Like numerals with different subscripts may represent different examples of like components. The several figures generally illustrate, for purposes of example and not limitation, various aspects described herein.

[0009]

Figure 1A

Figure 1B

Figure 1C

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

[0010] The following description and the multiple drawings sufficiently explain the aspects and enable those skilled in the art to implement them. Other aspects may include structural, logical, electrical, process, and other changes. Some parts and features of some of the multiple aspects may be included in or replaced by parts and features of other aspects. The aspects outlined in the claims encompass all available equivalents of those claims.

[0011] FIG. 1A illustrates the architecture of a network according to some of the multiple aspects. Network 140A is shown to include user equipment (UE) 101 and UE 102. Although UE 101 and UE 102 are illustrated as smartphones (such as handheld touchscreen mobile computing devices that can be connected to one or more cellular networks), they may also include any other mobile computing device or non-mobile computing device such as a personal data assistant (PDA), a pager, a laptop computer, a desktop computer, a wireless handset, a drone, or any other computing device including a wired communication interface and / or a wireless communication interface. UE 101 and UE 102 may be collectively referred to as UE 101 herein, and UE 101 may be used to execute one or more of the multiple technologies disclosed herein.

[0012] Any of the plurality of wireless links described herein (e.g., used within network 140A or within any other illustrated network) can operate in accordance with any exemplary wireless communication technology and / or exemplary wireless communication standard.

[0013] LTE and LTE-Advanced are standards for wireless communication of high-speed data for UEs such as mobile phones. In LTE-Advanced wireless systems and various wireless systems, carrier aggregation is a technique that uses multiple carrier signals operating at multiple different frequencies to increase the available bandwidth for a single device to carry communications for a single UE. In some of the multiple aspects, carrier aggregation may be used when one or more component carriers are operating at multiple unlicensed frequencies.

[0014] The aspects described herein may be used in connection with any spectrum management scheme, including, for example, dedicated licensed spectrum, unlicensed spectrum, (licensed shared access (LSA) at 2.3 [GHz] - 2.4 [GHz], 3.4 [GHz] - 3.6 [GHz], 3.6 [GHz] - 3.8 [GHz] and further frequencies), and spectrum access systems (SAS) at 3.55 [GHz] - 3.7 [GHz] and further frequencies). (LSA), and spectrum access system (SAS) at 3.55 [GHz] - 3.7 [GHz] and further frequencies), etc.) of (licensed) shared spectrum.

[0015] The multiple aspects described herein may also be applied to different single carriers or OFDM flavors (such as CP-OFDM, SC-FDMA, SC-OFDM, filter bank-based multi-carrier (FBMC), OFDMA, etc.), particularly to 3GPP NR (New Radio), by allocating OFDM carrier data bit vectors to corresponding symbol resources.

[0016] In some of the plurality of aspects, either UE101 or UE102 may include an Internet of Things (IoT) UE or a Cellular IoT (CIoT) UE, and those IoT UEs or CIoT UEs may include a network access layer designed for low-power IoT applications that utilize short-lived UE connections. In some of the plurality of aspects, either UE101 or UE102 may include a NarrowBand (NB) IoT UE (such as, for example, an enhanced NB-IoT (eNB-IoT) UE and a further enhanced (FeNB-IoT) UE). IoT UEs can utilize technologies such as Machine-to-Machine (M2M) communication or Machine-Type (MTC) communication, and those M2M or MTC communications are for exchanging data with an MTC server or an MTC device via a Public Land Mobile Network (PLMN), proximity communication-based services (ProSe), or Device-to-Device (D2D) communication, a sensor network, or an IoT network. The M2M or MTC data exchange may be data exchange initiated by a machine. The IoT network includes a function of interconnecting a plurality of IoT UEs by short-lived connections, and those plurality of IoT UEs may include embedded computing devices that are uniquely identifiable (within the Internet infrastructure). IoT UEs may execute background applications (such as, for example, keep-alive messages, status updates, etc.) to facilitate connection to the IoT network.

[0017] In some of the plurality of aspects, either UE101 or UE102 may include an enhanced MTC (eMTC) UE or a further enhanced MTC (FeMTC) UE.

[0018] UE101 and UE102 may be configured to connect to a Radio Access Network (RAN) 110, such as being communicatively coupled to the Radio Access Network (RAN) 110. The RAN 110 may be, for example, a Universal Mobile Telecommunications System (UMTS), an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), a NextGen RAN (NG RAN), or other types of RAN. UE101 and UE102 each utilize connections 103 and 104, and each of connections 103 and 104 includes a physical communication interface or layer (to be described in more detail below). In this example, connections 103 and 104 are illustrated as wireless interfaces, and those wireless interfaces enable a communication connection and are compatible with cellular communication protocols such as the Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, Push-to-Talk over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5th Generation (5G) protocol, and New Radio (NR) protocol, etc.

[0019] In one aspect, UE101 and UE102 may further directly exchange communication data via a ProSe interface 105. The ProSe interface 105 may alternatively be referred to as a sidelink interface, and the sidelink interface includes one or more logical channels including, but not limited to, a Physical Sidelink Control Channel (PSCCH), a Physical Sidelink Shared Channel (PSSCH), a Physical Sidelink Discovery Channel (PSDCH), and a Physical Sidelink Broadcast Channel (PSBCH).

[0020] UE102 is shown to be configured to access access point (AP) 106 via connection 107. Connection 107 may include, for example, a local wireless connection such as a connection that is compliant with any IEEE 802.11 protocol, and AP106 may include a wireless fidelity (WiFi (registered trademark)) router according to any of those IEEE 802.11 protocols. In this example, AP106 is shown to be connected to the Internet without connecting to the core network of the wireless system (as will be described in more detail below).

[0021] RAN110 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), and RAN network nodes, etc., and may include terrestrial stations or satellite stations that provide coverage (such as terrestrial wave access points, etc.) within a certain geographical area (such as a cell, etc.). In some of the plurality of aspects, communication node 111 and communication node 112 may be transmission / reception points (TRPs). In an example where communication node 111 and communication node 112 are NodeBs (such as eNB or gNB, etc.), one or more TRPs can function within the communication cell of the NodeB. RAN110 includes, for example, one or more RAN nodes for providing macrocells such as macro RAN node 111, and, for example, one or more RAN nodes for providing femtocells or picocells (such as cells with a smaller coverage area, a smaller user capacity, or a larger bandwidth compared to a macrocell, etc.) such as low-power (LP) RAN node 112 or license-exempt spectrum-based secondary RAN node 112.

[0022] Either of RAN node 111 and RAN node 112 can terminate the radio interface protocol and may be the first contact points of UE101 and UE102. In some of the multiple aspects, either of RAN node 111 and RAN node 112 can perform various logical functions for RAN110, and these logical functions include, but are not limited to, radio bearer management, dynamic radio resource management for uplink and downlink, and data packet scheduling, and radio network controller (RNC) functions such as mobility management. In one example, either of node 111 and / or node 112 may be a new generation of NodeB (gNB), evolved NodeB (eNB), or other types of RAN nodes.

[0023] RAN110 is shown to be communicatively coupled to core network (CN) 120 via S1 interface 113. In multiple aspects, CN120 may be an evolved packet core (EPC) network, a next generation (NextGen) packet core (NPC) network, or other types of CN (such as illustrated with reference to FIGS. 1B - 1C). In this aspect, S1 interface 113 is divided into two parts: S1-U interface 114 that carries user traffic data between RAN node 111 and RAN node 112 and serving gateway (S-GW) 122, and S1 mobility management entity (MME) interface 115 that is a signaling interface between RAN node 111 and RAN node 112 and MME121.

[0024] In this aspect, CN120 includes a Mobility Management Entity (MME) 121, a Serving Gateway (S-GW) 122, a Packet Data Network (PDN) Gateway (P-GW) 123, and a Home Subscriber Server (HSS) 124. The MME 121 may be functionally similar to the control plane of a legacy Serving General Packet Radio Service (GPRS) Support Node (SGSN). The MME 121 may manage mobility aspects in access, such as gateway selection and Tracking Area List management. The HSS 124 may include a database for network users, and the database includes subscription-related information for supporting the processing of communication sessions of network entities. CN120 may include one or more HSSs 124 depending on the number of mobile subscribers, device capacity, network configuration, etc. For example, the HSS 124 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc.

[0025] The S-GW 122 may terminate the S1 interface 113 towards the Radio Access Network (RAN) 110 and route data packets between the RAN 110 and the CN 120. Additionally, the S-GW 122 may be a local mobility anchor point for handovers between RAN nodes and may also provide an anchor for mobility between 3GPPs. Other responsibilities of the S-GW 122 may include lawful intercept, charging, and some policy enforcement.

[0026] P-GW 123 may terminate the SGi interface towards the PDN. P-GW 123 may route data packets between the EPC network 120 and an external network such as a network including an application server 184 (alternatively referred to as an Application Function (AF)) via an Internet Protocol (IP) interface 125. P-GW 123 may also communicate data to another external network 131A which may include an Internet Protocol (IP) Multimedia Subsystem (IMS) network and other networks. Generally, the application server 184 may be an element that provides an application using IP bearer resources through a core network (such as, for example, a UMTS Packet Service (PS) domain, an LTE PS data service, etc.). In this aspect, P-GW 123 is shown to be communicatively coupled to the application server 184 via the IP interface 125. The application server 184 may also be configured to support one or more communication services (such as, for example, a Voice over Internet Protocol (VoIP) session, a Push-to-Talk (PTT) session, a group communication session, a social networking service, etc.) for the UEs 101 and 102 via the CN 120.

[0027] P-GW 123 may further be a node for policy enforcement and charging data collection. The Policy and Charging Rules Function (PCRF) 126 is a policy and charging control element of the CN 120. In a non-roaming scenario, in some of the multiple aspects, a single PCRF may exist within the Home Public Land Mobile Network (HPLMN) associated with the Internet Protocol connection access network (IP-CAN) session of the UE. In a roaming scenario with local breakout of traffic, two PCRFs may exist associated with the IP-CAN session of the UE, and those two PCRFs may be a Home PCRF (H-PCRF) within the HPLMN and a Visited PCRF (V-PCRF) within the Visited Public Land Mobile Network (VPLMN). The PCRF 126 may be communicatively coupled to the application server 184 via the P-GW 123.

[0028] In some of the multiple aspects, the communication network 140A may be an IoT network or a 5G network, and the IoT network or 5G network includes a 5G new radio network that uses communication in licensed (5G NR) spectrum and unlicensed (5G NR-U) spectrum. One of the current implementations of IoT is NarrowBand IoT (NB-IoT).

[0029] The NG system architecture may include RAN110 and a 5G network core (5GC) 120. The NG-RAN110 may include multiple nodes such as gNB and NG-eNB. The core network 120 (such as a 5G core network or 5GC, for example) may include an access and mobility function (AMF) and / or a user plane function (UPF). The AMF and UPF may be communicatively coupled to the gNB and NG-eNB via an NG interface. More specifically, in some of the multiple aspects, the gNB and NG-eNB may be connected to the AMF via an NG-C interface and connected to the UPF via an NG-U interface. The gNB and NG-eNB may be coupled to each other via an Xn interface.

[0030] In some of the multiple aspects, the NG system architecture may use reference points between various nodes as provided by 3GPP technical specification (TS) 23.501 (such as V15.4.0, 2018-12, for example). In some of the multiple 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 a RAN network node, etc. In some of the multiple aspects, the gNB may be a master node (MN), and the NG-eNB may be a secondary node (SN) in the 5G architecture. In some of the multiple aspects, the master node / primary node may operate in a licensed band, and the secondary node may operate in an unlicensed band.

[0031] Figure 1B illustrates a non-roaming 5G system architecture according to some of the plurality of aspects. Referring to Figure 1B, the 5G system architecture 140B is illustrated in a reference point representation. More specifically, the UE 101 may communicate not only with the RAN 110 but also with one or more other 5G Core (5GC) network entities. The 5G system architecture 140B includes a plurality of network functions (NFs) such as an Access and Mobility Management Function (AMF) 132, a Location Management Function (LMF) 133, a Session Management Function (SMF) 136, a Policy Control Function (PCF) 148, an Application Function (AF) 150, a User Plane Function (UPF) 134, a Network Slice Selection Function (NSSF) 142, an Authentication Server Function (AUSF) 144, and an Integrated Data Management (UDM) / Home Subscriber Server (HSS) 146. The UPF 134 is capable of providing a connection to a Data Network (DN) 152, and the connection to the DN 152 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 a network slice selection function. The SMF 136 may be configured to set up and manage various sessions according to network policies. The UPF 134 may be deployed in one or more configurations according to the target service type. The PCF 148 may be configured to provide a policy framework using network slicing, mobility management, and roaming (similar to the PCRF in a 4G communication system). The UDM may be configured to store subscriber profiles and data (similar to the HSS in a 4G communication system).

[0032] The LMF133 may be used in connection with 5G positioning functionality. In some of the plurality of aspects, the LMF133 receives measurements and assistance information from the next-generation radio access network (NG-RAN) 110 and a mobile device (such as the UE101) via the AMF132 over the NLs interface to calculate the location of the UE101. In some of the plurality of aspects, the NR positioning protocol A (NRPPa) may be used to carry positioning information between the NG-RAN and the LMF133 via the next-generation control plane interface (NG-C). In some of the plurality of aspects, the LMF133 configures the UE using the LTE positioning protocol (LPP) via the AMF132. The NG RAN110 configures the UE101 using the radio resource control (RRC) protocol via the LTE-Uu interface and the NR-Uu interface.

[0033] In some of the plurality of aspects, the 5G system architecture 140B comprises a plurality of different reference signals to enable positioning measurements. Exemplary reference signals that may be used for positioning measurements include, in the downlink, positioning reference signals (NR PRS), and in the uplink, sounding reference signals (SRS) for positioning. The downlink positioning reference signal (PRS) is a reference signal configured to support downlink-based positioning methods.

[0034] In some of the plurality of aspects, the 5G system architecture 140B includes not only the IP Multimedia Subsystem (IMS) 168B but also a plurality of IP multimedia core network subsystem entities such as the Call Session Control Function (CSCF). More specifically, the IMS 168B includes a CSCF that can operate 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. The P-CSCF 162B may be configured to be the first contact point for the UE 102 within the IM Subsystem (IMS) 168B. The S-CSCF 164B may be configured to handle the session state within the network, and the E-CSCF may be configured to handle certain aspects of the emergency session, such as routing an emergency request to an appropriate emergency center or PSAP. The I-CSCF 166B may be configured to function as a contact point within the operator's network for all IMS connections destined for subscribers of that network operator or roaming subscribers currently located within the service area of that network operator. In some of the plurality of aspects, the I-CSCF 166B may be connected to other IP multimedia networks 170E, such as an IMS operated by a different network operator.

[0035] In some of the plurality of aspects, the UDM / HSS 146 may be coupled to the Application Server 160B, which may include a Telephony Application Server (TAS) or other Application Server (AS). The Application Server (AS) 160B may be coupled to the IMS 168B by the S-CSCF 164B or the I-CSCF 166B.

[0036] The reference point representation indicates that there may be interactions between multiple corresponding NF services. For example, Figure 1B shows N1 (between UE101 and AMF132), N2 (between RAN110 and AMF132), N3 (between RAN110 and UPF134), N4 (between SMF136 and UPF134), N5 (between PCF148 and AF150, not shown), N6 (between UPF134 and DN152), N7 (between SMF136 and PCF148, not shown), N8 (between UDM146 and AMF132, not shown), N9 (between two UPF134s, not shown), N10 (between UDM146 and SMF136, not shown), N11 (between AMF132 and SMF136, not shown), N12 (between AUSF144 and AMF132, not shown), N13 (between AUSF144 and UDM146, not shown), N14 (between two AMF132s, not shown), N15 (between PCF148 and AMF132 in a non-roaming scenario and between PCF148, visited network, and AMF132 in a roaming scenario, not shown), N16 (between two SMFs, not shown), and N22 (between AMF132 and NSSF142, not shown). Other reference point representations not shown in Figure 1B may also be used.

[0037] Figure 1C illustrates the 5G system architecture 140C and a service-based representation. In addition to the plurality of network entities illustrated in Figure 1B, the system architecture 140C may also include a network exposure function (NEF) 154 and a network repository function (NRF) 156. In some of the plurality of aspects, the 5G system architecture may be service-based, and the interactions between the plurality of network functions may be represented by corresponding point-to-point reference points Ni or as service-based interfaces.

[0038] In some of the plurality of aspects, as illustrated in Figure 1C, the service-based representation may be used to represent network functions in the control plane, and the control plane enables other authorized network functions to access their services. In this regard, the 5G system architecture 140C may include service-based interfaces of Namf 158H (which is a service-based interface presented by AMF 132), Nsmf 158I (which is a service-based interface presented by SMF 136), Nnef 158B (which is a service-based interface presented by NEF 154), Npcf 158D (which is a service-based interface presented by PCF 148), Nudm 158E (which is a service-based interface presented by UDM 146), Naf 158F (which is a service-based interface presented by AF 150), Nnrf 158C (which is a service-based interface presented by NRF 156), Nnssf 158A (which is a service-based interface presented by NSSF 142), Nausf 158G (which is a service-based interface presented by AUSF 144). Also, other service-based interfaces (such as Nudr, N5g-eir, and Nudsf, etc.) not shown in Figure 1C may be used.

[0039] Figures 2, 3, and 4 illustrate various systems, devices, and components, which can implement aspects of the disclosed embodiments in a plurality of different communication systems such as 5G-NR (and Beyond 5G) networks. A UE, a base station (such as a gNB), and / or other nodes (such as satellites or other NTN nodes) described in connection with FIGS. 1A-4 may be configured to execute the disclosed technology.

[0040] FIG. 2 illustrates a network 200 according to various embodiments. The network 200 can operate in a manner consistent with 3GPP technical specifications for an LTE or 5G / NR system. However, those exemplary embodiments are not limited in this regard, and the disclosed embodiments may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0041] The network 200 may include a UE 202, which may include any mobile computing device or non-mobile computing device designed to communicate with the RAN 204 via a wireless connection. The UE 202 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, in-vehicle infotainment, in-vehicle entertainment devices, instrument clusters, head-up display devices, in-vehicle diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M devices or D2D devices, IoT devices, etc.

[0042] In some of the embodiments, network 200 may include a plurality of UEs directly coupled to each other by a sidelink interface. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as, but not limited to, PSBCH, PSDCH, PSSCH, PSCCH, PSFCH, etc.

[0043] In some of the embodiments, UE 202 may additionally communicate with AP 206 via a wireless connection. AP 206 may manage a WLAN connection, which may help offload some or all of the network traffic from RAN 204. The connection between UE 202 and AP 206 may be capable of conforming to any IEEE 802.11 protocol, and AP 206 may be a wireless fidelity (Wi-Fi (registered trademark)) router. In some of the embodiments, UE 202, RAN 204, and AP 206 may utilize cellular WLAN aggregation (such as, for example, LWA / LWIP, etc.). Cellular WLAN aggregation may include UE 202 configured by RAN 204 to utilize both cellular radio resources and WLAN resources.

[0044] RAN 204 may include one or more access nodes, such as access node (AN) 208. AN 208 may terminate the radio interface protocol for UE 202 by providing an access stratum protocol that includes RRC, Packet Data Convergence Protocol (PDCP), Radio Link Control (RLC), MAC, and L1 protocol. Thus, AN 208 can enable a data connection / voice connection between core network (CN) 220 and UE 202. In some of the multiple embodiments, AN 208 may be implemented in an individual device, or may be implemented as one or more software entities executed by a server computer as part of a virtual network, such as what may be referred to as a Cloud Radio Access Network (CRAN) or virtual baseband unit pool. AN 208 may be referred to as a BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 208 may be a macrocell base station, or may be a femtocell, picocell, or other similar cell that provides a smaller coverage area, a smaller user capacity, or a higher bandwidth compared to a macrocell, i.e., a low-power base station.

[0045] In an embodiment where RAN 204 includes multiple ANs, (when RAN 204 is an LTE RAN) those multiple ANs may be coupled to each other by an X2 interface, or (when RAN 204 is a 5G RAN) those multiple ANs may be coupled to each other by an Xn interface. The X2 interface / Xn interface, which may be separated into a control plane interface / user plane interface in some of the multiple embodiments, may enable those multiple ANs to communicate information related to handover, data / context transfers, mobility, load management, interference coordination, etc.

[0046] Each of the plurality of ANs of RAN204 may manage one or more cells, cell groups, component carriers, etc., and provide a radio interface for the UE202 to access the network. The UE202 may be connected to a plurality of cells provided by the same AN or different ANs of the RAN204 simultaneously. For example, the UE202 and the RAN204 may use carrier aggregation to enable the UE202 to connect to a plurality of component carriers each corresponding to a Pcell or an Scell. In a dual connectivity scenario, the first AN may be a master node providing the MCG, and the second AN may be a secondary node providing the SCG. The first AN / second AN may be any combination of an eNB, a gNB, an ng-eNB, etc.

[0047] RAN204 may provide a radio interface over licensed spectrum or unlicensed spectrum. To operate in unlicensed spectrum, the nodes may use LAA, eLAA, and / or feLAA mechanisms based on CA technology between PCells / SCells. Before accessing unlicensed spectrum, those nodes may perform medium / carrier sensing operations based on, for example, the listen-before-talk (LBT) protocol.

[0048] In a V2X scenario, UE202 or AN208 may be a roadside unit (RSU), or may function as a roadside unit (RSU), and the roadside unit (RSU) may refer to any traffic infrastructure entity used for V2X communication. The RSU may be implemented in an appropriate AN or by an appropriate AN, or in a fixed (or relatively fixed) UE or by a fixed (or relatively fixed) UE. The RSU implemented in a UE or by a UE may be referred to as a "UE-type RSU", the RSU implemented in an eNB or by an eNB may be referred to as an "eNB-type RSU", the RSU implemented in a gNB or by a gNB may be referred to as a "gNB-type RSU", and so on. In one example, the RSU is a computing device, and the computing device is coupled to a radio frequency circuit located roadside that provides connection support to passing vehicle UEs. The RSU may also include an internal data storage circuit that stores intersection map shapes, traffic statistics, media, as well as only applications / software that detect and control ongoing vehicle and pedestrian traffic. The RSU may provide communication with extremely low latency required for high-speed events such as collision avoidance and traffic warnings. Additionally or alternatively, the RSU may provide other cellular / WLAN communication services. The components of the RSU may be packaged in a weather-resistant housing suitable for outdoor installation, and may include a network interface controller that provides a wired connection (e.g., Ethernet, etc.) to a traffic signal controller or a backhaul network.

[0049] In some of the embodiments, RAN204 may be an LTE RAN210 having an eNB such as eNB212. The LTE RAN210 may provide an LTE radio interface having characteristics such as a sub-carrier spacing (SCS) of 15 [kHz]; a CP-OFDM waveform for downlink (DL) and an SC-FDMA waveform for uplink (UL); a turbo code for data and a TBCC for control. The LTE radio interface may rely on CSI-RS for CSI acquisition and beam management; PDSCH / PDCCH DMRS for demodulation of PDSCH / PDCCH; and CRS for cell search and initial acquisition, channel quality measurement and channel estimation for coherent demodulation / detection at the UE. The LTE radio interface may operate in the sub-6 [GHz] band.

[0050] In some of the embodiments, RAN204 may be an NG-RAN214 having a gNB such as gNB216 or an ng-eNB such as ng-eNB218. The gNB216 may connect to a 5G-capable UE using a 5G NR interface. The gNB216 may connect to the 5G core via an NG interface that may include an N2 interface or an N3 interface. The ng-eNB218 may also connect to the 5G core via an NG interface and, on the other hand, connect to the UE via an LTE radio interface. The gNB216 and the ng-eNB218 may be connected using an Xn interface.

[0051] In some of the embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface that carries traffic data between nodes of the NG-RAN214 and a UPF248 (such as an N3 interface), and an NG control plane (NG-C) interface that is a signaling interface between nodes of the NG-RAN214 and an AMF244 (such as an N2 interface).

[0052] NG-RAN214 may provide a 5G-NR radio interface having the characteristics of variable SCS; CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL; polar code, repetition code, simplex code, and Reed-Muller code for control, and LDPC for data. The 5G-NR radio interface may rely on CSI-RS and PDSCH / PDCCH DMRS, similar to the LTE radio interface. The 5G-NR radio interface may not use CRS, but may use PBCH DMRS for PBCH demodulation; PTRS for phase tracking for PDSCH, and a tracking reference signal for time tracking. The 5G-NR radio interface may operate in the FR1 band including the sub-6 [GHz] band or the FR2 band including the band from 24.25 [GHz] to 52.6 [GHz]. The 5G-NR radio interface may include a synchronization signal and physical broadcast channel (SS / PBCH) block (SSB), which is an area of the downlink resource grid including PSS / SSS / PBCH.

[0053] In some of the embodiments, the 5G-NR radio interface may utilize multiple BWPs (bandwidth parts) for various purposes. For example, the BWP may be used for dynamic adaptation of the SCS. For example, the UE202 may be composed of multiple BWPs, and each BWP configuration has a different SCS. When a change in the BWP is instructed to the UE202, the SCS of the transmission is similarly changed. Other use cases of the BWP are related to power saving. In particular, multiple BWPs may be configured for the UE202 using different amounts of frequency resources (such as multiple PRBs, etc.) to support data transmission under multiple different traffic load scenarios. A BWP with a small number of PRBs may be used for data transmission with low traffic load while enabling power saving in the UE202 and possibly in the gNB216. A BWP with a large number of PRBs may be used for scenarios with a higher traffic load.

[0054] The RAN204 is communicatively coupled to a CN220 that includes a plurality of network elements to provide various functions for supporting data and communication services to customers / subscribers (such as the users of the UE202). The components of the CN220 may be implemented within one physical node or separate physical nodes. In some of the embodiments, NFV may be utilized to virtualize any or all of the functions provided by the network elements of the CN220 onto physical computing / memory resources such as servers, switches, etc. The logical instantiation of the CN220 may be referred to as a network slice, and some logical instantiations of the CN220 may be referred to as network sub-slices.

[0055] In some of the embodiments, CN220 may be connected to an LTE radio network as part of an Enhanced Packet System (EPS) 222, which may also be referred to as an EPC (or enhanced packet core). As shown, the EPC 222 may include an MME 224, an SGW 226, an SGSN 228, an HSS 230, a PGW 232, and a PCRF 234 that are coupled to each other by interfaces (or "reference points"). The functions of the multiple elements of the EPC 222 are briefly introduced as follows.

[0056] The MME 224 may implement a mobility management function to track the current location of the UE 202, facilitating paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0057] The SGW 226 may terminate the S1 interface towards the RAN and route data packets between the RAN and the EPC 222. The SGW 226 may be a local mobility anchor point for RAN node - to - RAN node handover and may also provide an anchor for inter - 3GPP mobility. Other roles may include lawful intercept, charging, and some policy enforcement.

[0058] The SGSN 228 may track the location of the UE 202 and perform security functions and access control. Additionally, the SGSN 228 may perform EPC node - to - node signaling for mobility between multiple different RAT networks, selection of the PDN and S - GW specified by the MME 224, selection of the MME for handover, etc. The S3 reference point between the MME 224 and the SGSN 228 may enable the exchange of user information and bearer information for mobility between 3GPP access networks in the idle / active state.

[0059] The HSS 230 may include a database for network users, and the database includes subscription - related information for supporting the processing by network entities of communication sessions. The HSS 230 may provide support for routing / roaming, authentication, authorization, naming / address resolution, location dependency, etc. The S6a reference point between the HSS 230 and the MME 224 may enable the transfer of subscription data and authentication data for authenticating / authorizing user access to the LTE CN 220.

[0060] PGW 232 may terminate the SGi interface towards a data network (DN) 236, which may include an application / content server 238. PGW 232 may route data packets between the LTE CN 220 and the data network 236. PGW 232 may be coupled to the SGW 226 by the S5 reference point to facilitate user plane tunneling and tunnel management. PGW 232 may further include a node (such as PCEF, etc.) for policy enforcement and charging data collection. Additionally, the SGi reference point between PGW 232 and the data network 236 may be, for example, an operator external public, private PDN, or intra-operator packet data network for providing IMS services. PGW 232 may be coupled to the PCRF 234 by the Gx reference point.

[0061] PCRF 234 is a policy and charging control element of the LTE CN 220. PCRF 234 may be communicatively coupled to the app / content server 238 to determine appropriate QoS and charging parameters for the service flow. PCRF 234 may provide relevant rules with appropriate TFT and QCI to the PCEF (via the Gx reference point).

[0062] In some of the multiple embodiments, the CN 220 may be the 5GC 240. As shown, the 5GC 240 may include an AUSF 242, an AMF 244, an SMF 246, a UPF 248, an NSSF 250, a NEF 252, an NRF 254, a PCF 256, a UDM 258, and an AF 260, which are coupled to each other by interfaces (or "reference points"). Multiple functions of the elements of the 5GC 240 are briefly introduced as follows.

[0063] The AUSF 242 may store data for the authentication of the UE 202 and handle functions related to authentication. The AUSF 242 may facilitate a common authentication framework for different access types. As shown, in addition to communication with other elements of the 5GC 240 through the reference points, the AUSF 242 may present an Nausf service-based interface.

[0064] The AMF 244 may also enable other functions of the 5GC 240 to communicate with the UE 202 and the RAN 204 and subscribe to notifications about mobility events with respect to the UE 202. The AMF 244 may be involved in registration management (e.g., for registering the UE 202), connection management, reachability management, mobility management, lawful interception of events related to the AMF, and access authentication and authorization. The AMF 244 may provide transport for SM messages between the UE 202 and the SMF 246 and function as a transparent proxy for routing SM messages. The AMF 244 may also provide transport for SMS messages between the UE 202 and the SMSF. The AMF 244 may interact with the AUSF 242 and the UE 202 to perform various security anchor and context management functions. Further, the AMF 244 may be a termination point of the RAN CP interface, which may include or be the N2 reference point between the RAN 204 and the AMF 244. The AMF 244 may be a termination point of the NAS (N1) signaling and may perform NAS ciphering and integrity protection. The AMF 244 may also support NAS signaling with the UE 202 through the N3 IWF interface.

[0065] The SMF 246 may be involved in session management (e.g., session establishment and tunnel management between, for example, the UPF 248 and the AN 208), allocation and management of UE IP addresses (including optional authentication), selection and control of the UPF function, configuration of traffic steering in the UPF 248 for routing traffic to appropriate destinations, termination of the interface towards the policy control function, policy enforcement, charging, and control of the QoS part, lawful intercept (for SM events and the interface to the LI system), termination of the SM part of the NAS message, notification of downlink data, initiation of AN-specific SM information sent to the AN 208 via the AMF 244 through N2, and determination of the SSC mode of the session. The session management may refer to the management of the PDU session, and the PDU session or "session" may refer to a PDU connectivity service that provides or enables the exchange of PDUs between the UE 202 and the data network 236.

[0066] UPF 248 may function as an anchor point for mobility within a RAT and between RATs, an external PDU session point for interconnection with the data network 236, and a branching point for supporting multi-homed PDU sessions. UPF 248 also performs packet routing and forwarding, performs packet inspection, enforces the user plane part of policy rules, lawfully intercepts packets (UP collection), performs traffic usage reporting, performs QoS processing for the user plane (e.g., packet filtering, gating, UL / DL rate enforcement, etc.), performs uplink traffic verification (e.g., SDF-to-QoS flow mapping, etc.), performs transport level packet marking on the uplink and downlink, and may perform buffering of downlink packets and trigger downlink data notifications. UPF 248 may include an uplink classifier, and the uplink classifier supports routing of traffic flows to the data network.

[0067] The NSSF 250 may select a set of network slice instances serving the UE 202. The NSSF 250 may also determine the mapping to the permitted NSSAI and the subscribed S-NSSAIs when required. The NSSF 250 may also determine the set of AMFs to be used to serve the UE 202, or may determine a list of candidate AMFs based on the appropriate configuration and, in some cases, by querying the NRF 254. The selection of the set of network slice instances for the UE 202 is triggered by the AMF 244 to which the UE 202 is registered by interacting with the NSSF 250, and the registration of the UE 202 with the AMF 244 may lead to a change of AMF. The NSSF 250 may interact with the AMF 244 through the N22 reference point and may communicate with other NSSFs in the visited network through the N31 reference point (not shown). Additionally, the NSSF 250 may present an Nnssf service-based interface.

[0068] The NEF 252 may securely expose services and capabilities provided by 3GPP network functions for third parties, internal exposure / re-exposure, an AF (such as AF 260), an edge computing system or a fog computing system, etc. In such embodiments, the NEF 252 may authenticate, authorize, or throttle the AF. The NEF 252 may also translate information exchanged with the AF 260 and information exchanged with internal network functions. For example, the NEF 252 may perform a translation between an AF-Service-Identifier and internal 5GC information. The NEF 252 may also receive information from other NFs based on the exposed functions of other NFs. This information may be stored in the NEF 252 as structured data, or may be stored in a data storage NF using a standardized interface. The stored information may then be re-exposed by the NEF 252 to other NFs and AFs, or may be used for other purposes such as analysis. Additionally, the NEF 252 may present an Nnef service-based interface.

[0069] The NRF254 may support service discovery functions, receive NF discovery requests from NF instances, and provide information on discovered NF instances to NF instances. The NRF254 may also hold information on available NF instances and the services supported by those NF instances. As used herein, terms such as "instantiate" and "instantiation" may refer to the creation of an instance, and "instance" may refer to a specific occurrence of an object, which may occur, for example, upon the execution of program code. Additionally, the NRF254 may present an Nnrf service-based interface.

[0070] The PCF256 may provide policy rules to control plane functions and enforce those policy rules, and may also assist an integrated policy framework in managing the behavior of the network. The PCF256 may also implement a front end to access subscription information related to policy decisions in the UDR of the UDM258. As shown, in addition to communication with multiple functions through reference points, the PCF256 presents an Npcf service-based interface.

[0071] The UDM 258 may process subscription-related information to assist in the processing of network entities for communication sessions and may store the subscription data of the UE 202. For example, the subscription data may be communicated via the N8 reference point between the UDM 258 and the AMF 244. The UDM 258 may include two parts: an application front-end and a UDR. The UDR may store subscription data and policy data for the UDM 258 and the PCF 256, and / or structured data for exposure and application data for the NEF 252 (including PFDs for application detection and application request information for multiple UEs 202). The Nudr service-based interface presented by the UDR enables not only the UDM 258, the PCF 256, and the NEF 252 to access a specific set of stored data, but also the UDM 258, the PCF 256, and the NEF 252 to read, update (e.g., add, modify), delete, and subscribe to notifications of related data changes in the UDR. The UDM may include a UDM-FE, and the UDM-FE plays roles such as processing credentials, location management, and subscription management. Some of the multiple different front-ends may serve the same user in multiple different transactions. The UDM-FE accesses the subscription information stored in the UDR and performs authentication credential processing, user identification handling, access authorization, registration / mobility management, and subscription management.As shown, in addition to communicating with other NFs through a plurality of reference points, the UDM 258 may present a Nudm service-based interface.

[0072] The AF 260 may affect the application for traffic routing, provide access to the NEF, and interact with the policy framework for policy control.

[0073] In some of the plurality of embodiments, the 5GC 240 may enable edge computing by selecting operator / third party services that are geographically close to the point where the UE 202 is attached to the network. This selection makes it possible to reduce latency and the load on the network. To provide an implementation of edge computing, the 5GC 240 may select a UPF 248 close to the UE 202 and perform traffic steering from the UPF 248 to the data network 236 via the N6 interface. This traffic steering may be based on UE subscription data, UE location, and information provided by the AF 260. Thus, the AF 260 may affect the (re)selection of the UPF and traffic routing. When the AF 260 is considered to be a reliable entity based on the operator's arrangement, the network operator may permit the AF 260 to directly interact with the related NFs. Additionally, the AF 260 may present a Naf service-based interface.

[0074] The data network 236 may represent various network operator services, Internet access, or third-party services provided by, for example, one or more servers including an application / content server 238.

[0075] FIG. 3 schematically illustrates a wireless network 300 according to various embodiments. The wireless network 300 may include a UE 302 in wireless communication with an AN 304. The UE 302 and the AN 304 may be similar to components of the same name described elsewhere in this specification and may be substantially interchangeable.

[0076] The UE 302 may be communicatively coupled to the AN 304 by a connection 306. The connection 306 is illustrated as a wireless interface enabling a communicative coupling and may be compatible with a cellular communication protocol such as the LTE protocol or the 5G NR protocol operating in mmWave or at sub-6 [GHz] frequencies.

[0077] The UE 302 may include a host platform 308 coupled to a modem platform 310. The host platform 308 may include an application processing circuit 312, and the application processing circuit 312 may be coupled to a protocol processing circuit 314 of the modem platform 310. The application processing circuit 312 may execute various applications that supply (source) / sink application data for the UE 302. The application processing circuit 312 may further implement one or more layer operations to transmit / receive application data to / from a data network. These layer operations may include transport operations (such as UDP) and Internet operations (such as IP).

[0078] The protocol processing circuit 314 may implement one or more layer operations to facilitate the transmission and reception of data through the connection 306. The layer operations implemented by the protocol processing circuit 314 may include, for example, MAC operations, RLC operations, PDCP operations, RRC operations, and NAS operations.

[0079] The modem platform 310 may further include a digital baseband circuit 316, and the digital baseband circuit 316 may implement one or more layer operations that are "below" layer operations executed by the protocol processing circuit 314 in the network protocol stack. These operations may include, for example, one or more of the HARQ-ACK functions, scrambling / descrambling, encoding / decoding, layer mapping / demapping, modulation symbol mapping, received symbol / bit metric determination, PHY operations including multi-antenna port precoding / decoding, and these PHY operations may include one or more of space-time coding, space-frequency coding, or spatial coding, reference signal generation / detection, preamble sequence generation and / or decoding, synchronization sequence generation / detection, blind decoding of control channel signals, and other related functions.

[0080] The modem platform 310 further includes a transmission circuit 318, a reception circuit 320, an RF circuit 322, and an RF front end (RFFE) 324, and the RF front end (RFFE) 324 may include or be connected to one or more antenna panels 326. Briefly, the transmission circuit 318 may include a digital / analog converter, a mixer, an intermediate frequency (IF) component, etc., the reception circuit 320 may include an analog / digital converter, a mixer, an IF component, etc., the RF circuit 322 may include a low noise amplifier, a power amplifier, a power tracking component, etc., and the RFFE 324 may include a filter (such as a surface / bulk acoustic wave filter, etc.), a switch, an antenna tuner, a beamforming component (such as a phased array antenna component, etc.), etc. The selection and arrangement of the components of the transmission circuit 318, the reception circuit 320, the RF circuit 322, the RFFE 324, and the antenna panel 326 (generally referred to as "transmission / reception components") may be specific to the details of a particular implementation, such as whether the communication is TDM or FDM, whether it is mmWave communication or communication at sub-6 [GHz] frequencies, etc. In some of the multiple embodiments, the transmission / reception components may be arranged in multiple parallel transmission / reception chains and may be arranged on the same chip / module or different chips / modules.

[0081] In some of the multiple embodiments, the protocol processing circuit 314 may include one or more instances of a control circuit (not shown) to provide control functions to the transmission / reception components.

[0082] UE reception may be established by or via the antenna panel 326, the RFFE 324, the RF circuit 322, the reception circuit 320, the digital baseband circuit 316, and the protocol processing circuit 314. In some of the multiple embodiments, the antenna panel 326 may receive the transmission from AN304 by a reception beamforming signal received by the elements of the multiple antennas / single antenna of one or more antenna panels 326.

[0083] UE transmission may be established by or via a protocol processing circuit 314, a digital baseband circuit 316, a transmission circuit 318, an RF circuit 322, an RFFE 324, and an antenna panel 326. In some of the plurality of embodiments, the transmission components of the UE 302 may apply a spatial filter to the data to be transmitted to form a transmission beam radiated by the antenna elements of the antenna panel 326.

[0084] Similar to the UE 302, the AN 304 may include a host platform 328 coupled to a modem platform 330. The host platform 328 may include an application processing circuit 332 coupled to a protocol processing circuit 334 of the modem platform 330. The modem platform may further include a digital baseband circuit 336, a transmission circuit 338, a reception circuit 340, an RF circuit 342, an RFFE circuit 344, and an antenna panel 346. The components of the AN 304 may be similar to the components of the UE 302 with the same name and may be substantially interchangeable with those components. In addition to performing the data transmission / reception described above, the components of the AN 304 may perform various logical functions, and those various logical functions include, for example, RNC functions such as radio bearer management, uplink and downlink dynamic radio resource management, and data packet scheduling.

[0085] FIG. 4 is a block diagram illustrating a plurality of components according to some of the plurality of exemplary embodiments, the plurality of components being capable of reading instructions from a machine-readable medium or a computer-readable medium (such as, for example, a non-transitory machine-readable storage medium) and executing any one or more of the methodologies described herein. Specifically, FIG. 4 shows a schematic representation of a hardware resource 400 that includes one or more processors (or processor cores) 410, one or more memory / storage devices 420, and one or more communication resources 430, each of these components being communicatively coupled by a bus 440 or other interface circuitry. In a plurality of embodiments where node virtualization (such as, for example, NFV) is utilized, a hypervisor 402 may be executed to provide an execution environment for one or more network slices / sub-slices and utilize the hardware resource 400.

[0086] Processor 410 may include, for example, processor 412 and processor 414. Processor 410 may be, for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a DSP such as a baseband processor, an ASIC, an FPGA, a radio frequency integrated circuit (RFIC), other processors (including the processors described herein), or any suitable combination thereof.

[0087] The memory / storage device 420 may include a main memory, a disk storage device, or a suitable combination of them. The memory / storage device 420 may include any type of volatile, non-volatile, or semi-volatile memory, including but not limited to dynamic random access memory (DRAM), static random access memory (SRAM), erasable and programmable read-only memory (EPROM), electrically erasable and programmable read-only memory (EEPROM), flash memory, solid state storage, etc.

[0088] The communication resource 430 may include an interconnect or network interface controller, component, or other suitable device to communicate via the network 408 with one or more peripheral device(s) 404, or one or more database(s) 406, or other network elements. For example, the communication resource 430 may include a wired communication component (for coupling via, e.g., USB, Ethernet, etc.), a cellular communication component, an NFC component, a Bluetooth® (or Bluetooth® Low Energy) component, a Wi-Fi® component, and other communication components.

[0089] Command 450 may include software, a program, an application, an applet, an app, or other executable code for causing at least any one of processors 410 to execute any one or more of the plurality of methodologies described herein. Command 450 may be wholly or partially present in at least one of processors 410, memory / storage device 420, or any suitable combination thereof (e.g., in the cache memory of a processor). Further, portions of any of command 450 may be transferred from any combination of peripheral devices 404 or database 406 to hardware resources 400. Accordingly, the memory of processor 410, memory / storage device 420, peripheral devices 404, and database 406 are examples of computer-readable media and machine-readable media.

[0090] In one or more embodiments, at least one of the components outlined in one or more of the above figures may be configured to perform one or more operations, techniques, processes, and / or methods as outlined in the following exemplary sections. For example, a baseband circuit associated with one or more of the above figures may be configured to operate in accordance with one or more of the examples described below. As another example, circuits associated with a UE, a base station, a satellite, network elements, etc., described above in connection with one or more of the above figures may be configured to operate in accordance with one or more of the examples described below in the exemplary sections.

[0091] The term "application" may refer to a complete and deployable package, environment for achieving a particular function in an operating environment. Terms such as "AI / ML application" may be an application that includes some of the artificial intelligence (AI) model / machine learning (ML) model and application-level descriptions. In some of the multiple embodiments, the AI / ML application may be used to construct or implement one or more of the disclosed aspects.

[0092] The term "machine learning" or "ML" refers to the use of a computer system that implements algorithms and / or statistical models to perform one or more specific tasks depending on patterns and inferences without using explicit instructions. The ML algorithm builds or estimates one or more mathematical models (referred to as "ML models" etc.) based on sample data (referred to as "training data" or "model training information" etc.) and makes predictions or decisions without being explicitly programmed to perform such tasks. Generally, an ML algorithm is a computer program that learns from experience regarding some of the tasks and some of the performance measurements, and an ML model may be any object or data structure created after the ML algorithm has been trained by one or more training data sets. After training, the ML model may be used to make predictions regarding new data sets. The term "ML algorithm" refers to a concept different from the term "ML model", but these terms described in this specification may be used interchangeably for the purposes of this disclosure.

[0093] The terms "machine learning model" or "ML model" may also refer to the ML methods and concepts used by an ML-assisted solution. An "ML-assisted solution" is a solution that uses an ML algorithm to handle a particular use case during operation. ML models include supervised learning (such as linear regression, k-nearest neighbor (KNN), decision tree algorithms, support machine vectors, Bayesian algorithms, ensemble algorithms, etc.), unsupervised learning (such as K-means clustering, principal component analysis (PCA), etc.), reinforcement learning (such as Q-learning, multi-armed bandit learning, deep RL, etc.), and neural networks. Depending on the implementation, a particular ML model may have many submodels as components, and the ML model may train all of the multiple submodels together. Individually trained ML models may also be concatenated together by an ML pipeline during inference. An "ML pipeline" is a set of functions, features, or functional entities specific to an ML-assisted solution, and the ML pipeline may include one or more data sources among a data pipeline, a model training pipeline, a model evaluation pipeline, and an actor. An "actor" is an entity that hosts an ML-assisted solution using the output of an ML model inference. The term "ML training host" refers to an entity such as a network function that hosts the training of the model.The term "ML inference host" refers to an entity such as a network function that hosts a model in inference mode (including, where applicable, both execution of the model and any online learning). The ML host notifies the actor of the output of the ML algorithm, and the actor determines an action (where "action" is what is executed by the actor as a result of the output of the ML-assisted solution). The term "model inference information" refers to the information used as input to the ML model to determine one or more inferences, and while the data used to train the ML model and the data used to determine inferences may overlap, "training data" and "inference data" refer to different concepts.

[0094] The high reliability and low latency of sidelink V2X communication are critical KPIs for the NR V2X system. In NR Rel.17, inter-UE coordination methods are beneficial for enhancing sidelink reliability. The disclosed techniques include specific inter-UE coordination solutions that can provide low latency and high reliability for future generations of NR V2X systems. In some of the multiple aspects, the following components (a) to (d) of the baseline NR V2X system may be used. (a) A UE that transmits sidelink data (while communicating in unicast mode, groupcast mode, or broadcast mode) reserves sidelink resources for future retransmission of the TB using the control channel. (b) The UE performs a sensing procedure by monitoring the sidelink control channel in each slot, decoding control channel transmissions from other UEs, and measuring the SL-RSRP. (c) The sidelink resources selected for transmission are determined based on the results of sensing and resource (re)selection procedures aimed at avoiding collisions among multiple UEs. (d) The UE uses the sidelink feedback channel introduced for HARQ operations in the case of unicast and groupcast communications.

[0095] The UE-autonomous sensing and resource (re)selection procedures defined in Rel. 16 provide performance advantages over random resource (re)selection. The disclosed technology further includes enhancements for improving the reliability of NR V2X sidelink communications using low latency inter-UE coordination feedback signaling.

[0096] Inter-UE coordination signaling helps increase reliability in the Rel. 16 NR-V2X communication system by reducing the negative performance impact due to half-duplex and co-cannel collision events. The disclosed technology may be used to identify multiple sidelink conflicts such as co-channel collisions including half-duplex conflicts, and the following definitions are used.

[0097] Side-link competition such as semi-duplex and collisions on the same channel

[0098] (A) Half-duplex conflicts

[0099] (A.1) (For example, UE P being a member of the UE Q group, etc.) UE P is UEQ In the case of being the target RX of P the UE Q has a half-duplex event with Q the UE, and due to its transmission, it may be impossible to receive the transmission from

[0100] (A.1.a) Half-duplex in transmission (HD-TX): P The UE Q and

[0101] (A.1.b) Half-duplex in reception (HD-RX): P The UE Q has reserved resources for the transmission to Q the UE P in slot "n". The UE

[0102] (A.1.c) Half-duplex in resource selection (HD-SLCT): P The UE Qhas already completed the selection of resources for transmission within the same slot (of resources with overlapping or non-overlapping frequencies). If a reservation for the selected resources has not yet been made by one of the multiple UEs and there is sufficient processing delay to reselect the resources, it is possible to partially address this type of conflict by the (re)evaluation procedure defined in Rel. 16.

[0103] (A.1.d) Half-Duplex in Resource Reservation (HD-RSV): UE P and UE Q have already completed the reservation of resources for transmission within the same slot (of resources with overlapping or non-overlapping frequencies). By introducing new UE-to-UE coordination signaling, it is possible to address this type of conflict.

[0104] (A.2) As if UE P and UE Q were transmitting in overlapping frequency resources (a co-channel collision of the same channel), half-duplex may significantly degrade the performance of sidelink reception for the other RX UE, and the transmissions of both sides will become non-decodable.

[0105] (B) Co-channel collision

[0106] (B.1) When UE P and UE Q transmit in overlapping frequency or time resources, UE P experiences a co-channel collision with UE Q . The following types of co-channel collisions may be discriminated as follows.

[0107] (B.1.a) Co-channel collision in transmission (CC-TX). In this case, the TX UEs (UE P and UE Q) has already completed transmission within the same sidelink slot of overlapping frequency resources (either complete overlap or partial overlap).

[0108] (B.1.b) Collision of the same channel in resource selection (CC-RS). In this case, the TX UEs (UE P and UE Q ) have completed the selection of resources for transmission within the same slot of overlapping frequency resources (either complete overlap or partial overlap). In some of the multiple aspects, this event may not be detectable unless one of the multiple TX UEs has not already made a resource reservation.

[0109] (B.1.c) Collision of the same channel in resource reservation (CC-RSV). In this case, the TX UEs (UE P and UE Q ) have completed the reservation of resources for transmission within the same slot of overlapping frequency resources (either complete overlap or partial overlap).

[0110] The sidelink conflicts described above are considered from the perspective of a single TX UE.

[0111] In some of the multiple aspects, half-duplex and co-channel collisions may occur in the resources used for the first transmission of a transport block (TB), retransmission, or any of various combinations from the perspective of the TX UE.

[0112] (a) Resources used by combination-A UEs P and UE Q for the first transmission of a TB.

[0113] (b) Resources used by combination-B UEs P and UE QResources used for retransmission of the TB.

[0114] (c) Combined-C UE P Resources used for the first transmission of the TB by, and the UE Q Resources carrying the retransmission of the TB by the UE.

[0115] In the Rel.16 V2X design, the following types of collisions on the same channel exist.

[0116] (a) Type 1 (Hidden Node): Collision on the same channel due to the hidden node problem. Fig. 5 illustrates a diagram 500 of a type 1 hidden node collision according to some of the plurality of aspects. One or more transmitting UEs are outside each other's communication range (i.e., cannot detect each other), but are within the communication range of the RX UE.

[0117] (b) Type 2 (Simultaneous Access): Collision on the same channel due to simultaneous resource (re)selection caused by processing time delay or lack of sensing data resulting from sidelink transmission etc. Fig. 6 illustrates a diagram 600 of a type 2 simultaneous access collision according to some of the plurality of aspects. A plurality of transmitting UEs are within each other's communication range (i.e., can detect each other), but perform resource (re)selection simultaneously and access the channel in the same slot of overlapping resources.

[0118] (c) Type 3 (Congested Medium): Collision of the same channel due to lack of unused resources (heavy medium congestion). The TX UEs are within each other's communication range (i.e., it is possible to detect each other), but access to the channel is congested (resources are occupied), and the UE selects an occupied resource from among the set of resources with the minimum RX power level. In this case, it is impossible to avoid collisions, so it is necessary to use a congestion control mechanism to reduce the collision rate.

[0119] The following list is a list of UE - to - UE coordination resolution methods for enhanced mode 2 resource allocation. Mode 2 is related to autonomous resource selection (such as autonomous selection of time and frequency resources, etc.). In some of the multiple aspects, UE - to - UE coordination feedback and signaling may be used to mitigate the contention of NR - V2X sidelink communication, such as half - duplex in transmission (HD - TX), half - duplex in reservation (HD - RSV), half - duplex in reception (HD - RX), collision of the same channel in transmission (CC - TX), and collision of the same channel in reservation (CC - RSV).

[0120] To address these contentions through UE - to - UE coordination, the proposed technique introduces low - latency sidelink feedback signaling. The proposed UE - to - UE coordination framework may include one or more of the following design components.

[0121] (a) A method for determining sidelink collisions and half - duplex contentions for reliable sidelink communication using UE - to - UE coordination feedback, the method including conditions for determining half - duplex and same - channel collisions by the RX UE.

[0122] (b) A method of prioritizing inter-UE adjustment feedback for reliable sidelink communication using inter-UE adjustment feedback, the method including UL, SL HARQ, SL half-duplex / same channel, and SL priority.

[0123] (c) A method of determining a UE for inter-UE adjustment feedback, the method including distance, RSRP, and detection of half-duplex / same channel collision events.

[0124] (d) A method of determining the timing of inter-UE adjustment feedback for reliable sidelink communication, the method including which slot to use for indication signaling and a new processing time for inter-UE adjustment.

[0125] (e) A method of determining sidelink half-duplex and collision events by a plurality of transmitting UEs and enhanced resource re-selection procedures, the method including autonomous detection by UEs of half-duplex and same channel collisions and the behavior of TX UEs regarding resource allocation.

[0126] (f) A method of determining resources for sidelink transmission for inter-UE adjustment feedback.

[0127] (g) A method of inter-UE adjustment feedback signaling for reliable sidelink communication.

[0128] Figures 7 to 10 illustrate NR sidelink communication problems that can be addressed using the above methods and the disclosed techniques.

[0129] Figure 7 illustrates a half-duplex diagram 700 for the case of transmission using adjustment feedback between UEs according to some of the multiple aspects. More specifically, Figure 7 illustrates a half-duplex contention for the case of transmission. In particular, UE1 and UE2 use half-duplex in the resources used for retransmission of the TB. UE3 provides UE1 and UE2 with feedback indicating half-duplex for the case of transmission and the potential need for additional retransmissions. In addition, UE4 and UE5 use half-duplex in the resources used for the first transmission of the transport block (TB). UE6 provides UE4 and UE5 with feedback indicating half-duplex for the case of the first transmission and the potential need for additional retransmissions.

[0130] Figure 8 illustrates a half-duplex diagram 800 for the case of resource reservation using adjustment feedback between UEs according to some of the multiple aspects. More specifically, Figure 8 illustrates the conflicts of half-duplex in the reservation. In particular, UE1 and UE2 use half-duplex in the reservation resources planned for retransmission of the TB. For example, UE2 detects the half-duplex reserved for the retransmission resources and provides feedback to UE1. In some of the multiple aspects, UE1 detects the half-duplex reserved for the retransmission resources and provides feedback to UE2. In some of the multiple embodiments, other UEs (such as UE3 not illustrated in Figure 8, for example) provide UE1 and UE2 with feedback indicating half-duplex in the reservation and the potential need for resource (re)selection.

[0131] Figure 9 illustrates diagram 900 of the collision of the same channel in the case of transmission using adjustment feedback between UEs according to some of the multiple aspects. More specifically, UE1 and UE2 have a collision of the same channel in the resources used for the retransmission of the TB. UE3 provides feedback to UE1 and UE2 indicating the collision of the same channel in the case of transmission and the potential need for additional retransmission. In addition, UE4 and UE5 have a collision of the same channel in the resources used for the first transmission of the TB. UE6 provides feedback to UE4 and UE5 indicating the collision of the same channel in the case of the first transmission and the potential need for additional retransmission.

[0132] Figure 10 illustrates diagram 1000 of the collision of the same channel in the reservation using adjustment feedback between UEs according to some of the multiple aspects. More specifically, UE1 and UE2 have reserved overlapping resources for the retransmission of the TB. UE3 provides feedback to UE1 and UE2 indicating the collision of the same channel in the reservation and the potential need for resource (re)selection or retransmission.

[0133] The following SL conflicts may cause reliability problems in NR side-link communication and can be solved using the disclosed techniques of half-duplex in transmission (HD-TX), half-duplex in reservation (HD-RSV), half-duplex in reception (HD-RX), collision of the same channel in transmission (CC-TX), and collision of the same channel in reservation (CC-RSV) for that NR side-link communication reliability problem.

[0134] The disclosed techniques include a method for determining sidelink collisions and half-duplex conflicts for reliable sidelink communication using adjustment feedback between UEs. The disclosed techniques may include UE behavior such as classification of sidelink conflicts, RX-based determination of sidelink conflicts as part of a sensing procedure, RX-based feedback indicating sidelink conflicts to the TX UE, and TX-based resource allocation enhancement based on adjustment feedback between UEs.

[0135] In some of the plurality of aspects, support for adjustment signaling between UEs for reliable sidelink communication may be based on defining procedures for determining half-duplex and same-channel collisions for multiple different communication types such as unicast (e.g., using ACK / NACK-based HARQ feedback or not using HARQ feedback), groupcast (e.g., using only NACK HARQ feedback, using ACK / NACK HARQ feedback, or not using HARQ feedback), and broadcast (e.g., not using HARQ feedback).

[0136] (A) Determination of half-duplex conflicts

[0137] To determine sidelink half-duplex conflicts (HD-TX and HD-RSV) by the RX UE, groupcast sidelink communication using only NACK feedback may be analyzed, and then groupcast sidelink communication may be generalized to other communication types.

[0138] In the case of groupcast sidelink transmission using only NACK feedback, the UE transmits control channel information using SCI formats (Stage 1 SCI - SCI Format 1 in PSCCH, Stage 2 SCI - SCI Format 2 multiplexed in PSSCH). In this mode, when the target RX UE fails to successfully decode the TB during PSSCH transmission, NACK HARQ signaling via PSFCH is used. The target RX UE is determined based on the distance value from the TX UE (and / or, if defined in addition to the distance, the sidelink RSRP). In some of the multiple embodiments, SL positioning / ranging information may be available, and this information may also be used to determine the distance.

[0139] The following procedure may be used by the RX UE (UER) to determine whether the TX UEs (UEP and UEQ) have a half-duplex collision (some of the multiple steps may not be possible in all cases).

[0140] (A.1) The RX UE R successfully decodes the control channel transmissions (SCI Formats) from the UE P and the UE Q .

[0141] (A.2) The RX UE R extracts the following information from the SCI.

[0142] (A.2.a) The zone ID of UE P and the zone ID of UE Q (zone ID P and zone ID Q );

[0143] (A.2.b) UEP and UE Q 's target communication ranges (RP and RQ);

[0144] (A.2.c) UE P and UE Q 's L1 source ID (or, L2 source ID);

[0145] (A.2.d) UE P and UE Q 's L1 destination ID (or, L2 destination ID);

[0146] (A.2.e) UE for sidelink transmission P and UE Q 's priority

[0147] (A.3) RX UE R checks whether the TX UE (UE P and UE R ) exists within each other's target communication ranges.

[0148] (A.3.a) When the target communication range R Q indicated by UE Q meets the preconfigured or predefined conditions, UE P is within the target communication range of UE Q .

[0149] (A.3.a.1) Example 1: R Q is the distance d Q between the centers of the zones (i.e., R PQ ) derived from the indicated zone ID and zone length L PQ exceeds.

[0150] (A.3.a.2) Other examples for generalization are as follows.

[0151] Example 2: R Q >d PQ +Δ where Δ is a function of the zone length L;

[0152] Example 3: R Q >f(L, zone IDP, zone IDQ, Source IDP, Source IDQ), f() is a pre-defined function;

[0153] Example 4: R Q >f(Coordinates of UEP, Coordinates of UEQ), f() is a pre-defined function.

[0154] (A.3.b) UE P When the target communication range RP indicated by UE satisfies a pre-configured condition or a pre-defined condition (refer to the above), UE Q is within the target communication range of UE P .

[0155] (A.4) RX UE R checks whether it is interested in the services provided by TX UE (UE P and UE R ).

[0156] (A.4.a) UE P is interested in the services provided by UE Q (for example, UE P may be a group member of UE Q discovered by L1 or L2 filtering of the signaled destination ID); and / or,

[0157] (A.4.b) UE Q is interested in the services provided by UE P (for example, UE Q may be a group member of UE P discovered by L1 or L2 filtering of the signaled destination ID); or,

[0158] (A.4.c) UE R is interested in UE P or UEQ is interested in one or both of the services, and w / o is the UE P for the UE Q examines the service relationship of.

[0159] Using a similar procedure, the UE R is the UE R can detect whether there is a half-duplex conflict in reception (HD-RX) between at least one TX UE (UE P and / or UE Q ) and itself. The UE R is the target RX of either or both of the TX UEs (UE R or UE P or UE Q ) that have completed the reservation for sidelink transmission to the UE R in slot "n", and the UE R has a higher-priority UL transmission or SL transmission in the same slot, and thus this conflict may occur when the UE P or UE Q is unable to receive the transmission from the UE

[0160] UE P and UE Q As a result of receiving the SCI from, the UE R is the UE P and / or UE Q in the case of transmission, the UE P and / or UE Q in the case of reservation, the UE P and / or UE Q in the case of both transmission and reservation, the half-duplex in the case of reception in UER, or not half-duplex in other cases, can determine the half-duplex conflict.

[0161] Regardless of a particular half-duplex conflict, the following cases are possible regarding the trigger / provision of UE-to-UE adjustment signaling based on the disclosed technology.

[0162] (a) Case 1: UE P needs to listen to UE Q (listen to UE Q ). (UE P is the target RX of UE Q ). In the case of half-duplex in transmission, in order to improve the reliability of sidelink communication, UE R may provide inter-UE coordination signaling to UE Q . In the case of half-duplex in reservation, in order to improve the reliability of sidelink communication, UE R may provide inter-UE coordination signaling to UE Q and / or UE P .

[0163] (b) Case 2: UE Q needs to listen to UE P (listen to UE P ). (UE Q is the target RX of UE P ). In the case of half-duplex in transmission, in order to improve the reliability of sidelink communication, UE R may provide inter-UE coordination signaling to UE P . In the case of half-duplex in reservation, in order to improve the reliability of sidelink communication, UE R may provide inter-UE coordination signaling to UE P and / or UE Q .

[0164] (c) Case 3: UE Q needs to listen to UE P (listen to UE P ), and UE P needs to listen to UE Q (listen to UE Q ). (Both TX UEs (UE P and UE Q) are each other's RX targets). In the case of half-duplex in transmission, in order to improve the reliability of sidelink communication, UE R is UE P and / or UE Q may provide inter-UE adjustment signaling to UE. In the case of half-duplex in reservation, in order to improve the reliability of sidelink communication, UE R is UE P and / or UE Q may provide inter-UE adjustment signaling to UE.

[0165] (d) Case 4: UE P and UE Q do not need to listen to each other (TX UE (UE P and UE Q ) are not each other's target RX, that is, not group members). In this case, if no feedback indication regarding collision on the same channel is required, inter-UE adjustment signaling may not be required by UE R .

[0166] (e) Case 5: UE R is required to listen to either UE P and / or UE Q (listen to either UE P and / or UE Q ). That is, one or both of the TX UE (UE P and UE Q ) are the RX targets of UE R . In the case of half-duplex in reception, in order to improve the reliability of sidelink communication, UE R is UE P and / or UE Q may provide inter-UE adjustment signaling to UE, whereby those UE P and / or UE Q may stop transmission on the reserved resources (can drop). Alternatively, if UE R is not scheduled by the gNB, UER It may also attempt to reselect resources for transmission.

[0167] In some of the multiple aspects, the principle of determining the target RX UE based on a distance criterion may be applicable only to groupcast communication that uses only NACK-only HARQ feedback. In some of the multiple aspects, this approach may be extended to other modes as a criterion for determining that the TX UE is facing a half-duplex event.

[0168] For groupcast sidelink transmission using ACK / NACK HARQ feedback, the indication by the TX UEs (UE P and UE Q ) of the common group destination ID (L1 or L2) for transmission in the same slot may be used as a criterion for determining a half-duplex event. On top of that, RSRP or a distance criterion may be used. In the latter case, a new SCI format definition for sending the TX UE coordinates by signaling may be required, or the zone ID-based principle may be reused. For example, it is possible to define a new SCI format 2-C (or other SCI format 2-x) that includes the union of the payloads of SCI format 2-A and SCI format 2-B.

[0169] For groupcast sidelink transmission that does not use HARQ feedback, the same approach as for groupcast sidelink transmission that uses ACK / NACK HARQ feedback may be used.

[0170] For unicast sidelink transmission using ACK / NACK HARQ feedback, the RX UE determines that the TX UEs (UE P and UE Q ) for transmission in the same slot are related to the TX UE (e.g., the source ID of UE Q == the destination ID of UE Q == UE P ).P and / or UE P source ID P == UE Q destination ID Q It may be necessary to check whether it indicates a destination ID (such as).

[0171] In the case of unicast sidelink transmission that does not use HARQ feedback, the same approach as unicast sidelink transmission that uses ACK / NACK HARQ feedback may be used.

[0172] In the case of broadcast sidelink transmission or connectionless groupcast, all transmissions by broadcast UEs P and broadcast UEs Q by default have a half-duplex problem, and thus the criterion is that the destination ID (L1 or L2) indicated by the UE P and UE Q may be to check whether it is associated with broadcast transmission or connectionless groupcast.

[0173] To summarize the above description, the determination by the RX UE of the half-duplex problem during UE P and UE Q transmission may be performed by signaling sent by the SCI (L1) or by analysis of the source ID and destination ID using upper layer signaling (L2). In addition, when generalizing the distance-based criterion for determining the target receiver, the distance between multiple TX UEs may be defined as a condition for determining the half-duplex between multiple TX UEs.

[0174] (B) Indicator of half-duplex awareness

[0175] In some of the multiple aspects, during the sensing and resource (re)selection procedure, the TX UE can also autonomously become aware of the half-duplex event. For example, a UE that decodes an SCI transmission P may detect the half-duplex in the case of resource reservation in resource Res P , but if resource Res P is recognized as a candidate resource and the UE P has already successfully decoded the transmission from a previous transmission of the same TB for the UE Q , the UE P may still select resource Res P for transmission. In this case, the UE P does not need UE-to-UE adjustment feedback from the UE R . To avoid feedback, the UE P may need to provide information regarding half-duplex recognition to the RX UE (UE R ). For this purpose, an additional field or reserved field in the SCI format may be used to carry an indicator of half-duplex recognition and also to require that UE-to-UE adjustment feedback is not provided.

[0176] (C) Feedback on half-duplex in reception

[0177] If the RX UE R has a half-duplex problem in receiving a transmission by the TX UE P , the transmission by the UE P is worthless, and thus, when feedback is provided to the UE R by the UE P in time, it is expected that the transmission of the reserved resources will occur. Therefore, it is necessary to discriminate the half-duplex in the case of reception collision from other sidelink collisions.

[0178] (D) Determination of co-channel collision conflicts

[0179] If the TX UE is not a group member and has no potential interest in each other's transmissions within the same slot, the co-channel collision problem may still exist. In some of the multiple scenarios, it may be necessary to distinguish / differentiate collision conflicts and configure which type of multiple collision types can be addressed by the adjustment feedback between UEs.

[0180] (D.1) Type-1: Hidden Node - The TX UE exists outside the sensing range or has a small RSRP range.

[0181] (D.2) Type-2: Simultaneous Access - The TX UE exists within the sensing range and accesses the channel simultaneously.

[0182] (D.3) Type-3: Congested Medium - The TX UE exists within the sensing range and the medium is congested.

[0183] RX UE (UE R ) The conditions for determining the co-channel collision event by may include one or more of the following conditions.

[0184] (a) RX UE R has successfully decoded the control channel transmissions from UE P and UE Q (SCI Formats - stage 1 and / or stage 2), and is measuring the SL-RSRP of the link towards the TX UE.

[0185] (b) RX UE R is determining the resource duplication at the frequency for the transmission of the same channel of the UE P or the UE Q . The ratio or percentage of the duplicated resources in a single transmission exceeds a predefined or preconfigured threshold (e.g., full duplication (100%), partial duplication (e.g., 50%), or duplication in at least one subchannel (>0%)).

[0186] (c) RX UE R is determining that it is close to the UE P or the UE Q . (For example, like the value being within a preconfigured SL-RSRP range or meeting the SL-RSRP or distance boundary), it may be estimated that the value of the sidelink RSRP of the RX UE R or the distance to the TX UE meets the preconfigured settings.

[0187] (d) RX UE R is determining / analyzing the criteria related to the probability of successful reception for the UE P or the UE Q . In some of the multiple aspects, the SINR P value and / or the SINR Q value exist within a preconfigured range for the RX UE R . In some of the multiple aspects, the predicted PER P / PER Q> It is a pre-configured or pre-defined PER threshold. In some of the multiple aspects, the estimated mutual information / capacity or effective MCS for the PSSCH for both or one of the multiple colliding UEs is smaller than the pre-configured or pre-defined threshold. In some of the multiple aspects, the priority of the colliding SL transmission is greater than the pre-configured or pre-defined threshold.

[0188] Alternatively, the determination of sidelink collisions by the RX UE may be left to the UE implementation.

[0189] In some of the multiple aspects, the main type of collision depends on the medium environment (e.g., vehicle density and transmission intensity, etc.). Regarding radio layer metrics, it may be characterized by measurements related to congestion control such as channel occupancy rate (CR) and channel busy ratio (CBR). These metrics may be used to adapt the behavior of the RX UE for UE-to-UE adjustment feedback and related thresholds.

[0190] In some of the multiple aspects, it may be possible to exclude the generation of feedback for a specific type of collision by pre-configuration or by specification. For example, the configuration may allow only feedback for type 2 or type 1 / type 2 collisions. In this case, a specific set of conditions may be configured to distinguish each collision type.

[0191] In some of the aspects, the disclosed technology includes a method for determining sidelink half-duplex and collision events by a plurality of transmitting UEs and enhanced resource re-selection procedures. The disclosed technology includes classification of sidelink conflicts, autonomous determination of sidelink conflicts by a TX UE as part of a sensing procedure, autonomous determination of sidelink conflicts by an RX UE as part of a sensing procedure, and RX-based feedback indicating sidelink conflicts to the TX UE, and UE behaviors such as TX-based resource allocation enhancement based on inter-UE coordination feedback.

[0192] In NR sidelink communication, there may be conflicts such as half-duplex in transmission (HD-TX), half-duplex in reservation (HD-RSV), half-duplex in reception (HD-RX), co-channel collision in transmission (CC-TX), and co-channel collision in reservation (CC-RSV).

[0193] Generally, each of these conflicts may affect the behavior of the TX UE. Additionally, some of those conflicts (such as conflicts in reservation, etc.) may be addressed / mitigated using either inter-UE coordination feedback or UE autonomous conflict resolution.

[0194] In some of the embodiments, the UEP and UE Q When SCI transmissions in slots "nP" and "nQ" indicate reservation of resources in the same slot "k", the TX UE (UE P or UE Q ) may autonomously detect and classify some of them and take necessary measures. To autonomously detect conflicts in reservations, UEs need to be within communication range of each other and need to transmit in multiple different slots (i.e., nP≠nQ).

[0195] In some of the multiple aspects, the UE P and UE Q When transmitting in multiple different slots, the UE P and UE Q do not have to reserve resources in the same slot, but may be the case as follows for various reasons.

[0196] Delay in sensing and resource (re)-selection processing;

[0197] (b) Lack of sensing results; and

[0198] (c) Half-duplex events due to UE transmissions

[0199] TX UE (UE P or UE Q ) In the case of autonomous conflict detection and classification, the following TX UE behaviors are possible.

[0200] (a) Option 1: Trigger resource yielding (i.e., exclude reserved resources from candidate resources) and a resource (re)-selection procedure.

[0201] (a.1) Option 1A: Resource generation is performed only when the priority of the sidelink transmission of the TX UE is lower or the same as that of the sidelink transmission (like the behavior of the UE when preemption is enabled in Rel. 16).

[0202] (a.2) Option 1B: Resource generation is performed regardless of the priority of the sidelink transmission.

[0203] (b) Option 2: Trigger the resource (re)selection / (re)evaluation procedure without excluding the reserved resources affected by the candidate resources.

[0204] (b.1) Options regarding the use of priority

[0205] (b.1.1) Alternative A: Resource (re)selection / (re)evaluation is performed only when the priority of the sidelink transmission of the TX UE is lower or the same as that of the sidelink transmission.

[0206] (b.1.2) Alternative B: Resource (re)selection / (re)evaluation is performed regardless of the priority of the sidelink transmission.

[0207] (b.2) Use of SL-RSRP

[0208] In some of the multiple aspects, a pair of prio_TX and prio_RX may provide a certain SL-RSRP threshold, where prio_TX is the priority associated with the current UE's transmission, prio_RX is the priority received in the SCI for the colliding resources, and prio_TX and prio_RX are configured separately from the set of SL-RSRP thresholds used for the normal (re)selection and (re)evaluation procedures.

[0209] (c) Option 3: Continuous transmission on the reserved resources

[0210] (c.1) Option 3A: The UE continues transmission on the reserved resources only if the priority of the UE's sidelink transmission is higher or equal.

[0211] (c.2) Option 3B: The UE continues transmission on the reserved resources regardless of the priority of the sidelink transmission (behavior when preemption in Rel.16 is disabled).

[0212] (c.3) Option 4: The operation of the UE is left to the implementation.

[0213] In some of the multiple aspects, TX UE-based autonomous detection and classification of sidelink conflicts is feasible and beneficial for conflicts in reservation. The main advantage of the autonomous detection of conflicting UEs is that the TX UE can extract additional information regarding the priority and proximity of the UEs involved in the conflict, and thus, depending on the conditions, the TX UE can determine the optimal strategy (i.e., the above alternatives) as the behavior for subsequent transmissions. This function may be further complemented by UE-to-UE adjustment feedback for conflicts in transmission and / or conflicts in reservation.

[0214] In some of the multiple aspects, the behavior of the TX UE may depend on the type of UE-to-UE adjustment feedback provided, as described below.

[0215] (a) When the TX UE receives feedback indicating a co-channel collision in transmission on the same channel, it is possible to consider the following behavior.

[0216] (a.1) Option 1: In addition to the Rel.16 functions, there is no change in behavior. In this case, the communication may support a configuration that can eliminate the generation of feedback for collisions of the same channel by the RX UE, or the feedback for collisions of the same channel should not be supported by NR.

[0217] (a.2) Option 2: Adjustment of retransmission

[0218] (a.2.1) Option 2A: The UE may select additional resources for retransmission until it reaches the maximum number of retransmissions for a given priority.

[0219] (a.2.2) Option 2B: If the UE is configured for a given priority, the UE may increase the maximum number of retransmissions per TB for the given priority level by Δ (e.g., Δ = 1). The increment value Δ may also depend on the number of feedbacks received by the TX UE for the given TB.

[0220] (a.2.3) Option 2C: Depending on the implementation, the UE may change the redundant version for the next transmission.

[0221] (b) If the TX UE receives feedback indicating half-duplex in transmission, the same behavior regarding feedback for collisions in transmission may be used.

[0222] (b.1) Assuming that the operation of the TX UE may be the same, there is no need to distinguish between half-duplex in transmission and collision in transmission.

[0223] (c) If the TX UE receives feedback indicating half-duplex in reservation or collision in the reservation, the following behavior can be considered.

[0224] (c.1) Option 1: In addition to the Rel.16 functionality, there is no change in behavior. In this case, the communication may support a configuration that can eliminate the generation of feedback for half-duplex / same-channel collisions in the reservation by the RX UE, or the feedback for half-duplex / same-channel collisions in the reservation should not be supported by NR.

[0225] (c.2) Option 2: Adjustment of retransmission

[0226] (c.2.1) Option 2A: The UE may select additional resources for retransmission until it reaches the maximum number of retransmissions for a given priority.

[0227] (c.2.2) Option 2B: If the UE is configured for a given priority, the UE may increase the maximum number of retransmissions per TB for the given priority level by Δ (e.g., Δ = 1). The increment value Δ may also depend on the number of feedbacks received for the TB given to the TX UE.

[0228] (c.3) Option 3: Follow the same behavior as the UE's autonomous collision detection. In this case, the feedback may also be considered to indicate the priority of the detected collision transmissions. In some of the multiple aspects, moreover, Options 1 to 4 described for the UE's autonomous collision detection and mitigation may be used.

[0229] (c.4) Option 4: It follows the same behavior as the UE's autonomous collision detection, but has no accurate knowledge about the priority of sidelink transmissions. In this case, the feedback does not indicate the priority of the detected transmissions during a collision, and thus the TX UE has to assume that the priorities of the colliding transmissions are the same, higher, or lower. The latter may be pre-configured or pre-defined. In some of the multiple aspects, moreover, Options 1 to 4 described for the UE's autonomous collision detection and mitigation may be used.

[0230] In some of the multiple aspects, when the TX UE receives feedback indicating half-duplex in reception, the Tx UE may be expected to perform a transmission. In addition to performing a transmission on the reserved resources, all of the other above options may be used if applicable.

[0231] FIG. 11 illustrates a block diagram of a communication device such as an evolved Node B (eNB), a new generation Node B (gNB) (or other RAN node or base station), a transmission and reception point (TRP), an access point (AP), a wireless station (STA), a mobile station (MS), or a user equipment (UE), etc., according to some of the multiple aspects. In an alternative aspect, the communication device 1100 may operate as a stand-alone device or may be connected to other communication devices (such as being networked, for example).

[0232] A circuit (e.g., a processing circuit, etc.) is a set of circuits implemented within a tangible entity of a device 1100 that includes hardware (e.g., simple circuits, gates, logic, etc.). Circuit membership may be flexible over time. A circuit includes members that can perform the specified operations when operating, either alone or in combination. In one example, the hardware of a circuit may be designed to be invariant (e.g., connected by wiring, etc.) to perform a particular operation. In one example, the hardware of a circuit includes a machine-readable medium (e.g., magnetic, electrical, movable arrangement of immovable particles, etc.) that is physically modified to encode instructions for that particular operation, and includes variable-connected physical components (e.g., execution units, transistors, simple circuits, etc.).

[0233] When connecting physical components, the underlying electrical characteristics of the hardware components change, for example, from an insulator to a conductor or vice versa. Instructions enable embedded hardware (e.g., an execution unit or a loading mechanism, etc.) to create members of a circuit within the hardware via variable connections and perform part of a particular operation during operation. Thus, in one example, a machine-readable medium element is part of a circuit or communicatively coupled to other components of the circuit when the device is operating. In one example, any of the plurality of physical components may be used in more than one member of more than one circuit. For example, during operation, an execution unit may be used by the first circuit among the first circuits at one point in time and reused by the second circuit in the first circuit or by the third circuit in the second circuit at different points in time. Additional examples of these components related to device 1100 are shown below.

[0234] In some of the plurality of aspects, device 1100 may operate as a stand-alone device or may be connected to other devices (such as being networked). In a networked deployment, communication device 1100 may operate as a server communication device, a client communication device, or both in a server-client network environment. In one example, communication device 1100 may operate as a peer communication device in a peer-to-peer (P2P) network environment (or other distributed network environment). Communication device 1100 may be any communication device capable of executing (sequential or other) instructions that specify the operations to be performed by a UE, eNB, PC, tablet PC, STB, PDA, mobile phone, smartphone, web device, network router, switch or bridge, or the communication device itself. Further, although only a single communication device is illustrated, the term "communication device" also includes any set of communication devices, and the set of communication devices may individually or jointly execute a set (or multiple sets) of instructions for performing any one or more of the methodologies described herein, such as cloud computing, software as a service (SaaS), and other computer cluster configurations.

[0235] As described herein, the various examples may include or operate in the form of logic or a number of components, modules, or mechanisms. A module is a tangible entity (e.g., such as hardware) capable of performing the specified operations and may be configured or arranged in a particular manner. In one example, a circuit may be arranged as a module in a specified manner (e.g., internally or with respect to external entities such as other circuits). In one example, all or part of one or more computer systems or one or more hardware processors (e.g., such as a stand-alone computer system, a client computer system, or a server computer system) may be configured by firmware or software (e.g., such as instructions, an application portion, or an application) as a module that operates to perform the specified operations. In one example, the software may reside on a communication device-readable medium. In one example, the software causes the hardware to perform the specified operations when executed by the hardware underlying the module.

[0236] Accordingly, the term "module" is understood to include a tangible entity, or an entity physically constructed (e.g., wired-connected), specifically configured (e.g., in a specified manner of operation or to perform some or all of any of the operations described herein), or temporarily (e.g., transiently) configured (e.g., programmed). Considering an example where a module is temporarily configured, each of the plurality of modules need not be instantiated at any one point in time. For example, if the plurality of modules includes a general-purpose hardware processor configured using software, the general-purpose hardware processor may be configured as different modules at different points in time. Thus, software may configure the hardware processor, and the hardware processor may configure a particular module at one point in time and a different module at a different point in time.

[0237] (For example, a) communication device 1100 (such as a UE) includes a hardware processor 1102 (such as a central processing unit (CPU), a graphics processing unit (GPU), a hardware processor core, or any combination thereof), a main memory 1104, a static memory 1106, and a storage device 1107 (such as a hard drive, a tape drive, a flash memory device, or other block or storage device), and some or all of them may communicate with each other via an interlink 1108 (such as a bus).

[0238] The communication device 1100 may further include a display device 1110, an alphanumeric input device 1112 (such as a keyboard, etc.), and a user interface (UI) navigation device 1114 (such as a mouse, etc.). In one example, the display device 1110, the input device 1112, and the UI navigation device 1114 may be a touch screen display. The communication device 1100 may additionally include a signal generation device 1118 (such as a speaker, etc.), a network interface device 1120, and one or more sensors 1121 such as a global positioning system (GPS) sensor, a compass, an accelerometer, or other sensors. The communication device 1100 includes an output controller 1128 such as a serial bus connection (such as a universal serial bus (USB), etc.), a parallel bus connection, or other wired or wireless connections (such as infrared (IR), near field communication (NFC), etc.) to communicate with or control one or more peripheral device(s) (such as a printer, a card reader, etc.).

[0239] The memory device 1107 may include a communication device-readable medium 1122, and the communication device-readable medium 1122 stores one or more sets of data structures or instructions (such as software, etc.), and one or more sets of those data structures or instructions may embody or be utilized by any one or more of the technologies or functions described herein. In some of the multiple aspects, the registers of the processor 1102, the main memory 1104, the static memory 1106, and / or the memory device 1107 may be the device-readable medium 1122, or may include (fully or at least partially) the device-readable medium 1122, and the device-readable medium 1122 may embody or be utilized by any one or more of the technologies or functions described herein. In one example, one or any combination of the hardware processor 1102, the main memory 1104, the static memory 1106, or the mass storage device 1116 may constitute the device-readable medium 1122.

[0240] As used herein, the term "device-readable medium" is interchangeable with "computer-readable medium" or "machine-readable medium". Although the communication device-readable medium 1122 is shown as a single medium, the term "communication device-readable medium" may include a single medium or multiple media configured to store one or more instructions 1124 (e.g., a centralized database or a distributed database, and / or related caches and servers, etc.). The term "communication device-readable medium" includes "machine-readable medium" or "computer-readable medium", and may include any of the media, any of which can store, encode, or carry instructions (such as instructions 1124, etc.) for execution by the communication device 1100, and enable the communication device 1100 to execute any one or more of the plurality of technologies of the present disclosure, or store, encode, or carry a data structure used by or related to such instructions. Non-limiting examples of communication device-readable media may include solid-state memory and optical and magnetic media. Specific examples of communication device-readable media may include semiconductor memory devices (such as electrically programmable read-only memory (EPROM), electrically erasable and programmable read-only memory (EEPROM), etc.) and non-volatile memory such as flash memory devices, magnetic disks such as internal hard disks and removable disks, magneto-optical disks, random access memory (RAM), and CD-ROM disks and DVD-ROM disks. In some of the plurality of examples, the communication device-readable medium may include a non-transitory communication device-readable medium. In some of the plurality of examples, the communication device-readable medium may include a communication device-readable medium that is not a transient propagation signal.

[0241] Further, a network interface device 1120 that utilizes any one of a number of transfer protocols may transmit and receive instructions 1124 via a communication network 1126 using a transmission medium. In one example, the network interface device 1120 may include one or more physical jacks (e.g., Ethernet, coaxial, or phone jacks, etc.) for connecting to the communication network 1126, or one or more antennas. In one example, the network interface device 1120 may include multiple antennas for wireless communication using at least one of single input multiple output (SIMO), MIMO, or multiple input single output (MISO) technologies. In some examples, the network interface device 1120 may communicate wirelessly using multi-user MIMO technology.

[0242] The term "transmission medium" is used to include any intangible medium capable of storing, encoding, or carrying instructions for execution by the communication device 1100, and also includes digital or analog communication signals that facilitate such software communication, or other intangible media. In this regard, the transmission medium in the context of this disclosure is a device-readable medium.

[0243] The terms "machine-readable medium", "computer-readable medium", and "device-readable medium" mean the same thing and may be used interchangeably in this disclosure. Those terms are defined to include both machine storage media and transmission media. Thus, those terms include both memory devices / media and carrier waves / modulated data signals.

[0244] The described implementations of the subject matter may include one or more features, alone or in combination, as explained below by way of example.

[0245] An apparatus for a user equipment (UE) configured to operate in a fifth generation new radio (5G NR) network, the apparatus comprising: a processing circuit that, when configuring the UE for sidelink operation in the 5G NR network, the processing circuit: encodes a first sidelink control information (SCI) for transmission, the first SCI including a first resource reservation for subsequent sidelink transmission by the UE in a preselected slot; decodes a second SCI received from a second UE, the second SCI including a second resource reservation for subsequent sidelink transmission by the second UE in the preselected slot; detects a reservation conflict based on the first resource reservation and the second resource reservation using the preselected slot; is configured to encode a third SCI for transmission based on the detection of the reservation conflict, the third SCI including a modified version of the first resource reservation for the subsequent sidelink transmission by the UE; a processing circuit; a memory coupled to the processing circuit and configured to store the first SCI, the second SCI, and the third SCI.

[0246] In example 2, the subject matter of example 1 includes the subject matter where the processing circuit is configured to exclude the preselected slot from candidate sidelink resources to obtain modified sidelink resources.

[0247] In example 3, the subject matter of example 2 includes the subject matter where the processing circuit selects a second slot from the modified sidelink resources and configures the third SCI to indicate the second slot as the modified version of the first resource reservation.

[0248] In Example 4, the subject matter of Examples 2 to 3 includes the subject matter in which the processing circuit is configured to exclude the preselected slot from candidate sidelink resources based on the priority of sidelink transmissions related to the subsequent sidelink transmissions by the UE.

[0249] In Example 5, the subject matter of Example 4 includes the subject matter in which the processing circuit is configured to exclude the preselected slot from candidate sidelink resources when the priority of the sidelink transmission is lower than the priority of sidelink transmissions related to the subsequent sidelink transmissions by the second UE.

[0250] In Example 6, the subject matter of Examples 1 to 5 includes the subject matter in which the processing circuit is configured to determine the priority of sidelink transmissions related to the subsequent sidelink transmissions by the second UE using the second SCI.

[0251] In Example 7, the subject matter of Example 6 includes the subject matter in which the processing circuit is configured to determine whether to continue the subsequent sidelink transmissions by the UE in the preselected slot based on the priority of the sidelink transmissions related to the subsequent sidelink transmissions by the second UE.

[0252] In Example 8, the subject matter of Examples 6 to 7 includes the subject matter in which the processing circuit is configured to determine to continue the subsequent sidelink transmissions by the UE in the preselected slot when the priority of the sidelink transmissions related to the subsequent sidelink transmissions by the second UE is lower than the priority of sidelink transmissions related to the subsequent sidelink transmissions by the UE.

[0253] In Example 9, the subject matter of Examples 1 to 8 is that the processing circuit Decode the feedback information from the second UE, the feedback information indicating a conflict of the reservation based on the first resource reservation and the second resource reservation using the preselected slot, and configured to encode a fourth SCI for transmission based on the feedback information, the fourth SCI including the modified version of the first resource reservation, the modified version indicating a second slot for subsequent sidelink transmission by the UE, including the subject matter.

[0254] In Example 10, the subject matter of Examples 1 to 9 includes a transceiver circuit coupled to the processing circuit and one or more antennas coupled to the transceiver circuit.

[0255] Example 11 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for sidelink operation in a fifth generation new radio (5G NR) network, the UE to an operation of encoding a first sidelink control information (SCI) for transmission, the first SCI including a first resource reservation for subsequent sidelink transmission by the UE in a preselected slot, and an operation of decoding feedback information from a second UE, the feedback information indicating a conflict of reservation based on the first resource reservation and a second resource reservation by the second UE using the preselected slot, and an operation of encoding, based on the feedback information, a second SCI for transmission, the second SCI including a modified version of the first resource reservation, the modified version indicating a second slot for subsequent sidelink transmission by the UE, the computer-readable storage medium causing the operations to be performed.

[0256] In Example 12, the subject matter of Example 11 is that the operation is an operation of decoding a third SCI received from the second UE, an operation of determining a priority of a sidelink transmission associated with the second resource reservation by the second UE using the third SCI, and an operation of determining whether to continue the subsequent sidelink transmission by the UE in the preselected slot based on the priority of the sidelink transmission associated with the second resource reservation by the second UE. The subject matter includes the above.

[0257] Example 13 is a computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for sidelink operations in a fifth-generation new radio (5G NR) network, and causing the UE to perform an operation of encoding a first sidelink control information (SCI) for transmission, the first SCI including a first resource reservation for subsequent sidelink transmission by the UE in a preselected slot, perform an operation of decoding a second SCI received from a second UE, the second SCI including a second resource reservation for subsequent sidelink transmission by the second UE in the preselected slot, perform an operation of detecting a reservation conflict based on the first resource reservation and the second resource reservation using the preselected slot, and perform an operation of encoding a third SCI for transmission based on the detection of the reservation conflict, the third SCI including a modified version of the first resource reservation for the subsequent sidelink transmission by the UE. The computer-readable storage medium causes the above operations to be executed.

[0258] In Example 14, the subject matter of Example 13 is that the operation is Further including an operation of excluding the pre-selected slot from the candidate sidelink resource to obtain a modified sidelink resource.

[0259] In Example 15, the subject matter of Example 14 is that the operation includes an operation of selecting a second slot from the modified sidelink resource and includes an operation of configuring the third SCI to indicate the second slot as the modified version of the first resource reservation.

[0260] In Example 16, the subject matter of Examples 14 to 15 is that the operation further includes an operation of excluding the pre-selected slot from the candidate sidelink resource based on the priority of the sidelink transmission related to the subsequent sidelink transmission by the UE.

[0261] In Example 17, the subject matter of Example 16 is that the operation further includes an operation of excluding the pre-selected slot from the candidate sidelink resource when the priority of the sidelink transmission is lower than the priority of the sidelink transmission related to the subsequent sidelink transmission by the second UE.

[0262] In Example 18, the subject matter of Examples 13 to 17 is that the operation further includes an operation of determining the priority of the sidelink transmission related to the subsequent sidelink transmission by the second UE using the second SCI.

[0263] In Example 19, the subject matter of Example 18 is that the operation further includes an operation of determining whether to continue the subsequent sidelink transmission by the UE in the pre-selected slot based on the priority of the sidelink transmission related to the subsequent sidelink transmission by the second UE.

[0264] In Example 20, the subject matter of Examples 18 to 19 includes that the operation determines to continue the subsequent sidelink transmission by the UE in the preselected slot when the priority of the sidelink transmission related to the subsequent sidelink transmission by the second UE is lower than the priority of the sidelink transmission related to the subsequent sidelink transmission by the UE, further including such an operation.

[0265] Example 21 is at least one machine-readable medium including instructions that, when executed by a processing circuit, cause the processing circuit to perform an operation of implementing any one of Examples 1 to 20.

[0266] Example 22 is an apparatus including means for implementing any one of Examples 1 to 20.

[0267] Example 23 is a system implementing any one of Examples 1 to 20.

[0268] Example 24 is a method implementing any one of Examples 1 to 20.

[0269] Although one particular exemplary aspect has been described with reference to specific exemplary aspects, it will become apparent that various modifications and changes can be made to those aspects without departing from the broader scope of the present disclosure. Accordingly, the specification and drawings are to be regarded in an illustrative rather than a limiting sense. Therefore, the detailed description of this invention should not be construed as having a limiting meaning, and the scope of the various aspects is defined only by the appended claims and the full scope of all equivalents to which the claims are entitled.

Claims

1. An apparatus for a user equipment (UE) configured to operate in a new 5th generation wireless (5G NR) network, the apparatus comprising: a processing circuit that, when configuring the UE for sidelink communication in the 5G NR network, decodes a sidelink control information (SCI) format 1-A to obtain a set of resources, the set of resources including resource blocks and one or more slots reserved for physical sidelink shared channel (PSSCH) transmission, detects a half-duplex collision associated with a slot in the set of resources, and encodes collision information regarding the half-duplex collision for transmission to a second UE via a physical sidelink feedback channel (PSFCH), a memory coupled to the processing circuit and configured to store the SCI, wherein the UE is configured to refrain from receiving on the PSSCH due to half-duplex operation in the one or more slots when the half-duplex collision is detected. Apparatus.

2. The apparatus of claim 1, wherein the UE is an intended receiver of the second UE for the one or more slots reserved for PSSCH transmission.

3. The processing circuit is configured to obtain modified sidelink resources by excluding the slot from the set of resources, the apparatus of claim 1.

4. The processing circuit is configured to encode a second SCI for transmission to the second UE based on the detection of the half-duplex collision, the second SCI including the modified sidelink resources, the apparatus of claim 3.

5. The processing circuit is configured to exclude the slot from the set of resources based on a priority of a sidelink transmission associated with the PSSCH transmission by the UE, the apparatus of claim 3.

6. The processing circuit is configured to exclude the slot from the set of resources when the priority of the sidelink transmission is lower than a priority of a sidelink transmission associated with a subsequent sidelink transmission by the second UE, the apparatus of claim 5.

7. The processing circuit is When the priority of the sidelink transmission associated with the subsequent sidelink transmission by the second UE is lower than the priority of the sidelink transmission associated with the subsequent sidelink transmission by the UE, the apparatus according to claim 6 is configured to determine to continue the subsequent sidelink transmission by the UE in the slot.

8. The processing circuit decodes feedback information from the second UE, the feedback information indicating the half-duplex contention, and is configured to encode a second SCI for transmission based on the feedback information, the second SCI including the modified sidelink resource, the modified sidelink resource indicating a second slot for subsequent sidelink transmission by the UE, the apparatus according to claim 3.

9. a transceiver circuit coupled to the processing circuit, and further includes one or more antennas coupled to the transceiver circuit, the apparatus according to claim 1.

10. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for sidelink communication in a fifth-generation new radio (5G NR) network, the UE to encode a first sidelink control information (SCI) for transmission, the first SCI including a first resource reservation for subsequent sidelink transmission by the UE in a preselected slot, decode feedback information from a second UE, the feedback information indicating a reservation conflict based on the first resource reservation using the preselected slot and a second resource reservation by the second UE, encode a second SCI for transmission based on the feedback information, the second SCI including a modified version of the first resource reservation, the modified version indicating a second slot for the subsequent sidelink transmission by the UE, A non-transitory computer-readable storage medium.

11. The UE further decodes a third SCI received from the second UE, an operation of determining a priority of sidelink transmission associated with the second resource reservation by the second UE using the third SCI; an operation of determining whether to continue the subsequent sidelink transmission by the UE in the preselected slot based on the priority of the sidelink transmission associated with the second resource reservation by the second UE, The non-transitory computer-readable storage medium according to claim 10, configured to execute an operation including the above.

12. A non-transitory computer-readable storage medium storing instructions for execution by one or more processors of a user equipment (UE), the instructions configuring the UE for sidelink communication in a fifth generation new radio (5G NR) network, the UE being an operation of decoding a sidelink control information (SCI) format 1-A to obtain a set of resources, the set of resources including resource blocks and one or more slots reserved for physical sidelink shared channel (PSSCH) transmission; an operation of detecting a half-duplex collision associated with a slot in the set of resources; and encoding collision information regarding the half-duplex collision for transmission to a second UE via a physical sidelink feedback channel (PSFCH). The UE is configured to refrain from receiving in the PSSCH due to half-duplex operation in the one or more slots when the half-duplex collision is detected. The UE is configured to refrain from receiving in the PSSCH due to half-duplex operation in the one or more slots when the half-duplex collision is detected. Non-transitory computer-readable storage medium.

13. The UE is the intended receiver of the second UE for the one or more slots reserved for the PSSCH transmission, The non-transitory computer-readable storage medium according to claim 12.

14. The UE further is configured to execute an operation including an operation of excluding the slot from the set of resources to obtain a modified sidelink resource, The non-transitory computer-readable storage medium according to claim 12.

15. The UE further configured to perform operations including an operation of encoding a second SCI for transmission to the second UE based on detection of the semi-duplex conflict, the second SCI including the modified sidelink resource, the non-transitory computer-readable storage medium of claim 14. **Claim 16** The UE further is configured to perform operations including an operation of excluding the slot from the set of resources based on a priority of a sidelink transmission associated with the PSSCH transmission by the UE, the non-transitory computer-readable storage medium of claim 14. **Claim 17** The UE further is configured to perform operations including an operation of excluding the slot from the set of resources when a priority of the sidelink transmission is lower than a priority of a sidelink transmission associated with a subsequent sidelink transmission by the second UE, the non-transitory computer-readable storage medium of claim 16. **Claim 18** The UE further is configured to perform operations including an operation of determining to continue a subsequent sidelink transmission by the UE in the slot when a priority of the sidelink transmission associated with the subsequent sidelink transmission by the second UE is lower than a priority of a sidelink transmission associated with a subsequent sidelink transmission by the UE, the non-transitory computer-readable storage medium of claim 17.

Images