WO2023141966A1

WO2023141966A1 - Ntn gnss measurement gap configuration

Info

Publication number: WO2023141966A1
Application number: PCT/CN2022/074681
Authority: WO
Inventors: Zhi YAN; Hongmei Liu; Yuantao Zhang; Haiming Wang
Original assignee: Lenovo Beijing Ltd
Current assignee: Lenovo Beijing Ltd
Priority date: 2022-01-28
Filing date: 2022-01-28
Publication date: 2023-08-03
Anticipated expiration: 2024-07-28

Abstract

Methods and apparatuses for NTN GNSS measurement gap configuration are disclosed. In one embodiment, a UE comprises a transceiver; and a processor, wherein the processor is configured to transmit, via the transceiver, first UL data; and insert a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

Description

NTN GNSS MEASUREMENT GAP CONFIGURATION

FIELD

The subject matter disclosed herein generally relates to wireless communications, and more particularly relates to methods and apparatuses for NTN GNSS measurement gap configuration.

BACKGROUND

The following abbreviations are herewith defined, at least some of which are referred to in the following description: New Radio (NR) , Very Large Scale Integration (VLSI) , Random Access Memory (RAM) , Read-Only Memory (ROM) , Erasable Programmable Read-Only Memory (EPROM or Flash Memory) , Compact Disc Read-Only Memory (CD-ROM) , Local Area Network (LAN) , Wide Area Network (WAN) , User Equipment (UE) , Evolved Node B (eNB) , Next Generation Node B (gNB) , Uplink (UL) , Downlink (DL) , Central Processing Unit (CPU) , Graphics Processing Unit (GPU) , Field Programmable Gate Array (FPGA) , Orthogonal Frequency Division Multiplexing (OFDM) , Radio Resource Control (RRC) , User Entity/Equipment (Mobile Terminal) , Internet-of-Things (IoT) , Narrowband Internet-of-Things (NB-IoT or NBIoT) , Downlink control information (DCI) , Physical Uplink Shared Channel (PUSCH) , NBIoT PUSCH (NPUSCH) , Physical Downlink Control Channel (PDCCH) , NBIoT PDCCH (NPDCCH) , NBIoT PDSCH (NPDSCH) , Hybrid Automatic Repeat reQuest (HARQ) , receiver and transmitter distance (RTD) , non-terrestrial networks (NTN) , global navigation satellite system (GNSS) , timing advance (TA) , low earth orbit (LEO) , geostationary earth orbit (GEO) , Frequency Time Division Duplex (FDD) , Half duplex Frequency Time Division Duplex (HD-FDD) , uplink transmission gap (UTG) , random access channel (RACH) , NBIoT physical RACH (NPRACH) , Primary Synchronization Signal (PSS) , Secondary Synchronization Signal (SSS) , Physical Broadcast Channel (PBCH) .

For NBIoT, DCI Format N0 (referred to as DCI N0 hereinafter) is used to trigger an NPUSCH (NBIoT Physical Uplink Shared Channel) format 1 uplink transmission. When an NBIoT UE (user equipment) receives a DCI N0 carried in NPDCCH (NBIoT Physical Downlink Control Channel) at time slot n (hereinafter, time slot is referred to as subframe) , the DCI N0 schedules the NPUSCH format 1 uplink transmission at subframe n + k. It means that the scheduling delay of the NPUSCH format 1 uplink transmission is k counted from the end of NPDCCH carrying DCI N0.

When the maximum HARQ process number is equal to 1, the NPDCCH search space constraint is described as follows:

If the NBIoT UE detects NPDCCH with DCI Format N0 ending in subframe n or receives a NPDSCH carrying a random access response grant ending in subframe n, and if the corresponding NPUSCH format 1 uplink transmission starts from subframe n+k, the UE is not required to monitor NPDCCH in any subframe starting from subframe n+1 to subframe n+k-1. As shown in Figure 1 (a) , the UE terminates NPDCCH monitoring from subframe n+1 to subframe n+k-1. In other words, subframe n+1 to subframe n+k-1 is NPDCCH monitoring termination period, during which the UE does not monitor NPDCCH.

When the maximum HARQ process number is equal to 2, the NPDCCH search space constraint is described as follows:

If the NBIoT UE detects NPDCCH with DCI N0 ending in subframe n, and if the corresponding NPUSCH format 1 transmission starts from subframe n+k, the UE is not required to monitor an NPDCCH candidate in two subframes starting from subframe n+k-2 to subframe n+k-1. When the maximum HARQ process number is equal to 2, the NBIoT UE has to monitor a second DCI N0 after receiving a first DCI N0. As shown in Figure 1 (b) , if the NBIoT UE detects NPDCCH with DCI N0 (e.g. the first DCI N0) ending in subframe n, and if the corresponding NPUSCH format 1 uplink transmission starts from n+k, the UE is required to monitor an NPDCCH candidate (for the second DCI N0) in subframes starting from subframe n+1 (the next subframe of the end subframe of DCI reception) to subframe n+k-3 (three subframes before the start subframe of uplink (NPUSCH) transmission) , and is not required to monitor the NPDCCH candidate in subframes starting from subframe n+k-2 to subframe n+k-1.

In NBIoT Release 16, for NPUSCH, when a coded data is transmitted from the remote unit (e.g. UE) to the base unit (e.g. eNB) , it is mapped to one or more resource units (N _RU) , each of which is transmitted a number of times (i.e. repetitions) (N _Rep) .

Table 1 indicates the number of resource units (N _RU) being determined by the resource assignment (I _RU) for NPUSCH. The resource assignment (I _RU) is indicated with 3 bits by the corresponding control signal (e.g., DCI format N0) . The resource unit for NPUSCH is determined by the subcarrier spacing of the NPUSCH data.

Table 1

Table 2 indicates the repetition number (N _Rep) being determined by repetition number index (I _Rep) for NPUSCH. The repetition number index (I _Rep) for NPUSCH is indicated with 3 bits by the corresponding control signal (e.g., DCI format N0) .

Table 2

The subcarriers to be used for NPUSCH data transmission are different for different subcarrier spacings. For subcarrier spacing of 3.75KHz, only single-tone

is supported. For subcarrier spacing of 15KHz, both single-tone and multiple-tone are supported. One or three or six or twelve of twelve subcarriers (

or 3 or 6 or 12) is used within one NBIoT carrier.

In scenario of converge enhancement for NBIoT, a total duration of a NPUSCH transmission may span tens of seconds. Table 3 indicates the maximum total durations of NPUSCH transmissions. It can be seen that a NPUSCH transmission can span up to 40960ms (approximately 40s) .

Table 3

The long receiver and transmitter distance (RTD) in NTN has an impact on timing relationship of NR (New Radio) . An additional delay offset K _offset can be introduced to modify relevant timing relationships.

For example, as shown in Figure 2 (a) , for the transmission timing of DCI scheduled NPUSCH in NBIoT legacy, the UE transmits the NPUSCH from subframe n + k ₀ (i.e. k = k ₀) . The scheduling delay (k ₀) between the end subframe of the DCI N0 and the start subframe of the corresponding NPUSCH (i.e. NPUSCH format 1) is indicated by DCI N0. In particular, the scheduling delay (k ₀) depends on the scheduling delay index (I _Delay) contained in the DCI N0, as shown in Table 4.

Table 4

On the other hand, as shown in Figure 2 (b) , for the transmission timing of DCI scheduled NPUSCH in NBIoT in NTN, the UE may transmit the NPUSCH from subframe n + k ₀ + K _offset (i.e. k = k ₀ + K _offset) . k ₀ is determined (or indicated) by the scheduling delay index (I _Delay) contained in DCI N0. An additional delay offset K _offset is related to the round trip distance from the UE and eNB. The additional delay offset K _offset can be configured in SIB or RRC signaling. If the UE has its location information and the earth orbit and ephemeris information, the UE can calculate the round trip delay between the eNB and the UE by itself. The earth orbit and ephemeris information (e. g GNSS information) indicate the position where the satellite is. In other words, the additional delay offset K _offset can be alternatively determined by the UE itself. The value of the additional delay offset K _offset may be determined by types of satellites. For example, if the eNB is on LEO, K _offset can be tens of milliseconds, while if the eNB is on GEO, K _offset can be hundreds of milliseconds.

As can be seen from Table 3, NPUSCH transmissions may span long time duration due to a large number of repetitions as well as due to time expansion in single subcarrier with 3.75 kHz subcarrier spacing. In HD-FDD NBIoT, it is hard to maintain 0.1ppm of frequency synchronization accuracy during long uplink transmission (e.g. with large number of repetitions) . Uplink transmission gaps for long uplink (e.g. NPUSCH or NPRACH) transmissions are introduced. During the uplink transmission gaps, the UE may switch to DL and perform time and/or frequency synchronization.

An uplink transmission with gap is defined by an uplink transmission duration (which can be referred to as UTG timer) and a transmission gap, as shown in Figure 3. The UTG timer has a period T _UTG, and the transmission gap has a length T _gap. Each uplink transmission of duration greater than or equal to T _UTG is inserted with the transmission gap after each T _UTG transmission until the uplink transmission completes. That is, the uplink data transmission is inserted with transmission gap (s) , the transmission gap is defined by the UTG timer (T _UTG) and the length (T _gap) of the transmission gap. After uplink transmission of each period T _UTG, one transmission gap with a length T _gap, during which the UE may switch to DL and perform time and/or frequency synchronization, is followed. The length of the uplink transmission duration (UTG timer) T _UTG and the length (T _gap) of the transmission gap can be in unit of millisecond (i.e. ms) . For NPUSCH, UTG timer T _UTG = 256 ms, and T _gap = 40 ms. For NPRACH, UTG timer T _UTG = 64 * (preamble duration) , and T _gap = 40 ms.

In TS 36.211 specification, UL transmission gap for NPUSCH transmission is defined as: after transmissions and/or postponements due to NPRACH of 256*30720*Ts time units (which equals to 256ms) , for frame structure type 1, a gap of 40*30720*Ts time units ( (which equals to 40ms) ) shall be inserted where the NPUSCH transmission is postponed, where a Ts time unit = 1 / (15000*2048) second (i.e. 30720*Ts = 30720/ (15000*2048) second = 1/1000 second = 1ms) .

The portion of a postponement due to NPRACH (indicated as “R” RACH resource in Figure 4) which coincides with a gap (i.e. uplink transmission gap, indicated as “GAP” in Figure 4) is counted as part of the gap. On the other hand, during the “R” RACH resource, the NPUSCH transmission is postponed. In the UL transmission gap (indicated as “GAP” in Figure 4) , the UE is not expected to monitor NPDCCH.

UL transmission gap during NPRACH transmission is defined as: for frame structure type 1, after transmissions of 4·64 (T _CP+T _SEQ) time units for NPRACH preamble formats 0 and 1, or 16·6 (T _CP+T _SEQ) time units for NPRACH preamble format 2, a gap of 40*30720*Ts time units shall be inserted, where T _CP is the time duration for transmitting cyclic prefix of preamble and T _SEQ is the time duration for transmitting preamble sequence as in TS36.211.

If the UE is configured with 2 HARQ process numbers, there is a restriction on scheduling to avoid misunderstanding of the position of the uplink transmission gap.

If the UTG timer T _UTG is configured as 256 ms, a normal uplink transmission (two NPUSCH transmissions are scheduled by two DCI format N0) is shown in Figure 5 (a) . A first DCI format N0 (DCI 0) schedules NPUSCH transmission 0, while a second DCI format N0 (DCI 1) schedules NPUSCH transmission 1. For simplicity, it is supposed that both DCI 0 and DCI 1 are transmitted in the same time slot (e.g. subframe n) . As shown in Figure 1 (b) , DCI 1 may alternatively be transmitted in any of subframes n+1 to n+k-3. For NPUSCH transmission 0 scheduled by DCI 0, the scheduling delay is 8ms, while the length of the NPUSCH transmission 0 is 56ms. For NPUSCH transmission 1 scheduled by DCI 1, the scheduling delay is 64ms, while the length of the NPUSCH transmission 1 is 256ms. When the UTG timer is configured as 256ms, there would be a transmission gap (labeled as “GAP” in Figure 5 (a) ) with a length T _gap after 256ms of transmission time (includes 56ms of NPUSCH transmission 0 and first 200ms of NPUSCH transmission 1) . The remaining 56ms of NPUSCH transmission 1 will be transmitted after the transmission gap.

However, misunderstanding of the position of the transmission gap may happen when the first DCI N0 (i.e. DCI 0) is missing (e.g. not correctly received by the UE) .

Suppose that DCI 0 schedules NPUSCH transmission 0 with a scheduling delay of 8ms and a length of 56ms, while DCI 1 schedules NPUSCH transmission 1 with a scheduling delay of 64ms and a length of 256ms. In addition, the UTG timer T _UTG is configured as 256 ms.

As shown in Figure 5 (b) , if DCI 0 is missing (not correctly received by the UE) while DCI 1 is correctly received by the UE, the UE would consider that the start of the UTG timer is the start of the NPUSCH transmission 1. As only 256ms transmission (including transmission of NPUSCH transmission 1) is scheduled, the UE would consider that there is no transmission gap. In other words, if a transmission gap exists, it is positioned after the NPUSCH transmission 1 of 256ms.

On the other hand, as shown in Figure 5 (c) , since the eNB does not know that DCI 0 is missing (not correctly received by the UE) (i.e. the eNB considers that the DCI 0 is correctly received by the UE) , the eNB would consider that the start of the UTG timer is the start of NPUSCH transmission 0. In this condition, the eNB would consider that a transmission gap with a length T _gap would be positioned 256 ms after the start of the NPUSCH transmission 0 (i.e. a 40 ms (T _gap) transmission gap would be 200ms after the start of the NPUSCH transmission 1) , and the last 56 ms of the NPUSCH transmission 1 would be transmitted after the 40 ms transmission gap.

A comparison of Figure 5 (b) and Figure 5 (c) indicates that the eNB and the UE have a misunderstanding on the position of the transmission gap (labeled as “GAP” in Figure 5(c) ) .

To avoid such misunderstanding, it is agreed that the UE does not expect to receive a second DCI Format N0 (i.e. DCI 1) before subframe n+k-2 for which the corresponding NPUSCH format 1 transmission scheduled by DCI 1 ends later than subframe n+k+255 (suppose T _UTG = 255+1) , where k = 8ms in Figures 5 (a) , 5 (b) and 5 (c) . According to this agreement, the total length of NPUSCH transmission 0 and NPUSCH transmission 1 would not be larger than 256ms (i.e. UTG timer) . Accordingly, no transmission gap would be necessary, which would guarantee no misunderstanding of the position of the transmission gap.

GNSS (global navigation satellite system) module is used for obtaining position information of UE, so that UE can calculate the positional difference between UE and satellite based on the position information of UE and the position information of the satellite broadcasted from the eNB, and accordingly estimate the TA information used for uplink transmission compensation. The GNSS information may become outdated due to UE behavior. It means that the GNSS information may be valid only within a period, which can be referred to as GNSS validity duration X. For example, if UE is static, the GNSS validity duration X can be long, while if UE is constantly moving (especially with high speed) , the GNSS validity duration X can be short. The UE autonomously determines its GNSS validity duration X and reports information associated with its GNSS validity duration to the network (e.g. gNB) via RRC signaling, where X = {10s, 20s, 30s, 40s, 50s, 60s, 5 min, 10 min, 15 min, 20 min, 25 min, 30 min, 60 min, 90 min, 120 min, infinity} . It can be seen that the GNSS validity duration X may be as small as e.g., 10s or 20s.

During NR Release 16 IoT NTN, only sporadic short transmission is supported. If GNSS becomes outdated (e.g. the GNSS validity duration is expired) , UE in RRC_CONNECTED should go back to idle mode and re-acquire a GNSS position fix in a GNSS measurement gap.

However, as described above, one PUSCH transmission may span up to 40s, that may be longer than the GNSS validity duration (e.g. when the GNSS validity duration is 10s or 20s, etc) . It means that, during the one PUSCH transmission (that may span up to 40s) , the UE is necessary to go back to idle mode and re-acquire a GNSS position fix in the GNSS measurement gap. During the GNSS measurement gap, the UE cannot perform the PUSCH transmission.

As shown in Figure 6, if GNSS measurement gap is supported for long uplink transmission, how to configure the GNSS measurement and how to handle the collision of GNSS measurement gap and legacy uplink transmission gap?

This disclosure targets the above issue, i.e. NTN GNSS measurement gap configuration.

BRIEF SUMMARY

Methods and apparatuses for NTN GNSS measurement gap configuration are disclosed.

In one embodiment, a UE comprises a transceiver; and a processor, wherein the processor is configured to transmit, via the transceiver, first UL data; and insert a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In one embodiment, the processor is further configured to insert the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In another embodiment, the processor is further configured to, in the second transmission length, insert the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In some embodiment, the first transmission length before the second gap is assumed to end when the second gap is inserted. In some embodiment, the first transmission length is counted by excluding the second gap. In some embodiment, the portion of the first gap which coincides with the second gap is counted as part of the second gap. In addition, the portion of the second gap which coincides with the first gap is counted as part of the first gap.

In some embodiment, the second transmission length is determined according to the first transmission length and the first gap length. Further, the second gap length is determined according to the first transmission length and the first gap length. The second transmission length and/or the second gap length are determined by a UE reported capability or UE reported signaling.

In some embodiment, the processor is further configured to monitor control signal in a time duration, the time duration starts from a first time offset from the end of the second gap. The first time offset may be configured with the unit of the period of control signal. The processor may be further configured to receive the control signal scheduling second UL data in the time duration, wherein the control signal indicates a second time offset of the start of transmitting the second UL data from the end of transmitting the first UL data.

In another embodiment, a method performed by a UE comprises transmitting first UL data; and inserting a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In one embodiment, a base unit comprises a transceiver; and a processor, wherein the processor is configured to receive, via the transceiver, first UL data; and determine a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In yet another embodiment, a method performed by a base unit comprises receiving first UL data; and determining a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described above will be rendered by reference to specific embodiments that are illustrated in the appended drawings. Understanding that these drawings depict only some embodiments, and are not therefore to be considered to be limiting of scope, the embodiments will be described and explained with additional specificity and detail through the use of the accompanying drawings, in which:

Figure 1 (a) illustrates a legacy DCI N0 scheduling NPUSCH transmission when maximum HARQ process number is equal to 1;

Figure 1 (b) illustrates a legacy DCI N0 scheduling NPUSCH transmission when maximum HARQ process number is equal to 2;

Figure 2 (a) illustrates a legacy scheduling delay in NBIoT;

Figure 2 (b) illustrates an updated legacy scheduling delay in NBIoT in NTN;

Figure 3 illustrates a legacy uplink transmission gap defined by a UTG timer and a length of the transmission gap;

Figure 4 illustrates the legacy uplink transmission gap with postponement of RACH resource;

Figure 5 (a) illustrates a normal uplink transmission including two scheduled NPUSCH transmissions;

Figure 5 (b) illustrates UE’s understanding when a first DCI is missed by the UE;

Figure 5 (c) illustrates eNB’s understanding when the eNB does not know that a first DCI is missed by the UE;

Figure 6 illustrates an example of collision of GNSS measurement gap and legacy uplink transmission gap;

Figure 7 (a) illustrates solution 1-1 of the first embodiment;

Figure 7 (b) illustrates solution 1-2 of the first embodiment;

Figure 7 (c) illustrates solution 2 of the first embodiment;

Figure 7 (d) illustrates solution 3 of the first embodiment;

Figure 8 illustrates solution 4 of the first embodiment;

Figure 9 illustrates an example of the second embodiment;

Figure 10 illustrates an example of the third embodiment;

Figure 11 is a schematic flow chart diagram illustrating an embodiment of a method;

Figure 12 is a schematic flow chart diagram illustrating another embodiment of a method; and

Figure 13 is a schematic block diagram illustrating apparatuses according to one embodiment.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art that certain aspects of the embodiments may be embodied as a system, apparatus, method, or program product. Accordingly, embodiments may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc. ) or an embodiment combining software and hardware aspects that may generally all be referred to herein as a “circuit” , “module” or “system” . Furthermore, embodiments may take the form of a program product embodied in one or more computer readable storage devices storing machine-readable code, computer readable code, and/or program code, referred to hereafter as “code” . The storage devices may be tangible, non-transitory, and/or non-transmission. The storage devices may not embody signals. In a certain embodiment, the storage devices only employ signals for accessing code.

Certain functional units described in this specification may be labeled as “modules” , in order to more particularly emphasize their independent implementation. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

Modules may also be implemented in code and/or software for execution by various types of processors. An identified module of code may, for instance, include one or more physical or logical blocks of executable code which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but, may include disparate instructions stored in different locations which, when joined logically together, include the module and achieve the stated purpose for the module.

Indeed, a module of code may contain a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules and may be embodied in any suitable form and organized within any suitable type of data structure. This operational data may be collected as a single data set, or may be distributed over different locations including over different computer readable storage devices. Where a module or portions of a module are implemented in software, the software portions are stored on one or more computer readable storage devices.

Any combination of one or more computer readable medium may be utilized. The computer readable medium may be a computer readable storage medium. The computer readable storage medium may be a storage device storing code. The storage device may be, for example, but need not necessarily be, an electronic, magnetic, optical, electromagnetic, infrared, holographic, micromechanical, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.

A non-exhaustive list of more specific examples of the storage device would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, random access memory (RAM) , read-only memory (ROM) , erasable programmable read-only memory (EPROM or Flash Memory) , portable compact disc read-only memory (CD-ROM) , an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this document, a computer-readable storage medium may be any tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device.

Code for carrying out operations for embodiments may include any number of lines and may be written in any combination of one or more programming languages including an object-oriented programming language such as Python, Ruby, Java, Smalltalk, C++, or the like, and conventional procedural programming languages, such as the "C" programming language, or the like, and/or machine languages such as assembly languages. The code may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the very last scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN) , or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider) .

Reference throughout this specification to “one embodiment” , “an embodiment” , or similar language means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, appearances of the phrases “in one embodiment” , “in an embodiment” , and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment, but mean “one or more but not all embodiments” unless expressly specified otherwise. The terms “including” , “comprising” , “having” , and variations thereof mean “including but are not limited to” , unless otherwise expressly specified. An enumerated listing of items does not imply that any or all of the items are mutually exclusive, otherwise unless expressly specified. The terms “a” , “an” , and “the” also refer to “one or more” unless otherwise expressly specified.

Furthermore, described features, structures, or characteristics of various embodiments may be combined in any suitable manner. In the following description, numerous specific details are provided, such as examples of programming, software modules, user selections, network transactions, database queries, database structures, hardware modules, hardware circuits, hardware chips, etc., to provide a thorough understanding of embodiments. One skilled in the relevant art will recognize, however, that embodiments may be practiced without one or more of the specific details, or with other methods, components, materials, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid any obscuring of aspects of an embodiment.

Aspects of different embodiments are described below with reference to schematic flowchart diagrams and/or schematic block diagrams of methods, apparatuses, systems, and program products according to embodiments. It will be understood that each block of the schematic flowchart diagrams and/or schematic block diagrams, and combinations of blocks in the schematic flowchart diagrams and/or schematic block diagrams, can be implemented by code. This code may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which are executed via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the schematic flowchart diagrams and/or schematic block diagrams for the block or blocks.

The code may also be stored in a storage device that can direct a computer, other programmable data processing apparatus, or other devices, to function in a particular manner, such that the instructions stored in the storage device produce an article of manufacture including instructions which implement the function specified in the schematic flowchart diagrams and/or schematic block diagrams block or blocks.

The code may also be loaded onto a computer, other programmable data processing apparatus, or other devices, to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the code executed on the computer or other programmable apparatus provides processes for implementing the functions specified in the flowchart and/or block diagram block or blocks.

The schematic flowchart diagrams and/or schematic block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of apparatuses, systems, methods and program products according to various embodiments. In this regard, each block in the schematic flowchart diagrams and/or schematic block diagrams may represent a module, segment, or portion of code, which includes one or more executable instructions of the code for implementing the specified logical function (s) .

It should also be noted that in some alternative implementations, the functions noted in the block may occur out of the order noted in the Figures. For example, two blocks shown in succession may substantially be executed concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. Other steps and methods may be conceived that are equivalent in function, logic, or effect to one or more blocks, or portions thereof, to the illustrated Figures.

Although various arrow types and line types may be employed in the flowchart and/or block diagrams, they are understood not to limit the scope of the corresponding embodiments. Indeed, some arrows or other connectors may be used to indicate only the logical flow of the depicted embodiment. For instance, an arrow may indicate a waiting or monitoring period of unspecified duration between enumerated steps of the depicted embodiment. It will also be noted that each block of the block diagrams and/or flowchart diagrams, and combinations of blocks in the block diagrams and/or flowchart diagrams, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and code.

The description of elements in each Figure may refer to elements of proceeding figures. Like numbers refer to like elements in all figures, including alternate embodiments of like elements.

A first embodiment relates to the configuration of the uplink transmission gap (e.g. indicated as “GAP” in Figure 6) and the GNSS measurement gap (e.g. indicated as “GNSS measurement gap” in Figure 6) .

To make clarification, some definitions are defined with reference to Figure 6 (and with reference to Figure 4) .

With reference to Figure 4, NPUSCH transmissions (each indicated as “0” ) are postponed due to RACH resource (each indicated as “R” ) . Accordingly, NPUSCH transmissions and postponement (s) due to RACH resource, before each “GAP” indicated in Figure 4, can be collectively referred to as first transmission length (e.g. UTG timer = 256ms in Figure 4) . For preamble transmission, since there is no postponement due to RACH resource, the preamble transmission before each “GAP” can be referred to as “first transmission length” (e.g. 64 *(preamble duration) ) . In Figure 6, postponements due to RACH resource (see “R” indicated in Figure 4) are not shown. So, the length of each indicated “0” in Figure 6 indicates the first transmission length (for both NPUSCH transmission and preamble transmission) . Each first transmission length can be alternatively represented by a first transmission timer. That is, the start of counting one first transmission length is the start or restart of the first transmission timer, and the end of counting the one first transmission length is equivalent to the expiration of the first transmission timer.

After each first transmission length, the uplink transmission gap (indicated as “GAP” in Figure 6) is referred to as the first gap. Each first gap has a first gap length. Incidentally, as shown in Figure 4, the postponements due to RACH resource are included in the first gap (i.e. counted as part of the first gap) .

The time length (indicated as “NPUSCH transmission” in Figure 6, i.e. a time period during which the GNSS information is not necessary to be updated) before each GNSS measurement gap is referred to as second transmission length. The second transmission length can be alternatively represented by a second transmission timer.

The GNSS measurement gap (indicated as “GNSS measurement gap” in Figure 6) is referred to as second gap. Each second gap has a second gap length.

Similar to the uplink transmission gap (i.e. first gap) defined in TS 36.211 described in the background part with reference to Figure 4, the GNSS measurement gap (i.e. second gap) can be defined as: after N*30720*Ts time units of transmission and/or postponement due to RACH resource and/or postponement due to a first gap (e.g. the uplink transmission gap with length of 40ms defined in TS 36.211) (or at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap) , a GNSS measurement gap (i.e. second gap) of M*30720*Ts time units shall be inserted where the transmission (e.g. NPUSCH transmission or preamble transmission) is postponed, where M and N can be configured. Since 30720*Ts time units = 1ms, M and N represent M ms and N ms. The transmission and/or postponement due to RACH resource can be indicated as the first transmission length (i.e. NPUSCH transmission and postponement due to RACH resource in the situation that the transmission is NPUSCH transmission, or preamble transmission in the situation that the transmission is preamble transmission. So, “at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap” may mean first transmission length and first gap, Incidentally, although 30720*Ts time units = 1ms is used as a unit in the above definition, other unit (s) can alternatively be used. For example, the second gap and/or the second transmission length can be measured by subframes (e.g. 1 subframe = 1ms) or frames, etc.

The second transmission length should include the first gap length. In other words, the second transmission timer should include the postponement due to the first gap.

On the other hand, the first transmission length should exclude the second gap length. In other words, the first transmission timer should exclude the postponement due to the second gap.

Depending on the time point (i.e. the end of the second transmission length) on which the second transmission timer expires and the time point (i.e. the end of the first transmission length) on which the first transmission timer expires, five solutions are proposed.

When the second transmission timer expires on a time point (i.e. depending on the end of the second transmission length) , there can be four situations:

(1) the first transmission timer is running on the time point (i.e. one first transmission length does not end on the time point) : situation of Figure 7 (a) or Figure 7 (b) ;

(2) on the time point, the first transmission timer has expired (i.e. one first transmission length has ended) and the first transmission timer is not running (or not restarted) (i.e. the counting of the next first transmission length has not started) , i.e. the time point is during one first gap: situation of Figure 7 (c) ;

(3) on the time point, the first transmission timer has expired (i.e. one first transmission length has ended) and the first transmission timer just restarts (i.e. the counting of the next first transmission length starts) , i.e. the time point is at the end of one first gap: situation of Figure 7 (d) ;

(4) the first transmission timer expires on the time point (i.e. one first transmission length ends on the time point) : situation of Figure 8.

In the first situation (i.e. the first transmission timer is running on the time point) , two solutions (solutions 1-1 and 1-2) are proposed:

Solution 1-1: as shown in Figure 7 (a) , due to the first UL data transmission is longer than the second transmission length (indicated as “NPUSCH transmission” ) , a second gap (indicated as “GNSS measurement gap” ) is inserted after each second transmission length (until the first UL data transmission is completed) . When the second gap is inserted, it is inserted within one first transmission length. After the inserted gap, the one first transmission length continues. The one first transmission length is counted by excluding the second gap (GNSS measurement gap) . That is, a first part of the one first transmission length (indicated as “0 ₁” ) is before the second gap, and a second part of the first transmission length (indicated as “0 ₂” ) is after the second gap. The sum of the length of the first part and the length of the second part is equal to the first transmission length. From another point of view, the first transmission timer (corresponding to the one first transmission length) (re) starts before the second gap, and does not end (or does not expire) when the second gap starts. After the second gap, the first transmission timer continues. The first transmission timer expires at the end of the one first transmission length (i.e. the end of the second part of the first transmission length (indicated as “0 ₂” ) ) .

Solution 1-2: as shown in Figure 7 (b) , due to the first UL data transmission is longer than the second transmission length (indicated as “NPUSCH transmission” ) , a second gap (indicated as “GNSS measurement gap” ) is inserted after each second transmission length (until the first UL data transmission is completed) . When the second gap is inserted, it is inserted within one first transmission length. After the inserted gap, the remaining first UL data transmission continues with the first transmission length being restarted to count (i.e. the first transmission timer restarts) . It means that, the first transmission length and the first gap are filled within each second transmission length, with the first transmission length being counted from the start of each second transmission length. The one first transmission length (indicated by 0’ in Figure 7 (b) ) does not end when the second gap (GNSS measurement gap) starts. After the second gap, a next first transmission length is recounted. In other words, the length of 0’ is smaller than the first transmission length. The first transmission length before the second gap is assumed to end when the second gap starts (i.e. when the second gap is inserted) . From another point of view, the first transmission timer (corresponding to 0’) (re) starts before the second gap. After the second gap, the first transmission timer restarts.

In the second situation (i.e. the time point is during one first gap) , one solution (solution 2) is proposed:

Solution 2: as shown in Figure 7 (c) , due to the first UL data transmission is longer than the second transmission length (indicated as “NPUSCH transmission” ) , a second gap (indicated as “GNSS measurement gap” ) is inserted after each second transmission length (until the first UL data transmission is completed) . When the second gap is inserted, it is inserted within one first gap. In other words, the one first gap length does not end. The portion of the first gap (including the portion of a postponement due to RACH resource within the first gap if the transmission is NPUSCH transmission) which coincides with the second gap (e.g. the portion with sloped line in Figure 7 (c) ) is counted as part of the first gap and is also counted as part of the second gap. After the second gap, the first transmission timer restarts.

In the third situation (i.e. the time point is at the end of one first gap) , one solution (solution 3) is proposed:

Solution 3: as shown in Figure 7 (d) , since the time point is at the end of one first gap, there is no coincided portion between the first gap and the second gap. After the second gap, the first transmission timer restarts. It means that the first transmission timer restarts by excluding the second gap.

In Solutions 1-1, 1-2, 2 and 3, no first transmission length ends on the time point. From another point of view, the first transmission timer does not expire on the time point on which the second transmission timer expires. It implies that no first gap is aligned with the second gap.

In the fourth situation, the first transmission timer expires on the time point on which the second transmission timer expires.

According to Solution 4, the first transmission timer can be configured to expire on the time point on which the second transmission timer expires, i.e. one first gap is aligned with one second gap (i.e. they start from the same time point) . From another point of view, one first transmission length and one second transmission length end on the same time point.

The second transmission length is N*30720*Ts time units (i.e. N ms) , i.e. the second transmission timer expires after N*30720*Ts time units (i.e. N ms) . If the second transmission length is equal to S number of the first transmission length (e.g. 256ms or 64 *(preamble duration) ) and S-1 number of the first gap (e.g. 40ms) , where S is equal to or larger than 2, the S ^th first gap is aligned with the second gap. So, for NPUSCH transmission, N can be configured as 256*S+40* (S-1) =296*S–40 (in unit of 30720*Ts, i.e. 1ms) , where S is a configurable number by higher layer signaling. S can be determined by UE reported capability. For example, S can be determined by GNSS validity duration X, e.g. S= floor ( (X-256) /296) . It means that the second transmission length is configured to be equal to or slightly smaller than the GNSS validity duration X, so that the S ^th first gap is aligned with the second gap. After the second gap, the first transmission timer restarts and, the NPUSCH transmission or postponement due to NPRACH, that is postponed by the second uplink transmission, continues. Figure 8 illustrates an example of Solution 4, in which S = 3.

For RACH transmission, N can be configured as (64*preamble duration) *S+40* (S-1) = 4*64 (T _CP+T _SEQ) *S+40* (S-1) (in unit of 30720*Ts, i.e. 1ms) .

According to Solution 4, there is no coincided portion between the first gap and the second gap, when the second gap starts (or when the second gap is inserted) .

The second gap is M*30720*Ts time units. Preferably in Solution 4, M is configured as 40*L+256* (L-1) for NPUSCH transmission, or configured as, 40*L+4*64 (T _CP+T _SEQ) * (L-1) , where L is a configurable number by higher layer signaling, e.g. L can be determined by UE reported capability.

As described in the background part, an NB-IoT UE is not required to monitor NPDCCH candidates of an NPDCCH search space during any first gap.

According to a second embodiment, UE is configured for monitoring NPDCCH during the GNSS measurement gap (i.e. the second gap) or before the restart of NPUSCH transmission. A NPDCCH monitoring duration may start from an offset from the end of the GNSS measurement gap or the start of the NPUSCH transmission.

In one embodiment, as shown in Figure 9, the second gap (i.e. GNSS measurement gap) includes a time duration for measuring GNSS (indicated as “GNSS measurement” in Figure 9) , and a NPDCCH monitoring time duration (indicated as “NPDCCH” in Figure 9) in addition to a downlink synchronization time duration (indicated as “DL SYNC/PBCH” in Figure 9) . So, it can be said that the NPDCCH monitoring time duration is during the GNSS measurement gap. As the NPUSCH transmission restarts (i.e. first transmission timer restarts) after the second gap (i.e. GNSS measurement gap) , it can also be said that the NPDCCH monitoring time duration is before the restart of NPUSCH transmission.

On the other hand, if the second gap (i.e. GNSS measurement gap) only refers to the time duration for measuring GNSS (indicated as “GNSS measurement” in Figure 9) , the downlink synchronization time duration as well as the NPDCCH monitoring time duration are after the GNSS measurement gap (indicated as “GNSS measurement” in Figure 9) and before the restart of the NPUSCH transmission. In this condition, it can be said that the NPDCCH monitoring time duration is before the restart of NPUSCH transmission.

When the NPDCCH monitoring time duration is during the GNSS measurement gap, the NPDCCH monitoring duration starts from an offset (e.g. Δt) from the end of the GNSS measurement gap.

When the NPDCCH monitoring time duration is before the restart of NPUSCH transmission, the NPDCCH monitoring duration starts from an offset (e.g. Δt) from the (re) start of the NPUSCH transmission.

In the NPDCCH monitoring time duration, the PRACH order, RRC reconfiguration or new UL scheduling can be monitored.

UE may lose the DL synchronization and UL synchronization after measuring the GNSS. So, UE is expected to re-connect to network by contention-free RACH. Accordingly, the PRACH order can be monitored in the NPDCCH monitoring time duration.

After long time disconnection with network due to GNSS measurement (e.g. 1s for hot start of GNSS) , UE is expected to monitor PSS or SSS or PBCH and also monitor RRC (re) configuration, in the NPDCCH monitoring time duration.

UE is expected to perform new transmission immediately after the previous uplink transmission, which can increase peak data rate. Accordingly, new UL scheduling can be received in the NPDCCH monitoring time duration.

the NPDCCH monitoring time duration can be regarded as NPDCCH search space (or NPDCCH period) . The length of NPDCCH search space may be indicated as T=G·R _max, in which G is determined by higher layer, R _max is the maximum number of NPDCCH repetition. Accordingly, the offset (e.g. Δt) can be configured with the period of one NPDCCH repetition as a unit.

If there is no NPDCCH monitoring time duration in the GNSS measurement gap, the UE has to monitor new UL scheduling after the GNSS measurement gap (as indicated by “NPDCCH” within the dotted line of Figure 9) , which would decrease peak data rate.

Optionally, the NPDCCH monitoring time duration is only configured in the last GNSS measurement gap (i.e. the last second gap) for NPUSCH transmission.

Further optionally, UE is not expected to receive a DCI Format N0 (used to trigger an NPUSCH format 1 uplink transmission) in the GNSS measurement gap except the last GNSS measurement gap.

According to a third embodiment, the scheduling delay of a NPUSCH transmission can be counted from the end of last NPUSCH transmission.

Traditionally, the scheduling delay of an NPUSCH transmission is counted from the end the NPDCCH carrying the DCI scheduling the NPUSCH transmission. Further, the scheduling delay can be selected from {8ms, 16ms, 32ms, 64ms} (see Table 4) . So, the maximum scheduling delay is 64ms.

However, if the DCI scheduling NPUSCH transmission is carried in the NPDCCH transmitted in a GNSS measurement gap, the previously scheduled NPUSCH transmission may have not been completed. It means that, if the scheduling delay is counted from the end of NPDCCH, the traditional scheduling delay (e.g. indicated in Figure 10) may be larger than 64ms, which would cause incapability of scheduling.

According to the third embodiment, the scheduling delay is counted from the end of the last scheduled NPUSCH transmission (e.g. the last scheduled PUSCH transmission that has not been completed) . In addition, the scheduling delay counted from the end of the last scheduled NPUSCH transmission can be selected from {0ms, 8ms, 16ms, 32ms} .

As shown in Figure 10, when the DCI scheduling NPUSCH transmission 1 is carried in NPDCCH in the GNSS measurement gap (while the previously scheduled NPUSCH transmission 0 has not been completed) , the scheduling delay of the scheduled NPUSCH transmission 1 can be counted from the end of the previously scheduled NPUSCH transmission 0.

The reason why the scheduling delay of a NPUSCH transmission can be counted from the end of last NPUSCH transmission (e.g. the last scheduled NPUSCH transmission that has not been completed) is because it is definite that the DCI scheduling the last scheduled NPUSCH transmission is not missing (due to the fact that the last scheduled NPUSCH transmission is ongoing (has not been completed) ) . So, no misunderstanding that described with respect to Figures 5 (a) to 5 (c) would happen.

Figure 11 is a schematic flow chart diagram illustrating an embodiment of a method 1100 according to the present application. In some embodiments, the method 1100 is performed by an apparatus, such as a remote unit (e.g. UE) . In certain embodiments, the method 1100 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 1100 is a method of a UE, comprising: 1102 transmitting first UL data; and 1104 inserting a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In one embodiment, the method further comprises inserting the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In another embodiment, the method further comprises, in the second transmission length, inserting the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In some embodiment, the method further comprises monitoring control signal in a time duration, the time duration starts from a first time offset from the end of the second gap. The first time offset may be configured with the unit of the period of control signal. The method may further comprise receiving the control signal scheduling second UL data in the time duration, wherein the control signal indicates a second time offset of the start of transmitting the second UL data from the end of transmitting the first UL data.

Figure 12 is a schematic flow chart diagram illustrating a further embodiment of a method 1200 according to the present application. In some embodiments, the method 1200 is performed by an apparatus, such as a base unit. In certain embodiments, the method 1200 may be performed by a processor executing program code, for example, a microcontroller, a microprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, or the like.

The method 1200 may comprise 1202 receiving first UL data; and 1204 determining a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In one embodiment, the method further comprises determining the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In another embodiment, the method further comprises, in the second transmission length, determining the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In some embodiment, the first transmission length before the second gap is assumed to end when the second gap is determined. In some embodiment, the first transmission length is counted by excluding the second gap. In some embodiment, the portion of the first gap which coincides with the second gap is counted as part of the second gap. In addition, the portion of the second gap which coincides with the first gap is counted as part of the first gap.

In some embodiment, the method further comprises transmitting a control signal in a time duration, the time duration starts from a first time offset from the end of the second gap. The first time offset may be configured with the unit of the period of control signal. The control signal schedules second UL data and indicates a second time offset of the start of transmitting the second UL data from the end of transmitting the first UL data.

Referring to Figure 13, the UE (i.e. the remote unit) includes a processor, a memory, and a transceiver. The processor implements a function, a process, and/or a method which are proposed in Figure 11.

The UE comprises a transceiver; and a processor, wherein the processor is configured to transmit, via the transceiver, first UL data; and insert a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

The eNB (i.e. base unit) includes a processor, a memory, and a transceiver. The processors implement a function, a process, and/or a method which are proposed in Figure 12.

The base unit comprises a transceiver; and a processor, wherein the processor is configured to receive, via the transceiver, first UL data; and determine a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.

In one embodiment, the processor is further configured to determine the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In another embodiment, the processor is further configured to, in the second transmission length, determine the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.

In some embodiment, the processor is further configured to transmit a control signal in a time duration, the time duration starts from a first time offset from the end of the second gap. The first time offset may be configured with the unit of the period of control signal. The control signal schedules second UL data and indicates a second time offset of the start of transmitting the second UL data from the end of transmitting the first UL data.

Layers of a radio interface protocol may be implemented by the processors. The memories are connected with the processors to store various pieces of information for driving the processors. The transceivers are connected with the processors to transmit and/or receive a radio signal. Needless to say, the transceiver may be implemented as a transmitter to transmit the radio signal and a receiver to receive the radio signal.

The memories may be positioned inside or outside the processors and connected with the processors by various well-known means.

In the embodiments described above, the components and the features of the embodiments are combined in a predetermined form. Each component or feature should be considered as an option unless otherwise expressly stated. Each component or feature may be implemented not to be associated with other components or features. Further, the embodiment may be configured by associating some components and/or features. The order of the operations described in the embodiments may be changed. Some components or features of any embodiment may be included in another embodiment or replaced with the component and the feature corresponding to another embodiment. It is apparent that the claims that are not expressly cited in the claims are combined to form an embodiment or be included in a new claim.

The embodiments may be implemented by hardware, firmware, software, or combinations thereof. In the case of implementation by hardware, according to hardware implementation, the exemplary embodiment described herein may be implemented by using one or more application-specific integrated circuits (ASICs) , digital signal processors (DSPs) , digital signal processing devices (DSPDs) , programmable logic devices (PLDs) , field programmable gate arrays (FPGAs) , processors, controllers, micro-controllers, microprocessors, and the like.

Embodiments may be practiced in other specific forms. The described embodiments are to be considered in all respects to be only illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.

Claims

A user equipment (UE) , comprising:

a transceiver; and

a processor, wherein the processor is configured to

transmit, via the transceiver, first uplink (UL) data; and

insert a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.
The UE of claim 1, wherein, the processor is further configured to

insert the first gap with a first gap length after a first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.
The UE of claim 1, wherein, the processor is further configured to

in the second transmission length, insert the first gap with a first gap length after the first transmission length, wherein the first transmission length includes at least one of the first UL data transmission, and the transmission postponement due to random access.
The UE of claim 2, wherein, the first transmission length before the second gap is assumed to end when the second gap is inserted.
The UE of claim 2, wherein, the first transmission length is counted by excluding the second gap.
The UE of claim 2, wherein, the portion of the first gap which coincides with the second gap is counted as part of the second gap.
The UE of claim 2, wherein, the portion of the second gap which coincides with the first gap is counted as part of the first gap.
The UE of claim 2, wherein, the second transmission length is determined according to the first transmission length and the first gap length.
The UE of claim 8, wherein, the second gap length is determined according to the first transmission length and the first gap length.
The UE of claim 8, wherein, the second transmission length and/or the second gap length are determined by a UE reported capability or UE reported signaling.
The UE of claim 1, wherein, the processor is further configured to

monitor control signal in a time duration, the time duration starts from a first time offset from the end of the second gap.
The UE of claim 10, wherein, the first time offset is configured with the unit of the period of control signal.
The UE of claim 10, wherein, the processor is further configured to

receive the control signal scheduling second UL data in the time duration, wherein the control signal indicates a second time offset of the start of transmitting the second UL data from the end of transmitting the first UL data.
A method performed by a user equipment (UE) , comprising:

transmitting first uplink (UL) data; and

inserting a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.
A base unit, comprising:

a transceiver; and

a processor, wherein the processor is configured to

receive, via the transceiver, first uplink (UL) data; and

determine a second gap with a second gap length after a second transmission length, wherein the second transmission length includes at least one of first UL data transmission, transmission postponement due to random access, and transmission postponement due to a first gap.