Sidelink request / authorization protocol for wireless networks

By executing the clear request/authorization handshake protocol in the wireless communication system, the frame conflict problem caused by side link communication in the unlicensed frequency band is solved, and the system performance is improved.

CN119096677APending Publication Date: 2024-12-06LENOVO (SINGAPORE) PTE LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036564.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-26
Filing Date
2023-04-26
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In wireless communication systems, side link communications in unlicensed frequency bands may result in increased probability of frame collisions, resulting in reduced performance, especially due to open nodes and hidden node problems.

Method used

By executing a clear request/authorization handshake protocol in the unlicensed frequency band, determine whether to perform side link communication, use source-destination identifier and signal strength information, and decide whether to perform side link communication based on network congestion level and service priority. , and data transmission is performed after the handshake is successfully completed.

Benefits of technology

It reduces the probability of frame conflict, improves the performance of wireless communication systems, and ensures the effectiveness and efficiency of side link communication.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096677A_ABST
    Figure CN119096677A_ABST
Patent Text Reader

Abstract

A transmitting (Tx) user equipment (UE) and one or more receiving (Rx) UEs may perform sidelink communications in an unlicensed band using a clear request / grant handshake. The clear request / grant handshake may include transmitting, by the Tx UE, a clear request broadcast signal indicating one or more Rx UEs using radio resources allocated to sidelink communications. The clear request / grant handshake is successfully completed when the Tx UE receives a clear grant signal corresponding to the first clear request broadcast signal from one or more of the Rx UEs. The sidelink communication is performed in response to successful completion of the clear request / grant handshake.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] The application claims priority to U.S. Provisional Patent Application No. 63 / 335,090, filed on April 26, 2022, entitled “SIDELINK REQUEST / GRANTPROTOCOL FOR WIRELESS NETWORKS,” the entire contents of which are hereby incorporated herein by reference. Technical Field

[0003] The present disclosure relates to wireless communications, and more particularly to sidelink communications conducted in unlicensed frequency bands by elements of a wireless communications system. Background Art

[0004] A wireless communication system may include one or more network communication devices, such as a base station, which may also be referred to as an eNodeB (eNB), a next generation NodeB (gNB) or other suitable terms. Each network communication device, such as a base station, may support wireless communication for one or more user communication devices, which may also be referred to as a user equipment (UE) or other suitable terms. A wireless communication system may support wireless communication with one or more user communication devices by utilizing resources of the wireless communication system, including time resources (e.g., symbols, time slots, subframes, frames, etc.), frequency resources (e.g., subcarriers, carriers) or a combination thereof. In addition, a wireless communication system may support wireless communication across various radio access technologies, including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, and other suitable radio access technologies other than 5G.

[0005] A UE in a wireless communication system may be configured to perform sidelink communications with other UEs, or more generally, with other devices other than a base station. Sidelink communications differ from other communications, such as uplink (UL) and downlink (DL) communications, in that sidelink communications are not performed through a base station, but rather involve direct radio frequency (RF) communications between two UEs that are transmitting or exchanging information.

[0006] When sidelink communication is performed in an unlicensed band, RF resources used by the sidelink communication between two UEs may be shared with other devices, which may create issues that the sidelink communication protocol may be suitable for improvement. Summary of the invention

[0007] The present disclosure relates to a method, apparatus and system for supporting sidelink communication using unlicensed bands by devices in a wireless communication system. The device may be a UE that directly communicates with other UEs. Since resource allocation for sidelink communication may be performed by a distributed mechanism, situations such as open node problems and hidden node problems may occur, which may increase the probability of frame collisions that may cause performance degradation. The present disclosure relates to reducing the probability of such frame collisions occurring, thereby improving the performance of the wireless communication system.

[0008] Some implementations of the methods and apparatus described herein determine whether to perform a clearance request / grant handshake before performing sidelink communication with one or more receiving (Rx) UEs in an unlicensed band, and in response to determining to perform a clearance request / grant handshake, perform a first clearance request / grant handshake, and in response to successful completion of the first clearance request / grant handshake, perform sidelink communication with one or more Rx UEs. The first clearance request / grant handshake includes sending a first clearance request broadcast signal indicating one or more Rx UEs by the Tx UE using radio resources allocated to the sidelink communication. When the Tx UE receives a clearance grant signal corresponding to the first clearance request broadcast signal from one or more of the Rx UEs, the clearance request / grant handshake is successfully completed.

[0009] In some implementations of the methods and apparatus described herein, instructing one or more Rx UEs to clear in a first clear-request broadcast signal is performed using one or more source-destination identifiers.

[0010] In some implementations of the methods and apparatus described herein, the methods and apparatus determine to perform a clear request / grant handshake based on a level of wireless network congestion, a priority of traffic to be transmitted in the sidelink communication, or a combination thereof.

[0011] In some implementations of the methods and apparatus described herein, the first clear request / grant handshake is unsuccessfully completed when the Tx UE does not receive a clear grant signal corresponding to the first clear request broadcast signal from one or more Rx UEs before expiration of a timeout interval.

[0012] In some implementations of the methods and apparatus described herein, the first clear request / grant handshake is not successfully completed when the Tx UE receives a signal from a UE other than one or more Rx UEs indicating that sidelink communication should not be performed.

[0013] In some implementations of the methods and apparatus described herein, the methods and apparatus perform sidelink communications without performing a clear request / grant handshake in response to determining not to perform a clear request / grant handshake.

[0014] In some implementations of the methods and apparatus described herein, the sidelink communication is a channel occupation time (COT) sharing communication.

[0015] In some implementations of the methods and apparatus described herein, wherein the methods and apparatus perform a second clear request / grant handshake by sending a second clear request broadcast signal in response to the first clear request / grant handshake not being successfully completed, the second clear request broadcast signal indicating one or more Rx UEs other than the one or more Rx UEs indicated in the first clear request broadcast signal.

[0016] In some implementations of the methods and apparatus described herein, the clear authorization signal includes a source-destination identifier corresponding to a source-destination identifier included in the first clear request broadcast signal, information about a signal strength of the first clear request broadcast signal at a UE that sends the clear authorization signal, information about an amount of interference present at a UE that sends the clear authorization signal on radio resources associated with sidelink communications, or a combination thereof.

[0017] In some implementations of the methods and apparatus described herein, a first clear request broadcast signal is sent on multiple transmission beams, a clear grant signal is received using the multiple transmission beams, and one or more measurements of corresponding channel characteristics of the multiple transmission beams are used to select a transmission beam for subsequent data transmission for sidelink communication.

[0018] Some implementations of the methods and apparatus described herein receive a clear-request broadcast signal from a transmitting (Tx) UE regarding a sidelink communication in an unlicensed band, determine whether the clear-request broadcast signal identifies the method and apparatus as participating in the sidelink communication, and in response to determining that the clear-request broadcast signal identifies the method and apparatus as participating in the sidelink communication, determine whether the Tx UE is authorized to perform a clear of the sidelink communication.

[0019] In some implementations of the methods and apparatus described herein, the methods and apparatus, in response to determining that the Tx UE is authorized to perform a clear for sidelink communication, the Tx UE sends a clear grant signal.

[0020] In some implementations of the methods and apparatus described herein, the clear grant signal includes an identifier corresponding to an identifier included in the clear request broadcast signal, information about received signal strength of the clear request broadcast signal, information about interference present at the Rx UE, or a combination thereof.

[0021] In some implementations of the methods and apparatus described herein, sending a clear grant signal to the Tx UE includes performing a listen-before-talk operation before sending the clear grant signal to the Tx UE.

[0022] In some implementations of the methods and apparatus described herein, determining whether the clear request broadcast signal identifies the Rx UE as participating in the sidelink communication includes comparing an identifier included in the clear request broadcast signal with an identifier associated with the Rx UE.

[0023] In some implementations of the methods and apparatus described herein, the methods and apparatus transmit a signal to the Tx UE indicating that the sidelink communication is not to be performed in response to determining that the Tx UE is not authorized to perform the clearing of the sidelink communication.

[0024] In some implementations of the methods and apparatus described herein, the sidelink communication is a channel occupation time (COT) sharing communication.

[0025] In some implementations of the methods and apparatus described herein, the methods and apparatus terminate communications performed by the Rx UE, perform a backoff operation, or both in response to determining that the clear request broadcast signal does not identify the Rx UE as participating in sidelink communications.

[0026] In some implementations of the methods and apparatus described herein, the methods and apparatus send a signal to the Tx UE to indicate that the Tx UE should not perform sidelink communication in response to determining that the clear request broadcast signal does not identify the Rx UE as participating in sidelink communication and when the priority indicated in the clear request broadcast signal is lower than the priority of pending traffic of the Rx UE. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 An example of a wireless communication system supporting sidelink communications according to aspects of the present disclosure is shown.

[0028] Figure 2 A time slot structure for NR sidelink communication according to an embodiment of the present disclosure is shown.

[0029] FIG. 3A to FIG. 3C It is shown that side link communication is performed according to an embodiment of the present disclosure.

[0030] Figure 4 It is shown that side link communication is performed according to another embodiment of the present disclosure.

[0031] Figure 5 is a block diagram of a device supporting sidelink communications according to aspects of the present disclosure.

[0032] Figure 6 and Figure 7 A flow chart of a method for supporting sidelink communications according to aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0033] Embodiments relate to a channel access mechanism for sidelink communications in an unlicensed band in a wireless communication system. Specifically, embodiments of the present disclosure address hidden node and open node scenarios that may occur when performing such sidelink communications in a New Radio Unlicensed Spectrum (NR-U) environment.

[0034] Embodiments of the present disclosure provide a handshake protocol that can prevent initiation of sidelink communication in an unlicensed band when interference at one of the devices participating in the sidelink communication makes it infeasible to perform the sidelink communication. The handshake protocol includes a potential initiator of the sidelink communication (referred to herein as a transmitting UE (Tx UE)) sending a request to perform the sidelink communication, and a receiver of the request (referred to herein as a receiving UE (Rx UE)) sending a clear to perform the sidelink communication when conditions at the Rx-UE do not make the sidelink communication infeasible.

[0035] Considering the distributed resource allocation mechanism used in sidelink communication, such a protocol should alleviate the performance degradation caused by frame collisions and similar phenomena.

[0036] Aspects of the present disclosure are described in the context of a wireless communication system. Aspects of the present disclosure will be further illustrated and described with reference to device diagrams, flow diagrams, data flow diagrams, and data model diagrams related to clear request / grant handshakes for performing sidelink communications in an unlicensed band.

[0037] Table 1 below provides a list of abbreviations that may be used herein:

[0038] Table 1: Abbreviations

[0039]

[0040]

[0041] Figure 1 An example of a wireless communication system 100 that supports sidelink communications according to aspects of the present disclosure is shown. The wireless communication system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communication system 100 may support various radio access technologies. In some implementations, the wireless communication system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communication system 100 may be a 5G network, such as a 3rd Generation Partnership Project (3GPP 5G) network. TM) New Radio (NR) network. In other implementations, the wireless communication system 100 may be a combination of a 4G network and a 5G network. The wireless communication system 100 may support radio access technologies other than 5G. In addition, the wireless communication system 100 may support technologies such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA).

[0042] One or more base stations 102 may be dispersed throughout a geographic area to form a wireless communication system 100. One or more base stations 102 described herein may be or include or may be referred to as a network entity, a network communication device, a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next generation NodeB (gNB), or other suitable terms. The base station 102 and the UE 104 may communicate via a communication link 108, which may be a wireless or wired connection.

[0043] Base stations 102 may provide geographic coverage areas 110 accordingly, and each base station may support services (e.g., voice, video, packet data, message, broadcast, etc.) for one or more UEs 104 within the geographic coverage area 110 for the geographic coverage area 110. For example, base stations 102 and UEs 104 may support wireless communications of signals related to services (e.g., voice, video, packet data, message, broadcast, etc.) according to one or more radio access technologies. In some implementations, one or more base stations 102 may be mobile, such as satellites associated with non-terrestrial networks. In some implementations, geographic coverage areas 110A and 110B may be associated with the same or different radio access technologies and may overlap, but different geographic coverage areas 110 may be associated with different base stations 102 accordingly. The information and signals described herein may be represented using any of a variety of different technologies and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, light fields or particles, or any combination thereof.

[0044] The base station 102 may support communication with the core network 106 or another base station 102 or both. For example, the base station 102 may interface with the core network 106 via one or more backhaul links 114 (e.g., via S1, N2, N2 or another network interface). The base stations 102 may communicate with each other via the backhaul links 114 (e.g., via X2, Xn or another network interface). In some implementations, the base stations 102 may communicate directly with each other. In some other implementations, the base stations 102 may communicate with each other or indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with one or more UEs 104 via one or more other access network transmission entities, which may be referred to as radio heads, smart radio heads, or transmission-reception points (TRPs).

[0045] The core network 106 may include one or more computers and associated communication interconnects, and may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions. The core network 106 may be an evolved packet core (EPC) or a 5G core (5GC), which may include control plane entities that manage access and mobility (e.g., a mobility management entity (MME), one or more access and mobility management functions (AMFs), and user plane entities that route or interconnect packets to external networks (e.g., a serving gateway (S-GW), a packet data network (PDN) gateway (P-GW), or a user plane function (UPF)). In some implementations, the control plane entities may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management for one or more UEs 104 served by one or more base stations 102 associated with the core network 106.

[0046] One or more UEs 104 may be dispersed throughout the geographic area of ​​the wireless communication system 100. UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, or a subscriber device, or some other suitable term. In some implementations, UE 104 may be referred to as a unit, a station, a terminal, or a client, etc. Additionally or alternatively, UE 104 may be referred to as an Internet of Things (IoT) device, an Internet of Everything (IoE) device, or a Machine Type Communication (MTC) device, etc. In some implementations, UE 104 may be stationary in the wireless communication system 100. In some other implementations, UE 104 may move in the wireless communication system 100.

[0047] One or more UEs 104 may be devices of different forms or with different functions. Some examples of UEs 104 are shown in FIG. Figure 1 UE 104 may be able to communicate with various types of devices, such as base station 102, other UEs 104, or network devices (e.g., core network 106, relay device, integrated access and backhaul (IAB) node, or another network device), such as Figure 1 Additionally or alternatively, the UE 104 can support communications with other base stations 102 or UEs 104, which can act as relays in the wireless communication system 100.

[0048] The UE 104 may also support wireless communications directly with other UEs 104 via a communication link 112; the communication link 112 may be a side link 112. For example, a first UE 104A may support wireless communications directly with one or more second UEs 104B via a device-to-device (D2D) communication link. For example, a UE 104 may support wireless communications directly with another UE 104 via a PC5 interface. The UE 104 may support unicast, multicast, and broadcast side links 112.

[0049] Figure 2 A time slot structure for NR sidelink communication according to an embodiment of the present disclosure is shown. In an embodiment, NR sidelink communication is performed using a radio frame, which may have a duration of 10 milliseconds. Each radio frame may be divided into 10 subframes, which may have a duration of 1 millisecond. Each subframe may have a variable number of time slots, depending on the symbol rate and the number of symbols per time slot.

[0050] exist Figure 2 In the figure, A shows the structure for a time slot without PSFCH, and B shows the structure for a time slot with PSFCH. Each time slot shown includes 14 symbols, but the embodiment is not limited thereto, and the time slot can be preconfigured to have 7 to 14 symbols. MPSSCH is the number of physical resource blocks (PRBs) in the time slot, LPSSCH is the number of subchannels used to perform sidelink communication, and MPSCCH is the number of PRBs used to communicate PSCCH.

[0051] In NR sidelink communications, PSSCH can be sent starting from the second sidelink symbol in a slot and ending at the second to last sidelink symbol. Therefore, depending on the length of the slot, PSSCH can be sent in 5 to 12 consecutive sidelink symbols. The number of PSSCH symbols also depends on whether PSFCH is sent in the slot.

[0052] When the PSCCH does not span the entire LPSSCH subchannel, the sidelink symbol carrying the PSCCH may also include the PSSCH via frequency multiplexing. This results in 2 or 3 PSCCH / PSSCH symbols. In the sidelink symbol without PSCCH, the PSSCH spans all LPSSCH subchannels. PSSCH Subchannel.

[0053] The second sidelink symbol (including the first PSCCH or PSCCH / PSSCH symbol) is repeated in the first sidelink symbol for use in automatic gain control (AGC). The symbols after the last PSSCH symbol are used as guard symbols.

[0054] In NR sidelink communications, PSFCH carries HARQ feedback from (multiple) RX UEs to TX UEs. Within the resource pool, resources for PSFCH can be configured periodically with a period of 1, 2 or 4 time slots. PSFCH is sent in one of the last sidelink symbols in the PSCCH / PSSCH time slot. Before the PSFCH symbol, a copy of the PSFCH symbol is sent for AGC use, and after the PSFCH symbol, the protection symbol is sent. The three sidelink symbols associated with PSFCH are located after all PSSCH symbols. Therefore, when a time slot carries PSFCH, the number of PSSCH symbols can be between 2 and 9 symbols (depending on the time slot length).

[0055] A bandwidth part (BWP) is a contiguous bandwidth portion within the carrier bandwidth with a single parameter configuration. Using a smaller BWP reduces the computational complexity and power consumption required by the UE. Each BWP can have different bandwidths and parameters, enabling more flexible and efficient use of resources.

[0056] The concept of BWP has also been adopted for some NR sidelink communications, where the sidelink BWP occupies a continuous bandwidth portion within the carrier. In a carrier, a single sidelink BWP can be configured for all UEs. Sidelink UE transmissions and receptions (including physical channels, reference signals, and synchronization signals) are contained within the sidelink BWP and use the same configuration parameters.

[0057] The sidelink BWP is divided into common resource blocks (RBs). A common RB includes 12 consecutive subcarriers with the same subcarrier spacing, where the subcarrier spacing is given by the parameter configuration of the sidelink BWP.

[0058] A resource pool includes contiguous physical RBs (PRBs) and contiguous or non-contiguous time slots that have been configured for sidelink communications. A resource pool must be defined within a sidelink BWP.

[0059] Therefore, a single value is used within the resource pool. If the UE has an active UL BWP, the sidelink BWP must be configured with the same parameters as the UL BWP if both the sidelink BWP and the UL BWP are included in the same carrier. Otherwise, the sidelink BWP will be deactivated.

[0060] In some NR sidelink communications, data in the NR sidelink communications may be organized into TBs carried in the PSSCH. Each TB is associated with an SCI that indicates the resources used by the PSSCH carrying the associated TB, as well as further information required to decode the TB. The SCI may be sent in two parts: the first stage SCI is carried in the PSCCH sent with the PSSCH, while the second stage SCI is sent in the PSSCH.

[0061] In resource allocation for certain NR sidelink communications, the subchannels used for sidelink communications are selected using one of two modes. In the first allocation mode (mode 1), the base station assigns and manages the radio resources used for sidelink communications. Therefore, the first mode can be used only when the UE for which the subchannel selection is performed is in network coverage.

[0062] Mode 1 uses dynamic grant (DG) scheduling, and for DG, a UE using Mode 1 must request resources from the base station for the transmission of each single TB. The base station sends the UE an indication of the sidelink resources (i.e., (multiple) time slots and (multiple) subchannels) allocated for the transmission of the TB and up to 2 possible retransmissions of the TB. The UE uses the first stage SCI to inform other UEs of the resources it will use to send the TB and up to 2 possible retransmissions. Mode 1 includes a configuration grant scheduling option to reduce latency by pre-allocating sidelink radio resources. With this scheme, the base station can assign a set of sidelink resources (called a configuration grant (CG)) to the UE to send several TBs.

[0063] In the second allocation mode (Mode 2), the UE autonomously selects its sidelink resources (one or more subchannels) from the resource pool. Therefore, in Mode 2, the UE can operate without network coverage. When the UE is in network coverage, the resource pool can be configured by the base station. The UE can select new sidelink resources when a new TB is generated. The new selection can also be triggered to select a new sidelink resource.

[0064] The UE first defines a selection window in which it searches for candidate resources for sending a TB. The selection window includes all resources within the time slot range, with the lower end determined by the processing time (in time slots) required for the UE to identify the candidate resources and select a new sidelink resource for transmission, and the upper end determined by an implementation-dependent value that must be less than the packet delay budget (in time slots). The packet delay budget is the delay deadline within which the TB must be sent.

[0065] When the UE is not transmitting, it senses the sidelink resources during the sensing window in order to identify available candidate resources. The sensing window is a time interval determined according to the resource selection trigger or the time slot in which a new resource must be selected, and is equivalent to a number of time slots of 1100 ms or 100 ms. The time required to complete the sensing process is equal to one time slot for a subchannel spacing of 15 or 30 kHz, 2 time slots for a subchannel spacing of 60 kHz, and 4 time slots for a subchannel spacing of 120 kHz.

[0066] During the sensing process, the UE decodes any first stage SCI received from other UEs in the sensed sidelink resources. The first stage SCI indicates the sidelink resources that other UEs have reserved for their TB and SCI transmissions in PSSCH and PSCCH.

[0067] A UE performing sidelink communication in an unlicensed band acquires the radio resources required for a COT. In an embodiment, a UE may share its acquired COT with another device. The benefit of such COT sharing is that a device initiating a COT may authorize another device to use the rights of the initiated COT without requiring the target device to initiate its own COT. Initiating a COT typically involves a specific sensing time before transmission is allowed, whereas starting transmission in a shared COT requires only a fraction of the sensing time required for initiating a COT.

[0068] A COT has one or more of the following properties:

[0069] • COT initiator: A node that initiates a COT, for example following the channel access procedure as specified in 3GPP TS 37.213.

[0070] Channel access priority class: One or more classes, e.g., implying the required sensing duration when initiating COT, MCOT, e.g., as defined in 3GPP TS 37.213.

[0071] MCOT: Maximum COT duration of channel occupancy, counted or measured from the first transmission after the initiation of COT.

[0072] In a traditional cellular topology with a centralized scheduler, a base station usually initiates a COT and may share this COT with one or more UEs, or a UE initiates a COT and may share this COT with a base station. In these cases, the sharing of the COT is indicated by a specific field in the downlink control information or the uplink control information. The COT sharing indicator may include a method to indicate the maximum remaining duration of the shared COT.

[0073] The following definitions are used for the purpose of sidelink channel access mechanisms related to COT sharing:

[0074] • Tx UE: A UE that sends a COT sharing indicator via a sidelink connection.

[0075] • Rx UE: A UE that receives the COT sharing indicator via a sidelink connection.

[0076] COT initiator: The sidelink device that initiates channel occupancy, such as Tx UE.

[0077] COT donor: A sidelink device that sends a COT sharing indicator, such as a Tx UE. The COT donor may be the same as the COT initiator.

[0078] COT receiver: A sidelink device that receives the COT sharing indicator, such as an Rx UE.

[0079] The UE-to-UE COT sharing principle should take into account that a COT initiator as a Tx UE may have connections with multiple Rx UEs or destinations. A COT initiator or Tx UE can share its initiated COT with multiple Rx UEs or destinations. A COT receiver acting as a Rx UE can send data or feedback in the remaining channel duration after receiving the COT sharing indicator.

[0080] The SCI format for UE to UE COT sharing operation and how to send the COT sharing indicator to multiple Rx UEs or destination IDs are outside the scope of this disclosure. The COT sharing indicator may include the remaining duration in terms of the number of physical time slots, channel access priority value, and destination ID of the COT receiver.

[0081] Figures 3A to 3C FIG. 1 shows performing side link communication according to an embodiment of the present disclosure. Figures 3A to 3C In each of the two embodiments, the Tx UE 302 seeks to perform sidelink communications with the first Rx UE 304 , and the second Rx UE 306 receives some or all sidelink-related communications between the Tx UE 302 and the first Rx UE 304 .

[0082] Figure 3AIt is shown that the sidelink communication is performed after a successful request / grant handshake between the Tx UE 302 and the first Rx UE 304 according to an embodiment of the present disclosure.

[0083] At S308, the Tx UE 302 is allocated radio resources (ie, time slots and subchannels) for performing sidelink communication. For example, radio resources may be allocated to the Tx UE 302 for sidelink communication according to the first or second allocation mode described above, but the embodiment is not limited thereto.

[0084] At S310, Tx UE 302 successfully performs clear channel assessment to determine that the allocated radio resources are not used by another device. Clear channel assessment may be based on the listen-before-talk procedure described in the 3GPP standard, for example, but the embodiment is not limited thereto.

[0085] It is worth noting that the clear channel assessment only evaluates the condition of the radio resources at the Tx UE 302 and may detect interference or competing use of the radio resources at the first Rx UE 304 in some cases.

[0086] Therefore, at S312, the Tx UE 302 may initiate a request / grant protocol by sending a clear request broadcast signal. The Tx UE may have performed a clear channel assessment procedure using a quasi-omni sensing beam and may send a clear request broadcast signal using a quasi-omni transmission beam.

[0087] The clear request broadcast signal may include a request information bit set in the first SCI or second SCI field, and then additional information, such as a CAPC value, MCOT duration, source-destination ID, or a combination thereof. The clear request broadcast signal indicates that the first Rx UE 304 is one of the one or more target receivers for sidelink communication. The clear request broadcast signal does not indicate that the second Rx UE 306 is one of the target receivers for sidelink communication.

[0088] In another implementation, MAC CE may also be used as signaling for sending a clear request broadcast signal having the above information, and the MAC CE may be sent together with the SCI.

[0089] In an embodiment, the request / grant protocol may be initiated based on whether the resource pool to be used for the sidelink communication indicates a protocol to be used, the priority of the type of traffic conveyed by the sidelink communication, an indication of congestion in the wireless network, a packet delay budget, or a combination thereof. Thus, in an embodiment, performing the sidelink communication may require successful completion of the request / grant protocol, may be performed when conditions for initiation exist, or may be performed without performing the request / grant protocol.

[0090] The clear request broadcast signal may be received by one or more Rx UEs (represented by the first Rx UE 304 in FIG. 3 ) that are potential participants in the sidelink communication and Rx UEs (represented by the second Rx UE 306 ) that are not potential participants in the sidelink communication.

[0091] At S314, the first Rx UE 304 uses the destination indication (such as the second protocol stack level (L2) source destination ID) in the clear request broadcast signal to determine that the Tx UE 302 is requesting it to provide a clear grant signal. Therefore, the first Rx UE 304 proceeds to S316A.

[0092] At S316A, the first Rx UE 304 may evaluate the strength of the received clear request broadcast signal to determine whether the transmission from the Tx UE 502 will be received with sufficient strength to support the side link communication. For example, the first Rx UE 304 may determine and evaluate the reference signal received power (RSRP) or received signal strength indicator (RSSI) of the received clear request broadcast signal. The first Rx UE 304 may also determine the interference level present in the channel in which the clear request broadcast signal is received.

[0093] At S318A, the first Rx UE 304 may perform a listen-before-talk (LBT) operation. In an embodiment, the LBT operation may be a 3GPP Cat 3 LBT operation. If the LBT operation indicates that the channel is idle, at S320, the first Rx UE 304 may send a clear grant signal to the Tx UE 302.

[0094] The first Rx UE 304 may perform an LBT operation using a directional sensing beam, which may be a beam used to receive a clear request broadcast signal.

[0095] In an embodiment, when the RSRP or RSSI is worse than the minimum received signal strength threshold, the first Rx UE 304 does not send a clear grant signal.

[0096] In other embodiments, when the interference level in the channel where the clear request broadcast signal is received is greater than the maximum interference threshold, the first Rx UE 304 does not send the clear grant signal.

[0097] In yet another embodiment, when any of the above conditions exist, the first Rx UE 304 does not send a clear grant signal.

[0098] In yet another embodiment, the first Rx UE 304 sends a clear grant signal regardless of whether the above conditions exist, but includes an indication that the Tx UE 502 is not authorized to send a clear. The indication may include a reason for not granting the clear, such as an indication related to RSRP, an indication related to the interference level measured by the first Rx UE 304, or both.

[0099] In an embodiment, the first Rx UE 304 may include an indication of preferred resources (e.g., preferred subchannels) for sidelink communication in the clear grant signal. For example, the first Rx UE 304 may indicate a subchannel set with the lowest channel loss (as determined using the RSRP or RSSI measured above) or the lowest measured interference as the preferred resource for sidelink communication.

[0100] The purge authorization signal may also include a source-destination ID corresponding to the received purge request broadcast signal to further associate the purge authorization signal with the purge request broadcast signal.

[0101] The clear grant signal may also include a maximum COT (MCOT). The MCOT may be based on the MCOT included in the clear request broadcast signal. The MCOT included in the clear grant signal may indicate a maximum channel occupancy duration given by a channel access priority class, or the clear grant may indicate a remaining COT for sidelink communication and may therefore correspond to the MCOT included in the clear request broadcast signal minus an amount corresponding to a delay between the clear request broadcast signal received by the first Rx UE (which may correspond to the remaining COT 304) and the clear grant signal sent by the first Rx UE 304.

[0102] In an embodiment, the first Rx UE 304 may send a clear grant signal in a PSFCH, a first SCI, a second SCI, a higher layer signaling such as a medium access control (MAC) element (CE), or a combination thereof.

[0103] In an embodiment, the first Rx UE 304 may transmit the clear grant signal using a directional transmission beam previously established between the Tx UE 302 and the source-destination ID of the first Rx UE 304 .

[0104] At S322A, the Tx UE 302 evaluates the clear grant signal received at S320 to determine whether it indicates that the Tx UE 302 has been authorized to begin clearing for sidelink communications.

[0105] In an embodiment, the Tx UE 302 may determine that the purge has been authorized in response to receiving a purge grant signal having the same source-destination ID as the purge request broadcast signal.

[0106] In an embodiment, Tx UE 302 may determine that purge is authorized in response to receiving a purge authorization signal having the same source-destination ID as the purge request broadcast signal and having an indication that purge is authorized for transmission set to a value corresponding to true or an indication that purge is not authorized for transmission set to a value corresponding to false.

[0107] In an embodiment, when the information about the channel condition satisfies one or more criteria, the Tx UE 302 may determine that clearing is authorized in response to receiving a clear grant signal having the same source-destination ID as the clear request broadcast signal and having information about the channel condition at the first Rx UE 304. The one or more criteria may include, for example, that the RSRP or RSSI corresponding to the clear request broadcast signal is sufficiently high, that the interference at the first Rx UE 304 is sufficiently low, or both.

[0108] In response to determining at S322A that the purge is authorized, at S324 , the Tx UE 302 may perform a substantial portion of the sidelink communication; that is, the portion of the sidelink communication remaining to be performed after the purge request / grant protocol, such as data transmission.

[0109] Returning to the time point after the transmission of the clear request broadcast signal at S312, at S334, the second Rx UE 306 uses the destination indication in the clear request broadcast signal to determine that the Tx UE 302 has not requested it to provide a clear grant signal. Therefore, the second Rx UE 306 proceeds to S336A.

[0110] The second Rx UE 306 may use the same process at S334 as used by the first Rx UE 304 at S314 , but may derive different results because the relevant identifier (eg, L2 source-destination ID) corresponding to the second Rx UE 306 is different from the relevant identifier corresponding to the first Rx UE 304 .

[0111] In an embodiment, at S336A, if the second Rx UE 306 seeks to use the radio resources allocated to the sidelink communication, the second Rx UE 306 may implement a random backoff for subsequent LBT, wherein the counter may be set to a random integer value selected from 0 and a preconfigured contention window size. Subsequently, the second Rx UE 306 may postpone performing sensing of an idle time slot until the counter is decremented to zero.

[0112] In an embodiment, at S336A, the second Rx UE 306 may compare the priority of the traffic type indicated in the clear request broadcast signal with the priority of the traffic that the second Rx UE 306 is communicating or intends to communicate. If the priority of the traffic type indicated in the clear request broadcast signal is higher, the second UE may defer transmission of its traffic until the MCOT indicated in the clear request broadcast signal has passed.

[0113] In an embodiment, at S336A, the second Rx UE 306 may compare the RSRP of the clear request broadcast signal with a preconfigured threshold. If the RSRP is higher than the threshold, in order not to interfere with the side link communication, the second Rx UE 306 may postpone the transmission of its traffic until the MCOT indicated in the clear request broadcast signal has passed.

[0114] Figure 3B An attempt to perform sidelink communication is shown where a request / grant handshake between the Tx UE 302 and the first Rx UE 304 is unsuccessful according to an embodiment of the present disclosure.

[0115] exist Figure 3B In the step S308, S310, S312, S314, S334 and S336A, Figure 3A The description is the same, and for the sake of brevity, repetition of the description is omitted.

[0116] Figure 3B The process and Figure 3A The process is different in that, in S316B, S318B or both, one of the criteria described with respect to S316A and S318A for authorizing clearing to perform side link communication is not met. Therefore, the first Rx UE 304 does not send a clearing authorization signal, or (not shown) sends a signal indicating that clearing is not authorized.

[0117] At S340 , when the first Rx UE 304 does not send a clear grant signal, the Tx UE 302 waits for expiration of a timeout duration, and defers sidelink communication after expiration of the timeout duration without receiving a clear grant signal.

[0118] In an embodiment, the Tx UE 302 may also defer sidelink communications in response to receiving a signal indicating clearing unauthorized.

[0119] In an embodiment, the Tx UE 302 may cancel the sidelink communication in certain circumstances rather than deferring it. Such circumstances may include when the sidelink communication is best effort, when a retry count is exceeded, and the like.

[0120] Figure 3CAn attempt to perform sidelink communication is shown wherein a request / grant handshake between a Tx UE 302 and a first Rx UE 304 is replaced by a response to the request / grant handshake generated by a second Rx UE 306 in accordance with an embodiment of the present disclosure.

[0121] exist Figure 3C In the step S308, S310, S312, S314, S316A, S318A, S320 and S334 and Figure 3A For the sake of brevity, repetition of this description is omitted.

[0122] Figure 3C The process and Figure 3A The process is different in that, in S336C, the priority of the service type indicated in the clear request broadcast signal is less than the priority of the service that the second Rx UE 306 is communicating or intends to communicate. In response, at S338, the second Rx UE 306 sends a "do not send" command to the Tx UE 302.

[0123] At S342, in response to receiving the "don't send" command, the Tx UE 302 may postpone (or in some cases cancel) the sidelink communication.

[0124] The Tx UE 302 may perform clear channel assessment using a quasi-omni beam but may transmit a clear request broadcast signal using a plurality of transmission beams associated with a sensing beam. A beam correspondence clear grant signal may be transmitted from the first Rx UE 304 using beam correspondence to consider each directional beam.

[0125] There may be a one-to-one mapping between the radio resources (such as time slot(s), sub-channel(s), or both) used by the clear-request broadcast signal and the radio resources used by the corresponding clear-grant signal.

[0126] In an embodiment, the first Rx UE 304 will not send a clear request broadcast signal in a transmission with a measured RSSI / RSRP above a preconfigured threshold. This may be useful in selecting an appropriate transmission beam for the Tx UE 302 to use.

[0127] Figure 4 It is shown that according to an embodiment of the present disclosure, COT sharing is performed in the sidelink communication after a successful request / grant handshake between the Tx UE 402 and the third Rx UE 404B.

[0128] Figure 4 A Tx UE 402, a first Rx UE 404A, and a third Rx UE 404B are shown. In an embodiment, the Tx UE 402 corresponds to Figures 3A to 3C The Tx UE 302 in FIG. 1 and the first and third Rx UEs 404A and 404B each correspond to Figures 3A to 3C A first Rx UE 304 participating in sidelink communication with the Tx UE.

[0129] The Tx UE 402, the first Rx UE 404A and the third Rx UE 404B are assumed to participate in Figure 4 The process shown in 404 begins with sidelink communication with a remaining COT, and the Tx UE 402 may have determined to share the COT with one or more of the first and third Rx UEs 404A and 404B after having completed sending its own data.

[0130] At S412-1, the Tx UE 402 sends a first COT sharing request, indicating that the Tx UE 402 intends to share the COT and identifies the first Rx UE 404A as a candidate for sharing the COT. The first COT sharing request may include information about Figure 3A Information included in a clear request broadcast signal described. The first COT sharing request may correspond to a clear request broadcast signal having an indication that the requested clear is for COT sharing.

[0131] At S414-1, the first Rx UE 404A uses Figure 3A The first Rx UE 404A then uses the same method as that described in S314 of S416-1 to determine that the first COT sharing request is for it. Figure 3B A similar process as described in S316B and / or S318B is used to determine whether to authorize the first COT sharing request.

[0132] and Figure 3B Similarly, the first Rx UE 404A determines that the COT sharing request is not authorized and therefore does not send a COT sharing grant to the Tx UE 402 .

[0133] In another embodiment (not shown), the first Rx UE 404A may send a signal to the Tx UE 402 indicating that the COT sharing request has been rejected.

[0134] At S440, after a timeout occurs (or after receiving a signal from the first Rx UE 404A indicating that the COT sharing request has been rejected), at S412-2, the Tx UE 402 sends a second COT sharing request indicating that the Tx UE 402 intends to share the COT and identifies the third Rx UE 404B as a candidate for sharing the COT. The second COT sharing request may include information about Figure 3ADescribes the information included in the clear request broadcast signal.

[0135] At S414-2, the third Rx UE 404B uses Figure 3A The third Rx UE 404B then uses the same method as that described in S314 of S416-2 to determine that the second COT sharing request is for it. Figure 3A A process similar to the process described in S316A and / or S318A is used to determine whether to authorize the COT sharing request.

[0136] and Figure 3A Similarly, the third Rx UE 404B determines to grant the second COT sharing request, and accordingly sends a COT sharing grant signal to the Tx UE 402 at S420. The COT sharing grant signal may include a Figure 3A The information included in the clear authorization signal described above may be sent in one or more of the ways described for the clear authorization signal.

[0137] At S422, the Tx UE 402 uses the received COT sharing grant signal to verify whether COT sharing has been granted. Subsequently, at S424, an additional transaction of the sidelink communication is performed to transmit data of the third Rx UE 404B.

[0138] Figure 5 A block diagram 500 of a device 502 for supporting a clear request / grant handshake for performing sidelink communications in an unlicensed band in a wireless communication network according to aspects of the present disclosure is shown. The device 502 may be an example of a UE 104 as described herein. The device 502 may support wireless communications with one or more base stations 102, UEs 104, other devices implementing corresponding network functions, or any combination thereof. The device 502 may include components for bidirectional communications, including components for sending and receiving communications, such as a communication manager 504, a processor 506, a memory 508, a receiver 510, a transmitter 512, and an I / O controller 514. These components may be in electronic communication or otherwise coupled (e.g., operationally, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., a bus).

[0139] The communication manager 504, the receiver 510, the transmitter 512, or various combinations thereof, or various components thereof, may be examples of means for performing various aspects of the present disclosure described herein. For example, the communication manager 504, the receiver 510, the transmitter 512, or various combinations thereof, or components thereof, may support methods for performing one or more functions described herein.

[0140] In some implementations, the communication manager 504, the receiver 510, the transmitter 512, or various combinations or components thereof may be implemented in hardware (e.g., in a communication management circuit system). The hardware may include a processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, configured to or otherwise support components for performing the functions described in the present disclosure. In some implementations, the processor 506 and a memory 508 coupled to the processor 506 may be configured to perform one or more functions described herein (e.g., by executing instructions stored in the memory 508 by the processor 506).

[0141] Additionally or alternatively, in some implementations, the communication manager 504, the receiver 510, the transmitter 512, or various combinations or components thereof may be implemented in code executed by the processor 506 (e.g., as communication management software or firmware). If implemented in code executed by the processor 506, the functionality of the communication manager 504, the receiver 510, the transmitter 512, or various combinations or components thereof may be performed by a general purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured or otherwise supported to perform the functions described in the present disclosure).

[0142] In some implementations, the communication manager 504 may be configured to perform various operations (e.g., receive, monitor, transmit) using or otherwise cooperating with the receiver 510, the transmitter 512, or both. For example, the communication manager 504 may receive information from the receiver 510, send information to the transmitter 512, or be integrated with the receiver 510, the transmitter 512, or a combination of the two to receive information, send information, or perform various other operations described herein. Although the communication manager 504 is shown as a separate component, in some implementations, one or more functions described with reference to the communication manager 504 may be supported or performed by the processor 506, the memory 508, or any combination thereof. For example, the memory 508 may store code that may include instructions executable by the processor 506 to cause the device 502 to perform various aspects of the present disclosure described herein, or the processor 506 and the memory 508 may be otherwise configured to perform or support such operations.

[0143] For example, the communication manager 504 can support wireless communication at a first device (e.g., device 502) according to examples disclosed herein. The communication manager 504 can be configured to or otherwise support means for performing a request / grant protocol to prevent frame collisions and other problems (such as those that may be caused by hidden or open nodes when performing sidelink communications in an unlicensed band).

[0144] The processor 506 may include an intelligent hardware device (e.g., a general purpose processor, a digital signal processor (DSP), a central processing unit (CPU), a microcontroller, an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 506 may be configured to operate the memory array using a memory controller. In some other implementations, the memory controller may be integrated into the processor 506. The processor 506 may be configured to execute computer readable instructions stored in a memory (e.g., memory 508) to cause the device 502 to perform various functions of the present disclosure.

[0145] The memory 508 may include random access memory (RAM) and read-only memory (ROM). The memory 508 may store computer-readable, computer-executable code, including instructions, that, when executed by the processor 506, cause the device 502 to perform various functions described herein. The code may be stored in a non-transitory computer-readable medium, such as a system memory or another type of memory. In some implementations, the code may not be directly executed by the processor 506, but may cause a computer (e.g., when compiled and executed) to perform the functions described herein. In some implementations, the memory 508 may include a basic I / O system (BIOS), which may control basic hardware or software operations, such as interaction with peripheral components or devices.

[0146] I / O controller 514 can manage input and output signals for device 502. I / O controller 514 can also manage peripheral devices that are not integrated into device 502. In some implementations, I / O controller 514 can represent a physical connection or port to an external peripheral device. In some implementations, I / O controller 514 can utilize an operating system, such as Or other known operating systems. In some implementations, I / O controller 514 can be implemented as part of the processor (which is the same as processor 506). In some implementations, a user can interact with device 502 via I / O controller 514 or via hardware components controlled by I / O controller 514.

[0147] In some embodiments, the device 502 may include a single antenna 516. However, in some other implementations, the device 502 may have more than one antenna 516, which may be able to send or receive multiple wireless transmissions concurrently. The receiver 510 and the transmitter 512 may communicate bidirectionally via one or more antennas 516, wired or wireless links as described herein. For example, the receiver 510 and the transmitter 512 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. The transceiver may also include a modem to modulate packets, provide the modulated packets to one or more antennas 516 for transmission, and demodulate packets received from one or more antennas 516.

[0148] Figure 6 and 7 A flow chart of a method for supporting sidelink communications according to aspects of the present disclosure is shown.

[0149] Figure 6 A flow chart of a method 600 for supporting sidelink communication according to aspects of the present disclosure is shown. The method 600 may be performed by a device operating as a Tx UE.

[0150] At S605, the device determines whether to perform a clear request / grant handshake before performing sidelink communication with one or more Rx UEs in the unlicensed band. The determination may be based on the level of wireless network congestion, the priority of the traffic to be transmitted in the sidelink communication, or a combination thereof.

[0151] In response to determining to perform a clear request / authorization handshake, at S605 , the device proceeds to S610 ; otherwise, the device proceeds to S620 .

[0152] At S610, the device transmits a clear request broadcast signal indicating one or more Rx UEs. The clear request broadcast signal may be transmitted using radio resources allocated to sidelink communication.

[0153] At S615, the device determines whether the clear request / grant handshake has been successfully completed. The clear request / grant handshake is successfully completed when a clear grant signal is received from one or more Rx UEs.

[0154] In an embodiment, the clear request / grant handshake is not successfully completed when the clear grant signal is not received before the expiration of a timeout period following the transmission of the clear request broadcast signal.

[0155] In an embodiment, the clear request / grant handshake is not successfully completed when a no-send signal sent in response to a clear request broadcast signal is received.

[0156] In response to determining that the clear request / authorization handshake has been successfully completed, at S615 , the device proceeds to S620 ; otherwise, the device exits method 600 .

[0157] At S620 , the device initiates sidelink communication with one or more Rx UEs.

[0158] In an embodiment, the sidelink communication may be a COT-shared communication that utilizes the remaining MCOT of another (already initiated) sidelink communication.

[0159] Operations S605 to S620 performed by the device may be performed according to the examples described herein. In some implementations, aspects of the operations may be referred to as Figure 5 The device described performs the following.

[0160] Figure 7 A flow chart of a method 700 for supporting sidelink communication according to aspects of the present disclosure is shown. The method 700 may be performed by a device operating as an Rx UE.

[0161] At S705, the device receives a clear request broadcast signal from the Tx UE. The clear request broadcast signal includes a clear request to perform sidelink communication on an unlicensed band.

[0162] In an embodiment, the side link communication may be a COT sharing communication of the remaining MCOT utilizing another (already initiated) side link communication.

[0163] At S705, the device determines whether the clear request broadcast signal identifies the device as a participant in the side link communication. In an embodiment, the determination is performed by comparing an identifier included in the clear request broadcast signal with an identifier associated with the device.

[0164] When the device determines that the clear request broadcast signal identifies the device as a participant in the side link communication, at S710 , the device proceeds to S715 ; otherwise, the device exits the method 600 .

[0165] At S715 , the device determines whether the purge request is authorized.

[0166] In an embodiment, the device determines to grant the clear request based on a strength of a clear request broadcast signal received at the device, an interference level on radio resources associated with sidelink communications at the device, or a combination thereof.

[0167] At S720 , if the device determines that the clear request is authorized, the device proceeds to S725 .

[0168] At S720 , if the device determines that the purge request is not authorized, the device exits the method 700 .

[0169] In an embodiment, if the device determines that the purge request is not authorized, the device sends a signal (such as no signal) to the Tx UE indicating that the purge request is denied before exiting the method 700 .

[0170] At S725, the device sends a clear authorization signal to the Tx UE. The clear authorization signal may include a source-destination identifier corresponding to the source-destination identifier included in the clear request broadcast signal, information about the signal strength of the clear request broadcast signal at the device, information about the amount of interference on the radio resources related to the side link communication present at the device, or a combination thereof.

[0171] Operations S705 to S725 performed by the device may be performed according to the examples described herein. In some implementations, aspects of the operations may be described by reference to Figure 5 The device described performs the following.

[0172] It should be noted that the methods described herein describe possible implementations, and that the operations and steps may be rearranged or otherwise modified, and that other implementations are possible. Furthermore, aspects from two or more methods may be combined.

[0173] The various illustrative blocks and components related to the disclosure herein may be implemented or performed with a general purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination designed to perform the functions described herein. A general purpose processor may be a microprocessor, but in an alternative, the processor may be any processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, a combination of one or more microprocessors with a DSP core, or any other such configuration).

[0174] The functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or sent through a computer-readable medium as one or more instructions or codes. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein may be implemented using software executed by a processor, hardware, firmware, hard wiring, or any combination thereof. Features that implement the functions may also be physically located in various locations, including distribution, such that parts of the functions are implemented at different physical locations.

[0175] Computer readable media include both non-transient computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one place to another. Non-transient storage media can be any available medium that can be accessed by a general or special-purpose computer. For example, and not limitation, non-transient computer readable media can include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compact disk (CD) ROM or other optical disk storage, disk storage or other magnetic storage device, or any other non-transient medium that can be used to carry or store required program code components in the form of instructions or data structures and can be accessed by a general or special-purpose computer or a general or special-purpose processor.

[0176] Any connection may be appropriately referred to as a computer-readable medium. For example, if the software is sent from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology (such as infrared, radio, and microwave), the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technology (such as infrared, radio, and microwave) are all included in the definition of computer-readable media. Disks and optical disks used herein include CDs, laser optical disks, optical disks, digital versatile disks (DVDs), floppy disks, and Blu-ray disks, where disks typically reproduce data magnetically, while optical disks reproduce data optically using lasers. The above combinations are also included within the scope of computer-readable media.

[0177] As used herein, including in the claims, "or" used in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more of which") indicates an inclusive list, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). In addition, the phrase "based on" used herein should not be interpreted as a reference to a closed set of conditions. For example, an example step described as "based on condition A" can be based on condition A and condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "based at least in part on". In addition, as used herein, including in the claims, a "set" may include one or more elements.

[0178] The description set forth herein in conjunction with the accompanying drawings describes example configurations and does not represent that all examples can be implemented or are within the scope of the claims. The term "example" used herein means "used as an example, instance, or illustration," rather than "preferably" or "better than other examples." The detailed description includes specific details for the purpose of providing an understanding of the technology. However, these technologies can be practiced without these specific details. In some cases, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the examples.

[0179] The description herein is intended to enable one of ordinary skill in the art to make or use the present disclosure. Various modifications to the present disclosure will be apparent to one of ordinary skill in the art, and the general principles defined herein may be applied to other variations without departing from the scope of the present disclosure. Therefore, the present disclosure is not limited to the examples and designs described herein, but should be given the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A transmitting (Tx) user equipment (UE), include: processor; as well as a memory coupled to the processor, wherein the processor is configured to: determining whether to perform a clear request / grant handshake prior to performing sidelink communications with one or more receiving (Rx) UEs in an unlicensed band; as well as In response to determining to perform the clear request / authorization handshake: Perform a first clear request / authorization handshake; as well as performing the sidelink communication with the one or more Rx UEs in response to successful completion of the first clear request / grant handshake, wherein the first clear request / grant handshake comprises: sending a first clear request broadcast signal by the Tx UE using radio resources allocated to the sidelink communication, the first clear request broadcast signal indicating the one or more Rx UEs, and The clear request / grant handshake is successfully completed when the Tx UE receives a clear grant signal corresponding to the first clear request broadcast signal from one or more of the Rx UEs. 2 . The Tx UE of claim 1 , wherein indicating the one or more Rx UEs is performed in the first clear-request broadcast signal using one or more source-destination identifiers.

3. The Tx UE according to claim 1, wherein the processor is further configured to enable the Tx UE to determine to perform the clear request / grant handshake based on a level of wireless network congestion, a priority of traffic to be transmitted in the sidelink communication, or a combination thereof. 4 . The Tx UE of claim 1 , wherein the first clear request / grant handshake is not successfully completed when the Tx UE does not receive a clear grant signal corresponding to the first clear request broadcast signal from the one or more Rx UEs before expiration of a timeout interval. 5 . The Tx UE of claim 1 , wherein the first clear request / grant handshake is not successfully completed when the Tx UE receives a signal indicating that the sidelink communication should not be performed from a UE other than the one or more Rx UEs. 6 . The Tx UE according to claim 1 , wherein the processor is further configured to cause the Tx UE to: in response to determining not to perform the clear request / grant handshake, perform the sidelink communication without performing the clear request / grant handshake. 7 . The Tx UE according to claim 1 , wherein the sidelink communication is a channel occupation time (COT) sharing communication.

8. The Tx UE according to claim 7, wherein the processor is further configured to cause the Tx UE to: in response to the first clear request / grant handshake not being successfully completed, perform a second clear request / grant handshake by sending a second clear request broadcast signal, wherein the second clear request broadcast signal indicates one or more Rx UEs other than the one or more Rx UEs indicated in the first clear request broadcast signal.

9. The Tx UE according to claim 1, wherein the clear grant signal include: a source-destination identifier corresponding to a source-destination identifier included in said first clear request broadcast signal, information about the signal strength of the first clear request broadcast signal at the UE that sends the clear grant signal, information about an amount of interference present at the UE that sent the clear grant signal on radio resources associated with the sidelink communication, or a combination thereof.

10. The Tx UE according to claim 1, wherein said first clear request broadcast signal is transmitted on a plurality of transmission beams, wherein the clear grant signal is received using the plurality of transmission beams, and One or more measurements of the respective channel characteristics of the plurality of transmission beams are used to select a transmission beam for subsequent data transmission of the sidelink communication.

11. A receiving (Rx) user equipment (UE), include: processor; as well as a memory coupled to the processor, wherein the processor is configured to: receiving a clear request broadcast signal from a transmitting (Tx) UE regarding sidelink communications in an unlicensed band; determining whether the clear-request broadcast signal identifies the Rx UE as participating in the sidelink communication; as well as In response to determining that the clear-request broadcast signal identifies the Rx UE as participating in the sidelink communication, determining whether the Tx UE is authorized to perform clearing of the sidelink communication. 12 . The Rx UE according to claim 11 , wherein the processor is further configured to cause the Rx UE to: in response to determining that the Tx UE is authorized to perform the clearing of the sidelink communication, send a clear grant signal to the Tx UE.

13. The Rx UE according to claim 12, wherein the clear grant signal include: An identifier corresponding to an identifier included in a clear request broadcast signal, information about a received signal strength of the clear request broadcast signal, information about interference existing at the Rx UE, or a combination thereof.

14. The Rx UE according to claim 12, wherein the clear grant signal is sent to the Tx UE include: A listen-before-talk operation is performed before sending the clear-grant signal to the Tx UE.

15. The Rx UE of claim 11, wherein determining whether the clear request broadcast signal identifies the Rx UE as participating in the sidelink communication include: An identifier included in the clear request broadcast signal is compared with an identifier associated with the Rx UE. 16 . The Rx UE according to claim 11 , wherein the processor is further configured to cause the Rx UE to: in response to determining that the Tx UE is not authorized to perform the clearing of the sidelink communication, send a signal to the Tx UE indicating that the sidelink communication is not performed.

17. The Rx UE according to claim 11, wherein the side link communication is a channel occupation time (COT) sharing communication.

18. The Rx UE according to claim 11, wherein the processor is further configured to cause the Rx UE to: terminate communication performed by the Rx UE, perform a backoff operation, or both in response to determining that the clear request broadcast signal does not identify the Rx UE as participating in the sidelink communication.

19. The Rx UE according to claim 11, wherein the processor is further configured to cause the Rx UE to: in response to determining that the clear request broadcast signal does not identify the Rx UE as participating in the side link communication, and when the priority indicated in the clear request broadcast signal is lower than the priority of the pending business of the Rx UE, send a signal to the Tx UE to indicate that the Tx UE should not perform the side link communication.

20. A method performed by a transmitting (Tx) user equipment (UE), the method include: determining whether to perform a clear request / grant handshake prior to performing sidelink communications with one or more receiving (Rx) UEs in an unlicensed band; as well as In response to determining to perform the clear request / authorization handshake: performing a first clear request / authorization handshake; and in response to successful completion of the first clear request / grant handshake, performing the sidelink communication with the one or more Rx UEs, wherein the first clear request / grant handshake comprises: the Tx UE sending a first clear request broadcast signal using radio resources allocated to the sidelink communication, the first clear request broadcast signal indicating the one or more Rx UEs, and The clear request / grant handshake is successfully completed when the Tx UE receives a clear grant signal corresponding to the first clear request broadcast signal from one or more of the Rx UEs.