Method and device for channel sensing technology based on unlicensed spectrum frames

Abstract

The present invention provides methods, circuits, and systems for performing frame-based equipment channel sensing in an unlicensed spectrum. In one example, a user equipment (UE) device includes a processor configured to perform operations including: receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) configurations from a base station (BS); performing UE-initiated COT FBE channel sensing based on a selected configuration among the received plurality of UE-initiated COT FBE configurations to obtain a COT; and transmitting data during the COT.

Description

Background Art

[0001] In unlicensed spectrum, a device seeking to transmit first performs a Clear Channel Assessment (CCA) procedure to ensure that the intended channel is clear. The CCA procedure adversely affects latency. BRIEF DESCRIPTION OF THE DRAWINGS

[0002] Some examples of circuits, devices and / or methods will be described below by way of example only.In this context, reference will be made to the accompanying drawings.

[0003] Figure 1 An exemplary fixed frame period (FFP) for frame-based equipment (FBE) type channel sensing is shown.

[0004] Figure 2 A flow chart illustrating exemplary signaling performed between a user equipment (UE) device and a base station (BS) in which the BS performs an FBE channel sensing procedure to obtain a channel occupation time (COT) for the UE to transmit data, according to various aspects described.

[0005] Figure 3 A flow chart illustrating exemplary signaling performed between a user equipment (UE) device and a base station (BS) to configure the UE to perform an FBE channel sensing procedure to obtain a channel occupancy time (COT) for transmitting data in accordance with various aspects described herein.

[0006] Figure 4A An example FBE configuration table for configuring a UE to perform FBE channel sensing in accordance with various described aspects is shown.

[0007] Figure 4B An example FBE configuration table is shown for configuring a UE to perform FBE channel sensing using different energy thresholds in different configurations in accordance with various described aspects.

[0008] Figure 5A An example FBE configuration table for configuring a UE to perform FBE channel sensing with offsets for different sets of resource blocks in a bandwidth part is shown in accordance with various described aspects.

[0009] Figure 5B A bandwidth portion is shown in accordance with various described aspects, wherein different fixed frame periods are configured for different resource block sets in the bandwidth portion.

[0010] Figure 6 A flowchart illustrating an example method for configuring a UE to perform FBE channel sensing in accordance with various described aspects is shown.

[0011] Figure 7A flowchart illustrating an example method for configuring a UE to perform FBE channel sensing in accordance with various described aspects is shown.

[0012] Figure 8 A flowchart is shown of an example method for configuring a device to perform FBE channel sensing on a per resource block set basis in accordance with various described aspects.

[0013] Figure 9 An exemplary communication network in accordance with various disclosed aspects is shown.

[0014] Figure 10 Exemplary infrastructure equipment devices (e.g., BS, eNB, gNB, etc.) according to various aspects disclosed are shown.

[0015] Figure 11 Exemplary user equipment devices (eg, UEs, wireless transmit and receive units, etc.) according to various disclosed aspects are shown. DETAILED DESCRIPTION

[0016] The present disclosure is described with reference to the accompanying drawings. The drawings are not drawn to scale and are provided solely for the purpose of illustrating the present disclosure. Several aspects of the present disclosure are described below with reference to example applications for illustration. Many specific details, relationships, and methods are set forth to provide an understanding of the present disclosure. The present disclosure is not limited by the order of the actions or events illustrated, as some actions may occur in a different order and / or simultaneously with other actions or events. Furthermore, not all illustrated actions or events are necessary to implement the method according to the selected disclosure.

[0017] In order to promote efficient and reasonable spectrum sharing in unlicensed spectrum, a dynamic shared spectrum sharing mechanism called Listen Before Talk (LBT) is provided in Long Term Evolution Unlicensed (LTE-U) and New Radio Unlicensed (NR-U) communication systems. LBT is a contention-based protocol that allows many users to use the same radio channel without prior coordination. There are two LBT mechanisms, namely frame-based equipment (FBE) and load-based equipment (LBE). In FBE, channel sensing is performed at fixed moments by devices seeking to transmit on the channel. If the channel is busy, the device backs off for a fixed time period and senses the channel again after the time period. In LBE, the device can sense the channel at any time, and if the channel is found to be busy, a random backoff period is used.

[0018] There are tradeoffs between these two LBT mechanisms. For example, LBE allows transmitters to contend for the channel as soon as it becomes idle, which tends to reduce latency. However, FBE is considered beneficial for NR-U networks because the fixed frame interval can be defined to be the same as the slot boundaries of the NR licensed carrier.

[0019] Figure 1 Time domain resources 110 are shown that constitute an exemplary fixed frame period (FFP) for FBE channel sensing. The FFP is configured by the gNB in ​​a system information block (SIB) (e.g., SIB1). The maximum channel occupancy time (COT) (e.g., 95% of the FFP) is defined by the regulatory body and encoded in the specification. In the NR specification, frame boundaries are fixed at 10 ms. The FBE configuration specifies a backoff period and an offset (in milliseconds) relative to the frame boundary. The idle time period in each FFP corresponds to the portion of the FFP not occupied by the COT. During the idle time period, a fixed backoff period and CCA occur. Various parameters can be adjusted to account for a number of factors, including channel load and conditions and the priority of the transmitted data. To prioritize channel access, channel access priority classes (CAPCs) can be assigned to various transmissions based on, for example, the quality of service (QoS) associated with the transmission.

[0020] During idle time periods, CCA is performed to compete for the COT in the subsequent FFP. The timing of CCA during idle time is determined by a fixed backoff period. During CCA, the transmitter senses the energy level in the channel and compares it to a threshold to determine whether the channel is considered busy. If the sensed energy is below the threshold, the transmitter "acquires" or "initiates" COT, meaning that the transmitter takes control of the channel by, for example, transmitting data or coordinating DL and UL transmissions during the COT.

[0021] NR-U Release 16 specifies that FBE sensing is limited to the BS (e.g., gNB or other infrastructure equipment). This means that the UE does not perform FBE channel sensing to initiate uplink transmissions, but relies on the BS to win the channel. Figure 2 As shown in the flowchart 210 of FIG. 2 , at 220, a UE seeking to transmit data in an unlicensed spectrum transmits a scheduling request to a BS at 220. In response, the BS performs the following steps: Figure 1 The FBE channel is shown sensing and ultimately obtaining a COT. During the COT, at 230, the BS transmits an UL grant to the UE, specifying that UL should be performed during a specific portion of the COT. At 240, the UE transmits UL data over the Physical Uplink Shared Channel (PUSCH) using the resources allocated in the UL grant. It can be seen that the delay is extended because the UE waits for the BS to obtain the COT and transmit the UL grant before transmitting the UL data. Furthermore, in some use cases, the BS may be located in a higher traffic area than the UE and may therefore have a harder time than the UE in achieving the COT.

[0022] This document describes systems, methods, and circuits for supporting UE-initiated COT for FBE operation. Figure 3, flowchart 310 shows that at 320, the BS transmits a set of UE-initiated FBE configurations to the UE. The UE-initiated FBE configurations include one or more FBE configurations that will allow the UE to perform FBE channel sensing. The UE-initiated FBE configurations may include, for example, a cycle length (e.g., 10 ms), a backoff period, and an offset (in ms) relative to the frame boundary. When the UE has data to transmit, the UE performs FBE channel sensing based on the selected UE-initiated FBE configuration, and once the UE acquires the COT, at 330, the UE transmits UL data via the PUSCH.

[0023] There are several techniques for signaling BS support for UE-initiated COT and UE-initiated COT configuration. In one example, a system information block (SIB) (e.g., SIB1) broadcast by the BS can signal the BS support for UE-initiated COT. UE-initiated COT FBE configuration can also be transmitted in the SIB, which means that all UEs within a cell will share the same UE-initiated COT FBE configuration, including a fixed frame period and starting position.

[0024] In another example, UE-initiated COT FBE configuration can be conveyed using UE-specific RRC signaling. This allows for UE-specific UE-initiated COT FBE configuration based on application type (e.g., ultra-reliable low-latency communication (URLLC), enhanced mobile broadband (eMBB), or QoS requirements). One benefit of UE-specific configuration is that it allows limiting the number of UEs contending for the channel to those transmitting high-priority data.

[0025] Figure 4A Table 400 is shown outlining an exemplary UE-initiated COT FBE configuration. The term "table" herein conceptually describes any ordered manner of representing or communicating parameter value sets. In the table representation, each parameter corresponds to a "column," and each parameter value set is arranged in a "row" identified by a unique index value (not shown). The UE-initiated COT FBE configuration includes multiple FBE configurations, each specifying a fixed frame period P (e.g., in slots, symbols, or milliseconds) and an offset value O. Each FBE configuration is mapped to a channel access priority class (CAPC). This allows the UE to select an FBE configuration based on the channel access priority class applicable to unicast user-plane data multiplexed in the PUSCH. In other examples, the UE may use other parameters to select from multiple FBE configurations. Alternatively, a single FBE configuration may be communicated to the UE for channel sensing, regardless of data priority.

[0026] Figure 4BTable 450 summarizes another exemplary UE-initiated COT FBE configuration. Different 5QI indicators are mapped to channel access priority levels, allowing the UE to select an FBE configuration based on the 5QI indicator or CAPC. In addition to a fixed frame period and offset, the exemplary FBE configuration also includes an energy threshold used in channel sensing. This allows for setting a larger threshold for low-latency applications, making it more likely that a UE operating in a particular FBE configuration will win the channel.

[0027] Figure 5A and Figure 5B An FBE configuration is shown that allows different FBE configurations for different resource block (RB) sets in a wideband bandwidth portion (eg, 80 MHz BW with 4 RB sets, each spanning 20 MHz). Figure 5A An FBE configuration table is shown, where a separate (possibly different) offset is configured for each of the different RBs. Figure 5B The time domain resource diagram 510 shows the assumed offset value O 1,0 The FBE configuration for CAPC 1 is equal to zero. Providing separate FBE configurations for different RB sets in a wideband channel provides a UE or BS with finer granularity to access the shared channel and ultimately reduces latency. In other examples, different FBE configurations are provided depending on the LBT bandwidth (e.g., the bandwidth over which the UE performs LBT) to provide additional granularity.

[0028] Below are several flow charts outlining example methods. In this specification and the appended claims, the use of the term "determine" when describing method steps or functions with reference to some entities (e.g., parameters, variables, etc.) is to be interpreted broadly. For example, "determine" is to be interpreted as covering communications such as receiving and parsing an encoded entity or value of an entity. "Determine" should be interpreted as covering accessing and reading a memory (e.g., a lookup table, register, device memory, remote memory, etc.) that stores an entity or value for an entity. "Determine" should be interpreted as covering calculating or deriving an entity or value of an entity based on other quantities or entities. "Determine" should be interpreted as covering any way of inferring or identifying an entity or value of an entity.

[0029] As used herein, the term "identify," when used with reference to an entity or a value of an entity, is to be broadly interpreted to encompass any manner of determining an entity or a value of an entity. For example, the term "identify" is to be interpreted to encompass, for example, receiving and parsing communications encoding an entity or a value of an entity. The term "identify" should be interpreted to encompass accessing and reading a memory (e.g., a device queue, a lookup table, a register, a device memory, a remote memory, etc.) storing an entity or a value for an entity.

[0030] As used herein, the term "select" when used with reference to an entity or value of an entity is to be interpreted broadly to encompass any way of determining an entity or a value of an entity from a plurality or a range of possible choices. For example, the term "select" is to be interpreted as encompassing accessing and reading a memory (e.g., a lookup table, register, device memory, remote memory, etc.) that stores entities or values ​​for entities and returning an entity or entity value from those stored. The term "select" is to be interpreted as applying one or more constraints or rules to a set of input parameters to determine an appropriate entity or entity value. The term "select" is to be interpreted broadly to encompass any way of selecting an entity based on one or more parameters or conditions.

[0031] As used herein, the term "derive" is to be interpreted broadly when used with reference to an entity or a value of an entity. "Deriving" should be interpreted to encompass accessing and reading a memory (e.g., a lookup table, registers, device memory, remote memory, etc.) that stores some initial or base values, and performing processing and / or logical / mathematical operations on one or more values ​​to generate a derived entity or value for an entity. "Deriving" should be interpreted to encompass calculating or measuring an entity or a value for an entity based on other quantities or entities. "Deriving" should be interpreted to encompass any way of inferring or identifying an entity or a value for an entity.

[0032] Figure 6 A flow chart outlining a method 600 performed by a UE is shown. The method includes receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations from a base station (BS) at 610. At 620, UE-initiated COT FBE channel sensing is performed based on a selected configuration from the received plurality of UE-initiated COT FBE configurations to obtain a COT. At 630, data is transmitted during the COT.

[0033] Figure 7 A flow chart outlining a method 700 performed by a base station is shown. The method includes transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations to a user equipment (UE) device at 710. The method includes receiving data from the UE during the UE-initiated COT at 720.

[0034] Figure 8A flow chart outlining a method 800 performed by a device (e.g., a UE or a base station) is shown. The method includes determining an FBE configuration at 810, the FBE configuration including a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs. At 820, FBE channel sensing is performed in the first set of RBs based on the first FBE configuration parameter value. At 830, FBE channel sensing is performed in the second set of RBs based on the second FBE configuration parameter value.

[0035] Figure 9 An exemplary architecture of a system 900 of a communication network according to various embodiments is shown. The following description is provided for an exemplary system 900 operating in conjunction with LTE system standards and 5G or NR system standards provided by 3GPP technical specifications. However, the exemplary embodiments are not limited in this regard and may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., sixth generation (6G) systems), IEEE 702.16 protocols (e.g., WMAN, WiMAX, etc.), and the like.

[0036] like Figure 9 As shown, system 900 includes UE 901a and UE 901b (collectively referred to as "UEs 901" or "UE 901"). In this example, UE 901 is shown as a smartphone (e.g., a handheld touchscreen mobile computing device that can connect to one or more cellular networks), but may also include any mobile or non-mobile computing device, such as a consumer electronic device, a mobile phone, a smartphone, a feature phone, a tablet computer, a wearable computer device, a personal digital assistant (PDA), a pager, a wireless handheld device, a desktop computer, a laptop computer, an in-vehicle infotainment (IVI), an in-car entertainment (ICE) device, an instrument panel (IC), a head-up display (HUD) device, an on-board diagnostic (OBD) device, a dashtop mobile equipment (DME), a mobile data terminal (MDT), an electronic engine management system (EEMS), an electronic / engine electronic control unit (ECU), an electronic / engine electronic control module (ECM), an embedded system, a microcontroller, a control module, an engine management system (EMS), a connected or "smart" appliance, a MTC device, an M2M device, an IoT device, etc.

[0037] In some embodiments, any of the UEs 901 may be an IoT UE, which may include a network access layer designed for low-power IoT applications that utilize short-term UE connections. The IoT UE may utilize technologies such as M2M or MTC to exchange data with an MTC server or device via a PLMN, ProSe or D2D communications, a sensor network, or an IoT network. M2M or MTC data exchanges may be machine-initiated data exchanges. The IoT network describes interconnected IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure) with short-term connections. The IoT UE may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity to the IoT network.

[0038] UE 901 may be configured to connect to, e.g., be communicatively coupled to, a RAN 910. In an embodiment, RAN 910 may be an NG RAN or 5G RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term "NGRAN," etc., may refer to a RAN 910 operating in an NR or 5G system 900, while the term "E-UTRAN," etc., may refer to a RAN 910 operating in an LTE or 4G system 900. UE 901 utilizes connections (or channels) 903 and 904, respectively, each of which includes a physical communication interface or layer (discussed in further detail below).

[0039] In this example, connections 903 and 904 are shown as air interfaces to achieve communication coupling and may be consistent with a cellular communication protocol, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a 5G protocol, a NR protocol, and / or any other communication protocol discussed herein. In an embodiment, the UE 901 may directly exchange communication data via a ProSe interface 905. The ProSe interface 905 may alternatively be referred to as an SL interface 905 and may include one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

[0040] UE 901b is shown as being configured to access AP 906 (also referred to as "WLAN node 906," "WLAN 906," "WLAN terminal 906," "WT 906," etc.) via connection 907. Connection 907 may comprise a local wireless connection, such as a connection consistent with any IEEE 702.11 protocol, wherein AP 906 would include Wireless Fidelity. router. In this example, AP 906 is shown connected to the Internet without being connected to the core network of the wireless system (described in further detail below). In various embodiments, UE 901b, RAN 910, and AP 906 can be configured to utilize LWA operation and / or LWIP operation. LWA operation can involve RAN nodes 911a-b configuring UE 901b in the RRC_CONNECTED state to utilize radio resources of LTE and WLAN. LWIP operation can involve UE 901b using WLAN radio resources (e.g., connection 907) via an IPsec protocol tunnel to authenticate and encrypt packets (e.g., IP packets) sent over connection 907. IPsec tunneling can include encapsulating the entire original IP packet and adding a new packet header, thereby protecting the original header of the IP packet.

[0041] The RAN 910 may include one or more AN nodes or RAN nodes 911a and 911b (collectively referred to as "RAN nodes 911") that enable connections 903 and 904. As used herein, the terms "access node," "access point," and the like may describe equipment that provides radio baseband functionality for data and / or voice connections between a network and one or more users. These access nodes may be referred to as BSs, gNBs, RAN nodes, eNBs, NodeBs, RSUs, TRxPs, or TRPs, and may include ground stations (e.g., terrestrial access points) or satellite stations that provide coverage within a geographic area (e.g., a cell). As used herein, the terms "NG RAN nodes" and the like may refer to RAN nodes 911 (e.g., gNBs) operating in NR or 5G systems 900, while the terms "E-UTRAN nodes" and the like may refer to RAN nodes 911 (e.g., eNBs) operating in LTE or 4G systems 900. According to various embodiments, the RAN node 911 may be implemented as one or more dedicated physical devices such as a macrocell base station and / or a low power (LP) base station for providing a femtocell, picocell or other similar cell with a smaller coverage area, smaller user capacity or higher bandwidth than a macrocell.

[0042] According to various embodiments, the UE 901 and the RAN node 911 communicate data (e.g., transmit data and receive data) via a licensed medium (also referred to as a "licensed spectrum" and / or a "licensed band") and an unlicensed shared medium (also referred to as an "unlicensed spectrum" and / or an "unlicensed band"). The licensed spectrum may include channels operating in a frequency range of approximately 400 MHz to approximately 3.8 GHz, while the unlicensed spectrum may include a 5 GHz band.

[0043] To operate in the unlicensed spectrum, the UE 901 and the RAN node 911 may operate using LAA, eLAA, and / or feLAA mechanisms. In these implementations, the UE 901 and the RAN node 911 may perform one or more known medium sensing operations and / or carrier sensing operations to determine whether one or more channels in the unlicensed spectrum are unavailable or otherwise occupied before transmitting in the unlicensed spectrum. The medium / carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

[0044] LBT is a mechanism by which equipment (e.g., UE 901, RAN node 911, etc.) senses the medium (e.g., a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a particular channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine whether other signals are present on the channel in order to determine whether the channel is occupied or idle. The LBT mechanism allows cellular / LAA networks to coexist with existing systems in unlicensed spectrum and with other LAA networks. ED may include sensing RF energy over a period of time on an intended transmission band and comparing the sensed RF energy to a predefined or configured threshold.

[0045] Typically, existing systems in the 5 GHz band are WLANs based on IEEE 702.11 technology. WLANs employ a contention-based channel access mechanism known as CSMA / CA. Here, when a WLAN node (e.g., a mobile station (MS) such as UE 901, AP 906, etc.) intends to transmit, the WLAN node may first perform CCA before transmitting. In addition, in the event that more than one WLAN node senses the channel as idle and transmits simultaneously, a backoff mechanism is used to avoid collisions. The backoff mechanism may be a counter randomly introduced within the CWS that increases exponentially when a collision occurs and is reset to a minimum value when the transmission is successful. The LBT mechanism designed for LAA is somewhat similar to CSMA / CA for WLAN. In some implementations, the LBT process for a DL or UL transmission burst (including PDSCH or PUSCH transmission) may have an LAA contention window of variable length between X and Y ECCA slots, where X and Y are the minimum and maximum values ​​of the CWS for LAA. In one example, the minimum CWS for LAA transmissions may be 8 microseconds (μs); however, the size of the CWS and MCOT (eg, transmission burst) may be based on government regulatory requirements.

[0046] The LAA mechanism is built on the Carrier Adaptation (CA) technology of the LTE-Advanced system. In CA, each aggregated carrier is called a CC. A CC can have a bandwidth of 1.4, 3, 5, 10, 15, or 20 MHz, and up to five CCs can be aggregated, resulting in a maximum aggregate bandwidth of 100 MHz. In an FDD system, the number of aggregated carriers can be different for DL ​​and UL, where the number of UL CCs is equal to or lower than the number of DL component carriers. In some cases, each CC can have a different bandwidth than other CCs. In a TDD system, the number of CCs and the bandwidth of each CC are generally the same for DL ​​and UL.

[0047] CA also includes individual serving cells to provide individual CCs. The coverage of the serving cells may be different, for example, because CCs on different frequency bands will experience different path losses. The primary serving cell or PCell may provide the PCC for both UL and DL and may handle activities related to RRC and NAS. The other serving cells are called SCells, and each SCell may provide individual SCCs for both UL and DL. SCCs may be added and removed as needed, and changing the PCC may require the UE 901 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in unlicensed spectrum (referred to as "LAA SCells"), and the LAA SCells are assisted by the PCells operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within the same subframe.

[0048] The PDSCH carries user data and higher-layer signaling to UE 901. The PDCCH carries, among other information, information about the transport format and resource allocation associated with the PDSCH channel. It can also inform UE 901 about the transport format, resource allocation, and HARQ information associated with the uplink shared channel. Typically, downlink scheduling (allocation of control and shared channel resource blocks to UE 901b within a cell) can be performed on any of the RAN nodes 911 based on channel quality information fed back from any of the UEs 901. Downlink resource allocation information can be sent on the PDCCH for (e.g., allocated to) each of the UEs 901.

[0049] RAN 910 is shown as being communicatively coupled to a core network—in this embodiment, to a core network (CN) 920. CN 920 may include multiple network elements 922 configured to provide various data and telecommunication services to customers / subscribers (e.g., users of UE 901) connected to CN 920 via RAN 910. Components of CN 920 may be implemented in a single physical node or separate physical nodes, including components for reading and executing instructions from machine-readable or computer-readable media (e.g., non-transitory machine-readable storage media). In some embodiments, NFV may be used to virtualize any or all of the aforementioned network node functions (described in further detail below) via executable instructions stored on one or more computer-readable storage media. A logical instance of CN 920 may be referred to as a network slice, and a logical instance of a portion of CN 920 may be referred to as a network sub-slice. NFV architecture and infrastructure may be used to virtualize one or more network functions onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches (alternatively, performed by proprietary hardware). In other words, the NFV system can be used to perform virtual or reconfigurable implementations of one or more EPC components / functions.

[0050] Figure 10 An example of infrastructure equipment 1000 according to various embodiments is shown. Infrastructure equipment 1000 (or "system 1000") can be implemented as a base station, a radio head, a RAN node (such as the RAN node 911 and / or AP 906 shown and described previously), an application server 930, and / or any other element / device discussed herein. In other examples, system 1000 can be implemented in or by a UE.

[0051] System 1000 includes application circuitry 1005, baseband circuitry 1010, one or more radio front-end modules (RFEMs) 1015, memory circuitry 1020, a power management integrated circuit (PMIC) 1025, power tee circuitry 1030, network controller circuitry 1035, a network interface connector 1040, satellite positioning circuitry 1045, and a user interface 1050. In some embodiments, device 1000 may include additional components such as, for example, memory / storage, a display, a camera, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be included in more than one device. For example, the circuitry described may be separately included in more than one device for a CRAN, vBBU, or other similar implementation.

[0052] Application circuit 1005 may include circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of the following: a low dropout voltage regulator (LDO), an interrupt controller, a serial interface such as SPI, I2C, or a general-purpose programmable serial interface module, a real-time clock (RTC), a timer-counter including an interval timer and a watchdog timer, general-purpose input / output (I / O or IO), a memory card controller such as a Secure Digital (SD) Multimedia Card (MMC) or similar product, a Universal Serial Bus (USB) interface, a Mobile Industry Processor Interface (MIPI) interface, and a Joint Test Access Group (JTAG) test access port. The processor (or core) of application circuit 1005 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on system 1000. In some implementations, the memory / storage element can be an on-chip memory circuit that can include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0053] The processor of the application circuit 1005 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSPs), one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuit 1005 may include or may be a dedicated processor / controller for operating in accordance with various embodiments herein. As an example, the processor of the application circuit 1005 may include one or more processor, Processor; Advanced Micro Devices (AMD) Processor, Accelerated Processing Unit (APU), or processors; ARM Holdings, Ltd. licensed ARM-based processors, such as the ARM Cortex-A series processors provided by Cavium (TM), Inc. and MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior P-class processor; etc. In some embodiments, system 1000 may not utilize application circuit 1005 and instead may include a dedicated processor / controller to process IP data received, for example, from an EPC or 5GC.

[0054] The user interface circuitry 1050 may include one or more user interfaces designed to enable a user to interact with the system 1000 or a peripheral component interface designed to enable a peripheral component to interact with the system 1000. The user interface may include, but is not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touch screen, a speaker or other audio transmitting device, a microphone, a printer, a scanner, a headset, a display screen or display device, etc. The peripheral component interface may include, but is not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, a power port, etc.

[0055] Figure 10 The components shown can communicate with each other using interface circuitry that can include any number of bus and / or interconnect (IX) technologies, such as Industry Standard Architecture (ISA), Extended ISA (EISA), Peripheral Component Interconnect (PCI), Peripheral Component Interconnect Extended (PCIx), PCI express (PCIe), or any number of other technologies. The bus / IX can be a proprietary bus, such as used in SoC-based systems. Other bus / IX systems can be included, such as an I2C interface, an SPI interface, a point-to-point interface, and a power bus, among others.

[0056] Figure 11 An example of a platform 1100 (or "device 1100") according to various embodiments is shown. In an embodiment, computer platform 1100 may be suitable for use as UE 901, application server 930, and / or any other element / device discussed herein. Platform 1100 may include any combination of components shown in the examples. Components of platform 1100 may be implemented as integrated circuits (ICs), portions of ICs, discrete electronic devices, or other modules, logic, hardware, software, firmware, or combinations thereof adapted within computer platform 1100, or as components otherwise incorporated within a chassis of a larger system. Figure 11 The block diagram is intended to show a high-level view of the components of computer platform 1100. However, some of the components shown may be omitted, additional components may be present, and different arrangements of the components shown may occur in other implementations.

[0057] The application circuit 1105 includes circuitry such as, but not limited to, one or more processors (or processor cores), cache memory, and one or more of an LDO, an interrupt controller, a serial interface (such as SPI), I2C or a general-purpose programmable serial interface module, an RTC, a timer (including an interval timer and a watchdog timer), general-purpose I / O, a memory card controller (such as an SD MMC or similar controller), a USB interface, a MIPI interface, and a JTAG test access port. The processor (or core) of the application circuit 1105 may be coupled to or include a memory / storage element and may be configured to execute instructions stored in the memory / storage device to enable various applications or operating systems to run on the system 1100. In some implementations, the memory / storage element may be an on-chip memory circuit that may include any suitable volatile and / or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, flash memory, solid-state memory, and / or any other type of memory device technology, such as those discussed herein.

[0058] For example, the processor of application circuit 1105 may include a general-purpose or special-purpose processor, such as a commercially available processor. Inc., Cupertino, CA A series processor (e.g., A13 Bionic) or any other such processor. The processor of the application circuit 1105 may also be one or more of the following: Advanced Micro Devices (AMD) Processor or Accelerated Processing Unit (APU); from Inc.'s core processors, Snapdragon by Technologies, Inc. TM processors, Texas Instruments, Open Multimedia ApplicationsPlatform(OMAP) TM processors; MIPS-based designs from MIPS Technologies, Inc., such as the MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; ARM-based designs licensed from ARM Holdings, Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M series processors; etc. In some implementations, the application circuit 1105 can be part of a system on a chip (SoC), in which the application circuit 1105 and other components are formed as a single integrated circuit or a single package.

[0059] Baseband circuit 1110 may be implemented, for example, as a solder-in substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board, or a multi-chip module containing two or more integrated circuits.

[0060] Platform 1100 may also include an interface circuit (not shown) for connecting external devices to platform 1100. External devices connected to platform 1100 via the interface circuit include sensor circuit 1121 and electromechanical components (EMC) 1122, as well as a removable memory device coupled to removable memory circuit 1123.

[0061] Battery 1130 can power platform 1100, but in some examples, platform 1100 can be installed in a fixed location and can have a power source coupled to the power grid. Battery 1130 can be a lithium-ion battery, a metal-air battery such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, etc. In some implementations, such as in V2X applications, battery 1130 can be a typical lead-acid automobile battery.

[0062] As used herein, the term "device" is interpreted broadly to encompass a circuit, a computer-readable medium storing computer-executable instructions, a processor programmed to perform a set of functions, an integrated circuit, a system on a chip (SoC), a chipset, etc.

[0063] Although the method is shown and described as a series of actions or events above, it should be understood that the order of such actions or events shown should not be interpreted as having a limiting meaning. For example, some actions can occur in different orders and / or simultaneously with other actions or events other than those shown and / or described herein. In addition, it may not be necessary for all the actions shown to implement one or more aspects or embodiments disclosed herein. In addition, one or more actions in the actions shown herein can be performed in one or more separate actions and / or stages. In some embodiments, the method shown above can be implemented in a computer-readable medium using instructions stored in a memory. Many other embodiments and variations are possible within the scope of the present disclosure protected by the claims.

[0064] Example

[0065] Embodiment 1 is a user equipment (UE) device, the UE device including a processor configured to perform operations including: receiving multiple UE-initiated channel occupancy time (COT) frame-based equipment (FBE) configurations from a base station (BS); performing UE-initiated COTFBE channel sensing to obtain COT based on a selected configuration among the received multiple UE-initiated COT FBE configurations; and transmitting data during the COT.

[0066] Embodiment 2 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the processor is configured to perform operations comprising: selecting one of a plurality of received UE-initiated COT FBE configurations based on a channel access priority level (CAPC) associated with the data; and performing UE-initiated COT FBE channel sensing based on the selected UE-initiated COT FBE configuration.

[0067] Embodiment 3 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the processor is configured to perform operations comprising: identifying an energy level threshold in the selected UE-initiated COT FBE configuration; and performing UE-initiated COT FBE channel sensing based on the identified energy level threshold.

[0068] Embodiment 4 includes the subject matter of embodiment 1, including or omitting optional elements, wherein the processor is configured to perform operations comprising: identifying, in the selected UE-initiated COT FBE configuration, a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; performing UE-initiated COT FBE channel sensing in the first set of RBs based on the first FBE configuration parameter value; and performing UE-initiated COT FBE channel sensing in the second set of RBs based on the second FBE configuration parameter value.

[0069] Embodiment 5 includes the subject matter of embodiment 4, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0070] Embodiment 6 includes the subject matter of embodiments 1 to 5, including or omitting optional elements, wherein the processor is configured to perform operations including receiving the plurality of UE-initiated COT FBE configurations in a system information block.

[0071] Embodiment 7 includes the subject matter of embodiments 1 to 5, including or omitting optional elements, wherein the processor is configured to perform operations including receiving the plurality of UE-initiated COT FBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0072] Embodiment 8 is a base station (BS) comprising a processor configured to perform operations including transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) configurations to a user equipment (UE) device.

[0073] Embodiment 9 includes the subject matter of embodiment 8, including or omitting optional elements, wherein the processor is configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration is associated with a channel access priority class (CAPC).

[0074] Embodiment 10 includes the subject matter of embodiment 8, including or omitting optional elements, wherein the processor is configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes an energy level threshold.

[0075] Embodiment 11 includes the subject matter of embodiment 8, including or omitting optional elements, wherein the processor is configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs.

[0076] Embodiment 12 includes the subject matter of embodiment 11, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0077] Embodiment 13 includes the subject matter of embodiments 8 to 12, including or omitting optional elements, wherein the processor is configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations in a system information block.

[0078] Embodiment 14 includes the subject matter of embodiments 8 to 12, including or omitting optional elements, wherein the processor is configured to perform operations including transmitting the plurality of UE-initiated COTFBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0079] Embodiment 15 is a wireless communication device, comprising a processor configured to perform operations including reading an FBE configuration, the FBE configuration including a first value of an FBE configuration parameter mapped to a first resource block (RB) set and a second value of the FBE configuration parameter mapped to a second RB set; performing FBE channel sensing in the first RB set based on the first FBE configuration parameter value; and performing FBE channel sensing in the second RB set based on the second FBE configuration parameter value.

[0080] Embodiment 16 includes the subject matter of embodiment 15, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0081] Embodiment 17 includes the subject matter of embodiment 15, including or omitting optional elements, wherein for each of four corresponding RB sets in an 80 MHz bandwidth portion, the FBE configuration includes a corresponding value of the FBE configuration parameter.

[0082] Embodiment 18 is a method comprising: receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) configurations from a base station (BS); performing UE-initiated COT FBE channel sensing to obtain a COT based on a selected configuration among the received plurality of UE-initiated COT FBE configurations; and transmitting data during the COT.

[0083] Embodiment 19 includes the subject matter of embodiment 18, including or omitting optional elements, including: selecting one of the received multiple UE-initiated COT FBE configurations based on a channel access priority level (CAPC) associated with the data; and performing UE-initiated COT FBE channel sensing based on the selected UE-initiated COT FBE configuration.

[0084] Embodiment 20 includes the subject matter of embodiment 18, including or omitting optional elements, including: identifying an energy level threshold in the selected UE-initiated COT FBE configuration; and performing UE-initiated COTFBE channel sensing based on the identified energy level threshold.

[0085] Embodiment 21 includes the subject matter of embodiment 18, including or omitting optional elements, including: in the selected UE-initiated COT FBE configuration, identifying a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; performing UE-initiated COT FBE channel sensing in the first set of RBs based on the first FBE configuration parameter value; and performing UE-initiated COT FBE channel sensing in the second set of RBs based on the second FBE configuration parameter value.

[0086] Embodiment 22 includes the subject matter of embodiment 21, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0087] Embodiment 23 includes the subject matter of embodiments 18 to 22, including or omitting optional elements, including receiving the plurality of UE-initiated COT FBE configurations in a system information block.

[0088] Embodiment 24 includes the subject matter of embodiments 18 to 22, including or omitting optional elements, including receiving the plurality of UE-initiated COT FBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0089] Embodiment 25 is a method comprising: transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) configurations to a user equipment (UE) device; and receiving data from the UE during the UE-initiated COT.

[0090] Embodiment 26 includes the subject matter of embodiment 25, including or omitting optional elements, including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration is associated with a channel access priority class (CAPC).

[0091] Embodiment 27 includes the subject matter of embodiment 25, including or omitting optional elements, including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes an energy level threshold.

[0092] Embodiment 28 includes the subject matter of embodiment 25, including or omitting optional elements, including transmitting the received multiple UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs.

[0093] Embodiment 29 includes the subject matter of embodiment 28, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0094] Embodiment 30 includes the subject matter of embodiments 25 to 29, including or omitting optional elements, including transmitting the multiple UE-initiated COT FBE configurations in a system information block.

[0095] Embodiment 31 includes the subject matter of embodiments 25 to 29, including or omitting optional elements, including transmitting the multiple UE-initiated COT FBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0096] Embodiment 32 is a method comprising determining an FBE configuration, the FBE configuration comprising a first value of an FBE configuration parameter mapped to a first resource block (RB) set and a second value of the FBE configuration parameter value mapped to a second RB set; performing FBE channel sensing in the first RB set based on the first FBE configuration parameter value; and performing FBE channel sensing in the second RB set based on the second FBE configuration parameter value.

[0097] Embodiment 33 includes the subject matter of embodiment 32, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0098] Embodiment 34 includes the subject matter of embodiment 32, including or omitting optional elements, wherein for each of four respective 20 MHz wide RB sets in an 80 MHz bandwidth portion, the FBE configuration includes a respective value of the FBE configuration parameter.

[0099] Embodiment 35 is a baseband processor configured to perform operations including: receiving a plurality of UE-initiated channel occupation time (COT) frame-based equipment (FBE) channel sensing configurations from a base station (BS);

[0100] performing UE-initiated COTFBE channel sensing to acquire a COT based on a selected configuration among the received plurality of UE-initiated COT FBE configurations; and transmitting data during the COT.

[0101] Embodiment 36 includes the subject matter of embodiment 35, including or omitting optional elements, and is further configured to perform operations including: selecting one of the received multiple UE-initiated COT FBE configurations based on a channel access priority level (CAPC) associated with the data; and performing UE-initiated COT FBE channel sensing based on the selected UE-initiated COT FBE configuration.

[0102] Embodiment 37 includes the subject matter of embodiment 35, including or omitting optional elements, and is further configured to perform operations including: identifying an energy level threshold in the selected UE-initiated COT FBE configuration; and performing UE-initiated COT FBE channel sensing based on the identified energy level threshold.

[0103] Embodiment 38 includes the subject matter of embodiment 35, including or omitting optional elements, and is further configured to perform operations including: identifying, in the selected UE-initiated COT FBE configuration, a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; performing UE-initiated COT FBE channel sensing in the first set of RBs based on the first FBE configuration parameter value; and performing UE-initiated COT FBE channel sensing in the second set of RBs based on the second FBE configuration parameter value.

[0104] Embodiment 39 includes the subject matter of embodiment 38, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0105] Embodiment 40 includes the subject matter of embodiments 35 to 39, including or omitting optional elements, and is further configured to perform operations including receiving the plurality of UE-initiated COT FBE configurations in a system information block.

[0106] Embodiment 41 includes the subject matter of embodiments 35 to 39, including or omitting optional elements, and is further configured to perform operations including receiving the plurality of UE-initiated COT FBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0107] Embodiment 42 is a baseband processor configured to perform operations including: transmitting multiple UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations to a user equipment (UE) device; and receiving data from the UE during the UE-initiated COT.

[0108] Embodiment 43 includes the subject matter of embodiment 42, including or omitting optional elements, and is further configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration is associated with a channel access priority class (CAPC).

[0109] Embodiment 44 includes the subject matter of embodiment 42, including or omitting optional elements, further configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes an energy level threshold.

[0110] Embodiment 45 includes the subject matter of embodiment 42, including or omitting optional elements, and is further configured to perform operations including transmitting the received multiple UE-initiated COT FBE configurations, wherein each UE-initiated COT FBE configuration includes a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs.

[0111] Embodiment 46 includes the subject matter of embodiment 45, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0112] Embodiment 47 includes the subject matter of embodiments 42 to 46, including or omitting optional elements, and is further configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations in a system information block.

[0113] Embodiment 48 includes the subject matter of embodiments 42 to 46, including or omitting optional elements, further configured to perform operations including transmitting the plurality of UE-initiated COT FBE configurations in radio resource control (RRC) signaling dedicated to the UE.

[0114] Embodiment 49 is a baseband processor configured to perform operations including determining an FBE configuration, the FBE configuration including a first value of an FBE configuration parameter mapped to a first resource block (RB) set and a second value of the FBE configuration parameter mapped to a second RB set; performing FBE channel sensing in the first RB set based on the first FBE configuration parameter value; and performing FBE channel sensing in the second RB set based on the second FBE configuration parameter value.

[0115] Embodiment 50 includes the subject matter of embodiment 49, including or omitting optional elements, wherein the FBE configuration parameters include offset values.

[0116] Embodiment 52 includes the subject matter of embodiment 49, including or omitting optional elements, wherein for each of four respective 20 MHz wide RB sets in an 80 MHz bandwidth portion, the FBE configuration includes a respective value of the FBE configuration parameter.

[0117] The term "coupled" is used throughout this specification. This term encompasses any connection, communication, or signal path that enables a functional relationship consistent with the description of this disclosure. For example, if device A generates a signal to control device B to perform an action, then in the first example, device A is coupled to device B. Alternatively, in the second example, if the intermediate component C does not substantially change the functional relationship between devices A and B such that device B is controlled by device A via the control signal generated by the devices, then device A is coupled to device B via the intermediate component C.

[0118] It is understood that the use of personally identifiable information should be subject to privacy policies and practices that are generally recognized to meet or exceed industry or government requirements for maintaining user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly stated to users.

Claims

1. A user equipment (UE), comprising: Memory; and a processor coupled to the memory, the processor configured to perform operations including: receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations from a base station (BS), wherein different ones of the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority classes (CAPCs); In response to uplink data being available for transmission, selecting one of the received plurality of UE-initiated COT FBE channel sensing configurations based on a CAPC associated with the uplink data; performing UE-initiated COT FBE channel sensing to obtain a COT based on the selected UE-initiated COT FBE channel sensing configuration; as well as The uplink data is transmitted during the COT.

2. The UE of claim 1 , wherein the processor is configured to perform operations comprising: identifying an energy level threshold in the selected UE-initiated COT FBE channel sensing configuration; and UE-initiated COT FBE channel sensing is performed based on the identified energy level threshold.

3. The UE of claim 1 , wherein the processor is configured to perform operations comprising: In the selected UE-initiated COT FBE channel sensing configuration, identifying a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; and Based on the configured RB set, UE-initiated COTFBE channel sensing is performed in the first RB set based on the first FBE configuration parameter value, or UE-initiated COT FBE channel sensing is performed in the second RB set based on the second FBE configuration parameter value. The UE of claim 1 , wherein each UE-initiated COT FBE channel sensing configuration indicates an offset value. The UE of claim 1 , wherein each UE-initiated COT FBE channel sensing configuration indicates a fixed frame period value.

6. The UE of claim 1 , wherein the processor is configured to perform operations comprising: The plurality of UE-initiated COT FBE channel sensing configurations are received in radio resource control (RRC) signaling dedicated to the UE.

7. A base station (BS), the BS comprising a processor configured to perform operations comprising: transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations to a user equipment (UE) device, wherein different ones of the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority levels (CAPCs); and Data is received from the UE during a UE-initiated COT. 8 . The BS of claim 7 , wherein each UE-initiated COT FBE channel sensing configuration includes an energy level threshold.

9. The BS of claim 7, wherein each UE-initiated COT FBE channel sensing configuration comprises a first value of an FBE configuration parameter mapped to a first resource block (RB) set and a second value of the FBE configuration parameter mapped to a second RB set. 10 . The BS of claim 7 , wherein each UE-initiated COT FBE channel sensing configuration indicates an offset value.

11. The BS of claim 7, wherein each UE-initiated COT FBE channel sensing configuration indicates a fixed frame period value.

12. The BS of claim 7, wherein the processor is configured to perform operations comprising: The plurality of UE-initiated COT FBE channel sensing configurations are transmitted in radio resource control (RRC) signaling dedicated to the UE.

13. A communication method, comprising: receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations from a base station (BS), wherein different ones of the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority classes (CAPCs); In response to uplink data being available for transmission, selecting one of the received plurality of UE-initiated COT FBE channel sensing configurations based on a CAPC associated with the uplink data; performing UE-initiated COT FBE channel sensing to obtain a COT based on the selected UE-initiated COT FBE channel sensing configuration; as well as The uplink data is transmitted during the COT.

14. The method according to claim 13, comprising: identifying an energy level threshold in a selected UE-initiated COT FBE channel sensing configuration; as well as UE-initiated COT FBE channel sensing is performed based on the identified energy level threshold.

15. The method according to claim 13, comprising: identifying, in the selected UE-initiated COT FBE channel sensing configuration, a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; as well as Based on the configured RB set, UE-initiated COTFBE channel sensing is performed in the first RB set based on the first FBE configuration parameter value, or UE-initiated COT FBE channel sensing is performed in the second RB set based on the second FBE configuration parameter value. The method of claim 13 , wherein each UE-initiated COT FBE channel sensing configuration indicates an offset value.

17. The method of claim 13, wherein each UE-initiated COT FBE channel sensing configuration indicates a fixed frame period value.

18. The method according to claim 13, comprising: The plurality of UE-initiated COT FBE channel sensing configurations are received in radio resource control (RRC) signaling dedicated to the UE.

19. A communication method comprising: transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations to a user equipment (UE) device, wherein different UE-initiated COTFBE channel sensing configurations among the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority levels (CAPCs); as well as Data is received from the UE during a UE-initiated COT.

20. The method of claim 19, wherein each UE-initiated COT FBE channel sensing configuration includes an energy level threshold.

21. The method of claim 19, wherein each UE-initiated COT FBE channel sensing configuration comprises a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs.

22. The method of claim 19, wherein each UE-initiated COT FBE channel sensing configuration indicates an offset value.

23. The method of claim 19, wherein each UE-initiated COT FBE channel sensing configuration indicates a fixed frame period value.

24. The method of claim 19, comprising: The plurality of UE-initiated COT FBE channel sensing configurations are transmitted in radio resource control (RRC) signaling dedicated to the UE.

25. A baseband processor, the baseband processor being configured to perform operations comprising: receiving a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations from a base station (BS), wherein different ones of the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority classes (CAPCs); In response to uplink data being available for transmission, selecting one of the received plurality of UE-initiated COT FBE channel sensing configurations based on a CAPC associated with the uplink data; performing UE-initiated COT FBE channel sensing to obtain a COT based on the selected UE-initiated COT FBE channel sensing configuration; as well as The uplink data is transmitted during the COT.

26. The baseband processor of claim 25, further configured to perform operations comprising: identifying an energy level threshold in the selected UE-initiated COT FBE channel sensing configuration; and UE-initiated COT FBE channel sensing is performed based on the identified energy level threshold.

27. The baseband processor of claim 25, further configured to perform operations comprising: In the selected UE-initiated COT FBE channel sensing configuration, identifying a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs; and Based on the configured RB set, UE-initiated COTFBE channel sensing is performed in the first RB set based on the first FBE configuration parameter value, or UE-initiated COT FBE channel sensing is performed in the second RB set based on the second FBE configuration parameter value.

28. The baseband processor of claim 25, wherein each UE-initiated COTFBE channel sensing configuration indicates an offset value.

29. The baseband processor of claim 25, wherein each UE-initiated COTFBE channel sensing configuration indicates a fixed frame period value.

30. The baseband processor of claim 25, further configured to perform operations comprising: The plurality of UE-initiated COT FBE channel sensing configurations are received in radio resource control (RRC) signaling dedicated to user equipment including the baseband processor.

31. A baseband processor, the baseband processor being configured to perform operations comprising: transmitting a plurality of UE-initiated channel occupancy time (COT) frame-based equipment (FBE) channel sensing configurations to a user equipment (UE) device, wherein different ones of the plurality of UE-initiated COT FBE channel sensing configurations are associated with different channel access priority levels (CAPCs); and Data is received from the UE during a UE-initiated COT.

32. The baseband processor of claim 31 , wherein each UE-initiated COTFBE channel sensing configuration includes an energy level threshold.

33. The baseband processor of claim 31 , wherein each UE-initiated COTFBE channel sensing configuration comprises a first value of an FBE configuration parameter mapped to a first set of resource blocks (RBs) and a second value of the FBE configuration parameter mapped to a second set of RBs.

34. The baseband processor of claim 31 , wherein each UE-initiated COTFBE channel sensing configuration indicates an offset value.

35. The baseband processor of claim 31 , wherein each UE-initiated COTFBE channel sensing configuration indicates a fixed frame period value.

36. The baseband processor of claim 31 , further configured to perform operations comprising: The plurality of UE-initiated COT FBE channel sensing configurations are transmitted in radio resource control (RRC) signaling dedicated to the UE.

Images