Patent Description:
NR-U is designed to maintain fair coexistence with other incumbent technologies using the shared spectrum, such as WiFi, and in order to do so, depending on the particular band in which it may operate, some regulatory restrictions may apply. For instance, if operating in the <NUM> band, a listen before talk (LBT) procedure may be required to acquire the medium before a transmission can occur. An LBT such as a clear channel assessment (CCA) may be performed by a next generation node B (gNB) on a downlink (DL) channel prior to a DL transmission occurring. Currently, a UE is allowed to perform (UL) transmissions only if a DL signal or channel is first detected. This requirement may increase UL latency, especially for physical resource access channels (PRACH) and some latency-sensitive service types, such as ultra-reliable low latency communications (URLLC).

The following document is relevant: 3GPP DRAFT; R1-<NUM>; Contribution by SAMSUNG which discusses channel access procedures for NR-U.

Further embodiments are described by the dependent claims.

Some exemplary aspects are related to a base station having a transceiver and one or more processors. The transceiver is configured to connect to a user equipment (UE) over a shared channel subject to channel access operations. The one or more processors are communicatively coupled to the transceiver and configured to perform operations. The operations include transmitting to the UE a first configuration for a BS-initiated fixed frame period (FFP) (BS-FFP) and a second configuration for a UE-initiated FFP (UE-FFP), wherein the BS-FFP overlaps the UE-FFP, scheduling an uplink (UL) transmission during the UE-FFP and when there is no downlink (DL) transmission in the BS-FFP, receiving the UL transmission from the UE during the BS-FFP.

Other exemplary aspects are related to a baseband processor that performs operations. The operations include transmitting, to a user equipment (UE), a first configuration for a base station (BS)-initiated fixed frame period (BS-FFP) and a second configuration for a UE-initiated FFP (UE-FFP), wherein the BS-FFP overlaps the UE-FFP, scheduling an uplink (UL) transmission during the UE-FFP and when there is no downlink (DL) transmission in the BS-FFP, receiving the UL transmission from the UE during the BS-FFP.

The exemplary aspects may be further understood with reference to the following description and the related appended drawings, wherein like elements are provided with the same reference numerals. The exemplary aspects describe configurations for a user equipment (UE) where the UE may, under certain conditions, initiate a channel access procedure for determining a channel status for a scheduled uplink (UL) transmission. The exemplary UE may, in some aspects, be configured with two fixed frame periods (FFPs), one corresponding to a channel access procedure initiated by a new generation node B (gNB), and the other corresponding to a channel access procedure initiated by the UE. The gNB-initiated channel access procedure may include a frame based equipment (FBE) listen before talk (LBT) operation, followed by the gNB-FFP, during which, when the FBE is successful at the gNB, the UE may detect a downlink (DL) transmission. In some aspects, when a DL transmission is not detected and certain conditions are met for a scheduled UL transmission, the UE may initiate its own channel access procedure including an FBE that, when successful, allows the UE to perform the scheduled UL transmission. In still other aspects, rather than configuring a UE-FFP, the UE may perform some UL transmissions when the UL transmissions are located within particular symbols in the gNB-FFP.

Although the exemplary aspects will be described with regard to the <NUM> NR network, those skilled in the art will understand the exemplary aspects may be modified and/or used with any network that supports a functionality that utilizes bandwidths outside a designated or licensed spectrum that may be shared amongst radio access technologies (RATs). For example, a legacy network such as LTE supports CA functionalities where an SCC may be established for an unlicensed band and certain of the exemplary aspects may be used with such a network, e.g. when Licensed Assisted Access (LAA) functionality is configured. In addition, NR-U may be used as a standalone functionality for connecting to an unlicensed bandwidth, independent from any CA operation. Thus, the exemplary aspects described below may be used in a CA configuration or in the absence of a CA configuration.

<FIG> shows an exemplary network arrangement <NUM> according to various exemplary aspects. The exemplary network arrangement <NUM> includes a plurality of UEs <NUM>, <NUM>. Those skilled in the art will understand that the UEs may be any type of electronic component that is configured to communicate via a network, e.g., a component of a connected car, a mobile phone, a tablet computer, a smartphone, a phablet, an embedded device, a wearable, an Internet of Things (IoT) device, etc. It should also be understood that an actual network arrangement may include any number of UEs being used by any number of users. Thus, the example of two UEs <NUM>, <NUM> is merely provided for illustrative purposes. In some of the exemplary aspects described below, groups of UEs may be employed to conduct respective channel measurements.

The UEs <NUM>, <NUM> may communicate directly with one or more networks. In the example of the network configuration <NUM>, the networks with which the UEs <NUM>, <NUM> may wirelessly communicate are a <NUM> NR radio access network (<NUM> NR-RAN) <NUM>, an LTE radio access network (LTE-RAN) <NUM> and a wireless local access network (WLAN) <NUM>. Therefore, the UEs <NUM>, <NUM> may include a <NUM> NR chipset to communicate with the <NUM> NR-RAN <NUM>, an LTE chipset to communicate with the LTE-RAN <NUM> and an ISM chipset to communicate with the WLAN <NUM>. However, the UEs <NUM>, <NUM> may also communicate with other types of networks (e.g. legacy cellular networks) and the UE <NUM> may also communicate with networks over a wired connection. With regard to the exemplary aspects, the UEs <NUM>, <NUM> may establish a connection with the <NUM> NR-RAN <NUM> and/or the LTE-RAN <NUM>.

The <NUM> NR-RAN <NUM> and the LTE-RAN <NUM> may be portions of cellular networks that may be deployed by cellular providers (e.g., Verizon, AT&T, Sprint, T-Mobile, etc.). These networks <NUM>, <NUM> may include, for example, cells or base stations (Node Bs, eNodeBs, HeNBs, eNBS, gNBs, gNodeBs, macrocells, microcells, small cells, femtocells, etc.) that are configured to send and receive traffic from UEs that are equipped with t' appropriate cellular chip set. The WLAN <NUM> may include any type of wireless local area network (WiFi, Hot Spot, IEEE <NUM>. 11x networks, etc.).

The UEs <NUM>, <NUM> may connect to the <NUM> NR-RAN via at least one of the next generation nodeB (gNB) 120A and/or the gNB 120B. The gNBs 120A, 120B may be configured with the necessary hardware (e.g., antenna array), software and/or firmware to perform massive multiple in multiple out (MIMO) functionality. Massive MIMO may refer to a base station that is configured to generate a plurality of beams for a plurality of UEs. Reference to two gNB 120A, 120B is merely for illustrative purposes. The exemplary aspects may apply to any appropriate number of gNBs. Specifically, the UEs <NUM>, <NUM> may simultaneously connect to and exchange data with a plurality of gNBs 120A, 120B in a multi-cell CA configuration. The UEs <NUM>, <NUM> may also connect to the LTE-RAN <NUM> via either or both of the eNBs 122A, 122B, or to any other type of RAN, as mentioned above. In the network arrangement <NUM>, the UE <NUM> is shown as having a connection to the gNB 120A, while the UE <NUM> is shown as having a connection to gNB 120B. The UE <NUM> connection to gNB 120A may be, for example, an NR-U connection utilizing an unlicensed portion of the RF spectrum.

In addition to the networks <NUM>, <NUM> and <NUM> the network arrangement <NUM> also includes a cellular core network <NUM>, the Internet <NUM>, an IP Multimedia Subsystem (IMS) <NUM>, and a network services backbone <NUM>. The cellular core network <NUM> may be considered to be the interconnected set of components that manages the operation and traffic of the cellular network, e.g. the 5GC for NR. The cellular core network <NUM> also manages the traffic that flows between the cellular network and the Internet <NUM>.

The IMS <NUM> may be generally described as an architecture for delivering multimedia services to the UE <NUM> using the IP protocol. The IMS <NUM> may communicate with the cellular core network <NUM> and the Internet <NUM> to provide the multimedia services to the UE <NUM>. The network services backbone <NUM> is in communication either directly or indirectly with the Internet <NUM> and the cellular core network <NUM>. The network services backbone <NUM> may be generally described as a set of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that may be used to extend the functionalities of the UE <NUM> in communication with the various networks.

<FIG> shows an exemplary UE <NUM> according to various exemplary aspects. The UE <NUM> will be described with regard to the network arrangement <NUM> of <FIG>. The UE <NUM> may represent any electronic device and may include a processor <NUM>, a memory arrangement <NUM>, a display device <NUM>, an input/output (I/O) device <NUM>, a transceiver <NUM>, and other components <NUM>. The other components <NUM> may include, for example, an audio input device, an audio output device, a battery that provides a limited power supply, a data acquisition device, ports to electrically connect the UE <NUM> to other electronic devices, sensors to detect conditions of the UE <NUM>, etc. The UE <NUM> illustrated in <FIG> may also represent the UE <NUM>.

The processor <NUM> may be configured to execute a plurality of engines for the UE <NUM>. For example, the engines may include a channel access engine <NUM> for performing operations including initiating a channel access procedure at the UE. The channel access procedure may include an FBE followed by a UE fixed frame period (FFP) comprising a channel occupancy time (COT) during which the UE may perform a UL transmission, to be described in detail below. In other aspects, the channel access engine <NUM> may cause the processor to perform operations including initiating an FBE during a gNB-FFP and performing a UL transmission when the UL transmission is located within particular symbols of the gNB-FFP, to be described in detail below.

The above referenced engine being an application (e.g., a program) executed by the processor <NUM> is only exemplary. The functionality associated with the engines may also be represented as a separate incorporated component of the UE <NUM> or may be a modular component coupled to the UE <NUM>, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines may also be embodied as one application or separate applications. In addition, in some UEs, the functionality described for the processor <NUM> is split among two or more processors such as a baseband processor and an applications processor. The exemplary aspects may be implemented in any of these or other configurations of a UE.

The memory <NUM> may be a hardware component configured to store data related to operations performed by the UE <NUM>. The display device <NUM> may be a hardware component configured to show data to a user while the I/O device <NUM> may be a hardware component that enables the user to enter inputs. The display device <NUM> and the I/O device <NUM> may be separate components or integrated together such as a touchscreen. The transceiver <NUM> may be a hardware component configured to establish a connection with the <NUM>-NR RAN <NUM>, the LTE RAN <NUM> etc. Accordingly, the transceiver <NUM> may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies). For example, the transceiver <NUM> may operate on the unlicensed spectrum when e.g. NR-U is configured.

<FIG> shows an exemplary network cell, in this case gNB 120A, according to various exemplary aspects. As noted above with regard to the UE <NUM>, the gNB 120A may represent a cell providing services as a PCell or an SCell, or in a standalone configuration with the UE <NUM>. The gNB 120A may represent any access node of the <NUM> NR network through which the UEs <NUM>, <NUM> may establish a connection and manage network operations. The gNB 120A illustrated in <FIG> may also represent the gNB 120B.

The gNB 120A may include a processor <NUM>, a memory arrangement <NUM>, an input/output (I/O) device <NUM>, a transceiver <NUM>, and other components <NUM>. The other components <NUM> may include, for example, an audio input device, an audio output device, a battery, a data acquisition device, ports to electrically connect the gNB 120A to other electronic devices, etc..

The processor <NUM> may be configured to execute a plurality of engines of the gNB 120A. For example, the engines may include a channel access engine <NUM> for performing operations including configuring a UE with a UE-FFP during which the UE may send UL transmissions, to be described in detail below.

The above noted engines each being an application (e.g., a program) executed by the processor <NUM> is only exemplary. The functionality associated with the engines may also be represented as a separate incorporated component of the gNB 120A or may be a modular component coupled to the gNB 120A, e.g., an integrated circuit with or without firmware. For example, the integrated circuit may include input circuitry to receive signals and processing circuitry to process the signals and other information. In addition, in some gNBs, the functionality described for the processor <NUM> is split among a plurality of processors (e.g., a baseband processor, an applications processor, etc.). The exemplary aspects may be implemented in any of these or other configurations of a gNB.

The memory <NUM> may be a hardware component configured to store data related to operations performed by the UEs <NUM>, <NUM>. The I/O device <NUM> may be a hardware component or ports that enable a user to interact with the gNB 120A. The transceiver <NUM> may be a hardware component configured to exchange data with the UEs <NUM>, <NUM> and any other UE in the system <NUM>. The transceiver <NUM> may operate on a variety of different frequencies or channels (e.g., set of consecutive frequencies). For example, the transceiver <NUM> may operate on unlicensed bandwidths when NR-U functionality is configured. Therefore, the transceiver <NUM> may include one or more components (e.g., radios) to enable the data exchange with the various networks and UEs.

NR-U is designed to maintain fair coexistence with other incumbent technologies using the shared spectrum, such as WiFi, and in order to do so, depending on the particular band in which it may operate, some regulatory restrictions may apply. For instance, if operating in the <NUM> band, a listen before talk (LBT) procedure may be used to acquire the medium before a transmission can occur. For example, a clear channel assessment (CCA) may be performed by a next generation node B (gNB) on a downlink (DL) channel prior to a DL transmission occurring to a user equipment (UE). However, Rel-<NUM> NR-U currently supports only the gNB as the initiating device for a CCA. Consequently, the UE is allowed to perform (UL) transmissions only if a DL signal or channel, for example a physical downlink control channel (PDCCH), a synchronization signal block (SSB), a system information block (SIB) (e.g. RMSI), or a group common (GC) PDCCH, is first detected in a fixed frame period (FFP).

An FFP is a time resource for a UE that is made available for sending/receiving transmissions. The FFP length and starting position (timing offset) are parameters provided by the network in, for example, SIB1 information. Each frame period consists of a channel occupancy time (COT) and an idle period at the end of the FFP, after which the FFP repeats. A gNB may perform an LBT, such as a frame based equipment (FBE) operation, e.g. one-shot CCA, during the idle period prior to the next FFP and, if the CCA is successful, perform DL signaling or data transmission at the beginning of the FFP. If the DL transmission is detected at the UE, the UE is allowed to perform UL transmissions within the FFP. The COT may be dimensioned according to rules defined for the FBE. For example, an idle period may be no shorter than <NUM>% of the FFP and a COT may be no longer than <NUM>% of the FFP.

<FIG> shows a diagram <NUM> for a channel access procedure operation for an NR-U unlicensed channel in which only a gNB is allowed to initiate a frame based equipment (FBE) listen before talk (LBT) operation, e.g. a clear channel assessment (CCA). The exemplary diagram <NUM> includes a first FFP <NUM> followed by a second FFP <NUM>. A first CCA <NUM> is performed by the gNB prior to the first FFP <NUM>, the first FFP <NUM> having a first scheduled UL transmission <NUM> in its COT <NUM>. In this exemplary operation, it may be considered that the first CCA <NUM> failed at the gNB. Thus, the gNB does not transmit on the DL during the first COT <NUM>. Because the UE does not detect any DL transmissions prior to the first scheduled UL transmission <NUM>, the UL transmission <NUM> is dropped. A second CCA <NUM> is performed by the gNB in the idle period <NUM> at the end of the first FFP <NUM> and prior to the COT <NUM> of the second FFP <NUM>. In this exemplary operation, it may be considered that the second CCA <NUM> is successful at the gNB. Thus, the gNB transmits on the DL <NUM> during the COT <NUM> and the UE detects the DL transmission <NUM> prior to a second scheduled UL transmission <NUM> in the COT <NUM>. Because the UE detects the DL transmission <NUM> prior to the second scheduled UL transmission <NUM>, the UE performs the second scheduled UL transmission <NUM>.

As shown in the exemplary diagram <NUM>, the requirement for the UE to first detect a DL transmission/signal prior to transmitting on the UL may increase UL latency, considering the UE was required to wait until the second COT <NUM> to perform an UL transmission <NUM>. This increased latency may be especially impactful for physical resource access channels (PRACH) and some latency-sensitive service types, such as ultra-reliable low latency communications (URLLC). For example, such a requirement may make it not feasible to operate URLLC services on an unlicensed band.

According to some exemplary aspects, a UE is configured to initiate an FBE and establish a second fixed frame period (FFP) / channel occupancy time (COT) within which to transmit UL data, for example high priority data such as URLLC communications, when a gNB-initiated FBE is unsuccessful. For example, the UE may be configured with a first FFP and corresponding offset configuration for the gNB as the FBE-initiating device (hereafter referred to as a "gNB-FFP") and a second FFP and corresponding offset configuration for the UE as the FBE-initiating device (hereafter referred to as a "UE-FFP"). The UE-FFP may be configured to be shorter than the gNB-FFP, such that one or more UE-FFPs may fall within the gNB-FFP. For example, the UE-FFP may be configured relative to the gNB-FFP, e.g. as a percentage of the gNB-FFP. The candidate percentage values X for the period of the UE-FFP may be fixed, for example, in the 3GPP Standards for the UE at values of, e.g., <NUM>, <NUM>, <NUM>, <NUM>, <NUM> and <NUM> percent of the period of the gNB-FFP, wherein a value of <NUM>, when configured, indicates that the UE is not allowed to be an FBE-initiating device. The UE-FFP may be configured by either a system information block (SIB), e.g. in SIB1 (common for all UEs within a same serving cell), or by dedicated RRC signaling.

<FIG> shows an information element (IE) <NUM> for semi-static channel access configuration information (SemiStaticChannelAccessConfig) for transmission in a system information block (SIB) to a UE. The IE <NUM> may be an ASN. <NUM> message providing for separate FBE configuration parameters to enable the UE to act as the FBE-initiating device. In this example, the IE <NUM> includes a first row (period) <NUM> for configuring the gNB-FFP and offset and a second row (period2) for configuring the UE-FFP and offset. In the IE <NUM>, the second row includes parameters corresponding to each of those included for the first row. However, as mentioned above, in some aspects, the UE-FFP configuration may be indicated as a percentage "X" of the period in the first row. For example, the value of X can be a fractional or integer number. In one aspect, candidate X values may be fixed in specification e.g. X = < <NUM>,<NUM>,<NUM>,<NUM>,<NUM>,<NUM> > %, with the value "<NUM>" indicating the UE is not allowed to initiate a COT.

When configured to initiate an FFP, the UE may perform an LBT operation such as, a CCA, during a single observation period, e.g. Tsl = <NUM> microseconds, immediately before starting transmissions at the start of the UE-FFP. The UE may perform the LBT operation and initiate the COT if the following two conditions are met. First, the UE does not detect any DL transmission burst(s) from the gNB at predefined time instances within the gNB-FFP before the start of the UE-FFP. As described above, the gNB-FFP overlaps at least part of one or multiple UE-FFPs, but the UE CCA (during the observation period immediately prior to the UE-FFP) may not be initiated during predefined times of the gNB-FFP when DL transmission burst(s) are expected. In some aspects, the predefined time instances at least include symbols configured for PDCCH, SSB and periodic CSI-RS monitoring.

Regarding the second condition, prior to initiating the UE CCA, the UE should have at least one PUSCH dynamically granted by a DCI Format (DG-PUSCH), or a configured grant (CG) PUSCH transmission(s) (CG-PUSCH), in the UE-FFP. In other words, a DG-PUSCH or a CG-PUSCH should be scheduled during the UE-FFP although the actual CG-PUSCH or DG-PUSCH transmission is subject to the outcome of CCA. Alternatively, some other "predefined" UL transmissions scheduled during the UE-FFP may trigger the UE CCA to initiate a COT.

In some aspects, for the second condition, the aforementioned DG-PUSCH and CG-PUSCH may be associated with a predefined channel access priority class (CAPC) 'p. ' For example, only high priority data e.g. having a priority class of "<NUM>" or "<NUM>," may trigger the UE to initiate the UE-FFP. In this situation, a CAPC threshold Tp would be <NUM>, where p ≤ Tp (e.g., higher priority package) allows triggering the UE CCA and associated UE-COT to occur. For DG-PUSCH transmissions, the CAPC value of 'p' may be indicated in the scheduling DCI corresponding to the UL transmission. For CG-PUSCH, the CAPC value of 'p' may be determined based on a <NUM> QoS identifier (5QI) values of all the quality of service (QoS) flows multiplexed in the CG-PUSCH.

In other aspects, for the second condition, the aforementioned CG-PUSCH corresponding to a configured grant may have a priority value set to <NUM> in a ConfiguredGrantConfig IE, indicating the CG-PUSCH is high priority. The DG-PUSCH is a PUSCH scheduled by the PDCCH, and may be indicated as higher priority by using a priority indicator field in the scheduling DCI. In still other aspects, the so-called "predefined" UL transmissions mentioned above in the second condition include, e.g., UL transmissions related to a RACH procedure (e.g. PRACH transmissions) and higher priority uplink control information (UCI) transmissions (e.g. HARQ-ACK and SR transmissions over PUCCH or PUSCH). In another aspect, SRS transmissions may also be included in the "predefined" UL transmissions.

<FIG> shows a diagram <NUM> of FBE operation for a UE-initiated FFP according to one exemplary aspect. The FBE in this exemplary aspect is described as a Type 2A CCA for both the gNB-initiated and UE-initiated FFPs (gNB-FFP and UE-FFP). However, in other aspects, other LBT categories e.g. Type <NUM> CCA may be used. The diagram <NUM> will be described relative to the method <NUM> shown in <FIG>.

<FIG> shows a method <NUM> for FBE operation for a UE-initiated FFP according to various exemplary aspects. In <NUM>, a gNB configures a UE with a gNB-FFP and a UE-FFP, as described above. In the example of <FIG>, the gNB-FFP <NUM> overlaps multiple UE-FFPs <NUM>, subject to the first condition discussed above, where the UE does not perform a CCA (prior to the UE-FFP) during the predefined time instances during which the UE may detect a DL transmission burst(s) from the gNB. Two UL grants are configured for the UE, specifically a first UL grant <NUM> that is, in this aspect, a DG-PUSCH scheduled with a CAPC value of p=<NUM> by a scheduling DCI and a second UL grant <NUM> that is, in this aspect, a CG-PUSCH determined to have a CAPC value of p=<NUM> based on 5QI values of a corresponding data flow. The threshold p value Tp, in this aspect, has a value of <NUM>. Thus, when p ≤ <NUM>, the UE-FFP may be allowed to occur. The first UL grant <NUM> is scheduled during UE-FFP 604a, while the second UL grant <NUM> is scheduled during UE-FFP 604b.

In <NUM>, the gNB performs a Type 2A CAA preceding the configured gNB-FFP. In the example of <FIG>, the gNB-initiated CAA <NUM> is performed before the gNB-FFP <NUM>. In this example, the CAA <NUM> fails at the gNB, preventing the gNB from transmitting a DL transmission burst within the gNB-FFP <NUM>. Accordingly, the UE does not detect any DL transmission bursts during the predefined time instance(s) discussed above.

In <NUM>, based on not detecting a DL transmission burst during the predefined times, the UE determines whether a DG-PUSCH or a CG-PUSCH, meeting the configured conditions, is scheduled for the following UE-FFP. In the example of <FIG>, the DG-PUSCH <NUM> is scheduled in the UE-FFP 604a following the gNB CCA. However, the priority p=<NUM> of the DG-PUSCH <NUM> is greater than the threshold value Tp=<NUM>. Accordingly, the conditions are not met.

In <NUM>, when the UE determines that no DG-PUSCH or CG-PUSCH meeting the conditions is scheduled for the following UE-FFP, the UE performs no UL transmissions during the UE-FFP. In other words, in the example of <FIG>, the UE drops the scheduled DG-PUSCH transmission <NUM>. If further UE-FFPs are established prior to the end of the gNB-FFP, then the method returns to <NUM> and the UE performs the same determination for the further UE-FFP(s). In the example of <FIG>, the UE determines the CG-PUSCH <NUM> is scheduled in the UE-FFP 604b. The CG-PUSCH <NUM> has a priority p=<NUM> that is less than or equal to the threshold value Tp = <NUM>. Accordingly, the conditions for the scheduled UL transmission <NUM> are met.

In <NUM>, when the UE determines that a DG-PUSCH or a CG-PUSCH meeting the conditions is scheduled for the following UE-FFP, the UE performs a Type 2A CCA prior to the following UE-FFP. In the example of <FIG>, the UE-initiated CAA <NUM> is performed before the UE-FFP 604b. In this example, the CAA <NUM> is successful at the UE, allowing the UE to access the channel for UL.

In <NUM>, when the CCA is successful, the UE performs the UL transmission scheduled for the following UE-FFP. In the example of <FIG>, based on the successful CAA <NUM> (which is only allowed to occur once the UL transmission conditions are met for the UE-FFP), the UE performs the CG-PUSCH transmission <NUM>.

According to some exemplary aspects, the UE may perform a Type <NUM> channel access procedure for the UE-FFP instead of a Type 2A channel access procedure. The UE may perform the Type <NUM> FBE operation if the Type <NUM> operation is configured and the two aforementioned conditions are met. Those skilled in the art will understand that a general characteristic of a Type 2A channel access procedure is that the device (e.g., UE) will transmit as soon as the channel is sensed as clear. Ion the other hand, a Type <NUM> channel access procedure may have the UE sense that multiple slots are clear. Thus, in the exemplary aspects related to a Type <NUM> CCA, the UE may maintain a contention window value CWp and adjust for transmissions corresponding to each channel access priority class (CAPC) 'p', e.g., the number of clear slots to be sensed may depend on the CAPC.

According to other exemplary aspects, an energy detection threshold XThreshUE used by the UE for the CCA may be configured separately by higher layers. Those skilled in the art will understand that the energy detection threshold is the minimum amount of energy required to declare the channel busy during the CCA procedure. The UE may autonomously select one of a set of energy detection thresholds based on the associated PUSCH transmission parameters, e.g. priority class and/or 5QI value (latency requirement). For example, for higher priority classes, the UE may set the energy detection threshold higher to attempt a transmission even if the channel is potentially occupied. In some aspects, the set of energy detection thresholds may be derived based on a basic threshold value and a number of offset values to this basic threshold. The offset values may be determined based at least on the corresponding CAPC values.

In still other exemplary aspects, the UE may share the UE-initiated COT with the gNB. In this way, the gNB may preserve resources if it has knowledge of when, if at all, the UE will initiate a UL transmission. The UE may inform the gNB of the sharing either implicitly or explicitly. In a first option, the detection of a PUSCH transmission (e.g., DG-PUSCH or CG-PUSCH) for the UE serves as an implicit indicator to share the corresponding UE-FFP with the gNB. In a second option, <NUM>-bit may be encoded into uplink control information (UCI) to indicate whether the UE-FFP can be shared with the gNB or not. This provides the flexibility to select different energy thresholds, as discussed above, for CCA operation and then correspondingly indicate the UE-FFP sharing. In a third option, according to the present invention, the UE provides a row index of a table configured by higher layers e.g. RRC signaling, where a number of slots for sharing, an offset indicating where the UL transmission starts, and a CAPC for the UL transmission are jointly encoded. One row may indicate no COT sharing with the gNB.

In some exemplary aspects, the UE may additionally perform CCA for a given UL transmission (e.g., DG-PUSCH or CG-PUSCH), if the UL transmission is aligned with a gNB-FFP boundary or if the gap between the start of the gNB-FFP and the beginning of the PUSCH symbol is less than N2 symbols. If the condition is met, the UE may transmit the PUSCH immediately after sensing the channel to be idle for at least a sensing slot duration Tsi = <NUM> microseconds. This configuration is based on a minimum scheduling delay between PDCCH and PUSCH being N2 symbols, making it impossible to schedule a PUSCH transmission by PDCCH within a same gNB-FFP.

<FIG> shows a diagram <NUM> of conditional CCA operation initiated by a UE according to one exemplary aspect. As discussed above, the conditional CCA operation depends on the presence of a CG-PUSCH or a DG-PUSCH having at least one symbol within a timing window, which starts from the beginning of one gNB-FFP and has a duration of N2 symbols. Referring to <FIG>, the gNB-FFP <NUM> includes a PDCCH transmission <NUM> and the gNB-FFP <NUM> includes a PUSCH transmission <NUM>. UE performs a Type 2A CCA operation <NUM> to sense the channel availability immediately preceding the PUSCH transmission <NUM>, as the first symbol(s) of the PUSCH <NUM> falls in the N2-symbol time window starting from the beginning of the gNB-FFP <NUM>.

In other exemplary aspects, the UE does not perform CCA for UL transmissions if it does not detect any DL signal/channel that ends N1 symbols prior to the start of the UL transmission in the gNB-FFP, where N1 is the PDSCH to HARQ-ACK timeline capability of the UE.

Those skilled in the art will understand that the above-described exemplary aspects may be implemented in any suitable software or hardware configuration or combination thereof. An exemplary hardware platform for implementing the exemplary aspects may include, for example, an Intel x86 based platform with compatible operating system, a Windows OS, a Mac platform and MAC OS, a mobile device having an operating system such as iOS, Android, etc. In a further example, the exemplary aspects of the above described method may be embodied as a program containing lines of code stored on a non-transitory computer readable storage medium that, when compiled, may be executed on a processor or microprocessor.

Claim 1:
A method performed by a baseband processor, comprising:
transmitting to a user equipment, UE, a first configuration for a base station, BS-initiated fixed frame period, FFP, BS-FFP, and a second configuration for a UE-initiated FFP, UE-FFP, wherein the BS-FFP overlaps the UE-FFP;
scheduling an uplink, UL, transmission during the UE-FFP;
when there is no downlink, DL, transmission in the BS-FFP, receiving the UL transmission from the UE during the BS-FFP; and
wherein the method is characterised by receiving, from the UE, a row index of a table, wherein the BS includes the table and the row index of the table indicates a number of slots for sharing, an offset indicating where the UL transmission starts, and a priority for the UL transmission.