CN116707733A

CN116707733A - HARQ-ACK in carrier aggregation with multiple serving cells

Info

Publication number: CN116707733A
Application number: CN202310226245.5A
Authority: CN
Inventors: 哈米德·萨贝尔; 裵正铉
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2022-03-03
Filing date: 2023-03-03
Publication date: 2023-09-05

Abstract

A system and method for HARQ-ACK in carrier aggregation with multiple serving cells is disclosed. In some embodiments, the method comprises: receiving, by a User Equipment (UE), downlink Control Information (DCI) that schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC; calculating, by the UE, a comparison value of the DCI; and transmitting one or more acknowledgement/negative acknowledgement (a/N) bits based on the comparison value, wherein the calculating step comprises: counting is performed on received PDSCH of CCs having up to and including the carrier index of the reference CC.

Description

HARQ-ACK in carrier aggregation with multiple serving cells

Cross Reference to Related Applications

The disclosure of which claims priority from U.S. provisional application No. 63/316,407, filed 3 at 2022, U.S. provisional application No. 63/388,603, filed 7 at 2022, U.S. provisional application No. 63/392,815, filed 7 at 2022, U.S. provisional application No. 63/415,263, filed 10 at 2022, U.S. provisional application No. 63/419,283, filed 24 at 2023, U.S. provisional application No. 63/440,856, filed 24 at 2023, and filed 18/174,574, is incorporated herein by reference as if fully set forth herein.

Technical Field

The present disclosure relates generally to wireless communications. More particularly, the subject matter disclosed herein relates to improvements to mobile communication systems.

Background

In a cellular system operating according to a fifth generation mobile phone (5G) standard promulgated by the 3 rd generation partnership project (3 GPP), a User Equipment (UE) may receive Downlink (DL) control information (DCI) by monitoring a physical Downlink (DL) control channel (PDCCH) to obtain scheduling information of a Physical DL Shared Channel (PDSCH) and a physical Uplink (UL) shared channel (PUSCH).

Communication with multiple carriers is supported in the form of Carrier Aggregation (CA). In CA, a UE can use multiple Component Carriers (CCs) for DL and UL, allowing the UE to utilize a larger bandwidth than is possible using a single CC. There may be multiple modes of CA including (i) in-band frequency aggregation with contiguous CCs, (ii) in-band frequency aggregation with non-contiguous CCs, and (iii) inter-band frequency aggregation with non-contiguous CCs.

The above classification of CA modes depends on the set of frequency bands containing the CC used; this set of frequency bands is called a band combination. The UE is initially connected to one cell in the CA, which is called the primary cell (PCell). The UE then finds and connects to a number of other cells in the CA, called secondary cells (scells).

The aforementioned CA may be extended to Dual Connectivity (DC), which may provide higher throughput per user by offloading data from a primary node to a secondary node in the event of an overload of the primary node. Offloading data from a macrocell to a small cell is an example use case. In a typical scenario, the UE connects first to the primary node and then to the secondary node. EN-DC, NE-DC, and NN-DC refer to DC scenarios in which the primary node and the secondary node are evolved node B (eNB), next generation node B (gNB), (gNB, eNB), and (gNB ), respectively. A deployment scenario where nodes have different radio access technologies is called MR-DC. NE-DC and EN-DC are two examples of MR-DC.

In some embodiments, multiple scheduled cells are scheduled with one DCI on a scheduling cell. To reduce control signaling overhead for scheduling downlink or uplink data channels, one DCI may schedule multiple different Transport Blocks (TBs) in multiple cells in a CA deployment.

One problem with the above approach is that when a single DCI schedules multiple PDSCH using cross-carrier scheduling, signaling of specific parameters that each PDSCH typically transmits may not be clearly defined.

Disclosure of Invention

To overcome these problems, systems and methods for defining well-defined signaling methods for these parameters are described herein. The above approach improves upon previous approaches because ambiguity that might otherwise exist is eliminated.

According to an embodiment of the present disclosure, there is provided a method comprising: receiving, by a User Equipment (UE), downlink Control Information (DCI) that schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC; calculating, by the UE, a comparison value of the DCI; and transmitting one or more acknowledgement/negative acknowledgement (a/N) bits based on the comparison value, wherein the calculating step comprises: counting is performed on received PDSCH of CCs having up to and including the carrier index of the reference CC.

In some embodiments, the method further comprises comparing the comparison value to a C-DAI value of the DCI.

In some embodiments, the method further comprises retrieving exactly one C-DAI value from the DCI.

In some embodiments, the reference CC is a CC with a larger carrier index of the first CC and the second CC.

In some embodiments, the reference CC is a CC with a smaller carrier index of the first CC and the second CC.

In some embodiments, the step of performing the count comprises: PDSCH is counted.

In some embodiments, the step of performing the count comprises: the PDCCHs are counted.

In some embodiments, the method further comprises: reserved by UEA number of acknowledgement/negative acknowledgement (a/N) bits, where M is the maximum number of PDSCH that the DCI can schedule across multiple serving cells; determining DCI scheduling K is less than or equal to M PDSCH; and an a/N bit including K PDSCH in a set order based on the index of the serving cell.

In some embodiments, the step of reserving the a/N bits comprises: only M a/N bits are reserved.

In some embodiments, the set order is an ascending order of indexes.

In some embodiments, the set order is a descending order of indexes.

In some embodiments, M is configured to the UE by a network node (gNB) Radio Resource Control (RRC).

According to an embodiment of the present disclosure, there is provided a User Equipment (UE) including: one or more processors; and a memory storing instructions that, when executed by the one or more processors, cause the following to be performed: receiving Downlink Control Information (DCI), wherein the DCI schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC; and calculating a comparison value of the DCI, wherein the calculating step includes: counting is performed on received PDSCH of CCs having up to and including the carrier index of the reference CC.

In some embodiments, the instructions, when executed by the one or more processors, further cause the following to be performed: comparing the comparison value with the C-DAI value of the DCI.

In some embodiments, the instructions, when executed by the one or more processors, further cause the following to be performed: exactly one C-DAI value is retrieved from the DCI.

According to an embodiment of the present disclosure, there is provided a User Equipment (UE) including: means for processing; and a memory storing instructions that, when executed by the means for processing, cause the following to be performed: receiving Downlink Control Information (DCI), wherein the DCI schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC; and calculating a comparison value of the DCI, wherein the calculating step includes: counting is performed on received PDSCH of CCs having up to and including the carrier index of the reference CC.

Drawings

In the following sections, aspects of the subject matter disclosed herein will be described with reference to exemplary embodiments shown in the drawings, in which:

FIG. 1 is a system diagram of a deployment according to some embodiments;

FIG. 2 is a schedule diagram according to some embodiments;

FIG. 3 is a schedule diagram according to some embodiments;

FIG. 4A is a schedule diagram according to some embodiments;

FIG. 4B is a schedule diagram according to some embodiments;

FIG. 5A is a schedule diagram according to some embodiments;

FIG. 5B is a schedule diagram according to some embodiments;

FIG. 6A is a dispatch diagram in accordance with some embodiments;

FIG. 6B is a resource element diagram according to some embodiments;

FIG. 6C is a resource element diagram according to some embodiments;

fig. 7A is a diagram of a portion of a wireless system, in accordance with some embodiments;

FIG. 7B is a flow chart of a method according to some embodiments; and

fig. 8 is a block diagram of an electronic device in a network environment according to an embodiment.

DETAILED DESCRIPTION OF EMBODIMENT (S) OF INVENTION

In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it will be understood by those skilled in the art that the disclosed aspects may be practiced without these specific details. In other instances, well-known methods, procedures, components, and circuits have not been described in detail so as not to obscure the subject matter disclosed herein.

Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment disclosed herein. Thus, the appearances of the phrase "in one embodiment" or "in an embodiment" or "according to one embodiment" (or other phrases having similar meanings) in various places throughout this specification are not necessarily all referring to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In this regard, as used herein, the word "exemplary" means "serving as an example, instance, or illustration. Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. Furthermore, depending on the context discussed herein, singular terms may include the corresponding plural forms and plural terms may include the corresponding singular forms. Similarly, hyphenated terms (e.g., "two-dimensional," "pre-determined," "pixel-specific," etc.) may occasionally be used interchangeably with, and are used interchangeably with, corresponding non-hyphenated versions (e.g., "two-dimensional," "pre-determined," "pixel-specific," etc.). Such occasional interchangeable uses should not be considered inconsistent with each other.

Furthermore, depending on the context discussed herein, singular terms may include the corresponding plural forms and plural terms may include the corresponding singular forms. It should also be noted that the various figures (including component figures) shown and discussed herein are for illustrative purposes only and are not drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals have been repeated among the figures to indicate corresponding and/or analogous elements.

The terminology used herein is for the purpose of describing some example embodiments only and is not intended to limit the claimed subject matter. As used herein, the singular is intended to include the plural unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It will be understood that when an element or layer is referred to as being "on," "connected to" or "coupled to" another element or layer, it can be directly on, connected or coupled to the other element or layer, or intervening elements or layers may be present. In contrast, when an element is referred to as being "directly on," "directly connected to" or "directly coupled to" another element or layer, there are no intervening elements or layers present. Like numbers refer to like elements throughout. As used herein, the term "and/or" includes any and all combinations of one or more of the associated listed items.

As used herein, the terms "first," "second," and the like are used as labels for nouns following them, and do not imply any type of ordering (e.g., spatial, temporal, logical, etc.), unless so defined explicitly. Furthermore, the same reference numbers may be used across two or more drawings to refer to parts, components, blocks, circuits, units, or modules having the same or similar functionality. However, such usage is merely for simplicity of illustration and ease of discussion; it is not intended that the constructional or architectural details of these components or units be the same in all embodiments, or that these commonly referenced parts/modules be the only way to implement some example embodiments disclosed herein.

Unless defined otherwise, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this subject matter belongs. It will be further understood that terms, such as those defined in commonly used dictionaries, should be interpreted as having a meaning that is consistent with their meaning in the context of the relevant art and will not be interpreted in an idealized or overly formal sense unless expressly so defined herein.

As used herein, the term "module" refers to any combination of software, firmware, and/or hardware configured to provide the functionality described herein in connection with the module. For example, software may be embodied as a software package, code, and/or instruction set or instructions, and the term "hardware" as used in any of the embodiments described herein may include, for example, components, hardwired circuitry, programmable circuitry, state machine circuitry, and/or firmware that stores instructions executed by the programmable circuitry, either alone or in any combination. Modules may be implemented collectively or individually as circuitry forming part of a larger system, such as, but not limited to, an Integrated Circuit (IC), a system-on-a-chip (SoC), a component, and so forth.

As used herein, "a portion" of an item refers to "at least some" of the item, and thus may refer to less than all of the item or all of the item. Thus, a "portion" of an object includes the whole object as a special case, i.e., the whole object is an example of a portion of an object. As used herein, when the second number is "within" the first number X, it means that the second number is at least X-Y and the second number is at most x+y. As used herein, when a second digit is within "Y% of a first digit, it means that the second digit is at least (1-Y/100) times the first digit and the second digit is at most (1+Y/100) times the first digit. As used herein, the term "or" should be interpreted as "and/or" such that, for example, "a or B" means "a" or "B" or any one of "a and B".

Each of the terms "processing circuitry" and "means for processing" is used herein to represent any combination of hardware, firmware, and software for processing data or digital signals. The processing circuit hardware may include, for example, an Application Specific Integrated Circuit (ASIC), a general purpose or special purpose Central Processing Unit (CPU), a Digital Signal Processor (DSP), a Graphics Processing Unit (GPU), a programmable logic device such as a Field Programmable Gate Array (FPGA). In processing circuitry, as used herein, each function is performed by hardware configured to (i.e., hardwired) perform the function, or by more general-purpose hardware (such as a CPU) configured to execute instructions stored in a non-transitory storage medium. The processing circuitry may be fabricated on a single Printed Circuit Board (PCB) or distributed over several interconnected PCBs. The processing circuitry may include other processing circuitry; for example, the processing circuitry may include two processing circuits interconnected on a PCB, an FPGA and a CPU.

As used herein, when a method (e.g., adjustment) or a first quantity (e.g., a first variable) is referred to as being "based on" a second quantity (e.g., a second variable), it is meant that the second quantity is an input to the method or affects the first quantity, e.g., the second quantity may be an input (e.g., a sole input, or one of several inputs) that is a function of calculating the first quantity, or the first quantity may be equal to the second quantity, or the first quantity may be the same as the second quantity (e.g., stored at the same location in memory as the second quantity).

FIG. 1 shows an NN-DC deployment scenario, comprising a primary node (MgNB) 105, two secondary nodes (SgNB-1 and SgNB-2) 110a and 110b, and three UEs (UE-1, UE-2 and UE-3) 115a, 115b, 115c. In the example of fig. 1, UE-3 is in DC mode and is connected to two New Radio (NR) nodes, namely the gNB, simultaneously. The primary node (MgNB) 105 configures a set of serving cells within a Master Cell Group (MCG), and each of the secondary nodes (SgNB) 110a, 110b configures a set of serving cells within a Secondary Cell Group (SCG). The primary cell of the MCG is called PCell, and the secondary cell of the MCG is called SCell. The primary cell of the SCG is called PSCell. PCell and PSCell are also known as special cells (spcells).

Some embodiments relate to a CA deployment scenario, and the concepts disclosed herein may be extended to each cell group in a DC scenario. In CA, a PDCCH is typically transmitted in each cell to schedule PDSCH or PUSCH on that cell. However, in the case of cross-carrier scheduling (CCS) where cells called scheduling cells transmit DCI for different cells called scheduled cells, this may not be the case. May be performed when there are identical or different parameter sets (μ for scheduling cells ₁ Mu for the scheduled cell ₂ ) CCS is performed between the scheduling cell and the scheduled cell.With different parameter sets (i.e. with μ ₁ ≠μ ₂ ) Has a strong use case of frequency range FR1 scheduling FR 2. This is because FR1 (e.g., at frequencies below 6 GHz) may have better coverage, and thus transmitting DL control information over FR1 may be more reliable. Cross-carrier scheduling may be an efficient way to transmit DL control information for FR2 on FR 1. Thus CCS with different parameter sets between the scheduling cell and the scheduled cell may have practical value. Fig. 2 shows an example of CCS with different parameter sets in which a scheduling cell with a subcarrier spacing (SCS) of 15kHz schedules a scheduled cell with scs=30 kHz. The PDCCH is transmitted on the first three symbols of slot n of the scheduling cell, and the PDSCH is scheduled on slot m+1 of the scheduled cell.

Monitoring of DCI is done on a Search Space (SS) of a scheduling cell to decode PDCCH. In ts38.213v17.2.0 of the 3GPP specification in clause 10.1, SS and related UE behavior are described.

The Search Spaces (SSs) are classified into common SSs (CSS) and UE-specific SSs (USS). In the current system, the CSS except for the type 3 Group Common (GC) PDCCH SS is monitored only on the primary cell, whereas the USS and the type 3CSS may be monitored in all cells. In the case of CC, the SS is not monitored in the scheduled cell. In some embodiments, the primary cell is a scheduled cell and Dynamic Spectrum Sharing (DSS) may be employed.

From the UE's point of view, processing DCI to receive PDSCH or transmit PUSCH is subject to processing time. In TS38.214V17.0.0 of the 3GPP standard, two different UE processing capabilities (capability 1 (cap#1 or Cap 1) and capability 2 (cap#2 or Cap 2)) are defined as specified in clauses 5.3 and 6.4. This capability is in terms of the number of Orthogonal Frequency Division Multiplexing (OFDM) symbols (N1 or N2) required for the UE to process PDSCH or PUSCH, and those capabilities depend on several parameters including subcarrier spacing (SCS) or parameter set μ. It can be seen that N1 or N2 is smaller for cap #2 (shortened processing time) than for cap # 1.

In some embodiments, multiple scheduled cells are scheduled with one DCI on a scheduling cell, as shown in fig. 3. To reduce control signaling overhead for scheduling downlink or uplink data channels, one DCI may schedule multiple different Transport Blocks (TBs) in multiple cells in a CA deployment.

In one embodiment, when one DCI schedules multiple cells, parameters in the DCI related to such allocation may be replicated to have multiple copies. Such allocation parameters may be, but are not necessarily limited to, time Domain Resource Allocation (TDRA), frequency Domain Resource Allocation (FDRA), redundancy Version (RV), modulation and Coding Scheme (MCS), PDCCH to PDSCH timing (K0), PDSCH to physical UL control signal (PUCCH) timing (K1), PDCCH to PUSCH timing (K2), or Data Allocation Index (DAI). Such duplication may increase DCI size and reduce efficiency, which is important for DCI. In another embodiment, a Radio Resource Control (RRC) provides a list of allocation parameter sets in all cells, and the DCI may indicate an index in the list. Such allocation parameters may be, but are not necessarily limited to, time Domain Resource Allocation (TDRA), frequency Domain Resource Allocation (FDRA), redundancy Version (RV), modulation and Coding Scheme (MCS), PDCCH to PDSCH timing (K0), PDSCH to physical UL control signal (PUCCH) timing (K1), or PDCCH to PUSCH timing (K2). In another embodiment, a particular parameter is shared by two cells.

The PDSCH-to-physical UL control signal (PUCCH) timing K1 and the use of PUCCH resource indicators may be affected by whether multiple cells belong to the same PUCCH group. In this case, it may not be advantageous to employ a separate PUCCH. In one embodiment, a single parameter for K1 and a single parameter for a PUCCH Resource Indicator (PRI) are provided, and an actual PUCCH is determined based on the latest PUCCH among PUCCHs constructed on the assumption corresponding to the PDSCH parameter set and the allocation parameter of each cell. In another embodiment, a single parameter for K1 and a single parameter for a PUCCH resource indicator are provided, and an actual PUCCH is determined based on an earliest PUCCH satisfying PDSCH processing times of all cells among PUCCHs constructed on the assumption corresponding to a PDSCH parameter set and allocation parameters of each cell. In another embodiment, a specific PDSCH cell is used as a reference cell for determining the actual PUCCH.

If one PUCCH is used, one or more DAI fields may be included in the DCI. If a DAI field is provided, the procedure of constructing a type 2 hybrid automatic repeat request (HARQ) acknowledgement or negative acknowledgement (ACK/NACK or A/N) (HARQA/N) codebook provided in clause 9.1.3.1 of TS38.213v17.2.0 of the 3GPP specification may be modified. For example, the a/N bit positions in the codebook may be generated as "N" consecutive positions, where the starting position corresponds to the position of the lowest scheduled cell index, where "N" is the number of scheduled cells in the DCI. In this case, the DAI-related operations in the codebook may be skipped for all other scheduled cell indexes, and the DAI delta may be one for the DCI. Detailed UE behavior for a type 2HARQ-ACK codebook is described in clause 9.1.3.1 of the 3GPP specification ts38.213v 17.2.0.

In another embodiment, multiple separate PUCCHs are used. A single parameter for K1 and a single parameter for the PUCCH resource indicator may be utilized, and a plurality of PUCCHs may be constructed based on the single parameter. Because the DAI is for one reference PUCCH slot, multiple DAI fields may be used.

Hereinafter, it is assumed that PDCCHs on a scheduling cell schedule N PDSCH on N serving cells. The present disclosure includes a portion for using a type 2 (dynamic) hybrid automatic repeat request (HARQ) acknowledgement (HARQ-ACK) codebook and a portion for using a type 2HARQ-ACK Codebook (CB) with a sub-codebook.

Type 2 (dynamic) HARQ-ACK codebook

Hereinafter, since the DAI field is for one Physical Uplink Control Channel (PUCCH) slot, one PUCCH slot is assumed. In Rel-15/16, C-DAI is defined as follows:

the value of the counter Downlink Assignment Indicator (DAI) field in the DCI format indicates, first in ascending order of the serving cell index and then in ascending order of the PDCCH monitoring occasion index M, until the cumulative number of { serving cell, PDCCH monitoring occasion } pairs of the current serving cell and current PDCCH monitoring occasion in which there is PDSCH reception or SPS PDSCH release associated with the DCI format, where 0+.m < M.

Where a "serving cell" is a scheduled cell. Fig. 4A shows DAI operation in Rel-15, where (C-DAI, T-DAI) pairs are shown inside each PDCCH. Cc#1 is a cross-carrier scheduled by cc#3.

Two methods, referred to herein as method 1 and method 2, are disclosed in the context of a type 2 (dynamic) HARQ-ACK codebook.

In method 1 (N DAI fields), the DAI definition and type 2CB are the same as in Rel-15. The UE may consider the detected DCI as N detected DCIs, each having a corresponding DAI field.

If only one DAI field exists in the scheduling DCI, the DAI field may be redefined. For example, fig. 4B is a modified version of fig. 4A, where there is a single DCI replacing two DCIs of schedules cc#1 and cc#3 in fig. 4B. The problem is what value should be used to replace the C-DAI in the PDCCH on CC # 3. If the C-DAI were to provide the cumulative number of { serving cell, PDCCH monitoring occasion } pairs up to CC #1, then the value should be 2. If the C-DAI is to provide an accumulated number up to CC #3, the value should be 4. Both options may be verified to work properly in terms of hybrid automatic repeat request (HARQ) and acknowledgement (HARQ-ACK) payload size determination.

In method 2 (1 DAI field), for PDCCH scheduling different cells, there is a single field for (C-DAI, T-DAI) in DCI. The schedule has index i ₁ 、i ₂ 、…、i _N The value of C-DAI on PDCCH of serving cell of (1) is expressed by first ascending order of serving cell index and then ascending order of PDCCH monitoring opportunity index m until the cumulative number of { serving cell, PDCCH monitoring opportunity } pairs of current serving cell and current PDCCH monitoring opportunity in which there is PDSCH reception or SPS PDSCH release associated with DCI format, where 0.ltoreq.m<M, wherein the current serving cell is one having i ₁ 、…、i _N Serving cell of the largest index or smallest index of the plurality of cells. That is, C-DAI is associated with cell index C' =max (i ₁ ,…,i _N ) Or c' =min (i _N ,…,i _N ) And (5) associating. The value of T-DAI has the same meaning as in Rel-15/16. Type 2CB operation is unchanged except (i) inIn the loop, set i is skipped ₁ 、…、i _N (ii) not including all Negative Acknowledgement (NACK) values for skipped indexes, and (iii) for valid ACK/NACK (a/N) bits of skipped indexes, the position in the codebook may be the original position of the NACK value or a new position of the a/N value consecutively following the maximum index or the minimum index.

For example, in fig. 4B, if c' =max (1, 3) =3 is considered, a=4, and the cell index c=1 in the while cycle is skipped. By skipping only the cell index c=1, a NACK value will be generated for the PDSCH on CC # 1. By modification, the NACK bits are replaced by valid A/N bits of PDSCH on CC#1. If c' =min (1, 3) =1, a=2, and the cell index c=3 is skipped. By skipping only the cell index c=1, a NACK value will be generated for the PDSCH on CC # 3. By modification, the NACK bits are replaced by valid A/N bits of PDSCH on CC#3.

It is also necessary to determine the ordering of the a/N bits in the type 2 CB. In one approach, the ordering is based on a start time of the scheduled PDSCH. That is, the a/N bits are included in ascending order of the starting time of the PDSCH. If the starting times of the two PDSCHs are the same, the PDSCH with the smallest or largest cell index may be placed before the other PDSCH. Alternatively, the a/N bits may simply be ordered in ascending or descending order of the corresponding cell index.

Rel-15 specifies the following behavior for type 2HARQ-ACK CB. In Rel-15, for a given PDSCH reception, a 1 or is generated by the User Equipment (UE) for a detected Dynamic Grant (DG) PDSCH or a missing PDCCH scheduling DG PDSCHBits, wherein->

In the above-mentioned context,representing the maximum number of codewords for serving cell c, for example>Indicated by Radio Resource Control (RRC) Information Element (IE) maxNrofCodeWordsSchedulyDCI, and +.>Indicating the number of HARQ-ACK bits per codeword or Transport Block (TB) for serving cell c, +.>Given by RRC IEmaxCodeBlockGroupsPerTransportBlock. Generating a fixed number for a detected or lost PDCCHThe reason behind the bits is that the UE may not know how many CBGs were scheduled in the missing DCI. The use of a fixed number of bits, albeit at the cost of redundant payload sizes, facilitates the UE and the gNB to have a common understanding of the a/N payload size.

In the above, it is assumed that the C-DAI count is based on the number of PDSCH scheduled. That is, the C-DAI counts the number of PDSCH. Alternatively, the C-DAI may count the number of PDCCHs. The problem with counting PDSCH is that if DCI schedules 4 PDSCH on 4 cells and is lost, the HARQ-ACK payload will be erroneous because DAI bit width is only 2 bits. If the DAI is configured to count the number of PDCCHs, the DAI is increased by 1 regardless of the number of PDSCH scheduled. The definition of C-DAI still requires a reference cell that can be determined according to any suitable method. In this case, the maximum number of PDSCH scheduled may be set together between the UE and the gNB, and if the number of PDSCH scheduled is less than the maximum number, the UE appends zero to the a/N bit of PDSCH actually scheduled. In general, the UE may be RRC configured to operate with PDCCH-based counts or PDSCH-based counts for the DAI field in the DCI. For PDSCH based counting, no special handling is required for type 2HARQ-ACK CB.

For PDCCH-based counting, for any transmitted PDCCH, the UE retainsA number of a/N bits, where M is the maximum number of PDSCH that can be scheduled across multiple cells by DCI; m may be RRC configured to the UE. If the DCI is lost, then all bits are NACK. If the DCI schedules K.ltoreq.M PDSCHs, the UE includes A/N bits of the PDSCHs in ascending/descending order of the serving cell index. The ordering of the a/N bits may also be based on the start time of the scheduled PDSCH. That is, the a/N bits are included in ascending order of the starting time of the PDSCH. If the starting times of the two PDSCHs are the same, the PDSCH with the smallest or largest cell index may be placed before the other PDSCH. For PDSCH scheduled on the serving cell, the UE includes additional zero bits according to Rel-15 behavior in addition to those bits for CBG of the PDSCH being scheduled. Placing +. >After a few bits, the UE includesAnd NACK bits (zero bits).

Type 2HARQ-ACK CB with sub-codebook

In release 15 (Rel-15) of the 5G New Radio (NR) standard, a dynamic (type 2) hybrid automatic repeat request (HARQ) Codebook (CB) is constructed based on a counter downlink allocation index (C-DAI) and a total downlink allocation index (T-DAI) indicated to the UE in the scheduling DCI or SPS release DCI.

In Rel-15, for a given PDSCH reception, a 1 or is generated by the User Equipment (UE) for a detected Dynamic Grant (DG) PDSCH or a missing PDCCH scheduling DG PDSCHA number of bits, wherein,

in the above-mentioned context,representing the maximum number of codewords for serving cell c, for example>Indicated by Radio Resource Control (RRC) Information Element (IE) maxNrofCodeWordsSchedulyDCI, and +.>Indicating the number of HARQ-ACK bits per codeword or Transport Block (TB) for serving cell c, +.>Given by RRC IE maxCodeBlockGroupsPerTransportBlock.

Generating a fixed number for a detected or lost PDCCHThe reason behind the bits is that the UE may not know how many CBGs were scheduled in the missing DCI. For example, referring to fig. 5a, the ue may be configured with four serving cells, the maximum number of codewords may be equal to one for each cell, and the maximum number of CBGs that can be received is 2, 3, 4, and 5 for CC #1 through CC # 4. If the UE loses DCI on CC #3 and detects the other two DCIs, the UE will realize that the UE has lost one DCI from the indicated DAI value. However, the UE cannot determine on which cell the missing DCI is transmitted. If the missing DCI is transmitted on CC #2, the UE should include 3 NACK bits, and if the missing DCI is transmitted on CC #3, the UE should include 4 NACK bits. To avoid any mismatch between the UE and the gNB with respect to the number of NACK bits included, the UE may simply include the maximum number of possible CBGs across all cells for each detected PDCCH or lost PDCCH . Considering the number of codewords per cell, the UE generates +/for each scheduling DCI>a/N bits. If the actual number of scheduled CBGs is less than the maximum number, the UE appends zero.

Although it includes for each PDSCHThe number of bits may solve the payload size mismatch problem, but it may become inefficient due to the additional zeros of the UE. The inefficiency becomes more severe when the maximum number of CBGs configured on different cells varies significantly. As an example, if two cells are configured with only one CBG (or TB-based transmission) and the other two cells are configured with eight CBGs, seven zero bits will be appended to each a/N bit of the first two cells, thereby possibly unnecessarily increasing the payload size and negatively affecting PUCCH reliability. To alleviate the zero-appending problem, rel-15 uses two subcodebooks as shown below. The first sub-codebook comprises all 1-bit HARQ-ACK bits and the second sub-codebook comprises all +.>HARQ-ACK bits of a single bit.

Providing to a UE forPDSCH-codeblockgrouppransision of the serving cell; and does not provide the UE with a solution for +.>PDSCH-codeblockgrouppransision of a serving cell, wherein,

Fig. 5B shows an example of a type 2HARQ codebook in Rel-15. There are four Monitor Opportunities (MOs) participating in sub-codebook 1 and seven MOs participating in sub-codebook 2. The UE will generate four HARQ-ACK bits for four MOs as (a) corresponding to (m=mo index, c=serving cell index (0, 2), (1, 1), (2, 0) and (2, 3), respectively ₁ ,a ₂ ,a ₃ ,a ₄ ). For the remaining MO, 8 bits are generated, resulting in an A/N bit (b ₁ ,b ₂ ,b ₃ ,b ₄ ,b ₅ ) Wherein each b _i Is 8 bits. All 4 cells participate in the first sub-codebook, while only cc#0, cc#2 and cc#3 participate in the second sub-codebook.

As mentioned above, if the maximum number of CBGs per serving cell configuration varies significantly from serving cell to serving cell, having a fixed HARQ-ACK bit width per serving cell would create an unnecessarily large overhead for the payload size, as the UE would need to append zero bits. If all but one serving cell is configured with the maximumA CBG and the one serving cell is configured with +>The UE will generate 8 bits for all MO and serving cells which is significantly redundant since there is only one CBG for all but the one serving cell. To solve this problem, two sub-codebooks are used in Rel-15, wherein 1 bit or +. >And a number of bits. The subcode is determined by the UE according to the following table:

in some embodiments, as shown in fig. 6A, when two cells fall into two different subcodebooks according to Rel-15/16/17 behavior, two PDSCH are allowed to be scheduled in cell #1 and cell # 2; in other embodiments, such scheduling is not allowed. Allowing such scheduling may defeat the purpose of using a separate codebook to provide robustness against missing DCI, at least when the DAI counts the number of PDSCH.

Two methods, referred to herein as method 1 and method 2, are disclosed in the context of a type 2HARQ-ACK CB with subcodebooks.

In method 1 (for the case where the use of different sub-codebooks is an error case), when the UE is configured with multiple sub-codebooks with type 2HARQ-ACK CBs, if DCI on a scheduling cell schedules two PDSCH on two different scheduled cells, the UE does not expect the two cells to belong to two different HARQ-ACK sub-codebooks according to Rel-15 behavior.

Alternatively, a reference serving cell of the scheduled serving cells may be selected to select the sub-codebook.

In method 2 (for the case where the use of different sub-codebooks is not an error case), when the UE is configured with a plurality of sub-codebooks with type 2HARQ-ACK CBs, if DCI on a scheduling cell schedules two PDSCH on two different scheduled cells cc#1 and cc#2 and the two cells belong to the two different sub-codebooks according to the Rel-15 rule, the UE includes HARQ-ACK bits of the PDSCH in a sub-codebook of a reference cell (e.g., a cell with a minimum (or maximum) cell index) among the two cells based on the associated scheduled cell determined from the CIF configuration. The value of (C-DAI, T-DAI) is incremented according to the determined sub-codebook.

In fig. 6A, if cc#1 is selected as a reference cell, DCI and two PDSCH are included in sub-codebook # 1. DAI value is (a, b) = (3, 3). In fig. 6A, if cc#2 is selected as a reference cell, DCI and two PDSCH are included in sub-codebook#2. DAI value is (a, b) = (2, 2).

For each scheduling cell, the UE may be configured with the maximum number of cells that may be scheduled by the MC DCI. The maximum number of cells may also be configured to be the same for all scheduling cells.This maximum number may be referred to as N _max . When the MC-DCI schedules N cells, the C-DAI is incremented by 1, but the UE retains N _max a/N bits. The first N bits correspond to the scheduled cell, and the last N _max The N bits are 0 (NACK) bits. The ordering of the a/N bits may be based on the cell index (in ascending or descending order) or the starting time or ending time of the PDSCH. For the latter, if two PDSCH have the same starting time, the ordering may be defined based on the cell index. For example, if two PDSCH have the same starting time, PDSCH with the smallest cell index may be ordered before PDSCH with the largest cell index.

HARQ-ACK multiplexing in PUSCH may be handled as follows. In the conventional NR, if PUCCH and PUSCH overlap, UCI transmitted in PUCCH by the UE is multiplexed in PUSCH. The number of REs for HARQ-ACK and CSI may be determined based on the number of REs of PUSCH and some control parameters called β -offset and α -offset configured to the UE via RRC and indicated via DCI, and HARQ-ACK and CSI payload sizes as follows.

The coded bits for HARQ-ACK, CSIpart1, and CSIpart2 may then be placed on REs of PUSCH. Since fewer REs are available for PUSCH data transmission after UCI multiplexing, only a subset of data symbols may be selected to be carried on the available REs of PUSCH.

There are two different methods for multiplexing UCI data on PUSCH: puncturing and rate matching. The UCI multiplexing process is briefly described as follows.

Uplink shared channel (UL-SCH) code bits:

HARQ-ACK code bits:

CSI-part1 code bits:

CSI-part2 code bits:

no UCI is mapped to any DMRS bearer symbol.

The ACK bits are mapped only to REs that occur after consecutive DMRS symbol sets.

And (3) reserving a plurality of REs for the ACK for the number of ACK information bits in the step 1 is less than or equal to 2.

For the number of ACK information bits >2 in step 2, multiple REs are mapped for ACK.

If the number of A/N bits is less than or equal to 2, puncturing is used. Fig. 6B shows an example of UCI multiplexing on PUSCH using puncturing. If the number of A/N bits is greater than 2, rate matching is used. Fig. 6C shows an example of UCI multiplexing on PUSCH using rate matching.

PUSCH decoding reliability may be affected. Using puncturing, PUSCH data symbols are punctured over reserved REs. The method has the following advantages: if the HARQ-ACK payload size is wrong, the PUSCH decoding can still be successful. This applies to fixed reserved or variable numbers of REs. On the other hand, rate matching with a variable number of REs is prone to HARQ-ACK payload size errors. As an example, in fig. 6C, if the HARQ-ACK payload size is wrong, the data symbols will be shifted over the REs and the gNB and UE will have different understandings of the data allocation over the REs. As a result, PUSCH decoding may fail. For a small number of DCIs participating in the codebook, the HARQ-ACK payload error probability is typically small. For example, if the payload has only one DCI and if the UE misses it, the payload size will be erroneous because the UE has no mechanism to determine the correct number of a/N bits. Therefore, it may be advantageous to ensure PUSCH decoding reliability for payloads generated by a small amount of DCI. To ensure PUSCH decoding reliability, two methods are possible, (i) rate matching with a fixed reserved number of REs determined based on the maximum number of a/N bits, or (ii) puncturing with or without a fixed number of REs determined based on the maximum number of a/N bits.

Traditional NR employs a combination of these two approaches. That is, if the number of A/N bits is less than or equal to the maximum number T _threhsold =2, then the UE reserves multiple REs assuming a payload size of 2. Puncturing is also applied to UCI multiplexing. Selecting the value T in a conventional NR _threhsold =2 to handle the case of missing one DCI scheduling 1 or 2 Transport Blocks (TBs). Although this value may properly address the missing DCI problem in a legacy NR where DCI can only schedule one TB (PDSCH), it may not be valid when the MC DCI scheduling framework is applied. This can be seen in the case of CMDCI scheduling 4 cells. Since the number of a/N bits is greater than 2, the conventional NR specifications apply rate matching. However, in this case, since the a/N payload size error probability may be high because there is only 1 DCI in the payload that may be easily lost by the UE, rate matching may not ensure PUSCH decoding reliability. Thus, the threshold with MC DCI may be determined by the actual number of DCIs, rather than the number of a/N bits. The following method may be employed. In case of MC scheduling DCI and type 2HARQ-ACK CB, if the UE multiplexes a/N bits in PUSCH, the determination for beating is made by any of the following methods Threshold T for hole and rate matching _threhsold 。

T _threhsold =2×the maximum number of cells that can be scheduled by the MC DCI.

T _threhsold Is an RRC configured to the UE.

If the UE is configured with multiple scheduling cells for MC scheduling, the threshold determination may consider the maximum of commonly scheduled cells on all scheduling cells. For example, if CC #0 is configured to schedule M via the MC DCI format ₀ Each cell, and CC #1 is configured to schedule M via an MC DCI format ₁ The maximum number of bits that can be caused by the 1MC DCI is max (M ₀ ,M ₁ ) So that if the target is a missing DCI, the threshold can be chosen to be max (M ₀ ,M ₁ ). If the target is up to 2 missing DCIs, the maximum number of A/N bits is max (2M ₀ ,2M ₁ ,M ₀ +M ₁ ))＝2max(M ₀ ,M ₁ ). Thus, in one embodiment, the threshold may be set to T _threshold ＝n×max _c M _c Or T _threshold ＝n×max _c M _c +1, where M _c Is the maximum number of co-scheduled cells that can be scheduled with one MC DCI format on scheduling cell c.

Such adjustment of the value of the threshold is only required if at least one cell is configured for MC DCI format monitoring and the corresponding a/N bits are multiplexed into the HARQ-ACK CB. In other words, if none of the cells in which the a/N bits are multiplexed in the HARQ-ACK CB is configured with the MC DCI format schedule, the legacy threshold may be used.

Once the threshold T _threhsold Is arranged to select between puncturing and rate matching, the number of a/N bits used by the UE to determine the number of a/NREs used for puncturing may be modified to be based on the actual number of bits rather than T _threhsol Is fixed in value. The actual number of use of a/N bits may have advantages and disadvantages compared to using a fixed threshold. The actual number of A/N bits that the UE possesses may be represented as A (e.g., the UE may possess A/N bits), where A<T _threhsold . Regardless of the correct A/N payload sizeThe following observations can be made as to how sexual.

One advantage of scheme 2 over scheme 1 is that in case of incorrect a/N payload size, the gNB can perform blind decoding of PUSCH by assuming different values of the actual payload size assumed by the UE, thereby improving decoding performance of PUSCH. In case of incorrect HARQ-ACK payload size, none of these schemes can recover the a/N information even though the gNB performs blind decoding of HARQ-ACKs.

Fig. 7A illustrates a portion of a wireless system. User Equipment (UE) 705 sends transmissions to network node (gNB) 710 and receives transmissions from gNB 710. The UE includes a radio 715 and processing circuitry (or "processor") 720. In operation, processing circuitry may perform various methods described herein, e.g., processing circuitry may receive information from the gNB 710 (via radio as part of a transmission received from the gNB 710), and processing circuitry may send information to the gNB 710 (via radio as part of a transmission sent to the gNB 710).

Fig. 7B is a flow chart of a method in some embodiments. The UE may determine, upon receiving the DCI, whether it has lost any DCI by calculating the value (referred to herein as the "comparison value") that it would expect the C-DAI of the DCI if no DCI was lost. The UE may also retrieve the C-DAI value from the DCI and compare the retrieved C-DAI value to the comparison value (the difference between the retrieved C-DAI value and the comparison value indicates that the DCI is lost). As such, the method may include receiving, by a User Equipment (UE), downlink Control Information (DCI) that schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC at 730. The method also includes calculating, by the UE, a comparison value of the DCI at 732, and transmitting one or more acknowledgement/negative acknowledgement (a/N) bits based on the comparison value at 733. The calculation may include counting scheduled PDSCH execution of CCs having carrier indexes up to and including the carrier index of the reference CC. The method also includes retrieving exactly one C-DAI value from the DCI at 734 and comparing the comparison value to the C-DAI value of the DCI at 736.

The method may further comprise: at 738, reservation by the UE A number of acknowledgement/negative acknowledgement (a/N) bits, where M is the maximum number of PDSCH that the DCI may schedule across multiple serving cells; at 740, determining that DCI schedules K is less than or equal to M PDSCH; and, at 742, the a/N bits of the K PDSCH are included in a set order based on the index of the serving cell.

Fig. 8 is a block diagram of an electronic device (e.g., UE 705) in a network environment 800 according to an embodiment. Referring to fig. 8, an electronic device 801 in a network environment 800 may communicate with the electronic device 802 via a first network 898 (e.g., a short-range wireless communication network) or with the electronic device 804 or a server 808 via a second network 899 (e.g., a long-range wireless communication network). The electronic device 801 may communicate with the electronic device 804 via a server 808. The electronic device 801 may include a processor 820, a memory 830, an input device 850, a sound output device 855, a display device 860, an audio module 870, a sensor module 876, an interface 877, a haptic module 879, a camera module 880, a power management module 888, a battery 889, a communication module 890, a Subscriber Identity Module (SIM) card 896, or an antenna module 897. In one embodiment, at least one of the components (e.g., display device 860 or camera module 880) may be omitted from electronic device 801, or one or more other components may be added to electronic device 801. Some components may be implemented as a single Integrated Circuit (IC). For example, the sensor module 876 (e.g., a fingerprint sensor, iris sensor, or illuminance sensor) can be embedded in a display device 860 (e.g., a display).

Processor 820 may execute software (e.g., program 840) to control at least one other component (e.g., hardware or software component) of electronic device 801 coupled to processor 820 and may perform various data processing or calculations.

As at least part of the data processing or calculation, processor 820 may load commands or data received from another component (e.g., sensor module 846 or communication module 890) into volatile memory 832, process commands or data stored in volatile memory 832, and store the resulting data in non-volatile memory 834. Processor 820 may include a main processor 821 (e.g., a Central Processing Unit (CPU) or an Application Processor (AP)) and an auxiliary processor 823 (e.g., a Graphics Processing Unit (GPU), an Image Signal Processor (ISP), a sensor hub processor, or a Communication Processor (CP)) that may be operatively independent of or combined with main processor 821. Additionally or alternatively, the auxiliary processor 823 may be adapted to consume less power than the main processor 821 or perform certain functions. The auxiliary processor 823 may be implemented separately from the main processor 821 or as part of the main processor 821. Nonvolatile memory 834 includes internal memory 836 and external memory 838.

The auxiliary processor 823 (instead of the main processor 821) may control at least some of the functions or states associated with at least one of the components of the electronic device 801 (e.g., the display device 860, the sensor module 876, or the communication module 890) while the main processor 821 is in an inactive (e.g., sleep) state, or may control at least some of the functions or states associated with at least one of the components of the electronic device 801 (e.g., the display device 860, the sensor module 876, or the communication module 890) with the main processor 821 while the main processor 821 is in an active state (e.g., executing an application). The auxiliary processor 823 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., a camera module 880 or a communication module 890) functionally associated with the auxiliary processor 823.

The memory 830 may store various data used by at least one component of the electronic device 801 (e.g., the processor 820 or the sensor module 876). The various data may include, for example, software (e.g., program 840) and input data or output data for commands associated therewith. Memory 830 may include volatile memory 832 or nonvolatile memory 834.

Program 840 may be stored as software in memory 830, and program 840 may include, for example, an Operating System (OS) 842, middleware 844, or applications 846.

The input device 850 may receive commands or data from outside the electronic device 801 (e.g., a user) to be used by another component of the electronic device 801 (e.g., the processor 820). Input device 850 may include, for example, a microphone, a mouse, or a keyboard.

The sound output device 855 may output a sound signal to the outside of the electronic device 801. The sound output device 855 may comprise, for example, a speaker or a receiver. Speakers may be used for general purposes, such as playing multimedia or album, and receivers may be used to receive incoming calls. The receiver may be implemented separately from the speaker or as part of the speaker.

The display device 860 may visually provide information to the outside (e.g., a user) of the electronic device 801. The display device 860 may include, for example, a display, a holographic device, or a projector, and control circuitry for controlling a respective one of the display, holographic device, and projector. The display device 860 may include touch circuitry adapted to detect touches, or sensor circuitry (e.g., pressure sensors) adapted to measure the strength of forces caused by touches.

The audio module 870 may convert sound into electrical signals and vice versa. The audio module 870 may obtain sound via the input device 850 or output sound via the sound output device 855 or headphones of the external electronic device 802 that is directly (e.g., wired coupling) or wirelessly coupled with the electronic device 801.

The sensor module 876 may detect an operational state (e.g., power or temperature) of the electronic device 801 or an environmental state (e.g., a state of a user) external to the electronic device 801 and then generate an electrical signal or data value corresponding to the detected state. The sensor module 876 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an Infrared (IR) sensor, a biological sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

The interface 877 may support one or more specified protocols for coupling the electronic device 801 directly (e.g., wired) or wirelessly with an external electronic device 802. The interface 877 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

The connection terminal 878 may include a connector via which the electronic device 801 may be physically connected to the external electronic device 802. The connection terminal 878 may include, for example, an HDMI connector, a USB connector, an SD card connector, or an audio connector (e.g., a headphone connector).

The haptic module 879 may convert the electrical signal into a mechanical stimulus (e.g., vibration or movement) or an electrical stimulus that may be recognized by the user via a sense of touch or kinesthetic sense. The haptic module 879 may include, for example, a motor, a piezoelectric element, or an electro-stimulator.

The camera module 880 may capture still images or moving images. The camera module 880 may include one or more lenses, image sensors, image signal processors, or flash lamps. The power management module 888 may manage power provided to the electronic device 801. The power management module 888 may be implemented, for example, as at least a portion of a Power Management Integrated Circuit (PMIC).

The battery 889 may provide power to at least one component of the electronic device 801. The battery 889 may include, for example, a non-rechargeable primary battery, a rechargeable secondary battery, or a fuel cell.

The communication module 890 may support establishing a direct (e.g., wired) communication channel or a wireless communication channel between the electronic device 801 and an external electronic device (e.g., electronic device 802, electronic device 804, or server 808) and performing communication via the established communication channel. The communication module 890 may include one or more communication processors capable of operating independently of the processor 820 (e.g., an AP) and support direct (e.g., wired) or wireless communication. The communication module 890 may include a wireless communication module 892 (e.g., a cellular communication module, a short-range wireless communication module, or a Global Navigation Satellite System (GNSS) communication module) or a wired communication module 894 (e.g., a Local Area Network (LAN) communication module or a Power Line Communication (PLC) module). Respective ones of these communication modules may be connected via a first network 898 (e.g., short range Communication networks, such as Bluetooth ^TM Wireless fidelity (Wi-Fi) direct or infrared data association (IrDA) standard) or a second network 899 (e.g., a long-range communications network such as a cellular network, the internet, or a computer network (e.g., a LAN or Wide Area Network (WAN)) with an external electronic device. These various types of communication modules may be implemented as a single component (e.g., a single IC), or may be implemented as multiple components (e.g., multiple ICs) separate from one another. The wireless communication module 892 may use user information (e.g., an International Mobile Subscriber Identity (IMSI)) stored in the user identification module 896 to identify and authenticate the electronic device 801 in a communication network, such as the first network 898 or the second network 899.

The antenna module 897 may send signals or power to or receive signals or power from outside of the electronic device 801 (e.g., an external electronic device). The antenna module 897 may include one or more antennas and at least one antenna suitable for a communication scheme used in a communication network, such as the first network 898 or the second network 899, may be selected from the one or more antennas, for example, by the communication module 890 (e.g., the wireless communication module 892). Signals or power may then be transmitted or received between the communication module 890 and the external electronic device via the selected at least one antenna.

Commands or data may be sent or received between the electronic device 801 and the external electronic device 804 via a server 808 coupled to the second network 899. Each of the electronic devices 802 and 804 may be the same type of device as the electronic device 801 or a different type of device from the electronic device 801. All or some of the operations to be performed at the electronic device 801 may be performed at one or more of the external electronic devices 802, 804, or 808. For example, if the electronic device 801 should automatically perform a function or service or should perform a function or service in response to a request from a user or another device, the electronic device 801 may request one or more external electronic devices to perform at least a portion of the function or service instead of or in addition to the function or service. The one or more external electronic devices that received the request may perform at least a portion of the requested function or service, or perform additional functions or additional services related to the request, and communicate the results of the execution to the electronic device 801. The electronic device 801 may provide the results as at least a portion of a reply to the request with or without further processing of the results. To this end, for example, cloud computing, distributed computing, or client-server computing techniques may be used.

Embodiments of the subject matter and the operations described in this specification can be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Embodiments of the subject matter described in this specification can be implemented as one or more computer programs, i.e., one or more modules of computer program instructions, encoded on a computer storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or additionally, the program instructions may be encoded on an artificially generated propagated signal, e.g., a machine-generated electrical, optical, or electromagnetic signal, wherein the artificially generated propagated signal is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer storage medium may be or be included in a computer readable storage device, a computer readable storage substrate, a random or serial access memory array or device, or a combination thereof. Furthermore, while the computer storage medium is not a propagated signal, the computer storage medium may be a source or target of computer program instructions encoded in an artificially generated propagated signal. Computer storage media may also be, or be included in, one or more separate physical components or media (e.g., a plurality of CDs, disks, or other storage devices). In addition, the operations described in this specification may be implemented as operations performed by a data processing apparatus on data stored on one or more computer readable storage devices or received from other sources.

Although this description may contain many specific embodiment details, the embodiment details should not be construed as limiting the scope of any claimed subject matter, but rather as descriptions of features specific to particular embodiments. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Furthermore, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

Similarly, although operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain situations, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the embodiments described above should not be understood as requiring such separation in all embodiments, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Thus, particular embodiments of the subject matter have been described herein. Other embodiments are within the scope of the following claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. In addition, the processes depicted in the accompanying drawings do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In particular embodiments, multitasking and parallel processing may be advantageous.

As will be recognized by those skilled in the art, the innovative concepts described herein can be modified and varied over a wide range of applications. Accordingly, the scope of the claimed subject matter should not be limited to any of the specific exemplary teachings discussed above, but is instead defined by the appended claims.

Claims

1. A method of communication, comprising:

receiving downlink control information, DCI, by user equipment, UE, wherein the DCI schedules a first physical downlink shared channel, PDSCH, in a first component carrier, CC, and a second PDSCH in a second CC;

calculating, by the UE, a comparison value of the DCI; and

one or more acknowledgement/negative acknowledgement a/N bits are sent based on the comparison value,

the calculating step comprises the following steps: counting is performed on received PDSCH of CCs having up to and including the carrier index of the reference CC.

2. The method of claim 1, further comprising: comparing the comparison value with the C-DAI value of the DCI.

3. The method of claim 2, further comprising: exactly one C-DAI value is retrieved from the DCI.

4. The method of claim 1, wherein the reference CC is a CC with a larger carrier index of the first CC and the second CC.

5. The method of claim 1, wherein the reference CC is a CC with a smaller carrier index of the first CC and the second CC.

6. The method of claim 1, wherein the step of performing a count comprises: PDSCH is counted.

7. The method of claim 1, wherein the step of performing a count comprises: the PDCCHs are counted.

8. The method of claim 1, further comprising:

reserved by UEA number of acknowledgement/negative acknowledgement a/N bits, where M is the maximum number of PDSCH that can be scheduled by DCI across multiple serving cells;

determining DCI scheduling K is less than or equal to M PDSCH; and

the a/N bits of the K PDSCH are included in a set order based on the index of the serving cell.

9. The method of claim 8, wherein the step of retaining the a/N bits comprises: only M a/N bits are reserved.

10. The method of claim 8, wherein the set order is an ascending order of indexes.

11. The method of claim 8, wherein the set order is a descending order of indexes.

12. The method of claim 8, wherein M is configured to the UE by a network node gNB radio resource control, RRC.

13. A user equipment, UE, comprising:

one or more processors; and

a memory storing instructions that when executed by the one or more processors cause performance of the following operations:

receiving Downlink Control Information (DCI), wherein the DCI schedules a first Physical Downlink Shared Channel (PDSCH) in a first Component Carrier (CC) and a second PDSCH in a second CC; and

a comparison value of the DCI is calculated,

14. The UE of claim 13, wherein the instructions, when executed by the one or more processors, further cause performance of: comparing the comparison value with the C-DAI value of the DCI.

15. The UE of claim 14, wherein the instructions, when executed by the one or more processors, further cause performance of: exactly one C-DAI value is retrieved from the DCI.

16. The UE of claim 13, wherein the reference CC is a CC with a larger carrier index of the first CC and the second CC.

17. The UE of claim 13, wherein the reference CC is a CC with a smaller carrier index of the first CC and the second CC.

18. The UE of claim 13, wherein the step of performing counting comprises: PDSCH is counted.

19. The UE of claim 13, wherein the step of performing counting comprises: the PDCCHs are counted.

20. A user equipment, UE, comprising:

means for processing; and

a memory storing instructions that, when executed by the means for processing, cause the following to be performed:

a comparison value of the DCI is calculated,