Method and medium for on-demand sensing inter-UE coordination

Abstract

The present disclosure relates to inter-UE coordination for on-demand sensing. Implementations of request and response signaling between first and second user equipment (UE) via a PC5 link for configuring inter-UE coordination are disclosed. In some implementations, the request signaling requires a first UE to identify a transmission resource pool of the first UE that the second UE is to sense or evaluate; instruct the second UE to report information indicating a certain amount of resources; and instruct the second UE to evaluate the resources to be reported. In other implementations, the response signaling requires the first UE to receive a request signal for inter-UE coordination from the second UE; indicate a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list; and provide a validity time for the indicated resources.

Description

Technical Field

[0001] The present application generally relates to wireless communication systems, including inter-UE coordination. Background Art

[0002] Wireless mobile communication technology uses various standards and protocols to transmit data between base stations and wireless mobile devices. Wireless communication system standards and protocols may include the 3rd Generation Partnership Project (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, which is generally referred to as Worldwide Interoperability for Microwave Access (WiMAX) by industry organizations; and the IEEE 802.11 standard for wireless local area networks (WLANs), which is generally referred to as Wi-Fi by industry organizations. In the 3GPP radio access network (RAN) in an LTE system, a base station may include a RAN node such as an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly referred to as an evolved Node B, an enhanced Node B, an eNodeB, or an eNB) and / or a radio network controller (RNC) in the E-UTRAN, which communicates with a wireless communication device referred to as a user equipment (UE). In the fifth generation (5G) wireless RAN, the RAN nodes may include 5G nodes, NR nodes (also called next generation Node B or g NodeB (gNB)).

[0003] The RAN uses radio access technologies (RATs) to communicate between RAN nodes and UEs. The RAN may include a global system for mobile communications (GSM), an enhanced data rate for GSM evolution (EDGE) RAN (GERAN), a universal terrestrial radio access network (UTRAN), and / or an E-UTRAN, which provides access to communication services through a core network. Each RAN in the RAN operates according to a specific 3GPP RAT. For example, GERAN implements GSM and / or EDGE RAT, UTRAN implements Universal Mobile Telecommunications System (UMTS) RAT or other 3GPP RAT, E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In some deployments, E-UTRAN may also implement 5G RAT.

[0004] The frequency bands for 5G NR can be divided into two different frequency ranges. Frequency range 1 (FR1) may include frequency bands operating at frequencies below 6 GHz, some of which may be used by previous standards and may potentially be expanded to cover new spectrum products from 410 MHz to 7125 MHz. Frequency range 2 (FR2) may include frequency bands from 24.25 GHz to 52.6 GHz. The frequency bands in the millimeter wave (mmWave) range of FR2 may have a smaller range but potentially higher available bandwidth than the frequency bands in FR1. The skilled person will recognize that these frequency ranges, which are provided by way of example, may vary from time to time or region to region. BRIEF DESCRIPTION OF THE DRAWINGS

[0005] To easily identify the discussion of any particular element or act, the most significant digit(s) in a reference number refers to the drawing number that first introduces the element.

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

[0007] Figure 2 is a block diagram of a vehicle-to-vehicle communication system.

[0008] Figure 3 is an annotated timing diagram showing an example of sensing for inter-UE coordination.

[0009] Figure 4 is an annotated message diagram showing an example of request and response signaling for on-demand sensing in conjunction with inter-UE coordination.

[0010] Figure 5 is a set of annotated message diagrams for three different subscription models.

[0011] Figure 6 is a pair of annotated sequence diagrams for different subscription mechanisms.

[0012] Figure 7 is a set of annotated timing diagrams for different single-shot triggering configurations.

[0013] Figure 8 is a flow chart of a process for configuring request signaling with a second UE via a PC5 link for inter-UE coordination with on-demand sensing.

[0014] Fig. 9 is a flow chart of a process for configuring response signaling with a second UE via a PC5 link for inter-UE coordination with on-demand sensing.

[0015] Fig.10 is a block diagram according to one embodiment. DETAILED DESCRIPTION

[0016] Figure 1An exemplary architecture of a system 100 of a network according to various embodiments is shown. The following description is provided for an example system 100 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard, and the embodiments may 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., WMAN, WiMAX, etc.), and the like.

[0017] like Figure 1 As shown, the system 100 includes a UE 122 and a UE 120. In this example, the UE 122 and the UE 120 are illustrated as smart phones (e.g., handheld touch screen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as consumer electronic devices, mobile phones, smart phones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handheld devices, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, instrument clusters (ICs), heads-up display (HUD) devices, on-board diagnostic (OBD) devices, dashboard mobile equipment (DME), mobile data terminals (MDTs), electronic engine management systems (EEMS), electronic / engine control units (ECUs), electronic / engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), connected or "smart" appliances, MTC devices, M2M, IoT devices, etc.

[0018] In some embodiments, UE 122 and / or UE 120 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via PLMN, ProSe or D2D communications, sensor networks, or IoT networks. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-lived connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0019] UE 122 and UE 120 may be configured to be connected, e.g., communicatively coupled, to an access node or radio access node (shown as (R)AN 108). In an embodiment, (R)AN 108 may be an NG RAN or SG RAN, an E-UTRAN, or a traditional RAN, such as a UTRAN or GERAN. As used herein, the term "NG RAN" or the like may refer to an (R)AN 108 operating in an NR or SG system, and the term "E-UTRAN" or the like may refer to an (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 connection (or channel) comprising a physical communication interface or layer (discussed in further detail below).

[0020] In this example, connection 104 and connection 102 are air interfaces for enabling communication coupling, and may conform to a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, UE 122 and UE 120 may exchange communication data directly via a ProSe interface 110. ProSe interface 110 may alternatively be referred to as a 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 illustrated as being configured to access AP 112 (also referred to as a "WLAN node," "WLAN," "WLAN terminal," "WT," etc.) via connection 124. Connection 124 may include a local wireless connection, such as a connection compliant with any IEEE 1002.11 protocol, where AP 112 would include Wireless Fidelity. router. In this example, AP 112 may be connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 120, (R) AN 108, 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 radio resources of LTE and WLAN. LWIP operation may involve UE 120 using WLAN radio resources (e.g., connection 124) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent through connection 124. IPsec tunneling may include encapsulating the entire original IP packet and adding a new packet header, thereby protecting 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 enable connection 104 and connection 102. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, 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 nodes," and the like may refer to RAN nodes (e.g., gNBs) operating in NR or SG systems, while the terms "E-UTRAN nodes," and the like may refer to RAN nodes (e.g., eNBs) operating in LTE or 4G systems 100. According to various embodiments, the RAN node 114 or the RAN node 116 may be implemented as one or more of a dedicated physical device such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0023] In some embodiments, all or part of the 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 that may be referred to as a CRAN and / or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement RAN functional splits, such as PDCP splits, where the RRC and PDCP layers are operated by the CRAN / vBBUP, while other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); MAC / PHY splits, where the RRC, PDCP, RLC, and MAC layers are operated by the CRAN / vBBUP, and the PHY layer is operated by individual RAN nodes (e.g., RAN node 114 or RAN node 116); or "lower PHY" splits, where the RRC, PDCP, RLC, MAC layers, and upper portions of the PHY layers are operated by the CRAN / vBBUP, while the lower portions of the PHY layers are operated by individual RAN nodes. This virtualization framework allows idle processor cores of the RAN node 114 or RAN node 116 to execute other virtualized applications. In some specific implementations, each RAN node may represent a node via each F1 interface ( Figure 1In some implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CUs may be operated by a server (not shown) located in the (R)AN 108 or by a pool of servers in a manner similar to the CRAN / vBBUP. Additionally or alternatively, one or more of the RAN node 114 or the 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 terminations to the UE 122 and the UE 120 and is connected to the SGC via an NG interface (discussed below). In a vehicle-to-everything (V2X) scenario, the RAN node 114 or one or more of the RAN nodes 116 may be an RSU or act as an RSU.

[0024] The term "roadside unit" or "RSU" may refer to any traffic infrastructure entity used for V2X communications. The RSU may 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 may be referred to as a "UE-type RSU", an RSU implemented in or by an eNB may be referred to as an "eNB-type RSU", an RSU implemented in 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 coupled to a radio frequency circuit located on the roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuits for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling ongoing vehicle and pedestrian traffic. The RSU may operate on the 5.9 GHz direct short range communication (DSRC) band to provide extremely low latency communications required for high-speed events, such as collision avoidance, traffic warnings, and the like. Additionally or alternatively, the RSU may operate on a cellular V2X band to provide the aforementioned low-latency communications as well as other cellular communications services. Additionally or alternatively, 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 RF circuitry may be packaged in a weather-resistant enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and / or backhaul network.

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

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

[0027] In some embodiments, a downlink resource grid may be used for downlink transmissions from RAN node 114 and / or RAN node 116 to UE 122 and UE 120, while uplink transmissions may utilize similar techniques. The grid may be a time-frequency grid, referred to as a resource grid or a time-frequency resource grid, which is a physical resource in the downlink in each time slot. For OFDM systems, such a time-frequency plane representation is common practice, which makes wireless resource allocation intuitive. Each column and each 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 includes a plurality of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block includes a set of resource elements; in the frequency domain, this may represent the minimum amount of resources that can currently be allocated. Such resource blocks are used to transmit several different physical downlink channels.

[0028] According to various embodiments, UE 122 and UE 120 and RAN node 114 and / or RAN node 116 communicate data (e.g., transmit data and receive data) through a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed frequency band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed frequency band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, and the unlicensed spectrum may include a 5 GHz frequency band.

[0029] To operate in the unlicensed spectrum, the UE 122 and the UE 120 and the RAN node 114 or the RAN node 116 may operate using LAA, eLAA, and / or feLAA mechanisms. In these specific implementations, the UE 122 and the UE 120 and the RAN node 114 or the RAN node 116 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0030] LBT is a mechanism by which equipment (e.g., UE 122 and UE 120, RAN node 114 or RAN node 116, etc.) senses a medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The 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 over a period of time on an expected transmission band and comparing the sensed RF energy to a predefined or configured threshold.

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

[0032] The LAA mechanism is built on the CA technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, so the maximum aggregated bandwidth is 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC may have a different bandwidth from other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are typically the same for DL ​​and UL.

[0033] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL, and may handle activities related to RRC and NAS. Other serving cells are referred to as SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing PCCs may require the UE 122 to undergo a switch. In LAA, eLAA, and feLAA, some or all of the SCells may operate in an unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may 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. The PDCCH carries, among other information, information about transport formats and resource allocations related to the PDSCH channel. It may also inform UE 122 and UE 120 about transport formats, resource allocations, and HARQ information related to uplink shared channels. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 120 within a cell) may be performed at either RAN node 114 or RAN node 116 based on channel quality information fed back from either UE 122 and UE 120. Downlink resource allocation information may be sent on the PDCCH for (e.g., allocated to) each of UE 122 and UE 120.

[0035] PDCCH uses CCE to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbols 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 of four physical resource elements, respectively, called REGs. Four quadrature phase shift keying (QPSK) symbols can be mapped to each REG. Depending on the size of the DCI and channel conditions, one or more CCEs can be used to transmit the PDCCH. There may be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation levels, L=1, 2, 4, or 8).

[0036] Some embodiments may use the concept of resource allocation for control channel information, which is an extension of the above concept. For example, some embodiments may utilize EPDCCH that uses PDSCH resources for control information transmission. One or more ECCEs may be used to transmit EPDCCH. Similar to the above, each ECCE may correspond to nine sets of four physical resource elements, referred to as EREG. In some cases, ECCE may have other numbers of EREGs.

[0037] The RAN node 114 or the RAN node 116 may be configured to communicate with each other via the interface 130. In an embodiment where the system 100 is an LTE system (e.g., when the CN 106 is an EPC), the interface 130 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs, etc.) connected to the EPC, 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). The X2-U may provide a flow control mechanism for user packets transmitted over the X2 interface, and may be used to transmit information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information about user data transmitted from the MeNB to the SeNB; information about the successful delivery of PDCP PDUs from the SeNB to the UE 122 in sequence for user data; information about PDCP PDUs that are not delivered to the UE 122; information about the current minimum expected buffer size at the Se NB for transmitting user data to the UE; and the like. X2-C can provide intra-LTE access mobility functions, including context transfer from source eNB to target eNB, user plane transmission control, etc.; load management functions; and inter-cell interference coordination functions.

[0038] In an embodiment where the system 100 is an SG or NR system (e.g., when the CN 106 is an SGC), the interface 130 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs, etc.) connected to an SGC, between a RAN node 114 (e.g., a gNB) and an eNB connected to an SGC, and / or between two eNBs connected to a 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. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support / provide data forwarding and flow control functions. The Xn-C may provide management and error handling functions for managing the functions of the Xn-C interface; mobility support for UE 122 in a connected mode (e.g., CM-CONNECTED) includes functions for managing UE mobility in a connected mode between one or more RAN nodes 114 or RAN nodes 116. The mobility support may include context transfer from the old (source) serving RAN node 114 to the new (target) serving RAN node 116; and control of the user plane tunnel between the old (source) serving RAN node 114 and the new (target) serving RAN node 116. The protocol stack of Xn-U may include a transport network layer built on an Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and / or IP layer 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 SCTP. SCTP may be on top of the IP layer and may provide guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transport 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 or similar to the user plane and / or control plane protocol stacks shown and described herein.

[0039] (R)AN 108 is illustrated as being communicatively coupled to a core network—in this embodiment, to CN 106. CN 106 may include one or more network elements 132 configured to provide various data and telecommunication 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 one physical node or separate physical nodes, including components for reading and executing instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, NFV may be used to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage media (described in further detail below). A logical instantiation of CN 106 may be referred to as a network slice, and a logical instantiation of a portion of CN 106 may be referred to as a network sub-slice. NFV architecture 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 (alternatively performed by proprietary hardware). In other words, the NFV system may be used to perform a virtual or reconfigurable implementation of one or more EPC components / functions.

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

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

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

[0043] Figure 2 An example of a V2X communication system is shown, and the figure is also provided to explain the hidden terminal problem in previous V2X attempts. Initially, it should be understood that direct communications between vehicles and other devices (V2V, V2I) use the so-called PC5 interface. PC5 refers to the reference point for a UE (i.e., a mobile handset) to communicate directly with another UE through a direct channel (communication with a base station is not used for a PC5 link). At the system architecture level, proximity services (ProSe) are features of the architecture that specify direct communications between UEs. In the 3GPP RAN specifications, "side link" is a term that refers to direct communications through PC5. The PC5 interface was originally used to address the needs of mission-critical communications for the public safety community (public safety LTE or PS-LTE) in previous versions of the 3GPP standard.

[0044] exist Figure 2 In the example of , UE B is within the transmission range of both UE A and UE C. UE B can then receive transmissions from UE A and UE C and detect the subchannel resource reservations of UE A and UE C. However, UE A and UE C are out of range of each other and thus experience the hidden terminal problem. Therefore, UE A and UE C may inadvertently select the same resources for their transmissions to UE B.

[0045] Release 16 (Rel-16) of the 3GPP standard (also known as 3GPP R16) defines two modes (Mode 1 and 2) for selecting subchannels in NR V2X SL communication using the NR V2X PC5 interface. In Mode 1, the gNB or eNB allocates and manages SL radio resources for V2V communication in Mode 1 using the NR (or LTE) Uu interface. Therefore, the UE operates in network coverage using Mode 1. In Mode 2, when in NR V2X, the UE can autonomously select its SL resources (one or several subchannels) from a resource pool. In this case, the UE can operate without network coverage.

[0046] Figure 3An example timing diagram is shown for sensing in NR V2X Rel-16 where the system is based on LTE-V2X (and is performed in a Mode 2 transmitting UE). Sensing requires collection, selection (evaluation), and reservation. Collection is done at all times (which has a cost in terms of power usage). Selection / reservation is done when resources need to be allocated. However, LTE-V2X partial sensing requires collection, limited selection, and reservation. In addition to the above reference Figure 2 Besides the mentioned collision (hidden node) problem, another problem not solved in previous sensing based resource selection (Mode 2) attempts is half duplex, e.g. because the UE cannot sense reservations from other UEs announced in the timeslots of the sensing window in which the UE transmits.

[0047] In inter-UE coordination (IUC)—an SL enhancement adapted for Release 17 (Rel-17) of the 3GPP standard designed to address the hidden terminal problem—UEs can assist other UEs in their resource selection process. The 3GPP RAN1#104 meeting concluded that inter-UE coordination in Mode 2 is feasible and beneficial (e.g., reliability, etc.) compared to Rel-16 Mode 2 Resource Allocation (RA), and therefore recommended the specification of this feature. In the 3GPP RAN1#104 meeting, items for future study include details of resource conflicts, such as the types of resource conflicts; details of UE A-side sensing operations; and which type(s) of resource set information is beneficial / feasible for which type(s) of forced conversion.

[0048] In some embodiments, there are three types of inter-UE coordination: Type A, B and C. In Type A, the assisting UE restricts the resources that the assisted UE can use (i.e., whitelist). In other words, UE A sends to UE B a set of resources that are preferred for UE B's transmissions, e.g., based on its sensing results. In Type B (i.e., blacklist), UE A sends to UE B a set of resources that are not preferred for UE B's transmissions, e.g., based on its sensing results and / or expected / potential resource conflicts. In Type C (i.e., collision list), UE A sends to UE B a set (history) of resources for which resource conflicts were detected. NOTE: These different types may be used in combination with each other.

[0049] According to the previous behavior (i.e., the behavior specified by 3GPP R16), the transmitting UE performs sensing at all times based on the RRC configuration. The problem with this approach is that UE B cannot assume that UE A is supporting IUC to always perform "full sensing" and always have results available for response. Another problem is the transmit / receive role mismatch: sensing is not used for receiving UEs at all. (SIBs are not configurable for transmission pools). Finally, there is the problem of configuration mismatch: even if UE A performs its own full sensing for transmission purposes, it may not be sensing the same transmission pool as UE B.

[0050] To support both Type A and Type B, some implementations include "sensing on demand". For example, Figure 4 It is shown that with on-demand sensing, UE A does not normally perform sensing. It starts sensing after receiving a request from another UE B via the PC5 link. This also means that the response may not be immediately available, because the sensing takes time to complete (i.e., collection + selection / evaluation). In order to perform on-demand sensing, it can be configured in the PC5 signaling. For type B or type C, sensing is optional. In addition, the detection of "negative" selection can come from: collision detection during the UE's own reception process, or resource reservation that UE A itself has completed.

[0051] In some embodiments, on-demand sensing and inter-UE coordination may be extended to Mode 1, for example, if simultaneous Mode 1 / Mode 2 is supported in Rel-17 / Rel-18.

[0052] In some embodiments, the triggering condition may be related to how the signaling is designed. For example, Figure 5 Three different triggering mechanisms are shown.

[0053] exist Figure 5 On the left side of FIG, a one-shot model is shown. According to this model, UE B tells UE A what to sense / check, and UE A responds with the result immediately or soon after. For one-shot IUC: MAC-CE is preferred, but PC5-RRC can also be used.

[0054] Figure 5 The middle and right sides of the figure show different subscription models. In both, UE B subscribes to UE A's IUC service using upper layer signaling. In some embodiments, the upper layer signaling includes PC5-RRC, and then the exact exchange after subscription can be performed as MAC CE or PC5-RRC. Once subscribed, UE A periodically (without request), such as Figure 5 , or the event trigger location, such as Figure 5In some embodiments, the triggering event for UE A may include: the number / ratio of good or bad resources exceeds a certain amount; the channel busy radio (CBR) is high, or UE B explicitly requests it (e.g., in L1 SCI signaling or MAC-CE).

[0055] Figure 6 Shows Figure 5 An example of the timing relationship of different subscription mechanisms is shown in . UE A starts sensing when UE A receives the target transmission pool information. Note that it is possible that UE A may have already started sensing the target pool due to some other reasons (e.g., previously requested by another peer UE).

[0056] It is possible that the "IUC subscription" signaling gives the UE the entire pool to sense, but sends a follow request to reduce the granularity of the reporting (only some resources need to be indicated as preferred or not preferred).

[0057] Figure 7 Shows Figure 5 In one embodiment, the one-shot model is basically used as a subscription mechanism, but with a one-time timing trigger. Figure 7 The left side of FIG. 4 shows an example of UE A receiving a request and responding after sensing. The top of the right side shows a Type C immediate response without sensing. Type C reporting may not require sensing (resource conflict detected). Figure 7 The bottom right side of the figure shows that the response is provided during sensing, and UE A may stop sensing to respond to the one-shot request.

[0058] Figure 8 A routine 800 is shown for request / subscription signaling with a second UE via a PC5 link for configuring inter-UE coordination with on-demand sensing performed by a first user equipment (UE) for a 5G network. In block 802, the routine 800 identifies a transmission resource pool of the first UE to be sensed or evaluated by the second UE. In block 804, the routine 800 instructs the second UE to report information indicating a quantity of resources. In block 806, the routine 800 instructs the second UE to evaluate the resources.

[0059] In some embodiments, the request / subscription signaling covers the following aspects: (1) identifying the transmission resource pool (of UE B) that UE A is to sense / evaluate (including the four options described below); (2) indicating how much resources need to be reported, such as minimum and maximum size limits, type A / B / C constraints; (3) instructing UE A how to evaluate resources with additional parameters, such as SL priority of UE B's service, periodicity of resource reservation, and a reselection counter (e.g., an upper limit on how long the periodicity will last, and the resources will be used periodically until the reselection counter is reached); and (4) optional additional constraints / conditions, such as immediate response timing requirements or timing boundaries based on packet delay budgets.

[0060] When instructing UE A how to evaluate resources with additional parameters, UE A may use priority x to evaluate the sensing result. For example, if UE A is sensing a transmission with a relatively lower priority than priority x in a certain resource, the evaluation result of the resource will be negatively affected (compared to a completely empty resource), but if the sensed SL transmission has a higher priority than priority x, the impact is greater. Moreover, the resource reservation period refers to the reliability of the sensing need to consider the "periodic" reservation, so in some embodiments, any conflict for future reservations of periodicity T will be considered.

[0061] The four options for identifying the transport resource pool include (1) a transport pool identifier (ID), i.e., an index, which means that the pool ID allocation is uniform across all gNBs and out-of-coverage (OOC) configurations; (2) an implicit indication corresponding to the transport pool used by UE B to transmit its request (without indicating the pool ID); (3) explicit transport pool configuration, i.e., providing pool information, which may have a large overhead suitable for RRC signaling; and (4) an explicit sequence of resources, such that for each resource, the frequency carrier, subchannel (starting resource block and number resource blocks), and time slot index are indicated. When there is an explicit sequence of resources to be signaled, there may be options to reduce the size and how to order the sequence (e.g., based on time or subchannel).

[0062] If request signaling is used as configuration of a subscription mechanism, it may include a periodic timer or indicate that it is event triggered. Examples of triggering events are described previously (e.g., the number / ratio of good or bad resources exceeds a certain amount, CBR is high, or UE explicitly requests).

[0063] Fig. 9A routine 900 is shown for configuring response signaling with a second UE via a PC5 link for inter-UE coordination with on-demand sensing performed by a first user equipment (UE) for a 5G network. In block 902, the routine 900 receives a request signal for inter-UE coordination from the second UE. In block 904, the routine 900 indicates a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list. In block 906, the routine 900 provides a validity time for the sensing result.

[0064] In some embodiments, the design of the response signaling includes information indicating a set of one or more resources. The information may include the set type (A (white list), B (black list) or C (collision list)). Each resource may be represented by an index, corresponding to the pool configuration or sequence of the resources requested in the request signaling. It may also be sent as a bitmap, where "0" means an unconventional resource and "1" means an available resource, or vice versa. Further information may also be included to classify the arguments for resource recommendations, for example, indicating whether the blacklist is based on sensing (i.e., potentially bad resources, but still available) or data reception decoding (i.e., obviously unusual resources). In addition, for resources indicated in type A or B, they are indicated as single-shot recommendations or periodic recommendations. This means that the resources indicated in set A or B are considered to be good for one-time use, or good for periodic resource reservation (e.g., use every 100ms).

[0065] The response signaling information may also include a validity time. It is not possible for UE A to always have a "fresh" result, because, for example, sensing is computationally intensive and takes time. To save power, UE A may just report some old results as a weak or general guide. This may also be replaced by a timestamp when the result was obtained. Thus, the validity information element (IE) may be used to indicate the validity of: (1) overall assistance information; (2) per individual type; or (3) per individual resource.

[0066] In some embodiments, there is a priority for IUC signaling. For SL MAC CE, this may be equal to or higher than the priority of SL-CSI reporting. For PC5-RRC, this is similar to the logical channel (LCH) priority of other PC5-RRC signaling in the same SL-SRB.

[0067] According to some embodiments, Uu signaling (e.g., signaling from the gNB) is included to enable additional functionality. For example, inter-UE coordination can be enabled or disabled per cell or per UE via Uu signaling, in which case the per-cell signaling can be in the V2X SIB, or the per-UE signaling can be in a dedicated RRC configuration (e.g., RRCReconfiguration) or pre-configured (out-of-coverage case). In another example, the RRC_CONNECTED UE B shares the received IUC content from UE A to its serving gNB in ​​UEAssistanceInformation. And in another example, "inter-UE coordination" is defined as a new UE capability for the sidelink exchanged in the Uu or PC5 interface.

[0068] Fig.10 1 is a block diagram illustrating a component 1000 capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and capable of performing any one or more of the methods discussed herein, according to some exemplary embodiments. Specifically, Fig.10 A schematic diagram of hardware resources 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 can be communicatively coupled via a bus 1016. For embodiments in which node virtualization (e.g., NFV) is utilized, a hypervisor 1022 can be executed to provide an execution environment for one or more network slices / sub-slices to utilize the hardware resources 1002.

[0069] 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.

[0070] 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, etc.

[0071] The communication resources 1024 may include interconnect or network interface components or other suitable devices to communicate with one or more peripheral devices 1004 or one or more databases 1020 via the network 1018. For example, the communication resources 1024 may include wired communication components (e.g., for coupling via a universal serial bus (USB)), cellular communication components, NFC components, Parts (e.g. Low power consumption), components and other communication components.

[0072] The instructions 1012 may include software, programs, applications, applet, applications, or other executable code for causing at least any one of the processors 1006 to perform any one or more of the methods discussed herein. The instructions 1012 may reside completely or partially in at least one of the processors 1006 (e.g., in a cache memory of the processor), the memory / storage device 1014, or any suitable combination thereof. In addition, any portion of the instructions 1012 may be transmitted to the hardware resources 1002 from any combination of the peripheral device 1004 or the database 1020. Therefore, the memory of the processor 1006, the memory / storage device 1014, the peripheral device 1004, and the database 1020 are examples of computer-readable and machine-readable media.

[0073] 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 following examples section. For example, the baseband circuit described above in conjunction with one or more of the foregoing figures may be configured to operate according to one or more of the following examples. For another example, the circuits 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.

[0074] The following examples relate to additional embodiments.

[0075] Embodiment 1 is a method for request signaling with a second UE via a PC5 link for configuring inter-UE coordination, performed by a first user equipment (UE) for a 5G network, the method comprising: identifying a transmission resource pool of the first UE that the second UE is to sense or evaluate; instructing the second UE to report information indicating a certain amount of resources; and instructing the second UE to evaluate the resources to be reported.

[0076] Embodiment 2 is a method according to embodiment 1, wherein the instructing the second UE to evaluate the resources to be reported is based on the sidelink priority of the traffic of the first user equipment, the periodicity of resource reservation, and a reselection counter.

[0077] Embodiment 3 is a method according to embodiment 1, wherein the instructing the second UE to evaluate the resources to be reported is also based on a timing requirement for the reporting information.

[0078] Embodiment 4 is a method according to embodiment 1, wherein the identifying the transmission resource pool includes providing a transmission pool identifier.

[0079] Embodiment 5 is a method according to embodiment 4, wherein the transmission pool identifier corresponds to a pool configured in radio resource control (RRC) signaling.

[0080] Embodiment 6 is a method according to embodiment 1, wherein the identification of the transmission resource pool comprises an implicit identification corresponding to the transmission resource pool used by the first UE to transmit its request.

[0081] Embodiment 7 is a method according to embodiment 1, wherein the identifying the transmission resource pool includes providing an explicit transmission pool configuration.

[0082] Embodiment 8 is a method according to embodiment 1, wherein the identifying the transmission resource pool includes providing an explicit sequence of resources.

[0083] Embodiment 9 is a method for configuring inter-UE coordination by performing response signaling with a second UE via a PC5 link by a first user equipment (UE) for a 5G network, the method comprising: receiving a request signal for inter-UE coordination from the second UE; indicating a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list; and providing a validity time of the indicated resources.

[0084] Embodiment 10 is a method according to embodiment 9, wherein each resource in the collection is represented by an index corresponding to a pool configuration.

[0085] Embodiment 11 is a method according to embodiment 9, wherein each resource in the set is represented by an index corresponding to a sequence of resources requested in the request signal.

[0086] Embodiment 12 is a method according to embodiment 9, wherein the resources in the set are whitelist type resources, and the indication further includes indicating that the resources are single-shot resources.

[0087] Embodiment 13 is a method according to embodiment 9, wherein the resources in the set are blacklist type resources, and the indication further includes indicating that the resources are single-shot resources.

[0088] Embodiment 14 is a method according to embodiment 9, wherein the resources in the set are whitelist type resources, and the indication further includes indicating that the resources are periodic resources.

[0089] Embodiment 15 is a method according to embodiment 9, wherein the resources in the set are blacklist type resources, and the indication further includes indicating that the resources are periodic resources.

[0090] Embodiment 16 is a method according to embodiment 9, wherein each resource in the collection is represented by a bitmap.

[0091] Embodiment 17 is a method according to embodiment 9, wherein the resources in the set are blacklist type resources, and further comprising indicating whether the resource is blacklisted based on sensing.

[0092] Embodiment 18 is a method according to embodiment 9, wherein the resources in the set are blacklist type resources, and further comprising indicating whether the resource is blacklisted based on the decoding.

[0093] Embodiment 19 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by a first user equipment (UE) configured to perform request signaling with a second UE via a PC5 link for inter-UE coordination, cause the first UE to: identify a transmission resource pool of the first UE that the second UE is to sense or evaluate; instruct the second UE to report information indicating a certain amount of resources; and instruct the second UE to evaluate the resources to be reported.

[0094] Embodiment 20 is a computer-readable storage medium according to embodiment 19, wherein the instructions further cause the first UE to instruct the second UE to evaluate the resources to be reported based on the sidelink priority of the service of the first user equipment, the periodicity of resource reservation, and the reselection counter.

[0095] Embodiment 21 is a computer-readable storage medium according to embodiment 19, wherein the instructions further cause the first UE to instruct the second UE to evaluate the resources to report based on a timing requirement of the reporting information.

[0096] Embodiment 22 is the computer-readable storage medium of embodiment 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on a transmission pool identifier.

[0097] Embodiment 23 is the computer-readable storage medium of embodiment 22, wherein the transmission pool identifier corresponds to a pool configured in radio resource control (RRC) signaling.

[0098] Embodiment 24 is a computer-readable storage medium according to embodiment 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an implicit identification corresponding to the transmission resource pool used by the first UE to transmit its request.

[0099] Embodiment 25 is a computer-readable storage medium according to embodiment 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an explicit transmission pool configuration.

[0100] Embodiment 26 is a computer-readable storage medium according to embodiment 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an explicit sequence of resources.

[0101] Embodiment 27 is a non-transitory computer-readable storage medium, which includes instructions that, when executed by a first user equipment (UE) configured to perform response signaling with a second UE via a PC5 link for inter-UE coordination, cause the first UE to: receive a request signal for inter-UE coordination from the second UE; indicate a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list; and provide a validity time for the indicated resources.

[0102] Embodiment 28 is the computer-readable storage medium of embodiment 27, wherein each resource in the collection is represented by an index corresponding to a pool configuration.

[0103] Embodiment 29 is the computer-readable storage medium of embodiment 27, wherein each resource in the set is represented by an index corresponding to a sequence of resources requested in the request signal.

[0104] Embodiment 30 is a computer-readable storage medium according to embodiment 27, wherein the resources in the set are whitelist type resources, and the indication further includes indicating that the resources are single-shot resources.

[0105] Embodiment 31 is a computer-readable storage medium according to embodiment 27, wherein the resources in the set are blacklist type resources, and the indication further includes indicating that the resources are single-shot resources.

[0106] Embodiment 32 is a computer-readable storage medium according to embodiment 27, wherein the resources in the set are whitelist type resources, and the indication further includes indicating that the resources are periodic resources.

[0107] Embodiment 33 is a computer-readable storage medium according to embodiment 27, wherein the resources in the set are blacklist type resources, and the indication further includes indicating that the resources are periodic resources.

[0108] Embodiment 34 is the computer-readable storage medium of embodiment 27, wherein each resource in the collection is represented by a bitmap.

[0109] Embodiment 35 is the computer-readable storage medium of embodiment 27, wherein the resources in the set are blacklisted type resources, and wherein the instructions further configure the computer to indicate whether the resource is blacklisted based on sensing.

[0110] Embodiment 36 is a computer-readable storage medium according to embodiment 27, wherein the resources in the set are blacklisted type resources, and wherein the instructions further configure the computer to indicate whether the resource is blacklisted based on the decoding.

[0111] Embodiment 1C may include an apparatus comprising means for performing one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0112] Embodiment 2C may include one or more non-transitory computer-readable media, which include instructions that, when executed by one or more processors of an electronic device, cause the electronic device to perform one or more elements of a method described in or related to any of the above embodiments or any other method or process described herein.

[0113] Embodiment 3C may include a device comprising logic components, modules, or circuits for performing one or more elements of the methods described in or related to any of the above embodiments or any other methods or processes described herein.

[0114] Embodiment 4C may include any of the methods, techniques or processes or parts or components thereof described in or related to any of the above embodiments.

[0115] Embodiment 5C may include a device comprising: one or more processors and one or more computer-readable media, wherein the one or more computer-readable media include instructions that, when executed by the one or more processors, cause the one or more processors to perform a method, technique, process, or portion thereof described in or related to any one of the above embodiments.

[0116] Embodiment 6C may include a signal or a portion or component thereof as described in or related to any of the above embodiments.

[0117] Embodiment 7C may include a datagram, packet, frame, segment, protocol data unit (PDU) or message or a portion or component thereof as described in or related to any of the above embodiments, or as otherwise described in the present disclosure.

[0118] Embodiment 8C may include a signal encoded with data or a portion or component thereof as described in any of the above embodiments or related thereto, or as otherwise described in this disclosure.

[0119] Embodiment 9C may include a signal or a portion or component thereof encoded with a datagram, packet, frame, segment, PDU or message as described in or related to any of the above embodiments, or described in other ways in the present disclosure.

[0120] Embodiment 10C may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors will cause the one or more processors to perform a method, technique, or process, or a portion thereof, described in or related to any of the above embodiments.

[0121] Embodiment 11C may include a computer program comprising instructions, wherein execution of the program by a processing element causes the processing element to perform a method, technique, or process, or a portion thereof, described in or related to any one of the above embodiments.

[0122] Embodiment 12C may include signals in a wireless network as shown and described herein.

[0123] Embodiment 13C may include a method of communicating in a wireless network as shown and described herein.

[0124] Embodiment 14C may include a system for providing wireless communications as shown and described herein.

[0125] Embodiment 15C may include an apparatus for providing wireless communications as shown and described herein.

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

[0127] Embodiments and implementations of the systems and methods described herein may include various operations that may be embodied in machine executable instructions to be executed by a computer system. A computer system may include one or more general or special purpose computers (or other electronic devices). A computer system may include hardware components that include specific logic components for performing operations, or may include a combination of hardware, software, and / or firmware.

[0128] It should be appreciated that the systems described herein include descriptions of specific embodiments. These embodiments may be combined into a single system, partially incorporated into other systems, separated into multiple systems, or otherwise divided or combined. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment may be used in another embodiment. For clarity, these parameters, attributes, aspects, etc. are described only in one or more embodiments, and it should be appreciated that unless otherwise stated herein, these parameters, attributes, aspects, etc. may be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment.

[0129] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining 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 the authorized use should be clearly stated to users.

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

Claims

1. A method for request signaling via a PC5 link with a second UE for configuring inter-UE coordination, performed by a first user equipment UE for a 5G network, the method comprising: identifying a transmission resource pool of the first UE to be sensed or evaluated by the second UE; indicating that the resource set from the transmission resource pool corresponds to a white list, a black list or a collision list; providing validity times for resources indicated in the resource set corresponding to the whitelist, blacklist or collision list; instructing the second UE to report information indicating a certain amount of resources based on the whitelist, blacklist or collision list; as well as The second UE is instructed to evaluate the resources to be reported.

2. The method of claim 1, wherein the instructing the second UE to evaluate the resources to be reported is based on a sidelink priority of a service of the first user equipment, a periodicity of resource reservation, and a reselection counter.

3. The method of claim 1, wherein the instructing the second UE to evaluate the resources to be reported is also based on a timing requirement for the reporting information. The method of claim 1 , wherein said identifying said transmission resource pool comprises providing a transmission pool identifier. The method of claim 4 , wherein the transmission pool identifier corresponds to a pool configured in radio resource control (RRC) signaling.

6. The method of claim 1, wherein the identifying the transmission resource pool comprises an implicit identification corresponding to a transmission resource pool used by the first UE to transmit its request.

7. The method of claim 1, wherein said identifying said transmit resource pool comprises providing an explicit transmit pool configuration.

8. The method of claim 1, wherein said identifying said transmission resource pool comprises providing an explicit sequence of resources.

9. A method for configuring inter-UE coordinated response signaling with a second UE via a PC5 link, performed by a first user equipment UE for a 5G network, the method comprising: receiving a request signal for inter-UE coordination from the second UE; indicating a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list; as well as A validity time is provided for resources indicated in the resource set corresponding to the whitelist, blacklist, or collision list.

10. The method of claim 9, wherein each resource in the collection is represented by an index corresponding to a pool configuration.

11. The method of claim 9, wherein each resource in the set is represented by an index corresponding to a sequence of resources requested in the request signal. 12 . The method according to claim 9 , wherein the resources in the set are whitelist type resources, and the indicating further comprises indicating that the resources are one-shot resources.

13. The method according to claim 9, wherein the resources in the set are blacklist type resources, and the indicating further comprises indicating that the resources are one-shot resources.

14. The method of claim 9, wherein the resources in the set are whitelist type resources, and the indicating further comprises indicating that the resources are periodic resources.

15. The method of claim 9, wherein the resources in the set are blacklist type resources, and the indicating further comprises indicating that the resources are periodic resources.

16. The method of claim 9, wherein each resource in the collection is represented by a bitmap.

17. The method of claim 9, wherein the resources in the set are blacklisted type resources, and further comprising indicating whether the resource is blacklisted based on sensing.

18. The method of claim 9, wherein the resources in the set are blacklisted type resources, and further comprising indicating whether the resource is blacklisted based on the decoding.

19. A non-transitory computer-readable storage medium comprising instructions that, when executed by a first user equipment (UE) configured to perform request signaling with a second UE via a PC5 link for inter-UE coordination, cause the first UE to: identifying a transmission resource pool of the first UE to be sensed or evaluated by the second UE; indicating that the resource set from the transmission resource pool corresponds to a white list, a black list or a collision list; providing validity times for resources indicated in the resource set corresponding to the whitelist, blacklist or collision list; instructing the second UE to report information indicating a certain amount of resources based on the whitelist, blacklist or collision list; as well as The second UE is instructed to evaluate the resources to be reported.

20. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to instruct the second UE to evaluate the resources to report based on a sidelink priority of traffic of the first user equipment, a periodicity of resource reservation, and a reselection counter.

21. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to instruct the second UE to evaluate the resources to report based on a timing requirement of the reporting information.

22. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on a transmission pool identifier.

23. The computer-readable storage medium of claim 22, wherein the transmission pool identifier corresponds to a pool configured in radio resource control (RRC) signaling.

24. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an implicit identification corresponding to the transmission resource pool used by the first UE to transmit its request.

25. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an explicit transmission pool configuration.

26. The computer-readable storage medium of claim 19, wherein the instructions further cause the first UE to identify the transmission resource pool based on an explicit sequence of resources.

27. A non-transitory computer-readable storage medium comprising instructions that, when executed by a first user equipment UE configured to perform response signaling with a second UE via a PC5 link for inter-UE coordination, cause the first UE to: receiving a request signal for inter-UE coordination from the second UE; indicating a set of one or more resources, wherein the set is indicated as corresponding to a whitelist, a blacklist, or a collision list; as well as A validity time is provided for resources indicated in the resource set corresponding to the whitelist, blacklist, or collision list.

28. The computer-readable storage medium of claim 27, wherein each resource in the collection is represented by an index corresponding to a pool configuration.

29. The computer-readable storage medium of claim 27, wherein each resource in the set is represented by an index corresponding to a sequence of resources requested in the request signal.

30. The computer-readable storage medium of claim 27, wherein the resources in the set are whitelist-type resources, and the indicating further comprises indicating that the resources are one-shot resources.

31. The computer-readable storage medium of claim 27, wherein the resources in the set are blacklist-type resources, and the indicating further comprises indicating that the resources are one-shot resources.

32. The computer-readable storage medium of claim 27, wherein the resources in the set are whitelist-type resources, and the indicating further comprises indicating that the resources are periodic resources.

33. The computer-readable storage medium of claim 27, wherein the resources in the set are blacklist-type resources, and the indicating further comprises indicating that the resources are periodic resources.

34. The computer-readable storage medium of claim 27, wherein each resource in the collection is represented by a bitmap.

35. The computer-readable storage medium of claim 27, wherein the resources in the set are blacklisted-type resources, and wherein the instructions further configure the computer to indicate whether the resource is blacklisted based on sensing.

36. The computer-readable storage medium of claim 27, wherein the resources in the set are blacklisted type resources, and wherein the instructions further configure the computer to indicate whether the resource is blacklisted based on the decoding.

Images