Mode 1 support for cross-mode coordination and inter-UE coordination

Abstract

This disclosure relates to cross-mode coordination and Mode 1 support for inter-UE coordination. An implementation scheme for exchanging sidelink (SL) capabilities between a first UE and a second UE via a PC 5 link for configuring inter-UE coordination (IUC) is disclosed. In one implementation, a method involves generating a Radio Resource Control (RRC) message for the second UE, the RRC message including information identifying the type of IUC supported by the first UE or providing an indication of which resource allocation mode the IUC supports; signaling the RRC message to the second UE via a first SL unicast transmission; and receiving the SL capabilities for configuring the IUC from the second UE via a second SL unicast transmission. Techniques for performing IUC with a UE configured for Mode 1 (network-controlled) sidelink (SL) resource allocation are also disclosed.

Description

Technical Field

[0001] This application relates to wireless communication systems in general, including coordination between UEs. Background Technology

[0002] Wireless mobile communication technologies use various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include 3GPP Long Term Evolution (LTE) (e.g., 4G) or New Radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, commonly referred to by the industry organization as WiMAX; and the IEEE 802.11 standard for Wireless Local Area Networks (WLANs), commonly referred to by the industry organization as Wi-Fi. In the 3GPP Radio Access Network (RAN) of an LTE system, a base station may include RAN nodes such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as Evolved Node B, Enhanced Node B, eNodeB, or eNB) and / or a Radio Network Controller (RNC) in the E-UTRAN, which communicates with wireless communication equipment called User Equipment (UE). In the fifth generation (5G) wireless RAN, RAN nodes may include 5G nodes and NR nodes (also known as next-generation node B or g NodeB (gNB)).

[0003] The RAN uses Radio Access Technology (RAT) to communicate between RAN nodes and UEs. The RAN can include Global System for Mobile Communications (GSM), Enhanced Data Rate GSM Evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and / or E-UTRAN, which provides access to communication services through the core network. Each RAN operates according to a specific 3GPP RAT. For example, GERAN implements the GSM and / or EDGE RAT, UTRAN implements the Universal System for Mobile Communications (UMTS) RAT or other 3GPP RATs, E-UTRAN implements the LTE RAT, and NG-RAN implements the 5G RAT. In some deployments, E-UTRAN may also implement the 5G RAT.

[0004] 5G NR frequency bands can be divided into two distinct frequency ranges. Frequency range 1 (FR1) may include bands operating at frequencies below 6 GHz, some of which are available for previous standards and can potentially be extended to cover new spectrum offerings from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include bands from 24.25 GHz to 52.6 GHz. The bands in the millimeter-wave (mmWave) range of FR2 may have a smaller range than those in FR1 but potentially higher available bandwidth. Those skilled in the art will recognize that these frequency ranges, presented by way of example, may vary over time or in different regions. Attached Figure Description

[0005] To facilitate identification of any particular element or action being discussed, one or more of the most significant digits in the reference numerals refer to the drawing number in which the element was first introduced.

[0006] Figure 1 This is a block diagram of a wireless communication system.

[0007] Figure 2 This is a note message diagram illustrating an example of request and response signaling used for coordination between UEs.

[0008] Figure 3 It is a set of three annotated block diagrams illustrating the half-duplex problem and the hidden terminal problem in a vehicle-to-vehicle communication system.

[0009] Figure 4 This is a table showing the coordination and compatibility between regular UEs.

[0010] Figure 5 This is a flowchart illustrating a routine for capability exchange via the PC5 link.

[0011] Figure 6 This is a pair of annotated diagrams illustrating the half-duplex and hidden terminal issues in intra-gNB IUC deployments.

[0012] Figure 7 This is a note message diagram illustrating the IUC mechanism and signaling of a Mode 1 UE.

[0013] Figure 8 This is a flowchart illustrating the IUC mechanism and signaling of a Mode 1 UE.

[0014] Figure 9 This is a pair of annotated diagrams illustrating the half-duplex and hidden terminal issues in inter-gNB IUC deployments.

[0015] Figure 10 It is a block diagram based on an implementation plan. Detailed Implementation

[0016] Figure 1 Exemplary architectures of system 100 for networks according to various implementations are shown. The following description is provided for example system 100 operating in combination with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary implementations are not limited in this respect, and the implementations can be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G)) systems, IEEE 1002.16 protocols (e.g., WLAN, WiMAX, etc.).

[0017] like Figure 1 As shown, system 100 includes UE 122 and UE 120. In this example, UE 122 and UE 120 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as consumer electronics devices, mobile phones, smartphones, feature phones, tablets, wearable computing devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptops, in-vehicle infotainment (IVI), in-vehicle entertainment (ICE) devices, instrument cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminal (MDT), electronic engine management system (EEMS), electronic / engine control unit (ECU), electronic / engine control module (ECM), embedded systems, microcontrollers, control modules, engine management system (EMS), connected or “smart” appliances, MTC devices, M2M, IoT devices, etc.

[0018] In some implementations, UE 122 and / or UE 120 may be IoT UEs, which may include a network access layer designed to utilize low-power IoT applications with short-lived UE connections. IoT UEs may utilize technologies such as M2M or MTC to exchange data with MTC servers or devices via PLMN, ProSe, or D2D communication, sensor networks, or IoT networks. M2M or MTC data exchange may be machine-initiated data exchange. An IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. IoT UEs may execute background applications (e.g., keeping track of activity messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0019] UE 122 and UE 120 can be configured to connect to an access node or radio access node (shown as (R)AN 108), for example, through communication coupling. In implementations, (R)AN 108 can be an NG RAN or SG RAN, E-UTRAN, or a legacy RAN such as UTRAN or GERAN. As used herein, the term "NG RAN," etc., can refer to (R)AN 108 operating in an NR or SG system, and the term "E-UTRAN," etc., can refer to (R)AN 108 operating in an LTE or 4G system. UE 122 and UE 120 utilize connections (or channels) (shown as connection 104 and connection 102, respectively), each of which includes a physical communication interface or layer (discussed in further detail below).

[0020] In this example, connection 104 and connection 102 are air interfaces for communication coupling and are compatible with cellular communication protocols such as GSM, CDMA, PTT, POC, UMTS, 3GPP LTE, SG, NR, and / or any other communication protocols discussed herein. In an implementation, UE 122 and UE 120 may directly exchange communication data via ProSe interface 110. ProSe interface 110 may alternatively be referred to as sidelink (SL) interface 110 and may include one or more logical channels, including but not limited to PSCCH, PSSCH, PSDCH, and PSBCH.

[0021] UE 120 is shown configured to access AP 112 (also referred to as a "WLAN node", "WLAN", "WLAN terminal", "WT", etc.) via connection 124. Connection 124 may include local wireless connectivity, such as a connection consistent with any IEEE 1002.11 protocol, where AP 112 will include Wireless Fibre. Router. In this example, AP 112 may connect to the Internet but not to the core network of the wireless system (described in further detail below). In various implementations, UE 120, (R)AN108, and AP 112 may be configured to utilize LWA operation and / or LWIP operation. LWA operation may involve UE 120 in RRC_CONNECTED being configured by RAN node 114 or RAN node 116 to utilize the radio resources of LTE and WLAN. LWIP operation may involve UE 120 using WLAN radio resources (e.g., connection 124) to authenticate and encrypt packets (e.g., IP packets) transmitted via connection 124 via IPsec protocol tunneling. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header to protect the original header of the IP packet.

[0022] (R)AN 108 may include one or more AN nodes, such as RAN node 114 and RAN node 116, that implement connection 104 and connection 102. As used herein, the terms “access node,” “access point,” etc., can describe equipment that provides radio baseband functionality for data and / or voice connections between the network and one or more users. These access nodes may be referred to as BS, gNB, RAN node, eNB, NodeB, RSU, TRxP, or TRP, etc., and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms “NG RAN node,” etc., can refer to a RAN node (e.g., gNB) operating in an NR or SG system, while the terms “E-UT RAN node,” etc., can refer to a RAN node (e.g., eNB) operating in an LTE or 4G system 100. According to various implementation schemes, RAN node 114 or RAN node 116 may be implemented as one or more of dedicated physical devices such as macro cell base stations and / or low-power (LP) base stations for providing smaller coverage areas, smaller user capacity or higher bandwidth compared to macro cells.

[0023] In some implementations, all or part of RAN node 114 or RAN node 116 may be implemented as one or more software entities running on a server computer as part of a virtual network, which may be referred to as CRAN and / or Virtual Baseband Unit Pool (vBBUP). In these implementations, CRAN or vBBUP may implement RAN function partitioning, such as PDCP partitioning, where the RRC and PDCP layers are operated by CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); MAC / PHY partitioning, where the RRC, PDCP, RLC, and MAC layers are operated by CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); or “lower PHY” partitioning, where the upper portion of the RRC, PDCP, RLC, MAC, and PHY layers is operated by CRAN / vBBUP, while the lower portion of the PHY layer is operated by individual RAN nodes. This virtualization framework allows idle processor cores of RAN node 114 or RAN node 116 to execute other virtualized applications. In some specific implementations, each RAN node can represent a connection via each F1 interface ( Figure 1(Not shown) Individual gNB-DUs connected to the gNB-CU. In these specific implementations, the gNB-DU may include one or more remote radio head units or RFEMs, and the gNB-CU may be operated by a server (not shown) located in (R)AN 108 or by a server pool in a manner similar to CRAN / vBBUP. Alternatively, one or more of RAN node 114 or RAN node 116 may be a next-generation eNB (ng-eNB), which is a RAN node that provides E-UTRA user plane and control plane protocol terminals to UE 122 and UE 120 and is connected to the SGC via the NG interface (discussed below). In vehicle-to-the-world (V2X) scenarios, one or more of RAN node 114 or RAN node 116 may be an RSU or act as an RSU.

[0024] The term "roadside unit" or "RSU" can refer to any traffic infrastructure entity used for V2X communication. An RSU can be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, wherein an RSU implemented in or by a UE can be referred to as a "UE-type RSU," an RSU implemented in or by an eNB can be referred to as an "eNB-type RSU," an RSU implemented in or by a gNB can be referred to as a "gNB-type RSU," and so on. In one example, an RSU is a computing device coupled to radio frequency circuitry located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. An RSU can operate on the 5.9 GHz Direct Near Range Communication (DSRC) band to provide extremely low-latency communication required for high-speed events, such as collision avoidance and traffic warnings. Alternatively or in addition to this, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications and other cellular communication services. Alternatively or in addition to this, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and / or provide connectivity to one or more cellular networks to provide uplink and downlink communications. Some or all of the computing device and the RSU's radio frequency circuitry may be packaged in a weather-resistant package suitable for outdoor installation and may include a network interface controller to provide wired connectivity (e.g., Ethernet) to traffic signal controllers and / or backhaul networks.

[0025] RAN node 114 and / or RAN node 116 may terminate the air interface protocol and may be the first point of contact for UE 122 and UE 120. In some implementations, RAN node 114 and / or RAN node 116 may perform various logical functions of (R)AN 108, including but not limited to the functions of the Radio Network Controller (RNC), such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

[0026] In the implementation, UE 122 and UE 120 may be configured to communicate with each other or with RAN node 114 and / or RAN node 116 on a multi-carrier communication channel using OFDM communication signals according to various communication technologies, such as, but not limited to, OFDMA communication technology (e.g., for downlink communication) or SC-FDMA communication technology (e.g., for uplink and ProSe or sidelink communication), but the scope of the implementation is not limited in this respect. The OFDM signal may include multiple orthogonal subcarriers.

[0027] In some implementations, the downlink resource grid can be used for downlink transmissions from RAN node 114 and / or RAN node 116 to UE 122 and UE 120, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, referred to as a resource grid or time-frequency resource grid, which represents the physical resources in the downlink within each time slot. This time-frequency plane representation is common practice for OFDM systems, making radio resource allocation intuitive. Each column and row of the resource grid corresponds to an OFDM symbol and an OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to a time slot in a radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid comprises multiple resource blocks that describe the mapping of certain physical channels to resource elements. Each resource block comprises a set of resource elements; in the frequency domain, this can represent the minimum amount of resources currently available for allocation. Such resource blocks are used to transmit several different physical downlink channels.

[0028] According to various implementations, UE 122 and UE 120, as well as RAN node 114 and / or RAN node 116, transmit data (e.g., transmit and receive data) through licensed media (also referred to as “licensed spectrum” and / or “licensed band”) and unlicensed shared media (also referred to as “unlicensed spectrum” and / or “unlicensed band”). Licensed spectrum may include channels operating in the frequency range of approximately 400 MHz to approximately 3.8 GHz, while unlicensed spectrum may include a 5 GHz band.

[0029] To operate in unlicensed spectrum, UE 122 and UE 120, along with RAN node 114 or RAN node 116, may use LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, UE 122 and UE 120, along with RAN node 114 or RAN node 116, may perform one or more known media sensing and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmission in the unlicensed spectrum. Media / carrier sensing operations may be performed according to a Listen-After-Speak (LBT) protocol.

[0030] LBT is a mechanism that equipment (e.g., UE 122 and UE 120, RAN node 114 or RAN node 116, etc.) uses to sense a medium (e.g., a channel or carrier frequency) and transmit when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence of other signals on the channel in order to determine whether the channel is occupied or idle. This LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy in the intended transmission band over a period of time and comparing the sensed RF energy with a predefined or configured threshold.

[0031] Typically, existing systems in the 5GHz band are WLANs based on IEEE 1002.11 technology. WLANs employ a contention-based channel access mechanism called CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 122, AP112, etc.) intends to transmit, the WLAN node can first perform CCA before transmitting. Additionally, in cases where more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. This backoff mechanism can be a counter randomly introduced within the CWS, which increases exponentially upon collision and resets to a minimum value upon successful transmission. The LBT mechanism designed for LAA is somewhat similar to WLAN's CSMA / CA. In some specific implementations, the LBT process for DL ​​or UL transmission bursts (including PDSCH or PUSCH transmissions) can have a variable-length LAA contention window between the X and Y ECCA time slots, where X and Y are the minimum and maximum values ​​of the LAA's CWS. In one example, the minimum CWS for LAA transmission can be 9 microseconds (μs); however, the size of the CWS and MCOT (e.g., transmission burst) can be based on government regulatory requirements.

[0032] The LAA mechanism is built upon the CA technology of LTE-Advanced systems. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4MHz, 3MHz, 5MHz, 10MHz, 15MHz, or 20MHz, and a maximum of five CCs can be aggregated, thus the maximum aggregated bandwidth is 100MHz. In FDD systems, the number of aggregated carriers can differ for DL ​​and UL, where the number of UL CCs is equal to or less than the number of DL component carriers. In some cases, individual CCs can have different bandwidths than the other CCs. In TDD systems, the number of CCs and the bandwidth of each CC are usually the same for DL ​​and UL.

[0033] The CA also includes individual serving cells to provide individual CCs. The coverage of serving cells can differ, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell, or PCell, provides PCCs for both UL and DL and handles activities related to RRC and NAS. Other serving cells are called SCells, and each SCell provides individual SCCs for both UL and DL. SCCs can be added and removed as needed, and changing the PCC may require UE 122 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells can operate in unlicensed spectrum (called "LAA SCells"), and LAA SCells are assisted by PCells operating in licensed spectrum. When a UE is configured to have more than one LAA SCell, the UE can receive UL grants on the configured LAA SCells, indicating different PUSCH start positions within the same subframe.

[0034] The PDSCH carries user data and higher-layer signaling to UE 122 and UE 120. Among other information, the PDCCH carries information about the transmission format and resource allocation related to the PDSCH channel. It can also inform UE 122 and UE 120 about the transmission format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 120 within the cell) can be performed at either RAN node 114 or RAN node 116 based on channel quality information fed back from either UE 122 or UE 120. Downlink resource allocation information can be transmitted on the PDCCH used (e.g., allocated to) each of UE 122 and UE 120.

[0035] PDCCH uses CCEs to transmit control information. Before being mapped to resource elements, the complex-valued symbols of the PDCCH can first be organized into quadruplets, which can then be arranged using a sub-block interleaver for rate matching. One or more of these CCEs can be used to transmit each PDCCH, where each CCE can correspond to nine sets, called REGs, each with four physical resource elements. Four Quadrature Phase Shift Keying (QPSK) symbols can be mapped to each REG. Depending on the DCI size and channel conditions, one or more CCEs can be used to transmit the PDCCH. Four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L = 1, 2, 4, or 8) can exist.

[0036] Some implementations may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some implementations may utilize EPDCCH, which uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similarly, each ECCE may correspond to a set of nine, each consisting of four physical resource elements, called EREG. In some cases, an ECCE may have a different number of EREGs.

[0037] RAN node 114 or RAN node 116 may be configured to communicate with each other via interface 130. In embodiments where system 100 is an LTE system (e.g., when CN 106 is an EPC), interface 130 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes connected to the EPC (e.g., two or more eNBs, etc.), and / or between two eNBs connected to the EPC. In some specific implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). X2-U may provide flow control mechanisms for user packets transmitted via the X2 interface and may be used to transmit information about the delivery of user data between eNBs. For example, X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful in-order delivery of PDCP PDUs from the SeNB to the UE 122 for user data; information about PDCP PDUs not delivered to the UE 122; information about the current minimum expected buffer size at the SeNB for transmitting user data to the UE; and so on. The X2-C provides LTE intra-eNB access mobility functions, including context transmission from the source eNB to the destination eNB, user plane transmission control, load management functions, and inter-cell interference coordination functions.

[0038] In implementations where system 100 is an SG or NR system (e.g., when CN 106 is an SGC), interface 130 may be an Xn interface. The Xn interface is defined between two or more RAN nodes connected to the SGC (e.g., two or more gNBs, etc.), between RAN nodes 114 (e.g., gNBs) connected to the SGC and eNBs, and / or between two eNBs connected to the 5GC (e.g., CN 106). In some specific implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. Xn-U provides non-guaranteed delivery of user plane PDUs and supports / provides data forwarding and flow control functions. Xn-C provides management and error handling functions for managing the functionality of the Xn-C interface; mobility support for UE 122 in connected modes (e.g., CM-CONNECTED), including functions for managing UE mobility in connected modes between one or more RAN nodes 114 or RAN nodes 116. This mobility support may include context transfer from the old (source) serving RAN node 114 to the new (destination) serving RAN node 116; and control of the user plane tunnel between the old (source) serving RAN node 114 and the new (destination) serving RAN node 116. The Xn-U protocol stack may include a transport network layer built on top of the Internet Protocol (IP) transport layer, and a GTP-U layer on top of the UDP and / or IP layers for carrying user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as the Xn Application Protocol (Xn-AP)) and a transport network layer built on top of SCTP. SCTP may be on top of the IP layer and provides guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver signaling PDUs. In other specific implementations, the Xn-U protocol stack and / or the Xn-C protocol stack may be the same as or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0039] (R)AN 108 is shown as being communicatively coupled to the core network—in this embodiment, communicatively coupled to CN 106. CN 106 may include one or more network elements 132 configured to provide various data and telecommunications services to customers / subscribers (e.g., users of UE 122 and UE 120) connected to CN 106 via (R)AN 108. Components of CN 106 may be implemented in a single physical node or in separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instance of CN 106 may be referred to as a network slice, and a logical instance of a portion of CN 106 may be referred to as a network subslice. NFV architectures and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (or alternatively, performed by proprietary hardware). In other words, an NFV system can be used to perform a virtual or reconfigurable concrete implementation of one or more EPC components / functions.

[0040] Generally, application server 118 can be a component that provides IP bearer resources for applications to use with the core network (e.g., UMTS PS domain, LTE PS data service, etc.). Application server 118 can also be configured to support one or more communication services for UE 122 and UE 120 via EPC (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.). Application server 118 can communicate with CN 106 via IP communication interface 136.

[0041] In this implementation, CN 106 may be an SGC, and (R)AN 116 may be connected to CN 106 via NG interface 134. In this implementation, NG interface 134 may be divided into two parts: an NG user plane (NG-U) interface 126, which carries traffic data between RAN node 114 or RAN node 116 and the UPF; and an S1 control plane (NG-C) interface 128, which is the signaling interface between RAN node 114 or RAN node 116 and the AMF.

[0042] In one implementation, CN 106 may be an SG CN, while in other implementations, CN 106 may be an EPC. If CN 106 is an EPC, (R)AN 116 may be connected to CN 106 via S1 interface 134. In one implementation, S1 interface 134 may be divided into two parts: an S1 user plane (S1-U) interface 126, which carries traffic data between RAN node 114 or RAN node 116 and the S-GW; and an S1-MME interface 128, which is the signaling interface between RAN node 114 or RAN node 116 and the MME.

[0043] Inter-UE Coordination (IUC) (i.e., the SL enhancement adopted for 3GPP standard version 17 (Rel-17), which aims to address the hidden terminal problem (see later)) Figure 3 In the discussion, UE A can assist other UEs (UE B) during their resource selection process. This is in accordance with the RAN1 protocol, and as... Figure 2 As shown, the IUC supports three types of "resource sets". However, it should be noted that the following different types can be used in combination with each other.

[0044] Type A: For example, UE A sending transmissions to UE B based on its sensing results is a preferred resource set. Under Type A, the assisting UE is restricted to the resources used by the assisting UE (i.e., a whitelist). In other words, UE A sending transmissions to UE B based on its sensing results is a preferred resource set.

[0045] Type B: UE A sends a set of resources (in the future) to UE B that are not preferred for transmissions to UE B, for example, based on its sensing results and / or anticipated / potential resource conflicts. Under Type B (i.e., blacklist), UE A sends a set of resources (in the future) to UE B that are not preferred for transmissions to UE B, for example, based on its sensing results and / or anticipated / potential resource conflicts.

[0046] Type C: UE A sends the set of resources (history) in which resource conflicts were detected to UE B. Under Type C (i.e., conflict list), UE A sends the set of resources (history) in which resource conflicts were detected to UE B.

[0047] Figure 3An example of a V2X communication system is shown, and a diagram is provided to explain resource allocation issues in previous V2X attempts. Initially, it should be understood that direct communication between vehicles and other devices (V2V, V2I) uses the so-called PC 5 interface. PC 5 refers to the reference point where a UE (i.e., a mobile handheld device) communicates directly with another UE via a direct channel (communication with a base station is not used for PC 5 links). At the system architecture level, Proximity Service (ProSe) is a feature of the architecture specifying direct communication between UEs. In the 3GPP RAN specification, "side link" refers to the term direct communication via PC5. The PC5 interface was initially defined to address the mission-critical communication needs of the public safety community (Public Safety LTE or PS-LTE) in previous versions of the 3GPP standard.

[0048] Figure 3 This demonstrates that any SL UE supporting SL data transmission / reception can detect half-duplex conflicts during previous inter-UE coordination attempts. A conflict occurs when a UE is unable to sense a subscription announced by another UE in the time slot of the sensing window that the UE is transmitting in.

[0049] Figure 3 Hidden terminal conflict is also illustrated. UE A is within the transmission range of both UE B and UE C. UE A can then receive transmissions from UE B and UE C and detect the subchannel resource reservations of UE B and UE C. However, UE B and UE C are outside each other's range, thus experiencing a hidden terminal problem. Therefore, UE B and UE C may inadvertently select the same resources for their transmissions to UE A. If the interfering transmission is directed to UE A, UE A can detect the resource conflict using a so-called SL data reception procedure. If the interfering transmission is not directed to UE A, UE A will not record this transmission during data reception and will detect the conflict using sensing.

[0050] To help UE A avoid those conflicts, UE A shares "decoded" or "predicted" resource information with UE B. Sensing is a tool used to detect all resource conflicts, but not all UEs support sensing.

[0051] Version 16 (Rel-16) of the 3GPP standard (also known as 3GPP R16) defines two modes (Mode 1 and Mode 2) for selecting sub-channels in NRV2X SL communication using the NR V2X PC 5 interface. In Mode 1, the gNB or eNB uses the NR (or LTE) Uu interface to allocate and manage SL radio resources for V2V communication. Therefore, the UE operates in Mode 1 within network coverage. In Mode 2, when in NR V2X, the UE can autonomously select its SL resources (one or more sub-channels) from the resource pool. In this case, the UE can operate even without network coverage.

[0052] Figure 4 This is a table illustrating an overview of how different transmission modes affect the IUC. As shown, regardless of the TX mode of UE A, at least type C can be supported. Type C can be supported by any SL RX UE. However, type A / B can depend on mode 1 / 2. This disclosure addresses the so-called cross-mode IUC, i.e., mismatched modes on UE A / B, such as... Figure 4 The middle two rows of the table are shown. Similarly, the addresses are in the last row, where both UEs are mode 1 UEs.

[0053] Some cross-mode IUC scenarios are supported by the UE capability design. For example, the first option is where the IUC capability depends on the "sl-transmissionmode2" capability (Rel-16 V2X capability). Therefore, a Mode 2 UE is allowed as UE A (if UE B is Mode 1, then cross-mode IUC is allowed). If a Mode 2 UE is allowed as either UE A or UE B, then cross-mode IUC is not permitted. The second option is to introduce an IUC that enables a Mode 1 UE as a new capability for UE A, UE B, or both. Therefore, cross-mode IUC is allowed in the second option.

[0054] Figure 5 This illustrates a routine 500 performed by a first User Equipment (UE) for a 5G network, involving SL capability exchange with a second UE via a PC 5 link for configuring Inter-UE Coordination (IUC). In block 502, routine 500 generates an RRC message for the second UE, which includes information to identify the supported IUC type of the first UE or to provide an indication of which resource allocation mode the IUC supports. In block 504, routine 500 signals the RRC message to the second UE via a first SL unicast transmission. In block 506, routine 500 receives the SL capabilities for configuring the IUC from the second UE via a second SL unicast transmission.

[0055] In some implementations, SL unicast UEs exchange SL capabilities via PC5-RRC messages using the following indications: (1) whether they support (basic, i.e., non-cross-mode) IUC; (2) identifying the type of IUC supported by the peer UE (type A / B / C, type B / C only, or others); and (3) whether they support cross-mode IUC. For example, the indications may include the capability parameters “sl-transmissionmode2” or “sl-transmissionmode1” directly in the signaling (similar to those capability parameters defined for Uu in NR Rel-16, see, for example, Rel-16 in 3GPP TS 38.331 or 38.306?), or they may use more explicit signaling to support cross-mode IUC. If cross-mode IUC is supported, the capability exchange facilitates the determination of the SL communication direction for the unicast link against which IUC can be performed.

[0056] To facilitate IUC between Mode 1 UEs, some implementations include gNB interaction for Mode 1 UEs (RRC_CONNECTED). The interaction between UE A and UE B is as follows.

[0057] In some implementations, Mode 1 UE A operation requires three steps. First, UE A follows its gNB configuration regarding whether it allows cross-mode IUC (or a subset of types for which cross-mode IUC is allowed). This can be done via a dedicated RRC exchange when UE A confirms to its serving gNB. Second, UE A maintains a record of all potential resource conflicts for each resource allocated by the gNB for Mode 1 transmissions or retransmissions, and combines this information with any resource conflicts detected as a receiving UE. Third, when requested by UE B, UE A shares the resource set in type B / C or both.

[0058] In some implementations, Mode 1 UE B operation requires four steps. First, UE B follows the gNB configuration regarding whether it allows cross-mode IUC (or a subset of cross-mode IUC types). Second, UE B sends an IUC request signaling to UE A. Third, UE B obtains IUC information from UE A. Fourth, UE B includes the IUC information in its Uu signaling to the gNB to assist with the resources allocated by the gNB (dynamic authorization or configured authorization).

[0059] The IUC between Mode 1 UEs introduces additional problems in intra-gNB scenarios, and these problems are Figure 6 The theme. For example... Figure 6 As shown, the half-duplex problem and hidden terminal problem occur not only in Mode 2. The Rel-17 Work Item Description (WID) proposes NR Sidelink Enhancement (SLE) to address these problems with Mode 1 Resource Allocation (RA) enhancement.

[0060] Figure 6 The left side illustrates a half-duplex problem. UE A and UE B will transmit to each other via SL unicast, but the gNB is unaware that the resources allocated to those two UEs are for a pair of SL unicast addresses. Therefore, it may allocate resource candidates to UE A and UE B simultaneously, but through different sub-channels (RBs).

[0061] Figure 6 The right side illustrates the hidden terminal issue. UE C and UE B both have license allocations. The gNB is unaware of the distance from UE A to UE C or UE B. When they broadcast on the same sub-channel, there is a collision that UE A will detect.

[0062] Existence is used to solve Figure 6 The text discusses at least three options for the intra-gNB problem, specifically addressing the IUC between Mode 1 UEs.

[0063] The first option is to always allocate resources in non-overlapping time slots. However, this option may waste resources because it does not utilize all sub-channels and hinders resource reuse.

[0064] The second option is for the UE and gNB to directly detect resource conflicts. The UE includes both the source (src) and destination (dest) addresses in its resource allocation request signaling (e.g., SidelinkUEInformation). The gNB matches the L2 addresses and avoids resource allocation conflicts. However, this may not be optimal for the UE, as it lacks a specific way to check if a peer UE is under the same gNB.

[0065] The third option is to use the IUC mechanism, which is... Figure 7 and Figure 8 The theme. Figure 7 The message transmission sequence requires six steps. First, UE B is allocated resources by the gNB. Second, UE B uses the resources for transmission. Third, if the Side Link Control Information (SCI) indicates that the transmission resource will be used for (re)transmission, but the UE cannot decode at the indicated resource, UE A can detect a conflict. Fourth, UE A sends IUC information to inform UE B that the resource is not preferred, or a resource conflict has been detected. Fifth, UE B informs the serving gNB that the resource is unavailable or needs to be avoided in RRC or L2 signaling. Sixth, UE B receives a New Mode 1 authorization, which takes into account the IUC information and avoids reported bad resources.

[0066] In some implementations, the IUC information is a new PC 5-RRC message, or it may be an existing PC 5-RRC message. When specified, it will appear in TS 38.331. The message includes the Type A / Type B / Type C resource set. The message may also include the validity period of the evaluation results.

[0067] Figure 8 This illustrates a routine 800 executed by a first user equipment (UE) for a 5G network, configuring an IUC with a second UE for network-controlled SL resource allocation. In block 802, routine 800 needs to transmit information to the second UE via the first SL resource in response to receiving a first authorized allocation to the first SL resource from the gNB. In block 804, routine 800 receives IUC information from the second UE indicating that the first SL resource is not preferred or a conflict has been detected. In block 806, routine 800 signals to the gNB that the first SL resource is invalid or should be avoided. In block 808, routine 800 receives a second authorized allocation from the gNB having a second SL resource different from the first SL resource.

[0068] The IUC between Mode 1 UEs introduces additional problems in inter-gNB scenarios, which is Figure 9 The theme. For example... Figure 9 As shown, a half-duplex problem occurs because UE A and UE B will transmit to each other via SL unicast, but they reside on different gNBs. Since one gNB is unaware of the resources allocated by the other gNB, resource allocation can cause UE A and UE B to transmit during overlapping times, resulting in a half-duplex conflict. Furthermore, a hidden node problem may occur because the gNBs of UE A and UE B may allocate overlapping transmission resources for UE A and UE B, thus affecting at least one of the victim SL destinations (UE C). To resolve these issues, as... Figure 7 A similar IUC solution is shown in the example for intra-gNB scenarios. Figure 6 It can also be used for Figure 9 The diagram illustrates an inter-gNB scenario. Two gNBs have an Xn interface with each other. However, for inter-UE coordination, no gNB coordination is required. The scheme used within a gNB can also be used for inter-gNB. The UE only needs to send assistance information to its own gNB, and its own gNB will assign new authorizations. The two gNBs do not need to coordinate authorization allocation.

[0069] Some implementation schemes include additional signaling designs for inter-UE coordination. For a Mode 1 UE, this additional signaling design may employ "IUC Assistance Information" signaling voluntarily sent by UE A to UE B. The IUC Assistance Information is related to... Figure 7Step 4 is relevant. For Mode 1 UEs, this additional signaling design can detect faults and compose voluntary IUC information (the same as the IUC information) for UE B. This is because for Mode 1 UEs (i.e., UE A, ...), Figure 7 No sensing is performed, and no configuration is required regarding how (on-demand) sensing will be performed. However, several other reasons can still trigger an IUC request for an IUC report from UE A. For voluntary IUC assistance information, it may contain either a Type B or Type C resource set.

[0070] For a Mode 1 UE, the following exemplary triggering conditions can still be configured by the gNB or by the peer UE: report only when the number of bad resources reaches a certain threshold; report only when resource conflicts cause data reception to fail completely (e.g., cannot be salvaged by HARQ or RLC confirmation mode (AM)); or report upon request by the peer UE.

[0071] Figure 10 This is a block diagram illustrating a component 1000, according to some exemplary embodiments, capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of executing any one or more of the methods discussed herein. Specifically, Figure 10 A schematic diagram of hardware resource 1002 is shown, which includes one or more processors 1006 (or processor cores), one or more memory / storage devices 1014, and one or more communication resources 1024, each of which is communicatively coupled via bus 1016. For an implementation utilizing node virtualization (e.g., NFV), an executable hypervisor 1022 is provided to provide an execution environment for one or more network slices / subslices to utilize hardware resource 1002.

[0072] Processor 1006 (e.g., 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 digital signal processor (DSP) (such as a baseband processor), an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof) may include, for example, processor 1008 and processor 1010.

[0073] The memory / storage device 1014 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1014 may include, but is not limited to, any type of volatile or non-volatile memory, such as dynamic random access memory (DRAM), static random access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state storage devices, etc.

[0074] Communication resource 1024 may include interconnect or network interface components or other suitable devices for communicating with one or more peripheral devices 1004 or one or more databases 1020 via network 1018. For example, communication resource 1024 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB), cellular communication components, NFC components, etc. Components (e.g.) (low power consumption) Components and other communication components.

[0075] Instruction 1012 may include software, programs, applications, applets, or other executable code for causing at least one processor in processor 1006 to perform any or more of the methods discussed herein. Instruction 1012 may reside wholly or partially within at least one of processors 1006 (e.g., within the processor's cache memory), memory / storage device 1014, or any suitable combination thereof. Furthermore, any portion of instruction 1012 may be transferred to hardware resource 1002 from any combination of peripheral device 1004 or database 1020. Therefore, the memory of processor 1006, memory / storage device 1014, peripheral device 1004, and database 1020 are examples of computer-readable and machine-readable media.

[0076] For one or more embodiments, at least one of the components shown in one or more of the foregoing figures may be configured to perform one or more operations, techniques, processes, and / or methods described in the Embodiments section below. For example, the baseband circuitry described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples below. As another example, circuitry associated with the UE, base station, network element, etc., described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the examples shown in the Examples section below.

[0077] The following examples relate to other implementation schemes.

[0078] Example 1 is a method performed by a first user equipment (UE) for a 5G network to exchange sidelink capabilities with a second UE via a PC5 link for configuring inter-UE coordination (IUC). The method includes: generating a radio resource control (RRC) message for the second UE, the RRC message including information for identifying the IUC type supported by the first UE or providing an indication of which resource allocation mode the IUC supports; signaling the RRC message to the second UE via a first SL unicast transmission; and receiving the SL capabilities of the second UE for configuring the IUC from the second UE via a second SL unicast transmission.

[0079] Example 2 is the method described in Example 1, wherein the information in the RRC message indicates whether IUC is supported with a UE having the same resource allocation mode as the first UE.

[0080] Example 3 is the method described in Example 1, wherein the IUC types supported by the first UE include all types A, B and C.

[0081] Example 4 is the method described in Example 1, wherein the IUC types supported by the first UE include only type B and type C.

[0082] Example 5 is the method described in Example 1, wherein the indication is the sl-TransmissionMode2 capability parameter in the information of the RRC message.

[0083] Example 6 is the method described in Example 1, wherein the indication is the sl-TransmissionMode1 capability parameter in the information of the RRC message.

[0084] Example 7 is the method described in Example 1, wherein the indication specifies one or more desired resource allocation modes for the second UE.

[0085] Example 8 is a method for configuring inter-UE coordination (IUC) with a second UE performed by a first user equipment (UE) for a 5G network, the first UE configuring a sidelink (SL) resource allocation controlled by the network, the method comprising: transmitting to the second UE via the first SL resource in response to receiving a first grant allocation to the first SL resource from a gNB; receiving from the second UE IUC information indicating that the first SL resource is not preferred or a conflict is detected; signaling to the gNB that the first SL resource is invalid or should be avoided; and receiving from the gNB a second grant allocation having a second SL different from the first SL resource.

[0086] Example 9 is the method described in Example 8, wherein the signaling includes a Radio Resource Control (RRC) message or L2 signaling.

[0087] Example 10 is the method described in Example 9, wherein the RRC message includes SidelinkUEInformation or UEAssistanceInformation.

[0088] Example 11 is the method described in Example 8, wherein the IUC information from the second UE includes a preferred resource set, and the signaling to the gNB provides the preferred resource set.

[0089] Example 12 is the method described in Example 8, wherein both the first UE and the second UE are controlled by the gNB configured to act as an intra-gNB.

[0090] Example 13 is the method described in Example 8, wherein the gNB is a first gNB, and the second UE is controlled by a second gNB that is different from the first gNB.

[0091] Example 14 is the method described in Example 8, and further includes: sending a request to the second UE to solicit IUC information indicating a resource set of type A, type B, or type C.

[0092] Example 15 is the method described in Example 8, further comprising: receiving voluntary IUC assistance information from the second UE indicating a type B or type C resource set.

[0093] Example 16 is a non-transitory computer-readable storage medium comprising instructions for side-link (SL) capability exchange between a first user equipment (UE) and a second UE via a PC 5 link for configuring inter-UE coordination (IUC). When executed by the first UE, these instructions cause the first UE to: generate a radio resource control (RRC) message for the second UE, the RRC message including information for identifying the supported IUC type of the first UE or providing an indication of which resource allocation mode the IUC supports; signal the RRC message to the second UE via a first SL unicast transmission; and receive from the second UE via a second SL unicast transmission the SL capability configured by the second UE for the IUC.

[0094] Example 17 is the computer-readable storage medium described in Example 16, wherein the information in the RRC message indicates whether IUC is supported with a UE having the same resource allocation mode as the first UE.

[0095] Example 18 is the computer-readable storage medium described in Example 16, wherein the IUC types supported by the first UE include all types A, B and C.

[0096] Example 19 is the computer-readable storage medium described in Example 16, wherein the IUC types supported by the first UE include only type B and type C.

[0097] Example 20 is the computer-readable storage medium described in Example 16, wherein the indication is the sl-TransmissionMode2 capability parameter in the information of the RRC message.

[0098] Example 21 is the computer-readable storage medium described in Example 16, wherein the indication is the sl-TransmissionMode1 capability parameter in the information of the RRC message.

[0099] Example 22 is the computer-readable storage medium described in Example 16, wherein the indication specifies one or more desired resource allocation modes for the second UE.

[0100] Example 23 is a non-transitory computer-readable storage medium including instructions for configuring inter-UE coordination (IUC) between a first user equipment (UE) and a second UE, the first UE configuring a network-controlled sidelink (SL) resource allocation. When executed by the first UE, these instructions cause the first UE to: transmit via the first SL resource to the second UE in response to receiving a first authorized allocation to the first SL resource from a gNB; receive from the second UE IUC information indicating that the first SL resource is not preferred or a conflict has been detected; signal to the gNB that the first SL resource is invalid or should be avoided; and receive from the gNB a second authorized allocation having a second SL different from the first SL resource.

[0101] Example 24 is the computer-readable storage medium described in Example 23, wherein the signal to the gNB includes a Radio Resource Control (RRC) message or L2 signaling.

[0102] Example 25 is the computer-readable storage medium described in Example 24, wherein the RRC message includes SidelinkUEInformation or UEAssistanceInformation.

[0103] Example 26 is the computer-readable storage medium described in Example 23, wherein the IUC information from the second UE includes a preferred resource set, and the signaling to the gNB provides the preferred resource set.

[0104] Example 27 is the computer-readable storage medium described in Example 23, wherein both the first UE and the second UE are controlled by the gNB configured to act as an intra-gNB.

[0105] Example 28 is the computer-readable storage medium described in Example 23, wherein the gNB is a first gNB, and the second UE is controlled by a second gNB that is different from the first gNB.

[0106] Example 29 is the computer-readable storage medium described in Example 23, wherein the instructions further configure the first UE to send a request to the second UE to solicit IUC information indicating a type A, type B, or type C resource set.

[0107] Example 30 is the computer-readable storage medium described in Example 23, wherein the instructions further configure the first UE to receive voluntary IUC assistance information indicating a type B or type C resource set from the second UE.

[0108] Example 31 may include an apparatus comprising means for performing one or more elements of the method or any other method or process described herein, as described in any of the above embodiments or in connection with them.

[0109] Example 32 may include one or more non-transitory computer-readable media, the one or more non-transitory computer-readable media including instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of any of the methods or processes described in or related to the above embodiments or any other methods or processes described herein.

[0110] Example 33 may include an apparatus comprising one or more elements of a logic component, module, or circuit for performing any of the methods described in or related to any of the above embodiments, or any other methods or processes described herein.

[0111] Example 34 may include any of the methods, techniques, or processes described or related to any of the above examples, or any part or component thereof.

[0112] Example 35 may include an apparatus comprising one or more processors and one or more computer-readable media, the one or more computer-readable media including instructions that, when executed by the one or more processors, cause the one or more processors to perform any of the methods, techniques or processes described in or related to the above embodiments, or a portion thereof.

[0113] Example 36 may include any of the signals or parts or components described or associated with any of the above examples.

[0114] Example 37 may include any datagram, packet, frame, segment, protocol data unit (PDU) or message, or any part or component thereof, as described in any of the above examples or in connection with them, or otherwise described in this disclosure.

[0115] Embodiment 38 may include a data-encoded signal or part or component thereof described or associated with any of the above embodiments, or otherwise described in this disclosure.

[0116] Embodiment 39 may include any of the above embodiments or related signals or portions thereof encoded as datagrams, packets, frames, segments, PDUs or messages, or otherwise described in this disclosure.

[0117] Example 40 may include an electromagnetic signal carrying computer-readable instructions, wherein one or more processors execute the computer-readable instructions to cause the one or more processors to perform any of the methods, techniques or processes, or portions thereof, described in or related to any of the above embodiments.

[0118] Example 41 may include a computer program comprising instructions, wherein the program is executed by a processing element to cause the processing element to perform any of the methods, techniques, or processes described in or related to the above embodiments, or a portion thereof.

[0119] Example 42 may include signals in a wireless network as shown and described herein.

[0120] Example 43 may include methods for communicating in a wireless network as shown and described herein.

[0121] Example 44 may include a system for providing wireless communication as shown and described herein.

[0122] Example 45 may include a device for providing wireless communication as shown and described herein.

[0123] Unless otherwise expressly stated, any of the above embodiments may be combined with any other embodiment (or combination of embodiments). The foregoing description of one or more specific embodiments provides illustration and description, but is not intended to be exhaustive or to limit the scope of the embodiments to the precise forms disclosed. In view of the teachings above, modifications and variations are possible, or modifications and variations may be obtained from the practice of various embodiments.

[0124] Implementations and specific embodiments of the systems and methods described herein may include various operations embodied in machine-executable instructions to be executed by a computer system. The computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components, including specific logical components for performing the operations, or may include a combination of hardware, software, and / or firmware.

[0125] It should be recognized that the systems described herein include descriptions of specific implementations. These implementations may be combined into a single system, partially integrated into other systems, divided into multiple systems, or otherwise partitioned or combined. Furthermore, it is conceivable to use parameters, attributes, aspects, etc., of one implementation in another implementation. For clarity, these parameters, attributes, aspects, etc., are described only in one or more implementations, and it should be recognized that unless specifically stated herein, these parameters, attributes, aspects, etc., may be combined with or substituted for parameters, attributes, aspects, etc., of another implementation.

[0126] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.

[0127] Although the foregoing has been described in considerable detail for clarity, it will be apparent that certain changes and modifications can be made without departing from the principles of the invention. It should be noted that many alternative ways exist to implement both the processes and apparatus described herein. Therefore, embodiments of the invention should be considered illustrative rather than restrictive, and this specification is not limited to the details given herein, but can be modified within the scope of the appended claims and their equivalents.

Claims

1. A method for configuring inter-UE coordinated IUC by exchanging sidelink SL capabilities with a second UE via a PC 5 link, performed by a first user equipment (UE) for a 5G network, the method comprising: Generate a Radio Resource Control (RRC) message for the second UE, the RRC message including: Information used to identify the IUC types supported by the first UE; An indication of which resource allocation mode the IUC supports, wherein the indication specifies whether the first UE supports cross-mode IUC; The RRC message is sent to the second UE via a first SL unicast transmission. Receive the SL capabilities of the second UE from the second UE via a second SL unicast transmission to configure the IUC; and The direction of SL communication for unicast links capable of performing cross-mode IUC is determined based on the configured IUC.

2. The method according to claim 1, wherein the information in the RRC message indicates whether IUC is supported with a UE having the same resource allocation mode as the first UE.

3. The method according to claim 1, wherein the supported IUC types of the first UE include all types A, B, and C, wherein: Support for IUC Type A includes support for preferred resource sets for transport; Support for IUC type B includes support for the less preferred resource set for transport; and Support for IUC type C includes support for resource sets in which resource conflicts are detected.

4. The method of claim 1, wherein the supported IUC types of the first UE include only type B and type C, wherein support for IUC type B includes support for a non-preferred resource set for transmission, and wherein support for IUC type C includes support for a resource set in which resource conflicts are detected.

5. The method of claim 1, wherein the indication is a parameter in the information of the RRC message, the parameter describing the sl-TransmissionMode2 capability as defined in the 3GPP standard.

6. The method of claim 1, wherein the indication is a parameter in the information of the RRC message, the parameter describing the sl-TransmissionMode1 capability as defined in the 3GPP standard.

7. The method of claim 1, wherein the indication specifies one or more desired resource allocation modes for the second UE.

8. A non-transitory computer-readable storage medium, the computer-readable storage medium comprising instructions for performing sidelink SL capability exchange between a first user equipment (UE) and a second UE via a PC 5 link for configuring inter-UE coordinated IUC, the instructions causing the first UE, when executed by the first UE, to: Generate a Radio Resource Control (RRC) message for the second UE, the RRC message including: Information used to identify the IUC types supported by the first UE; An indication of which resource allocation mode the IUC supports, wherein the indication specifies whether the first UE supports cross-mode IUC; The RRC message is sent to the second UE via a first SL unicast transmission. Receive the SL capabilities of the second UE from the second UE via a second SL unicast transmission to configure the IUC; as well as The direction of SL communication for unicast links capable of performing cross-mode IUC is determined based on the configured IUC.

9. The computer-readable storage medium of claim 8, wherein the information in the RRC message indicates whether IUC is supported with a UE having the same resource allocation mode as the first UE.

10. The computer-readable storage medium of claim 8, wherein the supported IUC types of the first UE include all types A, B, and C, wherein: Support for IUC Type A includes support for preferred resource sets for transport; Support for IUC type B includes support for the less preferred resource set for transport; and Support for IUC type C includes support for resource sets in which resource conflicts are detected.

11. The computer-readable storage medium of claim 8, wherein the supported IUC types of the first UE include only type B and type C, wherein support for IUC type B includes support for a less preferred set of resources for transmission, and wherein support for IUC type C includes support for a set of resources in which resource conflicts are detected.

12. The computer-readable storage medium of claim 8, wherein the indication is a parameter in the information of the RRC message, the parameter describing the sl-TransmissionMode2 capability as defined in the 3GPP standard.

13. The computer-readable storage medium of claim 8, wherein the indication is a parameter in the information of the RRC message, the parameter describing the sl-TransmissionMode1 capability as defined in the 3GPP standard.

14. The computer-readable storage medium of claim 8, wherein the indication specifies one or more desired resource allocation modes for the second UE.

Images