WO2022029461A1

WO2022029461A1 - Apparatus and method of physical uplink shared channel transmission

Info

Publication number: WO2022029461A1
Application number: PCT/IB2020/000812
Authority: WO
Inventors: Hao Lin
Original assignee: Orope France SARL
Current assignee: Orope France SARL
Priority date: 2020-08-05
Filing date: 2020-08-05
Publication date: 2022-02-10
Anticipated expiration: 2023-02-05

Abstract

An apparatus and a method of a physical uplink shared channel (PUSCH) transmission are provided. A method of a PUSCH transmission of a user equipment (UE) includes determining a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number to be transmitted and determining a second PUSCH transmission corresponding to a second TB of the HARQ process number to be transmitted, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission. This can 5 increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

Description

APPARATUS AND METHOD OF PHYSICAL UPLINK SHARED CHANNEL TRANSMISSION

BACKGROUND OF DISCLOSURE

1. Field of the Disclosure

[0001] The present disclosure relates to the field of communication systems, and more particularly, to an apparatus (such as a user equipment (UE) and/or a base station) and a method of a physical uplink shared channel (PUSCH) transmission in a non-terrestrial network (NTN), which can provide a good communication performance and high reliability.

2. Description of the Related Art

[0002] Non-terrestrial networks (NTNs) refer to networks, or segments of networks, using a spaceborne vehicle or an airborne vehicle for transmission. Spaceborne vehicles include satellites including low earth orbiting (LEO) satellites, medium earth orbiting (MEO) satellites, geostationary earth orbiting (GEO) satellites, and highly elliptical orbiting (HEO) satellites. Airborne vehicles include high altitude platforms (HAPs) encompassing unmanned aircraft systems (UAS) including lighter than air (LTA) unmanned aerial systems (UAS) and heavier than air (HTA) UAS, all operating in altitudes typically between 8 and 50 km, quasi-stationary.

[0003] Communication via a satellite is an interesting means thanks to its well-known coverage, which can bring the coverage to locations that normally cellular operators are not willing to deploy either due to non-stable crowd potential client, e.g. extreme rural, or due to high deployment cost, e.g. middle of ocean or mountain peak. Nowadays, the satellite communication is a separate technology to a 3rd generation partnership project (3GPP) cellular technology. Coming to 5G era, these two technologies can merge together, i.e. we can imagine having a 5G terminal that can access to a cellular network and a satellite network. The NTN can be good candidate technology for this purpose. It is to be designed based on 3GPP new radio (NR) with necessary enhancement. In NTN system, due to the very long round trip time between the satellite and the user equipment, the transmission throughput is limited.

[0004] Therefore, there is a need for an apparatus (such as a user equipment (UE) and/or a base station) and a method of a physical uplink shared channel (PUSCH) transmission, which can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

SUMMARY

[0005] An object of the present disclosure is to propose an apparatus (such as a user equipment (UE) and/or a base station) and a method of a physical uplink shared channel (PUSCH) transmission, which can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

[0006] In a first aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a user equipment comprises determining a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number to be transmitted and determining a second PUSCH transmission corresponding to a second TB of the HARQ process number to be transmitted, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

[0007] In a second aspect of the present disclosure, a user equipment of a physical uplink shared channel (PUSCH) transmission comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to determine a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number to be transmitted and determine a second PUSCH transmission corresponding to a second TB of the HARQ process number to be transmitted, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

[0008] In a third aspect of the present disclosure, a method of a physical uplink shared channel (PUSCH) transmission of a base station comprises determining a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number to be received and determining a second PUSCH transmission corresponding to a second TB of the HARQ process number to be received, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

[0009] In a fourth aspect of the present disclosure, a base station of communication comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to determine a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number to be received and determine a second PUSCH transmission corresponding to a second TB of the HARQ process number to be received, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

[0010] In a fifth aspect of the present disclosure, a non-transitory machine-readable storage medium has stored thereon instructions that, when executed by a computer, cause the computer to perform the above method.

[0011] In a sixth aspect of the present disclosure, a chip includes a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the above method.

[0012] In a seventh aspect of the present disclosure, a computer readable storage medium, in which a computer program is stored, causes a computer to execute the above method.

[0013] In an eighth aspect of the present disclosure, a computer program product includes a computer program, and the computer program causes a computer to execute the above method.

[0014] In a ninth aspect of the present disclosure, a computer program causes a computer to execute the above method.

BRIEF DESCRIPTION OF DRAWINGS

[0015] In order to more clearly illustrate the embodiments of the present disclosure or related art, the following figures will be described in the embodiments are briefly introduced. It is obvious that the drawings are merely some embodiments of the present disclosure, a person having ordinary skill in this field can obtain other figures according to these figures without paying the premise.

[0016] FIG. 1 is a block diagram of one or more user equipments (UEs) and a base station (e.g., gNB) of communication in a communication network system (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure.

[0017] FIG. 2 is a flowchart illustrating a method of a physical uplink shared channel (PUSCH) transmission of a user equipment in a non-terrestrial network (NTN) according to an embodiment of the present disclosure.

[0018] FIG. 3 is a flowchart illustrating a method of a physical uplink shared channel (PUSCH) transmission of a base station in a non-terrestrial network (NTN) according to an embodiment of the present disclosure.

[0019] FIG. 4 is a schematic diagram illustrating a communication system including a base station (BS) and a UE according to an embodiment of the present disclosure.

[0020] FIG. 5 is a schematic diagram illustrating that a BS transmits 3 beams to the ground forming 3 footprints according to an embodiment of the present disclosure.

[0021] FIG. 6 is a schematic diagram illustrating a method of a physical uplink shared channel (PUSCH) transmission according to an embodiment of the present disclosure. [0022] FIG. 7 is a schematic diagram illustrating a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure.

[0023] FIG. 8 is a schematic diagram illustrating a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure.

[0024] FIG. 9 is a schematic diagram illustrating a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure.

[0025] FIG. 10 is a schematic diagram illustrating a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure.

[0026] FIG. 11 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure.

DETAILED DESCRIPTION OF EMBODIMENTS

[0027] Embodiments of the present disclosure are described in detail with the technical matters, structural features, achieved objects, and effects with reference to the accompanying drawings as follows. Specifically, the terminologies in the embodiments of the present disclosure are merely for describing the purpose of the certain embodiment, but not to limit the disclosure.

[0028] FIG. 1 illustrates that, in some embodiments, one or more user equipments (UEs) 10 and a base station (e.g., gNB) 20 for transmission adjustment in a communication network system 30 (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure are provided. The communication network system 30 includes the one or more UEs 10 and the base station 20. The one or more UEs 10 may include a memory 12, a transceiver 13, and a processor 11 coupled to the memory 12, the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22, the transceiver 23. The processor 11 or 21 may be configured to implement proposed functions, procedures and/or methods described in this description. Layers of radio interface protocol may be implemented in the processor 11 or 21. The memory 12 or 22 is operatively coupled with the processor 11 or 21 and stores a variety of information to operate the processor 11 or 21. The transceiver 13 or 23 is operatively coupled with the processor 11 or 21, and the transceiver 13 or 23 transmits and/or receives a radio signal.

[0029] The processor 11 or 21 may include application-specific integrated circuit (ASIC), other chipset, logic circuit and/or data processing device. The memory 12 or 22 may include read-only memory (ROM), random access memory (RAM), flash memory, memory card, storage medium and/or other storage device. The transceiver 13 or 23 may include baseband circuitry to process radio frequency signals. When the embodiments are implemented in software, the techniques described herein can be implemented with modules (e.g., procedures, functions, and so on) that perform the functions described herein. The modules can be stored in the memory 12 or 22 and executed by the processor 11 or 21. The memory 12 or 22 can be implemented within the processor 11 or 21 or external to the processor 11 or 21 in which case those can be communicatively coupled to the processor 11 or 21 via various means as is known in the art.

[0030] In some embodiments, the communication between the UE 10 and the BS 20 comprises non-terrestrial network (NTN) communication. In some embodiments, the base station 20 comprises spaceborne platform or airborne platform or high altitude platform station.

[0031] In the present disclosure, some embodiments present a method to increase a transmission throughput that resolve a bottleneck due to a long round trip time (RRT). The method is to enable a so-called hybrid automatic repeat request (HARQ) disabling, which allows the base station 20 consecutively schedule multiple physical uplink shared channels (PUSCHs) that correspond to a same HARQ process number. However, if service requires a higher reliable transmission, an incremental redundancy should be ensured at the UE side, for which the HARQ retransmission should be redesigned taking into account the RRT. In the present disclosure, some embodiments present some methods for the UE 10 to transmit PUSCHs, which satisfy the above two objectives.

[0032] In some embodiments, the transceiver 13 is configured by the base station 20 to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number and transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

[0033] In some embodiments, the processor 21 is configured the UE 10 to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number and transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

[0034] FIG. 2 illustrates a method 200 of a physical uplink shared channel (PUSCH) transmission of a UE in a communication network system (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 200 includes: a block 202, the UE being configured by a base station to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and a block 204, the UE being configured by the base station to transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

[0035] FIG. 3 illustrates a method 300 of a physical uplink shared channel (PUSCH) transmission of a BS in a communication network system (e.g., non-terrestrial network (NTN)) according to an embodiment of the present disclosure. In some embodiments, the method 300 includes: a block 302, configuring a user equipment (UE) to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and a block 304, configuring the UE to transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission. This can solve issues in the prior art, increase a transmission throughput that can resolve a bottleneck due to a long round trip time, and/or provide a good communication performance and high reliability.

[0036] In some embodiments, the first PUSCH transmission is scheduled by a first downlink control information (DCI), or a configured grant. In some embodiments, the second PUSCH transmission is scheduled by a second DCI or a configured grant. In some embodiments, the second DCI is received to be at least the time interval after the first PUSCH transmission. In some embodiments, the time interval is relevant to at least one of the followings: a timing advance, a first offset for uplink resource determination, a round trip time, or a second offset between downlink uplink timing relationship. In some embodiments, the second PUSCH transmission starts at least the time interval after a last symbol of the first PUSCH transmission.

[0037] In some embodiments, the time interval starts after a last symbol of the first PUSCH transmission in an uplink frame timing. In some embodiments, an ending location of the time interval is relevant to a last symbol of a PUSCH resource for the first PUSCH transmission in a downlink frame timing. In some embodiments, the uplink frame timing and the downlink frame timing are at a UE side of the UE. In some embodiments, for a given frame number, the uplink frame timing starts earlier than the corresponding downlink frame timing by the second offset between downlink uplink timing relationship. In some embodiments, the PUSCH resource is obtained from at least one of the followings: the first DCI, or the configured grant, or the first offset for uplink resource determination. In some embodiments, the first offset for uplink resource determination is indicated by the first DCI and/or a third DCI and/or a radio resource control (RRC) and/or a medium access control-control element (MAC-CE) and/or a system information.

[0038] In some embodiments, the first DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2. In some embodiments, the second DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2. In some embodiments, the third DCI comprises a group-common DCI. In some embodiments, the third DCI comprises a DCI format. In some embodiments, the first DCI and/or the second DCI is transmitted in a type 3 physical downlink control channel (PDCCH) common search space set and/or in a UE-specific search space set. In some embodiments, the third DCI is transmitted in a type 3 PDCCH common search space set. In some embodiments, the DCI format of the third DCI is cyclic redundancy check (CRC) scrambled with slot format indication-radio network temporary identifier (SFI-RNTI). In some embodiments, the DCI format of the third DCI is DCI format 2_0.

[0039] In some embodiments, the first PUSCH transmission and the second PUSCH transmission are transmitted to a base station. In some embodiments, a value of the time interval is configured by the base station. In some embodiments, when the second TB of the HARQ process number is a first identity (ID) number, the time interval is configured to be zero by the base station. In some embodiments, when the second TB of the HARQ process number is a second ID number, the time interval is configured to be non-zero by the base station. In some embodiments, the first ID number and the second ID number are different. In some embodiments, the first ID number corresponds to 1 and the second ID number corresponds to 2. In some embodiments, the time interval is equal to zero.

[0040] FIG. 4 illustrates a communication system including a base station (BS) and a UE according to another embodiment of the present disclosure. Optionally, the communication system may include more than one base stations, and each of the base stations may connect to one or more UEs. In this disclosure, there is no limit. As an example, the base station illustrated in FIG. 1 may be a moving base station, e.g. spaceborne vehicle (satellite) or airborne vehicle (drone). The UE can transmit transmissions to the base station and the UE can also receive the transmission from the base station. Optionally, not shown in FIG. 4, the moving base station can also serve as a relay which relays the received transmission from the UE to a ground base station or vice versa.

[0041] Spaceborne platform includes satellite and the satellite includes LEO satellite, MEO satellite and GEO satellite. While the satellite is moving, the LEO and MEO satellite is moving with regards to a given location on earth. However, for GEO satellite, the GEO satellite is relatively static with regards to a given location on earth. A spaceborne or airborne base station (BS), e.g. in particular for LEO satellite or drone, communicates with a user equipment (UE) on the ground. The round trip time (RTT) between them is time varying due to the mobility of the base station. The RTT variation is related to the distance variation between the BS and the UE. The RTT variation rate is proportional to the BS motion velocity. To ensure a good uplink synchronization, the BS will adjust the uplink transmission timing and/or frequency for the UE.

[0042] Optionally, as illustrated in FIG. 5, where a base station is integrated in a satellite or a drone, and the base station transmits one or more beams to the ground forming one or more coverage areas called footprint. In FIG. 5, an example illustrates that the BS transmits three beams (beam 1, beam 2 and beam3) to form three footprints (footprint 1, 2 and 3), respectively. Optionally, 3 beams are transmitted at 3 different frequencies. In this example, the bit position is associated with a beam. FIG. 5 illustrates that, in some embodiments, a moving base station, e.g. in particular for LEO satellite or drone, communicates with a user equipment (UE) on the ground. Due to long distance between the UE and the base station on satellite the beamformed transmission is needed to extend the coverage. As illustrated in FIG. 5, where a base station is transmitting three beams to the earth forming three coverage areas called footpoints. Moreover, each beam may be transmitted at dedicated frequencies so that the beams for footprint 1, 2 and 3 are non-overlapped in a frequency domain.

[0043] FIG. 6 illustrates a method of a physical uplink shared channel (PUSCH) transmission according to an embodiment of the present disclosure. FIG. 6 illustrates that, in some embodiments, in NTN system, due to a very long round trip time between a satellite and a user equipment, an uplink transmission will arrive at a gNB side with propagation delay. In order to compensate this delay. An uplink frame timing can apply an offset with respect to a downlink frame timing as illustrated in FIG. 6. FIG. 6 illustrates that, in some embodiments, a UE receives a first DCI in slot i of DL frame n that schedules a first PUSCH transmission. A PUSCH resource of a first PUSCH transmission is indicated by a first DCI and/or RRC signaling. In an example as illustrated in FIG. 1, the PUSCH resource is allocated in a slot that is 27 slots after the slot i (i.e. slot i+27 slots), once the UE determines the PUSCH resource, the UE will transmit the first PUSCH transmission in the corresponding UL frame in the same slot index and frame index. In this case, there is a time interval between the slot i+27 of the UL frame and the slot i+27 of the DL frame.

[0044] FIG. 7 illustrates a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure. FIG. 7 illustrates that, in some embodiments, a PUSCH resource does not fill up all symbols in a slot. As illustrated in FIG. 7, a time interval is from the last symbol of the first PUSCH transmission in the UL frame to the last symbol of the PUSCH resource of the first PUSCH in a DL frame.

[0045] FIG. 8 illustrates a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure. FIG. 8 illustrates that, in some embodiments, a first PUSCH transmission transmitted by a UE corresponds to a HARQ process number. Then the UE is not expected to transmit a second PUSCH transmission corresponding to the same HARQ process number within a time interval, such as the example given in FIG. 8, a second PUSCH transmission corresponding to the same HARQ process number of the first PUSCH transmission is scheduled by a second DCI in slot j to allocate a PUSCH resource of the second PUSCH transmission in slot j+20. When the UE transmits the second PUSCH transmission in the UL frame in slot j+20, the second PUSCH transmission is after the time interval. The time interval is related to an offset between the DL and UL timing, which is used to absorb a round trip time (RTT) delay. In NTN system, due to high altitude of the satellite, the RTT delay is significantly larger than the traditional cellular network. Thus, if the second PUSCH transmission is transmitted within the time interval, the base station will not have enough time to process the first PUSCH, consequently, the buffer of the first PUSCH will be flushed. Limiting the second PUSCH transmission until the time interval is passed, will leave enough time for the first PUSCH transmission to arrive at the base station side and also for the PUSCH processing at the base station. This can improve transmission reliability.

[0046] FIG. 9 illustrates a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure. FIG. 9 illustrates that, in some embodiments, a first PUSCH transmission transmitted by a UE corresponds to a HARQ process number. Then the UE is not expected to transmit a second PUSCH transmission corresponding to the same HARQ process number within a time interval, such as the example given in FIG. 9, a second PUSCH transmission corresponding to the same HARQ process number of the first PUSCH transmission is scheduled by a second DCI in slot j to allocate a PUSCH resource of the second PUSCH transmission in slot j+20. When the UE transmits the second PUSCH transmission in the UL frame in slot j+20, the second DCI is after the time interval and the second PUSCH transmission is after the time interval. The time interval is related to an offset between the DL and UL timing, which is used to absorb a round trip time (RTT) delay. In NTN system, due to high altitude of the satellite, the RTT delay is significantly larger than the traditional cellular network. Thus, if the second PUSCH transmission is transmitted within the time interval, the base station will not have enough time to process the first PUSCH, consequently, the buffer of the first PUSCH will be flushed. Limiting the second PUSCH transmission until the time interval is passed, will leave enough time for the first PUSCH transmission to arrive at the base station side and also for the PUSCH processing at the base station. This can improve transmission reliability.

[0047] FIG. 10 illustrates a method of a physical uplink shared channel (PUSCH) transmission according to another embodiment of the present disclosure. FIG. 10 illustrates that, in some embodiments, a first PUSCH transmission transmitted by a UE corresponds to a HARQ process number. Then the UE is not expected to transmit a second PUSCH transmission corresponding to the same HARQ process number within the time interval, such as the example given in FIG. 10, a second PUSCH corresponding to the same HARQ process number of the first PUSCH is scheduled by a second DCI in slot i+4 to allocate a PUSCH resource of the second PUSCH in slot i+30. When the UE transmits the second PUSCH in the UE frame in slot i+30, the second PUSCH transmission is within the time interval. The advantage of this example is that the base station can directly schedule a second PUSCH without waiting after a time interval, thus, leading to an increased throughput.

[0048] In some examples, the base station can configure if the second PUSCH transmission corresponding to the same HARQ process number of the first PUSCH transmission can be transmitted within the time interval or it should be transmitted after the time interval. Optionally, the base station can configure if the second PUSCH transmission corresponding to the same HARQ process number of the first PUSCH transmission can be transmitted after the last symbol of the first PUSCH transmission in UL frame timing, or after the last symbol of the resource for the first PUSCH transmission in the DL frame timing. Optionally, the base station can configure a first HARQ process number. If a first PUSCH transmission is corresponding to the first HARQ process number, the UE can expect to transmit a second PUSCH transmission corresponding to the first HARQ process number after the last symbol of the PUSCH in the UL frame timing. If a first PUSCH transmission is corresponding to a second HARQ process number, where the second HARQ process number is different from the first HARQ process number, the UE expects to transmit a second PUSCH transmission corresponding to the second HARQ process number after the last symbol of the PUSCH resource of the first PUSCH transmission in the DL frame timing.

[0049] Commercial interests for some embodiments are as follows. 1. solving issues in the prior art. 2. increasing a transmission throughput that can resolve a bottleneck due to a long round trip time. 3. providing a good communication performance. 4. providing a high reliability. 5. Some embodiments of the present disclosure are used by 5G-NR chipset vendors, V2X communication system development vendors, automakers including cars, trains, trucks, buses, bicycles, moto-bikes, helmets, and etc., drones (unmanned aerial vehicles), smartphone makers, communication devices for public safety use, AR/VR device maker for example gaming, conference/seminar, education purposes. Some embodiments of the present disclosure are a combination of “techniques/processes” that can be adopted in 3GPP specification to create an end product. Some embodiments of the present disclosure could be adopted in the 5G NR unlicensed band communications. Some embodiments of the present disclosure propose technical mechanisms.

[0050] FIG. 11 is a block diagram of an example system 700 for wireless communication according to an embodiment of the present disclosure. Embodiments described herein may be implemented into the system using any suitably configured hardware and/or software. FIG. 11 illustrates the system 700 including a radio frequency (RF) circuitry 710, a baseband circuitry 720, an application circuitry 730, a memory/ storage 740, a display 750, a camera 760, a sensor 770, and an input/output (I/O) interface 780, coupled with each other at least as illustrated. The application circuitry 730 may include a circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors, such as graphics processors, application processors. The processors may be coupled with the memory/storage and configured to execute instructions stored in the memory/storage to enable various applications and/or operating systems running on the system. [0051] The baseband circuitry 720 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processors may include a baseband processor. The baseband circuitry may handle various radio control functions that enables communication with one or more radio networks via the RF circuitry. The radio control functions may include, but are not limited to, signal modulation, encoding, decoding, radio frequency shifting, etc. In some embodiments, the baseband circuitry may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[0052] In various embodiments, the baseband circuitry 720 may include circuitry to operate with signals that are not strictly considered as being in a baseband frequency. For example, in some embodiments, baseband circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency. The RF circuitry 710 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. In various embodiments, the RF circuitry 710 may include circuitry to operate with signals that are not strictly considered as being in a radio frequency. For example, in some embodiments, RF circuitry may include circuitry to operate with signals having an intermediate frequency, which is between a baseband frequency and a radio frequency.

[0053] In various embodiments, the transmitter circuitry, control circuitry, or receiver circuitry discussed above with respect to the user equipment, eNB, or gNB may be embodied in whole or in part in one or more of the RF circuitry, the baseband circuitry, and/or the application circuitry. As used herein, “circuitry” may refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or a memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some embodiments, the electronic device circuitry may be implemented in, or functions associated with the circuitry may be implemented by, one or more software or firmware modules. In some embodiments, some or all of the constituent components of the baseband circuitry, the application circuitry, and/or the memory/storage may be implemented together on a system on a chip (SOC). The memory/storage 740 may be used to load and store data and/or instructions, for example, for system. The memory/storage for one embodiment may include any combination of suitable volatile memory, such as dynamic random access memory (DRAM)), and/or non-volatile memory, such as flash memory.

[0054] In various embodiments, the I/O interface 780 may include one or more user interfaces designed to enable user interaction with the system and/or peripheral component interfaces designed to enable peripheral component interaction with the system. User interfaces may include, but are not limited to a physical keyboard or keypad, a touchpad, a speaker, a microphone, etc. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a universal serial bus (USB) port, an audio jack, and a power supply interface. In various embodiments, the sensor 770 may include one or more sensing devices to determine environmental conditions and/or location information related to the system. In some embodiments, the sensors may include, but are not limited to, a gyro sensor, an accelerometer, a proximity sensor, an ambient light sensor, and a positioning unit. The positioning unit may also be part of, or interact with, the baseband circuitry and/or RF circuitry to communicate with components of a positioning network, e.g., a global positioning system (GPS) satellite. [0055] In various embodiments, the display 750 may include a display, such as a liquid crystal display and a touch screen display. In various embodiments, the system 700 may be a mobile computing device such as, but not limited to, a laptop computing device, a tablet computing device, a netbook, an ultrabook, a smartphone, a AR/VR glasses, etc. In various embodiments, system may have more or less components, and/or different architectures. Where appropriate, methods described herein may be implemented as a computer program. The computer program may be stored on a storage medium, such as a non-transitory storage medium.

[0056] A person having ordinary skill in the art understands that each of the units, algorithm, and steps described and disclosed in the embodiments of the present disclosure are realized using electronic hardware or combinations of software for computers and electronic hardware. Whether the functions run in hardware or software depends on the condition of application and design requirement for a technical plan. A person having ordinary skill in the art can use different ways to realize the function for each specific application while such realizations should not go beyond the scope of the present disclosure. It is understood by a person having ordinary skill in the art that he/she can refer to the working processes of the system, device, and unit in the above-mentioned embodiment since the working processes of the above-mentioned system, device, and unit are basically the same. For easy description and simplicity, these working processes will not be detailed.

[0057] It is understood that the disclosed system, device, and method in the embodiments of the present disclosure can be realized with other ways. The above-mentioned embodiments are exemplary only. The division of the units is merely based on logical functions while other divisions exist in realization. It is possible that a plurality of units or components are combined or integrated in another system. It is also possible that some characteristics are omitted or skipped. On the other hand, the displayed or discussed mutual coupling, direct coupling, or communicative coupling operate through some ports, devices, or units whether indirectly or communicatively by ways of electrical, mechanical, or other kinds of forms.

[0058] The units as separating components for explanation are or are not physically separated. The units for display are or are not physical units, that is, located in one place or distributed on a plurality of network units. Some or all of the units are used according to the purposes of the embodiments. Moreover, each of the functional units in each of the embodiments can be integrated in one processing unit, physically independent, or integrated in one processing unit with two or more than two units.

[0059] If the software function unit is realized and used and sold as a product, it can be stored in a readable storage medium in a computer. Based on this understanding, the technical plan proposed by the present disclosure can be essentially or partially realized as the form of a software product. Or, one part of the technical plan beneficial to the conventional technology can be realized as the form of a software product. The software product in the computer is stored in a storage medium, including a plurality of commands for a computational device (such as a personal computer, a server, or a network device) to run all or some of the steps disclosed by the embodiments of the present disclosure. The storage medium includes a USB disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a floppy disk, or other kinds of media capable of storing program codes.

[0060] While the present disclosure has been described in connection with what is considered the most practical and preferred embodiments, it is understood that the present disclosure is not limited to the disclosed embodiments but is intended to cover various arrangements made without departing from the scope of the broadest interpretation of the appended claims.

Claims

What is claimed is:

1. A method of a physical uplink shared channel (PUSCH) transmission of a user equipment (UE), comprising: the UE being configured by a base station to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and the UE being configured by the base station to transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

2. The method of claim 1, wherein the first PUSCH transmission is scheduled by a first downlink control information (DCI), or a configured grant.

3. The method of claim 1 or 2, wherein the second PUSCH transmission is scheduled by a second DCI or a configured grant.

4. The method of claim 3, wherein the second DCI is received to be at least the time interval after the first PUSCH transmission.

5. The method of any one of claims 1 to 4, wherein the time interval is relevant to at least one of the followings: a timing advance, a first offset for uplink resource determination, a round trip time, or a second offset between downlink uplink timing relationship.

6. The method of any one of claims 1 to 5, wherein the second PUSCH transmission starts at least the time interval after a last symbol of the first PUSCH transmission.

7. The method of any one of claims 1 to 6, wherein the time interval starts after a last symbol of the first PUSCH transmission in an uplink frame timing.

8. The method of any one of claims 1 to 7, wherein an ending location of the time interval is relevant to a last symbol of a PUSCH resource for the first PUSCH transmission in a downlink frame timing.

9. The method of claim 8, wherein the uplink frame timing and the downlink frame timing are at a UE side of the UE.

10. The method of claim 8 or 9, wherein for a given frame number, the uplink frame timing starts earlier than the corresponding downlink frame timing by the second offset between downlink uplink timing relationship.

11. The method of any one of claims 8 to 10, wherein the PUSCH resource is obtained from at least one of the followings: the first DCI, or the configured grant, or the first offset for uplink resource determination.

12. The method of any one of claims 5 to 11, wherein the first offset for uplink resource determination is indicated by the first DCI and/or a third DCI and/or a radio resource control (RRC) and/or a medium access control-control element (MAC-CE) and/or a system information.

13. The method of any one of claims 2 to 12, wherein the first DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

14. The method of any one of claims 3 to 13, wherein the second DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

15. The method of any one of claims 12 to 14, wherein the third DCI comprises a group-common DCI.

16. The method of any one of claims 12 to 15, wherein the third DCI comprises a DCI format.

17. The method of any one of claims 3 to 16, wherein the first DCI and/or the second DCI is transmitted in a type 3 physical downlink control channel (PDCCH) common search space set and/or in a UE-specific search space set.

18. The method of any one of claims 12 to 17, wherein the third DCI is transmitted in a type 3 PDCCH common search space set.

19. The method of any one of claims 16 to 18, wherein the DCI format of the third DCI is cyclic redundancy check (CRC) scrambled with slot format indication-radio network temporary identifier (SFI-RNTI).

20. The method of any one of claims 16 to 19, wherein the DCI format of the third DCI is DCI format 2_0.

21. The method of any one of claims 1 to 20, wherein the first PUSCH transmission and the second PUSCH transmission are transmitted to the base station.

22. The method of any one of claims 1 to 21, wherein a value of the time interval is configured by the base station.

23. The method of claim 22, wherein when the second TB of the HARQ process number is a first identity (ID) number, the time interval is configured to be zero by the base station.

24. The method of claim 23, wherein when the second TB of the HARQ process number is a second ID number, the time interval is configured to be non-zero by the base station.

25. The method of claim 24, wherein the first ID number and the second ID number are different.

26. The method of claim 25, wherein the first ID number corresponds to 1 and the second ID number corresponds to 2.

27. The method of any one of claims 1 to 22, wherein the time interval is equal to zero.

28. A user equipment (UE) of communication, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the transceiver is configured by a base station to: transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

29. The UE of claim 28, wherein the first PUSCH transmission is scheduled by a first downlink control information (DCI), or a configured grant.

30. The UE of claim 28 or 29, wherein the second PUSCH transmission is scheduled by a second DCI or a configured grant.

31. The UE of claim 30, wherein the second DCI is received to be at least the time interval after the first PUSCH transmission.

32. The UE of any one of claims 28 to 31, wherein the time interval is relevant to at least one of the followings: a timing advance, a first offset for uplink resource determination, a round trip time, or a second offset between downlink uplink timing relationship.

33. The UE of any one of claims 28 to 32, wherein the second PUSCH transmission starts at least the time interval after a last symbol of the first PUSCH transmission.

34. The UE of any one of claims 28 to 33, wherein the time interval starts after a last symbol of the first PUSCH transmission in an uplink frame timing.

35. The UE of any one of claims 28 to 34, wherein an ending location of the time interval is relevant to a last symbol of a PUSCH resource for the first PUSCH transmission in a downlink frame timing.

36. The UE of claim 35, wherein the uplink frame timing and the downlink frame timing are at a UE side of the UE.

37. The UE of claim 35 or 36, wherein for a given frame number, the uplink frame timing starts earlier than the corresponding downlink frame timing by the second offset between downlink uplink timing relationship.

38. The UE of any one of claims 35 to 37, wherein the PUSCH resource is obtained from at least one of the followings: the first DCI, or the configured grant, or the first offset for uplink resource determination.

39. The UE of any one of claims 32 to 38, wherein the first offset for uplink resource determination is indicated by the first DCI and/or a third DCI and/or a radio resource control (RRC) and/or a medium access control-control element (MAC-CE) and/or a system information.

40. The UE of any one of claims 29 to 39, wherein the first DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

41. The UE of any one of claims 30 to 40, wherein the second DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

42. The UE of any one of claims 39 to 41, wherein the third DCI comprises a group-common DCI.

43. The UE of any one of claims 39 to 42, wherein the third DCI comprises a DCI format.

44. The UE of any one of claims 30 to 43, wherein the first DCI and/or the second DCI is transmitted in a type 3 physical downlink control channel (PDCCH) common search space set and/or in a UE-specific search space set.

45. The UE of any one of claims 39 to 43, wherein the third DCI is transmitted in a type 3 PDCCH common search space set.

46. The UE of any one of claims 43 to 45, wherein the DCI format of the third DCI is cyclic redundancy check (CRC) scrambled with slot format indication-radio network temporary identifier (SFI-RNTI).

47. The UE of any one of claims 43 to 46, wherein the DCI format of the third DCI is DCI format 2_0.

48. The UE of any one of claims 28 to 47, wherein the first PUSCH transmission and the second PUSCH transmission are transmitted to the base station.

49. The UE of any one of claims 28 to 48, wherein a value of the time interval is configured by the base station.

50. The UE of claim 49, wherein when the second TB of the HARQ process number is a first identity (ID) number, the time interval is configured to be zero by the base station.

51. The UE of claim 50, wherein when the second TB of the HARQ process number is a second ID number, the time interval is configured to be non-zero by the base station.

52. The UE of claim 51, wherein the first ID number and the second ID number are different.

53. The UE of claim 52, wherein the first ID number corresponds to 1 and the second ID number corresponds to 2.

54. The UE of any one of claims 28 to 49, wherein the time interval is equal to zero.

55. A method of a physical uplink shared channel (PUSCH) transmission of a base station, comprising: configuring a user equipment (UE) to transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and configuring the UE to transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

56. The method of claim 55, wherein the first PUSCH transmission is scheduled by a first downlink control information (DCI), or a configured grant.

57. The method of claim 55 or 56, wherein the second PUSCH transmission is scheduled by a second DCI or a configured grant.

58. The method of claim 57, wherein the second DCI is transmitted to be at least the time interval after the first PUSCH transmission.

59. The method of any one of claims 55 to 58, wherein the time interval is relevant to at least one of the followings: a timing advance, a first offset for uplink resource determination, a round trip time, or a second offset between downlink uplink timing relationship.

60. The method of any one of claims 55 to 59, wherein the second PUSCH transmission starts at least the time interval after a last symbol of the first PUSCH transmission.

61. The method of any one of claims 55 to 60, wherein the time interval starts after a last symbol of the first PUSCH transmission in an uplink frame timing.

62. The method of any one of claims 55 to 61, wherein an ending location of the time interval is relevant to a last symbol of a PUSCH resource for the first PUSCH transmission in a downlink frame timing.

63. The method of claim 62, wherein the uplink frame timing and the downlink frame timing are at a UE side of the UE.

64. The method of claim 62 or 63, wherein for a given frame number, the uplink frame timing starts earlier than the corresponding downlink frame timing by the second offset between downlink uplink timing relationship.

65. The method of any one of claims 62 to 64, wherein the PUSCH resource is obtained from at least one of the followings: the first DCI, or the configured grant, or the first offset for uplink resource determination.

66. The method of any one of claims 59 to 65, wherein the first offset for uplink resource determination is indicated by the first DCI and/or a third DCI and/or a radio resource control (RRC) and/or a medium access control-control element (MAC-CE) and/or a system information.

67. The method of any one of claims 56 to 66, wherein the first DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

68. The method of any one of claims 57 to 67, wherein the second DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

69. The method of any one of claims 66 to 68, wherein the third DCI comprises a group-common DCI.

70. The method of any one of claims 66 to 69, wherein the third DCI comprises a DCI format.

71. The method of any one of claims 57 to 70, wherein the first DCI and/or the second DCI is transmitted in a type 3 physical downlink control channel (PDCCH) common search space set and/or in a UE-specific search space set.

72. The method of any one of claims 66 to 71, wherein the third DCI is transmitted in a type 3 PDCCH common search space set.

73. The method of any one of claims 70 to 72, wherein the DCI format of the third DCI is cyclic redundancy check (CRC) scrambled with slot format indication-radio network temporary identifier (SFI-RNTI).

74. The method of any one of claims 70 to 73, wherein the DCI format of the third DCI is DCI format 2_0.

75. The method of any one of claims 55 to 74, wherein the first PUSCH transmission and the second PUSCH transmission are transmitted to the base station.

76. The method of any one of claims 55 to 75, wherein a value of the time interval is configured by the base station.

77. The method of claim 76, wherein when the second TB of the HARQ process number is a first identity (ID) number, the time interval is configured to be zero by the base station.

78. The method of claim 77, wherein when the second TB of the HARQ process number is a second ID number, the time interval is configured to be non-zero by the base station.

79. The method of claim 78, wherein the first ID number and the second ID number are different.

80. The method of claim 79, wherein the first ID number corresponds to 1 and the second ID number corresponds to 2.

81. The method of any one of claims 55 to 76, wherein the time interval is equal to zero.

82. A base station of communication, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured a user equipment (UE) to: transmit a first PUSCH transmission corresponding to a first transport block (TB) of a hybrid automatic repeat request (HARQ) process number; and transmit a second PUSCH transmission corresponding to a second TB of the HARQ process number, wherein the second PUSCH transmission is performed to be at least a time interval after the first PUSCH transmission.

83. The base station of claim 82, wherein the first PUSCH transmission is scheduled by a first downlink control information (DCI), or a configured grant.

84. The base station of claim 82 or 83, wherein the second PUSCH transmission is scheduled by a second DCI or a configured grant.

85. The base station of claim 84, wherein the second DCI is transmitted to be at least the time interval after the first PUSCH transmission.

86. The base station of any one of claims 82 to 85, wherein the time interval is relevant to at least one of the followings: a timing advance, a first offset for uplink resource determination, a round trip time, or a second offset between downlink uplink timing relationship.

87. The base station of any one of claims 82 to 86, wherein the second PUSCH transmission starts at least the time interval after a last symbol of the first PUSCH transmission.

88. The base station of any one of claims 82 to 87, wherein the time interval starts after a last symbol of the first PUSCH transmission in an uplink frame timing.

89. The base station of any one of claims 82 to 88, wherein an ending location of the time interval is relevant to a last symbol of a PUSCH resource for the first PUSCH transmission in a downlink frame timing.

90. The base station of claim 89, wherein the uplink frame timing and the downlink frame timing are at a UE side of the UE.

91. The base station of claim 89 or 90, wherein for a given frame number, the uplink frame timing starts earlier than the corresponding downlink frame timing by the second offset between downlink uplink timing relationship.

92. The base station of any one of claims 89 to 91, wherein the PUSCH resource is obtained from at least one of the followings: the first DCI, or the configured grant, or the first offset for uplink resource determination.

93. The base station of any one of claims 86 to 92, wherein the first offset for uplink resource determination is indicated by the first DCI and/or a third DCI and/or a radio resource control (RRC) and/or a medium access control-control element (MAC-CE) and/or a system information.

94. The base station of any one of claims 83 to 93, wherein the first DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

95. The base station of any one of claims 84 to 94, wherein the second DCI comprises DCI format 0_0 and/or DCI format 0_l and/or DCI format 0_2.

96. The base station of any one of claims 93 to 95, wherein the third DCI comprises a group-common DCI.

97. The base station of any one of claims 93 to 96, wherein the third DCI comprises a DCI format.

98. The base station of any one of claims 84 to 97, wherein the first DCI and/or the second DCI is transmitted in a type 3 physical downlink control channel (PDCCH) common search space set and/or in a UE-specific search space set.

99. The base station of any one of claims 93 to 97, wherein the third DCI is transmitted in a type 3 PDCCH common search space set.

100. The base station of any one of claims 97 to 99, wherein the DCI format of the third DCI is cyclic redundancy check (CRC) scrambled with slot format indication-radio network temporary identifier (SFI-RNTI).

101. The base station of any one of claims 97 to 100, wherein the DCI format of the third DCI is DCI format 2_0.

102. The base station of any one of claims 82 to 101, wherein the first PUSCH transmission and the second PUSCH transmission are transmitted to the base station.

103. The base station of any one of claims 82 to 102, wherein a value of the time interval is configured by the base station.

104. The base station of claim 103, wherein when the second TB of the HARQ process number is a first identity (ID) number, the time interval is configured to be zero by the base station.

105. The base station of claim 104, wherein when the second TB of the HARQ process number is a second ID number, the time interval is configured to be non-zero by the base station.

106. The base station of claim 105, wherein the first ID number and the second ID number are different.

107. The base station of claim 106, wherein the first ID number corresponds to 1 and the second ID number corresponds to

2.

108. The base station of any one of claims 82 to 103, wherein the time interval is equal to zero.

109. A non-transitory machine-readable storage medium having stored thereon instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 27 and 55 to 81.

110. A chip, comprising: a processor, configured to call and run a computer program stored in a memory, to cause a device in which the chip is installed to execute the method of any one of claims 1 to 27 and 55 to 81.

111. A computer readable storage medium, in which a computer program is stored, wherein the computer program causes a computer to execute the method of any one of claims 1 to 27 and 55 to 81.

112. A computer program product, comprising a computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 27 and 55 to 81.

113. A computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 27 and 55 to 81.