RELATED APPLICATIONS

[0001] This application claims priority to U.S. Patent Application Serial No. 63/335,640, filed 27 April 2022 entitled “CHANNEL OCCUPANCY TIME SHARING TERMINATION,” and to U.S. Patent Application Serial No. 63/335,630 filed 27 April 2022 entitled “CHANNEL OCCUPANCY TIME SHARING TERMINATION,” the disclosures of which are incorporated by reference herein in their entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to wireless communications, and more specifically to sidelink communications.

BACKGROUND

[0003] A wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB), a next-generation NodeB (gNB), or other suitable terminology. Each network communication device, such as a base station, may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE), or other suitable terminology. The wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system, such as time resources (e.g., symbols, slots, subslots, mini-slots, aggregated slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers). Additionally, the wireless communications system may support wireless communications across various radio access technologies (RATs) including third generation (3G) RAT, fourth generation (4G) RAT, fifth generation (5G) RAT, and other suitable RATs beyond 5G. In some cases, a wireless communications system may be a non-terrestrial network (NTN), which may support various communication devices for wireless communications in the NTN. For example, an NTN may include network entities onboard non-terrestrial vehicles such as satellites, unmanned aerial vehicles (UAV), and high-altitude platforms systems (HAPS), as well as network entities on the ground, such as gateway entities capable of transmitting and receiving over long distances.

[0004] In addition to utilizing network infrastructure for wireless communications, UEs can utilize sidelink communications for direct device-to-device communication. Sidelink communication, for instance, enables UEs to exchange wireless signals directly between the devices, such as independent of a network infrastructure component, e.g., a base station.

SUMMARY

[0005] The present disclosure relates to methods, apparatuses, and systems that support channel occupancy time (COT) sharing termination. In implementations, a first UE and a second UE engage in COT sharing. For instance, the first UE obtains a COT resource and shares the COT resource with the second UE, and the second UE utilizes at least a portion of the COT resource for transmission. The second UE can then determine that it is finished using the COT resource and can transmit an indicator ("COT sharing termination indicator" and/or “COT indicator”) to the first UE that the second UE is not using at least some of the remaining duration of the shared COT for its transmissions. The COT sharing termination indicator can be transmitted as part of sidelink control information (SCI) and can indicate a time instance at which the second UE is to terminate COT sharing. By implementing aspects of the present disclosure, COT resources that are available after COT sharing termination can be used for other purposes, such as for transmission by the first UE and/or for sharing with another UE. Thus, wireless resources are conserved by enabling unused COT to be utilized.

[0006] Some implementations of the method and apparatuses described herein may include wireless communication at an apparatus (e.g., a UE), and the apparatus generates a COT indicator to indicate a termination of transmission by a first apparatus (e.g., a first UE) as part of a shared COT between the first apparatus and a second apparatus (e.g., a second UE), the COT indicator including an indication of a time instance at which transmission by the first apparatus as part of the shared COT is to be terminated; and transmits the COT indicator as part of SCI to the second apparatus.

[0007] In some implementations of the method and apparatuses described herein, the indication of the time instance includes a time at which the COT indicator is transmitted by the first apparatus; the indication of the time instance includes an offset value to be applied to a time at which the COT indicator is transmitted by the first apparatus; the indication of the time instance is selected from a number of offset values, and the number of offset values is based at least in part on a number of slots in a physical sidelink feedback channel (PSFCH) period; the indication of the time instance includes one or more offset values represented by a state of a field of the COT indicator; the COT indicator is included as part of first stage SCI; the second apparatus includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and the SCI is addressed to a destination identifier of the second UE; the COT indicator is transmitted in a first slot, and the indicator of the time instance identifies a slot subsequent to the first slot at which transmission by the first apparatus as part of the shared COT is to be terminated; further including: receiving COT sharing termination configuration information from a network node; and generating the COT indicator based at least in part on the COT sharing termination configuration information; the COT indicator is transmitted in a first slot, and the indicator of the time instance includes an index value that correlates to a slot subsequent to the first slot at which transmission by the first apparatus as part of the shared COT is to be terminated; further including receiving COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission of the COT indicator; and selecting the index value from the different index values to identify the slot subsequent to the first slot.

[0008] Some implementations of the method and apparatuses described herein may include wireless communication at an apparatus (e.g., a UE), and the apparatus receives, at a first apparatus (e.g., a first UE), SCI from a second apparatus (e.g., a second UE) including a COT indicator indicating a termination of transmission by the second apparatus as part of a shared COT between the first apparatus and the second apparatus, the COT indicator including an indication of a time instance at which transmission by the second apparatus as part of the shared COT is to be terminated and/or a time instance at which transmission by the first apparatus as part of the shared COT may commence or recommence; and determines, based at least in part on the COT indicator, when the COT sharing between the first apparatus and the second apparatus is to be terminated and/or a time instance at which transmission by the first apparatus as part of the shared COT may commence or recommence.

[0009] In some implementations of the method and apparatuses described herein, the first apparatus includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and the SCI is addressed to a destination identifier of the first apparatus; the COT indicator is received as part of first stage SCI; the indication of the time instance includes an offset value, further including applying the offset value to a slot in which the COT indicator is transmitted or received to determine the time instance at which transmission by the second apparatus as part of the shared COT is to be terminated and/or a time instance at which transmission by the first apparatus as part of the shared COT may commence or recommence; further including: receiving COT sharing termination configuration information from a network node; and processing the COT indicator based at least in part on the COT sharing termination configuration information; further including: receiving COT sharing termination configuration information from a network node; and determining whether to utilize or further share a remaining COT based at least in part on the COT sharing termination configuration information and the COT indicator; the indication of the time instance includes an index value, further including receiving COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission of a COT indicator; and identifying the time instance by correlating the index value to the different index values to identify a slot at which transmission by the second apparatus as part of the shared COT is to be terminated and/or a slot at which transmission by the first apparatus as part of the shared COT may commence or recommence; further including determining whether to utilize or further share a remaining COT based on number of slots between the indication of a time instance at which transmission by the second apparatus as part of the shared COT is to be terminated and/or a time instance at which transmission by the first apparatus as part of the shared COT may commence or recommence, and a remaining maximum COT (MCOT) for the shared COT between the first apparatus and the second apparatus.

[0010] Some implementations of the method and apparatuses described herein may include wireless communication at a device (e.g., a network device such as a base station), and the device generates COT sharing termination configuration information identifying one or more termination parameters for terminating COT sharing between a set of UE; and transmits the COT sharing termination configuration information to one or more UEs.

[0011] In some implementations of the method and apparatuses described herein, the one or more termination parameters include an indication of whether the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; the one or more termination parameters include one or more conditions under which the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; the one or more termination parameters include a format for the one or more UEs to generate COT sharing termination information; the one or more termination parameters include correlations between different index values and different slot offsets for the one or more UEs to indicate termination of transmission by the one or more UEs as part of shared COT; the slot offsets are based at least in part on slot offsets from a slot in which the one or more UEs transmit a COT indicator indicating a termination of transmission by the one or more UEs as part of shared COT.

BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Various aspects of the present disclosure for COT sharing termination are described with reference to the following Figures. The same numbers may be used throughout to reference like features and components shown in the Figures.

[0013] FIG. 1 illustrates an example of a wireless communications system that supports COT sharing termination in accordance with aspects of the present disclosure.

[0014] FIG. 2 illustrates an example of a system that supports COT sharing termination in accordance with aspects of the present disclosure.

[0015] FIG. 3 illustrates an example block diagram of components of a device (e.g., a UE) that supports COT sharing termination in accordance with aspects of the present disclosure.

[0016] FIG. 4 illustrates an example block diagram of components of a device (e.g., a base station and/or other network device] that supports COT sharing termination in accordance with aspects of the present disclosure.

[0017] FIGs. 5-10 illustrate flowcharts of methods that support COT sharing termination in accordance with aspects of the present disclosure.

DETAILED DESCRIPTION

[0018] Implementations of COT sharing termination are described, such as related to methods, apparatuses, and systems that support COT sharing termination. The described implementations, for example, enable COT resources that are being used as part of COT sharing between two devices to be released for use by another device, such as by another device involved in the COT sharing and/or a different device.

[0019] In some wireless communications systems, mechanisms are provided for operation in unlicensed spectrum to share a COT with another device. One use of such COT sharing is that a device initiating a COT can grant another device the right to use the initiated COT without requiring the target device to initiate its own COT. However, a UE engaging in COT sharing may not have sufficient data to transmit for the full remainder of the shared COT or may terminate transmission because it intends to receive in some slots of the remaining shared COT. In that case, at least some of the remaining shared COT resources can no longer be used by neither the UE transmitting nor receiving the COT sharing indicator.

[0020] Accordingly, in implementations for COT sharing termination, ways for notifying devices (e.g., UEs) COT sharing termination are described. For instance, in implementations a first UE and a second UE engage in COT sharing. The first UE, for example, obtains a COT resource and shares the COT resource with the second UE, and the second UE utilizes at least a portion of the COT resource for transmission. The second UE can then determine that it is finished using the COT resource and can transmit an indicator ("COT sharing termination indicator") to the first UE indicating that the second UE is not using at least some of the remaining duration of the shared COT for its transmissions. The COT sharing termination indicator can be transmitted as part of SCI. By implementing aspects of the present disclosure, COT resources that are available after COT sharing termination can be used for other purposes, such as for transmission by the first UE and/or for sharing with another UE. Thus, wireless resources are conserved by enabling unused COT to be utilized.

[0021] Aspects of the present disclosure are described in the context of a wireless communications system. Aspects of the present disclosure are further illustrated and described with reference to device diagrams and flowcharts that relate to COT sharing termination.

[0022] FIG. 1 illustrates an example of a wireless communications system 100 that supports COT sharing termination in accordance with aspects of the present disclosure. The wireless communications system 100 may include one or more base stations 102, one or more UEs 104, and a core network 106. The wireless communications system 100 may support various radio access technologies. In some implementations, the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-Advanced (LTE-A) network. In some other implementations, the wireless communications system 100 may be a 5G network, such as a NR network. In other implementations, the wireless communications system 100 may be a combination of a 4G network and a 5G network. The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA), frequency division multiple access (FDMA), or code division multiple access (CDMA), etc.

[0023] The one or more base stations 102 may be dispersed throughout a geographic region to form the wireless communications system 100. One or more of the base stations 102 described herein may be, or include, or may be referred to as a base transceiver station, an access point, a NodeB, an eNodeB (eNB), a next-generation NodeB (gNB), a Radio Head (RH), a relay node, an integrated access and backhaul (IAB) node, or other suitable terminology. A base station 102 and a UE 104 may communicate via a communication link 108, which may be a wireless or wired connection. For example, a base station 102 and a UE 104 may perform wireless communication over a NR-Uu interface.

[0024] A base station 102 may provide a geographic coverage area 110 for which the base station

102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc.) for one or more UEs 104 within the geographic coverage area. For example, a base station 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc.) according to one or multiple radio access technologies. In some implementations, a base station 102 may be moveable, such as when implemented as a gNB onboard a satellite or other non-terrestrial station (NTS) associated with a non-terrestrial network (NTN). In some implementations, different geographic coverage areas 110 associated with the same or different radio access technologies may overlap, and different geographic coverage areas 110 may be associated with different base stations 102. Information and signals described herein may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof. [0025] The one or more UEs 104 may be dispersed throughout a geographic region or coverage area 110 of the wireless communications system 100. A UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a handheld device, a customer premise equipment (CPE), a subscriber device, or as some other suitable terminology. In some implementations, the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples. Additionally, or alternatively, a UE 104 may be referred to as an Internet-of-Things (loT) device, an Internet-of-Everything (loE) device, or as a machine-type communication (MTC) device, among other examples. In some implementations, a UE 104 may be stationary in the wireless communications system 100. In other implementations, a UE 104 may be mobile in the wireless communications system 100, such as an earth station in motion (ESIM).

[0026] The one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in FIG. 1. A UE 104 may be capable of communicating with various types of devices, such as the base stations 102, other UEs 104, or network equipment (e.g., the core network 106, a relay device, a gateway device, an integrated access and backhaul (IAB) node, a location server that implements the location management function (LMF), or other network equipment). Additionally, or alternatively, a UE 104 may support communication with other base stations 102 or UEs 104, which may act as relays in the wireless communications system 100.

[0027] A UE 104 may also support wireless communication directly with other UEs 104 over a communication link 112. For example, a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link. In some implementations, such as vehicle-to-vehicle (V2V) deployments, vehicle-to-everything (V2X) deployments, or cellular- V2X deployments, the communication link 112 may be referred to as a sidelink. For example, a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.

[0028] A base station 102 may support communications with the core network 106, or with another base station 102, or both. For example, a base station 102 may interface with the core network 106 through one or more backhaul links 114 (e.g., via an SI, N2, or other network interface). The base stations 102 may communicate with each other over the backhaul links 114 (e.g., via an X2, Xn, or another network interface). In some implementations, the base stations 102 may communicate with each other directly (e.g., between the base stations 102). In some other implementations, the base stations 102 may communicate with each other indirectly (e.g., via the core network 106). In some implementations, one or more base stations 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC). The ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as remote radio heads, smart radio heads, gateways, transmissionreception points (TRPs), and other network nodes and/or entities.

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

[0030] According to implementations, a UE 104a and a UE 104b can communicate with one another via sidelink connectivity 116. In conjunction with the sidelink connectivity 116 the UEs 104a, 104b can engage in COT sharing to enable various COT resources to be shared. For instance, the UE 104a (e.g., a Tx UE) acquires COT resources (e.g., in an unlicensed spectrum) and performs COT sharing 118 to share COT resources with the UE 104b, e.g., an Rx UE. As part of the COT sharing 118, for instance, the UE 104a notifies the UE 104b over the sidelink connectivity 116 that the UE 104a has a COT resource that the UE 104a can share with the 104b. Accordingly, the UE 104b performs COT sharing 120 to use at least part of a COT duration in the COT shared by the UE 104a. The UE 104b, for instance, can use at least part of the remaining COT duration to transmit control and/or data information to the UE 104a and/or a different UE 104.

[0031] Further to implementations, the UE 104b determines that it is finished with the COT sharing 120, such as based on determining that the UE 104b has no more data to transmit over a remaining COT and/or that the UE 104b intends to receive data in one or more slots of the remaining COT. Accordingly, the UE 104b transmits a COT sharing termination notification 122 notifying the UE 104a that the UE 104b intends to terminate the COT sharing 120. The COT sharing termination notification 122, for instance, includes an indication that the UE 104b is not using and/or will not use at least some of the remaining COT for transmission by the UE 104b. The COT sharing termination notification 122, for example, can be transmitted to the UE 104a as part of SCI. The COT sharing termination notification 122 can also include an indication of a time instance at which transmission by the UE 104b as part of the COT sharing 120 is to be terminated.

[0032] Further to implementations, a base station 102 and/or other network entity can communicate COT sharing termination configuration 124 information to UEs 104 to specify different parameters for terminating COT sharing. The COT sharing termination configuration 124, for instance, can indicate whether the UEs 104 are to communicate COT sharing termination information to one another. Further, the COT sharing termination configuration 124 can specify a format (e.g., a data format) for communicating COT sharing termination information. In at least one implementation, the COT sharing termination configuration 124 can specify a way in which COT sharing termination information is to be communicated among the UEs 104, such as via SCI, PSFCH, and so forth. Example implementations of the COT sharing termination configuration 124 are discussed throughout this disclosure.

[0033] FIG. 2 illustrates an example of a system 200 that supports COT sharing termination in accordance with aspects of the present disclosure. The system 200 may use the wireless communications system 100 and/or be implemented with the wireless communications system. In the system 200 the UEs 104a, 104b are engaged in the COT sharing 118, 120, respectively, such as described with reference to the wireless communications system 100. As part of the COT sharing 118, 120, the UEs 104a, 104b share a COT resource 202 associated with a COT duration 204. The COT duration 204, for instance, represents a maximum COT for the COT resource 202.

[0034] Further to the COT sharing 120, the UE 104b performs shared COT transmission 206 for data transmission over the COT resource 202, such as over sidelink to the UE 104a and/or other UE 104. Further, a termination event 208 occurs indicating that the UE 104b will terminate the COT sharing 120. The termination event 208, for instance, is based on the UE 104b having no more data to transmit using the COT resource 202 and/or that the UE 104b will receive data from another UE transmitted in one or more slots of the remaining COT resource 202. Accordingly, the UE 104b generates a COT sharing termination notification 122 and transmits the COT sharing termination notification 122 to the UE 104a. The UE 104b can transmit the COT sharing termination notification 122 in various ways, such as via SCI, PSFCH, and so forth.

[0035] The COT sharing termination notification 122 notifies the UE 104a that the UE 104b is terminating the COT sharing 120 and includes an indication of a time instance 210 at which transmission by the UE 104b as part of the COT sharing 120 is to be terminated. As further detailed throughout this disclosure, the time instance 210 can be identified in various ways. Accordingly, the UE 104a receives the COT sharing termination notification 122 and identifies the time instance 210 at which the UE 104b is to terminate the COT sharing 120, e.g., to stop transmission using the COT resource 202. In at least one implementation the UE 104a can perform an action based on the COT sharing termination. For instance, if a remaining COT duration 212 is sufficiently long (e.g., larger than a threshold remaining COT duration), the UE 104a can utilize the remaining COT duration 212 for its own transmissions and/or can share the remaining COT duration 212 with a different UE 104.

[0036] In some wireless communications systems, mechanisms are provided for operation in unlicensed spectrum to share a COT with another device. One use of such COT sharing is that a device initiating a COT can grant another device the right to use the initiated COT without requiring the target device to initiate its own COT. Initiating a COT may involve a certain sensing time before transmissions are allowed, while starting transmission in a shared COT may require little sensing or a fraction of sensing time specified for initiating a COT.

[0037] In some cellular topologies with a centralized scheduler, a gNB may initiate a COT and may share this COT with one or more UEs; or a UE may initiate a COT and may share this COT with a gNB. The sharing of a COT may be indicated by a specific field in downlink control information or uplink control information. The COT sharing indicator may include means to indicate the maximum remaining duration of the COT being shared. A UE receiving a COT sharing indicator may not have sufficient data to transmit for the full remainder of the shared COT or may terminate transmission because it intends to receive in some slots of the remaining shared COT. In such scenarios, at least some of the remaining shared COT resources can no longer be used by neither the UE transmitting nor receiving the COT sharing indicator, which is addressed by the present disclosure.

[0038] In some wireless communications systems, for sidelink unicast transmission, a receiver UE (RX UE) can send acknowledgement (ACK) if it has successfully decoded a TB carried in a PSSCH or can send negative ACK (NACK) if it has not decoded the TB after decoding Ist-stage SCI. For SL groupcast transmissions, two options (option 1 and option 2) can be supported for the SL HARQ feedback in NR V2X. For option 1, an RX UE can transmit NACK if it has not successfully decoded the TB (e.g., after decoding the Ist-stage SCI -stage SCI) and if its relative distance to the transmitter UE (TX UE) is less than or equal to a specified communication range, e.g., as indicated in 2nd-stage SCI. Otherwise, the RX UE may not transmit any HARQ feedback. As the HARQ feedback for this option may only consist of NACK, option 1 can be referred to as NACK-only feedback.

[0039] A PSFCH symbol that can be used for the HARQ feedback for a given PSSCH transmission corresponds to a PSFCH symbol in the first slot with PSFCH after a configured number of K slots after the PSSCH. K represents the minimum number of slots within the resource pool between a slot with a PSSCH transmission and the slot containing PSFCH for the HARQ feedback of this transmission. For instance, consider that the last symbol of a PSSCH transmission is on slot n. The HARQ feedback for this transmission can be expected in slot n + a, where a is the smallest integer equal or higher than K such that slot n + a contains PSFCH. For example, if an earliest slot for the HARQ feedback (slot n+a) does not contain PSFCH, then the HARQ feedback is sent at the next slot containing PSFCH, e.g., after slot n+a. A time gap of at least K slots allows considering the RX UE’s processing delay in decoding the PSCCH and generating the HARQ feedback. In some specifications K can be equal to 2 or 3, and a single value of K can be configured per resource pool. This allows several RX UEs using the same resource pool to utilize the same mapping of PSFCH resource(s) for the HARQ feedback. With the parameter K, the N PSSCH slots associated with a slot with PSFCH can be determined. In an example with K=3, the N=4 PSSCH slots associated with the PSFCHs at slot n+6 correspond to PSSCH slots n, n+1, n+2, and n+3.

[0040] Further, with L sub-channels in a resource pool and N PSSCH slots associated with a slot containing PSFCH, there can then be N times L sub-channels associated with a PSFCH symbol. With M PRBs available for PSFCH in a PSFCH symbol, there can be M PRBs available for the HARQ feedback of transmissions over N times L sub-channels. With M configured to be a multiple of N times L, then a distinct set of M _set = M/(N ■ L) PRBs can be associated with the HARQ feedback for each sub-channel within a PSFCH period. The first set of M _set PRBs among the M PRBs available for PSFCH can be associated with the HARQ feedback of a transmission in the first sub-channel in the first slot. The second set of M _set PRBs can be associated with the HARQ feedback of a transmission in the first sub-channel in the second slot, and so on. For example if N = 4, L = 3 and with all PRBs in a PSFCH symbol available for PSFCH, the HARQ feedback for a transmission at PSSCH x can be sent on the set x of M _set PRBs in the corresponding PSFCH symbol, with x=l,... , 12. For a transmission in a PSSCH with LPSSCH>1 sub-channels, LPSSCH times Mset PRBs can be available for the HARQ feedback of this transmission.

[0041] Further, a set of M _se t PRBs associated with a sub-channel can be shared among multiple RX UEs in scenarios that include ACK/NACK feedback for groupcast communications (option 2) or in scenarios that include different PSSCH transmissions in the same sub-channel. For each PRB available for PSFCH, there can be Q cyclic shift pairs available to support the ACK or NACK feedback of Q RX UEs within the PRB. For a resource pool, the number of cyclic shift pairs Q can be configured and can be equal to 1, 2, 3 or 6 according to some specifications. With each PSFCH used by one RX UE, F available PSFCHs can be used for the ACK/NACK feedback of up to F RX UEs. The F PSFCHs can be determined based on two options: either based on the LPSSCH sub-channels used by a PSSCH or based on the starting sub-channel used by a PSSCH, e.g., based on one subchannel for the case when LPSSCH >1. Thus, F can be computed based on: (i) LPSSCH sub-channels of a PSSCH; (ii) Mset PRBs for PSFCH associated with each sub-channel; and (iii) Q cyclic shift pairs available in each PRB. Depending on which of two supported HARQ feedback options is configured, there can be either then F= LPSSCH • Mset Q PSFCHs (associated with the LPSSCH sub-channels of a PSSCH) or F= Mset Q PSFCHs (associated with the starting sub-channel of a PSSCH) available for multiplexing the HARQ feedback for the PSSCH.

[0042] Similarly to PUCCH on the Uu interface, the available F PSFCHs can be indexed based on a PRB index (frequency domain) and a cyclic shift pair index (code domain). Depending on the configured option, there can be either LPSSCH • Mset or M _se t PRBs available for PSFCH. The mapping of the PSFCH index i (i=0, 1,2,... ,F-1) to the LPSSCH • Mset or Mset PRBs and to the Q cyclic shift pairs can be such that the PSFCH index i first increases with the PRB index until reaching the number of available PRBs for PSFCH, e.g., LPSSCH • Mset or M _set . Then, it can increase with the cyclic shift pair index, again with the PRB index, and so on. [0043] Among the F PSFCHs available for the HARQ feedback of a given transmission, an RX UE can select for its HARQ feedback the PSFCH with index i given by: i=(T iD+Rio)mod(F) where FID is the Layer 1 ID of the TX UE, such as indicated in the 2nd-stage SCI. /?ID=0 for unicast ACK/NACK feedback and groupcast NACK-only feedback (option 1). For groupcast ACK/NACK feedback (option 2), RID can be equal to the RX UE identifier within the group, which is indicated by higher layers. For a number X of RX UEs within a group, the RX UE identifier is an integer between 0 and X~1. An RX UE determines which PRB and cyclic shift pair is to be used for sending its HARQ feedback based on the PSFCH index i. The RX UE can use the first or second cyclic shift from the cyclic shift pair associated with the selected PSFCH index i in order to send NACK or ACK, respectively.

[0044] In implementations for COT sharing termination described herein, an Rx UE receiving a COT sharing indicator from a Tx UE through sidelink (e.g., PC5) may transmit an indicator ("COT sharing termination indicator") that it is not using at least some of the remaining duration of the shared COT for its transmissions. The COT sharing termination indicator can be transmitted as part of SCI. By implementing aspects of the present disclosure, COT resources that are available after COT sharing termination can be used for other purposes, such as for transmission by a Tx UE and/or for sharing with another UE. Thus, wireless resources are conserved by enabling unused COT to be utilized.

[0045] In implementations, an Rx UE can transmit a COT sharing termination indicator by means of an SCI transmission. The transmission of the COT sharing termination indicator can be facilitated by an explicit field in the SCI, where one state of the field indicates no COT sharing termination, and one or more states indicates COT sharing termination. In at least one example, the field can be an On/Off or True/False flag with the size of one bit. Alternatively or additionally, the COT sharing termination indicator can be conveyed by means of at least one state of a field, where the field includes at least one state indicating COT sharing. For example, a first state in the field indicates COT sharing, and a second state in the field indicates COT sharing termination. [0046] For instance, the COT sharing termination indicator indicates that the UE terminates its transmissions in a shared COT at a determined, predetermined, configured, and/or preconfigured time instant. The time instant may be determined as an offset in slots or symbols after transmission of the COT sharing termination indicator. For example, a COT sharing termination indicator transmitted in slot n can indicate that the transmission in slot n is the last transmission in the shared COT, e.g., a transmission by the terminating UE (if any) in slot n+1 and later is no longer part of the shared COT.

[0047] According to further implementations, a COT sharing termination indicator indicates a time instance after which the terminating UE terminates its transmissions in a shared COT, and/or equivalently a time instance at which a transmission by the UE, if any, is no longer part of the shared COT. This may be accomplished by a pre-determined association between a state (e.g., value) of the field conveying the COT sharing termination indicator and a slot or offset relative to the slot or symbol in which the COT sharing termination indicator is transmitted. For instance, a COT sharing termination indicator transmitted in slot n using a first state of the field conveying the COT sharing termination indicator can indicate that the transmission in a first slot is the last transmission in the shared COT, e.g., a transmission by the UE (if any) after the first slot and later is no longer part of the shared COT. Further, a COT sharing termination indicator transmitted in slot n using a second state of the field conveying the COT sharing termination indicator can indicate that the transmission in a second slot is the last transmission in the shared COT, e.g., a transmission by the UE (if any) after the second slot is no longer part of the shared COT, and so forth.

[0048] In an example (see, e.g., Table 1 below which represents an example implementation for a COT sharing termination indicator of two bits), a COT sharing termination indicator transmitted in slot n using a first state of a field conveying the COT sharing termination indicator can indicate that the transmission in slot n is the last transmission in the shared COT, e.g., a transmission by the UE (if any) in slot n+1 and later is no longer part of the shared COT. For instance, the first state of the field is associated with an offset of 0 slots. A COT sharing termination indicator transmitted in slot n using a second state of the field conveying the COT sharing termination indicator can indicate that the transmission in slot n+1 is the last transmission in the shared COT, e.g., a transmission by the UE (if any) in slot n+2 and later is no longer part of the shared COT. For instance, the second state of the field is associated with an offset of 1 slot. In at least one implementation, a number of states in the field conveying the COT sharing termination indicator associated with a COT sharing termination indicator is equivalent to a PSFCH periodicity.

Table 1: Slot Offset Values

[0049] Table 1 presents an example of a pre-determined association between a state (e.g., value) of a field conveying the COT sharing termination indicator and a slot or offset relative to the slot or symbol in which the COT sharing termination indicator is transmitted.

[0050] In an alternative or additional implementation, an association between a state (e.g., value) of the field conveying the COT sharing termination indicator and a slot or offset relative to the slot or symbol in which the COT sharing termination indicator is transmitted is configurable, such as depicted in example Table 2 below for a COT sharing termination indicator of two bits. For example, an RRC signal given by a gNB may establish the association, e.g., can provide configurable values for the COT sharing termination indicator states.

Table 2: Configurable Slot Offset Values [0051] Table 2 presents an example of a configurable association between a state (e.g., value) of the field conveying the COT sharing termination indicator and a slot or offset relative to the slot or symbol in which the COT sharing termination indicator is transmitted.

[0052] In at least one implementation, a COT sharing termination indicator can be transmitted as part of the Ist-stage SCI on PSCCH. The SCI, for instance, may be addressed to the destination ID of the device (e.g., a Tx UE) that indicated the shared COT and/or to the device that initiated the shared COT. In another example implementation, a UE is configured (e.g., by radio resource control (RRC) signalling from a gNB) whether it should transmit a COT sharing termination indicator as described herein. For instance, as introduced above, a base station can transmit COT sharing termination configuration information specifying different COT sharing termination behaviors that can be applied by a UE, and/or that are to be applied by a UE.

[0053] FIG. 3 illustrates an example of a block diagram 300 of a device 302 that supports COT sharing termination in accordance with aspects of the present disclosure. The device 302 may be an example of a UE 104 as described herein. The device 302 may support wireless communication and/or network signaling with one or more base stations 102, other UEs 104, network entities and devices, or any combination thereof. The device 302 may include components for bi-directional communications including components for transmitting and receiving communications, such as a communications manager 304, a processor 306, a memory 308, a receiver 310, a transmitter 312, and an I/O controller 314. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0054] The communications manager 304, the receiver 310, the transmitter 312, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communications manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0055] In some implementations, the communications manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 306 and the memory 308 coupled with the processor 306 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 306, instructions stored in the memory 308).

[0056] Additionally or alternatively, in some implementations, the communications manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 306. If implemented in code executed by the processor 306, the functions of the communications manager 304, the receiver 310, the transmitter 312, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0057] In some implementations, the communications manager 304 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 310, the transmitter 312, or both. For example, the communications manager 304 may receive information from the receiver 310, send information to the transmitter 312, or be integrated in combination with the receiver 310, the transmitter 312, or both to receive information, transmit information, or perform various other operations as described herein. Although the communications manager 304 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 304 may be supported by or performed by the processor 306, the memory 308, or any combination thereof. For example, the memory 308 may store code, which may include instructions executable by the processor 306 to cause the device 302 to perform various aspects of the present disclosure as described herein, or the processor 306 and the memory 308 may be otherwise configured to perform or support such operations.

[0058] For example, the communications manager 304 may support wireless communication and/or network signaling at a device (e.g., the device 302, a UE) in accordance with examples as disclosed herein. The communications manager 304 and/or other device components may be configured as or otherwise support an apparatus, such as a UE, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: generate at a first UE a COT indicator to indicate a termination of transmission by the first UE as part of a shared COT between the first UE and a second UE, the COT indicator including an indication of a time instance at which transmission by the first UE as part of the shared COT is to be terminated; and transmit the COT indicator as part of SCI to the second UE.

[0059] Additionally, the apparatus (e.g., a UE) includes any one or combination of: where the indication of the time instance includes a time at which the COT indicator is transmitted by the first UE; where the indication of the time instance includes an offset value to be applied to a time at which the COT indicator is transmitted by the first UE; where the indication of the time instance is selected from a number of offset values, and where the number of offset values is based at least in part on a number of slots in a PSFCH period; where the indication of the time instance includes one or more offset values represented by a state of a field of the COT indicator; where the COT indicator is included as part of first stage SCI; where the second UE includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and where the SCI is addressed to a destination identifier of the second UE.

[0060] Additionally, the apparatus (e.g., a UE) includes any one or combination of: where the COT indicator is transmitted in a first slot, and where the indicator of the time instance identifies a slot subsequent to the first slot at which transmission by the first UE as part of the shared COT is to be terminated; where the processor and the transceiver are configured to cause the first UE to: receive COT sharing termination configuration information from a network node; and generate the COT indicator based at least in part on the COT sharing termination configuration information; where the COT indicator is transmitted in a first slot, and where the indicator of the time instance includes an index value that correlates to a slot subsequent to the first slot at which transmission by the first UE as part of the shared COT is to be terminated; where the processor and the transceiver are configured to cause the first UE to: receive COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission of the COT indicator; and select the index value from the different index values to identify the slot subsequent to the first slot. [0061] The communications manager 304 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a UE, including generating a COT indicator to indicate a termination of transmission by a first UE as part of a shared COT between the first UE and a second UE, the COT indicator including an indication of a time instance at which transmission by the first UE as part of the shared COT is to be terminated; and transmitting the COT indicator as part of SCI to the second UE.

[0062] Additionally, wireless communication and/or network signaling at the UE includes any one or combination of: where the indication of the time instance includes a time at which the COT indicator is transmitted by the first UE; where the indication of the time instance includes an offset value to be applied to a time at which the COT indicator is transmitted by the first UE; where the indication of the time instance is selected from a number of offset values, and where the number of offset values is based at least in part on a number of slots in a PSFCH period; where the indication of the time instance includes one or more offset values represented by a state of a field of the COT indicator; where the COT indicator is included as part of first stage SCI; where the second UE includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and where the SCI is addressed to a destination identifier of the second UE; where the COT indicator is transmitted in a first slot, and where the indicator of the time instance identifies a slot subsequent to the first slot at which transmission by the first UE as part of the shared COT is to be terminated.

[0063] Additionally, wireless communication and/or network signaling at the UE includes any one or combination of: further including: receiving COT sharing termination configuration information from a network node; and generating the COT indicator based at least in part on the COT sharing termination configuration information; where the COT indicator is transmitted in a first slot, and where the indicator of the time instance includes an index value that correlates to a slot subsequent to the first slot at which transmission by the first UE as part of the shared COT is to be terminated; further including receiving COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission of the COT indicator; and selecting the index value from the different index values to identify the slot subsequent to the first slot.

[0064] The communications manager 304 and/or other device components may be configured as or otherwise support an apparatus, such as a UE, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: receive, at a first UE, SCI from a second UE including a COT indicator indicating a termination of transmission by the second UE as part of a shared COT between the first UE and the second UE, the COT indicator including an indication of a time instance at which transmission by the second UE as part of the shared COT is to be terminated and/or a time instance at which transmission by the first UE as part of the shared COT may commence or recommence; and determine, based at least in part on the COT indicator, when the COT sharing between the first UE and the second UE is to be terminated.

[0065] Additionally, the apparatus (e.g., a UE) includes any one or combination of: where the first UE includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and where the SCI is addressed to a destination identifier of the first UE; where the COT indicator is received as part of first stage SCI; where the indication of the time instance includes an offset value, and where the processor is configured to cause the UE apply the offset value to a slot in which the COT indicator is transmitted or received to determine the time instance at which transmission by the second UE as part of the shared COT is to be terminated and/or the time instance at which transmission by the first UE as part of the shared COT may commence or recommence; where the processor and the transceiver are configured to cause the first UE to: receive COT sharing termination configuration information from a network node; and process the COT indicator based at least in part on the COT sharing termination configuration information.

[0066] Additionally, the apparatus (e.g., a UE) includes any one or combination of: where the processor and the transceiver are configured to cause the first UE to: receive COT sharing termination configuration information from a network node; and determine whether to utilize or further share a remaining COT based at least in part on the COT sharing termination configuration information and the COT indicator; where the indication of the time instance includes an index value, and where the processor and the transceiver are configured to cause the first UE to: receive COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission or reception of a COT indicator; and identify the time instance by correlating the index value to the different index values to identify a slot at which transmission by the second UE as part of the shared COT is to be terminated and/or to identify a slot at which transmission by the first UE as part of the shared COT may commence or recommence); where the processor and the transceiver are configured to cause the first UE to determine whether to utilize or further share a remaining COT based on number of slots between the indication of a time instance at which transmission by the second UE as part of the shared COT is to be terminated, and a MCOT for the shared COT between the first UE and the second UE.

[0067] The communications manager 304 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a UE, including receiving, at a first UE, SCI from a second UE including a COT indicator indicating a termination of transmission by the second UE as part of a shared COT between the first UE and the second UE, the COT indicator including an indication of a time instance at which transmission by the second UE as part of the shared COT is to be terminated and/or a time instance at which transmission by the first UE as part of the shared COT may commence or recommence); and determining, based at least in part on the COT indicator, when the COT sharing between the first UE and the second UE is to be terminated.

[0068] Additionally, wireless communication and/or network signaling at the UE includes any one or combination of: where the first UE includes one or more of a UE that indicated the shared COT or a UE that initiated the shared COT, and where the SCI is addressed to a destination identifier of the first UE; where the COT indicator is received as part of first stage SCI; where the indication of the time instance includes an offset value, further including applying the offset value to a slot in which the COT indicator is transmitted or received to determine the time instance at which transmission by the second UE as part of the shared COT is to be terminated and/or a time instance at which transmission by the first UE as part of the shared COT may commence or recommence); further including: receiving COT sharing termination configuration information from a network node; and processing the COT indicator based at least in part on the COT sharing termination configuration information; further including: receiving COT sharing termination configuration information from a network node; and determining whether to utilize or further share a remaining COT based at least in part on the COT sharing termination configuration information and the COT indicator.

[0069] Additionally, wireless communication and/or network signaling at the UE includes any one or combination of: where the indication of the time instance includes an index value, further including receiving COT sharing termination configuration information from a network node, the COT sharing termination configuration information including correlations between different index values and different slot offsets from transmission or reception of a COT indicator; and identifying the time instance by correlating the index value to the different index values to identify a slot at which transmission by the second UE as part of the shared COT is to be terminated and/or a slot at which transmission by the first UE as part of the shared COT may commence or recommence); further including determining whether to utilize or further share a remaining COT based on number of slots between the indication of a time instance at which transmission by the second UE as part of the shared COT is to be terminated, and a remaining MCOT for the shared COT between the first UE and the second UE.

[0070] The processor 306 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 306 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 306. The processor 306 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 308) to cause the device 302 to perform various functions of the present disclosure.

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

[0072] The I/O controller 314 may manage input and output signals for the device 302. The I/O controller 314 may also manage peripherals not integrated into the device 302. In some implementations, the I/O controller 314 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 314 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the I/O controller 314 may be implemented as part of a processor, such as the processor 306. In some implementations, a user may interact with the device 302 via the I/O controller 314 or via hardware components controlled by the I/O controller 314.

[0073] In some implementations, the device 302 may include a single antenna 316. However, in some other implementations, the device 302 may have more than one antenna 316, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 310 and the transmitter 312 may communicate bi-directionally, via the one or more antennas 316, wired, or wireless links as described herein. For example, the receiver 310 and the transmitter 312 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 316 for transmission, and to demodulate packets received from the one or more antennas 316.

[0074] FIG. 4 illustrates an example of a block diagram 400 of a device 402 that supports COT sharing termination in accordance with aspects of the present disclosure. The device 402 may be an example of a base station 102, such as a gNB as described herein. The device 402 may support wireless communication and/or network signaling with one or more base stations 102, other UEs 104, core network devices and functions (e.g., core network 106), or any combination thereof. The device 402 may include components for bi-directional communications including components for transmitting and receiving communications, such as a communications manager 404, a processor 406, a memory 408, a receiver 410, a transmitter 412, and an VO controller 414. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses).

[0075] The communications manager 404, the receiver 410, the transmitter 412, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein. For example, the communications manager 404, the receiver 410, the transmitter 412, or various combinations or components thereof may support a method for performing one or more of the functions described herein.

[0076] In some implementations, the communications manager 404, the receiver 410, the transmitter 412, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry). The hardware may include a processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure. In some implementations, the processor 406 and the memory 408 coupled with the processor 406 may be configured to perform one or more of the functions described herein (e.g., by executing, by the processor 406, instructions stored in the memory 408).

[0077] Additionally or alternatively, in some implementations, the communications manager 404, the receiver 410, the transmitter 412, or various combinations or components thereof may be implemented in code (e.g., as communications management software or firmware) executed by the processor 406. If implemented in code executed by the processor 406, the functions of the communications manager 404, the receiver 410, the transmitter 412, or various combinations or components thereof may be performed by a general-purpose processor, a DSP, a central processing unit (CPU), an ASIC, an FPGA, or any combination of these or other programmable logic devices (e.g., configured as or otherwise supporting a means for performing the functions described in the present disclosure).

[0078] In some implementations, the communications manager 404 may be configured to perform various operations (e.g., receiving, monitoring, transmitting) using or otherwise in cooperation with the receiver 410, the transmitter 412, or both. For example, the communications manager 404 may receive information from the receiver 410, send information to the transmitter 412, or be integrated in combination with the receiver 410, the transmitter 412, or both to receive information, transmit information, or perform various other operations as described herein. Although the communications manager 404 is illustrated as a separate component, in some implementations, one or more functions described with reference to the communications manager 404 may be supported by or performed by the processor 406, the memory 408, or any combination thereof. For example, the memory 408 may store code, which may include instructions executable by the processor 406 to cause the device 402 to perform various aspects of the present disclosure as described herein, or the processor 406 and the memory 408 may be otherwise configured to perform or support such operations. [0079] For example, the communications manager 404 may support wireless communication and/or network signaling at a device (e.g., the device 402, a base station) in accordance with examples as disclosed herein. The communications manager 404 and/or other device components may be configured as or otherwise support an apparatus, such as a base station and/or network device, including a transceiver; a processor coupled to the transceiver, the processor and the transceiver configured to cause the apparatus to: generate COT sharing termination configuration information identifying one or more termination parameters for terminating COT sharing between a set of UE; and transmit the COT sharing termination configuration information to one or more UEs.

[0080] Additionally, the apparatus (e.g., a base station) includes any one or combination of: where the one or more termination parameters include an indication of whether the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; where the one or more termination parameters include one or more conditions under which the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; where the one or more termination parameters include a format for the one or more UEs to generate COT sharing termination information; where the one or more termination parameters include correlations between different index values and different slot offsets for the one or more UEs to indicate termination of transmission by the one or more UEs as part of shared COT; where the slot offsets are based at least in part on slot offsets from a slot in which the one or more UEs transmit a COT indicator indicating a termination of transmission by the one or more UEs as part of shared COT.

[0081] The communications manager 404 and/or other device components may be configured as or otherwise support a means for wireless communication and/or network signaling at a network device, including generating COT sharing termination configuration information identifying one or more termination parameters for terminating COT sharing between a set of UE; and transmitting the COT sharing termination configuration information to one or more UEs.

[0082] Additionally, wireless communication at the network device includes any one or combination of: where the one or more termination parameters include an indication of whether the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; where the one or more termination parameters include one or more conditions under which the one or more UEs are to transmit an indication of termination of transmission by the one or more UEs as part of shared COT; where the one or more termination parameters include a format for the one or more UEs to generate COT sharing termination information; where the one or more termination parameters include correlations between different index values and different slot offsets for the one or more UEs to indicate termination of transmission by the one or more UEs as part of shared COT; where the slot offsets are based at least in part on slot offsets from a slot in which the one or more UEs transmit a COT indicator indicating a termination of transmission by the one or more UEs as part of shared COT.

[0083] The processor 406 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof). In some implementations, the processor 406 may be configured to operate a memory array using a memory controller. In some other implementations, a memory controller may be integrated into the processor 406. The processor 406 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 408) to cause the device 402 to perform various functions of the present disclosure.

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

[0085] The I/O controller 414 may manage input and output signals for the device 402. The I/O controller 414 may also manage peripherals not integrated into the device 402. In some implementations, the I/O controller 414 may represent a physical connection or port to an external peripheral. In some implementations, the I/O controller 414 may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In some implementations, the EO controller 414 may be implemented as part of a processor, such as the processor 406. In some implementations, a user may interact with the device 402 via the I/O controller 414 or via hardware components controlled by the I/O controller 414.

[0086] In some implementations, the device 402 may include a single antenna 416. However, in some other implementations, the device 402 may have more than one antenna 416, which may be capable of concurrently transmitting or receiving multiple wireless transmissions. The receiver 410 and the transmitter 412 may communicate bi-directionally, via the one or more antennas 416, wired, or wireless links as described herein. For example, the receiver 410 and the transmitter 412 may represent a wireless transceiver and may communicate bi-directionally with another wireless transceiver. The transceiver may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 416 for transmission, and to demodulate packets received from the one or more antennas 416.

[0087] FIG. 5 illustrates a flowchart of a method 500 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 500 may be implemented and performed by a device or its components, such as a UE 104 as described with reference to FIGs. 1 through 3. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0088] At 502, the method may include generating a COT indicator to indicate a termination of transmission by a first apparatus as part of a shared COT between the first apparatus and a second apparatus, the COT indicator comprising an indication of a time instance at which transmission by the first apparatus as part of the shared COT is to be terminated. The operations of 502 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 502 may be performed by a device as described with reference to FIG. 1.

[0089] At 504, the method may include transmitting the COT indicator as part of SCI to the second apparatus. The operations of 504 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 504 may be performed by a device as described with reference to FIG. 1. [0090] FIG. 6 illustrates a flowchart of a method 600 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 600 may be implemented and performed by a device or its components, such as a UE 104 as described with reference to FIGs. 1 through 3. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0091] At 602, the method may include receiving COT sharing termination configuration information from a network node. The operations of 602 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 602 may be performed by a device as described with reference to FIG. 1.

[0092] At 604, the method may include generating the COT indicator based at least in part on the COT sharing termination configuration information. The operations of 604 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 604 may be performed by a device as described with reference to FIG. 1.

[0093] FIG. 7 illustrates a flowchart of a method 700 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 700 may be implemented and performed by a device or its components, such as a UE 104 as described with reference to FIGs. 1 through 3. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0094] At 702, the method may include receiving, at a first apparatus, SCI from a second apparatus comprising a COT indicator indicating a termination of transmission by the second apparatus as part of a shared COT between the first apparatus and the second apparatus, the COT indicator comprising an indication of a time instance at which transmission by the second apparatus as part of the shared COT is to be terminated. The operations of 702 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 702 may be performed by a device as described with reference to FIG. 1. [0095] At 704, the method may include determining, based at least in part on the COT indicator, when the COT sharing between the first apparatus and the second apparatus is to be terminated. The operations of 704 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 704 may be performed by a device as described with reference to FIG. 1.

[0096] FIG. 8 illustrates a flowchart of a method 800 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 800 may be implemented and performed by a device or its components, such as a UE 104 as described with reference to FIGs. 1 through 3. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0097] At 802, the method may include receiving COT sharing termination configuration information from a network node. The operations of 802 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 802 may be performed by a device as described with reference to FIG. 1.

[0098] At 804, the method may include processing the COT indicator based at least in part on the COT sharing termination configuration information. The operations of 804 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 804 may be performed by a device as described with reference to FIG. 1.

[0099] FIG. 9 illustrates a flowchart of a method 900 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 900 may be implemented and performed by a device or its components, such as a UE 104 as described with reference to FIGs. 1 through 3. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0100] At 902, the method may include receiving COT sharing termination configuration information from a network node. The operations of 902 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 902 may be performed by a device as described with reference to FIG. 1.

[0101] At 904, the method may include determining whether to utilize or further share a remaining COT based at least in part on the COT sharing termination configuration information and the COT indicator. The operations of 904 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 904 may be performed by a device as described with reference to FIG. 1.

[0102] FIG. 10 illustrates a flowchart of a method 1000 that supports COT sharing termination in accordance with aspects of the present disclosure. The operations of the method 1000 may be implemented and performed by a device or its components, such as a base station 102, gNB as described with reference to FIGs. 1 through 4. In some implementations, the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.

[0103] At 1002, the method may include generating COT sharing termination configuration information identifying one or more termination parameters for terminating COT sharing between a set of UE. The operations of 1002 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1002 may be performed by a device as described with reference to FIG. 1.

[0104] At 1004, the method may include transmitting the COT sharing termination configuration information to one or more UEs. The operations of 1004 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1004 may be performed by a device as described with reference to FIG. 1.

[0105] It should be noted that the methods described herein describe possible implementations, and that the operations and the steps may be rearranged or otherwise modified and that other implementations are possible. Further, aspects from two or more of the methods may be combined. The order in which the methods are described is not intended to be construed as a limitation, and any number or combination of the described method operations may be performed in any order to perform a method, or an alternate method. [0106] The various illustrative blocks and components described in connection with the disclosure herein may be implemented or performed with a general-purpose processor, a DSP, an ASIC, a CPU, an FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but in the alternative, the 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 in conjunction with a DSP core, or any other such configuration.

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

[0108] Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A non-transitory storage medium may be any available medium that may be accessed 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, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or specialpurpose processor.

[0109] Any connection may be properly termed a computer-readable medium. For example, if the software is transmitted from a website, server, or other remote source using a coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technologies such as infrared, radio, and microwave, then the coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave are included in the definition of computer-readable medium. Disk and disc, as used herein, include CD, laser disc, optical disc, digital versatile disc (DVD), floppy disk and Blu-ray disc where disks usually reproduce data magnetically, while discs reproduce data optically with lasers. Combinations of the above are also included within the scope of computer- readable media.

[0110] As used herein, including in the claims, “or” as used in a list of items (e.g., a list of items prefaced by a phrase such as “at least one of’ or “one or more of’) indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C, or AB or AC or BC, or ABC (i.e., A and B and C). Similarly, a list of one or more of A, B, or C means A or B or C, or AB or AC orBC, or ABC (i.e., A and B and C). Also, as used herein, the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure. In other words, as used herein, the phrase “based on” shall be construed in the same manner as the phrase “based at least in part on. Further, as used herein, including in the claims, a “set” may include one or more elements.

[0111] The description set forth herein, in connection with the appended drawings, describes example configurations and does not represent all the examples that may be implemented or that are within the scope of the claims. The term “example” used herein means “serving as an example, instance, or illustration,” and not “preferred” or “advantageous over other examples.” The detailed description includes specific details for the purpose of providing an understanding of the described techniques. These techniques, however, may be practiced without these specific details. In some instances, known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described example.

[0112] The description herein is provided to enable a person having ordinary skill in the art to make or use the disclosure. Various modifications to the disclosure will be apparent to a person having ordinary skill in the art, and the generic principles defined herein may be applied to other variations without departing from the scope of the disclosure. Thus, the disclosure is not limited to the examples and designs described herein but is to be accorded the broadest scope consistent with the principles and novel features disclosed herein.