CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Patent Application Serial Number 63/137,636 entitled “CHANNEL OCCUPANCY SHARING AND CORRESPONDING INDICATION IN MULTI-BEAM OPERATION” and fried on January 14, 2021 for Alexander Johann Maria Golitschek Edler von Elbwart, which is incorporated herein by reference in its entirety.

FIELD

[0002] The subject matter disclosed herein relates generally to wireless communications and more particularly relates to configuring channel occupancy sharing.

BACKGROUND

[0003] In certain wireless communications networks, channel occupancy may be used. In such networks, the channel occupancy may be shared.

BRIEF SUMMARY

[0004] Methods for configuring channel occupancy sharing are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a user equipment, a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. In some embodiments, the method includes applying the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0005] One apparatus for configuring channel occupancy sharing includes a user equipment. In some embodiments, the apparatus includes a receiver that receives a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. In various embodiments, the apparatus includes a processor that applies the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0006] Another embodiment of a method for configuring channel occupancy sharing includes transmitting, from a network device, a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

[0007] Another apparatus for configuring channel occupancy sharing includes a network device. In some embodiments, the apparatus includes a transmitter that transmits a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

BRIEF DESCRIPTION OF THE DRAWINGS

[0008] A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

[0009] Figure 1 is a schematic block diagram illustrating one embodiment of a wireless communication system for configuring channel occupancy sharing;

[0010] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring channel occupancy sharing;

[0011] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus that may be used for configuring channel occupancy sharing;

[0012] Figure 4 is a schematic block diagram illustrating one embodiment of a system for configuring channel occupancy sharing;

[0013] Figure 5 is a flow chart diagram illustrating one embodiment of a method for configuring channel occupancy sharing; and

[0014] Figure 6 is a flow chart diagram illustrating another embodiment of a method for configuring channel occupancy sharing.

DETAILED DESCRIPTION

[0015] As will be appreciated by one skilled in the art, aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine readable code, computer readable code, and/or program code, referred hereafter as code. The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

[0016] Certain of the functional units described in this specification may be labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (“VLSI”) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[0017] Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

[0018] Indeed, a module of code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

[0019] Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing the code. The storage device may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

[0020] More specific examples (a non-exhaustive list) of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (“RAM”), a read-only memory (“ROM”), an erasable programmable read-only memory (“EPROM” or Flash memory), a portable compact disc readonly memory (“CD-ROM”), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.

[0021] Code for carrying out operations for embodiments may be any number of lines and may be written in any combination of one or more programming languages including an object oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (“LAN”) or a wide area network (“WAN”), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0022] Reference throughout this specification to “one embodiment,” “an embodiment,” or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment,” “in an embodiment,” and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including,” “comprising,” “having,” and variations thereof mean “including but not limited to,” unless expressly specified otherwise. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, unless expressly specified otherwise. The terms “a,” “an,” and “the” also refer to “one or more” unless expressly specified otherwise.

[0023] Furthermore, the described features, structures, or characteristics of the embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of an embodiment. [0024] Aspects of the embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. The code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0025] The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function/act specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

[0026] The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0027] The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function(s).

[0028] It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, of the illustrated Figures. [0029] Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

[0030] The description of elements in each figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

[0031] Figure 1 depicts an embodiment of a wireless communication system 100 for configuring channel occupancy sharing. In one embodiment, the wireless communication system 100 includes remote units 102 and network units 104. Even though a specific number of remote units 102 and network units 104 are depicted in Figure 1, one of skill in the art will recognize that any number of remote units 102 and network units 104 may be included in the wireless communication system 100.

[0032] In one embodiment, the remote units 102 may include computing devices, such as desktop computers, laptop computers, personal digital assistants (“PDAs”), tablet computers, smart phones, smart televisions (e.g., televisions connected to the Internet), set-top boxes, game consoles, security systems (including security cameras), vehicle on-board computers, network devices (e.g., routers, switches, modems), aerial vehicles, drones, or the like. In some embodiments, the remote units 102 include wearable devices, such as smart watches, fitness bands, optical head-mounted displays, or the like. Moreover, the remote units 102 may be referred to as subscriber units, mobiles, mobile stations, users, terminals, mobile terminals, fixed terminals, subscriber stations, UE, user terminals, a device, or by other terminology used in the art. The remote units 102 may communicate directly with one or more of the network units 104 via UL communication signals. In certain embodiments, the remote units 102 may communicate directly with other remote units 102 via sidelink communication.

[0033] The network units 104 may be distributed over a geographic region. In certain embodiments, a network unit 104 may also be referred to and/or may include one or more of an access point, an access terminal, a base, a base station, a location server, a core network (“CN”), a radio network entity, a Node-B, an evolved node-B (“eNB”), a 5G node-B (“gNB”), a Home Node-B, a relay node, a device, a core network, an aerial server, a radio access node, an access point (“AP”), new radio (“NR”), a network entity, an access and mobility management function (“AMF”), a unified data management (“UDM”), a unified data repository (“UDR”), a UDM/UDR, a policy control function (“PCF”), a radio access network (“RAN”), a network slice selection function (“NSSF”), an operations, administration, and management (“0AM”), a session management function (“SMF”), a user plane function (“UPF”), an application function, an authentication server function (“AUSF”), security anchor functionality (“SEAF”), trusted non- 3GPP gateway function (“TNGF”), or by any other terminology used in the art. The network units 104 are generally part of a radio access network that includes one or more controllers communicably coupled to one or more corresponding network units 104. The radio access network is generally communicably coupled to one or more core networks, which may be coupled to other networks, like the Internet and public switched telephone networks, among other networks. These and other elements of radio access and core networks are not illustrated but are well known generally by those having ordinary skill in the art.

[0034] In one implementation, the wireless communication system 100 is compliant with NR protocols standardized in third generation partnership project (“3GPP”), wherein the network unit 104 transmits using an OFDM modulation scheme on the downlink (“DL”) and the remote units 102 transmit on the uplink (“UL”) using a single-carrier frequency division multiple access (“SC-FDMA”) scheme or an orthogonal frequency division multiplexing (“OFDM”) scheme. More generally, however, the wireless communication system 100 may implement some other open or proprietary communication protocol, for example, WiMAX, institute of electrical and electronics engineers (“IEEE”) 802.11 variants, global system for mobile communications (“GSM”), general packet radio service (“GPRS”), universal mobile telecommunications system (“UMTS”), long term evolution (“LTE”) variants, code division multiple access 2000 (“CDMA2000”), Bluetooth®, ZigBee, Sigfoxx, among other protocols. The present disclosure is not intended to be limited to the implementation of any particular wireless communication system architecture or protocol.

[0035] The network units 104 may serve a number of remote units 102 within a serving area, for example, a cell or a cell sector via a wireless communication link. The network units 104 transmit DL communication signals to serve the remote units 102 in the time, frequency, and/or spatial domain.

[0036] In various embodiments, a remote unit 102 may receive a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. In some embodiments, the remote unit 102 may apply the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof. Accordingly, the remote unit 102 may be used for configuring channel occupancy sharing.

[0037] In certain embodiments, a network unit 104 may transmit a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. Accordingly, the network unit 104 may be used for configuring channel occupancy sharing.

[0038] Figure 2 depicts one embodiment of an apparatus 200 that may be used for configuring channel occupancy sharing. The apparatus 200 includes one embodiment of the remote unit 102. Furthermore, the remote unit 102 may include a processor 202, a memory 204, an input device 206, a display 208, a transmitter 210, and a receiver 212. In some embodiments, the input device 206 and the display 208 are combined into a single device, such as a touchscreen. In certain embodiments, the remote unit 102 may not include any input device 206 and/or display 208. In various embodiments, the remote unit 102 may include one or more of the processor 202, the memory 204, the transmitter 210, and the receiver 212, and may not include the input device 206 and/or the display 208.

[0039] The processor 202, in one embodiment, may include any known controller capable of executing computer-readable instructions and/or capable of performing logical operations. For example, the processor 202 may be a microcontroller, a microprocessor, a central processing unit (“CPU”), a graphics processing unit (“GPU”), an auxiliary processing unit, a field programmable gate array (“FPGA”), or similar programmable controller. In some embodiments, the processor 202 executes instructions stored in the memory 204 to perform the methods and routines described herein. The processor 202 is communicatively coupled to the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212.

[0040] The memory 204, in one embodiment, is a computer readable storage medium. In some embodiments, the memory 204 includes volatile computer storage media. For example, the memory 204 may include a RAM, including dynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or static RAM (“SRAM”). In some embodiments, the memory 204 includes non-volatile computer storage media. For example, the memory 204 may include a hard disk drive, a flash memory, or any other suitable non-volatile computer storage device. In some embodiments, the memory 204 includes both volatile and non-volatile computer storage media. In some embodiments, the memory 204 also stores program code and related data, such as an operating system or other controller algorithms operating on the remote unit 102. [0041] The input device 206, in one embodiment, may include any known computer input device including a touch panel, a button, a keyboard, a stylus, a microphone, or the like. In some embodiments, the input device 206 may be integrated with the display 208, for example, as a touchscreen or similar touch-sensitive display. In some embodiments, the input device 206 includes a touchscreen such that text may be input using a virtual keyboard displayed on the touchscreen and/or by handwriting on the touchscreen. In some embodiments, the input device 206 includes two or more different devices, such as a keyboard and a touch panel.

[0042] The display 208, in one embodiment, may include any known electronically controllable display or display device. The display 208 may be designed to output visual, audible, and/or haptic signals. In some embodiments, the display 208 includes an electronic display capable of outputting visual data to a user. For example, the display 208 may include, but is not limited to, a liquid crystal display (“LCD”), a light emitting diode (“LED”) display, an organic light emitting diode (“OLED”) display, a projector, or similar display device capable of outputting images, text, or the like to a user. As another, non-limiting, example, the display 208 may include a wearable display such as a smart watch, smart glasses, a heads-up display, or the like. Further, the display 208 may be a component of a smart phone, a personal digital assistant, a television, a table computer, a notebook (laptop) computer, a personal computer, a vehicle dashboard, or the like.

[0043] In certain embodiments, the display 208 includes one or more speakers for producing sound. For example, the display 208 may produce an audible alert or notification (e.g., a beep or chime). In some embodiments, the display 208 includes one or more haptic devices for producing vibrations, motion, or other haptic feedback. In some embodiments, all or portions of the display 208 may be integrated with the input device 206. For example, the input device 206 and display 208 may form a touchscreen or similar touch-sensitive display. In other embodiments, the display 208 may be located near the input device 206.

[0044] In certain embodiments, the receiver 212 receives a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. In various embodiments, the processor 202 applies the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0045] Although only one transmitter 210 and one receiver 212 are illustrated, the remote unit 102 may have any suitable number of transmitters 210 and receivers 212. The transmitter 210 and the receiver 212 may be any suitable type of transmitters and receivers. In one embodiment, the transmitter 210 and the receiver 212 may be part of a transceiver. [0046] Figure 3 depicts one embodiment of an apparatus 300 that may be used for configuring channel occupancy sharing. The apparatus 300 includes one embodiment of the network unit 104. Furthermore, the network unit 104 may include a processor 302, a memory 304, an input device 306, a display 308, a transmitter 310, and a receiver 312. As may be appreciated, the processor 302, the memory 304, the input device 306, the display 308, the transmitter 310, and the receiver 312 may be substantially similar to the processor 202, the memory 204, the input device 206, the display 208, the transmitter 210, and the receiver 212 of the remote unit 102, respectively.

[0047] In certain embodiments, the transmitter 310 transmits a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

[0048] In certain embodiments, such as for operation in unlicensed spectrum, especially when operating with millimetre waves, antenna patches may be efficiently used to create narrow beams where most of the transmitted power and energy is directed generally towards the intended recipient of the transmission, largely avoiding transmissions in other directions. In such embodiments, when operating in a license-exempt spectrum, a maximum channel occupancy time may be observed to enable fair use and sharing of the spectrum. However it may also be desirable that a receiving device is able to respond immediately with an acknowledgement of a received transmission. Therefore, it may be possible that a transmitting device, having obtained channel access, shares its channel occupancy with one or more receiving devices.

[0049] In some embodiments, a channel occupancy may be shared by a transmitting device with a receiving device; however, this does not give any beam-specific information about whether sharing is possible or not.

[0050] In various embodiments, a transmitter may indicate channel occupancy sharing with one or more receiving devices to facilitate beam-specific sharing.

[0051] In certain embodiments, a carrier occupancy time (“COT”) sharing indicator may be applicable to one or more beams (e.g., to a transmission configuration indicator (“TCI”) state, a synchronization signal block (“SSB”), or another beam-corresponding property such as a reference signal configuration).

[0052] In some embodiments, a COT sharing indicator may be transmitted in a group- common or broadcast signal, such as DCI format 2 0, or downlink configuration indicator (“DQ”) indicating resource assignment. In various embodiments, there may be a COT sharing indication to indicate COT sharing from a gNB to a user equipment (“UE”). [0053] In certain embodiments, a gNB conveys COT sharing information to a UE through a DCI message, such as a broadcast or group-common DCI as provided by DCI format 2 0, or through a DCI message indicating transmission or reception resources to a UE as provided by DCI format 0 0, DCI format 0 1, DCI format 0 2, DCI format 1 0, DCI format 1 1, and/or DCI format 1_2.

[0054] In some embodiments, COT sharing information may be indicated by a COT sharing field in a DCI message, where a COT sharing field is associated with one or more transmission beams (eg.., represented by a TCI state or a quasi-co-location (“QCL”) Type D relationship). The association may be established by a semi-static configuration such as by radio resource configuration (“RRC”).

[0055] In various embodiments, a configuration of an association includes information indicating a position of a corresponding COT sharing field in DCI. For example, a first configuration of the association establishes that for a first TCI state the applicable COT sharing field is found at a first position within a group-common or broadcast DCI, and that for a second TCI state the applicable COT sharing field is found at a second position within a group-common or broadcast DCI. From the UE’s perspective, there may be a mapping between a COT sharing field and at least one SSB index, and a plurality of one or more COT sharing fields may be signaled in a DCI. RRC signaling may provide mapping between the COT sharing field and at least one SSB index. In certain embodimnets, there may be a pre-defined order (e.g., where a first of the plurality of COT sharing fields is linked to a lowest SSB index, and the last of the plurality of COT sharing fields is linked to a highest SSB index).

[0056] In some embodiments, after receiving DCI, a UE may identify a beam for which COT sharing is indicated (e.g., where the UE may switch the channel access category) by comparing the COT beam (e.g., from indicated SSB index) with the beam configured and/or indicated to the UE for uplink (“UL”) transmission. If both of the beams are QCL-ed, then the UE may do category 2 (“Cat2”) listen before talk (“LBT”) within the COT.

[0057] In various embodiments, restricting COT sharing only with cell specific beams may be considered for UE initiated COT.

[0058] In certain embodiments, a UE may identify a COT sharing indicator among multiple COT sharing indicators to be applicable for itself to do either category 1 (“Catl”) or Cat2 LBT under 2 possibilities: 1) once the UE is configured with configured grant (“CG”) resources and corresponding TCI states (e.g., UL transmit (“TX”) beams), and then the UE determines COT sharing applicability by comparing whether the TCI associated with COT is QCLed (e.g., with type D assumption) with that of TCI indicated for that UE for CG resources; and 2) if the UE is not indicated with any UL TX for its CG resources, then the TCI state (e.g., downlink (“DL”) receive (“RX”) beam) used for receiving a DL physical downlink control channel (“PDCCH”) (e.g., group common DCI and/or UE specific DCI) is compared with the TCI state and corresponding COT, and based on that determines the COT.

[0059] In some embodiments, a first configuration of an association establishes that for a first TCI state, the applicable COT sharing field is found at a first position within a group-common or broadcast DCI, and that for a second TCI state, the applicable COT sharing field is also found at the first position within a group-common or broadcast DCI.

[0060] In various embodiments, if a COT sharing field indicates that the COT is shared for a beam, the corresponding COT sharing information does not change if the COT sharing field is transmitted within the same COT; therefore, if a COT sharing field indicates sharing of the COT, then within the same COT a receiver does not need to expect a change of this indication to no sharing of the COT.

[0061] In certin embodiments, if it is detected that a COT is shared, a receiver may use this information to apply a channel access category that is generally shorter or a different category compared with what would be applied if COT sharing is not detected. The purpose of such a change of channel access category is to make a clear channel assessment (“CCA”) succeed more likely compared to a channel access type that would be applicable if a COT is not shared. For example, a channel access type may be applicable as a function of the COT sharing indication as shown in Table 1.

Table 1

[0062] In some embodiments, there may be COT sharing from a UE to a gNB.

[0063] In various embodiments, a UE conveys COT sharing information to a gNB through an uplink control information (“UCI”) message, such as is contained in a configured grant (e.g., CG) transmission (“CG-UCI”).

[0064] In certain embodiments, a COT sharing field is associated with one or more transmission beams. The association may be established by a semi-static configuration such as by RRC (e.g., by configuring one or more TCI states or QCL relationships for which a COT sharing indicator is to be included in UCI). Such embodiments optionally includes a position of a COT sharing indicator within the UCI.

[0065] In some embodiments, UCI includes for each COT sharing field a corresponding beam field indicating for which TCI state or QCL relationship the COT sharing field applies.

[0066] In various embodiments, from the UE’s perspective, there may be a mapping between a COT sharing field and an SSB index, and a plurality of one or more COT sharing fields signaled in UCI. In such embodiments, RRC signaling provides mapping between the COT sharing field and the SSB index. In certain embodiments, there may be a pre-defined order (e.g., where the first of the plurality of COT sharing fields is linked to the lowest SSB index, and the last of the plurality of COT sharing fields is linked to the highest SSB index).

[0067] In some embodiments, there may be COT sharing conditions.

[0068] In various embodiments, there may be COT sharing from a gNB to a UE.

[0069] In certain embodiments, a UE intending to share a channel occupancy initiated by a gNB may transmit a transmission that follows a DL transmission by the gNB if the UE’s transmission corresponds to a beam or spatial pattern in accordance with a beam or spatial pattern indicated by the gNB.

[0070] In some embodiments, a UE intending to share a channel occupancy initiated by a gNB may transmit a transmission that follows a DL transmission if the UE’s transmission corresponds to a beam or spatial pattern in accordance with the beam or spatial pattern where the gNB’s transmission was transmitted or received.

[0071] In various embodiments, a COT sharing may be determined in association with a TCI state, or in association with a quasi -colocation relationship (e.g. QCL-TypeD) with a signal or channel of a communication system.

[0072] In certain embodiments, there may beCOT sharing from a UE to a gNB.

[0073] In some embodiments, a gNB intending to share a channel occupancy initiated by a UE may transmit a transmission that follows a UL transmission on scheduled resources or a physical uplink shared cahnnel (“PUSCH”) transmission on configured resources by the UE if the gNB’s transmission corresponds to a beam or spatial pattern in accordance with a beam or spatial pattern indicated by the UE.

[0074] In various embodiments, a gNB intending to share a channel occupancy initiated by a UE may transmit a transmission that follows an UL transmission on scheduled resources or a PUSCH transmission on configured resources by the UE if the gNB’s transmission corresponds to a beam or spatial pattern in accordance with the beam or spatial pattern where the UE’s transmission was transmitted or received.

[0075] Figure 4 is a schematic block diagram illustrating one embodiment of a system 400 for configuring channel occupancy sharing. The system 400 includes a UE 402 and a gNB 404. Each of the communications in the system 400 may include one or more messages. In a first communication 406, the UE 402 receives a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. The UE 402 applies 408 the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0076] Figure 5 is a flow chart diagram illustrating one embodiment of a method 500 for configuring channel occupancy sharing. In some embodiments, the method 500 is performed by an apparatus, such as the remote unit 102. In certain embodiments, the method 500 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like. [0077] In various embodiments, the method 500 includes receiving 502 a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof. In some embodiments, the method 500 includes applying 504 the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0078] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship. In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus. In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0079] In one embodiment, the method 500 further comprises configuring a position within the control message for the channel occupancy sharing indicator corresponding to the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof. In certain embodiments, the method 500 further comprises determining a channel access category for transmission using the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof depending on the value of the channel occupancy sharing indicator, wherein the channel access category for a first value of the channel occupancy sharing indicator is different from the channel access category for a second value of the channel occupancy sharing indicator.

[0080] In some embodiments, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof. In various embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling. In one embodiment, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0081] In certain embodiments, the method 500 further comprises determining a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index. In some embodiments, the mapping between the channel occupancy time sharing field and the SSB index is determined based on a predefined order. In various embodiments, the method 500 further comprises receiving RRC signaling indicating a mapping between the channel occupancy time sharing field and an SSB index.

[0082] Figure 6 is a flow chart diagram illustrating another embodiment of a method 600 for configuring channel occupancy sharing. In some embodiments, the method 600 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 600 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

[0083] In various embodiments, the method 600 includes transmitting 602 a signal in a communication system. The signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

[0084] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship. In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus. In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0085] In one embodiment, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof. In certain embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling. In some embodiments, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0086] In various embodiments, a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index is determined based on a predefined order. In one embodiment, the method 600 further comprises transmitting RRC signaling indicating a mapping between the channel occupancy time sharing field and a SSB index.

[0087] In one embodiment, a method of a user equipment (UE) comprises: receiving a signal in a communication system, wherein the signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof; and applying the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof. [0088] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship.

[0089] In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus.

[0090] In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0091] In one embodiment, the method further comprises configuring a position within the control message for the channel occupancy sharing indicator corresponding to the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0092] In certain embodiments, the method further comprises determining a channel access category for transmission using the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof depending on the value of the channel occupancy sharing indicator, wherein the channel access category for a first value of the channel occupancy sharing indicator is different from the channel access category for a second value of the channel occupancy sharing indicator.

[0093] In some embodiments, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0094] In various embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling.

[0095] In one embodiment, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0096] In certain embodiments, the method further comprises determining a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index.

[0097] In some embodiments, the mapping between the channel occupancy time sharing field and the SSB index is determined based on a predefined order.

[0098] In various embodiments, the method further comprises receiving RRC signaling indicating a mapping between the channel occupancy time sharing field and an SSB index.

[0099] In one embodiment, an apparatus comprises a user equipment (UE). The apparatus further comprises: a receiver that receives a signal in a communication system, wherein the signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof; and a processor that applies the channel occupancy sharing indicator to a transmission, a reception, or a combination thereof.

[0100] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship.

[0101] In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus.

[0102] In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0103] In one embodiment, the processor configures a position within the control message for the channel occupancy sharing indicator corresponding to the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0104] In certain embodiments, the processor determines a channel access category for transmission using the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof depending on the value of the channel occupancy sharing indicator, and the channel access category for a first value of the channel occupancy sharing indicator is different from the channel access category for a second value of the channel occupancy sharing indicator.

[0105] In some embodiments, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0106] In various embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling.

[0107] In one embodiment, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0108] In certain embodiments, the processor determines a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index.

[0109] In some embodiments, the mapping between the channel occupancy time sharing field and the SSB index is determined based on a predefined order.

[0110] In various embodiments, the receiver receives RRC signaling indicating a mapping between the channel occupancy time sharing field and an SSB index. [0111] In one embodiment, a method of a network device comprises: transmitting a signal in a communication system, wherein the signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

[0112] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship.

[0113] In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus.

[0114] In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0115] In one embodiment, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0116] In certain embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling.

[0117] In some embodiments, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0118] In various embodiments, a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index is determined based on a predefined order.

[0119] In one embodiment, the method further comprises transmitting RRC signaling indicating a mapping between the channel occupancy time sharing field and a SSB index.

[0120] In one embodiment, an apparatus comprises a network device. The apparatus further comprises: a transmitter that transmits a signal in a communication system, wherein the signal includes a channel occupancy sharing indicator, and the channel occupancy sharing indicator is applicable to a spatial transmission characteristic, a spatial reception characteristic, or a combination thereof.

[0121] In certain embodiments, the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is a preconfigured transmission configuration indicator (TCI) state or quasi-colocation relationship. [0122] In some embodiments, the spatial transmission characteristic for a transmission transmitted by the apparatus corresponds to the spatial reception characteristic for a reception received by the apparatus.

[0123] In various embodiments, the channel occupancy sharing indicator is included in a control message transmitted in the communication system.

[0124] In one embodiment, the channel occupancy sharing indicator indicates a channel occupancy time sharing field associated with the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof.

[0125] In certain embodiments, an association between the channel occupancy time sharing field and the spatial transmission characteristic, the spatial reception characteristic, or the combination thereof is indicated via radio resource control (RRC) signaling.

[0126] In some embodiments, a position of the channel occupancy time sharing field is indicated in downlink control information (DCI).

[0127] In various embodiments, a mapping between the channel occupancy time sharing field and a synchronization signal block (SSB) index is determined based on a predefined order.

[0128] In one embodiment, the transmitter transmits RRC signaling indicating a mapping between the channel occupancy time sharing field and a SSB index.

[0129] Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.