Semi-static mode of a cell used to change the Physical Uplink Control Channel (PUCCH).

Abstract

Systems, methods, apparatus, and computer program products are provided for modifying the semi-static mode of a cell for physical uplink control channel (PUCCH). One method may include: configuring more than one serving cell to at least one user equipment (UE) for physical uplink control channel (PUCCH) transmission within at least one group of physical uplink control channel (PUCCH) cells; and configuring the time-domain mode of at least one applicable physical uplink control channel (PUCCH) cell within the at least one group of physical uplink control channel (PUCCH) cells to at least one UE.

Description

Technical Field

[0001] Some example embodiments may generally relate to communications including mobile or wireless telecommunication systems such as Long Term Evolution (LTE) or 5G radio access technology or New Radio (NR) access technology or other communication systems. For example, some example embodiments may generally relate to systems and / or methods for altering the semi-static mode of a cell's Physical Uplink Control Channel (PUCCH). Background Technology

[0002] Examples of mobile or wireless telecommunications systems can include Universal Mobile Telecommunications System (UMTS), Terrestrial Radio Access Network (UTRAN), Evolved UTRAN (E-UTRAN) for Long Term Evolution (LTE), LTE Advanced (LTE-A), MulteFire, LTE-A Pro, and / or 5G or New Radio (NR) access technologies. 5G wireless systems refer to next-generation (NG) radio systems and network architectures. 5G systems are primarily built on 5G New Radio (NR), but 5G (or NG) networks can also be built on E-UTRA radio. NR is estimated to provide bit rates of approximately 10 to 20 Gbit / s or higher and is capable of supporting at least service classes such as enhanced mobile broadband (eMBB) and ultra-reliable low-latency communications (URLLC) and massive machine-type communications (mMTC). NR is expected to deliver extreme broadband and ultra-robust, low-latency connectivity and massive networking to support the Internet of Things (IoT). As IoT and machine-to-machine (M2M) communications become increasingly prevalent, the demand for networks that meet the requirements of lower power, lower data rates, and longer battery life will continue to grow. Next-Generation Radio Access Network (NG-RAN) refers to the RAN of 5G, which is capable of providing both NR and LTE (and LTE Advanced) radio access. It should be noted that in 5G, nodes capable of providing radio access functionality to user equipment (i.e., similar to Node B, NB in ​​UTRAN or Evolved NB, eNB in ​​LTE) can be named Next-Generation NB (gNB) when built on NR radio and Next-Generation eNB (NG-eNB) when built on E-UTRA radio. Summary of the Invention

[0003] The subject matter of the independent claims is provided according to several aspects. Other aspects are defined in the dependent claims. Embodiments that do not fall within the scope of the claims should be interpreted as examples that can be used to understand this disclosure. Attached Figure Description

[0004] To correctly understand the exemplary embodiments, reference should be made to the accompanying drawings, in which:

[0005] Figure 1 The illustration shows an example operation of cell selection for PUCCH based on semi-static configuration according to an embodiment;

[0006] Figure 2 The illustration shows example configurations of different SCSs according to one embodiment, including a reference subcarrier spacing (SCS) and a primary cell (PCell) and a secondary cell (Scell).

[0007] Figure 3 Another example of a configuration having a reference SCS and different SCSs for Pcell and Scell ​​according to one embodiment is illustrated;

[0008] Figure 4 An example of a configuration with a 2-symbol time granularity used in a time-dependent pattern, according to an embodiment, is illustrated.

[0009] Figure 5 An example flowchart of a method according to an embodiment is illustrated;

[0010] Figure 6 An example flowchart of a method according to an embodiment is illustrated;

[0011] Figure 7A An example block diagram of a device according to an embodiment is illustrated; and

[0012] Figure 7B An example block diagram of a device according to an embodiment is illustrated. Detailed Implementation

[0013] It should be readily understood that, as generally described herein and illustrated in the figures herein, components of certain example embodiments may be arranged and designed in various different configurations. Therefore, the following detailed description of some example embodiments of systems, methods, apparatuses, and computer program products for changing the semi-static mode of a cell for PUCCH is not intended to limit the scope of any particular embodiment, but rather represents selected example embodiments.

[0014] The features, structures, or characteristics of the exemplary embodiments described throughout this specification may be combined in any suitable manner in one or more exemplary embodiments. For example, the phrases "some embodiments," "some examples," or other similar language used throughout this specification refer to the fact that a particular feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment. Therefore, the phrases "some embodiments," "some examples," "other examples," or other similar language appearing throughout this specification do not necessarily refer to the same set of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more exemplary embodiments.

[0015] Additionally, as needed, the different functions or processes discussed below may be performed in different orders and / or simultaneously with each other. Furthermore, as needed, one or more functions or processes described may be optional or may be combined. Therefore, the following description should be considered as an illustration of the principles and teachings of some exemplary embodiments, and not as a limitation thereof.

[0016] The goals of 3GPP Release 17 New Radio (NR) related to Industrial IoT (IIoT) and / or URLLC include enhanced UE feedback for Hybrid Automatic Repeat Request (HARQ) Acknowledgment (ACK). Here, an area of ​​interest includes Physical Uplink Control Channel (PUCCH) carrier handover for HARQ feedback.

[0017] The motivation for considering PUCCH carrier switching for HARQ feedback is the latency issue in Time Division Duplex (TDD) operation. More specifically, when scheduling the Physical Downlink Shared Channel (PDSCH), the gNB can indicate the time slot of the PUCCH that maps the HARQ-ACK to the PDSCH using only the k1 value (in terms of the number of time slots). In the case of TDD operation, this means that the PUCCH carrying the HARQ-ACK may need to be delayed in time to ensure that the symbols of the PUCCH transmission are actually valid for the PUCCH transmission, which takes into account the time slot format including uplink (UL), downlink (DL), and / or flexible symbols.

[0018] For URLLC services, low latency is critical. Therefore, enabling PUCCH carrier handover for HARQ-ACK feedback has been proposed, for example, for inter-band TDD with different UL / DL configurations, where this PUCCH carrier handover can provide some latency benefits. Two different modes of PUCCH carrier handover have been anticipated: dynamic indication of PUCCH carrier handover (Alternative 1) and PUCCH cell handover based on semi-static configuration / rules (Alternative 2).

[0019] Dynamic indication of PUCCH carrier handover (Alternative 1) would be, for example, through some fields in the downlink control information (DCI) of the scheduling PDSCH, indicating the PUCCH carrier handover as a direct indication of the UL serving cell to which the PUCCH should be mapped. A drawback of this method is the problem of missing DCI for scheduling the PDSCH (which could lead to misunderstanding between the gNB and UE regarding the UL serving cell to be used for PUCCH transmission). Furthermore, this would be unavailable for semi-persistent scheduling (SPS) PDSCH, and a separate DCI transmission would be required solely to indicate the PUCCH carrier handover that would increase DL control overhead. Therefore, PUCCH cell handover based on semi-static configuration / rules (Alternative 2) could become the preferred alternative.

[0020] For PUCCH cell handover based on semi-static configuration (Alternative Scenario 2), the method is to determine whether PUCCH can be transmitted on a PUCCH cell (such as Pcell or PUCCH-Scell), and if this is not possible due to conflicts with, for example, DL or Synchronization Signalling Block (SSB) symbols, then the UE will select another UL serving cell that can transmit PUCCH.

[0021] Uplink control signals (UCI) can include HARQ-ACK, scheduling request (SR) or link recovery request (LRR), and channel state information (CSI). SR / LRR and CSI use configured PUCCH resources. When the UCI includes HARQ-ACK for PDSCH used for dynamic scheduling, PUCCH resource determination can occur in three steps. In the first step, the UE can configure up to four PUCCH resource sets. For each set, the minimum and maximum payloads are predetermined or configured. The UE selects a PUCCH resource set based on the number of UCI bits to be transmitted (i.e., the UCI payload size). In the second step, the DL assignment includes a PUCCH resource indicator (PRI) field, and the UE selects PUCCH resources from the selected PUCCH resource sets (in step 1) based on the PRI value. In the third step, in the case of PUCCH format 2 or 3, the UE determines the number of resource blocks (RBs) to be used in the transmission based on the UCI payload and the configured maximum code rate. The number of RBs is determined as the minimum number of RBs with a bitrate lower than the maximum bitrate, with an upper limit of the number of RBs for the resource configuration.

[0022] If PUCCHs of different UCIs overlap in time, then the UCIs are multiplexed (according to a set of rules regarding, for example, UE processing time) into a single PUCCH transmission. As a result of this multiplexing, a new PUCCH resource can be selected for transmission. In version 16, priority indices were associated with each UCI type, and only UCIs with the same priority index were multiplexed. However, in version 17, multiplexing of UCIs with different priority indices may be supported.

[0023] Some example embodiments described herein relate to the selection of a cell for PUCCH transmission by the UE in the case of a PUCCH cell handover based on a semi-static configuration (i.e., Alternative Scenario 2). One example embodiment may involve a semi-static configuration of the cell carrying the PUCCH at certain times (i.e., the time-domain pattern of the cell for PUCCH). The cell for PUCCH can be determined directly based on this pattern, rather than based on specific rules. Some embodiments described herein provide details of such a semi-static configuration and the operation of PUCCH cell handover based on this configuration. The example embodiments described in this disclosure also cover details of the mechanism for determining the PUCCH resources on the UL serving cell applied to the PUCCH.

[0024] Some embodiments may be based on gNB configuration (such as RRC) that determines the PUCCH cell given the timing relationship (i.e., time pattern) of a semi-static configuration of a cell carrying the PUCCH. Embodiments provide operation for a time-dependent configuration of a cell that will carry the PUCCH and the associated PUCCH resource selection. Example embodiments consider different options for the RRC configuration of a time-dependent PUCCH cell and the operation of cells with different subcarrier spacings (SCS).

[0025] It should be noted that, according to some embodiments, the cell carrying the PUCCH is not semi-statically fixed during the configuration period, but for certain times, there may be time-dependent PUCCH cell configurations. These time-dependent PUCCH cell configurations allow for reduced latency because possible PUCCH transmissions are not limited by the UL / DL configuration of a single cell.

[0026] In some embodiments, it is not necessary to specify rules regarding the determination of the cell carrying the PUCCH based on interactions such as with available UL symbols (e.g., TDD UL / DL configuration, SSB, etc.) and cell order. However, in some embodiments, the gNB can directly indicate at a certain time which serving cell will carry the PUCCH for UCI feedback. This reduces ambiguity and, in particular, simplifies cell selection, and will allow the gNB to better control the potentially required UL resources (i.e., UL resource management / UL scheduler operation) for the PUCCH on different serving cells. Using semi-statically configured timing relationships allows the network to control the cells used for the PUCCH without satisfying a predefined set of rules.

[0027] As will be discussed below, certain embodiments provide solutions for determining alternative serving cells for PUCCH and PUCCH resources for PUCCH transmission. This determination can occur at the UE based on a time-dependent (mode) configuration of the cells for PUCCH by the gNB.

[0028] The following sections describe example operations for a scenario with more constraints in terms of configuration (per-slot configuration) and cell settings (the same SCS for all cells). Then, additional examples and more detailed operations will be provided for a case with increased time-domain configuration granularity (i.e., down to the symbol level) and considering cells with different SCS.

[0029] In this embodiment, the gNB can configure more than one serving cell for PUCCH transmission within a PUCCH cell group to the UE. Alternatively, the gNB can configure more than one serving cell for PUCCH transmission across more than one PUCCH cell group to the UE. For example, the same PUCCH configuration can be applied to all cells used for PUCCH transmission, or alternatively, an independent PUCCH configuration (including PUCCH resource configuration) can exist for each applicable PUCCH cell.

[0030] According to some embodiments, the gNB can also configure a time-dependent mode for the PUCCH cell applicable to the UE. The granularity of the time-domain mode can be defined in the specification (fixed) or can be configurable for the UE. The granularity of the time-domain mode can be multiple time slots (N time slots) or symbols (M symbols). In one example, the granularity can be 2 symbols, 7 symbols (6 symbols for a normal CP, 6 symbols for an extended CP), or time slots, aligned with the Version 16 PUCCH configuration that allows PUCCH configuration based on time slots or sub-time slots. The periodicity of the time-domain mode can be predetermined in the specification or can be based on RRC configuration. In example implementations, the configurable periodicity can have the same candidate values ​​as the TDD UL / DL configuration (e.g., 0.5, 0.625, 1, 1.25, 2, 2.5, 3, 4, 5, and 10 ms).

[0031] In some embodiments, the configuration may include a reference subcarrier spacing to determine the timing and granularity of the time-domain pattern. According to one option, as with TDD UL / DL configuration, the reference SCS may be a directly configurable parameter. According to another option, for the case of mixed SCS of different applicable UL serving cells, the SCS of the reference cell may determine the timing. According to embodiments, the reference cell may be implicitly determined or explicitly configured by the gNB. In one embodiment, the implicitly determined reference cell may be a Pcell or PUCCH Scell ​​of at least one PUCCH cell group. In one embodiment, the implicitly determined reference cell may be a UL serving cell with the lowest (or highest) serving cell index. In another embodiment, the implicitly determined reference cell may be a UL serving cell applicable to PUCCH transmissions with the highest SCS. In the case of more than one cell with the highest SCS, a UL serving cell with the lowest (or highest) serving cell index may be used. For each time-domain indication, the configuration may include an index of the cell used for PUCCH transmission. The index of the PUCCH cell can be given by the RRC configuration (i.e., the index of a specific PUCCH cell is 0…K) or it can be given implicitly by the index of the serving cell.

[0032] For example, for two cells available for PUCCH transmission, a single bit (0 or 1) will indicate the applicable PUCCH cell at a given time. The UE can determine the cell for the PUCCH transmission for the desired UCI transmission based on a time-dependent pattern configured by RRC. This can include one of the UE's cells within at least one PUCCH cell group acting as a timing reference cell, whose time slot / sub-time slot configuration is used to determine the timing from PDSCH transmission to HARQ-ACK transmission based on timing parameters in the DCI, which schedules PDSCH(K1) or activates SPS PDSCH transmission.

[0033] In embodiments, the UE can perform UCI multiplexing and PUCCH resource determination based on the configuration used on the determined cell for PUCCH transmission. The UE can check and / or determine the validity of the PUCCH resources on the determined cell for PUCCH transmission. For example, the UE can determine whether the determined PUCCH resources are valid for PUCCH transmission. Here, the validity check can be based on the determined cell for PUCCH (instead of the Pcell / PUCCH Scell). For example, the UL / DL mode of the determined cell for PUCCH can be used in the validity check. If the PUCCH resources are not valid, then the PUCCH (and associated UCI) can be discarded. In some embodiments, the UCI can be transmitted on either the PUCCH or the PUSCH, and if the resulting PUCCH resources even partially overlap with a PUSCH in any serving UL cell, then the UCI can be mapped on the overlapping PUSCH based on the (version 15 / 16) NR multiplexing rules of the UCI on the PUSCH. Otherwise, the PUCCH can be transmitted on the determined cell for PUCCH transmission.

[0034] Figure 1 An example of baseline operation for cell selection for PUCCH based on semi-static configuration, according to an embodiment, is illustrated. Figure 1 The example shown is provided based on the following assumptions: two cells are available for PUCCH transmission (Pcell and Scell) – in the configured time-domain mode, Pcell is associated with '0' and Scell ​​with the value '1'; the configured reference SCS and the SCS of both cells are 15kHz SCS (i.e., a 1ms slot length); and the time-domain configuration granularity is at the slot level, and the mode periodicity is 5ms (i.e., a mode length of 5 slots). For example, the gNB configures mode "00011" for a 5ms periodicity with slot granularity (i.e., 1ms granularity for a 15kHz SCS).

[0035] Based on the time-domain pattern configured for the PUCCH cell '00011', the UE can determine the PUCCH cell given by the pattern. That is, for slots#{0,1,2}+k*pattern_length, where k≥0, the UE can determine the Pcell as the cell for PUCCH transmission. Figure 1 In the example, slots 0 to 2 and 5 to 7 are shown in gray shading. Based on the pattern with '1', an Scell ​​can be configured as a cell for PUCCH transmission, meaning that for slots#{3,4}+k*pattern_length, k≥0, an SCell is selected.

[0036] One embodiment includes a time-dependent pattern with slot time granularity at the reference SCS. The slot timing for UCI transmission can be determined based on the reference SCS or reference cell slot timing (e.g., K1 in the case of HARQ-ACK).

[0037] Figure 2 The illustration shows an example configuration of a reference SCS and different SCSs, PCell and Scell, according to one embodiment. More specifically, Figure 2 The example illustration shows a configuration with a reference SCS, which is equal to the Pcell SCS but twice the size of the ScellSCS. Figure 2 In the example, the time-domain pattern granularity is equal to the Pcell slot (half the Scell ​​slot), and the pattern length is five. For this configuration to be meaningful, the Scell's PUCCH resource configuration includes resources restricted to the first and second halves of the slot. In the example embodiment, a separate PUCCH configuration may exist for each applicable cell or for each applicable SCS value. In the case of HARQ-ACK, the appropriate PUCCH resource can be selected using the PRI dynamically indicated in the DCI that schedules the PDSCH. In the case of semi-persistent PUCCH resource allocation (SR, LLR, P-CSI or SP-CSI, HARQ-ACK for SP PDSCH), two resource allocations can be given to the UE in the first and second halves of the slot. The UE can select the appropriate resource based on the determined timing. It should be noted that this approach can be extended to apply to larger differences between the SCell SCS and the reference SCS.

[0038] Figure 3 Another example of a configuration with a reference SCS and different SCSs for Pcell and Scell, according to one embodiment, is illustrated. More specifically, Figure 3 The diagram illustrates a configuration with a reference SCS, which is equal to the Pcell SCS but half the size of the Scell ​​SCS. Figure 3 In the example, the time-domain mode granularity is equal to the Pcell slot (two Scell ​​slots), and the mode length is five. According to the embodiment, when selecting an Scell ​​for a PUCCH, rules can be used to determine which SCell in the SCell slots is used for PUCCH transmission. For example, one approach could be to determine the reference PUCCH resource (or reference slot / sub-slot) on the reference cell (corresponding to, for example, the reference SCS of the PCell), including any UCI multiplexing steps. The last SCell slot overlapping with the determined reference PUCCH resource can be selected for UCI transmission.

[0039] Another embodiment may include a time-dependent pattern with time granularity (e.g., 7, 2, or 1 symbols), which is shorter than the time slot at the reference SCS. The Scell ​​time slot determination mechanism discussed above for patterns with time slot granularity can also be applied to this case. However, due to the finer time granularity, some other rules can be utilized.

[0040] According to some embodiments, the slot timing for UCI transmission can be determined based on a reference SCS or reference cell slot timing (e.g., K1 in the case of HARQ-ACK). Further, to account for a finer time granularity of the mode, a reference PUCCH resource (including any UCI multiplexing steps) on the reference cell (corresponding to the reference SCS, such as PCell) can be determined. The symbol of the determined reference PUCCH resource can be used to select the correct time portion of the mode for cell selection. Figure 4 An example of this configuration, according to an embodiment, is illustrated, having a 2-symbol time granularity used in a time-dependent pattern. As an example, the PUCCH resources occupying the last two symbols of time slot #4 will be transmitted on the Pcell, while the PUCCH resources occupying symbols #7 and #8 of time slot #4 will be transmitted on the Scell.

[0041] In some embodiments, special rules can be provided for the reference PUCCH resources that occupy symbols on the PUCCH cell change boundary. For example, the pattern for the PUCCH resources occupying the last 6 symbols of slot #4 would be {1 1 0 0 0 0} (where the pattern is presented at the symbol granularity). Some alternatives may include discarding such a PUCCH, transmitting the PUCCH between cells indicated on the overlapping portion of the pattern on the cell with the highest configuration priority or the lowest (or highest) cell ID, or transmitting the PUCCH on the cell that applies to the first or last symbol of the reference PUCCH.

[0042] When PUCCH resources are configured individually for each applicable cell or SCS value, PUCCH resource determination and possible UCI multiplexing can be re-executed after the cell for PUCCH is selected. This may result in changes to the symbols occupied by the PUCCH resources, and thus conflicts with the cell selection mode. For example, the PUCCH resources determined for the reference cell may occupy symbols #7 and #8 of slot #4 based on which Scell ​​is selected. Another PUCCH resource may also exist in slot #4, occupying symbols #5 and #6, and an Scell ​​is selected for that PUCCH as well. The Scell ​​has its own PUCCH resource configuration, which is applied to the UCI mapped to the Scell. Therefore, UCI is multiplexed on the PUCCH resources occupying symbols #7, #8, and #9. The cell selection mode for these symbols is {1 1 0}. Some alternatives for handling this situation may include discarding the PUCCH, or selecting a cell only once for the PUCCH and then no longer considering the cell selection mode (for that PUCCH transmission). If possible, the PUCCH is transmitted on the Scell ​​according to the Scell ​​UL / DL mode. Furthermore, it is possible for PUCCH transmissions on different cells to overlap in time. To prevent this, according to some embodiments, subsequent PUCCHs can be discarded.

[0043] In some embodiments, cell selection for PUCCH can be restricted (predefined or configured) for certain UCI priorities or UCI components (HARQ-ACK, CSI, L1-RSRP, SR, LRR). For example, cell selection may be applied only for high-priority HARQ-ACK. If the PUCCH cell is selected based on a time-dependent cell selection pattern or if there is no UCI following a time-dependent cell selection pattern transmitted on the same time slot, then other UCI components may be transmitted on the PUCCH cell (depending on the PUCCH cell's UL / DL pattern).

[0044] Figure 5 An example flowchart of a method for cell selection for PUCCH based on semi-static configuration according to one embodiment is illustrated. In some example embodiments, Figure 5 The example flowchart can be executed by network entities or network nodes in a communication system (such as LTE or 5G NR). In some example embodiments, execution... Figure 5The network entities in one or more processes described herein may include or be included in UE, SL UE, relay UE, mobile station, mobile device, fixed device, wireless transmission / reception unit, IoT device or sensor, etc.

[0045] like Figure 5 As illustrated in the example, in step 505, the method may include: receiving configuration information from the gNB, the configuration information having more than one serving cell for PUCCH transmissions within at least one PUCCH cell group. Furthermore, the method may include: in step 510, receiving configuration information from the gNB, the configuration information having a time-dependent pattern applicable to the PUCCH cell. In an embodiment, the method may include: in step 515, determining the cell for the desired UCI transmission based on the configured time-dependent pattern.

[0046] like Figure 5 The example further illustrates that the method may include: in 520, performing UCI multiplexing and PUCCH resource determination based on the configuration used on the determined cell for PUCCH transmission. The method may also include: in 525, determining the validity of PUCCH resources on the determined cell for PUCCH transmission. In an embodiment, the method may include: in 530, performing UCI transmission on the PUCCH or PUSCH on the determined cell for PUCCH transmission.

[0047] Figure 6 An example flowchart of a method for changing the semi-static mode of a cell used for PUCCH, according to one embodiment, is illustrated. In some example embodiments, Figure 6 The example flowchart can be executed by network entities or network nodes in a communication system (such as LTE or 5G NR). In some example embodiments, execution... Figure 6 The network entities of the method may include base stations, access nodes, node B, eNB, gNB, NG-RAN nodes, Transmitter Receiver Points (TRPs), High Altitude Platform Stations (HAPS), relay stations, etc., or may be included in base stations, access nodes, node B, eNB, gNB, NG-RAN nodes, Transmitter Receiver Points (TRPs), High Altitude Platform Stations (HAPS), relay stations, etc.

[0048] like Figure 6As illustrated in the example, the method may include, in step 605, configuring at least one UE with configurations for more than one serving cell for PUCCH transmission within at least one PUCCH cell group. The method may also include, in step 610, configuring at least one UE with a time-domain mode or time-dependent mode configuration for applicable PUCCH cells within at least one PUCCH cell group. In some embodiments, the same PUCCH configuration may be applied to all cells used for PUCCH transmission, or an independent PUCCH configuration may be applied to each applicable PUCCH cell among the applicable PUCCH cells.

[0049] According to an embodiment, the granularity of the time-domain mode can be fixed or configurable for at least one UE. Further, in an embodiment, the granularity of the time-domain mode can be in the form of multiple time slots or symbols.

[0050] In some embodiments, the periodicity of the time-domain pattern can be fixed in the specification or determined based on Radio Resource Configuration (RRC). According to one embodiment, the configuration of the time-domain pattern may include a reference subcarrier spacing (SCS) to determine the timing and granularity of the time-domain pattern. In embodiments, the reference SCS may be a directly configurable parameter. According to some embodiments, in the case of mixed SCSs for different applicable UL serving cells, the SCS of the reference cell can determine the timing. In one example, the reference cell may be implicitly determined or explicitly configured by a network node (such as a base station or gNB).

[0051] In some embodiments, the implicitly determined reference cell may include a Pcell or PUCCH Scell ​​of at least one PUCCH cell group. According to embodiments, the implicitly determined reference cell may include a UL serving cell with the lowest (or highest) serving cell index. According to some embodiments, the implicitly determined reference cell may include a UL serving cell applicable to PUCCH transmissions with the highest SCS. In one example, when there are more than one cell with the highest subcarrier spacing (SCS), an uplink (UL) serving cell with the lowest (or highest) serving cell index may be used. According to embodiments, the time-domain mode configuration may include the index of the cell used for PUCCH transmission for each time-domain indication, and the index of the PUCCH cell may be given by the RRC configuration or implicitly given by the serving cell index. In some embodiments, Figure 6 The method may also include: in 615, receiving uplink control information (UCI) on PUCCH or PUSCH from at least one UE.

[0052] Figure 7AAn example of apparatus 10 according to an embodiment is illustrated. In the embodiment, apparatus 10 may be a node, host, or server in or serving a communication network. For example, apparatus 10 may be a network node, sensing node, satellite, base station, Node B, evolved Node B (eNB), 5G Node B or access point, next-generation Node B (NG-NB or gNB), TRP, HAPS, integrated access and backhaul (IAB) node, and / or WLAN access point associated with a radio access network (such as an LTE network, 5G, or NR). In some example embodiments, apparatus 10 may be an eNB in ​​LTE or a gNB in ​​5G.

[0053] It should be understood that in some example embodiments, device 10 may comprise an edge cloud server as part of a distributed computing system, in which the server and radio nodes may be standalone devices communicating with each other via a radio path or via a wired connection, or the server and radio nodes may reside in the same entity communicating via a wired connection. For example, in some example embodiments where device 10 represents a gNB, it may be configured in a central unit (CU) and distributed unit (DU) architecture that divides gNB functionality. In such an architecture, the CU may be a logical node that includes gNB functions such as user data transfer, mobility control, radio access network sharing, location and / or session management, etc. The CU may control the operation of the DU(s) through a frontend interface. The DU may be a logical node that includes a subset of gNB functions, depending on the functional splitting option. It should be noted that those skilled in the art will understand that device 10 may include Figure 7A Components or features not shown in the diagram.

[0054] like Figure 7A As illustrated in the example, device 10 may include a processor 12 for processing information and executing instructions or operations. Processor 12 may be any type of general-purpose or special-purpose processor. In practice, as an example, processor 12 may include one or more of the following: a general-purpose computer, a special-purpose computer, a microprocessor, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), and a processor or any other processing unit based on a multi-core processor architecture. Although in Figure 7A A single processor 12 is shown, but multiple processors may be utilized according to other embodiments. For example, it should be understood that in some embodiments, device 10 may include two or more processors, which may form a multiprocessor system capable of supporting multiple processing (e.g., in this case, processor 12 may represent multiple processors). In some embodiments, the multiple processors may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0055] The processor 12 can perform functions associated with the operation of the device 10, which may include, for example, precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the device 10, including processes related to the management of communication or communication resources.

[0056] Device 10 may also include or be coupled to memory 14 (internal or external), which may be coupled to processor 12 for storing information and instructions that can be executed by processor 12. Memory 14 may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and / or removable memory. For example, memory 14 may consist of any combination of random access memory (RAM), read-only memory (ROM), static storage devices (such as disks or optical discs), hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium or other suitable storage components. Instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 12, enable device 10 to perform the tasks described herein.

[0057] In embodiments, device 10 may also include or be coupled to (internal or external) a drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software for execution by processor 12 and / or device 10.

[0058] In some embodiments, device 10 may further include or be coupled to one or more antennas 15 for transmitting and / or receiving signals and / or data to and from device 10. Device 10 may also include or be coupled to a transceiver 18 configured to transmit and receive information. Transceiver 18 may include, for example, multiple radio interfaces that may be coupled to antenna(s) 15, or may include any other suitable transceiver components. The radio interfaces may correspond to a variety of radio access technologies, including one or more of the following: GSM, NB-IoT, LTE, 5G, WLAN, Bluetooth, BT-LE, NFC, Radio Frequency Identification (RFID), Ultra Wideband (UWB), MulteFire, etc. The radio interfaces may include components such as filters, converters (e.g., digital-to-analog converters, mappers, Fast Fourier Transform (FFT) modules, etc.) to generate symbols for transmission via one or more downlinks and to receive symbols (e.g., via an uplink).

[0059] Therefore, transceiver 18 can be configured to modulate information onto a carrier waveform for transmission by antenna(s)15 and demodulate information received via antenna(s)15 for further processing by other elements of device 10. In other embodiments, transceiver 18 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some embodiments, device 10 may include input and / or output devices (I / O devices) or input / output components.

[0060] In an embodiment, memory 14 may store software modules that provide functionality when executed by processor 12. These modules may include, for example, an operating system that provides operating system functionality to device 10. The memory may also store one or more functional modules (such as applications or programs) to provide additional functionality to device 10. Components of device 10 may be implemented in hardware or as any suitable combination of hardware and software.

[0061] According to some embodiments, the processor 12 and memory 14 may be included in or form part of a processing circuit system / component or a control circuit system / component. Furthermore, in some embodiments, the transceiver 18 may be included in or form part of a transceiver circuit system / component.

[0062] As used herein, the term "circuit system" can refer to a purely hardware circuit system implementation (e.g., analog and / or digital circuit systems), a combination of hardware circuitry and software, a combination of analog and / or digital hardware circuitry and software / firmware, any portion of (multiple) hardware processors and software (including digital signal processors) that work together to enable a device (e.g., device 10) to perform various functions, and / or (multiple) hardware circuitry and / or (multiple) processors or portions thereof that operate using software, but which may be absent when operation is not required. As another example, as used herein, the term "circuit system" can also encompass implementations of hardware circuitry or processors (or processors) alone, or a portion of hardware circuitry or processors and their accompanying software and / or firmware. The term "circuit system" can also encompass baseband integrated circuits, such as those in servers, cellular network nodes or devices, or other computing or networking devices.

[0063] As introduced above, in some embodiments, device 10 may be a network element or RAN node, such as a base station, access point, Node B, eNB, gNB, TRP, HAPS, IAB node, WLAN access point, etc. In one example embodiment, device 10 may be a gNB. According to some embodiments, device 10 may be controlled by memory 14 and processor 12 to perform functions associated with any of the embodiments described herein. For example, in some embodiments, device 10 may be configured to execute the flowcharts or signaling diagrams described herein (such as...). Figure 6 The process is one or more of the processes depicted in any flowchart or signaling diagram (or any other method described herein). In some embodiments, such as those discussed herein, apparatus 10 may be configured to perform processes related to changing the semi-static mode of the cell used for PUCCH.

[0064] According to embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to configure more than one serving cell for PUCCH transmission within at least one PUCCH cell group for at least one UE. In embodiments, the apparatus 10 may be controlled by the memory 14 and the processor 12 to configure at least one UE for a time-domain mode or a time-dependent mode for applicable PUCCH cells within at least one PUCCH cell group. In some embodiments, the apparatus 10 may also be controlled by the memory 14 and the processor 12 to receive uplink control information (UCI) on PUCCH or PUSCH from at least one UE.

[0065] Figure 7BAn example of device 20 according to another embodiment is illustrated. In the embodiment, device 20 may be a node or element in or associated with a communication network, such as a UE, communication node, mobile equipment (ME), mobile station, mobile device, fixed equipment, IoT device, or other device. As described herein, a UE may alternatively be referred to as, for example, a mobile station, mobile equipment, mobile unit, mobile device, user equipment, subscriber station, wireless terminal, tablet, smartphone, IoT device, sensor or NB-IoT device, watch or other wearable device, head-mounted display (HMD), vehicle, drone, medical device and its applications (e.g., remote surgery), industrial device and its applications (e.g., robots and / or other wireless devices operating in the context of industrial and / or automated processing chains), consumer electronics devices, devices operating on commercial and / or industrial wireless networks, etc. As an example, device 20 may be implemented in, for example, a wireless handheld device, a wireless plug-in accessory, etc.

[0066] In some example embodiments, device 20 may include one or more processors, one or more computer-readable storage media (e.g., memory, storage device, etc.), one or more radio access components (e.g., modem, transceiver, etc.), and / or a user interface. In some embodiments, device 20 may be configured to operate using one or more radio access technologies (such as GSM, LTE, LTE-A, NR, 5G, WLAN, WiFi, NB-IoT, Bluetooth, NFC, MulteFire, and / or any other radio access technology). It should be noted that those skilled in the art will understand that device 20 may include... Figure 7B Components or features not shown in the diagram.

[0067] like Figure 7B As illustrated in the example, device 20 may include or be coupled to a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general-purpose or special-purpose processor. In practice, as an example, processor 22 may include one or more of the following: general-purpose computer, special-purpose computer, microprocessor, digital signal processor (DSP), field-programmable gate array (FPGA), application-specific integrated circuit (ASIC), and processor based on a multi-core processor architecture. Although in Figure 7B A single processor 22 is shown, but multiple processors may be utilized according to other embodiments. For example, it should be understood that in some embodiments, device 20 may include two or more processors that can form a multiprocessor system capable of supporting multiple processing (e.g., in this case, processor 22 may represent multiple processors). In some embodiments, the multiple processors may be tightly coupled or loosely coupled (e.g., to form a computer cluster).

[0068] The processor 22 can perform functions associated with the operation of the device 20. As some examples, these functions may include precoding of antenna gain / phase parameters, encoding and decoding of individual bits forming communication messages, formatting of information, and overall control of the device 20, including processes related to the management of communication resources.

[0069] Device 20 may also include or be coupled to memory 24 (internal or external), which may be coupled to processor 22 for storing information and instructions that can be executed by processor 22. Memory 24 may be one or more memories and may be of any type suitable for the local application environment, and may be implemented using any suitable volatile or non-volatile data storage technology, such as semiconductor-based memory devices, magnetic memory devices and systems, optical memory devices and systems, fixed memory and / or removable memory. For example, memory 24 may consist of any combination of random access memory (RAM), read-only memory (ROM), static storage devices (such as disks or optical discs), hard disk drives (HDDs), or any other type of non-transitory machine or computer-readable medium. Instructions stored in memory 24 may include program instructions or computer program code that, when executed by processor 22, enable device 20 to perform the tasks described herein.

[0070] In embodiments, device 20 may also include or be coupled to (internal or external) a drive or port configured to accept and read external computer-readable storage media, such as an optical disc, USB drive, flash drive, or any other storage media. For example, the external computer-readable storage media may store computer programs or software for execution by processor 22 and / or device 20.

[0071] In some embodiments, device 20 may further include or be coupled to one or more antennas 25 for receiving downlink signals from device 20 and transmitting them via an uplink. Device 20 may also include a transceiver 28 configured to transmit and receive information. Transceiver 28 may also include a radio interface (e.g., a modem) coupled to antenna 25. The radio interface may correspond to a variety of radio access technologies, including one or more of the following: GSM, LTE, LTE-A, 5G, NR, WLAN, NB-IoT, Bluetooth, BT-LE, NFC, RFID, UWB, etc. The radio interface may include other components (such as filters, converters (e.g., digital-to-analog converters, symbol demappers, signal shaping components, inverse fast Fourier transform (IFFT) modules, etc.) to process symbols carried by the downlink or uplink, such as OFDMA symbols.

[0072] For example, transceiver 28 may be configured to modulate information onto a carrier waveform for transmission by antenna(s)25 and demodulate information received via antenna(s)25 for further processing by other elements of device 20. In other embodiments, transceiver 28 may be able to directly transmit and receive signals or data. Additionally or alternatively, in some embodiments, device 20 may include input and / or output devices (I / O devices). In some embodiments, device 20 may also include a user interface, such as a graphical user interface or a touchscreen.

[0073] In an embodiment, memory 24 stores software modules that provide functionality when executed by processor 22. These modules may include, for example, an operating system that provides operating system functionality to device 20. The memory may also store one or more functional modules (such as applications or programs) to provide additional functionality to device 20. Components of device 20 may be implemented in hardware or as any suitable combination of hardware and software. Optionally, according to an example embodiment, device 20 may be configured to communicate with device 10 via wireless or wired communication link 70 according to any radio access technology (such as NR).

[0074] According to some embodiments, the processor 22 and memory 24 may be included in or form part of a processing circuit system or control circuit system. Furthermore, in some embodiments, the transceiver 28 may be included in or form part of a transceiver circuit system.

[0075] As discussed above, according to some embodiments, device 20 may be a UE, SL UE, relay UE, mobile device, mobile station, ME, IoT device, and / or NB-IoT device, etc. According to some embodiments, device 20 may be controlled by memory 24 and processor 22 to perform functions associated with any of the embodiments described herein, such as... Figure 5 The diagram in the image or relative to the image in the image Figure 5 One or more of the operations described herein, or any other method described herein. For example, in an embodiment, device 20 may be controlled to perform processes related to changing the semi-static mode of a cell used for PUCCH.

[0076] According to some embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to receive configuration information for more than one serving cell for PUCCH transmission within at least one PUCCH cell group, and to receive configuration information including a time-domain mode or a time-dependent mode for applicable Physical Uplink Control Channel (PUCCH) cells within at least one Physical Uplink Control Channel (PUCCH) cell group. In embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to determine the cell for PUCCH transmission for UCI transmission based on the configured time-domain mode. According to some embodiments, one cell in the PUCCH cell group acts as a timing reference cell, whose time slot / sub-time slot configuration is used to determine the timing from PDSCH transmission to HARQ-ACK transmission based on timing parameters in the DCI, which schedules PDSCH(K1) or activates SPS PDSCH transmission.

[0077] In some embodiments, the apparatus 20 may be controlled by the memory 24 or the processor 22 to perform UCI multiplexing and PUCCH resource determination based on the configuration used on the determined cell for PUCCH transmission. According to embodiments, the apparatus 20 may be controlled by the memory 24 and the processor 22 to determine or check the validity of PUCCH resources on the determined cell for PUCCH transmission. In one embodiment, the apparatus 20 may be controlled by the memory 24 and the processor 22 to check validity by determining whether the determined PUCCH resources are valid for PUCCH transmission, at least in part based on the determined cell for PUCCH. According to embodiments, when it is determined that the PUCCH resources are not valid, the PUCCH may be discarded.

[0078] According to embodiments, apparatus 20 may be controlled by memory 24 and processor 22 to transmit UCIs on PUCCH or PUSCH. In some embodiments, when the generated PUCCH resources completely or partially overlap with PUSCHs on the same or different serving UL cells, transmitting UCIs may include mapping UCIs on the overlapping PUSCHs according to (version 15 / version 16) NR UCI multiplexing on the PUSCH operation. In embodiments, when the generated PUCCH resources do not overlap with PUSCHs on the same or different serving UL cells, transmitting UCIs may include transmitting UCIs on the determined cells for PUCCH transmission.

[0079] In some embodiments, the apparatus (e.g., apparatus 10 and / or apparatus 20) may include components for performing a method, process, or any variation of the variations discussed herein. Examples of components may include one or more processors, memories, controllers, transmitters, receivers, and / or computer program code for inducing the execution of operations.

[0080] In light of the foregoing, certain exemplary embodiments provide several technical improvements, enhancements, and / or advantages over the prior art, and constitute improvements at least in the technical field of radio network control and management. For example, certain embodiments are applicable to semi-persistent UCI configurations (e.g., CSI, SR, LRR) and HARQ-ACK triggered by SPS PDSCH, and also to DCI-triggered UCI, such as PDSCH scheduled by DCI or HARQ-ACK triggered by aperiodic CSI. The exemplary embodiments do not increase the DCI payload. Furthermore, certain embodiments support time-dependent configuration of the cell carrying the PUCCH, thereby allowing for more optimized configurations and the possibility of reduced UCI latency, since PUCCH transmission may not be limited by the UL / DL configuration of a single cell. Moreover, according to certain embodiments, it is not necessary to specify potentially complex rules regarding the determination of the cell carrying the PUCCH based on interactions such as with available UL symbols (e.g., TDD UL / DL configuration, SSB, etc.) and cell order. This reduces ambiguity and, in particular, simplifies cell selection. The network can also adjust cell selection to better suit the network's resource management and scheduling strategies, as cell selection is controlled by the gNB via configuration. Therefore, the use of certain example embodiments leads to improvements in the functionality of the communication network and its nodes (such as base stations, eNBs, gNBs, and / or IoT devices, UEs, or mobile stations).

[0081] In some example embodiments, the functionality of any of the methods, processes, signaling diagrams, algorithms, or flowcharts described herein may be implemented by software and / or computer program code or portions thereof stored in memory or other computer-readable or tangible media and may be executed by a processor.

[0082] In some example embodiments, the device may include or be associated with at least one software application, module, unit, or entity configured as (multiple) arithmetic operations or a program or part of a program (including added or updated software routines), which may be executed by at least one operating processor or controller. The program (also referred to as a program product or computer program, including software routines, applets, and macros) may be stored in any device-readable data storage medium and may include program instructions for performing a specific task. The computer program product may include one or more computer-executable components configured to perform some example embodiments when the program is run. One or more computer-executable components may be at least one piece of software code or code. Modifications and configurations required to implement the functionality of the example embodiments may be executed as (multiple) routines, which may be implemented as added or updated software routines. In one example, (multiple) software routines may be downloaded to the device.

[0083] As an example, software or computer program code, or portions thereof, may be in the form of source code, object code, or some intermediate form, and may be stored on some carrier, distribution medium, or computer-readable medium, which may be any entity or device capable of carrying the program. For example, such a carrier may include recording media, computer memory, read-only memory, optoelectronic and / or electrical carrier signals, telecommunication signals, and / or software distribution packages. Depending on the required processing power, the computer program may execute in a single electronic digital computer, or it may be distributed across several computers. The computer-readable medium or computer-readable storage medium may be a non-transitory medium.

[0084] In other example embodiments, the functionality of the example embodiments may be performed by hardware or circuitry systems included in the device, such as by using application-specific integrated circuits (ASICs), programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), or any other combination of hardware and software. In yet another example embodiment, the functionality of the example embodiments may be implemented as a signal (such as a non-tangible component) carried by an electromagnetic signal downloaded from the Internet or another network.

[0085] According to example embodiments, an apparatus (such as a node, device, or corresponding component) may be configured as a circuit system, a computer, or a microprocessor (such as a single-chip computer element) or a chipset that may include at least a memory for providing storage capacity for arithmetic operations(s) and / or an operation processor for performing arithmetic operations(s).

[0086] The exemplary embodiments described herein can be applied to both singular and plural implementations, regardless of whether singular or plural language is used in conjunction with the description of certain embodiments. For example, an embodiment describing the operation of a single network node can also be applied to embodiments that include multiple instances of network nodes, and vice versa.

[0087] Those skilled in the art will readily understand that the exemplary embodiments discussed above can be practiced with processes of different sequences and / or hardware components with configurations different from the disclosed configurations. Therefore, although some embodiments have been described based on these exemplary embodiments, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be readily apparent while still remaining within the spirit and scope of the exemplary embodiments.

Claims

1. An apparatus for communication, comprising: means for configuring more than one serving cell for a physical uplink control channel transmission within at least one physical uplink control channel cell group to at least one user equipment; and means for configuring a time domain pattern to determine a physical uplink control channel cell within the at least one physical uplink control channel cell group to the at least one user equipment, wherein one of the cells within the at least one physical uplink control channel cell group acts as a timing reference cell, a slot or sub-slot configuration of the timing reference cell is used to determine timing from a physical downlink shared channel transmission to a hybrid automatic repeat request acknowledgement transmission according to a timing parameter in a downlink control information that schedules a physical downlink shared channel or activates a semi-persistent scheduled physical downlink shared channel transmission.

2. The apparatus of claim 1, wherein a same physical uplink control channel configuration is applied for all cells used for the physical uplink control channel transmission.

3. The apparatus of claim 1, wherein a granularity of the time domain pattern is at least one of the following: fixed for the at least one user equipment; configurable for the at least one user equipment; and in terms of a number of slots or symbols.

4. The apparatus of claim 1, wherein a periodicity of the time domain pattern is fixed in a specification or determined based on a radio resource configuration.

5. The apparatus of claim 1, wherein the configuration of the time domain pattern includes a reference subcarrier spacing to determine timing and granularity of the time domain pattern.

6. The apparatus of claim 1, wherein for a case of different uplink serving cell hybrid subcarrier spacing, the subcarrier spacing of a reference cell determines timing and granularity of the time domain pattern.

7. The apparatus of any one of claims 1 to 6, wherein the configuration of the time domain pattern includes, for each time domain indication, an index of the cell used for physical uplink control channel transmission, and wherein the index of the physical uplink control channel cell is given by a radio resource control configuration or implicitly given by a serving cell index.

8. A method for communication, comprising: receiving configuration information for more than one serving cell for a physical uplink control channel transmission within at least one physical uplink control channel cell group at a user equipment; receiving configuration information including a time domain pattern to determine a physical uplink control channel cell within the at least one physical uplink control channel cell group; determining a cell for a physical uplink control channel transmission of an uplink control information transmission based on the configured time domain pattern; performing uplink control information multiplexing and physical uplink control channel resource determination according to the configuration information used on the determined cell for the physical uplink control channel transmission; checking validity of the determined physical uplink control channel resources on the determined cell for the physical uplink control channel transmission; and transmitting uplink control information on physical uplink control channel or physical uplink shared channel when the physical uplink control channel resources are valid, wherein one of the cells within the at least one physical uplink control channel cell group acts as a timing reference cell, a slot or sub-slot configuration of the timing reference cell being used to determine timing from a physical downlink shared channel transmission to a hybrid automatic repeat request acknowledgement transmission according to a timing parameter in downlink control information scheduling a physical downlink shared channel or activating a semi-persistent scheduled physical downlink shared channel transmission.

9. An apparatus for communication, comprising: means for receiving configuration information for more than one serving cell for physical uplink control channel transmission within at least one physical uplink control channel cell group; means for receiving configuration information including a time domain pattern to determine physical uplink control channel cells within the at least one physical uplink control channel cell group; means for determining cells for the physical uplink control channel transmission of uplink control information transmission based on the configured time domain pattern; means for performing uplink control information multiplexing and physical uplink control channel resource determination according to the configuration information used on the determined cells for the physical uplink control channel transmission; means for checking validity of the determined physical uplink control channel resources on the determined cells for the physical uplink control channel transmission; and and means for transmitting uplink control information on physical uplink control channel or physical uplink shared channel when the physical uplink control channel resources are valid, wherein one of the cells within the at least one physical uplink control channel cell group acts as a timing reference cell, a slot or sub-slot configuration of the timing reference cell being used to determine timing from a physical downlink shared channel transmission to a hybrid automatic repeat request acknowledgement transmission according to a timing parameter in downlink control information scheduling a physical downlink shared channel or activating a semi-persistent scheduled physical downlink shared channel transmission.

10. The apparatus of claim 9, wherein the reference cell is explicitly configured by a network node or implicitly determined.

11. The apparatus of claim 10, wherein the implicitly determined reference cell includes a primary cell or a physical uplink control channel secondary cell of the at least one physical uplink control channel cell group.

12. The apparatus of claim 10, wherein the implicitly determined reference cell includes an uplink serving cell having a lowest or highest serving cell index.

13. The apparatus of claim 9, wherein the means for checking the validity of the physical uplink control channel resource further comprises: means for determining whether the determined physical uplink control channel resource is valid for the physical uplink control channel transmission based at least in part on the determined cell for physical uplink control channel.

14. The apparatus of any one of claims 9-13, wherein the means for transmitting the uplink control information further comprises: means for mapping the uplink control information on the physical uplink shared channel that is fully or partially overlaid by the obtained physical uplink control channel resource when the obtained physical uplink control channel resource fully or partially overlaps the physical uplink shared channel on the same or different uplink serving cell; and means for transmitting the uplink control information on the determined cell for the physical uplink control channel transmission when the obtained physical uplink control channel resource does not overlap the physical uplink shared channel on the same or different uplink serving cell.

Images