CN112369097A - Unified uplink control information for uplink transmission with configuration grant - Google Patents

Unified uplink control information for uplink transmission with configuration grant Download PDF

Info

Publication number
CN112369097A
CN112369097A CN201880095255.7A CN201880095255A CN112369097A CN 112369097 A CN112369097 A CN 112369097A CN 201880095255 A CN201880095255 A CN 201880095255A CN 112369097 A CN112369097 A CN 112369097A
Authority
CN
China
Prior art keywords
uci
urllc
embb
transmission
control information
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN201880095255.7A
Other languages
Chinese (zh)
Inventor
陶涛
刘建国
骆喆
孟艳
武卓
沈钢
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Shanghai Bell Co Ltd
Nokia Oyj
Nokia Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Shanghai Bell Co Ltd, Nokia Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Publication of CN112369097A publication Critical patent/CN112369097A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/20—Control channels or signalling for resource management
    • H04W72/21—Control channels or signalling for resource management in the uplink direction of a wireless link, i.e. towards the network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0048—Allocation of pilot signals, i.e. of signals known to the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L5/00—Arrangements affording multiple use of the transmission path
    • H04L5/003—Arrangements for allocating sub-channels of the transmission path
    • H04L5/0053—Allocation of signaling, i.e. of overhead other than pilot signals
    • H04L5/0055—Physical resource allocation for ACK/NACK
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1263—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows
    • H04W72/1268—Mapping of traffic onto schedule, e.g. scheduled allocation or multiplexing of flows of uplink data flows

Abstract

According to some embodiments, an apparatus includes at least one processor and at least one memory including computer program code. The at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to generate one or more of: at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The apparatus may also map one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by a network entity. The apparatus may also transmit the U-CG-UCI to at least one network entity.

Description

Unified uplink control information for uplink transmission with configuration grant
Technical Field
Certain embodiments may relate to a communication system. For example, some embodiments may relate to configuring grant uplink control information.
Background
In New Radios (NR), transmissions using a Configuration Grant (CG), such as unlicensed transmissions and autonomous transmissions, are specified to meet the stringent delay and reliability requirements of ultra-reliable low-delay communications (URLLC). For example, a 32 byte URLLC traffic may be required to have a 1 x 10 duration of 1ms-5The transmission of (2) is successful. UL transmissions with configured grants can meet the latency requirements of URLLC traffic by reducing the latency incurred by scheduling requests and Uplink (UL) grants for Physical Uplink Shared Channel (PUSCH) transmissions.
Both enhanced mobile broadband (eMBB) and URLLC traffic may be sent in unlicensed spectrum via UL transmissions with a configuration grant. The network entity may configure separate resource pools for the eMBB and URLLC, such as by introducing Logical Channel Priority (LCP) restrictions for resource allocation. However, to achieve higher flexibility and lower latency of URLLC, network resources may be wasted by limiting and prohibiting how the user equipment utilizes the configured resources (i.e., eMBB and URLLC). By using a common resource pool, the user equipment may send both eMBB and URLLC traffic in the same time slot. To illustrate this technique, fig. 1 shows an example of URLLC Transmit Blocks (TBs) and eMBB TBs multiplexed into a single slot.
Using current techniques, each TB may need to be associated with configuration grant uplink control information (CG-UCI) to indicate various data, such as hybrid automatic repeat request (HARQ) process identification, Resource Blocks (RBs), and New Data Indicators (NDIs). As shown in fig. 1, there may be two CG-UCI in each slot, one for the eMBB TB and the other for the URLLC TB. However, transmitting two separate UCI in one slot is very inefficient. Furthermore, transmitting two separate CG-UCIs may result in unreliable transmission performance, especially for CG-UCIs associated with eMBB TBs.
Disclosure of Invention
According to some embodiments, a method may include generating, by a user device, one or more of: at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The method may also include mapping, by the user equipment, one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by the network entity. The method may also include transmitting, by the user equipment, the U-CG-UCI to at least one network entity.
According to some embodiments, an apparatus may include means for generating one or more of at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The apparatus may also include means for mapping one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by a network entity. The apparatus may also include means for transmitting the U-CG-UCI to at least one network entity.
According to 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 may be configured, with the at least one processor, to cause the apparatus at least to generate one or more of at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to map one or more of 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 may also be configured to, with the at least one processor, cause the apparatus at least to transmit the U-CG-UCI to at least one network entity.
According to some embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, may perform a method. The method may generate one or more of at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The method may also map one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by the network entity. The method may also transmit the U-CG-UCI to at least one network entity.
According to some embodiments, a computer program product may perform a method. The method may generate one or more of at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The method may also map one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by the network entity. The method may also 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 Configuration Grant (CG) enhanced mobile broadband (eMBB) Transmit Block (TB) and at least one unified CG uplink control information (U-CG-UCI). The circuitry may also map one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by a network entity. The circuitry may also transmit the U-CG-UCI to at least one network entity.
According to 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 also include decoding, by the network entity, the at least one U-CG-UCI in one or more preconfigured locations. The method may also include receiving, by the network entity, at least one ultra-reliable low-latency communication (URLLC). The method may also include decoding, by the network entity, the at least one URLLC based on the uplink control information.
According to 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 also include means for decoding at least one U-CG-UCI in one or more preconfigured locations. The apparatus may also include means for receiving at least one ultra-reliable low latency communication (URLLC). The apparatus may also include means for decoding the at least one URLLC based on the uplink control information.
According to 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 may be configured to, with the at least one processor, cause the apparatus at least to 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 may also be configured to, with the at least one processor, cause the apparatus at least to decode the at least one U-CG-UCI in one or more preconfigured locations. The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to receive at least one ultra-reliable low latency communication (URLLC). The at least one memory and the computer program code may also be configured to, with the at least one processor, cause the apparatus at least to decode the at least one URLLC based on the uplink control information.
According to some embodiments, a non-transitory computer-readable medium may be encoded with instructions that, when executed in hardware, 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 also decode at least one U-CG-UCI in one or more preconfigured locations. The method may also receive at least one ultra-reliable low-latency communication (URLLC). The method may also decode the at least one URLLC based on the uplink control information.
According to 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 also decode at least one U-CG-UCI in one or more preconfigured locations. The method may also receive at least one ultra-reliable low-latency communication (URLLC). The method may also decode the at least one URLLC based on 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 also decode at least one U-CG-UCI in one or more preconfigured locations. The circuitry may also receive at least one ultra-reliable low-latency communication (URLLC). The circuitry may also decode the at least one URLLC based on the uplink control information.
Drawings
For a proper understanding of the present disclosure, reference should be made to the accompanying drawings, in which:
fig. 1 shows an example of eMBB and URLLC multiplexing within a UE.
Fig. 2 shows an example of two-stage U-CG-UCI preparation.
Fig. 3 shows an example of eMBB and URLLC resource configurations in CG time slots.
Fig. 4 shows an example of eMBB and URLLC resource configurations in CG time slots.
Fig. 5 illustrates an example of a signaling diagram in accordance with some embodiments.
Fig. 6 illustrates an example of a method performed by a user equipment according to some embodiments.
Fig. 7 illustrates an example of a method performed by a network entity, in accordance with certain embodiments.
FIG. 8 illustrates an example of a system according to some embodiments.
Detailed Description
Certain embodiments described herein may have various benefits and/or advantages. For example, some embodiments may minimize signaling overhead associated with multiple types of transport blocks multiplexed in the same configured grant resource. In addition, certain embodiments may improve control signaling performance when transport block puncturing occurs. Some embodiments provide a multi-stage data preparation and single-shot transmission mechanism to facilitate U-CG-UCI transmission while also reducing the resources required for decoding by a network entity. Accordingly, certain embodiments are directed to improvements in computer-related technology, particularly by conserving network resources and reducing power consumption of network entities and/or user equipment located in a network.
Uplink Control Information (UCI) may be associated with one type of TB transmitted in a UL configuration grant resource such as a slot. As an example, the type of TB may be eMBB, URLLC TB, and/or mtc TB. To support multiple types of TB transmission in the same CG resource, the U-CG-UCI may contain two types of information: common information of a plurality of types of TBs, and TB type specific information.
The common information may include channel access related information, ACK/NACK feedback for DL transmission, Channel State Indication (CSI) feedback, and/or scheduling requests. In addition, the TB type specific information may include HARQ related information such as HARQ process ID, RV, and/or NDI. In addition, the content of the U-CG-UCI may vary according to TB multiplexing in CG resources. For example, a signal indicating TB multiplexing situation may be introduced in the U-CG-UCI.
The U-CG-UCI may contain uplink control information for more than one transmitting TB. In addition, the user equipment can adapt the information in the U-CG-UCI according to the TB multiplexing condition in the configuration authorized resource. The transmission scheme for U-CG-UCI may include multi-stage data preparation as well as single shot transmission, detection and decoding.
For multi-stage U-CG-UCI preparation, if multiple types of TB transmissions with configuration grants support UL resources such as slots, the user equipment may prepare U-CG-UCI for slots in multiple stages. When the U-CG-UCI is transmitted on the PUSCH, data of the U-CG-UCI may be prepared together with the PUSCH data. However, the data preparation timeline may vary by traffic type. When and how to prepare common control information for multiple types of TBs becomes a problem. Therefore, a multi-stage data preparation mechanism may be used for U-CG-UCI.
In a first phase, the user equipment may prepare a first transmission TB, such as an eMBB TB or multiple TBs, from the traffic in the buffer and the corresponding U-CG-UCI. The U-CG-UCI may be mapped to a predefined location. For example, the predefined location may be in an overlapping resource of potentially multiple TBs configured for transmission. Alternatively, the predefined location may be in the first few symbols of the configuration grant slot.
Furthermore, in the second phase, if another type of traffic (such as higher priority data) arrives in the buffer and the user equipment decides to send another TB (such as URLLC TB) on the same configured grant slot, the user equipment may prepare a new U-CG-UCI at a second point in time. Specifically, the user equipment may prepare TBs for higher priority services. The new U-CG-UCI may contain information needed by the old TB and the new TB, which may be transmitted in the same configured grant slot. The new U-CG-UCI may also be located at a predefined location. Fig. 2 shows 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 resources, the user equipment may enter a third and subsequent stages to prepare a new U-CG-UCI and a corresponding new TB. Although the preparation of the U-CG-UCI may occur in multiple stages, the actual transmission of the U-CG-UCI may occur only once for configuring the granted resources. The network entity may detect and decode the U-CG-UCI only at the pre-configured location. The configuration of the U-CG-UCI may be predefined by the network or may be indicated by RRC signaling from a network entity. The configuration may also include the structure of the U-CG-UCI, the location of the U-CG-UCI transmission, and/or other parameters.
Fig. 3 shows an example of eMBB and URLLC resources configured in CG time slots. The eMBB and URLLC traffic may be configured to be sent via UL transmissions with configuration grants. The configured UL CG resources may be used for both eMBB traffic and URLLC traffic. For example, the entire CG slot may be used for eMBB traffic transmission, while a portion of the resource elements in the CG slot are valid for URLLC traffic transmission. As shown in fig. 3, the potential URLLC resources may be configured as symbols.
Fig. 4 shows a U-CG-UCI that can be used in case of a more flexible CG URLLC resource allocation. There may be multiple transmission opportunities for URLLC traffic in CG slots. Multiple transmission opportunities may also reduce the transmission delay of URLLC traffic. In this example, there may be seven potential URLLC transmission opportunities in a CG slot. The user equipment may use any one or some of these time slots to perform URLLC transmissions.
Fig. 5 shows an example of a signaling diagram illustrating communication between a User Equipment (UE)530 and a Network Entity (NE) 540. The UE 530 may be similar to the UE 810 as shown in fig. 8. Likewise, NE540 may be similar to NE 820 also shown in fig. 8.
In step 501, the UE 530 may generate at least one CG eMBB TB and/or at least one U-CG-UCI. In step 503, the UE 530 may map at least one U-CG-UCI to a pre-configured resource. Additionally and/or alternatively, the UE 530 may rate match the eMBB TB.
In step 505, UE 530 may receive URLLC traffic. In step 507, the UE 530 may prepare at least one URLLC TB. Alternatively or additionally, the UE 530 may map at least one URLLC TB to at least one URLLC resource in at least one CG slot.
In step 509, the UE 530 may puncture at least one eMBB TB using a URLLC TB. In step 511, the UE 530 may transmit at least one U-CG-UCI. In step 513, NE540 may interpret the control information for the eMBB and/or URLLC.
In step 515, the NE540 may decode at least one eMBB TB based on the control information. In step 517, NE540 may monitor for receipt of URLLC. In step 519, UE 530 may send URLLC to NE 540. In step 521, the NE540 may decode at least one URLLC TB according to the received U-CG-UCI.
Fig. 6 illustrates an example of a method performed by a user equipment according to some embodiments. In step 601, the 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 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, in accordance with certain embodiments. In step 701, a network entity may receive at least one U-CG-UCI. In step 703, the network entity may interpret the control information for the eMBB and/or URLLC. In step 705, the network entity may decode at least one eMBB TB based on 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 some embodiments. In one embodiment, the system may include multiple devices, such as user equipment 810 and/or network entity 820.
User device 810 may include one or more of the following: a mobile device (such as a mobile phone, a smart phone, a Personal Digital Assistant (PDA), a tablet computer, or a portable media player), a digital camera, a camcorder, a video game player, a navigation unit (such as a Global Positioning System (GPS) device), a desktop or portable computer, a 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 a new wireless node b (gnb), a serving gateway, a server, and/or any other access node or combination thereof. Further, the network entity 810 and/or the user equipment 820 may be one or more of a citizen broadband radio service device (CBSD).
One or more of these devices may include at least one processor, represented as 811 and 821, respectively. Processors 811 and 821 may be embodied by any computing or data processing device, such as a Central Processing Unit (CPU), Application Specific Integrated Circuit (ASIC), or similar device. The processor may be implemented as a single controller or as multiple controllers or processors.
At least one memory may be provided in one or more of the devices indicated by 812 and 822. The memory may be fixed or removable. The memory may include computer program instructions or computer code embodied therein. The 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 memory may be combined as the processor on a single integrated circuit, or may be separate from the one or more processors. Furthermore, the computer program instructions stored in the memory and processable by the processor may be computer program code in any suitable form, such as a compiled or interpreted computer program written in any suitable programming language. The memory may or may not be removable.
Processors 811 and 821 and memories 812 and 822, or a subset thereof, may be configured to provide modules corresponding to the various blocks of fig. 1-7. Although not shown, the device may also include positioning hardware, such as GPS or micro-electromechanical systems (MEMS) hardware, which may be used to determine the position of the device. Other sensors to determine position, altitude, orientation, etc. are also contemplated and may be included, such as a barometer, compass, etc.
As shown in fig. 8, transceivers 813 and 823 may be provided, and one or more of the devices may further include at least one antenna, denoted 814 and 824, respectively. The device may have many antennas, such as an antenna array configured for multiple-input multiple-output (MIMO) communication or multiple antennas for multiple radio access technologies. For example, other configurations of these devices may be provided. Transceivers 813 and 823 may be transmitters, receivers, or both transmitters and receivers, or may be units or devices configured for both transmission and reception.
The memory and computer program instructions may be configured to, with the processor for a particular device, cause a hardware device, such as a user device, to perform any of the processes described below (e.g., see fig. 1-7). Thus, 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, some embodiments may be implemented entirely in hardware.
In some embodiments, an apparatus may include circuitry configured to perform any of the processes or functions illustrated in fig. 1-7. For example, the circuitry may be hardware-only circuit implementations, such as analog and/or digital circuitry. In another example, the circuitry may be a combination of hardware circuitry and software, such as a combination of analog and/or digital hardware circuitry and software or firmware, and/or a hardware processor with software (including a digital signal processor), software, and any portion of at least one memory that work together to cause an apparatus to perform various processes or functions. In yet another example, the circuitry may be hardware circuitry and/or a processor, such as a microprocessor or a portion of a microprocessor, including software, such as operating firmware. Software in the circuitry may not be present when hardware operation is not required.
The features, structures, or characteristics of some embodiments described throughout this specification may be combined in any suitable manner in one or more embodiments. For example, throughout the specification, use of the phrases "certain embodiments," "some embodiments," "other embodiments," or other similar language refers to the fact that: the particular features, structures, or characteristics described in connection with the embodiment may be included in at least one embodiment of the invention. Thus, appearances of the phrases "in certain embodiments," "in some embodiments," "in other embodiments," or other similar language throughout this specification do 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 of ordinary skill in the art will readily appreciate that certain embodiments discussed above may be implemented with a different order of steps and/or with differently configured hardware elements than those disclosed. Accordingly, it will be apparent to those skilled in the art that certain modifications, variations, and alternative constructions will be apparent, while remaining within the spirit and scope of the invention. Therefore, to ascertain the scope of the invention, the following claims should be referenced.
Part of the vocabulary
3 GPP: third generation partnership project
5G: fifth generation wireless system
CG: configuration authorization
CG-UCI: configuring authorized UCI
COT: channel occupancy time
CSI: channel state indication
DL: downlink link
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: logical channel priority
MCS: modulation order and coding scheme
mMTC: large scale machine type communication
And g NB: next generation node B
TBS: transport block size
UCI: UL control information
UE: user equipment
UL: uplink link
URLLC: ultra-reliable low latency communication
RRC: radio resource control
SR: scheduling requests
TB: transmission block

Claims (26)

1. 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:
generating one or more of: at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transport Block (TB) and at least one unified CG uplink control information (U-CG-UCI);
mapping one or more of the at least one CG eMBB and the at least one U-CG-UCI to at least one resource configured by a network entity; and
transmitting the U-CG-UCI to at least one network entity.
2. The apparatus of claim 1, wherein the U-CG-UCI comprises at least a common field region and a transport block type specific field region,
wherein the common field region comprises 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 transport block type specific field region is 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) start and end position.
3. The apparatus of claim 1 or 2, wherein a length of the U-CG-UCI is associated with the network entity configuration, and wherein the network entity configuration defines at least the length of the U-CG-UCI as a variable length or a predetermined length.
4. The apparatus of any of claims 1 to 3, wherein the at least one resource is one or more of:
at least one overlapping region configured for ultra-reliable low-latency communication (URLLC) CG transmission and eMBB CG transmission;
at least one resource within a URLLC transmission; and
at least a first predetermined number of symbols of the grant slot are configured.
5. The apparatus of any of claims 1-4, wherein the U-CG-UCI is an uplink transmission configured to send one or more of eMBB traffic and URLLC traffic.
6. The apparatus of any of claims 1-5, wherein at least a portion of a CG time slot is used for eMBB traffic transmission.
7. 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.
8. The apparatus of 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:
generating at least one CG URLLC TB in the at least one pre-allocated CG URLLC resource; and
rate matching at least one CG URLLC TB associated with at least one U-CG-UCI.
9. The apparatus of 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:
generating at least one CG eMBB TB in at least one pre-allocated CG eMBB resource; and
rate matching at least one CG eMBB TB associated with the at least one U-CG-UCI and CG URLLC TB.
10. The apparatus of 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:
receiving URLLC service; and
generating at least one U-CG-UCI in response to receiving the URLLC traffic,
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.
11. 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:
receiving at least one unified CG uplink control information (U-CG-UCI) associated with the uplink control information;
decoding the at least one U-CG-UCI in one or more preconfigured locations;
receiving one or more of: at least one enhanced mobile broadband (eMBB) and at least one ultra-reliable low latency communication (URLLC); and
decoding the one or more of the at least one eMBB and the at least one URLLC based on the uplink control information.
12. A method, comprising:
generating, by a user equipment, one or more of: at least one Configuration Grant (CG) enhanced mobile broadband (eMBB) Transport 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 the 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.
13. The method of claim 12, wherein the U-CG-UCI includes at least a common field region and a transport block type specific field region,
wherein the common field region comprises 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 transport block type specific field region is 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) start and end position.
14. The method of claim 12 or 13, wherein a length of the U-CG-UCI is associated with the network entity configuration, and wherein the network entity configuration defines at least the length of the U-CG-UCI as a variable length or a predetermined length.
15. The method of any of claims 12 to 14, wherein the at least one resource is one or more of:
at least one overlapping region configured for ultra-reliable low-latency communication (URLLC) CG transmission and eMBB CG transmission;
at least one resource within a URLLC transmission; and
at least the first few symbols of the grant slot are configured.
16. The method of any of claims 12-15, wherein the U-CG-UCI is an uplink transmission configured to send one or more of eMBB traffic and URLLC traffic.
17. The method of any of claims 12-16, wherein at least a portion of a CG slot is used for eMBB traffic transmission.
18. 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.
19. The method of any of claims 12 to 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.
20. The method of any of claims 12 to 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.
21. The method of any of claims 12 to 20, further comprising:
receiving, by the user equipment, URLLC traffic; and
generating, by the user equipment, at least one U-CG-UCI in response to receiving URLLC traffic,
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.
22. 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 preconfigured 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 on the uplink control information.
23. A non-transitory computer-readable medium encoding instructions that, when executed in hardware, perform the processes of any of claims 1-22.
24. An apparatus comprising means for performing a process according to any one of claims 1 to 22.
25. An apparatus comprising circuitry configured to cause the apparatus to perform the process of any of claims 1-22.
26. A computer program product encoded with instructions for performing a process according to any of claims 1-22.
CN201880095255.7A 2018-07-03 2018-07-03 Unified uplink control information for uplink transmission with configuration grant Pending CN112369097A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/094339 WO2020006687A1 (en) 2018-07-03 2018-07-03 Unified uplink control information for uplink transmission with configured grant

Publications (1)

Publication Number Publication Date
CN112369097A true CN112369097A (en) 2021-02-12

Family

ID=69060551

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201880095255.7A Pending CN112369097A (en) 2018-07-03 2018-07-03 Unified uplink control information for uplink transmission with configuration grant

Country Status (2)

Country Link
CN (1) CN112369097A (en)
WO (1) WO2020006687A1 (en)

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2021213606A1 (en) * 2020-04-20 2021-10-28 Nokia Technologies Oy Use of priority mismatch indication for uplink transmission for wireless networks
CN115669160A (en) * 2020-07-31 2023-01-31 Oppo广东移动通信有限公司 HARQ process determination method, device, equipment and medium
WO2022029273A1 (en) * 2020-08-06 2022-02-10 Sony Group Corporation Uplink control information related to configured grants
US20230328785A1 (en) * 2020-08-07 2023-10-12 Lenovo (Beijing)Limited Method and apparatus for channel access
CN116321492A (en) * 2020-08-26 2023-06-23 Oppo广东移动通信有限公司 Method for configuring authorized CG resource, terminal equipment and network equipment
CN114285534A (en) * 2020-09-28 2022-04-05 维沃移动通信有限公司 Transmission information determining method, device and terminal
WO2022240325A1 (en) * 2021-05-11 2022-11-17 Telefonaktiebolaget Lm Ericsson (Publ) Pre-configured allocation with multiple traffic types
US11690047B2 (en) 2021-06-09 2023-06-27 Qualcomm Incorporated Methods and apparatus for configuring intra-slot time-division multiplexed transport blocks
CN115589609A (en) * 2021-07-05 2023-01-10 索尼集团公司 Electronic device, method, and storage medium for wireless communication system

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102687455A (en) * 2010-01-08 2012-09-19 诺基亚西门子通信公司 Uplink control information transmission
GB201700108D0 (en) * 2017-01-05 2017-02-22 Tcl Communication Ltd Methods and devices for downlink resource sharing between URLLC and eMBB transmissions in wireless communication systems
US20170332359A1 (en) * 2016-05-11 2017-11-16 Convida Wireless, Llc Radio Download Control Channel
CN107734676A (en) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 A kind of method and apparatus of data transfer

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2009157184A1 (en) * 2008-06-24 2009-12-30 パナソニック株式会社 Mimo transmitting apparatus, mimo receiving apparatus, mimo transmission signal formation method, and mimo transmission signal separation method
CN101615986A (en) * 2008-06-27 2009-12-30 华为技术有限公司 A kind of data transmission method, device and communication system
WO2016064048A1 (en) * 2014-10-21 2016-04-28 Lg Electronics Inc. Method for monitoring downlink control channel in wireless communication system and apparatus for the same

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102687455A (en) * 2010-01-08 2012-09-19 诺基亚西门子通信公司 Uplink control information transmission
US20170332359A1 (en) * 2016-05-11 2017-11-16 Convida Wireless, Llc Radio Download Control Channel
CN107734676A (en) * 2016-08-12 2018-02-23 中兴通讯股份有限公司 A kind of method and apparatus of data transfer
GB201700108D0 (en) * 2017-01-05 2017-02-22 Tcl Communication Ltd Methods and devices for downlink resource sharing between URLLC and eMBB transmissions in wireless communication systems

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "R1-1806014 "UCI Transmission for URLLC"", 3GPP TSG_RAN\\WG1_RL1, no. 1, pages 1 - 2 *
HUAWEI等: "UCI piggyback on PUSCH for URLLC", 《3GPP TSG RAN WG1 MEETING #92BIS R1-1804290》, pages 1 - 10 *

Also Published As

Publication number Publication date
WO2020006687A1 (en) 2020-01-09

Similar Documents

Publication Publication Date Title
CN112369097A (en) Unified uplink control information for uplink transmission with configuration grant
US11233551B2 (en) Dynamically enabling and disabling multiplexing of HARQ-ACK feedback for different types of traffic
CN110035550B (en) Uplink control information transmission method and communication device
WO2020063611A1 (en) Two-stage design for new radio (nr) sidelink control information (sci)
US11743868B2 (en) Short physical uplink shared channel arrangement
EP4013161A1 (en) Data transmission method and device
JP5718452B2 (en) Control information transmission / reception method based on spatial multiplexing gain
US20200053528A1 (en) Multiplexing of physical sidelink control channel (pscch) and physical sidelink shared channel (pssch)
CN111436128A (en) Method and communication device for transmitting uplink information
CN114208320B (en) Method and apparatus for hybrid automatic repeat request process
US11394504B2 (en) Method and apparatus for uplink transmission
CN108631929B (en) Data transmission method and device
CN112583558A (en) Resource allocation method, terminal equipment and network equipment
CN112398579A (en) Method for sending and receiving downlink feedback information
CN108809496B (en) Information processing method and equipment
CN109088702B (en) Communication method, network equipment and terminal
EP3595220A1 (en) Method and apparatus for sending and receiving feedback information
US10568078B2 (en) User equipment and base station
CN113472489A (en) Information transmission method, device and system
CN110730513B (en) Communication method and device
WO2018201984A1 (en) Data transmission method and device
CN112187401B (en) Multi-time unit transmission method and related device
CN104753654A (en) HARQ feedback information coding and decoding method, device and system
CN108632885B (en) Method for sending buffer status report, terminal equipment and network equipment
CN111435847A (en) Method and device for transmitting information

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination