Method and apparatus for cot / ffp scheduling in unlicensed spectrum

Abstract

According to some embodiments, a method is performed by a wireless device for operating with shared spectrum channel access, where a first plurality of fixed frame periods (FFPs) is associated with the wireless device and a second plurality of fixed frame periods (FFPs) is associated with a network node, and where each FFP comprises an idle period without transmission and a channel occupancy time (COT) for potential transmission. The method comprises initiating a COT in one of the FFPs in the first plurality of FFPs, and transmitting uplink data from a start of the COT once the COT is successfully initiated.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to wireless communications, and more particularly to channel occupancy time (COT) / fixed frame period (FFP) scheduling in unlicensed spectrum. BACKGROUND

[0002] Generally, all terms used herein are to be interpreted according to their ordinary meaning in the technical field of the disclosure, unless explicitly given a different meaning in the present document and / or in the context of their use. All references to a / an / the item, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one and only one instance of the item, apparatus, component, means, step, etc., unless explicitly indicated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless explicitly specified and / or suggested in the present document. Any of the embodiments disclosed herein can be applied to any other embodiments, wherever technically feasible. Similarly, any advantages, features, or benefits of any of the embodiments disclosed herein can be applied to any of the other embodiments, and vice versa, wherever technically feasible. Further objects, features and advantages of the enclosed embodiments will be apparent from the following description.

[0003] Ultra-reliable and low-latency communications (URLLC) is one of the main use cases for the fifth generation (5G) New Radio (NR). URLLC has stringent requirements on transmission reliability and latency, i.e., 99.9999% reliability within 1 ms one-way latency. NR Rel-15 includes several new features and enhancements to support these requirements. Rel-16 standardization work focuses on further enhancing URLLC system performance, as well as ensuring reliable and efficient coexistence of URLLC and other NR use cases. One example scenario is when enhanced mobile broadband (eMBB) and URLLC user equipment (UE) coexist in the same cell. There are two main approaches to support multiplexing / prioritization.

[0004] In addition to operation in licensed bands, NR includes operation in unlicensed bands, i.e., NR-Unlicensed (NR-U). Allowing unlicensed networks (i.e., networks operating in unlicensed or shared spectrum) to efficiently use the available spectrum is an attractive approach to increase system capacity. For convenience, unlicensed spectrum herein can refer to both unlicensed spectrum and shared spectrum.

[0005] While unlicensed spectrum does not match the quality of licensed regimes, solutions that allow efficient use of the spectrum as a complement to licensed deployments have the potential to bring great value to network operators and ultimately the entire wireless industry. Certain features in NR need to be adapted to comply with the special characteristics of unlicensed bands and different regulations. In addition, UEs that intend to use unlicensed spectrum can employ a clear channel assessment (CCA) scheme to ascertain whether the channel is clear for a certain period of time.

[0006] One such technique is listen before talk (LBT). Depending on the channel access mode used by the device and the type of data it wishes to transmit in the upcoming transmission occasion, referred to as channel occupancy time (COT), there are different types of LBT. Common to all types is that the sensing is done in a specific channel (corresponding to a defined carrier frequency) and within a predefined bandwidth. In addition, two access operation modes are defined - Frame Based Equipment (FBE) and Load Based Equipment (LBE). In FBE mode, the sensing period is simple, while the sensing scheme in LBE mode is more complex.

[0007] FBE includes semi-static channel occupancy. In Figure 1 An example is shown in

[0008] Figure 1 is a timing diagram showing an example FBE procedure depicting Third Generation Partnership Project (3GPP) semi-static channel occupancy [ETSI Harmonized Standard EN 301 893 Section 4.2.7.3.1]. In FBE mode as defined in 3GPP specifications and shown in Figure 1 In FBE mode as defined in 3GPP specifications and shown in

[0009] In FFP, downlink / uplink transmissions are only allowed within the COT (a subset of the FFP resources), with the remaining idle period reserved so that other nodes also have the opportunity to sense and use the channel. Thus, in FBE operation, the channel is sensed at a specific interval just before the FFP boundary. The FFP can be set to a value between 1 and 10 ms and can be changed after a minimum of 200 ms. The idle period is a regulatory requirement and should be at least T IDLE ≥ max(0.05*COT, 100 us). In 3GPP TS 37.213, this has been simplified to T IDLE ≥ max(0.05*FFP, 100 us), i.e., the maximum channel occupancy time MCOT is defined as T MCOT= min(0.95 * FFP, FFP - 0.1 ms). So for a FFP of 10 ms, the MCOT is 9.5 ms, and for a FFP of 1 ms, the MCOT is 0.9 ms = 0.9 * FFP.

[0010] LBE includes dynamic channel occupancy. The default LBT mechanism for LBE operation (LBT category 4) is similar to existing Wi-Fi operation, where a node can sense the channel at any time and start transmitting if the channel is idle after a delay and backoff period. For certain cases, e.g., shared COT, other LBT categories that allow very short sensing periods are allowed.

[0011] There are different wideband operation modes. A node performs LBT on a specific bandwidth, called LBT channel, which is up to 20 MHz to comply with a WiFi channel. Therefore, the transmission bandwidth is also limited by the LBT bandwidth. However, it is possible to aggregate channels using carrier aggregation (where LBT is performed separately on each carrier) or using one wideband carrier split into several resource block sets (RB sets) (also called LBT bandwidth or LBT sub-band) (where LBT is performed on each RB set) in wideband operation mode.

[0012] There are certain challenges currently. For example, for COT initiation in FBE mode, only gNB initiated COT is considered in 3GPP specifications, i.e., gNB transmits at the start of the COT, and then the UE can transmit within the same COT (there can be multiple switching points between downlink and uplink within the same COT). This can lead to some issues.

[0013] If a configured grant (CG) occasion falls at the start of a COT, the gNB initiated COT procedure can collide in time domain with the CG occasion. Using gNB initiated COT as the only option can not be desirable for certain latency critical cases. For example, if an emergency URLLC request needs to be allocated immediately, and if there is an allocation occasion that intersects with the idle period and / or the start of a COT, the UE cannot use the (full) allocation because the UE has to wait for the gNB initiated procedure in the start of the next COT.

[0014] Therefore, UE initiated COT is a useful alternative, but supporting this feature brings new challenges. One is physical uplink shared channel (PUSCH) segmentation. If the PUSCH is segmented over a time period that spans a part of two FFPs, its segmentation behavior can depend on the type of initiation - gNB based or UE based. SUMMARY

[0015] As noted above, there are certain challenges with channel occupancy time (COT) / fixed frame period (FFP) scheduling in unlicensed spectrum currently. Certain aspects of the present disclosure and its embodiments can provide solutions for these or other challenges. For example, some embodiments include flexible scheduling, where COT behavior is not limited to gNB initiated COT. Some embodiments consider other initiation types and mode combinations (e.g., LBE and FBE) for flexible scheduling for reliable and low latency applications.

[0016] According to some embodiments, a method is performed by a wireless device for operating with shared spectrum channel access, where a first plurality of FFPs is associated with the wireless device and a second plurality of FFPs is associated with a network node, and where each FFP includes an idle period without transmission and a COT for potential transmission. The method includes initiating a COT in one of the FFPs in the first plurality of FFPs, and upon successfully initiating the COT, transmitting uplink data from a start of the COT.

[0017] In particular embodiments, the method further includes receiving an indication that the wireless device can initiate a COT in one of the FFPs in the first plurality of FFPs.

[0018] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain. Transmitting uplink data can include avoiding transmitting uplink data in an idle period of any of the FFPs in the second plurality of FFPs. Transmitting uplink data can include segmenting the uplink data into two or more segments, and avoiding transmitting any of the two or more segments that overlap with an idle period of any of the FFPs in the second plurality of FFPs. Transmitting uplink data can include segmenting the uplink data into two or more segments, and avoiding transmitting all of the two or more segments if any of the two or more segments overlap with an idle period of any of the FFPs in the second plurality of FFPs. Transmitting uplink data can include segmenting the uplink data into two or more segments, and avoiding transmitting any of the two or more segments after one of the two or more segments overlaps with an idle period of any of the FFPs in the second plurality of FFPs.

[0019] In particular embodiments, transmitting uplink data includes segmenting the uplink data into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next one of the two or more segments using a wireless device initiated COT in a next one of the first plurality of FFPs.

[0020] In particular embodiments, the method further comprises determining, at a start of a COT, that the wireless device has no uplink data to transmit, and transmitting, to a base station at the start of the COT, an indication that the wireless device has no uplink data to transmit.

[0021] In particular embodiments, the method further comprises signaling, to another wireless device or network node, whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

[0022] According to some embodiments, a wireless device comprises processing circuitry operable to perform any of the above wireless device methods.

[0023] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code which, when executed by processing circuitry, is operable to perform any of the methods performed by the above wireless devices.

[0024] According to some embodiments, a method is performed by a network node for operating with shared spectrum channel access, wherein a first plurality of FFPs is associated with a wireless device and a second plurality of FFPs is associated with the network node, and wherein each FFP comprises an idle period without transmission and a channel occupancy time (COT) for potential transmission. The method comprises determining that the wireless device initiated a COT in one of the FFPs of the second plurality of FFPs, and receiving uplink data from a start of the COT.

[0025] In particular embodiments, the method further comprises transmitting an indication that the wireless device can initiate a COT in one of the FFPs of the first plurality of FFPs.

[0026] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and no uplink data is received in an idle period of any of the FFPs of the second plurality of FFPs. The uplink data can be segmented into two or more segments, and no segment is received that overlaps with an idle period of any of the FFPs of the second plurality of FFPs. The uplink data can be segmented into two or more segments, and all of the two or more segments are not received if any of the two or more segments overlaps with an idle period of any of the FFPs of the second plurality of FFPs. The uplink data can be segmented into two or more segments, and a segment is not received after one of the two or more segments overlaps with an idle period of any of the FFPs of the second plurality of FFPs.

[0027] In particular embodiments, the uplink data is segmented into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next segment of the two or more segments in a next FFP of the first plurality of FFPs using a wireless device initiated COT.

[0028] In particular embodiments, the method further includes receiving an indication at a start of a COT that a wireless device has no uplink data to transmit.

[0029] In particular embodiments, the method further includes signaling to another wireless device or network node whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

[0030] According to some embodiments, a network node comprises processing circuitry operable to perform any of the above described network node methods.

[0031] Also disclosed is a computer program product comprising a non-transitory computer readable medium storing computer readable program code which, when executed by processing circuitry, is operable to perform any of the methods performed by the above described network node.

[0032] Certain embodiments can provide one or more of the following technical advantages. For example, in some embodiments, flexible COT behavior facilitates reliable and low latency transmissions. BRIEF DESCRIPTION OF DRAWINGS

[0033] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which:

[0034] Figure 1 is a timing diagram illustrating an example FBE procedure depicting a third generation partnership project (3GPP) semi-static channel occupancy;

[0035] Figure 2 is a timing diagram illustrating gNB initiated and UE initiated channel occupancy time (COT) transmissions according to particular embodiments;

[0036] Figure 3 is a timing diagram illustrating gNB initiated and UE initiated COT transmissions according to particular embodiments, where FFPs are not aligned;

[0037] Figure 4 is a timing diagram illustrating segmented portions of a transport block that occur on gNB initiated resources and idle periods intended for a COT that is not transmitted according to particular embodiments;

[0038] Figure 5 is a timing diagram illustrating a repeated segmented portion that is not transmitted within an idle period according to certain embodiments;

[0039] Figure 6 is a timing diagram illustrating a repeated segmented portion that is transmitted overlapping with invalid symbols after invalid resources according to certain embodiments;

[0040] Figure 7 is a timing diagram illustrating an example in which a UE transmits its repetition X in a gNB initiated COT and in the next COT, the UE initiates the transmission by transmitting the next Rep#X+1;

[0041] Figure 8 is a timing diagram illustrating UCI indicating a COT initiation failure for another FFP according to certain embodiments;

[0042] Figure 9 is a block diagram illustrating an example wireless network;

[0043] Figure 10 an example user equipment according to certain embodiments is shown;

[0044] Figure 11 is a flowchart illustrating an example method in a wireless device according to certain embodiments;

[0045] Figure 12 is a flowchart illustrating an example method in a network node according to certain embodiments;

[0046] Figure 13 schematic block diagrams of a wireless device and a network node in a wireless network according to certain embodiments are shown;

[0047] Figure 14 an example virtualization environment according to certain embodiments is shown;

[0048] Figure 15 an example telecommunication network connected via an intermediate network to a host computer according to certain embodiments is shown;

[0049] Figure 16 an example host computer in communication with user equipment through a base station over a partially wireless connection according to certain embodiments is shown;

[0050] Figure 17 is a flowchart illustrating a method implemented according to certain embodiments;

[0051] Figure 18 is a flowchart illustrating a method implemented in a communication system according to certain embodiments;

[0052] Figure 19is a flowchart illustrating a method implemented in a communication system, in accordance with certain embodiments; and

[0053] Figure 20 is a flowchart illustrating a method implemented in a communication system, in accordance with certain embodiments. DETAILED DESCRIPTION

[0054] As noted above, channel occupancy time (COT) / fixed frame period (FFP) scheduling in unlicensed spectrum currently presents certain challenges. Certain aspects of the present disclosure, and embodiments thereof, can provide solutions to these or other challenges.

[0055] Certain embodiments are described more fully below with reference to the accompanying drawings. Other embodiments, however, can be incorporated and are within the scope of the presently disclosed subject matter, which should not be interpreted as limited to the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0056] Certain embodiments include FFP / COT scheduling with multiple behaviors subject to COT initiation (e.g., gNB and / or UE) and mode of operation (LBE FBE).

[0057] In a first set of embodiments, for NR-U operation, radio resource control (RRC) or downlink control information (DCI) based signaling is used to disable or enable UE initiated COT behavior. This means that if a UE transmission falls in the start of a COT, then the user equipment (UE) can perform LBT and transmit its data or control signaling in the start of the COT if the UE initiated COT feature is enabled. The enabling or disabling of the UE initiated COT feature can be done, for example, according to any of the following.

[0058] For example, the signaling can be in unicast, or multicast, or broadcast fashion (e.g., group common DCI can be used). The signaling can be based on component carriers (CCs), e.g., the UE initiated COT feature is disabled on some CCs and enabled on some other CCs. The signaling can be based on listen-before-talk (LBT) channels, where the sensing procedure is performed if the cell is divided into multiple LBT channels.

[0059] The UE initiated COT transmission can include, for example, any of the following. They can include uplink data transmission on physical uplink shared channel (PUSCH), uplink control information (UCI) on physical uplink control channel (PUCCH) or PUSCH, sounding reference signal (SRS), and / or any uplink transmission (e.g., physical random access channel (PRACH)) initiated by the UE.

[0060] In some embodiments, the FFPs of the gNB and the UE(s) are perfectly aligned (same duration, same boundaries). In Figure 2 An example is shown in FIG. 1.

[0061] Figure 2 is a timing diagram showing gNB-initiated and UE-initiated COT transmissions according to certain embodiments. Figure 2 The data transmissions planned by the gNB and the UE are shown in the first row. For the gNB-initiated COT (second row), the second part of the UE transmission is postponed to the next uplink transmission occasion after the gNB initiates the next COT. Moreover, due to the UE transmission delay, the second part of the gNB is postponed to the third COT.

[0062] With the UE-initiated COT, the UE can directly transmit the second part of its transmission after the first FFP at the start of the next COT, so that all transmissions can be performed in this COT.

[0063] In some embodiments, the FFPs of the gNB and the UE(s) are not aligned (different duration, different boundaries). In Figure 3 An example is shown in FIG. 2.

[0064] Figure 3 is a timing diagram showing gNB-initiated and UE-initiated COT transmissions according to certain embodiments, where the FFPs are not aligned. Figure 3 The data transmissions planned by the gNB and the UE are shown in the first row. As shown in the second row, only the gNB-initiated COT is shown, the second UE transmission burst intersects with the idle period of the gNB’s FFP. Thus, the UE has to wait until the next gNB-initiated COT and its downlink transmission before it can transmit its data, resulting in some uplink transmission delay.

[0065] If the gNB has no downlink data, the gNB can decide not to initiate its COT. For UEs allowed to initiate their own COT within the gNB’s unused FFP, the UE can even perform a second transmission burst in the gNB’s idle period, as the gNB is not using its FFP. The gNB can initiate a new COT. However, whenever the COTs overlap, the nodes need to respect the other node’s idle period. As shown in Figure 3 the gNB needs to cancel or postpone its transmission during the UE’s idle period.

[0066] In a second set of embodiments, for NR-U operation with UE-initiated COT by disabling in the gNB’s FFP, if a (dynamic or CG-based) PUSCH transmission occurs on resources that cross the FFP boundary, the following embodiments handle the segmentation of repetitions.

[0067] In some embodiments, repetitions that fully or partially overlap with invalid resources are not transmitted. In this case, resources that fall in the idle period plus an extra margin (X, where X > 0 ms) are considered invalid. If the UE detects that a subsequent COT is initiated and has been assigned a downlink transmission of (dynamically scheduled or configured) resources, it can resume transmission in that COT. In Figure 4 Examples are shown in

[0068] Figure 4 is a timing diagram showing the segmented part of a transport block that occurs on gNB initiated resources intended for a COT that is not transmitted and an idle period, according to particular embodiments. As shown in Figure 4 As shown in, the transmission (PUSCH transport block) is segmented into three repetitions Rep#1, Rep#2, and Rep#3. Rep#1 occurs on the COT of the FFP where the transmission of the unsegmented PUSCH transport block (TB) should start. Rep#2 occurs on the idle period plus the resources intended for gNB-COT initiation in the next FFP, and Rep#3 occurs in the COT of the next FFP after the gNB initiation.

[0069] When the transmission intersects the FFP boundary, there are multiple options for UE transmission behavior. In some embodiments, the UE only does not transmit the intersecting repetitions, i.e., transmits Rep#1 and Rep#3, but not Rep#2, because it occurs on invalid symbols or resources.

[0070] In some embodiments, the complete PUSCH TB is not transmitted (i.e., Rep#1, Rep#2, and Rep#3 are not transmitted).

[0071] In some embodiments, only the repetitions that can be transmitted in the current COT are transmitted, and all other repetitions that would occur within or after the invalid symbols / resources and / or in the subsequent FFP are not transmitted, i.e., Rep#1 is transmitted, and Rep#2 and Rep#3 are not transmitted.

[0072] In a third set of embodiments, for NR-U operation with UE initiated COT enabled in the FFP, if a (dynamic or CG based) PUSCH transmission occurs on resources that cross the FFP boundary, the following embodiments handle the segmentation of repetitions. Repetitions that fully or partially overlap with invalid resources are not transmitted. In this case, resources that are in the idle period are considered invalid. If the UE is assigned (dynamically scheduled or configured) resources and is able to successfully initiate a UE COT at the start of the FFP, the UE can resume transmission in the subsequent COT. In Figure 5 Examples are shown in

[0073] Figure 5is a timing diagram showing a repeated segmented part that is not transmitted in an idle period, according to particular embodiments. As shown in Figure 5 The transmission of the PUSCH TB is segmented into three repetitions Rep#1, Rep#2, and Rep#3, as shown in

[0074] In some embodiments, the indication of the UE-initiated COT with Rep#3 can be indicated in Rep#2.

[0075] In a fourth set of embodiments, unlike Figure 4 and Figure 5 Rep#2 is transmitted after invalid symbols / resources, as shown in Figure 6

[0076] Figure 6 is a timing diagram showing a repeated segmented part that overlaps with invalid symbols transmitted after invalid resources, according to particular embodiments. The invalid symbols can indicate an idle period, or an idle period plus downlink resources (e.g., intended for gNB-initiated signaling).

[0077] In a fifth set of embodiments, any of the second, third, and fourth sets of embodiments can further include segmenting the repetitions around a slot boundary when the slot boundary occurs in the COT / FFP.

[0078] In a sixth set of embodiments, if a UE is scheduled with a transmission in the start of a FFP, and the UE has no data to transmit, the UE can inform or signal the gNB of the “no data” transmission. This signaling (in the form of UCI / sequence on PUCCH or PUSCH) serves the purpose of grabbing the COT, and also enables the gNB to act quickly, as in the case where the gNB intends to keep the COT (especially if an interferer is operating in the same spectrum nearby), there will be no data transmission from the UE, and the gNB needs to transmit or allocate resources to other UEs.

[0079] In a seventh set of embodiments, if a UE is configured with a normal / larger PUSCH (which can belong to dynamic or CG allocation), an additional smaller PUSCH or PUCCH can be configured, which starts simultaneously with the normal PUSCH.

[0080] ​The purpose of a smaller PUSCH or PUCCH is to allow the UE to transmit specific data sequences or UCIs in the smaller PUSCH if no data needs to be transmitted in the normal PUSCH, or to transmit UCIs in the PUCCH. The transmission of data sequences or UCIs is useful when the gNB does not initiate a COT and waits for the UE to initiate one. This allows the gNB to retain resources in the normal PUSCH when no data needs to be transmitted, while simultaneously allowing the UE to capture a COT by transmitting in a smaller PUSCH / PUCCH, enabling the gNB to continue transmitting within the same COT.

[0081] In the eighth set of embodiments, UE-initiated COT behavior can be enabled for some carriers or channels, and the behavior can be disabled for some carriers.

[0082] In the ninth set of embodiments, gNBs can be dynamically or based on CGs using cross-FFP scheduling (e.g., see...). Figure 6 This involves assigning one repeat in one FFP and another repeat in the next FFP. If the repeat falls at the beginning of a COT, the following options may apply. (Regarding...) Figure 7 Describe some options.

[0083] Figure 7 The following is a timing diagram illustrating an example, in which the UE transmits its repeat X in a COT initiated by the gNB (because the gNB transmits some DL signaling at the beginning of the COT), and in the next COT, the UE initiates a transmission by transmitting the next Rep#X+1.

[0084] If UE-initiated COT is not allowed, then the UE will not transmit the duplicate (i.e., Figure 7 (Rep#X+1 in the context of gNB-COT). The UE waits for gNB-COT initiation signaling, and if it receives or decodes the signaling, the UE transmits its Rep#X+1. The gNB-COT initiation signaling occurs at the beginning of the repeated resource intended for Rep#X+1, so the following options may be available.

[0085] In one option, if duplicate X+1 can still be accommodated, Rep#X+1 appears on the remaining resources (originally intended for Rep#X+1 before the gNB COT initiation signaling), or a segment of Rep#X+1 appears on the remaining resources, and Rep#X+1 is split into two segments, one of which overlaps with the gNB COT initiation signaling and is therefore not transmitted; the other segment occurs on the remaining resources.

[0086] If UE initiated COT is allowed, in this case, UE can transmit immediately from the start of COT if LBT at the end of the idle period is successful (gNB can assume this repetition transmission as implicit indication for COT initiation). UE can indicate during its uplink transmission in gNB initiated COT that it will initiate the next COT.

[0087] In the tenth set of embodiments, if UE is scheduled or performs transmission at the end of COT and if it is also granted transmission at the start of the next FFP, while UE has no more data to transmit, UE can inform or signal to gNB about “no data” transmission in UCI and thereby allow gNB to initiate the next COT.

[0088] The eleventh set of embodiments includes UE initiated COT in FBE scenario. If UE transmission is scheduled (i.e., not pre-configured) by the UE, gNB can derive the remaining COT duration that gNB can use without explicit indication from the UE.

[0089] If UE performs transmission based on pre-configured resources, even if gNB knows the start of UE’s COT, the duration of uplink transmission depends on the UE (depends on UE’s buffer and available resources). UE can indicate to gNB the start time, or its own transmission duration (gNB start time = UE start time plus transmission duration), or the remaining COT (gNB start time = COT end minus remaining COT). UE can indicate one of the parameters to gNB through UCI (on PUSCH or PUCCH on pre-configured uplink resources).

[0090] In the twelfth set of embodiments, repetitions (or multi-segment transmissions) are allocated based on which node initiates the COT. For example, all repetitions can be on gNB initiated COT(s), or all repetitions can be on UE initiated COT(s). Some repetitions can be allocated on gNB initiated COT(s) and some repetitions can be allocated on UE initiated COT(s) (e.g., see Figure 4 ).

[0091] In some embodiments, the repeated transmission can fall in the start of the COT, and if the UE is not allowed to initiate the COT by default, the following solutions can be considered. In some embodiments, the UE skips the transmission in the start of the COT. In some embodiments, the gNB sends downlink signaling, e.g., DCI, in the start of the COT, and then the UE can transmit in the remaining resources, and the UE can include UCI (in the PUSCH transmission) indicating that it is updated information to decode the transmission. In some embodiments, the gNB can pre-inform the UE and give permission to initiate in such COT, where the UE’s transmission falls in the start of the COT, and for this, appropriate downlink signaling (DCI / reference signaling) can be used.

[0092] If the UE fails to grab the channel, the following solutions can be considered on how the gNB can find out that the UE missed the COT initiation. In some embodiments, if the UE is allowed to transmit a TB in the start of the COT, and if the gNB does not detect the TB (i.e., the DMRS of the TB), the gNB concludes that the UE did not grab the COT. In some embodiments, if the UE is allowed to transmit UCI in the start of the COT, and if the gNB does not detect the UCI, the gNB concludes that the UE did not grab the COT. In some embodiments, if the UE has allocated UCI resources later in the same FFP (i.e., FFP #A) (and in another FFP, i.e., FFP #B), and can transmit negative feedback (LBT failure indication) in the UCI about the COT initiation (e.g., see Figure 8 ). In addition, the UE can indicate its buffer status so that the gNB can provide uplink grant to the UE in the COT of FFP #B. In other words, this UCI can act as a scheduling request (SR).

[0093] Figure 8 is a timing diagram illustrating UCI indicating COT initiation failure for another FFP, according to certain embodiments.

[0094] In some embodiments, the transmission can fall on the idle period of the FFP, then the following solutions can be considered. In some embodiments, the UE skips the transmission if a part of the transmission intersects with the idle period. In some embodiments, the UE can only transmit the transmission in the resources that are not part of the idle period in the FFP (i.e., only on the COT), and for this, the UE can include UCI (to indicate that it is updated control information) in the PUSCH transmission when the transmission is dynamically squeezed to fewer resources. Further options can also be considered.

[0095] In some embodiments, a gNB or UE initiated COT can be employed if the resource is in the start of a COT. For example, if the transmission falls in the end of a COT, a COT in the next FFP, and the start of a COT, the transmission can be segmented into two or more segments, where the segments are transmitted only in the COT, i.e., one or more segments in the COT before the idle period and one or more segments in the COT after the idle period.

[0096] Each segment transmission can be equipped with UCI to indicate decoding information, segment identification, etc.

[0097] A thirteenth set of embodiments includes a single UE configured with both modes - LBE and FBE, which can occur in the case of resource allocation for the same HARQ process, e.g., (a) with different component carriers (CCs), (b) with different repetitions, (c) with transmission modes - initial transmission, retransmission, and re-try. In some embodiments, in a cell, some UEs can be configured with FBE mode only and some UEs can be configured with LBE mode only.

[0098] In a fourteenth set of embodiments, a UE is configured with both LBE and FBE modes and the UE can dynamically change between FBE mode and LBE mode, with LBE mode operating as a fallback LBT mode.

[0099] In FBE mode, when a UE or gNB determines that a COT is not initiated, the UE / gNB can attempt to perform an LBE based channel access procedure to access the channel. In this case, for initial transmission, the UE / gNB must use LBE channel access rules to perform an LBT procedure based on LBE corresponding to the intended transmission properties.

[0100] A UE can include the type of LBT or the mode of LBT in its uplink UCI. A gNB, upon detecting the UCI and determining that the UE has performed a Cat 4 LBT, can switch to LBE based channel access operation in the current FFP or the next FFP or some other FFP.

[0101] A gNB can include an LBE channel access command for uplink transmission in downlink control information to a UE or a group of UEs for scheduling or other purposes, such as group common control signaling.

[0102] In another example, a gNB can indicate to a UE or a group of UEs to switch to and maintain LBE mode by using a flag in DCI. The gNB can switch back to the FBE mode of operation from the start of a FFP, for example, and indicate to the UE or the group of UEs to switch to FBE mode using a flag in DCI.

[0103] The FFP in which the channel access mode can change can follow a mode provided by configuration or a mode dynamically signaled.

[0104] In a fifteenth set of embodiments, in a UE initiated COT, the gNB signals other UEs sharing the COT about COT success (i.e., other UEs sharing the COT can transmit as per the regulations for unlicensed operation). The signaling can be based on a DCI transmitted on PDCCH or PDSCH or in the form of a transmission of a reference or synchronization signal that is broadcast / multicast / unicast to indicate COT success.

[0105] In some embodiments, in a UE initiated COT, the UE that initiated the COT signals other UEs about COT success over a sidelink channel. The signaling can be transmitted over a sidelink control channel (SLCCH) or a sidelink shared channel (SLSCH) or a reference signal to indicate COT success.

[0106] In some embodiments, in a UE initiated COT, if there is a COT grab failure (i.e., COT is busy or occupied and cannot be grabbed), the gNB signals only other UEs sharing the COT. This is beneficial in a controlled environment scenario, for example, where the likelihood of COT success is high and the gNB transmits signaling / indication only in case of COT success failure as this causes less signaling transmission overhead. The signaling can be based on a DCI on PDCCH or PDSCH or in the form of a transmission of a reference or synchronization signal that is broadcast / multicast / unicast to indicate COT success failure.

[0107] In a sixteenth set of embodiments, the gNB prioritizes which type of signaling information to use to indicate whether COT is successful or not. For example, in an uncontrolled environment, the gNB can prefer to send signaling related to positive COT success (i.e., LBT before COT success and COT is available for grabbing) as the probability of success can be low and thus can have a lower signaling overhead. In a controlled environment, the gNB can prefer to deliver signaling indicating negative COT success (i.e., COT is busy or occupied and cannot be grabbed).

[0108] In the above embodiments, the transmission can be in uplink or downlink. For example, if the transmission is in uplink, the data transmission can occur on PUSCH. Further, the PUSCH can be equipped with UCI (included in the PUSCH) to update its decoding information. Similarly, in downlink, the data transmission can occur on PDSCH. Further, the PUSCH can be equipped with DCI (included in the PDSCH) to update its decoding information.

[0109] In the embodiments described above, the transmissions can be part of SPS / CG or dynamic based allocation whenever possible. The embodiments described above can be used individually or in combination.

[0110] Although specific embodiments and examples are described herein for NR-U, the described embodiments and examples are generally applicable to any shared spectrum channel access operation (e.g., not limited to unlicensed operation, but also generally applicable to shared spectrum operation).

[0111] Figure 9 An example wireless network is illustrated in accordance with certain embodiments. The wireless network can comprise and / or interface with any type of communication, telecommunication, data, cellular, and / or radio network or other similar type of system. In some embodiments, the wireless network can be configured to operate in accordance with certain pre-defined rules or other types of procedures. Thus, particular embodiments of the wireless network can implement communication standards, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and / or ZigBee standards.

[0112] The network 106 can comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), local-area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication among devices.

[0113] Network nodes 160 and WDs 110 include various components described in more detail below. These components work together to provide network node and / or wireless device functionality such as providing wireless connections in a wireless network. In different embodiments, the wireless network can comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that can facilitate or participate in communication of data and / or signals (whether via wired or wireless connections).

[0114] As used herein, a network node is any device that can, does, or is capable of supporting communication with wireless devices and / or other network nodes in a wireless network and / or performing other functions that support the wireless network, such as management functions.

[0115] Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR NodeBs (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, in other words, the transmission power level at which they operate) and can then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.

[0116] A base station can be a relay node, or a relay-donating node controlling a relay. Network nodes can also include one or more (or all) parts of some embodiments of distributed radio base stations, such as centralized, digital, and / or remote radio units (RRUs), which can be sometimes referred to as remote radio heads (RRHs). Such remote radio units can or can not be integrated with antennas, as antenna-integrated radio equipment. Parts of a distributed radio base station can also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and / or MDTs.

[0117] As another example, a network node can be a virtual network node as described in more detail below. More generally, however, a network node can represent any suitable apparatus (or group of apparatuses) capable, configured, arranged, and / or operable to implement and / or provide a wireless device with access to and / or some other service provided by a wireless network.

[0118] In Figure 9 The network node 160, in this example, includes processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. While Figure 9 The network node 160 illustrated in the example wireless network of

[0119] It is to be understood that a network node includes any suitable combination of hardware and / or software needed for performing the tasks disclosed herein. Further, while the components of the network node 160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, the network node can comprise multiple different physical components (e.g., the device readable medium 180 can comprise multiple separate hard drives as well as multiple RAM modules) that make up the components illustrated as single boxes.

[0120] Similarly, the network node 160 can be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which can each have their own respective components. In certain scenarios in which the network node 160 includes multiple separate components (e.g., BTS and BSC components), one or more of the separate components can be shared among several network nodes. For example, a single RNC can control multiple NodeB’s. In such scenarios, each unique pair of a NodeB and an RNC can in some instances be considered a single separate network node.

[0121] In some embodiments, the network node 160 can be configured to support multiple radio access technologies (RATs). In such embodiments, some of the components can be duplicated (e.g., separate device readable medium 180 for the different RATs) and some of the components can be reused (e.g., the same antenna 162 can be shared by the RATs). The network node 160 can also include multiple sets of various illustrated components for the different wireless technologies integrated into the network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies can be integrated into the network node 160 within the same or different chip or chipset and other components.

[0122] The processing circuitry 170 is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations, as performed by the processing circuitry 170, can include processing information obtained by the processing circuitry 170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing, making a determination.

[0123] The processing circuitry 170 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other processing circuitry, functioning instruction execution units, or processing circuitry, as well as software and / or firmware directing the operation of such hardware.

[0124] For example, processing circuitry 170 can execute instructions stored in device readable medium 180 or in memory within processing circuitry 170. Such functionality can include providing various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry 170 can include a system on a chip (SOC).

[0125] In some embodiments, processing circuitry 170 can include one or more of radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174. In some embodiments, radio frequency (RF) transceiver circuitry 172 and baseband processing circuitry 174 can be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 172 and baseband processing circuitry 174 can be on the same chip or set of chips, boards, or units.

[0126] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device can be provided by the processing circuitry 170 executing instructions stored in device readable medium 180 or memory within processing circuitry 170. In alternative embodiments, some or all of the functionality can be provided by processing circuitry 170 without executing instructions stored in a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether

[0127] Device readable medium 180 can include any form of volatile or non-volatile computer readable memory including without limitation persistent storage, solid-state memory, remote installation memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a compact disc (CD), or a digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device readable and / or computer-executable memory devices that store information, data, and / or instructions that can be used by processing circuitry 170. Device readable medium 180 can be used to store any

[0128] Interface 190 is used in the wired or wireless communication of signalling and / or data between network nodes 160, network 106, and / or WDs 110. As illustrated, interface 190 comprises port(s) / terminal(s) 194 for sending and receiving data, for example to and from network 106 over a wired connection. Interface 190 also includes radio front end circuitry 192 that can be coupled to, or in some embodiments a part of, antenna 162.

[0129] Radio front end circuitry 192 comprises filters 198 and amplifiers 196. Radio front end circuitry 192 can be connected to antenna 162 and processing circuitry 170. Radio front end circuitry can be configured to condition signals communicated between antenna 162 and processing circuitry 170. Radio front end circuitry 192 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 192 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 can collect radio signals, which are then converted into digital data by radio front end circuitry 192. The digital data can be passed to processing circuitry 170. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0130] In certain alternative embodiments, network node 160 can not include separate radio front-end circuitry 192, but rather processing circuitry 170 can comprise radio front-end circuitry and can be connected to antenna 162 without separate radio front-end circuitry 192. Similarly, in some embodiments, all or some of RF transceiver circuitry 172 can be considered a part of interface 190. In still other embodiments, interface 190 can include one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172, as part of a radio

[0131] Antenna 162 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals. Antenna 162 can be coupled to radio front-end circuitry 192 and can be any type of antenna and / or antennas in

[0132] Antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by a network node. Any information, data and / or signals can be received from a wireless device, another network node and / or any other network equipment. Similarly, antenna 162, interface 190, and / or processing circuitry 170 can be configured to perform any transmitting operations described herein as being performed by a network node. Any information, data and / or signals can be transmitted to a wireless device, another network node, and / or any other network equipment.

[0133] Power supply circuitry 187 can comprise or be coupled to power management circuitry and is configured to supply the components of network node 160 with power for performing the functionality described herein. Power supply circuitry 187 can receive power from power source 186. Power source 186 and / or power supply circuitry 187 can be configured to provide power to the various components of network node 160 in a form suitable for use by each respective component (e.g., at a voltage and current level that each respective component needs). Power source 186 can be included in power supply circuitry 187 and / or network node 160 or external to power supply circuitry 187 and / or network node 160.

[0134] For example, network node 160 can be connectable to an external power source, such as an electrical outlet, via an input circuitry or interface, such as an electrical cable, whereby the external power source supplies power to power supply circuitry 187. As another example, power source 186 can comprise a source of power, such as a battery or battery pack, connected to or integrated in power supply circuitry 187. The battery can provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, can also be used.

[0135] Alternative embodiments of network node 160 can include additional components not Figure 9 shown in FIG. 1 1 that can be responsible for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, network node 160 can include user interface equipment to allow interaction with a user of network node 160. This can allow for a user to perform diagnostic, maintenance, repair, and other administrative functions for network node 160.

[0136] As used herein, a wireless device (WD) refers to a device capable of, configured for, arranged for, and / or operable to communicate wirelessly with a network node and / or other wireless devices. Unless otherwise noted, the term WD can be used interchangeably herein with user equipment (UE). Wireless communication can involve transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information over air.

[0137] In some embodiments, a WD can be configured to transmit and / or receive information without direct human interaction. For instance, a WD can be designed to transmit information to a network on a predetermined schedule, when requested by the network, or in response to a particular event.

[0138] Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE), a vehicle-mounted wireless terminal device, etc. A WD can support device-to-device (D2D) communication, such as using

[0139] As yet another specific example, in an Internet of Things (IoT) scenario, a WD can represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another WD and / or a network node. The WD can in this case be a machine-to-machine (M2M) device, which can in a 3GPP context be referred to as an MTC device. As one example, the WD can be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Examples of such machines or devices are sensors, metering devices (such as power meters), industrial machinery, or home or personal appliances (e.g., refrigerators, televisions, etc.), personal devices (e.g., watches, fitness trackers, etc.).

[0140] In other scenarios, a WD can represent a vehicle or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation. A WD as described above can represent the endpoint of a wireless connection, in which case the device can be referred to as a wireless terminal. Furthermore, a WD as described above can be mobile, in which case it can also be referred to as a mobile device or a mobile terminal.

[0141] As illustrated, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. WD 110 can include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies can integrate into the same chip set or different chip sets as other components within WD 110.

[0142] Antenna 111 can include one or more antennas or antenna arrays configured to send and / or receive wireless signals, and is connected to interface 114. In certain alternative embodiments, antenna 111 can be separate from WD 110 and be connectable to WD 110 through an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 can be configured to perform any receiving or transmitting described herein as being performed by a WD. Any information, data and / or signals can be received from a network node and / or another WD. In some embodiments, radio front end circuitry and / or antenna 111 can be considered an interface.

[0143] As illustrated, interface 114 includes radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 includes one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120. Radio front end circuitry 112 can be coupled to or a part of antenna 111. In some embodiments, WD 110 can not include separate radio front end circuitry 112; rather, processing circuitry 120 can comprise radio front end circuitry and can be connected to antenna 111. Similarly, in some embodiments, some or all of RF transceiver circuitry 122 can be considered a part of interface 114.

[0144] Radio front end circuitry 112 can receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry 112 can convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using combinations of filters 118 and / or amplifiers 116. The radio signal can then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 can collect radio signals, which are then converted into digital data by radio front end circuitry 112. The digital data can be passed to processing circuitry 120. In other embodiments, the interface can comprise different components and / or different combinations of components.

[0145] The processing circuitry 120 can comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide WD 110 functionality either alone or in combination with other WD 110

[0146] As illustrated, processing circuitry 120 includes one or more of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the processing circuitry can comprise different components and / or different combinations of components. In certain embodiments processing circuitry 120 of WD 110 can comprise a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 can be on separate chips or chipsets.

[0147] In alternative embodiments, some or all of baseband processing circuitry 124 and application processing circuitry 126 can be combined into one chip or chipset, and RF transceiver circuitry 122 can be on a separate chip or chipset. In still alternative embodiments, some or all of RF transceiver circuitry 122 and baseband processing circuitry 124 can be on the same chip or chipset, and application processing circuitry 126 can be on a separate chip or chipset. In yet other alternative embodiments, some or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 can be combined in the same chip or chipset. In some embodiments, RF transceiver circuitry 122 can be part of interface 114. RF transceiver circuitry 122 can condition RF signals for processing circuitry 120.

[0148] In certain embodiments, some or all of the functionality described herein as being performed by a WD can be performed by the processing circuitry 120 executing instructions stored on device readable medium 130, which in certain embodiments can be a computer-readable storage medium. In alternative embodiments, some or all of the functionality can be performed by processing circuitry 120 without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner.

[0149] In any of those embodiments, the processing circuitry 120 can be configured to perform the described functionality whether or not instructions are stored on the device readable storage medium. The benefits provided by such functionality are not limited to the processing circuitry 120 or other components of the WD 110 alone or the WD 110 generally, but are also enjoyed by end users and wireless networks that deploy the WD 110 e.g.

[0150] The processing circuitry 120 can be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by the processing circuitry 120, can include processing information obtained by the processing circuitry 120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by the WD 110, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing, making a determination.

[0151] The device readable medium 130 can be operable to store data, instructions, software, and / or any non-transitory, tangible, machine -readable media information. The device readable medium 130 can include random access memory (RAM), read only memory (ROM), programmable read only memory (PROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), magnetic disks, optical disks, floppy disks, flash memories, or a tape. Note that the device readable medium 130 can comprise other types of device readable media in different embodiments.

[0152] The user interface equipment 132 can provide components that allow for human user interaction with the WD 110. Such interaction can be of many forms, such as visual, audial, tactile, etc. The user interface equipment 132 can be operable to produce output to the user and allow the user to provide input to the WD 110. The type of interaction can vary depending on the type of equipment installed in the WD 110. For example, if the WD 110 is a smart phone, the interaction can be via a touch screen; if the WD 110 is a smart meter, the interaction can be through a screen that provides usage amounts (e.g., how many gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected).

[0153] The user interface equipment 132 can include input interfaces, devices, and circuits, and output interfaces, devices, and circuits. The user interface equipment 132 is configured to allow input of information into the WD 110 and is connected to the processing circuitry 120 to allow the processing circuitry 120 to process input information. The user interface equipment 132 can include, for example, a microphone, a proximity or other sensor, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface equipment 132 is also configured to allow output of information from the WD 110 and to allow the processing circuitry 120 to output information from the WD 110. The user interface equipment 132 can include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface equipment 132, the WD 110 can communicate with end users and / or other wireless networks and allow them to benefit from the functionality described herein.

[0154] The auxiliary equipment 134 is operable to provide more specialized functionality that can not be generally performed by WDs. This can include specialized sensors for making measurements for various purposes, interfaces for additional types of communication, such as wired communication, etc. The inclusion and type of components of the auxiliary equipment 134 can vary depending on the embodiment and / or scenario.

[0155] The power source 136 can in some embodiments take the form of a battery or battery pack. Other types of power sources, such as an external power supply (e.g., an electricity outlet), photovoltaic, or kinetic, can also be used. The WD 110 can further comprise power circuitry 137 for delivering power from the power source 136 to the various parts of the WD 110 which need power from the power source 136 to carry out any of the functionality described or indicated herein. The power circuitry 137 can in certain embodiments comprise power management circuitry.

[0156] The power circuitry 137 can additionally or alternatively be operable to receive power from an external power source; in which case the WD 110 can be connectable to the external power source via an input circuitry or interface such as an electrical cable. The power circuitry 137 can also in certain embodiments be operable to deliver power from an external power source to the power source 136. This can be, for example, for the charging of the power source 136. The power circuitry 137 can perform any formatting, converting, or other modification to the power from the power source 136 as is necessary to make the power suitable for the respective components of the WD 110 to which power is supplied.

[0157] Although the subject matter described herein can be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described primarily in the context of wireless networks, such as the example wireless network illustrated in Figure 1. Figure 9 For simplicity,Figure 9 The wireless network depicted in FIG. 1 only depicts network 106, network nodes 160 and 160b, and WDs 110, 110b, and 110c. In practice, the wireless network can further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device (such as a landline telephone, a service provider, or any other network node or end device). Of the illustrated components, network node 160 and wireless device (WD) 110 are depicted with additional detail. The wireless network can provide communication and other types of services to one or more wireless devices to facilitate the wireless devices’ access to and / or use of the services provided by, or via, the wireless network.

[0158] Figure 10 An example user equipment is shown in accordance with certain embodiments. As used herein, a user equipment or UE can not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE can represent a device that is intended for sale to, or operation by, a human user but that can not, or that can initially not, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE can represent a device that is not intended for sale to or operation by an end user but that can be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 200 can be any UE identified by the Third Generation Partnership Project (3GPP) including a NB-IoT UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As illustrated in FIG. 2 of the Prior Art, Figure 10 The UE 200 illustrated in FIG. 2 of the Prior Art is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP’s GSM, UMTS, LTE, and / or 5G standards. As previously mentioned, the term WD and UE can be used interchangeably. Thus, although the Figure 10 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

[0159] In Figure 10 the UE 200 includes processing circuitry 201 operatively coupled to an input / output interface 205, a radio frequency (RF) interface 209, a network connection interface 211, a memory 215 including a random access memory (RAM) 217, a read-only memory (ROM) 219, and a storage medium 221, a communication subsystem 231, a power source 213, and / or any other component, or any combination thereof. The storage medium 221 includes an operating system 223, application program 225, and data 227. In other embodiments, the storage medium 221 can include other similar types of information. Some of the components can not be Figure 10All of the components illustrated in FIG. 2 can be used, or just a subset of the components. The level of integration of the components can vary from one UE to another. Moreover, certain UEs can contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0160] In Figure 10 In some embodiments, the processing circuit 201 can be configured to process computer instructions and data. The processing circuit 201 can be configured to implement any sequential state machine operative to

[0161] In the depicted embodiment, the input / output interface 205 can be configured to provide a communication interface to an input device, output device, or input and output device. The UE 200 can be configured to use the output device via the input / output interface 205.

[0162] The output device can use the same type of interface port as the input device. For example, a USB port can be used to provide input to and output from the UE 200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, transmitter, smartcard, another output device, or any combination thereof.

[0163] The UE 200 can be configured to use the input device via the input / output interface 205 to allow a user to capture information into the UE 200. The input device can include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display can include a capacitive or resistive touch sensor to sense input from a user. The sensor can be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a

[0164] In Figure 10In particular embodiments, RF interface 209 can be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface 211 can be configured to provide a communication interface to network 243a. Network 243a can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network 243a can include a Wi-Fi network. Network connection interface 211 can be configured to include a receiver and a transmitter interface for communicating with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, or the like. Network connection interface 211 can implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions can share circuit components, software, or firmware, or alternatively can be implemented separately.

[0165] RAM 217 can be configured to interface with processing circuitry 201 via bus 202 to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM 219 can be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 can be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I / O) operations, or to load instructions or data into

[0166] Storage medium 221 can be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium 221 can be configured to include operating system 223, application program 225 such as a web browser application, a widget or gadget engine or another application, and data file 227. Storage medium 221 can store any of a variety of various operating systems or combinations of operating systems usable by UE 200.

[0167] The storage medium 221 can be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High-Density Digital Versatile Disc (DVD) optical drive, internal hard disk drive, Blu-Ray optical drive, holographic digital data storage (HDDS) optical drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory such as a subscriber identity module or removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 can allow the UE 200 to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to store

[0168] In Figure 10 The processing circuitry 201 can be configured to use the communication subsystem 231 to communicate with the network 243b. The network 243a and the network 243b can be the same network or different networks. The communication subsystem 231 can be configured to include one or more transceivers used to communicate with the network 243b. For example, the communication subsystem 231 can be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver can include a transmitter 233 and / or a receiver 235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN link (e.g., frequency allocations and the like). Further, the transmitter 233 and the receiver 235 of each transceiver can share circuit components, software or firmware, or alternatively can be implemented separately.

[0169] In the illustrated embodiment, the communication functions of communication subsystem 231 can include data communication, voice communication, multimedia communication, short-range communications, such as Bluetooth, near-field communication, location-based communication, such as the use of the global positioning system (GPS) to determine a location, another like function, or any combination thereof. For example, communication subsystem 231 can include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b can encompass wired and / or wireless networks, such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network, or any combination thereof. For example, network 243b can be a cellular network, a Wi-Fi network, and / or a near-field network. Power source 213 can be configured to supply alternating current (AC) or direct current (DC) power to components of UE 200.

[0170] The features, benefits and / or functions described herein can be implemented in one of the components of UE 200 or divided among multiple components of UE 200. Further, the features, benefits, and / or functions described herein can be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 can be configured to include any of the components described herein. Further, processing circuitry 201 can be configured to communicate with any of such components over bus 202. In another example, any of such components can be represented by program instructions stored in memory that when executed by processing circuitry 201 perform the corresponding functions described herein. In another example, the functionality of any of such components can be divided between processing circuitry 201 and communication subsystem 231. In another example, non-computationally intensive functions of any of such components can be implemented in software or firmware and computation-intensive functions can be implemented in hardware.

[0171] Figure 11 is a flowchart illustrating an example method in a wireless device, in accordance with certain embodiments. In particular embodiments, Figure 11 one or more steps of the method of Figure 9 described can be performed by the wireless device 110 described with respect to The wireless device can be operable to operate in shared spectrum channel access. A first plurality of FFPs is associated with the wireless device and a second plurality of FFPs is associated with a network node (e.g., network node 160). Each FFP includes an idle period without transmission and a COT for potential transmission.

[0172] The method can begin, at step 1112, with the wireless device (e.g., wireless device 110) receiving an indication that the wireless device can initiate a COT in one of the first plurality of FFPs. For example, wireless device 110 can receive the indication from network node 160 (e.g., via RRC, DCI, etc.). The indication can be unicast, multicast, or broadcast. The indication can be per component carrier or per LBT channel. The indication can include any of the indications described above with respect to the first set of embodiments.

[0173] At step 1114, the wireless device initiates the COT in one of the first plurality of FFPs, and at step 1116, transmits uplink data from the start of the COT. For example, wireless device 110 can transmit uplink data on PUSCH, UCI on PUSCH or PUCCH, PRACH, a reference signal, or any other transmission initiated by the wireless device. In Figures 2-8 Examples are shown in

[0174] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in the time domain, and transmitting the uplink data includes avoiding transmitting the uplink data in an idle period of any of the second plurality of FFPs. For example, the wireless device does not transmit uplink in its own idle period, and the wireless device also avoids transmitting in an idle period of the network node. In Figure 3 Examples are shown in

[0175] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in the time domain, and transmitting the uplink data includes segmenting the uplink data into two or more segments, and avoiding transmitting any of the two or more segments that overlap with an idle period of any of the second plurality of FFPs. In Figure 4 Examples are shown in

[0176] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in the time domain, and transmitting the uplink data includes segmenting the uplink data into two or more segments, and avoiding transmitting all of the two or more segments if any of the two or more segments overlap with an idle period of any of the second plurality of FFPs. That is, if any segment overlaps with an idle period of the network node, the wireless device does not transmit any segments.

[0177] In particular embodiments, the first and second pluralities of FFPs are not aligned in the time domain, and transmitting the uplink data includes segmenting the uplink data into two or more segments, and refraining from transmitting any of the two or more segments after one of the two or more segments overlaps with an idle period of any of the second plurality of FFPs. That is, the wireless device transmits segments until one segment overlaps with an idle period of the network node, and then the wireless device refrains from transmitting any more subsequent segments.

[0178] In particular embodiments, transmitting the uplink data includes segmenting the uplink data into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next one of the two or more segments using a wireless device initiated COT in a next one of the first plurality of FFPs.

[0179] In some embodiments, the wireless device can initiate the COT, but the wireless device can not have data to send, so the wireless device can inform the network node so that the network node can begin using the COT. In this case, the method continues to step 1118, where the wireless device determines that the wireless device has no uplink data to transmit at the start of the COT, and step 1120, where the wireless device transmits an indication to the base station that the wireless device has no uplink data to transmit at the start of the COT.

[0180] In some embodiments, the wireless device can attempt to initiate the COT, but fail to successfully initiate the COT (e.g., a collision occurs). In this case, the method continues to step 1122, where the network node signals to another wireless device or the network node whether the wireless device was able to successfully obtain the COT for the wireless device initiated COT. Examples are described with respect to the fifteenth, sixteenth, seventeenth groups of embodiments.

[0181] The method 1100 of Figure 11 may be modified, added to, or omitted. In addition, Figure 11 one or more steps in the method of may be performed in parallel or in any suitable order.

[0182] Figure 12 is a flowchart illustrating an example method in a network node, in accordance with certain embodiments. In particular embodiments, Figure 12 one or more steps of the method of may be performed by the network node 160 described with reference to Figure 9 The network node can operate in shared spectrum channel access. A first plurality of FFPs is associated with a wireless device (e.g., the wireless device 110), and a second plurality of FFPs is associated with the network node. Each FFP includes an idle period with no transmissions and a COT for potential transmissions.

[0183] The method can begin at step 1212, where the network node (e.g., network node 160) transmits an indication that a wireless device can initiate a COT in one of a first plurality of FFPs. The indication can be the indication described with respect to Figure 11 step 1112.

[0184] At step 1214, the network node determines that the wireless device initiated a COT in one of a second plurality of FFPs, and at step 1216, the network node receives uplink data from the start of the COT. Examples are described with respect to Figures 2-9

[0185] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and no uplink data is received in an idle period of any of the FFPs in the second plurality of FFPs. Examples are shown in Figure 3

[0186] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and no segment is received that overlaps an idle period of any of the FFPs in the second plurality of FFPs.

[0187] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and all of the two or more segments are not received if any of the two or more segments overlap an idle period of any of the FFPs in the second plurality of FFPs.

[0188] In particular embodiments, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and a segment is not received after one of the two or more segments overlaps an idle period of any of the FFPs in the second plurality of FFPs.

[0189] In particular embodiments, the uplink data is segmented into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next segment of the two or more segments in a COT initiated by the wireless device in a next FFP of the first plurality of FFPs using the wireless device.

[0190] At step 1218, the network node can receive an indication at the start of the COT that the wireless device has no uplink data to transmit. The network node can then use the COT for its own purposes.

[0191] ​​In step 1220, the wireless device may send a signaling message to another wireless device or network node to notify whether it has successfully obtained the COT for the COT initiated by the wireless device. Examples have been described with respect to the fifteenth, sixteenth, and seventeenth sets of embodiments. Examples have been described above with respect to the fifteenth set of embodiments.

[0192] Can be Figure 12 Method 1200 can be modified, added to, or omitted. Additionally, Figure 12 One or more steps in the method can be performed in parallel or in any suitable order.

[0193] Figure 13 A wireless network (e.g.) is shown. Figure 9 The diagram shows a schematic block diagram of two devices in a wireless network (as illustrated). The devices may include a network node and a wireless device (e.g., Figure 9 (Wireless device 110 and network node 160). Devices 1600 and 1700 are operable to implement respective references. Figure 11 and Figure 12 The example methods described herein. Devices 1600 and 1700 may be operable to implement any other processes or methods disclosed herein. It will also be understood that... Figure 11 and Figure 12 The method is not necessarily performed solely by devices 1600 and 1700. At least some operations of the method may be performed by one or more other entities.

[0194] The virtual device 1600 may include processing circuitry, which may include one or more microprocessors or microcontrollers, and other digital hardware (which may include digital signal processors (DSPs), application-specific digital logic, etc.). The processing circuitry may be configured to execute program code stored in memory, which may include one or more types of memory, such as read-only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. In several embodiments, the program code stored in the memory includes program instructions for executing one or more telecommunications and / or data communication protocols and instructions for implementing one or more of the techniques described herein.

[0195] In some implementations, the processing circuitry can be used to cause the receiving module 1602, the determining module 1604, the transmitting module 1606, and any other suitable unit of the device 1600 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0196] like Figure 13As shown in FIG. 16, the device 1600 includes a reception module 1602 configured to receive an indication of whether the device can initiate a COT according to any of the embodiments and examples described herein. A determination module 1604 is configured to determine whether uplink is available, whether a transmission will overlap with an idle period, and how to segment the transmission if needed according to any of the embodiments and examples described herein. A transmission module 1606 transmits uplink data according to any of the embodiments and examples described herein.

[0197] In some implementations, the processing circuitry can be used to cause the reception module 1702, the determination module 1704, the transmission module 1706, and any other suitable units of the device 1700 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0198] As Figure 13 As shown in FIG. 17, the device 1700 includes a reception module 1702 configured to receive uplink data from a wireless device according to any of the embodiments and examples described herein. A determination module 1704 is configured to determine whether the wireless device initiated a COT according to any of the embodiments and examples described herein. A transmission module 1706 is configured to transmit an indication to the wireless device about whether the wireless device can initiate a COT according to any of the embodiments and examples described herein.

[0199] Figure 14 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments can be virtualized. In the present context, virtualization refers to the creation of virtual versions of physical devices or computational resources in which virtual machines or virtual components are run on top of an operating system, which is run on a physical processing node. As used herein, virtualization can apply to a node (e.g., a virtualized base station or a virtualized radio access node) or to an application (e.g., a UE, a wireless device, or any other type of communication device) or components thereof and relate to an implementation in which at least a part of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers executing on one or more physical processing nodes in one or more networks).

[0200] In some embodiments, some or all of the functions described herein can be implemented as virtual components executed by one or more virtual machines hosted by one or more of the hardware nodes 330 within one or more virtual environments 300. Additionally, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node can be entirely virtualized.

[0201] The functions can be implemented by one or more applications 320 (which can alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 are run in virtualization environment 300 which provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 contains instructions 395 executable by the processing circuitry 360 whereby the application 320 is operative to provide one or more of the features, benefits, and / or functions disclosed herein.

[0202] Virtualization environment 300 comprises general-purpose or special-purpose network hardware devices 330 comprising a set of one or more processors or processing circuitry 360, which can be commercial off-the-shelf (COTS) processors, dedicated Application-Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device can include memory 390-1 which can be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device can include one or more network interface controllers (NICs) 370, also commonly referred to as network interface cards, which include physical network interfaces 380. Each hardware device can also include non-transitory, persistent, machine-readable storage media 390-2 having stored therein software 395 and / or instructions executable by processing circuitry 360. Software 395 can include any type of software including software to instantiate one or more virtualization layers 350 (also referred to as hypervisors), software to execute virtual machines 340 and allow it to execute software 395 that enables it to perform the

[0203] Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and can be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the instance of virtual appliance 320 can be implemented in one or more of the virtual machines 340 and can be implemented in different ways.

[0204] During operation, processing circuitry 360 executes software 395 to instantiate the hypervisor or virtualization layer 350, which can sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer 350 can present a virtual operating platform that appears like networking hardware to virtual machine 340.

[0205] As in Figure 14As illustrated, hardware 330 can be a standalone network node with generic or specific components. Hardware 330 can comprise antenna 3225 and can implement some functions via virtualization. Alternatively, hardware 330 can be part of a larger cluster of hardware, e.g., such as in a data center or customer premise equipment (CPE), where many hardware nodes work together and are managed via management and orchestration (MANO) 3100, which, among others, oversees lifecycle management of applications 320.

[0206] Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV can be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches and physical storage, which can be located in data centers, and customer premise equipment.

[0207] In the context of NFV, virtual machine 340 can be a software implementation of a physical machine that runs programs just as if they were executing on a physical, non-virtual machine. Each of virtual machines 340, and that part of hardware 330 that executes that virtual machine, whether it is hardware dedicated to that virtual machine and / or hardware that is shared by that virtual machine with others of the virtual machines 340, forms a separate Virtual Network Element (VNE).

[0208] Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that are run in one or more virtual machines 340 on top of hardware networking infrastructure 330 and corresponds to Figure 14 application 320 in Figure 3.

[0209] In some embodiments, one or more radio units 3200 that each include one or more transmitters 3220 and one or more receivers 3210 can be coupled to one or more antennas 3225. Radio units 3200 can communicate directly with hardware nodes 330 via one or more appropriate network interfaces and can be used in combination with virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

[0210] In some embodiments, some signaling can be effected with the aid of a control system 3230, which can alternatively be used for communication between hardware nodes 330 and radio units 3200.

[0211] Reference is made to Figure 15According to an embodiment, the communication system includes a telecommunication network 410, such as a 3GPP-type cellular network, which comprises access networks 411, such as radio access networks, and a core network 414. The access network 411 comprises a plurality of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c is connectable to the core network 414 over a wired or wireless connection 415. A first UE 491 located in coverage area 413c is configured to wirelessly connect to, or be paged by, the corresponding base station 412c. A second UE 492 in coverage area 413a is wirelessly connectable to the corresponding base station 412a. While a plurality of UEs 491, 492 are illustrated in this example, the

[0212] The telecommunication network 410 is itself connected to a host computer 430, which can be implemented as a standalone server, a cloud-implemented server, a distributed server or as a server farm, and can include processor and memory. The host computer 430 can be under the ownership or control of a service provider, or can be operated by the service provider or on behalf of the service provider. Connections 421 and 422 between the telecommunication network 410 and the host computer 430 can be implemented via wired or wireless connections. The intermediate network 420 can be a public, private, or hosted network; the intermediate network 420 can be a bulk network, an Internet, or a combination of networks. For example, the intermediate network 420 can include a core network, an IP

[0213] Figure 15The communication system as a whole enables connectivity between the connected UEs 491, 492 and the host computer 430. The connectivity can be described as an over-the-top (OTT) connection 450. The host computer 430 and the connected UEs 491, 492 are configured to communicate using the OTT connection 450 via the access network 411, the core network 414, any intermediate network 420 and possible further infrastructure (not shown) as the communication pathway. The OTT connection 450 can be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of uplink and downlink communications. For example, a base station 412 can not or need not be informed about the past routing of an incoming downlink communication with data originating from a host computer 430 to be forwarded (e.g., handed over) to a connected UE 491. Similarly, the base station 412 need not be aware of the future routing of an outgoing uplink communication originating with the UE 491 towards the host computer 430.

[0214] Figure 16 An example host computer communicating via a base station with a user equipment over a partially wireless connection is shown in accordance with certain embodiments. In accordance with embodiments, reference will now be made to the Figure 16 Example implementations of the UEs, base stations and host computer discussed in the preceding paragraphs will now be described. In communication system 500, host computer 510 comprises hardware 515 including communication interface 516 configured to set up and maintain at least one wired or wireless connection 520 with a corresponding interface of a different communication device of communication system 500. Host computer 510 further comprises processing circuitry 518, which can have storage and / or processing capabilities. In particular, processing circuitry 518 can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer 510 further comprises software 511, which is stored in or accessible by host computer 510 and executable by processing circuitry 518. Software 511 includes host application 512. Host application 512 can be operable to provide services to users remote from host computer 510, such as users operating UEs 530. In providing services to the users, host application 512 can provide user data which is transmitted using OTT connection 550. OTT connection 550 is thus a connection between host computer 510 and a user of UE 530 via a network 420. This connection can pass via different networks and intermediaries, including a server computer 540, but to the user of UE 530 and to the owner of host computer 510, the connection can appear as a simple direct connection.

[0215] The communication system 500 further includes the base station 520 provided in a telecommunication system and comprising hardware 525 enabling it to communicate with the host computer 510 and the UE 530. The hardware 525 can include a communication interface 526 for Figure 16 setting up and maintaining at least a wired or wireless connection with the different communication devices of the communication system 500, as well as a radio interface 527 for setting up and maintaining at least a wireless connection 570 with a UE 530 located in a coverage area (not shown in Figure 16 FIGURE 1) served by the base station 520. The communication interface 526 can be configured to facilitate a connection 560 to the host computer 510. The connection 560 can be direct or it can pass through the core network (not shown in FIGURE 1) of the telecommunication system and / or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, the hardware 525 of the base station 520 further includes processing circuitry 528, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The base station 520 further has software 521 stored internally or accessible via an external connection.

[0216] The communication system 500 further includes the UE 530 already referred to. Its hardware 535 can include a radio interface 537 configured to set up and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 currently is located. The hardware 535 of the UE 530 further includes processing circuitry 538, which can comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. The UE 530 further comprises software 531 stored internally or accessible via an external connection and executable by the processing circuitry 538. The software 531 includes a client application 532. The client application 532 can be operable to provide a service to a human or non-human user via the UE 530 with the support of the host computer 510. In the host computer 510, an executing host application 512 can communicate with the executing client application 532 via the OTT connection 550 terminating at the UE 530 and the host computer 510. In providing the service to the user, the client application 532 can receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 can transfer both the request data and the user data. The client application 532 can generate the user data by interacting with the user.

[0217] It is noted that the host computer 510, the base station 520 and the UE 530 illustrated in Figure 16 FIGURE 1 can comprise respective parts of a Figure 15the host computer 430, the base station 412a, 412b, 412c, and the UE 491, 492 are similar or identical to those of the host computer 510, the base station 520, and the UE 530, respectively. That is, the inner workings of these entities can be as shown in FIG. 5 and, independently, the surrounding network topology can be that of FIG. 5. Figure 16 Figure 15

[0218] In FIG. 5, the OTT connection 550 has been drawn abstractly to illustrate the communication between the host computer 510 and the UE 530 via the base station 520, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure can determine the routing, which it can be configured to hide from the UE 530 or from the service provider operating the host computer 510, or both. Figure 16

[0219] The wireless connection 570 between the UE 530 and the base station 520 is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to the UE 530 using the OTT connection 550, in which the wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments can improve the signaling overhead and reduce the latency, which can provide faster Internet access for the user.

[0220] ​​​A measurement procedure can be provided for monitoring data rate, latency and other factors of the data transmission improved by one or more embodiments. There can further be an optional network functionality for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530, in response to variations in the measurement results. The measurement procedure and / or the network functionality for reconfiguring the OTT connection 550 can be implemented in the software 511 and the hardware 515 of the host computer 510 or in the software 531 and the hardware 535 of the UE 530, or both. In embodiments, sensors (not shown) can be deployed in or in association with the communication devices through which the OTT connection 550 traverses; the sensors can participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software 511, 531 can compute or estimate the monitored quantities. The reconfiguring of the OTT connection 550 can include message format, retransmission settings, preferred routing, etc.; the reconfiguring need not affect the base station 520, and it can be unknown or unnoticed by the base station 520. Such procedures and functionality can be known and practiced in the art. In certain embodiments, measurements can involve special UE signaling facilitating the host computer's 510 measurements of throughput, propagation times, latency and the like. The measurements can be implemented due to the software 511, 531 causing the transmission of messages, specifically also empty or 'dummy' messages, using the OTT connection 550 while the software 511, 531 monitors propagation times, errors etc.

[0221] Figure 17 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 15 and Figure 16 The description will only include references to the accompanying drawings to the extent that the drawings are necessary for understanding the disclosure. Figure 17

[0222] In step 610, the host computer provides user data. In sub-step 611 (which can be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission carrying the user data to the UE. In step 630 (which can be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which can also be optional), the UE executes a client application associated with the host application executed by the host computer.

[0223] Figure 18 is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 15 and​Figure 16 Those described with reference to the DETAILED DESCRIPTION will be included in this section. In order to simplify the present disclosure, in this section only diagram references to Figure 18 will be included.

[0224] In step 710 of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission carrying the user data to the UE. The transmission can pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step 730, which can be optional, the UE receives the user data carried in the transmission.

[0225] Figure 19 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 15 and Figure 16 Those described with reference to the DETAILED DESCRIPTION will be included in this section. In order to simplify the present disclosure, in this section only diagram references to Figure 19 will be included.

[0226] In step 810, which can be optional, the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In substep 821 of step 820, which can be optional, the UE provides the user data by executing a client application. In substep 811 of step 810, which can be optional, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application can further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep 830, which can be optional, transmission of the user data to the host computer. In step 840 of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

[0227] Figure 20 is a flow chart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which can be those described with reference to Figure 15 and Figure 16 Those described with reference to the DETAILED DESCRIPTION will be included in this section. In order to simplify the present disclosure, in this section only diagram references to Figure 20 will be included.

[0228] In step 910, which can be optional, the base station receives user data from the UE, in accordance with the teachings of the embodiments described throughout this disclosure. In step 920, which can be optional, the base station initiates transmission of the received data to the host computer. In step 930, which can be optional, the host computer receives the user data carried in the transmission initiated by the base station.

[0229] The term unit can have conventional meaning within the electronics industry and can include, for example, electrical and / or electronic circuitry, devices, modules, processors, memories, logic solid state and / or discrete devices, computer programs or instructions, etc., such as those that are described herein.

[0230] Modifications, additions, or omissions can be made to the systems and apparatuses disclosed herein without departing from the scope of the disclosure. The components of the systems and apparatuses can be integrated or separated. Moreover, the operations of the systems and apparatuses can be performed by more, fewer, or other components. Additionally, operations of the systems and apparatuses can be performed using any suitable logic comprising software, hardware, and / or other logic. As used in this document, "each" refers to each member of a set or each member of a subset of a set.

[0231] Modifications, additions, or omissions can be made to the methods disclosed herein without departing from the scope of the disclosure. The methods can include more, fewer, or other steps. Additionally, steps can be performed in any suitable order.

[0232] The foregoing description discloses merely exemplary embodiments of this application. However, various modifications are made within the scope of the present application. For example, elements described in association with particular embodiments can be interchanged with similar elements or equivalents. Moreover, the methods described herein do not have to be performed in the order described. In addition, the description above is intended to be illustrative, and not restrictive. Many other embodiments will be apparent to those of skill in the art upon reviewing the above description. The scope of the application should, therefore, be determined not with reference to the above description, but instead with reference to the appended claims, along with their full scope of equivalents.

[0233] Reference throughout this specification to "an embodiment," "embodiments," "one embodiment," "an example embodiment," etc., means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the appearances of the phrase "in one embodiment" or "in an example embodiment" in various places throughout this specification are not necessarily referring to the same embodiment. Furthermore, the particular features, structures, or characteristics can be combined in any suitable manner in one or more embodiments.

[0234] While the disclosure has been described in accordance with certain embodiments, modifications and substitutions can be made by those skilled in the art without departing from the spirit of the disclosure. Therefore, the above description should not be taken as limiting on the scope of the disclosure. Other changes, modifications, and variations can be made by those skilled in the art without departing from the scope of the disclosure as defined by the claims below.

[0235] At least some of the following abbreviations can be used in the present disclosure. If there is an inconsistency between the abbreviation and the above description of how it is used, the above description should prevail. If a term is listed multiple times below, the first listing should prevail over any subsequent listing(s).

[0236] 1x RTT CDMA2000 1x Radio Transmission Technology

[0237] 3GPP 3rd Generation Partnership Project

[0238] 5G 5th Generation

[0239] 5GS 5G System

[0240] ABS Almost Blank Subframe

[0241] ARQ Automatic Repeat reQuest

[0242] AWGN Additive White Gaussian Noise

[0243] BCCH Broadcast Control Channel

[0244] BCH Broadcast Channel

[0245] BW Bandwidth

[0246] CA Carrier Aggregation

[0247] CC Carrier Component

[0248] CCA Clear Channel Assessment

[0249] CCCH SDU Common Control Channel SDU

[0250] CDMA Code Division Multiple Access

[0251] CE Control Element

[0252] CGI Cell Global Identifier

[0253] CIR Channel Impulse Response

[0254] CNC Central Network Controller (for TSN)

[0255] COT Channel Occupancy Time

[0256] CP Cyclic Prefix

[0257] CPICH Common Pilot Channel

[0258] CPICH Ec / No CPICH energy per chip divided by power density in the frequency band

[0259] CQI Channel Quality Information

[0260] C-RNTI Cell RNTI

[0261] CSI Channel State Information

[0262] D2D Device-to-Device

[0263] DCCH Dedicated Control Channel

[0264] DL Downlink

[0265] DM Demodulation

[0266] DMRS Demodulation Reference Signal

[0267] DRX Discontinuous Reception

[0268] DS-TT Device Side TSN Translator

[0269] DTX Discontinuous Transmission

[0270] DTCH Dedicated Traffic Channel

[0271] DUT Device Under Test

[0272] E-CID Enhanced Cell ID (positioning method)

[0273] E-SMLC Evolved Serving Mobile Location Center

[0274] ECGI Evolved CGI

[0275] eNB E-UTRAN NodeB

[0276] ePDCCH Enhanced Physical Downlink Control Channel

[0277] E-SMLC Evolved Serving Mobile Location Center

[0278] E-UTRA Evolved UTRA

[0279] E-UTRAN Evolved UTRAN

[0280] FBE Frame Based Equipment

[0281] FDD Frequency Division Duplex

[0282] FFP Fixed Frame Period

[0283] GERAN GSM EDGE Radio Access Network

[0284] GM Grand Master

[0285] gNB Base station in NR

[0286] GNSS Global Navigation Satellite System

[0287] GSM Global System for Mobile Communications

[0288] HARQ Hybrid Automatic Repeat reQuest

[0289] HO Handover

[0290] HSPA High Speed Packet Access

[0291] HRPD High Rate Packet Data

[0292] IIoT Industrial Internet of Things

[0293] LBE Load Based Equipment

[0294] LBT Listen Before Talk

[0295] LOS Line of Sight

[0296] LPP LTE Positioning Protocol

[0297] LTE Long Term Evolution

[0298] MAC Medium Access Control

[0299] MBMS Multimedia Broadcast Multicast Service

[0300] MBSFN Multimedia Broadcast Multicast Service Single Frequency Network

[0301] MBSFN ABS MBSFN Almost Blank Subframe

[0302] MDT Minimization of Drive Tests

[0303] MIB Master Information Block

[0304] MME Mobility Management Entity

[0305] MSC Mobile Switching Center

[0306] NPDCCH Narrowband Physical Downlink Control Channel

[0307] NR New Radio

[0308] NW-TT Network-side TSN Translator

[0309] OCNG OFDMA channel noise generator

[0310] OFDM orthogonal frequency division multiplexing

[0311] OFDMA orthogonal frequency division multiple access

[0312] OSS operation support system

[0313] OTA over-the-air

[0314] OTDOA observed time difference of arrival

[0315] O&M operation and maintenance

[0316] PBCH physical broadcast channel

[0317] P-CCPCH primary common control physical channel

[0318] PCell primary cell

[0319] PCFICH physical control format indicator channel

[0320] PDCCH physical downlink control channel

[0321] PD propagation delay

[0322] PDP propagation delay profile

[0323] PDSCH physical downlink shared channel

[0324] PGW packet gateway

[0325] PHICH physical hybrid-ARQ indicator channel

[0326] PLMN public land mobile network

[0327] PMI precoder matrix indicator

[0328] ppb parts per billion

[0329] PRACH physical random access channel

[0330] PRS positioning reference signal

[0331] PSS primary synchronization signal

[0332] PTP precision time protocol

[0333] PUCCH physical uplink control channel

[0334] PUSCH physical uplink shared channel

[0335] RACH random access channel

[0336] QAM quadrature amplitude modulation

[0337] RAN radio access network

[0338] RAT radio access technology

[0339] RAR random access response

[0340] RLM radio link management

[0341] RNC radio network controller

[0342] RNTI radio network temporary identifier

[0343] RRC radio resource control

[0344] RRM radio resource management

[0345] RS reference signal

[0346] RSCP received signal code power

[0347] RSRP reference symbol received power or reference signal received power

[0348] RSRQ reference signal received quality or reference symbol received quality

[0349] RSSI received signal strength indicator

[0350] RSTD reference signal time difference

[0351] RTT round trip time

[0352] SCH synchronization channel

[0353] SCell secondary cell

[0354] SCS subcarrier spacing

[0355] SDU service data unit

[0356] SFN system frame number

[0357] SGW serving gateway

[0358] SI system information

[0359] SIB system information block

[0360] SNR signal to noise ratio

[0361] SON self-optimizing network

[0362] SS synchronization signal

[0363] SSS secondary synchronization signal

[0364] TA timing advance

[0365] TDD time division duplex

[0366] TDOA time difference of arrival

[0367] TOA time of arrival

[0368] TS time synchronization

[0369] TSN time sensitive networking

[0370] TSS tertiary synchronization signal

[0371] TTI transmission time interval

[0372] UE user equipment

[0373] UL uplink

[0374] UMTS universal mobile telecommunications system

[0375] UPF user plane function

[0376] URLLC ultra-reliable low latency communication

[0377] USIM universal subscriber identity module

[0378] UTDOA uplink time difference of arrival

[0379] UTRA universal terrestrial radio access

[0380] UTRAN universal terrestrial radio access network

[0381] WCDMA wide CDMA

[0382] WLAN wireless local area network

Claims

1. A method performed by a wireless device for operating with shared spectrum channel access, wherein, A first plurality of fixed frame periods (FFPs) is associated with the wireless device and a second plurality of fixed frame periods (FFPs) is associated with a network node, and wherein each FFP comprises an idle period without transmissions and a channel occupancy time (COT) allowing the wireless device or the network node to transmit, the method comprising: initiating (1114) a COT in one of the FFPs in the first plurality of FFPs; and transmitting (1116) uplink data from a start of the COT to the network node once the COT is successfully initiated, wherein the first and second pluralities of FFPs are not aligned in time domain, and transmitting uplink data comprises segmenting the uplink data into two or more segments and refraining from transmitting any of the two or more segments that overlap with an idle period of any of the FFPs in the second plurality of FFPs.

2. The method of claim 1, further comprising receiving (1112) an indication that the wireless device can initiate a COT in one of the FFPs in the first plurality of FFPs.

3. The method of any one of claims 1-2, wherein, The first and second pluralities of FFPs are not aligned in time domain, and transmitting uplink data comprises refraining from transmitting uplink data in an idle period of any of the FFPs in the second plurality of FFPs.

4. The method of any one of claims 1-2, wherein, The first and second pluralities of FFPs are not aligned in time domain, and transmitting uplink data comprises segmenting the uplink data into two or more segments and refraining from transmitting all of the two or more segments if any of the two or more segments overlap with an idle period of any of the FFPs in the second plurality of FFPs.

5. The method of any one of claims 1-2, wherein, The first and second pluralities of FFPs are not aligned in time domain, and transmitting uplink data comprises segmenting the uplink data into two or more segments and refraining from transmitting any of the two or more segments after one of the two or more segments overlaps with an idle period of any of the FFPs in the second plurality of FFPs.

6. The method of any one of claims 1-2, wherein, Transmitting uplink data comprises segmenting the uplink data into two or more segments, and one of the two or more segments comprises an indication that the wireless device will transmit a next one of the two or more segments in a next one of the first plurality of FFPs using a wireless device initiated COT in the next one of the first plurality of FFPs.

7. The method of any of claims 1-2, the method further comprising: determining (1118) at a start of a COT that the wireless device has no uplink data to transmit; and transmitting (1120) an indication to a base station at the start of the COT that the wireless device has no uplink data to transmit.

8. The method of any of claims 1-2, the method further comprising signaling (1122) to another wireless device or network node whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

9. A wireless device (110) operable to operate in shared spectrum channel access, wherein, a first plurality of fixed frame periods (FFPs) is associated with the wireless device and a second plurality of fixed frame periods (FFPs) is associated with a network node (160), and wherein each FFP comprises an idle period with no transmissions and a channel occupancy time (COT) allowing the wireless device or the network node to transmit, the wireless device comprising processing circuitry (120) operable to: initiate a COT in one of the FFPs in the first plurality of FFPs; and once the COT is successfully initiated, transmit uplink data from a start of the COT to the network node, wherein the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the processing circuitry is operable to transmit uplink data by segmenting the uplink data into two or more segments and refraining from transmitting any of the two or more segments overlapping an idle period of any of the FFPs in the second plurality of FFPs.

10. The wireless device of claim 9, the processing circuitry further operable to receive an indication that the wireless device can initiate a COT in one of the FFPs in the first plurality of FFPs.

11. The wireless device of any one of claims 9-10, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the processing circuitry is operable to transmit uplink data by refraining from transmitting uplink data in an idle period of any of the FFPs in the second plurality of FFPs.

12. The wireless device of any one of claims 9-10, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the processing circuitry is operable to transmit uplink data by segmenting the uplink data into two or more segments and refraining from transmitting all of the two or more segments if any of the two or more segments overlap an idle period of any of the FFPs in the second plurality of FFPs.

13. The wireless device of any one of claims 9-10, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the processing circuitry is operable to transmit uplink data by segmenting the uplink data into two or more segments and refraining from transmitting any of the two or more segments after one of the two or more segments overlaps an idle period of any of the FFPs in the second plurality of FFPs.

14. The wireless device of any one of claims 9-10, wherein, The processing circuitry can be operable to transmit uplink data by segmenting the uplink data into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next segment of the two or more segments using a wireless device initiated COT in a next FFP of the first plurality of FFPs.

15. The wireless device of any of claims 9-10, the processing circuitry further operable to: determine at a start of a COT that the wireless device has no uplink data to transmit; and transmit, to a base station at the start of the COT, an indication that the wireless device has no uplink data to transmit.

16. The wireless device of any of claims 9-10, the processing circuitry further operable to signal to another wireless device or network node whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

17. A method for operating with shared spectrum channel access performed by a network node, wherein, a first plurality of fixed frame periods (FFPs) are associated with a wireless device and a second plurality of fixed frame periods (FFPs) are associated with the network node, and wherein each FFP includes an idle period with no transmissions and a channel occupancy time (COT) allowing the wireless device or the network node to transmit, the method comprising: determining (1214) that a wireless device initiated a COT in one of the FFPs of the second plurality of FFPs; and receiving (1216) uplink data from the wireless device from a start of the COT, wherein the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and no segment is received that overlaps an idle period of any of the FFPs of the second plurality of FFPs.

18. The method of claim 17, further comprising transmitting (1212) an indication that the wireless device can initiate a COT in one of the FFPs of the first plurality of FFPs.

19. The method of any one of claims 17-18, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and no uplink data is received in an idle period of any of the FFPs of the second plurality of FFPs.

20. The method of any one of claims 17-18, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and all of the two or more segments are not received if any of the two or more segments overlap an idle period of any of the FFPs of the second plurality of FFPs.

21. The method of any one of claims 17-18, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in time domain, and the uplink data is segmented into two or more segments, and a segment is not received after one of the two or more segments overlaps an idle period of any of the FFPs of the second plurality of FFPs.

22. The method of any one of claims 17-18, wherein, segmenting the uplink data into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next one of the two or more segments in a next one of the first plurality of FFPs using a wireless device initiated COT.

23. The method of any of claims 17-18, further comprising receiving (1218) an indication at a start of a COT that a wireless device has no uplink data to transmit.

24. The method of any of claims 17-18, further comprising signaling (1220) to another wireless device or network node whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

25. A network node (160) operable to operate in shared spectrum channel access, wherein, a first plurality of fixed frame periods (FFPs) is associated with a wireless device, and a second plurality of fixed frame periods (FFPs) is associated with the network node, and wherein each FFP includes an idle period with no transmissions and a channel occupancy time (COT) that allows the wireless device or the network node to transmit, the network node comprising processing circuitry (170) operable to: determine that a wireless device initiated a COT in one of the FFPs in the second plurality of FFPs; and receive uplink data from the wireless device from a start of the COT, wherein the first plurality of FFPs and the second plurality of FFPs are not aligned in a time domain, and segmenting the uplink data into two or more segments, and not receiving a segment that overlaps an idle period of any of the FFPs in the second plurality of FFPs.

26. The network node of claim 25, the processing circuitry further operable to transmit an indication that the wireless device can initiate a COT in one of the FFPs in the first plurality of FFPs.

27. The network node of any of claims 25-26, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in a time domain, and not receiving uplink data in an idle period of any of the FFPs in the second plurality of FFPs.

28. The network node of any of claims 25-26, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in a time domain, and segmenting the uplink data into two or more segments, and not receiving all of the two or more segments if any of the two or more segments overlap an idle period of any of the FFPs in the second plurality of FFPs.

29. The network node of any of claims 25-26, wherein, the first plurality of FFPs and the second plurality of FFPs are not aligned in a time domain, and segmenting the uplink data into two or more segments, and not receiving a segment after one of the two or more segments overlaps an idle period of any of the FFPs in the second plurality of FFPs.

30. The network node of any of claims 25-26, wherein, segmenting the uplink data into two or more segments, and one of the two or more segments includes an indication that the wireless device will transmit a next segment of the two or more segments in a next FFP of the first plurality of FFPs using a wireless device initiated COT.

31. The network node of any of claims 25-26, the processing circuitry further operable to receive an indication at a start of a COT that a wireless device has no uplink data to transmit.

32. The network node of any of claims 25-26, the processing circuitry further operable to signal to another wireless device or network node whether the wireless device was able to successfully obtain a COT for a wireless device initiated COT.

Images