Communication system

Abstract

A communication system is disclosed in which a user equipment (UE) receives data associated with Ultra Reliable and Low Latency Communication (URLLC) services and data associated with Enhanced Mobile Broadband (eMBB) services. The UE generates a first Hybrid Automatic Repeat Request (HARQ) codebook for the URLLC services, i.e., a first HARQ codebook, and a second HARQ codebook for the eMBB services. The first HARQ codebook is bundled into a single bit and appended to the end of the second HARQ codebook to form a multiplexed HARQ codebook. The UE then transmits the multiplexed HARQ codebook to the access network node.

Description

Technical Field

[0001] This invention relates to wireless communication systems and apparatuses operating according to 3GPP standards or their equivalents or derivatives. This disclosure particularly, but not exclusively, relates to improvements in the transmission of Hybrid Automatic Repeat Request Acknowledgment (HARQ-ACK) feedback in so-called “5G” (or “next-generation”) systems. Background Technology

[0002] The latest development in 3GPP standards is the so-called "5G" or "New Radio" (NR) standards, which refer to evolving communication technologies expected to support a wide range of applications and services, such as Machine Type Communication (MTC), Internet of Things (IoT) / Industrial Internet of Things (IIoT) communication, vehicle communication and autonomous vehicles, high-resolution video streaming, smart city services, and / or the like. 3GPP intends to support 5G through the so-called 3GPP Next Generation Radio Access Network (RAN) and 3GPP Next Generation Core (NGC) networks. Various details of 5G networks are described in, for example, the Next Generation Mobile Network (NGMN) Alliance's "NGMN 5G White Paper" V1.0, which is available at https: / / www.ngmn.org / 5g-white-paper.html.

[0003] End-user communication devices are typically referred to as user equipment (UE), which can be human-operated or include automated (MTC / IoT) devices. While base stations for 5G / NR communication systems are generally referred to as New Radio base stations (“NR-BS”) or “gNB”, it will be understood that they can be referred to using the term “eNB” (or 5G / NR eNB), which is more typically associated with Long Term Evolution (LTE) base stations (also commonly referred to as “4G” base stations). 3GPP technical specifications (TS) 38.300 V16.3.0 and TS 37.340 V16.3.0 define the following nodes, etc.:

[0004] gNB: A node that provides NR user plane and control plane protocol terminals to UEs and connects to the 5G core network (5GC) via the NG interface.

[0005] ng-eNB: A node that provides the UE with Evolved Universal Terrestrial Radio Access (E-UTRA) user plane and control plane protocol terminals and connects to the 5GC via the NG interface.

[0006] En-gNB: A node that provides NR user plane and control plane protocol terminals to the UE and acts as an auxiliary node in E-UTRA-NR dual connectivity (EN-DC).

[0007] NG-RAN nodes: gNB or ng-eNB.

[0008] 3GPP also defines the so-called "Xn" interface as the network interface between adjacent NG-RAN nodes.

[0009] The Physical Uplink Control Channel (PUCCH) carries a set of information known as Uplink Control Information (UCI). The format of the PUCCH depends on the type of information carried by the UCI. The PUCCH format to be used is determined by the number of bits of information to be carried and the number of symbols assigned. The UCI used in NR (5G) includes one or more of the following: Channel State Information (CSI); ACK / NAK; and Scheduling Request (SR). This is generally the same as in LTE (4G).

[0010] Next-generation mobile networks support diverse service requirements, which have been categorized by the International Telecommunication Union (ITU) into three classes: enhanced mobile broadband (eMBB); ultra-reliable and low-latency communications (URLLC); and massive machine-type communications (mMTC). eMBB aims to provide enhanced support for traditional mobile broadband, focusing on services requiring high bandwidth and guaranteed bandwidth, such as high-definition (HD) video, virtual reality (VR), and augmented reality (AR). URLLC addresses the requirements of critical applications such as autonomous driving and factory automation, demanding guaranteed access for very short periods. mMTC needs to support a large number of connected devices, such as smart metering and environmental monitoring, but typically tolerates some access latency. It will be understood that some of these applications may have relatively relaxed Quality of Service / Quality of Experience (QoS / QoE) requirements, while others may have relatively stringent QoS / QoE requirements (e.g., high bandwidth and / or low latency).

[0011] In version 16, when uplink transmissions of different priorities overlap, the problem is addressed by dropping lower-priority transmissions. This method prioritizes URLLC services (which have relatively high priority) and associated HARQ feedback over other types of transmissions, but it is inefficient when eMBB services are also present. For example, when HARQ feedback for downlink eMBB data is dropped due to the priority of URLLC feedback (relative to eMBB feedback), system efficiency is affected because eMBB data for which feedback (acknowledgment) has not been received needs to be retransmitted.

[0012] In Release 17, enhancements to Industrial Internet of Things (IIoT) and URLLC aim to specify the required multiplexing behavior between HARQ-ACK / SR / CSI and the Physical Uplink Shared Channel (PUSCH) for different service types with varying priorities. This behavior applies to UCI regardless of whether it is transmitted on PUCCH or PUSCH. At a recent 3GPP meeting (RAN1#102), it was agreed that high-priority HARQ-ACK and low-priority HARQ-ACK would be multiplexed into the PUCCH in Release 17, although further details are not yet known. The key principle is to guarantee the latency and reliability of URLLC UCI transmission.

[0013] Several recommendations exist for reducing the eMBB HARQ-ACK codebook size to minimize the impact on high-priority HARQ-ACKs (e.g., URLLC). For example, this size reduction can be achieved by compressing the eMBB HARQ-ACK codebook using transport block (TB)-based feedback, or by dropping as many component carriers as needed to adapt the feedback to the UCI payload size. Alternatively, the maximum allowed code rate can be configured independently for eMBB and URLLC HARQ-ACKs, and the final payload can be adjusted by suppressing eMBB HARQ-ACKs or amplifying URLLC HARQ-ACKs. Spatial bundling can be used to generate low-priority HARQ codebooks regardless of the associated RRC configuration. Summary of the Invention

[0014] However, none of the existing technologies have been accepted by 3GPP. Therefore, the present invention seeks to provide methods and associated devices for resolving or at least mitigating some of the aforementioned problems related to the priority of URLLC services and associated HARQ feedback over other types of transmissions.

[0015] Although the invention will be described in detail in the context of a 3GPP system (5G network) for the efficiency of understanding by those skilled in the art, the principles of the invention can also be applied to other systems.

[0016] In one example aspect, the present invention provides a method performed by a user equipment (UE), the method comprising: receiving from an access network node a signal for carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; generating a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service, and generating a second HARQ codebook for the data associated with the second service; generating HARQ information for the URLLC service based on the first HARQ codebook, and multiplexing the HARQ information for the URLLC service with the second HARQ codebook to derive a multiplexed HARQ codebook; and transmitting the multiplexed HARQ codebook to the access network node using at least one communication resource associated with the URLLC.

[0017] In one example aspect, the present invention provides a method performed by a user equipment (UE), the method comprising: receiving from an access network node a signal for carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; generating a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service, and generating a second HARQ codebook for the data associated with the second service; binding one of the first and second HARQ codebooks to a single bit according to at least one predetermined rule; multiplexing the bound bit with the other of the first and second HARQ codebooks to derive a multiplexed HARQ codebook; and transmitting the multiplexed HARQ codebook to the access network node.

[0018] In one example aspect, the present invention provides a method performed by an access network node, the method comprising: transmitting to a user equipment (UE) a signal for carrying data associated with a first ultra-reliable and low-latency communication service (URLLC) and data associated with a second service; and receiving from the UE a multiplexed hybrid automatic repeat request codebook (HARQ codebook) using at least one communication resource associated with the URLLC, wherein the multiplexed HARQ codebook is based on HARQ information of the URLLC service, the HARQ information of the URLLC service being generated based on a first HARQ codebook for the data associated with the URLLC service and multiplexed with a second HARQ codebook for the data associated with the second service.

[0019] In one example aspect, the present invention provides a method performed by an access network node, the method comprising: transmitting to a user equipment (UE) a signal for carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and receiving from the UE a multiplexed hybrid automatic repeat request codebook (HARQ codebook), wherein the multiplexed HARQ codebook includes: i) a first HARQ codebook for data associated with one of the URLLC service and the second service; and ii) binding bits based on a second HARQ codebook for data associated with the other of the URLLC service and the second service.

[0020] In one example aspect, the present invention provides a user equipment (UE) comprising: means for receiving from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC) and data associated with a second service; means for generating a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service and for generating a second HARQ codebook for the data associated with the second service; means for generating HARQ information for the URLLC service based on the first HARQ codebook and for multiplexing the HARQ information for the URLLC service with the second HARQ codebook to derive a multiplexed HARQ codebook; and means for transmitting the multiplexed HARQ codebook to the access network node using at least one communication resource associated with the URLLC.

[0021] In one example aspect, the present invention provides a user equipment (UE) comprising: means for receiving from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; means for generating a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service and for generating a second HARQ codebook for the data associated with the second service; means for binding one of the first HARQ codebook and the second HARQ codebook to a single bit according to at least one predetermined rule; means for multiplexing the bound bit with the other of the first HARQ codebook and the second HARQ codebook to derive a multiplexed HARQ codebook; and means for transmitting the multiplexed HARQ codebook to the access network node.

[0022] In one example aspect, the present invention provides an access network node comprising: means for transmitting to a user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC) and data associated with a second service; and means for receiving from the UE a multiplexed hybrid automatic repeat request codebook (HARQ codebook) using at least one communication resource associated with the URLLC, wherein the multiplexed HARQ codebook is based on HARQ information of the URLLC service, the HARQ information of the URLLC service being generated based on a first HARQ codebook for the data associated with the URLLC service and multiplexed with a second HARQ codebook for the data associated with the second service.

[0023] In one example aspect, the present invention provides an access network node comprising: means for transmitting to a user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and means for receiving from the UE a multiplexed hybrid automatic repeat request codebook (HARQ codebook), wherein the multiplexed HARQ codebook includes: i) a first HARQ codebook for data associated with one of the URLLC service and the second service; and ii) binding bits based on a second HARQ codebook for data associated with the other of the URLLC service and the second service.

[0024] In another example aspect, the present invention provides a user equipment (UE) comprising: a controller and a transceiver, wherein the transceiver is configured to receive from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC) and data associated with a second service; the controller is configured to generate a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service and to generate a second HARQ codebook for the data associated with the second service; the controller is configured to generate HARQ information for the URLLC service based on the first HARQ codebook and to multiplex the HARQ information for the URLLC service with the second HARQ codebook to derive a multiplexed HARQ codebook; and the transceiver is configured to transmit the multiplexed HARQ codebook to the access network node using at least one communication resource associated with the URLLC.

[0025] In another example aspect, the present invention provides a user equipment (UE) comprising: a controller and a transceiver, wherein the transceiver is configured to receive from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; the controller is configured to generate a first hybrid automatic repeat request codebook (HARQ codebook) for the data associated with the URLLC service and a second HARQ codebook for the data associated with the second service; the controller is configured to bind one of the first HARQ codebook and the second HARQ codebook to a single bit according to at least one predetermined rule; the controller is configured to multiplex the bound bit with the other of the first HARQ codebook and the second HARQ codebook to derive a multiplexed HARQ codebook; and the transceiver is configured to transmit the multiplexed HARQ codebook to the access network node.

[0026] In another example aspect, the present invention provides an access network node comprising: a controller and a transceiver, wherein the transceiver is configured to: transmit to a user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC) and data associated with a second service; and to receive from the UE a multiplexed hybrid automatic repeat request codebook (HARQ codebook) using at least one communication resource associated with the URLLC, wherein the multiplexed HARQ codebook is based on HARQ information of the URLLC service, the HARQ information of the URLLC service being generated based on a first HARQ codebook for the data associated with the URLLC service and multiplexed with a second HARQ codebook for the data associated with the second service.

[0027] In another example aspect, the present invention provides an access network node comprising: a controller and a transceiver, wherein the transceiver is configured to: transmit to a user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and receive from the UE a multiplexed hybrid automatic repeat request codebook, i.e., a multiplexed HARQ codebook, wherein the multiplexed HARQ codebook includes: i) a first HARQ codebook for data associated with one of the URLLC service and the second service; and ii) binding bits based on a second HARQ codebook for data associated with the other of the URLLC service and the second service.

[0028] The exemplary aspects of the invention extend to corresponding systems, devices, and computer program products, such as computer-readable storage media storing instructions operable to program a programmable processor to perform methods as set forth above or described in the exemplary aspects and possibilities set forth in the claims and / or to program a suitably adapted computer to provide the apparatus set forth in any of the claims.

[0029] Various features disclosed in this specification (the term includes the claims) and / or shown in the drawings may be incorporated into the invention independently of any other disclosed and / or shown features (or in combination with any other disclosed and / or shown features). In particular, but not limitingly, features of any claim dependent on a particular independent claim may be introduced into that independent claim in any combination or individually. Attached Figure Description

[0030] Example embodiments of the invention will now be described by way of example with reference to the accompanying drawings, in which:

[0031] Figure 1 This illustration shows an example embodiment of the invention that can be applied to a mobile (cellular or wireless) telecommunications system;

[0032] Figure 2 It is used to form Figure 1 A schematic block diagram of a mobile device that is part of the system shown;

[0033] Figure 3 It is used to form Figure 1 A schematic block diagram of an access network node (e.g., a base station) that is part of the system shown;

[0034] Figure 4 It is used to form Figure 1 A schematic block diagram of a core network node, representing a portion of the system; and

[0035] Figure 5 This is a flowchart illustrating some exemplary ways in which HARQ-ACK multiplexing can be performed according to an example embodiment of the present invention.

[0036] Figure 6 This is a flowchart illustrating some exemplary ways in which HARQ-ACK multiplexing can be performed according to an example embodiment of the present invention. Detailed Implementation

[0037] Overview

[0038] Under the 3GPP standard, a NodeB (or "eNB" in LTE, "gNB" in 5G) is a base station through which a communication device (User Equipment or "UE") connects to the core network and communicates with other communication devices or remote servers. Communication devices can be, for example, mobile communication devices such as mobile phones, smartphones, smartwatches, personal digital assistants, laptops / tablets, web browsers, e-book readers, and / or the like. Such mobile (or even generally fixed) devices are typically operated by the user (and therefore are often collectively referred to as User Equipment "UE"), although IoT devices and similar MTC devices can also be connected to the network. For simplicity, this application will use the term "base station" to refer to any such base station, and the terms "mobile device" or "UE" to refer to any such communication device.

[0039] Figure 1 The illustration shows an example embodiment of the invention that can be applied to a mobile (cellular or wireless) telecommunications system 1.

[0040] In system 1, users of mobile device 3 (UE) can communicate with each other and with other users via corresponding base stations 5 and core network 7 using appropriate 3GPP radio access technologies (RAT) (e.g., E-UTRA and / or 5G RAT). It will be understood that multiple base stations 5 form a (radio)access network or (R)AN. As those skilled in the art will understand, although for illustrative purposes... Figure 1 The diagram shows a mobile device 3 and a base station 5, but in practice, the system will typically include other base station / RAN nodes and mobile devices (UEs).

[0041] Each base station 5 (directly or via other nodes such as femtocells, repeaters, remote wireless heads, distributed units, and / or similar entities) controls one or more associated cells. Base station 5 supporting E-UTRA / 4G protocols may be referred to as "eNB," and base station 5 supporting next-generation / 5G protocols may be referred to as "gNB." It will be understood that some base stations 5 may be configured to support both 4G and 5G protocols, and / or any other 3GPP or non-3GPP communication protocols.

[0042] Mobile device 3 and its serving base station 5 are connected via a suitable air interface (e.g., a so-called "Uu" interface and / or the like). Adjacent base stations 5 are connected to each other via suitable base station-to-base station interfaces (such as so-called "X2" interfaces, "Xn" interfaces and / or the like). Base station 5 is also connected to the core network node via suitable interfaces (such as so-called "S1", "NG-C", "NG-U" interfaces and / or the like).

[0043] Core network 7 (e.g., EPC in LTE or NGC in NR / 5G) typically includes logical nodes (or "functions") for supporting communications in telecommunications system 1 and for subscriber management, mobility management, billing, security, call / session management (and others). For example, core network 7 of a "next-generation" / 5G system would include user plane entities and control plane entities. In this example, the core network includes at least one control plane function (CPF) 11 and at least one user plane function (UPF) 12. Core network 7 is also (via UPF 12) coupled to a data network (DN) 20, such as the Internet or a similar Internet Protocol (IP) based network (in... Figure 1 (represented as "external network" in Chinese, etc.)

[0044] It will be understood that each mobile device 3 can support various services with different priorities. These services may fall into one of the categories defined above (URLLC / eMBB / mMTC). Each service will typically have associated requirements (e.g., latency / data rate / packet loss requirements, etc.), which may differ for different services. It will be understood that URLLC has a relatively higher priority than other services to ensure adequate (low) latency for that service.

[0045] When UE 3 is receiving data for a specific service (e.g., URLLC), UE 3 uses the resources associated with that service to transmit appropriate HARQ-ACK feedback to base station 5. Typically, HARQ-ACK feedback is provided in the form of a codebook (bit string), where bits in the codebook indicate which data has been successfully received and which has not. Since URLLC is designed for high reliability, in most cases, URLLC data will be successfully received, and the associated HARQ feedback will carry an ACK (acknowledgment). Advantageously, in this system, the URLLC-related feedback (or information representing that feedback) is provided as a single bit after the bit carrying the eMBB feedback. In practice, the URLLC feedback is bundled with a single bit of information and that information is appended to the end of the eMBB HARQ feedback. In other words, the eMBB feedback and the (bundled bit) URLLC feedback are multiplexed to form a combined codebook (eMBB codebook + 1 bit representing the URLLC codebook). Advantageously, to ensure that the latency requirements of URLLC are met, multiplexing feedback is transmitted on URLLC HARQ-ACK resources instead of eMBB resources. By prioritizing eMBB feedback over URLLC feedback (since eMBB HARQ feedback is more likely to carry NACK compared to URLLC HARQ feedback) and by sending the complete eMBB codebook to the transmitter (base station 5), the transmitter can accurately determine which part of the eMBB data needs to be retransmitted, while also indicating whether the transmission of the URLLC data was successful.

[0046] In variations of the above method, the type of service being bundled is determined based on one or more rules. For example, the following rule could be used: if the URLLC codebook carries both ACK and NACK, the eMBB bit is bundled into one bit and appended to the end of the URLLC codebook; if the URLLC codebook carries only ACK (or only NACK), the URLLC bit is bundled into one bit and appended to the end of the eMBB codebook. When the bundled eMBB feedback indicates NACK (the first case above), the complete eMBB codebook can be transmitted later (e.g., using normal eMBB HARQ resources).

[0047] Alternatively, the rule could specify that if the URLLC codebook carries only ACK or only NACK, and if the eMBB codebook carries both ACK and NACK, then the URLLC bits are bundled into one bit and appended to the end of the eMBB codebook. Otherwise, the eMBB bits are bundled into one bit and appended to the end of the URLLC codebook. If one of these rules is applied, an indication of which codebook is bundled can be provided explicitly (e.g., using an append bit) or implicitly (e.g., based on which resource is used to transmit feedback).

[0048] User Equipment (UE)

[0049] Figure 2 It is shown Figure 1 The diagram shows a block diagram of the main components of the mobile device (UE) 3. As shown, the UE 3 includes a transceiver circuit 31 operable to transmit signals to (one or more) connected nodes and receive signals from (one or more) connected nodes via one or more antennas 33. Although it is not necessary to... Figure 2 As shown, UE 3 will of course have all the common functions of conventional mobile devices (such as user interface 35, etc.), and this can be provided appropriately by any one or any combination of hardware, software, and firmware. Controller 37 controls the operation of UE 3 according to the software stored in memory 39. For example, the software may be pre-installed in memory 39 and / or may be downloaded via telecommunications network 1 or from a removable data storage device (RMD). The software includes operating system 41 and communication control module 43, among others.

[0050] The communication control module 43 is responsible for processing (generating / sending / receiving) signaling messages and uplink / downlink data packets between UE 3 and other nodes (including (R)AN node 5 and core network nodes). Signaling may include control signaling (including UCI and DCI) related to PUCCH and / or PDCCH (and others). The communication control module 43 is also responsible for controlling the transmission of HARQ-ACK feedback.

[0051] Access network node (base station)

[0052] Figure 3 It is shown Figure 1 The diagram shows a block diagram of the main components of base station 5 (or a similar access network node). As shown, base station 5 includes transceiver circuitry 51 operable to transmit signals to and receive signals from one or more connected UEs 3 via one or more antennas 53, and to transmit signals to and receive signals from other network nodes via network interface 55 (directly or indirectly). Network interface 55 typically includes appropriate base station-to-base station interfaces (such as X2 / Xn) and appropriate base station-core network interfaces (such as S1 / NG-C / NG-U). Controller 57 controls the operation of base station 5 based on software stored in memory 59. For example, the software may be pre-installed in memory 59 and / or downloadable via telecommunications network 1 or from a removable data storage device (RMD). The software includes operating system 61 and communication control module 63, among others.

[0053] The communication control module 63 is responsible for processing (generating / sending / receiving) signaling between base station 5 and other nodes (such as UE 3 and core network nodes). Signaling may include control signaling (including UCI and DCI) related to PUCCH and / or PDCCH (and others). The communication control module 63 is also responsible for receiving HARQ-ACK feedback from UE 3.

[0054] Core network functions

[0055] Figure 4 It demonstrates the general core network functions (such as...) Figure 1The diagram shows a block diagram of the main components of the CPF 11 or UPF 12, etc. As shown, the core network function includes a transceiver circuit 71 operable to transmit signals to and receive signals from other nodes (including UE 3, base station 5, and other core network nodes) via a network interface 75. A controller 77 controls the operation of the core network function based on software stored in a memory 79. For example, the software may be pre-installed in the memory 79 and / or may be downloaded via the telecommunications network 1 or from a removable data storage device (RMD). The software includes an operating system 81 and a communication control module 83, among others.

[0056] The communication control module 83 is responsible for processing (generating / sending / receiving) signaling between core network functions and other nodes (such as UE 3, base station 5 and other RAN / core network nodes).

[0057] Detailed description

[0058] Section 8.2.2.2 of 3GPP TR 38.912v16.0.0 provides the following overview of the HARQ codebook and processes used in NR systems:

[0059] Supports HARQ-ACK feedback with one bit per TB. Supports operation of more than one downlink (DL) HARQ process for a given UE, while supporting operation of one DL HARQ process for some UEs. Both the UE and the NR (base station) have minimum HARQ processing time. The HARQ processing time includes at least the delay between the DL data reception timing and the corresponding HARQ-ACK transmission timing, and the delay between the uplink (UL) grant reception timing and the corresponding UL data transmission timing.

[0060] Asynchronous and adaptive DL HARQ is supported at least for eMBB and URLLC. From the UE's perspective, HARQ ACK / NACK feedback for multiple DL transmissions can be transmitted in a timed manner within a single UL data / control area. The timing between DL data reception and the corresponding acknowledgment is indicated by a field in the DCI from a set of values ​​configured by a higher layer. At least one or more timings are defined for situations where the UE is unaware of (one or more) timings.

[0061] It supports block group (CBG) based transmission with single / multi-bit HARQ-ACK feedback, and has the following characteristics:

[0062] - For the same TB for the HARQ process, only CBG-based (re)transmissions are allowed;

[0063] Regardless of the size of the TB, the CBG can include the entire codebook of the TB. In this case, the UE reports a single HARQ ACK bit for the TB;

[0064] -CBG can include a codebook;

[0065] -CBG granularity is configurable.

[0066] The following is for reference Figure 5 and Figure 6 To provide a more detailed description of some example embodiments and features.

[0067] URLLC feedback is bound to one bit and appended to eMBB HARQ feedback.

[0068] In this option, URLLC-related feedback is provided after the bit used to indicate eMBB feedback, in the form of a single bit indicating whether any URLLC data was not successfully received. For example, when all associated URLLC data is successfully received, the information (1 bit) can be set to a value (e.g., "1") to indicate "ACK", and when at least some of the associated URLLC data is not successfully received, the information (1 bit) can be set to a different value (e.g., "0") to indicate "NACK". By a specific example, when the original URLLC feedback is in the form of "11111", UE 3 can provide URLLC-related feedback by transmitting a single bit of information set to the value "1". When the original URLLC feedback is in the form of "11011" (or any other form with at least one zero value), UE 3 can provide URLLC-related feedback by setting that single bit of information to the value "0".

[0069] Therefore, in practice, the URLLC feedback is bundled into a single bit and appended to the end of the eMBB HARQ feedback. Using the specific example given above, and assuming an eMBB HARQ feedback in the form of "11011", the actual feedback transmitted by UE 3 will be in the form of "110111" (the last bit indicating "ACK" for all URLLC transmissions expected to provide feedback) or in the form of "110110" (where the last bit indicates that UE 3 failed to receive one or more URLLC transmissions expected to provide feedback).

[0070] Beneficially, to ensure that the latency requirements of URLLC are met, multiplexing feedback is transmitted on URLLC HARQ-ACK resources instead of eMBB resources.

[0071] Figure 5This is a flowchart illustrating an exemplary method by which URLLC feedback can be bundled into a single bit and attached to eMBB HARQ feedback according to this option. The flowchart illustrates the processing performed by UE 3 (using its communication control module 43) for each round of HARQ feedback reports. It will be understood that although this flowchart is illustrated with reference to the actions performed by UE 3, base station 5 (communication control module 63) may also perform the same (or similar) actions for transmitting HARQ feedback to UE 3.

[0072] As can be seen, the process depends on the type of feedback that needs to be sent. In fact, steps S4 and S5 represent the scheme when HARQ feedback does not need to be reused since only one type of service exists. When only the URLLC feedback to be sent exists (when no eMBB transmission exists), the feedback (i.e., the "complete" URLLC codebook) is transmitted on the resource associated with the URLLC feedback (step S4). Similarly, when only the eMBB feedback to be sent exists (e.g., no URLLC transmission exists within the relevant time period), the feedback (the "complete" eMBB codebook) is transmitted on the resource associated with the eMBB feedback (step S5).

[0073] Advantageously, when feedback needs to be sent for both URLLC and eMBB services, UE 3 is configured to perform the aforementioned codebook bundling and multiplexing. Specifically, when UE 3 determines in step S1 that HARQ-ACK information needs to be sent for both URLLC and eMBB, UE 3 (using its communication control module 43) bundles bits of the HARQ codebook into a single bit (step S2). As mentioned above, when this bit is set to "1", it can indicate that all associated URLLC packets have been successfully received (therefore, detailed feedback is omitted). Alternatively, when this bit is set to "0", it can indicate that at least one associated URLLC packet has not been successfully received.

[0074] In step S3, UE 3 appends the bundled URLLC feedback (a single bit in this example) to the end of the eMBB codebook and continues to transmit HARQ-ACK feedback using the URLLC feedback resources. Advantageously, based on the number of bits received, base station 5 can determine whether the received feedback is only for URLLC or for both URLLC and eMBB.

[0075] It will also be understood that when the additional bit is set to "0", base station 5 can be configured to retransmit at least one of the following data packets (e.g., the last data packet or all data packets), for which feedback was sent.

[0076] Reusing eMBB and URLLC HARQ-ACK feedback based on codebook (CB) content

[0077] Figure 6 This is a flowchart schematically illustrating another exemplary method of providing bundled and multiplexed feedback based on the contents of the URLLC / eMBB codebook. It will be understood that although this flowchart is illustrated with reference to the actions performed by UE 3, base station 5 may also perform the same (or similar) actions for transmitting HARQ feedback to UE 3.

[0078] For reference Figure 5 Variations of the method may select the type of service with bundled feedback based on one or more bundling rules. For example, UE 3 (communication control module 43) may be configured to (in Figure 6 In step S2), the following set of rules is applied:

[0079] - If the URLLC codebook carries both ACK and NACK, then the eMBB bit is bundled into 1 bit and appended to the end of the URLLC codebook;

[0080] - If the URLLC codebook carries only ACK (or only NACK), then the URLLC bit is bundled into 1 bit and appended to the end of the eMBB codebook.

[0081] UE 3 can also be configured to apply the following set of rules:

[0082] - If the URLLC codebook carries only ACK (or only NACK), and if the eMBB codebook carries both ACK and NACK, then UE 3 will bundle the URLLC bit into 1 bit and append that bit to the end of the eMBB codebook.

[0083] - Otherwise, bundle the eMBB bit into 1 bit and append it to the end of the URLLC codebook.

[0084] In step S3, the bundled feedback (URLLC or eMBB feedback) is attached to the original feedback / codebook of another service and (in step S4 or S5) transmitted to base station 5.

[0085] In other words, the multiplexing feedback includes the original codebook of a service, followed by a bit representing the result of binding another codebook. When the bound eMBB feedback indicates a NACK (sent using the URLLC resource in step S4), it can be (e.g., using the eMBB HARQ resource in step S5, as in...) Figure 6(As shown by dashed lines) The complete eMBB codebook is transmitted later. In this case, features of various versions 16 (e.g., Type 3 codebook, enhanced Type 2 codebook, and / or NNK1) can be used for the actual (uncompressed) eMBB HARQ-ACK feedback transmission.

[0086] If the above rules are applied, an indication of which codebook is bundled can be provided explicitly (e.g., using additional bits), where in this case, the bundled feedback (URLLC or eMBB feedback) can be transmitted using URLLC resources in step S4. Alternatively, an indication of which codebook is bundled can be provided implicitly (e.g., based on which resource is used to transmit feedback). For example, multiplexed feedback can be transmitted on a resource intended for uncompressed feedback. The resource used to carry multiplexed feedback can implicitly indicate which codebook is bundled. For example, a URLLC resource (step S4) can be used to indicate that the bundled URLLC feedback has been multiplexed with eMBB feedback, and an eMBB resource (step S5) can be used to indicate that the bundled eMBB feedback has been multiplexed with URLLC feedback, or vice versa. In this case, base station 5 needs to perform blind decoding on the two conflicting resources.

[0087] benefit

[0088] Compared to always binding the eMBB codebook, the above method provides more accurate feedback for eMBB transmissions when it is determined that the URLLC feedback can be bound to a single bit without compromising the URLLC service requirements.

[0089] Modification and replacement

[0090] The above describes detailed exemplary embodiments. As those skilled in the art will understand, many modifications and substitutions can be made to the above exemplary embodiments while still benefiting from the invention embodied in these modifications and substitutions. Many of these substitutions and modifications will now be described by way of example only.

[0091] It will be understood that the above example embodiments can be applied to both 5G New Radio and LTE systems (E-UTRAN).

[0092] The UE can use dynamic scheduling (also known as "one-time" grant) and / or pre-allocated communication resources (e.g., via semi-persistent scheduling or configured grant) to transmit or receive data. It will be understood that the feedback multiplexing technique described above can be applied to data transmitted using any type of scheduling.

[0093] In the above description, URLLC and eMBB are used as exemplary services, wherein HARQ feedback is transmitted for the exemplary service. However, it will be understood that the above methods can be applied to other combinations of services with different priorities (e.g., URLLC and any other relatively low-priority service (e.g., mMTC and / or the like)).

[0094] Regarding URLLC latency requirements, it will be understood that the base station can configure appropriate URLLC PUCCH resources to meet the latency and reliability requirements of URLLC HARQ-ACK (whether bundled or not) when using the above-described in-UE HARQ-ACK multiplexing. More specifically, the base station can indicate appropriate URLLC PUCCH resources based on the larger of the maximum number of HARQ-ACK bits (e.g., i) the number of eMBB HARQ-ACK bits plus (one or more) bundle bits and ii) the number of URLLC HARQ-ACK bits plus (one or more) bundle bits) plus any additional bits used to indicate which HARQ codebook has been bundled.

[0095] In NR, HARQ uses an asynchronous mechanism for both the downlink and uplink, while in LTE, HARQ uses a synchronous mechanism for the uplink. In the case of asynchronous HARQ, multiple HARQ processes can run in any order, and these processes are identified by the associated HARQ process number for each transmission / reception of HARQ data.

[0096] In steps S4 and S5, HARQ feedback can be transmitted using either PUCCH or PUSCH, and different services can use different channels. It will also be understood that different HARQ processes can use different channels if appropriate.

[0097] In the above description, for ease of understanding, the UE, access network node (base station), and core network node are described as having multiple discrete modules (such as communication control modules). While these modules can be provided in this way for certain applications, such as where existing systems have been modified to implement the present invention, in other applications, such as in systems designed from the outset with the utilization of this inventive feature in mind, these modules can be built into the entire operating system or code, and therefore these modules may not be identifiable as discrete entities. These modules can also be implemented in software, hardware, firmware, or a combination of these.

[0098] Each controller may include any suitable form of processing circuitry, including (but not limited to) such as: one or more hardware-implemented computer processors; microprocessors; central processing units (CPUs); arithmetic logic units (ALUs); input / output (I / O) circuitry; internal memory / cache (program and / or data); processing registers; communication buses (e.g., control, data, and / or address buses); direct memory access (DMA) functionality; hardware or software-implemented counters, pointers, and / or timers; and / or the like.

[0099] In the above example embodiments, multiple software modules are described. As those skilled in the art will understand, the software modules may be provided in compiled or uncompiled form and may be supplied as signals to the UE, access network node (base station), and core network node on a computer network or on a recording medium. Furthermore, one or more dedicated hardware circuits may be used to perform some or all of the functions performed by the software. However, the use of software modules is preferred because they facilitate updating the UE, access network node (base station), and core network node to update their functionality.

[0100] It should be understood that when a control plane-user plane (CP-UP) separation is adopted, the base station can be separated into separate control plane entities and user plane entities. Each entity may include associated transceiver circuitry, antennas, network interfaces, controllers, memory, operating systems, and communication control modules. When the base station includes distributed base stations, the network interface ( Figure 3 The attached figure (reference numeral 55) also includes an E1 interface and an F1 interface (F1-C for the control plane and F1-U for the user plane) to communicate signals between the corresponding functions of the distributed base station. In this case, the communication control module is also responsible for communication between the control plane and user plane parts of the base station (generating, sending, and receiving signaling messages).

[0101] The above example embodiments can also be applied to "non-mobile" or generally fixed user equipment. The mobile devices described above may include MTC / IoT devices and / or the like.

[0102] A multiplexed HARQ codebook can be derived by appending HARQ information to a second HARQ codebook. HARQ information for a URLLC service can be generated by bundling a first HARQ codebook to a single bit. The HARQ information for a URLLC service may include a bit set to a first value (e.g., "1") to indicate that data associated with the URLLC service has been successfully received, or set to a second value (e.g., "0") to indicate that at least a portion of the data associated with the URLLC service has not been successfully received.

[0103] The second service may include enhanced mobile broadband (eMBB) service.

[0104] The method performed by the UE may include: using at least one communication resource associated with the URLLC to transmit a multiplexed HARQ codebook.

[0105] At least one predefined rule may include one or more of the following:

[0106] - A rule used to specify that if the first HARQ codebook carries both ACK and NACK, then the second HARQ codebook is bundled into one bit and appended to the end of the first HARQ codebook.

[0107] - A rule specifying that if the first HARQ codebook carries only ACK or only NACK and the second HARQ codebook carries both ACK and NACK, then the first HARQ codebook is bundled into a single bit and appended to the end of the second HARQ codebook; and

[0108] - This rule specifies that if the second HARQ codebook carries only ACK or only NACK, then the second HARQ codebook is bundled into one bit and appended to the end of the first HARQ codebook.

[0109] When the binding bit is based on the second codebook, the method performed by the UE may further include: transmitting the second codebook to the access network node after transmitting the multiplexed HARQ-ACK codebook. The method may further include: transmitting information indicating which codebook has been bound into a single bit. The information indicating which codebook has been bound into a single bit may include a bit indicator prior to the multiplexing of the HARQ codebook.

[0110] Various other modifications will be obvious to those skilled in the art, and will not be described in further detail here.

[0111] All or part of the exemplary embodiments disclosed above may be described in, but are not limited to, the following supplementary description.

[0112] (Supplementary Note 1)

[0113] A method performed by a user equipment (UE), the method comprising:

[0114] Receive signals from the access network node for carrying data associated with the first ultra-reliable and low-latency communication service, namely the first URLLC service, and data associated with the second service;

[0115] Generate a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for data associated with the URLLC service, and generate a second HARQ codebook for data associated with the second service;

[0116] Based on the first HARQ codebook, generate the HARQ information of the URLLC service, and multiplex the HARQ information of the URLLC service with the second HARQ codebook to derive a multiplexed HARQ codebook; and

[0117] The multiplexed HARQ codebook is transmitted to the access network node using at least one communication resource associated with the URLLC.

[0118] (Supplementary Note 2)

[0119] According to the method described in Supplementary Explanation 1, the multiplexed HARQ codebook is derived by appending the HARQ information to the second HARQ codebook.

[0120] (Supplementary Explanation 3)

[0121] According to the method described in Supplementary Note 1 or 2, the HARQ information of the URLLC service is generated by binding the first HARQ codebook to a single bit.

[0122] (Supplementary Note 4)

[0123] According to any one of Supplementary Notes 1 to 3, the HARQ information of the URLLC service includes a bit that is set to a first value (e.g., "1") to indicate that data associated with the URLLC service has been successfully received, or is set to a second value (e.g., "0") to indicate that at least a portion of the data associated with the URLLC service has not been successfully received.

[0124] (Supplementary Note 5)

[0125] According to any one of Supplementary Notes 1 to 4, the method wherein the second service includes enhanced mobile broadband service, i.e., eMBB service.

[0126] (Supplementary Note 6)

[0127] A method performed by a user equipment (UE), the method comprising:

[0128] Receive signals from the access network node for carrying data associated with the first ultra-reliable and low-latency communication service, namely the first URLLC service, and data associated with the second service;

[0129] Generate a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for data associated with the URLLC service, and generate a second HARQ codebook for data associated with the second service;

[0130] According to at least one predetermined rule, one of the first HARQ codebook and the second HARQ codebook is bound to one bit;

[0131] The binding bit is multiplexed with another codebook in the first and second HARQ codebooks to derive the multiplexed HARQ codebook; and

[0132] The multiplexed HARQ codebook is transmitted to the access network node.

[0133] (Supplementary Note 7)

[0134] The method according to Supplementary Note 6 includes: using at least one communication resource associated with the URLLC to transmit the multiplexed HARQ codebook.

[0135] (Supplementary Note 8)

[0136] According to the method described in Supplementary Note 6 or 7, the at least one predetermined rule includes one or more of the following rules:

[0137] - A rule that specifies that if the first HARQ codebook carries both ACK and NACK, the second HARQ codebook is bundled into one bit and appended to the end of the first HARQ codebook.

[0138] - A rule specifying that if the first HARQ codebook carries only ACK or only NACK and the second HARQ codebook carries both ACK and NACK, then the first HARQ codebook is bundled into a single bit and appended to the end of the second HARQ codebook; and

[0139] - A rule used to specify that if the second HARQ codebook carries only ACK or only NACK, then the second HARQ codebook is bundled into one bit and appended to the end of the first HARQ codebook.

[0140] (Supplementary Note 9)

[0141] According to any one of Supplementary Notes 6 to 8, wherein, when the binding bit is based on the second codebook, the method further includes: transmitting the second codebook to the access network node after transmitting the multiplexed HARQ-ACK codebook.

[0142] (Supplementary Note 10)

[0143] The method according to any one of Supplementary Notes 6 to 9 further includes: transmitting information for indicating which codebook has been bundled into a single bit.

[0144] (Supplementary Note 11)

[0145] According to the method described in Supplementary Note 10, the information used to indicate which codebook has been bundled into a single bit includes an indicator preceding the multiplexed HARQ codebook.

[0146] (Supplementary Note 12)

[0147] According to any one of Supplementary Notes 6 to 11, the method wherein the second service includes enhanced mobile broadband service, i.e., eMBB service.

[0148] (Supplementary Note 13)

[0149] A method performed by an access network node, the method comprising:

[0150] Transmit to the user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and

[0151] The UE receives a multiplexed hybrid automatic repeat request codebook, i.e., a multiplexed HARQ codebook, using at least one communication resource associated with the URLLC, wherein the multiplexed HARQ codebook is based on the HARQ information of the URLLC service, the HARQ information of the URLLC service being generated based on a first HARQ codebook for data associated with the URLLC service and multiplexed with a second HARQ codebook for data associated with the second service.

[0152] (Supplementary Note 14)

[0153] A method performed by an access network node, the method comprising:

[0154] Transmit to the user equipment (UE) a signal carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and

[0155] The UE receives a multiplexed hybrid automatic repeat request codebook, i.e., a multiplexed HARQ codebook, wherein the multiplexed HARQ codebook includes: i) a first HARQ codebook for data associated with one of the URLLC service and the second service; and ii) binding bits based on a second HARQ codebook for data associated with the other of the URLLC service and the second service.

[0156] (Supplementary Note 15)

[0157] A user equipment, or UE, includes:

[0158] A component for receiving from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service, namely a first URLLC service, and data associated with a second service;

[0159] Components for generating a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for data associated with the URLLC service, and for generating a second HARQ codebook for data associated with the second service;

[0160] A component for generating HARQ information for the URLLC service based on the first HARQ codebook, and for multiplexing the HARQ information of the URLLC service with the second HARQ codebook to derive a multiplexed HARQ codebook; and

[0161] A component for transmitting the multiplexed HARQ codebook to the access network node using at least one communication resource associated with the URLLC.

[0162] (Supplementary Note 16)

[0163] A user equipment, or UE, includes:

[0164] A component for receiving from an access network node a signal carrying data associated with a first ultra-reliable and low-latency communication service, namely a first URLLC service, and data associated with a second service;

[0165] Components for generating a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for data associated with the URLLC service, and for generating a second HARQ codebook for data associated with the second service;

[0166] A component for binding one of the first HARQ codebook and the second HARQ codebook to a single bit according to at least one predetermined rule;

[0167] A component for multiplexing the binding bit with another codebook in the first and second HARQ codebooks to derive a multiplexed HARQ codebook; and

[0168] A component used to transmit the multiplexed HARQ codebook to the access network node.

[0169] (Supplementary Note 17)

[0170] An access network node, comprising:

[0171] Components for transmitting to a user equipment (UE) signals carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and

[0172] A component for receiving a multiplexed hybrid automatic repeat request codebook, i.e., a multiplexed HARQ codebook, from the UE using at least one communication resource associated with the URLLC, wherein the multiplexed HARQ codebook is based on HARQ information of the URLLC service, the HARQ information of the URLLC service being generated based on a first HARQ codebook for data associated with the URLLC service and multiplexed with a second HARQ codebook for data associated with the second service.

[0173] (Supplementary Note 18)

[0174] An access network node, comprising:

[0175] Components for transmitting to a user equipment (UE) signals carrying data associated with a first ultra-reliable and low-latency communication service (URLLC service) and data associated with a second service; and

[0176] Components for receiving a multiplexed hybrid automatic repeat request codebook, i.e., a multiplexed HARQ codebook, from the UE, wherein the multiplexed HARQ codebook includes: i) a first HARQ codebook for data associated with one of the URLLC service and the second service; and ii) binding bits based on a second HARQ codebook for data associated with the other of the URLLC service and the second service.

[0177] This application is based on and claims the benefit of priority to UK patent application 2016378.8, filed on 15 October 2020, the disclosure of which is incorporated herein by reference in its entirety.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receive signals from the access network node for carrying first data corresponding to the ultra-reliable and low-latency communication service, i.e., URLLC service, and second data corresponding to the second service; Generate a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for the first data to be transmitted in the first physical uplink channel; A second HARQ codebook is generated for the second data to be transmitted in a second physical uplink channel that is different from the first physical uplink channel; The HARQ information of the URLLC service is generated based on the first HARQ codebook, wherein the generation is performed by the following operation: generating the uplink control information of the URLLC service by reducing the number of bits of content to be transmitted in the first physical uplink channel based on content that includes only negative acknowledgment information; The uplink control information is multiplexed with the second HARQ codebook to derive multiplexed uplink control information; and The multiplexed uplink control information is transmitted to the access network node in the second physical uplink channel.

2. The method according to claim 1, wherein, The HARQ information includes a bit that is set to a first value to indicate that the first data has been successfully received, or set to a second value to indicate that at least a portion of the first data has not been successfully received.

3. The method according to claim 1 or 2, wherein, When the first HARQ codebook carries only ACK or only NACK, the HARQ information is a single bit and is appended to the second HARQ codebook.

4. The method according to claim 1 or 2, further comprising: After transmitting the multiplexed uplink control information, the first HARQ codebook is transmitted to the access network node.

5. The method according to claim 1 or 2, further comprising: The transmission indicates which HARQ codebook already contains one bit of information.

6. The method according to claim 5, wherein, The information includes a bit of an indicator preceding the multiplexed uplink control information.

7. The method according to claim 1 or 2, wherein, The first data corresponds to the high priority, and The second data corresponds to the low priority.

8. The method according to claim 1 or 2, wherein, The multiplexed uplink control information is derived by appending the HARQ information to the second HARQ codebook.

9. The method according to claim 1 or 2, wherein, The HARQ information is generated by binding the first HARQ codebook to one bit.

10. The method according to claim 1 or 2, wherein, The second service includes enhanced mobile broadband service, namely eMBB service.

11. A method performed by an access network node, the method comprising: Transmit signals to the user equipment (UE) for carrying first data corresponding to the ultra-reliable and low-latency communication service (URLLC) and second data corresponding to the second service; as well as Multiplexed uplink control information is received from the UE in a second physical uplink channel, which is different from the first physical uplink channel, wherein The multiplexed uplink control information is based on the uplink control information of the URLLC service. The uplink control information of the URLLC service is generated based on the first hybrid automatic repeat request codebook (i.e., the first HARQ codebook) for the first data, and is multiplexed with the second HARQ codebook for the second data. The uplink control information is generated by reducing the number of bits of content to be transmitted in the first physical uplink channel based on content that includes only negative acknowledgment information. A first HARQ codebook has been generated for transmission in the first physical uplink channel, and The second HARQ codebook has been generated for transmission in the second physical uplink channel.

12. A user equipment, or UE, comprising: Memory, used to store instructions; as well as At least one processor is configured to process the instructions such that: Receive signals from the access network node for carrying first data corresponding to the ultra-reliable and low-latency communication service, i.e., URLLC service, and second data corresponding to the second service; Generate a first hybrid automatic repeat request codebook, i.e., a first HARQ codebook, for the first data to be transmitted in the first physical uplink channel; A second HARQ codebook is generated for the second data to be transmitted in a second physical uplink channel that is different from the first physical uplink channel; The HARQ information of the URLLC service is generated based on the first HARQ codebook, wherein the generation is performed by the following operation: generating the uplink control information of the URLLC service by reducing the number of bits of content to be transmitted in the first physical uplink channel based on content that includes only negative acknowledgment information; The uplink control information is multiplexed with the second HARQ codebook to derive multiplexed uplink control information; and The multiplexed uplink control information is transmitted to the access network node in the second physical uplink channel.

13. An access network node, comprising: Memory, used to store instructions; as well as At least one processor is configured to process the instructions such that: Transmit signals to the user equipment (UE) for carrying first data corresponding to the ultra-reliable and low-latency communication service (URLLC) and second data corresponding to the second service; as well as Multiplexed uplink control information is received from the UE in a second physical uplink channel, which is different from the first physical uplink channel, wherein The multiplexed uplink control information is based on the uplink control information of the URLLC service. The uplink control information of the URLLC service is generated based on the first hybrid automatic repeat request codebook (i.e., the first HARQ codebook) for the first data, and is multiplexed with the second HARQ codebook for the second data. The uplink control information is generated by reducing the number of bits of content to be transmitted in the first physical uplink channel based on content that includes only negative acknowledgment information. A first HARQ codebook has been generated for transmission in the first physical uplink channel, and The second HARQ codebook has been generated for transmission in the second physical uplink channel.

Images