CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to United States Patent Application Serial Number 63/138,288 entitled “APPARATUSES, METHODS, AND SYSTEMS FOR RACH-BASED UE- INITIATED CHANNEL OCCUPANCY TIME” and filed on January 15, 2021 for Hossein Bagheri, 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 random access for a channel occupancy time.

BACKGROUND

[0003] In certain wireless communications networks, a device may acquire a channel occupancy time. In such networks, the channel occupancy time may not be configured for some communication configurations.

BRIEF SUMMARY

[0004] Methods for configuring random access for a channel occupancy time are disclosed. Apparatuses and systems also perform the functions of the methods. One embodiment of a method includes receiving, at a user equipment, a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. In some embodiments, the method includes performing the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration. In certain embodiments, the method includes performing the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

[0005] One apparatus for configuring random access for a channel occupancy time includes a user equipment. In some embodiments, the apparatus includes a receiver that receives a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. In various embodiments, the apparatus includes a processor that: performs the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration; and performs the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

[0006] Another embodiment of a method for configuring random access for a channel occupancy time includes transmitting, from a network device, a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. The first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration. The second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

[0007] Another apparatus for configuring random access for a channel occupancy time includes a network device. In some embodiments, the apparatus includes a transmitter that transmits a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. The first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration. The second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

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 random access for a channel occupancy time;

[0010] Figure 2 is a schematic block diagram illustrating one embodiment of an apparatus including a user equipment that may be used for configuring random access for a channel occupancy time;

[0011] Figure 3 is a schematic block diagram illustrating one embodiment of an apparatus including a network device that may be used for configuring random access for a channel occupancy time;

[0012] Figure 4 is a timing diagram illustrating one embodiment of a timing for UE-COT (channel occupancy acquired by the UE) being sharable with a gNB after a time duration ‘x’;

[0013] Figure 5 is a timing diagram illustrating one embodiment of a timing for RACH occasion skipping and/or RACH dropping based on an SR proximity;

[0014] Figure 6 is a flow chart diagram illustrating one embodiment of a method of a user equipment for configuring random access for a channel occupancy time; and

[0015] Figure 7 is a flow chart diagram illustrating another embodiment of a method of a network device for configuring random access for a channel occupancy time.

DETAILED DESCRIPTION

[0016] 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.

[0017] 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. [0018] 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.

[0019] 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.

[0020] 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.

[0021] More specific examples (anon-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.

[0022] 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).

[0023] 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.

[0024] 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.

[0025] 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 fiinctions/acts specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks. [0026] 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.

[0027] 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.

[0028] 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).

[0029] 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.

[0030] 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. [0031] 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.

[0032] Figure 1 depicts an embodiment of a wireless communication system 100 for configuring random access for a channel occupancy time. 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.

[0033] 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.

[0034] 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.

[0035] 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.

[0036] 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.

[0037] In various embodiments, a remote unit 102 may receive, at a UE, a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. In some embodiments, the remote unit 102 may perform the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration. In certain embodiments, the remote unit 102 may perform the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration. Accordingly, the remote unit 102 may be used for configuring random access for a channel occupancy time. [0038] In certain embodiments, a network unit 104 may transmit a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. The first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration. The second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration. Accordingly, the network unit 104 may be used for configuring random access for a channel occupancy time.

[0039] Figure 2 depicts one embodiment of an apparatus 200 that may be used for configuring random access for a channel occupancy time. 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.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] In certain embodiments, the receiver 212 receives a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. In various embodiments, the processor 202: performs the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration; and performs the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

[0046] 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.

[0047] Figure 3 depicts one embodiment of an apparatus 300 that may be used for configuring random access for a channel occupancy time. 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.

[0048] In certain embodiments, the transmitter 310 transmits a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. The first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration. The second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

[0049] In certain embodiments, such as for operation in an unlicensed spectrum (e.g., especially in a semi-static channel access such as for operation according to frame-based equipment (“FBE”)), downlink and uplink transmissions are allowed after a node such as a gNB or a user equipment (“UE”) has acquired a shared channel by a successful clear channel assessment following a listen-before-talk (“LBT”) procedure. Procedures for gNBs and UEs acquiring a channel occupancy time (“COT”) for dynamic channel access may be predetermined. In some embodiments, a UE may initiate a channel occupancy (“CO”) in semi-static channel access. [0050] In various embodiments, a UE may initiate a CO to reduce latency of a configured grant physical uplink shared channel (“PUSCH”) transmission as the gNB is not aware if there is any data to be transmitted by the UE and the gNB may not have any downlink (“DL”) or uplink (“UL”) data, control, and/or reference signal to schedule and/or transmit and may not intend to sense the channel to acquire a COT.

[0051] In certain embodiments, a UE may initiate a CO to reduce latency of transitioning from an idle and/or an inactive mode to a radio resource control (“RRC”) connected mode. This may be useful for battery powered ultra-reliable low-latency communication (“URLLC”) sensors which frequently may go to idle and/or inactive mode to save power. In addition, in some embodiments, if a UE cannot initiate a CO via a random access channel (“RACH”) transmission, a gNB may need to initiate a CO itself to provide opportunities for a UE to perform potential RACH operations. Since the gNB may not be aware if the UE wants to perform the RACH procedure using RACH occasions, relying solely on gNB-initated COT may be inefficient, especially if the gNB does not have any other DL data and/or control transmissions in that CO.

[0052] In various embodiments, there may be mechanisms to enable a UE to initiate a COT via RACH transmission.

[0053] In certain embodiments, there may be a random access operation. In some embodiments, a random access procedure may be applicable for a UE in an idle and/or an inactive mode as well a UE in an RRC-connected mode. If a UE is in an RRC-idle and/or an RRC -inactive state and/or mode, the UE is not expected to transmit and/or receive unicast data from and/or to the network, and is not expected to receive physical downlink control channel (“PDCCH”) commands.

[0054] In various embodiments, there may be operation in an unlicensed spectrum. In certain embodiments, devices and/or network nodes such as gNBs operating in an unlicensed spectrum may be required to perform LBT (e.g., channel sensing) prior to being able to transmit in the unlicensed spectrum. If the device and/or network node performing LBT does not detect the presence of other signals in the channel, the medium and/or channel may be considered for transmission. In an FBE mode of operation, a device and/or network node performs LBT in an idle period and, once acquired, the channel and/or medium, the device and/or network node may communicate within a non-idle time of a fixed frame period duration (e.g., COT). In some embodiments, such as in current specifications and/or regulations, an idle time is not shorter than a maximum of 5% of a fixed frame period (“FFP”) and 100 microseconds.

[0055] In certain embodiments, there may be UE initiated CO. In some embodiments, a UE may perform channel sensing and access a channel if it senses the channel to be idle. UE initiated CO may be useful in low-latency applications in which having UL data to be sent in configured grant resources is enabled to initiate a CO.

[0056] In various embodiments, it should be noted that symbols, slots, subslots, and/or transmission time intervals (“TTIs”) may be a time unit with a particular duration (e.g., symbol may be a fraction and/or percentage of an orthogonal frequency division multiplexing (“OFDM”) symbol length associated with a particular subcarrier spacing (“SCS”)). Moreover, an uplink (“UL”) transmission (e.g., UL transmission burst) may include multiple transmissions (e.g., of the same and/or different priority if a priority is associated with the transmissions) potentially with gaps between the transmissions, wherein the gaps are short enough in duration to not necessitate performing a channel sensing and/or LBT operation between the transmissions.

[0057] In certain embodiments, for RACH operation to succeed, a UE-COT may need to be shared with the gNB. In some embodiments, there may be mechanisms for sharing UE-COT initiated by RACH transmission with the gNB.

[0058] In various embodiments, sharing a COT implies that a device or node with which the COT is shared can forego an indicated or configured channel access category and/or type and instead apply and/or perform a channel access according to a category and/or type whose characteristic includes a generally shorter sensing period, an increased likelihood for the channel sensing to result in being able to transmit, or no required sensing period prior to transmission in the shared COT.

[0059] In certain embodiments, there may be UE-to-gNB COT sharing. In some embodiments, a UE-COT that is initiated by RACH transmission (e.g., a transmission of a physical RACH (“PRACH”) preamble in a 4-step RACH procedure or a Msg A in a 2-step RACH procedure in an idle and/or an inactive mode, or in an RRC-connected mode if no scheduling resource (“SR”) is configured for a logical channel by a first UE is automatically shared with the gNB.

[0060] In various embodiments, a gNB is not expected and/or will not start a DL transmission (or a UE is not expected to receive a DL signal and/or RACH response) to the UE earlier than ‘x’ ms, symbols, and/or time units from a ‘time boundary’, wherein ‘x’ is higher layer configured and/or reported by the UE (e.g., via UE capability signaling), fixed in a specifications, indicated by a gNB via physical layer signaling such as PDCCH (e.g., a group-common PDCCH or UE-specific PDCCH), dependent on SCS, and/or physical downlink shared channel (“PDSCH”) processing capability. In some embodiments, the ‘time boundary’ is determined based on: 1) a last symbol of PRACH transmission and/or valid PRACH occasion; 2) a last symbol of a latest PRACH occasion associated with a synchronization signal block (“SSB”) and/or channel state information (“CSI”) reference signal (“RS”) (“CSI-RS”) (e.g., a latest SSB and/or CSI-RS received that is at least Ngap symbols prior to the PRACH occasion, wherein Ngap is defined in a specification or indicated); 3) a last symbol of a MsgA-PUSCH for 2-step RACH operation (or last symbol of UL transmission burst in general); 4) a start of UE-FFP; and/or 5) a last symbol of a PRACH slot including the PRACH transmission occasion.

[0061] In certain embodiments, one motivation of having at least ‘x’ time units is to help a second UE in determining that a subsequent gNB transmission is associated with a COT initiated and/or shared by a first UE, and not belonging to a gNB-initiated COT. In one example, the second UE is not allowed to transmit an UL transmission in the gNB-FFP corresponding to the gNB random access response (“RAR”) and/or MsgB transmission to the first UE. In another example, the second UE is not allowed to share the COT (e.g., COT initiated and/or shared by the first UE) after the gNB RAR and/or MsgB transmission to the first UE. In a further example, the first UE may indicate COT sharing information (e.g., in MsgA or in Msg3 or implicitly by selecting a PRACH preamble from a PRACH preamble group configured for indicating COT sharing), which may include: 1) the remaining duration of the COT from a time reference point (e.g., PRACH transmission, first and/or last symbol of PRACH, MsgA, and/or Msg3 transmission occasion and/or PRACH slot comprising the PRACH transmission occasion); 2) the remaining duration until the end of the FFP of the initiating node (e.g., first UE, UE1) including or not including a guard period; 3) whether the UE1 COT can be shared with gNB; and/or 4) whether the UE1 COT can be shared with another UE via gNB. In some embodiments, a first UE’s UE-COT is shared (e.g., automatically) with a gNB after ‘x’ time units from a time reference. In one example, a rule is specified such that upon UE-COT initiation via RACH transmission, the COT is shared with gNB after ‘x’ time units from the time reference.

[0062] Figure 4 is a timing diagram illustrating one embodiment of a timing 400 for UE- COT (channel occupancy acquired by the UE) being sharable with a gNB after a time duration ‘x’ . The timing 400 is over a time 402 and includes a reference time 404 after which a RACH transmission 406 is made. At a time 408, a gNB may share a UE’s COT. A time duration ‘x’ 410 is the time between the reference time 404 and the time 408. A UE-FFP 412 is further illustrated.

[0063] In various embodiments, a UE indicates to a network COT sharing information for the UE-COT that is initiated by RACH transmission (e.g., a transmission of a PRACH preamble in a 4-step RACH procedure or a Msg A in a 2-step RACH procedure in an idle and/or an inactive mode, or in an RRC-connected mode if no SR resource is configured for a logical channel). In one example, a UE indicates: 1) whether the COT is shared; 2) whether the UE initiated the COT; 3) the remaining duration until the end of the FFP of the initiating node (e.g., including or not including the guard period); and/or 4) the DL starting offset (e.g., DL starting offset should not be larger than the RAR-window).

[0064] In certain embodiments, a UE indicates to the network whether the UE has included COT sharing or other information in Msg-A PUSCH or Msg3.

[0065] In some embodiments, a UE-COT that is initiated by RACH transmission (e.g., a transmission of a PRACH preamble in a 4-step RACH procedure or a Msg A in a 2-step RACH procedure in an idle and/or an inactive mode, or in an RRC -connected mode if no SR resource is configured for a logical channel) by a first UE is not shared with the gNB if the RACH transmission occurs close (e.g., ‘w’ time units before the next UE-FFP boundary and/or start of the next UE- FFP) to the end of UE-FFP. In one example, a UE-COT is not shared with the gNB if the RACH transmission (e.g., end of the RACH transmission) occurs close to an upcoming gNB-FFP boundary. In such an example, the gNB may be given a chance to address and/or communicate with multiple UEs in a gNB-FFP. In another example, a UE may not initiate a COT via a RACH transmission if the PRACH occasion associated with the RACH transmission is close to the upcoming gNB-FFP boundary (or the PRACH occasion is not valid). In such an example, the UE expects the gNB to initiate a COT in the upcoming gNB-FFP (e.g., for a system information block (“SIB”) or other DL transmissions (e.g., such as SSB transmissions).

[0066] In various embodiments, a UE is not expected and/or may not transmit a first UL transmission prior to receiving a RAR in a UE-COT that is initiated by a RACH transmission and then shared with a gNB. In one example, a UE is in an RRC -connected mode (e.g., if no SR resource is configured for a logical channel). In another example, a first UL transmission is a configured sounding reference signal (“SRS”) transmission. In a further example, a UE is not expected and/or may not transmit a first UL transmission prior to receiving a RAR in a UE-COT that is initiated by RACH transmission and then shared with gNB if the RAR window (e.g., ra- ResponseWindow) is smaller than a threshold. The threshold may be specified in specifications, may be SCS dependent, may be higher layer signaled, and/or may be physical layer signaled.

[0067] In certain embodiments, a UE skips a first (e.g., valid) PRACH occasion if it is prior but close to a configured UL transmission. In one example, the configured UL transmission is a SRS. In another example, a UE skips a first PRACH occasion if there is a second PRACH occasion after the configured UL transmission resource . In a further example, a time gap between the first and the second PRACH occasions is smaller than a threshold. The threshold may be: 1) dependent on latency requirements of a communication; and/or 2) determined based on a SCS, a PDSCH processing capability, and/or a PUSCH preparation time. [0068] In some embodiments, there may be a COT association. In such embodiments, there may be mechanisms for a UE to determine if the UE’s PRACH transmission is associated with a gNB-FFP or UE-FFP, and hence, e.g., whether there may be any UL transmission within a UE-FFP idle period or gNB-FFP idle period or whether there may be any subsequent uplink transmission within the determined FFP (e.g., gNB-FFP or UE-FFP based on the COT association).

[0069] In various embodiments, in a semi-static channel access mode, if a RACH transmission is aligned with a UE FFP boundary and ends before an idle period of that UE FFP associated with the UE, one or more of the following may be used to determine whether the RACH transmission is associated with UE-FFP or gNB-FFP: 1) if the RACH transmission is confined within a gNB FFP before the idle period of that gNB FFP, and the UE has already determined that the gNB has initiated that gNB FFP, the UE assumes that the RACH transmission corresponds to gNB-initiated COT - otherwise, the UE assumes that the RACH transmission corresponds to UE-initiated COT; 2) the UE assumes that the RACH transmission corresponds to UE-initiated COT; and/or 3) the UE assumption on whether the RACH transmission is allowed to correspond to UE-initiated COT is based on gNB configuration.

[0070] In certain embodiments, if a RACH transmission starts after a UE FFP boundary (e.g., UE FFP can be initiated by an UL transmission such as SRS transmission on configured SRS resources) and ends before the idle period of that UE FFP associated to the UE: 1) if the UE has already initiated the UE FFP, then the UE assumes that the RACH transmission corresponds to a UE-initiated COT; and 2) otherwise, if the transmission is confined within a gNB FFP before the idle period of that gNB FFP, and if the UE has already determined that gNB has initiated that gNB FFP, then the UE assumes that the RACH transmission corresponds to gNB- initiated COT.

[0071] In some embodiments, there may be a valid PRACH occasion.

[0072] In various embodiments, a PRACH occasion (e.g., for FBE operation if a UE can initiate a COT via PRACH transmission) is valid if there is at least DL transmission (e.g., SSB, remaining minimum system information (“RMSI”), SIBs, and so forth detected) within a certain time period (or evaluation period) prior to a time reference. The time reference may be: 1) the first and/or last symbol of the PRACH occasion; and/or 2) the start of UE-FFP. Moreover, the certain time period may be: 1) a gNB-FFP duration; and/or 2) fixed in a specification (e.g., based on a formula, and may be based on a discontinuous reception (“DRX”) configuration (e.g., no DRX, or based on the DRX cycle duration)).

[0073] In certain embodiments, a UE may initiate a COT via PRACH transmission if there is no high-priority SR within ‘w’ symbols of the PRACH transmission. The priority of a SR may be determined by the priority of a logical channel that triggered the SR. The priority of the SR may be compared against a preconfigured threshold. If the priority of the SR is lower than a configured threshold, the UE may initiate a COT via PRACH transmissions. In some embodiments, a “cut-off time” may denote a time when a UE is determining whether a SR has been triggered within ‘w’ symbols of the PRACH transmission.

[0074] Figure 5 is atiming diagram illustrating one embodiment of atiming 500 for RACH skipping and/or dropping based on an SR proximity. The timing 500 is over a time 502 and includes a reference time 504 after which a RACH transmission 506 is possible, but is skipped in this embodiment. At a time 508, a gNB may share a UE’s COT. A time duration ‘x’ 510 is the time between the reference time 504 and the time 508. A UE-FFP1 512 is further illustrated, with an SR 514 near the end of the UE-FFP1 512. A UE-FFP2 516 is also illustrated, and a RACH transmission 518 is made. Specifically, in Figure 5, the UE may skip and/or drop the RACH transmission 506 in a first RACH occasion in the UE-FFP1 512 since the configured SR 514 is within ‘w’ time units of the RACH occasion 506. The UE may initiate a COT in the UE-FFP2 516 by transmitting the RACH 518.

[0075] In some embodiments, a UE-FFP is associated with RACH.

[0076] In various embodiments, a UE may receive (e.g., via SIB signaling) information regarding UE-FFP. The UE-FFP information may include a UE-FFP duration.

[0077] In certain embodiments, an idle and/or an inactive mode UE (and gNB) determines a UE-FFP start based on a PRACH transmission (e.g., PRACH occasion used for PRACH transmission, first and/or last symbol of PRACH, MsgA, and/or Msg3 transmission occasion and/or PRACH slot including a PRACH transmission occasion).

[0078] In some embodiments, there may be a RACH configuration. In various embodiments, a UE may receive separate RACH configurations (or separate subsets of RACH configurations) for RACH transmission in gNB-initiated FFP and UE-initiated FFP.

[0079] In one example, one or more of prach-Configurationlndex, powerRampingStep, and ra-ResponseWindow parameters (of a RACH configuration) may be different to accommodate different (e.g., gNB and UE) FFP durations (e.g., so that the RACH procedure may be done in one FFP duration). In another example, a RACH transmission is from an idle and/or an inactive mode UE.

[0080] Figure 6 is a flow chart diagram illustrating one embodiment of a method 600 for configuring random access for a channel occupancy time. In some embodiments, the method 600 is performed by an apparatus, such as the remote unit 102. 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.

[0081] In various embodiments, the method 600 includes receiving 602, at a UE, a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. In some embodiments, the method 600 includes performing 604 the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration. In certain embodiments, the method 600 includes performing 606 the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

[0082] In certain embodiments, the method 600 further comprises: determining valid physical random access channel (PRACH) occasions, wherein a PRACH occasion in the second channel occupancy initiated by the UE is valid if the PRACH occasion occurs a certain time before a start of a base station fixed frame period; and performing the second random access operation in a valid PRACH occasion of the valid PRACH occasions. In some embodiments, the method 600 further comprises initiating a channel occupancy via a PRACH transmission, wherein the initiated channel occupancy is shared with the base station after a certain time from a time reference. In various embodiments, the time reference is a start of a fixed frame period corresponding to the channel occupancy.

[0083] In one embodiment, the method 600 further comprises initiating a channel occupancy via a PRACH transmission, wherein a duration of a random access response window for a random access operation associated with the PRACH transmission is larger than a threshold value. In certain embodiments, the method 600 further comprises transmitting an UL transmission prior to reception of a random access response corresponding to the PRACH transmission. In some embodiments, the method 600 further comprises skipping a first PRACH occasion if the first PRACH occasion is within a certain time from an upcoming configured UL transmission.

[0084] In various embodiments, the method 600 further comprises skipping the first PRACH occasion if there is a second PRACH occasion after the configured UL transmission resource, wherein a time gap between the first PRACH occasion and the second PRACH occasion is smaller than a threshold value. In one embodiment, a random access response window duration is different between the first random access configuration and the second random access configuration. In certain embodiments, the UE is in a radio resource control connected mode and no scheduling resource is configured for at least one logical channel.

[0085] Figure 7 is a flow chart diagram illustrating another embodiment of a method 700 for configuring random access for a channel occupancy time. In some embodiments, the method 700 is performed by an apparatus, such as the network unit 104. In certain embodiments, the method 700 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.

[0086] In various embodiments, the method 700 includes transmitting 702, from a network device, a first random access configuration and a second random access configuration. The first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum. The first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration. The second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

[0087] In certain embodiments, a random access response window duration is different between the first random access configuration and the second random access configuration.

[0088] In one embodiment, a method of a user equipment (UE) comprises: receiving a first random access configuration and a second random access configuration, wherein: the first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum; performing the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration; and performing the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

[0089] In certain embodiments, the method further comprises: determining valid physical random access channel (PRACH) occasions, wherein a PRACH occasion in the second channel occupancy initiated by the UE is valid if the PRACH occasion occurs a certain time before a start of a base station fixed frame period; and performing the second random access operation in a valid PRACH occasion of the valid PRACH occasions.

[0090] In some embodiments, the method further comprises initiating a channel occupancy via a PRACH transmission, wherein the initiated channel occupancy is shared with the base station after a certain time from a time reference.

[0091] In various embodiments, the time reference is a start of a fixed frame period corresponding to the channel occupancy.

[0092] In one embodiment, the method further comprises initiating a channel occupancy via a PRACH transmission, wherein a duration of a random access response window for a random access operation associated with the PRACH transmission is larger than a threshold value.

[0093] In certain embodiments, the method further comprises transmitting an UL transmission prior to reception of a random access response corresponding to the PRACH transmission.

[0094] In some embodiments, the method further comprises skipping a first PRACH occasion if the first PRACH occasion is within a certain time from an upcoming configured UL transmission.

[0095] In various embodiments, the method further comprises skipping the first PRACH occasion if there is a second PRACH occasion after the configured UL transmission resource, wherein a time gap between the first PRACH occasion and the second PRACH occasion is smaller than a threshold value.

[0096] In one embodiment, a random access response window duration is different between the first random access configuration and the second random access configuration.

[0097] In certain embodiments, the UE is in a radio resource control connected mode and no scheduling resource is configured for at least one logical channel.

[0098] In one embodiment, an apparatus comprises a user equipment (UE). The apparatus further comprises: a receiver that receives a first random access configuration and a second random access configuration, wherein: the first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum; and a processor that: performs the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration; and performs the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration. [0099] In certain embodiments, the processor: determines valid physical random access channel (PRACH) occasions, wherein a PRACH occasion in the second channel occupancy initiated by the UE is valid if the PRACH occasion occurs a certain time before a start of a base station fixed frame period; and performs the second random access operation in a valid PRACH occasion of the valid PRACH occasions.

[0100] In some embodiments, the processor initiates a channel occupancy via a PRACH transmission, and the initiated channel occupancy is shared with the base station after a certain time from a time reference.

[0101] In various embodiments, the time reference is a start of a fixed frame period corresponding to the channel occupancy.

[0102] In one embodiment, the processor initiates a channel occupancy via a PRACH transmission, and a duration of a random access response window for a random access operation associated with the PRACH transmission is larger than a threshold value.

[0103] In certain embodiments, the apparatus further comprises a transmitter that transmits an UL transmission prior to reception of a random access response corresponding to the PRACH transmission.

[0104] In some embodiments, the processor skips a first PRACH occasion if the first PRACH occasion is within a certain time from an upcoming configured UL transmission.

[0105] In various embodiments, the processor skips the first PRACH occasion if there is a second PRACH occasion after the configured UL transmission resource, wherein a time gap between the first PRACH occasion and the second PRACH occasion is smaller than a threshold value.

[0106] In one embodiment, a random access response window duration is different between the first random access configuration and the second random access configuration.

[0107] In certain embodiments, the UE is in a radio resource control connected mode and no scheduling resource is configured for at least one logical channel.

[0108] In one embodiment, a method of a network device comprises: transmitting a first random access configuration and a second random access configuration, wherein: the first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum; wherein the first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration; and wherein the second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

[0109] In certain embodiments, a random access response window duration is different between the first random access configuration and the second random access configuration.

[0110] In one embodiment, an apparatus comprises a network device. The apparatus further comprises: a transmitter that transmits a first random access configuration and a second random access configuration, wherein: the first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum; wherein the first random access operation is performed in the first channel occupancy initiated by the base station based on the first random access configuration; and wherein the second random access operation is performed in the second channel occupancy initiated by the UE based on the second random access configuration.

[0111] In certain embodiments, a random access response window duration is different between the first random access configuration and the second random access configuration.

[0112] 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.

CLAIMS

1. A method of a user equipment (UE), the method comprising: receiving a first random access configuration and a second random access configuration, wherein: the first random access configuration contains first random access parameters corresponding to a first random access operation in a first channel occupancy initiated by a base station in a shared spectrum; and the second random access configuration contains second random access parameters corresponding to second random access operation in a second channel occupancy initiated by the UE in the shared spectrum; performing the first random access operation in the first channel occupancy initiated by the base station based on the first random access configuration; and performing the second random access operation in the second channel occupancy initiated by the UE based on the second random access configuration.

2. The method of claim 1, further comprising: determining valid physical random access channel (PRACH) occasions, wherein a PRACH occasion in the second channel occupancy initiated by the UE is valid if the PRACH occasion occurs a certain time before a start of a base station fixed frame period; and performing the second random access operation in a valid PRACH occasion of the valid PRACH occasions.

3. The method of claim 1, further comprising initiating a channel occupancy via a PRACH transmission, wherein the initiated channel occupancy is shared with the base station after a certain time from a time reference.

4. An apparatus comprising a user equipment (UE), the apparatus further comprising: