WO2022148982A1

WO2022148982A1 - Apparatus and method of wireless communication

Info

Publication number: WO2022148982A1
Application number: PCT/IB2021/000051
Authority: WO
Inventors: Hao Lin
Original assignee: Orope France Sarl
Priority date: 2021-01-08
Filing date: 2021-01-08
Publication date: 2022-07-14

Abstract

An apparatus and a method of wireless communication are provided. The method by a user equipment (UE) includes receiving a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission. This can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability.

Description

APPARATUS AND METHOD OF WIRELESS COMMUNICATION 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 and a method of wireless communication, which can provide a good communication performance and/or high reliability. 2. Description of the Related Art [0002] An unlicensed spectrum is a shared spectrum. A communication device in different communication systems can use the unlicensed spectrum as long as the communication device meets regulatory requirements set by the country or region on the unlicensed spectrum and does not need to apply for a proprietary spectrum authorization from the government. [0003] In order to allow various communication systems that use the unlicensed spectrum for wireless communication to coexist friendly in the unlicensed spectrum, some countries or regions specify regulatory requirements that must be met to use the unlicensed spectrum. For example, the communication device follows the principle of “a channel access procedure (or called a listen before talk (LBT) procedure”, that is, the communication device needs to perform channel sensing before transmitting a signal on the channel. Only when the LBT outcome shows that the channel is idle, the communication device can perform signal transmission, or otherwise, the communication device cannot perform the signal transmission. In order to ensure fairness, once the communication device successfully occupies the channel, a transmission duration cannot exceed the maximum channel occupancy time (MCOT). The LBT mechanism is also called channel access procedure. In a new radio (NR) release 16 (R16), there are different types of channel access procedures, e.g. type 1, type 2A, type 2B, and type 2C channel access procedures as described in a third generation partnership project (3GPP) technical specification (TS) 37.213. [0004] At present, a network needs to spend many downlink control information (DCI) in order to schedule many data transmissions. Obviously, it will consume a lot of signaling overhead. [0005] Therefore, there is a need for an apparatus (such as a user equipment (UE) and/or a base station) and a method of wireless communication, which can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. SUMMARY [0006] 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 wireless communication, which can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. [0007] In a first aspect of the present disclosure, a method of wireless communication by a user equipment (UE), comprising receiving a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission. [0008] In a second aspect of the present disclosure, a method of wireless communication by a base station comprising transmitting a first downlink control information (DCI) and/or a second DCI to a UE, wherein the first DCI and/or the second DCI schedules more than one data transmission. [0009] In a third aspect of the present disclosure, a user equipment comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to receive a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission. [0010] In a fourth aspect of the present disclosure, a base station comprises a memory, a transceiver, and a processor coupled to the memory and the transceiver. The processor is configured to control the transceiver to transmit a first downlink control information (DCI) and/or a second DCI to a base UE, wherein the first DCI and/or the second DCI schedules more than one data transmission. [0011] 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. [0012] 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. [0013] 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. [0014] 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. [0015] In a ninth aspect of the present disclosure, a computer program causes a computer to execute the above method. BRIEF DESCRIPTION OF DRAWINGS [0016] 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. [0017] FIG. 1 is a block diagram of one or more user equipments (UEs) and a base station (e.g., gNB or eNB) of communication in a communication network system according to an embodiment of the present disclosure. [0018] FIG. 2 is a flowchart illustrating a method of wireless communication performed by a user equipment (UE) according to an embodiment of the present disclosure. [0019] FIG.3 is a flowchart illustrating a method of wireless communication performed by a base station according to an embodiment of the present disclosure. [0020] FIG. 4 is a block diagram of a system for wireless communication according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF EMBODIMENTS [0021] 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. [0022] FIG.1 illustrates that, in some embodiments, one or more user equipments (UEs) 10 and a base station (e.g., gNB or eNB) 20 for transmission adjustment in a communication network system 30 (e.g., non-terrestrial network (NTN) or terrestrial network) 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 and the transceiver 13. The base station 20 may include a memory 22, a transceiver 23, and a processor 21 coupled to the memory 22 and 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. [0023] 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. [0024] In Release 15 and Release 16 of new radio (NR) system, a resource allocation for downlink data such as a physical downlink shared channel (PDSCH) have been specified in TS 38.214 section 5. A PDSCH may be scheduled by a downlink control information (DCI) format. The PDSCH contains a transport block (TB) corresponding to a HARQ process number. However, in some cases, e.g. high throughput requested application such as virtual reality/augmented reality (VR/AR), or non-terrestrial communications as described in TR 38.811 or TS 38.821, a user equipment UE needs to receive PDSCHs carrying different transport blocks consecutively in time domain. In some extreme cases, the UE receives PDSCH in consecutive slots. For such applications, if a network follows Release 15 or Release16 specifications, the network needs to spend many DCIs in order to schedule these PDSCH transmissions. Obviously, it will consume a lot of signaling overhead. [0025] In the present disclosure, some embodiments present a method relevant to a single DCI scheduling multiple PDSCHs/PUSCHs, then the signaling overhead can be greatly reduced. In the present disclosure, some embodiments also present some methods relevant to multiple PDSCH/PUSCH scheduling by a single DCI for an out of order (OOO) reception issue and/or a transmission configuration indication (TCI) state indication. [0026] In some embodiments, the processor 11 is configured to control the transceiver 13 to receive a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission. This can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. [0027] In some embodiments, the processor 21 is configured to control the transceiver 23 to transmit a first downlink control information (DCI) and/or a second DCI to a UE, wherein the first DCI and/or the second DCI schedules more than one data transmission. This can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. [0028] FIG.2 illustrates a method 200 of wireless communication by a user equipment (UE) according to an embodiment of the present disclosure. In some embodiments, the method 200 includes: a block 202, receiving a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission. This can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. [0029] FIG.3 illustrates a method 300 of wireless communication by a base station according to an embodiment of the present disclosure. In some embodiments, the method 300 includes: a block 302, transmitting a first downlink control information (DCI) and/or a second DCI to a UE, wherein the first DCI and/or the second DCI schedules more than one data transmission. This can solve issues in the prior art, reduce signaling overhead, provide a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions, provide a good communication performance, and/or provide high reliability. [0030] In some embodiments, the data transmission comprises a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH). In some embodiments, the first DCI schedules at least a first data transmission and a second data transmission, where the first data transmission and the second data transmission carry a same transport block (TB) or different TBs. In some embodiments, the second DCI schedules at least a third data transmission and a fourth data transmission, where the third data transmission and the fourth data transmission carry a same TB or different TBs. In some embodiments, the first DCI is received before the second DCI. In some embodiments, the first data transmission scheduled is before the second data transmission. In some embodiments, the third data transmission scheduled is before the fourth data transmission. In some embodiments, the third data transmission scheduled is after the first data transmission. In some embodiments, the third data transmission scheduled is after the second data transmission. [0031] In some embodiments, the first DCI schedules a first set of data transmissions. In some embodiments, the second DCI schedules a second set of data transmissions. In some embodiments, the first DCI is received before the second DCI. In some embodiments, an earliest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions. In some embodiments, a latest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions. In some embodiments, the UE is configured to transmits, to the base station, one or more first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to the first set of data transmissions and/or one or more second HARQ-ACK information corresponding to the second set of data transmissions. In some embodiments, the one or more first HARQ-ACK information and/or the one or more second HARQ-ACK information is transmitted in an uplink control information (UCI) and is carried in a physical uplink control channel (PUCCH) in a slot. [0032] In some embodiments, the first DCI indicates a first PUCCH resource of a first PUCCH for the UE reporting the one or more first HARQ-ACK information corresponding to the first set of data transmissions and/or the second DCI indicates a second PUCCH resource of a second PUCCH for the UE reporting the one or more second HARQ-ACK information corresponding to the second set of data transmissions. In some embodiments, when the first DCI is before the second DCI, the first PUCCH is allocated before the second PUCCH. In some embodiments, the first DCI indicates a same transmission configuration indication (TCI) state for the first data transmission and/or the second data transmission and/or the second DCI indicates a same transmission configuration indication (TCI) state for the third data transmission and/or the fourth data transmission. In some embodiments, the first DCI indicates dedicated TCI states for the first data transmission and/or the second data transmission and/or the second DCI indicates dedicated TCI states for the third data transmission and/or the fourth data transmission. [0033] FIG. 4 is a schematic diagram illustrating each downlink control information (DCI) scheduling a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH) according to an embodiment of the present disclosure. FIG. 4 illustrates that, in some embodiments, in a legacy system, when a gNB schedules a downlink data transmission (PDSCH) to or uplink data transmission (PUSCH) from a UE. The gNB will first transmit a DCI to the UE and the DCI is called scheduling DCI which is used to schedule a PDSCH or PUSCH for the UE. For a case where there is significant amount of data transmissions between the gNB and the UE, the gNB needs to transmit many DCI, each scheduling a PDSCH or PUSCH. In this disclosure, we propose that one DCI can schedule more than one PDSCH or PUSCH. This can reduce significantly the signalling overhead. [0034] In some examples, for any two HARQ process IDs in a given scheduled cell, if the UE is scheduled to start receiving a first PDSCH starting in symbol j by a PDCCH ending in symbol i, the UE is not expected to be scheduled to receive a PDSCH starting earlier than the end of the first PDSCH with a PDCCH that ends later than symbol i. This condition is denoted by an out-of-order (OOO) condition. [0035] FIG. 5 is a schematic diagram illustrating one DCI scheduling multiple PDSCHs or PUSCHs according to an embodiment of the present disclosure. FIG. 5 illustrates that, in some embodiments, for multi-PDSCH scheduling, if the OOO condition applies on the first scheduled PDSCH or all PDSCHs. Similar method is applied for multi-PUSCH scheduling. In some examples, a UE receives a first DCI that schedules at least a first PDSCH and a second PDSCH, where the first PDSCH and the second PDSCH carry a same transport block (TB) or different TBs. The UE receives a second DCI that schedules at least a third PDSCH and a fourth PDSCH, where third PDSCH and the fourth PDSCH carry a same TB or different TBs. The first DCI is received before the second DCI. In some examples, the first PDSCH is before the second PDSCH. In some examples, the third PDSCH is before the fourth PDSCH. In some embodiments, the third PDSCH should be after the first PDSCH. [0036] For example, a UE receives DCI 1 and DCI 2 from a gNB, where the DCI 1 schedules PDSCH 1 and PDSCH 2. The PDSCH 1 and PDSCH 2 carry a same TB or different TBs; the DCI 2 schedules PDSCH 3 and PDSCH 4, where the PDSCH 3 and PDSCH 4 carry a same TB or different TBs. Moreover, the PDSCH 1 is scheduled before the PDSCH 2 and the PDSCH 3 is scheduled before the PDSCH 4. In this example, in order to avoid the out of order issue, the UE expects that the first PDSCH should be scheduled before the third PDSCH because the UE receives the first DCI first therefore the UE will process the data reception scheduled by the earlier received DCI early. Similarly, the gNB needs to schedule the PDSCH 1 before the PDSCH 3 as shown in FIG.5. [0037] FIG.6 is a schematic diagram illustrating one DCI scheduling multiple PDSCHs or PUSCHs according to another embodiment of the present disclosure. FIG. 6 illustrates that, in some embodiments, in order to ensure a full pipeline processing, the UE expects that the PDSCH 3 is scheduled after the PDSCH 2. Similarly, the gNB needs to schedule a PDSCH 2 before the PDSCH 3. [0038] FIG.7 is a schematic diagram illustrating one DCI scheduling multiple PDSCHs or PUSCHs according to another embodiment of the present disclosure. FIG.7 illustrates that, in some embodiments, a UE receives a first DCI that schedules a first set of PDSCHs and a second DCI that schedules a second set of PDSCHs. The first DCI is before the second DCI. In some examples, the UE expects that the earliest PDSCH of the first set of PDSCHs is before the earliest PDSCH of the second set of PDSCHs. In some examples, the UE expects that the latest PDSCH of the first set of PDSCHs is before the earliest PDSCH of the second set of PDSCHs. [0039] In some examples, when a UE receives a PDSCH, the UE shall report a HARQ-ACK information corresponding to the PDSCH. The HARQ-ACK information is transmitted in a UCI and it is carried in a PUCCH in a slot. When a UE receives a first set of PDSCHs that are scheduled by a first DCI, the first DCI indicates a first PUCCH resource (PUCCH 1). In some embodiments, the UE transmits one or more HARQ-ACK information corresponding to the first set of PDSCHs reception in the first PUCCH. In some examples, when the UE receives a second set of PDSCHs scheduled by a second DCI, the second DCI indicates a second PUCCH resource for the UE reporting one or more HARQ-ACK information corresponding to the second set of PDSCHs. In some examples, when the first DCI is before the second DCI and the first PUCCH shall be allocated before the second PUCCH. [0040] In some examples, a UE receives a DCI that schedules a first PDSCH and a second PDSCH. In the DCI, the gNB indicates a TCI state for the first and/or the second PDSCH according to TS 38.212. In some examples, a same TCI state indication is used for the first PDSCH and the second PDSCH, e.g. the DCI contains a TCI state indication field and it indicates a TCI state for both the first PDSCH and the second PDSCH. Optionally, the DCI indicates dedicated TCI state for the first PDSCH and the second PDSCH, respectively. For example, the DCI contains a TCI state indication field, which respectively indicates the TCI state for the first PDSCH and the second PDSCH. Optionally, in the same DCI, all PDSCHs are configured with the same TCI state. Optionally, in the same DCI, different PDSCHs have their own TCI states. [0041] In some embodiments, a channel refers to a carrier or a part of a carrier consisting of a contiguous set of resource blocks (RBs) on which a channel access procedure is performed in shared spectrum. In some embodiments, a channel access procedure is a procedure based on sensing that evaluates the availability of a channel for performing transmissions. The basic unit for sensing is a sensing slot with a duration T_si = 9us. The sensing slot duration T_sl is considered to be idle if an eNB/gNB or a UE senses the channel during the sensing slot duration, and determines that the detected power for at least 4us within the sensing slot duration is less than energy detection threshold X_Thresh. Otherwise, the sensing slot duration T_sl is considered to be busy. [0042] Type 1 DL channel access procedures: This describes channel access procedures to be performed by an eNB/gNB where the time duration spanned by the sensing slots that are sensed to be idle before a downlink transmission(s) is random. [0043] Type 2 DL channel access procedures: This describes channel access procedures to be performed by an eNB/gNB where the time duration spanned by sensing slots that are sensed to be idle before a downlink transmission(s) is deterministic. [0044] Type 2A DL channel access procedures: An eNB/gNB may transmit a DL transmission immediately after sensing the channel to be idle for at least a sensing interval T_{short_dl} = 25us . T_{short_dl} consists of a duration T_f = 16us immediately followed by one sensing slot and T_f includes a sensing slot at start of T_f. The channel is considered to be idle for T_{short_dl} if both sensing slots of T_{short_dl} are sensed to be idle. [0045] Type 2B DL channel access procedures: A gNB may transmit a DL transmission immediately after sensing the channel to be idle within a duration of T_f = 16us. T_f includes a sensing slot that occurs within the last 9us of T_f. The channel is considered to be idle within the duration T_f if the channel is sensed to be idle for a total of at least 5us with at least 4us of sensing occurring in the sensing slot. [0046] Type 2C DL channel access procedures: When a gNB follows the procedures in this clause for transmission of a DL transmission, the gNB does not sense the channel before transmission of the DL transmission. The duration of the corresponding DL transmission is at most 584us. [0047] Uplink channel access procedures: A UE performing transmission(s) on LAA Scell(s), an eNB scheduling or configuring UL transmission(s) for a UE performing transmission(s) on LAA Scell(s), and a UE performing transmission(s) on channel(s) and a gNB scheduling or configuring UL transmission(s) for a UE performing transmissions on channel(s) shall perform the procedures for the UE to access the channel(s) on which the transmission(s) are performed. If a UE fails to access the channel(s) prior to an intended UL transmission to a gNB, Layer 1 notifies higher layers about the channel access failure. [0048] Type 1 UL channel access procedure: This describes channel access procedures by a UE where the time duration spanned by the sensing slots that are sensed to be idle before a UL transmission(s) is random. [0049] Type 2 UL channel access procedure: This describes channel access procedures by UE where the time duration spanned by the sensing slots that are sensed to be idle before a UL transmission(s) is deterministic. [0050] Type 2A UL channel access procedure: If a UE is indicated to perform Type 2A UL channel access procedures, the UE uses Type 2A UL channel access procedures for a UL transmission. The UE may transmit the transmission immediately after sensing the channel to be idle for at least a sensing interval T_{short_ul} = 25us. T_{short_ul} consists of a duration T_f = 16us immediately followed by one slot sensing slot and T_f includes a sensing slot at start of T_f . The channel is considered to be idle for T_{short_ul} if both sensing slots of T_{short_ul}.are sensed to be idle. [0051] Type 2B UL channel access procedure: If a UE is indicated to perform Type 2B UL channel access procedures, the UE uses Type 2B UL channel access procedure for a UL transmission. The UE may transmit the transmission immediately after sensing the channel to be idle within a duration of T_f = 16us. T_f includes a sensing slot that occurs within the last 9us of T_f. The channel is considered to be idle within the duration T_f if the channel is sensed to be idle for total of at least 5us with at least 4us of sensing occurring in the sensing slot. [0052] Type 2C UL channel access procedure: If a UE is indicated to perform Type 2C UL channel access procedures for a UL transmission, the UE does not sense the channel before the transmission. The duration of the corresponding UL transmission is at most 584us. [0053] Commercial interests for some embodiments are as follows. 1. Solving issues in the prior art. 2. Reducing signaling overhead.3. Providing a method relevant to a single downlink control information (DCI) scheduling multiple data transmissions. 4. Providing a good communication performance. 5. Providing a high reliability. 6. 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 5G NR licensed and non-licensed or shared spectrum communications. Some embodiments of the present disclosure propose technical mechanisms. [0054] FIG.4 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. 4 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. [0055] 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. [0056] 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. [0057] 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. [0058] 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. [0059] 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, an 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. [0060] 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. [0061] 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. [0062] 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. [0063] 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. [0064] 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 wireless communication method, by a user equipment (UE), comprising: receiving a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission.

2. The method of claim 1, wherein the data transmission comprises a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

3. The method of claim 1 or 2, wherein the first DCI schedules at least a first data transmission and a second data transmission, where the first data transmission and the second data transmission carry a same transport block (TB) or different TBs.

4. The method of any one of claims 1 to 3, wherein the second DCI schedules at least a third data transmission and a fourth data transmission, where the third data transmission and the fourth data transmission carry a same TB or different TBs.

5. The method of any one of claims 1 to 4, wherein the first DCI is received before the second DCI.

6. The method of claim 5, wherein the first data transmission scheduled is before the second data transmission.

7. The method of claim 5 or 6, wherein the third data transmission scheduled is before the fourth data transmission.

8. The method of any one of claims 5 to 7, wherein the third data transmission scheduled is after the first data transmission.

9. The method of any one of claims 5 to 7, wherein the third data transmission scheduled is after the second data transmission.

10. The method of claim 1 or 2, wherein the first DCI schedules a first set of data transmissions.

11. The method of any one of claims 1, 2, and 10, wherein the second DCI schedules a second set of data transmissions.

12. The method of any one of claims 1, 2, 10, and 11, wherein the first DCI is received before the second DCI.

13. The method of claim 12, wherein an earliest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions.

14. The method of claim 12 or 13, wherein a latest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions.

15. The method of any one of claims 10 to 14, wherein the UE is configured to transmits, to the base station, one or more first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to the first set of data transmissions and/or one or more second HARQ-ACK information corresponding to the second set of data transmissions.

16. The method of claim 15, wherein the one or more first HARQ-ACK information and/or the one or more second HARQ- ACK information is transmitted in an uplink control information (UCI) and is carried in a physical uplink control channel (PUCCH) in a slot.

17. The method of claim 15 or 16, wherein the first DCI indicates a first PUCCH resource of a first PUCCH for the UE reporting the one or more first HARQ-ACK information corresponding to the first set of data transmissions and/or the second DCI indicates a second PUCCH resource of a second PUCCH for the UE reporting the one or more second HARQ-ACK information corresponding to the second set of data transmissions.

18. The method of claim 17, wherein when the first DCI is before the second DCI, the first PUCCH is allocated before the second PUCCH.

19. The method of any one of claim 3 to 18, wherein the first DCI indicates a same transmission configuration indication (TCI) state for the first data transmission and/or the second data transmission and/or the second DCI indicates a same transmission configuration indication (TCI) state for the third data transmission and/or the fourth data transmission.

20. The method of any one of claim 3 to 18, wherein the first DCI indicates dedicated TCI states for the first data transmission and/or the second data transmission and/or the second DCI indicates dedicated TCI states for the third data transmission and/or the fourth data transmission.

21. A wireless communication method, by a base station, comprising: transmitting a first downlink control information (DCI) and/or a second DCI to a user equipment, wherein the first DCI and/or the second DCI schedules more than one data transmission.

22. The method of claim 21, wherein the data transmission comprises a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

23. The method of claim 21 or 22, wherein the first DCI schedules at least a first data transmission and a second data transmission, where the first data transmission and the second data transmission carry a same transport block (TB) or different TBs.

24. The method of any one of claims 21 to 23, wherein the second DCI schedules at least a third data transmission and a fourth data transmission, where the third data transmission and the fourth data transmission carry a same TB or different TBs.

25. The method of any one of claims 21 to 24, wherein the first DCI is transmitted before the second DCI.

26. The method of claim 25, wherein the first data transmission scheduled is before the second data transmission.

27. The method of claim 25 or 26, wherein the third data transmission scheduled is before the fourth data transmission.

28. The method of any one of claims 25 to 27, wherein the third data transmission scheduled is after the first data transmission.

29. The method of any one of claims 25 to 27, wherein the third data transmission scheduled is after the second data transmission.

30. The method of claim 21 or 22, wherein the first DCI schedules a first set of data transmissions.

31. The method of any one of claims 21, 22, and 30, wherein the second DCI schedules a second set of data transmissions.

32. The method of any one of claims 21, 22, 30, and 31, wherein the first DCI is received before the second DCI.

33. The method of claim 32, wherein an earliest data transmission of the first set of data transmissions is transmitted by the base station before an earliest data transmission of the second set of data transmissions.

34. The method of claim 32 or 33, wherein a latest data transmission of the first set of data transmissions is transmitted by the base station before an earliest data transmission of the second set of data transmissions.

35. The method of any one of claims 30 to 34, wherein the base station is configured to receives, from the UE, one or more first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to the first set of data transmissions and/or one or more second HARQ-ACK information corresponding to the second set of data transmissions.

36. The method of claim 35, wherein the one or more first HARQ-ACK information and/or the one or more second HARQ- ACK information is received in an uplink control information (UCI) and is carried in a physical uplink control channel (PUCCH) in a slot.

37. The method of claim 35 or 36, wherein the first DCI indicates a first PUCCH resource of a first PUCCH for the UE reporting the one or more first HARQ-ACK information corresponding to the first set of data transmissions and/or the second DCI indicates a second PUCCH resource of a second PUCCH for the UE reporting the one or more second HARQ-ACK information corresponding to the second set of data transmissions.

38. The method of claim 37, wherein when the first DCI is before the second DCI, the first PUCCH is allocated before the second PUCCH.

39. The method of any one of claim 23 to 38, wherein the first DCI indicates a same transmission configuration indication (TCI) state for the first data transmission and/or the second data transmission and/or the second DCI indicates a same transmission configuration indication (TCI) state for the third data transmission and/or the fourth data transmission.

40. The method of any one of claim 23 to 38, wherein the first DCI indicates dedicated TCI states for the first data transmission and/or the second data transmission and/or the second DCI indicates dedicated TCI states for the third data transmission and/or the fourth data transmission.

41. A user equipment (UE), comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to control the transceiver to receive a first downlink control information (DCI) and/or a second DCI from a base station, wherein the first DCI and/or the second DCI schedules more than one data transmission.

42. The UE of claim 41, wherein the data transmission comprises a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

43. The UE of claim 41 or 42, wherein the first DCI schedules at least a first data transmission and a second data transmission, where the first data transmission and the second data transmission carry a same transport block (TB) or different TBs.

44. The UE of any one of claims 41 to 43, wherein the second DCI schedules at least a third data transmission and a fourth data transmission, where the third data transmission and the fourth data transmission carry a same TB or different TBs.

45. The UE of any one of claims 41 to 44, wherein the first DCI is received before the second DCI.

46. The UE of claim 45, wherein the first data transmission scheduled is before the second data transmission.

47. The UE of claim 45 or 46, wherein the third data transmission scheduled is before the fourth data transmission.

48. The UE of any one of claims 45 to 47, wherein the third data transmission scheduled is after the first data transmission.

49. The UE of any one of claims 45 to 47, wherein the third data transmission scheduled is after the second data transmission.

50. The UE of claim 41 or 42, wherein the first DCI schedules a first set of data transmissions.

51. The UE of any one of claims 41, 42, and 50, wherein the second DCI schedules a second set of data transmissions.

52. The UE of any one of claims 41, 42, 50, and 51, wherein the first DCI is received before the second DCI.

53. The UE of claim 52, wherein an earliest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions.

54. The UE of claim 52 or 53, wherein a latest data transmission of the first set of data transmissions is received by the UE before an earliest data transmission of the second set of data transmissions.

55. The UE of any one of claims 50 to 54, wherein the transceiver is configured to transmits, to the base station, one or more first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to the first set of data transmissions and/or one or more second HARQ-ACK information corresponding to the second set of data transmissions.

56. The UE of claim 55, wherein the one or more first HARQ-ACK information and/or the one or more second HARQ- ACK information is transmitted in an uplink control information (UCI) and is carried in a physical uplink control channel (PUCCH) in a slot.

57. The UE of claim 55 or 56, wherein the first DCI indicates a first PUCCH resource of a first PUCCH for the UE reporting the one or more first HARQ-ACK information corresponding to the first set of data transmissions and/or the second DCI indicates a second PUCCH resource of a second PUCCH for the UE reporting the one or more second HARQ-ACK information corresponding to the second set of data transmissions.

58. The UE of claim 57, wherein when the first DCI is before the second DCI, the first PUCCH is allocated before the second PUCCH.

59. The UE of any one of claim 43 to 58, wherein the first DCI indicates a same transmission configuration indication (TCI) state for the first data transmission and/or the second data transmission and/or the second DCI indicates a same transmission configuration indication (TCI) state for the third data transmission and/or the fourth data transmission.

60. The UE of any one of claim 43 to 58, wherein the first DCI indicates dedicated TCI states for the first data transmission and/or the second data transmission and/or the second DCI indicates dedicated TCI states for the third data transmission and/or the fourth data transmission.

61. A base station, comprising: a memory; a transceiver; and a processor coupled to the memory and the transceiver; wherein the processor is configured to control the transceiver to transmit a first downlink control information (DCI) and/or a second DCI to a user equipment, wherein the first DCI and/or the second DCI schedules more than one data transmission.

62. The base station of claim 61, wherein the data transmission comprises a physical downlink shared channel (PDSCH) or physical uplink shared channel (PUSCH).

63. The base station of claim 61 or 62, wherein the first DCI schedules at least a first data transmission and a second data transmission, where the first data transmission and the second data transmission carry a same transport block (TB) or different TBs.

64. The base station of any one of claims 61 to 63, wherein the second DCI schedules at least a third data transmission and a fourth data transmission, where the third data transmission and the fourth data transmission carry a same TB or different TBs.

65. The base station of any one of claims 61 to 64, wherein the first DCI is transmitted before the second DCI.

66. The base station of claim 65, wherein the first data transmission scheduled is before the second data transmission.

67. The base station of claim 65 or 66, wherein the third data transmission scheduled is before the fourth data transmission.

68. The base station of any one of claims 65 to 67, wherein the third data transmission scheduled is after the first data transmission.

69. The base station of any one of claims 65 to 67, wherein the third data transmission scheduled is after the second data transmission.

70. The base station of claim 61 or 62, wherein the first DCI schedules a first set of data transmissions.

71. The base station of any one of claims 61, 62, and 70, wherein the second DCI schedules a second set of data transmissions.

72. The base station of any one of claims 61, 62, 70, and 71, wherein the first DCI is received before the second DCI.

73. The base station of claim 72, wherein an earliest data transmission of the first set of data transmissions is transmitted by the base station before an earliest data transmission of the second set of data transmissions.

74. The base station of claim 72 or 73, wherein a latest data transmission of the first set of data transmissions is transmitted by the base station before an earliest data transmission of the second set of data transmissions.

75. The base station of any one of claims 70 to 74, wherein the transceiver is configured to receives, from the UE, one or more first hybrid automatic repeat request acknowledgement (HARQ-ACK) information corresponding to the first set of data transmissions and/or one or more second HARQ-ACK information corresponding to the second set of data transmissions.

76. The base station of claim 75, wherein the one or more first HARQ-ACK information and/or the one or more second HARQ-ACK information is received in an uplink control information (UCI) and is carried in a physical uplink control channel (PUCCH) in a slot.

77. The base station of claim 75 or 76, wherein the first DCI indicates a first PUCCH resource of a first PUCCH for the UE reporting the one or more first HARQ-ACK information corresponding to the first set of data transmissions and/or the second DCI indicates a second PUCCH resource of a second PUCCH for the UE reporting the one or more second HARQ-ACK information corresponding to the second set of data transmissions.

78. The base station of claim 77, wherein when the first DCI is before the second DCI, the first PUCCH is allocated before the second PUCCH.

79. The base station of any one of claim 63 to 78, wherein the first DCI indicates a same transmission configuration indication (TCI) state for the first data transmission and/or the second data transmission and/or the second DCI indicates a same transmission configuration indication (TCI) state for the third data transmission and/or the fourth data transmission.

80. The base station of any one of claim 63 to 78, wherein the first DCI indicates dedicated TCI states for the first data transmission and/or the second data transmission and/or the second DCI indicates dedicated TCI states for the third data transmission and/or the fourth data transmission.

81. 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 40.

82. 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 40.

83. 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 40.

84. 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 40.

85. A computer program, wherein the computer program causes a computer to execute the method of any one of claims 1 to 40.