WO2020006687A1

WO2020006687A1 - Unified uplink control information for uplink transmission with configured grant

Info

Publication number: WO2020006687A1
Application number: PCT/CN2018/094339
Authority: WO
Inventors: Tao Tao; Jianguo Liu; Zhe LUO; Yan Meng; Zhuo WU; Gang Shen
Original assignee: Nokia Shanghai Bell Co., Ltd.; Nokia Solutions And Networks Oy; Nokia Technologies Oy
Priority date: 2018-07-03
Filing date: 2018-07-03
Publication date: 2020-01-09
Also published as: CN112369097B; CN112369097A

Abstract

In accordance with some embodiments, an apparatus, comprising at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI). The apparatus may further map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The apparatus may further transmit the U-CG-UCI to at least one network entity.

Description

UNIFIED UPLINK CONTROL INFORMATION FOR UPLINK TRANSMISSION WITH CONFIGURED GRANT

BACKGROUND: Field:

Certain embodiments may relate to communication systems. For example, some embodiments may relate to configured grant uplink control information.

Description of the Related Art:

In new radio (NR) , transmissions using a configured grant (CG) , such as grant-free transmission and autonomous transmission, are specified to meet stringent latency and reliability requirements of ultra-reliable low latency communication (URLLC) . For example, 32 bytes of URLLC traffic may be required to have a transmission success of 1x10 ^-5 within the duration of 1ms. By reducing the latency given by the scheduling request and uplink (UL) grant to physical uplink shared channel (PUSCH) transmission, UL transmissions with configured grants can satisfy the latency requirements of URLLC traffic.

Both enhanced mobile broadband (eMBB) and URLLC traffic may be transmitted via UL transmission with configured grants in unlicensed spectrum. A network entity may configure separate resource pools for eMBB and URLLC, such as by introducing logic channel priority (LCP) restrictions for resource allocation. However, in order to achieve higher flexibility and lower latency for URLLC, network resources may be wasted by restricting and prohibiting how user equipment utilizes configured resources, namely, eMBB and URLLC. By using a common resource pool, user equipment can transmit both eMBB and URLLC traffic in the same slot. To illustrate this technique, FIG. 1 shows an example of a URLLC transmission block (TB) and an eMBB TB multiplexed into a single slot.

Using current techniques, each TB may need to be associated with configured grant uplink control information (CG-UCI) to indicate various data, such as hybrid automatic repeat request (HARQ) process identification, resource block (RB) , and new data indicator (NDI) . As shown in FIG. 1, two CG-UCIs may exist in each slot, where one slot is used for eMBB TB, and the other slot is used for URLLC TB. However, transmission of two separate UCIs in one slot is extremely inefficient. Furthermore, transmitting two separate CG-UCI results in unreliable transmission performance, especially for CG-UCI associated with eMBB TB.

SUMMARY:

In accordance with some embodiments, a method may include generating, by user equipment, one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The method may further include mapping, by the user equipment, one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The method may further include transmitting, by the user equipment, the U-CG-UCI to at least one network entity.

In accordance with some embodiments, an apparatus may include means for generating one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The apparatus may further include means for mapping one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The apparatus may further include means for transmitting the U-CG-UCI to at least one network entity.

In accordance with some embodiments, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus to at least generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least transmit the U-CG-UCI to at least one network entity.

In accordance with some embodiments, a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method. The method may generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The method may further map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The method may further transmit the U-CG-UCI to at least one network entity.

In accordance with some embodiments, a computer program product may perform a method. The method may generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The method may further map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The method may further transmit the U-CG-UCI to at least one network entity.

In accordance with some embodiments, an apparatus may include circuitry configured to generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) . The circuitry may further map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity. The circuitry may further transmit the U-CG-UCI to at least one network entity.

In accordance with some embodiments, a method may include receiving, by a network entity, at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The method may further include decoding, by the network entity, the at least one U-CG-UCI in one or more pre-configured locations. The method may further include receiving, by the network entity, at least one ultra-reliable low latency communication (URLLC) . The method may further include decoding, by the network entity, the at least one URLLC based upon the uplink control information.

In accordance with some embodiments, an apparatus may include means for receiving at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The apparatus may further include means for decoding the at least one U-CG-UCI in one or more pre-configured locations. The apparatus may further include means for receiving at least one ultra-reliable low latency communication (URLLC) . The apparatus may further include means for decoding the at least one URLLC based upon the uplink control information.

In accordance with some embodiments, an apparatus may include at least one processor and at least one memory including computer program code. The at least one memory and the computer program code can be configured to, with the at least one processor, cause the apparatus to at least receive at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least decode the at least one U-CG-UCI in one or more pre-configured locations. The at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least receive at least one ultra-reliable low latency communication (URLLC) . The at least one memory and the computer program code can be further configured to, with the at least one processor, cause the apparatus to at least decode the at least one URLLC based upon the uplink control information.

In accordance with some embodiments, a non-transitory computer readable medium can be encoded with instructions that may, when executed in hardware, perform a method. The method may receive at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The method may further decode the at least one U-CG-UCI in one or more pre-configured locations. The method may further receive at least one ultra-reliable low latency communication (URLLC) . The method may further decode the at least one URLLC based upon the uplink control information.

In accordance with some embodiments, a computer program product may perform a method. The method may receive at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The method may further decode the at least one U-CG-UCI in one or more pre-configured locations. The method may further receive at least one ultra-reliable low latency communication (URLLC) . The method may further decode the at least one URLLC based upon the uplink control information.

In accordance with some embodiments, an apparatus may include circuitry configured to receive at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information. The circuitry may further decode the at least one U-CG-UCI in one or more pre-configured locations. The circuitry may further receive at least one ultra-reliable low latency communication (URLLC) . The circuitry may further decode the at least one URLLC based upon the uplink control information.

BRIEF DESCRIPTION OF THE DRAWINGS:

For proper understanding of this disclosure, reference should be made to the accompanying drawings, wherein:

FIG. 1 illustrates an example of intra-UE eMBB and URLLC multiplexing.

FIG. 2 illustrates an example of two-stage U-CG-UCI preparation.

FIG. 3 illustrates an example of eMBB and URLLC resource configuration in a CG slot.

FIG. 4 illustrates an example of eMBB and URLLC resource configuration in a CG slot.

FIG. 5 illustrates an example of a signaling diagram according to some embodiments.

FIG. 6 illustrates an example of a method performed by user equipment according to certain embodiments.

FIG. 7 illustrates an example of a method performed by a network entity according to certain embodiments.

FIG. 8 illustrates an example of a system according to certain embodiments.

DETAILED DESCRIPTION:

Certain embodiments described herein may have various benefits and/or advantages. For example, some embodiments may minimize the signaling overhead associated with multiple types of transmission blocks multiplexing in the same configured grant resource. In addition, certain embodiments may improve the control signaling performance when transmission block puncturing occurs. Some embodiments provide multi-stage data preparation and one-shot transmission mechanism to facilitate U-CG-UCI transmission, while also reducing the resources required for decoding by a network entity. Certain embodiments are, therefore, directed to improvements in computer-related technology, specifically, by conserving network resources and reducing power consumption of network entities and/or user equipment located within the network.

Uplink control information (UCI) may be associated with one type of TB transmitted in a UL configured grant resource, such as a slot. As an example, the type of TB may be an eMBB, URLLC TB, and/or mMTC TB. To support multiple types of TB transmissions in the same CG resource, U-CG-UCI may contain two types of information: common information for multiple types of TBs, and TB type-specific information.

Common information may include channel access related information, ACK/NACK feedback for DL transmission, channel status indication (CSI) feedback, and/or scheduling requests. In addition, TB type-specific information may include HARQ related information, such as HARQ process ID, RV, and/or NDI. Furthermore, the content of U-CG-UCI may vary according to TB multiplexing situations in the CG resource. For example, signals indicating the TB multiplexing situation may be introduced in U-CG-UCI.

U-CG-UCI may contain uplink control information for more than one transmitted TB. Furthermore, user equipment may adapt the information in U-CG-UCI according to TB multiplexing situations in the configured grant resource. The transmission scheme for U-CG-UCI may include multi-stage data preparation and one-shot transmission, detection, and decoding.

For multi-stage U-CG-UCI preparation, if a UL resource, such as a slot, is supported for multiple types of TB transmission with configured grants, user equipment may prepare the U-CG-UCI for the slot in multiple stages. As the U-CG-UCI is transmitted on PUSCH, the data of U-CG-UCI may be prepared together with PUSCH data. However, the data preparation timeline may be different for traffic types. When and how to prepare common control information for multiple types of TB becomes an issue. Thus, a multi-stage data preparation mechanism may be used for U-CG-UCI.

In the first stage, user equipment may prepare a first transmission TB, such as an eMBB TB, or TBs according to the traffic in the buffer and corresponding U-CG-UCI. The U-CG-UCI may be mapped to a pre-defined location. For example, the pre-defined location may be in an overlapped resource configured for potential multiple TBs being transmitted. Alternatively, the pre-defined location may be in the first few symbols of a configured grant slot.

Furthermore, in the second stage, if another type of traffic, such as higher priority data, comes to the buffer and the user equipment decides to transmit another TB, such as URLLC TB, on the same configured grant slot, user equipment may prepare a new U-CG-UCI at the second time point. Specifically, user equipment may prepare the TB for a higher priority traffic. The new U-CG-UCI may contain information required for old and new TBs, which may be transmitted in the same configured grant slot. The new U-CG-UCI may also be located in the pre-defined location. FIG. 2 illustrates such an example of a two-stage U-CG-UCI preparation mechanism.

If there are still new TBs to be transmitted in the same CG resource, user equipment may enter a third and subsequent stages for preparation of a new U-CG-UCI and corresponding new TB. Although the preparation of U-CG-UCI may occur in multiple stages, the actual transmission of U-CG-UCI may happen only once for a configured grant resource. The network entity may detect and decode the U-CG-UCI only at a pre-configured location. The configuration of U-CG-UCI may be pre-defined by the network, or may be indicated by RRC signaling from the network entity. The configuration may also include the structure of U-CG-UCI, the location of U-CG-UCI transmission, and/or other parameters.

FIG. 3 illustrates an example of eMBB and URLLC resources being configured in a CG slot. eMBB and URLLC traffic may be configured to be transmitted via UL transmission with a configured grant. The configured UL CG resource may be used for both eMBB traffic and URLLC traffic. For example, the whole CG slot can be used for eMBB traffic transmission, whereas partial resource elements in the CG slot are valid for URLLC traffic transmission. As shown in FIG. 3, potential URLLC resources may be configured to be symbols.

FIG. 4 illustrates a U-CG-UCI that may be used in the case of more flexible CG URLLC resource allocation. There may be multiple transmission occasions for URLLC traffic in a CG slot. Multiple transmission occasions may further reduce the transmission latency for URLLC traffic. In this example, there may be seven potential URLLC transmission occasions in the CG slot. User equipment may use any of these slots to perform URLLC transmission.

FIG. 5 illustrates an example of a signaling diagram showing communications between user equipment (UE) 530 and network entity (NE) 540. UE 530 may be similar to UE 810, as illustrated in FIG. 8. Likewise, NE 540 may be similar to NE 820, also illustrated in FIG. 8.

In step 501, UE 530 may generate at least one CG eMBB TB and/or at least one U-CG-UCI. In step 503, UE 530 may map the at least one U-CG-UCI to a pre-configured resource. Additionally and/or alternatively, UE 530 may rate-match the eMBB TB.

In step 505, UE 530 may receive URLLC traffic. In step 507, UE 530 may prepare at least one URLLC TB. Alternatively or additionally, UE 530 may map the at least one URLLC TB to at least one URLLC resource in at least one CG slot.

In step 509, UE 530 may use the URLLC TB to puncture at least one eMBB TB. In step 511, UE 530 may transmit at least one U-CG-UCI. In step 513, NE 540 may interpret control information for eMBB and/or URLLC.

In step 515, NE 540 may decode at least one eMBB TB based upon control information. In step 517, NE 540 may monitor for reception of URLLC. In step 519, UE 530 may transmit URLLC to NE 540. In step 521, NE 540 may decode the at least one URLLC TB according to the received U-CG-UCI.

FIG. 6 illustrates an example of a method performed by user equipment according to certain embodiments. In step 601, user equipment may generate one or more of at least one CG eMBB TB and at least one U-CG-UCI.

In step 603, the user equipment may map the at least one U-CG-UCI to at least one pre-configured resource, and rate-match the at least one eMBB TB. In step 605, the user equipment may receive URLLC traffic. In step 607, the user equipment may generate at least one URLLC TB. In step 609, the user equipment may map the at least one URLLC TB to at least one URLLC resource in at least one CG slot. In step 611, the user equipment may puncture the at least one eMBB with the at least one URLLC TB. In step 613, the user equipment may transmit at least one U-CG-UCI to at least one network entity.

FIG. 7 illustrates an example of a method performed by a network entity according to certain embodiments. In step 701, the network entity may receive at least one U-CG-UCI. In step 703, the network entity may interpret control information for eMBB and/or URLLC. In step 705, the network entity may decode at least one eMBB TB based upon the received control information. In step 707, the network entity may monitor for reception of at least one URLLC TB.In step 709, the network entity may receive at least one URLLC TB. In step 711, the network entity may decode the at least one received URLLC TB according to the U-CG-UCI.

FIG. 8 illustrates an example of a system according to certain embodiments. In one embodiment, a system may include multiple devices, such as, for example, user equipment 810 and/or network entity 820.

User equipment 810 may include one or more of a mobile device, such as a mobile phone, smart phone, personal digital assistant (PDA) , tablet, or portable media player, digital camera, pocket video camera, video game console, navigation unit, such as a global positioning system (GPS) device, desktop or laptop computer, single-location device, such as a sensor or smart meter, or any combination thereof.

Network entity 820 may be one or more of a base station, such as an evolved node B (eNB) or 5G or New Radio node B (gNB) , a serving gateway, a server, and/or any other access node or combination thereof. Furthermore, network entity 810 and/or user equipment 820 may be one or more of a citizens broadband radio service device (CBSD) .

One or more of these devices may include at least one processor, respectively indicated as 811 and 821.

Processors

811 and 821 may be embodied by any computational or data processing device, such as a central processing unit (CPU) , application specific integrated circuit (ASIC) , or comparable device. The processors may be implemented as a single controller, or a plurality of controllers or processors.

At least one memory may be provided in one or more of devices indicated at 812 and 822. The memory may be fixed or removable. The memory may include computer program instructions or computer code contained therein.

Memories

812 and 822 may independently be any suitable storage device, such as a non-transitory computer-readable medium. A hard disk drive (HDD) , random access memory (RAM) , flash memory, or other suitable memory may be used. The memories may be combined on a single integrated circuit as the processor, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory and which may be processed by the processors may be any suitable form of computer program code, for example, a compiled or interpreted computer program written in any suitable programming language. Memory may be removable or non-removable.

Processors

811 and 821 and

memories

812 and 822 or a subset thereof, may be configured to provide means corresponding to the various blocks of FIGS. 1-7. Although not shown, the devices may also include positioning hardware, such as GPS or micro electrical mechanical system (MEMS) hardware, which may be used to determine a location of the device. Other sensors are also permitted and may be included to determine location, elevation, orientation, and so forth, such as barometers, compasses, and the like.

As shown in FIG. 8,

transceivers

813 and 823 may be provided, and one or more devices may also include at least one antenna, respectively illustrated as 814 and 824. The device may have many antennas, such as an array of antennas configured for multiple input multiple output (MIMO) communications, or multiple antennas for multiple radio access technologies. Other configurations of these devices, for example, may be provided.

Transceivers

813 and 823 may be a transmitter, a receiver, or both a transmitter and a receiver, or a unit or device that may be configured both for transmission and reception.

The memory and the computer program instructions may be configured, with the processor for the particular device, to cause a hardware apparatus such as user equipment to perform any of the processes described below (see, for example, FIGS. 1-7) . Therefore, in certain embodiments, a non-transitory computer-readable medium may be encoded with computer instructions that, when executed in hardware, perform a process such as one of the processes described herein. Alternatively, certain embodiments may be performed entirely in hardware.

In certain embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in FIGS. 1-7. For example, circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, circuitry may be a combination of hardware circuits and software, such as a combination of analog and/or digital hardware circuit (s) with software or firmware, and/or any portions of hardware processor (s) with software (including digital signal processor (s) ) , software, and at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, circuitry may be hardware circuit (s) and or processor (s) , such as a microprocessor (s) or a portion of a microprocessor (s) , that include software, such as firmware for operation. Software in circuitry may not be present when it is not needed for the operation of the hardware.

The features, structures, or characteristics of certain embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, the usage of the phrases “certain embodiments, ” “some embodiments, ” “other embodiments, ” or other similar language, throughout this specification refers to the fact that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present invention. Thus, appearance of the phrases “in certain embodiments, ” “in some embodiments, ” “in other embodiments, ” or other similar language, throughout this specification does not necessarily refer to the same group of embodiments, and the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

One having ordinary skill in the art will readily understand that certain embodiments discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Partial Glossary

3GPP 3rd Generation Partnership Project

5G 5th Generation Wireless System

CG Configured Grant

CG-UCI Configured Grant UCI

COT Channel Occupancy Time

CSI Channel Status Indication

DL Downlink

DCI Downlink Control Information

DFI Downlink Feedback Information

DMRS Demodulation Reference Signal

eMBB Enhanced Mobile Broadband

NR New Radio

NR-U NR Unlicensed

LAA Licensed Assisted Access

LBT Listen-Before-Talk

LCP Logic Channel Priority

MCS Modulation Order and Coding Scheme

mMTC Massive Machine Type Communication

gNB next Generation Node B

TBS Transmission Block Size

UCI UL Control Information

UE User Equipment

UL Uplink

URLLC Ultra-reliable Low Latency Communication

RRC Radio Resource Control

SR Scheduling Request

TB Transmission Block

Claims

An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to:

generate one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) ;

map one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity; and

transmit the U-CG-UCI to at least one network entity.
The apparatus according to claim 1, wherein the U-CG-UCI includes at least a common field region and a transmission block type-specific field region,

wherein the common field region contains one or more of at least one multiplexing indication, at least one user equipment identifier, at least one channel occupancy time (COT) sharing indicator, at least one cyclic redundancy check (CRC) , and

wherein the transmission block type-specific field region one or more of at least one hybrid automatic repeat request (HARQ) identifier, at least one new data indicator (NDI) , at least one redundancy version (RV) , and at least one physical uplink shared channel (PUSCH) starting and ending position.
The apparatus according to claim 1 or 2, wherein the length of the U-CG-UCI is associated with the network entity configuration, and wherein the network entity configuration at least defines the length of the U-CG-UCI as a variable length or a predetermined length.
The apparatus according to any of claims 1-3, wherein the at least one resource is one or more of:

at least one overlapped area configured for ultra-reliable low latency communication (URLLC) CG transmission and eMBB CG transmission;

at least one resource within URLLC transmission; and

at least the first predetermined number of symbols of a configured grant slot.
The apparatus according to any of claims 1-4, wherein the U-CG-UCI is an uplink transmission configured to transmit one or more of eMBB traffic and URLLC traffic.
The apparatus according to any of claims 1-5, wherein at least part of a CG slot is used for eMBB traffic transmission.
The apparatus according to any of claims 1-6, wherein one or more partial resource elements in the CG slot are valid for URLLC traffic transmission.
The apparatus according to any of claims 1-7, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:

generate at least one CG URLLC TB in at least one pre-allocated CG URLLC resource; and

rate-match at least one CG URLLC TB associated with at least one U-CG-UCI.
The apparatus according to any of claims 1-8, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:

generate at least one CG eMBB TB in at least one pre-allocated CG eMBB resource; and

rate-match at least one CG eMBB TB associated with at least one U-CG-UCI and CG URLLC TB.
The apparatus according to any of claims 1-9, wherein the at least one memory and the computer program code are further configured to, with the at least one processor, cause the apparatus to:

receive URLLC traffic; and

in response to receiving the URLLC traffic, generating at least one U-CG-UCI,

wherein the at least one U-CG-UCI includes control information for one or more of at least one eMBB transmission and at least one URLLC transmission.
An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to:

receive at least one untied CG uplink control information (U-CG-UCI) associated with uplink control information;

decode the at least one U-CG-UCI in one or more pre-configured locations;

receive one or more of at least one enhanced mobile broadband (eMBB) and at least one ultra-reliable low latency communication (URLLC) ; and

decode the one or more of the at least one eMBB and the at least one URLLC based upon the uplink control information.
A method, comprising:

generating, by user equipment, one or more of at least one configured grant (CG) enhanced mobile broadband (eMBB) transmission block (TB) and at least one unified CG uplink control information (U-CG-UCI) ;

mapping, by the user equipment, one or more of the at least one CG eMBB and at least one U-CG-UCI to at least one resource configured by a network entity; and

transmitting, by the user equipment, the U-CG-UCI to at least one network entity.
The method according to claim 12, wherein the U-CG-UCI includes at least a common field region and a transmission block type-specific field region,

wherein the common field region contains one or more of at least one multiplexing indication, at least one user equipment identifier, at least one channel occupancy time (COT) sharing indicator, at least one cyclic redundancy check (CRC) , and

wherein the transmission block type-specific field region one or more of at least one hybrid automatic repeat request (HARQ) identifier, at least one new data indicator (NDI) , at least one redundancy version (RV) , and at least one physical uplink shared channel (PUSCH) starting and ending position.
The method according to claim 12 or 13, wherein the length of the U-CG-UCI is associated with the network entity configuration, and wherein the network entity configuration at least defines the length of the U-CG-UCI as a variable length or a predetermined length.
The method according to any of claims 12-14, wherein the at least one resource is one or more of:

at least one overlapped area configured for ultra-reliable low latency communication (URLLC) CG transmission and eMBB CG transmission;

at least one resource within URLLC transmission; and

at least the first few symbols of a configured grant slot.
The method according to any of claims 12-15, wherein the U-CG-UCI is an uplink transmission configured to transmit one or more of eMBB traffic and URLLC traffic.
The method according to any of claims 12-16, wherein at least part of a CG slot is used for eMBB traffic transmission.
The method according to any of claims 12-17, wherein one or more partial resource elements in the CG slot are valid for URLLC traffic transmission.
The method according to any of claims 12-18, further comprising:

generating, by the user equipment, at least one CG URLLC TB in at least one pre-allocated CG URLLC resource; and

rate-matching, by the user equipment, at least one CG URLLC TB associated with at least one U-CG-UCI.
The method according to any of claims 12-19, further comprising:

generating, by the user equipment, at least one CG eMBB TB in at least one pre-allocated CG eMBB resource; and

rate-matching, by the user equipment, at least one CG eMBB TB associated with at least one U-CG-UCI and CG URLLC TB.
The method according to any of claims 12-20, further comprising:

receiving, by the user equipment, URLLC traffic; and

in response to receiving the URLLC traffic, generating, by the user equipment, at least one U-CG-UCI,

wherein the at least one U-CG-UCI includes control information for one or more of at least one eMBB transmission and at least one URLLC transmission.
A method, comprising:

receiving, by a network entity, at least one unified CG uplink control information (U-CG-UCI) associated with uplink control information;

decoding, by the network entity, the at least one U-CG-UCI in one or more pre-configured locations;

receiving, by the network entity, one or more of at least one enhanced mobile broadband (eMBB) and at least one ultra-reliable low latency communication (URLLC) ; and

decoding, by the network entity, the one or more of the at least one eMBB and the at least one URLLC based upon the uplink control information.
A non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform a process according to any of claims 1-22.
An apparatus comprising means for performing a process according to any of claims 1-22.
An apparatus comprising circuitry configured to cause the apparatus to perform a process according to any of claims 1-22.
A computer program product encoded with instructions for performing a process according to any of claims 1-22.