CN114451038A - Uplink control information for uplink configuration grant transmission - Google Patents

Uplink control information for uplink configuration grant transmission Download PDF

Info

Publication number
CN114451038A
CN114451038A CN201980100866.0A CN201980100866A CN114451038A CN 114451038 A CN114451038 A CN 114451038A CN 201980100866 A CN201980100866 A CN 201980100866A CN 114451038 A CN114451038 A CN 114451038A
Authority
CN
China
Prior art keywords
uplink control
configuration
control information
transmission
channel
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
CN201980100866.0A
Other languages
Chinese (zh)
Inventor
C·罗萨
T·伦蒂拉
K·肖伯
陶涛
K·霍利
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 Solutions and Networks Oy
Original Assignee
Nokia Shanghai Bell Co Ltd
Nokia Solutions and 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 Solutions and Networks Oy filed Critical Nokia Shanghai Bell Co Ltd
Publication of CN114451038A publication Critical patent/CN114451038A/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/0091—Signaling for the administration of the divided path
    • H04L5/0094—Indication of how sub-channels of the path are allocated
    • 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
    • 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

Abstract

Embodiments of the present disclosure relate to uplink control information for uplink configuration grant transmission. According to an embodiment of the present disclosure, a network device sends a configuration of resource allocation to a terminal device. The terminal device determines resources for transmitting the CG-UCI on the uplink control channel. In this way, the collision probability on the physical resources carrying CGUCI is reduced and multiplexing of CG UCI information from one or more terminal devices with PUCCH transmitted by other terminal devices is achieved. Therefore, the reliability of UCI is improved and the latency of uplink CG transmission is reduced.

Description

Uplink control information for uplink configuration grant transmission
Technical Field
Embodiments of the present disclosure relate generally to communication technology and, more particularly, relate to a method, apparatus, and computer-readable medium for uplink control information in uplink configuration grant transmission.
Background
With the development of communication systems, new technologies have been proposed. For example, to increase utilization of periodically allocated resources, the communication system enables multiple devices to share the periodically allocated resources with a configuration authorization mechanism. The base station allocates configuration grant resources to a plurality of terminal devices, and when the terminal devices have data to transmit, they randomly utilize these resources. By allocating the configuration grant resources, the communication system eliminates packet transmission delays due to scheduling requests and scheduling procedures.
Disclosure of Invention
In general, embodiments of the present disclosure relate to a method and corresponding apparatus for uplink control information in uplink configuration grant transmission.
In a first aspect, a first device is provided. The first device comprises 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 first apparatus to: a configuration for configuring the grant uplink transmission is received from the second device. The configuration indicates at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring the grant uplink control information. The first device is caused to determine resources for sending configuration grant uplink control information on an uplink control channel based on the received configuration. The first device is caused to send configuration grant uplink control information to the second device on the determined resource with at least one of the transmission bursts.
In a second aspect, a second apparatus is provided. The second device comprises 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 second apparatus to: a configuration is generated regarding configuring the authorized uplink transmissions. The configuration indicates at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring the grant uplink control information. The second device is also caused to send a configuration regarding configuring the grant uplink transmission. The second device is further caused to receive configuration grant uplink control information from the first device on the resource with at least one of the transmission bursts.
In a third aspect, a method is provided. The method comprises receiving, at a first device, a configuration from a second device regarding configuring a granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring granted uplink control information. The method also includes determining resources for sending configuration grant uplink control information on an uplink control channel based on the received configuration. The method also includes sending configuration grant uplink control information to the second device on the determined resource with at least one of the transmission bursts.
In a fourth aspect, a method is provided. The method comprises the following steps: at the second device, a configuration is generated regarding configuring the granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on the uplink shared channel and a resource allocation for configuring the granted uplink control information. The method also includes sending a configuration to the first device regarding configuring the authorized uplink transmission. The method also includes receiving configuration grant uplink control information from the first device on the resource with at least one of the transmission bursts.
In a fifth aspect, an apparatus is provided. The apparatus comprises means for receiving, at a first device, a configuration from a second device regarding configuring a granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring granted uplink control information; means for determining resources for transmitting configuration grant uplink control information on an uplink control channel based on the received configuration; and means for transmitting configuration grant uplink control information to the second device on the determined resource with at least one of the transmission bursts.
In a sixth aspect, an apparatus is provided. The apparatus comprises means for generating, at a second device, a configuration for configuring a licensed uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring licensed uplink control information; means for sending a configuration to the first device regarding configuring the authorized uplink transmission; and means for receiving configuration grant uplink control information from the first device on the resource with at least one of the transmission bursts.
In a seventh aspect, a computer-readable medium is provided. The computer readable medium comprises program instructions for causing an apparatus to at least perform the method according to the third or fourth aspect described above.
It should be understood that the summary is not intended to identify key or essential features of embodiments of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Other features of the present disclosure will become readily apparent from the following description.
Drawings
Some example embodiments will now be described with reference to the accompanying drawings, in which:
fig. 1 shows a schematic diagram of a communication system according to an embodiment of the present disclosure;
FIG. 2 shows a schematic diagram of interactions between devices according to an embodiment of the present disclosure;
3A-3C illustrate schematic diagrams of resource allocation according to embodiments of the present disclosure;
FIG. 4 shows a flow diagram of a method according to an embodiment of the present disclosure;
FIG. 5 shows a flow diagram of a method according to an embodiment of the present disclosure;
FIG. 6 shows a flow diagram of a method according to an embodiment of the present disclosure;
FIG. 7 shows a simplified block diagram of an apparatus suitable for implementing embodiments of the present disclosure; and
fig. 8 illustrates a block diagram of an example computer-readable medium, in accordance with some example embodiments of the present disclosure.
Throughout the drawings, the same or similar reference numbers refer to the same or similar elements.
Detailed Description
The principles of the present disclosure will now be described with reference to a few exemplary embodiments. It is understood that these embodiments are described only for the purpose of illustration and to aid those skilled in the art in understanding and practicing the present disclosure, and do not set forth any limitations on the scope of the present disclosure. The disclosure described herein may be implemented in various other ways than those described below.
In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs.
References in the present disclosure to "one embodiment," "an example embodiment," etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
It will be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and, similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term "and/or" includes any and all combinations of one or more of the listed terms.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises," "comprising," "has," "having," "includes," and/or "including," when used herein, specify the presence of stated features, elements, and/or components, but do not preclude the presence or addition of one or more other features, elements, components, and/or groups thereof.
As used herein, the term "circuitry" may refer to one or more or all of the following:
(a) a purely hardware circuit implementation (such as an implementation in analog and/or digital circuitry only), and
(b) a combination of hardware circuitry and software, such as (as applicable):
(i) combinations of analog and/or digital hardware circuitry and software/firmware, and
(ii) a hardware processor with software (including a digital signal processor), software and any portion of memory that work together to cause a device (such as a mobile phone or server) to perform various functions, and
(c) a hardware circuit and/or a processor, such as a microprocessor or a portion of a microprocessor, that requires software (e.g., firmware) for operation, but may not be present when operation is not required.
The definition of circuitry applies to all uses of the term in this application, including in any claims. As another example, as used in this application, the term circuitry also encompasses implementations in hardware circuitry only or a processor (or multiple processors) or a portion of a hardware circuitry or a processor and its (or their) accompanying software and/or firmware. The term circuitry also encompasses (e.g., and if applicable to a particular claim element) a baseband integrated circuit or processor integrated circuit of a mobile device, or a similar integrated circuit in a server, a cellular network device, or other computing or network device.
As used herein, the term "communication network" refers to a network that conforms to any suitable communication standard, such as Long Term Evolution (LTE), LTE-advanced (LTE-a), Wideband Code Division Multiple Access (WCDMA), High Speed Packet Access (HSPA), narrowband internet of things (NB-IoT), New Radio (NR), and so forth. Further, communication between the terminal device and the network device in the communication network may be performed according to any suitable generation communication protocol, including, but not limited to, first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocols, and/or any other protocol now known or later developed. Embodiments of the present disclosure may be applied to various communication systems. Given the rapid development of communications, there will, of course, also be future types of communication technologies and systems that may be used to embody the present disclosure. The scope of the present disclosure should not be limited to the above-described systems.
As used herein, the term "network device" refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. A network device may refer to a Base Station (BS) or an Access Point (AP), e.g., a NodeB (NodeB or NB), evolved NodeB (eNodeB or eNB), NR NB (also known as gNB), Remote Radio Unit (RRU), Radio Head (RH), Remote Radio Head (RRH), relay, low power node (such as femto, pico), etc., depending on the terminology and technology applied.
The term "terminal device" refers to any terminal device capable of wireless communication. By way of example, and not limitation, a terminal device may also be referred to as a communication device, User Equipment (UE), Subscriber Station (SS), portable subscriber station, Mobile Station (MS), or Access Terminal (AT). End devices may include, but are not limited to, mobile phones, cellular phones, smart phones, voice over IP (VoIP) phones, wireless local loop phones, tablets, wearable end devices, Personal Digital Assistants (PDAs), portable computers, desktop computers, image capture end devices such as digital cameras, gaming end devices, music storage and playback devices, in-vehicle wireless end devices, wireless endpoints, mobile stations, laptop embedded devices (LEEs), laptop installed devices (LMEs), USB dongle (dongles), smart devices, wireless client devices (CPE), internet of things (IoT) devices, watches or other wearable devices, Head Mounted Displays (HMDs), vehicles, targets, medical devices and applications (e.g., tele-surgery), industrial devices and applications (e.g., robots and/or other wireless devices operating in industrial and/or automated processing chain environments, consumer electronics devices, devices operating on commercial and/or industrial wireless networks, and the like. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.
As described above, uplink transmission based on a Configuration Grant (CG) has been proposed. Mechanisms similar to the Uplink (UL) CG in unlicensed spectrum, known as Autonomous Uplink (AUL), are also supported in Long Term Evolution (LTE) Licensed Assisted Access (LAA).
The terminal device may indicate to the network device, along with each CG UL transmission, the selected HARQ process ID, new data indicator, redundancy version, UE ID, Physical Uplink Shared Channel (PUSCH) start and end points, and whether the UE-acquired Channel Occupancy Time (COT) may be shared with the network device.
The network device may provide HARQ feedback for AUL-enabled HARQ processes and transmit power commands to the terminal device via Downlink (DL) control signaling messages referred to as autonomous uplink downlink feedback information (AUL-DFI).
AUL also allows configuring a set of starting positions for a terminal device with a very fine raster (raster) within the first single carrier frequency division multiple access (SC-FDMA) symbol of a subframe: 16, 25, 34, 43, 52, or 61 microseconds after a subframe boundary, or at the beginning of the second symbol of a subframe. Since all terminal devices perform listen-before-talk operations prior to AUL transmission to determine whether the channel is idle, the different starting points allow, for example, prioritizing transmissions for certain terminal devices (by assigning earlier starting points) and reducing the number of collisions. The transmission within the first symbol is not PUSCH data, but rather a very long Cyclic Prefix (CP) extending from the next symbol # 2.
The CP extension is used to reserve a channel for a given terminal device by blocking other terminal devices. However, collisions on the AUL resources cannot always be avoided because only 7 starting positions are supported in the LAA-AUL and the terminal devices may not always be in each other's LBT sensing region (and thus they may not always block each other's transmissions).
Autonomous uplink-uplink control information (AUL-UCI) is multiplexed with UL-SCH data on the AUL-PUSCH resources in a manner similar to the case of Uplink Control Information (UCI) on PUSCH on licensed spectrum in LTE. UL-SCH data information and control information are multiplexed such that the AUL-UCI is mapped from symbol 1 to symbol 12 of the subframe, excluding symbols containing demodulation reference signals. More robust coding can be applied to the AUL-UCI (compared to the UL-SCH) while the data and control information share the same modulation order.
With a similar purpose to LAA AUL (reducing overhead of multiple LBT operations during handshaking between the network device and the terminal device associated with SR and UL grants), new radio unlicensed (NR-U) agrees to support configured grant-based UL transmissions.
In release-15 NR, a configuration grant based transmission is introduced. In NR CG operation, the network device semi-statically configures CG-PUSCH resources to the terminal device, and the terminal device may transmit PUSCH, or transmit data, on the CG-PUSCH resources when it has an uplink shared channel. In release-15 NR configuration grant based transmissions, the HARQ process Identifier (ID) is implicitly determined based on the resources configured for UL transmissions with a configuration grant. Further, when a repetition of the same Transport Block (TB) is introduced, a HARQ RV sequence is preconfigured. Due to the uncertainty of channel access, the fixed HARQ process ID determination (i.e., linking the HARQ ID with the allocated resources for the configured grant) has low HARQ process utilization efficiency in the unlicensed carrier.
In release-15 NR, Physical Uplink Control Channel (PUCCH) formats 0-4 are introduced. The format may be classified based on the supported UCI payload: PUCCH formats 0 and 1 are used to indicate 1 or 2 a/N bits plus SR, while PUCCH formats 2-4 support a larger UCI payload. Another way to classify the PUCCH format is based on the transmission duration: PUCCH formats 0 and 2 occupy 1 or 2 symbols, while PUCCH formats 1, 3, 4 occupy 4 to 14 symbols. In NR-U, PUCCH formats 0-3 are enhanced to support interleaved Physical Resource Block (PRB) allocation. Code-domain multiplexing may be introduced to the enhanced PUCCH formats 2 and 3 for NR-U.
PUCCH resources or resource groups comprising a set of resource elements and possibly code domain configurations such as cyclic shifts and/or orthogonal cover code indices are semi-statically configured. When there are a plurality of PUCCH resources from which the terminal device selects a PUCCH resource, selection of the PUCCH resource depends on the content of UCI and the size of UCI. For example, if the UCI includes HARQ-ACKs (with at least one HARQ-ACK received in response to a PDSCH with a corresponding PDCCH), a PUCCH resource set is selected based on the number of UCI bits. A terminal device may be configured with up to 4 PUCCH resource sets for UCI including HARQ-ACK, with a particular range of UCI payload sizes associated with each resource set. Selecting a PUCCH resource to use from the determined PUCCH resource set according to a PUCCH resource indicator included in the DL assignment downlink control information.
In another example, if the UCI includes CSI and HARQ-ACK associated with the PDSCH without a corresponding PDCCH, a PUCCH resource is selected from a list of configured CSI PUCCH resources based on the number of UCI bits. Selecting a minimum PUCCH resource that provides a sufficiently low code rate for the determined UCI payload.
In release-15 NR, PUCCH and PUSCH may be multiplexed in time within a single slot. However, concurrent transmission of PUCCH and PUSCH (i.e., symbols overlapping in time) within a single cell group (or concurrent transmission of multiple PUCCHs) is not supported. In case of simultaneous PUCCH and PUSCH transmission, UCI is typically multiplexed on the resources of PUSCH and PUCCH transmission is dropped.
In LAA-AUL, a network device typically configures CG-PUSCH resources to multiple terminal devices, and multiple terminal devices may transmit PUSCH simultaneously, and collision cannot be completely avoided despite LAA collision avoidance mechanism. In LAA-AUL, control information is multiplexed and interleaved with data, and it is impossible to apply an enhanced collision avoidance technique to control information (CG UCI) as compared to UL-SCH data. When a collision occurs on the UL CG resources, the collision affects the control information and data equally.
Although NR-U CG UCI is required for reception of NR-U CG-PUSCH, some CG-UCI fields (e.g. UE ID, HARQ process ID) are also important when reception of CG-PUSCH is destined to fail, e.g. due to collision. Therefore, it is beneficial to provide CG-UCI with a lower collision probability (or higher decoding probability) than CG-PUSCH.
According to an embodiment of the present disclosure, a network device sends a configuration of resource allocation to a terminal device. The terminal device determines resources for transmitting the CG-UCI on the uplink control channel. In this way, the collision probability on the physical resource carrying CG UCI is reduced, and multiplexing of CG UCI information from one or more terminal devices with PUCCHs transmitted by other terminal devices is achieved. Therefore, the reliability of UCI is improved and the latency of uplink CG transmission is reduced.
Fig. 1 shows a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented. Communication system 100, which is part of a communication network, includes device 110-1, device 110-2. The communication system 100 also includes a device 120. One or more devices are associated with and covered by a cell. It should be understood that the number of devices and cells shown in fig. 1 is given for illustrative purposes and does not imply any limitation. Communication system 100 may include any suitable number of devices and cells. In communication system 100, device 110 and device 120 may communicate data and control information with each other. In the case where device 110 is a terminal device and device 120 is a network device, the link from device 120 to device 110 is referred to as a Downlink (DL) and the link from device 110 to device 120 is referred to as an Uplink (UL). The number of devices shown in fig. 1 is given for illustrative purposes and does not imply any limitation.
Communications in communication system 100 may be implemented in accordance with any suitable communication protocol, including, but not limited to, first-generation (1G), second-generation (2G), third-generation (3G), fourth-generation (4G), and fifth-generation (5G), etc. cellular communication protocols, wireless local area network communication protocols such as Institute of Electrical and Electronics Engineers (IEEE)802.11, etc., and/or any other protocol currently known or developed in the future. Further, the communication may utilize any suitable wireless communication technology, including but not limited to: code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple Input Multiple Output (MIMO), Orthogonal Frequency Division Multiplexing Access (OFDMA) and/or any other technique now known or later developed.
Fig. 2 shows a schematic diagram of interactions 200 between devices according to an embodiment of the present disclosure. The interaction 200 may be implemented on any suitable device. For purposes of illustration only, interaction 200 is described as being implemented at terminal device 110-1 and network device 120. For illustration purposes only, the uplink control channel refers to PUCCH and the uplink shared channel refers to PUSCH.
Network device 120 generates 2005 a configuration for uplink control information transmission. The configuration indicates at least a resource allocation of a transmission burst on the uplink shared channel and a resource allocation for configuring the grant uplink control information. The configuration may indicate resources allocated to the terminal device for the shared channel and/or the control channel. The resources may be in the frequency domain. Alternatively or additionally, the resources may be in the time domain. The configuration may also include one or more of: duration of uplink transmission, cyclic shift, demodulation reference signal (DMRS) Orthogonal Cover Code (OCC). The duration of the uplink transmission may be configured by network device 120 or fixed in the standard. The term "transmission burst" as used herein may encompass one or more uplink transmissions. The uplink transmission may be an uplink shared channel transmission having a duration of at most one slot.
In some embodiments, network device 120 may determine the configuration based on whether other UCIs (in addition to CG-UCI, e.g., Channel State Information (CSI)) are to be transmitted by the terminal device.
Network device 120 sends 2010 the configuration to terminal device 110-1. In some embodiments, the configuration may be sent via Radio Resource Control (RRC) signaling. In other embodiments, the configuration may be sent via physical layer (PHY) signaling. For example, the configuration may be sent via CG activation signaling. In this way, the collision probability of CG-UCI is reduced, thereby increasing the probability that at least CG-UCI can be correctly decoded at the network device even if a collision occurs on UL CG resources for UL-SCH channel or data transmission. This improvement in CG UCI reliability may translate into latency reduction because, for example, it may enable a network device to schedule retransmissions on contention-free resources for the correct UE and HARQ process. Furthermore, the possibility of using different modulation orders for the data and control channels also supports a more reliable transmission of CG-UCI information.
Terminal device 110-1 determines 2025 resources for CG-UCI. In some embodiments, the CG-UCI may occupy one or more symbols in the time domain. In some embodiments, terminal device 110-1 may determine the transport format based on the configuration. Alternatively or additionally, terminal device 110-1 may determine 2015 a transmission format based on whether CG-PUSCH resources immediately follow a regular PUCCH occasion. The term "PUCCH" used herein refers to a PUCCH other than CG PUCCH. This may be determined based on a Group Common (GC) -PDCCH indicating the link direction within the COT and transmitted by network device 120 in one or more downlink slots/subframes prior to the PUCCH occasion. Alternatively, network device 120 may indicate the regular PUCCH occasion to terminal device 110-1 via dedicated signaling (e.g., in a DL grant).
In some embodiments, terminal device 110-1 may determine that the uplink control channel overlaps with the uplink shared channel according to a transmission mode. In this case, the resources for transmitting the CG-UCI on the uplink control channel may occupy N symbols of the uplink shared channel, followed by symbols of the uplink shared channel. In other words, the resources allocated to the uplink shared channel may include resources allocated to the uplink control channel, and the uplink shared channel is not mapped into N symbols reserved for the uplink control channel. The resources on the uplink control channel for CG-UCI may be one or more symbols in the PUSCH. For example, if the resource for PUSCH may include 14 symbols, the resource for CG-UCI on the uplink control channel may be the first one or two symbols of the 14 symbols.
As shown in fig. 3A, resources of a CG-PUCCH 3012-1 for transmitting a CG-UCI may be included in resources of a PUSCH 3013-1 in a transmission burst. Resources of the CG-PUCCH3012-2 for transmitting the CG-UCI may be included in resources for the PUSCH 3013-2.
As shown in fig. 3B, resources of a CG-PUCCH 3022-1 for transmitting CG-UCI may be included in resources of a PUSCH 3023-1 in a transmission burst. Resources of the CG-PUCCH 3022-2 for transmitting the CG-UCI may be included in resources for the PUSCH 3023-2.
In some embodiments, terminal device 110-1 may determine from the transmission mode that the uplink control channel does not overlap with the uplink shared channel. The resources allocated to the uplink shared channel may precede the resources allocated to the uplink control channel. For example, the resources for CG-UCI on the uplink control channel may be one or more symbols followed by resources comprising 14 symbols allocated to the uplink shared channel. As shown in fig. 3C, the resource of the CG-PUCCH 3032-1 for transmitting the CG-UCI may precede the resource of the PUSCH 3033-1.
In some embodiments, network device 120 may transmit 2020 an indication to transmit the resource configuring the authorized uplink control information. The indication may be sent via RRC signaling. In this case, terminal device 110-1 may determine 2025 resources based on the indication.
In some embodiments, network device 120 may determine information about the frequency domain configuration. Further, network device 120 may determine 2030 information regarding the code domain configuration. The information may include a cyclic shift. Alternatively or additionally, the information may include orthogonal cover codes for terminal device 110-1 configured with overlapping CG-PUCCH resources. RRC signaling may be used to indicate code domain resources for terminal device 110-1. Network device 120 may send 2035 the information to terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE specific.
Terminal device 110-1 may determine 2040 code domain resources based on the identity of terminal device 110-1. Alternatively or additionally, terminal device 110-1 may determine the 2040 code domain resources based on a cell radio network temporary identifier (C-RNTI) or a scrambling ID of the DMRS. For example, code domain resource derivation may be time-varying based on the slot index.
The terminal device 110-1 transmits 2050CG-UCI on the uplink control channel using the determined resources. In some embodiments, the CG-PUCCH occurs only prior to the first CG-PUSCH transmission of a consecutive CG-PUSCH transmission burst, and the CG-UCI may additionally be transmitted on the CG-PUSCH with each CG-PUSCH transmission in the burst. For example, terminal device 110-1 may transmit the first portion of the CG-UCI with the first transmission of the transmission burst on the uplink control channel. The first part of the CG-UCI may be common for transmission in one transmission burst. Terminal device 110-1 may transmit the second portion of CG-UCI with each transmission of a transmission burst on the uplink shared channel.
In some embodiments, as shown in FIG. 3A, terminal device 110-1 may perform listen before talk during 3011-1. Terminal device 110-1 may transmit the CG-UCI on CG-PUCCH 3012-1. Terminal device 110-1 may perform listen before talk during 3011-2 and transmit the CG-UCI on CG-PUSCH 3014-1. Terminal device 110-1 may perform listen before talk during 3011-3 and transmit the CG-UCI on CG-PUSCH 3014-2. The CG-UCI transmitted on the uplink control channel and the CG-UCI transmitted on the uplink shared channel may be different.
In some embodiments, terminal device 110-1 may perform listen before talk during 3031-1, as shown in FIG. 3C. Terminal device 110-1 may transmit the CG-UCI on CG-PUCCH 3032-1. Terminal device 110-1 may perform listen before talk during 3031-2 and transmit CG-UCI on CG-PUSCH 3034-1. Terminal device 110-1 may perform listen before talk during 3031-2 and transmit the CG-UCI on CG-PUSCH 3034-2. Terminal device 110-1 may perform listen before talk during 3031-3 and transmit the CG-UCI on CG-PUSCH 3034-3. The CG-UCI transmitted on the uplink control channel and the CG-UCI transmitted on the uplink shared channel may be different.
The CG-UCI transmitted on the CG-PUCCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUSCH may include HARQ related information associated with each CG-PUSCH transmission in a burst, such as a HARQ process ID, a New Data Indicator (NDI), and/or a Redundancy Version (RV).
In other embodiments, the CG-PUCCH may be present in each slot along with the CG-PUSCH. In this case, CG-PUCCH transmission is used to reduce collision probability of a portion of CG-UCI, while payload size of CG-UCI on CG-PUCCH is minimized. For example, terminal device 110-1 may transmit a first portion of the CG-UCI on an uplink control channel prior to a set of data bursts. Terminal device 110-1 may transmit the second portion of CG-UCI and the set of data bursts on the uplink shared channel.
As shown in fig. 3B, terminal device 110-1 may perform listen before talk during 3021-1. Terminal device 110-1 may transmit the CG-UCI on CG-PUCCH 3022-1. Terminal device 110-1 may perform listen before talk during 3021-2 and transmit the CG-UCI on CG-PUCCH 3022-2. Terminal device 110-1 may perform listen before talk during 3021-3 and transmit the CG-UCI on CG-PUSCH 3024-2. The CG-UCI transmitted on the uplink control channel and the CG-UCI transmitted on the uplink shared channel may be different.
The CG-UCI transmitted on the CG-PUSCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUCCH may include more critical information, such as HARQ process ID.
The terminal device 110-1 may multiplex CG-UCI. Terminal device 110-1 may transmit CG-PUSCH simultaneously with other PUSCHs on other cells. Terminal device 110-1 may transmit a normal UCI (i.e., non-CG) on the PUCCH, e.g., on another cell. In some embodiments, CG-PUCCH and CG-PUSCH are considered CG-PUSCH from a conventional UCI multiplexing perspective.
In some embodiments, terminal device 110-1 may multiplex UCI in overlapping PUCCH transmissions into one PUCCH resource (resource Z) for UCI multiplexing on PUSCH within a PUCCH group. Terminal device 110-1 may multiplex UCI not including resource Z into one PUSCH in priority (in order from high to low) as listed below, if Z overlaps with at least one PUSCH: the first priority: PUSCH with a-CSI, as long as it coincides with Z; the second priority is: the earliest PUSCH slot based on the start of the slot. If there are still multiple PUSCHs overlapping Z in the earliest PUSCH slot, follow the following third priority (sequentially from high to low): dynamically authorizing PUSCHs > CG-PUSCH or CG-PUCCH; fourth priority: PUSCH on serving cell with smaller serving cell index > PUSCH on serving cell with larger serving cell index; fifth priority: earlier PUSCH transmission > later PUSCH transmission.
In this way, the CG-UCI remains on the same cell and thus under the same LBT as the CG-PUSCH. This is advantageous because: CG-UCI is required for CG-PUSCH detection and is quite unnecessary if CG-PUSCH is not transmitted. The network device 120 does not need to blindly detect whether CG-UCI is multiplexed with UCI and transmitted on a scheduled PUSCH on some other cell.
Fig. 4 shows a flow diagram of a method 400 according to an embodiment of the present disclosure. Method 400 may be implemented at any suitable device. For example, the method may be implemented at terminal device 110.
At block 410, terminal device 110-1 receives a configuration from network device 120. In some embodiments, the configuration may be sent via RRC signaling. In other embodiments, the configuration may be sent via physical layer (PHY) signaling. For example, the configuration may be sent via CG activation signaling. The configuration indicates at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring grant uplink control information.
At block 420, terminal device 110-1 determines resources for CG-UCI. In some embodiments, the CG-UCI may occupy one or more symbols in the time domain. In some embodiments, terminal device 110-1 may determine the transport format based on the configuration. Alternatively or additionally, terminal device 110-1 may determine the transmission format based on whether a PUCCH occasion in the cell immediately follows a CG-PUSCH resource. This may be determined based on the GC-PDCCH sent by network device 120 in one or more downlink slots/subframes prior to the PUCCH occasion.
In some embodiments, terminal device 110-1 may determine from the transmission mode that the uplink control channel does not overlap with the uplink shared channel. In this case, the resource for transmitting the CG-UCI on the uplink control channel may be a plurality of symbols of the uplink shared channel followed by the uplink shared channel. In other words, the resources allocated to the uplink shared channel may include resources allocated to the uplink control channel, and the uplink shared channel is not mapped into N symbols reserved for the uplink control channel. The resources on the uplink control channel for CG-UCI may be one or more symbols in the PUSCH. For example, if the resource for PUSCH may include 14 symbols, the resource for CG-UCI on the uplink control channel may be the first one or two symbols of the 14 symbols.
In some embodiments, terminal device 110-1 may determine that the uplink control channel overlaps with the uplink shared channel according to a transmission mode. The resources allocated to the uplink shared channel may precede the resources allocated to the uplink control channel. For example, the resources for CG-UCI on the uplink control channel may be one or more symbols followed by resources comprising 14 symbols allocated to the uplink shared channel.
In some embodiments, terminal device 110-1 may receive an indication to transmit resources configuring the grant uplink control information. The indication may be sent via radio resource signaling. In this case, terminal device 110-1 may determine 2025 resources based on the indication.
Network device 120 may generate information regarding the code domain configuration and/or the frequency domain configuration. The information may include a cyclic shift. Alternatively or additionally, the information may include orthogonal cover codes for terminal device 110-1 configured with overlapping CG-PUCCH resources. RRC signaling may be used to indicate code domain resources for terminal device 110-1. Network device 120 may send 2035 the information to terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE specific.
Terminal device 110-1 may determine the code domain resources based on the identity of terminal device 110-1 and/or the DMRS scrambling ID assigned to the terminal device. Alternatively or additionally, terminal device 110-1 may determine 2040 code domain resources based on a cell radio network temporary identifier (C-RNTI). For example, code domain resource derivation may be time-varying based on the slot index.
Terminal device 110-1 may determine the frequency domain resources based on the identity of terminal device 110-1 and/or the DMRS ID assigned to the terminal device. Alternatively or additionally, terminal device 110-1 may determine 2040 frequency domain resources based on a cell radio network temporary identifier (C-RNTI).
At block 430, terminal device 110-1 transmits the CG-UCI using the determined resources on an uplink control channel. In some embodiments, the CG-PUCCH occurs only prior to the first CG-PUSCH transmission of a consecutive CG-PUSCH transmission burst, and CG-UCI may additionally be transmitted on the CG-PUSCH with each CG-PUSCH transmission in the burst. For example, terminal device 110-1 may transmit a first portion of the CG-UCI on an uplink control channel prior to a set of data bursts. The first part of the CG-UCI is common to the transmission groups in one transmission burst. Terminal device 110-1 may transmit the second portion of CG-UCI and the set of data bursts on the uplink shared channel. Terminal device 110-1 may transmit a first portion of CG-UCI with a first transmission of a transmission burst on an uplink control channel, the first portion of CG-UCI being common for transmission of one of the transmission bursts, and transmit a second portion of CG-UCI with each transmission of the transmission burst on an uplink shared channel.
The CG-UCI transmitted on the CG-PUCCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUSCH may include HARQ related information associated with each CG-PUSCH transmission in a burst, such as a HARQ process ID, a New Data Indicator (NDI), and/or a Redundancy Version (RV).
In other embodiments, the CG-PUCCH may be present in each slot along with the CG-PUSCH. In this case, CG-PUCCH transmission is used to reduce collision probability of a portion of CG-UCI, while payload size of CG-UCI on CG-PUCCH is minimized. For example, terminal device 110-1 may transmit a first portion of the CG-UCI on an uplink control channel prior to a set of data bursts. Terminal device 110-1 may transmit the second portion of CG-UCI and the set of data bursts on the uplink shared channel.
The CG-UCI transmitted on the CG-PUSCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUCCH may include more critical information, such as HARQ process ID.
Terminal device 110-1 may send configuration grant uplink control information on an uplink control channel prior to transmitting the burst. In some embodiments, terminal device 110-1 may send configuration grant uplink control information with the first transmission of the transmission burst.
The terminal device 110-1 may multiplex CG-UCI. Terminal device 110-1 may transmit CG-PUSCH simultaneously with other PUSCHs on other cells. Terminal device 110-1 may transmit a normal UCI (i.e., non-CG) on the PUCCH, e.g., on another cell. In some embodiments, CG-PUCCH and CG-PUSCH are considered CG-PUSCH from a regular UCI multiplexing perspective.
Fig. 5 shows a flow diagram of a method 500 according to an embodiment of the present disclosure. The method 500 may be merely an example of selecting resources for multiplexing the rule UCI with the GC-UCI. Method 500 may be implemented on any suitable device. For example, the method may be implemented at terminal device 110.
At block 510, terminal device 110-1 may determine whether terminal device 110-1 is configured with a CG-PUCCH. If terminal device 110-1 is configured with CG-PUCCH, terminal device 110-1 may determine whether to map the regular UCI onto slots of CG-PUSCH at block 520. If the normal UCI is not mapped onto slots of CG-PUSCH, terminal device 110-1 may transmit the CG on the CG-PUCCH at block 540.
If legacy UCI is mapped onto slots of CG-PUSCH, terminal device 110-1 may determine whether CG-PUCCH resources are of sufficient size at block 550. If the CG-PUCCH resources are of sufficient size, terminal device 110-1 may transmit the CG-UCI with the regular UCI appended thereto on the CG-PUCCH at block 560. If the CG-PUCCH resources do not have sufficient size, terminal device 110-1 may transmit the CG-UCI with the regular UCI appended thereto on the CG-PUCCH at block 570.
Referring to block 530, terminal device 110-1 may determine whether to map the regular UCI onto a slot of a CG-PUSCH if terminal device 110-1 is not configured with a CG-PUCCH. If the regular UCI is not mapped onto slots of CG-PUSCH, terminal device 110-1 may transmit the CG-UCI on the CG-PUSCH at block 580. If regular UCI is mapped onto slots of CG-PUSCH, terminal device 110-1 may transmit CG-UCI with the regular UCI appended thereto on CG-PUSCH at block 570.
Fig. 6 shows a flow chart of a method 600. Method 600 may be implemented at any suitable device. For example, the method may be implemented at network device 120.
At block 610, network device 120 generates a configuration for transmission of uplink control information. The configuration indicates at least a resource allocation for uplink transmission. The configuration may indicate resources allocated to the terminal device for the data channel and/or the control channel. The resources may be in the frequency domain. Alternatively or additionally, the resources may be in the time domain. The configuration may also include one or more of: duration of uplink transmission, cyclic shift, demodulation reference signal (DMRS) Orthogonal Cover Code (OCC). The duration of the uplink transmission may be configured by network device 120 or fixed in the standard. The configuration indicates at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring the grant uplink control information.
In some embodiments, the network device 120 may determine the configuration based on whether other UCI (in addition to CG-UCI, e.g., Channel State Information (CSI) is to be transmitted by the terminal device).
Network device 120 sends the configuration to terminal device 110-1 at block 620. In some embodiments, the configuration may be sent via radio resource control. In other embodiments, the configuration may be transmitted via physical layer (PHY) signaling. For example, the configuration may be sent via CG activation signaling. In this way, the collision probability of CG-UCI is reduced, thereby increasing the probability that at least CG-UCI can be correctly decoded at the network device even if a collision occurs on the UL CG resources for UL-SCH data transmission. This improvement in CG UCI reliability may translate into latency reduction because, for example, it may enable a network device to schedule retransmissions on contention-free resources for the correct UE and HARQ process. Furthermore, the possibility to use different modulation orders for data and control also supports a more reliable transmission of CG-UCI information.
In some embodiments, network device 120 may send an indication to send resources configuring the grant uplink control information. The indication may be sent via radio resource signaling.
In some embodiments, network device 120 may determine information about the code domain configuration. The information may include a cyclic shift. Alternatively or additionally, the information may include orthogonal cover codes for terminal device 110-1 configured with overlapping CG-PUCCH resources. RRC signaling may be used to indicate code domain resources for terminal device 110-1. Network device 120 may send information to terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE specific.
At block 630, the network device 120 receives the CG-UCI on the uplink control channel using the determined resources. In some embodiments, the CG-PUCCH occurs only before the first CG-PUSCH transmission of a consecutive CG-PUSCH transmission burst, and the CG-UCI may additionally be transmitted on the CG-PUSCH with each CG-PUSCH transmission in the burst. For example, the network device 120 may receive a first portion of the CG-UCI and a first transmission of the transmission burst on an uplink control channel. The first portion of the CG-UCI may be common to the transmission of one of the transmission bursts. The network device 120 may receive the second portion of the CG-UCI with each transmission of a transmission burst on the uplink shared channel.
The CG-UCI transmitted on the CG-PUCCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUSCH may include HARQ related information associated with each CG-PUSCH transmission in a burst, such as a HARQ process ID, a New Data Indicator (NDI), and/or a Redundancy Version (RV).
In other embodiments, the CG-PUCCH may be present in each slot along with the CG-PUSCH. In this case, CG-PUCCH transmission is used to reduce collision probability of a portion of CG-UCI, while payload size of CG-UCI on CG-PUCCH is minimized. For example, the network device 120 may receive a first portion of the CG-UCI on the uplink control channel prior to a group of data bursts. Network device 120 may receive the second portion of the CG-UCI and the set of data bursts on the uplink shared channel.
The CG-UCI transmitted on the CG-PUSCH may include one or more of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a number of uplink transmissions (e.g., a remaining duration of an uplink burst) by terminal device 110-1 in channel occupancy, or a configuration grant configuration according to which terminal device 110-1 should transmit. The CG-UCI transmitted on the CG-PUCCH may include more critical information, such as HARQ process ID.
In some embodiments, an apparatus (e.g., terminal device 110) for performing method 400 may include respective means for performing respective steps in method 400. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
In some embodiments, the apparatus includes means for receiving, at a first device from a second device, a configuration for configuring a granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring granted uplink control information; means for determining resources for transmitting configuration grant uplink control information on an uplink control channel based on the received configuration; and means for transmitting configuration grant uplink control information to the second device on the determined resource with at least one of the transmission bursts.
In some embodiments, the means for determining resources comprises: means for determining a transport format based on the received configuration; and means for selecting a resource from the resources allocated to the transmission burst on the uplink shared channel if it is determined that the uplink control channel overlaps the transmission format of the uplink shared channel.
In some embodiments, the means for determining resources comprises: means for determining a transport format based on the received configuration; and means for selecting a resource from previous resources allocated to transmission bursts on the uplink shared channel if it is determined that the uplink control channel does not overlap with the uplink shared channel in the transmission format.
In some embodiments, the means for selecting resources comprises: means for receiving, via radio resource control signaling, an indication to transmit resources configuring a grant uplink control information; and means for determining the resource based on the indication.
In some embodiments, the means for transmitting the configuration grant uplink control information comprises: means for transmitting a first portion of configuration grant uplink control information on an uplink control channel with a first transmission of a transmission burst, the first portion of configuration grant uplink control information being common to a transmission of one of the transmission bursts; and means for transmitting a second portion of the configuration grant uplink control information with each transmission of a transmission burst on the uplink shared channel.
In some embodiments, configuring the first portion of the grant uplink control information comprises at least one of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a remaining duration of an uplink transmission burst, or a configuration of a configuration granted uplink shared channel, and a second portion of the configuration granted uplink control information includes hybrid automatic repeat request (HARQ) -related information associated with the group of data bursts.
In some embodiments, the means for transmitting the configuration grant uplink control information comprises: means for transmitting a first portion of configuration grant uplink control information on an uplink control channel during a transmission burst; and means for transmitting a second portion of the configuration grant uplink control information on the uplink shared channel during the transmission burst.
In some embodiments, the first portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) -related information, and the second portion of the configuration grant uplink control information includes at least one of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a remaining duration of an uplink transmission burst, a configuration of a grant uplink shared channel.
In some embodiments, the means for transmitting the configuration grant uplink control information comprises: means for transmitting configuration grant uplink control information on an uplink control channel prior to transmitting the burst; or means for sending configuration grant uplink control information with the first transmission of the transmission burst.
In some embodiments, the apparatus further comprises means for receiving information about the frequency domain configuration from the second device via radio resource control signaling; means for determining a frequency domain configuration allocated to the first apparatus from the information based on at least one of: an identity of the first device and a demodulation reference signal scrambling identity; and multiplexing the configuration grant uplink control information on the uplink control channel based on the frequency domain configuration.
In some embodiments, the apparatus further comprises means for receiving information about the code domain configuration from the second device via radio resource control signaling; means for determining a code domain configuration allocated to the first device from the second information based on at least one of: an identity of the first device and a demodulation reference signal scrambling identity; and multiplexing the configuration grant uplink control information on an uplink control channel based on the code domain configuration.
In some embodiments, the first device comprises a terminal device and the second device comprises a network device.
In an embodiment, an apparatus (e.g., network device 120) for performing method 600 may include corresponding means for performing the corresponding steps in method 600. These components may be implemented in any suitable manner. For example, it may be implemented by a circuit or a software module.
In some embodiments, the apparatus includes means for generating, at the second device, a configuration for configuring the granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on the uplink shared channel and a resource allocation for configuring the granted uplink control information; means for sending a configuration to the first device regarding configuring the authorized uplink transmission; and means for receiving configuration grant uplink control information from the first device on the resource with at least one of the transmission bursts.
In some embodiments, the configuration indication configures a transport format of the grant uplink control information.
In some embodiments, the transport format indicates whether the uplink control channel overlaps with the uplink shared channel.
In some embodiments, the apparatus further comprises: means for generating an indication to transmit resources configuring a grant uplink control information; and means for transmitting the first information to the first device via radio resource control signaling.
In some embodiments, the means for receiving the configuration grant uplink control information comprises: means for receiving a first portion of configuration grant uplink control information on an uplink control channel with a first transmission of a transmission burst, the first portion of configuration grant uplink control information being common for transmission of one of the transmission bursts; and means for receiving a second portion of the configuration grant uplink control information with each transmission of a transmission burst on the uplink shared channel.
In some embodiments, configuring the first portion of the grant uplink control information comprises at least one of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a remaining duration of the uplink burst, or a configuration of a configuration granted uplink shared channel, and a second portion of the configuration granted uplink control information comprises hybrid automatic repeat request (HARQ) -related information associated with the transmission burst.
In some embodiments, the means for receiving the configuration grant uplink control information comprises: means for receiving a first portion of configuration grant uplink control information on an uplink control channel prior to transmission of a transmission burst; and means for receiving a second portion of the configuration grant uplink control information on the uplink shared channel during transmission of the transmission burst.
In some embodiments, the first portion of the configuration granted uplink control information comprises hybrid automatic repeat request (HARQ) -related information, and the second portion of the configuration granted uplink control information comprises at least one of: an identity of the first device, a Channel Access Priority Class (CAPC) of the first device, a listen before talk type, a duration of channel occupancy, an indication of whether the second device is allowed to share channel occupancy with the first device, a remaining duration of an uplink burst, a configuration of a grant uplink shared channel.
In some embodiments, the apparatus comprises means for receiving configuration grant uplink control information on an uplink control channel prior to transmitting the burst; or means for receiving configuration grant uplink control information with a first transmission of a transmission burst.
In some embodiments, the apparatus comprises means for generating information about a frequency domain configuration; and means for transmitting information to the first device via radio resource control signaling.
In some embodiments, the apparatus comprises means for generating information about a code domain configuration; and means for transmitting information to the first device via radio resource control signaling.
In some embodiments, the first device comprises a terminal device and the second device comprises a network device.
Fig. 7 is a simplified block diagram of a device 700 suitable for implementing embodiments of the present disclosure. Device 700 may be used to implement a communication device such as terminal device 110 or network device 120 shown in fig. 1. As shown, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processors 710, and one or more communication modules 740 coupled to the processors 710.
The communication module 740 is used for bidirectional communication. The communication module 740 has at least one antenna to facilitate communication. The communication interface may represent any interface required to communicate with other network elements.
The processor 710 may be of any type suitable for a local technology network, and may include, by way of non-limiting example, one or more of the following: general purpose computers, special purpose computers, microprocessors, Digital Signal Processors (DSPs), and processors based on a multi-core processor architecture. Device 700 may have multiple processors, such as an application specific integrated circuit chip that is time dependent from a clock synchronized to the main processor.
Memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memory include, but are not limited to, Read Only Memory (ROM)724, Electrically Programmable Read Only Memory (EPROM), flash memory, a hard disk, a Compact Disk (CD), a Digital Video Disk (DVD), and other magnetic storage and/or optical storage devices. Examples of volatile memory include, but are not limited to, Random Access Memory (RAM)722 and other volatile memory that does not persist for the duration of the power down.
The computer programs 730 include computer-executable instructions that are executed by the associated processor 710. The program 730 may be stored in, for example, the ROM 724. The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.
Embodiments of the disclosure may be implemented by the program 730 so that the device 700 may perform any of the processes of the disclosure as discussed with reference to fig. 2-6. Embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.
In some example embodiments, the program 730 may be tangibly embodied in a computer-readable medium, which may be included in the device 700 (such as in the memory 720) or other storage device accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium into the RAM 722 for execution. The computer readable medium may include any type of tangible, non-volatile memory, such as ROM, EPROM, flash memory, a hard disk, a CD, a DVD, etc. Fig. 8 shows an example of a computer readable medium 800 in the form of a CD or DVD. The computer readable medium has a program 630 stored thereon.
It should be understood that future networks may utilize Network Function Virtualization (NFV), which is a network architecture concept that proposes virtualizing network node functions as "building blocks" or entities that may be operatively connected or linked together to provide services. A Virtualized Network Function (VNF) may comprise one or more virtual machines running computer program code using standard or generic type servers instead of custom hardware. Cloud computing or data storage may also be used. In radio communication this may mean node operations to be performed at least partly in a central/centralized unit CU (e.g. a server, a host or a node) operatively coupled to a distributed unit DU (e.g. a radio head/node). Node operations may also be distributed among multiple servers, nodes, or hosts. It should also be understood that the labor distribution between core network operations and base station operations may vary depending on the implementation.
In one embodiment, the server may generate a virtual network through which the server communicates with the distributed elements. In general, virtual networking may involve the process of combining hardware and software network resources and network functions into a single software-based management entity (virtual network). Such a virtual network may provide flexible distribution of operations between the server and the wireless head/node. In fact, any digital signal processing task may be performed in a CU or DU, and the boundary at which responsibility is transferred between the CU and DU may be chosen depending on the implementation.
Thus, in one embodiment, a CU-DU architecture is implemented. In this case, the device 700 may be included in a central unit (e.g., control unit, edge cloud server, server) operatively coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., remote radio head/node). That is, the central unit (e.g., edge cloud server) and the distributed units may be independent devices that communicate with each other via a radio path or via a wired connection. Alternatively, they may be in the same entity communicating via a wired connection or the like. An edge cloud or edge cloud server may serve multiple distributed units or radio access networks. In one embodiment, at least some of the processes may be performed by a central unit. In another embodiment, the device 700 may instead be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit.
In one embodiment, the performance of at least some of the functions of the device 700 may be shared between two physically separated devices (DU and CU) forming one operational entity. It will thus be seen that the apparatus describes an operational entity comprising one or more physically separated devices for performing at least some of the described processes. In one embodiment, this CU-DU architecture may provide flexible operation distribution between CUs and DUs. In fact, any digital signal processing task may be performed in a CU or DU, and the boundary at which responsibility is transferred between the CU and DU may be chosen depending on the implementation. In one embodiment, the device 700 controls the execution of processes regardless of the location of the device and where the processes/functions are performed.
In general, the various embodiments of the disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. While various aspects of the embodiments of the disclosure are illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that the block diagrams, apparatus, systems, techniques or methods described herein may be implemented in hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.
The present disclosure also provides at least one computer program product tangibly stored on a non-transitory computer-readable storage medium. The computer program product includes computer-executable instructions, such as those included in program modules, that execute in a device on a target real or virtual processor to perform the method 400 described above with reference to fig. 3-6. Generally, program modules include routines, programs, libraries, objects, classes, components, data types, etc. that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed facility, program modules may be located in both local and remote memory storage media.
Program code for performing the methods of the present disclosure may be written in any combination of one or more programming languages. These program codes may be provided to a processor or controller of a general purpose computer, special purpose computer, or other programmable data processing apparatus, such that the execution of the program codes by the processor or controller causes the functions/operations specified in the flowchart and/or block diagram to be performed. The program code may execute entirely on the machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.
In the context of the present disclosure, computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform various processes and operations as described above. Examples of a carrier include a signal, computer readable medium, and the like.
The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination thereof. More specific examples of a computer-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In some cases, multitasking and parallel processing may be advantageous. Also, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure, but rather as descriptions of features that may be specific to particular embodiments. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the disclosure has been described in language specific to structural features and/or methodological acts, it is to be understood that the disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims (33)

1. A method, comprising:
receiving, at a first device, a configuration from a second device regarding configuring a licensed uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring licensed uplink control information;
determining, based on the received configuration, resources for transmitting the configuration grant uplink control information on an uplink control channel; and
transmitting the configuration grant uplink control information to the second device on the determined resource with at least one of the transmission bursts.
2. The method of claim 1, wherein determining the resource comprises:
determining a transport format based on the received configuration; and
selecting the resource from the resources allocated to the transmission burst on the uplink shared channel if it is determined that the uplink control channel overlaps with the uplink shared channel in the transmission format.
3. The method of claim 1, wherein determining the resource comprises:
determining a transport format based on the received configuration; and
selecting the resource from previous resources allocated to the transmission burst on the uplink shared channel if it is determined that the uplink control channel and the uplink shared channel do not overlap transmission formats.
4. The method of claim 3, wherein selecting the resource comprises:
receiving an indication of the resources for transmitting the configuration grant uplink control information via radio resource control signaling; and
determining the resource based on the indication.
5. The method of claim 2 or 3, wherein determining the transport format further comprises:
determining the transport format based on whether resources for uplink configuration grant transmission are after a regular Physical Uplink Control Channel (PUCCH) occasion.
6. The method of claim 1, wherein sending the configuration grant uplink control information comprises:
transmitting a first portion of the configuration grant uplink control information with a first transmission of a transmission burst on the uplink control channel, the first portion of the configuration grant uplink control information being common to the transmission of the transmission burst; and
transmitting a second portion of the configuration grant uplink control information with each transmission of the transmission burst on an uplink shared channel.
7. The method of claim 6, wherein the first portion of the configuration grant uplink control information comprises at least one of:
the identity of the first device is determined,
a Channel Access Priority Class (CAPC) of the first device,
the type of listening before speaking,
the duration of the channel occupancy is such that,
an indication as to whether the second device is allowed to share the channel occupancy with the first device,
the remaining duration of the uplink transmission burst, or
Configuring a grant uplink shared channel, an
The second portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) related information associated with the group of data bursts.
8. The method of claim 1, wherein sending the configuration grant uplink control information comprises:
transmitting a first portion of the configuration grant uplink control information on the uplink control channel prior to transmission of a transmission burst; and
transmitting a second portion of the configuration grant uplink control information on an uplink shared channel during the transmission of the transmission burst.
9. The method of claim 8, wherein the first portion of the configuration grant uplink control information comprises at least one of:
the identity of the first device is determined,
a hybrid automatic repeat request (HARQ) identification,
a Channel Access Priority Class (CAPC) of the first device,
the type of listening before speaking,
the duration of the channel occupancy is such that,
an indication as to whether the second device is allowed to share the channel occupancy with the first device,
the remaining duration of the uplink transmission burst, or
Configuring a configuration of a grant uplink shared channel; and
the second portion of the configuration grant uplink control information includes configuration grant uplink control information that is not included in the first portion or the entire configuration grant uplink control information.
10. The method of claim 1, wherein sending the configuration grant uplink control information comprises:
transmitting the configuration grant uplink control information on the uplink control channel prior to the transmission burst; or
Transmitting the configuration grant uplink control information with a first transmission of the transmission burst.
11. The method of claim 1, further comprising:
receiving information on a frequency domain configuration from the second device via radio resource control signaling;
determining a frequency domain configuration allocated to the first device from the information based on at least one of: an identity of the first device and a demodulation reference signal scrambling identity; and
multiplexing the configuration grant uplink control information on the uplink control channel based on the frequency domain configuration.
12. The method of claim 1, further comprising:
receiving information on a code domain configuration from the second device via radio resource control signaling;
determining a code domain configuration allocated to the first device from the information based on at least one of: an identity of the first device and a demodulation reference signal scrambling identity; and
multiplexing the configuration grant uplink control information on the uplink control channel based on the code domain configuration.
13. The method of claim 1, wherein the first device comprises a terminal device and the second device comprises a network device.
14. A method, comprising:
generating, at a second device, a configuration regarding configuring a granted uplink transmission, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring granted uplink control information;
sending the configuration for the configuration grant uplink transmission to a first device; and
receiving configuration grant uplink control information from the first device on a resource with at least one of the transmission bursts.
15. The method of claim 14, wherein the configuration indicates a transport format for the configuration grant uplink control information.
16. The method of claim 15, wherein the transport format indicates whether the uplink control channel resources overlap with resources configured for an uplink shared channel.
17. The method of claim 16, further comprising:
generating an indication of the resources for transmitting the configuration grant uplink control information; and
transmitting the first information to the first device via radio resource control (R C) signaling.
18. The method of claim 14, wherein receiving the configuration grant uplink control information comprises:
receiving a first portion of the configuration grant uplink control information on the uplink control channel with a first transmission of the transmission bursts, the first portion of the configuration grant uplink control information being common for transmission of one of the transmission bursts; and
receiving a second portion of the configuration grant uplink control information with each transmission of the transmission burst on an uplink shared channel.
19. The method of claim 18, wherein the first portion of the configuration grant uplink control information comprises at least one of:
the identity of the first device is determined,
a Channel Access Priority Class (CAPC) of the first device,
the type of listening before speaking,
the duration of the channel occupancy is such that,
an indication as to whether the second device is allowed to share the channel occupancy with the first device,
the remaining duration of the uplink transmission burst, or
Configuring a grant uplink shared channel, an
The second portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) related information associated with the group of data bursts.
20. The method of claim 14, wherein receiving the configuration grant uplink control information comprises:
receiving a first portion of the configuration grant uplink control information on the uplink control channel prior to transmission of a transmission burst; and
receiving a second portion of the configuration grant uplink control information on an uplink shared channel during the transmission of the transmission burst.
21. The method of claim 20, wherein the configuring the first portion of the grant uplink control information comprises:
the identity of the first device is determined,
a Channel Access Priority Class (CAPC) of the first device,
the type of listening before speaking,
the duration of the channel occupancy is such that,
an indication as to whether the second device is allowed to share the channel occupancy with the first device,
the remaining duration of the uplink transmission burst, or
Configuring a configuration of a grant uplink shared channel; and
the second portion of the configuration grant uplink control information includes the configuration grant uplink control information that is not included in the first portion or the entire configuration grant uplink control information.
22. The method of claim 14, wherein receiving the configuration grant uplink control information comprises:
receiving the configuration grant uplink control information on the uplink control channel before the transmission burst; or
Receiving the configuration grant uplink control information with a first transmission of the transmission burst.
23. The method of claim 14, further comprising:
generating information on a frequency domain configuration; and
transmitting the information to the first device via radio resource control signaling.
24. The method of claim 14, further comprising:
generating information on code domain configuration; and
transmitting the information to the first device via radio resource control signaling.
25. The method of claim 14, wherein the first device comprises a terminal device and the second device comprises a network device.
26. A first device, comprising:
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 first device to perform the method of any of claims 1-13.
27. A second device, 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 second apparatus to perform the method of any of claims 14-25.
28. A computer readable storage medium comprising program instructions stored thereon that, when executed by an apparatus, cause the apparatus to perform the method of any of claims 1-13.
29. A computer readable storage medium comprising program instructions stored thereon that, when executed by an apparatus, cause the apparatus to perform the method of any of claims 14-25.
30. An apparatus comprising means for performing the method of any of claims 1-13.
31. An apparatus comprising circuitry configured to cause the apparatus to perform the processes of any of claims 1-13.
32. An apparatus comprising means for performing the method of any of claims 14-25.
33. An apparatus comprising circuitry configured to cause the apparatus to perform the processes of any of claims 14-25.
CN201980100866.0A 2019-09-30 2019-09-30 Uplink control information for uplink configuration grant transmission Pending CN114451038A (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2019/109725 WO2021062800A1 (en) 2019-09-30 2019-09-30 Uplink control information for uplink configured grant transmission

Publications (1)

Publication Number Publication Date
CN114451038A true CN114451038A (en) 2022-05-06

Family

ID=75336767

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201980100866.0A Pending CN114451038A (en) 2019-09-30 2019-09-30 Uplink control information for uplink configuration grant transmission

Country Status (2)

Country Link
CN (1) CN114451038A (en)
WO (1) WO2021062800A1 (en)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116095842A (en) * 2023-04-06 2023-05-09 深圳国人无线通信有限公司 Method and device for multiplexing transmission resources of user terminal
CN117278975A (en) * 2023-11-20 2023-12-22 湖南湘邮科技股份有限公司 Wireless communication method and system between part label host and part label peripheral
WO2024012355A1 (en) * 2022-07-14 2024-01-18 华为技术有限公司 Communication method and apparatus

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2023211235A1 (en) * 2022-04-28 2023-11-02 엘지전자 주식회사 Method and device for transmitting and receiving configured grant pusch in wireless communication system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10182424B2 (en) * 2016-12-16 2019-01-15 Qualcomm Incorporated Techniques and apparatuses for configuring transmission of corresponding uplink control information in new radio
US10362593B2 (en) * 2017-09-01 2019-07-23 Huawei Technologies Co., Ltd. Grant-free uplink transmission in unlicensed spectrum
CN109788561B (en) * 2017-11-15 2021-06-01 华为技术有限公司 Method for transmitting control information, terminal equipment and network equipment
US11323227B2 (en) * 2017-11-17 2022-05-03 Qualcomm Incorporated Multiplexing of physical uplink shared channel (PUSCH) and physical uplink control channel (PUCCH) in uplink short burst transmission

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024012355A1 (en) * 2022-07-14 2024-01-18 华为技术有限公司 Communication method and apparatus
CN116095842A (en) * 2023-04-06 2023-05-09 深圳国人无线通信有限公司 Method and device for multiplexing transmission resources of user terminal
CN116095842B (en) * 2023-04-06 2023-08-15 深圳国人无线通信有限公司 Method and device for multiplexing transmission resources of user terminal
CN117278975A (en) * 2023-11-20 2023-12-22 湖南湘邮科技股份有限公司 Wireless communication method and system between part label host and part label peripheral
CN117278975B (en) * 2023-11-20 2024-01-30 湖南湘邮科技股份有限公司 Wireless communication method and system between part label host and part label peripheral

Also Published As

Publication number Publication date
WO2021062800A1 (en) 2021-04-08

Similar Documents

Publication Publication Date Title
CN109997405B (en) Method for performing random access channel procedure and user equipment thereof
US10999846B2 (en) Resource allocation in random access procedure
US11057872B2 (en) Method and device for transmitting uplink control information
US20200305189A1 (en) Method and apparatus for facilitating coexistence of 4th and 5th generation communication systems
JP6936253B2 (en) Resource instruction method and related devices and systems
EP3101982A1 (en) Base station, transmission method, mobile station, and retransmission control method
CN114451038A (en) Uplink control information for uplink configuration grant transmission
CN107295663B (en) Method and device for obtaining hybrid automatic repeat request acknowledgement information feedback
CN108702595B (en) Method and apparatus for performing uplink transmission
JP2022520589A (en) User equipment and systems that perform transmit and receive operations
KR20200007974A (en) Method and Device for Resizing Competitive Windows
CN104662978A (en) Resource allocation method and device
CN116744459A (en) Base station and user equipment for mobile communication system
KR102150368B1 (en) Uplink data transmission method and related device
WO2016184365A1 (en) Uplink scheduling method, apparatus, device and system
US20220201697A1 (en) Terminal and communication method
CN113518385A (en) Operations related to LBT procedures
CN114208076A (en) Sharing HARQ processes by multiple configuration grant resources
CN111436065B (en) Method and equipment for transmitting data and indicating data transmission
JP6590287B2 (en) Data transmission method and data transmission apparatus
US8099643B2 (en) Minimizing slot wastage using overlapping HARQ regions in OFDMA WiMAX system
AU2019474027B2 (en) Methods, devices and computer readable media for communication on unlicensed band
JP7444293B2 (en) Terminal device and method for the terminal device
JP2021100250A (en) Method and terminal for data transmission
EP4020857A1 (en) Resource conflict handling method and apparatus, terminal and storage medium

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