Method and user equipment for constructing downlink control information format

Abstract

A user equipment (UE) and method for constructing a downlink control information format, the method comprising: receiving a radio resource control (RRC) message from a base station (BS), the RRC message including information for configuring a hybrid automatic repeat request acknowledgement (HARQ-ACK) codebook list, first downlink control information (DCI), and second DCI; determining a size difference between a first downlink assignment index (DAI) field of the first DCI and a second DAI field of the second DCI; and when the size difference between the first DAI field of the first DCI and the second DAI field of the second DCI is determined, inserting at least one zero-valued bit into one of the first DAI field and the second DAI field, wherein the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicated by the first DCI and a second HARQ-ACK codebook indicated by the second DCI.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This disclosure claims the benefit of and priority to provisional U.S. patent application serial number 62 / 932,206, filed on November 7, 2019 (“‘206 Provisional”), entitled “Handling of DCI size budge per serving cell.” The contents of the ’206 Provisional are hereby incorporated by reference in their entirety for all purposes. Technical Field

[0003] The present disclosure relates generally to wireless communications, and more particularly, to methods and apparatus for construction of downlink control information (DCI) formats. Background Art

[0004] With the tremendous growth in the number of connected devices and the rapid increase in user / network (NW) communication volume, various efforts have been made to improve different aspects of wireless communications in next-generation wireless communication systems such as fifth-generation (5G) New Radio (NR) by enhancing data rate, latency, reliability, and flexibility.

[0005] The 5G NR system is designed to provide flexibility and configurability to optimize NW services and types to accommodate various use cases such as enhanced mobile broadband (eMBB), massive machine-type communications (mMTC), and ultra-reliable low-latency communications (URLLC).

[0006] However, as the demand for radio access continues to increase, there is a need in the art to unify the different DCI formats. Summary of the Invention

[0007] The present disclosure relates to a method and apparatus for constructing a DCI format.

[0008] According to one aspect of the present disclosure, a method for constructing a downlink control information format performed by a user equipment (UE) is provided. The method includes: receiving a radio resource control (RRC) message from a base station (BS), the RRC message including information for configuring a hybrid automatic repeat request acknowledgment (HARQ-ACK) codebook list, a first downlink control information (DCI), and a second DCI, wherein the first DCI and the second DCI have the same format; determining whether there is a size difference between a first downlink assignment index (DAI) field of the first DCI and a second DAI field of the second DCI; and when it is determined that there is the size difference between the first DAI field of the first DCI and the second DAI field of the second DCI, inserting at least one bit having a zero value into one of the first DAI field and the second DAI field, wherein the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicated by the first DCI and a second HARQ-ACK codebook indicated by the second DCI.

[0009] According to another aspect of the present disclosure, a user equipment (UE) for constructing a downlink control information format in a wireless communication system having a base station (BS) is provided. The UE includes a memory and at least one processor coupled to the memory. The at least one processor is configured to: receive a radio resource control (RRC) message from the BS, the RRC message including information for configuring a hybrid automatic repeat request confirmation (HARQ-ACK) codebook list, first downlink control information (DCI), and second DCI, wherein the first DCI and the second DCI have the same format; determine whether there is a size difference between a first downlink assignment index (DAI) field of the first DCI and a second DAI field of the second DCI; and when it is determined that the size difference exists between the first DAI field of the first DCI and the second DAI field of the second DCI, insert at least one bit having a zero value into one of the first DAI field and the second DAI field, wherein the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicated by the first DCI and a second HARQ-ACK codebook indicated by the second DCI. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] Various aspects of the present disclosure are best understood from the following detailed description when read in conjunction with the accompanying drawings. Various features are not drawn to scale. The dimensions of various features may be arbitrarily increased or decreased for clarity of discussion.

[0011] Figure 1 The present invention relates to a DCI format construction process performed by a UE according to an exemplary embodiment of the present disclosure.

[0012] Figure 2 is a block diagram of a node for wireless communication according to an exemplary embodiment of the present disclosure. DETAILED DESCRIPTION

[0013] The following description contains specific information related to exemplary embodiments of the present disclosure. The drawings and the accompanying detailed disclosure are directed only to exemplary embodiments. However, the present disclosure is not limited to these exemplary embodiments. Other variations and embodiments of the present disclosure will occur to those skilled in the art. Unless otherwise indicated, identical or corresponding elements in the drawings may be represented by identical or corresponding reference designators. In addition, the drawings and illustrations in the present disclosure are generally not drawn to scale and are not intended to correspond to actual relative dimensions.

[0014] For consistency and ease of understanding, similar features are identified by numbers in the example figures (although not shown in some examples). However, features in different embodiments may be different in other aspects and should not be narrowly limited to the features shown in the figures.

[0015] References to "one embodiment," "an embodiment," "an exemplary embodiment," "various embodiments," "some embodiments," "embodiments of the present disclosure," etc., may indicate that embodiments of the present disclosure may include particular features, structures, or characteristics, but not every possible embodiment of the present disclosure must include the particular features, structures, or characteristics. Furthermore, repeated use of the phrases "in one embodiment," "in an exemplary embodiment," or "an embodiment" does not necessarily refer to the same embodiment, although they may be the same. Furthermore, any use of the phrases "embodiments" or the like in connection with "the present disclosure" does not necessarily mean that all embodiments of the present disclosure must include the particular features, structures, or characteristics, but rather that "at least some embodiments of the present disclosure" include the particular features, structures, or characteristics. The term "coupled" is defined as connected directly or indirectly through intermediate components and is not necessarily limited to physical connections. The term "comprising," when used, means "including, but not necessarily limited to," and it expressly indicates open inclusion or membership in the disclosed combinations, groups, series, and equivalents.

[0016] The term "and / or" is used herein only to describe the association relationship of associated objects and indicates that three relationships may exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. "A and / or B and / or C" can mean that at least one of A, B, and C exists. The character " / " used herein generally indicates that the former and the latter associated objects are in an "or" relationship.

[0017] In addition, for the purpose of non-limiting explanation, specific details such as functional entities, technologies, protocols, standards, etc. are set forth to provide an understanding of the disclosed technology. In other instances, detailed disclosure of well-known methods, technologies, systems, architectures, and the like are omitted to avoid obscuring the present disclosure with unnecessary details.

[0018] Those skilled in the art will immediately recognize that any (one or more) NW functions or (one or more) algorithms can be implemented by hardware, software, or a combination of software and hardware. The disclosed functions may correspond to modules, which may be software, hardware, firmware, or any combination thereof. Software implementations may include computer-executable instructions stored on computer-readable media such as memory or other types of storage devices. For example, one or more microprocessors or general-purpose computers with communication processing capabilities may be programmed with corresponding executable instructions and execute the disclosed (one or more) NW functions or (one or more) algorithms. The microprocessor or general-purpose computer may be composed of an application-specific integrated circuit (ASIC), a programmable logic array, and / or one or more digital signal processors (DSP). Although some of the disclosed example embodiments are oriented toward software installed and executed on computer hardware, alternative example embodiments implemented as firmware or hardware or a combination of hardware and software are within the scope of this disclosure.

[0019] Computer-readable media include, but are not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, compact disc read-only memory (CD-ROM), magnetic tape cassettes, magnetic tapes, disk storage devices, or any other equivalent medium that can store computer-readable instructions.

[0020] A radio communication NW architecture (such as a Long-Term Evolution (LTE) system, an Advanced LTE (LTE-Advanced, LTE-A) system, or an Advanced LTE Pro system) typically includes at least one base station (BS), at least one UE, and one or more optional NW elements that provide connectivity within the NW. The UE communicates with an NW (such as a Core Network (CN), an Evolved Packet Core (EPC) network, an Evolved Universal Terrestrial RAN (E-UTRAN), a Next-Generation Core (NGC), or the Internet) via a Radio Access Network (RAN) established by the BS.

[0021] It should be noted that in the present disclosure, a UE may include, but is not limited to, a mobile station, a mobile terminal or device, or a user communication radio terminal. For example, a UE may be a portable radio device, including, but not limited to, a mobile phone, a tablet, a wearable device, a sensor, or a personal digital assistant (PDA) with wireless communication capabilities. A UE may be configured to receive signals over an air interface and to transmit signals to one or more cells in a RAN.

[0022] The BS may include, but is not limited to, a Node B (NB) in the Universal Mobile Telecommunication System (UMTS), an evolved Node B (eNB) in LTE-A, a Radio Network Controller (RNC) in UMTS, a Base Station Controller (BSC) in the Global System for Mobile communication (GSM) / GERAN (Edge Radio Access Network), a next-generation eNB (ng-eNB) in an E-UTRA BS connected to a 5GC, a next-generation Node B (gNB) in a 5G Access Network (5G-AN), and any other device capable of controlling radio communications and managing radio resources within a cell. The BS may be connected to the NW via a radio interface to serve one or more UEs.

[0023] The BS may be configured to provide communication services based on at least one of the following radio access technologies (RATs): Worldwide Interoperability for Microwave Access (WiMAX), GSM (commonly referred to as 2G), GERAN, General Packet Radio Service (GPRS), UMTS based on basic Wideband-Code Division Multiple Access (W-CDMA) (commonly referred to as 3G), High-Speed Packet Access (HSPA), LTE, LTE-A, enhanced LTE (eLTE), NR (commonly referred to as 5G), and LTE-A Pro. However, the scope of the present disclosure should not be limited to the above protocols.

[0024] The BS may be operable to provide radio coverage to a specific geographical area using multiple cells included in the RAN. The BS may support the operation of cells. Each cell may be operable to provide services to at least one UE within its radio coverage. More specifically, each cell (commonly referred to as a serving cell) may provide services to one or more UEs within its radio coverage (for example, each cell schedules downlink (DL) resources and optional uplink (UL) resources to at least one UE within its radio coverage for DL and optional UL packet transmission). The BS may communicate with one or more UEs in a radio communication system through multiple cells. The cell may allocate sidelink (SL) resources to support proximity services (ProSe), LTE SL services, and LTE / NR vehicle-to-everything (V2X) services. Each cell may have a coverage area that overlaps with other cells. In the case of Multi-RAT Dual Connectivity (MR-DC), the master cell of the Master Cell Group (MCG) or the Secondary Cell Group (SCG) may be referred to as a Special Cell (SpCell). The Primary Cell (PCell) may refer to the SpCell of the MCG. The Primary SCG Cell (PSCell) may refer to the SpCell of the SCG. The MCG may refer to a group of service cells associated with the Master Node (MN), including the SpCell and optionally one or more Secondary Cells (SCell). The SCG may refer to a group of service cells associated with the Secondary Node (SN), including the SpCell and optionally one or more SCells.

[0025] As previously disclosed, the NR frame structure supports flexible configuration to accommodate various next-generation (e.g., 5G) communication requirements, such as eMBB, mMTC, and URLLC, while meeting high reliability, high data rate, and low latency requirements. rdThe Orthogonal Frequency-Division Multiplexing (OFDM) technology agreed upon in the 3GPP (3rd Generation Partnership Project) can be used as the baseline for the NR waveform. Scalable OFDM parameter sets such as adaptive subcarrier spacing, channel bandwidth, and cyclic prefix (CP) can also be used. Additionally, two coding schemes are applied to NR: (1) Low-Density Parity-Check (LDPC) and (2) Polar codes. Coding scheme adaptability can be configured based on channel conditions and / or service applications.

[0026] In addition, it should be considered that the transmission time interval of a single NR frame should include at least DL transmission data, guard period, and UL transmission data, where the respective parts of DL transmission data, guard period, and UL transmission data should also be configurable, for example, based on NR network dynamics. In addition, SL resources can also be provided in NR frames to support ProSe services.

[0027] In order to reduce device complexity, a "3+1" downlink control information (DCI) size budget is defined in the Rel-15 3GPP specification. In other words, as shown in Table 1, a UE (or another similar device) uses at most one cell radio network temporary identifier (C-RNTI) to monitor three different DCI sizes, and uses other RNTIs to monitor one DCI size. In order to comply with the DCI size budget of each serving cell of the UE, DCI size alignment is a process to ensure that the restrictions are met. In NRRel-16, smaller DCI sizes and new DCI formats for scheduling ultra-reliability low-latency communication (URLLC) data can be introduced. Specifically, the bit field width in the new DCI format field can be made configurable. In addition, a new DCI format for indicating the cancellation of uplink transmission can be introduced for URLLC. In addition, for power saving purposes, a new DCI format for providing an indication of power saving information used outside of active time can be introduced.

[0028] Table 1

[0029]

[0030] It has been agreed that for NR URLLC, the maximum time domain resource allocation (TDRA) table size will be increased to 64 to accommodate non-slot-based repetitions of the Physical Uplink Shared Channel (PUSCH). Furthermore, it has been agreed that the number of carrier indicator bits in the new DCI formats for DL scheduling and UL scheduling can be configured separately.

[0031] Furthermore, it has been agreed that, to support different service types, up to two Hybrid Automatic Repeat reQuest-ACKnowledge (HARQ-ACK) codebooks can be generated for a UE simultaneously. In other words, the PDSCH-HARQ-ACK-Codebook can be configured individually for each UE. In other words, different types of HARQ-ACK codebooks can be configured in the PUCCH-Config.

[0032] The introduction of new DCI for scheduling URLLC data, such as DCI formats 0-2, DCI formats 1-2, and DCI formats 2-4, may require further provisions for DCI size alignment. Since most bit field sizes in the new DCI format are configurable, this may lead to an increase in the diversity of DCI sizes. Therefore, an enhanced DCI size budget and detailed DCI size alignment should be defined. It is not yet clear how to align the new DCI format size with the old DCI format, and a detailed process should be introduced in the 3GPP specification. In addition, DCI sizes outside of active time also need to be considered, such as DCI formats 2-6 for scheduling power saving indications. In addition, unlike configuring cell group-specific HARQ-ACK codebook types, configuring physical uplink control channel (PUCCH)-resource-specific HARQ-ACK codebook types becomes more possible. In addition, larger TDRA table sizes are supported based on PUSCH repetition within a time slot. In addition, the configurable number of bits used for carrier indicators in the new DCI format means that carrier indicators for DL scheduling and UL scheduling can be configured separately. In other words, when the Physical Downlink Shared Channel (PDSCH) HARQ-ACK codebook is configured individually for a UE, the PUSCH TDRA size increases to 64 and the number of redundancy versions (RVs) becomes configurable, which may cause some impact on DCI fields (e.g., downlink assignment index (DAI), TDRA, RV). Therefore, solutions to the problems caused by configurable DCI fields need to be further clarified.

[0033] In some embodiments of the present disclosure, the new DCI formats used to schedule URLLC data (but not excluding scheduling other service types) may be DCI formats 1-2 (for DL) and DCI formats 0-2 (for UL), respectively. In some embodiments of the present disclosure, the new DCI formats used to notify a UE of the resources where a corresponding UL transmission from the UE may be canceled may be DCI formats 2-4. In some embodiments of the present disclosure, the new DCI formats used to indicate power saving information outside of active hours may be DCI formats 2-6.

[0034] Implementations of enhanced DCI size budget and detailed DCI size alignment may be presented below along with solutions A and B.

[0035] Solution A. The DCI size budget can remain the same as the value in Rel-15, i.e., "3+1" based on some predefined conditions, and the method for distinguishing DCI formats with the same payload size can be further clarified in the following:

[0036] ■A1. The payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-1 is equal to the payload size of DCI format 0-1; and the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2.

[0037] ■A2. The payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2; the payload size of DCI format 1-0 / 0-0 is equal to the payload size of DCI format 1-2 / 0-2.

[0038] ■A3. The payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-2 is equal to the payload size of DCI format 1-1; the payload size of DCI format 0-2 is equal to the payload size of DCI format 0-1.

[0039] ■A4. Regardless of whether DCI format 1-0 / 0-0 is monitored in the CSS or the USS, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0 monitored in the CSS; and, the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2.

[0040] Solution B. Increase the value of the DCI size budget to "4+1" or "3+2" without any condition or based on the reported UE capabilities or some predefined conditions as follows:

[0041] ■B1. For a DCI size budget value of "4+1", the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2.

[0042] ■B2. For a DCI size budget value of "4+1", regardless of whether DCI format 1-0 / 0-0 is monitored in the CSS or in the USS, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0 monitored in the CSS.

[0043] ■B3. For a DCI size budget value of "3+2", the payload sizes of DCI formats configured outside the active time (e.g., DCI formats 2-6) can be counted together with the payload sizes of DCI formats configured within the active time. Therefore, when the UE monitors three different DCI sizes using the C-RNTI and two different DCI sizes using other Radio Network Temporary Identifiers (RNTIs, such as Power Saving (PS)-RNTI), the above-mentioned DCI size alignment procedure (e.g., DCI budget "3+1" procedure) can be applied. More details are as follows:

[0044] ▲B3-1. A DCI size budget value of "3+2" or "3+1" may be used, depending on whether DCI formats 2-6 or other DCI formats outside of active time are configured.

[0045] If there are two or more different sizes for DCI format 2-6, one of the payload sizes of DCI format 2-6 must be aligned with DCI format 2-0 / 2-1 / 2-4 / 1-0 / 0-0. Note that DCI format 1-0 / 0-0 can be detected in the CSS.

[0046] ▲B3-3. The payload size of DCI format 2-1 must be aligned with the payload size of DCI format 2-4 according to certain conditions.

[0047] The following describes the impact on DCI format fields. This is because, for Type 2 configurations of grant configuration or semi-persistent scheduling, the payload size of the DCI format used for initial transmission may need to be the same as the payload size of the DCI format used for retransmission (e.g., a DCI format using Configured Scheduling (CS)-RNTI scrambling and a DCI format using C-RNTI scrambling). Furthermore, certain field positions may need to be aligned between the DCI format used for initial transmission and the DCI format used for retransmission. Furthermore, aligning the sizes of configurable fields across different DCI formats can reduce the diversity of DCI sizes.

[0048] First, if there are different types of PDSCH-HARQ-ACK-Codebooks configured to the UE (e.g., semi-static type and / or dynamic type), the size of the downlink assignment indicator (DAI) field may be equal to the size of the DCI used to schedule data corresponding to the type 2 HARQ-ACK codebook. Specifically, the type 1 HARQ-ACK codebook is referred to as a semi-static HARQ-ACK codebook, and the type 2 HARQ-ACK codebook is referred to as a dynamic HARQ-ACK codebook, respectively. Second, if the priority indication field is configured, the size of the field may be the same between different DCI formats and / or the same DCI format scrambled with different RNTIs. Third, for the TDRA field and the RV field, if the Rel-16 PUSCH scheme is configured, the size of the field may be aligned with the maximum size between different DCI formats and / or the same DCI format scrambled with different RNTIs.

[0049] More detailed disclosures / solutions / embodiments / examples / methods are given below. It is noteworthy that any two or more of the following paragraphs, solutions, embodiments, methods, examples, operations, points, actions, behaviors, items or claims can be logically, reasonably and appropriately combined to form a specific method. Any sentence, paragraph, solution, embodiment, method, example, operation, point, action, behavior, item or claim described below can be implemented independently and individually to form a specific method. Dependency, for example, "based on", "more specifically", "preferably", "in one embodiment" and the like in the following disclosure is only a possible example and does not limit the specific method.

[0050] Embodiments of the present disclosure include increasing the DCI size budget. Specifically, the possible DCI size budget may require some improvement. In one example, the DCI size budget remains the same as the DCI size budget of Rel-15. Preferably, for a cell, the total number of different DCI sizes configured for monitoring may be 4. Specifically, for the cell, the number of different DCI sizes scrambled with C-RNTI configured for monitoring may be 3, and the number of DCI sizes scrambled with other RNTIs configured for monitoring may be 1.

[0051] In one example, the DCI size budget is increased to 5. In one aspect of this example, for a cell, the total number of different DCI sizes configured for monitoring may be 5. Specifically, for the cell, the number of different DCI sizes with C-RNTI configured for monitoring may be 4, and the number of DCI sizes with other RNTIs configured for monitoring may be 1. In another aspect of this example, for the cell, the total number of different DCI sizes configured for monitoring may be 5. Specifically, for the cell, the number of different DCI sizes scrambled with C-RNTI configured for monitoring may be 3, and the number of DCI sizes scrambled with other RNTIs configured for monitoring may be 2.

[0052] In some embodiments, the DCI size budget can be explicitly determined based on reported UE capabilities. In one example, the UE may report the exact supported DCI size budget, and the UE may not expect to process a configuration that would result in the total number of different DCI sizes configured for monitoring exceeding that value for that cell. In another example, the UE may indicate a capability that indicates support for different service types for the cell based on that capability, and the UE may not expect to process a configuration that would result in the total number of different DCI sizes configured for monitoring exceeding a value or within a range for the cell. In another example, the UE may indicate multiple capabilities, such as DCI budgets "3+1" and "4+1," and the DCI budget applied may depend on the gNB's configuration. More specifically, if a DCI budget of "3+1" is applicable, the gNB may not configure the UE with such scheduling associated with a DCI budget of "4+1."

[0053] In some embodiments, the DCI size budget can be indirectly determined based on certain conditions. In one example, when a UE is directly or indirectly configured for power saving mode, a DCI size budget of "3+1" can be used as the default for the UE. More specifically, if a DCI size budget of "4+1" is initially applied to the UE, the UE can fall back to the default state (i.e., DCI budget of "3+1") after receiving certain instructions or configurations.

[0054] Similarly, in some embodiments, the DCI size budget can be indirectly determined based on some conditions. In another example, the DCI size budget can depend on the ability to indicate URLLC services, power saving services, or other types of services with different requirements. More details will be introduced in the following scenarios.

[0055] In one aspect of these examples, the DCI size budget may depend on the PDCCH monitoring capability reported by the UE. The PDCCH monitoring capability may indicate whether URLLC data is scheduled, so when certain specific monitoring spans are supported, such as the PDCCH monitoring span (2,2), the DCI size budget may be larger. Otherwise, there is no need to increase the DCI size budget.

[0056] In one aspect of these examples, the DCI size budget may depend on whether a new DCI format (eg, DCI Format 0-2 / DCI Format 1-2 / DCI Format 2-4 / DCI Format 2-6) is configured on the same carrier.

[0057] In one aspect of these examples, the DCI size budget may depend on whether different minimum PDSCH processing time capabilities on the same carrier are supported.

[0058] In one aspect of these examples, the DCI size budget may depend on whether out-of-order transmission on the same carrier is supported.

[0059] In one aspect of these examples, the DCI size budget may depend on whether intra-slot based PUSCH repetition on the same carrier is supported (eg, the PUSCH transmission scheme in Rel-16).

[0060] In one aspect of these examples, the DCI size budget may depend on whether multiple configured grants / SPS configurations on the same carrier are supported.

[0061] In one aspect of these examples, the DCI size budget may depend on whether cross-slot scheduling on the same carrier is supported.

[0062] In one aspect of these examples, the DCI size budget may depend on whether configuration of PDCCH-based indication of power saving information outside of active time is supported on the same carrier.

[0063] In one aspect of these examples, the DCI size budget may depend on whether the scheduled data or DCI is configured to the UE in a specific BWP or in a default BWP.

[0064] In one aspect of these examples, the DCI size budget may depend on whether the UE is configured for a long DRX state.

[0065] Embodiments of the present disclosure include improving DCI size alignment. Specifically, the DCI budget is equal to the DCI budget "3 + 1." If necessary, padding or truncation can be applied to the DCI format, and more details are presented in the following embodiments.

[0066] In one example, if the DCI budget "3+1" is applied, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-1 is equal to the payload size of DCI format 0-1; and the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2. An exemplary embodiment is shown in Table 2.

[0067] Table 2

[0068]

[0069]

[0070] In one example, if the DCI budget of "3+1" is applied, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2; and the payload size of DCI format 1-0 / 0-0 is equal to the payload size of DCI format 1-2 / 0-2. An exemplary embodiment is shown in Table 3.

[0071] Table 3

[0072]

[0073]

[0074] As shown in Table 3, in one aspect of this example, the payload size of DCI format 1-0 / 0-0 can be the same as the payload size of DCI format 1-2 / 0-2, and both can be scrambled using the C-RNTI. Therefore, further explanation may be needed to distinguish between DCI formats of the same size. A new field in the DCI format, such as an identifier, can be used. For example, "0" can refer to DCI format 1-0 / 0-0, and "1" can refer to DCI format 1-2 / 0-2. As another example, "0" can refer to DCI format 1-2 / 0-2, and "1" can refer to DCI format 1-0 / 0-0.

[0075] In another aspect of this example, a new field can be used to indicate the priority in the DCI format. For example, "0" can refer to DCI format 1-0 / 0-0; and "1" can refer to DCI format 1-2 / 0-2. As another example, "0" can refer to DCI format 1-2 / 0-2; and "1" can refer to DCI format 1-0 / 0-0.

[0076] In one aspect of this example, a new RNTI or Modulation Coding Scheme-Cell (MCS-C)-RNTI can be used to prioritize DCI formats. For example, if the payload size of DCI format 1-0 / 0-0 is the same as the payload size of DCI format 1-2 / 0-2, one of the DCI formats can be scrambled with the new RNTI or MCS-C-RNTI, and the DCI format scrambled with the new RNTI or MCS-C-RNTI can be referred to as DCI format 1-2 / 0-2. In another example, the DCI format scrambled with the new RNTI or MCS-C-RNTI can be referred to as DCI format 1-0 / 0-0.

[0077] In one aspect of this example, a CORESET or search space can be utilized. For example, DCI format 1-0 / 0-0 can be detected in a different CORESET / search space than DCI format 1-2 / 0-2. Another example can be that a specific CORESET ID or search space ID can refer to different DCI formats. Furthermore, DCI format 1-2 / 0-2 can be configured to a smaller CORESET ID / search space ID, and vice versa.

[0078] In one embodiment, if the DCI budget "3+1" is applied, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; the payload size of DCI format 1-2 is equal to the payload size of DCI format 1-1; and the payload size of DCI format 0-2 is equal to the payload size of DCI format 0-1. The specific implementation is shown in Table 4.

[0079] Table 4

[0080]

[0081]

[0082] As shown in Table 4, in one aspect of this example, the payload size of DCI format 1-1 can be the same as the payload size of DCI format 1-2, and the payload size of DCI format 0-1 can be the same as the payload size of DCI format 0-2. Therefore, more explanation may be needed to distinguish DCI formats of the same size. New fields in the DCI format, such as identifiers, can be used. For example, "0" can refer to DCI format 1-1 / 0-1, and "1" can refer to DCI format 1-2 / 0-2, and vice versa.

[0083] In one aspect of this example, a new field may be used to indicate the priority in the DCI format. For example, "0" may refer to DCI format 1-1 / 0-1; "1" may refer to DCI format 1-2 / 0-2, and vice versa.

[0084] In one aspect of this example, a new RNTI or MCS-C-RNTI may be used to prioritize DCI formats. For example, if the payload size of DCI format 1-1 / 0-1 is the same as the payload size of DCI format 1-2 / 0-2, one of the DCI formats may be scrambled with the new RNTI or MCS-C-RNTI, and the DCI format scrambled with the new RNTI or MCS-C-RNTI may be DCI format 1-2 / 0-2, and vice versa.

[0085] In one aspect of this example, a CORESET or search space can be used. For example, DCI format 1-1 / 0-1 can be monitored in a different CORESET / search space than DCI format 1-2 / 0-2. As another example, a specific CORESET ID or search space ID can refer to a different DCI format. Furthermore, DCI format 1-2 / 0-2 can be assigned a smaller CORESET ID / search space ID, and vice versa.

[0086] In one embodiment, if the DCI budget of "3+1" is applied, regardless of whether DCI format 1-0 / 0-0 is monitored in the CSS or the USS, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0 monitored in the CSS. In other words, the present disclosure discloses aligning the payload size of DCI format 1-0 / 0-0 monitored in the CSS with the payload size of DCI format 1-0 / 0-0 monitored in the USS, and the payload size of DCI format 1-0 / 0-0 monitored in the USS is given based on the size of the initial BWP or CORESET 0. In addition, the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2. An exemplary embodiment is shown in Table 5.

[0087] Table 5

[0088]

[0089]

[0090] Embodiments of the present disclosure include performing a DCI size alignment process on a DCI budget equal to "3+1". In one example, the DCI size alignment process may be applied according to the following six actions (i.e., actions 0 to 5, as shown below). Notably, in one embodiment, each action in the process may be arbitrarily combined or exchanged. Furthermore, in one embodiment, the DCI size alignment of DCI format 1-2 and DCI format 0-2 may be performed before or after the UE performs DCI size alignment for DCI format 0-0 and DCI format 1-0, and / or performs DCI size alignment for DCI format 0-1 and DCI format 1-1.

[0091] In one embodiment, the following actions may be examples of performing the DCI size alignment process of Table 2.

[0092] Action 0:

[0093] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 0-0 monitored in the CSS is determined, and the DCI format size may be related to the initial UL BWP.

[0094] It may be disclosed that, based on a given configuration (e.g., SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 1-0 monitored in the CSS is determined, and the DCI format size may be associated with: (1) the size of CORESET 0 (if CORESET 0 is configured for the cell); and (2) the size of the initial DL bandwidth portion (if CORESET 0 is not configured for the cell).

[0095] If DCI format 0-0 is monitored in the CSS, and if the number of information bits in DCI format 0-0 before padding is less than the payload size of DCI format 1-0 monitored in the CSS for scheduling the same serving cell, multiple zero padding bits can be generated for DCI format 0-0 until the payload size is equal to the payload size of DCI format 1-0.

[0096] If DCI format 0-0 is monitored in the CSS, and if the number of information bits in DCI format 0-0 before truncation is greater than the payload size of DCI format 1-0 monitored in the CSS for scheduling the same serving cell, the bit width of the frequency domain resource allocation field in DCI format 0-0 can be reduced by truncating the first few most significant bits so that the size of DCI format 0-0 is equal to that of DCI format 1-0.

[0097] Action 1:

[0098] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 0-0 monitored in the USS is determined, and the DCI format size may be related to the size of the active UL BWP.

[0099] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI formats 1-0 monitored in the USS are determined, and the DCI format size may be related to the size of the active DL BWP.

[0100] For a UE in a cell with supplementaryUplink configured in ServingCellConfig, if PUSCH is configured for transmission on both supplementary UL (SUL) and non-SUL of the cell, and if the number of information bits for DCI format 0-0 in the USS for SUL is not equal to the number of information bits for DCI format 0-0 in the USS for non-SUL, multiple zero padding bits may be generated for the smaller DCI format 0-0 until the payload size is equal to the payload size of the larger DCI format 0-0.

[0101] If DCI format 0-0 is monitored in the USS, and if the number of information bits in DCI format 0-0 before padding is less than the payload size of DCI format 1-0 monitored in the USS for scheduling the same serving cell, multiple zero padding bits may be generated for DCI format 0-0 until the payload size is equal to the payload size of DCI format 1-0.

[0102] If DCI format 1-0 is monitored in the USS, and if the number of information bits in DCI format 1-0 before padding is less than the payload size of DCI format 0-0 monitored in the USS for scheduling the same serving cell, zeros may be appended to DCI format 1-0 until the payload size is equal to DCI format 0-0.

[0103] Action 2:

[0104] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI formats 0-1 monitored in the USS are determined, and the DCI format size may be related to the size of the active UL BWP.

[0105] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 1-1 monitored in the USS is determined, and the DCI format size may be related to the size of the active DL BWP.

[0106] For a UE in a cell with supplementaryUplink configured in ServingCellConfig, if PUSCH is configured for transmission on both SUL and non-SUL of the cell, and if the number of information bits of DCI format 0-1 for SUL is not equal to the number of information bits of DCI format 0-1 for non-SUL, zeros may be appended to the smaller DCI format 0-1 until the payload size is equal to the larger DCI format 0-1.

[0107] If the size of DCI format 0-1 monitored in a USS is equal to the size of DCI format 0-0 / 1-0 monitored in another USS, one-bit zero padding may be appended to DCI format 0-1.

[0108] If the size of DCI format 1-1 monitored in a USS is equal to the size of DCI format 0-0 / 1-0 monitored in another USS, one-bit zero padding may be appended to DCI format 1-1.

[0109] Action 3:

[0110] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI formats 0-2 monitored in the USS are determined, and the DCI format size may be related to the size of the active UL BWP.

[0111] It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI formats 1-2 monitored in the USS are determined, and the DCI format size may be related to the size of the active DL BWP.

[0112] For a UE in a cell with supplementaryUplink configured in ServingCellConfig, if PUSCH is configured for transmission on both SUL and non-SUL of the cell, and if the number of information bits in DCI formats 0-2 for SUL is not equal to the number of information bits in DCI formats 0-2 for non-SUL, bits with values set to zero may be appended to the smaller DCI format 0-2 until the payload size is equal to the larger DCI format 0-2.

[0113] If DCI format 0-2 is monitored in the USS, and if the number of information bits in DCI format 0-2 before padding is less than the payload size of DCI format 1-2 monitored in the USS for scheduling the same serving cell, multiple zero padding bits may be generated for DCI format 0-2 until the payload size is equal to the payload size of DCI format 1-2.

[0114] If DCI format 1-2 is monitored in the USS, and if the number of information bits in DCI format 1-2 before padding is less than the payload size of DCI format 0-2 monitored in the USS for scheduling the same serving cell, multiple zero padding bits may be appended to DCI format 1-2 until the payload size is equal to the size of DCI format 0-2.

[0115] Action 4:

[0116] The size alignment process can be completed if the following two conditions are met: (1) for the cell, the total number of different DCI sizes configured for monitoring does not exceed 4; and (2) for the cell, the total number of different DCI sizes scrambled with C-RNTI configured for monitoring does not exceed 3.

[0117] Action 5:

[0118] Otherwise, the following operations may be performed.

[0119] ■ It may be disclosed to remove the padding bits introduced in action 2 above (if any).

[0120] ■ It may be disclosed that, based on a given configuration (e.g., SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 1-0 monitored in the USS is determined, and the DCI format size may be related to the size of the active DL BWP, where the active DL BWP is given by: (1) the size of CORESET 0 (if CORESET 0 is configured for the cell); and (2) the size of the initial DL BWP (if CORESET 0 is not configured for the cell).

[0121] ■ It may be disclosed that based on a given configuration (eg, SearchSpace-Config, PDCCH-Config) and / or RNTI, the DCI format 0-0 monitored in the USS is determined, and the DCI format size may be related to the size of the initial UL BWP.

[0122] ■If the number of information bits of the DCI format 0-0 monitored in the USS before padding is less than the payload size of the DCI format 1-0 monitored in the USS for scheduling the same serving cell, multiple zero padding bits can be generated for the DCI format 0-0 monitored in the USS until the payload size is equal to the payload size of the DCI format 1-0 monitored in the USS.

[0123] ■If the number of information bits of DCI format 0-0 monitored in the USS before truncation is larger than the payload size of DCI format 1-0 monitored in the USS for scheduling the same serving cell, the bit width of the frequency domain resource allocation field in DCI format 0-0 can be reduced by truncating the first few most significant bits so that the size of DCI format 0-0 monitored in the USS is equal to the size of DCI format 1-0 monitored in the USS.

[0124] In some embodiments, the UE may not expect to process a configuration that, after applying the above actions, would result in any of the following situations: (1) the total number of different DCI sizes configured for monitoring for the cell exceeds 4; (2) the total number of different DCI sizes with C-RNTI configured for monitoring for the cell exceeds 3; (3) the size of DCI format 0-0 in one USS can be equal to the size of DCI format 0-1 in the same USS or another USS; (4) the size of DCI format 0-2 in one USS can be equal to the size of DCI format 0-1 in the same USS or another USS; (5) the size of DCI format 1-0 in one USS can be equal to the size of DCI format 1-1 in the same USS or another USS; or (6) the size of DCI format 1-2 in one USS can be equal to the size of DCI format 1-1 in the same USS or another USS.

[0125] In some embodiments, the DCI budget is equal to "4+1". In one example, if the DCI budget "4+1" is applied, the payload size of DCI format 1-0 is equal to the payload size of DCI format 0-0; and the payload size of DCI format 1-2 is equal to the payload size of DCI format 0-2. The specific implementation is shown in Table 6.

[0126] Table 6

[0127]

[0128]

[0129] Furthermore, in one example, if the DCI budget of "4+1" is applied, regardless of whether DCI format 1-0 / 0-0 is monitored in the CSS or the USS, the payload size of DCI format 1-0 may be equal to the payload size of DCI format 0-0 monitored in the CSS. In other words, it is disclosed that the DCI format 1-0 / 0-0 monitored in the USS is determined, where the BWP is given by the initial BWP or the size of CORESET 0. An exemplary embodiment is shown in Table 7.

[0130] Table 7

[0131]

[0132]

[0133] In some embodiments, the DCI size budget can be equal to "3+2." In one example, there may be DCI formats configured outside of active time, such as DCI formats 2-6, in which case a DCI budget of "3+2" may be applied. The DCI size alignment process for C-RNTI-scrambled DCI formats can refer to the process mentioned in the previous paragraph and will be omitted for brevity.

[0134] In one aspect of this example, the payload size of a DCI format outside of active time may be equal to the payload size of a DCI format scrambled by a non-C-RNTI within active time. For example, if there are two or more different DCI format sizes outside of active time, DCI format 2-6 scrambled with PS-RNTI may have the same payload size as DCI format 2-0 scrambled with SFI-RNTI, DCI format 2-1 scrambled with INT-RNTI, DCI format 2-4 scrambled with CI-RNTI, DCI format 1-0 scrambled with non-CRNTI, or DCI format 0-0 scrambled with non-C-RNTI. Alternatively, DCI format 2-1 scrambled with INT-RNTI and DCI format 2-4 scrambled with CI-RNTI may have the same payload size.

[0135] In some embodiments, the disclosure considers the impact from a configurable bit field. First, the disclosure considers the DAI corresponding to the DAI field, which may include a counter DAI (cDAI) field and / or a total DAI (tDAI) field. In addition, the value of the cDAI field in the DCI format represents the cumulative number of {serving cell, PDCCH monitoring opportunity} pairs, where the number of PDSCH receptions or SPS PDSCH releases associated with the DCI format in the {serving cell, PDCCH monitoring opportunity} pair exists until the current serving cell and the current PDCCH monitoring opportunity. The value of the tDAI field (when present) in the DCI format represents the total number of {serving cell, PDCCH monitoring opportunity} pairs, where the number of PDSCH receptions or SPS PDSCH releases associated with the DCI format in the {serving cell, PDCCH monitoring opportunity} pair exists until the current PDCCH monitoring opportunity m, and its number is updated from the PDCCH monitoring opportunity. In addition, the UE may assume the same tDAI value in all DCI formats that include a tDAI field in the PDCCH monitoring opportunity m. The UE does not expect to multiplex HARQ-ACK information in the same Type 2 HARQ-ACK codebook in response to detecting DCI formats with cDAI fields of different number of bits.

[0136] In an example showing a wireless communication system including at least one BS and one UE, the UE may receive a radio resource control (RRC) message from the BS, the message including information for configuring a HARQ-ACK codebook list, a first DCI, and a second DCI, wherein the HARQ-ACK codebook list includes a first HARQ-ACK codebook indicated by the first DCI and a second HARQ-ACK codebook indicated by the second DCI. It is worth noting that the first priority of the first HARQ-ACK codebook and the second priority of the second HARQ-ACK codebook are different, and the first DCI and the second DCI have the same format. In another example, the UE may determine whether there is a size difference between the first DAI field of the first DCI and the second DAI field of the second DCI. In another example, when it is determined that there is a size difference between the first DAI field of the first DCI and the second DAI field of the second DCI, the UE may insert at least one bit having a zero value into one of the first DAI field and the second DAI field, wherein the inserted at least one zero-value bit forms the most significant bit in the first DAI field or the second DAI field. Preferably, the first HARQ-ACK codebook and the second HARQ-ACK codebook are of different types, where these types refer to a semi-static type and a dynamic type, respectively. Specifically, if different types of PDSCH-HARQ-ACK-Codebooks are configured to the UE, the size of the DAI field may be equal to the size of the DAI field in the DCI for scheduling data corresponding to the type 2 HARQ-ACK codebook. For example, if the UE configures PDSCH-HARQ-ACK-Codebook=semi-static and PDSCH-HARQ-ACK-Codebook=dynamic in PUCCH-Config, the number of bits of the DAI field in the DCI format for scheduling the PDSCH with the semi-static HARQ-ACK codebook may be zero, and the number of bits of the DAI field in the DCI format for scheduling the PDSCH with the dynamic HARQ-ACK codebook may be 2 or 4.

[0137] Specifically, in one aspect of this example, the DAI field in a DCI format for scheduling a PDSCH with a semi-static HARQ-ACK codebook may be configured with "00" or "0000." In other words, the UE may insert multiple bits into the DAI field in the corresponding DCI with a smaller bit size, where each bit is set to a value of zero. In another aspect of this example, the DAI field in a DCI format for scheduling a PDSCH with a semi-static HARQ-ACK codebook may be configured with "11" or "1111."

[0138] Figure 1FIG. 1 shows a DCI format construction process 10 performed by a UE according to an exemplary embodiment of the present disclosure. Figure 1 As shown, the DCI format construction process 10 for the UE includes:

[0139] ■Action 100: Start.

[0140] ■ Action 102: Receive an RRC message including information for configuring a HARQ-ACK codebook list, a first DCI, and a second DCI from the BS.

[0141] ■Action 104: Determine whether there is a size difference between the first DAI field of the first DCI and the second DAI field of the second DCI.

[0142] ■ Action 106: When it is determined that there is a size difference between the first DAI field of the first DCI and the second DAI field of the second DCI, insert at least one zero-valued bit into one of the first DAI field and the second DAI field.

[0143] ■Action 108: End.

[0144] Preferably, actions 102 to 106 of the DCI format construction process 10 are applicable to both UE and BS. Since the detailed operations of actions 102 to 106 have been fully discussed and / or introduced above, the details of the related operations are omitted for the sake of brevity.

[0145] Second, embodiments of the present disclosure consider a priority indication field. In one example, if the priority indication field is configured in the DCI format for a dynamic grant but not in the DCI format for a configured grant, the sizes of the fields may need to be the same to avoid ambiguity between (de)activation DCI and retransmission DCI.

[0146] Specifically, in one aspect of this example, the priority indication field may have the same bit width between (de)activation DCI and retransmission DCI. For example, the priority indication field may have a width of 1 bit in DCI for dynamic grants, while this field may be filled with "0" in DCI for configured grants. Optionally, in another aspect of this example, if the UE detects inconsistent information regarding the priority indication between different DCI formats or between the same DCI formats scrambled with different RNTIs, the UE may discard the priority information in the DCI format.

[0147] Third, embodiments of the present disclosure consider the TDRA field. In one example, if the Rel-16 PUSCH scheme is configured, the size of the TDRA field can be the minimum configured bit width between different DCI formats or the same DCI format scrambled with different RNTIs.

[0148] Fourth, embodiments of the present disclosure consider the RV field. In one example, the size of the RV field can be the maximum configured bit width between different DCI formats or the same DCI format scrambled with different RNTIs.

[0149] Figure 2 1 shows a block diagram of a node 200 for wireless communication according to various aspects of the present disclosure. Figure 2 As shown, the node 200 may include a transceiver 206, a processor 208, a memory 202, one or more presentation components 204, and at least one antenna 210. The node 200 may also include a radio frequency (RF) spectrum band module, a BS communication module, a NW communication module, and a system communication management module, input / output (I / O) ports, I / O components, and a power supply ( Figure 2 Each of these components may communicate with each other directly or indirectly via one or more buses 224. In one embodiment, the node 200 may be a UE or a BS, which performs, for example, Figure 1 Various functions are described here.

[0150] The transceiver 206 has a transmitter 216 (e.g., transmitting / transmission circuitry) and a receiver 218 (e.g., receiving / reception circuitry) and can be configured to transmit and / or receive time and / or frequency resource partitioning information. In one embodiment, the transceiver 206 can be configured to transmit in different types of subframes and time slots, including but not limited to usable, unusable, and flexibly usable subframe and time slot formats. The transceiver 206 can be configured to receive data and control channels.

[0151] Node 200 may include a variety of computer-readable media. Computer-readable media can be any available media that can be accessed by node 200, and includes both volatile (and non-volatile) media and removable (and non-removable) media. By way of example and not limitation, computer-readable media include computer storage media and communication media. Computer storage media may include volatile (and / or non-volatile) and removable (and / or non-removable) media implemented according to any method or technology for storing information such as computer-readable instructions, data structures, program modules, or data.

[0152] Computer storage media may include RAM, ROM, EEPROM, flash memory (or other storage technology), CD-ROM, Digital Versatile Disk (DVD) (or other optical disk storage), magnetic tape, magnetic disk storage (or other magnetic storage devices), etc. Computer storage media may not include propagated data signals. Communication media can generally contain computer-readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and include any information delivery media. The term "modulated data signal" refers to a signal having one or more characteristics that are set or changed in order to encode information in the signal. By way of example and not limitation, communication media can include wired media, such as a wired network or direct wired connection, and wireless media, such as acoustic, RF, infrared and other wireless media. Any combination of the above should also be included within the scope of computer-readable media.

[0153] The memory 202 may include computer storage media in the form of volatile and / or non-volatile memory. The memory 202 may be removable, non-removable, or a combination thereof. For example, the memory 202 may include solid-state memory, a hard drive, an optical drive, etc. Figure 2 As shown, the memory 202 may store computer-readable and / or computer-executable instructions 214 (e.g., software code) that, when executed, are configured to cause the processor 208 to perform various functions described herein, such as referring to Figure 1 Alternatively, instructions 214 may not be directly executable by processor 208, but may be configured to cause node 200 (eg, when compiled and executed) to perform the various functions described herein.

[0154] The processor 208 (e.g., having processing circuitry) may include an intelligent hardware device, a central processing unit (CPU), a microcontroller, an ASIC, etc. The processor 208 may include a memory. The processor 208 may process data 212 and instructions 214 received from the memory 202, as well as information transmitted through the transceiver 206, the baseband communication module, and / or the network communication module. The processor 208 may also process information to be sent to the transceiver 206 for transmission to the network communication module via the antenna 210 for transmission to the CN.

[0155] One or more presentation components 204 can present the data indication to a person or other device. Examples of presentation components 204 can include a display device, a speaker, a printing component, a vibration component, and the like.

[0156] As can be seen from this disclosure, various techniques can be used to implement the concepts described in this application without departing from the scope of these concepts. In addition, although these concepts have been described with specific reference to certain implementations, those of ordinary skill in the art will recognize that changes can be made in form and detail without departing from the scope of these concepts. Therefore, the described implementations will be considered illustrative and not restrictive in all aspects. It should also be understood that this disclosure is not limited to the above-mentioned specific embodiments. However, many rearrangements, modifications, and replacements are possible without departing from the scope of this disclosure.

Claims

1. A method for constructing a downlink control information format performed by a user equipment (UE), the method comprising: receiving, from a base station BS, first downlink control information DCI including a first downlink assignment index DAI field, second DCI including a second DAI field, and a radio resource control RRC message, wherein the RRC message includes information for configuring a hybrid automatic repeat request acknowledgement HARQ-ACK codebook list, wherein the first DCI and the second DCI have the same format, the HARQ-ACK codebook list includes a first HARQ-ACK codebook corresponding to a first priority and a second HARQ-ACK codebook corresponding to a second priority, the first priority and the second priority are different, the first DAI field is used for the first HARQ-ACK codebook, and the second DAI field is used for the second HARQ-ACK codebook; determining whether there is a size difference between the first DAI field and the second DAI field; as well as When it is determined that there is the size difference between the first DAI field and the second DAI field, at least one bit having a zero value is inserted into one of the first DAI field and the second DAI field.

2. The method according to claim 1, wherein The inserted at least one bit having a zero value forms the most significant bit in the first DAI field or the second DAI field.

3. The method according to claim 1, wherein The first HARQ-ACK codebook and the second HARQ-ACK codebook have different types, where the types refer to a semi-static type and a dynamic type.

4. A user equipment (UE) for constructing a downlink control information format in a wireless communication system, the wireless communication system including a base station (BS), the UE comprising: Memory; as well as at least one processor coupled to the memory, the at least one processor configured to: receiving, from the base station BS, first downlink control information DCI including a first downlink assignment index DAI field, second DCI including a second DAI field, and a radio resource control RRC message, wherein the RRC message includes information for configuring a hybrid automatic repeat request acknowledgement HARQ-ACK codebook list, wherein the first DCI and the second DCI have the same format, the HARQ-ACK codebook list includes a first HARQ-ACK codebook corresponding to a first priority and a second HARQ-ACK codebook corresponding to a second priority, the first priority and the second priority are different, the first DAI field is used for the first HARQ-ACK codebook, and the second DAI field is used for the second HARQ-ACK codebook; determining whether there is a size difference between the first DAI field and the second DAI field; as well as When it is determined that there is the size difference between the first DAI field and the second DAI field, at least one bit having a zero value is inserted into one of the first DAI field and the second DAI field.

5. The UE according to claim 4, wherein: The inserted at least one bit having a zero value forms the most significant bit in the first DAI field or the second DAI field.

6. The UE according to claim 4, wherein: The first HARQ-ACK codebook and the second HARQ-ACK codebook have different types, where the types refer to a semi-static type and a dynamic type.

Images