CN117296432A

CN117296432A - Channel occupancy time initiator determination in a frame-based device scene

Info

Publication number: CN117296432A
Application number: CN202180098176.3A
Authority: CN
Inventors: T·E·伦蒂拉; C·罗萨; K·J·霍利; 陶涛
Original assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Current assignee: Nokia Shanghai Bell Co Ltd; Nokia Solutions and Networks Oy
Priority date: 2021-05-11
Filing date: 2021-05-11
Publication date: 2023-12-26
Also published as: WO2022236716A1

Abstract

The present disclosure presents apparatus, methods and systems that allow a communication system of a communication node and a User Equipment (UE) to select a Channel Occupation Time (COT) initiator, using a communication node Fixed Frame Period (FFP) or UE FFP, to address a 3gpp REL 17 work item RP-210854 with communication node configuration parameters, one or more UE processing time capability parameters, and other parameters. The UE may determine whether the initial timing, the default timing, or the modified timing is applicable to data transmission from the UE to the communication node. In some aspects, the UE may calculate whether the start of the UE FFP is offset from the start of the communication node FFP by a specified number of symbols. The UE may determine which transmission FFP to utilize and the timing of the utilization.

Description

Channel occupancy time initiator determination in a frame-based device scene

Technical Field

The present application relates generally to user equipment uplink data transmission and, more particularly, to selecting a channel occupation time initiator.

Background

In a communication system having a User Equipment (UE) and a communication node, when using a frame-based device, the UE typically utilizes a semi-static Fixed Frame Period (FFP) to transmit data. For example, the transmission may begin at the beginning of the FFP. The communication node indicates its FFP configuration to the UE through SIB1 or dedicated signaling. The FFP configuration parameters are limited to a set of timing values. The UE may transmit in the Uplink (UL) after detecting the Downlink (DL) from the communication node. The UE is allowed to transmit within a Channel Occupation Time (COT) initiated by the communication node. It would be beneficial to allow more flexibility in the communication system to select the following devices: the device selects an FFP and the device initiates the FFP for use by the UE.

Disclosure of Invention

In a first example embodiment, an apparatus is disclosed. A first example embodiment includes (1) one or more processors, and (2) a memory storing instructions and data that, when executed by the one or more processors, cause the apparatus to: (1) sending a processing time capability parameter of a User Equipment (UE) to a communication node, (2) calculating a length and an offset of at least one of a plurality of FFPs using a Fixed Frame Period (FFP) configuration received from the communication node, and (3) selecting a Channel Occupation Time (COT) initiator for transmission at a time of data transmission in an Uplink (UL), wherein one of the FFPs of the plurality of FFPs is selected as a transmission FFP using the processing time capability parameter, an FFP configuration from the plurality of FFPs, and a processing parameter, wherein the processing parameter is a number of symbols, and the plurality of FFPs includes the UE FFP and the communication node FFP.

In a second example embodiment, an apparatus is disclosed. A second example embodiment includes (1) one or more processors, and (2) a memory storing instructions and data that, when executed by the one or more processors, cause the apparatus to: (1) receive processing time capability parameters of one or more User Equipments (UEs), (2) determine, for each of the one or more UEs, a respective time at which UE transmissions begin, and (3) determine a time at which a communication node Fixed Frame Period (FFP) begins, and one or more processing parameters, wherein the one or more processing parameters are generated using the one or more processing time capability parameters.

In a third example embodiment, a method is disclosed. A third example embodiment includes (1) sending a processing time capability parameter of a UE to a communication node, (2) calculating a length and an offset of at least one FFP of a plurality of FFPs using an FFP configuration received from the communication node, (2) a time of data transmission in UL, selecting a COT initiator for the transmission, wherein one FFP of the plurality of FFPs is selected as a transmission FFP using the processing time capability parameter, the FFP configuration using the plurality of FFPs, and a processing parameter, wherein the processing parameter is a number of symbols, and the plurality of FFPs includes the UE FFP and the communication node FFP.

In a fourth example embodiment, a system is disclosed. A fourth example embodiment includes (1) a communication node capable of transceiving communications and determining an FFP configuration using a received UE processing time capability parameter, and (2) a UE capable of transceiving communications with the communication node, transmitting a particular UE processing time capability parameter, determining a COT initiator for a transmission using a transmission FFP selected using the UE processing time capability parameter, the FFP configuration, and the UE processing time parameter, wherein the transmission FFP is one of a UE FFP or a communication node FFP.

Drawings

Reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

fig. 1 is a schematic diagram of an example communication scenario with a Radio Access Network (RAN) and a plurality of User Equipments (UEs);

fig. 2A is a schematic diagram of an example table of PDSCH decoding times;

fig. 2B is a schematic diagram of an example table of PDSCH processing times;

fig. 2C is a schematic diagram of a PUSCH preparation time example table for capability 1;

fig. 2D is a schematic diagram of a PUSCH preparation time example table for capability 2;

fig. 3 is a flow chart of an example method of determining a transmission Fixed Frame Period (FFP);

FIG. 4 is a schematic illustration of a communication scenario using modified timing;

FIG. 5 is a schematic diagram of an example communication scheme using FFP-K2 parameters;

fig. 6 is a block diagram of an example communication system using a transmission FFP; and

fig. 7 is an example block diagram of an FFP controller according to the principles of the present disclosure.

Detailed Description

In the 5G third generation partnership project (3 GPP) Release 17 proposed standard, there is one work item (RP-210854), titled "Enhanced Industrial Internet of Things (IoT) and ultra-reliable and low latency communication (URLLC) support for NR", for implementing a User Equipment (UE) initiated Channel Occupation Time (COT). The UE may be capable of transceiving communications, e.g., transmitting and receiving communications, with one or more communication nodes.

UEs, such as mobile phones, tablets, laptops, and other 5G devices, whether mobile, or stationary, may establish a communication link with one or more network devices (i.e., communication nodes). For example, the various communication nodes may be Radio Access Networks (RANs), such as 5G base stations (gnbs), evolved Universal Mobile Telecommunications Systems (UMTS), terrestrial radio access (E-UTRA), enhanced 4G eNodeB E-UTRA base stations (enbs), such as enhanced node bs, enhanced gnbs (en-gnbs), or next generation enbs (ng-enbs).

One allowed channel access mechanism is a frame-based device (FBE) when operating in the 5GHz unlicensed spectrum. In 3GPP Rel-16 NR-U, the corresponding channel access mechanism is specified as a semi-static channel occupancy mode.

Channel access using FBE is based on the definition of a Fixed Frame Period (FFP). FFP may be in the range of 1 millisecond (ms) to 10 ms. The transmission may begin at the beginning of the FFP. The device may change its FFP every 200 ms. The timing of the FFP is therefore semi-static in nature. Immediately prior to starting transmission on the working channel at the beginning of the FFP, the initiating device may perform a Clear Channel Assessment (CCA) check during a single observation slot. An operating channel may be considered occupied if the energy level in the channel exceeds an energy detection threshold level. If the initiating device finds that the working channel is idle (clear), it can transmit immediately. If the initiating device finds that the working channel is occupied, there should not be any transmission on that channel during the next FFP. A responding device that receives a transmission grant (grant) from an associated originating device may continue transmitting on the current operating channel: a) If the transmission is initiated within at most 16 microseconds (mus) after the last transmission by the initiating device, no CCA need be performed; b) After performing CCA on the working channel during a single observation time slot (e.g., 9 mus) within a 25 mus period ending immediately before the authorized transmission time.

Rel-16 (TS 37.213, section 4.3) of the 3GPP specifications specifies that the communication node indicates its FFP configuration to the UE through SIB1 or dedicated RRC signaling. The communication node FFP duration values are limited to a set of {1ms,2ms,2.5ms,4ms,5ms,10ms } including idle periods. The idle period of a given SCS is equal to (minimum idle period allowed by regulations/Ts) rounded up (ceil), where the minimum idle period allowed by regulations is equal to the larger of 5% and 100 μs of FFP, and Ts is the symbol duration of a given subcarrier spacing (SCS). The UE may transmit in the Uplink (UL) after detecting a Downlink (DL) transmission from the communication node (e.g., detecting the presence of the communication node COT). The UE cannot initiate its own COT. The UE is allowed to transmit within the COT initiated by the communication node. To overcome these limitations, support for FBE by UE-initiated COT is introduced in Rel-17 in 3GPP work item RP-210854.

Determination of the COT initiator depends on detection of the communication node transmission by the UE. The detected DL transmission may mean that the communication node has initiated a COT and thus the UE may transmit as a responding device within such a COT. Detecting DL transmissions by a UE may take time. There is currently no processing time requirement set for the UE to detect DL COT. In the related art, NR REL-15 has specified UE processing time for PDSCH processing and PUSCH preparation (see fig. 2A, 2B, 2C, and 2D).

The NR supports two processing functions related to decoding and hybrid automatic repeat request (HARQ) Acknowledgement (ACK) (HARQ-ACK) feedback timing (see 3gpp 38.214, section 5.3), a baseline function, and advanced functions of low latency use cases. Advanced functions may implement HARQ feedback after a few symbols.

When operating in accordance with semi-static channel access, it is important for the communication node and UE to know which has initiated or should initiate the COT for a given transmission, e.g., the channel access type and the length of the cyclic prefix extension may depend on the COT initiator (UE or communication node). In some example embodiments, the cyclic prefix extension may be omitted. If the UE is a COT initiator, the UE may be allowed to transmit during the communication node idle period. The UE may not transmit if the UE shares the communication node initiated COT. The transmission time may depend on the COT initiator.

For dynamically scheduled UL transmissions, the desired communication node indicates to the UE whether the UE should initiate FFP. When the UL transmission occurs within the same communication node FFP as the communication node FFP that sent the dynamic scheduling grant, the communication node may indicate that the UE is not to initiate FFP. Otherwise, the communication node may instruct the UE to start UE FFP. For semi-static UL transmissions, the UE may initiate UE FFP by default unless it knows that the transmission will occur within the communication node COT. The UE may determine this using blind detection of a Synchronization Signal Block (SSB) or by decoding COT structure signaling in a Group Common (GC) Physical Downlink Control Channel (PDCCH).

SSB blind detection and GC-PDCCH decoding may require processing time. Shortly after the start of the communication node FFP, the UE may not know whether the communication node has initiated COT. The UE needs to know when it can start transmitting during the first symbol of the communication node FFP, but it may not know if the communication node initiated COT.

The periodicity of the semi-static UL transmissions may be different from the periodicity of the communication node FFP, which may be a fraction of the communication node FFP periodicity. Thus, without further rules, the UE behavior cannot be part of the resource configuration. Furthermore, it is beneficial to remove the restrictions of the semi-static UL resource configurations so that they can overlap with the first symbol of the communication node FFP, thereby removing unnecessary restrictions in the resource configurations, thereby reducing e.g. multiplexing capacity and efficiency of the system.

A problem may occur with Physical Uplink Shared Channel (PUSCH) scheduling within the same communication node in which the COT is initiated in the FFP, i.e. the UE receives the UL grant and transmits the corresponding PUSCH within the same communication node that obtained the COT, e.g. intra-FFP PUSCH scheduling. For continuous transmission, each COT needs to contain a DL portion of minimum length (e.g., symbol count) to allow enough time for PUSCH preparation. When there are few UEs serving in the cell of the communication node, there may not be enough DL data to be transmitted for the required DL portion. The communication node may need to send a reservation (reservation) signal or leave the channel unused. If there is a transmission interval (gap) of more than 16 mus between DL and UL transmissions, the UE may need to perform a new Clear Channel Assessment (CCA) prior to transmission. Thus, two successful CCA's may be required before the UE can transmit PUSCH, one performed by the communication node and the other performed by the UE. This may increase the probability that another device may occupy the channel between DL (PDCCH) and UL (PUSCH) transmissions.

PUSCH scheduling across FFPs, e.g., scheduling PUSCH during communication node initiated COT, prior to communication node initiated COT during which PUSCH is expected to occur, may improve this situation, as PUSCH preparation or a portion thereof may occur during the previous scheduled COT and idle periods. Cross FFP scheduling within a communication node FFP may require that the communication node be able to access and initiate the next COT.

The present disclosure proposes a solution that enables use of multiple COT initiators (e.g., communication node FFP and UE FFP) to obtain channel access for PUSCH or Physical Uplink Control Channel (PUCCH) scheduled for the same cross FFP or for semi-statically scheduled UL transmissions, such as configured grant PUSCH, periodic or semi-persistent Channel State Information (CSI), scheduling request, or Physical Random Access Channel (PRACH). The disclosed solution may utilize processing parameters of a UE to determine the COT initiator of transmissions that may be scheduled outside a given communication node FFP. The disclosed solution may be represented, for example, by a pseudo code of algorithm 1.

Algorithm 1: example pseudocode for an aspect of the disclosed solution:

where UE-TX-start is the corresponding time at which UE transmission on UL starts (e.g. data transmission),

communication-node-FFP-start is the time when communication node FFP starts, and

d is a processing parameter of the UE and may be expressed in terms of time or number of symbols.

When the difference between UE-TX-start and communication-node-FFP-start is less than D, the communication node may configure via higher layer signaling (e.g., radio Resource Control (RRC) messages) whether UL transmissions are allowed to be sent on semi-static UL resources in the communication node FFP. D can be defined in a number of ways. D may be UE processing capability plus transmission time of DL signals (e.g., PDCCH, SSB, and other DL signals). Since the conventional processing time is generally defined from the end of the PDCCH or PDSCH transmission or the last symbol, such adjustment may take into account the time required to transmit the signal in the DL, e.g., the processing time and the transmission time of the signal. In some aspects, D may utilize the reported UE capabilities, e.g., through received assistance information. In some aspects, D may be different for communication node COT detection using DCI, SSB, or reference signals. In some aspects, D may be determined using a transmission time of the DCI, SSB, or reference signal relative to a time at which the communication node FFP starts and a UE processing capability of the DCI, SSB, or reference signal.

In some aspects, D may be the same as a Physical Downlink Shared Channel (PDSCH) processing time capability parameter, e.g., in some aspects, the processing parameter may be the same as the processing time capability parameter. The processing time capability parameter may be received from the UE from a system information signal (e.g., assistance information). In some aspects, D may be determined using a worst, e.g., slowest, PDSCH processing time capability parameter among UEs within a cell of the communication node.

In some aspects, if the communication node COT detection utilizes SSB or reference signals, D may correspond to the second column of table 5.3-1 of 3gpp 38.214 (see fig. 2A). In some aspects, if the communication node COT detection utilizes PDCCH, D may correspond to the third column of table 5.3-1 of 3gpp 38.214 (see fig. 2A). In some aspects, communication node COT detection with SSB may follow UE processing capability 1 of 3 GPP. In some aspects, communication node COT detection with PDCCH may follow UE processing capability 2 of 3 GPP.

In some aspects, a determination of PUSCH timing may be made such that initial dynamic or semi-static scheduling of UL grant timing may be maintained if PUSCH may be transmitted within the COT of the communication node FFP. Otherwise, if UE FFP is used for PUSCH, PUSCH timing may be modified to align with the start of UE FFP.

The determination of PUSCH timing may be further refined because the UE and the communication node may use the described algorithm to determine PUSCH timing when the UE receives a UL grant in the COT within the communication node ffp#n. If the DCI indicates PUSCH transmission within the COT of the communication node ffp#n, the UE may follow the initial UL timing indicated in the DCI, i.e., legacy behavior.

If the DCI indicates PUSCH within the COT of a communication node ffp#n+1 (e.g., a subsequent FFP), then if the UE detects a DL signal at the beginning of the communication node ffp#n+1, e.g., the UE detects data transmission at the beginning of the communication node FFP, where the UE may verify the presence of the communication node ffp#n+1 using algorithm 1. The UE may follow the initial UL timing indicated in the DCI.

If the UE fails to detect a DL signal at the beginning of the communication node ffp#n+1, e.g., there is no DL signal or the UE does not have enough processing time to detect, and the scheduling Downlink Control Information (DCI) or RRC indicates that the UE FFP is allowed, the UE may transmit with the UE FFP. The UE may modify PUSCH transmission timing to correspond to the start of the UE FFP.

In some aspects, UE FFP may be indicated in the scheduling DCI. In some aspects, the UE FFP may be the next FFP or FFP within the communication node ffp#n+1 with the start time closest to the initial PUSCH timing. In some aspects, the UE FFP may be a first UE FFP within the communication node ffp#n+1 that satisfies the UE processing time. In some aspects, a UE may attempt channel access in N (N > 1) consecutive UE FFPs, with a first UE FFP determined by the previously described aspects.

For demonstration purposes, table 1 shows an example of messaging modification of the 3GPP standard. Other messaging changes and different messaging changes may be utilized to implement the present disclosure; take table 1 as an example.

Table 1: message passing examples supporting dynamic transport FFP

A summary of some of the definitions used in this disclosure is provided herein. The communication node or UE may initiate a COT at the beginning of the communication node FFP or UE FFP, respectively. The communication node FFP may follow a 3gpp REL 16 definition for duration, e.g., 1ms, 2ms, 2.5ms, 4ms, 5ms, or 10ms, as indicated in System Information (SI). The start position is determined relative to the radio frame as defined in TS 37.213: "starting position of FFP within every two radio frames starts from an even radio frame and is given by i x P, where i= {0,1,..20/P-1 }, where P is a fixed frame period in ms).

The UE FFP duration and start position may be configured by SI or RRC. The UE FFP start position may be relative to a radio frame, a communication node FFP, or other signals. The UE FFP duration may be shorter than the communication node FFP such that the communication node FFP duration is a multiple of the UE FFP duration. The UE FFP may have the same duration as the communication node FFP, or a longer duration. The UE FFP may be numbered, e.g., for DCI indication, starting from a first UE FFP that partially overlaps with the communication node FFP #n+1. Alternatively, the numbering may start from the first UE FFP starting within the communication node ffp#n+1.

The disclosed solution may provide a number of advantages. For example, the disclosed solution may improve cross FFP scheduling, which may reduce the duration of the minimum DL resources required at the beginning of the communication node COT and may increase the flexibility of selecting the DL/UL ratio. The disclosed solution may improve the use of semi-statically configured UL resources. Since the UE behaviour during the first D symbols of the communication node FFP is known and can be controlled by the communication node, there is no need to avoid occasional overlapping of those symbols on the semi-static UL resource configuration. The disclosed solution may allow for using the communication node FFP and the UE FFP to increase the channel access probability, as channel access may be attempted at different time instances. Semi-static configuration, such as semi-static scheduling, may be adjusted for cyclic prefix extension. In some example embodiments, the cyclic prefix extension may be omitted.

Turning now to the drawings. Fig. 1 is a schematic diagram of an example communication scenario 100 with a RAN and multiple UEs. The communication scenario 100 is a presentation of one type of environment of the present disclosure. The environment of communication scenario 100 includes UE 110a, UE 110b, UE 110c (collectively referred to as UE 110), and RAN 120. Fewer or more UEs may be present in UE 110. RAN 120 may be a gNB or other type of communication node.

An example set of messages is shown in the communication scenario 100. At the registration time of UE 110a, UE 110a sends message 130a to RAN 120. Message 130a may include one or more UE parameters, such as a UE processing time capability parameter. Likewise, UE 110b may send its UE parameters via message 130b and UE 110c may send its UE parameters via message 130c (collectively referred to as message 130). Message 130 may be an RRC message, for example, when communicating with RAN 120.

In some aspects, RAN 120 may determine a RAN configuration, such as a communication node FFP configuration, used by UEs in UE 110. The RAN configuration may be transmitted to UE 110 using message 140a for UE 110a, message 140b for 110b, and message 140c for 110c (collectively referred to as message 140), e.g., using a system information signal, an RRC release signal, an RRC reconfiguration (rrcrecon configuration) signal, or a DCI signal. In some aspects, message 140 may be targeted to each respective UE of UEs 110, where message 140 specifies a respective RAN configuration for the respective UE 110. In some aspects, message 140 may be broadcast to UE 110.

At the time of data transmission via UL from one of the UEs of UE 110 (e.g., UE 110 a), UE 110a may determine a COT initiator, e.g., a transmission FFP to utilize, e.g., UE 110a FFP or a communication node FFP. UE 110a may then transmit a data transmission, such as shown by signal 150a, using the selected transmission FFP.

Fig. 2A is a schematic diagram of an example table 201 of PDSCH decoding times. Table 201 shows tables 5.3-1"PDSCH processing time for PDSCH processing capability 1 of the 3GPP standards. The values shown in the table may be used as default, initial, or example timing in a scenario where UE FFP is being used and modified timing is allowed, e.g., parameters of UE PDSCH processing capability 1.

Fig. 2B is a schematic diagram of an example table 202 of PDSCH processing times. Table 202 shows tables 5.3-2"PDSCH processing time for PDSCH processing capability 2 of the 3GPP standards. The values shown in the table may be used as default, initial, or example timing in a scenario where UE FFP is being used and modified timing is allowed, e.g., parameters of UE PDSCH processing capability 2.

Fig. 2C is a schematic diagram of an example table 203 of PUSCH preparation times for capability 1. Table 203 shows tables 6.4-1"PUSCH preparation time for PUSCH timing capability 1 of the 3GPP standards. The values shown in the table may be used as default, initial, or example timings in a scenario where the UE FFP is used and modified timing is allowed.

Fig. 2D is a schematic diagram of an example table 204 of PUSCH preparation times for capability 2. Table 204 shows tables 6.4-2"PUSCH preparation time for PUSCH timing capability 2 of the 3GPP standards. The values shown in the table may be used as default, initial, or example timings in a scenario where the UE FFP is used and modified timing is allowed.

Fig. 3 is an illustration of a flowchart of an example method 300 of determining a transmission FFP. The method 300 may be performed by a UE, a communication node, or both. In some aspects, the UE processing time capability parameter may be received by the communication node from more than one UE within a cell of the communication node. Method 300 may be performed, for example, in whole or in part by communication scenario 100 of fig. 1, by communication system 600 of fig. 6, or by FFP controller 700 of fig. 7.

The method 300 starts at step 305 and proceeds to step 310. In step 310, the UE may report its processing time capability parameters, such as what D values the UE supports, to the communication node. In step 315, the UE may determine the timing, e.g., length (e.g., symbol count) and offset, of the communication node FFP and the UE FFP using configuration information received, e.g., from system information, DCI, or RRC reconfiguration (rrcrecnonconfiguration) signals. .

In step 320, the UE may determine a need to transmit data or control signals in the UL. The determination may utilize received information, such as UL grants or DL assignments (assignments) requiring transmission of HARQ acknowledgements, configurations for periodic or semi-persistent UL transmissions, or a determination that such transmissions should be made.

In decision step 325, the following determination may be made using the processing time capability parameter or the processing parameter: whether UL data transmission will occur inside or outside the communication node COT. This may involve determining whether the start of UL transmission is less than D symbols (or other parameters, such as time) late from the start of the communication node FFP. If the result is "Yes," the method 300 proceeds to decision step 330. If the result is "NO," the method 300 proceeds to decision 335.

In decision step 330, a determination is made as to whether UL transmission is enabled in the communication node FFP. If the result is "yes," the method 300 proceeds to step 345. If the result is "NO," the method 300 proceeds to step 340.

In decision step 335, a determination is made regarding: whether the UE detects a data transmission from the communication node at the beginning of the communication node FFP. If the result is "yes," the method 300 proceeds to step 350. If the result is "NO," the method 300 proceeds to step 345.

In step 340, the UE should discard the UL transmission if the UL transmission is not allowed to overlap with the first D symbols or times of the communication node FFP. The method 300 proceeds to step 395. In step 345, the UE attempts to initiate a UE FFP and, if successful, transmits an UL signal. The UE may select the default, initial or modified timing or be directed by the communication node to select the default, initial or modified timing. The method 300 proceeds to step 395. In step 350, the UE sends UL transmissions with the indicated timing. The method 300 proceeds to step 395. In step 395, the method 300 ends.

Fig. 4 is a schematic diagram of an example communication scenario 400 using modified timing. The UE receives PUSCH scheduled for the next communication node ffp#n+1 (see element 410). At the beginning of communication node ffp#n+1, the UE verifies that communication node FFP is present considering processing time D and detects that communication node COT is not present (see element 415). When the scheduling DCI (or RRC message) indicates that the UE FFP is allowed, the UE determines whether the Tx timing needs to be modified to align with the start of the UE FFP (see element 420). In this example, the DCI is equipped with a UE FFP indicator that facilitates Tx timing modification. The UE FFP indicator in the DCI indicates that the third UE FFP overlaps with the communication node ffp#n+1 (see element 425), e.g., the COT of the communication node FFP subsequent to the current communication node FFP is detected or not detected by the UE. The UE may modify PUSCH transmission timing to correspond to the start of the UE's third FFP (see element 430).

It may be beneficial to offset the communication node FFP and the UE FFP. When the start of the UE FFP is delayed relative to the start of the communication node FFP, the UE detects that the communication node FFP is not initiated at the end of D symbols or times, the UE may initiate the UE FFP with a short delay, such as without waiting for the start of the next UE FFP. The time offset between the communication node FFP and the UE FFP start time means that the UE may need to modify the Tx timing.

Fig. 5 is a schematic diagram of an example communication scenario 500 using FFP-K2 parameters. In some aspects, the UE FFP indicator in the UL grant may be implemented as FFP-K2, e.g., FFP-K2 may be an FFP offset. Instead of a single K2 value, the UL grant includes an additional K2 value dedicated to UE FFP initiation, where the K2 value indicates the time interval between UL grant reception and PUSCH transmission (see element 510). If the UE fails to detect the presence of COT in communication node ffp#n+1, the UE may utilize the secondary FFP-K2 (see FFP offset 520) to determine PUSCH timing, e.g., the value of DCI-to-PUSCH timing in UL grant.

This approach may be advantageous because it indicates the timing offset as an absolute number of slots. When the communication node knows the UE FFP offset and duration, the communication node can utilize the UE FFP offset and duration to select the FFP-K2 value. To the extent that the communication node has knowledge of an error, e.g., an outdated UE FFP offset and duration, the UE may detect the error and not transmit PUSCH on the UE FFP. With the UE FFP indicator, in case such an error occurs, the UE may transmit PUSCH at the wrong time. In aspects where UE FFP is used for dynamically scheduled PUSCH and not for configured UL Tx, the communication node may dynamically select an FFP offset for the UE within 200ms of upcoming and signal the UE FFP offset with FFP-K2. The FFP-K2 value may be independently configured, separate from the conventional K2 value.

The communication node 530 knows that the FFP 535 of the UE is offset by two slots and of the same duration, which indicates k2=6 (see FFP offset 540) to place the UL transmission at the end of the communication node FFP. When the UE does not detect a DL signal in the first slot communication node FFP m+1 545, the UE attempts to transmit in PUSCH timing provided by K2-FFP (see FFP offset 520) in UL grant.

Fig. 6 is an illustration of a block diagram of an example communication system 600 that utilizes transmission FFP. Communication system 600 is an example system and may have additional communication nodes and additional UEs. Communication system 600 may implement the disclosed solution, e.g., method 300 of fig. 3, and implement FFP controller 700 of fig. 7. The communication system 600 has a UE 610 and a communication node 630 (shown as a RAN in this example).

The UE 610 has a transceiver 620 capable of receiving communication signals and transmitting communication signals with the communication node 630 using a signal connection 680, e.g. transmitting UE processing time capability parameters, PUSCH, or receiving FFP configuration information, e.g. using DCI or RRC reconfiguration (rrcrecon configuration) signals. UE 610 has a UE FFP processor 625 that may determine whether UE 610 may initiate COT or use COT initiated from communication node 630, e.g., with communication node FFP or UE FFP for UL data transmission to communication node 630.

The communication node 630 has a transceiver 640 that is capable of receiving communication signals and transmitting communication signals with the UE 610 using a signal connection 680. Communication node 630 has an FFP configurator 645, which FFP configurator 645 is capable of analyzing received UE processing time capability parameters, e.g., received from UE 610. FFP configurator 645 is capable of determining the configuration of communication nodes FFP and UE FFP, e.g., allowing UE FFP, allowing modified timing and other configuration parameters, e.g., the algorithm described in method 300 of fig. 3. Communication node 630 may transmit the FFP configuration to UE 610 using, for example, a system information signal, an RRC signal, DCI, or other signal.

Elements of UE 610 and communication node 630 are shown as functional views, where they may be implemented in software, hardware, or a combination thereof. In some aspects, the functionality shown may be combined with other functionalities of the corresponding UE 610 or communication node 630.

Fig. 7 is an illustration of a block diagram of an example of an FFP controller 700 in accordance with the principles of the present disclosure. FFP controller 700 may be stored on a single computer or on multiple computers. The various components of FFP controller 700 may communicate via a wireless or wired conventional connection. A portion or the entirety of FFP controller 700 may be located as part of a RAN, and other portions of FFP controller 700 may be located as part of a UE in communication with the RAN. FFP controller 700 may be virtual or partially virtual while hosted on another system or process.

FFP controller 700 may be configured to perform various functions disclosed herein, including receiving communication node FFP configuration parameters. The various functions performed may be the performance of the methods and processes described herein, such as the method 300 of fig. 3. FFP controller 700 may implement communication system 600 of fig. 6. FFP controller 700 includes a communication interface 710, a memory 720, and a processor 730.

The communication interface 710 is configured to transmit and receive data. For example, communication interface 710 may receive communication node configuration parameters, such as K2 parameters (FFP offset), whether UE FFP is allowed, whether modified timing is allowed, and other configuration parameters, from the communication node. Communication interface 710 may send the selected transmission FFP, timing, other generated results, and data transmissions. The timing may be a modified timing, an initial timing, or a default timing. The communication interface 710 may communicate through a communication system used in the industry. For example, a wireless or wired protocol may be used. The communication interface 710 is capable of performing the operations as described by the transceiver 620 of fig. 6.

Memory 720 may be configured to store a series of operational instructions, such as stored instructions that upon initiation direct the operation of processor 730, including code representing algorithms for determining the COT initiator, transmitting FFPs, and data, parameters, and other information. Memory 720 is a non-transitory computer-readable medium. Multiple types of memory may be used for data storage and memory 720 may be distributed.

Processor 730 may be configured to determine and select a transmission FFP using the received configuration information. For example, processor 730 may perform an analysis to determine whether the transmission FFP is a communication node FFP or a UE FFP and whether to use modified, default, or initial timing. Processor 730 may be configured to direct the operation of FFP controller 700. Processor 730 includes logic for communicating with communication interface 710 and memory 720 and performing the functions described herein to determine a transmission FFP. Processor 730 is capable of performing or directing operations as described by FFP configurator 645 of fig. 6.

Portions of the above described apparatus, systems, or methods may be embodied in or executed by various analog or digital data processors, where the processors are programmed or store an executable program of software instruction sequences to perform one or more of the following steps: the method. The processor may be, for example, a programmable logic device such as a Programmable Array Logic (PAL), a general purpose array logic (GAL), a Field Programmable Gate Array (FPGA), or another type of Computer Processing Device (CPD). The software instructions of such programs may represent algorithms and be encoded on non-transitory digital data storage media, such as magnetic or optical disks, random Access Memory (RAM), magnetic hard disks, flash memory, and/or read-only memory (ROM), in a machine-executable form, to enable various types of digital data processors or machines to perform one, more, or all of the steps of one or more of the methods, functions, systems, or devices described herein.

Portions of the disclosed examples or embodiments may relate to a computer storage product with a non-transitory computer-readable medium that has program code thereon for performing various computer-implemented operations that embody a portion of an apparatus, device, or perform steps of a method set forth herein. Non-transitory as used herein refers to all computer readable media except for transitory propagating signals. Examples of non-transitory computer readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROM disks; magneto-optical media such as floppy disks; hardware devices such as ROM and RAM devices that are dedicated to storing and executing program code. Examples of program code include machine code, such as produced by a compiler, and files containing higher level code that may be executed by the computer using an interpreter.

In interpreting the disclosure, all terms should be interpreted in the broadest possible manner consistent with the context. In particular, the terms "comprises" and "comprising" should be interpreted as referring to elements, components, or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present, or utilized, or combined with other elements, components, or steps that are not expressly referenced.

Those skilled in the art to which the present application relates will appreciate that other and further additions, deletions, substitutions and modifications may be made to the described embodiments. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to be limiting, since the scope of the present disclosure will be limited only by the appended claims. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. Although any methods and materials similar or equivalent to those described herein can also be used in the practice or testing of the present disclosure, a limited number of exemplary methods and materials are described herein.

Each of the aspects described in the summary section may incorporate one or more of the following additional elements.

Element 1: wherein the instructions further cause the apparatus to transmit a data transmission to the communication node using the transmission FFP.

Element 2: when the first start of the data transmission in the UL is less than the processing parameter from the second start of the communication node FFP, the UE will discard the data transmission in the UL and the first start of the data transmission is later than the second start of the communication node FFP and the UL is not allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length equal to the symbol count of the processing parameter.

Element 3: wherein the selecting the COT initiator is for selecting the UE FPP as the transmission FPP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length equal to a symbol count of the processing parameter.

Element 4: wherein the selecting the COT initiator is for selecting the UE FPP as the transmission FPP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the UE utilizes dynamic scheduling of the data transmission, or semi-static scheduling of the data transmission and a configuration from the communication node, wherein the configuration from the communication node indicates the UE FPP.

Element 5: wherein the selecting the COT initiator is for selecting the communication node FFP as the transmission FFP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the first data transmission is later than the second start of the communication node FFP, and the UE detects a second data transmission from the communication node FFP at the second start of the communication node FFP.

Element 6: wherein the selecting the COT initiator is for selecting the UE FPP as the transmission FPP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UE does not detect the communication node FFP.

Element 7: wherein the UE determines the first start of the data transmission using one of the modified timing, the initial timing, or a default timing.

Element 8: wherein the initial time comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission.

Element 9: the modified timing includes: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission, wherein cyclic prefix extension is omitted.

Element 10: wherein the modified timing includes a UE FFP offset, the UE does not detect a COT of a next communication node FFP of the communication node FFP, and the UE utilizes the UE FFP offset to determine a Physical Uplink Shared Channel (PUSCH) timing.

Element 11: wherein the UE is a first UE, more than one UE sends their respective processing time capability parameters to the communication node, and the communication node utilizes the respective processing time capability parameters to determine the FFP configuration.

Element 12: wherein the communication node is one of: a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).

Element 13: wherein the transmission FFP is further determined using a scheduling type, wherein the scheduling type is one of semi-static scheduling or dynamic scheduling.

Element 14: wherein a time of UE transmission start indicated by the communication node in UL grant or in semi-static configuration is maintained when the transmission FFP is the communication node FFP, and PUSCH is transmitted within the COT of the communication node FFP.

Element 15: wherein PUSCH transmissions are aligned with a start of the transmission FFP, wherein the transmission FFP is the UE FFP.

Element 16: wherein the processing parameters are determined using at least one of: processing time, and transmission of one of Downlink Control Information (DCI), a Synchronization Signal Block (SSB), a reference signal, or a Physical Downlink Shared Channel (PDSCH).

Element 17: wherein the processing parameters are determined by the communication node according to a slowest PDSCH processing time from a group of UEs among which the group of UEs has registered with the communication node.

Element 18: wherein the processing parameter is determined according to one of: third generation partnership project (3 GPP) technical standard 38.214 table 5.3-1, second column, and the COT detection of the communication node utilizes SSB or reference signals; the 3GPP technical standard 38.214, column three of table 5.3-1, and the COT detection of the communication node utilizes a Physical Downlink Control Channel (PDCCH); parameters of UE PDSCH processing capability 1, and the COT detection of the communication node utilizes SSB; or parameters of UE PDSCH processing capability 2, and the COT detection of the communication node utilizes PDCCH.

Element 19: wherein the device is one of: a communication node, a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).

Element 20: wherein the instructions further cause the apparatus to: the one or more processing parameters and a time at which the communication node FFP starts are transmitted to the one or more UEs.

Element 21: wherein the instructions further cause the apparatus to: a transmission FFP to be utilized is indicated to the one or more UEs, wherein the transmission FFP is one of a respective UE FFP or the communication node FFP.

Element 22: wherein the one or more processing time capability parameters include: a Physical Downlink Shared Channel (PDSCH) processing time from the one or more UEs, and the one or more processing parameters are generated according to a slowest PDSCH processing time.

Element 23: wherein the one or more processing parameters are determined from at least one processing time and transmission of one of: reception capability from the one or more UEs; downlink Control Information (DCI) of the one or more UEs; a Synchronization Signal Block (SSB) of the one or more UEs; reference signals for the one or more UEs; third generation partnership project (3 GPP) technical standards 38.214 table 5.3-1 for the one or more UEs, wherein the communication node utilizes the SSB; a reference signal from the communication node; or a Physical Downlink Control Channel (PDCCH); processing capability 1 of the one or more UEs, wherein the communication node utilizes the SSB; or processing power 2 of the one or more UEs, wherein the communication node utilizes PDCCH.

Element 24: and transmitting the data transmission to the communication node by using the transmission FFP.

Element 25: wherein when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, the UE will discard the data transmission in the UL and the first start of the data transmission is later than the second start of the communication node FFP and the UL is not allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length equal to the processing parameter.

Element 26: wherein the selecting is for selecting the UE FFP as the transmission FFP for the UL when a first start of the data transmission of the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is allowed to overlap with the communication node FFP for a period of time starting at the second start and having a symbol count of length equal to the processing parameter.

Element 27: wherein the selecting is for selecting the UE FFP as the transmission FFP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the UE utilizes dynamic scheduling of the data transmission or the UE utilizes the data transmission semi-static scheduling and a configuration from the communication node, wherein the configuration from the communication node indicates the UE FPP.

Element 28: wherein the data transmission is a first data transmission and the selecting is for selecting the communication node FFP as the transmission FFP when a first start of the first data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the first data transmission is later than the second start of the communication node FFP, and the UE detects a second data transmission from the communication node FFP at the start of the communication node FFP.

Element 29: wherein the selecting is for selecting the UE FFP as the transmission FFP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UE does not detect the communication node FFP.

Element 30: wherein the UE determines the first start of the data transmission using one of the modified timing, the initial timing, or a default timing.

Element 31: wherein the initial timing includes: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission.

Element 32: wherein the modified timing comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission, wherein cyclic prefix extension is omitted.

Element 33: wherein the modified timing includes a UE FFP offset, the UE does not detect a COT of a next communication node FFP of the communication node FFP, and the UE utilizes the UE FFP offset to determine a Physical Uplink Shared Channel (PUSCH) timing.

Element 34: wherein the UE is a first UE, more than one UE sends their respective processing time capability parameters to the communication node, and the communication node determines the FFP configuration using the respective processing time capability parameters.

Element 35: wherein the transmission FFP is further determined using a scheduling type, wherein the scheduling type is one of semi-static scheduling or dynamic scheduling.

Element 36: wherein a time of UE transmission start indicated by the communication node in UL grant, or in semi-static configuration, is maintained when the transmission FFP is the communication node FFP, and PUSCH is transmitted within the COT of the communication node FFP.

Element 37: wherein PUSCH transmissions are aligned with a start of the transmission FFP, wherein the transmission FFP is the UE FFP.

Element 38: wherein the processing parameters are determined using at least one of: processing time, and transmission of one of Downlink Control Information (DCI), a Synchronization Signal Block (SSB), a reference signal, or a Physical Downlink Shared Channel (PDSCH).

Element 39: wherein the processing parameters are determined by the communication node according to a slowest PDSCH processing time from a group of UEs among which the group of UEs has registered with the communication node.

Element 40: wherein the transmission FFP is the UE FFP when: the specific UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is equal to or greater than a second start of the communication node FFP added to the UE processing time capability parameter, and a communication node COT is not detected by the UE.

Element 41: the transmission FFP is the UE FFP when: the particular UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is less than a second start of the communication node FFP added to the UE processing time parameter, and the UE utilizes dynamic scheduling or the UE utilizes a configuration from the communication node, wherein the configuration from the communication node indicates the UE FFP.

Element 42: wherein said transmission FFP is said communication node FFP when: the UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is equal to or greater than a second start of the communication node FFP added to the UE processing time parameter, and a communication node COT is detected by the UE.

Element 43: wherein said transmission FFP is said communication node FFP when: the UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is less than a second start of the communication node FFP added to the UE processing time parameter, the UE utilizes a semi-static configuration, and the configuration from the communication node indicates the communication node FFP.

Claims

1. An apparatus, comprising:

one or more processors; and

a memory storing instructions and data that, when executed by the one or more processors, cause the apparatus to:

transmitting a processing time capability parameter of a User Equipment (UE) to a communication node;

calculating a length and an offset of at least one of a plurality of FFPs using a Fixed Frame Period (FFP) configuration received from the communication node; and

A time of data transmission in an Uplink (UL), a Channel Occupation Time (COT) initiator for the transmission is selected, wherein one of the FFPs of the plurality of FFPs is selected as a transmission FFP using the processing time capability parameter, an FFP configuration from the plurality of FFPs, and a processing parameter, wherein the processing parameter is a number of symbols, and the plurality of FFPs includes a UE FFP and a communication node FFP.

2. The apparatus of claim 1, wherein the instructions further cause the apparatus to:

and transmitting the data transmission to the communication node by using the transmission FFP.

3. The apparatus of claim 1, wherein the UE is to discard the data transmission in the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is not allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length of a symbol count equal to the processing parameter.

4. The apparatus of claim 1, wherein the selecting the COT initiator is to select the UE FPP as the transmission FPP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length equal to a symbol count of the processing parameter.

5. The apparatus of claim 1, wherein the selecting the COT initiator is to select the UE FPP as the transmission FPP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the UE utilizes dynamic scheduling of the data transmission, or semi-static scheduling of the data transmission and a configuration from the communication node, wherein the configuration from the communication node indicates the UE FPP.

6. The apparatus of claim 1, wherein the selecting the COT initiator is to select the communication node FFP as the transmission FFP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the first data transmission is later than the second start of the communication node FFP, and the UE detects a second data transmission from the communication node at the second start of the communication node FFP.

7. The apparatus of claim 1, wherein the selecting the COT initiator is to select the UE FPP as the transmission FPP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UE does not detect the communication node FFP.

8. The apparatus of claim 7, wherein the UE determines the first start of the data transmission using one of a modified timing, an initial timing, or a default timing.

9. The apparatus of claim 8, wherein the initial timing comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission.

10. The apparatus of claim 8, wherein the modified timing comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission, wherein cyclic prefix extension is omitted.

11. The apparatus of claim 8, wherein the modified timing comprises a UE FFP offset, the UE does not detect a COT of a next communication node FFP of the communication node FFP, and the UE utilizes the UE FFP offset to determine a Physical Uplink Shared Channel (PUSCH) timing.

12. The apparatus of claim 1, wherein the UE is a first UE, more than one UE sends their respective processing time capability parameters to the communication node, and the communication node utilizes the respective processing time capability parameters to determine the FFP configuration.

13. The apparatus of claim 1, wherein the communication node is one of: a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).

14. The apparatus of claim 1, wherein the transmission FFP is further determined with a scheduling type, wherein the scheduling type is one of semi-static scheduling or dynamic scheduling.

15. The apparatus of claim 1, wherein a time of a UE transmission start indicated by the communication node in UL grant or in semi-static configuration is maintained when the transmission FFP is the communication node FFP, and PUSCH is transmitted within the COT of the communication node FFP.

16. The apparatus of claim 1, wherein PUSCH transmissions are aligned with a start of the transmission FFP, wherein the transmission FFP is the UE FFP.

17. The apparatus of claim 1, wherein the processing parameter is determined using at least one of: processing time, and transmission of one of Downlink Control Information (DCI), a Synchronization Signal Block (SSB), a reference signal, or a Physical Downlink Shared Channel (PDSCH).

18. The apparatus of claim 1, wherein the processing parameters are determined by the communication node according to a slowest PDSCH processing time from a group of UEs in which the UEs are registered and on which the group of UEs has registered.

19. The device of claim 1, wherein the processing parameter is determined according to one of: third generation partnership project (3 GPP) technical standard 38.214 table 5.3-1, second column, and the COT detection of the communication node utilizes SSB or reference signals; the 3GPP technical standard 38.214, column three of table 5.3-1, and the COT detection of the communication node utilizes a Physical Downlink Control Channel (PDCCH); parameters of UE PDSCH processing capability 1, and the COT detection of the communication node utilizes SSB; or parameters of UE PDSCH processing capability 2, and the COT detection of the communication node utilizes PDCCH.

20. An apparatus, comprising:

one or more processors; and

receiving one or more processing time capability parameters of one or more User Equipments (UEs);

Determining, for each of the one or more UEs, a respective time at which UE transmission begins; and

a time at which a communication node Fixed Frame Period (FFP) begins, and one or more processing parameters, wherein the one or more processing parameters are generated using the one or more processing time capability parameters, are determined.

21. The device of claim 20, wherein the device is one of: a communication node, a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).

22. The device of claim 20, wherein the instructions further cause the device to:

the one or more processing parameters and the time at which the communication node FFP starts are transmitted to the one or more UEs.

23. The device of claim 20, wherein the instructions further cause the device to:

a transmission FFP to be utilized is indicated to the one or more UEs, wherein the transmission FFP is one of a respective UE FFP or the communication node FFP.

24. The apparatus of claim 20, wherein the one or more processing time capability parameters comprise: a Physical Downlink Shared Channel (PDSCH) processing time from the one or more UEs, and the one or more processing parameters are generated according to a slowest PDSCH processing time.

25. The apparatus of claim 20, wherein the one or more processing parameters are determined from at least one processing time and transmission of one of: reception capability from the one or more UEs; downlink Control Information (DCI) of the one or more UEs; a Synchronization Signal Block (SSB) of the one or more UEs; reference signals for the one or more UEs; third generation partnership project (3 GPP) technical standards 38.214 table 5.3-1 for the one or more UEs, wherein the communication node utilizes the SSB; a reference signal from the communication node; or a Physical Downlink Control Channel (PDCCH); processing capability 1 of the one or more UEs, wherein the communication node utilizes the SSB; or processing power 2 of the one or more UEs, wherein the communication node utilizes PDCCH.

26. A method, comprising:

a time of data transmission in an Uplink (UL), a Channel Occupation Time (COT) initiator for transmission is selected, wherein one of the FFPs of the plurality of FFPs is selected as a transmission FFP with the processing time capability parameter, with the FFP configuration of the plurality of FFPs, and a processing parameter, wherein the processing parameter is a number of symbols, and the plurality of FFPs includes a UE FFP and a communication node FFP.

27. The method of claim 26, further comprising:

28. The method of claim 26, wherein the UE is to discard the data transmission in the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is not allowed to overlap with the communication node FFP for a period of time equal in length to the processing parameter starting at the second start.

29. The method of claim 26, wherein the selecting is for selecting the UE FFP as the transmission FFP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UL is allowed to overlap with the communication node FFP for a period of time starting at the second start and having a length equal to a symbol count of the processing parameter.

30. The method of claim 26, wherein the selecting is for selecting the UE FFP as the transmission FFP for the UL when a first start of the data transmission in the UL is less than the processing parameter from a second start of the communication node FFP, and the UE utilizes dynamic scheduling of the data transmission or semi-static scheduling of the data transmission and a configuration from the communication node, wherein the configuration from the communication node indicates the UE FPP.

31. The method of claim 26, wherein the data transmission is a first data transmission, and the selecting is for selecting the communication node FFP as the transmission FFP when a first start of the first data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the first data transmission is later than the second start of the communication node FFP, and the UE detects a second data transmission from the communication node FFP at the start of the communication node FFP.

32. The method of claim 26, wherein the selecting is for selecting the UE FFP as the transmission FFP when a first start of the data transmission in the UL is at least the processing parameter from a second start of the communication node FFP, and the first start of the data transmission is later than the second start of the communication node FFP, and the UE does not detect the communication node FFP.

33. The method of claim 32, wherein the UE determines the first start of the data transmission using one of a modified timing, an initial timing, or a default timing.

34. The method of claim 33, wherein the initial timing comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission.

35. The method of claim 33, wherein the modified timing comprises: transmission timing indicated in UL grant, or in semi-static configuration of the data transmission, wherein cyclic prefix extension is omitted.

36. The method of claim 33, wherein the modified timing comprises a UE FFP offset, the UE does not detect a COT of a next communication node FFP of the communication node FFP, and the UE utilizes the UE FFP offset to determine a Physical Uplink Shared Channel (PUSCH) timing.

37. The method of claim 26, wherein the UE is a first UE, more than one UE sends their respective processing time capability parameters to the communication node, and the communication node utilizes the respective processing time capability parameters to determine the FFP configuration.

38. The method of claim 26, wherein the communication node is one of: a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).

39. The method of claim 26, wherein the transmission FFP is further determined with a scheduling type, wherein the scheduling type is one of semi-static scheduling or dynamic scheduling.

40. The method of claim 26, wherein a time of a UE transmission start indicated by the communication node at UL grant, or in semi-static configuration, is maintained when the transmission FFP is the communication node FFP, and PUSCH is transmitted within the COT of the communication node FFP.

41. The method of claim 26, wherein PUSCH transmissions are aligned with a start of the transmission FFP, wherein the transmission FFP is the UE FFP.

42. The method of claim 26, wherein the processing parameters are determined using at least one of: processing time, and transmission of one of Downlink Control Information (DCI), a Synchronization Signal Block (SSB), a reference signal, or a Physical Downlink Shared Channel (PDSCH).

43. The method of claim 26, wherein the processing parameters are determined by the communication node according to a slowest PDSCH processing time from a group of UEs in which the UEs are registered and on which the group of UEs has registered.

44. The method of claim 26, wherein the processing parameter is determined according to one of: third generation partnership project (3 GPP) technical standard 38.214 table 5.3-1, second column, and the COT detection of the communication node utilizes SSB or reference signals; the 3GPP technical standard 38.214, column three of table 5.3-1, and the COT detection of the communication node utilizes a Physical Downlink Control Channel (PDCCH); parameters of UE PDSCH processing capability 1, and the COT detection of the communication node utilizes SSB; or parameters of UE PDSCH processing capability 2, and the COT detection of the communication node utilizes PDCCH.

45. A system, comprising:

a communication node capable of transceiving communications and determining a Fixed Frame Period (FFP) configuration using a received User Equipment (UE) processing time capability parameter; and

a UE capable of transceiving communications with the communication node, transmitting a particular UE processing time capability parameter, determining a Channel Occupation Time (COT) initiator for a transmission using a transmission FFP selected using the UE processing time capability parameter, the FFP configuration, and the UE processing time parameter of the UE, wherein the transmission FFP is one of a UE FFP or a communication node FFP.

46. The system of claim 45, wherein the transmission FFP is the UE FFP when: the specific UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is equal to or greater than a second start of the communication node FFP added to the UE processing time capability parameter, and a communication node COT is not detected by the UE.

47. The system of claim 45, wherein the transmission FFP is the UE FFP when: the particular UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is less than a second start of the communication node FFP added to the UE processing time parameter, and the UE utilizes dynamic scheduling or the UE utilizes a configuration from the communication node, wherein the configuration from the communication node indicates the UE FFP.

48. The system of claim 45, wherein the transmission FFP is the communication node FFP when: the UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is equal to or greater than a second start of the communication node FFP added to the UE processing time parameter, and a communication node COT is detected by the UE.

49. The system of claim 45, wherein the transmission FFP is the communication node FFP when: the UE processing time capability parameter is a symbol count, a first start of data transmission from the UE is less than a second start of the communication node FFP added to the UE processing time parameter, the UE utilizes a semi-static configuration, and the configuration from the communication node indicates the communication node FFP.

50. The system of claim 45, wherein the communication node is one of: a 5G base station (gNB), an evolved Universal Mobile Telecommunications System (UMTS), terrestrial radio access (E-UTRA), an enhanced 4G eNodeB E-UTRA base station (eNB), an enhanced gNB (en-gNB), or a next generation eNB (ng-eNB).