Techniques for recovering sidelink transmissions within shared channel occupancy time

Abstract

Methods, systems, and devices for wireless communication are described. A user equipment (UE) performs a first channel access procedure for accessing a channel occupancy time (COT) within a sidelink channel. The UE transmits a second stage sidelink control information (SCI) message (SCI-2) including COT sharing information (COT-SI) for sharing the COT with other devices, and transmits a first sidelink message within a first portion of the COT. The UE identifies a second sidelink message expected to be received within a second portion of the COT, and performs a second channel access procedure for accessing the COT after the second sidelink message is identified based on the second sidelink message being expected to be within a resource set reserved for the second sidelink message. The UE then transmits a third sidelink message within a third portion of the COT based on completion of the second channel access procedure.

Description

[0001] Cross-referencing

[0002] This patent application claims priority to U.S. Patent Application No. 18 / 790,221, filed July 31, 2024, entitled “TECHNIQUES FORRESUMING SIDELINK TRANSMISSIONS WITHIN A SHARED CHANNEL OCCUPANCY TIME,” which claims the benefit of U.S. Provisional Patent Application No. 63 / 586,996, filed September 29, 2023, entitled “TECHNIQUES FORRESUMING SIDELINK TRANSMISSIONS WITHIN A SHARED CHANNEL OCCUPANCY TIME,” each of which is assigned to the assignee of this application and each of which is expressly incorporated herein by reference. Technical Field

[0003] The following discussion relates to wireless communications, including techniques for resuming sidelink transmission during the Shared Channel Occupied Time (COT). Background Technology

[0004] Wireless communication systems are widely deployed to provide various types of communication content, such as voice, video, packet data, message sending and receiving, broadcasting, and so on. These systems can support communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multiple access systems include fourth-generation (4G) systems (such as Long Term Evolution (LTE) systems, LTE-A Advanced (LTE-A) systems, or LTE-A Pro systems) and fifth-generation (5G) systems (which may be referred to as New Radio (NR) systems). These systems may employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal FDMA (OFDMA), or Discrete Fourier Transform Extended Orthogonal Frequency Division Multiplexing (DFT-S-OFDM). A wireless multiple access communication system may include one or more base stations, each supporting wireless communication of communication devices, which may be referred to as User Equipment (UE).

[0005] In the context of unlicensed spectrum, wireless devices can be configured to perform a channel access procedure to gain access to the Channel Occupied Time (COT), during which the device can perform communications. In some cases, wireless devices may be able to share access to the COT. Summary of the Invention

[0006] A method for wireless communication by a first user equipment (UE) is described. The method may include monitoring a sidelink channel as part of a first channel access procedure for accessing a channel occupied time (COT) within a sidelink channel; transmitting a second-phase sidelink control information (SCI) message including COT sharing information (COT-SI) for sharing the COT with one or more additional UEs; transmitting a first sidelink message within a first portion of the COT; identifying a second sidelink message expected to be received within a second portion of the COT based on the transmission of the second-phase SCI message; performing a second channel access procedure for accessing the COT after identifying the second sidelink message based on the second sidelink message being expected to be within a resource set of sidelink channels reserved for the second sidelink message; and transmitting a third sidelink message within a third portion of the COT based on the completion of the second channel access procedure.

[0007] A first UE for wireless communication is described. The first UE may include one or more memories storing processor-executable code, and one or more processors coupled to the one or more memories. The one or more processors may operate individually or collectively to execute code to cause the first UE to monitor a sidelink channel as part of a first channel access procedure for accessing a COT within a sidelink channel; transmit a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs; transmit a first sidelink message within a first portion of the COT; identify a second sidelink message expected to be received within a second portion of the COT based on the transmission of the second-phase SCI message; perform a second channel access procedure for accessing the COT after identifying the second sidelink message based on the second sidelink message being expected to be received within a resource set of sidelink channels reserved for the second sidelink message; and transmit a third sidelink message within a third portion of the COT based on the completion of the second channel access procedure.

[0008] Another first UE for wireless communication is described. This first UE may include components for monitoring a sidelink channel as part of a first channel access procedure for accessing a COT within a sidelink channel; components for transmitting a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs; components for transmitting a first sidelink message within a first portion of the COT; components for identifying a second sidelink message expected to be received within a second portion of the COT based on transmitting the second-phase SCI message; components for performing a second channel access procedure for accessing the COT after identifying the second sidelink message based on the second sidelink message being expected to be within a resource set of sidelink channels reserved for the second sidelink message; and components for transmitting a third sidelink message within a third portion of the COT based on the completion of the second channel access procedure.

[0009] A non-transitory computer-readable medium storing code for wireless communication is described. The code may include instructions executable by a processor to: monitor a sidelink channel as part of a first channel access procedure for accessing a COT within a sidelink channel; transmit a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs; transmit a first sidelink message within a first portion of the COT; identify a second sidelink message expected to be received within a second portion of the COT based on the transmission of the second-phase SCI message; perform a second channel access procedure for accessing the COT after identifying the second sidelink message based on the second sidelink message being expected to be within a resource set of sidelink channels reserved for the second sidelink message; and transmit a third sidelink message within a third portion of the COT based on the completion of the second channel access procedure.

[0010] The methods described herein, examples of the first UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for sending a fourth sidelink message to a second UE, wherein a resource set may be reserved for a feedback message in response to the fourth sidelink message, the second sidelink message including the feedback message, and wherein a second channel access procedure may be performed after the second sidelink message is identified based on the feedback message being expected to be within the resource set reserved for the feedback message.

[0011] In the methods described herein, in some examples of the first UE and non-transitory computer-readable media, a second-stage SCI message including COT-SI may be sent to the second UE, and the second channel access procedure may be performed after identifying the second sidelink message based on sending COT-SI to the second UE and a feedback message identifying the second UE.

[0012] The methods described herein, examples of the first UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for identifying satisfaction of a matching identifier criterion based on a first identifier within a fourth sidelink message and a second identifier within a COT-SI, wherein the second channel access procedure may be performed after identifying the second sidelink message based on satisfaction of the matching identifier criterion.

[0013] In the methods described herein, and in some examples of the first UE and non-transitory computer-readable media, the first identifier and the second identifier include logical identifiers associated with the second-phase SCI message.

[0014] The methods described herein, examples of the first UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for receiving a fourth sidelink message from a second UE, wherein the fourth sidelink message reserves a resource set for the second sidelink message, and wherein the second channel access procedure may be performed after the second sidelink message is identified based on the second sidelink message being expected to be within the resource set reserved by the fourth sidelink message.

[0015] In the methods described herein, and in some examples of the first UE and non-transitory computer-readable media, the fourth sidechain message includes a first-stage SCI message.

[0016] In some examples of the methods described herein, the first UE, and non-transitory computer-readable media, a second-stage SCI message including COT-SI may be sent to the second UE, and the second channel access procedure may be performed after identifying the second sidelink message based on sending COT-SI to the second UE and identifying the second sidelink message from the second UE.

[0017] The methods described herein, examples of the first UE, and some examples of non-transitory computer-readable media may also include operations, features, components, or instructions for identifying satisfaction of a matching identifier criterion based on a first identifier within a fourth sidelink message and a second identifier within a COT-SI, wherein the second channel access procedure may be performed after identifying the second sidelink message based on satisfaction of the matching identifier criterion.

[0018] In the methods described herein, and in some examples of the first UE and non-transitory computer-readable media, the first identifier and the second identifier include logical identifiers associated with the second-phase SCI message.

[0019] In the methods described herein, and in some examples of the first UE and non-transitory computer-readable media, the second sidelink message includes a sidelink shared channel message and a sidelink control channel message.

[0020] The methods described herein, examples of the first UE, and non-transitory computer-readable media may also include operations, features, components, or instructions for avoiding the transmission of sidelink messages within the second part of the COT based on a resource set that reserves a sidelink channel for second sidelink messages within the second part of the COT, wherein the second sidelink messages can be received based on avoiding the transmission of sidelink messages within the second part of the COT.

[0021] The methods described herein, and some examples of the first UE and non-transitory computer-readable media, may also include operations, features, components, or instructions for receiving second-sidelink messages within a resource set reserved for second-sidelink messages to avoid processing information included in second-stage SCI messages.

[0022] In the methods described herein, and in some examples of the first UE and non-transitory computer-readable medium, the first channel access procedure includes a type 1 channel access procedure, and the second channel access procedure includes a type 2 channel access procedure. Attached Figure Description

[0023] Figure 1 An example of a wireless communication system is shown that supports techniques for resuming sidelink transmission during the shared channel occupancy time (COT) according to one or more aspects of this disclosure.

[0024] Figure 2 An example of a wireless communication system supported by one or more aspects of this disclosure for resuming sidelink transmission within a shared COT is shown.

[0025] Figure 3 An example of resource configuration supporting a technique for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown.

[0026] Figure 4 An example of a process flow supporting a technique for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown.

[0027] Figure 5 and Figure 6 A block diagram of an apparatus supporting a technique for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown.

[0028] Figure 7 A block diagram of a communication manager supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown.

[0029] Figure 8A diagram of a system including a device supporting technology for resuming sidelink transmission within a shared COT is shown, according to one or more aspects of this disclosure.

[0030] Figure 9 A flowchart illustrating a method for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0031] In some wireless communication systems, wireless devices may be able to communicate via licensed spectrum, unlicensed spectrum, or both. In the context of unlicensed spectrum, a wireless device may be configured to perform a channel access procedure to gain access to a channel occupied time (COT), during which the device can perform communication. In some cases, wireless devices may be able to share access to the COT. For example, a first user equipment (UE) may successfully perform a channel access procedure to gain access to the COT and may share the COT with a second UE. In this example, the first UE may transmit sidelink communication within the COT and stop transmitting at some point, allowing the second UE to transmit within the COT. However, according to some conventional techniques, in order for the first UE to resume transmission within the COT, the first UE is expected to fully decode messages received from the second UE and perform a new channel access procedure before it can resume transmission within the COT. The requirement to fully decode messages and perform a new channel access procedure can increase the latency for the first UE to resume communication within the COT. Furthermore, other wireless devices may successfully gain access to the COT before the first UE decodes the message and successfully executes the channel access procedure, thereby causing the first UE to lose access to the COT.

[0032] Therefore, aspects of this disclosure relate to techniques that enable wireless devices reserving and sharing a COT (e.g., "reserved" devices) to verify received communications and efficiently resume transmission within the COT. Specifically, aspects of this disclosure relate to techniques that enable reserved UEs to share a COT with other devices and perform channel access procedures to resume transmission within the COT without fully decoding messages received from other devices sharing the COT.

[0033] In some implementations, a first UE (e.g., a "reserved" UE) may obtain access to the COT and share the COT with a second UE. The first / serving UE may send messages within the COT and may cease sending within the COT to allow the second UE to send messages within the COT. In this example, as long as the message is an "expected" message, the first UE may be able to avoid fully decoding messages received from the second UE within the COT (and directly proceed to perform a channel access procedure to resume sending within the COT). Additionally or alternatively, the UE may initiate a decoding procedure to decode the received message, but may initiate (and / or complete) the channel access procedure before the decoding procedure is finished (e.g., without fully decoding the message).

[0034] The term "expected" message can refer to a message received within previously reserved or allocated resources. For example, an "expected" message may include a feedback message from a second UE in response to a sidelink message previously sent by a first UE, wherein there is a relationship (e.g., a pre-configured relationship) between the resources used to send the sidelink message and the resources used to receive the feedback message. As another example, an "expected" message may include a sidelink message previously scheduled by a second UE. In such cases, upon determining that the received message is an "expected" message (e.g., received on previously reserved or allocated resources), the first UE may directly jump to performing a channel access procedure to resume communication on the COT without fully decoding the expected message.

[0035] The aspects of this disclosure are first described in the context of a wireless communication system. Additional aspects of this disclosure are described in the context of example resource configurations and example process flows. The aspects of this disclosure are also illustrated and described with reference to apparatus diagrams, system diagrams, and flowcharts relating to techniques for resuming sidelink transmission within a shared COT.

[0036] Figure 1 An example of a wireless communication system 100 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. The wireless communication system 100 may include one or more network entities 105, one or more UEs 115, and a core network 130. In some examples, the wireless communication system 100 may be a Long Term Evolution (LTE) network, an Advanced LTE (LTE-A) network, an LTE-A Pro network, a New Radio (NR) network, or a network operating under other systems and radio technologies, including future systems and radio technologies not explicitly mentioned herein.

[0037] Network entity 105 may be distributed across a geographical area to form wireless communication system 100, and may include devices employing different forms or having different capabilities. In various examples, network entity 105 may be referred to as a network element, mobility element, radio access network (RAN) node, or network equipment, among other designations. In some examples, network entity 105 and UE 115 may wirelessly communicate via one or more communication links 125 (e.g., radio frequency (RF) access links). For example, network entity 105 may support coverage area 110 (e.g., a geographical coverage area) within which UE 115 and network entity 105 may establish one or more communication links 125. Coverage area 110 may be an example of a geographical area within which network entity 105 and UE 115 may support the transmission of signals according to one or more radio access technologies (RATs).

[0038] UE 115 can be distributed throughout the coverage area 110 of wireless communication system 100, and each UE 115 can be stationary or mobile, or stationary and mobile at different times. UE 115 can be devices in different forms or with different capabilities. Figure 1 Some example UE 115s are illustrated herein. The UE 115 described herein can be able to support various types of devices (such as, e.g., ...). Figure 1 It communicates with other UEs (115 or network entity 105) as shown.

[0039] As described herein, nodes of the wireless communication system 100 (which may be referred to as network nodes or wireless nodes) may be network entity 105 (e.g., any network entity described herein), UE 115 (e.g., any UE described herein), network controller, apparatus, device, computing system, one or more components, or another suitable processing entity configured to perform any of the techniques described herein. For example, a node may be UE 115. Alternatively, a node may be network entity 105. Furthermore, a first node may be configured to communicate with a second or third node. In one aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be UE 115. In another aspect of this example, the first node may be UE 115, the second node may be network entity 105, and the third node may be network entity 105. In other aspects of this example, the first node, the second node, and the third node may be different from these examples. Similarly, references to UE 115, network entity 105, device, equipment, computing system, etc., may include disclosures of UE 115, network entity 105, device, equipment, computing system, etc., as nodes. For example, a disclosure that UE 115 is configured to receive information from network entity 105 also discloses that a first node is configured to receive information from a second node.

[0040] In some examples, network entity 105 may communicate with core network 130, communicate with each other, or both. For example, network entity 105 may communicate with core network 130 via one or more backhaul communication links 120 (e.g., according to S1, N2, N3, or other interface protocols). In some examples, network entities 105 may communicate with each other directly (e.g., directly between network entities 105) or indirectly (e.g., via core network 130) via backhaul communication links 120 (e.g., according to X2, Xn, or other interface protocols). In some examples, network entities 105 may communicate with each other via midhaul communication link 162 (e.g., according to midhaul interface protocol) or fronthaul communication link 168 (e.g., according to fronthaul interface protocol) or any combination thereof. Backhaul communication link 120, midhaul communication link 162, or fronthaul communication link 168 may be or include one or more wired links (e.g., electrical links, fiber optic links), one or more wireless links (e.g., radio links, wireless optical links), etc., or various combinations thereof. UE 115 can communicate with core network 130 via communication link 155.

[0041] One or more network entities in network entity 105 described herein may include or be referred to as base station 140 (e.g., transceiver base station, radio base station, NR base station, access point, radio transceiver, node B, eNodeB (eNB), next-generation node B or gigabit node B (any of which may be referred to as gNB), 5G NB, next-generation eNB (ng-eNB), home node B, home evolution node B, or other suitable terms). In some examples, network entity 105 (e.g., base station 140) may be implemented in an aggregated (e.g., monolithic, standalone) base station architecture that may be configured to utilize a protocol stack that is physically or logically integrated within a single network entity 105 (e.g., a single RAN node, such as base station 140).

[0042] In some examples, network entity 105 may be implemented in a decomposed architecture (e.g., a decomposed base station architecture, a decomposed RAN architecture) that can be configured to utilize protocol stacks physically or logically distributed across two or more network entities 105, such as an integrated access backhaul (IAB) network, an open RAN (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance), or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN)). For example, network entity 105 may include one or more of the following: a central unit (CU) 160, a distributed unit (DU) 165, a radio unit (RU) 170, a RAN intelligent controller (RIC) 175 (e.g., a near real-time RIC, a non-real-time RIC), a service management and orchestration (SMO) 180 system, or any combination thereof. 170 may also be referred to as a radio headend, intelligent radio headend, remote radio headend (RRH), remote radio unit (RRU), or transmit / receive point (TRP). One or more components of network entity 105 in a decomposed RAN architecture may be co-located, or one or more components of network entity 105 may be located in distributed locations (e.g., separate physical locations). In some examples, one or more network entities 105 in a decomposed RAN architecture may be implemented as virtual units (e.g., virtual CU (VCU), virtual DU (VDU), virtual RU (VRU)).

[0043] The functional splitting among CU 160, DU 165, and RU 170 is flexible and can support different functionalities depending on which functions (e.g., network layer functions, protocol layer functions, baseband functions, RF functions, and any combination thereof) are performed at CU 160, DU 165, or RU 170. For example, a protocol stack functional splitting can be used between CU 160 and DU 165, allowing CU 160 to support one or more layers of the protocol stack, and DU 165 to support one or more different layers of the protocol stack. In some examples, CU 160 can host higher protocol layer (e.g., Layer 3 (L3), Layer 2 (L2)) functionalities and signaling (e.g., Radio Resource Control (RRC), Serving Data Adaptation Protocol (SDAP), Packet Data Convergence Protocol (PDCP)). CU 160 can connect to one or more DU 165 or RU 170, and one or more DU 165 or RU 170 can host lower protocol layers, such as Layer 1 (L1) (e.g., Physical (PHY) layer) or L2 (e.g., Radio Link Control (RLC) layer, Medium Access Control (MAC) layer) functionality and signaling, and each can be at least partially controlled by CU 160. Additionally or alternatively, a protocol stack functional split can be employed between DU 165 and RU 170, such that DU 165 can support one or more layers of the protocol stack, and RU 170 can support one or more different layers of the protocol stack. DU 165 can support one or more different cells (e.g., via one or more RU 170). In some cases, functional decomposition between CU 160 and DU 165, or between DU 165 and RU 170, can be performed within the protocol layer (e.g., some functions of the protocol layer can be performed by one of CU 160, DU 165, or RU 170, while other functions of the protocol layer can be performed by different of CU 160, DU 165, or RU 170). CU 160 can be further functionally decomposed into CU control plane (CU-CP) and CU user plane (CU-UP) functions. CU 160 can be connected to one or more DU 165 via midhaul communication link 162 (e.g., F1, F1-c, F1-u), and DU 165 can be connected to one or more RU 170 via fronthaul communication link 168 (e.g., open fronthaul (FH) interface). In some examples, the midhaul communication link 162 or the fronthaul communication link 168 may be implemented based on the interfaces (e.g., channels) between the layers of the protocol stack, which are supported by the corresponding network entities 105 communicating via such communication links.

[0044] In some wireless communication systems (e.g., wireless communication system 100), the infrastructure and spectrum resources for radio access may support wireless backhaul link capabilities to supplement wired backhaul connections, thereby providing an IAB network architecture (e.g., to core network 130). In some cases, in an IAB network, one or more network entities 105 (e.g., IAB node 104) may be partially controlled by each other. One or more IAB nodes 104 may be referred to as donor entities or IAB donors. One or more DU 165s or one or more RU 170s may be partially controlled by one or more CU 160s associated with donor network entity 105 (e.g., donor base station 140). One or more donor network entities 105 (e.g., IAB donors) may communicate with one or more additional network entities 105 (e.g., IAB node 104) via supported access and backhaul links (e.g., backhaul communication link 120). IAB node 104 may include an IAB mobile terminal (IAB-MT) controlled (e.g., scheduled) by a DU 165 of a coupled IAB donor. The IAB-MT may include a separate set of antennas for relaying communication with UE 115, or may share the same antennas (e.g., those of RU 170) for access to IAB node 104 via DU 165 of IAB node 104. (e.g., referred to as a virtual IAB-MT (vIAB-MT)). In some examples, IAB node 104 may include a DU 165 that supports communication links with additional entities (e.g., IAB node 104, UE 115) within a relay chain or configuration (e.g., downstream) of the access network. In such cases, one or more components of the decomposed RAN architecture (e.g., one or more IAB nodes 104 or components of IAB node 104) may be configured to operate according to the techniques described herein.

[0045] For example, the access network (AN) or RAN may include communication between an access node (e.g., an IAB donor), IAB node 104, and one or more UEs 115. The IAB donor may facilitate connectivity between the core network 130 and the AN (e.g., via a wired or wireless connection to the core network 130). That is, an IAB donor may refer to a RAN node having a wired or wireless connection to the core network 130. The IAB donor may include a CU 160 and at least one DU 165 (e.g., and RU 170), in which case the CU 160 may communicate with the core network 130 via an interface (e.g., a backhaul link). The IAB donor and IAB node 104 may communicate via an F1 interface according to a protocol defining the signaling messages (e.g., the F1 AP protocol). Additionally or alternatively, the CU 160 may communicate with the core network via an interface (which may be a part of the backhaul link) and may communicate with other CU 160s (e.g., a CU 160 associated with an alternative IAB donor) via an Xn-C interface (which may be a part of the backhaul link).

[0046] IAB node 104 may refer to a RAN node that provides IAB functionality (e.g., access for UE 115, radio self-backhaul capability). DU 165 may act as a distributed scheduling node toward child nodes associated with IAB node 104, and IAB-MT may act as a scheduled node toward a parent node associated with IAB node 104. That is, an IAB donor may be referred to as a parent node communicating with one or more child nodes (e.g., an IAB donor may relay UE transmissions through one or more other IAB nodes 104). Additionally or alternatively, depending on the AN's relay chain or configuration, IAB node 104 may also be referred to as a parent node or child node of other IAB nodes 104. Therefore, the IAB-MT entity of IAB node 104 may provide a Uu interface for child IAB node 104 to receive signaling from parent IAB node 104, and the DU interface (e.g., DU 165) may provide a Uu interface for parent IAB node 104 to signal to child IAB node 104 or UE 115.

[0047] For example, IAB node 104 may be referred to as a parent node supporting communication to child IAB nodes, or as a child IAB node associated with an IAB donor, or both. An IAB donor may include a CU 160 having a wired or wireless connection to core network 130 (e.g., backhaul communication link 120) and may act as a parent node of IAB node 104. For example, the IAB donor's DU 165 may relay transmissions to UE 115 via IAB node 104, or may signal transmissions directly to UE 115, or both. The IAB donor's CU 160 may signal the establishment of a communication link to IAB node 104 via an F1 interface, and IAB node 104 may schedule transmissions via DU 165 (e.g., transmissions relayed from the IAB donor to UE 115). That is, data may be relayed to and from IAB node 104 via signaling through the NR Uu interface of the MT to IAB node 104. Communication with IAB node 104 can be scheduled by DU 165 of the IAB donor, and communication with IAB node 104 can be scheduled by DU 165 of IAB node 104.

[0048] In the context of applying the techniques described herein to a decomposed RAN architecture, one or more components of the decomposed RAN architecture may be configured to support techniques as described herein for resuming sidelink transmission within a shared COT. For example, some operations described as being performed by UE 115 or network entity 105 (e.g., base station 140) may additionally or alternatively be performed by one or more components of the decomposed RAN architecture (e.g., IAB node 104, DU 165, CU 160, RU 170, RIC 175, SMO 180).

[0049] UE 115 may include or be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or any other suitable term, wherein "device" may also be referred to as a cell, station, terminal, or client, etc. UE 115 may also include or be referred to as a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 may include or be referred to as a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or machine-type communication (MTC) device, etc., which may be implemented in various objects such as appliances or vehicles, meters, etc.

[0050] The UE 115 described herein can communicate with various types of devices, such as other UEs 115 that sometimes act as relays, network entities 105, and network equipment including macro eNBs or gNBs, small cell eNBs or gNBs, or relay base stations, etc. Figure 1 As shown.

[0051] UE 115 and network entity 105 can wirelessly communicate with each other via one or more communication links 125 (e.g., access links) using resources associated with one or more carriers. The term "carrier" can refer to a set of RF spectrum resources having a physical layer structure defined for supporting communication link 125. For example, a carrier for communication link 125 may include a portion of the RF spectrum band (e.g., a bandwidth portion (BWP)) operating according to one or more physical layer channels for a given radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR). Each physical layer channel may carry acquisition signaling (e.g., synchronization signals, system information), control signaling coordinating carrier operation, user data, or other signaling. Wireless communication system 100 may support communication with UE 115 using carrier aggregation or multi-carrier operation. Depending on the carrier aggregation configuration, UE 115 may be configured using multiple downlink component carriers and one or more uplink component carriers. Carrier aggregation may be used in conjunction with both frequency division duplex (FDD) component carriers and time division duplex (TDD) component carriers. Communication between network entity 105 and other devices can refer to communication between these devices and any part of network entity 105 (e.g., entity, sub-entity). For example, the terms “send,” “receive,” or “communicate” when referring to network entity 105 can refer to any part of the RAN’s network entity 105 (e.g., base station 140, CU160, DU 165, RU 170) communicating with another device (e.g., directly or via one or more other network entities 105).

[0052] In some examples, such as in carrier aggregation configurations, a carrier may also have acquisition signaling or control signaling to coordinate the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified according to a channel grating used for discovery by UE 115. A carrier may operate in standalone mode, in which case initial acquisition and connection can be performed by UE 115 via that carrier, or the carrier may operate in non-standalone mode, in which case different carriers (e.g., the same or different radio access technologies) are used to anchor the connection.

[0053] The communication link 125 shown in the wireless communication system 100 may include downlink transmission (e.g., forward link transmission) from network entity 105 to UE 115, uplink transmission (e.g., return link transmission) from UE 115 to network entity 105, or both, as well as other transmission configurations. A carrier may carry downlink communication or uplink communication (e.g., in FDD mode), or may be configured to carry both downlink and uplink communication (e.g., in TDD mode).

[0054] A carrier may be associated with a specific bandwidth of the RF spectrum, and in some examples, the carrier bandwidth may be referred to as the carrier or the “system bandwidth” of the wireless communication system 100. For example, the carrier bandwidth may be one bandwidth in a set of bandwidths for a particular radio access technology (e.g., 1.4 MHz, 3 MHz, 5 MHz, 10 MHz, 15 MHz, 20 MHz, 40 MHz, or 80 MHz). Devices of the wireless communication system 100 (e.g., network entity 105, UE 115, or both) may have hardware configurations that support communication using a specific carrier bandwidth, or may be configured to support communication using one carrier bandwidth in a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network entity 105 or UE 115 that supports concurrent communication using carriers associated with multiple carrier bandwidths. In some examples, each served UE 115 may be configured to operate using a portion (e.g., subband, BWP) or all of the carrier bandwidth.

[0055] The signal waveform transmitted via a carrier may include multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques, such as orthogonal frequency division multiplexing (OFDM) or discrete Fourier transform extended OFDM (DFT-S-OFDM)). In a system employing MCM, a resource element may refer to a resource of one symbol period (e.g., the duration of one modulation symbol) and one subcarrier, in which case the symbol period and subcarrier spacing may be inversely related. The number of bits carried by each resource element may depend on the modulation scheme (e.g., the order of the modulation scheme, the decoding rate of the modulation scheme, or both), such that a relatively high number of resource elements (e.g., in the transmission duration) and a relatively high modulation scheme order may correspond to a relatively high communication rate. Wireless communication resources may refer to a combination of RF spectrum resources, temporal resources, and spatial resources (e.g., spatial layers or beams), and the use of multiple spatial resources may increase the data rate or data integrity used for communication with UE 115.

[0056] It can support one or more sets of parameters for a carrier, and the set of parameters may include subcarrier spacing ( (and cyclic prefix). A carrier can be divided into one or more BWPs with the same or different sets of parameters. In some examples, multiple BWPs can be used to configure UE 115. In some examples, a single BWP of a carrier can be active at a given time, and the communication of UE 115 can be constrained to one or more active BWPs.

[0057] The time interval for network entity 105 or UE 115 can be expressed as a multiple of a basic time unit, such as the sampling period. seconds, of which It can represent the supported subcarrier spacing, and This can represent the supported Discrete Fourier Transform (DFT) size. The time interval of the communication resources can be organized according to radio frames, each with a specified duration (e.g., 10 milliseconds (ms)). Each radio frame can be identified by a System Frame Number (SFN) (e.g., ranging from 0 to 1023).

[0058] Each frame may include multiple consecutively numbered subframes or time slots, and each subframe or time slot may have the same duration. In some examples, a frame may (e.g., in the time domain) be divided into subframes, and each subframe may be further divided into a number of time slots. Alternatively, each frame may include a variable number of time slots, and the number of time slots may depend on the subcarrier spacing. Each time slot may include a number of symbol periods (e.g., depending on the length of the cyclic prefix appended to each symbol period). In some wireless communication systems 100, time slots may be further divided into multiple micro-time slots associated with one or more symbols. Excluding the cyclic prefix, each symbol period may be associated with one or more (e.g., The duration of a symbol period is associated with a (number) sampling period. The duration of a symbol period can depend on the subcarrier spacing or the operating frequency band.

[0059] A subframe, time slot, micro-time slot, or symbol can be the smallest scheduling unit of the wireless communication system 100 (e.g., in the time domain) and can be referred to as a transmission time interval (TTI). In some examples, the duration of the TTI (e.g., the number of symbol periods in the TTI) can be variable. Additionally or alternatively, the smallest scheduling unit of the wireless communication system 100 can be dynamically selected (e.g., in a burst of shortened TTIs (sTTIs)).

[0060] Depending on the technology, carriers can be used to multiplex physical channels for communication. One or more of Time Division Multiplexing (TDM), Frequency Division Multiplexing (FDM), or hybrid TDM-FDM techniques can be used, for example, to multiplex physical control channels and physical data channels for signaling via a downlink carrier. The control region of the physical control channel (e.g., a control resource set (CORESET)) can be defined by a set of symbol periods and can extend across the system bandwidth of the carrier or a subset of that bandwidth. One or more control regions (e.g., CORESET) can be configured for a set of UEs 115. For example, one or more UEs in UE 115 can monitor or search control regions to obtain control information based on one or more search space sets, and each search space set can include one or more control channel candidates in one or more aggregation levels arranged in a concatenated manner. The aggregation level of control channel candidates can refer to the amount of control channel resources (e.g., control channel elements (CCEs)) associated with coded information for a control information format having a given payload size. The search space set may include: a common search space set configured to transmit control information to multiple UEs 115, and a UE-specific search space set used to transmit control information to a specific UE 115.

[0061] In some examples, network entity 105 (e.g., base station 140, RU 170) may be mobile, and thus provide communication coverage to mobile coverage areas 110. In some examples, different coverage areas 110 associated with different technologies may overlap, but the different coverage areas 110 may be supported by the same network entity 105. In some other examples, overlapping coverage areas 110 associated with different technologies may be supported by different network entities 105. The wireless communication system 100 may include, for example, a heterogeneous network in which different types of network entities 105 use the same or different radio access technologies to provide coverage for various coverage areas 110.

[0062] Wireless communication system 100 may be configured to support ultra-reliable communication or low-latency communication, or various combinations thereof. For example, wireless communication system 100 may be configured to support ultra-reliable low-latency communication (URLLC). UE 115 may be designed to support ultra-reliable or low-latency or critical functions. Ultra-reliable communication may include private or group communication and may be supported by one or more services, such as push-to-talk, video, or data. Support for ultra-reliable, low-latency functions may include prioritization of services, and such services may be used for public safety or general business applications. The terms “ultra-reliable,” “low-latency,” and “ultra-reliable low-latency” are used interchangeably herein.

[0063] In some examples, UE 115 may be configured to support direct communication with other UE 115s via device-to-device (D2D) communication link 135 (e.g., according to peer-to-peer (P2P), D2D, or sidelink protocols). In some examples, one or more UE 115s performing D2D communication in a group may be within the coverage area 110 of network entity 105 (e.g., base station 140, RU 170), which may support aspects of such D2D communication configured (e.g., scheduled by network entity 105). In some examples, one or more UE 115s in such a group may be outside the coverage area 110 of network entity 105, or may otherwise be unable or not configured to receive transmissions from network entity 105. In some examples, the group of UE 115s communicating via D2D communication may support a one-to-many (1:M) system, where each UE 115 transmits to each of the other UE 115s in the group. In some examples, network entity 105 may facilitate the scheduling of resources used for D2D communication. In other examples, D2D communication may be performed between UEs 115 without involving network entity 105.

[0064] In some systems, the D2D communication link 135 may be an example of a communication channel (such as a sidelink communication channel) between vehicles (e.g., UE 115). In some examples, vehicles may communicate using vehicle-to-vehicle (V2X) communication, vehicle-to-vehicle (V2V) communication, or a combination of these. Vehicles may signal information related to traffic conditions, signal control, weather, safety, emergencies, or any other information relevant to the V2X system. In some examples, vehicles in a V2X system may communicate with roadside infrastructure (such as roadside units), or communicate with the network via one or more network nodes (e.g., network entity 105, base station 140, RU 170) using vehicle-to-network (V2N) communication, or both.

[0065] Core network 130 provides user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC) or a 5G core (5GC), and may include at least one control plane entity (e.g., a Mobility Management Entity (MME), Access and Mobility Management Function (AMF)) for managing access and mobility, and at least one user plane entity (e.g., a Serving Gateway (S-GW), Packet Data Network (PDN) Gateway (P-GW), or User Plane Function (UPF)) for routing packets or interconnecting to external networks. The control plane entity manages non-access stratum (NAS) functions, such as mobility, authentication, and bearer management of UE 115 served by network entity 105 (e.g., base station 140) associated with core network 130. User IP packets can be delivered through the user plane entity, which provides IP address allocation and other functions. The user plane entity may connect to one or more network operator IP services 150. IP services 150 may include access to the Internet, intranets, IP Multimedia Subsystem (IMS), or packet-switched streaming services.

[0066] Wireless communication system 100 can operate using one or more frequency bands in the range of 300 MHz to 300 GHz. Generally, the region from 300 MHz to 3 GHz is referred to as the Ultra High Frequency (UHF) region or decimeter band because the wavelength range is approximately one decimeter to one meter in length. UHF waves may be blocked or redirected by buildings and environmental features (which may be referred to as clusters), but these waves are sufficient to penetrate structures so that macrocells can provide service to UE 115 located indoors. Compared to communication using smaller frequencies and longer waves in the High Frequency (HF) or Very High Frequency (VHF) portions of the spectrum below 300 MHz, communication using UHF waves can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0067] The wireless communication system 100 can also operate using the ultra-high frequency (SHF) region (also known as the centimeter band) in the range of 3 GHz to 30 GHz or the extremely high frequency (EHF) region (e.g., 30 GHz to 300 GHz) (also known as the millimeter band). In some examples, the wireless communication system 100 can support millimeter-wave (mmW) communication between the UE 115 and network entity 105 (e.g., base station 140, RU 170), and the EHF antennas of the corresponding devices can be smaller and more closely spaced than UHF antennas. In some examples, such techniques facilitate the use of antenna arrays within the device. However, compared to SHF or UHF transmissions, EHF transmissions may experience even greater attenuation and shorter range. The techniques disclosed herein can be adopted across transmissions using one or more different frequency regions, and the frequency band usage specified across these frequency regions may vary by country or regulatory authority.

[0068] Wireless communication system 100 may utilize licensed and unlicensed RF spectrum bands. For example, wireless communication system 100 may use unlicensed frequency bands (such as the 5 GHz Industrial, Scientific, and Medical (ISM) band) to employ licensed assisted access (LAA), LTE unlicensed (LTE-U) radio access technology, or NR technology. When operating with unlicensed RF spectrum bands, devices such as network entity 105 and UE 115 may employ carrier sensing for collision detection and avoidance. In some examples, operation using unlicensed frequency bands may be combined with component carriers operating with licensed frequency bands based on carrier aggregation configurations (e.g., LAA). Operation using unlicensed spectrum may include downlink transmission, uplink transmission, P2P transmission, or D2D transmission, etc.

[0069] Network entity 105 (e.g., base station 140, RU 170) or UE 115 may be equipped with multiple antennas that can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. The antennas of network entity 105 or UE 115 may be located within one or more antenna arrays or antenna panels, which can support MIMO operation or transmit or receive beamforming. For example, one or more base station antennas or antenna arrays may be co-located at an antenna assembly such as an antenna tower. In some examples, the antennas or antenna arrays associated with network entity 105 may be located at different geographical locations. Network entity 105 may include an antenna array having a collection of multiple rows and columns of antenna ports that network entity 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may include one or more antenna arrays that can support various MIMO or beamforming operations. Additionally or alternatively, the antenna panel may support RF beamforming for signals transmitted via the antenna ports.

[0070] Network entity 105 or UE 115 may use MIMO communication to leverage multipath signal propagation and improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers. This technique may be referred to as spatial multiplexing. The multiple signals may be transmitted, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports used for channel measurement and reporting. MIMO techniques include: single-user MIMO (SU-MIMO), for which multiple spatial layers are transmitted to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are transmitted to multiple devices.

[0071] Beamforming (also known as spatial filtering, directional transmission, or directional reception) is a signal processing technique that can be used at a transmitting or receiving device (e.g., network entity 105, UE 115) to shape or guide an antenna beam (e.g., a transmit beam, a receive beam) along a spatial path between the transmitting and receiving devices. Beamforming can be achieved by combining signals transmitted via antenna elements of an antenna array such that some signals propagating along a specific orientation relative to the antenna array experience constructive interference, while other signals experience destructive interference. Adjustments to the signals transmitted via the antenna elements may include applying amplitude shifts, phase shifts, or both to the signals carried via the antenna elements associated with the device. The adjustments associated with each of these antenna elements may be defined by a beamforming weight set associated with a specific orientation (e.g., relative to the antenna array of the transmitting or receiving device or relative to some other orientation).

[0072] Network entity 105 or UE 115 may use beam scanning technology as part of beamforming operations. For example, network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network entity 105 in different directions. For example, network entity 105 may transmit signals according to different beamforming weight sets associated with different transmission directions. Transmission along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105) or by a receiving device (such as UE 115)) the beam direction for later transmission or reception by network entity 105.

[0073] Some signals (such as data signals associated with a specific receiving device) may be transmitted by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., the direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115). In some examples, the beam direction associated with transmission along a single beam direction may be determined based on the signals transmitted along one or more beam directions. For example, UE 115 may receive one or more signals transmitted by network entity 105 in different directions and may report to network entity 105 an indication of signals received by UE 115 with the highest signal quality or other acceptable signal quality.

[0074] In some examples, transmissions performed by a device (e.g., network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital pre-decoding or beamforming to generate combined beams for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating pre-decoding weights for one or more beam directions, and this feedback may correspond to a set of beams configured across the system bandwidth or one or more sub-bands. Network entity 105 may transmit reference signals (e.g., cell-specific reference signals (CRS), channel state information reference signals (CSI-RS)) that may or may not be pre-decoded. UE 115 may provide feedback for beam selection, which may be a pre-decoding matrix indicator (PMI) or codebook-based feedback (e.g., multi-panel codebook, linear combination codebook, port selection codebook). Although these techniques are described with reference to signals transmitted by network entity 105 (e.g., base station 140, RU 170) in one or more directions, UE 115 may use similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction used by UE 115 for subsequent transmission or reception), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0075] A receiving device (e.g., UE 115) may perform reception operations according to multiple reception configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a transmitting device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple reception directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array (e.g., different directional listening weight sets); or processing the received signal according to different sets of reception beamforming weights applied to signals received at multiple antenna elements of the antenna array. Any of these operations may be referred to as “listening” according to different reception configurations or reception directions. In some examples, the receiving device may use a single reception configuration to receive along a single beam direction (e.g., when a data signal is received). A single receiver configuration can be aligned along a beam direction determined based on listening according to different receiver configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0076] The wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or PDCP layer can be IP-based. The RLC layer performs packet segmentation and reassembly for transmission via logical channels. The MAC layer performs priority processing and multiplexing of logical channels to transport channels. The MAC layer can also use error detection, error correction, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer provides the establishment, configuration, and maintenance of RRC connections between the UE 115 and network entity 105 or core network 130 that support user plane data radio bearers. The PHY layer maps transport channels to physical channels.

[0077] UE 115 and network entity 105 can support data retransmission to increase the likelihood of successful data reception. Hybrid Automatic Repeat Request (HARQ) feedback is a technique used to increase the likelihood of correctly receiving data via communication links (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, the device may support same-slot HARQ feedback, in which case the device can provide HARQ feedback in a specific time slot for data received via a previous symbol in that time slot. In some other examples, the device may provide HARQ feedback in subsequent time slots or according to a different time interval.

[0078] Wireless devices in wireless communication system 200 can be configured to support technologies that enable wireless devices reserving and sharing a COT (e.g., “reserved” devices) to verify received communications and efficiently resume transmission within the COT. Specifically, wireless communication system 100 can support signaling, configuration, and technologies that enable a reserved UE 115 to share a COT with other devices and perform a channel access procedure to resume transmission within the COT without fully decoding messages received from other devices sharing the COT (e.g., initiating the channel access procedure before completing the decoding process for the received messages).

[0079] For example, in some implementations, a first UE 115 within a wireless communication system 100 may perform a channel access procedure to gain access to the COT and share the COT with a second UE 115. The first UE 115 may transmit messages within the COT and may stop transmitting within the COT to allow the second UE 115 to transmit messages within the COT. In this example, as long as the message is an "expected" message, the first UE 115 may be able to avoid fully decoding messages received from the second UE 115 within the COT (and directly proceed to perform the channel access procedure to resume transmission within the COT). Additionally or alternatively, the UE 115 may begin a decoding procedure to decode the "expected" message, but may begin (and / or complete) the channel access procedure before the decoding procedure is finished (e.g., without fully decoding the expected message).

[0080] The term "expected" message can refer to a message received within previously reserved or allocated resources. For example, an "expected" message may include a feedback message from a second UE 115 in response to a sidelink message previously sent by a first UE 115, wherein a pre-configured relationship exists between the resources used to send the sidelink message and the resources used to receive the feedback message. As another example, an "expected" message may include a sidelink message previously scheduled by the second UE 115. In such cases, upon determining that the received message is an "expected" message (e.g., received on previously reserved or allocated resources), the first UE 115 may directly jump to performing a channel access procedure to resume communication on the COT without fully decoding the expected message.

[0081] Figure 2 An example of a wireless communication system 200 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Aspects of the wireless communication system 200 may implement, or be implemented by, aspects of the wireless communication system 100. For example, the wireless communication system 200 exemplifies signaling between UEs 115 that enables UEs 115 to share a COT and allows reserved space for UEs 115 to efficiently resume transmission within the shared COT after receiving a message within the COT.

[0082] The wireless communication system 200 may include a first UE 115-a (UE1), a second UE 115-b (UE2), and a network entity 105-a, which may be as shown in the reference. Figure 1Examples of UE 115, network entity 105, and other wireless devices described herein. In some aspects, the first UE 115-a and the second UE 115-b may communicate with network entity 105-a via communication link 205-a and communication link 205-b, respectively. In some cases, communication links 205-a and 205-b may include examples of access links (e.g., Uu links). Communication links 205-a and 205-b may include bidirectional links that may include both uplink and downlink communication. For example, the first UE 115-a may use communication link 205-a to send uplink transmissions, such as uplink control signals or uplink data signals, to network entity 105-a, and network entity 105-a may use communication link 205-a to send downlink transmissions, such as downlink control signals or downlink data signals, to the first UE 115-a. Similarly, the first UE 115-a and the second UE 115-b can communicate with each other via communication link 205-c, which can be an example of a PC5 link between devices.

[0083] The corresponding devices of the wireless communication system 200 can be configured to communicate via resources in licensed spectrum, unlicensed spectrum, or both. For example, each UE 115 can be configured using a single sidelink BWP (SL-BWP), wherein the configured active SL-BWP can be associated with resources in the frequency band of licensed or unlicensed spectrum.

[0084] In the context of unlicensed spectrum, UE 115, network entity 105-a, or both can be configured to perform a channel access procedure, wherein the corresponding device monitors and evaluates channels or carriers associated with the unlicensed spectrum. For example, as part of the channel access procedure, the first UE 115-a can monitor resource set 215 (e.g., a sidelink channel) associated with the unlicensed spectrum to attempt to request use of the channel. In some aspects, as part of the channel access procedure, the device can monitor and evaluate resource set 215 (e.g., a channel) to determine whether the channel is freely accessible. In some aspects, if the first UE 115-a determines, through the channel access procedure, that the channel has been idle for a pre-configured time duration (e.g., a pre-configured number of sensing slots), then the first UE 115-a can determine that the channel (e.g., resource set 215) is freely accessible. In one aspect, if the channel has been idle for a random number of sensing slots, the channel can be determined to be freely accessible according to a first type of channel access procedure for NR-U (e.g., a type 1 channel access procedure, a countdown-based listen-before-talk (LBT) procedure). In this example, the first UE 115-a can send and acquire a channel (e.g., acquire access to COT 220 within the channel) after successfully completing a Type 1 channel access procedure using a random number of sensing time slots.

[0085] In some respects, if a channel is idle for a fixed period of time (e.g., 25µs for a Type 2A channel access procedure and 16µs for a Type 2B channel access procedure), the channel can be determined to be freely accessible based on an additional type of channel access procedure (e.g., a Type 2 channel access procedure or a “single” LBT). In this example, the first UE 115-a can transmit and acquire the channel after successfully completing a Type 2A or 2B channel access procedure using a predefined number of sensing slots. Additionally or alternatively, if the interval between two transmissions is less than a fixed period of time within the COT (e.g., 16µs), the corresponding device may not need to perform a channel access procedure (e.g., perform channel access sensing) before transmission (e.g., a Type 2C channel access procedure).

[0086] After successfully performing the channel access procedure, the first UE 115-a can perform communication within the COT 220 of the channel. In other words, the first UE 115-a can reserve the time / frequency resource set of COT 220 within the channel (e.g., within resource set 215) after successfully performing the channel access procedure within the channel (e.g., within resource set 215).

[0087] In some cases, the first UE 115-a may be able to share access to COT 220 with other devices such as the second UE 115-b. COT sharing is an agreed-upon mechanism in which a responder (e.g., the second UE 115-b) can use Type 2 channel access (e.g., a single LBT) in response to a COT-initiating UE 115 (e.g., the first UE 115-a) performing Type 1 channel access (a countdown-based LBT). To share COT 220, the COT-sharing UE 115 (e.g., the second UE 115-b) can receive COT sharing information (COT-SI) from the UE 115 that has reserved COT 220.

[0088] For example, as previously described herein, the first UE 115-a can successfully perform a Type 1 channel access procedure to secure access to COT 220. In some cases, COT 220 can span one or more Transmission Time Intervals (TTIs), such as a first time slot 225-a (e.g., time slot n-1), a second time slot 225-b (e.g., time slot n), and a third time slot 225-c (e.g., time slot n+1). The first UE 115-a can send a Phase 1 Side Link Control Information (SCI) (SCI-1) message (e.g., SCI-1 210-a) to one or more additional UEs 115 (such as a second UE 115-b). SCI-1 210-a can be communicated via the Physical Side Link Control Channel (PSCCH), and a set of resources can be reserved within the channel for communicating a Phase 2 SCI message (e.g., SCI-2 210-b). In some aspects, the second-phase SCI (e.g., SCI-2 210-b) may include a COT-SI and may be communicated via resources reserved through the first-phase SCI (e.g., SCI-1 210-a). In some cases, the second UE 115-b may send a feedback message 230 (e.g., in response to SCI-2 210-b, via the Physical Sidelink Feedback Channel (PSFCH)). After the COT-SI is exchanged, the corresponding UE 115 may be able to share COT 220 and communicate (e.g., send) sidelink messages 235-a and 235-b within COT 220.

[0089] In this regard, in some cases, wireless devices may be able to share access to COT 220. For example, as described herein, a first UE 115-a can successfully perform a channel access procedure to gain access to COT 220 and can send an SCI-2 210-b (e.g., a second-phase SCI message) including COT-SI to a second UE 115-b in order to share COT 220 with the second UE 115-b. In this example, the first UE 115-a can send a sidelink message 235-a within COT 220 and stop sending at some point, allowing the second UE 115-b to send within COT 220. However, according to some conventional techniques, in order for the first UE 115-a to resume sending within COT 220, the first UE 115-a can be expected to fully decode the messages received from the second UE 115-b and perform a new channel access procedure before it can resume sending within COT 220. The requirement to fully decode the message and execute a new channel access procedure can increase the latency for the first UE 115-a to resume communication within COT 220. Furthermore, other wireless devices (such as Wi-Fi devices) can successfully gain access to COT 220 before the first UE 115-a decodes the message and successfully executes the channel access procedure, thus causing the first UE 115-a to lose access to COT 220.

[0090] Therefore, the equipment of the wireless communication system 200 can be configured to support a technology that enables the first UE 115-a, which reserves and shares the COT 220, to verify received communications and efficiently resume transmission within the COT 220. Specifically, the wireless communication system 200 can support signaling, configuration, and techniques that enable the first UE 115-a (e.g., reserved UE 115-a) to share the COT 220 with other devices (e.g., the second UE 115-b) and perform a channel access procedure to resume transmission within the COT 220 without fully decoding messages received from other devices sharing the COT 220 (such as communications from the second UE 115-b).

[0091] The shortcomings of conventional methods for sharing COT and the accompanying advantages of this disclosure (see reference). Figure 3 and Figure 4 Further illustration and description.

[0092] Figure 3An example of resource configuration 300 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Aspects of resource configuration 300 may implement aspects of wireless communication system 100, wireless communication system 200, or both, or be implemented by these aspects. Specifically, Figure 3 Resource configuration 300 illustrates separate COT shared configurations 305-a and 305-b, which allow for the reservation of UE 115 (e.g., Figure 2 The first UE 115-a in the system is able to communicate with another device (e.g., Figure 2 The second UE 115-b) in the system shares COT 410 and efficiently resumes transmission within COT 410.

[0093] Referring to the first COT sharing configuration 305-a, the first UE 115-a can perform a channel access procedure (e.g., a type 1 channel access procedure) within an unlicensed channel to gain access to COT 310-a, which has an unlicensed channel. COT 310-a can span one or more TTIs, such as a first time slot 315-a and a second time slot 315-b. The first UE 115-a can send a second-stage SCI message with COT-SI to other devices to share COT 310-a with other devices.

[0094] As previously described herein, the first UE 115-a can transmit within COT 310-a and can cease transmitting to allow other radio devices sharing COT 310-a to transmit within COT 310-a. In some wireless communication systems, after receiving a message from another device within COT 310-a, the first UE 115-a may be able to resume its own transmission within COT 310-a after performing a Type 2 channel access procedure following the received message. In some conventional systems, it may be necessary (or anticipated) for the first UE 115-a to fully decode the received message and resume transmission within COT 310-a before the first UE 115-a can perform a Type 2 channel access procedure.

[0095] For example, continuing with the first COT shared configuration 305-a, the first UE 115-a can perform transmission bursts (e.g., multiple consecutive transmissions), such as sidelink messages 320-a, 320-b, and 320-c exemplified within COT 310-a. When the first UE 115-a shares COT 310-a with other devices, the first UE 115-a can stop transmitting sidelink messages 320 to allow other devices to transmit messages, such as feedback messages 325 (e.g., sharing COT 310-a for the PSFCH slot). In this example, the first UE 115-a might want to resume transmission within COT 310-a after receiving the incoming feedback message 325 (PSFCH). In some conventional systems, it might be necessary for the first UE 115-a to fully decode (e.g., turn on the modem, buffer and process / decode data, etc.) the feedback message 325 and perform a Type 2 channel access procedure to resume transmission within COT 310-a. However, in some cases, there may not be enough time for the first UE 115-a to decode the feedback message 325 (PSFCH) and successfully execute the Type 2 channel access procedure to resume transmission within COT 310-a. For example, in some cases, the feedback message 325 (PSFCH) may terminate in symbol #12, leaving only symbol #13 of time slot 315-a for decoding and executing the Type 2 channel access procedure. This may not provide enough time for the first UE 115-a to complete before the end of time slot 315-a, which could allow other devices to hop in and gain access to COT 310-a.

[0096] A similar problem arises in the context of the second COT shared configuration 305-b (e.g., insufficient time to fully decode the received message and perform Type 2 channel access). For example, referring to the second COT shared configuration 305-b, the first UE115-a receives a sidelink message 335-b from another device within a reserved COT 310-b spanning time slots 315-c, 315-d, and 315-e, and there is insufficient time to fully decode the sidelink message 335-b and perform Type 2 channel access before the end of time slot 315-d to restore communication within COT 310-b.

[0097] Therefore, aspects of this disclosure relate to standards for COT-initiating UE 115 (e.g., first UE 115-a) to verify received transmissions (e.g., feedback message 325) without forcing a full decoding of the received transmission itself. Such techniques described herein can help tighten the use of reserved COT 310, prevent other unwanted devices (e.g., Wi-Fi devices) from jumping in and “stealing” COT 310, and improve the throughput of reserved devices.

[0098] In other words, aspects of this disclosure relate to techniques that enable radio devices reserving and sharing COT 310 (e.g., "reserved" devices) to verify received communications (e.g., feedback message 325, sidelink message 335-b) and efficiently resume transmission within COT 310. Aspects of this disclosure also relate to techniques that enable a reserved UE 115 to share COT 310 with other devices and perform channel access procedures to resume transmission within COT 310 without fully decoding messages received from other devices sharing COT 310.

[0099] Specifically, aspects of this disclosure enable the reserved UE 115 to share COT 310 with other devices and perform channel access procedures to resume transmission within COT 310 without fully decoding “expected” messages received from other devices sharing COT 310. For the purposes of this disclosure, the term “expected” message may refer to a message received within previously reserved or allocated resources. For example, an “expected” message may include a feedback message (e.g., feedback message 325 in the first COT sharing configuration 305-a) from the second UE 115-b in response to a sidelink message (e.g., sidelink message 320-a) previously sent by the first UE 115-a, wherein a pre-configured relationship exists between the resources used to send the sidelink message and the resources used to receive the feedback message. As another example, an “expected” message may include a sidelink message (e.g., sidelink message 335-b in the second COT sharing configuration 305-b) previously scheduled by the second UE 115-b (e.g., via sidelink message 335-a).

[0100] In such cases, upon determining that the received message is an "expected" message (e.g., received on previously reserved or allocated resources), the first UE 115-a may directly jump to performing a channel access procedure (assuming a minimum "gap," such as 16µs or 25µs, as previously described) to resume communication on COT 310 after the expected message, without needing to fully decode the "expected" message. Specifically, the first UE 115-a may receive the expected message, but may not fully decode it (because it was received on previously reserved / allocated resources) because the first UE 115-a has not fully powered on the modem to process and / or decode the information / data included within the expected message. Alternatively, the first UE 115-a may simply receive the expected message and identify the signal power / gain of the expected message within the expected resources, but may not be able to fully process and decode the information within the expected message. If the first UE 115-a does not decode the message before performing the channel access procedure, the first UE 115-a may buffer the message in its memory so that the information / data included in the message can be processed / decoded at a later time.

[0101] Referring to the first COT sharing configuration 305-a. According to some aspects of this disclosure, a COT-initiating UE 115 (e.g., the first UE 115-a) that reserves COT 310-a and sends COT-SI 340-a to share COT 310-a can resume its transmission within COT 310-a after a Type 2 channel access (e.g., channel access procedure 330-b) following a cessation of its transmission to receive an “expected” PSFCH message. For example, as shown in the first COT sharing configuration 305-a, the first UE 115-a may have previously transmitted a sidelink message 320-a (e.g., PSCCH, PSSCH), where the sidelink message 320-a is associated with resources allocated for responding to a feedback message 325 (PSFCH) in response to the sidelink message 320-a. That is, the PSFCH resources are mapped to the PSSCH timing. In this respect, after sending a sidelink message 320-a (e.g., PSSCH), the first UE 115-a will "expect" a feedback message 325 from the second UE 115-b on a specific mapped resource (where the second UE 115-b may need to / expect to perform a Type 2 channel access procedure 330-a before sending the feedback message 325). Therefore, since the feedback message 325 is received on resources allocated / reserved for feedback in response to the sidelink message 320-a, the feedback message 325 in the first COT shared configuration 305-a can be "expected". In this respect, because the feedback message 325 constitutes an "expected" message, the first UE 115-a can avoid fully decoding the feedback message 325 and, after receiving the feedback message 325, perform a channel access procedure 330-b (e.g., Type 2) to resume sending the sidelink message 320-c within COT 310-a. As previously noted herein, channel access procedure 330-b may be associated with different numbers of sensing symbols / time slots (e.g., “gap”), such as 25 µs for a type 2A channel access procedure and 16 µs for a type 2B channel access procedure.

[0102] In some cases, feedback message 325 can qualify as "expected" PSFCH as long as it is received from "responding" UE 115 (thus allowing first UE 115-a to avoid decoding feedback message 325). In some cases, UE 115 can qualify as "responding" UE 115 if another UE 115 receives COT-SI 340-a from first UE 115-a. For example, after reserving COT 310-a, first UE 115-a can send COT-SI 340-a to second UE 115-b within SCI-2 or other sidelink message 320-b (PSSCH), thus making second UE 115-b a "responding" UE 115-b.

[0103] In some cases, determining that the expected PSFCH (e.g., feedback message 325) originates from the responding UE 115 is based on a matching identifier (ID) criterion. That is, the first UE 115-a can determine whether the matching ID criterion is met to determine whether the feedback link message 325 was received from the "responding" UE 115, thereby qualifying the feedback link message 325 as an "expected" message. In some cases, the matching ID criterion can be met if the identifier within the side link message 320-a (which is associated with feedback message 325) matches the identifier within COT-SI 340-a.

[0104] For example, in some cases, as long as the PSFCH (e.g., feedback message 325) is in response to a previous PSSCH (e.g., sidelink message 320-a) from the first UE 115-a, the matching ID criterion can be satisfied (thus limiting feedback message 325 to an "expected" message that enables the first UE 115-a to avoid decoding feedback message 325), the previous PSSCH carries an SCI-2 logical ID that is equal to the logical ID carried in the SCI-2 carrying COT-SI 340-a.

[0105] The second COT shared configuration 305-b will now be referred to. The second COT shared configuration 305-b illustrates how a reserved UE 115 (e.g., the first UE 115-a) can resume the signaling and configuration of COT 310-b after a time slot (e.g., time slot 315-d) reserved for PSSCH from another UE 115 (e.g., the second UE 115-b).

[0106] For example, according to some aspects of this disclosure, a COT-initiating UE 115 (e.g., the first UE 115-a) that sends COT-SI 340-b to share COT 310-b may resume its transmission after a Type 2 channel access (e.g., channel access procedure 330-d) after ceasing its transmission to receive the expected PSSCH (e.g., sidelink message 335-b). For example, as shown in the second COT sharing configuration 305-b, the second UE 115-b may have previously sent a sidelink message 335-a (e.g., PSCCH, PSSCH), where the sidelink message 335-a schedules another sidelink message 335-b to be sent by the second UE 115-b (e.g., sidelink message 335-a reserves resources for sidelink message 335-b). In this respect, after receiving sidelink message 335-a (e.g., PSSCH), the first UE 115-a will "expect" to receive scheduled sidelink message 335-b on reserved / allocated resources (where it may be necessary / expected that the second UE 115-b performs a type 2 channel access procedure 330-c before sending sidelink message 335-b). Therefore, sidelink message 335-b in the second COT shared configuration 305-b can be "expected" due to the fact that it was previously scheduled by the second UE 115-b via sidelink message 335-a. In this respect, because sidelink message 335-b (e.g., PSSCH, PSCCH) constitutes an "expected" message, the first UE 115-a can avoid fully decoding sidelink message 335-b and perform channel access procedure 330-d (e.g., type 2) after receiving sidelink message 335-b to resume sending sidelink message 320-e within COT 310-b.

[0107] In some respects, sidelink message 335-b can qualify as an "expected" message as long as the resource reservation for the anticipated PSSCH (e.g., sidelink message 335-b) has been declared via another UE 115 in SCI-1 (thus allowing the first UE 115-a to avoid decoding sidelink message 335-b). That is, sidelink message 335-b can qualify as an "expected" message as long as the second UE 115-b sends an SCI-1 (e.g., sidelink message 335-a) reserving / scheduling resources for receiving sidelink message 335-b.

[0108] In some cases, sidelink message 335-b can qualify as an expected PSFCH as soon as it is received from the "responding" UE 115 (thus allowing the first UE 115-a to avoid decoding feedback message 325). In some cases, UE 115 can qualify as a "responding" UE 115 if another UE 115 receives COT-SI 340-b from the first UE 115-a. For example, after reserving COT 310-b, the first UE 115-a can send COT-SI 340-b to the second UE 115-b in SCI-2 or another sidelink message 320-d (PSSCH), thus making the second UE 115-b a "responding" UE 115-b.

[0109] In some other cases, determining that the expected PSSCH (e.g., sidelink message 335-b) originates from the responding UE 115 is based on a matching ID criterion, as previously described herein. That is, the first UE 115-a can determine whether the matching ID criterion is met in order to determine whether sidelink message 335-b was received from the "responding" UE 115, thereby qualifying sidelink message 335-b as an "expected" message. In some cases, the matching ID criterion can be satisfied if the identifier of the scheduled expected sidelink message 335-b within sidelink message 335-a matches the identifier within COT-SI 340-b.

[0110] For example, in some cases, the matching ID criterion can be satisfied as long as the transmission containing resource reservation from the second UE 115-b (e.g., sidelink message 335-a) carries one or more SCI-2 logical IDs that match the logical ID carried in the SCI-2 of the transmission from the first UE 115-a carrying COT-SI 340-b. (Thus limiting the sidelink message 335-b to an “expected” message that allows the first UE 115-a to avoid decoding the sidelink message 335-b.)

[0111] Figure 4 An example of a process flow 400 supporting a technique for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Aspects of process flow 400 may implement aspects of, or be implemented by, wireless communication system 100, wireless communication system 200, resource configuration 300, or any combination thereof. For example, process flow 400 exemplifies signaling between UEs 115 that enables UEs 115 to share a COT and allows reserved UEs 115 to efficiently resume transmission within the shared COT after receiving a message within the COT.

[0112] Process flow 400 includes a first UE 115-c and a second UE 115-d, which can be examples of UE 115 and other wireless devices as described herein. For example, Figure 4 The first UE 115-c and the second UE 115-d illustrated can be respectively as follows: Figure 2 Examples of the first UE 115-a and the second UE 115-b are shown.

[0113] In some examples, the operations illustrated in process flow 400 may be performed by hardware (e.g., including circuits, processing blocks, logic components, and other components), code executed by a processor (e.g., software or firmware), or any combination thereof. Alternative examples are possible, some of which may be performed in a different order than described or not at all. In some cases, steps may include additional features not mentioned below, or additional steps may be added.

[0114] At point 405, the first UE 115-c can send a sidelink message (e.g., PSSCH / PSCCH) to the second UE 115-d. For example, as Figure 3 As shown in the first COT shared configuration 305-a, the first UE 115-c can send a sidelink message 320-a to the second UE 115-d. As previously described herein, PSFCH resources can be mapped to PSSCH timing. That is, the sidelink message at 405 can be associated with a set of resources allocated / reserved for a feedback message (e.g., feedback message 325). In this regard, as will be described in further detail herein, in the case where the first UE 115-c sends a sidelink message at 405, the “expected” message at step 445 may include a feedback message (PSFCH) in response to the sidelink message, and the feedback message is received on the PSFCH resources mapped to the sidelink message at 405.

[0115] At position 410, the first UE 115-c can receive sidelink messages (e.g., PSSCH / PSCCH) from the second UE 115-d. For example, as... Figure 3As shown in the second COT shared configuration 305-b, the first UE 115-c can receive a sidelink message 335-a (PSCCH) from the second UE 115-d, wherein the sidelink message 335-a schedules another sidelink message 335-b (PSSCH) to be sent by the second UE 115-d. In other words, the sidelink message at 410 can schedule the sidelink message at 445. In this regard, as will be described in further detail herein, if the first UE 115-c receives a sidelink message at 410, the “expected” message at step 445 may include another sidelink message (PSSCH) scheduled by the sidelink message at 410.

[0116] At 415, the first UE 115-c may perform a channel access procedure within the sidelink channel to obtain access to the COT within the sidelink channel. In some cases, the channel access procedure at 415 may include a Type 1 channel access procedure.

[0117] At 420, the first UE 115-c may send a Phase 1 SCI message (SCI-1). In some cases, SCI-1 may schedule an SCI-2 message (e.g., to reserve resources for SCI-2). The SCI-1 message may be delivered via PSCCH. In some cases, the first UE 115-c may send SCI-1 based on performing a channel access procedure at 415.

[0118] At 425, the first UE 115-c can send a second-stage SCI message (SCI-2). In some cases, the SCI-2 message can be sent at 420 within the resources reserved for the SCI-1 message. The SCI-2 message can be delivered via PSSCH. In some aspects, the SCI-2 message may include COT-SI (e.g., Figure 3 The COT-SI 340 in the document includes information for sharing the COT with other devices. In some cases, the first UE 115-c may transmit SCI-2 based on performing a channel access procedure at 415, transmitting SCI-1 at 420, or both.

[0119] At 430, the first UE 115-c can send one or more sidelink messages (e.g., PSSCH / PSCCH) within the COT. For example, as... Figure 3 As shown in the first COT shared configuration 305-a, the first UE 115-c can send a sidelink message 320-b to the second UE 115-d. In some cases, such as Figure 3As shown, sidelink message 320-b may include COT-SI 340-a. That is, in some cases, SCI-2 carrying COT-SI at 425 can be multiplexed with the sidelink message at 430.

[0120] At point 435, the first UE 115-c may cease transmission within the COT. Specifically, the first UE 115-c may cease transmission within the COT based on the identification of “expected” resources reserved or otherwise allocated for transmissions by another device sharing the COT (e.g., the second UE 115-d). Thus, the first UE 115-c may cease transmission at point 435 to monitor resources reserved / allocated for “expected” messages.

[0121] At 440, the second UE 115-d may perform a channel access procedure within the sidelink channel to obtain access to the COT previously reserved by the first UE 115-c. In some cases, the channel access procedure at 440 may include a type 2 channel access procedure.

[0122] At 445, the first UE 115-c can receive an "expected" message. As previously described herein, a message received at 445 may qualify as an "expected" message if it is received within resources previously reserved or allocated for the message. For example, if the first UE 115-c sends a sidelink message at 405, the "expected" message at step 445 may include a feedback message (PSFCH) in response to the sidelink message, wherein the feedback message at 445 is received on the PSFCH resource mapped to the sidelink message at 405. As another example, if the first UE 115-c receives a sidelink message at 410, the "expected" message at step 445 may include another sidelink message (PSSCH) scheduled by the sidelink message at 410.

[0123] For reference Figure 3 As described, there may be other conditions or criteria that can be met for a message received at 445 to qualify as an "expected" message. For example, in some cases, a message received at 445 may qualify as an "expected" message simply as long as it is received from a "responding" UE (e.g., UE 115 receiving COT-SI from first UE 115-c). In other cases, a message received at 445 may qualify as an "expected" message simply as long as the matching ID criterion is met. In such cases, process flow 400 may proceed to step 450.

[0124] At 450, the first UE 115-c can assess whether the matching ID criterion is met. As previously described herein, as long as the matching ID criterion is met, the message received at 445 can be received from the "responding" UE (thus qualifying the message at 445 as an "expected" message and allowing the first UE 115-c to avoid decoding the message at 445).

[0125] For example, in some cases, the Match ID criterion can be satisfied if the identifier in the sidelink message at 405 (which is associated with the feedback message received at 445) matches the identifier in the COT-SI sent via SCI-2 at 425. As another example, the Match ID criterion can be satisfied if the identifier of the sidelink message scheduled at 445 in the sidelink message at 410 matches the identifier in the COT-SI sent via SCI-2 at 425.

[0126] If the message received at 445 qualifies as an "expected" message, and / or if the matching ID criterion is met at 450, the first UE 115-c may be able to avoid decoding the received message and proceed directly to the Type 2 channel access procedure to restore access to the COT. As previously noted herein, the first UE 115-c may avoid decoding the message received at 445 by not fully powering on the modem and / or avoiding processing and / or decoding the information / data included in the message at 445. If the first UE 115-c does not decode the message at 445 before performing the channel access procedure, the first UE 115-c may buffer the message in memory so that the information / data included in the message can be processed / decoded at a later time (e.g., after the channel access procedure is completed and access to the COT is regained).

[0127] At 455, the first UE 115-c may perform a channel access procedure within the sidelink channel to regain access to the COT after receiving the message at 445. In some cases, the channel access procedure at 455 may include a type 2 channel access procedure.

[0128] At 460, the first UE 115-c may resume transmitting one or more sidelink messages (e.g., PSSCH / PSCCH) within the COT. The first UE 115-c may resume transmitting messages within the COT at 460 based on determining that the message received at 445 is an "expected" message (e.g., received on reserved / allocated resources), based on identifying the satisfaction of the matching ID criterion at 450, based on successfully completing the channel access procedure at 455, or any combination thereof.

[0129] Figure 5A block diagram 500 of an apparatus 505 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Apparatus 505 may be an example of various aspects of a UE 115 as described herein. Apparatus 505 may include a receiver 510, a transmitter 515, and a communication manager 520. Apparatus 505, or one or more components of apparatus 505 (e.g., receiver 510, transmitter 515, and communication manager 520), may include at least one processor that may be coupled to at least one memory to individually or jointly support or implement the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0130] Receiver 510 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 505. In some examples, receiver 510 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 510 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0131] Transmitter 515 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 505. For example, transmitter 515 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 515 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 515 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 515 and receiver 510 may be co-located in a transceiver, which may include or be coupled to a modem.

[0132] The communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or various components thereof, may be examples of components used to perform various aspects of the techniques described herein for restoring sidelink transmission within a shared COT. For example, the communication manager 520, receiver 510, transmitter 515, or various combinations thereof, or components thereof, may be able to perform one or more of the functions described herein.

[0133] In some examples, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in hardware (e.g., in communication management circuitry). The hardware may include at least one of a processor, DSP, CPU, ASIC, FPGA, or other programmable logic device, microcontroller, discrete gate or transistor logic device, discrete hardware component, or any combination thereof, configured as or otherwise individually or collectively to support components for performing the functions described herein. In some examples, at least one processor and at least one memory coupled to said at least one processor may be configured to perform one or more of the functions described herein (e.g., executing instructions stored in at least one memory individually or collectively by one or more processors).

[0134] Additionally or alternatively, the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be implemented in code executed by at least one processor (e.g., as communication management software or firmware). If implemented in code executed by at least one processor, the functionality of the communication manager 520, receiver 510, transmitter 515, or various combinations or components thereof may be performed by any combination of a general-purpose processor, DSP, CPU, ASIC, FPGA, microcontroller, or these or other programmable logic devices (e.g., configured as or otherwise individually or jointly to support components for performing the functions described in this disclosure).

[0135] In some examples, the communication manager 520 may be configured to use or otherwise cooperate with the receiver 510, the transmitter 515, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, the communication manager 520 may receive information from the receiver 510, transmit information to the transmitter 515, or be integrated with the receiver 510, the transmitter 515, or both to acquire information, output information, or perform various other operations as described herein.

[0136] For example, the communication manager 520 can be configured or operated to support components for monitoring the sidelink channel as part of a first channel access procedure for accessing the COT within the sidelink channel. The communication manager 520 can be configured or operated to support components for transmitting a second-stage SCI message including a COT-SI for sharing the COT with one or more additional UEs. The communication manager 520 can be configured or operated to support components for transmitting a first sidelink message within the first part of the COT. The communication manager 520 can be configured or operated to support components for receiving a second sidelink message within the second part of the COT based on the transmission of the second-stage SCI message. The communication manager 520 can be configured or operated to support components for performing a second channel access procedure for accessing the COT and decoding the second sidelink message without requiring it to be received within the resource set of the sidelink channel reserved for the second sidelink message. The communication manager 520 is capable of, can be configured to, or is operable to support components for sending third-side link messages within the third part of the COT based on the completion of the second channel access procedure.

[0137] Figure 6 A block diagram 600 of an apparatus 605 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure, is shown. Apparatus 605 may be an example of aspects of apparatus 505 or UE 115 as described herein. Apparatus 605 may include a receiver 610, a transmitter 615, and a communication manager 620. Apparatus 605, or one or more components of apparatus 605 (e.g., receiver 610, transmitter 615, and communication manager 620), may include at least one processor coupled to at least one memory to support the described techniques. Each of these components may communicate with each other (e.g., via one or more buses).

[0138] Receiver 610 may provide components for acquiring (e.g., receiving, determining, identifying) information (such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units)) associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack). The information may be passed to other components of device 605. In some examples, receiver 610 may support acquiring information by receiving signals via one or more antennas. Additionally or alternatively, receiver 610 may support acquiring information by receiving signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof.

[0139] Transmitter 615 may provide components for outputting (e.g., transmitting, providing, conveying, transmitting) information generated by other components of device 605. For example, transmitter 615 may output information associated with various channels (e.g., control channels, data channels, information channels, channels associated with a protocol stack), such as user data, control information, or any combination thereof (e.g., I / Q samples, symbols, packets, protocol data units, service data units). In some examples, transmitter 615 may support outputting information by transmitting signals via one or more antennas. Additionally or alternatively, transmitter 615 may support outputting information by transmitting signals via one or more wired (e.g., electrical, fiber optic) interfaces, wireless interfaces, or any combination thereof. In some examples, transmitter 615 and receiver 610 may be co-located in a transceiver, which may include or be coupled to a modem.

[0140] Device 605 or its various components may be examples of parts for performing various aspects of the techniques described herein for resuming sidelink transmission within a shared COT. For example, communication manager 620 may include channel access procedure manager 625, SCI-2 transmission manager 630, sidelink message transmission manager 635, sidelink message reception manager 640, or any combination thereof. Communication manager 620 may be examples of aspects of communication manager 520 as described herein. In some examples, communication manager 620 or its various components may be configured to use or otherwise cooperate with receiver 610, transmitter 615, or both to perform various operations (e.g., receiving, acquiring, monitoring, outputting, transmitting). For example, communication manager 620 may receive information from receiver 610, transmit information to transmitter 615, or be integrated in combination with receiver 610, transmitter 615, or both to acquire information, output information, or perform various other operations as described herein.

[0141] The Channel Access Procedure Manager 625 is capable of, configured to, or operable to support components for monitoring the sidelink channel as part of a first channel access procedure for accessing the COT within the sidelink channel. The SCI-2 Transmission Manager 630 is capable of, configured to, or operable to support components for transmitting a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs. The Sidelink Message Transmission Manager 635 is capable of, configured to, or operable to support components for transmitting a first sidelink message within the first part of the COT. The Sidelink Message Reception Manager 640 is capable of, configured to, or operable to support components for receiving a second sidelink message within the second part of the COT based on the transmission of the second-phase SCI message. The Channel Access Procedure Manager 625 is capable of, configured to, or operable to support components for performing a second channel access procedure for accessing the COT and for decoding the second sidelink message without requiring it to be received within the resource set of the sidelink channel reserved for the second sidelink message. The sidelink message sending manager 635 is capable of, can be configured to, or is operable to support components for sending third sidelink messages within the third part of the COT based on the completion of the second channel access procedure.

[0142] Figure 7 A block diagram 700 is shown of a communication manager 720 supporting techniques for resuming sidelink transmission within a shared COT, according to one or more aspects of this disclosure. The communication manager 720 may be an example of aspects of the communication manager 520, communication manager 620, or both as described herein. The communication manager 720 or its various components may be examples of parts for performing various aspects of the techniques for resuming sidelink transmission within a shared COT as described herein. For example, the communication manager 720 may include a channel access procedure manager 725, an SCI-2 transmission manager 730, a sidelink message transmission manager 735, a sidelink message reception manager 740, a sidelink message decoding manager 745, an SCI-1 transmission manager 750, a match ID standard manager 755, or any combination thereof. These components, or each of their components or sub-components (e.g., one or more processors, one or more memories), may communicate directly or indirectly with each other (e.g., via one or more buses), and such communication may include communication within the protocol layers of the protocol stack, communication associated with logical channels of the protocol stack (e.g., between protocol layers of the protocol stack, within devices, components, or virtualization components associated with network entity 105, between devices, components, or virtualization components associated with network entity 105), or any combination thereof.

[0143] The Channel Access Procedure Manager 725 is capable of, configured to, or operable to support components for monitoring the sidelink channel as part of a first channel access procedure for accessing the COT within the sidelink channel. The SCI-2 Transmission Manager 730 is capable of, configured to, or operable to support components for transmitting a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs. The Sidelink Message Transmission Manager 735 is capable of, configured to, or operable to support components for transmitting a first sidelink message within the first part of the COT. The Sidelink Message Reception Manager 740 is capable of, configured to, or operable to support components for receiving a second sidelink message within the second part of the COT based on the transmission of the second-phase SCI message. In some examples, the Channel Access Procedure Manager 725 is capable of, configured to, or operable to support components for performing a second channel access procedure for accessing the COT and for decoding the second sidelink message without requiring it to be received within a resource set of sidelink channels reserved for the second sidelink message. In some examples, the sidelink message sending manager 735 is capable of, configured to, or able to operate to support components for sending third sidelink messages within the third part of the COT based on the completion of the second channel access procedure.

[0144] In some examples, the sidelink message sending manager 735 is capable of, configured to, or able to operate to support components for sending a fourth sidelink message to a second UE, wherein a resource set is reserved for a feedback message in response to the fourth sidelink message, the second sidelink message including the feedback message, and wherein a second channel access procedure is performed without decoding the second sidelink message based on the feedback message being received within the resource set reserved for the feedback message.

[0145] In some examples, the SCI-2 transmission manager 730 is capable of, configured to, or able to operate to support components for transmitting a second-stage SCI message, including a COT-SI, to a second UE, wherein a second channel access procedure is performed without decoding the second sidelink message based on transmitting the COT-SI to the second UE and receiving a feedback message from the second UE.

[0146] In some examples, the Match ID Standard Manager 755 is capable of, configured to, or able to operate to support components for identifying satisfaction of the Match ID Standard based on the matching of a first identifier within a fourth sidelink message with a second identifier within a COT-SI, wherein a second channel access procedure is performed without decoding the second sidelink message based on satisfaction of the Match ID Standard.

[0147] In some examples, the first identifier and the second identifier include logical identifiers associated with the second-stage SCI message.

[0148] In some examples, feedback messages are received via PSSCH.

[0149] In some examples, the sidelink message receiving manager 740 is capable of, configured to, or able to operate to support components for receiving a fourth sidelink message from a second UE, wherein the fourth sidelink message is a resource set reserved for the second sidelink message, and wherein a second channel access procedure is performed without decoding the second sidelink message based on the fact that the second sidelink message is received within the resource set reserved by the fourth sidelink message.

[0150] In some examples, the fourth sidelink message includes the first-stage SCI message.

[0151] In some examples, the SCI-2 transmission manager 730 is capable of, configured to, or able to operate to support components for transmitting a second-stage SCI message, including a COT-SI, to a second UE, wherein a second channel access procedure is performed without decoding the second sidelink message based on transmitting the COT-SI to the second UE and receiving the second sidelink message from the second UE.

[0152] In some examples, the Match ID Standard Manager 755 is capable of, configured to, or able to operate to support components for identifying satisfaction of the Match ID Standard based on the matching of a first identifier within a fourth sidelink message with a second identifier within a COT-SI, wherein a second channel access procedure is performed without decoding the second sidelink message based on satisfaction of the Match ID Standard.

[0153] In some examples, the first identifier and the second identifier include logical identifiers associated with the second-stage SCI message.

[0154] In some examples, the second lateral link message includes a lateral link shared channel message or a lateral link control channel message.

[0155] In some examples, the sidelink message sending manager 735 is capable of, configured to, or operable to support components for avoiding the sending of sidelink messages within the second part of the COT based on a resource set that reserves a sidelink channel for second sidelink messages within the second part of the COT, wherein the second sidelink messages are received based on avoiding the sending of sidelink messages within the second part of the COT.

[0156] In some examples, the sidelink message decoding manager 745 is capable of, can be configured to, or is operable to support components for avoiding processing of information included in the second-stage SCI message based on the second sidelink message being received within a resource set reserved for the second sidelink message.

[0157] In some examples, the SCI-1 transmission manager 750 is capable of, configured to, or operable to support components for transmitting first-stage SCI messages that reserve a resource set for second-stage SCI messages based on the completion of the first channel access procedure, wherein the second-stage SCI messages are transmitted within the resource set.

[0158] In some examples, the first channel access procedure includes a type 1 channel access procedure. In some examples, the second channel access procedure includes a type 2 channel access procedure.

[0159] Figure 8 A diagram of a system 800 including device 805 supporting techniques for resuming sidelink transmission during shared channel occupancy time, according to one or more aspects of this disclosure, is shown. Device 805 may be an example of device 505, device 605, or UE 115 as described herein, or may include components thereof. Device 805 may communicate with one or more network entities 105, one or more UEs 115, or any combination thereof (e.g., wirelessly). Device 805 may include components for bidirectional voice and data communication, including components for transmitting and receiving communications, such as a communication manager 820, an input / output (I / O) controller 810, a transceiver 815, an antenna 825, at least one memory 830, code 835, and at least one processor 840. These components may communicate electronically or be coupled in other ways (e.g., operational ground, communication ground, functional ground, electronic ground, electrical ground) via one or more buses (e.g., bus 845).

[0160] I / O controller 810 manages the input and output signals of device 805. I / O controller 810 can also manage peripheral devices not integrated into device 805. In some cases, I / O controller 810 may represent a physical connection or port to an external peripheral device. In some cases, I / O controller 810 may utilize an operating system such as iOS. ® ANDROID ® MS-DOS ® MS-WINDOWS ® OS / 2 ® UNIX ® LINUX ® Alternatively, the I / O controller 810 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, the I / O controller 810 may be implemented as part of one or more processors, such as at least one processor 840. In some cases, a user may interact with the device 805 via the I / O controller 810 or via hardware components controlled by the I / O controller 810.

[0161] In some cases, device 805 may include a single antenna 825. However, in other cases, device 805 may have more than one antenna 825, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. Transceiver 815 may communicate bidirectionally via one or more antennas 825 as described herein, or via a wired or wireless link. For example, transceiver 815 may represent a wireless transceiver and may communicate bidirectionally with another wireless transceiver. Transceiver 815 may also include a modem for: modulating packets; providing the modulated packets to one or more antennas 825 for transmission; and demodulating packets received from one or more antennas 825. Transceiver 815, or transceiver 815 and one or more antennas 825, may be an example of transmitter 515, transmitter 615, receiver 510, receiver 610, or any combination thereof or components thereof as described herein.

[0162] At least one memory 830 may include random access memory (RAM) and read-only memory (ROM). At least one memory 830 may store computer-readable, computer-executable code 835, including instructions that, when executed by at least one processor 840, cause device 805 to perform the various functions described herein. Code 835 may be stored in a non-transitory computer-readable medium such as system memory or another type of memory. In some cases, code 835 may not be directly executable by at least one processor 840, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein. In some cases, among other things, at least one memory 830 may also include a basic I / O system (BIOS) that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0163] At least one processor 840 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, at least one processor 840 may be configured to operate a memory array using a memory controller. In some other cases, the memory controller may be integrated into at least one processor 840. At least one processor 840 may be configured to execute computer-readable instructions stored in memory (e.g., at least one memory 830) to cause device 805 to perform various functions (e.g., functions or tasks supporting techniques for resuming sidelink transmission during shared channel occupancy). For example, device 805 or components of device 805 may include at least one processor 840 and at least one memory 830 coupled to or coupled to at least one processor 840, wherein at least one processor 840 and at least one memory 830 are configured to perform the various functions described herein. In some examples, at least one processor 840 may include multiple processors, and at least one memory 830 may include multiple memories. One or more of a plurality of processors may be coupled to one or more of a plurality of memories, which may be configured individually or collectively to perform the various functions described herein. In some examples, at least one processor 840 may be a component of a processing system, which may refer to a system of machines (such as a series of machines), circuitry (including, for example, one or both of processor circuitry (which may include at least one processor 840) and memory circuitry (which may include at least one memory 830)) or components that receive or receive input and process the input to produce, generate or obtain a set of outputs. The processing system may be configured to perform one or more of the functions described herein. Thus, at least one processor 840 or a processing system including at least one processor 840 may be configured, capable of being configured, or operable to cause device 805 to perform one or more of the functions described herein. Furthermore, as described herein, “configured to,” “capable of being configured,” and “operable to” are used interchangeably and may be associated with the ability to perform one or more of the functions described herein when executing code stored in at least one memory 830 or otherwise.

[0164] For example, the communication manager 820 can be configured or operated to support components for monitoring the sidelink channel as part of a first channel access procedure for accessing the sidelink channel during Channel Occupancy Time (COT). The communication manager 820 can be configured or operated to support components for transmitting a second-phase sidelink control information message including COT-sharing information for sharing the COT with one or more additional UEs. The communication manager 820 can be configured or operated to support components for transmitting a first sidelink message within the first part of the COT. The communication manager 820 can be configured or operated to support components for receiving a second sidelink message within the second part of the COT based on the transmission of the second-phase sidelink control information message. The communication manager 820 can be configured or operated to support components for performing a second channel access procedure for accessing the COT and decoding the second sidelink message without requiring it to be received within a resource set of sidelink channels reserved for the second sidelink message. The communication manager 820 is capable of, can be configured to, or is operable to support components for sending third-side link messages within the third part of the COT based on the completion of the second channel access procedure.

[0165] In some examples, the communication manager 820 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or in cooperation with transceiver 815, one or more antennas 825, or any combination thereof. Although the communication manager 820 is illustrated as a separate component, in some examples, one or more functions described with reference to the communication manager 820 may be supported by or performed by at least one processor 840, at least one memory 830, code 835, or any combination thereof. For example, code 835 may include instructions executable by at least one processor 840 to cause device 805 to perform various aspects of techniques described herein for resuming sidelink transmission during shared channel occupancy periods, or at least one processor 840 and at least one memory 830 may be otherwise configured to perform or support such operations individually or jointly.

[0166] Figure 9 A flowchart illustrating a method 900 for resuming sidelink transmission within a shared COT, exemplifying various aspects of this disclosure, is shown. Operation of method 900 may be implemented by a UE 115 or its components as described herein. For example, operation of method 900 may be implemented by, as referenced... Figures 1 to 7 The UE 115 described herein is used to perform the functions. In some examples, the UE 115 may execute a set of instructions to control the functional elements of the UE 115 to perform the described functions. Additionally or alternatively, the UE 115 may use dedicated hardware to perform aspects of the described functions.

[0167] At 905, the method may include monitoring the sidelink channel as part of a first channel access procedure for accessing the COT within the sidelink channel. Operation of block 905 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 905 may be provided by reference to [reference needed]. Figure 7 The described channel access process manager 725 is used to execute it.

[0168] At 910, the method may include sending a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs. The operation of box 910 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 910 may be provided by reference to [reference needed]. Figure 7 The SCI-2 send manager 730 described is used to perform this.

[0169] At 915, the method may include sending a first side-link message within the first part of the COT. The operation of box 915 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 915 may be derived from references... Figure 7 The sidelink message sending manager 735 described is used to perform this.

[0170] At 920, the method may include identifying a second sidelink message expected to be received within the second part of the COT based on sending a second-stage SCI message. Operation of block 920 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 920 may be derived from references... Figure 7 The described sidelink message receiving manager 740 is used to perform this.

[0171] At 925, the method may include performing a second channel access procedure for accessing the COT after identifying the second sidelink message based on the fact that the second sidelink message is expected to be within a resource set of sidelink channels reserved for the second sidelink message. The operation of block 925 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 925 may be derived from references... Figure 7 The described channel access process manager 725 is used to execute it.

[0172] At 930, the method may include sending a third-side link message within the third part of the COT based on the completion of the second channel access procedure. The operation of block 930 may be performed according to examples as disclosed herein. In some examples, aspects of the operation of 930 may be provided by reference to [reference needed]. Figure 7 The sidelink message sending manager 735 described is used to perform this.

[0173] The following provides an overview of the various aspects of this disclosure:

[0174] Aspect 1: A method for wireless communication at a first UE, the method comprising: monitoring the sidelink channel as part of a first channel access procedure for accessing a COT within a sidelink channel; transmitting a second-phase SCI message including a COT-SI for sharing the COT with one or more additional UEs; transmitting a first sidelink message within a first portion of the COT; identifying a second sidelink message expected to be received within a second portion of the COT based at least in part on the transmission of the second-phase SCI message; performing a second channel access procedure for accessing the COT after identifying the second sidelink message at least in part on the fact that the second sidelink message is expected to be within a resource set of the sidelink channel reserved for the second sidelink message; and transmitting a third sidelink message within a third portion of the COT based at least in part on the completion of the second channel access procedure.

[0175] Aspect 2: According to the method of aspect 1, the method further includes: sending a fourth sidelink message to a second UE, wherein the resource set is reserved for a feedback message in response to the fourth sidelink message, the second sidelink message including the feedback message, and wherein the second channel access procedure is performed after identifying the second sidelink message based at least in part on the fact that the feedback message is expected to be within the resource set reserved for the feedback message.

[0176] Aspect 3: The method according to aspect 2 includes the second phase SCI message of the COT-SI being sent to the second UE, and the second channel access procedure being performed after the second side link message is identified at least in part based on sending the COT-SI to the second UE and the feedback message identifying the second UE.

[0177] Aspect 4: According to the method of aspect 3, the method further includes: identifying a satisfaction of a matching identifier criterion based at least in part on a first identifier in the fourth side link message matching a second identifier in the COT-SI, wherein the second channel access procedure is performed after identifying the second side link message based at least in part on the satisfaction of the matching identifier criterion.

[0178] Aspect 5: According to the method of aspect 4, wherein the first identifier and the second identifier include logical identifiers associated with the second stage SCI message.

[0179] Aspect 6: The method according to any one of Aspects 1 to 5, the method further comprising: receiving a fourth sidelink message from a second UE, wherein the fourth sidelink message reserves the resource set for the second sidelink message, and wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on the second sidelink message being expected to be within the resource set reserved by the fourth sidelink message.

[0180] Aspect 7: According to the method of aspect 6, the fourth side link message includes a first-stage SCI message.

[0181] Aspect 8: The method according to any one of Aspects 6 to 7 includes the second-stage SCI message of the COT-SI being sent to the second UE, and the second channel access procedure being performed after the second sidelink message is identified at least in part based on sending the COT-SI to the second UE and identifying the second sidelink message from the second UE.

[0182] Aspect 9: The method according to any one of Aspects 6 to 8, the method further comprising: identifying a satisfaction of a matching identifier criterion based at least in part on a first identifier in the fourth sidelink message matching a second identifier in the COT-SI, wherein the second channel access procedure is performed after identifying the second sidelink message based at least in part on the satisfaction of the matching identifier criterion.

[0183] Aspect 10: According to the method of aspect 9, wherein the first identifier and the second identifier include logical identifiers associated with the second stage SCI message.

[0184] Aspect 11: The method according to any one of Aspects 6 to 10, wherein the second sidelink message includes a sidelink shared channel message and a sidelink control channel message.

[0185] Aspect 12: The method according to any one of Aspects 1 to 11, the method further comprising: avoiding the transmission of a sidelink message in the second part of the COT based at least in part on the resource set of the sidelink channel reserved for the second sidelink message in the second part of the COT, wherein the second sidelink message is received based at least in part on avoiding the transmission of a sidelink message in the second part of the COT.

[0186] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: avoiding processing information included in the second-stage SCI message based at least in part on the fact that the second sidelink message is received within the resource set reserved for the second sidelink message.

[0187] Aspect 14: The method according to any one of Aspects 1 to 13, wherein identifying the second sidelink message includes receiving the second sidelink message, the method further comprising: initiating a decoding process for decoding information included in the second sidelink message based at least in part on receiving the second sidelink message, wherein the second channel access process is performed prior to the completion of the decoding process.

[0188] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the first channel access procedure includes a type 1 channel access procedure, and the second channel access procedure includes a type 2 channel access procedure.

[0189] Aspect 16: A first UE for wireless communication, the first UE comprising: one or more memories storing processor-executable code; and one or more processors coupled to the one or more memories and capable of operating individually or jointly to execute the code to cause the first UE to perform a method according to any one of aspects 1 to 15.

[0190] Aspect 17: A first UE for wireless communication, the first UE comprising at least one component for performing the method according to any one of aspects 1 to 15.

[0191] Aspect 18: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by a processor to perform the method according to any one of Aspects 1 to 15.

[0192] It should be noted that the methods described herein describe possible specific implementations, and the operations and steps can be rearranged or otherwise modified, and other specific implementations are also possible. Furthermore, aspects from two or more of these methods can be combined.

[0193] While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR may be used in most of the description, the techniques described herein are also applicable to networks other than LTE, LTE-A, LTE-A Pro, or NR networks. For example, the techniques described are applicable to a variety of other wireless communication systems, such as Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, Flash-OFDM, and other systems and radio technologies not explicitly mentioned herein.

[0194] The information and signals described herein can be represented using any of a variety of different techniques and methods. For example, data, instructions, commands, information, signals, bits, symbols, and chips mentioned throughout the description can be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or optical particles, or any combination thereof.

[0195] The various exemplary blocks and components described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, CPU, FPGA or other programmable logic device, discrete gate or transistor logic unit, discrete hardware component, or any combination thereof, designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in alternative embodiments, a processor may be any processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors working in conjunction with a DSP core, or any other such configuration). Any function or operation described herein that can be performed by a processor may be performed by multiple processors capable of performing the described functions or operations individually or jointly.

[0196] The functions described herein can be implemented using hardware, software executed by a processor, firmware, or any combination thereof. When implemented using software executed by a processor, the functions can be stored as one or more instructions or code on a computer-readable medium or transmitted using one or more instructions or code on a computer-readable medium. Other examples and specific implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functions described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these. Features implementing the functions can also be physically located in various locations, including portions distributed such that the functions are implemented in different physical locations.

[0197] Computer-readable media includes both non-transitory computer storage media and communication media, encompassing any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible by a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM), flash memory, compressed optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be used to carry or store desired program code components in the form of instructions or data structures, and accessible by a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, if software is transmitted from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included within the definition of computer-readable media. As used herein, disks and optical discs include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks can magnetically reproduce data, and optical discs can optically reproduce data using lasers. Combinations of the above are also included within the scope of computer-readable media. Any function or operation described herein that can be performed by memory can be performed by multiple memories capable of performing the described function or operation individually or jointly.

[0198] As used herein, the word "or" in a list of items (e.g., a list of items accompanied by phrases such as "at least one of" or "one or more of") in the claims indicates an inclusive list, such that a list of at least one of, for example, 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). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an example step described as "based on condition A" could be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

[0199] As used herein, including in claims, the article “a” preceding a noun is open-ended and is understood to refer to “at least one” or “one or more” of those nouns. Therefore, the terms “a,” “at least one,” “one or more,” and “at least one of one or more” are interchangeable. For example, where a claim enumerates “components” performing one or more functions, each of the individual functions may be performed by a single component or by any combination of multiple components. Thus, the term “component” having a characteristic or performing a function may refer to “at least one of one or more components” having a particular characteristic or performing a particular function. Subsequent references to a component introduced with the article “a” using the terms “the” or “the” can refer to any or all of the one or more components. For example, a component introduced with the article “a” can be understood to mean “one or more components,” and subsequent reference to “the component” in a claim can be understood as equivalent to referring to “at least one of the one or more components.” Similarly, subsequent references to a component introduced with the terms “the” or “the” as “one or more components” can refer to any or all of those one or more components. For example, reference to "the one or more components" in the subsequent claims can be understood as equivalent to reference to "at least one of the one or more components".

[0200] The term "determine" encompasses a variety of actions, and therefore, "determine" can include calculation, computation, processing, derivation, investigation, lookup (such as by searching in a table, database, or other data structure), identification, and similar actions. Furthermore, "determine" can include receiving (e.g., receiving information), accessing (e.g., accessing data stored in memory), etc. Moreover, "determine" can include parsing, acquiring, selecting, choosing, creating, and other similar actions.

[0201] In the accompanying drawings, similar components or features may have the same reference numerals. Furthermore, various components of the same type can be distinguished by adding a dash after the reference numeral and a second reference numeral to differentiate them. If only the first reference numeral is used in the description, the description can be applied to any of the similar components having the same first reference numeral, regardless of the second or other subsequent reference numerals.

[0202] The description herein, illustrated with reference to the accompanying drawings, describes an example configuration and does not represent all achievable examples or those within the scope of the claims. The term "example" as used herein means "serving as an example, instance, or illustration," not "preferred" or "advantageous over other examples." The detailed description includes specific details used to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concept of the described examples.

[0203] The description herein is provided to enable those skilled in the art to implement or use this disclosure. Various modifications to this disclosure will be apparent to those skilled in the art, and the general principles defined herein may be applied to other variations without departing from the scope of this disclosure. Therefore, this disclosure is not limited to the examples and designs described herein, but should be granted the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A first user equipment (UE), the first user equipment (UE) comprising: One or more memories, wherein the one or more memories store processor-executable code; and One or more processors, said one or more processors coupled to said one or more memories and capable of operating individually or jointly to execute said code to enable the first UE: The sidelink channel is monitored as part of the first channel access procedure for accessing the channel occupancy time (COT) within the sidelink channel; Send a second-phase sidelink control information message that includes COT sharing information for sharing the COT with one or more additional UEs; Send a first sidelink message within the first part of the COT; The second sidelink message expected to be received within the second part of the COT is identified at least in part based on the transmission of the second-stage sidelink control information message; After identifying the second sidelink message at least in part based on the fact that the second sidelink message is expected to be within the resource set of the sidelink channel reserved for the second sidelink message, a second channel access procedure for accessing the COT is performed; as well as The third side link message is sent within the third part of the COT, at least in part based on the completion of the second channel access procedure.

2. The first UE according to claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: A fourth sidelink message is sent to a second UE, wherein the resource set is reserved for a feedback message in response to the fourth sidelink message, the second sidelink message including the feedback message, and wherein the second channel access procedure is performed after the second sidelink message is identified, at least in part, based on the expectation that the feedback message is expected to be within the resource set reserved for the feedback message.

3. The first UE according to claim 2, wherein a second-stage sidelink control information message, including the COT sharing information, is sent to the second UE, wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on sending the COT sharing information to the second UE and the feedback message identifying the second UE.

4. The first UE according to claim 3, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: The satisfaction of the matching identifier criterion is identified at least in part based on the matching of a first identifier within the fourth sidelink message with a second identifier within the COT shared information, wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on the satisfaction of the matching identifier criterion.

5. The first UE according to claim 4, wherein the first identifier and the second identifier include logical identifiers associated with the second phase sidelink control information message.

6. The first UE according to claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: The second UE receives a fourth sidelink message, wherein the fourth sidelink message reserves the resource set for the second sidelink message, and wherein the second channel access procedure is performed after the second sidelink message is identified, at least in part, based on the expectation that the second sidelink message is within the resource set reserved by the fourth sidelink message.

7. The first UE according to claim 6, wherein the fourth sidelink message includes a first-stage sidelink control information message.

8. The first UE of claim 6, wherein a second-stage sidelink control information message, including the COT sharing information, is sent to the second UE, wherein the second channel access procedure is performed after identifying the second sidelink message based at least in part on sending the COT sharing information to the second UE and identifying the second sidelink message from the second UE.

9. The first UE of claim 6, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: The satisfaction of the matching identifier criterion is identified at least in part based on the matching of a first identifier within the fourth sidelink message with a second identifier within the COT shared information, wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on the satisfaction of the matching identifier criterion.

10. The first UE of claim 9, wherein the first identifier and the second identifier include logical identifiers associated with the second phase sidelink control information message.

11. The first UE according to claim 6, wherein the second sidelink message includes a sidelink shared channel message and a sidelink control channel message.

12. The first UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: The transmission of sidelink messages within the second part of the COT is avoided at least in part based on the resource set that reserves the sidelink channel for the second sidelink message within the second part of the COT, wherein the second sidelink message is received at least in part based on avoiding the transmission of sidelink messages within the second part of the COT.

13. The first UE of claim 1, wherein the one or more processors are further capable of operating individually or jointly to execute the code to cause the first UE to: At least in part, processing of information included in the second-stage sidelink control information message is avoided because the second sidelink message is received within the resource set reserved for the second sidelink message.

14. The first UE of claim 1, wherein identifying the second sidelink message includes receiving the second sidelink message, wherein the one or more processors are also capable of operating individually or jointly to execute the code to cause the first UE to: A decoding process for decoding information included in the second sidelink message is initiated at least in part based on the receipt of the second sidelink message, wherein the second channel access process is performed before the completion of the decoding process.

15. The first UE according to claim 1, wherein the first channel access procedure includes a type 1 channel access procedure, and wherein the second channel access procedure includes a type 2 channel access procedure.

16. A method for conducting wireless communication at a first user equipment (UE), the method comprising: The sidelink channel is monitored as part of the first channel access procedure for accessing the channel occupancy time (COT) within the sidelink channel; Send a second-phase sidelink control information message that includes COT sharing information for sharing the COT with one or more additional UEs; Send a first sidelink message within the first part of the COT; The second sidelink message expected to be received within the second part of the COT is identified at least in part based on the transmission of the second-stage sidelink control information message; After identifying the second sidelink message at least in part based on the fact that the second sidelink message is expected to be within the resource set of the sidelink channel reserved for the second sidelink message, a second channel access procedure for accessing the COT is performed; as well as The third side link message is sent within the third part of the COT, at least in part based on the completion of the second channel access procedure.

17. The method according to claim 16, further comprising: A fourth sidelink message is sent to a second UE, wherein the resource set is reserved for a feedback message in response to the fourth sidelink message, the second sidelink message including the feedback message, and wherein the second channel access procedure is performed after the second sidelink message is identified, at least in part, based on the expectation that the feedback message is expected to be within the resource set reserved for the feedback message.

18. The method of claim 17, wherein the second phase sidelink control information message of the COT sharing information is sent to the second UE, and wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on sending the COT sharing information to the second UE and the feedback message identifying the second UE.

19. The method according to claim 18, further comprising: The satisfaction of the matching identifier criterion is identified at least in part based on the matching of a first identifier within the fourth sidelink message with a second identifier within the COT shared information, wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on the satisfaction of the matching identifier criterion.

20. The method of claim 19, wherein the first identifier and the second identifier include logical identifiers associated with the second phase side link control information message.

21. The method according to claim 16, further comprising: The second UE receives a fourth sidelink message, wherein the fourth sidelink message reserves the resource set for the second sidelink message, and wherein the second channel access procedure is performed after the second sidelink message is identified, at least in part, based on the expectation that the second sidelink message is within the resource set reserved by the fourth sidelink message.

22. The method of claim 21, wherein the fourth sidelink message includes a first-stage sidelink control information message.

23. The method of claim 21, wherein the second phase sidelink control information message of the COT sharing information is sent to the second UE, and wherein the second channel access procedure is performed after identifying the second sidelink message based at least in part on sending the COT sharing information to the second UE and identifying the second sidelink message from the second UE.

24. The method according to claim 21, further comprising: The satisfaction of the matching identifier criterion is identified at least in part based on the matching of a first identifier within the fourth sidelink message with a second identifier within the COT shared information, wherein the second channel access procedure is performed after the second sidelink message is identified at least in part based on the satisfaction of the matching identifier criterion.

25. The method of claim 24, wherein the first identifier and the second identifier include logical identifiers associated with the second phase side link control information message.

26. The method of claim 21, wherein the second sidelink message includes a sidelink shared channel message and a sidelink control channel message.

27. The method according to claim 16, further comprising: The transmission of sidelink messages within the second part of the COT is avoided at least in part based on the resource set that reserves the sidelink channel for the second sidelink message within the second part of the COT, wherein the second sidelink message is received at least in part based on avoiding the transmission of sidelink messages within the second part of the COT.

28. The method according to claim 16, further comprising: At least in part, processing of information included in the second-stage sidelink control information message is avoided because the second sidelink message is received within the resource set reserved for the second sidelink message.

29. The method of claim 16, wherein identifying the second sidelink message includes receiving the second sidelink message, the method further comprising: A decoding process for decoding information included in the second sidelink message is initiated at least in part based on the receipt of the second sidelink message, wherein the second channel access process is performed before the completion of the decoding process.

30. A non-transitory computer-readable medium storing code for wireless communication, said code comprising instructions executable by one or more processors to perform the following operations: The sidelink channel is monitored as part of the first channel access procedure for accessing the channel occupancy time (COT) within the sidelink channel; Send a second-phase sidelink control information message that includes COT sharing information for sharing the COT with one or more additional UEs; Send a first sidelink message within the first part of the COT; The second sidelink message expected to be received within the second part of the COT is identified at least in part based on the transmission of the second-stage sidelink control information message; After identifying the second sidelink message at least in part based on the fact that the second sidelink message is expected to be within the resource set of the sidelink channel reserved for the second sidelink message, a second channel access procedure for accessing the COT is performed; as well as The third side link message is sent within the third part of the COT, at least in part based on the completion of the second channel access procedure.

Images