Method and device for aligning downlink control information size in mobile communications

Abstract

Various solutions for downlink control information (DCI) size alignment for user equipment and network devices in mobile communications are described. The device may receive a configuration for configuring multiple DCI formats. The device may determine whether the number of DCI sizes for multiple DCI formats is greater than a DCI size budget. In the case where the number of DCI sizes is greater than the DCI size budget, the device may determine a DCI size to be monitored within the DCI size budget according to a DCI size alignment rule. The device may monitor the DCI format according to the determined DCI size.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application is a part of a non-provisional application claiming the benefit of priority of U.S. Patent Application No. 62 / 833,861, filed on April 15, 2019, the contents of which are incorporated herein by reference in their entirety. Technical Field

[0003] The present invention generally relates to mobile communications, and more particularly, to downlink control information (DCI) size alignment associated with user equipment (UE) and network devices in mobile communications. Background Art

[0004] Unless otherwise indicated herein, the approaches described in this section are not prior art to the claims listed below and are not admitted to be prior art by inclusion in this section.

[0005] In New Radio (NR), new DCI formats are introduced to provide better flexibility for scheduling specific services. For example, ultra-reliable and low latency communication (URLLC) is supported for emerging applications with high requirements for end-to-end latency and reliability. The general URLLC reliability requirement is that a 32-byte data packet should be transmitted in 10 -5 The probability of success is 1 millisecond of end-to-end delay. To meet the stringent delay and reliability requirements, the 3GPP (3 rd Two additional DCI sizes (e.g., compact DCI) were introduced in Release-16 of the 3rd Generation Partnership Project (3GPP) specification, mainly for scheduling URLLC services. For example, DCI format 0_2 is proposed for scheduling uplink data, and DCI format 1_2 is proposed for scheduling downlink data.

[0006] An agreement was reached in 3GPP to support a new DCI format with configurable size. For example, the maximum DCI size can be larger than the existing Release 15 DCI. The minimum DCI size can be reduced by 10 to 16 bits compared to the DCI format size of Release 15 DCI. DCI with configurable fields can be very beneficial. These fields can be configured to different bit widths depending on the application scenario. For example, when all functions are supported, some fields (e.g., fields related to multiple-input multiple-output (MIMO)) can be included in the enhanced URLLC (eURLLC) DCI. Therefore, a new DCI format with configurable size and flexible fields is important for accommodating URLLC / eURLLC services.

[0007] However, the new DCI format should be carefully designed so as not to increase the complexity of PDCCH monitoring and avoid confusion with fallback Release 15 DCI and non-fallback Release 15 DCI. Adding new DCI sizes monitored on the user equipment (UE) side will increase the total number of DCI sizes monitored and increase the complexity of UE blind decoding. On the other hand, if a new DCI format is introduced and if the size of the new DCI (possibly configurable size) may be similar or identical to an existing DCI format, it may be impossible for the UE to distinguish between the new DCI format and other existing DCI formats. Therefore, some restrictions are needed to avoid such problems.

[0008] Therefore, for newly developed wireless communication networks, how to reduce the complexity of PDCCH monitoring and avoid confusion with existing DCI formats is an important issue. It is necessary to provide appropriate DCI size alignment rules and / or restrictions to reduce UE design complexity. Summary of the invention

[0009] The following summary of the invention is merely illustrative and is not intended to be limiting in any way. That is, the following summary of the invention is provided to introduce the concepts, highlights, benefits, and advantages of the novel and non-obvious technologies described herein. Selected implementations are further described in the detailed description below. Therefore, the following summary of the invention is not intended to identify the essential features of the claimed subject matter, nor is it intended to be used to determine the scope of the claimed subject matter.

[0010] The object of the present invention is to propose a solution or mechanism to solve the above-mentioned problems related to the DCI size alignment between user equipment and network devices in mobile communications.

[0011] In one aspect, a method may involve receiving, by an apparatus, a configuration for configuring a plurality of DCI formats. The method may also involve the apparatus determining whether the number of DCI sizes of the DCI format is greater than the DCI size budget. The method may further involve, in the case where the number of DCI sizes is greater than the DCI size budget, the apparatus determining, according to a DCI size alignment rule, a DCI size to monitor within the DCI size budget. The method may further involve the apparatus monitoring the DCI format according to the determined DCI size.

[0012] In one aspect, a method may involve determining, by a device, that a number of DCI sizes is greater than a DCI size budget. The method may also involve determining, by the device, whether a first payload size of a first DCI format is less than a second payload size of a second DCI format. The method may further involve, in a case where the first payload size of the first DCI format is less than the second payload size of the second DCI format, adding, by the device, a plurality of zero padding bits to the first DCI format until the first payload size of the first DCI format is equal to the second payload size of the second DCI format. The method may further involve sending, by the device, the first DCI format with zero padding bits.

[0013] In one aspect, a method may involve determining, by an apparatus, whether a first payload size of a first DCI format is equal to a second payload size of a second DCI format. The method may also involve, if the first payload size of the first DCI format is equal to the second payload size of the second DCI format, the apparatus appending zero padding bits to the first DCI format. The method may further involve the apparatus sending the first DCI format with zero padding bits.

[0014] It is worth noting that although the description provided herein may be in the context of certain radio access technologies, networks and network topologies, such as Long-Term Evolution (LTE), LTE-A, LTE-A Pro, 5G, New Radio (NR), Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT) and Industrial Internet of Things (IIoT), the proposed concepts, schemes and any variants / derivatives thereof may be implemented in, for and through other types of radio access technologies, networks and network topologies. Therefore, the scope of the present invention is not limited to the examples described herein. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The accompanying drawings are included to provide a further understanding of the present invention, are incorporated into the present invention and constitute a part of the present invention. The accompanying drawings illustrate implementations of the present invention and together with the description serve to explain the principles of the present invention. It is understood that the drawings are not necessarily to scale, as some components may be shown out of proportion to the size in the actual implementation in order to clearly illustrate the concept of the present invention.

[0016] Figure 1 An exemplary scenario according to an embodiment of the present invention is shown.

[0017] Figure 2 Block diagrams of an example communication device and an example network device according to embodiments of the present invention are shown.

[0018] Figure 3 A flow chart showing an example process according to an embodiment of the invention is shown.

[0019] Figure 4 A flow chart showing an example process according to an embodiment of the invention is shown.

[0020] Figure 5 A flow chart showing an example process according to an embodiment of the invention is shown. DETAILED DESCRIPTION

[0021] Detailed embodiments and implementations of the claimed subject matter are disclosed herein. However, it should be understood that the disclosed detailed embodiments and implementations are only for the purpose of illustrating the claimed subject matter embodied in various forms. However, the present invention can be embodied in a variety of different forms and should not be construed as being limited to the illustrative embodiments and implementations. These illustrative embodiments and implementations are provided to make the description of the present invention comprehensive and complete and to fully convey the scope of the present invention to those of ordinary skill in the art. In the following description, details of known features and technologies are omitted to avoid unnecessarily obscuring the embodiments and implementations of the present invention.

[0022] Overview

[0023] The implementation of the present invention relates to various technologies, methods, schemes and / or solutions related to DCI size alignment related to user equipment and network devices in mobile communications. According to the present invention, many possible solutions can be implemented individually or jointly. That is, although these possible solutions can be described separately below, two or more of these possible solutions can be implemented in one combination or another combination.

[0024] In NR, new DCI formats are introduced to provide better flexibility for scheduling specific services. For example, URLLC is supported for emerging applications with high requirements for end-to-end delay and reliability. The general URLLC reliability requirement is that a data packet of size 32 bytes should be transmitted in 10 -5 The success probability of the transmission is within 1 millisecond end-to-end delay. In order to meet the strict delay and reliability requirements, two additional DCI sizes (e.g., compact DCI) were introduced in Release-16 of the 3GPP specification, mainly for scheduling URLLC services. For example, DCI format 0_2 is proposed for scheduling uplink data, and DCI format 1_2 is proposed for scheduling downlink data.

[0025] An agreement was reached in 3GPP to support a new DCI format with configurable size. For example, the maximum DCI size can be larger than the existing Release 15 DCI. The minimum DCI size can be reduced by 10 to 16 bits compared to the DCI format size of Release 15 DCI. DCI with configurable fields can be very beneficial. These fields can be configured to different bit widths depending on the application scenario. For example, when all functions are supported, some fields (e.g., fields related to MIMO) can be included in the eURLLC DCI. Therefore, a new DCI format with configurable size and flexible fields is important for accommodating URLLC / eURLLC services.

[0026] However, the new DCI format should be carefully designed to avoid increasing the complexity of PDCCH monitoring and to avoid confusion with fallback Release 15 DCI and non-fallback Release 15 DCI. The fallback DCI of Release 15 may include DCI format 0_0 and DCI format 1_0. The non-fallback DCI of Release 15 may include DCI format 0_1 ​​and DCI format 1_1. Adding new DCI sizes monitored on the UE side will increase the total number of DCI sizes monitored and increase the complexity of UE blind decoding. On the other hand, if a new DCI format is introduced and if the size of the new DCI (possibly configurable size) may be similar or identical to an existing DCI format, it is impossible for the UE to distinguish between the new DCI format and other existing DCI formats. Therefore, some restrictions are needed to avoid such problems.

[0027] In view of the above, the present invention proposes a variety of schemes for DCI size alignment and restriction for UE and network devices. It is agreed to maintain the same DCI size budget in version 16 as in version 15. Therefore, some DCI size alignment rules are proposed to limit the number of possible DCI sizes monitored on the UE side. According to the scheme of the present invention, the total number of different DCI sizes monitored by the UE will not exceed a predetermined number (e.g., 4) for a cell. Moreover, the total number of different DCI sizes with a cell-radio network temporary identifier (C-RNTI) monitored by the UE will not exceed a predetermined number (e.g., 3) for the cell. When the total number of different DCI sizes exceeds a predetermined number, the DCI sizes of different DCI formats can be aligned with each other to reduce the total number of different DCI sizes. On the other hand, when the DCI size of the new DCI format is the same as the DCI size of the existing DCI format, a zero padding bit can be added to the new DCI format to distinguish the new DCI format from the existing DCI format. Therefore, the complexity of UE monitoring and blind decoding can be reduced, and the risk of confusion between new DCI formats and existing DCI formats can be avoided.

[0028] In NR, new DCI formats are introduced to schedule traffic for specific services (e.g., URLLC / eURLLC services). For example, DCI format 0_2 is proposed to schedule uplink data (e.g., physical uplink shared channel (PUSCH)), and DCI format 1_2 is proposed to schedule downlink data (e.g., physical downlink shared channel (PDSCH)). The new DCI format can coexist with existing DCI formats (e.g., fallback DCI and non-fallback DCI). Fallback DCI may include DCI format 0_0 for scheduling PUSCH and DCI format 1_0 for scheduling PDSCH. Non-fallback DCI may include DCI format 0_1 ​​for scheduling PUSCH or indicating downlink feedback information for a configured authorized PUSCH, and DCI format 1_1 for scheduling PDSCH and / or triggering a single (one shot) hybrid automatic repeat request-acknowledgement (HARQ-ACK) codebook feedback. Fallback DCI has fewer bits than non-fallback DCI, so it has higher reliability and less scheduling flexibility. Therefore, the network node needs to configure multiple DCI formats for the UE. The UE needs to monitor different DCI formats with different DCI sizes.

[0029] Specifically, the network node can configure multiple DCI formats to the UE for monitoring by the UE via radio resource control (RRC) configuration. In order not to increase the complexity of UE monitoring and blind decoding, 5G NR of Release 15 and Release 16 define a DCI size budget. For one cell, the maximum number of DCI sizes monitored by the UE is 4. For one cell, the total number of different DCI sizes with C-RNTI is 3. Therefore, the network node determines whether the number of configured DCI sizes monitored by the UE is greater than the DCI size budget. In the case where the number of DCI sizes is greater than the DCI size budget, the network node can be configured to apply / use DCI size alignment rules to reduce the total number of different DCI sizes.

[0030] Figure 1An example scenario under a scheme according to an embodiment of the present invention is shown. Scenarios 101, 102, and 103 may involve a UE and a network node, which may be part of a wireless communication network (e.g., an LTE network, an LTE-A network, an LTE-A Pro network, a 5G network, an NR network, an IoT network, an NB-IoT network, or an IIoT network). The UE may be configured by the network node to monitor multiple DCI formats. The DCI format may include, for example, but not limited to, DCI formats 0_1 and 0_2 for uplink PUSCH scheduling, DCI formats 1_0, 1_1, and 1_2 for downlink PDSCH scheduling, and DCI format 2_0 for slot format indicator (SFI) information. Therefore, as shown in scenario 101, the UE should monitor 5 DCI formats in which the CRC is scrambled by the C-RNTI and one DCI format in which the CRC is scrambled by the SFI-RNTI. Assume that these 6 different DCI formats include 6 different DCI sizes (e.g., size_1 to size_6). Therefore, the number of DCI sizes monitored by the UE is greater than the DCI size budget (e.g., 3 for C-RNTI and 1 for any other RNTI). Therefore, in this scenario, a DCI size alignment rule is needed.

[0031] For example, the network node may first align DCI formats 0_2 and 1_2. The DCI format with a smaller DCI size will be aligned with the DCI format with a larger DCI size. Assuming that size_5 is larger than size_2, DCI formats 0_2 and 1_2 will be aligned and both have size size_5, as shown in scenario 102. After alignment, the DCI sizes that the UE should monitor may be reduced to 4 DCI sizes scrambled by C-RNTI and 1 DCI size scrambled by SFI-RNTI. However, the number of monitored DCI sizes is still larger than the DCI size budget. Therefore, the network node may further align DCI formats 0_1 and 1_1. The DCI format with a smaller DCI size will be aligned with the DCI format with a larger DCI size. Assuming that size_4 is larger than size_1, DCI formats 0_1 and 1_1 will be aligned and both have size size_4, as shown in scenario 103. After alignment, the DCI sizes that the UE should monitor may be reduced to 3 DCI sizes scrambled by C-RNTI and 1 DCI size scrambled by SFI-RNTI, which is within the DCI size budget.

[0032] In some embodiments, when executing the DCI size alignment rule, the network node may be configured to determine whether the first payload size of the first DCI format is less than the second payload size of the second DCI format. For example, the network node may determine whether the number of information bits of the first DCI format is less than the second payload size of the second DCI format before adding zero padding bits. In the case where the first payload size of the first DCI format is less than the second payload size of the second DCI format, the network node may be configured to add multiple zero padding bits to the first DCI format until the first payload size of the first DCI format is equal to the second payload size of the second DCI format. For example, if the number of information bits of the DCI format is less than 12 bits, zeros should be appended to the DCI format until the payload size is equal to 12 bits. The network node may then be configured to send the first DCI format with zero padding bits.

[0033] In some implementations, the first DCI format may include DCI format 0_1. The second DCI format may include DCI format 1_1. By adding a plurality of zero padding bits to DCI format 0_1, the network node may align the DCI size of DCI format 0_1 ​​with the DCI size of DCI format 1_1.

[0034] In some implementations, the first DCI format may include DCI format 1_1. The second DCI format may include DCI format 0_1. By adding a plurality of zero padding bits to DCI format 1_1, the network node may align the DCI size of DCI format 1_1 with the DCI size of DCI format 0_1.

[0035] In some embodiments, a first DCI format may be monitored in a UE-specific search space. A second DCI format may be monitored in the UE-specific search space to schedule the same serving cell. DCI size alignment rules or restrictions may be specified / pre-stored in a network node, or may be configured semi-statically and / or dynamically by the network. For example, when a high priority service (e.g., URLLC / eURLLC service) is available, a DCI size alignment rule or restriction may be triggered.

[0036] On the other hand, when a new DCI format is introduced, some restrictions or rules may be used / applied to distinguish the new DCI format from the existing DCI format. Specifically, the network node may be configured to determine whether the first payload size of the first DCI format is equal to the second payload size of the second DCI format. In the case where the first payload size of the first DCI format is equal to the second payload size of the second DCI format, the network node may be configured to attach at least one (e.g., one or more) zero padding bits to the first DCI format. The zero padding bits are used to distinguish the first DCI format from the second DCI format. The network node may then send the first DCI format with the zero padding bits. Therefore, when a new DCI format is introduced, the network node may be configured to limit the first payload size of the first DCI format to be different from the second payload size of the second DCI format.

[0037] In some embodiments, the first DCI format (e.g., a newly introduced DCI format) may include at least one of DCI format 0_2 and DCI format 1_2. One or more zero padding bits may be appended to DCI format 0_2 and / or DCI format 1_2. The second DCI format may include at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1, and DCI format 1_1. The first DCI format may be monitored in a UE-specific search space. The second DCI format may be monitored in another / different or the same UE-specific search space.

[0038] On the UE side, the UE should know the DCI size alignment rules in order to determine what DCI size it needs to monitor. Based on the RRC configuration and the configured DCI format, the UE can first determine the DCI size it needs to monitor. In the case where the number of DCI sizes that need to be monitored is greater than the DCI size budget, the UE can determine the DCI size it needs to monitor within the budget based on the DCI size alignment rules.

[0039] Specifically, the UE may receive a configuration for configuring a plurality of DCI formats. The UE may determine whether the number of DCI sizes of these DCI formats is greater than the DCI size budget. In the case where the number of DCI sizes is greater than the DCI size budget, the UE may determine the DCI size to be monitored within the DCI size budget according to the DCI size alignment rule. The UE may then monitor the DCI format according to the determined DCI size.

[0040] In some embodiments, the DCI size alignment rule may include aligning a first payload size of a first DCI format with a second payload size of a second DCI format. Thus, the UE may be configured to monitor the first DCI format and the second DCI format through the same DCI size. The first DCI format may include at least one zero padding bit.

[0041] In some embodiments, the first DCI format may include DCI format 0_1. The second DCI format may include DCI format 1_1. The UE may be configured to monitor DCI format 0_1 ​​by using the DCI size of DCI format 1_1. DCI format 0_1 ​​may include at least one zero padding bit.

[0042] In some embodiments, the first DCI format may include DCI format 1_1. The second DCI format may include DCI format 0_1. The UE may be configured to monitor DCI format 1_1 by using the DCI size of DCI format 0_1. DCI format 1_1 may include at least one zero padding bit.

[0043] In some implementations, the UE may be configured to monitor a first DCI format in a UE-specific search space. The UE may be configured to monitor a second DCI format in the UE-specific search space to schedule the same serving cell.

[0044] Similarly, when a new DCI format is introduced, the UE can distinguish the new DCI format from the existing DCI format according to some restrictions or rules. The DCI size of the new DCI format is limited to be different from the existing DCI format (e.g., fallback DCI and non-fallback DCI). Specifically, the UE can be configured to distinguish the first DCI format from the second DCI format by at least one zero padding bit attached to the first DCI format. The first payload size of the first DCI format with zero padding bits is different from the second payload size of the second DCI format. The first DCI format (e.g., the newly introduced DCI format) may include at least one of DCI format 0_2 and DCI format 1_2. One or more zero padding bits may be attached to DCI format 0_2 and / or DCI format 1_2. The second DCI format may include at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1, and DCI format 1_1. The UE may be configured to monitor the first DCI format in a UE-specific search space. The UE may be configured to monitor the second DCI format in another / different or the same UE-specific search space.

[0045] Therefore, it is not expected that the UE monitors a first decoding PDCCH candidate with a DCI format of 0_0 / 1_0 and a second decoding PDCCH candidate with a DCI format of 0_2 / 1_2, wherein the two decoding PDCCH candidates are mapped to the same resource and the sizes of DCI formats 0_0 / 1_0 and 0_2 / 1_2 are the same. It is not expected that the UE monitors a first decoding PDCCH candidate with a DCI format of 0_1 / 1_1 and a second decoding PDCCH candidate with a DCI format of 0_2 / 1_2, wherein the two decoding PDCCH candidates are mapped to the same resource and the sizes of DCI formats 0_1 / 1_1 and 0_2 / 1_2 are the same.

[0046] Exemplary Implementations

[0047] Figure 2 An example communication device 210 and an example network device 220 according to an embodiment of the present invention are shown. Each of the communication device 210 and the network device 220 can perform various functions to implement the schemes, techniques, processes and methods described herein for DCI size alignment related to user equipment and network devices in wireless communication, including the above-mentioned scenarios / mechanisms and processes 300, 400 and 500 described below.

[0048] The communication device 210 may be part of an electronic device, which may be a UE such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 210 may be implemented in a smartphone, a smart watch, a personal digital assistant, a digital camera, or a computing device such as a tablet, a laptop, or a notebook computer. The communication device 210 may also be part of a machine-type device, which may be an IoT, NB-IoT, or IIOT device, a home device, a wired communication device, or a computing device such as a non-movable or fixed device. For example, the communication device 210 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 210 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 210 may include Figure 2The communication device 210 may also include one or more other components (e.g., an internal power supply, a display device, and / or a user interface device) that are not related to the proposed solution of the present invention, and therefore, for the sake of simplicity and brevity, the following Figure 2 These components of the communication device 210 are not described in FIG.

[0049] The network device 220 may be part of an electronic device, which may be a network node such as a base station, a small cell, a router, or a gateway. For example, the network device 220 may be implemented in an eNodeB in an LTE, LTE-A, or LTE-A Pro network, or in a gNB in ​​a 5G, NR, IoT, NB-IoT, or IIOT network. Alternatively, the network device 220 may be implemented in the form of one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. The network device 220 may include Figure 2 The network device 220 may also include one or more other components not related to the proposed solution of the present invention (e.g., an internal power supply, a display device and / or a user interface device), and for the sake of simplicity and brevity, the following Figure 2 These components of network device 220 are not described in FIG.

[0050] In one aspect, each of the processors 212 and 222 may be implemented in the form of one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even if the singular term "processor" is used here to refer to the processors 212 and 222, each of the processors 212 and 222 may include multiple processors in some implementations and may include a single processor in other implementations according to the present invention. On the other hand, each of the processors 212 and 222 may be implemented in the form of hardware (and optionally, firmware), and the electronic components of the hardware include, for example, 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 to achieve a specific purpose. In other words, in at least some embodiments, each of the processors 212 and 222 may be a dedicated device, which is specially designed, arranged and configured to perform specific tasks (including power consumption reduction) in devices (e.g., as shown in the communication device 210) and networks (e.g., as shown in the network device 220) according to various embodiments of the present invention.

[0051] In some implementations, the communication device 210 may further include a transceiver 216 coupled to the processor 212 and capable of wirelessly sending and receiving data. In some implementations, the communication device 210 may further include a memory 214 coupled to the processor 212 and capable of storing and accessing data therein by the processor 212. In some implementations, the network device 220 may further include a transceiver 226 coupled to the processor 222 and capable of wirelessly sending and receiving data. In some implementations, the network device 220 may further include a memory 224 coupled to the processor 222 and capable of storing and accessing data therein by the processor 222. Therefore, the communication device 210 and the network device 220 may wirelessly communicate with each other via the transceiver 216 and the transceiver 226, respectively. To help better understanding, the following description of the operation, functions and performance of each of the communication device 210 and the network device 220 is based on a mobile communication environment, wherein the communication device 210 is implemented in a communication device or UE or is implemented as a communication device or UE, and the network device 220 is implemented in a network node of a communication network or is implemented as a network node of a communication network.

[0052] In some embodiments, the processor 222 may be configured to configure multiple DCI formats to the communication device 210 via RRC configuration for monitoring by it. The processor 222 may be configured with a DCI size budget. The processor 222 may be configured to determine whether the number of DCI sizes that it is configured to monitor by the processor 212 is greater than the DCI size budget. In the case where the number of DCI sizes is greater than the DCI size budget, the processor 222 may be configured to apply / use DCI size alignment rules to reduce the total number of different DCI sizes.

[0053] In some embodiments, when executing the DCI size alignment rule, the processor 222 may be configured to determine whether the first payload size of the first DCI format is less than the second payload size of the second DCI format. For example, the processor 222 may determine whether the number of information bits of the first DCI format is less than the second payload size of the second DCI format before adding zero padding bits. In the case where the first payload size of the first DCI format is less than the second payload size of the second DCI format, the processor 222 may be configured to add multiple zero padding bits to the first DCI format until the first payload size of the first DCI format is equal to the second payload size of the second DCI format.

[0054] In some implementations, the processor 222 may align the DCI size of DCI format 0_1 ​​with the DCI size of DCI format 1_1 by adding a plurality of zero padding bits to DCI format 0_1.

[0055] In some implementations, the processor 222 may align the DCI size of DCI format 1_1 with the DCI size of DCI format 0_1 ​​by adding a plurality of zero padding bits to DCI format 1_1.

[0056] In some embodiments, when a new DCI format is introduced, the processor 222 may use / apply some restrictions or rules to distinguish the new DCI format from the existing DCI format. Specifically, the processor 222 may be configured to determine whether the first payload size of the first DCI format is equal to the second payload size of the second DCI format. In the case where the first payload size of the first DCI format is equal to the second payload size of the second DCI format, the processor 222 may be configured to attach at least one (e.g., one or more) zero padding bits to the first DCI format. The zero padding bits are used to distinguish the first DCI format from the second DCI format. Then, the processor 222 may send the first DCI format with zero padding bits via the transceiver 226.

[0057] In some embodiments, the processor 212 should know the DCI size alignment rules in order to determine what DCI size it needs to monitor. Based on the RRC configuration and the configured DCI format, the processor 212 can first determine the DCI size it needs to monitor. In the case where the number of DCI sizes that need to be monitored is greater than the DCI size budget, the processor 212 can determine the DCI size that it needs to monitor within the budget based on the DCI size alignment rules.

[0058] In some embodiments, the processor 212 may be configured to receive a configuration for configuring a plurality of DCI formats via the transceiver 216. The processor 212 may be configured to determine whether the number of DCI sizes of the DCI format is greater than the DCI size budget. In the case where the number of DCI sizes is greater than the DCI size budget, the processor 212 may be configured to determine the DCI size to be monitored within the DCI size budget according to the DCI size alignment rule. The processor 212 may then monitor the DCI format according to the determined DCI size.

[0059] In some embodiments, the DCI size alignment rule may include aligning a first payload size of the first DCI format with a second payload size of the second DCI format. Thus, the processor 212 may be configured to monitor the first DCI format and the second DCI format with the same DCI size. The first DCI format may include at least one zero padding bit.

[0060] In some implementations, the processor 212 may be configured to monitor DCI format 0_1 ​​by using the DCI size of DCI format 1_1. DCI format 0_1 ​​may include at least one zero padding bit.

[0061] In some embodiments, the processor 212 may be configured to monitor DCI format 1_1 by using the DCI size of DCI format 0_1. DCI format 1_1 may include at least one zero padding bit.

[0062] In some implementations, the processor 212 may be configured to monitor the first DCI format in a UE-specific search space.The processor 212 may be configured to monitor the second DCI format in the UE-specific search space to schedule the same serving cell.

[0063] In some embodiments, when a new DCI format is introduced, the processor 212 may distinguish the new DCI format from the existing DCI format according to some restrictions or rules. Specifically, the processor 212 may be configured to distinguish the first DCI format from the second DCI format by at least one zero padding bit attached to the first DCI format. The first payload size of the first DCI format with zero padding bits is different from the second payload size of the second DCI format. The processor 212 may be configured to monitor the first DCI format in a UE-specific search space. The processor 212 may be configured to monitor the second DCI format in another / different or the same UE-specific search space.

[0064] In some embodiments, it is not desirable for the processor 212 to monitor a first decoded PDCCH candidate having a DCI format 0_0 / 1_0 and a second decoded PDCCH candidate having a DCI format 0_2 / 1_2, wherein the two decoded PDCCH candidates are mapped to the same resource and the sizes of the DCI formats 0_0 / 1_0 and 0_2 / 1_2 are the same. It is not desirable for the processor 212 to monitor a first decoded PDCCH candidate having a DCI format of 0_1 / 1_1 and a second decoded PDCCH candidate having a DCI format of 0_2 / 1_2, wherein the two decoded PDCCH candidates are mapped to the same resource and the sizes of the DCI formats 0_1 / 1_1 and 0_2 / 1_2 are the same.

[0065] Illustrative Process

[0066] Figure 3 An example process 300 is shown in accordance with an embodiment of the present invention. Process 300 may be an example implementation, either partial or complete, of the above-described scenarios / schemes related to DCI size alignment in accordance with the present invention. Process 300 may represent an implementation of multiple features of communication device 210. Process 300 may include one or more operations, actions, or functions as shown in one or more of blocks 310, 320, 330, and 340. Although shown as discrete blocks, the various blocks of process 300 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks of process 300 may be arranged in accordance with Figure 3 The process 300 may be performed in the order shown in , or may be performed in a different order. The process 300 may be implemented by the communication device 210 or any suitable UE or machine type device. For illustrative purposes only and not limiting, the process 300 is described below in the context of the communication device 210. The process 300 starts at block 310.

[0067] At 310, process 300 may involve processor 212 of apparatus 210 receiving a configuration for configuring a plurality of DCI formats. Process 300 may proceed from 310 to 320.

[0068] At 320 , process 300 may involve processor 212 determining whether the number of DCI sizes for the DCI format is greater than a DCI size budget. Process 300 may proceed from 320 to 330 .

[0069] At 330 , process 300 may involve, if the number of DCI sizes is greater than the DCI size budget, processor 212 determining a DCI size to monitor within the DCI size budget according to a DCI size alignment rule. Process 300 may proceed from 330 to 340 .

[0070] At 340 , process 300 may involve processor 212 monitoring the DCI format based on the determined DCI size.

[0071] In some implementations, the DCI size alignment rule may include aligning a first payload size of a first DCI format with a second payload size of a second DCI format.

[0072] In some implementations, the first DCI format may include DCI format 0_1. The second DCI format may include DCI format 1_1.

[0073] In some implementations, the first DCI format may include DCI format 1_1. The second DCI format may include DCI format 0_1.

[0074] In some implementations, process 300 may involve processor 212 monitoring a first DCI format and a second DCI format with the same DCI size.The first DCI format may include at least one zero padding bit.

[0075] In some implementations, process 300 may involve processor 212 monitoring a first DCI format in a UE-specific search space.Process 300 may further involve processor 212 monitoring a second DCI format in the UE-specific search space to schedule the same serving cell.

[0076] In some implementations, process 300 may involve processor 212 distinguishing a first DCI format from a second DCI format by appending zero padding bits to the first DCI format. A first payload size of the first DCI format with zero padding bits may be different from a second payload size of the second DCI format.

[0077] In some embodiments, the first DCI format may include at least one of DCI format 0_2 and DCI format 1_2. The second DCI format may include at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1, and DCI format 1_1.

[0078] In some implementations, process 300 may involve processor 212 monitoring a first DCI format in a UE-specific search space.Process 300 may further involve processor 212 monitoring a second DCI format in another UE-specific search space.

[0079] Figure 4 An example process 400 is shown in accordance with an embodiment of the present invention. Process 400 may be an example implementation, either partial or complete, of the above-described scenarios / schemes related to DCI size alignment according to the present invention. Process 400 may represent an implementation of multiple features of network device 220. Process 400 may include one or more operations, actions, or functions as shown in one or more of blocks 410, 420, 430, and 440. Although shown as discrete blocks, the various blocks of process 400 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks of process 400 may be arranged as follows: Figure 4 4. The process 400 may be performed in the order shown in FIG. 4 or may be performed in a different order. The process 400 may be implemented by the network device 220 or any suitable machine type device. For illustrative purposes only and not limiting, the process 400 is described below in the context of the network device 220. The process 400 begins at block 410.

[0080] At 410 , process 400 may involve processor 222 of apparatus 220 determining whether the number of DCI sizes is greater than a DCI size budget. Process 400 may proceed from 410 to 420 .

[0081] At 420 , process 400 may involve processor 222 determining whether a first payload size of a first DCI format is less than a second payload size of a second DCI format. Process 400 may proceed from 420 to 430 .

[0082] At 430, process 400 may involve, if a first payload size of the first DCI format is less than a second payload size of the second DCI format, processor 222 adding a plurality of zero padding bits to the first DCI format until the first payload size of the first DCI format is equal to the second payload size of the second DCI format. Process 400 may proceed from 430 to 440.

[0083] At 440 , process 400 may involve processor 222 sending the first DCI format with zero padding bits.

[0084] In some implementations, the first DCI format may include DCI format 0_1. The second DCI format may include DCI format 1_1.

[0085] In some implementations, the first DCI format may include DCI format 1_1. The second DCI format may include DCI format 0_1.

[0086] In some implementations, process 400 may involve processor 222 determining whether the number of information bits of the first DCI format before adding zero padding bits is less than a second payload size of the second DCI format.

[0087] In some implementations, the first DCI format may be monitored in a UE-specific search space.The second DCI format may be monitored in the UE-specific search space to schedule the same serving cell.

[0088] Figure 5 An example process 500 is shown in accordance with an embodiment of the present invention. Process 500 may be an example implementation, either partial or complete, of the above-described scenarios / schemes related to DCI size alignment in accordance with the present invention. Process 500 may represent an implementation of multiple features of network device 220. Process 500 may include one or more operations, actions, or functions as shown in one or more of blocks 510, 5205, and 530. Although shown as discrete blocks, the various blocks of process 500 may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation. In addition, the blocks of process 500 may be arranged as follows: Figure 5 5. The process 500 may be performed in the order shown in FIG. 5 or may be performed in a different order. The process 500 may be implemented by the network device 220 or a machine-type device. For illustrative purposes only and not limiting, the process 500 is described below in the context of the network device 220. The process 500 begins at block 510.

[0089] At 510 , process 500 may involve processor 222 of apparatus 220 determining whether a first payload size of a first DCI format is equal to a second payload size of a second DCI format. Process 500 may proceed from 510 to 520 .

[0090] At 520 , process 500 may involve processor 222 appending zero padding bits to the first DCI format if the first payload size of the first DCI format is equal to the second payload size of the second DCI format. Process 500 may proceed from 520 to 530 .

[0091] At 530 , process 500 may involve processor 222 sending the first DCI format with zero padding bits.

[0092] In some embodiments, the first DCI format may include at least one of DCI format 0_2 and DCI format 1_2. The second DCI format may include at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1, and DCI format 1_1.

[0093] In some implementations, the first DCI format may be monitored in a UE-specific search space.The second DCI format may be monitored in another UE-specific search space.

[0094] In some implementations, zero padding bits may be used to distinguish between the first DCI format and the second DCI format.

[0095] In some implementations, process 500 may involve processor 222 limiting a first payload size of a first DCI format to be different than a second payload size of a second DCI format.

[0096] Additional Notes

[0097] The subject matter described herein sometimes illustrates different components contained in or connected to different other components.It is to be understood that these depicted architectures are only examples, and in fact many other architectures that realize the same function can be implemented.In a conceptual sense, any arrangement of components that realize the same function is effectively "associated" so that the desired function is realized.Therefore, independent of the architecture or intermediate components, any two components that are combined to realize a specific function herein can be regarded as "associated" to each other so that the desired function is realized.Similarly, any two components so associated can also be regarded as "operationally connected" or "operationally coupled" to each other to realize the desired function, and any two components that can be so associated can also be regarded as "operationally couplable" to each other to realize the desired function.Specific examples of operation that can be coupled include but are not limited to physically matching and / or physically interactive components and / or wirelessly interactive and / or wirelessly interactive components and / or logically interactive and / or logically interactive components.

[0098] In addition, with respect to the extensive use of any plural and / or singular terms herein, those of ordinary skill in the art may convert from the plural to the singular and / or from the singular to the plural as needed for context and / or application. For the sake of clarity, various singular / plural reciprocities may be explicitly set forth herein.

[0099] In addition, those skilled in the art will understand that, in general, the terms used herein and especially in the appended claims (e.g., the bodies of the appended claims) are generally intended to be "open" terms, e.g., the term "comprising" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "including" should be interpreted as "including but not limited to", etc. Those skilled in the art will also understand that if a specific number of an introduced claim recitation is intended, such intent will be explicitly recited in the claim, and in the absence of such a recitation, no such intent is present. For example, as an aid to understanding, the appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of such phrases should not be interpreted as implying that a claim recitation, through the introduction of the indefinite article "a" or "an", will limit any particular claim that includes such introduced claim recitation to implementations that include only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article such as "a" or "an" (e.g., "a and / or an" should be interpreted as meaning "at least one" or "one or more"). In addition, even if a specific number of introduced claim recitations is explicitly recited, those skilled in the art will recognize that such recitation should be interpreted as meaning at least the recited number (e.g., an unmasked recitation of "two recitations" means at least two recitations or two or more recitations in the absence of other modifiers). Furthermore, in those cases where a convention similar to “at least one of A, B, and C, etc.” is used, such an interpretation is generally intended in the sense that a person skilled in the art would understand this convention (e.g., “a system having at least one of A, B, and C” would include but is not limited to systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In those cases where a convention similar to “at least one of A, B, or C, etc.” is used, such an interpretation is generally intended in the sense that a person skilled in the art would understand this convention (e.g., “a system having at least one of A, B, or C” would include but is not limited to systems having A alone, B alone, C alone, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). A person skilled in the art would also understand that any transitional words and / or phrases that actually present two or more alternative items, whether in the specification, claims, or drawings, should be understood to contemplate the possibility of including one, either, or both of these items. For example, the phrase "A or B" will be understood to include the possibilities of "A" or "B" or "A and B."

[0100] According to the above, it will be appreciated that various implementations of the present invention have been described herein for illustrative purposes, and various modifications may be made without departing from the scope and spirit of the present invention. Therefore, the various implementations disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the appended claims.

Claims

1. A wireless communication method, comprising: Receiving, by a processor of the device, a configuration for configuring a plurality of downlink control information (DCI) formats; determining, by the processor, whether a number of DCI sizes of the plurality of DCI formats is greater than a DCI size budget; If the number of the DCI sizes is greater than the DCI size budget, determining, by the processor, a DCI size to monitor within the DCI size budget according to a DCI size alignment rule; as well as monitoring, by the processor, the DCI format according to the determined DCI size; The DCI size alignment rule includes: First, the payload size of DCI format 0_2 and the payload size of DCI format 1_2 are aligned; wherein the DCI format 0_2 and the DCI format 1_2 have configurable fields; the configurable fields can be configured to different bit widths; After the payload size of the DCI format 0_2 and the payload size of the DCI format 1_2 are aligned, if the number of the DCI sizes is still greater than the DCI size budget, the payload size of the DCI format 0_1 ​​and the payload size of the DCI format 1_1 are aligned.

2. The method according to claim 1, further comprising: monitoring, by the processor, the DCI format 0_1 ​​and the DCI format 1_1 with the same DCI size, The DCI format 0_1 ​​or the DCI format 1_1 includes at least one zero padding bit.

3. The method according to claim 1, further comprising: Monitoring, by the processor, the DCI format 0_1 ​​in a search space specific to a user equipment UE; as well as The processor monitors the DCI format 1_1 in the UE-specific search space to schedule the same serving cell.

4. The method according to claim 1, further comprising: The processor distinguishes the first DCI format from a second DCI format by appending zero padding bits to the first DCI format; A first payload size of the first DCI format having zero padding bits is different from a second payload size of the second DCI format.

5. The method according to claim 4, wherein: The first DCI format includes at least one of DCI format 0_2 and DCI format 1_2.

6. The method according to claim 5, wherein: The second DCI format includes at least one of DCI format 0_0, DCI format 1_0, DCI format 0_1 ​​and DCI format 1_1.

7. The method according to claim 4, further comprising: Monitoring, by the processor, the first DCI format in a search space specific to a user equipment UE; as well as The second DCI format is monitored, by the processor, in another UE-specific search space.

8. A wireless communication method, comprising: determining, by a processor of the device, that a number of the plurality of downlink control information (DCI) sizes is greater than a DCI size budget; The processor first aligns the payload size of DCI format 0_2 with the payload size of DCI format 1_2; wherein the DCI format 0_2 and the DCI format 1_2 have configurable fields; the configurable fields can be configured to have different bit widths; after aligning the payload size of the DCI format 0_2 with the payload size of the DCI format 1_2, if the number of the DCI sizes is still greater than the DCI size budget, aligning the payload size of the DCI format 0_1 ​​with the payload size of the DCI format 1_1.

9. The method according to claim 8, wherein: Aligning the payload size of DCI format 0_1 ​​with the payload size of DCI format 1_1 includes: when the payload size of the first DCI format is smaller than the payload size of the second DCI format, the processor adds multiple zero padding bits to the first DCI format until the payload size of the first DCI format is equal to the payload size of the second DCI format; wherein the first DCI format includes DCI format 0_1 ​​and the second DCI format includes DCI format 1_1, or the first DCI format includes DCI format 1_1 and the second DCI format includes DCI format 0_1.

10. The method according to claim 9, wherein: Also includes: The first DCI format with the zero padding bits is sent by the processor.

11. The method according to claim 9, wherein: The step of determining whether the payload size of the first DCI format is smaller than the payload size of the second DCI format includes determining whether the number of information bits in the first DCI format before adding the zero padding bits is smaller than the payload size of the second DCI format.

12. The method according to claim 9, wherein: The first DCI format is monitored in a UE-specific search space, and the second DCI format is monitored in the UE-specific search space to schedule the same serving cell.

Images