Method and apparatus for enhanced resource allocation in sl communications

Abstract

This disclosure relates to a communication method and system for integrating fifth-generation (5G) communication systems, which support higher data rates than fourth-generation (4G) systems, with technologies for the Internet of Things (IoT). This disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, security, and safety services. Methods and apparatus in wireless communication systems are also included. A method for operating a first user equipment (UE) includes: receiving inter-UE coordination information from a second UE, including sidelink (SL) resources and a district identifier (ID), the information being used for resource allocation for the transmission of SL data; identifying the transmission range of the SL data transmission; calculating the distance between the second UE and the first UE based on the district ID; determining whether the inter-UE coordination information is valid based on the transmission range and distance; confirming the SL resources based on the determination that the inter-UE coordination information is valid; and transmitting the SL data.

Description

Technical Field

[0001] This disclosure generally relates to wireless communication systems, and more specifically, to enhanced resource allocation in wireless communication systems. Background Technology

[0002] To meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop improved 5G or near-5G communication systems. Therefore, 5G or near-5G communication systems are also referred to as "super-4G networks" or "post-LTE systems." 5G communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., the 60GHz band) to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies have been discussed in 5G communication systems. Furthermore, improvements to the system network are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding and modulation (ACM), as well as filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet (as a human-centric network of connections where humans generate and consume information) is now evolving into the Internet of Things (IoT) (where distributed entities such as things exchange and process information without human intervention). The Internet of Everything (IoE) has emerged, a combination of IoT technology and big data processing technology connected to cloud servers. Because IoT implementations require technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology, sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have recently been studied. Such an IoT environment can provide intelligent Internet of Things (IoT) technology services that create new value for human life by collecting and analyzing data generated in connected things. IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, healthcare, smart appliances, and advanced medical services, through the integration and combination of existing information technology (IT) with various industrial applications.

[0004] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RAN), as an application of the aforementioned big data processing technologies, can also be considered an example of the convergence between 5G and IoT technologies. Summary of the Invention

[0005] Technical issues

[0006] Fifth-generation (5G), or new radio (NR) mobile communications, is currently gaining momentum due to global technological activity from both industry and academia regarding various candidate technologies. Potential drivers for 5G / NR mobile communications include massive MIMO (Massively Multi-band Antenna) technologies from traditional cellular bands to higher frequencies to provide beamforming gain and support increased capacity; new waveforms for flexible adaptation to various services / applications with different requirements (e.g., new radio access technologies (RAT)); and new multiple access schemes to support massive connectivity.

[0007] Technical solution

[0008] In one embodiment, a first user equipment (UE) is provided in a wireless communication system. The first UE includes a transceiver configured to receive inter-UE coordination information from a second UE, including sidelink (SL) resources and a district identifier (ID), the inter-UE coordination information being used for resource allocation for the transmission of SL data. The first UE further includes a processor operatively coupled to the transceiver, the processor being configured to: identify a transmission range for the transmission of the SL data; calculate a distance between the second UE and the first UE based on the district ID; determine whether the inter-UE coordination information is valid based on the transmission range and the distance; and confirm the SL resources based on the determination that the inter-UE coordination information is valid. The transceiver of the first UE is further configured to transmit the SL data.

[0009] In another embodiment, a method for a first UE in a wireless communication system is provided. The method includes: receiving inter-UE coordination information including SL resources and a district ID from a second UE, the inter-UE coordination information being used for resource allocation for the transmission of SL data; identifying the transmission range of the SL data transmission; calculating the distance between the second UE and the first UE based on the district ID; determining whether the inter-UE coordination information is valid based on the transmission range and the distance; confirming the SL resources based on determining that the inter-UE coordination information is valid; and transmitting the SL data.

[0010] In another embodiment, a second UE is provided in a wireless communication system. The second UE includes a processor configured to generate inter-UE coordination information including SL resources and a district ID. The second UE also includes a transceiver operatively connected to the processor, configured to: transmit the inter-UE coordination information to a first UE for resource allocation for the transmission of SL data; and receive the SL data from the first UE, wherein, for the transmission of the SL data, a transmission range is identified, a distance between the second UE and the first UE is calculated based on the district ID, the validity of the inter-UE coordination information is determined based on the transmission range and the distance, and the SL resources are confirmed based on the determination that the inter-UE coordination information is valid.

[0011] Other technical features will be readily apparent to those skilled in the art from the following figures, descriptions and claims.

[0012] Before proceeding with specific embodiments, it may be advantageous to define certain words and phrases used throughout this patent document. The term “coupled” and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether these elements are physically in contact with each other. The terms “transmit,” “receive,” and “communicate,” and their derivatives, include both direct and indirect communication. The terms “comprising” and “including,” and their derivatives, mean unrestricted inclusion. The term “or” is inclusive, meaning and / or. The phrase “associated with” and its derivatives mean including, being contained within, interconnected with, containing, being included in, connected to or connected with, coupled to or coupled with, communicable with, cooperating with, interleaved, juxtaposed, proximate, bound to or bound with, having, possessing the properties of, related to, etc. The term “controller” refers to any device, system, or part thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can be centralized or distributed, whether local or remote. The phrase "at least one of..." when used with a list of items means that different combinations of one or more of the listed items can be used, and only one item from the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B, and C.

[0013] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each computer program being formed by computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation in appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium accessible by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, optical disc (CD), digital video disc (DVD), or any other type of storage. The term "non-transitory computer-readable medium" excludes wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media capable of permanently storing data and media capable of storing and later overwriting data, such as rewritable optical discs or erasable storage devices.

[0014] Definitions of certain other words and phrases are provided throughout this patent document. Those skilled in the art will understand that in many (if not most) cases, such definitions apply to both the prior and future uses of the words and phrases defined herein.

[0015] Beneficial effects

[0016] This disclosure relates to wireless communication systems, and more specifically, to enhanced resource allocation in wireless communication systems. Attached Figure Description

[0017] To more fully understand this disclosure and its advantages, reference will now be made to the following description taken in conjunction with the accompanying drawings, in which similar reference numerals denote similar parts:

[0018] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0019] Figure 2 An example gNB according to an embodiment of this disclosure is shown;

[0020] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0021] Figure 4 and Figure 5 An example wireless transmission path and an example wireless reception path are shown according to this disclosure;

[0022] Figure 6 An example V2X communication on a side link according to an embodiment of this disclosure is illustrated;

[0023] Figure 7 The signaling flow for enhanced SL resource allocation according to an embodiment of this disclosure is illustrated;

[0024] Figure 8 An example of full-channel sensing and resource selection according to an embodiment of the present disclosure is shown;

[0025] Figure 9A An example portion of channel sensing and resource selection according to an embodiment of this disclosure is shown;

[0026] Figure 9B Another example of a portion of channel sensing and resource selection according to an embodiment of this disclosure is shown;

[0027] Figure 10 The signaling flow for channel sensing and resource selection according to an embodiment of the present disclosure is shown;

[0028] Figure 11 A flowchart of a method for enhancing resource allocation according to an embodiment of the present disclosure is shown. Detailed Implementation

[0029] The following discussion Figures 1 to 11 The various embodiments used to describe the principles of this disclosure in this patent document are for illustrative purposes only and should not be construed as limiting the scope of this disclosure in any way. Those skilled in the art will understand that the principles of this disclosure can be implemented in any suitably arranged system or apparatus.

[0030] The following documents are hereby incorporated herein by reference, as fully set forth herein: 3GPP TS38.213v16.3.0, “NR; Physical Layer Procedures for Control”; 3GPP TS38.321v16.2.0, “Medium Access Control (MAC) protocol specification”; 3GPP TS38.331v.16.2.0, “Radio Resource Control (RRC) protocol specification”; and 3GPPTR 38.885v.16.0.0, “Study on NR Vehicle-to-Everything (V2X)”.

[0031] Down Figure 1-3 Various embodiments of communication technologies implemented in wireless communication systems and using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) are described. Figure 1-3The description is not intended to imply any physical or architectural limitation on the ways in which different embodiments may be implemented. Different embodiments of this disclosure may be implemented in any suitably arranged communication system.

[0032] Figure 1 An example wireless network according to an embodiment of this disclosure is shown. Figure 1 The illustrated embodiments of the wireless network are for illustrative purposes only. Other embodiments of the wireless network 100 may be used without departing from the scope of this disclosure.

[0033] like Figure 1 As shown, the wireless network includes gNB 101 (e.g., a base station, BS), gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130, such as the Internet, a proprietary Internet Protocol (IP) network, or other data network.

[0034] gNB 102 provides wireless broadband access to network 130 to a first plurality of UEs within its coverage area 120. The first plurality of UEs includes: UE 111, which may be located in a small business; UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a mobile phone, wireless laptop, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 to a second plurality of UEs within its coverage area 125. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101-103 may communicate with each other and with UEs 111-116 using 5G / NR, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.

[0035] Depending on the network type, the term "base station" or "BS" can refer to any component (or set of components) configured to provide wireless access to a network, such as a transmitting point (TP), a transmitting and receiving point (TRP), an enhanced base station (eNodeB or eNB), a 5G / NR base station (gNB), a macro cell, a femtocell, a WiFi access point (AP), or other wirelessly enabled device. A base station can provide wireless access in accordance with one or more wireless communication protocols, such as 5G / NR 3rd Generation Partnership Project (3GPP) NR, Long Term Evolution (LTE), LTE-A Advanced (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Similarly, depending on the network type, the term "user equipment" or "UE" can refer to any component such as a "mobile station," "subscriber station," "remote terminal," "wireless terminal," "receiving point," or "user device." For convenience, the terms “user equipment” and “UE” are used in this patent document to refer to a remote wireless device that wirelessly accesses the BS, regardless of whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered to be a fixed device (such as a desktop computer or vending machine).

[0036] The dashed lines show the approximate extent of coverage areas 120 and 125, which are shown as approximately circular for illustrative purposes only. It should be clearly understood that, depending on the configuration of the gNB and variations associated with natural and man-made obstacles in the wireless environment, the coverage areas associated with the gNB (such as coverage areas 120 and 125) may have other shapes, including irregular shapes.

[0037] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for enhanced resource allocation in SL communications. In some embodiments, one or more of gNBs 101-103 include circuitry, programming, or a combination thereof for enhanced resource allocation in SL communications.

[0038] As discussed in more detail below, wireless network 100 may have communication facilitated by one or more devices (e.g., UEs 112A to 112C) that can have sidelink communication with UE 111. UE 111 can provide sidelink communication by communicating directly with UEs 112A to 112C via a set of sidelinks, for example, when UEs 112A to 112C are located remotely, or when UEs 112A to 112C require the convenience of a network access connection (e.g., BS 102) in addition to or attached to conventional forward and / or backhaul connections. In one example, UE 111 is able to communicate directly with UEs 112A to 112C via sidelink communication, whether or not it is supported by BS 102. Various UEs (e.g., as depicted by UEs 113 to 116) may be able to communicate with one or more of their own devices (such as 112A to 112C of UE 111) or other devices.

[0039] although Figure 1 An example of a wireless network is shown, but more can be found on... Figure 1 Various modifications can be made. For example, the wireless network can include any number of gNBs and any number of UEs in any suitable arrangement. Similarly, gNB 101 can communicate directly with any number of UEs and provide these UEs with wireless broadband access to network 130. Likewise, each gNB 102-103 can communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Furthermore, gNB 101, gNB 102, and / or gNB 103 can provide access to other or additional external networks such as external telephone networks or other types of data networks.

[0040] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustrative purposes only, and Figure 1 The gNB 101 and gNB 103 can have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 2 This disclosure is not limited to any particular implementation of gNB.

[0041] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple RF transceivers 210a-210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0042] RF transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals transmitted by a UE in network 100 or by other UEs on a side link. RF transceivers 210a-210n down-convert the incoming RF signals to generate IF signals or baseband signals. The IF signals or baseband signals are sent to RX processing circuitry 220, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband signals or IF signals. RX processing circuitry 220 sends the processed baseband signals to controller / processor 225 for further processing.

[0043] TX processing circuit 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 225. TX processing circuit 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceivers 210a-210n receive the processed baseband or IF signals from TX processing circuit 215 and up-convert these baseband or IF signals into RF signals transmitted via antennas 205a-205n.

[0044] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of uplink channel signals and the transmission of downlink channel signals by the RF transceivers 210a-210n, the RX processing circuitry 220, and the TX processing circuitry 215 according to known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, the controller / processor 225 may support beamforming or directional routing operations, wherein outgoing signals from multiple antennas 205a-205n and incoming signals to multiple antennas 205a-205n are weighted differently to effectively guide the outgoing signals in a desired direction. In the gNB 102, any of a wide variety of other functions can be supported by the controller / processor 225.

[0045] The controller / processor 225 can also execute programs and other processes residing in memory 230, such as an operating system. The controller / processor 225 can move data into or out of memory 230 as needed by the executing processes.

[0046] The controller / processor 225 is also coupled to the backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. Interface 235 can support communication over any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a cellular communication system supporting 5G / NR, LTE, or LTE-A), interface 235 can allow the gNB 102 to communicate with other gNBs over a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, interface 235 can allow the gNB 102 to communicate over a wired or wireless local area network or over a wired or wireless connection to a larger network (such as the Internet). Interface 235 includes any suitable architecture that supports communication over wired or wireless connections, such as Ethernet or RF transceivers.

[0047] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0048] although Figure 2 An example of gNB 102 is shown, but it is possible to compare it with other models. Figure 2 Various changes can be made. For example, gNB 102 can include... Figure 2 Each component can be any number shown. As a particular example, an access point may include a plurality of interfaces 235, and a controller / processor 225 may support enhanced resource allocation. As another particular example, although gNB 102 is shown as a single instance including TX processing circuitry 215 and a single instance of RX processing circuitry 220, gNB 102 may include multiple instances of each (e.g., one per RF transceiver). Similarly, Figure 2 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed.

[0049] Figure 3 A UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of UE 116 shown is for illustrative purposes only, and Figure 1 UEs 111-115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 This disclosure is not intended to limit the scope to any particular implementation of the UE.

[0050] like Figure 3As shown, UE 116 includes an antenna 305, a radio frequency (RF) transceiver 310, a TX processing circuit 315, a microphone 320, and a receive (RX) processing circuit 325. UE 116 also includes a speaker 330, a processor 340, an input / output (I / O) interface (IF) 345, a touchscreen 350, a display 355, and a memory 360. The memory 360 includes an operating system (OS) 361 and one or more applications 362.

[0051] RF transceiver 310 receives incoming RF signals transmitted by a gNB of network 100 from antenna 305. RF transceiver 310 down-converts the incoming RF signals to generate an intermediate frequency (IF) signal or a baseband signal. The IF signal or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband signal or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., to obtain voice data) or to processor 340 for further processing (e.g., to obtain web browsing data).

[0052] The TX processing circuit 315 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (such as web data, email, or interactive video game data) from the processor 340. The TX processing circuit 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband signal or IF signal. The RF transceiver 310 receives the processed outgoing baseband signal or IF signal from the TX processing circuit 315 and up-converts the baseband signal or IF signal into an RF signal transmitted via the antenna 305.

[0053] Processor 340 may include one or more processors or other processing devices and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control the reception of downlink channel signals and / or sidelink channel signals and the transmission of uplink channel signals and / or sidelink channel signals by RF transceiver 310, RX processing circuitry 325 and TX processing circuitry 315 in accordance with known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0054] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as processes for enhancing resource allocation. Processor 340 can move data into or out of memory 360 as required by the executing processes. In some embodiments, processor 340 is configured to execute application 362 based on OS 361 or in response to signals received from gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptop computers and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0055] The processor 340 is also coupled to the touchscreen 350 and the display 355. The operator of the UE 116 can use the touchscreen 350 to input data into the UE 116. The display 355 may be a liquid crystal display, a light-emitting diode display, or other display capable of rendering text such as from a website and / or at least limited graphics.

[0056] The memory 360 is coupled to the processor 340. A portion of the memory 360 may include random access memory (RAM), and another portion of the memory 360 may include flash memory or other read-only memory (ROM).

[0057] although Figure 3 An example of UE 116 is shown, but it is possible to modify it. Figure 3 Make various changes. For example, Figure 3 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). Furthermore, although... Figure 3 The UE116 is shown configured as a mobile phone or smartphone, but the UE can be configured to operate as other types of mobile devices or fixed devices.

[0058] To meet the increased demand for wireless data services since the deployment of 4G communication systems and to enable various vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher frequency (mmWave) bands (e.g., the 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower frequency bands (such as 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive MIMO technologies are discussed in 5G / NR communication systems.

[0059] In addition, in 5G / NR communication systems, development is underway to improve system networks based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), and receiver interference cancellation.

[0060] The discussion of 5G systems and their associated frequency bands is for reference only, as certain embodiments of this disclosure can be implemented in 5G systems. However, this disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of this disclosure can be utilized in combination with any frequency band. For example, aspects of this disclosure can also be applied to the deployment of 5G communication systems, 6G, or even later versions that may use terahertz (THz) frequency bands.

[0061] The communication system includes a downlink (DL), an uplink (UL), and a sidelink (SL). The DL refers to a transmission from a base station or one or more transmitting points to a UE. The UL refers to a transmission from a UE to a base station or one or more receiving points. The SL refers to a transmission from one or more UEs to one or more UEs.

[0062] The time unit used for DL ​​signaling or UL signaling on a cell is called a time slot and may include one or more symbols. Symbols can also be used as an additional time unit. The frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes many subcarriers (SCs). For example, a time slot may have a duration of 0.5 milliseconds or 1 millisecond and include 14 symbols, and an RB may include 12 SCs with SC spacing of 15 kHz or 30 kHz, etc.

[0063] DL signals include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding Physical DL Shared Channel (PDSCH) or Physical DL Control Channel (PDCCH). The PDSCH or PDCCH can be transmitted on a variable number of time slot symbols, each consisting of one time slot symbol. For simplicity, the DCI format received by the UE-scheduled PDSCH is called the DL DCI format, while the DCI format transmitted from the UE-scheduled Physical Uplink Shared Channel (PUSCH) is called the UL DCI format.

[0064] The gNB transmits one or more types of RS, including Channel State Information RS (CSI-RS) and Demodulated RS (DMRS). CSI-RS is primarily used by the UE to perform measurements and provide CSI to the gNB. For channel measurements, the Non-Zero Power CSI-RS (NZP CSI-RS) resource is used. For Interference Measurement Reporting (IMR), the CSI Interference Measurement (CSI-IM) resource associated with the Zero Power CSI-RS (ZP CSI-RS) configuration is used. The CSI process includes both NZP CSI-RS and CSI-IM resources.

[0065] The UE can determine the CSI-RS transmission parameters via DL control signaling or higher-level signaling (such as Radio Resource Control (RRC) signaling) from the gNB. The transmission instance of CSI-RS can be indicated by DL control signaling or configured by higher-level signaling. DMRS is only transmitted in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0066] Figure 4 and Figure 5 Example wireless transmit and receive paths according to this disclosure are shown. In the following description, transmit path 400 may be described as being implemented in a gNB (such as gNB 102), and receive path 500 may be described as being implemented in a UE (such as UE 116). However, it is understood that receive path 500 may be implemented in a gNB and transmit path 400 may be implemented in a UE. It is also understood that, in order to support SL communication, receive path 500 may be implemented in a first UE and transmit path 400 may be implemented in a second UE. In some embodiments, receive path 500 is configured to support sidelink measurements in V2X communication as described in embodiments of this disclosure.

[0067] like Figure 4The transmission path 400 shown includes a channel coding and modulation block 405, a serial-to-parallel (S-TO-P) block 410, an N-size inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial (P-TO-S) block 420, a cyclic prefix addition block 425, and an up-converter (UC) 430. For example... Figure 5 The receiver path 500 shown includes a downconverter (DC) 555, a cyclic prefix removal block 560, a serial-to-parallel (S-TO-P) block 565, a fast Fourier transform (FFT) block of size N, a parallel-to-serial (P-TO-S) block 575, and a channel decoding and demodulation block 580.

[0068] As shown in Figure 400, the channel coding and modulation block 405 receives a set of information bits, applies coding (such as low-density parity-check (LDPC) coding), and modulates the input bits (e.g., using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to generate a sequence of frequency domain modulation symbols.

[0069] Serial-to-parallel block 410 converts (e.g., demultiplexes) serial modulated symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. IFFT block 415 of size N performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial block 420 converts (e.g., multiplexes) the parallel time-domain output symbols from IFFT block 415 of size N to generate a serial time-domain signal. Cyclic prefix addition block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (e.g., upconverts) the output of cyclic prefix addition block 425 to an RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to the RF frequency.

[0070] The RF signal transmitted from gNB 102 reaches UE 116 after passing through the wireless channel, and UE 116 performs the opposite operation to that at gNB 102.

[0071] like Figure 5 As shown, downconverter 555 downconverts the received signal to the baseband frequency, and cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel block 565 converts the time-domain baseband signal into a parallel time-domain signal. FFT block 570 of size N performs the FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial block 575 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.

[0072] Each of gNB 101-103 can achieve the following: Figure 4 The diagram shows a transmission path 400 similar to that sent to UE 111-116 in the downlink, and it can achieve the following: Figure 5 The diagram illustrates a receive path 500, which is similar to the one received from UEs 111-116 in the uplink. Similarly, each of UEs 111-116 can implement a transmit path 400 for transmitting to gNBs 101-103 in the uplink and / or to another UE in the sidelink, and can implement a receive path 500 for receiving from gNBs 101-103 in the downlink and / or from another UE in the sidelink.

[0073] Figure 4 and Figure 5 Each component can be implemented using only hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some components can be implemented in software; however, other components can be implemented in configurable hardware or a hybrid of software and configurable hardware. For example, FFT block 570 and IFFT block 515 can be implemented as configurable software algorithms, where the value of size N can be modified depending on the implementation.

[0074] Furthermore, although described as using FFT and IFFT, this is for illustrative purposes only and should not be construed as limiting the scope of this disclosure. Other types of transforms may be used, such as the Discrete Fourier Transform (DFT) and Inverse Discrete Fourier Transform (IDFT) functions. It will be understood that for the DFT and IDFT functions, the value of variable N can be any integer (e.g., 1, 2, 3, 4, etc.), while for the FFT and IFFT functions, the value of variable N can be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0075] although Figure 4 and Figure 5 Examples of wireless transmit and receive paths are shown, but more can be found on other devices. Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5 The various components can be combined, further subdivided, or omitted, and additional components can be added as needed. Furthermore, Figure 4 and Figure 5 This is intended to illustrate examples of the types of transmit and receive paths that can be used in a wireless network. Any other suitable architecture can be used to support wireless communication in a wireless network.

[0076] In the 3GPP wireless standards, NR has been discussed as a 5G wireless communication technology. One of the features of NR under discussion is V2X.

[0077] Figure 6 An example V2X communication on a side link 600 according to an embodiment of the present disclosure is shown. Figure 6 The example of V2X communication on side link 600 shown is for illustrative purposes only.

[0078] Figure 6 This illustrates an example scenario of vehicle-to-vehicle communication. Two or more vehicles can send and receive data / control signals over a direct link / interface between them. In 3GPP, a direct link / interface between vehicles or between a vehicle and other objects is called a side link (SL). Note that... Figure 6 The description covers a scenario where vehicles can still communicate with the gNB to obtain SL resources, SL radio bearer configurations, etc. However, it is equally possible that vehicles can still communicate with each other on the SL even without interacting with the gNB. In this case, SL resources, SL radio bearer configurations, etc., are pre-configured (e.g., via a V2X server or any other core network entity).

[0079] To provide further details, V2X scenarios and research are introduced in the 3GPP standard specification. One of the main differences compared to UL (e.g., the link from the UE to the gNB) is the transmission resource allocation mechanism. In UL, transmission resources are allocated by the gNB; however, in SL, the UE selects resources itself from an SL resource pool configured by the gNB. If multiple SL resource pools are configured, the UE selects based on its channel sensing results and the number of resources required for data / control transmissions. The details of SL resource selection are specified in the 3GPP standard specification.

[0080] In 3GPP Release 16, basic SL communication functions are supported. For Release 17, more enhancements are planned to be introduced into SL. One feature of Release 17 is the introduction of an enhanced SL resource allocation mechanism that considers the SL channel sensing results of other UEs in addition to the SL channel sensing of the TX UE (the UE intending to transmit data / control on SL). One or more other UEs can inform the TX UE of their preferred and / or non-preferred resource information sets derived from their channel sensing via control messages called inter-UE coordination information. This embodiment provides an efficient resource allocation mechanism based on inter-UE coordination.

[0081] Figure 7 A signaling flow 700 for enhancing SL resource allocation according to an embodiment of this disclosure is illustrated. For example, it can be provided by a UE (e.g., such as...). Figure 1 (as shown in 111-116) and (one or more) other UEs (e.g., such as Figure 1 The signaling flow 700 executed by 111A-111C shown is shown. Figure 7 The example of signaling flow 700 shown is for illustrative purposes only.

[0082] like Figure 7 As shown, SL UE#1 701 intends to transmit data / control on SL, and SL UE#2 703 can provide inter-UE coordination information. SL UE#2 703 can be the receiving UE of the data / control to be transmitted by SL UE#1 or any other UE that can provide inter-UE coordination information. In steps 711 and 713, SL UE#1 and SL UE#2 perform SL channel sensing on resources within the selected resource pool for transmission. UE#2 can perform step 713 after receiving the inter-UE coordination REQ 721a.

[0083] Note that from UE#2's perspective, although UE#2 has no data / control to transmit, UE#2 still performs SL channel sensing to provide inter-UE coordination information. Furthermore, note that once SL UE#1 is configured to transmit data / control, step 711 can continue to execute in the background, and once UE#2 is configured to provide inter-UE coordination information, step 713 can continue to execute in the background. In step 721a, SL UE#1 sends an inter-UE coordination request (REQ). SL UE#1 can send the inter-UE coordination REQ using any SL broadcast type (SL unicast, SL multicast, or SL broadcast).

[0084] The UE-to-UE coordination REQ may include or a portion of the following information: (i) a list of {preferred resource sets and corresponding resource pool IDs}; (ii) SL UE#1 location information (e.g., the location area ID of SL UE#1) and transmission range information; (iii) the SL broadcast type and target UE ID that provide the UE-to-UE coordination information; and (iv) resource filtering indication.

[0085] The corresponding resource pool ID indicates the selected resource pool used for transmissions by SL UE#1. The preferred resource set represents the preferred resource information for SL UE#1, which may include, for example, the preferred SL channel index / number within the corresponding resource pool or an indication of whether an SL channel is preferred or non-preferred for each SL channel within the corresponding resource pool. Preferred resources (one or more) can be determined based on channel sensing of SL UE#1; for example, if the channel sensing result indicates that the measured channel busy rate of a resource is below a threshold, then this resource can be determined as a preferred resource for transmission. For this determination, the threshold and / or hysteresis parameters used to compare the measured channel busy rate can also be configured by the gNB or pre-configured, but in Figure 7 This is not explained in the text.

[0086] In one example, the entry condition for setting a resource as the preferred resource is provided by the following formula: Ms + Hys < Thresh.

[0087] In one example, the leave condition for not setting a resource as the preferred resource is provided by the following formula: Ms-Hys > Thresh.

[0088] The variables in the formula are defined as follows: (i) Ms is a measurement of the channel busy rate of the resources in the transmission resource pool; (ii) Hys is the hysteresis parameter used for this determination; and (iii) Thresh is the threshold parameter used for this determination.

[0089] If multiple resources meet the example conditions described above, then SL UE#1 can include multiple preferred resources. To limit the number of preferred resources, the maximum number of preferred resource information to be included in the inter-UE coordinated REQ can also be configured or pre-configured by the gNB. Figure 7 This is not explained in the text.

[0090] Note that if multiple resource pools are (pre)configured for transmission, SL UE#1 can include multiple preferred resources from multiple resource pools for transmission. To limit the number of lists of {preferred resource sets and corresponding resource pool IDs}, the maximum number of lists to be included in the inter-UE coordinated REQ can also be configured or pre-configured by the gNB. Figure 7 This is not explained in the text.

[0091] The location information for SL UE#1 indicates the location of SL UE#1. For example, it may include detailed GPS location information. Alternatively, to reduce the overhead of detailed GPS location information, it may include the location area ID of SL UE#1 instead of the detailed GPS location information. The location area ID of SL UE#1 can be determined based on which area the actual location of SL UE#1, derived from GPS, belongs to.

[0092] Zone information (e.g., how the entire world is divided into zones) can be configured by the gNB or pre-configured. For example, the following zone ID calculation, introduced in Release 16SL for the SL multicast-specific Hybrid Automatic Repeat Request (HARQ) feedback mechanism, can be reused for UE location information in inter-UE coordination information. The sl-ZoneConfig, including sl-ZoneLength (in meters), is configured by the gNB (via system information or a UE-specific RRC connection reconfiguration message) or pre-configured.

[0093] If sl-ZoneConfig is configured, the UE can use the following formula, as shown in Table 1, to determine the identity of the zone in which the UE is located (i.e., Zone_id).

[0094] Table 1. Formula

[0095]

[0096] For the formulas shown in Table 1, the parameters in the formulas are defined as follows: (i) L is the value of sl-ZoneLength included in sl-ZoneConfig; (ii) x is the longitude geodesic distance between the current location of the UE and the geographic coordinates (0,0) according to the 3GPP standard specification, and x is expressed in meters; and (iii) y is the latitude geodesic distance between the current location of the UE and the geographic coordinates (0,0) according to the 3GPP standard specification, and y is expressed in meters.

[0097] Transmission range information (or communication range information) indicates the required transmission range for the SL data / control to be transmitted. This information is provided by the upper layer with the required Quality of Service (QoS) information for the SL data / control to be transmitted, or it can be configured by the gNB (via system information or UE-dedicated RRC connection reconfiguration messages) with the corresponding SL PQI (PC5 5G QoS identifier) ​​or pre-configured with the corresponding SL PQI. This information can be associated with the destination Layer 2 (L2) ID or logical channel ID. If (pre-)configured, this information represents the distance in meters. Note that if the SL data / control arrives from different SL logical channels (or different SL applications), the SL data / control may have different required transmission ranges.

[0098] The broadcast type information indicates whether the broadcast type is for SL unicast (one-to-one communication), SL multicast (one-to-M communication where M belongs to the same group as the transmitting UE), or SL broadcast (one-to-all communication). The target UE ID represents the L1 / L2 ID of (one or more) destination / receiving UEs. The L1 ID is the ID used for the L1 (or physical) control channel, and the L2 ID is the ID used in the Multiple Access Control (MAC) header. The L1 ID can be a part of the L2 ID. In SL unicast, the target UE ID can represent a specific destination / receiving UE; in SL multicast, the target UE ID can represent a group ID or a specific service ID; and in SL broadcast, it can represent all SL UEs. The broadcast type and / or target UE ID information can be set based on the broadcast type and / or target UE ID of the data / control to be transmitted, or they can be set independently to select only the target UEs that can provide inter-UE coordination information regardless of the actual destination / receiving UEs of the data / control to be transmitted.

[0099] The resource filtering indication specifies under what circumstances SL UE#2 can send the corresponding inter-UE coordination information. For example, it may include the following information.

[0100] In one example, indication A is included. Indication A indicates that SL UE#2 may send the corresponding inter-UE coordination information only if SL UE#2 has different information for the preferred resource set received in step 721a. For example, if SL UE#2 has a "non-preferred resource" for any "preferred resource" received in step 721a, then SL UE#2 will not send the corresponding inter-UE coordination information.

[0101] In one example, Instruction B is included. Instruction B indicates that when SL UE#2 has any information for the preferred resource set received in step 721a, SL UE#2 may send the corresponding inter-UE coordination information. It is not important whether it is the same information as the received information.

[0102] In one example, instruction C is included. Instruction C indicates that when SL UE#2 has any information (without any restrictions related to the preferred resource set received in step 721a), SL UE#2 can send the corresponding inter-UE coordination information.

[0103] Once SL UE#1 sends a signal in step 721a, SL UE#1 starts timer T#1. T#1 is used to wait for the corresponding inter-UE coordination information. If the inter-UE coordination information is received before T#1 expires, SL UE#1 can consider the information included in the inter-UE coordination information in the final resource selection in step 743; otherwise, SL UE#1 can only consider its own information in the final resource selection in step 743.

[0104] Once SL UE#2 receives the inter-UE coordination REQ in step 721a, it determines in step 721b whether SL UE#2 can send the corresponding inter-UE coordination information. This can be determined based on the calculated distance between SL UE#1 and SL UE#2 and the received transmission / communication range information. The distance between SL UE#1 and SL UE#2 can be calculated based on the location of SL UE#2 obtained from GPS / GNSS (or the location area ID of SL UE#2, which can be calculated in the same way as SL UE#1) and the location of SL UE#1 (or the location area ID of SL UE#1) received in step 721a. For example, SL UE#2 determines to send the corresponding inter-UE coordination information if the following conditions are met. Otherwise, SL UE#2 determines not to send the corresponding inter-UE coordination information.

[0105] In one example of condition #1a, the calculated distance between SL UE#2 and SL UE#1 is (equal to or) greater than distance-threshold#1 and / or the calculated distance is (equal to or) less than the received transmission range. Distance-threshold#1 (in meters) can be signaled in step 721a, or distance-threshold#1 can be configured or pre-configured by the gNB (via system information or a UE-specific RRC connection reconfiguration message).

[0106] In one example of condition #1b, the calculated distance between SL UE#2 and SL UE#1 is (equal to or) greater than {received transmission range minus Distance-offset#1} and / or the calculated distance is (equal to or) less than the received transmission range. Distance-offset#1 (in meters) can be signaled in step 721a, or it can be configured or pre-configured by the gNB (via system information or a UE-specific RRC connection reconfiguration message). Note that Distance-offset can also be signaled or (pre-)configured as a percentage. If Distance-offset is determined as a percentage, then "{received transmission range minus Distance-offset#1}" above can be replaced with {received transmission range multiplied by the represented percentage} or {received transmission range minus (received transmission range multiplied by the represented percentage)}.

[0107] In one example of condition 2, if the ID of SL UE#2 matches the received target UE ID under the corresponding broadcast type. For example, if the received broadcast type is SL unicast and the received target UE ID matches the source ID of SL UE#2 for SL unicast, or if the received broadcast type is SL multicast and the received target UE ID matches the group ID or service ID to which SL UE#2 belongs for SL multicast, or if the received broadcast type is SL broadcast and / or the received target UE ID matches a code point (value) reserved for SL broadcast. Note that the broadcast type information can be omitted in step 721a, and in this case, the UE determines the condition based solely on the target UE ID information.

[0108] In one example of condition 3, if SL UE#2 has inter-UE coordination information that can satisfy the resource preference indication. For example, if indication A is received and SL UE#2 has different information for the received preferred resource set (e.g., SL UE#2 has "non-preferred" information for the preferred resource received in step 721a).

[0109] Notice, Figure 7 Step 721b is described based on the assumption of having Example #1a or Example #1b, but other examples may also be used in the determination process. In addition, a combination of multiple examples may be used (e.g., if Example 1a / 1b and Example 2 are satisfied, or if Example 1a / 1b and Example 3 are satisfied, or if Example 1a / 1b and Example 2 and Example 3 are satisfied, then SL UE#2 determines to send the corresponding inter-UE coordination information).

[0110] In step 731, SL UE#2 sends inter-UE coordination information based on the channel sensing results of SL UE#2. Note that, although Figure 7 (Using steps 721a and 721b) it is shown that the inter-UE coordination information of SL UE#2 is sent as a response to the inter-UE coordination REQ from SL UE#1, but SL UE#2 may also send the inter-UE coordination information as a separate message (without receiving the inter-UE coordination REQ). In this case, steps 721a and 721b are skipped. This means that steps 721a and 721b are only needed if the transmission of the inter-UE coordination information of SL UE#2 is triggered by the inter-UE coordination REQ. The inter-UE coordination information includes the following information: (i) a list of {preferred and / or non-preferred resource sets and corresponding resource pool IDs}; and (ii) the location information of SL UE#2 (e.g., the location area ID of SL UE#2).

[0111] The corresponding resource pool ID represents the index of the resource pool to which the preferred and / or non-preferred resource sets belong. The preferred and / or non-preferred resource sets represent the recommended preferred and / or non-preferred resource information for SL UE#2. For example, it may include the preferred or non-preferred SL channel index / number within the corresponding resource pool or an indication of whether an SL channel is preferred or non-preferred for each SL channel within the corresponding resource pool.

[0112] Preferred resources (one or more) can be determined based on channel sensing of SL UE#2. For example, if the measured channel busy rate of a resource as a result of channel sensing is below a threshold, this resource can be determined as a preferred resource for transmission. For this determination, the threshold and / or hysteresis parameter used to compare the measured channel busy rates can also be configured by the gNB or pre-configured, but in Figure 7Not specified. See the following example of a deterministic expression.

[0113] In one example, the entry condition for setting a resource as the preferred resource is given by the following formula: Ms + Hys < Thresh.

[0114] In one example, the departure condition for not setting a resource as the preferred resource is given by the following formula: Ms-Hys > Thresh.

[0115] In this example, the variables in the formula are defined as follows: (i) Ms is a measurement of the channel busy rate of the resources in the transmission resource pool; (ii) Hys is the hysteresis parameter used for this determination; and (iii) Thresh is the threshold parameter used for this determination.

[0116] Alternatively, one or more non-preferred resources can be determined based on channel sensing of SL UE#2. For example, if the measured channel busy rate of a resource does not meet the above-mentioned entry conditions for preferred resources, the resource can be determined as a non-preferred resource. As an alternative, separate additional conditions can be defined for non-preferred resources. For example: (i) the entry condition for setting a resource as a non-preferred resource is given by: Ms + Hys#2 > Thresh#2; and (ii) the exit condition for setting a resource as a non-preferred resource is given by: Ms - Hys#2 <Thresh#2。

[0117] The variables in the formulas mentioned above are defined as follows: (i) Ms is a measurement of the channel busy rate of the resources within the transmission resource pool; (ii) Hys#2 is the hysteresis parameter used for this determination; and (iii) Thresh#2 is the threshold parameter used for this determination. Note that if the same values ​​are used, Hys#2 and / or Thresh#2 can be replaced with Hys and Thresh in the preferred resource determination conditions.

[0118] Note that if the inter-UE coordination information is sent as a response in step 721a, the resource information to be included in step 731 may only have information corresponding to the resource information included in step 721a.

[0119] The location information for SL UE#2 indicates the location of SL UE#2. For example, it may include detailed GPS location information. Alternatively, to reduce the overhead of detailed GPS location information, it may include the location area ID of SL UE#2 instead of the detailed GPS location information. The location area ID of SL UE#2 can be determined based on which area the actual location of SL UE#2, derived from GPS, belongs to.

[0120] Zone information (e.g., how the world is divided into different zones) can be configured by the gNB or pre-configured. For example, the following zone ID calculation, introduced in 3GPP Release 16SL for the SL multicast-specific HARQ feedback mechanism, can be reused for UE location information in inter-UE coordination information. The sl-ZoneConfig, including sl-ZoneLength (in meters), is configured by the gNB (via system information or a UE-specific RRC connection reconfiguration message) or pre-configured.

[0121] If sl-ZoneConfig is configured, the UE can use the following formula, as shown in Table 2, to determine the identity of the zone in which the UE is located (i.e., Zone_id).

[0122] Table 2. Formula

[0123]

[0124] The parameters in the formulas shown in Table 2 are defined as follows: (i) L is the value of sl-ZoneLength included in sl-ZoneConfig; (ii) x is the longitude geodesic distance between the current location of the UE and the geographic coordinates (0,0) according to the 3GPP standard specification, and x is expressed in meters; and (iii) y is the latitude geodesic distance between the current location of the UE and the geographic coordinates (0,0) according to the 3GPP standard specification, and y is expressed in meters.

[0125] When SL UE#1 (in step 731) receives inter-UE coordination information before T#1 expires, SL UE#1 (in step 741) determines whether it can consider this inter-UE coordination information valid. This can be determined based on the calculated distance between SL UE#1 and SL UE#2 and the transmission / communication range information of the data / control to be sent by SL UE#1. The distance between SL UE#1 and SL UE#2 can be calculated based on the location of SL UE#1 obtained from GPS / GNSS (or the location area ID of SL UE#1, which has been explained above) and the location of SL UE#2 (or the location area ID of SL UE#2) received in step 731.

[0126] For example, if the calculated distance between SL UE#1 and SL UE#2 is (equal to or less than) the SL transmission / communication range for the data / control to be sent, then SL UE#1 considers the inter-UE coordination information valid. Otherwise, SL UE#1 considers the inter-UE coordination information invalid.

[0127] In another example, if the calculated distance between SL UE#1 and SL UE#2 is greater than (equal to or equal to) distance-threshold#2 and / or the calculated distance is less than the SL transmission / communication range for the data / control to be sent, then SL UE#1 may consider the inter-UE coordination information valid. Otherwise, SL UE#1 considers the inter-UE coordination information invalid.

[0128] Distance-threshold#2 can be configured by the gNB (via system information or a UE-dedicated RRC connection reconfiguration) or preconfigured. SL transmission / communication range information indicates the required transmission range for the SL data / control to be transmitted. This information is provided by the upper layer along with the required QoS information for the SL data / control to be transmitted, or it can be configured by the gNB (via system information or a UE-dedicated RRC connection reconfiguration message) with the corresponding SL PQI (PC5 5G QoS Identifier) ​​or preconfigured with the corresponding SL PQI. This information can be associated with the destination Layer 2 (L2) ID or logical channel ID. If (pre)configured, this information represents meters. Note that if the SL data / control arrives from different SL logical channels (or different SL applications), the SL data / control can have different required transmission ranges.

[0129] like Figure 7 As shown, in step 743, SL UE#1 performs the final resource selection for data / control transmission, taking into account its own channel sensing results in step 711 or 721a and the valid received inter-UE coordination information from SL UE#2. For example, SL UE#1 may exclude resources represented by the inter-UE coordination information as non-preferred, or SL UE#1 may select one of the resources represented by the inter-UE coordination information as preferred.

[0130] Note that if SL UE#1 does not receive any valid inter-UE coordination information before timer T#1 expires, SL UE#1 performs final resource selection for data / control transmission solely based on its own channel sensing results. In this case, once timer T#1 expires, SL UE#1 will not attempt to receive further inter-UE coordination information. Once one or more final resources are selected in step 743, SL UE#1 transmits data / control on the selected resources in step 745.

[0131] Note that, although it is assumed that Figure 7The transmission / communication range information is included in step 721a or step 731, but the UE can derive it even without including the transmission / communication range information in step 721a or step 731. As mentioned above, the transmission / communication range information is provided by the upper layer as part of the required QoS information. Therefore, the UE can simply derive the transmission / communication range information from the QoS information associated with the destination L2 ID or logical channel.

[0132] Figure 8 An example of full-channel sensing and resource selection 800 according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of the full-channel sensing and resource selection 800 shown is for illustrative purposes only.

[0133] Basic SL communication functions are supported in 3GPP Release 16. For Release 17, more enhancements are planned to be introduced to SL. One of the features of Release 17 is the introduction of an enhanced SL resource allocation mechanism by taking power saving into account. Figure 8 The 3GPP Release 16 full-channel sensing operation for the UE autonomous resource selection process is shown.

[0134] like Figure 8 As shown, it can be assumed that at time N, the UE triggers resource selection for data / control transmissions arriving from the upper layer. The UE continuously performs channel sensing operations to identify unoccupied channels for possible data / control transmissions. If resource selection for data / control transmissions is triggered at time N, the UE uses the result of the channel sensing operations performed between time N-T3 and time N-T4 to select / reserve unoccupied resources / channels. If the UE identifies an unoccupied resource / channel as a result of the channel sensing operations between time N-T3 and time N-T4, that resource / channel can be selected / reserved in the time domain for data / control transmissions between time N+T1 and time N+T2. Note that in 3GPP Release 16, the UE performs channel sensing continuously between time N-T3 and time N-T4.

[0135] Figure 9A An example portion of channel sensing and resource selection according to an embodiment of this disclosure is shown. Figure 9A The partial embodiment of channel sensing and resource selection 900 shown is for illustrative purposes only.

[0136] Figure 9B Another example portion of channel sensing and resource selection 950 according to an embodiment of this disclosure is shown. Figure 9B The partial embodiment of channel sensing and resource selection 950 shown is for illustrative purposes only.

[0137] Figure 9A and Figure 9BThis illustrates a portion of the channel sensing operation in the UE autonomous resource selection process, which has been reconsidered for UE power saving in 3GPP Release 17. Figure 9A and Figure 8 The operation described in the text is similar. Figure 9A The main difference is that the UE actually performs channel sensing operations discontinuously during the channel sensing window between time N-T3 and time N-T4, so it is different from... Figure 8 Compared to continuous channel sensing, the UE can have power saving gains.

[0138] like Figure 9A As shown, it can be assumed that at time N, the UE triggers resource selection for data / control transmissions arriving from the upper layer. The UE uses the result of channel sensing operations performed discontinuously in the time domain between time N-T3 and time N-T4 to identify unoccupied resources / channels for its data / control transmissions. If the UE identifies an unoccupied resource / channel as a result of partial channel sensing operations between time N-3 and time N-4, then that resource / channel can be selected / reserved in the time domain for data / control transmissions between time N+T1 and time N+T2. Figure 9B In this scenario, it can be assumed that the UE triggers resource selection for data / control transmissions arriving from the upper layer at time N. In this case, once resource selection is triggered at time N, the UE begins channel sensing operations between time N+Ta and time N+Tb.

[0139] The UE performs continuous channel sensing operations between time N+Ta and time N+Tb to identify unoccupied resources / channels; however, the duration between N+Ta and N+Tb is longer than... Figure 8 The channel sensing window described (between N-T3 and N-T4) is short. By utilizing shorter consecutive channel sensing operations after resource selection is triggered, the UE can achieve power saving gains and, moreover, meet the required latency budget. If, as a result of partial channel sensing operations between time N+Ta and time N+Tb, the UE identifies an unoccupied resource / channel, that resource / channel can be selected / reserved in the time domain between time N+T1 and time N+T2 for data / control transmissions.

[0140] Notice, Figure 8 , Figure 9A and Figure 9B The UE behavior described herein refers to a UE performing resource selection / reservation for data / control transmissions. For partial channel sensing operations, as mentioned above, two modes are considered (one in...) Figure 9A As described in the text, while another one is in Figure 9B(As described in the text). If two partial channel sensing operations coexist, the performance of partial channel sensing may be degraded because the duration of partial channel sensing differs for each mode in the time domain. Mechanisms may exist to avoid the aforementioned problems.

[0141] Figure 10 A partial signaling flow 1000 for channel sensing and resource selection according to an embodiment of this disclosure is shown. For example, it can be generated by a UE (e.g., such as...). Figure 1 (as shown in 111-116) and base stations (e.g., such as Figure 1 Signaling flow 1000 is executed as shown in 101-103. Figure 10 The example of signaling flow 1000 shown is for illustrative purposes only.

[0142] Figure 10 An example of this embodiment is shown. SL UE (e.g., as Figure 10 In step 1001, data / control transmissions are performed. The UE can be referred to as an SL TX UE. In step 1003, a gNB or another network entity (e.g., the network entity responsible for SL pre-configuration) is shown. In step 1003, (in step 1011) all necessary radio resources and bearer parameters / information for SL communication are configured or pre-configured. This configuration can be signaled via a System Information Block (SIB) or a UE-specific RRC message (e.g., an RRC connection reconfiguration message) or pre-configuration.

[0143] The configuration includes a list of TX resource pools (i.e., resource pools that can be used to select resources for transmitting data / control) and an indicator of the allowed partial channel sensing mode for each TX resource pool. Once the SL TX UE receives the configuration in step 1011, the SL TX UE selects a partial channel sensing mode for data / control transmission in step 1021. For example, for periodic data patterns, the UE can select... Figure 9A The partial channel sensing mode described herein. This partial channel sensing mode can be partial channel sensing mode 1. Furthermore, for aperiodic data patterns, the UE can select... Figure 9B The partial channel sensing mode described herein. This partial channel sensing mode may be partial channel sensing mode 2.

[0144] Once the SL TX UE selects a partial channel sensing mode in step 1021, the SL TX UE (in step 1031) selects a TX resource pool where the indicator for the selected partial channel sensing mode is set to "true". "True" means that the selected partial channel sensing mode is allowed for use in that TX resource pool. For example, if the UE selects partial channel sensing mode 1 in step 1021, the UE selects a TX resource pool where the indicator for partial channel sensing mode 1 is set to "true". If the UE selects partial channel sensing mode 2 in step 1021, the UE selects a TX resource pool where the indicator for partial channel sensing mode 2 is set to "true". Once the UE selects a TX resource pool in step 1031, the UE selects the actual resources for data / control transmission within the selected TX resource pool based on the selected partial channel sensing mode (in step 1041). Figure 9A or Figure 9B This is described in the text.

[0145] Figure 11 A flowchart of a method 1100 for enhancing resource allocation according to an embodiment of the present disclosure is shown. For example, it can be performed by a UE (e.g., such as...) Figure 1 Method 1100 is executed as shown in 111-116). Figure 11 The embodiments of method 1100 shown are for illustrative purposes only. Figure 11 One or more components shown may be implemented in a dedicated circuit configured to perform the indicated function, or one or more components may be implemented by one or more processors that execute instructions to perform the indicated function.

[0146] like Figure 11 As shown, method 1100 begins at step 1102. In step 1102, the first UE receives inter-UE coordination information from the second UE, including SL resources and area IDs. The inter-UE coordination information is used for resource allocation for the transmission of SL data. In step 1102, the inter-UE coordination information further includes at least one of the following: a preferred resource set, a non-preferred resource set, and resource pool ID sets corresponding to the preferred and non-preferred resource sets, respectively.

[0147] Subsequently, in step 1104, the first UE identifies the transmission range of the SL data transmission.

[0148] Subsequently, in step 1106, the first UE calculates the distance between the second UE and the first UE based on the area ID.

[0149] Subsequently, in step 1108, the first UE determines whether the inter-UE coordination information is valid based on the transmission range and distance.

[0150] Next, in step 1110, the first UE identifies the SL resource based on the determination that the inter-UE coordination information is valid.

[0151] Finally, in step 1112, the first UE sends SL data.

[0152] In one embodiment, the first UE determines the transmission range based on the Layer 2 multicast destination ID and the QoS information corresponding to the Layer 2 multicast destination ID, wherein the inter-UE coordination information also includes the transmission range.

[0153] In one embodiment, when the distance is greater than the transmission range, the first UE determines that the inter-UE coordination information is invalid, while when the distance is less than or equal to the transmission range, the first UE determines that the inter-UE coordination information is valid.

[0154] In one embodiment, the first UE calculates its area ID based on its current location and geographic coordinates, and calculates the distance based on the area ID and the area ID received from the second UE.

[0155] In one embodiment, the first UE sends an inter-UE coordination information request including the area ID to the second UE, and receives inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE.

[0156] In one embodiment, the first UE sends an inter-UE coordination information request, which also includes a transmission range, to the second UE, and receives inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE. In this embodiment, the inter-UE coordination information request also includes a preferred resource set, a non-preferred resource set, or a resource pool ID set corresponding to the preferred resource set.

[0157] The flowcharts above illustrate example methods that can be implemented according to the principles of this disclosure, and various modifications can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the various steps in each diagram can overlap, occur in parallel, occur in different orders, or occur multiple times. In another example, steps can be omitted or replaced with other steps.

[0158] Although this disclosure has been described with reference to exemplary embodiments, various changes and modifications may be suggested to those skilled in the art. This disclosure is intended to include such changes and modifications as fall within the scope of the appended claims. The descriptions in this application should not be construed as implying that any particular element, step, or function is essential and must be included within the scope of the claims. The scope of the patent subject matter is defined by the claims.

Claims

1. A first user equipment (UE) in a wireless communication system, the first UE comprising: A transceiver configured to receive inter-UE coordination information from a second UE, including sidelink SL resources and a district identifier ID, the inter-UE coordination information being used for resource allocation for SL data transmission; and A processor, operatively connected to the transceiver, is configured to: Identify the transmission range of the SL data; Based on the area ID, the distance between the second UE and the first UE is calculated; When the distance is greater than the transmission range, the inter-UE coordination information is determined to be invalid; when the distance is less than or equal to the transmission range, the inter-UE coordination information is determined to be valid. Based on the confirmation that the inter-UE coordination information is valid, the SL resource is verified. The transceiver is further configured to transmit the SL data.

2. The first UE according to claim 1, wherein: The inter-UE coordination information also includes the transmission range; and The processor is further configured to identify the transmission range based on the Layer 2 multicast destination ID and the Quality of Service (QoS) information corresponding to the Layer 2 multicast destination ID.

3. The first UE of claim 1, wherein, The processor is further configured to: Based on the geographic coordinates and the current location of the first UE, the region ID of the first UE is calculated; and The distance is calculated based on the area ID of the first UE and the area ID received from the second UE, and The UE-to-UE coordination information further includes at least one of the following: a preferred resource set, a non-preferred resource set, and a set of resource pool IDs corresponding to the preferred resource set and the non-preferred resource set, respectively.

4. The first UE of claim 1, wherein, The transceiver is further configured to: Send a UE coordination information request, including the area ID, to the second UE; and Receive the inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE, and in: The transceiver is further configured to: Send a request for inter-UE coordination information, including transmission range, to the second UE, and Receive inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE; and The UE-to-UE coordination information request further includes a preferred resource set, a non-preferred resource set, or a resource pool ID set corresponding to the preferred resource set.

5. A method for a first user equipment (UE) in a wireless communication system, the method comprising: The second UE receives inter-UE coordination information including sidelink SL resources and area identifier ID, which is used for resource allocation for the transmission of SL data; Identify the transmission range of the SL data; Based on the area ID, the distance between the second UE and the first UE is calculated; When the distance is greater than the transmission range, the inter-UE coordination information is determined to be invalid; when the distance is less than or equal to the transmission range, the inter-UE coordination information is determined to be valid. Based on the determination that the inter-UE coordination information is valid, the SL resource is confirmed; and Send the SL data.

6. The method according to claim 5, wherein the method further comprises: The transmission range is identified based on the Layer 2 multicast destination ID and the Quality of Service (QoS) information corresponding to the Layer 2 multicast destination ID, wherein the inter-UE coordination information also includes the transmission range.

7. The method according to claim 5, wherein the method further comprises: Based on the geographic coordinates and the current location of the first UE, the area ID of the first UE is calculated; as well as The distance is calculated based on the area ID of the first UE and the area ID received from the second UE, and The UE-to-UE coordination information further includes at least one of the following: a preferred resource set, a non-preferred resource set, and a set of resource pool IDs corresponding to the preferred resource set and the non-preferred resource set, respectively.

8. The method according to claim 5, wherein the method further comprises: Send a UE coordination information request, including the area ID, to the second UE; as well as Receive inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE, or Send a request for inter-UE coordination information, including the transmission range, to the second UE; and Receive inter-UE coordination information corresponding to the inter-UE coordination information request from the second UE. The UE-to-UE coordination information request also includes a preferred resource set, a non-preferred resource set, or a resource pool ID set corresponding to the preferred resource set.

9. A second user equipment (UE) in a wireless communication system, the second UE comprising: A processor configured to generate inter-UE coordination information including sidelink SL resources and area identifier IDs; as well as A transceiver, operatively connected to the processor, is configured to: The inter-UE coordination information is sent to the first UE. This inter-UE coordination information is used for resource allocation for the transmission of SL data. Receive the SL data from the first UE in: Regarding the transmission of the SL data, the transmission range has been identified. The distance between the second UE and the first UE is calculated based on the area ID. When the distance is greater than the transmission range, the inter-UE coordination information is determined to be invalid, and when the distance is less than or equal to the transmission range, the inter-UE coordination information is determined to be valid. and SL resources are confirmed based on the determination that the inter-UE coordination information is valid.

10. The second UE according to claim 9, wherein: The inter-UE coordination information also includes the transmission range; and The transmission range is identified based on the Layer 2 multicast destination ID and the Quality of Service (QoS) information corresponding to the Layer 2 multicast destination ID.

11. The second UE according to claim 9, wherein, The transceiver is further configured to: Receive an inter-UE coordination information request including the area ID from the first UE; and Send the inter-UE coordination information corresponding to the inter-UE coordination information request to the first UE, and in: The UE coordination information also includes at least one of the following: a preferred resource set, a non-preferred resource set, and a set of resource pool IDs corresponding to the preferred resource set and the non-preferred resource set, respectively. The region ID of the first UE is calculated based on geographical coordinates and the current location of the first UE; and The distance is calculated based on the area ID of the first UE and the area ID received from the second UE.

12. The second UE according to claim 9, wherein: The transceiver is further configured to: The first UE receives a request for inter-UE coordination information, which also includes the transmission range. Send the inter-UE coordination information corresponding to the inter-UE coordination information request to the first UE; and The UE-to-UE coordination information request also includes a preferred resource set, a non-preferred resource set, or a resource pool ID set corresponding to the preferred resource set.

Images