Increasing spectral efficiency and reducing latency of random data arrival time

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. An apparatus and method for reducing latency in data transmission. A method performed by a user equipment (UE) includes receiving first information of a configured grant (CG) configuration for transmission of a physical uplink shared channel (PUSCH) through radio resource control signaling, where the first information includes a time period; determining a first transmission opportunity (TO) for transmitting the corresponding plurality of first CG-PUSCHs from the first TO set in the time period; and determining first control information providing an indication of the first TO. The method further includes: multiplexing the first control information in a first CG-PUSCH from the plurality of first CG-PUSCHs, and multiplexing the second control information in PUSCHs other than the first CG-PUSCHs; and transmitting the first CG-PUSCH and the PUSCH. The second control information provides first acknowledgement information or channel state information. The transmission of the first CG-PUSCH overlaps with the transmission of the PUSCH in time.

Description

Technical Field

[0001] The present disclosure relates generally to wireless communication systems, and more particularly to resolving conflicts between transmissions of user devices in a network on data channels, as well as enhancing the capacity and reducing transmission latency of user devices in the network, such as for supporting services that may be associated with augmented reality, virtual reality, or cloud gaming (collectively referred to as XR services). Background Art

[0002] Fifth-generation (5G) or new radio (NR) mobile communications have been gaining momentum recently, with global technical activities from industry and academia on various candidate technologies. Candidate enablers for 5G / NR mobile communications include massive antenna technologies that provide beamforming gain and support increased capacity from traditional cellular frequency bands to high frequencies, new waveforms (e.g., new radio access technologies (RATs)) that can flexibly adapt to various services / applications with different requirements, and new multiple access schemes that support large-scale connectivity.

[0003] 5G mobile communications technology defines a wide frequency band capable of high transmission rates and new services, and can be implemented not only in "sub-6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands, known as millimeter waves, including 28 GHz and 39 GHz. Furthermore, consideration is being given to implementing 6G mobile communications technology (referred to as "beyond 5G systems") in terahertz frequency bands (e.g., the 95 GHz to 3 THz band) in order to achieve transmission rates fifty times faster than 5G mobile communications technology and ultra-low latency, one-tenth that of 5G mobile communications technology.

[0004] At the beginning of the development of 5G mobile communication technology, regarding enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC) and massive machine-type communication (mMTC), in order to support services and meet performance requirements, standardization of the following technologies has been ongoing: beamforming and massive MIMO for reducing radio wave path loss and increasing radio wave transmission distance in millimeter waves, supporting parameter sets for dynamic operation of efficient utilization of millimeter wave resources and time slot formats (for example, operation of multiple subcarrier spacing), initial access technology for supporting multi-beam transmission and wide frequency bands, definition and operation of bandwidth parts (BWPs), new channel coding methods such as low-density parity-check (LDPC) codes for large-scale data transmission and polar codes for highly reliable transmission of control information, L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0005] Currently, with respect to services supported by 5G mobile communication technology, the industry is continuously discussing improvements and performance enhancements to initial 5G mobile communication technology, and has completed physical layer standardization for technologies such as vehicle-to-everything (V2X) for assisting driving decisions of autonomous vehicles based on information transmitted by the vehicle regarding its location and status and for improving user convenience, New Radio Unlicensed (NR-U) for system operation in compliance with various regulatory requirements in unlicensed frequency bands, NR UE energy saving, non-terrestrial network (NTN) for direct UE satellite communication to ensure coverage in areas where communication with terrestrial networks is not possible, and positioning.

[0006] In addition, standardization of air interface architecture / protocols for the following technologies is ongoing: for example, the Industrial Internet of Things (IIoT) for supporting new services through interoperability and integration with other industries; Integrated Access and Backhaul (IAB) for providing nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; mobility enhancements including conditional handover and DAPS (Dual Active Protocol Stack) handover; and two-step random access (2-step RACH for NR) for simplifying the random access process. Furthermore, standardization of system architecture / services for the following technologies is ongoing: a 5G baseline architecture (e.g., a service-based architecture or service-based interface) for combining network function virtualization (NFV) and software-defined networking (SDN) technologies; and mobile edge computing (MEC) for receiving services based on UE location.

[0007] With the commercialization of 5G mobile communication systems, the exponentially growing number of connected devices will be connected to the communication network, and it is expected that the functionality and performance of 5G mobile communication systems and the integrated operation of connected devices will need to be enhanced. To this end, new research is being put on the agenda regarding the following technologies: extended reality (XR) for efficient support of augmented reality (AR), virtual reality (VR), mixed reality (MR), etc.; 5G performance improvements and complexity reduction through the use of artificial intelligence (AI) and machine learning (ML); support for AI services, support for metaverse services, and drone communications.

[0008] Furthermore, this development of 5G mobile communication systems will not only lay the foundation for the development of new waveforms for providing coverage in the terahertz band for 6G mobile communication technology; multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and massive antennas; metamaterial-based lenses and antennas for improving coverage of terahertz band signals; and high-dimensional spatial multiplexing technologies using orbital angular momentum (OAM) and reconfigurable smart surfaces (RIS). It will also lay the foundation for the development of full-duplex technologies for improving the frequency efficiency of 6G mobile communication technology and improving system networks; AI-based communication technologies for achieving system optimization by leveraging satellites and artificial intelligence (AI) from the design stage and internalizing end-to-end AI support functions; and next-generation distributed computing technologies for implementing services at a complexity level that exceeds the operational capabilities of UEs by utilizing ultra-high-performance communication and computing resources.

[0009] The above information is provided as background information only to assist with understanding the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above information may qualify as prior art with respect to the present disclosure. Summary of the Invention

[0010] [Technical Issues]

[0011] The present disclosure relates to apparatus and methods for improving spectrum efficiency and reducing delays in random data arrival times.

[0012] The technical objectives achieved by the various embodiments of the present disclosure are not limited to the above-mentioned technical objectives, and those skilled in the art may consider other technical objectives not mentioned from the various embodiments of the present disclosure to be described below.

[0013] [Solution to the problem]

[0014] In one embodiment, a method performed by a user equipment (UE) is provided. The method includes: receiving, via radio resource control signaling, first information regarding a configured grant (CG) configuration for transmitting a physical uplink shared channel (PUSCH), wherein the first information includes a time period; determining, from a first set of TOs within the time period, a first transmission opportunity (TO) for transmitting each first CG-PUSCH; and determining first control information indicating the first TO. The method also includes: multiplexing the first control information in a first CG-PUSCH from a plurality of first CG-PUSCHs and multiplexing second control information in a PUSCH other than the first CG-PUSCH; and transmitting the first CG-PUSCH and the PUSCH. The first CG-PUSCH is the earliest in time among the plurality of first CG-PUSCHs. The second control information provides first acknowledgment information or channel state information. The transmission of the first CG-PUSCH overlaps in time with the transmission of the PUSCH.

[0015] In another embodiment, a UE is provided. The UE includes a transceiver configured to receive first information of a CG configuration for sending a PUSCH through radio resource control signaling. The first information includes a time period. The UE also includes a processor operably connected to the transceiver. The processor is configured to determine a first TO for sending each first CG-PUSCH from a first TO set within the time period; determine first control information providing an indication of the first TO; multiplex the first control information in a first CG-PUSCH from a plurality of first CG-PUSCHs; and multiplex second control information in a PUSCH other than the first CG-PUSCH. The first CG-PUSCH is the earliest in time among the plurality of first CG-PUSCHs. The second control information provides first confirmation information or channel state information. The transceiver is also configured to send the first CG-PUSCH and the PUSCH. The transmission of the first CG-PUSCH overlaps in time with the transmission of the PUSCH.

[0016] In another embodiment, a base station (BS) is provided. The BS includes a transceiver configured to send first information of a CG configuration for receiving a PUSCH through radio resource control signaling. The first information includes a time period. The BS also includes a processor operably connected to the transceiver. The processor is configured to determine a first RO for receiving each first CG-PUSCH from a first RO set within the time period. The transceiver is further configured to receive a first CG-PUSCH from a plurality of first CG-PUSCHs and a PUSCH other than the first CG-PUSCH. The first CG-PUSCH is the earliest in time among the plurality of first CG-PUSCHs. The reception of the first CG-PUSCH overlaps in time with the reception of the PUSCH. The first CG-PUSCH includes multiplexed first control information providing an indication of the first RO. The PUSCH includes multiplexed second control information providing first confirmation information or channel state information.

[0017] Other technical features will be apparent to those skilled in the art from the following drawings, description, and claims.

[0018] The above-mentioned various embodiments of the present disclosure are only some preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the present disclosure can be derived and understood by those skilled in the art based on the following detailed description of the present disclosure.

[0019] Before describing the following specific embodiments, it may be helpful to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupled" and its derivatives refer to any direct or indirect communication between two or more elements, regardless of whether those elements are in physical contact with one another. The terms "send," "receive," and "communicate," and their derivatives, encompass both direct and indirect communication. The terms "include," "comprise," and their derivatives, are intended to include, without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with" and its derivatives mean to include, be included within, be interconnected with, contain, be contained within, be connected to or connected with, be coupled to or coupled with, be communicable with, collaborate with, be interwoven, be in parallel, be in proximity to, be bound to or bound with, have, have the characteristics of, have a relationship with, and the like. The term "controller" refers to any device, system, or portion thereof that controls at least one operation. Such a controller may be implemented in hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller may be centralized or distributed, whether local or remote. The phrase "at least one of," when used with a list of items, means that different combinations of one or more of the listed items can be used, and only one of the items in the list may be required. For example, "at least one of the following: A, B, and C" includes any of the following combinations: A, B, C, A and B, A and C, B and C, and A, B, and C.

[0020] In addition, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer-readable program code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, processes, functions, objects, classes, instances, related data, or portions thereof suitable for implementation in suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random-access memory (RAM), hard drives, compact disks (CDs), digital video disks (DVDs), or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical, or other communication links that transmit transient electrical or other signals. Non-transitory computer-readable media includes media in which data can be permanently stored, as well as media in which data can be stored and subsequently overwritten, such as rewritable optical disks or erasable storage devices.

[0021] Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.

[0022] [Beneficial Effects of the Invention]

[0023] The present disclosure relates to apparatus and methods for improving spectrum efficiency and reducing delays in random data arrival times.

[0024] Effects that can be achieved by the present disclosure are not limited to the effects mentioned in the respective embodiments, and other effects that are not mentioned will be clearly understood by those skilled in the art from the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts: Figure 1 illustrates an example wireless network according to an embodiment of the present disclosure; Figure 2 An example gNodeB (gNB) according to an embodiment of the present disclosure is shown; Figure 3 An example user equipment (UE) according to an embodiment of the present disclosure is shown; Figure 4 illustrates an example wireless transmission path according to an embodiment of the present disclosure; Figure 5 illustrates an example wireless receive path according to an embodiment of the present disclosure; Figure 6 shows an example transmitter structure using orthogonal frequency division multiplexing (OFDM) according to an embodiment of the present disclosure; Figure 7 shows an example receiver structure using OFDM according to an embodiment of the present disclosure; Figure 8 An example procedure is shown for a UE to indicate the total number of CG-PUSCH TOs of a CG-PUSCH configuration in a transmission period in which the UE transmits a CG-PUSCH according to the present disclosure; Figure 9 An example procedure for a UE to indicate the remaining number of CG-PUSCH TOs in a transmission cycle in which the UE transmits CG-PUSCH is shown according to the present disclosure; Figure 10 An example process for a UE to count a certain number of CG-PUSCH TOs configured for a CG-PUSCH in a transmission period in which the UE transmits a CG-PUSCH according to the present disclosure is shown; Figure 11 An example procedure for a UE to indicate whether to use a CG-PUSCH TO subset of a certain number of CG-PUSCH TOs from a CG-PUSCH configuration in a transmission period for CG-PUSCH transmission according to the present disclosure is shown; Figure 12 An example procedure according to the present disclosure is shown in which a UE provides new radio CG uplink control information (nrCG-UCI) when a CG-PUSCH TO on a first cell, for a CG-PUSCH configuration with more than one CG-PUSCH TO in a transmission period, overlaps in time with a PUSCH or physical uplink control channel (PUCCH) transmission on a second cell; Figure 13 An example process according to the present disclosure is shown in which a UE determines a first number of CG-PUSCHs to transmit and a second number of CG-PUSCHs to drop from transmission when the first number and the second number of CG-PUSCHs overlap in time; Figure 14 An example process according to the present disclosure is shown in which a UE resolves a collision between a CG-PUSCH on a cell with a first transport block (TB) and a PUSCH on a cell with a second TB by multiplexing a first transport block (TB) in a PUSCH using the same time-frequency resources; Figure 15 An example process according to the present disclosure is shown in which a UE resolves a collision between a first CG-PUSCH having a first TB on a cell and a second CG-PUSCH having a second TB on a cell by multiplexing the first TB in the CG-PUSCH and increasing frequency resources or time resources for the second CG-PUSCH; Figure 16 An example process according to the present disclosure is shown in which a UE resolves a collision between a first CG-PUSCH on a cell having a first TB and a second PUSCH on a cell having a second TB by quantizing information from the first TB and multiplexing the quantized information as UCI in the second PUSCH; and Figure 17 An example process for a UE to resolve a conflict between a PUCCH transmission on a first cell and a PUSCH transmission on a second cell according to the present disclosure is shown. DETAILED DESCRIPTION

[0026] Discussed below Figures 1 to 17 The various embodiments used to describe the principles of the present disclosure in this patent document are merely examples and should not be interpreted in any way as limiting the scope of the present disclosure. Those skilled in the art will understand that the principles of the present disclosure can be implemented in any suitably arranged system or device.

[0027] The following documents and standard descriptions are incorporated by reference into the present disclosure as if fully set forth herein: 3GPP TS 38.211 v17.4.0, “NR; Physical Channels and Modulation”; 3GPP TS 38.212 v17.4.0, “E-UTRA; NR; Multiplexing and Channel Coding”; 3GPP TS 38.213 v17.4.0, “NR; Physical Layer Procedures for Control”; 3GPP TS 38.214 v17.4.0, “NR; Physical Layer Procedures for Data”; 3GPP TS 38.321 v17.3.0, “NR; Medium Access Control (MAC) Protocol Specification”; 3GPP TS 38.331 v17.3.0, “NR; Radio Resource Control (RRC) Protocol Specification”.

[0028] Wireless communications are one of the most successful innovations in recent history. The number of wireless subscriptions recently surpassed 5 billion and continues to grow rapidly. Demand for wireless data services is rapidly increasing due to the growing consumer and business adoption of smartphones and other mobile data devices (e.g., tablets, notebooks, netbooks, e-readers, and machine-type devices). To meet this high growth in mobile data services and support new applications and deployments, improvements in radio interface efficiency and coverage are crucial.

[0029] To meet the increased demand for wireless data services since the deployment of 4G communication systems, and to enable a variety of vertical applications, 5G / NR communication systems have been developed and are currently being deployed. 5G / NR communication systems are considered to be implemented in higher-frequency (millimeter wave) bands (e.g., 28 GHz or 60 GHz bands) to achieve higher data rates, or in lower-frequency bands (e.g., 6 GHz) to achieve robust coverage and mobility support. To reduce radio wave propagation losses and increase transmission distances, beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antenna technologies are being discussed in 5G / NR communication systems.

[0030] Furthermore, in 5G / NR communication systems, system network improvements are being developed based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, cooperative communications, coordinated multi-point (CoMP), and receiver-side interference cancellation.

[0031] The discussion of 5G systems and their associated frequency bands is for reference only, as certain embodiments of the present disclosure may be implemented in 5G systems. However, the present disclosure is not limited to 5G systems or their associated frequency bands, and embodiments of the present disclosure may be used in conjunction with any frequency band. For example, aspects of the present disclosure may also be applied to the deployment of 5G communication systems, 6G, or even later versions that may utilize terahertz (THz) frequency bands.

[0032] The following Figures 1 to 3 Various embodiments are described for implementing and using Orthogonal Frequency Division Multiplexing (OFDM) or Orthogonal Frequency Division Multiple Access (OFDMA) communication techniques in wireless communication systems. Figures 1 to 3 The description is not meant to imply physical or architectural limitations to the manner in which different embodiments may be implemented. Different embodiments of the disclosure may be implemented in any suitably arranged communications system.

[0033] Figure 1 An example wireless network 100 according to the present disclosure is shown. Figure 1 The embodiment of the wireless network 100 shown is for illustration only. Other embodiments of the wireless network 100 may be used without departing from the scope of the present disclosure.

[0034] Wireless network 100 includes gNodeB (gNB) 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one Internet Protocol (IP) network 130, such as the Internet, a private IP network, or other data network.

[0035] Depending on the network type, other well-known terms such as "base station" or "access point" may be used instead of "gNodeB" or "gNB." For convenience, the terms "gNodeB" and "gNB" are used in this patent document to refer to network infrastructure components that provide wireless access to remote terminals. Furthermore, depending on the network type, other well-known terms such as "mobile station," "subscriber station," "remote terminal," "wireless terminal," or "user equipment" may be used instead of "user equipment" or "UE." For convenience, the terms "user equipment" and "UE" are used in this patent document to refer to remote wireless devices that wirelessly access a gNB, whether the UE is a mobile device (e.g., a mobile phone or smartphone) or something typically considered a stationary device (e.g., a desktop computer or vending machine). A UE may also be a car, truck, van, drone, or any similar machine or a device within such a machine.

[0036] gNB 102 provides wireless broadband access to network 130 for a plurality of first user equipment (UEs) within gNB 102's coverage area 120. The plurality of first UEs include: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M) such as a cellular phone, wireless laptop, wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a plurality of second UEs within gNB 103's coverage area 125. The plurality of second UEs include UE 115, UE 116, UE 117, and UE 118. In some embodiments, one or more of gNBs 101-103 can communicate with each other and with UEs 111-118 using 5G, Long Term Evolution (LTE), LTE-A, WiMAX, or other advanced wireless communication technologies. In some embodiments, multiple UEs (e.g., UE 117, UE 118, and UE 119) can communicate directly with each other via device-to-device communication. In some embodiments, a UE (e.g., UE 119) is outside the coverage area of the network but can communicate with other UEs within or outside the coverage area of the network (e.g., UE 118).

[0037] The dashed lines illustrate the approximate extents of coverage areas 120 and 125, which are shown as approximately circular for purposes of illustration and explanation only. It should be clearly understood that coverage areas associated with gNBs, such as coverage areas 120 and 125, may have other shapes, including irregular shapes, depending on the configuration of the gNB and variations in the radio environment associated with natural and man-made obstacles.

[0038] although Figure 1 One example of a wireless network 100 is shown, but may be Figure 1 Various changes may be made. For example, wireless network 100 may include any number of gNBs and any number of UEs in any suitable arrangement. Furthermore, gNB 101 may communicate directly with any number of UEs and provide those UEs with wireless broadband access to network 130. Similarly, each of gNBs 102-103 may communicate directly with network 130 and provide UEs with direct wireless broadband access to network 130. Furthermore, gNB 101, gNB 102, and / or gNB 103 may provide access to other or additional external networks, such as an external telephone network or other types of data networks.

[0039] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof to support improved spectral efficiency and reduced delays in random data arrival times. In certain embodiments, one or more of gNBs 101-103 include circuitry, programming, or a combination thereof to support improved spectral efficiency and reduced delays in random data arrival times.

[0040] Figure 2 An example gNB 102 according to the present disclosure is shown. Figure 2 The embodiment of gNB 102 shown is for illustration only and Figure 1 Other gNBs in the same or similar configurations may have the same or similar configurations. However, gNBs have multiple configurations, and Figure 2 The scope of this disclosure is not limited to any particular implementation of a gNB. Note that gNB 101 and gNB 103 may include the same or similar structure as gNB 102.

[0041] like Figure 2 As shown, gNB 102 includes multiple antennas 205a-205n, multiple transceivers 210a-210n, a controller / processor 225, memory 230, and a backhaul or network interface 235.

[0042] Transceivers 210a-210n receive incoming RF signals from antennas 205a-205n, such as signals transmitted by UEs in network 100. Transceivers 210a-210n downconvert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are processed by receive (RX) processing circuitry within transceivers 210a-210n and / or controller / processor 225. The RX processing circuitry within transceivers 210a-210n and / or controller / processor 225 filters, decodes, and / or digitizes the baseband or IF signals to generate processed baseband signals. Controller / processor 225 may further process the baseband signals.

[0043] Transmit (TX) processing circuitry within transceivers 210a-210n and / or controller / processor 225 receives analog or digital data (e.g., voice data, web page data, email, or interactive video game data) from controller / processor 225. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to produce processed baseband or IF signals. Transceivers 210a-210n upconvert the baseband or IF signals into RF signals that are transmitted via antennas 205a-205n.

[0044] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the reception of uplink (UL) channel signals and the transmission of downlink (DL) channel signals by transceivers 210a-210n according to well-known principles. The controller / processor 225 may also support additional functionality, such as more advanced wireless communication capabilities. For example, the controller / processor 225 may support beamforming or directional routing operations, in which output / input signals from / to multiple antennas 205a-205n are weighted differently to effectively steer the output signals in a desired direction. As another example, the controller / processor 225 may support methods for improving spectral efficiency and reducing random data arrival delays. The controller / processor 225 may also support any of a variety of other functions within the gNB 102.

[0045] The controller / processor 225 is also capable of executing programs and other processes, such as the OS, that reside in the memory 230. The controller / processor 225 can move data into or out of the memory 230 as required by the executing processes.

[0046] The controller / processor 225 is also coupled to a backhaul or network interface 235. The backhaul or network interface 235 allows the gNB 102 to communicate with other devices or systems via a backhaul connection or over a network. The interface 235 can support communication over any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a system supporting 5G / NR, LTE, or LTE-A), the interface 235 can allow the gNB 102 to communicate with other gNBs via a wired or wireless backhaul connection. When the gNB 102 is implemented as an access point, the interface 235 can allow the gNB 102 to communicate over a wired or wireless local area network (LAN) or with a larger network (e.g., the Internet) via a wired or wireless connection. The interface 235 includes any suitable structure that supports communication over a wired or wireless connection (e.g., Ethernet or a transceiver).

[0047] Memory 230 is coupled to controller / processor 225. A portion of memory 230 may include RAM, and another portion of memory 230 may include flash memory or other ROM.

[0048] although Figure 2 An example of gNB 102 is shown, but the Figure 2 For example, gNB 102 may include any number of Figure 2 Each component shown. In addition, Figure 2 The various components in can be combined, further subdivided, or omitted, and additional components can be added according to specific needs.

[0049] Figure 3 An example UE 116 is shown in accordance with an embodiment of the present disclosure. Figure 3 The embodiment of UE 116 shown is for illustration only. Figure 1 UE 111-UE 115 may have the same or similar configuration. However, UE has a variety of configurations, and Figure 3 The scope of this disclosure is not limited to any particular implementation of a UE.

[0050] like Figure 3 As shown, UE 116 includes antenna 305, transceiver 310, and microphone 320. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface (IF) 345, input 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0051] Transceiver 310 receives an incoming RF signal from antenna 305, transmitted by a gNB in network 100. Transceiver 310 downconverts the incoming RF signal to produce an intermediate frequency (IF) or baseband signal. The IF or baseband signal is processed by RX processing circuitry within transceiver 310 and / or processor 340, which filters, decodes, and / or digitizes the baseband or IF signal to produce a processed baseband signal. The RX processing circuitry transmits the processed baseband signal to speaker 330 (e.g., for voice data) or to processor 340 (e.g., for web browsing data) for processing.

[0052] The TX processing circuitry in the transceiver 310 and / or processor 340 receives analog or digital voice data from the microphone 320 or other outgoing baseband data (e.g., web page data, email, or interactive video game data) from the processor 340. The TX processing circuitry encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. The transceiver 310 up-converts the baseband or IF signal into an RF signal that is transmitted via the antenna 305.

[0053] The processor 340 may include one or more processors or other processing devices and executes the OS 361 stored in the memory 360 to control the overall operation of the UE 116. For example, the processor 340 may control the transceiver 310 to receive downlink channel signals and transmit uplink channel signals according to well-known principles. In some embodiments, the processor 340 includes at least one microprocessor or microcontroller.

[0054] Processor 340 is also capable of executing other processes and programs residing in memory 360, such as processes for improving spectral efficiency and reducing delays in random data arrival times. Processor 340 can move data into or out of memory 360 as needed by the executing processes. In some embodiments, processor 340 is configured to execute applications 362 based on OS 361 or in response to signals received from a gNB or operator. Processor 340 is also coupled to I / O interface 345, which provides UE 116 with the ability to connect to other devices such as laptops and handheld computers. I / O interface 345 is the communication path between these accessories and processor 340.

[0055] The processor 340 is also coupled to an input 350, including, for example, a touch screen, a keypad, etc., and a display 355. An operator of the UE 116 can use the input 350 to enter data into the UE 116. The display 355 can be a liquid crystal display, a light emitting diode display, or other display capable of presenting text and / or at least limited graphics, such as from a website.

[0056] Memory 360 is coupled to processor 340. A portion of memory 360 may include random access memory (RAM), and another portion of memory 360 may include flash memory or other read-only memory (ROM).

[0057] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3 Various components in the can be combined, further subdivided, or omitted, and additional components can be added as needed. As a specific example, processor 340 can be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In another example, transceiver 310 can include any number of transceivers and signal processing chains and can be connected to any number of antennas. In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smartphone, but the UE may be configured to operate as other types of mobile or stationary devices.

[0058] Figure 4 and Figure 5 1 shows an example wireless transmit and receive path according to the present disclosure. In the following description, Figure 4 The transmit path 400 of can be described as being implemented in a gNB (e.g., gNB 102), and Figure 5The receive path 500 of FIG. 5 may be described as being implemented in a UE (e.g., UE 116). However, it is understood that the receive path 500 may be implemented in a gNB and the transmit path 400 may be implemented in a UE. Furthermore, it is understood that in the case of device-to-device communication, the receive path 500 may be implemented in one UE and the transmit path 400 may be implemented in another UE. In some embodiments, as described in the embodiments of the present disclosure, the receive path 500 is configured to support improved spectral efficiency and reduced delay in random data arrival times.

[0059] like Figure 4 The transmit path 400 shown includes a channel coding and modulation block 405, a serial-to-parallel conversion (S-to-P) block 410, an N-point inverse fast Fourier transform (IFFT) block 415, a parallel-to-serial conversion (P-to-S) block 420, a cyclic prefix addition block 425, and an upconverter (UC) 430. Figure 5 The illustrated receive path 500 includes a downconverter (DC) 555 , a remove cyclic prefix block 560 , a serial-to-parallel (S-to-P) block 565 , an N-point fast Fourier transform (FFT) block 570 , a parallel-to-serial (P-to-S) block 575 , and a channel decoding and demodulation block 580 .

[0060] like Figure 4 As shown, channel coding and modulation block 405 receives a set of information bits, applies coding (e.g., low-density parity check (LDPC) coding), and modulates the input bits (e.g., using quadrature phase shift keying (QPSK) or quadrature amplitude modulation (QAM)) to produce a sequence of frequency-domain modulation symbols. Serial-to-parallel conversion block 410 converts (e.g., demultiplexes) the serial modulation symbols into parallel data to generate N parallel symbol streams, where N is the IFFT / FFT size used in gNB 102 and UE 116. N-point IFFT block 415 performs an IFFT operation on the N parallel symbol streams to generate a time-domain output signal. Parallel-to-serial conversion block 420 converts (e.g., multiplexes) the parallel time-domain output symbols from N-point IFFT block 415 to generate a serial time-domain signal. Add cyclic prefix block 425 inserts a cyclic prefix into the time-domain signal. Upconverter 430 modulates (e.g., upconverts) the output of Add cyclic prefix block 425 to RF frequency for transmission via a wireless channel. The signal may also be filtered at baseband before conversion to RF frequency.

[0061] The transmitted RF signal from gNB 102 reaches UE 116 after passing through the wireless channel, and operations reverse to those at gNB 102 are performed at UE 116.

[0062] like Figure 5As shown, downconverter 555 downconverts the received signal to baseband frequency, and cyclic prefix removal block 560 removes the cyclic prefix to generate a serial time-domain baseband signal. Serial-to-parallel conversion block 565 converts the time-domain baseband signal into parallel time-domain signals. N-point FFT block 570 performs an FFT algorithm to generate N parallel frequency-domain signals. Parallel-to-serial conversion block 575 converts the parallel frequency-domain signals into a sequence of modulated data symbols. Channel decoding and demodulation block 580 demodulates and decodes the modulated symbols to recover the original input data stream.

[0063] Each of gNB 101-gNB 103 can implement the following Figure 4 The transmission path 400 shown is similar to that for transmitting to UE111-UE116 in the downlink, and can be implemented as follows: Figure 5 The illustrated receive path 500 is similar to that for receiving in the uplink from UEs 111-116. Similarly, each of UEs 111-116 may implement transmit path 400 for transmitting in the uplink to BSs 101-103 and may implement receive path 500 for receiving in the downlink from gNBs 101-103.

[0064] Figure 4 and Figure 5 Each of the components in may be implemented using hardware or a combination of hardware and software / firmware. As a specific example, Figure 4 and Figure 5 At least some of the components in can be implemented in software, while other components can be implemented by configurable hardware or a mixture of software and configurable hardware. For example, FFT block 570 and IFFT block 515 can be implemented as configurable software algorithms, where the value of size N can be modified according to the implementation.

[0065] Furthermore, although FFT and IFFT are described as being used, this is for illustrative purposes only and should not be construed as limiting the scope of the present disclosure. Other types of transforms, such as discrete Fourier transform (DFT) and inverse discrete Fourier transform (IDFT) functions, may be used. It will be appreciated that for DFT and IDFT functions, the value of the variable N may be any integer (e.g., 1, 2, 3, 4, etc.), while for FFT and IFFT functions, the value of the variable N may be any integer that is a power of 2 (e.g., 1, 2, 4, 8, 16, etc.).

[0066] although Figure 4 and Figure 5 Examples of wireless transmit and receive paths are shown, but Figure 4 and Figure 5 Make various changes. For example, Figure 4 and Figure 5The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs. Figure 4 and Figure 5 Examples illustrating the types of transmit and receive paths that may be used in a wireless network. Any other suitable architecture may be used to support wireless communications in a wireless network.

[0067] In the following, an italicized name of a parameter means that the parameter is provided by a higher level.

[0068] The unit used for DL signaling or UL signaling on a cell is called a time slot and can include one or more symbols. The bandwidth (BW) unit is called a resource block (RB). One RB includes multiple subcarriers (SCs). For example, a time slot may have a duration of 1 millisecond, and an RB may have a bandwidth of 180 kHz and include 12 SCs with an inter-SC spacing of 15 kHz. The subcarrier spacing (SCS) can be configured by the SCS. Determined kHz. A subcarrier on a symbol is called a resource element (RE). A RB on a symbol is called a physical RB (PRB).

[0069] DL signals include data signals conveying information content, control signals conveying DL control information (DCI), and reference signals (RS), also known as pilot signals. The gNB transmits data information or DCI via the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The PDSCH or PDCCH can be transmitted over a variable number of time slot symbols, including one time slot symbol. PDCCH transmissions are performed on multiple control channel elements (CCEs) within a control resource set (CORESET), with the multiple CCEs selected from a predetermined set of CCE numbers (called the CCE aggregation level).

[0070] PDSCH transmissions are scheduled by a DCI format or semi-persistently scheduled (SPS) as configured by higher layers and activated by the DCI format. SPS PDSCH reception can be based on one or more configurations for corresponding parameters provided by higher layers, as described in TS 38.331 v17.0.0, "NR; Radio Resource Control (RRC) Protocol Specification." A UE's PDSCH reception provides one or more transport blocks (TBs), where a TB is associated with a Hybrid Automatic Repeat Request (HARQ) process indicated by the HARQ process number field in the DCI format that schedules PDSCH reception or activates SPS PDSCH reception. A TB transmission can be an initial transmission or a retransmission, as identified by the New Data Indicator (NDI) field in the DCI format that schedules PDSCH reception providing a retransmission of a TB for a given HARQ process number.

[0071] The gNB transmits one or more of several types of RS, including Channel State Information RS (CSI-RS) and Demodulation RS (DMRS), as described in TS 38.211 v17.1.0, "NR; Physical Channels and Modulation." CSI-RS is primarily used by UEs to perform measurements and provide channel state information (CSI) to the gNB. For channel measurements or time tracking, non-zero power CSI-RS (NZP CSI-RS) resources are used. For interference measurement reporting (IMR), CSI-Interference Measurement (CSI-IM) resources are used (see also TS 38.213 v17.1.0, "NR; Controlled Physical Layer Procedures"). CSI-IM resources can also be associated with zero power CSI-RS (ZP CSI-RS) configurations. The UE can determine the CSI-RS reception parameters through DL control signaling or higher-layer signaling, such as radio resource control (RRC) signaling from the gNB (see also TS 38.331 v16.5.0 “NR; Radio Resource Control (RRC) Protocol Specification”). DMRS is typically transmitted only within the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0072] UL signals also include data signals conveying information content, control signals conveying UL control information (UCI), DMRS associated with data or UCI demodulation, sounding RS (SRS) for the gNB to perform UL channel measurements, and random access (RA) preambles for UEs to perform random access (see also TS 38.211 v17.1.0, "NR; Physical Channels and Modulation"). UEs transmit data information or UCI via their respective physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). The PUSCH or PUCCH can be transmitted over a variable number of symbols, including one symbol, in a slot. When a UE transmits both data information and UCI simultaneously, it may multiplex both on the PUSCH or, depending on UE capabilities, may simultaneously transmit the PUSCH with data information and the PUCCH with UCI, at least when transmissions occur in different cells.

[0073] PUSCH transmissions can be scheduled by DCI format or configured by higher layers, which is then called configured grant (CG) PUSCH. As described in TS 38.214 v17.1.0 "NR; Physical layer procedures for data", multiple configurations for CG-PUSCH transmissions can be provided to the UE, and the configuration can be selected based on the characteristics of the CG-PUSCH transmission (e.g., transport block size or delay requirements).

[0074] UCI includes: Hybrid Automatic Repeat Request Acknowledgement (HARQ-ACK) information, which indicates correct or incorrect decoding of a transport block (TB) or code block group (CBG) in the PDSCH; a Scheduling Request (SR), which indicates whether the UE has data to transmit in its buffer; and a CSI report, which enables the gNB to select appropriate parameters for PDSCH / TB or PDCCH / DCI format transmission to the UE. HARQ-ACK information is a positive acknowledgement (ACK) when the TB is decoded correctly, or a negative acknowledgement (NACK) when the TB is decoded incorrectly. The UE may need to report HARQ-ACK information in response to correct or incorrect decoding of the DCI format, as well as in response to correct or incorrect decoding of the TB. For example, the decoded HARQ-ACK information for the DCI format may be a DCI format for indicating SPS PDSCH activation / release, or a DCI format for indicating dormant / non-dormant BWP for a cell from a group of cells, etc., as described in TS 38.213 v17.4.0 "NR; Physical layer procedures for control". The UE is in the slot indicated by the PDSCH-to-HARQ_feedback timing indicator field in the DCI format, from a group of slot timing values. The HARQ-ACK information is multiplexed in the time slot indicated by the higher layer or the time slot indicated by the higher layer.

[0075] The UE sends a PUCCH with a (positive) SR to indicate that it has data in its buffer for transmission. Upon detecting a PUCCH with an SR, the gNB can schedule a PUSCH for the UE to also provide a Buffer Status Report (BSR), which gives the gNB information about the amount of data the UE needs to provide. This process introduces additional latency in the UE providing data, particularly for unpaired spectrum operation (TDD), because the UE needs to send a PUSCH to provide the BSR before the gNB can schedule the UE with the required resources, which the gNB can determine based on the BSR.

[0076] UL RSs include DMRS and SRS. DMRS is typically transmitted within the bandwidth of the corresponding PUSCH or PUCCH. The gNB can use DMRS to demodulate information in the corresponding PUSCH or PUCCH. The SRS is transmitted by the UE to provide the gNB with UL CSI and, for TDD systems, the PMI for DL transmissions. Additionally, the UE may transmit the Physical Random Access Channel (PRACH) as part of the random access procedure or for other purposes.

[0077] DL reception and UL transmission by a UE can be configured to occur within corresponding DL bandwidth parts (BWPs) and UL BWPs. The DL / UL BWPs are less than or equal to the DL / UL bandwidth of the serving cell. Multicast (or groupcast) PDSCH reception can occur in a common frequency region for a group of UEs, where the common frequency region is within the active DL BWP for each UE in the group. DL transmissions from the gNB and UL transmissions from the UE can be based on orthogonal frequency division multiplexing (OFDM) waveforms, including a variant called DFT-spread OFDM that uses DFT precoding (see also TS 38.211 v17.4.0, "NR; Physical Channels and Modulation").

[0078] Figure 6 An example transmitter structure using OFDM 600 is shown according to an embodiment of the present disclosure. Figure 6 The embodiment of the transmitter structure using OFDM 600 shown in FIGURE 6 is for illustration only. Figure 6 One or more of the components shown may be implemented in dedicated circuitry configured to perform the recited functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the recited functions. Figure 6 The scope of this disclosure is not limited to any particular implementation of a transmitter structure using OFDM 600 .

[0079] like Figure 6 As shown, information bits such as DCI bits or data bits 610 are encoded by an encoder 620, rate-matched to the allocated time / frequency resources by a rate matcher 630, and modulated by a modulator 640. Subsequently, the modulated coded symbols and DMRS or CSI-RS 650 are mapped to an SC 660 by an SC mapping unit 665, an inverse fast Fourier transform (IFFT) is performed by a filter 670, a cyclic prefix (CP) is added by a CP insertion unit 680, and the resulting signal is filtered by a filter 690 and transmitted by a radio frequency (RF) unit 695.

[0080] Figure 7 An example receiver structure using OFDM 700 is shown in accordance with an embodiment of the present disclosure. Figure 7 The embodiment of the receiver structure using OFDM 700 shown in FIGURE 7 is for illustration only. Figure 7 One or more of the components shown may be implemented in dedicated circuitry configured to perform the recited functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the recited functions. Figure 7 The scope of this disclosure is not limited to any particular implementation of a receiver structure using OFDM 700 .

[0081] like Figure 7 As shown, a received signal 710 is filtered by a filter 720 , a CP removal unit removes the CP 730 , a filter 740 applies a fast Fourier transform (FFT), an SC demapping unit 750 demaps the SC selected by a BW selector unit 755 , received symbols are demodulated by a channel estimator and demodulator unit 760 , a rate dematcher 770 restores rate matching, and a decoder 780 decodes the resulting bits to provide information bits 790 .

[0082] One important application of wireless communications is augmented reality (AR), cloud gaming, and virtual reality (VR), collectively referred to as XR. XR services, including video services, represent challenging scenarios for networks to support due to the need for very large physical layer data rates (e.g., 30Mbps-60Mbps for video services) and low end-to-end latency (also known as packet delay budget (PDB), e.g., 10 msec).

[0083] PUSCH transmissions may be scheduled by a DCI format or configured by higher layers and are then referred to as configured grant (CG) PUSCH. Despite the inability to perform dynamic link adaptation, CG-PUSCH transmissions may provide capacity improvements by facilitating achievement of PDB targets at the expense of worse spectral efficiency compared to PUSCH transmissions scheduled by a DCI format (UL grant). In the case of small PDB, CG-PUSCH transmissions avoid the delay associated with the transmission of a PUCCH providing an SR followed by the transmission of a PDCCH providing an UL grant that schedules the PUSCH transmission. A UE may provide multiple CG-PUSCH transmission opportunities in the period of a single CG-PUSCH configuration, for example based on parameters as described in TS 38.214 v17.4.0 “NR; Physical layer procedures for data” cg-nrofSlot and cg-nrofPUSCH-InSlot .

[0084] XR services from a UE may include multiple data streams, each with its own characteristics, such as the required data rate and packet delay budget (PDB). The communication may be based on a packet data unit (PDU) set, which includes a certain number of PDUs with information generated at the application level, such as frames / video segments. The individual IP packets of a PDU set are interdependent and need to be received within the PDB for the PDU set. In some implementations, the application layer requires all PDUs, and if at least one PDU cannot be delivered within the PDB, the entire PDU set may be discarded, while in other implementations, error concealment may be applied to up to a certain number of lost PDUs, but then the order of the PDUs is also critical.

[0085] For example, XR traffic may include video frames and attitude / control information, which describes the state of the viewer in the XR scene tracked by the UE (also known as the field of view (FoV)) and can be used by the gNB scheduler to adjust the data rate of the XR traffic. The attitude / control information is periodic, for example, with a period of 4 or 5 msec, and typically has a small terabyte size, making it suitable for transmission via CG-PUSCH. Video traffic is also periodic, with a period of 16.67 or 33.33 msec, but is primarily characterized by jitter due to the video codec. This jitter can be described by a distribution such as a truncated Gaussian with a variance of 4 msec. Video traffic also has a small PDB requirement, for example, 20 or 30 msec, and requires a large data rate, for example, 30 Mbps. To facilitate achieving the PDB target, CG-PUSCH transmissions can also be applied to video frames to avoid scheduling delays associated with the following scenario: the UE requests PUSCH scheduling via a PUCCH transmission with a positive SR, and the gNB provides the DCI format for PUSCH scheduling via a subsequent PDCCH transmission before the UE sends the PUSCH. In addition, to achieve large data rates within the PDB target for video frames while considering the maximum transmit power available at the UE, multiple CG-PUSCH transmissions are required over consecutive slots (e.g., UL slots of a TDD UL-DL configuration) with enough symbols to carry the CG-PUSCH transmissions.

[0086] One issue arising from UEs with continuous CG-PUSCH transmissions for video traffic and frequent CG-PUSCH transmissions with attitude / control information is that these CG-PUSCH transmissions may occur in overlapping symbols (temporal overlap). This conflict between UE transmissions is common but is particularly severe in networks operating with TDD. For example, with a DL-focused TDD UL-DL configuration, such as a periodic configuration with DDD DU slots, conflicts between UE transmissions on different channels may occur consistently because they may always need to occur in the same slot. One approach to resolving conflicts between CG-PUSCH transmissions is to define rules for the UE to discard some overlapping CG-PUSCH transmissions. This approach may be sufficient when such overlap does not occur across multiple consecutive transmission opportunities for the CG-PUSCH transmissions that the UE is discarding. Another approach is to define rules to multiplex information from the CG-PUSCH transmissions that the UE is discarding (e.g., attitude / control information) into CG-PUSCH transmissions that the UE is not discarding (e.g., for video information). Another approach is to avoid such conflicts through network configuration of corresponding CG-PUSCH transmissions.

[0087] Another problem caused by UEs having time-overlapping PUSCH transmissions in a time slot is the need to define a multiplexing procedure for UCI in one or more PUCCH transmissions that overlap in time with the PUSCH transmission.

[0088] For multiple CG-PUSCH transmission opportunities (TOs) within a single CG-PUSCH configuration period and for periodic traffic generation such as video frames in XR, the UE can determine the size of the frames / PDUs in the period in which the UE generates frames. The UE can then determine the number of CG-PUSCH TOs in that period required to provide frames / PDUs of that size to the serving gNB based on the time-frequency resources, MCS, and number of layers used for CG-PUSCH transmission. For example, for a total of eight CG-PUSCH TOs in a transmission period, a small video frame / PDU may require CG-PUSCH transmission in only two CG-PUSCH TOs, while a large video frame / PDU may require CG-PUSCH transmission in eight CG-PUSCH TOs. To improve resource utilization and thereby spectral efficiency on the cell, the UE can inform the serving gNB of the number of CG-PUSCH TOs in the period in which the UE will transmit CG-PUSCH. The CG-PUSCH TOs may be consecutive to minimize the delay in providing video frames, or generally data packets. The UE can provide this information in the form of UCI multiplexed in the CG-PUSCH transmission. For simplicity, the UCI is referred to as nrCG-UCI. Since the UE will not transmit CG-PUSCH in the CG-PUSCH TO following the CG-PUSCH TO required for providing data packets within the period, the gNB can use the corresponding time-frequency resources to schedule other services. To functionally and efficiently support the above features, the following design aspects need to be defined.

[0089] The first design aspect is to define the procedure for the UE to provide nrCG-UCI, such as when the UE provides nrCG-UCI, the information provided by the nrCG-UCI, and the multiplexing of nrCG-UCI with other UCI in CG-PUSCH.

[0090] The second design aspect is to define a procedure for the UE to determine the nrCG-UCI when the UE cancels a certain number of CG-PUSCH TOs for which the UE was to transmit the corresponding TB, e.g., because the corresponding time resources overlap with another PUSCH transmission scheduled by the serving gNB, or because they overlap with DL symbols in case of TDD operation.

[0091] The third design aspect is to enable the UE to utilize time-frequency resources for CG-PUSCH transmission in the period before the UE sends the CG-PUSCH TO for the first CG-PUSCH. For example, due to jitter in the video frame generation time at the UE, the UE may not have any data to send in the first few CG-PUSCH TOs in the period, and a large amount of time-frequency resources on the cell may usually remain idle, thereby significantly reducing the spectrum efficiency on the cell.

[0092] The fourth design aspect is to select a PUSCH for multiplexing nrCG-UCI when the UE transmits more than one PUSCH simultaneously on corresponding more than one cell. Generally, as described in TS 38.213 v17.4.0, the UE determines the PUSCH for UCI multiplexing among the candidate PUSCHs as follows: - If the candidate PUSCHs include a first PUSCH scheduled by a DCI format and a second PUSCH not scheduled by a DCI format, and the UE is to multiplex UCI in one of the candidate PUSCHs, and the candidate PUSCHs satisfy the conditions for UCI multiplexing, the UE multiplexes UCI in the PUSCH from the first PUSCH.

[0093] - If the UE is to multiplex UCI in one of the candidate PUSCHs and the UE does not multiplex aperiodic CSI in any candidate PUSCH, then the UE multiplexes UCI in the PUSCH of the serving cell with the smallest index, provided that the UCI multiplexing conditions are met. If the UE transmits more than one PUSCH that meets the UCI multiplexing conditions on the serving cell with the smallest index in a timeslot, then the UE multiplexes UCI in the earliest PUSCH transmitted in the timeslot.

[0094] Therefore, the UE prefers to multiplex UCI in PUSCH transmissions scheduled by a DCI format over CG-PUSCH transmissions. However, this rule does not apply to multiple CG-PUSCH transmission opportunities within a single CG-PUSCH configuration period, because some of the earliest CG-PUSCH TOs may not be associated with any CG-PUSCH transmissions because the UE may not have generated the corresponding TBs. Consequently, the serving gNB cannot know whether nrCG-UCI is included in a PUSCH transmission scheduled by a DCI format on another cell.

[0095] Likewise, as described in TS 38.213 v17.4.0, if the UE

[0096] - configured for simultaneous PUCCH-PUSCH and to transmit a PUCCH with a first priority index and a PUSCH with a second priority index different from the first priority index, wherein the PUCCH and PUSCH overlap in time; - PUCCH and PUSCH can be sent simultaneously [18, TS 38.306], To resolve the temporal overlap between PUCCH and PUSCH, the UE excludes PUSCH, where no timeline condition is required for the excluded PUSCH. For example, when the UE is to transmit PUCCH and PUSCH on cells operating on different frequency bands, and the UE is configured for simultaneous PUCCH and PUSCH transmissions, and the PUCCH and PUSCH transmissions have different priorities, the UE multiplexes UCI in the PUCCH and transmits both the PUCCH and PUSCH. Similar to multiplexing nrCG-UCI in PUSCH transmissions scheduled by a DCI format, the serving gNB may not be able to determine whether the UE includes nrCG-UCI in the PUCCH transmission because the UE may or may not have PUCCH that temporally overlaps with the CG-PUSCH used for the transmission.

[0097] Various embodiments of the present disclosure recognize the need to define a UE procedure for providing an nrCG-UCI that indicates a certain number of CG-PUSCH TOs that the UE sends for a CG-PUSCH configuration having more than one CG-PUSCH TO in a transmission period.

[0098] Various embodiments of the present disclosure recognize the need to define a UE procedure for instructing the UE to send a certain number of CG-PUSCH TOs of a CG-PUSCH configuration in a transmission period when the UE cancels CG-PUSCH transmission in some CG-PUSCH TOs, where the CG-PUSCH configuration has more than one CG-PUSCH TO.

[0099] Various embodiments of the present disclosure recognize the need to enable the following CG-PUSCH TOs that utilize a CG-PUSCH configuration in a transmission period (the CG-PUSCH configuration has more than one CG-PUSCH TO) that are not used for CG-PUSCH transmission and precede the first CG-PUSCH TO used for CG-PUSCH transmission.

[0100] Various embodiments of the present disclosure recognize the need to define a UE process for multiplexing indications of a certain number of CG-PUSCH TOs when the UE sends more than one channel overlapping in time, and the UE sends a CG-PUSCH with a CG-PUSCH configuration of more than one CG-PUSCH TO in a transmission period in a certain number of CG-PUSCH TOs.

[0101] Various embodiments of the present disclosure recognize the need to define UE procedures for resolving time overlap between CG-PUSCH transmissions.

[0102] Various embodiments of the present disclosure recognize the need to be able to implement CG-PUSCH configurations that avoid collisions between CG-PUSCH transmissions corresponding to different CG-PUSCH configurations.

[0103] Various embodiments of the present disclosure recognize the need to define UE procedures for multiplexing information from a first CG-PUSCH to a second PUSCH, dropping the transmission of the first CG-PUSCH, and sending the second PUSCH.

[0104] Various embodiments of the present disclosure recognize the need to define UE procedures for multiplexing UCI from one or more PUCCH transmissions that overlap in time with more than one PUSCH transmission that also overlap in time.

[0105] Therefore, various embodiments of the present disclosure provide a mechanism for defining a UE process for providing an nrCG-UCI, which indicates that the UE sends a certain number of CG-PUSCH TOs for a CG-PUSCH configuration with more than one CG-PUSCH TO in a transmission period.

[0106] Various embodiments of the present disclosure provide a mechanism for defining a UE process for instructing the UE to send a certain number of CG-PUSCH TOs of a CG-PUSCH configured with more than one CG-PUSCH TO in a transmission period when the UE cancels CG-PUSCH transmission in some CG-PUSCH TOs.

[0107] Various embodiments of the present disclosure provide mechanisms for enabling utilization of a CG-PUSCH configuration in a transmission period (the CG-PUSCH configuration having more than one CG-PUSCH TO) that is not used for CG-PUSCH transmission and precedes the first CG-PUSCH TO used for CG-PUSCH transmission.

[0108] Various embodiments of the present disclosure provide a mechanism for defining a UE process for multiplexing indications of a certain number of CG-PUSCH TOs when the UE sends more than one channel that overlap in time, and the UE sends a CG-PUSCH with a CG-PUSCH configuration having more than one CG-PUSCH TO in a transmission period in a certain number of CG-PUSCH TOs.

[0109] Various embodiments of the present disclosure provide mechanisms to define UE procedures for resolving time overlap between CG-PUSCH transmissions.

[0110] Various embodiments of the present disclosure provide mechanisms for enabling CG-PUSCH configurations that avoid collisions between CG-PUSCH transmissions corresponding to different CG-PUSCH configurations.

[0111] Various embodiments of the present disclosure provide mechanisms for defining UE procedures for multiplexing information from a first CG-PUSCH to a second PUSCH, dropping the transmission of the first CG-PUSCH, and sending the second PUSCH.

[0112] Various embodiments of the present disclosure provide mechanisms to define UE procedures for multiplexing UCI from one or more PUCCH transmissions that overlap in time with more than one PUSCH transmission that also overlap in time.

[0113] The term "higher layers" is used to refer to control information that provides the UE with control information in PDSCH reception, such as radio resource control (RRC) or medium access control (MAC) control elements (CEs).

[0114] In one embodiment, a mechanism and procedure are considered for a UE to indicate to a serving gNB a certain number of CG-PUSCH TOs for a CG-PUSCH configuration in a transmission period that the UE will use to transmit CG-PUSCH.

[0115] The UE may provide the nrCG-UCI in a CG-PUSCH transmission to indicate to the serving gNB the number of CG-PUSCH TOs configured for the CG-PUSCH in the transmission period that the UE will use to transmit the CG-PUSCH. The UE may provide the nrCG-UCI in each CG-PUSCH transmission. The number of bits of the nrCG-UCI may be indicated from the serving gNB to the UE via RRC signaling. Because the number of bits required to provide the nrCG-UCI is typically several orders of magnitude smaller than the number of bits in the TB in the CG-PUSCH, the corresponding overhead is practically negligible. For example, considering TDD operation and small PDBs for UEs providing video frames, the total number of CG-PUSCH TOs in a transmission period is relatively small, e.g., less than or equal to 8 or 16, and if the indication is for consecutive TOs, the nrCG-UCI may be represented by 4 bits or less. In contrast, for data rates in the tens of Mbps, the size of the TB in a CG-PUSCH transmission is on the order of tens of thousands of bits.

[0116] In the first method, in each CG-PUSCH TO, the nrCG-UCI may be the same and indicate the total number of CG-PUSCH TOs with CG-PUSCH transmissions The first approach contemplates that the serving gNB may determine, for a CG-PUSCH configuration having more than one CG-PUSCH TO in a transmission period, based on a determination of corresponding CG-PUSCH reception, the first CG-PUSCH TO among the CG-PUSCH TOs comprising a CG-PUSCH transmission from the UE. Thus, the gNB may explicitly determine consecutive CG-PUSCH TOs comprising a CG-PUSCH transmission based on an indication of the total number of CG-PUSCH TOs with CG-PUSCH transmissions from the UE.

[0117] The advantages of the first approach are that by having the same nrCG-UCI value in each CG-PUSCH transmission, the error in determining the nrCG-UCI value can be reduced at the gNB, and the gNB can also combine the corresponding soft values of nrCG-UCI from different CG-PUSCH receptions in a period to improve the reception reliability of nrCG-UCI in subsequent CG-PUSCH receptions. For example, for a CG-PUSCH configuration in a transmission period CG-PUSCH TO, and the indication of continuous TO, by 2 bits nrCG-UCI and CG-PUSCH transmission The total number of CG-PUSCH TOs, nrCG-UCI can be used in The first CG-PUSCH TO and the second CG-PUSCH TO in the CG-PUSCH TO are indicated .

[0118] In the second method, nrCG-UCI can indicate the number of CG-PUSCH transmissions in a transmission period. The advantage of the second method is that it does not require the serving gNB to accurately detect the presence of previous CG-PUSCH transmissions from the UE in the CG-PUSCH TOs of the CG-PUSCH configuration in the transmission period. Similar to the first method, another advantage of the second method by including the nrCG-UCI in each CG-PUSCH transmission is that when the gNB does not correctly receive / detect the nrCG-UCI in the previous CG-PUSCH transmission for a CG-PUSCH configuration with more than one CG-PUSCH TO in the transmission period, the serving gNB can determine a certain number of remaining / subsequent CG-PUSCH TOs with CG-PUSCH transmissions. For example, for a CG-PUSCH configuration with CG-PUSCH TO, and nrCG-UCI indicating a certain number of consecutive CG-PUSCH TO, consisting of 2 bits nrCG-UCI, and for CG-PUSCH transmission The total number of CG-PUSCH TOs, nrCG-UCI can be indicated in the first CG-PUSCH TO with CG-PUSCH transmission , and indicated in the second CG-PUSCH TO with CG-PUSCH transmission There is also a possibility that the current CG-PUSCH transmission is not counted in the nrCG-UCI for the remaining CG-PUCCH TOs with CG-PUSCH transmissions. Then, in the above example, the nrCG-UCI may indicate in the first CG-PUSCH TO with CG-PUSCH transmission , and indicated in the second CG-PUSCHTO with CG-PUSCH transmission .

[0119] Figure 8 An example process 800 is shown for a UE to indicate the total number of CG-PUSCH TOs of CG-PUSCH configurations in a transmission period in which the UE transmits CG-PUSCH according to the present disclosure. The process 800 may be performed by a UE (e.g., Figure 1Any one of the UEs 111-119 shown) is executed. Figure 8 The embodiment of the UE process 800 shown in FIG. 8 is for illustration only and does not limit the scope of the present disclosure to any particular implementation.

[0120] Provide the UE with the transmission period including Based on, for example, the time-frequency resources, MCS and number of layers for CG-PUSCH transmission configured for CG-PUSCH, the UE determines the number of frames that the UE needs to send in the transmission period. CG-PUSCH TO with CG-PUSCH transmission (820). In each of the CG-PUSCH TOs, the UE provides The bit has equal The value of nrCG-UCI (830).

[0121] Figure 9 An example process 900 is shown for a UE to indicate the remaining number of CG-PUSCH TOs in a transmission cycle in which the UE transmits CG-PUSCH according to the present disclosure. The process 900 may be performed by a UE (e.g., Figure 1 Any one of the UE111-UE 119 shown) executes. Figure 9 The embodiment of the UE process 900 shown in FIG. 9 is for illustration only and does not limit the scope of the present disclosure to any particular implementation.

[0122] Provide the UE with the transmission period including Based on, for example, the time-frequency resources, MCS, and number of layers for CG-PUSCH transmission configured for the CG-PUSCH, the UE determines the number of frames that the UE needs to send in the transmission period. CG-PUSCH TO with CG-PUSCH transmission (920). In each of the CG-PUSCH TOs, the UE provides The nrCG-UCI (930) of bits has a value equal to the remaining number of CG-PUSCH TOs with CG-PUSCH transmission.

[0123] The serving gNB can also instruct the UE to suspend transmission of CG-PUSCH TOs for CG-PUSCH configurations with more than one CG-PUSCH TO in a transmission period. For example, after obtaining an indication of the required number of CG-PUSCH TOs with CG-PUSCH transmissions, the serving gNB can estimate the size of the video frame that the UE needs to provide in the transmission period based on the time-frequency resources, MCS, and number of spatial layers used for the CG-PUSCH transmissions. For example, the UE can provide a buffer status report (BSR) in the CG-PUSCH transmission to indicate the remaining size of the video frame. The serving gNB can then schedule subsequent PUSCH transmissions from the UE for the video frame to perform link adaptation and improve spectral efficiency, particularly given that the resources required for PDCCH transmissions with DCI formats of tens of bits are orders of magnitude smaller than those required for PUSCH transmissions of terabytes (TBs) with tens of thousands of bits.

[0124] In the first method, when a UE receives a PDCCH with a DCI format that schedules an initial transmission of a transport block in a PUSCH, where the PUSCH spans multiple symbols including the symbol of the CG-PUCCH TO in a slot, the UE considers that the gNB has released the CG-PUSCH configuration for the transmission period and suspends CG-PUSCH transmissions in subsequent CG-PUCCH TOs for the transmission period. The scheduled PUSCH transmission may have the same priority as the CG-PUSCH transmission.

[0125] In a second method, the DCI format includes, for example, a 1-bit field indicating whether the CG-PUSCH configuration is released within the transmission period. For example, the DCI format may be a format for scheduling PUSCH transmissions. The DCI format may include a priority indicator field whose value indicates the same priority as the CG-PUSCH transmission of the CG-PUSCH configuration.

[0126] In one embodiment, in a period of a single CG-PUSCH configuration, when the UE cancels some CG-PUSCH transmissions in the corresponding CG-PUSCH TO and postpones providing the corresponding TBs in the CG-PUSCH transmission in a subsequent CG-PUSCH TO, the UE considers a mechanism and process for counting CG-PUSCH TOs with CG-PUSCH transmissions.

[0127] The serving gNB may not correctly receive the first TB of the HARQ process in a CG-PUSCH transmission from the UE. In this case, the gNB may send a PDCCH with a DCI format that schedules a PUSCH transmission including the first TB of the HARQ process to the UE, typically with a different redundancy version (RV), so that the UE can provide the first TB again. The symbols of the timeslot in which the PUSCH transmission occurs may overlap with the symbols of a CG-PUSCH TO that the UE previously indicated, for example, via nrCG-UCI, for a CG-PUSCH transmission with the second TB. The UE then transmits the PUSCH with the first TB in the timeslot, cancels the CG-PUSCH transmission with the second TB, and provides the second TB in a subsequent CG-PUSCH TO, such as the next CG-PUSCH TO in which the UE may transmit a CG-PUSCH.

[0128] The CG-PUSCH transmission in a timeslot may also include symbols indicated to or determined by the UE as DL symbols, for example, based on RRC signaling or based on an indication based on a DCI format (e.g., DCI format 2_0) as described in TS 38.213 v17.4.0. The UE then cancels the CG-PUSCH transmission in the timeslot, if any, under applicable timeline conditions, and provides the corresponding TB in a CG-PUSCH transmission in a subsequent CG-PUSCH TO (e.g., the next CG-PUSCH TO in which the UE may send a CG-PUSCH). When the UE is aware in advance (e.g., based on information provided by higher layers) that the UE needs to cancel the CG-PUSCH transmission in the timeslot, the UE may include or exclude the corresponding CG-PUSCH TO in the number of CG-PUSCH TOs used for CG-PUSCH transmission indicated by the UE via the nrCG-UCI. The corresponding UE behavior may be defined in the specifications for system operation.

[0129] Typically, there may also be conditions where the UE indicates, for example via nrCG-UCI, that a CG-PUSCH TO is to be used for CG-PUSCH transmission, and the UE needs to subsequently cancel the CG-PUSCH transmission in that CG-PUSCH TO based on a determination of the contents of the DCI format. For example, the DCI format may schedule a PUSCH transmission of a TB with a HARQ process provided by the UE in a previous CG-PUSCH transmission, or schedule a PUSCH transmission of a new TB with another HARQ process including symbols of the CG-PUSCH transmission in the CG-PUSCH TO. For example, when the CG-PUSCH TO includes flexible symbols, DCI format 2_0 may indicate that those flexible symbols are DL symbols. Since the CG-PUSCH transmission provides new TBs, the UE needs to provide the TBs of the canceled CG-PUSCH transmission from the CG-PUSCH TO in the CG-PUSCH transmission of a subsequent CG-PUSCH TO. UE procedures then need to be defined for interpreting / processing the UE's previous indication of the number of consecutive CG-PUSCH TOs with CG-PUSCH transmissions.

[0130] In the first method, the UE does not consider the CG-PUSCH TO for which the UE cancels the CG-PUSCH transmission due to the indication of the DCI format to be included in the number of consecutive CG-PUSCH TOs indicated by the UE for CG-PUSCH transmission. For example, when the number of CG-PUSCH TOs configured for CG-PUSCH in a transmission period is 8, the UE indicates, for example via nrCG-UCI, that the third CG-PUSCHTO and the fourth CG-PUSCH TO are to be used for CG-PUSCH transmission, and the UE cancels the CG-PUSCH transmission in the fourth CG-PUSCH TO, and the UE does not count the fourth CG-PUSCH TO. The UE provides the TB associated with the canceled CG-PUSCH transmission in the earliest CG-PUSCH TO among the remaining CG-PUSCH TOs to which the UE can send CG-PUSCH. Equivalently, the UE considers only the valid CG-PUSCHTO to be counted in the number of CG-PUSCH TOs indicated for CG-PUSCH transmission, where the valid CG-PUSCH TO is the CG-PUSCH TO to which the UE is able to send CG-PUSCH. Furthermore, the indication of CG-PUSCH TOs with CG-PUSCH transmissions for a CG-PUSCH configuration in a transmission period may exclude invalid CG-PUSCH TOs as determined based on information provided to the UE via RRC signaling, such as for example for a TDD UL-DL configuration, because the UE may know the invalid CG-PUSCH TOs in advance, for example because they include DL symbols as indicated by the TDD UL-DL configuration.

[0131] In the second method, when the UE indicates the remaining CG-PUSCH TOs with CG-PUSCH transmissions, for example, via nrCG-UCI, if the UE cancels a certain number of consecutive previous CG-PUSCH transmissions due to invalidation of the corresponding CG-PUSCH TOs based on the indication in the DCI format, the UE does not reduce / change the nrCG-UCI value of the TOs in the CG-PUSCH. Since both the gNB and the UE can have the same understanding of the canceled CG-PUSCH transmissions, the UE provides the corresponding TBs in subsequent CG-PUSCH transmissions, and the gNB and the UE can maintain a common understanding of the CG-PUSCH TOs for which the UE will transmit CG-PUSCH.

[0132] Figure 10 An example process 1000 is shown for a UE to count the number of G-PUSCH TOs of CG-PUSCH configurations in a transmission period in which the UE transmits CG-PUSCH according to the present disclosure. The process 1000 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 10 The embodiment of the UE process 1000 shown in FIGURE 1 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0133] Provide the UE with the transmission period including Based on, for example, the time-frequency resources, MCS, and number of layers for CG-PUSCH transmission of the CG-PUSCH configuration, the UE determines the number of packets required to send a packet in a transmission period. CG-PUSCH TO with CG-PUSCH transmission (1020). Based on the information provided by the DCI format or RRC signaling, the UE determines whether the UE can transmit the CG-PUSCH in the CG-PUSCH TO of CG-PUSCH TO is sent (1030). When the UE sends CG-PUSCH, the UE counts the CG-PUSCH TO in the number CG-PUSCH TO (1040); otherwise, the UE does not count the CG-PUSCH TO in the number CG-PUSCH TO (1050). Similarly, when the UE indicates the remaining number When a CG-PUSCH TO with CG-PUSCH transmission is received, the UE does not count the CG-PUSCH TO into the remaining number of CG-PUSCH TOs. For the determination based on the information provided by RRC signaling, the UE may always ignore invalid CG-PUSCH TOs, such as CG-PUSCH TOs overlapping with DL symbols.

[0134] In addition to the counter, and with reference to CG-PUSCH transmission on the serving cell, the nrCG-UCI may be a bitmap, wherein, in a CG-PUSCH TO, the bitmap indicates the CG-PUSCH TO and the number of subsequent CG-PUSCH TOs in which the UE may transmit a CG-PUSCH or the UE will not transmit a CG-PUSCH. For example, the number of subsequent CG-PUSCH TOs including the CG-PUSCH TO may be equal to the size of the bitmap, in which a bit value of "0" indicates that there is a transmission in the corresponding CG-PUSCH TO and a bit value of "1" indicates that there is no transmission in the corresponding CG-PUSCH TO, or vice versa.

[0135] In the first method, in order to enable the scheduler to utilize a CG-PUSCH TO in which the UE has indicated that the UE will not transmit a CG-PUSCH, it may be specified that the UE cannot change such an indication later and cannot transmit a CG-PUSCH in the CG-PUSCH TO. However, this may also create a problem in the case where the UE needs to cancel a CG-PUSCH transmission in a CG-PUSCH TO that the UE has indicated for CG-PUSCH transmission, because the UE cannot then utilize the CG-PUSCH TO for CG-PUSCH transmission in which the UE has indicated that it will not transmit a CG-PUSCH. For example, the UE needs to cancel a CG-PUSCH transmission in a CG-PUSCH TO due to a PUSCH transmission being scheduled via a DCI format, the PUSCH transmission providing a PUSCH transmission of a TB that the gNB incorrectly received in a previous CG-PUSCH. Typically, a CG-PUSCH transmission in a valid CG-PUSCH TO may be canceled due to various reasons, such as those described in REF3 and REF4. In order to enable the UE to reclaim, for CG-PUSCH transmission, a CG-PUSCH TO for which the UE had previously indicated that the UE would not send CG-PUSCH, while enabling the scheduler to utilize the resources of the CG-PUSCH TO for which the UE indicated that there would be no CG-PUSCH transmission, a timeline may be introduced from the end of CG-PUSCH transmission (the end of a first CG-PUSCH TO) until the start of a second CG-PUSCH TO, wherein the UE indicates that the state of the subsequent second CG-PUSCH TO is switched from not used for CG-PUSCH transmission to used for CG-PUSCH transmission. If the time between the end of the first CG-PUSCH TO and the start of the second CG-PUSCH TO is less than (or equal to) the timeline, the UE shall not indicate such a switch and shall not use the second CG-PUSCH TO for CG-PUSCH transmission; otherwise, the UE may indicate such a switch and may use the second CG-PUSCH TO for CG-PUSCH transmission. The timeline may be indicated to the UE by a higher layer, such as, for example, by UE-specific radio resource control (RRC) signaling. The timeline may be a certain number of absolute time units, such as milliseconds (msec), or may be a certain number of time slots for subcarrier spacing corresponding to CG-PUSCH transmissions or for a reference subcarrier spacing such as 15 kHz.For example, assuming: a 4 msec timeline; CG-PUSCH transmission in the first CG-PUSCH TO; and the UE indicates no CG-PUSCH transmission in the second CG-PUSCH TO starting 2 msec after the end of the first CG-PUSCH TO and in the third CG-PUSCH TO starting 6 msec after the end of the first CG-PUSCH TO, then the UE will not indicate the second CG-PUSCH TO for CG-PUSCH transmission and may indicate the third CG-PUSCH TO for CG-PUSCH transmission.

[0136] In a second method, the UE may determine, based on its implementation, a certain number of CG-PUSCH TOs to indicate for CG-PUSCH transmission (or, to indicate no CG-PUSCH transmission). For example, the UE may perform such a determination by taking into account possible cancellations of CG-PUSCH transmissions. For example, the UE may determine or be instructed to indicate a target error rate for TBs to be transmitted in the CG-PUSCH, and based on a certain number of CG-PUSCH TOs required for CG-PUSCH transmission in a CG-PUSCH transmission period, the UE may determine to indicate a certain number of additional CG-PUSCH TOs to be used for CG-PUSCH transmission in the CG-PUSCH transmission period, for example by using a ceiling function of the number of TBs that are expected to be erroneously received from the number of TBs that the UE needs to provide in the CG-PUSCH transmission period. The UE may then indicate additional CG-PUSCH TOs for CG-PUSCH transmission, even if the UE does not need to use these additional CG-PUSCH TOs for CG-PUSCH transmission if the TBs are always received correctly or if the UE does not generally need to cancel CG-PUSCH transmissions.

[0137] In one embodiment, a mechanism and process for utilizing CG-PUSCH TOs not used for CG-PUSCH transmission in a transmission period of a CG-PUSCH configuration is considered.

[0138] The UE may include nrCG-UCI in CG-PUSCH transmissions that are associated with a first CG-PUSCH configuration having one CG-PUSCH TO in a first transmission period, the first CG-PUSCH configuration being different from a second CG-PUSCH configuration having more than one CG-PUSCH TO in a second transmission period and being associated with nrCG-UCI. For example, for an XR application, attitude / control information may be provided by a first CG-PUSCH configuration having a single CG-PUSCH TO with a first period (e.g., 4 msec or 5 msec), and a video frame may be provided by a second CG-PUSCH configuration having multiple CG-PUSCH TOs with a second period (e.g., 16 msec or 33 msec). Then, at least when CG-PUSCH transmissions for the first CG-PUSCH configuration occur more frequently and deterministically than CG-PUSCH transmissions for the second CG-PUSCH configuration, those CG-PUSCH transmissions may be used to provide nrCG-UCI in addition to, or instead of, providing nrCG-UCI in the CG-PUSCH transmissions for the second CG-PUSCH configuration.

[0139] An advantage of providing the nrCG-UCI associated with the second CG-PUSCH configuration in the CG-PUSCH transmission of the first CG-PUSCH configuration is that the UE can provide an indication of the CG-PUCCH TO earlier in the absence of a CG-PUSCH transmission for the second CG-PUSCH configuration, so that the scheduler can reallocate resources for unused CG-PUSCH TOs. The indication can also be provided before any CG-PUSCH transmission for the second CG-PUSCH configuration so that other services can be scheduled using the resources used for the CG-PUSCH TO before the first CG-PUSCH TO with CG-PUSCH transmission for the second CG-PUSCH configuration.

[0140] The indication of the nrCG-UCI in a CG-PUSCH transmission of a first CG-PUSCH configuration that is different from the second CG-PUSCH configuration associated with the nrCG-UCI may indicate whether the UE is to transmit in at least one of the CG-PUSCH TOs for the second CG-PUSCH configuration before the next CG-PUSCH transmission for the first CG-PUSCH configuration. For example, for a total of two consecutive CG-PUSCH transmissions for the first CG-PUSCH configuration, the UE may transmit in at least one of the CG-PUSCH TOs for the second CG-PUSCH configuration before the next CG-PUSCH transmission for the first CG-PUSCH configuration. CG-PUSCH TO, among which, After the earlier CG-PUSCH transmission in two consecutive CG-PUSCH transmissions, the 1-bit nrCG-UCI can indicate whether the CG-PUSCH TO will be used for the CG-PUSCH transmission of the second CG-PUSCH configuration. The first CG-PUSCH TO may include the latter of two consecutive CG-PUSCH transmissions of the first CG-PUSCH configuration. The indication may be encoded and multiplexed in the same manner as the HARQ-ACK information. When HARQ-ACK information is also included in the CG-PUSCH transmission of the first CG-PUSCH configuration, the indication may be appended to the HARQ-ACK information codeword before encoding and multiplexing.

[0141] Figure 11 An example process 1100 is shown for determining whether a UE uses a CG-PUSCH TO subset of a certain number of CG-PUSCH TOs from a CG-PUSCH configuration in a transmission period for CG-PUSCH transmission according to the present disclosure. The process 1100 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 11 The embodiment of the UE process 1100 shown in FIGURE 1 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0142] A first CG-PUSCH configuration and a second CG-PUSCH configuration are provided to the UE, wherein the first CG-PUSCH configuration includes one CG-PUSCH TO in the first transmission cycle and the second CG-PUSCH configuration includes CG-PUSCH TO (1110). The UE determines whether there is at least one CG-PUSCH transmission of the second CG-PUSCH configuration after the CG-PUSCH transmission of the first CG-PUSCH configuration (1120). The determination may also additionally set a condition for the CG-PUSCH transmission of the second CG-PUSCH configuration, the second CG-PUSCH configuration being no later than the immediately next CG-PUSCH transmission for the first CG-PUSCH configuration. The UE includes an indication for making the determination in the CG-PUSCH transmission of the first CG-PUSCH configuration, for example using 1 bit (1130).

[0143] By providing nrCG-UCI in a PUCCH transmission, a function similar to providing nrCG-UCI in a CG-PUSCH transmission of a CG-PUSCH configuration different from one of the nrCG-UCIs can be achieved. For example, similar to providing periodic CSI reports, a configuration for PUCCH transmission with nrCG-UCI can be provided to the UE. In addition, the configuration can only be valid during the transmission period of the CG-PUSCH configuration for nrCG-UCI. In addition, the configuration may be valid only before the first CG-PUSCH transmission of the CG-PUSCH configuration for nrCG-UCI, and the nrCG-UCI may be provided in the CG-PUSCH transmission thereafter.

[0144] In one embodiment, a mechanism and procedure are considered for enabling a UE to report nrCG-UCI when the UE will simultaneously transmit a CG-PUSCH on a first cell and a PUSCH or PUCCH on a second cell, and after performing the procedure for determining a UCI multiplexed channel as described in TS 38.213 v17.4.0, the UE determines the PUSCH or PUCCH. The PUSCH is considered to be scheduled by a DCI format.

[0145] In the first method, the UE multiplexes all UCI, including the nrCG-UCI, in the PUSCH or PUCCH and does not multiplex the nrCG-UCI in the CG-PUSCH. To avoid ambiguity at the serving gNB as to whether the nrCG-UCI is included in the UCI, the UE includes the nrCG-UCI in the UCI even when the UE does not transmit a CG-PUSCH that would include the nrCG-UCI. For example, when the UE does not transmit a CG-PUSCH in a CG-PUSCH TO from a certain number of more than one CG-PUSCH TOs configured in the CG-PUSCH transmission period due to unavailability of the associated video frame, the UE still multiplexes the CG-UCI that temporally overlaps with the CG-PUSCH TO in the PUSCH or PUCCH. In this case, the value of the nrCG-UCI may be predetermined, such as a minimum value (e.g., 0 or 1) or a maximum value corresponding to all CG-PUSCH TOs configured in the CG-PUSCH transmission period.

[0146] In the second approach, the UE multiplexes all UCI in PUSCH or PUCCH in addition to nrCG-UCI (and CG-UCI as described in TS 38.213 v17.4.0). The UE multiplexes nrCG-UCI only in CG-PUSCH transmissions, such as CG-PUSCH transmissions associated with a CG-PUSCH configuration with more than one CG-PUSCH TO in a transmission period. This approach avoids including nrCG-UCI with other UCI, which is beneficial for the reliability of other UCI, especially when nrCG-UCI does not provide actual information as described above. For UCI multiplexing in PUCCH, the second approach also avoids any modifications to the corresponding procedures for multiplexing or for determining PUCCH transmission power or PUCCH resources, etc.

[0147] When a UE will simultaneously transmit PUCCH with UCI, CG-PUSCH with nrCG-UCI, or CG-PUSCH with CG-UCI, and one or more PUSCHs without UCI, where all channels have equal priority and the total power would exceed the maximum power, the UE may prioritize power allocation for PUCCH transmissions, followed by power allocation for CG-PUSCH transmissions with nrCG-UCI, and finally for the remaining PUSCH transmissions, including (if any) CG-PUSCH transmissions providing CG-UCI. Power may also be allocated to CG-PUSCH transmissions with nrCG-UCI over PUCCH transmissions. When a UE will simultaneously transmit PUSCH with UCI (e.g., HARQ-ACK information or CSI) and CG-PUSCH with nrCG-UCI, the UE may prioritize power allocation to PUSCH transmissions with UCI during periods of temporal overlap between PUSCH and CG-PUSCH transmissions. Alternatively, the UE may assign equal priority to power allocation for PUSCH and CG-PUSCH.

[0148] In the third method, when the UE simultaneously transmits a first PUSCH and a second PUSCH with a first priority or a PUCCH with a second priority, the UE multiplexes the UCI with the first priority in the first PUSCH and the UCI with the second priority in the PUCCH. The nrCG-UCI is included in the UCI with the same priority as the nrCG-UCI. The third method can also be combined with the first method or the second method.

[0149] In order to multiplex nrCG-UCI with or without other UCI in PUSCH or PUCCH, nrCG-UCI can be considered as HARQ-ACK information. For example, when there is no multiplexed HARQ-ACK information in PUSCH or PUCCH, nrCG-UCI is encoded and multiplexed in PUSCH or PUCCH using the same process as for HARQ-ACK information with the same payload. When there is multiplexed HARQ-ACK information in PUSCH or PUCCH, nrCG-UCI is attached to the HARQ-ACK information, and the HARQ-ACK information and nrCG-UCI are jointly encoded and multiplexed in PUSCH or PUCCH using the same process as for HARQ-ACK information with the same payload.

[0150] Figure 12 An example process 1200 is shown according to the present disclosure, in which a UE provides nrCG-UCI when a CG-PUSCH TO on a first cell, for a CG-PUSCH configuration with more than one CG-PUSCH TO in a transmission period, overlaps in time with a PUSCH or PUCCH transmission on a second cell. The process 1200 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 12 The embodiment of the UE process 1200 shown in FIGURE 1 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0151] The UE determines that for a CG-PUSCH configuration with more than one CG-PUSCH TO in a transmission period, a CG-PUSCH transmission on a first cell overlaps with a PUSCH or PUCCH transmission on a second cell (1210). The UE multiplexes the nrCG-UCI in the CG-PUSCH transmission and multiplexes other UCI (if any) in the PUSCH or PUCCH transmission (1220). The UE transmits a CG-PUSCH on the first cell and transmits a PUSCH or PUCCH on the second cell (1230).

[0152] In one embodiment, mechanisms and procedures are contemplated for enabling a UE to resolve conflicts between CG-PUSCH transmissions associated with corresponding CG-PUSCH configurations. CG-PUSCH transmissions are assumed to have the same priority. References to overlap between CG-PUSCH transmissions refer to overlap in time, e.g., overlap in time of symbols of a time slot.

[0153] When a UE is configured to transmit more than one CG-PUSCH and the transmissions will overlap over multiple symbols, the UE may perform a process to identify the CG-PUSCH to be transmitted and, therefore, also identify the CG-PUSCH to be dropped from the transmission. The priority of the CG-PUSCHs for transmission may be based on ascending order of the indices associated with the corresponding CG-PUSCH configurations. This approach enables the network to control which CG-PUSCHs the UE will transmit. For example, when a CG-PUSCH transmission with video information overlaps with a CG-PUSCH transmission with attitude / control information, the gNB may assign a smaller index to the CG-PUSCH configuration associated with the video information, and the UE will then transmit the CG-PUSCH with the video information and drop the CG-PUSCH transmission with the attitude / control information. The opposite is true when the CG-PUSCH configuration associated with the attitude / control information has a smaller index, such as when the gNB prefers attitude / control information from the UE over video information.

[0154] After the UE discards the first CG-PUSCH transmission, a second CG-PUSCH transmission that overlaps with the first CG-PUSCH transmission may not overlap with any third CG-PUSCH transmission and may therefore be sent by the UE without being discarded. Therefore, the process by which the UE determines the CG-PUSCH that the UE will transmit needs to be recursive, wherein the UE determines the CG-PUSCH transmission and CG-PUSCH discard at each iteration. The process may exclude CG-PUSCHs that overlap with DL symbols of the TDD UL-DL configuration provided by higher layers before its initialization, for example by parameters as described in TS 38.213 v17.4.0 and TS 38.331 v17.3.0 tdd- UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated .

[0155] Therefore, in solving and passing tdd-UL-DL-ConfigurationCommon or tdd-UL-DL- ConfigurationDedicated After indicating the overlap of symbols in the downlink time slot and discarding the corresponding CG-PUSCH transmission, the UE sends one or more overlapping CG-PUSCHs according to the following procedure. If there is no CG-PUSCH overlap, the UE sends all CG-PUSCHs.

[0156] will be collected Q Set to the CG-PUSCH configuration index set of the CG-PUSCH that overlaps in the time slot

[0157] will be collected T Set as the CG-PUSCH configuration index set to be transmitted in the time slot, where T is initialized to an empty set (T=Ø )

[0158] When the collection Q When it is not an empty set (when Q≠Ø )

[0159] will be collected Q The smallest index in q min Add to Collection T middle( T=T∪q min )

[0160] From the collection Q Remove index q min , and with index q min There is an overlapping CG-PUSCH configuration index set for the CG-PUSCH transmission of the CG-PUSCH configuration P ( Q=Q\P,Q=Q\q min )

[0161] End the loop

[0162] For example, if the UE is to transmit (after resolving overlap with DL symbols, if any) a first overlapping CG-PUSCH, a second overlapping CG-PUSCH, a third overlapping CG-PUSCH, and a fourth overlapping CG-PUSCH in time slots associated with corresponding CG-PUSCH configurations with indices 0, 1, 2, and 3, the UE first determines to transmit the first CG-PUSCH in the time slot. Assuming that the transmission of the second CG-PUSCH and the third CG-PUSCH in the time slot will overlap with the transmission of the first CG-PUSCH in the time slot, the UE discards the transmission of the second CG-PUSCH and the third CG-PUSCH in the time slot. When the fourth CG-PUSCH does not overlap with the first CG-PUSCH, the UE also transmits the fourth CG-PUSCH in the time slot, although the fourth CG-PUSCH may overlap with at least one of the second CG-PUSCH and the third CG-PUSCH.

[0163] Figure 13 An example process 1300 is shown according to the present disclosure, in which a UE determines a first number of CG-PUSCHs to transmit and a second number of CG-PUSCHs to drop from transmission when the first number and the second number of CG-PUSCHs overlap in time. The process 1300 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 13 The embodiment of the UE process 1300 shown in FIGURE 1 is for illustration only and does not limit the scope of the present disclosure to any particular implementation.

[0164] The UE determines that a certain number of CG-PUSCHs overlap in time, wherein the CG-PUSCHs are associated with corresponding CG-PUSCH configurations with corresponding indices (1310). The UE determines a first CG-PUSCH associated with the CG-PUSCH configuration with the smallest index from the certain number of CG-PUSCHs for transmission (1320). The UE removes the first CG-PUSCH from the certain number of CG-PUSCHs and also removes the second CG-PUSCH overlapping with the first CG-PUSCH (1330). When there is a remaining non-zero number of CG-PUSCHs (1340), the UE repeats step 1310; otherwise, the UE ends the process and during the overlap resolution process, the UE considers only the CG-PUSCH determined by the UE for transmission for transmission (1350). When there are no other conditions for the UE to drop the transmission, such as a conflict with another PUSCH with a higher priority, or the conditions generally described in TS 38.213 v17.4.0, the UE transmits the CG-PUSCH determined for transmission.

[0165] In addition to the UE performing the process of determining which CG-PUSCH to transmit and which to discard from a certain number of overlapping CG-PUSCHs, the gNB can avoid such conflicts by enhancing the parameters of the CG-PUSCH configuration. Since CG-PUSCH transmissions are periodic, the gNB has prior knowledge of the CG-PUSCH configurations that will result in overlapping CG-PUSCH transmissions in a slot. The gNB can then provide a bitmap that spans the slot, or a bitmap with finer granularity when multiple CG-PUSCH transmissions for a CG-PUSCH configuration may exist in a slot, where the bit value in the bitmap indicates whether the UE will discard a CG-PUSCH transmission in the slot. The bitmap length can be equal to the least common multiple of the periodicity of the CG-PUSCH configurations or can be predetermined. The bitmap length can also be shortened and equal to the maximum of the ratios when certain conditions are met, such as when each ratio between each larger period and each smaller period of the CG-PUSCH configuration is an integer. For example, for three CG-PUSCH configurations with corresponding periods of 1 msec, 2 msec, and 5 msec, the bitmap length may be equal to 10. A bitmap may be provided for each configuration, or may be optional for certain configurations, and then a default behavior may be applied, such as always dropping the corresponding CG-PUSCH from transmission, or always sending the corresponding CG-PUSCH. The default behavior may be indicated by higher layers or may be defined in the specification of the system operation.

[0166] In one embodiment, mechanisms and procedures are considered for enabling a UE to multiplex information from a first CG-PUSCH in a second PUSCH in the case of overlap. The second PUSCH can be a CG-PUSCH or a PUSCH scheduled by a DCI format (DG-PUSCH). References to overlap between CG-PUSCH transmissions refer to overlap in time, such as overlap in time of symbols of a timeslot. Furthermore, without loss of generality, reference is made to TBs in a CG-PUSCH, although a PUSCH can also be a DG-PUSCH.

[0167] A UE dropping a CG-PUSCH transmission in the event of a collision with another PUSCH transmission can be detrimental to service quality or system spectral efficiency. For example, when a UE drops a CG-PUSCH transmission with a TB for video information, service quality decreases as the probability of failing to deliver a video frame at the PDB target increases. For example, when a UE drops a CG-PUSCH transmission with a TB for attitude / control information, system spectral efficiency or service quality decreases as the serving gNB does not have the latest information to schedule the UE's PDSCH reception at the data rate required for the FOV, and the gNB may therefore schedule an unnecessarily large or inappropriately low data rate.

[0168] For some applications associated with the use of CG-PUSCH, the size of a first TB provided by a first CG-PUSCH can be much smaller than the size of a second TB provided by a second PUSCH. For example, the size of a TB providing posture / control information is typically several orders of magnitude smaller than the size of a TB providing video information. In this case, rather than completely losing the smaller TB due to a conflict between the corresponding CG-PUSCH and PUSCH transmissions, the smaller TB can be multiplexed in the PUSCH, or information associated with the smaller TB can be multiplexed in the PUSCH.

[0169] When the first TB associated with the first CG-PUSCH is multiplexed in the second PUSCH, the first TB can be provided via one or more separate code blocks (CBs) that are different from the CB corresponding to the second TB associated with the second PUSCH. In this way, the encoding process of the two TBs (or the CBs comprising each of the two TBs) remains separate, and there are no additional processing requirements for the UE regarding the encoding of the first and second TBs. The multiplexing of the first TB in the second PUSCH can precede or follow the multiplexing of the second TB in the second PUSCH. Therefore, the UE's multiplexing process for the first and second TBs in the second PUSCH can be similar to the multiplexing process when the UE generates a larger TB including the CB of the first TB and the CB of the second TB.

[0170] In the first method, in the case where the second PUSCH is a CG-PUSCH, the time-frequency resource set (symbol-RB) used to transmit the second PUSCH can be maintained as provided by the corresponding second CG-PUSCH configuration, regardless of whether the first TB is also multiplexed in the second CG-PUSCH. For UEs that are not power-limited, for example, based on the power for determining PUSCH transmission as described in TS 38.213 v17.4.0 component, reception reliability can be kept largely unchanged by increasing the power per resource unit for the second CG-PUSCH transmission to compensate for the increase in the code rate for the second TB.

[0171] In the second method, the second CG-PUSCH configuration may include two sets of time-frequency resources (symbols - RBs) in the time slot for the second CG-PUSCH transmission: a first set corresponding to the case where the first TB is not multiplexed in the second CG-PUSCH and a second set corresponding to the case where the first TB is multiplexed in the second CG-PUSCH. In this way, the reception reliability of the second CG-PUSCH is maintained while avoiding increasing the power of the second CG-PUSCH transmission per resource element.

[0172] For the first and second methods, when the first TB is not multiplexed in the second CG-PUSCH transmission, the increase in power or time-frequency resources for the second CG-PUSCH transmission will be small relative to the corresponding values, because the size of the first TB is typically several orders of magnitude smaller than the size of the second TB. Therefore, for the first method, when the first and second TBs are multiplexed in the second CG-PUSCH, the resulting increase in the code rate of the first and second TBs will be small relative to when only the second TB is multiplexed in the second CG-PUSCH (and the first TB is multiplexed in the first CG-PUSCH). Similarly, for the second method, the number of additional RBs (and / or symbols) used to multiplex the first and second TBs in the second CG-PUSCH will be small relative to when only the second TB is multiplexed in the CG-PUSCH, and therefore the increase in CG-PUSCH transmission power with the increase in the number of relevant RBs will be small.

[0173] In the third method, the information of the first TB can be quantized and multiplexed as UCI in the second PUSCH. The third method is applicable in the case where the first TB provides control type information such as posture / control information. For example, for field of view (FOV) N The attitude / control information set can be uniquely mapped to the multiplexed Bit N values, among which is a ceiling function that maps a number to its next larger integer, while log2 is the logarithm with base 2. N A state set or N A state set and Bit N The mapping between the values can be provided to the UE in advance by the higher layer, or can be defined in the specification of the system operation. For example, the first set of FOV states can be mapped to Bit N The first value of the value, while the second set of FOV states can be mapped to Bit N The UCI corresponding to the quantized information of the first TB may be multiplexed in the second PUSCH in the same manner as the HARQ-ACK information, such as the FOV state set, rather than a state from the FOV state set. If the UE also multiplexes HARQ-ACK information in the PUSCH, the UCI may be appended to the HARQ-ACK information before encoding.

[0174] Figure 14 An example process 1400 is shown according to the present disclosure, in which a UE resolves a conflict between a CG-PUSCH having a first TB on a cell and a PUSCH having a second TB on a cell by multiplexing the first TB in a PUSCH using the same time-frequency resources. The process 1400 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 14 The embodiment of the UE process 1400 shown in FIGURE 14 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0175] The UE determines that a CG-PUSCH transmission providing a first TB on a cell will span symbols of a time slot including symbols of a PUSCH transmission providing a second TB on the cell (1410). The UE multiplexes the first TB and the second TB in the PUSCH (1420). The coding of each TB may be separate, and the multiplexing of the first TB in the PUSCH may be before or after the multiplexing of the second TB in the PUSCH. The UE transmits the PUSCH on the cell and drops the transmission of the CG-PUSCH (1430). When the first TB and the second TB are multiplexed, the power used for the PUSCH transmission may be greater than the power of the PUSCH transmission when only the second TB is multiplexed.

[0176] Figure 15An example process 1500 is shown according to the present disclosure, in which a UE resolves a conflict between a first CG-PUSCH having a first TB on a cell and a second CG-PUSCH having a second TB on a cell by multiplexing the first TB in the CG-PUSCH and increasing the frequency resources or time resources used for the second CG-PUSCH. The process 1500 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 15 The embodiment of the UE process 1500 shown in FIGURE 1 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0177] The UE determines that a first CG-PUSCH transmission providing a first TB on a cell will span symbols of a time slot including symbols of a second CG-PUSCH transmission providing a second TB on the cell (1510). The UE determines a second frequency resource (RB) or a second time resource (symbol) for multiplexing both the first TB and the second TB in a second CG-PUSCH that is different from (e.g., greater than) the first frequency resource (RB) or the first time resource (symbol) for multiplexing only the second TB in the second CG-PUSCH (1520). The UE multiplexes both the first TB and the second TB on the second frequency resource or on the second time resource in the second CG-PUSCH (1530). The coding of each TB may be separate, and the multiplexing of the first TB in the PUSCH may be before or after the multiplexing of the second TB in the second CG-PUSCH. The UE transmits the second CG-PUSCH on the cell and discards the transmission of the first CG-PUSCH (1540).

[0178] Figure 16 An example process 1600 is shown according to the present disclosure, in which a UE resolves a collision between a first CG-PUSCH on a cell having a first TB and a second PUSCH on a cell having a second TB by quantizing information from the first TB and multiplexing the quantized information as UCI in a second PUSCH. The process 1600 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 16 The embodiment of the UE process 1600 shown in FIGURE 1 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0179] The UE determines that a first CG-PUSCH transmission providing a first TB on a cell will span symbols of a time slot including symbols of a second PUSCH transmission providing a second TB on a cell (1610). The UE determines based on the information of the first TB that N status and bits NOne-to-one mapping between values to determine bits of value (1620). N The information and / or mapping of each state is provided to the UE in advance through high-layer signaling, or is predetermined in the specification of system operation. bits (1630). Multiplexing may be used to multiplex HARQ-ACK information bits. The UE transmits a second PUSCH on the cell and discards the transmission of the first CG-PUSCH (1640).

[0180] In one embodiment, mechanisms and procedures are considered for enabling a UE to multiplex information from a first CG-PUSCH in a second PUSCH in the case of overlap. The second PUSCH can be a CG-PUSCH or a PUSCH scheduled by a DCI format (DG-PUSCH). References to overlap between CG-PUSCH transmissions refer to overlap in time, for example, overlap in time of symbols of a timeslot. Furthermore, without loss of generality, reference is made to TBs in a CG-PUSCH, although a PUSCH can also be a DG-PUSCH.

[0181] The third embodiment of the present disclosure considers the process of UE resolving conflicts between PUSCH transmissions and PUCCH transmissions. It is assumed that PUSCH transmissions and PUCCH transmissions have the same priority. PUSCH transmissions are on the same or different cell as the cell used for PUCCH transmissions. References to overlap between PUSCH and PUCCH transmissions refer to overlap in time. It is assumed that simultaneous PUCCH transmissions on a first cell and PUSCH transmissions on a second cell are not supported, and are based on specified criteria such as those described in TS 38.213 v17.4.0. It is assumed that the UE multiplexes UCI in the PUSCH transmissions on the second cell. The PUSCH transmissions can be CG-PUSCH transmissions or scheduled by a DCI format (DG-PUSCH transmissions).

[0182] In the first method, the UE first resolves collisions (if any) in the PUCCH to generally obtain a final PUCCH, for example, as described in TS 38.213 v17.4.0. Subsequently, if a certain number of PUCCHs overlap with the PUSCH, the UE multiplexes the corresponding UCI in the PUSCH and does not transmit the PUCCH. Finally, the UE resolves collisions between overlapping PUSCHs. With the first method, due to the process for resolving overlaps between PUSCHs, the UE can then discard the transmission of the PUSCH in which the UE multiplexed UCI, for example, as described in the first embodiment of the present disclosure.

[0183] In the second method, the UE performs a first procedure and a second procedure in parallel, with the first procedure being used to resolve conflicts between PUCCH transmissions and the second procedure being used to resolve conflicts between PUSCH transmissions. Following the first procedure (e.g., as described in TS 38.213 v17.4.0) and the second procedure (e.g., as described in the first embodiment of the present disclosure), if a PUCCH transmission would overlap with a PUSCH transmission, the UE may multiplex UCI in the PUSCH and discard the PUCCH transmission. Because the PUSCH transmissions are non-overlapping after the second procedure, the UE does not discard the first PUSCH transmission with UCI due to a conflict with the second PUSCH transmission. In the event that a PUCCH overlaps with more than one PUSCH, the UE may multiplex UCI in the earlier PUSCH among the more than one PUSCHs that meets the timeline conditions for UCI multiplexing in the PUSCHs, such as those described in TS 38.213 v17.4.0.

[0184] Figure 17 An example process 1700 is shown for a UE to resolve a conflict between a PUCCH transmission on a first cell and a PUSCH transmission on a second cell according to the present disclosure. The process 1700 may be performed by a UE (e.g., Figure 1 Any one of the UEs 111-119 shown) is executed. Figure 17 The embodiment of the UE process 1700 shown in FIGURE 17 is for illustration only and does not limit the scope of this disclosure to any particular implementation.

[0185] The UE determines a temporal overlap between a PUCCH transmission on a first cell and a PUSCH transmission on a second cell (1710). The first cell and the second cell may be the same or different. The UE performs a first procedure to resolve the overlap between the PUCCH transmissions and a second procedure to resolve the overlap between the PSCCH transmissions (1720). Following the first and second procedures, the UE multiplexes UCI for the PUCCH on the first cell that overlaps with the PUSCH on the second cell in one of the PUSCHs, transmits the PUSCH, and discards the PUCCH transmission (1730).

[0186] The above flowcharts illustrate example methods that can be implemented according to the principles of the present disclosure, and various changes can be made to the methods shown in the flowcharts herein. For example, although shown as a series of steps, the individual steps in each figure can overlap, occur in parallel, occur in a different order, or occur multiple times. In another example, steps can be omitted or replaced with other steps.

[0187] Although the figures illustrate different examples of user equipment, various changes may be made to the figures. For example, the user equipment may include any number of each component in any suitable arrangement. Generally, the figures do not limit the scope of the present disclosure to any particular configuration. Furthermore, although the figures illustrate operating environments in which various user equipment features disclosed in this patent document may be used, these features may be used in any other suitable system.

[0188] Although the present disclosure has been described using example embodiments, various changes and modifications may be proposed by those skilled in the art. The present disclosure is intended to include such changes and modifications as fall within the scope of the appended claims. Nothing in this application should be construed as implying that any particular element, step, or function is essential to be included within the scope of the claims. The scope of a patent protected subject matter is defined by the claims.

Claims

1. A method performed by a user equipment (UE), the method comprising: Receiving, through radio resource control signaling, first information for a configuration grant CG configuration for transmitting a plurality of physical uplink shared channels (PUSCHs), wherein the first information includes a time period; Determine, from a first set of transmission opportunities TO within the time period, a plurality of first TOs for transmitting corresponding plurality of first CG-PUSCHs; determining first control information providing an indication of the plurality of first TOs; multiplexing the first control information in a first CG-PUSCH from the plurality of first CG-PUSCHs, wherein the first CG-PUSCH is earliest in time among the plurality of first CG-PUSCHs; multiplexing second control information in a PUSCH other than the first CG-PUSCH, wherein the second control information provides first confirmation information or first channel state information; and The first CG-PUSCH and the PUSCH are transmitted, wherein the transmission of the first CG-PUSCH and the transmission of the PUSCH overlap in time.

2. The method according to claim 1, further comprising: Determine a plurality of second TOs for transmitting a plurality of second CG-PUSCHs from a second set of TOs within the time period; determining third control information providing an indication of the plurality of second TOs; as well as The third control information and the fourth control information are multiplexed in the first CG-PUSCH from the plurality of second CG-PUSCHs, wherein: The fourth control information is confirmation information, and Before jointly encoding the third control information and the fourth control information, the third control information is appended to the fourth control information, Herein, sending the first CG-PUSCH includes sending the first CG-PUSCH from the multiple second CG-PUSCHs.

3. The method according to claim 1, further comprising: Determine a second TO for transmitting a plurality of second CG-PUSCHs from a second set of TOs within the time period; determining third control information providing an indication of the plurality of second TOs; multiplexing the third control information in the first CG-PUSCH from the plurality of second CG-PUSCHs; multiplexing fourth control information in a physical uplink control channel (PUCCH), wherein the fourth control information is confirmation information or channel state information; and The PUCCH is transmitted, wherein the transmission of the first CG-PUSCH from the plurality of second CG-PUSCHs overlaps in time with the transmission of the PUCCH.

4. The method according to claim 1, wherein The determining and the multiplexing are performed for the transmission of each CG-PUSCH in each corresponding TO from the set of TOs within the time period.

5. The method according to claim 1, further comprising: receiving second information regarding uplink-downlink UL-DL time domain duplex TDD configuration through radio resource control signaling; as well as Based on the UL-DL TDD configuration, invalid TOs are determined from the first set of TOs within the time period, wherein: Invalid TO is a TO for which a CG-PUSCH transmission would include downlink symbols of the UL-DL TDD configuration, and The invalid TO is not included in the first TO.

6. The method according to claim 1, further comprising: receiving second information regarding a time value through radio resource control signaling; as well as Determining a plurality of second TOs for transmitting corresponding plurality of second CG-PUSCHs from a second set of TOs within the time period, wherein: The plurality of second TOs are later than the plurality of first TOs, and In the case where a TO is in the first set of TOs, in the second set of TOs and not in the multiple first TOs, if the start time of the one TO is not later than the end time of the first CG-PUSCH transmission by a duration greater than or equal to the time value, then the one TO is not in the multiple second TOs.

7. The method according to claim 1, further comprising: During the time overlap, power allocation is prioritized for transmission of the PUSCH over transmission of the first CG-PUSCH.

8. A user equipment (UE), comprising: transceiver; as well as a processor operatively coupled to the transceiver, the processor configured to: Receiving first information for a configuration grant CG configuration for transmitting a plurality of physical uplink shared channels (PUSCHs) through radio resource control signaling, wherein the first information includes a time period, Determine a plurality of first TOs for transmitting corresponding plurality of first CG-PUSCHs from a first set of transmission opportunities TO within the time period, determining first control information providing an indication of the plurality of first TOs, multiplexing the first control information in a first CG-PUSCH from the plurality of first CG-PUSCHs, wherein the first CG-PUSCH is earliest in time among the plurality of first CG-PUSCHs, multiplexing second control information in a PUSCH other than the first CG-PUSCH, wherein the second control information provides first confirmation information or first channel state information, and sending the first CG-PUSCH and the PUSCH, and The transmission of the first CG-PUSCH overlaps with the transmission of the PUSCH in time.

9. The UE according to claim 8, wherein: The processor is further configured to: determining a plurality of second TOs for transmitting a plurality of second CG-PUSCHs from a second set of TOs within the time period, determining third control information providing an indication of the plurality of second TOs, and The third control information and the fourth control information are multiplexed in the first CG-PUSCH from the plurality of second CG-PUSCHs, wherein: The fourth control information is confirmation information, and Before jointly encoding the third control information and the fourth control information, the third control information is appended to the fourth control information, and The processor is further configured to transmit the first CG-PUSCH from the plurality of second CG-PUSCHs.

10. A method performed by a base station BS, the method comprising: Sending first information for a configuration grant CG configured for receiving a physical uplink shared channel PUSCH through radio resource control signaling, wherein the first information includes a time period; Determining a plurality of first ROs for receiving corresponding plurality of first CG-PUSCHs from a first set of reception opportunities ROs within the time period; and receiving a first CG-PUSCH from among the plurality of first CG-PUSCHs and a PUSCH other than the first CG-PUSCH, The first CG-PUSCH is the earliest in time among the multiple first CG-PUSCHs. The reception of the first CG-PUSCH overlaps with the reception of the PUSCH in time, The first CG-PUSCH includes multiplexed first control information, the first control information provides an indication of the multiple first ROs, and The PUSCH includes multiplexed second control information, and the second control information provides first confirmation information or first channel state information.

11. A base station BS, comprising: transceiver; as well as a processor operatively coupled to the transceiver, the processor configured to: The method further comprises transmitting first information for configuring a configuration grant CG for receiving a physical uplink shared channel PUSCH through radio resource control signaling, wherein the first information includes a time period. determining a plurality of first ROs for receiving corresponding plurality of first CG-PUSCHs from a first set of reception opportunities ROs within the time period, and receiving a first CG-PUSCH from among the plurality of first CG-PUSCHs and a PUSCH other than the first CG-PUSCH, The first CG-PUSCH is the earliest in time among the multiple first CG-PUSCHs. The reception of the first CG-PUSCH overlaps with the reception of the PUSCH in time, The first CG-PUSCH includes multiplexed first control information, the first control information provides an indication of the multiple first ROs, and The PUSCH includes multiplexed second control information, and the second control information provides first confirmation information or first channel state information.

12. The BS according to claim 11, wherein: The processor is further configured to determine a plurality of second ROs for receiving a plurality of second CG-PUSCHs from a second set of ROs within the time period, The first CG-PUSCH is from the plurality of second CG-PUSCHs, The first CG-PUSCH also includes multiplexed third control information and fourth control information, The third control information provides an indication of the plurality of second ROs, The fourth control information is confirmation information, and Prior to joint encoding of the third control information and the fourth control information, the third control information is appended to the fourth control information.

13. The BS according to claim 11, wherein: The processor is further configured to determine a plurality of second ROs for receiving a plurality of second CG-PUSCHs from a second set of ROs within the time period, The first CG-PUSCH is from the plurality of second CG-PUSCHs, The first CG-PUSCH further includes multiplexed third control information, wherein the third control information provides an indication of the plurality of second ROs. The processor is further configured to receive a physical uplink control channel (PUCCH) including the multiplexed fourth control information, and The fourth control information is confirmation information or channel state information.

14. The BS according to claim 11, wherein: The processor is further configured to: sending second information for uplink-downlink UL-DL time domain duplex TDD configuration through radio resource control signaling, and determining an invalid RO from the first set of ROs within the time period based on the UL-DL TDD configuration, An invalid RO is an RO for which CG-PUSCH reception would include downlink symbols of the UL-DL TDD configuration, and The invalid RO is not included in the first RO.

15. The BS according to claim 11, wherein: The processor is further configured to: sending second information for the time value through radio resource control signaling, and determining a plurality of second ROs for receiving corresponding plurality of second CG-PUSCHs from a second set of ROs within the time period, The plurality of second ROs are later than the plurality of first ROs, and In the case where an RO is in the first set of ROs, in the second set of ROs, and not in the multiple first ROs, if the start time of the one RO is not later than the first CG-PUSCH reception end time by a duration greater than or equal to the time value, then the one RO is not in the multiple second ROs.

Images