Method for scheduling of transmissions

Abstract

This invention describes various solutions for improving multi-cell PUSCH / PDSCH transmission scheduling utilizing a single DCI. The apparatus can receive a DCI indicating the scheduling of multiple cells from a network node of a wireless network. The DCI includes a first DCI, a second DCI, or a third DCI. The apparatus can perform PDSCH reception or PUSCH transmission with at least one of the multiple cells based on the DCI. The first DCI includes common bit fields and multiple specified bit fields corresponding to the multiple cells; the second DCI includes common bit fields and a first portion of specified bit fields corresponding to at least one of the multiple cells; and the third DCI includes a second portion of specified bit fields corresponding to at least one of the multiple cells.

Description

[Technical Field]

[0001] This invention relates generally to mobile communications, and more specifically, to improved transmission scheduling of multi-cell physical uplink shared channel (PUSCH) / physical downlink shared channel (PDSCH) using a single downlink control information (DCI). [Previous Technology]

[0002] Unless otherwise stated, the methods described in this section are not considered prior art to the claims listed below, nor are they considered prior art by virtue of their inclusion in this section.

[0003] In current network implementations, a base station (BS) can provide radio coverage to a specific geographic area using multiple cells forming a radio access network. The BS can support the operation of multiple cells, each of which can provide service to at least one user equipment (UE) within its radio coverage area. Specifically, each cell can provide service based on at least one DCI to serve one or more UEs within its radio coverage area, where the radio coverage area of ​​one cell may overlap with another radio coverage area of ​​other cells. In one example, each cell can schedule downlink (DL) / uplink (UL) resources to a UE within its radio coverage area via a DCI to perform DL / UL transmissions. If the UE can support multiple cells (e.g., in dual connectivity / carrier aggregation), the UE can receive multiple DCIs to schedule DL / UL transmissions with multiple cells. Therefore, the network and the BS need to configure multiple DCIs corresponding to multiple cells for the UE to schedule DL / UL transmissions between the UE and the cells, which may result in transmission inefficiency and waste of available network resources. Additionally, if the UE uses a specific decoding technique (e.g., polar decoding), there are bit limits for decoding the DCI. Accordingly, the number / size of the DCI fields should comply with the bit limit rules / regulations.

[0004] Accordingly, how to improve the multi-cell PUSCH / PDSCH transmission scheduling using a single DCI has become an important issue for newly developed wireless communication networks. Therefore, it is necessary to provide appropriate DCI structure / segment design to improve scheduling efficiency and comply with certain decoding rules. [Summary of the Invention]

[0005] The following summary is illustrative only and is not intended to be limiting in any way. That is, the following summary is provided to introduce the concepts, key points, benefits, and advantageous effects of the novel and non-obvious techniques described herein. Selected embodiments are further described in the detailed description below. Therefore, the following summary is not intended to identify the essential features of the claimed subject matter, nor is it intended to define the scope of the claimed subject matter.

[0006] The purpose of this invention is to propose a scheme and a solution to address the problem, as described above, regarding the improvement of multi-cell UL (e.g., PUSCH) / DL (e.g., PDSCH) transmission scheduling using a single DCI.

[0007] In one aspect, a method may include a processor of the apparatus receiving a DCI indicating the scheduling of multiple cells from a network node of a wireless network. The DCI includes a first DCI, a second DCI, or a third DCI, wherein the first DCI corresponds to a one-segment DCI structure, and the second and third DCIs correspond to a two-segment DCI structure. The method may further include the processor of the apparatus performing PDSCH reception or PUSCH transmission with at least one of the multiple cells based on the DCI. The first DCI includes a common bit field and multiple designated bit fields corresponding to the multiple cells; the second DCI includes a common bit field and a first portion of designated bit fields corresponding to at least one of the multiple cells; and the third DCI includes a second portion of designated bit fields corresponding to at least one of the multiple cells.

[0008] In one aspect, a method may include a processor of a network node configuring a DCI, wherein the DCI instructs a device of a wireless network to schedule multiple cells. The DCI includes a first DCI, a second DCI, or a third DCI. The first DCI corresponds to a single-segment DCI structure, and the second and third DCIs correspond to a two-segment DCI structure. The method may further include a processor of the network node sending a DCI to a device to schedule PDSCH reception or PUSCH transmission with at least one of the multiple cells based on the DCI. The first DCI includes common bit fields and multiple specified bit fields corresponding to the multiple cells; the second DCI includes common bit fields and a first portion of specified bit fields corresponding to at least one of the multiple cells; and the third DCI includes a second portion of specified bit fields corresponding to at least one of the multiple cells.

[0009] Please note that while the background described in this invention may be certain specific radio access technologies, networks, and network topologies, such as Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, 5G, NR, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), and 6G, the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in, used in, or through any other type of radio access technology, network, and network topology. Therefore, the scope of this invention is not limited to the examples described herein.

Implementation Method

[0011] This invention discloses detailed embodiments and implementations of the claimed subject matter. However, it should be understood that the disclosed embodiments and implementations are merely illustrative of the claimed subject matter, which can be implemented in various forms. Moreover, the invention can be implemented in many different forms and should not be construed as limited to the exemplary embodiments and implementations set forth herein. Rather, these exemplary embodiments and implementations are provided to make the specification of this invention comprehensive and complete, and to fully convey the scope of the invention to those skilled in the art. In the following description, details of known features and techniques may be omitted to avoid unnecessarily obscuring the presented embodiments and implementations. Overview

[0012] Embodiments of the present invention relate to various techniques, methods, schemes, and / or solutions related to improving multi-cell PUSCH / PDSCH transmission scheduling using a single DCI. According to the present invention, multiple possible schemes can be implemented individually or in combination. That is, although these possible solutions can be described individually below, two or more of these possible solutions can be implemented in a combination or other combination manner.

[0013] In 3GPP, a radio access network (e.g., a 5G NR access network) may include multiple base stations (BSs), such as next-generation node-Bs (gNBs), to communicate with multiple mobile stations referred to as UEs. For current network implementations, a BS may use multiple cells forming the radio access network to provide radio coverage to a specific geographic area. A BS may support the operation of multiple cells, each capable of serving at least one UE within its radio coverage area. Specifically, each cell may provide service based on at least one digital communication interface (DCI) to serve one or more UEs within its radio coverage area, where the radio coverage area of ​​one cell may overlap with another radio coverage area of ​​another cell. In one example, each cell may schedule DL / UL resources to a UE within its radio coverage area via a DCI for performing DL / UL transmissions. If a UE can support multiple cells (e.g., applications in dual connectivity), the UE may receive multiple DCIs for scheduling DL / UL transmissions with multiple cells.

[0014] Figure 1 is a schematic diagram of an exemplary scenario 100 of DCI reception corresponding to multiple cells according to the present invention. As shown in scenario 100, at least one BS can provide services for the UE with four DCIs 102, 104, 106, and 108. Specifically, DCI 102 is used to schedule the first cell with the UE, DCI 104 is used to schedule the second cell with the UE, DCI 106 is used to schedule the third cell with the UE, and DCI 108 is used to schedule the fourth cell with the UE. In one example, each DCI is accompanied by a cyclic redundancy check (CRC) for error decoding and includes at least one designated bit field (e.g., 60 bits) and one CRC field (e.g., 24 bits), wherein the designated bit field includes scheduling information for one cell. In this way, the UE can communicate with four cells (e.g., the first cell, the second cell, the third cell, and the fourth cell) and perform PDSCH reception or PUSCH transmission scheduled by four DCIs 102, 104, 106, and 108, respectively.

[0015] Based on different transmission and UE capabilities, the network and BS can configure multiple DCIs corresponding to multiple cells for the UE to schedule the relevant resources for DL / UL transmissions between the UE and the cells. However, this may not be efficient if network resources are insufficient to serve all UEs within the radio coverage area. Additionally, if the UE uses a specific decoding technique (e.g., polarization decoding), there is a bit limitation for decoding the DCI (e.g., less than 140 bits). Therefore, DCI aggregation for multi-cell PUSCH / PDSCH transmission scheduling is proposed.

[0016] Figure 2 is a schematic diagram of an exemplary scenario 200 of two types of DCI structures according to the present invention. As shown in scenario 200, the implementation of scenario 200 is similar to that of scenario 100, and may include at least one BS providing services to the UE through four cells (e.g., a first cell, a second cell, a third cell, and a fourth cell). The difference is that the BS in scenario 200 can configure a single DCI for the UE under four cells (e.g., a first cell, a second cell, a third cell, and a fourth cell). In one example, the UE can receive a single DCI via one cell (e.g., a first cell), and the other cells (e.g., a second cell, a third cell, and a fourth cell) are scheduled by the same single DCI received in the previous cell (e.g., a first cell). Since the UE can utilize a specific decoding technique (e.g., polarization decoding technique) to decode the single DCI, the network and / or the BS can adaptively configure the number / size of fields of the single DCI to conform to bit limit rules (e.g., less than 140 bits).

[0017] In some implementations, based on bit restriction rules, a single DCI can have two types of DCI structures: a single-segment DCI structure 202 and a two-segment DCI structure 204. In one example, the single-segment DCI structure 202 can be an aggregated DCI, which includes a common bit field, four designated bit fields corresponding to four cells (e.g., the first cell, the second cell, the third cell, and the fourth cell), and a CRC bit field. Furthermore, the two-segment DCI structure 204 can include two DCI segments 2040 and 2042, which can be formed by adaptively dividing the single-segment DCI structure 202 into two independent DCIs, and the UE can link these two DCI segments 2040 and 2042 before determining the DCI used for scheduling information. Specifically, DCI segment 2040 may include a common bit field, a first portion of designated bit fields corresponding to at least one of the four cells, and a CRC bit field, while DCI segment 2042 may include a second portion of designated bit fields corresponding to the other cells and a CRC bit field. In one example, DCI segment 2040 may have one designated bit field corresponding to one cell (e.g., the first cell), and DCI segment 2042 may have three designated bit fields corresponding to three cells (e.g., the second, third, and fourth cells).

[0018] In some embodiments, the UE can receive radio resource control (RRC) from the BS to configure one or more DCI fields as common bit fields and one or more DCI fields as designated bit fields. That is, the UE can adaptively determine the field numbers of the common bit fields and multiple designated bit fields in the single-segment DCI structure 202 or the two-segment DCI structure 204. Specifically, for multi-cell PUSCH / PDSCH scheduling, the network can use the BS to allocate one or more fields in the DCI (e.g., the single-segment DCI structure 202 or the two-segment DCI structure 204) as common bit fields or designated bit fields using RRC configuration. In addition, the network can independently allocate DCI (e.g., the single-segment DCI structure 202 or the two-segment DCI structure 204) fields for each scheduled cell (e.g., the first cell, the second cell, the third cell, and the fourth cell).

[0019] In some embodiments, the UE can receive a bitmap, a medium access control (MAC) control element (CE), another DCI (e.g., other than the received single-segment DCI structure 202 or the received two-segment DCI structure 204), or any signaling / instruction from the BS, according to predetermined rules, to configure certain DCI fields(s) as common bit fields and certain DCI fields(s) as designated bit fields. That is, the UE can adaptively determine the field numbers of the common bit fields and multiple designated bit fields of the DCI (e.g., the single-segment DCI structure 202 or the received two-segment DCI structure 204). Therefore, based on different transmission and scheduling cell numbers, the network can adaptively configure certain DCI fields(s) as common bit fields / designated bit fields and / or the field numbers of the common bit fields / designated bit fields of the DCI (e.g., the single-segment DCI structure 202 or the received two-segment DCI structure 204) through any of the aforementioned signaling / instructions. In one example, the common bit field can be configured to 2, and the specified bit field can be configured to 4 for each cell, but the invention is not limited thereto.

[0020] In some embodiments, based on the scheduled cells and transmission conditions, the DCI may include at least one of the following information: information indicating the type of single-segment DCI structure or two-segment DCI structure, information indicating which cell to be scheduled by the DCI (e.g., single-segment DCI structure 202 or two-segment DCI structure 204), the number of carriers scheduled by the DCI (e.g., single-segment DCI structure 202 or two-segment DCI structure 204), and matching information specifying the bit field between multiple cells scheduled by the DCI (e.g., single-segment DCI structure 202 or two-segment DCI structure 204).

[0021] In one example, if the BS sends a single-segment DCI structure 202 to the UE through a cell (e.g., the first cell), the UE can be informed that this is a single-segment DCI structure. Furthermore, the number of cells and / or carriers can be notified by an indication of the cell identification (ID) or a bitmap, and the UE can be informed which cells(s) are scheduled by a specified bit field. In another example, if the BS sends two-segment DCI structures 204 to the UE through a cell (e.g., the first cell), the UE can be informed that this is a two-segment DCI structure and which segment (e.g., DCI segment 2040 or DCI segment 2042) has been received. Furthermore, the number of cells and / or carriers can be notified by an indication of the cell ID or a bitmap, and the UE can be informed which cells(s) are scheduled by which DCI segment (e.g., DCI segment 2040 or DCI segment 2042) and its specified bit field. In this way, a single DCI (e.g., a single-segment DCI structure 202 or a two-segment DCI structure 204) can be configured with scheduling information for all cells (e.g., the first cell, the second cell, the third cell, and the fourth cell) that perform any UL / DL transmission (e.g., PUSCH or PDSCH) with the UE, which is more efficient and complies with bit limit rules while saving transmission / resources.

[0022] In some embodiments, the UE can receive a physical downlink control channel (PDCCH) scrambled by a first demodulation reference signal (DMRS) from the BS. Accordingly, the UE can refer to the first DMRS to determine the number of cells scheduled by a single DCI (e.g., a single-segment DCI structure 202 or a two-segment DCI structure 204). In some embodiments, the UE can receive a PDCCH scrambled by a second DMRS from the BS. Accordingly, the UE can refer to the second DMRS to determine which cells are scheduled by two segments of DCI (e.g., DCI segment 2042 of two-segment DCI structure 204).

[0023] In one example, the scrambling sequence of the first DMRS (or the second DMRS) may be used to indicate the absence of two DCI segments (e.g., two DCI segments 204) or the absence of two DCI segments (e.g., DCI segment 2042). In another example, the scrambling sequence of the first DMRS may be used to indicate the number of cells scheduled in the two DCI segments (e.g., DCI segment 2042). In yet another example, the scrambling sequence of the second DMRS may be used to indicate which cells are scheduled by the two DCI segments (e.g., DCI segment 2042).

[0024] In some implementations, the UE may send a report to the BS and / or network. Specifically, the report may indicate the number of cells that can be supported simultaneously by a single DCI (e.g., a single-segment DCI structure 202, a DCI segment 2040 of a two-segment DCI structure 204, and / or a DCI segment 2042 of a two-segment DCI structure 204). In this way, based on the UE capabilities indicated in the report, the BS and / or network can adaptively determine / configure the number of cells that the UE can afford before the UE performs UL / DL transmissions with the cells.

[0025] In some embodiments, the UE can receive configuration from the BS or from the network, wherein the configuration can configure the maximum number of cells simultaneously scheduled by a single DCI (e.g., a single-segment DCI structure 202, a DCI segment 2040 of a two-segment DCI structure 204, and / or a DCI segment 2042 of a two-segment DCI structure 204). In this way, based on the available resources of the network, the BS and / or the network can adaptively determine / configure the available cells for the UE before the UE performs UL / DL transmissions. In one example, the maximum number of cells in the network may not exceed the number of cells that the UE can support.

[0026] In some implementations, the UE can determine the PUSCH preparation time based on its capabilities, and the UE can notify the BS and / or the network of the preparation time. Specifically, the preparation time can begin after the UE receives the last symbol of the PDCCH. Furthermore, the preparation time can be determined based on the maximum time value among different parameter sets (numerology, e.g., based on sub-carrier space (SCS)) of multiple cells (e.g., cells that may receive a single DCI or cells scheduled by the same DCI, such as the first, second, third, and / or fourth cells). In one example, among the scheduled cells (e.g., the first, second, third, and fourth cells), if the SCS of some cells (e.g., the first and third cells) is 15 kHz while the SCS of others (e.g., the second and fourth cells) is 30 kHz, the preparation time can be determined based on the maximum time value (e.g., 1 / 14 ms corresponding to the 15 kHz SCS).

[0027] In some implementations, the UE can determine the processing time of the PDSCH, and the UE can notify the BS and / or the network of the processing time. Specifically, the processing time can begin after the UE receives the last symbol of the PDSCH. Furthermore, the processing time can be determined based on the maximum time value among different parameter sets (e.g., based on SCS) of multiple cells (e.g., possibly receiving a single DCI, sending a hybrid automatic repeat request-acknowledgement (HARQ-ACK), or being scheduled by the same DCI for the first, second, third, and / or fourth cells). In one example, among the scheduled cells (e.g., the first, second, third, and fourth cells), if the SCS of some cells (e.g., the first and third cells) is 15 kHz, while the SCS of other cells (e.g., the second and fourth cells) is 30 kHz, the preparation time can be determined based on the maximum time value (e.g., 1 / 14 ms corresponding to the 15 kHz SCS). Illustrative Implementation

[0028] Figure 3 is a schematic diagram of an exemplary communication system 300 according to an embodiment of the present invention, including an exemplary communication device 310 and an exemplary network device 320. Each of the communication device 310 and the network device 320 can perform various functions to implement the schemes, techniques, processes and methods described herein related to improving multi-cell PUSCH / PDSCH transmission scheduling using a single DCI, including the scenarios / schemes described above and processes 400 and 500 described below.

[0029] The communication device 310 may be part of an electronic device, such as a UE (User Equipment) such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 310 may be implemented in a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet computer, laptop computer, or notebook computer. The communication device 310 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIoT device, such as a fixed or static device, a home appliance, a wired communication device, or a computing device. For example, the communication device 310 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Alternatively, the communication device 310 may be implemented in the form of one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set computing (RISC) processors, or one or more complex-instruction-set computing (CISC) processors. The communication device 310 may include at least a portion of the elements shown in Figure 3, such as the processor 312 in Figure 3. The communication device 310 may further include one or more other elements (such as an internal power supply, a display device, and / or user peripheral devices) unrelated to the proposed solution. However, for simplicity and brevity, these elements in the communication device 310 are not depicted in Figure 3, nor are they described below.

[0030] Network device 320 may be part of an electronic device, such as a network node of a base station, small cell, router, or gateway. For example, network device 320 may be implemented in an eNB in ​​an LTE, Advanced LTE, or Advanced LTE Upgrade network, or in a gNB in ​​a 5G, NR, IoT, NB-IoT, or IIoT network. Alternatively, network device 320 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 320 may include at least a portion of the elements shown in Figure 3, such as processor 322 in Figure 3. Network device 320 may further include one or more other elements (such as internal power supply, display device, and / or user peripheral devices) unrelated to the proposed solution of the present invention. However, for simplicity and brevity, these elements in network device 320 are not described in Figure 3, nor are they described below.

[0031] On the one hand, each of processors 312 and 322 may be implemented as one or more single-core processors, one or more multi-core processors, or one or more CISC processors. That is, even though the singular term "processor" is used to refer to processors 312 and 322 in this invention, each of processors 312 and 322 may include multiple processors in some embodiments and a single processor in other embodiments, according to the invention. On the other hand, each of processors 312 and 322 may be implemented as hardware (and optionally firmware) having electronic components, including but not limited to one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes configured and arranged for a specific purpose according to the invention. In other words, at least in some embodiments, each of processors 312 and 322 may serve as a dedicated machine specially designed, configured, and arranged to perform specific tasks including autonomous reliability enhancement in devices (such as communication device 310) and wireless networks (such as network device 320) according to various embodiments of the invention.

[0032] In some embodiments, the communication device 310 may further include a transceiver 316 coupled to the processor 312, the transceiver 316 being capable of wirelessly transmitting and receiving data. In some embodiments, the communication device 310 may further include a memory 314 coupled to the processor 312, which stores data and is accessible by the processor 312. In some embodiments, the network device 320 may further include a transceiver 326 coupled to the processor 322, the transceiver 326 being capable of wirelessly transmitting and receiving data. In some embodiments, the network device 320 may further include a memory 324 coupled to the processor 322, which stores data and is accessible by the processor 322. Accordingly, the communication device 310 and the network device 320 may wirelessly communicate with each other via transceiver 316 and transceiver 326, respectively. To aid in better understanding, the following description of the operation, functions, and capabilities of each of the communication device 310 and the network device 320 is provided in the context of a mobile communications environment, wherein the communication device 310 is implemented as a communication device or UE, and the network device 320 is implemented as a network node of a wireless network.

[0033] In some embodiments, the processor 312 may receive a DCI indicating the scheduling of multiple cells from the network device 320 via a transceiver 316, wherein the DCI includes a first DCI, a second DCI, or a third DCI, the first DCI corresponding to a single-segment DCI structure, and the second and third DCIs corresponding to a two-segment DCI structure. Subsequently, the processor 312 may perform PDSCH reception or PUSCH transmission with at least one of the multiple cells based on the DCI. The first DCI includes common bit fields and multiple specified bit fields corresponding to the multiple cells, the second DCI includes common bit fields and a first portion of specified bit fields corresponding to at least one of the multiple cells, and the third DCI includes a second portion of specified bit fields corresponding to at least one of the multiple cells.

[0034] In some embodiments, the processor 312 may receive RRC from the network device 320 via the transceiver 316 to configure a certain DCI field as a common bit field and some DCI fields as multiple specified bit fields.

[0035] In some embodiments, the processor 312 may receive bitmaps, MAC CE, fourth DCI, or predetermined rules from the network device 320 via transceiver 316 to configure a certain DCI field as a common bit field and some DCI fields as multiple specified bit fields.

[0036] In some embodiments, the DCI includes at least one of the following information: information indicating the type of a single-segment DCI structure or a two-segment DCI structure, information indicating which cell is to be scheduled by the first DCI, the second DCI or the third DCI, the number of carriers scheduled by the first DCI, the second DCI or the third DCI, and matching information specifying the bit field between the multiple cells scheduled by the first DCI, the second DCI or the third DCI.

[0037] In some embodiments, the processor 312 may receive a PDCCH scrambled by the first DMRS from the network device 320 via a transceiver 316. Subsequently, the processor 312 may determine the number of cells scheduled by at least one of the first DCI, second DCI, and third DCI based on the first DMRS.

[0038] In some embodiments, the processor 312 may receive a PDCCH scrambled by the second DMRS from the network device 320 via a transceiver 316. Subsequently, the processor 312 may determine which cell is scheduled by the third DCI based on the second DMRS.

[0039] In some embodiments, the processor 312 may send a report to the network device 320 via the transceiver 316. The report indicates the number of supported cells that can be simultaneously scheduled by at least one of the first DCI, the second DCI, and the third DCI.

[0040] In some embodiments, the processor 312 may receive configuration from the wireless network via the transceiver 316 through the network device 320. The configuration is used to configure the maximum number of cells simultaneously scheduled by at least one of the first DCI, second DCI, and third DCI.

[0041] In some embodiments, the processor 312 may determine the PUSCH preparation time. The preparation time begins after the communication device 310 receives the last symbol of the PDCCH and is determined based on the maximum time value from different parameter sets of multiple cells.

[0042] In some embodiments, the processor 312 may determine the processing time of the PDSCH. The processing time begins after the communication device 310 receives the last symbol of the PDSCH and is determined based on the maximum time value from different parameter sets of multiple cells.

[0043] In some embodiments, the processor 322 can configure the communication device 310 with a DCI indicating the scheduling of multiple cells, wherein the DCI includes a first DCI, a second DCI, or a third DCI. The first DCI corresponds to a single-segment DCI structure, and the second and third DCIs correspond to a two-segment DCI structure. Subsequently, the processor 322 can send the DCI to the communication device 310 via the transceiver 326 to schedule PDSCH reception or PUSCH transmission with at least one of the multiple cells based on the DCI. The first DCI includes common bit fields and multiple specified bit fields corresponding to the multiple cells, the second DCI includes common bit fields and a first portion of specified bit fields corresponding to at least one of the multiple cells, and the third DCI includes a second portion of specified bit fields corresponding to at least one of the multiple cells.

[0044] In some embodiments, the processor 322 may configure RRC to the communication device 310 to configure a certain DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0045] In some embodiments, the processor 322 may send a bitmap, MAC CE, fourth DCI, or predetermined rule to the communication device 310 via the transceiver 326 to configure a certain DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0046] In some embodiments, the DCI includes at least one of the following information: information indicating the type of a single-segment DCI structure or a two-segment DCI structure, information indicating which cell is to be scheduled by the first DCI, the second DCI or the third DCI, the number of carriers scheduled by the first DCI, the second DCI or the third DCI, and matching information specifying the bit field between the multiple cells scheduled by the first DCI, the second DCI or the third DCI.

[0047] In some embodiments, the processor 322 may transmit a PDCCH scrambled by a first DMRS to the communication device 310 via a transceiver 326. The first DMRS indicates the number of cells scheduled by at least one of a first DCI, a second DCI, and a third DCI.

[0048] In some embodiments, the processor 322 may send a PDCCH scrambled by a second DMRS to the communication device 310 via a transceiver 326. The second DMRS indicates which cell is scheduled by a third DCI.

[0049] In some embodiments, the processor 322 may receive reports from the communication device 310 via a transceiver 326. The reports indicate the number of supported cells that can be simultaneously scheduled by at least one of the first DCI, the second DCI, and the third DCI.

[0050] In some embodiments, the processor 322 may send configuration to the communication device 310 via the transceiver 326. The configuration is used to configure the maximum number of cells simultaneously scheduled by at least one of the first DCI, the second DCI, and the third DCI.

[0051] In some embodiments, the processor 322 may determine the PUSCH preparation time of the communication device 310. The preparation time begins after the communication device 310 receives the last symbol of the PDCCH and is determined based on the maximum time value from different parameter sets of multiple cells.

[0052] In some embodiments, the processor 322 may determine the processing time of the PDSCH of the communication device 310. The processing time begins after the communication device 310 receives the last symbol of the PDSCH and is determined based on the maximum time value from different parameter sets of multiple cells. (Illustrative process)

[0053] Figure 4 is a flowchart of an exemplary process 400 according to an embodiment of the present invention. Process 400 may be an exemplary implementation of the above-described scenario / scheme (whether partially or completely) regarding improved multi-cell PUSCH / PDSCH transmission scheduling utilizing a single DCI. Process 400 may represent one aspect of the implementation of features of communication device 310. Process 400 may include one or more operations, actions, or functions as shown in one or more of blocks 410 to 420. Although the various blocks shown are discrete, depending on the desired implementation, the various blocks in process 400 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks / sub-blocks of process 400 may be executed in the sequence shown in Figure 4 or may be executed in a different sequence. Process 400 may be implemented by communication device 310 or any suitable UE or machine type device. For illustrative purposes only and not for limitation, process 400 is described below in the context of communication device 310. Process 400 may begin at block 410.

[0054] At 410, process 400 may include the processor 312 of communication device 310 receiving a DCI indicating the scheduling of multiple cells from a network node (e.g., network device 320) in the wireless network, wherein the DCI includes a first DCI, a second DCI, or a third DCI, the first DCI corresponding to a single-segment DCI structure, and the second and third DCIs corresponding to a two-segment DCI structure. Process 400 may proceed from 410 to 420.

[0055] At 420, process 400 may include processor 312 performing PDSCH reception or PUSCH transmission with at least one of a plurality of cells based on DCI, the first DCI including common bit fields and a plurality of specified bit fields corresponding to the plurality of cells, the second DCI including common bit fields and a first portion of specified bit fields corresponding to at least one of the plurality of cells, and the third DCI including a second portion of specified bit fields corresponding to at least one of the plurality of cells.

[0056] In some embodiments, process 400 may further include processor 312 receiving RRC from network node (e.g., network device 320) to configure a DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0057] In some embodiments, process 400 may further include processor 312 receiving bitmaps, MAC CE, fourth DCI, or predetermined rules from network nodes (e.g., network device 320) to configure a DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0058] In some embodiments, the DCI includes at least one of the following information: information indicating the type of a single-segment DCI structure or a two-segment DCI structure, information indicating which cell is to be scheduled by the first DCI, the second DCI or the third DCI, the number of carriers scheduled by the first DCI, the second DCI or the third DCI, and matching information specifying the bit field between the multiple cells scheduled by the first DCI, the second DCI or the third DCI.

[0059] In some embodiments, process 400 may further include processor 312 receiving a PDCCH scrambled by the first DMRS from a network node (e.g., network device 320). Subsequently, process 400 may further include processor 312 determining, based on the first DMRS, the number of cells scheduled by at least one of the first DCI, second DCI, and third DCI.

[0060] In some embodiments, process 400 may further include processor 312 receiving a PDCCH scrambled by a second DMRS from a network node (e.g., network device 320). Subsequently, process 400 may further include processor 312 determining, based on the second DMRS, which cell is scheduled by a third DCI.

[0061] In some embodiments, process 400 may further include processor 312 sending a report to a network node (e.g., network device 320), wherein the report indicates the number of supported cells that can be simultaneously scheduled by at least one of the first DCI, second DCI and third DCI.

[0062] In some embodiments, process 400 may further include processor 312 receiving configuration from a wireless network via a network node (e.g., network device 320), wherein the configuration is for configuring the maximum number of cells simultaneously scheduled by at least one of a first DCI, a second DCI, and a third DCI.

[0063] In some embodiments, process 400 may further include processor 312 determining the PUSCH preparation time. The preparation time begins after communication device 310 receives the last symbol of PDCCH and is determined based on the maximum time value from different parameter sets of multiple cells.

[0064] In some embodiments, process 400 may further include processor 312 determining the processing time of PDSCH. The processing time begins after communication device 310 receives the last symbol of PDSCH and is determined based on the maximum time value from different parameter sets of multiple cells.

[0065] Figure 5 is a flowchart of an exemplary process 500 according to an embodiment of the present invention. Process 500 may be an exemplary implementation of the above-described scenario / scheme (whether partially or completely) regarding improved multi-cell PUSCH / PDSCH transmission scheduling utilizing a single DCI. Process 500 may represent one aspect of the implementation of features of network device 320. Process 500 may include one or more operations, actions, or functions as shown in one or more of blocks 510 to 520. Although the various blocks shown are discrete, depending on the desired implementation, the various blocks in process 500 may be split into more blocks, combined into fewer blocks, or have some blocks deleted. Furthermore, the blocks / sub-blocks of process 500 may be executed in the sequence shown in Figure 5 or may be executed in a different sequence. Process 500 may be implemented by network device 320 or any suitable BS or network node. For illustrative purposes only and not for limitation, process 500 is described below in the context of network device 320. Process 500 may begin at block 510.

[0066] At 510, process 500 may include a processor 322 of network device 320 configuring a DCI (Distributed Cell Interchange) indicating the scheduling of multiple cells for a device in the wireless network (e.g., communication device 310), wherein the DCI includes a first DCI, a second DCI, or a third DCI, the first DCI corresponding to a single-segment DCI structure, and the second and third DCIs corresponding to a two-segment DCI structure. Process 500 may proceed from 510 to 520.

[0067] At 520, process 500 may include processor 322 sending a DCI to a device (e.g., communication device 310) to schedule PDSCH reception or PUSCH transmission with at least one of a plurality of cells based on the DCI. A first DCI includes common bit fields and a plurality of specified bit fields corresponding to the plurality of cells; a second DCI includes common bit fields and a first portion of specified bit fields corresponding to at least one of the plurality of cells; and a third DCI includes a second portion of specified bit fields corresponding to at least one of the plurality of cells.

[0068] In some embodiments, process 500 may further include processor 322 configuring RRC for a device (e.g., communication device 310) to configure a DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0069] In some embodiments, process 500 may further include processor 322 sending bitmaps, MAC CE, fourth DCI, or predetermined rules to a device (e.g., communication device 310) to configure a DCI field as a common bit field and to configure certain DCI fields as multiple specified bit fields.

[0070] In some embodiments, the DCI includes at least one of the following information: information indicating the type of a single-segment DCI structure or a two-segment DCI structure, information indicating which cell is to be scheduled by the first DCI, the second DCI or the third DCI, the number of carriers scheduled by the first DCI, the second DCI or the third DCI, and matching information specifying the bit field between the multiple cells scheduled by the first DCI, the second DCI or the third DCI.

[0071] In some embodiments, process 500 may further include processor 322 sending a PDCCH scrambled by a first DMRS to a device (e.g., communication device 310), wherein the first DMRS indicates the number of cells scheduled by at least one of a first DCI, a second DCI, and a third DCI.

[0072] In some embodiments, process 500 may further include processor 322 sending a PDCCH scrambled by a second DMRS to a device (e.g., communication device 310), wherein the second DMRS indicates which cell is scheduled by a third DCI.

[0073] In some embodiments, process 500 may further include processor 322 receiving a report from a device (e.g., communication device 310), wherein the report indicates the number of supported cells that can be simultaneously scheduled by at least one of the first DCI, second DCI and third DCI.

[0074] In some embodiments, process 500 may further include processor 322 sending configuration to device (e.g., communication device 310), wherein the configuration is used to configure the maximum number of cells simultaneously scheduled by at least one of the first DCI, second DCI and third DCI.

[0075] In some embodiments, process 500 may further include processor 322 determining the preparation time of the PUSCH of the device (e.g., communication device 310). The preparation time begins after the device (e.g., communication device 310) receives the last symbol of the PDCCH and is determined based on the maximum time value in different parameter sets of multiple cells.

[0076] In some embodiments, process 500 may further include processor 322 determining the processing time of the PDSCH of the device (e.g., communication device 310). The processing time begins after the device (e.g., communication device 310) receives the last symbol of the PDSCH and is determined based on the maximum time value from different parameter sets of multiple cells. Additional Notes

[0077] The subject matter described in this invention sometimes illustrates different elements included within or connected to other elements. However, it should be understood that these depicted architectures are merely examples, and in reality, many other architectures that achieve the same functionality can be implemented. Conceptually, any arrangement of components that achieve the same functionality is effectively "associated" to enable the desired functionality. Therefore, regardless of architecture or intermediate elements, any two components combined in this invention to achieve a particular function can be considered as "associated" with each other to enable the desired functionality. Similarly, any two elements so associated can also be considered as "operationally connected" or "operationally coupled" to each other to achieve the desired functionality, and any two elements that can be so associated can also be considered as "operationally coupled" to each other to achieve the desired functionality. Specific examples of operationally coupled elements include, but are not limited to, physically mating and / or physically interacting elements and / or wirelessly interacting elements and / or logically interacting and / or logically interactable elements.

[0078] Furthermore, regarding any plural and / or singular terms used substantially in this invention, those skilled in the art can convert them from plural to singular and / or from singular to plural as appropriate for the content and / or application. For clarity, various singular / plural substitutions may be explicitly stated in this invention.

[0079] Furthermore, those skilled in the art will understand that, generally, the terms used in this invention, and especially in the appended claims (e.g., the body of the appended claims), are generally meant as "open-ended" terms. For example, the term "comprising" should be interpreted as "including but not limited to," the term "having" should be interpreted as "at least having," the term "comprising" should be interpreted as "including but not limited to," and so on. Those skilled in the art will also understand that if a specific number is intentionally listed in the introduced claim, such intention will be explicitly listed in the claim, and such intention will not exist in the absence of such listing. For example, to aid understanding, the appended claims may include the use of the introductory phrases "at least one" and "one or more." However, the use of such phrases should not be construed as implying that the introduction of the indefinite article "a" or "an" limits any particular claim that includes such an introduced claim list to only one implementation of such a list, even when the same claim includes the introductory phrase "a or more" or "at least one" and indefinite articles such as "a" or "an," for example, "a and / or one," should be interpreted as meaning "at least one" or "one or more." The same applies to the use of definite articles used to introduce the claim list. Furthermore, even when a specific number of introduced claims is explicitly listed, those skilled in the art will recognize that such a list should be interpreted as meaning at least the number listed; for example, in the absence of other modifiers, an unobstructed list of "two lists" means at least two lists or two or more lists. Furthermore, when using the convention of "at least one of A, B, and C," it is generally understood by a person skilled in the art to mean that such a convention is interpreted as follows (e.g., "a system having at least one of A, B, and C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together). When using the convention of "at least one of A, B, or C," it is generally understood by a person skilled in the art to mean that such a convention is interpreted as follows (e.g., "a system having at least one of A, B, or C" includes, but is not limited to, systems having A alone, having B alone, having C alone, having A and B together, having A and C together, having B and C together, and / or having A, B, and C together). A person skilled in the art will also understand that any transitional words and / or phrases that actually indicate two or more options, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one, any, or both of these items. For example, the phrase "A or B" would be understood to include the possibility of "A" or "B" or "A and B".

[0080] Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Various changes, modifications and combinations of the features in the various embodiments may be made without departing from the scope of protection of the present invention as defined in the claims. [Simplified Explanation of the Diagram]

[0010] The accompanying drawings, included to provide a further understanding of the invention, are incorporated in and constitute a part of this invention. The drawings illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention. It is understood that, in order to clearly illustrate the concepts of the invention, the drawings are not necessarily drawn to scale, and some elements shown may be shown at a scale greater than that of the actual embodiments. Figure 1 is a schematic diagram of an exemplary scenario of DCI reception corresponding to multiple cells according to the invention. Figure 2 is a schematic diagram of an exemplary scenario of two types of DCI structures according to the invention. Figure 3 is a block diagram of an exemplary communication system according to an embodiment of the invention. Figure 4 is a flowchart of an exemplary process according to an embodiment of the invention. Figure 5 is a flowchart of another exemplary process according to an embodiment of the invention.

Claims

1. A transmission scheduling method, comprising: A processor of a device receives downlink control information (DCI) indicating a scheduling of multiple cells from a network node of a wireless network, wherein the DCI includes a first DCI, a second DCI, or a third DCI, the first DCI corresponding to a single-segment DCI structure, and the second and third DCIs corresponding to a two-segment DCI structure; and the processor performs a Physical Downlink Shared Channel (PDSCH) reception or a Physical Uplink Shared Channel (PUSCH) transmission based on the DCI and at least one of the multiple cells, wherein the first DCI includes a common bit field and a plurality of designated bit fields corresponding to the multiple cells, the second DCI includes the common bit field and a first portion of designated bit fields corresponding to at least one of the multiple cells, and the third DCI includes a second portion of designated bit fields corresponding to at least one of the multiple cells, wherein the transmission scheduling method further includes: the processor receiving a Radio Resource Control (RRC) from the network node to configure a certain DCI field as the common bit field and some DCI fields as the plurality of designated bit fields.

2. The transmission scheduling method as described in request item 1, wherein, Further including: the processor receiving a bitmap, a Media Access Control (MAC) element (CE), a fourth DCI, or a predetermined rule from the network node to configure a certain DCI field as the common bit field and to configure certain DCI fields as the plurality of specified bit fields.

3. The transmission scheduling method as described in request item 1, wherein, The DCI includes at least one of the following: information indicating a type of the single-segment DCI structure or the two-segment DCI structure; information indicating which cell should be scheduled by the first DCI, the second DCI, or the third DCI; A number of carriers scheduled by the first DCI, the second DCI, or the third DCI; and matching information between the specified bit field and the plurality of cells scheduled by the first DCI, the second DCI, or the third DCI.

4. The transmission scheduling method as described in request item 1, wherein, Further includes: receiving, by the processor, a physical downlink control channel (PDCCH) scrambled by a first demodulation reference signal (DMRS) from the network node; and determining, by the processor, a number of cells scheduled by at least one of the first DCI, the second DCI, and the third DCI based on the first DMRS.

5. The transmission scheduling method as described in request item 1, wherein, Further includes: the processor receiving a PDCCH scrambled by a second DMRS from the network node; and the processor determining, based on the second DMRS, which cell is scheduled by the third DCI.

6. The transmission scheduling method as described in Request 1, wherein, The process further includes sending a report from the processor to the network node, wherein the report indicates the number of cells that can be simultaneously scheduled by one of the first DCI, the second DCI, and the third DCI.

7. The transmission scheduling method as described in Request 1, wherein, The further includes: receiving a configuration from the wireless network via the network node by the processor, wherein the configuration is used to configure a maximum number of cells simultaneously scheduled by at least one of the first DCI, the second DCI, and the third DCI.

8. The transmission scheduling method as described in request item 1, wherein, Further comprising: the processor determining a preparation time for the PUSCH, wherein the preparation time begins after the device receives a last symbol of the PDCCH and is determined based on a maximum time value from a set of different parameters of multiple cells.

9. The transmission scheduling method as described in claim 1, wherein, The process further includes: determining a processing time for the PDSCH by the processor, wherein the processing time begins after the device receives a last symbol of the PDSCH and is determined based on a maximum time value from a set of different parameters of multiple cells.

10. A transmission scheduling method, comprising: A processor in a network node configures downlink control information (DCI) for a device in a wireless network, indicating a schedule for multiple cells. The DCI includes a first DCI, a second DCI, or a third DCI. The first DCI corresponds to a single-segment DCI structure, and the second and third DCIs correspond to a two-segment DCI structure. The processor then sends the DCI to the device to schedule the reception of a Physical Downlink Shared Channel (PDSCH) or the transmission of a Physical Uplink Shared Channel (PUSCH) with at least one of the multiple cells. The first DCI includes a common bit field and multiple specified bit fields corresponding to the multiple cells. The second DCI includes the common bit field and a first portion of specified bit fields corresponding to at least one of the multiple cells. The third DCI includes a second portion of specified bit fields corresponding to at least one of the multiple cells. The transmission scheduling method further includes: the processor configuring a Radio Resource Control (RRC) for the device to configure a certain DCI field as the common bit field and some DCI fields as the plurality of specified bit fields.

11. The transmission scheduling method as described in claim 10, wherein, Further including: the processor sending a bitmap, a Media Access Control (MAC) control element (CE), a fourth DCI, or a predetermined rule to configure a certain DCI field as the common bit field and to configure certain DCI fields as the plurality of specified bit fields.

12. The transmission scheduling method as described in claim 10, wherein, The DCI includes at least one of the following: information indicating the type of the single-segment DCI structure or the two-segment DCI structure; information indicating which cell should be scheduled by the first DCI, the second DCI, or the third DCI; A number of carriers scheduled by the first DCI, the second DCI, or the third DCI; and matching information between the specified bit field and the plurality of cells scheduled by the first DCI, the second DCI, or the third DCI.

13. The transmission scheduling method as described in claim 10, wherein, The further includes: the processor sending a Physical Downlink Control Channel (PDCCH) scrambled with a first demodulation reference signal (DMRS) to the device, wherein the first DMRS indicates a number of cells scheduled by at least one of the first DCI, the second DCI, and the third DCI.

14. The transmission scheduling method as described in claim 10, wherein, Further includes: the processor sending a PDCCH scrambled by a second DMRS to the device, wherein the second DMRS indicates which cell is scheduled by the third DCI.

15. The transmission scheduling method as described in claim 10, wherein, The further includes: receiving a report from the device by the processor, wherein the report indicates the number of cells that can be simultaneously scheduled by one of the first DCI, the second DCI, and the third DCI.

16. The transmission scheduling method as described in claim 10, wherein, The further includes: the processor sending a configuration to the device, wherein the configuration is used to configure a maximum number of cells simultaneously scheduled by at least one of the first DCI, the second DCI, and the third DCI.

17. The transmission scheduling method as described in claim 10, wherein, Further comprising: the processor determining a preparation time for the PUSCH of the device, wherein the preparation time begins after the device receives a last symbol of the PDCCH and is determined based on a maximum time value from a set of different parameters of multiple cells.

18. The transmission scheduling method as described in claim 10, wherein, Further comprising: the processor determining a processing time for the PDSCH of the device, wherein the processing time begins after the device receives a last symbol of the PDSCH and is determined based on a maximum time value from a set of different parameters of multiple cells.

Images