Uplink control information for uplink configuration grant transmission

Abstract

Embodiments of the present disclosure relate to uplink control information for uplink configuration authorization 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 the resources for sending CG‑UCI on an uplink control channel. In this way, the probability of collision on the physical resources carrying CUGCI is reduced, and multiplexing of CG UCI information from one or more terminal devices with PUCCH sent by other terminal devices is achieved. Therefore, the reliability of UCI is improved and the waiting time for uplink CG transmission is reduced.

Description

Technical Field

[0001] Embodiments of the present disclosure generally relate to communication technology, and more particularly, to methods, devices, and computer-readable media for uplink control information in uplink configuration grant transmission. Background Art

[0002] As communication systems develop, new technologies have been proposed. For example, in order to increase the utilization of periodically allocated resources, communication systems enable multiple devices to share periodic resources allocated using a configuration grant mechanism. The base station allocates configuration grant resources to multiple terminal devices, and when the terminal devices have data to send, they utilize these resources randomly. By allocating configuration grant resources, the communication system eliminates packet transmission delays caused by scheduling requests and scheduling processes. Summary of the invention

[0003] Generally speaking, embodiments of the present disclosure relate to a method and corresponding apparatus for uplink control information in uplink configuration grant transmission.

[0004] In a first aspect, a first device is provided. The first device includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to: receive a configuration about configuring an authorized uplink transmission from a second device. The configuration indicates at least resource allocation for a transmission burst on an uplink shared channel and resource allocation for configuring authorized uplink control information. The first device is caused to determine resources for sending the configuration authorized uplink control information on an uplink control channel based on the received configuration. The first device is caused to send the configuration authorized uplink control information to the second device on the determined resources together with at least one transmission burst in the transmission burst.

[0005] In a second aspect, a second device is provided. The second device includes at least one processor; and at least one memory including computer program code; the at least one memory and the computer program code are configured to, with the at least one processor, cause the second device to: generate a configuration for configuring an authorized uplink transmission. The configuration at least indicates resource allocation for a transmission burst on an uplink shared channel and resource allocation for configuring authorized uplink control information. The second device is also caused to send a configuration for configuring authorized uplink transmission. The second device is also caused to receive configuration authorized uplink control information from the first device on a resource together with at least one transmission burst in the transmission burst.

[0006] In a third aspect, a method is provided. The method includes receiving, at a first device, a configuration for configuring an authorized uplink transmission from a second device, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring authorized uplink control information. The method also includes determining, based on the received configuration, resources for sending the configured authorized uplink control information on an uplink control channel. The method also includes sending the configured authorized uplink control information to the second device on the determined resources together with at least one transmission burst in the transmission burst.

[0007] In a fourth aspect, a method is provided. The method includes: generating, at a second device, a configuration for configuring an authorized 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 authorized uplink control information. The method also includes sending the configuration for configuring the authorized uplink transmission to a first device. The method also includes receiving the configured authorized uplink control information from the first device on a resource together with at least one transmission burst in the transmission burst.

[0008] In a fifth aspect, an apparatus is provided. The apparatus includes a component for receiving a configuration about configuring an authorized uplink transmission from a second device at a first device, the configuration at least indicating resource allocation for a transmission burst on an uplink shared channel and resource allocation for configuring authorized uplink control information; a component for determining resources for sending the configured authorized uplink control information on an uplink control channel based on the received configuration; and a component for sending the configured authorized uplink control information to the second device on the determined resources together with at least one transmission burst in the transmission burst.

[0009] In a sixth aspect, an apparatus is provided. The apparatus includes a component for generating a configuration for configuring an authorized uplink transmission at a second device, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring authorized uplink control information; a component for sending the configuration for configuring the authorized uplink transmission to a first device; and a component for receiving the configured authorized uplink control information from the first device on a resource together with at least one transmission burst in the transmission burst.

[0010] In a seventh aspect, a computer-readable medium is provided, wherein the computer-readable medium includes program instructions for causing a device to at least execute the method according to the third or fourth aspect.

[0011] It should be understood that the summary is not intended to identify the key or essential features of the embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] Some example embodiments will now be described with reference to the accompanying drawings, in which:

[0013] Figure 1 A schematic diagram of a communication system according to an embodiment of the present disclosure is shown;

[0014] Figure 2 A schematic diagram showing interactions between devices according to an embodiment of the present disclosure;

[0015] Figure 3A-3C A schematic diagram showing resource allocation according to an embodiment of the present disclosure is shown;

[0016] Figure 4 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0017] Figure 5 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0018] Figure 6 A flowchart of a method according to an embodiment of the present disclosure is shown;

[0019] Figure 7 shows a simplified block diagram of an apparatus suitable for implementing an embodiment of the present disclosure; and

[0020] Figure 8 A block diagram of an example computer-readable medium is shown according to some example embodiments of the present disclosure.

[0021] Throughout the drawings, the same or similar reference numerals refer to the same or similar elements. DETAILED DESCRIPTION

[0022] The principle of the present disclosure will now be described with reference to some example embodiments. It should be understood that these embodiments are described only for the purpose of illustrating and helping those skilled in the art to understand and realize the present disclosure, without any limitation to the scope of the present disclosure. The disclosure described herein can be realized in various other ways except as described below.

[0023] 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.

[0024] References in this disclosure to "one embodiment," "an embodiment," "an example embodiment," etc. indicate that the described embodiment may include a particular feature, structure, or characteristic, but not every embodiment must include the particular feature, structure, or characteristic. Furthermore, these phrases do not necessarily refer to the same embodiment. Furthermore, when a particular feature, structure, or characteristic is described in conjunction with an embodiment, it is considered to be within the knowledge of those skilled in the art to affect such feature, structure, or characteristic in conjunction with other embodiments (whether or not explicitly described).

[0025] It should be understood that although the terms "first" and "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 element. For example, without departing from the scope of the exemplary embodiment, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element. As used herein, the term "and / or" includes any and all combinations of one or more of the listed terms.

[0026] The terms used herein are only used for the purpose of describing specific embodiments and are not intended to limit the exemplary embodiments. As used herein, the singular forms "a", "an", and "the" are also intended to include the plural forms, unless the context clearly indicates otherwise. It will be further understood that the terms "comprise", "including", "having", "having", "including" and / or "comprising" when used herein specify the presence of the features, elements and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0027] As used in this application, the term "circuitry" may refer to one, more, or all of the following:

[0028] (a) pure hardware circuit implementation (such as implementation in analog and / or digital circuitry only), and

[0029] (b) a combination of hardware circuitry and software such as (where applicable):

[0030] (i) a combination of analog and / or digital hardware circuitry and software / firmware, and

[0031] (ii) any portion of a hardware processor (including a digital signal processor) with software, software and memory that work together to cause a device (such as a mobile phone or server) to perform various functions, and

[0032] (c) Hardware circuits and / or processors, such as a microprocessor or portion of a microprocessor, that require software (e.g., firmware) to operate, but which may not be present when not required for operation.

[0033] This 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 covers an implementation of only a hardware circuit or processor (or multiple processors) or a portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers (for example 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, cellular network device, or other computing or network device.

[0034] As used herein, the term "communication network" refers to a network that follows any suitable communication standard, such as Long Term Evolution (LTE), Advanced LTE (LTE-A), Wideband Code Division Multiple Access (WCDMA), High Speed ​​Packet Access (HSPA), Narrowband Internet of Things (NB-IoT), New Radio (NR), etc. In addition, the communication between the terminal device and the network device in the communication network can be performed according to any suitable generation communication protocol, including but not limited to the first generation (1G), second generation (2G), 2.5G, 2.75G, third generation (3G), fourth generation (4G), 4.5G, future fifth generation (5G) communication protocol, and / or any other protocol currently known or developed in the future. The embodiments of the present disclosure can be applied to various communication systems. In view of the rapid development of communication, of course, there will also be communication technologies and systems that can be used to embody future types of the present disclosure. The scope of the present disclosure should not be limited to the above-mentioned system.

[0035] 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), for example, a NodeB (NodeB or NB), an evolved NodeB (eNodeB or eNB), a NR NB (also known as a gNB), a remote radio unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, a low power node (such as a femto, a pico), etc., depending on the terminology and technology applied.

[0036] 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). The terminal device may include, but is not limited to, a mobile phone, a cellular phone, a smart phone, a voice over IP (VoIP) phone, a wireless local loop phone, a tablet computer, a wearable terminal device, a personal digital assistant (PDA), a portable computer, a desktop computer, an image capture terminal device such as a digital camera, a game terminal device, a music storage and playback device, a vehicle-mounted wireless terminal device, a wireless endpoint, a mobile station, a laptop embedded device (LEE), a laptop mounted device (LME), a USB dongle, a smart device, a wireless client equipment (CPE), an Internet of Things (IoT) device, a watch or other wearable device, a head mounted display (HMD), a vehicle, a target, medical equipment and applications (e.g., remote surgery), industrial equipment and applications (e.g., robots and / or other wireless devices operating in industrial and / or automated process chain environments, consumer electronic devices, devices operating on commercial and / or industrial wireless networks, etc. In the following description, the terms "terminal device", "communication device", "terminal", "user equipment" and "UE" may be used interchangeably.

[0037] As mentioned above, uplink transmission based on configuration grant (CG) has been proposed. A mechanism similar to uplink (UL) CG in unlicensed spectrum is also supported in Long Term Evolution (LTE) License Assisted Access (LAA), called Autonomous Uplink (AUL).

[0038] The terminal device can indicate to the network device the selected HARQ process ID, new data indicator, redundancy version, UE ID, physical uplink shared channel (PUSCH) start and end points, and whether the channel occupation time (COT) acquired by the UE can be shared with the network device together with each CG UL transmission.

[0039] The network equipment may provide HARQ feedback for enabling the HARQ process of the AUL and send power commands to the terminal device via a downlink (DL) control signaling message called Autonomous Uplink Downlink Feedback Information (AUL-DFI).

[0040] AUL also allows configuration of a set of starting positions for terminal devices with a very fine 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 the subframe boundary, or at the beginning of the second symbol of the subframe. Since all terminal devices perform a listen-before-talk operation before AUL transmission to determine if the channel is idle, different starting points allow, for example, to prioritize the transmissions of certain terminal devices (by assigning an earlier starting point) and reduce the number of collisions. The transmission within the first symbol is not PUSCH data, but a very long cyclic prefix (CP) extending from the next symbol #2.

[0041] CP extension is used to reserve a channel for a given terminal device by blocking other terminal devices. However, conflicts on AUL resources cannot always be avoided because only 7 starting positions are supported in LAA-AUL and terminal devices may not always be in each other's LBT sensing area (so they may not always block each other's transmissions).

[0042] Autonomous Uplink - Uplink Control Information (AUL-UCI) is multiplexed with UL-SCH data on AUL-PUSCH resources in a similar manner 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 AUL-UCI is mapped from symbol 1 to symbol 12 of a subframe, excluding symbols containing demodulation reference signals. More robust coding can be applied to AUL-UCI (compared to UL-SCH), while data and control information share the same modulation order.

[0043] With a similar purpose as LAA AUL (reducing the overhead of multiple LBT operations during the handshake between network equipment and terminal devices associated with SR and UL grants), New Radio Unlicensed (NR-U) agrees to support configured grant-based UL transmissions.

[0044] In Release-15NR, transmission based on configuration grant is introduced. In NR CG operation, the network device semi-statically configures the CG-PUSCH resources to the terminal device, and the terminal device can send PUSCH on the CG-PUSCH resources when it has an uplink shared channel, or send data. In Release-15NR transmission based on configuration grant, the HARQ process identifier (ID) is implicitly determined based on the resources configured for UL transmission with configuration grant. In addition, when repetition of the same transport block (TB) is introduced, the HARQ RV sequence is pre-configured. Due to the uncertainty of channel access, 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 unlicensed carriers.

[0045] In Release-15 NR, physical uplink control channel (PUCCH) formats 0-4 were introduced. The formats can 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 larger UCI payloads. Another way to classify PUCCH formats is based on 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 can be introduced to PUCCH formats 2 and 3 enhanced for NR-U.

[0046] A PUCCH resource or resource group comprising a set of resource elements and a code domain configuration that may include, for example, a cyclic shift and / or an orthogonal cover code index is semi-statically configured. When there are multiple PUCCH resources from which a terminal device selects a PUCCH resource, the selection of the PUCCH resource depends on the content of the UCI and the size of the UCI. For example, if the UCI includes HARQ-ACK (with at least one HARQ-ACK received in response to a PDSCH with a corresponding PDCCH), the PUCCH resource set is selected based on the number of UCI bits. The terminal device can be configured with up to 4 PUCCH resource sets for UCI containing HARQ-ACK, with a specific range of UCI payload sizes associated with each resource set. The PUCCH resource used is selected from the determined PUCCH resource set according to the PUCCH resource indicator included in the DL assignment downlink control information.

[0047] In another example, if the UCI includes CSI and HARQ-ACK associated with a 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. A minimum PUCCH resource that provides a sufficiently low code rate for the determined UCI payload is selected.

[0048] In Release-15 NR, PUCCH and PUSCH can be multiplexed in time within a single time slot. However, concurrent transmission of PUCCH and PUSCH within a single cell group (i.e., symbols overlap in time) (or concurrent transmission of multiple PUCCHs) is not supported. In the case of simultaneous transmission of PUCCH and PUSCH, UCI is typically multiplexed on the resources of PUSCH and the PUCCH transmission is dropped.

[0049] In LAA-AUL, the network equipment usually configures CG-PUSCH resources to multiple terminal devices, and multiple terminal devices can send PUSCH at the same time, and despite the LAA conflict avoidance mechanism, conflicts cannot be completely avoided. In LAA-AUL, control information is multiplexed and interleaved with data, and it is not possible to apply enhanced conflict avoidance techniques to control information (CG UCI) compared to UL-SCH data. When a conflict occurs on the UL CG resource, the conflict affects the control information and data equally.

[0050] Although NR-U CG UCI is required for the reception of NR-U CG-PUSCH, some CG-UCI fields (e.g., UE ID, HARQ process ID) are also important when the reception of CG-PUSCH is destined to fail, for example due to a collision. Therefore, it is beneficial to provide CG-UCI with a lower collision probability (or higher decoding probability) than CG-PUSCH.

[0051] 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 the resources for sending CG-UCI on an uplink control channel. In this way, the probability of collision on the physical resources carrying the CG UCI is reduced, and the multiplexing of CG UCI information from one or more terminal devices with the PUCCH sent by other terminal devices is achieved. Therefore, the reliability of UCI is improved, and the waiting time for uplink CG transmission is reduced.

[0052] Figure 11 shows a schematic diagram of a communication system in which embodiments of the present disclosure may be implemented. The communication system 100 as part of a communication network includes a device 110-1, a device 110-2, ..., a device 110-N, which may be collectively referred to as "device 110". The communication system 100 also includes a device 120. One or more devices are associated with a cell and covered by the cell. It should be understood that Figure 1 The number of devices and cells shown in is given for illustrative purposes and does not imply any limitation. The communication system 100 may include any suitable number of devices and cells. In the communication system 100, the device 110 and the device 120 may transmit data and control information to each other. In the case where the device 110 is a terminal device and the device 120 is a network device, the link from the device 120 to the device 110 is called a downlink (DL), and the link from the device 110 to the device 120 is called an uplink (UL). Figure 1 The number of devices shown in the figures is given for illustrative purposes and does not imply any limitation.

[0053] The communication in the communication system 100 can be implemented according to any appropriate communication protocol, including but not limited to cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G) and the fifth generation (5G), wireless local area network communication protocols such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11, and / or any other protocol currently known or developed in the future. In addition, the communication can utilize any appropriate 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 technology currently known or to be developed in the future.

[0054] Figure 2 A schematic diagram of an interaction 200 between devices according to an embodiment of the present disclosure is shown. The interaction 200 may be implemented on any suitable device. For illustrative purposes only, the interaction 200 is described as being implemented at the terminal device 110-1 and the network device 120. For illustrative purposes only, the uplink control channel refers to the PUCCH and the uplink shared channel refers to the PUSCH.

[0055] The network device 120 generates 2005 a configuration for uplink control information transmission. The configuration indicates at least resource allocation for transmission bursts on an uplink shared channel and resource allocation for configuring authorized uplink control information. The configuration may indicate resources allocated to a terminal device for a shared channel and / or a 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 the following: duration of uplink transmission, cyclic shift, demodulation reference signal (DMRS) orthogonal cover code (OCC). The duration of uplink transmission may be configured by the network device 120 or may be fixed in the standard. The term "transmission burst" used herein may include one or more uplink transmissions. An uplink transmission may be an uplink shared channel transmission having a duration of at most one time slot.

[0056] In some embodiments, the network device 120 may determine the configuration based on whether other UCI (in addition to the CG-UCI, such as channel state information (CSI)) is to be transmitted by the terminal device.

[0057] The network device 120 sends 2010 the configuration to the 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 probability of collision of the CG-UCI is reduced, thereby increasing the probability that at least the CG-UCI can be correctly decoded at the network device even if a collision occurs on the UL CG resources used for the UL-SCH channel or data transmission. This improvement in the reliability of the CG UCI can translate into a reduction in delay, because, for example, it can enable the network device to schedule retransmissions on contention-free resources for the correct UE and HARQ process. In addition, the possibility of using different modulation orders for data and control channels also supports more reliable transmission of CG-UCI information.

[0058] The terminal device 110-1 determines 2025 resources for the CG-UCI. In some embodiments, the CG-UCI may occupy one or more symbols in the time domain. In some embodiments, the terminal device 110-1 may determine the transport format based on the configuration. Alternatively or additionally, the terminal device 110-1 may determine the 2015 transport format based on whether the CG-PUSCH resource is immediately after the regular PUCCH opportunity. The term "regular PUCCH" used herein refers to a PUCCH other than the CG PUCCH. This can be determined based on a group common (GC)-PDCCH that indicates the link direction within the COT and is sent by the network device 120 in one or more downlink time slots / subframes before the PUCCH opportunity. Alternatively, the network device 120 may indicate a regular PUCCH opportunity to the terminal device 110-1 via dedicated signaling (e.g., in a DL grant).

[0059] In some embodiments, the terminal device 110-1 can determine that the uplink control channel overlaps with the uplink shared channel based on the transmission mode. In this case, the resources used to send the CG-UCI on the uplink control channel can occupy N symbols of the uplink shared channel, followed by the 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 to the N symbols reserved for the uplink control channel. The resources for the CG-UCI on the uplink control channel may be one or more symbols in the PUSCH. For example, if the resources for the PUSCH may include 14 symbols, the resources for the CG-UCI on the uplink control channel may be the first one or two symbols of the 14 symbols.

[0060] like Figure 3A As shown, resources of CG-PUCCH 3012-1 for transmitting CG-UCI may be included in resources of PUSCH 3013-1 in a transmission burst. Resources of CG-PUCCH 3012-2 for transmitting CG-UCI may be included in resources for PUSCH 3013-2.

[0061] like Figure 3B As shown, resources of CG-PUCCH 3022-1 for transmitting CG-UCI may be included in resources of PUSCH 3023-1 in a transmission burst. Resources of CG-PUCCH 3022-2 for transmitting CG-UCI may be included in resources for PUSCH 3023-2.

[0062] 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 be located before the resources allocated to the uplink control channel. For example, the resources for the CG-UCI on the uplink control channel may be one or more symbols, followed by resources including 14 symbols allocated to the uplink shared channel. Figure 3C As shown, the resources of CG-PUCCH 3032-1 used to send CG-UCI can be located before the resources of PUSCH 3033-1.

[0063] In some embodiments, the network device 120 may send 2020 an indication of resources for sending configuration grant uplink control information. The indication may be sent via RRC signaling. In this case, the terminal device 110-1 may determine 2025 resources based on the indication.

[0064] In some embodiments, the network device 120 may determine information about the frequency domain configuration. In addition, the network device 120 may determine 2030 information about the code domain configuration. The information may include a cyclic shift. Alternatively or additionally, the information may include an orthogonal cover code for the terminal device 110-1 configured with overlapping CG-PUCCH resources. The code domain resources may be indicated to the terminal device 110-1 using RRC signaling. The network device 120 may send 2035 the information to the terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE-specific.

[0065] The terminal device 110-1 may determine 2040 the code domain resource based on the identity of the terminal device 110-1. Alternatively or additionally, the terminal device 110-1 may determine 2040 the code domain resource based on a cell radio network temporary identifier (C-RNTI) or a scrambling ID of the DMRS. For example, the code domain resource derivation may be time-varying according to a time slot index.

[0066] The terminal device 110-1 sends 2050 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 consecutive CG-PUSCH transmission bursts, and the CG-UCI can be additionally transmitted on the CG-PUSCH together with each CG-PUSCH transmission in the burst. For example, the terminal device 110-1 can send a first part of the CG-UCI on the uplink control channel together with the first transmission of the transmission burst. The first part of the CG-UCI can be common to the transmissions in one transmission burst. The terminal device 110-1 can send a second part of the CG-UCI on the uplink shared channel together with each transmission of the transmission burst.

[0067] In some embodiments, Figure 3A As shown, the terminal device 110-1 may perform listen before talk during 3011-1. The terminal device 110-1 may send a CG-UCI on CG-PUCCH 3012-1. The terminal device 110-1 may perform listen before talk during 3011-2 and send a CG-UCI on CG-PUSCH 3014-1. The terminal device 110-1 may perform listen before talk during 3011-3 and send a CG-UCI on CG-PUSCH 3014-2. The CG-UCI sent on the uplink control channel and the CG-UCI sent on the uplink shared channel may be different.

[0068] In some embodiments, Figure 3C As shown, the terminal device 110-1 may perform listen before talk during 3031-1. The terminal device 110-1 may send a CG-UCI on CG-PUCCH 3032-1. The terminal device 110-1 may perform listen before talk during 3031-2 and send a CG-UCI on CG-PUSCH 3034-1. The terminal device 110-1 may perform listen before talk during 3031-2 and send a CG-UCI on CG-PUSCH 3034-2. The terminal device 110-1 may perform listen before talk during 3031-3 and send a CG-UCI on CG-PUSCH 3034-3. The CG-UCI sent on the uplink control channel and the CG-UCI sent on the uplink shared channel may be different.

[0069] The CG-UCI transmitted on the CG-PUCCH may include one or more of the following: an identification 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 the channel occupancy with the first device, the number of uplink transmissions of the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the 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 the burst, such as a HARQ process ID, a new data indicator (NDI), and / or a redundancy version (RV).

[0070] In other embodiments, the CG-PUCCH may appear in each time slot together with the CG-PUSCH. In this case, the CG-PUCCH transmission is used to reduce the probability of collision of a portion of the CG-UCI, and the payload size of the CG-UCI on the CG-PUCCH is minimized. For example, the terminal device 110-1 may send the first part of the CG-UCI on the uplink control channel before a set of data bursts. The terminal device 110-1 may send the second part of the CG-UCI and the data burst set on the uplink shared channel.

[0071] like Figure 3B As shown, the terminal device 110-1 may perform listen before talk during 3021-1. The terminal device 110-1 may send a CG-UCI on CG-PUCCH 3022-1. The terminal device 110-1 may perform listen before talk during 3021-2 and send a CG-UCI on CG-PUCCH 3022-2. The terminal device 110-1 may perform listen before talk during 3021-3 and send a CG-UCI on CG-PUSCH 3024-2. The CG-UCI sent on the uplink control channel and the CG-UCI sent on the uplink shared channel may be different.

[0072] The CG-UCI sent on the CG-PUSCH may include one or more of the following: an identification 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 by the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the terminal device 110-1 should transmit. The CG-UCI sent on the CG-PUCCH may include more critical information, such as a HARQ process ID.

[0073] Terminal device 110-1 may multiplex CG-UCI. Terminal device 110-1 may send other PUSCHs on other cells while sending CG-PUSCH. Terminal device 110-1 may, for example, send conventional UCI (i.e., non-CG) on PUCCH on another cell. In some embodiments, CG-PUCCH and CG-PUSCH are considered to be CG-PUSCH from a conventional UCI multiplexing perspective.

[0074] In some embodiments, for UCI multiplexing on PUSCH within a PUCCH group, the terminal device 110-1 may multiplex the UCI in the overlapping PUCCH transmissions into one PUCCH resource (resource Z). The terminal device 110-1 may multiplex the UCI excluding resource Z into one PUSCH according to the priorities listed below (in order from high to low), if Z overlaps with at least one PUSCH: First priority: PUSCH with A-CSI as long as it coincides with Z; Second priority: The earliest PUSCH time slot based on the start of the time slot. If there are still multiple PUSCHs overlapping with Z in the earliest PUSCH time slot, the following priorities are followed (in order from high to low): Third priority: Dynamically granted PUSCHs > CG-PUSCH or CG-PUCCH; Fourth priority: PUSCH on a serving cell with a smaller serving cell index > PUSCH on a serving cell with a larger serving cell index; Fifth priority: Earlier PUSCH transmissions > Later PUSCH transmissions.

[0075] In this way, the CG-UCI remains on the same cell as the CG-PUSCH and therefore under the same LBT. This is beneficial because: the CG-UCI is required for CG-PUSCH detection and is quite unnecessary if the CG-PUSCH is not sent. The network device 120 does not need to blindly detect whether the CG-UCI is multiplexed with the UCI and sent on a scheduled PUSCH on some other cell.

[0076] Figure 4 4 is a flow chart of a method 400 according to an embodiment of the present disclosure. The method 400 may be implemented at any suitable device. For example, the method may be implemented at the terminal device 110.

[0077] At block 410, the terminal device 110-1 receives a configuration from the 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 resource allocation for transmission bursts on an uplink shared channel and resource allocation for configuring grant uplink control information.

[0078] At block 420, the terminal device 110-1 determines resources for the CG-UCI. In some embodiments, the CG-UCI may occupy one or more symbols in the time domain. In some embodiments, the terminal device 110-1 may determine the transport format based on the configuration. Alternatively or additionally, the terminal device 110-1 may determine the transport format based on whether the PUCCH opportunity in the cell is immediately followed by the CG-PUSCH resources. This may be determined based on the GC-PDCCH sent by the network device 120 in one or more downlink time slots / subframes prior to the PUCCH opportunity.

[0079] In some embodiments, the terminal device 110-1 can determine from the transmission mode that the uplink control channel does not overlap with the uplink shared channel. In this case, the resources used to send the CG-UCI on the uplink control channel can be the uplink shared channel followed by multiple symbols of the uplink shared channel. In other words, the resources allocated to the uplink shared channel may include the resources allocated to the uplink control channel, and the uplink shared channel is not mapped to the N symbols reserved for the uplink control channel. The resources for the CG-UCI on the uplink control channel may be one or more symbols in the PUSCH. For example, if the resources for the PUSCH may include 14 symbols, the resources for the CG-UCI on the uplink control channel may be the first one or two symbols of the 14 symbols.

[0080] In some embodiments, the terminal device 110-1 may determine that the uplink control channel overlaps with the uplink shared channel based on the transmission mode. The resources allocated to the uplink shared channel may be located before the resources allocated to the uplink control channel. For example, the resources for the CG-UCI on the uplink control channel may be one or more symbols and the subsequent resources including 14 symbols allocated to the uplink shared channel.

[0081] In some embodiments, the terminal device 110-1 may receive an indication of resources for sending configuration grant uplink control information. The indication may be sent via radio resource signaling. In this case, the terminal device 110-1 may determine 2025 resources based on the indication.

[0082] The network device 120 may generate information about the code domain configuration and / or the frequency domain configuration. The information may include a cyclic shift. Alternatively or additionally, the information may include an orthogonal cover code for the terminal device 110-1 configured with overlapping CG-PUCCH resources. The code domain resources may be indicated to the terminal device 110-1 using RRC signaling. The network device 120 may send 2035 the information to the terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE-specific.

[0083] The terminal device 110-1 may determine the code domain resources based on an identification of the terminal device 110-1 and / or a DMRS scrambling ID assigned to the terminal device. Alternatively or additionally, the terminal device 110-1 may determine 2040 the code domain resources based on a cell radio network temporary identifier (C-RNTI). For example, the code domain resource derivation may be time-varying according to a time slot index.

[0084] The terminal device 110-1 may determine the frequency domain resources based on an identity of the terminal device 110-1 and / or a DMRS ID allocated to the terminal device.Alternatively or additionally, the terminal device 110-1 may determine 2040 the frequency domain resources based on a cell radio network temporary identifier (C-RNTI).

[0085] At box 430, the terminal device 110-1 sends 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 consecutive CG-PUSCH transmission bursts, and the CG-UCI can be additionally transmitted on the CG-PUSCH together with each CG-PUSCH transmission in the burst. For example, the terminal device 110-1 can send the first part of the CG-UCI on the uplink control channel before a group of data bursts. The first part of the CG-UCI is common to the transmission group in one transmission burst. The terminal device 110-1 can send the second part CG-UCI and the data burst set on the uplink shared channel. The terminal device 110-1 can send the first part of the CG-UCI on the uplink control channel together with the first transmission of the transmission burst, the first part of the CG-UCI is common to the transmission of one burst in the transmission burst, and the second part of the CG-UCI is sent on the uplink shared channel together with each transmission of the transmission burst.

[0086] The CG-UCI transmitted on the CG-PUCCH may include one or more of the following: an identification 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 the channel occupancy with the first device, the number of uplink transmissions of the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the 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 the burst, such as a HARQ process ID, a new data indicator (NDI), and / or a redundancy version (RV).

[0087] In other embodiments, the CG-PUCCH may appear in each time slot together with the CG-PUSCH. In this case, the CG-PUCCH transmission is used to reduce the probability of collision of a portion of the CG-UCI, and the payload size of the CG-UCI on the CG-PUCCH is minimized. For example, the terminal device 110-1 may send the first part of the CG-UCI on the uplink control channel before a set of data bursts. The terminal device 110-1 may send the second part of the CG-UCI and the data burst set on the uplink shared channel.

[0088] The CG-UCI sent on the CG-PUSCH may include one or more of the following: an identification 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 by the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the terminal device 110-1 should transmit. The CG-UCI sent on the CG-PUCCH may include more critical information, such as a HARQ process ID.

[0089] The terminal device 110-1 may send the configuration grant uplink control information on the uplink control channel prior to the transmission burst.In some embodiments, the terminal device 110-1 may send the configuration grant uplink control information together with the first transmission of the transmission burst.

[0090] Terminal device 110-1 may multiplex CG-UCI. Terminal device 110-1 may send other PUSCHs on other cells while sending CG-PUSCH. Terminal device 110-1 may, for example, send regular UCI (i.e., non-CG) on PUCCH on another cell. In some embodiments, CG-PUCCH and CG-PUSCH are considered to be CG-PUSCH from a regular UCI multiplexing perspective.

[0091] Figure 5 1 shows a flow chart of a method 500 according to an embodiment of the present disclosure. The method 500 may be only an example of selecting resources for multiplexing regular UCI and GC-UCI. The method 500 may be implemented on any suitable device. For example, the method may be implemented at the terminal device 110.

[0092] At block 510, terminal device 110-1 may determine whether terminal device 110-1 is configured with CG-PUCCH. If terminal device 110-1 is configured with CG-PUCCH, terminal device 110-1 may determine whether to map regular UCI to a time slot of CG-PUSCH at block 520. If regular UCI is not mapped to a time slot of CG-PUSCH, terminal device 110-1 may send CG on CG-PUCCH at block 540.

[0093] If the legacy UCI is mapped to a time slot of the CG-PUSCH, then at block 550, the terminal device 110-1 may determine whether the CG-PUCCH resources have sufficient size. If the CG-PUCCH resources have sufficient size, then at block 560, the terminal device 110-1 may send the CG-UCI with the conventional UCI appended on the CG-PUCCH. If the CG-PUCCH resources do not have sufficient size, then at block 570, the terminal device 110-1 may send the CG-UCI with the conventional UCI appended on the CG-PUCCH.

[0094] Referring to block 530, if the terminal device 110-1 is not configured with CG-PUCCH, the terminal device 110-1 may determine whether to map the regular UCI to the time slot of the CG-PUSCH. If the regular UCI is not mapped to the time slot of the CG-PUSCH, at block 580, the terminal device 110-1 may send the CG-UCI on the CG-PUSCH. If the regular UCI is mapped to the time slot of the CG-PUSCH, at block 570, the terminal device 110-1 may send the CG-UCI with the regular UCI attached to it on the CG-PUSCH.

[0095] Figure 6A flow chart of method 600 is shown. Method 600 may be implemented at any suitable device. For example, the method may be implemented at network device 120.

[0096] At box 610, the network device 120 generates a configuration for the transmission of uplink control information. The configuration indicates at least resource allocation for uplink transmission. The configuration may indicate resources allocated to the terminal device for data channels and / or control channels. 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 the following: duration of uplink transmission, cyclic shift, demodulation reference signal (DMRS) orthogonal cover code (OCC). The duration of uplink transmission may be configured by the network device 120 or may be fixed in the standard. The configuration indicates at least resource allocation for transmission bursts on an uplink shared channel and resource allocation for configuring authorized uplink control information.

[0097] In some embodiments, the network device 120 may determine the configuration based on whether other UCI (in addition to the CG-UCI, for example, channel state information (CSI)) is to be sent by the terminal device.

[0098] At box 620, the network device 120 sends the configuration to the terminal device 110-1. In some embodiments, the configuration can be sent via radio resource control. In other embodiments, the configuration can be transmitted via physical layer (PHY) signaling. For example, the configuration can be sent via CG activation signaling. In this way, the collision probability of the CG-UCI is reduced, thereby increasing the probability that at least the CG-UCI can be correctly decoded at the network device even if a collision occurs on the UL CG resources used for UL-SCH data transmission. This improvement in the reliability of the CG UCI can be translated into a reduction in delay, because, for example, it can enable the network device to schedule retransmissions on contention-free resources for the correct UE and HARQ process. In addition, the possibility of using different modulation orders for data and control also supports more reliable transmission of CG-UCI information.

[0099] In some embodiments, network device 120 may send an indication of resources for sending configuration grant uplink control information. The indication may be sent via radio resource signaling.

[0100] In some embodiments, the 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 an orthogonal cover code for the terminal device 110-1 configured with overlapping CG-PUCCH resources. RRC signaling may be used to indicate the code domain resources to the terminal device 110-1. The network device 120 may send the information to the terminal device 110-1. For example, the information may be sent via radio resource signaling. The code domain resources may be UE-specific.

[0101] At box 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 consecutive CG-PUSCH transmission bursts, and the CG-UCI can be additionally transmitted on the CG-PUSCH with each CG-PUSCH transmission in the burst. For example, the network device 120 can receive the first part of the CG-UCI and the first transmission of the transmission burst on the uplink control channel. The first part of the CG-UCI can be shared by the transmission of one transmission burst in the transmission burst. The network device 120 can receive the second part of the CG-UCI on the uplink shared channel together with each transmission of the transmission burst.

[0102] The CG-UCI transmitted on the CG-PUCCH may include one or more of the following: an identification 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 the channel occupancy with the first device, the number of uplink transmissions of the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the 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 the burst, such as a HARQ process ID, a new data indicator (NDI), and / or a redundancy version (RV).

[0103] In other embodiments, the CG-PUCCH may appear in each time slot together with the CG-PUSCH. In this case, the CG-PUCCH transmission is used to reduce the probability of collision of a portion of the CG-UCI, and the payload size of the CG-UCI on the CG-PUCCH is minimized. For example, the network device 120 may receive the first part of the CG-UCI on the uplink control channel before a set of data bursts. The network device 120 may receive the second part of the CG-UCI and the set of data bursts on the uplink shared channel.

[0104] The CG-UCI sent on the CG-PUSCH may include one or more of the following: an identification 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 by the terminal device 110-1 in the channel occupancy (e.g., the remaining duration of the uplink burst), or a configuration authorization configuration according to which the terminal device 110-1 should transmit. The CG-UCI sent on the CG-PUCCH may include more critical information, such as a HARQ process ID.

[0105] In some embodiments, the apparatus for executing method 400 (eg, terminal device 110) may include corresponding components for executing corresponding steps in method 400. These components may be implemented in any appropriate manner. For example, it may be implemented by a circuit or a software module.

[0106] In some embodiments, the apparatus includes a component for receiving, at a first device, a configuration for configuring an authorized uplink transmission from a second device, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring authorized uplink control information; a component for determining, based on the received configuration, resources for sending the configured authorized uplink control information on an uplink control channel; and a component for sending the configured authorized uplink control information to the second device on the determined resources together with at least one transmission burst in the transmission burst.

[0107] In some embodiments, the means for determining resources includes: means for determining a transmission format based on a received configuration; and means for selecting resources from resources allocated to a transmission burst on an uplink shared channel if a transmission format in which an uplink control channel overlaps with an uplink shared channel is determined.

[0108] In some embodiments, the means for determining resources includes: means for determining a transmission format based on a received configuration; and means for selecting resources from previous resources allocated to a transmission burst on an uplink shared channel if a transmission format in which the uplink control channel does not overlap with an uplink shared channel is determined.

[0109] In some embodiments, means for selecting resources includes: means for receiving, via radio resource control signaling, an indication of resources for transmitting configuration grant uplink control information; and means for determining the resources based on the indication.

[0110] In some embodiments, the component for sending configuration authorization uplink control information includes: a component for sending a first part of the configuration authorization uplink control information together with a first transmission of a transmission burst on an uplink control channel, wherein the first part of the configuration authorization uplink control information is common to the transmission of a burst in the transmission burst; and a component for sending a second part of the configuration authorization uplink control information together with each transmission of the transmission burst on an uplink shared channel.

[0111] In some embodiments, the first portion of the configuration grant uplink control information includes at least one of: an identification of the first device, a channel access priority category (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 grant uplink shared channel, and 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.

[0112] In some embodiments, the means for sending configuration authorization uplink control information includes: means for sending a first portion of the configuration authorization uplink control information on an uplink control channel during a transmission burst; and means for sending a second portion of the configuration authorization uplink control information on an uplink shared channel during a transmission burst.

[0113] In some embodiments, the first portion of the configuration authorization uplink control information includes hybrid automatic repeat request (HARQ) related information, and the second portion of the configuration authorization uplink control information includes at least one of the following: an identification of the first device, a channel access priority category (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, and a configuration of a configuration authorization uplink shared channel.

[0114] In some embodiments, means for sending configuration grant uplink control information comprises means for sending configuration grant uplink control information on an uplink control channel prior to a transmission burst; or means for sending configuration grant uplink control information together with a first transmission of a transmission burst.

[0115] In some embodiments, the device also includes a component for receiving information about the frequency domain configuration from a second device via wireless resource control signaling; a component for determining the frequency domain configuration assigned to the first device from the information based on at least one of: an identifier of the first device and a demodulation reference signal scrambling identifier; and a component for multiplexing the configuration authorization uplink control information on an uplink control channel based on the frequency domain configuration.

[0116] In some embodiments, the apparatus further comprises a component for receiving information about the code domain configuration from a second device via wireless resource control signaling; a device for determining the code domain configuration assigned to the first device from the second information based on at least one of: an identifier of the first device and a demodulation reference signal scrambling identifier; and a component for multiplexing configuration authorization uplink control information on an uplink control channel based on the code domain configuration.

[0117] In some embodiments, the first device comprises a terminal device and the second device comprises a network device.

[0118] In an embodiment, an apparatus for executing method 600 (eg, network device 120) may include corresponding components for executing corresponding steps in method 600. These components may be implemented in any appropriate manner. For example, it may be implemented by a circuit or a software module.

[0119] In some embodiments, the apparatus includes a component for generating a configuration for configuring an authorized uplink transmission at a second device, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring authorized uplink control information; a component for sending the configuration for configuring the authorized uplink transmission to a first device; and a component for receiving the configured authorized uplink control information from the first device on a resource together with at least one transmission burst in the transmission burst.

[0120] In some embodiments, the configuration indication configures a transmission format of the grant uplink control information.

[0121] In some embodiments, the transport format indicates whether the uplink control channel overlaps with the uplink shared channel.

[0122] In some embodiments, the apparatus further comprises: means for generating an indication for sending resources for configuring grant uplink control information; and means for sending the first information to the first device via radio resource control signaling.

[0123] In some embodiments, the component for receiving configuration authorization uplink control information includes: a component for receiving a first part of the configuration authorization uplink control information together with a first transmission of a transmission burst on an uplink control channel, wherein the first part of the configuration authorization uplink control information is common to the transmission of one transmission burst in the transmission burst; and a component for receiving a second part of the configuration authorization uplink control information together with each transmission of the transmission burst on an uplink shared channel.

[0124] In some embodiments, the first portion of the configuration grant uplink control information includes at least one of: an identification of the first device, a channel access priority category (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 grant uplink shared channel, and the second portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) related information associated with the transmission burst.

[0125] In some embodiments, the component for receiving configuration authorization uplink control information includes: a component for receiving a first portion of the configuration authorization uplink control information on an uplink control channel prior to transmission of a transmission burst; and a component for receiving a second portion of the configuration authorization uplink control information on an uplink shared channel during transmission of the transmission burst.

[0126] 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 the following: an identification of the first device, a channel access priority category (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, and a configuration of the configuration grant uplink shared channel.

[0127] In some embodiments, the apparatus includes means for receiving configuration grant uplink control information on an uplink control channel prior to a transmission burst; or means for receiving configuration grant uplink control information together with a first transmission of a transmission burst.

[0128] In some embodiments, the apparatus includes means for generating information about frequency domain configuration; and means for sending the information to the first device via radio resource control signaling.

[0129] In some embodiments, the apparatus includes means for generating information regarding code domain configuration; and means for sending the information to the first device via radio resource control signaling.

[0130] In some embodiments, the first device comprises a terminal device and the second device comprises a network device.

[0131] Figure 7 is a simplified block diagram of a device 700 suitable for implementing an embodiment of the present disclosure. The device 700 may be used to implement a communication device, such as Figure 1 The terminal device 110 or the network device 120 is shown. As shown in the figure, the device 700 includes one or more processors 710, one or more memories 720 coupled to the processor 710, and one or more communication modules 740 coupled to the processor 710.

[0132] The communication module 740 is used for two-way 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.

[0133] Processor 710 may be of any type suitable for the local technology network, and may include, as non-limiting examples, one or more of a general purpose computer, a special purpose computer, a microprocessor, a digital signal processor (DSP), and a processor based on a multi-core processor architecture. Device 700 may have multiple processors, such as application specific integrated circuit chips that are time slaved to a clock synchronized with a main processor.

[0134] The memory 720 may include one or more non-volatile memories and one or more volatile memories. Examples of non-volatile memories include, but are not limited to, read-only memory (ROM) 724, electrically programmable read-only memory (EPROM), flash memory, hard disks, compact disks (CDs), digital video disks (DVDs), and other magnetic storage and / or optical storage devices. Examples of volatile memories include, but are not limited to, random access memory (RAM) 722 and other volatile memories that do not persist over the duration of a power outage.

[0135] The computer program 730 includes computer executable instructions that are executed by the associated processor 710. The program 730 may be stored, for example, in the ROM 724. The processor 710 may perform any suitable actions and processes by loading the program 730 into the RAM 722.

[0136] The embodiments of the present disclosure may be implemented by a program 730, so that the device 700 may execute the Figures 2 to 6 Any process of the present disclosure discussed. The embodiments of the present disclosure may also be implemented by hardware or a combination of software and hardware.

[0137] 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 in other storage devices accessible to the device 700. The device 700 may load the program 730 from the computer-readable medium to the RAM 722 for execution. The computer-readable medium may include any type of tangible non-volatile memory, such as ROM, EPROM, flash memory, hard disk, CD, DVD, etc. Figure 8 An example of a computer readable medium 800 in the form of a CD or DVD is shown. The computer readable medium has a program 630 stored thereon.

[0138] 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 into "building blocks" or entities that can be operationally connected or linked together to provide services. A virtualized network function (VNF) may include one or more virtual machines that use standard or general-purpose servers rather than custom hardware to run computer program code. Cloud computing or data storage may also be used. In radio communications, this may mean node operations to be performed at least in part in a central / centralized unit CU (e.g., a server, host, or node) that is operably 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 distribution of labor between core network operations and base station operations may vary depending on the implementation.

[0139] In one embodiment, the server can generate a virtual network through which the server communicates with the distributed units. In general, virtual networking can 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 can provide a flexible distribution of operations between servers and wireless heads / nodes. In fact, any digital signal processing task can be performed in the CU or DU, and the boundaries of transferring responsibilities between the CU and DU can be selected based on the implementation.

[0140] 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., a control unit, an edge cloud server, a server) that is operably coupled (e.g., via a wireless or wired network) to a distributed unit (e.g., a remote radio head / node). That is, the central unit (e.g., an 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 that communicates via a wired connection, etc. The 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 the central unit. In another embodiment, the device 700 may alternatively be included in a distributed unit, and at least some of the described processes may be performed by the distributed unit.

[0141] In one embodiment, the execution of at least some functions of the device 700 can be shared between two physically separate devices (DU and CU) forming an operational entity. Therefore, it can be seen that the apparatus describes an operational entity comprising one or more physically separate devices for performing at least some of the described processes. In one embodiment, this CU-DU architecture can provide a flexible distribution of operations between the CU and the DU. In fact, any digital signal processing task can be performed in the CU or the DU, and the boundary for transferring responsibilities between the CU and the DU can be selected based on the implementation. In one embodiment, the device 700 controls the execution of the process regardless of the location of the device and where the process / function is executed.

[0142] Generally, various embodiments of the present disclosure may be implemented in hardware or dedicated circuits, software, logic, or any combination thereof. Some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software that may be executed by a controller, microprocessor, or other computing device. Although various aspects of the embodiments of the present disclosure are shown and described as block diagrams, flow charts, or using some other graphical representations, it should be understood that the block diagrams, devices, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuits or logic, general hardware or controllers or other computing devices, or some combination thereof.

[0143] The present disclosure also provides at least one computer program product tangibly stored on a non-transient computer-readable storage medium. The computer program product includes computer executable instructions, such as computer executable instructions included in a program module, which are executed in a device on a target reality or virtual processor to perform the above reference Figures 3-6 to describe methods 400-600. Typically, a program module includes routines, programs, libraries, objects, classes, components, data types, etc. that perform specific tasks or implement specific abstract data structures. The functions of the program modules can be combined or split between program modules as needed in various embodiments. Machine executable instructions for program modules can be executed in local or distributed devices. In distributed devices, program modules can be located in local and remote storage media.

[0144] The program code for executing the method of the present disclosure can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer or other programmable data processing device, so that these program codes cause the functions / operations specified in the flow chart and / or block diagram to be implemented when executed by the processor or controller. The program code can be executed completely on the machine, partially on the machine, executed as an independent software package, partially on the machine and partially on a remote machine, or completely on a remote machine or server.

[0145] In the context of the present disclosure, computer program codes 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 carriers include signals, computer readable media, etc.

[0146] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination thereof. More specific examples of computer readable storage media include an electrical connection with one or more wires, a portable computer floppy disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof.

[0147] In addition, although the operations are depicted in a particular order, this should not be understood as requiring such operations to be performed in the particular order shown or in a continuous order or to perform all the operations shown to achieve the desired result. In some cases, multitasking and parallel processing may be advantageous. Similarly, although the above discussion includes several specific implementation details, these details should not be interpreted as limitations on the scope of the present disclosure, but should be interpreted as descriptions of features that may be specific to a particular embodiment. Certain features described in the context of a separate embodiment may also be implemented in combination in a single embodiment. On the contrary, the various features described in the context of a single embodiment may also be implemented in multiple embodiments or in any suitable sub-combination, respectively.

[0148] Although the disclosure has been described in language specific to structural features and / or methodological acts, it should 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

1. A method comprising: At the first device, receiving a configuration for configuring a grant uplink transmission from the second device, the configuration indicating at least a resource allocation for a transmission burst on an uplink shared channel and a resource allocation for configuring grant uplink control information; Based on the received configuration, determining resources for sending the configuration grant uplink control information on an uplink control channel; as well as sending the configuration grant uplink control information to the second device on the determined resources together with at least one of the transmission bursts; The resources are determined to include: determining a transmission format based on the received configuration; and If it is determined that the uplink control channel has a transmission format overlapping with an uplink shared channel, selecting the resource from resources allocated to the transmission burst on the uplink shared channel; Wherein determining the transmission format further comprises: The transmission format is determined based on whether the resources used for the uplink configuration grant transmission are after a conventional physical uplink control channel (PUCCH) opportunity.

2. The method of claim 1, wherein determining the resource further comprises: determining a transmission format based on the received configuration; as well as If a transmission format of the uplink control channel that does not overlap with an uplink shared channel is determined, the resource is selected from previous resources allocated to the transmission burst on the uplink shared channel.

3. The method of claim 2, wherein selecting the resource comprises: receiving, via radio resource control signaling, an indication of the resources for sending the configuration grant uplink control information; as well as The resource is determined based on the indication.

4. 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 together with a first transmission of a transmission burst, the first portion of the configuration grant uplink control information being common to the transmissions of the transmission burst; as well as A second portion of the configuration grant uplink control information is sent with each transmission of the transmission burst on an uplink shared channel.

5. The method of claim 4, wherein the first portion of the configuration grant uplink control information comprises at least one of: an identification of the first device, a channel access priority class (CAPC) of the first device, Listen first, speak later type, The duration of channel occupancy, an indication of whether the second device is allowed to share the channel occupancy with the first device, The remaining duration of the uplink transmission burst, or Configure the configuration of the granted uplink shared channel, and The second portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) related information associated with a data burst group.

6. The method of claim 1, wherein sending the configuration grant uplink control information comprises: prior to transmission of a transmission burst, sending a first portion of said configuration grant uplink control information on said uplink control channel; as well as During said transmission of said transmission burst, a second portion of said configuration grant uplink control information is sent 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: an identification of the first device, Hybrid Automatic Repeat Request (HARQ) flag, a channel access priority class (CAPC) of the first device, Listen first, speak later type, The duration of channel occupancy, an indication of 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 granted uplink shared channel; and The second part of the configuration grant uplink control information includes configuration grant uplink control information that is not included in the first part or the entire configuration grant uplink control information.

8. The method of claim 1, wherein sending the configuration grant uplink control information comprises: prior to the transmission burst, sending the configuration grant uplink control information on the uplink control channel; or The configuration grant uplink control information is sent together with a first transmission of the transmission burst.

9. The method according to claim 1, further comprising: receiving information about frequency domain configuration from the second device via radio resource control signaling; determining, from the information, a frequency domain configuration assigned to the first device based on at least one of: an identifier of the first device and a demodulation reference signal scrambling identifier; as well as The configuration grant uplink control information is multiplexed on the uplink control channel based on the frequency domain configuration.

10. The method according to claim 1, further comprising: receiving information about code domain configuration from the second device via radio resource control signaling; determining, from the information, a code domain configuration assigned to the first device based on at least one of: an identifier of the first device and a demodulation reference signal scrambling identifier; as well as The configuration grant uplink control information is multiplexed on the uplink control channel based on the code domain configuration.

11. The method of claim 1, wherein the first device comprises a terminal device, and the second device comprises a network device.

12. A method comprising: At the second device, generating a configuration for configuring a grant 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 grant uplink control information; Sending the configuration regarding the configuration authorization uplink transmission to the first device; as well as receiving configuration grant uplink control information from the first device on a resource along with at least one of the transmission bursts; The receiving of the configuration authorization uplink control information comprises: receiving a first portion of the configuration grant uplink control information together with a first transmission of the transmission burst on an uplink control channel, the first portion of the configuration grant uplink control information being common to transmissions of one of the transmission bursts; as well as A second portion of the configuration grant uplink control information is received with each transmission of the transmission burst on an uplink shared channel.

13. The method according to claim 12, wherein the configuration indicates a transmission format of the configuration grant uplink control information.

14. The method of claim 13, wherein the transmission format indicates whether the uplink control channel resources overlap with resources configured for an uplink shared channel.

15. The method according to claim 14, further comprising: generating an indication of said resources for sending said configuration grant uplink control information; as well as The indication is sent to the first device via a radio resource control signal.

16. The method of claim 12, wherein the first portion of the configuration grant uplink control information comprises at least one of: an identification of the first device, a channel access priority class (CAPC) of the first device, Listen first, speak later type, The duration of channel occupancy, an indication of whether the second device is allowed to share the channel occupancy with the first device, The remaining duration of the uplink transmission burst, or Configure the configuration of the granted uplink shared channel, and The second portion of the configuration grant uplink control information includes hybrid automatic repeat request (HARQ) related information associated with a data burst group.

17. The method of claim 12, wherein receiving the configuration grant uplink control information comprises: receiving a first portion of said configuration grant uplink control information on said uplink control channel prior to transmission of a transmission burst; as well as During the transmission of the transmission burst, a second portion of the configuration grant uplink control information is received on an uplink shared channel.

18. The method of claim 17, wherein the configuring the first portion of grant uplink control information comprises: an identification of the first device, a channel access priority class (CAPC) of the first device, Listen first, speak later type, The duration of channel occupancy, an indication of whether the second device is allowed to share the channel occupancy with the first device, The remaining duration of the uplink transmission burst, or Configure the configuration of the authorized uplink shared channel; as well as The second part of the configuration grant uplink control information includes the configuration grant uplink control information that is not included in the first part or the entire configuration grant uplink control information.

19. The method of claim 12, wherein receiving the configuration grant uplink control information comprises: Prior to the transmission burst, receiving the configuration grant uplink control information on the uplink control channel; or The configuration grant uplink control information is received with a first transmission of the transmission burst.

20. The method of claim 12, further comprising: generating information about a frequency domain configuration; as well as The information is sent to the first device via radio resource control signaling.

21. The method of claim 12, further comprising: generating information about code domain configuration; as well as The information is sent to the first device via radio resource control signaling.

22. The method of claim 12, wherein the first device comprises a terminal device and the second device comprises a network device.

23. A first device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the first device to perform a method according to any one of claims 1-11.

24. A second device, comprising: at least one processor; as well as at least one memory including computer program code; The at least one memory and the computer program code are configured to, together with the at least one processor, cause the second device to perform the method according to any one of claims 12-22.

25. A computer-readable storage medium, the computer-readable storage medium comprising program instructions stored thereon, the instructions, when executed by a device, causing the device to perform the method according to any one of claims 1-11.

26. A computer-readable storage medium comprising program instructions stored thereon, which instructions, when executed by a device, cause the device to perform the method according to any one of claims 12-22.

27. An apparatus comprising means for performing the method according to any one of claims 1-11.

28. An apparatus comprising circuitry configured to cause the apparatus to perform the method according to any one of claims 1-11.

29. An apparatus comprising means for performing the method according to any one of claims 12-22.

30. An apparatus comprising circuitry configured to cause the apparatus to perform the method according to any one of claims 12-22.

Images