PDCCH-based User Equipment (UE) Channel Occupancy Time (COT) Trigger in Frame-based Equipment (FBE) Mode

Abstract

A wireless communication system and method related to communication with a frame-based device (FBE) in a wireless communication network are provided. A method of operating a base station (BS) includes: transmitting a channel occupancy time (COT) indicator to a user equipment (UE) in a first fixed frame period (FFP) in a frame-based device (FBE) mode; transmitting downlink control information (DCI) during a window of the first FFP; and receiving uplink (UL) data from the UE during a second FFP following the first FFP according to the DCI. A method of operating a UE includes: receiving a COT indicator from a base station BS in a first FFP in an FBE mode; monitoring a window of the first FFP; receiving DCI during the window; and transmitting UL data to the BS during a second FFP following the first FFP according to the DCI.

Description

Technical Field

[0001] This application relates to wireless communication systems, and more particularly, to frame-based device (FBE) communication of user equipment (UE) based on PDCCH in a wireless communication network. Background Art

[0002] Wireless communication systems are widely deployed to provide various types of communication content such as voice, video, packet data, messaging, broadcasting, and so on. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). A wireless multi-access communication system may include multiple base stations (BSs), each of which simultaneously supports communication for multiple communication devices (which may otherwise be referred to as user equipment (UE)).

[0003] To meet the growing demand for extended mobile broadband connectivity, wireless communication technologies are evolving from Long Term Evolution (LTE) technologies to next-generation New Radio (NR) technologies, which may be referred to as the fifth generation (5G). For example, NR is designed to provide lower latency, higher bandwidth or higher throughput, and higher reliability compared to LTE. NR is designed to operate in a variety of frequency bands (e.g., from low-frequency bands below about 1 gigahertz (GHz) and mid-frequency bands from about 1 GHz to about 6 GHz to high-frequency bands such as millimeter-wave bands). NR is also designed to operate across different spectrum types, from licensed spectrum to unlicensed and shared spectrum. Spectrum sharing enables operators to opportunistically aggregate spectrum to dynamically support high-bandwidth services. Spectrum sharing can extend the benefits of NR technologies to operating entities that may not have access to licensed spectrum.

[0004] One way to avoid collisions when communicating in shared or unlicensed spectrum is to use a Listen Before Talk (LBT) procedure to ensure that the shared channel is idle before transmitting a signal on the shared channel. The operation or deployment of NR in unlicensed spectrum is referred to as NR-U. In NR-U, the BS may schedule the UE to perform UL transmission in an unlicensed band. The UE may perform the LBT procedure before the scheduled time. When the LBT is successful, the UE may continue to transmit UL data according to the schedule. When the LBT fails, the UE may avoid transmitting.

[0005] There are two types of LBT processes: LBT according to a frame-based device (FBE) and LBT according to a load-based device (LBE). In FBE-based LBT, channel sensing is performed at a predetermined time. For example, if the channel is busy, the transmitting node may back off for a predetermined period of time and sense the channel again after that period. In LBE-based LBT, channel sensing is performed at any time, and if the channel is found to be busy, random back-off is used.

[0006] However, in the FBE mode, UE processing delay time may lead to inefficiency. Therefore, a method for efficiently using resources in the FBE operation mode is needed. SUMMARY OF THE INVENTION

[0007] To provide a basic understanding of the technology under discussion, some aspects of the present disclosure are outlined below. This summary is not an extensive review of all the expected features of the present disclosure, and is neither intended to identify the key or important elements of all aspects of the present disclosure, nor to delineate the scope of any or all aspects of the present disclosure. Its sole purpose is to present some concepts of one or more aspects of the present disclosure in an overview form as a prelude to a more detailed description presented later.

[0008] According to some embodiments, a method of operating a base station (BS) is proposed. For example, the method includes: sending a channel occupancy time (COT) indicator in a first fixed frame period (FFP) to a user equipment (UE) in a frame-based device (FBE) mode; sending downlink control information (DCI) during a window of the first FFP; and receiving uplink (UL) data from the UE during a second FFP following the first FFP according to the DCI.

[0009] A method of operating a UE is also proposed. For example, the method includes: receiving a COT indicator in a first FFP from a base station BS in FBE mode; monitoring a window of the first FFP; receiving DCI during the window; and sending UL data to the BS during a second FFP following the first FFP according to the DCI.

[0010] A BS according to some embodiments includes a transceiver and an FBE communication module coupled to the transceiver. In some embodiments, the FBE communication module is configured to execute instructions to perform the following operations: send a COT indicator in a first FFP to a UE in FBE mode; send DCI during a window of the first FFP; and receive UL data from the UE during a second FFP following the first FFP according to the DCI.

[0011] A UE according to some embodiments includes a transceiver and an FBE communication module coupled to the transceiver. In some embodiments, the FBE communication module is configured to execute instructions to perform the following operations: receive a channel occupancy time (COT) indicator in a first fixed frame period (FFP) from a base station (BS) in FBE mode; monitor a window of the first FFP; receive downlink control information (DCI) during the window; and transmit uplink (UL) data to the BS during a second FFP following the first FFP according to the DCI.

[0012] A non-transitory computer-readable medium according to some embodiments is also disclosed. The non-transitory computer-readable medium includes program code recorded thereon for operations on a BS, and the program code includes: code for transmitting a COT indicator in a first FFP to a UE in FBE mode; code for transmitting DCI during a window of the first FFP; and code for receiving UL data from the UE during a second FFP following the first FFP according to the DCI.

[0013] A non-transitory computer-readable medium is also proposed, and the non-transitory computer-readable medium has program code recorded thereon for operations on a UE. The program code includes: code for receiving a COT indicator in a first FFP from a BS in FBE mode; code for monitoring a window of the first FFP; code for receiving DCI during the window; and code for transmitting UL data to the BS during a second FFP following the first FFP according to the DCI.

[0014] A BS according to some embodiments may include: a unit for transmitting a COT indicator in a first FFP to a UE in FBE mode; a unit for transmitting DCI during a window of the first FFP; and a unit for receiving UL data from the UE during a second FFP following the first FFP according to the DCI.

[0015] A UE according to some embodiments includes: a unit for receiving a COT indicator in a first FFP from a BS in FBE mode; a unit for monitoring a window of the first FFP; a unit for receiving DCI during the window; and a unit for transmitting UL data to the BS during a second FFP following the first FFP according to the DCI.

[0016] After reviewing the following description of specific exemplary embodiments of the present invention in conjunction with the accompanying drawings, other aspects, features, and embodiments of the present invention will become apparent to those of ordinary skill in the art. Although the features of the present invention may be discussed below with respect to certain embodiments and drawings, all embodiments of the present invention may include one or more of the advantageous features discussed herein. In other words, although one or more embodiments may be discussed as having certain advantageous features, one or more of these features may also be used in accordance with the various embodiments of the present invention discussed herein. In a similar manner, although the exemplary embodiments may be discussed below as device, system, or method embodiments, it should be understood that these exemplary embodiments may be implemented in a variety of devices, systems, and methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] Figure 1 A wireless communication network is shown in accordance with some aspects of the present disclosure.

[0018] Figure 2 A radio frame structure is shown in accordance with some aspects of the present disclosure.

[0019] Figure 3A An example of a wireless communication network that supports media sharing across multiple network operating entities is shown in accordance with some aspects of the present disclosure.

[0020] Figure 3B A frame-based device (FBE) communication scheme is shown in accordance with some aspects of the present disclosure.

[0021] Figure 4 is a block diagram of a user equipment (UE) in accordance with some aspects of the present disclosure.

[0022] Figure 5 is a block diagram of an exemplary base station (BS) in accordance with some embodiments of the present disclosure.

[0023] Figure 6 A signaling diagram between a BS and a UE is shown in accordance with some embodiments of the present disclosure.

[0024] Figure 7 Another signaling diagram between a BS and a UE is shown in accordance with some embodiments of the present disclosure.

[0025] Figure 8 A signaling diagram between a BS and a group of UEs is shown in accordance with some embodiments of the present disclosure.

[0026] Figure 9 An algorithm that can operate on a BS is shown in accordance with an embodiment of the present disclosure.

[0027] Figure 10 An algorithm operable on a UE according to an embodiment of the present disclosure is shown. Detailed Description

[0028] The detailed description set forth below in connection with the appended drawings is intended as a description of various configurations and is not intended to represent the only configurations in which the concepts described herein may be implemented. For purposes of providing a thorough understanding of the various concepts, the detailed description includes specific details. It will be apparent, however, to one of ordinary skill in the art that the concepts may be practiced without these specific details. In some instances, well-known structures and components are shown in block diagram form in order to avoid obscuring such concepts.

[0029] Broadly speaking, the present disclosure relates to wireless communication systems (also referred to as wireless communication networks). In various embodiments, the techniques and apparatus may be used for wireless communication networks and other communication networks such as: Code Division Multiple Access (CDMA) networks, Time Division Multiple Access (TDMA) networks, Frequency Division Multiple Access (FDMA) networks, Orthogonal FDMA (OFDMA) networks, Single-Carrier FDMA (SC-FDMA) networks, LTE networks, Global System for Mobile Communications (GSM) networks, Fifth Generation (5G) or New Radio (NR) networks. As described herein, the terms "network" and "system" may be used interchangeably.

[0030] OFDMA networks may implement radio technologies such as evolved UTRA (E-UTRA), Institute of Electrical and Electronics Engineers (IEEE) 802.11, IEEE 802.16, IEEE 802.20, Flash-OFDM, etc. UTRA, E-UTRA, and GSM are part of the Universal Mobile Telecommunications System (UMTS). Specifically, Long-Term Evolution (LTE) is a version of UMTS that uses E-UTRA. UTRA, E-UTRA, GSM, UMTS, and LTE are described in documents provided by an organization named "Third Generation Partnership Project" (3GPP), and cdma2000 is described in documents from an organization named "Third Generation Partnership Project 2" (3GPP2). These various radio technologies and standards are known or are under development. For example, the Third Generation Partnership Project (3GPP) is a cooperation among groups of telecommunications associations aimed at defining globally applicable third-generation (3G) mobile phone specifications. 3GPP Long-Term Evolution (LTE) is a 3GPP project aimed at improving the UMTS mobile phone standard. 3GPP may define specifications for next-generation mobile networks, mobile systems, and mobile devices. The present disclosure relates to the evolution from LTE, 4G, 5G, NR, and beyond wireless technologies, which have shared access to the wireless spectrum among networks using some new and different radio access technologies or radio air interfaces.

[0031] Specifically, 5G networks are expected to enable diverse deployments, diverse spectrums, and diverse services and devices implemented using an OFDM-based unified air interface. To achieve these goals, in addition to developing new radio technologies for 5G NR networks, further enhancements to LTE and LTE-A are also considered. 5G NR will be able to scale to provide coverage for: (1) massive Internet of Things (IoT), with massive IoT having ultra-high density (e.g., ~1M nodes / km 2 ), ultra-low complexity (e.g., ~10s of bits / second), ultra-low energy (e.g., ~10+ year battery life), and deep coverage with the ability to reach challenging locations; (2) mission-critical control for users including strong security for protecting sensitive personal, financial, or confidential information, ultra-high reliability (e.g., ~99.9999% reliability), ultra-low latency (e.g., ~1ms), and with a wide range of mobility or lack of mobility; and (3) enhanced mobile broadband, which includes extremely high capacity (e.g., ~10 Tbps / km 2 ), extreme data rates (e.g., multi-Gbps rates, 100+ Mbps user experience rate), and improved discovery and optimized depth perception.

[0032] 5G NR can be implemented to use an optimized OFDM-based waveform with scalable numerology and transmission time intervals (TTIs); with a common, flexible framework to efficiently multiplex services and features using dynamic, low-latency time division duplex (TDD) / frequency division duplex (FDD) designs; and with advanced radio technologies such as massive multiple input multiple output (MIMO), robust millimeter wave (mmWave) transmission, advanced channel coding, and device-centric mobility. The scalability of the numerology in 5G NR (with scaling of the subcarrier spacing) can efficiently address operating diverse services across diverse spectrums and diverse deployments. For example, in various outdoor and macro coverage deployments with less than 3 GHz FDD / TDD implementations, the subcarrier spacing can occur at 15 kHz for bandwidths (BW) such as 5, 10, 20 MHz, etc. For various other outdoor and small cell coverage deployments with TDD greater than 3 GHz, the subcarrier spacing can occur at 30 kHz for 80 / 100 MHz BW. For various other indoor broadband implementations using TDD in the unlicensed portion of the 5 GHz band, the subcarrier spacing can occur at 60 kHz for 160 MHz BW. Finally, for various deployments transmitting using the mmWave component at 28 GHz with TDD, the subcarrier spacing can occur at 120 kHz for 500 MHz BW.

[0033] The scalable numerology of 5G NR enables scalable TTIs for different latency and quality of service (QoS) requirements. For example, shorter TTIs can be used for low latency and high reliability, while longer TTIs can be used for higher spectral efficiency. The efficient multiplexing of long and short TTIs allows transmissions to start at symbol boundaries. 5G NR also anticipates a self-contained integrated subframe design where uplink / downlink scheduling information, data, and acknowledgments are in the same subframe. The self-contained integrated subframe supports communication in unlicensed or contention-based shared spectrums, adaptive uplink / downlink (which can be flexibly configured on a per-cell basis to dynamically switch between UL and downlink to meet current traffic demands).

[0034] Various other aspects and features of the present disclosure are further described below. It should be apparent that the teachings herein can be embodied in a variety of forms, and any specific structure, function, or both disclosed herein are merely representative and not restrictive. Based on the teachings herein, those of ordinary skill in the art should understand that the aspects disclosed herein can be implemented independently of any other aspect, and two or more of these aspects can be combined in various ways. For example, using any number of the aspects set forth herein, an apparatus can be implemented or a method can be practiced. In addition, such an apparatus can be implemented or such a method can be practiced using other structures, functions, or a combination of structures and functions in addition to or different from one or more of the aspects set forth herein. For example, a method can be implemented as part of a system, apparatus, device, and / or as instructions stored on a computer-readable medium for execution on a processor or computer. In addition, one aspect can include at least one element of a claim.

[0035] This application describes a mechanism for signaling an FBE structure for communication on a shared radio frequency band and for triggering the transmission of UL data by a UE at the start of a subsequent FFP of the FBE structure. For example, a BS can send a system information signal (such as a Physical Broadcast Channel (PBCH) signal or a Remaining System Information (RMSI) signal) to indicate an FBE configuration for communication on a shared radio frequency band. The FBE configuration can indicate multiple frame periods shared by multiple wireless communication devices. Each frame period includes a gap period at the start of the frame period. The frame period can be referred to as a Fixed Frame Period (FFP). The gap period can be used for contention. For example, the BS can perform LBT during the contention period. Upon successful LBT, the BS can use the non-gap portion of the frame period to communicate with a User Equipment (UE) for UL and / or DL.

[0036] In an embodiment of the present disclosure, upon successful LBT, the BS can provide a Channel Occupancy Time (COT) indicator indicating that the BS has an FFP. Then, the BS can send Downlink Control Information (DCI) to the UE in the PDCCH, which has a trigger indicating availability for UL transmission at the start of a subsequent FFP of the FBE structure. When the UE receives the DCI indicating availability, the UE can send UL data at the start of the subsequent FFP or multiple subsequent FFPs.

[0037] Figure 1FIG. 100 shows a wireless communication network 100 in accordance with some aspects of the present disclosure. The network 100 may be a 5G network. The network 100 includes a plurality of base stations (BSs) 105 (labeled 105a, 105b, 105c, 105d, 105e, and 105f, respectively) and other network entities. The BS 105 may be a station that communicates with a UE 115 and may also be referred to as an evolved Node B (eNB), a next-generation eNB (gNB), an access point, etc. Each BS 105 may provide communication coverage for a particular geographical area. In 3GPP, the term “cell” may refer to this particular geographical coverage area of the BS 105 and / or the BS subsystem serving this coverage area, depending on the context in which the term is used.

[0038] The BS 105 may provide communication coverage for macro cells or small cells (e.g., pico cells or femto cells) and / or other types of cells. Macro cells typically cover a relatively large geographical area (e.g., several kilometers in radius) and may allow unrestricted access by UEs having a service subscription with the network provider. Small cells (e.g., pico cells) typically will cover a relatively small geographical area and may allow unrestricted access by UEs having a service subscription with the network provider. Small cells (e.g., femto cells) typically will also cover a relatively small geographical area (e.g., a residence) and may provide restricted access in addition to unrestricted access by UEs associated with the femto cell (e.g., UEs in a closed subscriber group (CSG), UEs for users in a residence, etc.). The BS for a macro cell may be referred to as a macro BS. The BS for a small cell may be referred to as a small cell BS, a pico BS, a femto BS, or a home BS. In Figure 1 the example shown in FIG. 105d and 105e may be conventional macro BSs, while BSs 105a - 105c may be macro BSs implemented with one of three-dimensional (3D), full-dimensional (FD), or massive MIMO. BSs 105a - 105c may utilize their higher-dimensional MIMO capabilities to employ 3D beamforming in both elevation and azimuth beamforming to increase coverage and capacity. BS 105f may be a small cell BS, which may be a home node or a portable access point. The BS 105 may support one or more (e.g., two, three, four, etc.) cells.

[0039] The network 100 may support synchronous operation or asynchronous operation. For synchronous operation, the BSs may have similar frame timings, and transmissions from different BSs may be approximately aligned in time. For asynchronous operation, the BSs may have different frame timings, and transmissions from different BSs may not be aligned in time.

[0040] UE 115s are spread throughout the wireless network 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a terminal, mobile station, subscriber unit, station, etc. UE 115 can be a cellular phone, personal digital assistant (PDA), wireless modem, wireless communication device, handheld device, tablet computer, laptop computer, cordless phone, wireless local loop (WLL) station, etc. In one aspect, UE 115 can be a device including a universal integrated circuit card (UICC). In another aspect, the UE can be a device that does not include a UICC. In some aspects, UE 115 that does not include a UICC can also be referred to as an IoT device or an Internet of Everything (IoE) device. UE 115a - 115d are examples of mobile smart phone - type devices accessing the network 100. UE 115 can also be a machine specifically configured for connected communication (including machine - type communication (MTC), enhanced MTC (eMTC), narrow - band IoT (NB - IoT), etc.). UE 115e - 115h are examples of various machines configured for communication accessing the network 100. UE 115i - 115k are examples of vehicles equipped with wireless communication devices configured for communication accessing the network 100. UE 115 is capable of communicating with any type of BS (whether it is a macro BS, small cell, etc.). In Figure 1 it, lightning (e.g., communication link) indicates a wireless transmission between UE 115 and serving BS 105 (which is the BS designated to serve UE 115 on the downlink (DL) and / or uplink (UL)), a desired transmission between BSs 105, a backhaul transmission between BSs, or a sidelink transmission between UE 115s.

[0041] In operation, BSs 105a - 105c can use 3D beamforming and cooperative spatial techniques (e.g., coordinated multipoint (CoMP) or multi - connection) to serve UE 115a and 115b. Macro BS 105d can perform backhaul communication with BSs 105a - 105c and small cell (BS 105f). Macro BS 105d can also send multicast services subscribed to and received by UE 115c and 115d. Such multicast services can include mobile TV or streaming video, or can include other services for providing community information, such as weather emergencies or alerts (e.g., Amber alert or Gray alert).

[0042] BS105 can also communicate with the core network. The core network can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. At least some of the BS105s in BS105 (e.g., which can be an example of a gNB or an access node controller (ANC)) can interface with the core network via a backhaul link (e.g., NG-C, NG-U, etc.), and can perform radio configuration and scheduling for communication with the UE 115. In various examples, the BS105s can communicate directly or indirectly (e.g., via the core network) with each other over a backhaul link (e.g., X1, X2, etc.), which can be a wired or wireless communication link.

[0043] Network 100 can also support mission-critical communication using ultra-reliable and redundant links for mission-critical devices (e.g., UE 115e, which can be a drone). The redundant communication links to UE 115e can include links from macro BS105d and 105e and a link from small cell BS105f. Other machine type devices (e.g., UE 115f (e.g., a thermometer), UE 115g (e.g., a smart meter), and UE 115h (e.g., a wearable device)) can communicate directly with the BSs (e.g., small cell BS105f and macro BS105e) via Network 100, or be in a multi-hop configuration by communicating with another user device for relaying their information to the network (e.g., UE 115f transmits temperature measurement information to a smart meter (UE 115g), and the temperature measurement information is then reported to the network via small cell BS105f). Network 100 can also provide additional network efficiency via dynamic, low-latency TDD / FDD communication such as vehicle-to-vehicle (V2V), vehicle-to-everything (V2X), cellular V2X (C-V2X) communication between UE 115i, 115j, or 115k and other UEs 115, and / or vehicle-to-infrastructure (V2I) communication between UE 115i, 115j, or 115k and BS105.

[0044] In some implementations, Network 100 uses an OFDM-based waveform for communication. An OFDM-based system can divide the system BW into multiple (K) orthogonal subcarriers, which are also commonly referred to as subcarriers, tones, bins, etc. Each subcarrier can be modulated with data. In some cases, the subcarrier spacing between adjacent subcarriers can be fixed, and the total number of subcarriers (K) can depend on the system BW. The system BW can also be divided into subbands. In other cases, the subcarrier spacing and / or the duration of the TTI can be scalable.

[0045] In some aspects, BS105 may assign or schedule transmission resources (e.g., in the form of time-frequency resource blocks (RBs)) for downlink (DL) and uplink (UL) transmissions in network 100. DL refers to the transmission direction from BS105 to UE 115, while UL refers to the transmission direction from UE 115 to BS105. The communication may be in the form of radio frames. The radio frames may be divided into multiple subframes or time slots, e.g., approximately 10. Each time slot may be further divided into mini-slots. In the FDD mode, simultaneous UL and DL transmissions may occur in different frequency bands. For example, each subframe includes a UL subframe in the UL frequency band and a DL subframe in the DL frequency band. In the TDD mode, UL and DL transmissions occur at different time periods using the same frequency band. For example, a subset of subframes in the radio frame (e.g., DL subframes) may be used for DL transmissions, while another subset of subframes in the radio frame (e.g., UL subframes) may be used for UL transmissions.

[0046] DL subframes and UL subframes may be further divided into several regions. For example, each DL or UL subframe may have predefined regions for the transmission of reference signals, control information, and data. The reference signal is a predefined signal that facilitates communication between BS105 and UE 115. For example, the reference signal may have a specific pilot pattern or structure, where the pilot tones may span the operational BW or frequency band, and each pilot tone is located at a predefined time and a predefined frequency. For example, BS105 may transmit a cell-specific reference signal (CRS) and / or a channel state information-reference signal (CSI-RS) to enable UE 115 to estimate the DL channel. Similarly, UE 115 may transmit a sounding reference signal (SRS) to enable BS105 to estimate the UL channel. The control information may include resource assignment and protocol control. The data may include protocol data and / or operational data. In some aspects, BS105 and UE 115 may use self-contained subframes for communication. The self-contained subframe may include a portion for DL communication and a portion for UL communication. The self-contained subframe may be DL-centric or UL-centric. A DL-centric subframe may include a longer duration for DL communication (compared to that for UL communication). A UL-centric subframe may include a longer duration for UL communication (compared to that for UL communication).

[0047] In some aspects, network 100 may be an NR network deployed on licensed spectrum. BS105 may send synchronization signals (e.g., including a Primary Synchronization Signal (PSS) and a Secondary Synchronization Signal (SSS)) in network 100 to facilitate synchronization. BS105 may broadcast system information associated with network 100 (e.g., including a Master Information Block (MIB), Remaining System Information (RMSI), and Other System Information (OSI)) to facilitate initial network access. In some cases, BS105 may broadcast the PSS, SSS, and / or MIB in the form of a Synchronization Signal Block (SSB) on the Physical Broadcast Channel (PBCH), and may broadcast the RMSI and / or OSI on the Physical Downlink Shared Channel (PDSCH).

[0048] In some aspects, UE 115 attempting to access network 100 may perform initial cell search by detecting the PSS from BS105. The PSS may achieve slot timing synchronization and may indicate a physical layer identity value. Then, UE 115 may receive the SSS. The SSS may achieve radio frame synchronization and may provide a cell identity value, which may be combined with the physical layer identity value to identify the cell. The PSS and SSS may be located in the central part of the carrier or at any appropriate frequency within the carrier.

[0049] After receiving the PSS and SSS, UE 115 may receive the MIB. The MIB may include system information for initial network access and scheduling information for the RMSI and / or OSI. After decoding the MIB, UE 115 may receive the RMSI and / or OSI. The RMSI and / or OSI may include Radio Resource Control (RRC) information related to the Random Access Channel (RACH) procedure, paging, Control Resource Set (CORESET) for Physical Downlink Control Channel (PDCCH) monitoring, Physical UL Control Channel (PUCCH), Physical UL Shared Channel (PUSCH), power control, and SRS.

[0050] After obtaining the MIB, RMSI, and / or OSI, the UE 115 may perform a random access procedure to establish a connection with the BS 105. In some examples, the random access procedure may be a four-step random access procedure. For example, the UE 115 may send a random access preamble, and the BS 105 may respond with a random access response. The random access response (RAR) may include the detected random access preamble identifier (ID) corresponding to the random access preamble, timing advance (TA) information, UL grant, temporary cell radio network temporary identifier (C-RNTI), and / or backoff indicator. Upon receiving the random access response, the UE 115 may send a connection request to the BS 105, and the BS 105 may respond with a connection response. The connection response may indicate contention resolution. In some examples, the random access preamble, RAR, connection request, and connection response may be referred to as Message 1 (MSG1), Message 2 (MSG2), Message 3 (MSG3), and Message 4 (MSG4), respectively. In some examples, the random access procedure may be a two-step random access procedure, where the UE 115 may send the random access preamble and the connection request in a single transmission, and the BS 105 may respond by sending the random access response and the connection response in a single transmission.

[0051] After establishing the connection, the UE 115 and the BS 105 may enter a normal operation phase, in which operation data may be exchanged. For example, the BS 105 may schedule the UE 115 for UL and / or DL communication. The BS 105 may send UL and / or DL scheduling grants to the UE 115 via the PDCCH. The scheduling grant may be sent in the form of DL control information (DCI). The BS 105 may send a DL communication signal (e.g., carrying data) to the UE 115 via the PDSCH according to the DL scheduling grant. The UE 115 may send a UL communication signal to the BS 105 via the PUSCH and / or PUCCH according to the UL scheduling grant.

[0052] In some aspects, BS105 can communicate with UE 115 using Hybrid Automatic Repeat reQuest (HARQ) techniques to improve communication reliability, e.g., to provide Ultra-Reliable Low-Latency Communication (URLLC) services. BS105 can schedule UE 115 for PDSCH communication by sending DL grants in the PDCCH. BS105 can send DL data packets to UE 115 according to the scheduling in the PDSCH. The DL data packets can be sent in the form of Transport Blocks (TBs). If UE 115 successfully receives the DL data packet, UE 115 can send a HARQ acknowledgement (ACK) to BS105. Conversely, if UE 115 fails to successfully receive the DL transmission, UE 115 can send a HARQ negative acknowledgement (NACK) to BS105. Upon receiving a HARQ NACK from UE 115, BS105 can retransmit the DL data packet to UE 115. The retransmission can include the same coded version of the DL data as the initial transmission. Alternatively, the retransmission can include a different coded version of the DL data from the initial transmission. UE 115 can apply soft combining to combine the coded data received from the initial transmission and the retransmission for decoding. BS105 and UE 115 can also apply HARQ to UL communication using a mechanism substantially similar to DL HARQ.

[0053] In some aspects, network 100 can operate on the system BW or a Component Carrier (CC) BW. Network 100 can divide the system BW into multiple BWPs (e.g., parts). BS105 can dynamically assign UE 115 to operate on a certain BWP (e.g., a certain part of the system BW). The assigned BWP can be referred to as the active BWP. UE 115 can monitor the active BWP for signaling information from BS105. BS105 can schedule UE 115 for UL or DL communication in the active BWP. In some aspects, BS105 can assign a pair of BWPs within a CC to UE 115 for UL and DL communication. For example, the BWP pair can include one BWP for UL communication and one BWP for DL communication.

[0054] In some aspects, network 100 may operate on a shared channel, which may include a shared frequency band or an unlicensed frequency band. For example, network 100 may be a New Radio Unlicensed (NR-U) network. BS105 and UE 115 may be operated by multiple network operating entities. To avoid collisions, BS105 and UE 115 may adopt a Listen Before Talk (LBT) procedure to monitor the Transmission Opportunity (TXOP) in the shared channel. For example, a transmitting node (e.g., BS105 or UE 115) may perform LBT before transmitting in the channel. When LBT passes, the transmitting node may continue the transmission. When LBT fails, the transmitting node may avoid transmitting in the channel. In one example, LBT may be energy detection-based. For example, when the signal energy measured from the channel is below a threshold, LBT results in passing. Conversely, when the signal energy measured from the channel exceeds the threshold, LBT results in failure. In another example, LBT may be signal detection-based. For example, when no channel reservation signal (e.g., a predefined preamble signal) is detected in the channel, LBT results in passing. In some aspects, network 100 may utilize an FBE-based contention scheme to share the radio channel among multiple BS105s and / or UE 115s of different network operating entities and / or different Radio Access Technologies (RATs).

[0055] Figure 2 is a timing diagram showing a radio frame structure 200 according to some aspects of the present disclosure. BSs (such as BS105) and UEs (such as UE 115) in a network (such as network 100) may communicate using radio frame structure 200. Specifically, the BS may use the time-frequency resources configured as shown in radio frame structure 200 to communicate with the UE. In Figure 2 it, the x-axis represents time in some arbitrary unit, and the y-axis represents frequency in some arbitrary unit. The transmission frame structure 200 includes radio frame 201. The duration of radio frame 201 may vary according to various aspects. In one example, radio frame 201 may have a duration of approximately 10 milliseconds. Radio frame 201 includes M time slots 202, where M may be any suitable positive integer. In one example, M may be approximately 10.

[0056] Each time slot 202 includes a plurality of subcarriers 204 in frequency and a plurality of symbols 206 in time. The number of subcarriers 204 and / or the number of symbols 206 in time slot 202 may vary according to various aspects, e.g., based on the channel bandwidth, Subcarrier Spacing (SCS), and / or CP mode. One subcarrier 204 in frequency and one symbol 206 in time form one Resource Element (RE) 212 for transmission. A Resource Block (RB) 210 is formed from a plurality of consecutive subcarriers 204 in frequency and a plurality of consecutive symbols 206 in time.

[0057] In one example, a BS (e.g., BS105 in Figure 1 ) may schedule a UE (e.g., UE 115 in Figure 1 ) for UL and / or DL communication at a time granularity of time slot 202 or mini-slot 208. Each time slot 202 may be time-divided into K mini-slots 208. Each mini-slot 208 may include one or more symbols 206. The mini-slots 208 in time slot 202 may have variable lengths. For example, when time slot 202 includes N symbols 206, the mini-slot 208 may have a length between one symbol 206 and (N - 1) symbols 206. In some aspects, the mini-slot 208 may have a length of approximately two symbols 206, approximately four symbols 206, or approximately seven symbols 206. In some examples, the BS may schedule the UE at a frequency granularity of resource blocks (RBs) 210 (e.g., including approximately 12 subcarriers 204).

[0058] Figure 3A and 3B collectively illustrate FBE-based communication over a radio frequency channel for communication (e.g., in a shared radio frequency band or an unlicensed band). Figure 3A illustrates an example of a wireless communication network 300 that supports media sharing across multiple network operating entities, in accordance with some aspects of the present disclosure. Network 300 may correspond to a portion of network 100. For simplicity of discussion, Figure 3A illustrates two BSs 305 (shown as BS 305a and BS 305b) and two UEs 315 (shown as UE315a and UE 315b), but it will be appreciated that aspects of the present disclosure may be extended to more UEs 315 and / or BSs 305. The BS 305 and UE 315 may be similar to BS105 and UE 115, respectively. Figure 3B illustrates an FBE communication scheme 350, in accordance with some aspects of the present disclosure. As shown in scheme 350, the BS 305 and UE 315 may communicate with each other. In Figure 3B , the x-axis represents time in some arbitrary units, and the y-axis represents frequency in some arbitrary units.

[0059] Referring to Figure 3A, in network 300, BS 305a serves UE 315a in serving cell or coverage area 340a, while BS 305b serves UE 315b in serving cell or coverage area 340b. BS 305a and BS 305b can communicate with UE 315a and UE 315b respectively in the same frequency channel. In some cases, BS 305a and BS 305b can be operated by different network operating entities. In some other cases, BS 305a and BS 305b can be operated by different network operating entities. In some cases, BS 305a and BS 305b can use the same RAT (e.g., NR-based technology or WiFi-based technology) respectively to communicate with UE 315a and UE 315b. In some other cases, BS 305a and BS 305b use different RATs respectively to communicate with UE 315a and UE 315b. For example, BS 305a and UE 315a can communicate using NR-based technology, while BS 305b and UE 315b can communicate using WiFi-based technology. Generally, BS 305a and BS 305b can be operated by the same network operating entity or different network operating entities, and can use the same RAT or different RATs to communicate in network 300. BS 305a, BS 305b, UE 315a and UE 315b can use the FBE-based contention mode to share access to the channel, as shown in FBE communication scheme 350.

[0060] Referring to Figure 3B , FBE communication scheme 350 includes a series of frame periods 352, showing sequential frame periods 352-N and 352-(N + 1) therein. Each frame period 352 includes a contention or gap period 354 and a transmission period or channel occupancy time (COT) 356. COT 356 can have a resource structure as shown in radio frame structure 200. In some cases, each COT 356 can include one or more time slots similar to time slot 202. In some cases, each COT 356 can include one or more symbols similar to symbol 206. The start time and duration of COT 356 and gap period 354 are predetermined. Additionally, each COT 352 can have the same duration. Similarly, each gap period 354 can have the same duration. Thus, frame period 352 can also be referred to as a fixed frame period (FFP).

[0061] As Figure 3B shown, scheme 350 divides frequency band 302 into multiple fixed frame periods (FFPs) 352 in FBE mode. As Figure 3BAs shown, the FFP 352 used by a base station (e.g., gNB) 305 may have a channel occupancy time (COT) portion 356 for transmitting downlink or receiving uplink communications. The gNB 305 may share the COT portion 356 with the UE 315 for receiving uplink communications. During an idle period or gap period 354 after the COT 356 at the end of the FFP 352, it may be used to perform a LBT procedure for the next FFP 352. In Figure 3B the example shown, the gap 354 of the FFP 352-N may be used to perform a LBT for contending for the FFP 352-(N+1).

[0062] The FFP 352 may be 1 millisecond (ms), 2 ms, 2.5 ms, 4 ms, 5 ms, 10 ms, etc. (including the idle period). The starting position of the FFP 352 within every two radio frames (e.g., even radio frames) may be given by i*P, where i = {0,1,...,20 / P - 1}, and P is the FFP 352 in ms. The idle period for a given subcarrier spacing (SCS) may be the upper limit value of the specified minimum allowed idle period divided by Ts, where the allowed minimum idle period = max(5% of the FFP, 100 microseconds (μs)), and Ts is the symbol duration for the given SCS. The idle period may have no less than 5% of the FFP 352.

[0063] The FFP configuration 350 for FBE may be included in the system information block (e.g., SIB-1) or signaled in UE-specific radio resource control (RRC) signaling. If the network indicates FBE operation for fallback downlink and uplink grants, for the indication of the LBT type for Cat-2 or Cat-4 LBT, the UE may follow the following mechanism: where one 9 μs time slot is measured within a 9 μs interval (e.g., single LBT). It should be noted that the Cat-2 LBT for the FBE mode is different from the Cat-2 LBT in LBE (which has a duration of 25 or 16 μs). In the FBE mode, a single 9 μs measurement is required exactly before transmission, with at least 4 μs for the measurement.

[0064] If a downlink signal or channel within the FFP is detected (such as the physical downlink control channel (PDCCH), synchronization signal block (SSB), physical broadcast channel (PBCH), remaining minimum system information (RMSI), group common PDCCH (GC-PDCCH), etc.), then UE transmission within the FFP may occur. The same 2-bit field in the load-based device (LBE) mode may be used or reinterpreted to indicate the FBE LBT type, cyclic prefix extension, and / or channel access priority class indication.

[0065] For example, in Release 16 New Radio - Unlicensed (NR - U), the base station (e.g., gNB) 305 can act as the initiating device, and the UE 315 can act as the responding device. Thus, the channel access rules can be as follows. If the gNB 315 initiates a COT 356, then Cat - 1 LBT may not apply, and the gNB 356 can perform Cat - 2 LBT just before the FFP 352. If the gNB 305 is to send a downlink burst in the gNB COT 356, then: if the gap from the previous downlink or uplink burst is within 16 μs, the gNB 305 can perform Cat - 1 LBT, and if the gap is greater than 16 μs, the gNB 305 can perform Cat - 2 LBT. If the UE initiates a COT, then Cat - 1 LBT and Cat - 2 LBT may not apply. If the UE is to send an uplink burst in the gNB COT, then: if the gap is within 16 μs, the UE can perform Cat - 1 LBT, and if the gap is greater than 16 μs, the UE can perform Cat - 2 LBT. As discussed above, it should be noted that Cat - 2 LBT for FBE may be different from Cat - 2 LBT in LBE (25 μs or 16 μs). In some aspects, a 9 - μs measurement may be required just before transmission, with at least 4 μs for measurement. This can be referred to as single - shot LBT.

[0066] Nodes (e.g., BS 305a or BS 305b) interested in communicating using the FFP 352 can compete for the channel during the gap period 354 before the desired FFP 352, e.g., by performing LBT to determine whether another node has reserved the same frame period 352. If the LBT is successful, the node can send an indication of the reservation for the FFP 332 during the COT 356, so that other nodes can avoid using the same FFP 352. The LBT can be energy - detection - based or signal - detection - based. The reservation indication can be a predefined sequence or waveform or any suitable signal. If the LBT is unsuccessful, the node can back off until the start of the next gap period 354, during which the node can attempt another competition for a subsequent FFP 352.

[0067] Although Figure 3B it is shown that the gap period 354 for a particular FFP 352 is located at the end of the FFP 352, in some cases, the gap period 354 can be located at the start of the FFP 352. In either case, the gap period 354 between COTs 356 can be used for competition for the next COT 356.

[0068] InFigure 3B In the example shown, BS 305a and BS 305b may compete for FFP 352 during the corresponding gap period 354. BS 305a may win the competition for the first FFP 352 shown, while BS 305b may win the competition for the next frame period 352. After winning the competition, BS 305a or BS 305b may schedule DL communication and / or UL communication with UE 315a or UE 315b, respectively, within the corresponding non-gap duration or transmission period 356. The DL communication may include DL control information (e.g., PDCCH control information) and / or DL data (e.g., PDSCH data). The UL communication may include UL control information (e.g., PUCCH control information), PRACH signal, random access message, periodic sounding reference signal (p-SRS), and / or UL data (e.g., PUSCH data). For example, BS 305a may send a DL scheduling grant (e.g., PDCCH-scheduled DCI) or UL scheduling grant (e.g., PDCCH-scheduled DCI) for DL communication or UL communication with UE 315a during frame period 352. UE 315a may monitor the scheduling grant from BS 305a and send UL communication to BS 305a or receive DL communication from BS 305a according to the grant.

[0069] In some embodiments, BS 305a may send a PDCCH signal at the start of transmission period 356 to signal to UE 315a that BS 305a has won the competition for FFP 352. In some cases, the PDCCH signal may include group common PDCCH (GC-PDCCH) DCI, which signals to a group of UEs served by BS 305a that BS 305a has won the competition for FFP 352, so that the UEs may monitor the PDCCH from BS 305a. In some cases, the GC-PDCCH may include a slot format indicator (SFI), which indicates the transmission direction of the symbols within the COT 356 assigned to FFP 352. The indication that BS 350a has won access to FFP 352 is generally referred to as a COT indication.

[0070] In addition, once BS 305a or BS 305b has won the competition for frame period 352, FFP 352 is exclusively used by the winning BS 305a or BS 305b. Thus, BS 305a or BS 305b may leave idle periods (shown as blank boxes) in FFP 352 without transmission. When operating in the FBE mode, another node may not occupy the channel during the idle periods because competition may occur during gap period 354.

[0071] In some embodiments, BS 305a may configure UE 315a with a configured grant or configured resources for configured UL transmissions. The configured grant or resources may be periodic. When the configured resources or grant are within the FFP 356 of frame period 352, UE 315a may monitor for a COT indication from BS 305a during frame period 352. Upon detecting a COT indication from BS 305a, UE 315a may transmit using the configured grant resources in frame period 352.

[0072] As discussed above, when operating in the FBE communication mode, the FFP 352 and the gap period 354 are predetermined or known prior to communication in the FBE mode. Accordingly, the present disclosure provides techniques for signaling an FBE structure for FBE communication on a shared radio frequency band. The present disclosure also provides techniques for enabling a UE (e.g., UE 115 and / or 315) to access a network (e.g., network 100 and / or 300) when the network is operating in the FBE mode. Specifically, embodiments of the present invention provide access to UE 115 to provide UL transmissions at the start of a subsequent FFP 352.

[0073] Figure 4 is a block diagram of an exemplary UE 400 in accordance with some aspects of the present disclosure. UE 400 may be the UE 115 discussed above in Figure 1 As shown, UE 400 may include a processor 402, a memory 404, an FBE-based communication module 408, a transceiver 410 including a modem subsystem 412 and a radio frequency (RF) unit 414, and one or more antennas 416. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0074] Processor 402 may include a central processing unit (CPU), a digital signal processor (DSP), an application specific integrated circuit (ASIC), a controller, a field programmable gate array (FPGA) device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. Processor 402 may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

[0075] Memory 404 may include cache memory (e.g., the cache memory of processor 402), random access memory (RAM), magnetoresistive RAM (MRAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, solid-state memory devices, hard disk drives, other forms of volatile and non-volatile memory, or combinations of different types of memory. In one aspect, memory 404 includes non-transitory computer-readable media. Memory 404 may store or have instructions 406 recorded thereon. Instructions 406 may include: when executed by processor 402, causing processor 402 to perform the operations described herein in connection with aspects of the present disclosure (e.g., Figure 2 , 3A -3B and aspects 6-10) with reference to UE 115. Instructions 406 may also be referred to as program code. The program code may be used to cause the wireless communication device to perform these operations, e.g., by causing one or more processors (such as processor 402) to control or command the wireless communication device to do so. The terms "instructions" and "code" should be construed broadly to include any type of computer-readable statement. For example, the terms "instructions" and "code" may refer to one or more programs, routines, subroutines, functions, procedures, etc. "Instructions" and "code" may include a single computer-readable statement or multiple computer-readable statements.

[0076] The FBE-based communication module 408 may be implemented via hardware, software, or a combination thereof. For example, the FBE-based communication module 408 may be implemented as a processor, circuitry, and / or instructions 406 stored in memory 404 and executed by processor 402. In some examples, the FBE-based communication module 408 may be integrated within the modem subsystem 412. For example, the FBE-based communication module 408 may be implemented through a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 412.

[0077] The FBE-based communication module 408 may be used in various aspects of the present disclosure, e.g., Figure 2 , 3AAspects of -3B and 6 - 10. The FBE - based communication module 408 is configured to: receive a system information signal indicating FBE configuration and PRACH configuration from a BS (e.g., BS105 and / or 305); transmit a PRACH signal based on the PRACH configuration to initiate a random access procedure with the BS; and / or communicate UL communication (e.g., PUCCH and / or PUSCH) and / or DL communication (e.g., PDCCH and / or PDSCH) with the BS based on the FBE configuration.

[0078] In some aspects, the system information signal may indicate an FBE contention mode or a load - based device (LBE) contention mode. The FBE configuration may indicate the duration of a frame period, the duration of a gap period, and the alignment of the frame boundary between the frame period and a radio frame. In some cases, the FBE configuration may indicate the duration of the gap period (in symbols or time slots). In some cases, when the FBE configuration does not include the duration of the gap period, the FBE - based communication module 408 is configured to calculate the duration of the gap period based on the duration of the frame period and the minimum duration of the gap period relative to the frame period. In some cases, in addition to the minimum duration, the FBE configuration may also indicate the number of symbols or time slots for the gap period.

[0079] In some aspects, the system information signal may indicate a physical random access channel (PRACH) configuration. In some cases, the PRACH configuration may indicate that the UE can transmit a PRACH signal during a frame period acquired by the BS. In some cases, the PRACH configuration may indicate that the UE can transmit a PRACH signal during any gap period based on successful contention. In some cases, the PRACH configuration may indicate that the UE can autonomously transmit a PRACH signal at any time based on a reference channel occupancy duration parameter (e.g., specified by an official agency). In some cases, the PRACH configuration may indicate that the UE can contend for a frame period for transmitting a PRACH signal and can share the acquired frame period with the BS. The mechanism for FBE communication is described in more detail herein.

[0080] As shown in the figure, the transceiver 410 may include a modem subsystem 412 and an RF unit 414. The transceiver 410 may be configured to communicate bidirectionally with other devices (such as BS105). The modem subsystem 412 may be configured to modulate and / or encode data from the memory 404 and / or the FBE-based communication module 408 according to a modulation and coding scheme (MCS) (e.g., low-density parity-check (LDPC) coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). The RF unit 414 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from the modem subsystem 412 (e.g., PUCCH control information, PRACH signal, PUSCH data) (for outbound transmission) or the modulated / encoded data of a transmission from another source (such as UE 115 or BS105). The RF unit 414 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 410, the modem subsystem 412 and the RF unit 414 may be separate devices that are coupled together at the UE 115 to enable the UE 115 to communicate with other devices.

[0081] The RF unit 414 may provide the modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 416 for transmission to one or more other devices. The antenna 416 may also receive data messages sent from other devices. The antenna 416 may provide the received data messages for processing and / or demodulation at the transceiver 410. The transceiver 410 may provide the demodulated and decoded data (e.g., SSB, RMSI, MIB, SIB, FBE configuration, PRACH configuration, PDCCH, PDSCH) to the FBE-based communication module 408 for processing. The antenna 416 may include multiple antennas with similar or different designs to maintain multiple transmission links. The RF unit 414 may configure the antenna 416.

[0082] In one example, the transceiver 410 is configured to: receive system information including an FBE configuration from the BS, the FBE configuration indicating multiple frame periods, each frame period including a gap period for contention at the start of the frame period; and communicate with the BS based on the FBE configuration, e.g., by coordinating with the FBE-based communication module 408.

[0083] In one aspect, the UE 400 may include multiple transceivers 410 that implement different RATs (e.g., NR and LTE). In one aspect, the UE 400 may include a single transceiver 410 that implements multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 410 may include various components, and different combinations of the components may implement different RATs.

[0084] Figure 5 is a block diagram of an exemplary BS 500 according to some aspects of the present disclosure. The BS 500 may be the BS105 in the network 100 as discussed above in Figure 1 As shown, the BS 500 may include a processor 502, a memory 504, a FBE-based communication module 508, a transceiver 510 including a modem subsystem 512 and an RF unit 514, and one or more antennas 516. These elements may communicate directly or indirectly with each other, for example, via one or more buses.

[0085] The processor 502 may have various features as a type-specific processor. For example, these may include a CPU, a DSP, an ASIC, a controller, an FPGA device, another hardware device, a firmware device, or any combination thereof configured to perform the operations described herein. The processor 502 may also be implemented as a combination of computing devices, for example, a combination of a DSP and a microprocessor, multiple microprocessors, the combination of one or more microprocessors and a DSP core, or any other such configuration.

[0086] The memory 504 may include cache memory (e.g., the cache memory of the processor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, solid-state memory devices, one or more hard disk drives, a memristor-based array, other forms of volatile and non-volatile memory, or a combination of different types of memory. In some aspects, the memory 504 may include non-transitory computer-readable media. The memory 504 may store instructions 506. The instructions 506 may include: when executed by the processor 502, causing the processor 502 to perform the operations described herein (e.g., Figure 2 , 3A -3B and aspects 6-10). The instructions 506 may also be referred to as code, and the code may be broadly interpreted to include any type of computer-readable statement, as discussed above with respect to Figure 4 as discussed.

[0087] The FBE-based communication module 508 can be implemented via hardware, software, or a combination thereof. For example, the FBE-based communication module 508 can be implemented as a processor, circuitry, and / or instructions 506 stored in the memory 504 and executed by the processor 502. In some cases, the FBE-based communication module 508 can be integrated within the modem subsystem 512. For example, the FBE-based communication module 508 can be implemented by a combination of software components (e.g., executed by a DSP or a general-purpose processor) and hardware components (e.g., logic gates and circuitry) within the modem subsystem 512.

[0088] The FBE-based communication module 508 can be used in various aspects of the present disclosure, for example, Figure 2 , 3A - aspects of 3B and 6-10. The FBE-based communication module 508 is configured to: send a system information signal indicating the FBE configuration and the PRACH configuration to a BS (e.g., UE 115, 315, and / or 400); receive a PRACH signal from a UE based on the PRACH configuration; and / or transmit UL communication (e.g., PUCCH and / or PUSCH) and / or DL communication (e.g., PDCCH and / or PDSCH) with a UE based on the FBE configuration.

[0089] In some aspects, the system information signal can indicate an FBE contention mode or an LBE contention mode. The FBE configuration can indicate the duration of a frame period, the duration of a gap period, and the alignment of the frame boundary between the frame period and a radio frame. In some cases, the FBE configuration can indicate the duration of the gap period (in symbols or time slots). In some cases, the FBE-based communication module 408 is configured to calculate the duration for the gap period based on the duration of the frame period and the minimum duration of the gap period relative to the frame period. In some cases, in addition to the minimum duration, the FBE configuration can also indicate the number of symbols or time slots for the gap period.

[0090] In some aspects, the system information signal may indicate a Physical Random Access Channel (PRACH) configuration. In some cases, the PRACH configuration may indicate that the UE may transmit a PRACH signal during a frame period obtained by the BS 500. In some cases, the PRACH configuration may indicate that the UE may transmit a PRACH signal during any gap period based on successful contention. In some cases, the PRACH configuration may indicate that the UE may autonomously transmit a PRACH signal at any time based on a reference channel occupancy duration parameter (e.g., specified by an official body). In some cases, the PRACH configuration may indicate that the UE may contend for a frame period for transmitting a PRACH signal and may share the obtained frame period with the BS. The mechanisms for FBE communication are described in more detail herein.

[0091] As shown, the transceiver 510 may include a modem subsystem 512 and an RF unit 514. The transceiver 510 may be configured to communicate bidirectionally with other devices such as the UE 115 and / or 300 and / or another core network element. The modem subsystem 512 may be configured to modulate and / or encode data according to an MCS (e.g., LDPC coding scheme, turbo coding scheme, convolutional coding scheme, digital beamforming scheme, etc.). The RF unit 514 may be configured to process (e.g., perform analog-to-digital conversion or digital-to-analog conversion, etc.) the modulated / encoded data from the modem subsystem 512 (e.g., SSB, RMSI, MIB, SIB, FBE configuration, PRACH configuration, PDCCH, PDSCH) (for outbound transmission) or the modulated / encoded data of a transmission originating from another source such as the UE 115, UE 315, and / or UE 400. The RF unit 514 may also be configured to perform analog beamforming in combination with digital beamforming. Although shown as being integrated together in the transceiver 510, the modem subsystem 512 and / or the RF unit 514 may be separate devices that are coupled together at the BS 105 to enable the BS 105 to communicate with other devices.

[0092] The RF unit 514 may provide the modulated and / or processed data (e.g., data packets (or more generally, data messages that may include one or more data packets and other information)) to the antenna 516 for transmission to one or more other devices. For example, according to some aspects of the present disclosure, this may include the transmission of information to complete an attachment to a network and communication with the resident UE 115 or 215. The antenna 516 may also receive data messages sent from other devices and provide the received data messages for processing and / or demodulation at the transceiver 510. The transceiver 510 may provide the demodulated and decoded data (e.g., PUCCH control information, PRACH signals, PUSCH data) to the FBE-based communication module 508 for processing. The antenna 516 may include multiple antennas with similar or different designs to maintain multiple transmission links.

[0093] In one example, the transceiver 510 is configured to: send system information including an FBE configuration indicating multiple frame periods to the UE, each frame period including a contention gap period at the start of the frame period; and communicate with the UE based on the FBE configuration, e.g., by coordinating with the FBE-based communication module 508.

[0094] In one aspect, the BS 500 may include multiple transceivers 510 implementing different RATs (e.g., NR and LTE). In one aspect, the BS 500 may include a single transceiver 510 implementing multiple RATs (e.g., NR and LTE). In one aspect, the transceiver 510 may include various components, and different combinations of the components may implement different RATs.

[0095] One aspect of the present disclosure is that the application of FBE-based communication to unlicensed spectrum can be used for ultra-reliable low-latency communication (URLLC) and industrial Internet of Things (IIoT) applications involving controlled environments. A controlled environment may be an environment that is controlled such that no other radio access technology (RAT) or other operator is operating in the coverage area. Thus, even if the LBT process is performed for an FBE device, the LBT process can always pass. More generally, even if the factory owner or operator can clear the environment, there may still be a possibility that some other RAT is operating. In some embodiments, for Wi-Fi devices, even when no access point is deployed, access probes may be sent from stations. The factory may implement rules regarding not deploying Wi-Fi access points inside the factory floor, but it may be difficult to ensure that no employee is carrying a smartphone. Thus, the possibility of the gNB LBT process failing is very small.

[0096] Further reference Figure 3B, in FBE mode, there is a processing time at UE 315 for the communication received from BS 305. This processing time occurs between the time when BS 305 sends the COT indicator and the time when UE 315 receives and interprets the indicator. Similar processing times occur when UE 315 receives a PDCCH with DCI for scheduling UL transmissions and when UE 315 interprets the DCI. Thus, this processing time in UE 315 is time wasted for scheduling UL transmissions. This presents several different case scenarios, some of which will be discussed specifically below. Embodiments in accordance with the present disclosure can result in better utilization of available resources.

[0097] In a first case scenario, BS 305 does not have downlink data for transmission, but there is a need to transmit UL data. Thus, BS 305 contends for the channel at the start of FFP 352 to provide the required UL transmission in UE 315 (e.g., dynamic scheduling or CG-UL scheduling). In this scenario, if LBT passes, then gNB 305 obtains access to the channel at FFP 352 and sends a DL signal with a COT indicator. UE 315 can then send UL data after the processing time (conditioned on having detected the DL signal / channel). Since gNB 305 does not send anything during this duration, resources during the processing time are wasted. If the DL signal is used to trigger UL transmission in UE 315, the DL signal itself may not be necessary, which can reduce the latency of UL data.

[0098] In a second case scenario, when gNB 305 contends for the channel at the start of FFP 352, LBT fails. This normally results in no DL data transmission and no UL data transmission. UE 315 cannot send UL data because no DL signal is detected.

[0099] In a third case applicable to ultra-reliable low-latency communication (URLLC) environments, it may be necessary to schedule UE UL transmissions (PUCCH or PUSCH for URLLC DL / UL services respectively) at the start of FFP352. If there is a processing time occurring as a wait in UE 315, the timeline requirements from some URLLC services may not be met.

[0100] Embodiments of the present disclosure help alleviate these problems in resource usage. According to various embodiments described herein, the UE 315 may transmit uplink data during the COT indicator processing time so that the time resources of the FFP 352 are not wasted. If the UE 314 is able to transmit uplink data during the FFP 352 without waiting until a later FFP 352, the service may not be interrupted. The UE 315 may transmit uplink data in the first part of the FFP 352 at least partially based on the grant information received during the previous FFP 352. The UE 315 may not need to rely on the COT indicator reception for successful LBT from the gNB 305. If the LBT is successful, the UE 315 may not wait until after the COT indicator is processed to transmit data, thereby also saving resources and avoiding service interruption.

[0101] Figure 6 An example communication 600 in the FBE mode between the gNB 305 and the UE 315 according to some embodiments of the present disclosure is shown. Specifically, due to the COT trigger initiated by the gNB 305 in the UE 315, the communication 600 results in the transmission of UL data 622 at the start of the second FFP 352-(N + 1) in the FBE mode.

[0102] As Figure 6 shown, the base station gNB 305 communicates with the UE 315. For example, the BS 305 is further shown above in Figure 1 、 3A and 5. For example, the UE 315 is further shown above in Figure 1 、 3A and 4. Figure 6 The operations of both the BS 305 and the UE 315 using the sequence of the FFP 352 in the FBE mode are shown.

[0103] As Figure 6 shown, the BS 305 performs LBT 602 in the idle period 354 before the first FFP 352-N. As discussed above, the LBT 602 may be a 9 μs single LBT. If the LBT 602 fails, the gNB 305 loses the competition for the FFP 352-N and thus does not transmit DL data during the COT 356 of the FFP 352-N.

[0104] If the LBT 602 is successful (as in Figure 6As in the case of the example shown in [Figure number], the gNB 305 sends a COT indication 612 at the start of the COT 356 of the FFP 352-N. The gNB 305 can then send DL data 606 during the COT period 356 of the FFP 352. Additionally, as shown, DCI can be sent during the PDCCH 610. According to an embodiment of the present disclosure, the PDCCH 610 can be constrained to be sent during a specific window 608 within the COT 356. In one aspect, the start and duration of the window 608 can be predefined. For example, the start of the window 608 can be a fixed offset relative to the start of the COT 356, and the duration can be a fixed number of symbols. In another aspect, the start (e.g., start symbol) and duration (e.g., number of symbols) of the window 608 can be configured via higher layer parameters. It should be understood that the start and / or duration of the window can depend on the duration of the COT.

[0105] Therefore, the gNB 305 can also compete for the second FFP 352-(N + 1) shown in Figure 6 However, regardless of whether there is competition for the second FFP 352 or not, if the DCI sent in the PDCCH 610 indicates the availability for UL data transmission, the gNB 305 can expect UL data at the start of the second FFP 352 according to this DCI.

[0106] As Figure 6 Further shown, if the LBT 602 for the gNB 305 is successful, the UE 315 receives the COT indicator 612. As Figure 6 shown and as discussed above, during the processing time 616 after completion, the COT indicator 612 is processed in the UE 315. If the LBT 602 fails, the COT indicator 612 may not be sent. If the COT indicator 612 is received, the UE expects to receive DCI with a UL grant in the PDCCH 610. If the PDCCH 610 is sent, it is processed by the UE 315 after a delay 618. The DCI received in the PDCCH 610 can trigger a UL transmission from the UE 315 at the start of the subsequent 352. Specifically, the DCI in the PDCCH 610 triggers a UL transmission that introduces an indicator to notify the UE 315 to use its own FFP 352 (in this case 352-(N + 1)) for UL transmission instead of relying on the DL signal / channel detection of the gNB 305 for transmission. The DCI can be used to trigger the PUSCH or PUCCH.

[0107] As Figure 6As shown, in response to DCI received in PDCCH 610, UE 315 may transmit UL data 622 at the start of subsequent FFT 352-(N+1). In some embodiments, UE 315 may perform LBT 620 in gap 354 before FFT 352-(N+1).

[0108] As Figure 6 shown, window 608 in which DCI can be sensed in PDCCH 610 helps capture UE COT triggering. In some embodiments, the UE COT trigger may be a single bit of DCI in PDCCH 610 in window 608. DL and UL grants for uplink transmission will not directly initiate COT. However, if a DCI with a trigger bit set to 1 is detected in window 608, UE 315 may initiate COT 356 of FFP 352-(N+1) and transmit UL data 622 according to the RRC configuration for UL data transmission.

[0109] In Figure 6 the communication 600 shown, the DCI in PDCCH 610 may include a single bit to trigger UE 315 to upload data at the start of the second FFP 352-(N+1). Figure 7 Communication 700 is shown, where the DCI includes two or more bits for this trigger. In communication 700, the DCI may notify UE 315 to use multiple subsequent FFP 352s for UL data transmission. As Figure 7 shown, the DCI in PDCCH 702 is included within window 608. The DCI in PDCCH 702 includes two or more trigger bits indicating whether UL data can be transmitted in subsequent FFP 352s. For example, in a two-bit system, "00" may indicate that UE 315 cannot transmit UL data at the start of any subsequent FFP 352; "01" may indicate that UE 315 can transmit UL data at the start of subsequent FFP (i.e., FFP 352-(N+1)); "10" may indicate that UE 315 can transmit UL data at the start of the next two FFP (i.e., FFP 352-(N+1) and FFP 352-(N+2)); and "11" may indicate that UE315 can transmit UL data at the start of the next three FFP (i.e., FFP 352-(N+1), FFP 352-(N+2), and FFP 352-(N+3)).

[0110] As Figure 7As shown, gNB 305 obtains a successful LBT 602 and provides a COT indicator 604. Additionally, as discussed above, gNB 305 may provide DL data 506 during COT 356. Further, during window 608, gNB provides DCI as discussed above during PDCCH 702. As described above, in Figure 7 the embodiment shown, the DCI includes two or more bits indicating whether UL data can be transmitted in a subsequent FFP 352.

[0111] As Figure 7 further shown, UE 315 may receive and process the COT indicator 604 to obtain a COT result 612 at processing time 616. As discussed above, when UE 315 recognizes the COT indicator 604, it monitors PDCCH 702 with DCI in window 608. Then, UE 315 performs processing during processing time 618 to determine whether UL data can be transmitted and how many subsequent FFP 352 can be used based on the COT trigger bit in the DCI. In Figure 7 the specific example shown, the DCI COT trigger bit indicates that the next two FFP 352 can be used. Accordingly, UE 315 performs a successful LBT 708 to transmit UL data 706 at the start of FFP 352-(N+1), and performs a successful LBT 712 to transmit UL data 710 at the start of FFP 352-(N+2).

[0112] It should be understood that any number of COT trigger bits can be used. Additionally, if LBT 708 fails, UL data 706 may not be transmitted, and if LBT 712 fails, UL data 710 may not be transmitted.

[0113] Figure 8 Communication 800 between BS 305 and a group of UEs 315-1 to 315-N according to some embodiments is shown. Specifically, Figure 8 starting UE COT for preconfigured CG-PUSCH or other RRC-configured UL transmissions using a group common PDCCH (GC-PDCCH) is shown. In this case, one or more trigger bits are provided in the DCI transmitted in the GC-PDCCH within window 608.

[0114] As Figure 8As shown, BS 305 performs LBT 602 as discussed above before FFP 352-N. If LBT 602 is successful, BS 305 may send a COT indicator 802. BS 305 may then send DL data 606 and, during window 608, send a GC-PDCCH 804 with DCI pointing to the group of UEs 315-1 to 315-N.

[0115] As Figure 8 As further shown, UEs 315-1 to 315-N receive and process COT 802 during processing times 808-1 to 808-N to COT detections 806-1 to 806-N. When COT 802 is detected in COTs 801-1 to 806-N, UEs 315-1 to 315-N monitor GC-PDCCH 804 during window 608. As further shown, when GC-PDCCH 804 is detected in window 608 and processed during processing times 812-1 to 812-N to obtain results (PDCCHs 812-1 to 812-N).

[0116] As discussed above, detecting DCI GC-PDCCH 804 may trigger an RRC-configured UL-initiated COT. In some embodiments, GC-PDCCH 804 may include a specially formatted DCI to notify each of UEs 315-1 to 315-N of scheduling of UL transmissions from each of UEs 315-1 to 315-N at a subsequent FFP 352. In some embodiments, GC-PDCCH 804 may introduce a new radio network temporary identity (RNTI), namely a COT trigger indicator RNTI (CTI-RNTI). For example, the new DCI format 2_7 may be used for UE COT triggering and may be scrambled with the new CTI-RNTI. In some embodiments, a standard format DCI may be used with introduced higher parameters (e.g., COT-IndicatorPerCell-r17). For example, DCI format 2_0 may be used for UE COT triggering and may include information fields (e.g., COT indicator 1, COT indicator 2, COT indicator 3, etc.) that may be configured via higher layer parameters.

[0117] In some embodiments, the DCI in GC-PDCCH 804 may be a one-bit bit field. In this case, each of UEs 315-1 to 315-N monitors the same bit in the DCI of GC-PDCCH 804. In this case, if the bit indicates that a UL transmission may occur at the start of the next FFP 352, then as Figure 8As shown, each UE 315-1 to 315-N having data to upload can compete for transmission in FFP 352-(N+1). As Figure 8 shown, for example, both UE315-1 and UE 316-N perform LBT 814-1 and 814-N before FFP 352-(N+1), and the one that succeeds sends UL data. If LBT 814-1 is successful, UL data 816-1 is sent, and if LBT 814-N is successful, UL data 816-N is sent.

[0118] As discussed above with respect to Figure 7 the bit field can be multi-bit, which indicates the number of FFP 352s that can be used to send UL data. In this case, each of UE 315-1 to 315-N monitors the same bit, and those UEs having UL data can compete for the next FFP. As Figure 8 shown, for example, if multiple bits indicate that the next two FFP can be used, UE 315-N (having won LBT 814-N) can send UL data 816-N in FFP 352-(N+1), and then continue to compete for FFP 352-(N+2) by performing LBT 818-N before the start of FFP 352-(N+2), and if successful, send UL data 818-N at the start of FFP 352-(N+2).

[0119] In some embodiments, more complex DCI can be sent in GC-PDCCH 804. In this case, the DCI can include one or more bits individually pointing to each of UE 315-1 to 315-N. Thus, during processing times 812-1 to 812-N, UE 315-1 to 315-N determine, based on the DCI in GC-PDCCH 804, whether they individually have an indicator for sending UL data in a subsequent FFP 352. In some embodiments, the DCI in GC-PDCCH 804 can include a one-bit determination for each of UE 315-1 to 315-N, which indicates which of UE 315-1 to 315-N (if any) can send UL data at the start of FFP 352-(N+1). In some embodiments, the DCI in GC-PDCCH 804 can include more than one bit pointing to each of UE 315-1 to 315-N, which indicates how many subsequent FFP can be used. In some embodiments, the DCI in GC-PDCCH 804 can include more than one bit indicating to each of UE 315-1 to 315-N the specific subsequent FFP that it can use for transmitting UL data.

[0120] Figure 9 represents algorithm 900 that can operate on BS 305 according to some embodiments of the present disclosure, and BS 305 can have a structure as described in Figure 5 . For example, Figure 9 shows that algorithm 900 can be executed in the FBE-based communication module 508 of BS 500 as shown in Figure 5 . As shown in Figure 9 , algorithm 900 starts at step 902. In step 904, BS 305 can perform LBT, such as LBT 602 shown in Figures 6 - 8 . In step 906, if the LBT is successful, algorithm 900 proceeds to step 908. If not successful, algorithm 900 returns to the starting step 902.

[0121] In step 908 of algorithm 900, BS 305 can send a COT indicator, such as COT indicator 604 shown in Figure 6 and 7 , or COT indicator 802 shown in Figure 8 . Then, algorithm 908 can proceed to step 910, where if DL data is available, DL data 606 is sent. In step 912, BS 305 sends DCI within a window. As shown in Figure 6 and Figure 7 , DCI data is sent in PDCCH 610 and PDCCH 702 respectively. As discussed above, the DCI shown in Figure 6 includes a one-bit trigger to indicate the availability of UL data to be sent at the start of a subsequent FFP. The DCI shown in Figure 7 includes a multi-bit trigger to indicate the availability of UL data to be sent at the start of the indicated multiple subsequent FFP. The DCI shown in Figure 8 indicates to multiple UEs in a group whether a subsequent FFP is available for UL data transmission, and can also indicate which UEs in the group are to transmit and how many subsequent FFP are available for UL data transmission.

[0122] In step 914 of algorithm 900, BS 305 receives UL data that has been sent at the start of a subsequent FFP 352, as shown in Figures 6 - 8 . Once completed, algorithm 900 then returns to the starting step 902.

[0123] Figure 10 shows algorithm 1000 that can operate on UE 315 according to some embodiments of the present disclosure, and UE 315 can have a structure as described in Figure 5 . For example, Figure 10 shows that it can be inFigure 4 The algorithm 1000 executed in the FBE-based communication module 408 of the UE 400 shown. As Figure 10 shown, when the UE 315 receives a COT indicator, the UE 315 starts the algorithm 1000 at step 1002. The COT indicator processing obtains the result indicated in Figure 6 and 7 (COT indicator 612 or the COT indicator 806 indicated in Figure 8 ). Once it is determined that the COT indicator has been received, at step 1004, the UE 315 executing the algorithm 1000 monitors the window 608 to receive DCI in the PDCCH. At step 1006, the UE 315 receives the PDCCH with DCI and interprets it to determine whether the subsequent FFP is available for UL data transmission. At step 1008 of the algorithm 1000, the UE 315 transmits UL data according to the DCI. As discussed above, the DCI can indicate whether the subsequent FFP 352 is available for UL data transmission or how many subsequent FFP 352 (see FIG. 3) are available for UL transmission. In the GC-PDCCH 804 shown in Figure 8 , the DCI can indicate whether a permission to transmit UL data at the start of the subsequent FFP 352 is provided to each UE.

[0124] Information and signals can be represented using any of a variety of different technologies and methods. For example, the data, instructions, commands, information, signals, bits, symbols, and chipsets that may be referred to throughout the above description may be represented by voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

[0125] The various illustrative blocks and modules described in connection with the disclosure herein can be implemented or executed using a general-purpose processor, DSP, ASIC, FPGA, or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. The general-purpose processor may be a microprocessor, but in an alternative manner, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration).

[0126] The functions described herein can be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions can be stored on or transmitted via a computer-readable medium as one or more instructions or code. Other examples and implementations are within the scope of the present disclosure and the appended claims. For example, due to the nature of software, the functions described above can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination of these items. The features implementing the functions can also be physically located in various positions, including being distributed such that different portions of the functions are implemented at different physical locations. Further, as used herein (including in the claims), the "or" as used in a list of items (e.g., a list that ends with a phrase such as "at least one of" or "one or more of") indicates an inclusive list, such that a list of, for example, [at least one of A, B, or C] means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

[0127] As will be apparent to those of ordinary skill in the art so far, and depending on the particular application at hand, many modifications, substitutions, and changes can be made in the materials, devices, configurations, and methods of use of the devices of the present disclosure, and to them, without departing from the spirit and scope of the present disclosure. In view of this, the scope of the present disclosure should not be limited to the scope of the specific implementations shown and described herein (since they are only by way of some examples thereof), but should be fully commensurate with the appended claims and their functional equivalents.

Claims

1. A method of operating a network entity, comprising: Sending a Channel Occupancy Time (COT) indicator to a User Equipment (UE) in a first Fixed Frame Period (FFP) in a Frame-based Equipment (FBE) mode; Sending Downlink Control Information (DCI) during a window of the first FFP, wherein the DCI comprises two or more bits that indicate to the UE that a plurality of subsequent FFP can be used for Uplink (UL) data; and Receiving UL data from the UE during a second FFP following the first FFP according to the DCI.

2. The method according to claim 1, wherein Sending DCI during the window comprises: sending the DCI in a Group Common Physical Downlink Control Channel (GC-PDCCH).

3. The method according to claim 2, wherein, The DCI notifies each UE in the group whether UL transmission can be performed at the start of a subsequent FFP.

4. The method according to claim 2, wherein The DCI is associated with a COT Trigger Indicator New Radio Network Temporary Identifier (CTI-RNTI).

5. The method according to claim 2, wherein, The DCI comprises DCI format 2_0 associated with a configured higher layer parameter for UE COT trigger.

6. The method according to claim 2, wherein The DCI comprises a one-bit field monitored by a plurality of UEs in the group.

7. The method according to claim 2, wherein, The DCI comprises a plurality of bits providing an indication to a plurality of UEs.

8. A method of operating a User Equipment (UE), comprising: Receiving a Channel Occupancy Time (COT) indicator from a network entity in a first Fixed Frame Period (FFP) in a Frame-based Equipment (FBE) mode; Monitoring a window of the first FFP; Receiving Downlink Control Information (DCI) during the window; And Sending Uplink (UL) data to the network entity during a second FFP following the first FFP according to the DCI, wherein sending UL data comprises: determining whether the UE can perform transmission of the UL data during a plurality of subsequent FFP according to two or more bits of the DCI.

9. The method according to claim 8, wherein Receiving DCI during the window comprises: receiving the DCI in a Group Common Physical Downlink Control Channel (GC-PDCCH).

10. The method according to claim 9, wherein, Sending UL data comprises: determining whether the UE can perform UL transmission at the start of a subsequent FFP according to the DCI.

11. The method according to claim 10, wherein, Determining according to the DCI comprises: monitoring a one-bit field monitored by a plurality of UEs in the group.

12. The method according to claim 10, wherein, Determining according to the DCI comprises: monitoring a specific bit assigned to the UE from a plurality of bits providing an indication to a plurality of UEs.

13. The method according to claim 12, wherein, Determining according to the DCI comprises: monitoring several bits in the plurality of bits that indicate which subsequent FFP are available for UL transmission by the UE.

14. A network entity, comprising: A transceiver; And A Frame-based Equipment (FBE) communication module coupled to the transceiver, the FBE communication module being configured to execute instructions to perform the following operations: Sending a Channel Occupancy Time (COT) indicator to a User Equipment (UE) in a first Fixed Frame Period (FFP) in an FBE mode, Transmit downlink control information (DCI) during a window of the first FFP, where the DCI includes two or more bits that indicate to the UE that multiple subsequent FFPs can be used for uplink (UL) data transmission, and Receive UL data from the UE during a second FFP following the first FFP according to the DCI.

15. The network entity according to claim 14, wherein, Transmitting the DCI during the window includes: transmitting the DCI in a group common physical downlink control channel (GC-PDCCH).

16. The network entity according to claim 15, wherein, The DCI notifies each UE in the group whether UL transmission can be performed at the start of a subsequent FFP.

17. The network entity according to claim 15, wherein, The DCI is associated with a COT trigger indicator new radio network temporary identifier (CTI-RNTI).

18. The network entity according to claim 15, wherein, The DCI includes DCI format 2_0 associated with a configured higher layer parameter for UE COT trigger.

19. The network entity according to claim 15, wherein, The DCI includes a one-bit field monitored by multiple UEs in the group.

20. The network entity according to claim 15, wherein, The DCI includes multiple bits that provide an indication to multiple UEs.

21. A user equipment (UE) includes: A transceiver; And A frame-based device (FBE) communication module coupled to the transceiver, the FBE communication module being configured to execute instructions to perform the following operations: Receive a channel occupancy time (COT) indicator from a network entity in a first fixed frame period (FFP) in FBE mode, Monitor a window of the first FFP, Receive downlink control information (DCI) during the window, and Transmit uplink (UL) data to the network entity during a second FFP following the first FFP according to the DCI. Wherein, to transmit UL data, the UE executes instructions to perform the following operations: determine whether the UE can perform transmission of the UL data during multiple subsequent FFPs according to two or more bits of the DCI.

22. The UE according to claim 21, wherein, To receive the DCI during the window, the UE executes instructions to perform the following operations: receive the DCI in a group common physical downlink control channel (GC-PDCCH).

23. The UE according to claim 22, wherein, To transmit the UL data, the UE executes instructions to perform the following operations: determine whether the UE can perform transmission of the UL data at the start of a subsequent FFP according to the DCI.

24. The UE according to claim 23, wherein To make a determination according to the DCI, the UE executes instructions to perform the following operations: monitor a one-bit field monitored by multiple UEs in the group.

25. The UE according to claim 23, wherein, To make a determination according to the DCI, the UE executes instructions to perform the following operations: monitor a specific bit assigned to the UE from multiple bits that provide an indication to multiple UEs.

26. The UE according to claim 25, wherein, To make a determination according to the DCI, the UE executes instructions to perform the following operations: monitor several bits among the multiple bits that indicate which subsequent FFPs are available for UL transmission by the UE.

27. A non-transitory computer-readable medium having program code recorded thereon for operations on a network entity, the program code, when executed, causing the network entity to perform the method according to any one of claims 1 to 7.

28. A non-transitory computer-readable medium having program code recorded thereon for operations on a user equipment (UE), the program code, when executed, causing the UE to perform the method according to any one of claims 8 to 13.

Images