Method and apparatus for mobile communications

Abstract

Methods and apparatuses for mobile communications. Various solutions for dynamic and static cross-carrier PUCCH signaling and configuration in mobile communications are described. An apparatus that can be implemented in a UE utilizes a static method or a dynamic method to select a CC from a plurality of CCs. The UE then performs PUCCH transmission to the network using the selected CC. By utilizing the present invention, mobile communications can be better performed.

Description

[0001] Cross-referencing of related patent applications

[0002] This invention is part of a non-provisional application and claims priority to U.S. Patent Application 63 / 094,369, filed October 21, 2020, the entire contents of which are incorporated herein by reference. Technical Field

[0003] This invention relates generally to mobile communications, and more particularly to techniques for dynamic and static cross-carrier physical uplink control channel (PUCCH) signaling and configuration in mobile communications. Background Technology

[0004] Unless otherwise stated by the present invention, the methods described in this section are not prior art as claimed in the claims, and are not acknowledged as prior art by virtue of their inclusion in this section.

[0005] In wireless communication (such as according to fifth generation (5G) thIn mobile communications compliant with the 3rd Generation Partnership Project (3GPP) specifications for New Radio (NR) in Generation 5G, while Ultra-Reliable Low-Latency Communication (URLLC) deployed in sub-6GHz bands using Time-Division Duplex (TDD) enjoys wider bandwidth availability, it still faces challenges related to suboptimal latency performance dominated by TDD uplink (UL) and downlink (DL) configurations. For example, in outdoor wide-area deployments, TDD patterns tend to support either UL-intensive or DL-intensive traffic; however, these TDD patterns tend to introduce additional latency, thus compromising both latency and reliability requirements. In indoor local deployments, although latency-friendly patterns can be deployed, such patterns tend to be more suitable for symmetrical traffic. URLLC services can be mixed with enhanced Mobile Broadband (eMBB) services for indoor deployments. Furthermore, spectral efficiency is reduced because handover between UL and DL transmissions requires longer guard intervals. Alternative options are needed where traditional TDD operators are unwilling to change their TDD UL / DL configurations. For example, inter-band TDD carrier aggregation (CA) can be used to mitigate the additional alignment delay introduced by UL / DL modes on TDD carriers. Given the above, further research in 3GPP involves how to support PUCCH carrier handover within PUCCH groups. Therefore, a solution for dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications is required. Summary of the Invention

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

[0007] The object of this invention is to provide solutions or schemes for addressing the problems described herein. More specifically, the various schemes proposed in this invention are intended to provide solutions for dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications. For example, dynamic selection of component carriers (CCs) used for PUCCH transmission can help reduce the latency of CA operations for two or more inter-band carriers with different TDD modes. Furthermore, using the nearest UL transmission opportunity on different CCs for PUCCH transmission can help reduce hybrid automatic repeat request (HARQ) feedback latency.

[0008] In one aspect, a method may include: the UE selecting a CC from multiple CCs using a static or dynamic method. The method may also include: the UE transmitting a PUCCH to the network using the selected CC.

[0009] By utilizing this invention, mobile communication can be improved.

[0010] It is worth noting that although the description provided in this invention may be within the context of some radio access technologies, networks, and network topologies (such as 5G / NR mobile communication), the proposed concepts, schemes, and any variations / derivatives thereof can be implemented in other types of radio access technologies, networks, and network topologies, and can be implemented for other types of radio access technologies, networks, and network topologies, such as, but not limited to, Long-Term Evolution (LTE), LTE-Advanced, LTE-Advanced Pro, Internet of Things (IoT), Narrow Band Internet of Things (NB-IoT), Industrial Internet of Things (IIoT), Vehicle-to-Everything (V2X), and non-terrestrial network (NTN) communication. Therefore, the scope of this invention is not limited to the examples described herein. Attached Figure Description

[0011] The accompanying drawings are included to provide a further understanding of the invention, and these drawings are incorporated in and constitute a part of this invention. The drawings illustrate implementations of the invention and, together with the description, serve to explain the principles of the invention. It will be apparent that the drawings are not necessarily drawn to scale, as some components may be shown out of proportion to their actual dimensions in order to clearly illustrate the concepts of the invention.

[0012] Figure 1 This is a schematic diagram of an example network environment that can implement various proposed solutions according to the present invention.

[0013] Figure 2 This is a schematic diagram of an example scenario under the proposed solution according to the present invention.

[0014] Figure 3 This is a schematic diagram of an example scenario under the proposed solution according to the present invention.

[0015] Figure 4 This is a schematic diagram of an example scenario under the proposed solution according to the present invention.

[0016] Figure 5 This is a block diagram of an example system implemented according to the present invention.

[0017] Figure 6 This is a flowchart of an example process implemented according to the present invention. Detailed Implementation

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

[0019] Overview

[0020] Implementations of the present invention relate to various techniques, methods, schemes, and / or solutions related to dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications. According to the present invention, many possible solutions can be implemented separately or in combination. That is, although these possible solutions may be described separately below, two or more of these possible solutions may be implemented in one combination or another.

[0021] Figure 1An example network environment 100 is illustrated, which can implement various solutions and schemes according to the present invention. (Reference) Figure 1 Network environment 100 may include user equipment (UE) 110 that wirelessly communicates with wireless network 120 (e.g., a 5G NR mobile network and / or another type of network, such as an LTE network, LTE-Advance network, NB-IoT network, IoT network, IIoT network, and / or NTN). UE 110 may wirelessly communicate with wireless network 120 via base station or network node 125 (e.g., eNB, gNB, or transmit-receive point (TRP)). As described below, in network environment 100, UE 110 and wireless network 120 can implement various schemes related to dynamic and static cross-carrier PUCCH signaling and configuration in mobile communications.

[0022] Figure 2 An example scenario 200 for dynamic and static carrier selection for PUCCH transmission according to the scheme proposed in this invention is illustrated. In the example shown in scenario 200, a cell group may include multiple CCs (such as CC1, CC2, CC3, and CC4), each CC being configured with a corresponding TDD mode. For example, CC1 may have the following TDD mode: where 3 consecutive DL slots are followed by 1 UL slot (in... Figure 2 This is represented as "CC1, TDD 3:1"). Similarly, CC2 can have the following TDD mode: where 4 consecutive DL slots are followed by 1 UL slot (in... Figure 2 This is represented as "CC2, TDD 4:1" in Chinese. Similarly, CC3 can have the following TDD mode: where two consecutive DL slots are followed by one UL slot (in... Figure 2 This is represented as "CC3, TDD2:1" in Chinese. Furthermore, CC4 can have the following TDD mode: where three consecutive DL slots are followed by one UL slot (in...). Figure 2 (This is represented as "CC4, TDD 3:1"). Figure 2 As shown, UE 110 can receive multiple dynamic signaling messages (e.g., downlink control information (DCI)) from radio network 120 on multiple CCs, including CC1, CC2, CC3, and CC4. Furthermore, multiple DCIs received on multiple CCs can point to the same available UL timeslot (e.g., on CC3) for PUCCH transmission. Under the proposed scheme, as described below, several methods (static and dynamic) can exist regarding how to select the carrier for PUCCH transmission in scenario 200.

[0023] The first approach can be a static approach, and it has several options. In the first option, the carrier with the smallest carrier index can be selected. Therefore, the PUCCH payload can be located on a specific carrier, and this approach is efficient if that carrier has the most UL-friendly TDD mode. In the second option, the carrier in the PUCCH resource set with the earliest UL opportunity or PUCCH resource can be selected. However, a problem associated with this option is that resources in the PUCCH resource set can be aligned across some carrier boundaries. Another problem is that simultaneous HARQ acknowledgement (HARQ-ACK) codebooks (CBs) may select the same resource. In the third option, a new priority index can be defined (e.g., primary PUCCH carrier, then secondary PUCCH carrier, etc.). For example, if carrier #k is available in slot #n, carrier #k can be selected; otherwise, carrier #k+1 in slot #n can be selected, where k is the priority order of the PUCCH carriers.

[0024] The second approach can be a dynamic approach utilizing DCI. In the proposed scheme, support for PUCCH carrier handover can be based on dynamic indications and semi-static configurations in the DCI that schedules the PUCCH. Dynamic indications and / or semi-static configurations can be subject to individual UE capabilities. The semi-static PUCCH carrier handover configuration operation can be based on the PUCCH cell timing pattern of the applicable radio resource control (RRC) configuration for the PUCCH cell, which supports PUCCH carrier handover across cells with different parameter sets (numerology). Several options are possible under this approach. In the first option, the last DCI from the base station (e.g., network node 125) can be used to select the transmission carrier for a specific HARQ-ACK codebook. This allows for the possibility of PUCCH carrier overriding, but may impose constraints on implementation. In the second option, a PUCCH carrier selection deadline can be defined, and the last DCI before the deadline can be used to select the carrier. In the third option, the first DCI from the base station can be used to select the PUCCH carrier, and this carrier may remain unchanged thereafter. Since TDD mode is static, the carrier does not need to be changed during codebook construction (unless the base station also takes fast fading and UL channel quality into account). In the third option, because the first DCI is used to select the PUCCH carrier, there will be no PUCCH carrier index coverage.

[0025] Figure 3 Example scenario 300 of the proposed solution is illustrated. Figure 4 Example scenario 400 of the proposed scheme is illustrated. Specifically, scenario 300 shows an example of dynamic indication in the DCI of PUCCH scheduling, which has the advantages of flexibility, dynamic load balancing, and frequency-selective gain. In addition, scenario 400 shows an example of a semi-static PUCCH cell timing pattern, which has the advantage of lower overhead in dynamic transmission.

[0026] In 3GPP Release 16 (Rel-16), PUCCH configurations are defined per carrier, per bandwidth part (BWP), and per HARQ-ACK codebook. Since only one BWP is active per carrier, and there is only one PUCCH carrier in each PUCCH group, at most two PUCCH configurations in each PUCCH group can be active simultaneously, one for the high-priority (HP) codebook and the other for the low-priority (LP) codebook. Under the proposed scheme according to the present invention, there are multiple methods for PUCCH configuration. When multiple PUCCH carriers are defined in each PUCCH group (e.g., CC1, CC2, CC3, and CC4 in scenario 200 can be defined as a PUCCH group), a first method can be used, and multiple options can exist under this method. In the first option, PUCCH configurations can be defined per PUCCH carrier. This option may be relatively simple to implement, but some information may be redundant or conflicting (e.g., the k1 list for each DCI format). In the second option, the PUCCH configuration can be inherited from the primary PUCCH carrier. This option is also relatively simple to implement, but some information may be carrier-specific (e.g., PUCCH format, PUCCH resources, power control, etc.). In the third option, two levels of PUCCH configuration can be defined: per PUCCH group and per PUCCH carrier.

[0027] Under the proposed scheme, the second approach can have multiple options to address multiple PUCCH configurations within a PUCCH group. In the first option, a new parameter structure can be defined for each HARQ codebook to collect redundant and / or conflicting settings (e.g., a k1 list). This configuration can be applied to the codebook regardless of the PUCCH carrier. In the second option, a new PUCCH configuration-common parameter structure can be defined for each PUCCH group to collect any PUCCH configurations shared by the PUCCH group. In the third option, the PUCCH configuration for the PUCCH carrier can be used. Since the k1 list can differ, this option may require checking whether k1 was used in the codebook construction. In both the first and second options, information can be reconfigured for any new BWP selected.

[0028] It is worth noting that in events supporting dynamic indications in DCI based on scheduled PUCCH for PUCCH carrier handover, several options exist regarding PUCCH resource configuration. For example, the PUCCH resource configuration can be the same for all candidate cells (e.g., independent of subcarrier spacing (SCS)). Alternatively, the PUCCH resource configuration can be configured independently for each candidate cell. Alternatively, the PUCCH resource configuration can be performed per candidate cell using a combination of "per carrier" and "per PUCCH group" parameters. Alternatively, the PUCCH resource configuration can be configured based on the candidate cell's SCS (e.g., candidate cells with the same SCS can have the same PUCCH resource configuration).

[0029] Under the scheme proposed according to the present invention, there can be multiple methods for the HARQ-ACK codebook for each PUCCH group or PUCCH carrier. In a first method, with each PUCCH group having a PUCCH configuration, the HARQ-ACK codebook can be defined per PUCCH group. Therefore, there can be only one PUCCH at a time, and the carrier can be dynamic. In a second method, with each PUCCH carrier having a PUCCH configuration, the HARQ-ACK codebook can be defined per PUCCH carrier. Within the same PUCCH group, the number of HARQ-ACK codebooks can be as many as the number of PUCCH carriers. In cases of time overlap, the UE (e.g., UE 110) may have problems transmitting simultaneous PUCCHs, and therefore some limitations may be required.

[0030] It is worth noting that, regarding HARQ codebook segmentation, there exists a potential codebook for each slot or sub-slot on each CC. The DCI can select the potential codebooks for acknowledgment (ACK) and negative acknowledgment (NACK) by specifying the CC and the sub-slots on that CC. However, one codebook may be used in parallel with another codebook for another PUCCH transmission. Furthermore, a given CC may be overwritten by another CC. Under the proposed scheme according to the invention, regarding the issue of CC overwriting, a given CC (e.g., CC "A") cannot be overwritten, which is similar to having two separate PUCCH groups. Because CC "A" is travelable in the DCI, the mapping from another CC (e.g., CC "D") to CC "A" can be dynamic. Alternatively, CC "A" can be overwritten, which is similar to having a single PUCCH group. Therefore, a PUCCH can be overwritten by another scheduled PUCCH before the guard period.

[0031] According to the scheme proposed in this invention, the K1 field in the DCI carried in the physical downlink control channel (PDCCH) on CC "D" can be an index to a row in the K1 set, where that row in the K1 set is configured with the PUCCH configuration on CC "A", where "A" is different from "D". Regarding the definition of K1, one or more separate K1 sets can be defined for each CC. Alternatively, each K1 set can be interpreted in the UL sub-slot based on the partition and parameter set on the CC selected by "A" (the field in the DCI). Alternatively, a shared K1 set can be used. It is worth noting that the value of K1 can indicate the offset between the DL slot where data is scheduled on the physical downlink shared channel (PDSCH) and the UL slot where ACK (or NACK) feedback for the scheduled PDSCH data needs to be sent.

[0032] Under the proposed scheme according to the invention, regarding the DCI bit field used for K1 indication, the size of the K1 bit field in the DCI (format 1_2, format 1_1) can be determined based on the largest K1 list in the PUCCH group. Under the proposed scheme, when using a shorter list, the bit field can be padded with one or more zero bits.

[0033] Under the scheme proposed according to the present invention, several options are available for implementing simultaneous PUCCH transmission across carriers. In the first option, simultaneous PUCCH transmissions can be allowed within a PUCCH group. This option has no impact on UE implementation. Furthermore, this option uses a PUCCH CC index for differentiation. Two different codebooks can be constructed, one codebook per PUCCH carrier. In the second option, for time-overlapping slots and / or sub-slots, only one slot or sub-slot within a PUCCH group can carry a PUCCH. Cross-carrier overlapping PUCCH transmissions within the same PUCCH group can be disallowed. This may be relevant if a codebook construction is defined for each PUCCH group (rather than each carrier). In the third option, simultaneous PUCCH transmissions can be allowed within a PUCCH group under certain conditions. For example, one condition may include slot overlap but no PUCCH time resource overlap. Another condition may include two HP PUCCHs.

[0034] Under the scheme proposed according to the present invention, the DCI bit field, which serves as the PUCCH resource indicator, can be defined as three bits for DCI format 1_1, but for DCI format 1_2, the DCI bit field is configurable. In the first option, the "PUCCH resource indicator" bit field for all PUCCH carriers of DCI format 1_2 can be configured with the same number of bits. In the second option, when DCI format 1_2 is scheduling PUCCHs on each PUCCH carrier, a maximum number of bits can be used, and zero padding can be used to align the size of the bit field.

[0035] According to the proposed scheme, the PUCCH carrier can be associated with service priority. Under the proposed scheme, the PUCCH carrier can be semi-statically configured to transmit feedback for HP services. For example, for a carrier with a higher parameter set, the DL / UL handover frequency can be higher. Furthermore, carriers with more UL opportunities can be associated with higher service priorities. Additionally, the PUCCH carrier can be semi-statically configured to transmit feedback for LP services. Under the proposed scheme, the PUCCH carrier can be implicitly determined based on a priority field.

[0036] It is worth noting that carrier switching for PUCCH transmission may require additional processing, especially when the carrier is changed very dynamically (e.g., by the last DCI). Under the scheme proposed according to the invention, the UE processing time N1 can be relaxed for dynamic PUCCH. Alternatively, N1 can be replaced by N1+d, where d depends on the number of PUCCH carriers in each PUCCH group. For example, in an event where the last PDSCH is N1 from the PUCCH, N1 can be associated with N1+d.

[0037] Under the scheme proposed according to the present invention, in events where PUCCH transmission overlaps with the high-priority physical uplink shared channel (HP-PUSCH), dynamic PUCCH can be used as an alternative scheme to select different PUCCH carriers, thereby avoiding dropping or multiplexing in some scenarios. In other words, it can avoid intra-UE multiplexing with dynamic PUCCH.

[0038] It is worth noting that when the transmitted PUCCH only includes HARQ-ACK feedback, the selection of PUCCH resources can be accomplished by first selecting a resource set based on the UCI payload, and then using the PUCCH resource indicator (PRI) bit field in the DCI and the first control channel element (CCE) associated with the PDCCH carrying the DCI to select PUCCH resources within the PUCCH resource set. Under the scheme proposed according to the present invention, the PRI used for PUCCH resource selection can be determined based on the first DCI or the last DCI. For example, the first DCI (mapped to slot-subslot) in the HARQ-ACK codebook construction can be used. PRI coverage can be disallowed. Alternatively, the last DCI (mapped to slot / subslot) in the HARQ-ACK codebook construction can be used. PRI coverage can be allowed.

[0039] It is worth noting that DCI format 2_2 (e.g., TPC-PUCCH-RNTI) is typically used to provide transmit power control (TPC) commands for PUCCH. In millimeter-wave operation, the medium access control (MAC) control element (CE) (e.g., for PUCCH spatial relationship activation / deactivation) can signal to the UE (e.g., UE 110) to change the beam used for PUCCH transmission. Simultaneously with changing the beam, the UE can also change the set of power control parameters. Under the scheme proposed according to the present invention, several methods for TPC for cross-carrier dynamic PUCCH can exist. In a first method, several options for transmit power control for cross-carrier dynamic PUCCH can exist. In the first option, each cell carrying the PUCCH can have its own TPC configuration (e.g., PUCCH-PowerControl) and can have its own TPC loop. In the second option, each cell carrying a PUCCH can have two levels of configuration for TPC and / or TPC loop: Level 1 per PUCCH group and / or cell group, and Level 2 per cell. In this option, some parameters can be defined per cell, and other parameters can be defined per PUCCH / cell group. In the third option, a single TPC configuration and / or TPC loop can be used per PUCCH / cell group. Alternatively, a cell index can be considered to select parameters within this single TPC configuration.

[0040] In the proposed scheme, in the second method, for DCI format 2_2 carrying a TPC command, a new DCI bit field can be included in DCI format 2_2 to indicate the PUCCH carrier to which the TPC command is applied. Alternatively, the cell receiving DCI format 2_2 can be indicated or otherwise mapped to the PUCCH cell to which the TPC command is applied. A new radio network temporary identifier (RNTI) can be introduced to indicate which PUCCH carrier the TPC command transmitted on DCI format 2_2 applies to. In the third method, when the UE (e.g., UE 110) changes the PUCCH carrier, the UE can automatically select the set of power control parameters for the newly selected PUCCH carrier.

[0041] Indicative implementation

[0042] Figure 5An example communication system 500 with a communication device 510 and a network device 520 according to an implementation of the present invention is illustrated. Each of the communication device 510 and the network device 520 can perform various functions to implement the schemes, techniques, processes, and methods described in this invention relating to dynamic and static cross-carrier PUCCH signaling and configuration in mobile communications, including the scenarios / schemes described above and the processes described below.

[0043] The communication device 510 may be part of an electronic device, which may be a UE (User Equipment), such as a portable or mobile device, a wearable device, a wireless communication device, or a computing device. For example, the communication device 510 may be implemented as a smartphone, smartwatch, personal digital assistant, digital camera, or computing device such as a tablet computer, desktop computer, or laptop computer. The communication device 510 may also be part of a machine-type device, which may be an IoT, NB-IoT, IIoT, or NTN device, such as a non-mobile or fixed device, a home appliance, a wired communication device, or a computing device. For example, the communication device 510 may be implemented in a smart thermostat, a smart refrigerator, a smart door lock, a wireless speaker, or a home control center. Furthermore, the communication device 510 may be implemented as one or more integrated circuit (IC) chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, one or more reduced-instruction-set-computing (RISC) processors, or one or more complex-instruction-set-computing (CISC) processors. The communication device 510 may include... Figure 5 At least some of the components shown, such as processor 512. Communication device 510 may also include one or more other components (e.g., internal power supply, display device, and / or user interface device) unrelated to the proposed solution of this disclosure; therefore, for the sake of brevity, these components of communication device 510 are not listed in the [specific description of the components]. Figure 5 It is shown in the text, but not described in the following text.

[0044] Network device 520 may be part of an electronic device / site, which may be a network node such as a base station, small cell, router, gateway, or satellite. For example, network device 520 may be implemented in an eNodeB in LTE, in a gNB in ​​5G, NR, IoT, NB-IoT, IIoT, or in a satellite in an NTN network. Alternatively, network device 520 may be implemented as one or more IC chips, such as, but not limited to, one or more single-core processors, one or more multi-core processors, or one or more RISC or CISC processors. Network device 520 may include... Figure 5 At least some of the components shown, such as processor 522. Network device 520 may also include one or more other components unrelated to the proposed solution of this invention (e.g., internal power supply, display device, and / or user interface device); therefore, for the sake of brevity, these components of network device 520 are not listed in the [specific description of the components]. Figure 5 It is shown in the text, but not described in the following text.

[0045] In one aspect, each of processors 512 and 522 may be implemented as one or more single-core processors, one or more multi-core processors, one or more RISC processors, or one or more CISC processors. That is, even though the singular term "processor" is used herein to refer to processors 512 and 522, each of processors 512 and 522 according to the invention may include multiple processors in some implementations and a single processor in other implementations. In another aspect, each of processors 512 and 522 may be implemented as hardware (and optionally firmware) having electronic components including, for example, but not limited to, one or more transistors, one or more diodes, one or more capacitors, one or more resistors, one or more inductors, one or more memristors, and / or one or more varactor diodes, configured and arranged to achieve a specific purpose according to the invention. In other words, in at least some implementations, each of processors 512 and 522 is a dedicated machine specifically designed, arranged, and configured to perform specific tasks, including dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications according to various implementations of the invention.

[0046] In some implementations, the communication device 510 may further include a transceiver 516 coupled to the processor 512 and capable of wirelessly transmitting and receiving data. In some implementations, the communication device 510 may also include a memory 514 coupled to the processor 512 and accessible by the processor 512, and storing data therein. In some implementations, the network device 520 may further include a transceiver 526 coupled to the processor 522 and capable of wirelessly transmitting and receiving data. In some implementations, the network device 520 may also include a memory 524 coupled to the processor 522 and accessible by the processor 522, and storing data therein. Therefore, the communication device 510 and the network device 520 can wirelessly communicate with each other via transceiver 516 and transceiver 526, respectively.

[0047] Each of the communication device 510 and the network device 520 can be a communication entity capable of communicating with each other using various proposed solutions according to the present invention. To aid in better understanding, the following description of the operation, function, and capabilities of each of the communication device 510 and the network device 520 is provided in the context of a mobile communication environment in which the communication device 510 may be implemented in or as a communication device or UE (e.g., UE 110) of a communication network (e.g., wireless network 120), and the network device 520 may be implemented in or as a network node or base station (e.g., network node 125) of the communication network (e.g., wireless network 120). It is also noteworthy that although the example implementations described below are provided in the context of mobile communication, they may also be implemented in other types of networks.

[0048] In various proposed schemes related to dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications according to the present invention, wherein in network environment 100, communication device 510 is implemented in or as UE 110 and network device 520 is implemented in or as network node 125, the processor 512 of communication device 510 can select a CC from a plurality of CCs using a static or dynamic method. Furthermore, processor 512 can use the selected CC to perform PUCCH transmission to the network (e.g., network 120 via device 520 as network node 125) via transceiver 516.

[0049] In some implementations, each of the multiple CCs can be associated with a corresponding priority index. Therefore, when selecting a CC from the multiple CCs, processor 512 can select one CC for a time slot based on the priority order of the corresponding priority indices among the multiple CCs. In some implementations, processor 512 can perform certain operations when selecting one CC from the multiple CCs based on the priority order of the corresponding priority indices among the multiple CCs. For example, processor 512 can select a first CC with a first priority index from the multiple CCs. Optionally, in an event where the first CC is unavailable in the time slot, processor 512 can select a second CC with a second priority index from the multiple CCs. In this case, the value of the second priority index can differ from the value of the first priority index by 1 (e.g., increment by 1).

[0050] In some implementations, when selecting a CC from multiple CCs, processor 512 may select the CC based on dynamic signaling with DCI from the network. In some implementations, the dynamic signaling may include multiple DCI signals received from the network. In this case, when selecting a CC based on dynamic signaling from the network, processor 512 may perform one of the following: (a) selecting a CC from multiple CCs based on the first received DCI signal among the multiple DCI signals received from the network; (b) selecting a CC from multiple CCs based on the last received DCI signal among the multiple DCI signals received from the network; or (c) selecting a CC from multiple CCs based on the last DCI signal among the multiple DCI signals before the deadline.

[0051] In some implementations, the corresponding PUCCH configuration can be configured for each of the multiple BWPs in the working bandwidth, per PUCCH carrier.

[0052] In some implementations, the corresponding HARQ codebook can be defined for each PUCCH carrier in a plurality of PUCCH carriers or for each PUCCH group that includes a plurality of CCs.

[0053] In some implementations, one or more separate K1 sets can be defined for each of the multiple PUCCH carriers. In some implementations, for each of the multiple PUCCH carriers, each of the one or more separate K1 sets can be interpreted in the UL sub-slot based on the partition and parameter set on that PUCCH carrier.

[0054] In some implementations, processor 512 may perform certain operations during PUCCH transmission. For example, processor 512 may receive DCI from the network. Additionally, processor 512 may determine the size of the k1-bit field in the DCI based on the largest of multiple lists within a PUCCH group that includes multiple CCs.

[0055] In some implementations, processor 512 may perform certain operations during PUCCH transmission. For example, processor 512 may receive DCI from the network. Additionally, processor 512 may fill the k1-bit field in the DCI during events where the shorter of the multiple lists in a PUCCH group comprising multiple CCs is used.

[0056] In some implementations, when performing PUCCH transmission, processor 512 can perform PUCCH transmission in the same PUCCH group that includes multiple CCs without PUCCH slots that overlap in time across carriers.

[0057] In some implementations, processor 512 may perform certain operations during PUCCH transmission. For example, processor 512 may receive DCI signals from the network. Furthermore, processor 512 may align the size of the PRI bit field in events using DCI format 1_2 within the DCI signal by using a maximum number of bits with zero padding.

[0058] In some implementations, processor 512 may perform certain operations during PUCCH transmission. For example, processor 512 may switch to a different CC among multiple CCs as the PUCCH carrier. Additionally, processor 512 may relax the processing time in dynamic PUCCH selection to produce a relaxed processing time that is longer than the original processing time without a relaxed delta time. In some implementations, the delta time may depend on the number of PUCCH carriers in each PUCCH group.

[0059] In some implementations, when selecting a CC from multiple CCs, the processor 512 may perform certain operations. For example, the processor 512 may determine the PRI based on either: (a) the first DCI signal in the HARQ-ACK configuration; or (b) the last DCI signal in the HARQ-ACK configuration. Furthermore, the processor 512 may use the PRI to select a CC from multiple CCs.

[0060] In some implementations, each cell carrying a PUCCH may have a corresponding TPC configuration. Alternatively, each cell carrying a PUCCH may have a corresponding TPC configuration and a corresponding TPC loop.

[0061] In some implementations, processor 512 may perform certain operations during PUCCH transmission. For example, processor 512 may receive DCI format 2_2 from the network, where DCI format 2_2 includes a TPC command and a DCI bit field indicating the PUCCH carrier to which the TPC command is applied. Furthermore, processor 512 may apply the TPC command on one of a plurality of CCs selected as the PUCCH carrier.

[0062] In some implementations, processor 512 can perform additional operations during PUCCH transmission. For example, processor 512 can switch to another CC among a plurality of CCs as the new PUCCH carrier. Furthermore, processor 512 can select a set of power control parameters corresponding to the new PUCCH carrier. Additionally, processor 512 can apply the set of power control parameters to the new PUCCH carrier.

[0063] Indicative process

[0064] Figure 6 An example process 600 according to an implementation of the invention is illustrated. Process 600 may be an example implementation of part or all of the above-described schemes concerning dynamic and static cross-carrier PUCCH transmission and configuration in mobile communications according to the invention. Process 600 may represent aspects of the implementation of features of communication device 510 and network device 520. Process 600 may include one or more operations, actions, or functions as illustrated in one or more of blocks 610 and 612. Although illustrated as discrete blocks, the individual blocks of process 600 may be divided into additional blocks, combined into fewer blocks, or eliminated according to the desired implementation. Furthermore, the blocks of process 600 may be arranged according to Figure 6 The blocks of process 600 may be executed in the order shown, or alternatively, they may be executed in a different order. Process 600 may be implemented by communication device 510 or any suitable UE or machine-type device and by network device 520 or any suitable network node or base station. For illustrative purposes only and not as a limitation, process 600 is described in the context of communication device 510 implemented in or as UE 110 and network device 520 implemented in or as network node 125. Process 600 may begin at block 610.

[0065] At 610, process 600 may include: a processor 512 of a communication device 510 (implemented in or as a UE 110) selecting a CC from a plurality of CCs using a static or dynamic method. Process 600 may proceed from 610 to 620.

[0066] At 620, process 600 may include: processor 512 using a selected CC to perform a PUCCH transmission to a network (e.g., network 120 via device 520 as network node 125) via transceiver 516.

[0067] In some implementations, each of the multiple CCs can be associated with a corresponding priority index. Therefore, when selecting a CC from the multiple CCs, process 600 may include: processor 512 selecting one CC from the multiple CCs for a time slot according to the priority order of the corresponding priority indices among the multiple CCs. In some implementations, when selecting one CC from the multiple CCs according to the priority order of the corresponding priority indices among the multiple CCs, process 600 may include: processor 512 performing some operation. For example, process 600 may include: processor 512 selecting a first CC from the multiple CCs with a first priority index. Optionally, process 600 may also include: in an event that the first CC is unavailable in the time slot, processor 512 selecting a second CC from the multiple CCs with a second priority index. In this case, the value of the second priority index may differ from the value of the first priority index by 1 (e.g., increment by 1).

[0068] In some implementations, when selecting a CC from multiple CCs, process 600 may include: processor 512 selecting a CC based on dynamic signaling with a DCI from the network. In some implementations, the dynamic signaling may include multiple DCI signals received from the network. In this case, when selecting a CC based on dynamic signaling from the network, process 600 may include processor 512 performing one of the following: (a) selecting a CC from multiple CCs based on the first received DCI signal among the multiple DCI signals received from the network; (b) selecting a CC from multiple CCs based on the last received DCI signal among the multiple DCI signals received from the network; or (c) selecting a CC from multiple CCs based on the last DCI signal among the multiple DCI signals before a deadline.

[0069] In some implementations, the corresponding PUCCH configuration can be configured for each of the multiple BWPs in the working bandwidth, per PUCCH carrier.

[0070] In some implementations, the corresponding HARQ codebook can be defined for each PUCCH carrier in a plurality of PUCCH carriers or for each PUCCH group that includes a plurality of CCs.

[0071] In some implementations, one or more separate K1 sets can be defined for each of the multiple PUCCH carriers. In some implementations, for each of the multiple PUCCH carriers, each of the one or more separate K1 sets can be interpreted in the UL sub-slot based on the partition and parameter set on that PUCCH carrier.

[0072] In some implementations, during PUCCH transmission, process 600 may include processor 512 performing certain operations. For example, process 600 may include: processor 512 receiving DCI from the network. Additionally, process 600 may include: processor 512 determining the size of the k1-bit field in the DCI based on the largest of multiple lists in a PUCCH group that includes multiple CCs.

[0073] In some implementations, during a PUCCH transmission, process 600 may include: processor 512 performing some operations. For example, process 600 may include: processor 512 receiving a DCI from the network. Additionally, process 600 may include: processor 512 filling the k1 bit field in the DCI in an event using the shorter of a list of multiple lists in a PUCCH group that includes multiple CCs.

[0074] In some implementations, when performing a PUCCH transmission, process 600 may include: processor 512 performing a PUCCH transmission in the same PUCCH group that includes multiple CCs without PUCCH slots that overlap in time across carriers.

[0075] In some implementations, during a PUCCH transmission, process 600 may include: processor 512 performing some operations. For example, process 600 may include: processor 512 receiving a DCI signal from the network. Furthermore, process 600 may include: processor 512 aligning the size of the PRI bit field in an event where the DCI signal uses DCI format 1_2, by using a maximum number of bits with zero padding.

[0076] In some implementations, during PUCCH transmission, process 600 may include: processor 512 performing some operations. For example, process 600 may include: processor 512 switching to a different CC among a plurality of CCs as the PUCCH carrier. Additionally, process 600 may include: processor 512 relaxing the processing time in dynamic PUCCH selection to produce a relaxed processing time that is longer than the original processing time without relaxation of the increment time. In some implementations, the increment time may depend on the number of PUCCH carriers in each PUCCH group.

[0077] In some implementations, when selecting a CC from multiple CCs, process 600 may include: processor 512 performing some operations. For example, process 600 may include: processor 512 determining PRI based on either: (a) the first DCI signal in the HARQ-ACK construct; or (b) the last DCI signal in the HARQ-ACK construct. Furthermore, process 600 may include: processor 512 using PRI to select a CC from multiple CCs.

[0078] In some implementations, each cell carrying a PUCCH may have a corresponding TPC configuration. Alternatively, each cell carrying a PUCCH may have a corresponding TPC configuration and a corresponding TPC loop.

[0079] In some implementations, during PUCCH transmission, process 600 may include: processor 512 performing some operations. For example, process 600 may include: processor 512 receiving DCI format 2_2 from the network, wherein DCI format 2_2 includes a TPC command and a DCI bit field indicating the PUCCH carrier to which the TPC command is applied. Furthermore, process 600 may include: processor 512 applying the TPC command on one of a plurality of CCs selected as the PUCCH carrier.

[0080] In some implementations, during PUCCH transmission, process 600 may include: processor 512 performing additional operations. For example, process 600 may include: processor 512 switching to another CC among a plurality of CCs as a new PUCCH carrier. Furthermore, process 600 may include: processor 512 selecting a set of power control parameters corresponding to the new PUCCH carrier. Additionally, process 600 may include: processor 512 applying the set of power control parameters to the new PUCCH carrier.

[0081] Additional Notes

[0082] The subject matter described in this invention sometimes illustrates different components contained within or connected to other components. It should be understood that the architectures depicted are merely exemplary, and in practice, many other architectures can be implemented to achieve the same functionality. Conceptually, any arrangement of components for achieving the same functionality is effectively “associated” to achieve the desired function. Thus, any two components combined herein to achieve a particular function can be considered “associated” with each other to achieve the desired function, regardless of the architecture or intermediate components. Similarly, any two such associated components can also be considered “operably connected” or “operably coupled” to each other to achieve the desired function, and any two components that can be suchly associated can also be considered “operably coupled” to each other to achieve the desired function. Specific examples of operably coupled components include, but are not limited to, components that can physically cooperate and / or physically interact and / or components that can wirelessly interact and / or components that can logically interact and / or components that can logically interact.

[0083] Furthermore, regarding any plural and / or singular terms used in this context, those skilled in the art can translate them from plural to singular and / or from singular to plural as appropriate, depending on the context and / or application. For clarity, various singular / plural substitutions can be explicitly described in this invention.

[0084] Furthermore, those skilled in the art will understand that, generally, the terminology used as in this invention, and especially in the appended claims (e.g., the body of the appended claims), is intended to be “open-ended” terms (e.g., the term “comprising” should be interpreted as “including but not limited to,” the term “having” should be interpreted as “having at least,” the term “including” should be interpreted as “including but not limited to,” etc.). Those skilled in the art will also understand that if there is an intent to state a particular number of referenced claims, such intent will be explicitly stated in the claims, and without such a statement, such intent does not exist. For example, to aid understanding, the appended claims may contain the use of introductory phrases “at least one” and “one or more” to introduce the claim statements. However, the use of such phrases should not be construed as implying that a claim statement introduced by the indefinite article “a” or “an” will limit any particular claim containing such an introductory claim statement to containing only one implementation of such a statement, even if the same claim includes the introductory phrases “one or more” or “at least one” and indefinite articles such as “a” or “an” (e.g., “a” or “an” should be interpreted as meaning “at least one” or “one or more”); the same applies to the use of definite articles for referencing claim statements. Furthermore, even when a specific number of claims are explicitly stated, those skilled in the art should recognize that such a statement should be interpreted as meaning at least the number stated (e.g., a bare statement of "two statements" means at least two statements, or two or more statements, in the absence of other modifiers). Moreover, in instances where the convention of "at least one of A, B, and C" is used, this syntactic structure is generally intended to be understood by those skilled in the art to be meaning-wise (e.g., "a system having at least one of A, B, and C" should include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). In instances where the convention of "at least one of A, B, or C" is used, this syntactic structure is generally intended to be understood by those skilled in the art to be meaning-wise (e.g., "a system having at least one of A, B, or C" should include, but is not limited to, systems having a single A, a single B, a single C, A and B together, A and C together, B and C together, and / or A, B, and C together, etc.). Those skilled in the art should also understand that, in practice, any transition words and / or phrases presenting two or more alternative terms (whether in the specification, claims, or drawings) should be understood to imply the possibility of including one, any, or both of these terms. For example, the phrase "A or B" should be understood to include the possibility of including "A" or "B" or "A and B".

[0085] Based on the foregoing, it will be clear that various implementations of the invention have been described for illustrative purposes, and various modifications can be made without departing from the scope and spirit of the invention. Therefore, the various implementations disclosed herein are not intended to be limiting, and the true scope and spirit are indicated by the appended claims.

Claims

1. A method for mobile communication, the method comprising: The processor of the device implemented in the user equipment selects a component carrier from multiple component carriers; as well as The processor uses the selected component carriers to perform physical uplink control channel transmissions to the network. The use of the component carriers selected from the plurality of component carriers to perform the physical uplink control channel transmission includes: Receive downlink control information from the network; and The size of the k1 bit field in the downlink control information is determined based on the largest of multiple k1 lists in the physical uplink control channel group, wherein the physical uplink control channel group includes the multiple component carriers, and the value of k1 indicates the offset between the downlink time slot for scheduling data on the physical downlink shared channel and the uplink time slot for sending acknowledgment or negative acknowledgment feedback for the scheduled physical downlink shared channel data.

2. The method for mobile communication according to claim 1, wherein, Each of the plurality of component carriers is associated with a corresponding priority index, and wherein selecting the component carrier from the plurality of component carriers includes: selecting one of the plurality of component carriers for a time slot according to the priority order of the corresponding priority indexes of the plurality of component carriers.

3. The method for mobile communication according to claim 2, wherein, Selecting one component carrier from the plurality of component carriers according to the priority order of the corresponding priority indexes of the plurality of component carriers includes: Select the first component carrier with a first priority index from the plurality of component carriers; and In the event that the first component carrier is unavailable in the time slot, a second component carrier with a second priority index is selected from the plurality of component carriers. The value of the second priority index differs from the value of the first priority index by 1.

4. The method for mobile communication according to claim 1, wherein, Selecting the component carrier from the plurality of component carriers includes: The component carrier is selected based on dynamic signaling from the network that carries the downlink control information.

5. The method for mobile communication according to claim 4, wherein, The dynamic signaling includes multiple downlink control information signals received from the network, and wherein selecting the component carrier based on the dynamic signaling from the network includes: The component carrier is selected from the plurality of component carriers based on the first received downlink control information signal among the plurality of downlink control information signals received from the network.

6. The method for mobile communication according to claim 4, wherein, The dynamic signaling includes multiple downlink control information signals received from the network, and wherein selecting the component carrier based on the dynamic signaling from the network includes: The component carrier is selected from the plurality of component carriers based on the last received downlink control information signal among the plurality of downlink control information signals received from the network.

7. The method for mobile communication according to claim 4, wherein, The dynamic signaling includes multiple downlink control information signals received from the network, and wherein selecting the component carrier based on the dynamic signaling from the network includes: The component carrier is selected from the plurality of component carriers based on the last downlink control information signal before the deadline among the plurality of downlink control information signals.

8. The method for mobile communication according to claim 1, wherein, For each bandwidth portion, the corresponding physical uplink control channel configuration is configured for each physical uplink control channel carrier.

9. The method for mobile communication according to claim 1, wherein, Define a corresponding hybrid automatic repeat request codebook for each physical uplink control channel carrier among multiple physical uplink control channel carriers, or A corresponding hybrid automatic repeat request codebook is defined for each physical uplink control channel group, wherein the physical uplink control channel group includes the plurality of component carriers.

10. The method for mobile communication according to claim 1, wherein, One or more separate K1 sets are defined for each of the plurality of physical uplink control channel carriers, and each of the one or more separate K1 sets is interpreted in the uplink sub-slot according to the partition and parameter set on that physical uplink control channel carrier for each of the plurality of physical uplink control channel carriers.

11. The method for mobile communication according to claim 1, wherein, The execution of the physical uplink control channel transmission includes: In the event of using the shorter K1 list among the plurality of lists in the physical uplink control channel group, the k1 bit field in the downlink control information is filled, wherein the physical uplink control channel group includes the plurality of component carriers.

12. The method for mobile communication according to claim 1, wherein, The execution of the physical uplink control channel transmission includes: The physical uplink control channel transmission is performed when there are no overlapping physical uplink control channel slots across carriers in the same physical uplink control channel group that includes the multiple component carriers.

13. The method for mobile communication according to claim 1, wherein, The execution of the physical uplink control channel transmission includes: Receive downlink control information signals from the network; In events where downlink control information format 1_2 is used in the downlink control information signal, the size of the physical uplink control channel resource indicator bit field is aligned by using a maximum number of bits with zero padding.

14. The method for mobile communication according to claim 1, wherein, The execution of the physical uplink control channel transmission includes: Switching to different component carriers among the plurality of component carriers as physical uplink control channel carriers; and The processing time in dynamic physical uplink control channel selection is relaxed to produce a relaxed processing time, which is longer than the original processing time without relaxation of the increment time. The incremental time depends on the number of physical uplink control channel carriers in each physical uplink control channel group.

15. The method for mobile communication according to claim 1, wherein, Selecting the component carrier from the plurality of component carriers includes: The Physical Uplink Control Channel Resource Indicator (PHCI) is determined based on: the first downlink control information signal in the Hybrid Automatic Repeat Request Acknowledgment (HARQ) construct; or the last downlink control information signal in the HARQ construct; and The resource indicator is used to select the component carrier from the plurality of component carriers.

16. The method for mobile communication according to claim 1, wherein, Each physical uplink control channel carrier has a corresponding transmit power control configuration.

17. The method for mobile communication according to claim 1, wherein, Each physical uplink control channel carrier has a corresponding transmit power control configuration and a corresponding transmit power control loop.

18. The method for mobile communication according to claim 1, wherein, The execution of the physical uplink control channel transmission includes: The network receives downlink control information format 2_2, which includes a transmit power control command and a downlink control information bit field. The downlink control information bit field indicates the physical uplink control channel carrier on which the transmit power control command is applied. The transmit power control command is applied on one of the component carriers selected as the physical uplink control channel carrier among the plurality of component carriers.

19. The method for mobile communication according to claim 18, wherein, The execution of the physical uplink control channel transmission also includes: Switch to another component carrier among the plurality of component carriers as the new physical uplink control channel carrier; Select the set of power control parameters corresponding to the new physical uplink control channel carrier; and The power control parameter set is applied to the new physical uplink control channel carrier.

20. An apparatus for mobile communication, comprising: A processor, which, when executing program instructions stored in a memory, performs the method for mobile communication as described in any one of claims 1-19.

21. A memory storing program instructions that, when executed by a processor, cause the processor to perform the method for mobile communication as described in any one of claims 1-19.

Images