Methods and apparatuses for UCI multiplexing in a wireless communication system

Abstract

The present disclosure relates to a 5G communication system or a 6G communication system for supporting higher data rates beyond 4G communication systems such as Long Term Evolution (LTE). Methods and apparatuses in a wireless communication system include: determining the number of bits for a PUSCH; generating a first set of bits for CG-UCI; generating a second set of bits for HARQ feedback; if the sum of the first set of bits and the second set of bits does not exceed the determined number of bits for the PUSCH, multiplexing the first set of bits for CG-UCI and the second set of bits for HARQ feedback into the PUSCH, wherein the first set of bits for CG-UCI is multiplexed with a higher priority than the second set of bits for HARQ feedback; and transmitting, via an uplink channel, the PUSCH including the multiplexed first set of bits and second set of bits for CG-UCI and HARQ feedback, respectively, to a BS.

Description

Technical Field

[0001] This application generally relates to wireless communication systems, and more particularly, the present disclosure relates to window size adaptation for broadband operation in NR unlicensed. Background Art

[0002] Considering the development of wireless communication from generation to generation, technologies have been developed mainly for human-oriented services, such as voice calls, multimedia services, and data services. With the commercialization of 5G (fifth generation) communication systems, the number of connected devices is expected to grow exponentially. These devices will be increasingly connected to communication networks. Examples of connected things can include vehicles, robots, drones, household appliances, displays, smart sensors connected to various infrastructures, construction machinery, and factory instruments. Mobile devices are expected to evolve into various form-factors, such as augmented reality glasses, virtual reality headsets, and holographic devices. In order to provide various services by connecting hundreds of billions of devices and things in the 6G (sixth generation) era, efforts have been made to develop improved 6G communication systems. For these reasons, 6G communication systems are called ultra-5G systems.

[0003] The 6G communication system expected to be commercialized around 2030 will have a peak data rate of tera (1000 giga) bytes per second (bps) and a radio latency of less than 100 microseconds, and thus will be 50 times the data rate of 5G communication systems and have 1 / 10 of the radio latency of 5G communication systems.

[0004] To achieve such high data rates and ultra-low latency, it has been considered to implement 6G communication systems in the terahertz frequency band (e.g., 95 GHz to 3 THz band). Since path loss and atmospheric absorption in the terahertz band are more severe than those in the millimeter wave band introduced in 5G, technologies capable of ensuring signal transmission distance (i.e., coverage) are expected to become more critical. It is necessary to develop radio frequency (RF) components, antennas, innovative waveforms with better coverage than orthogonal frequency division multiplexing (OFDM), beamforming, and massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, and multi-antenna transmission technologies (such as massive antennas) as the main technologies for ensuring coverage. In addition, new technologies for improving the coverage of terahertz band signals, such as metamaterial-based lenses and antennas, orbital angular momentum (OAM), and reconfigurable intelligent surface (RIS), have been discussed.

[0005] In addition, to improve spectral efficiency and overall network performance, the following technologies have been developed for 6G communication systems: full-duplex technology that enables uplink and downlink transmissions to use the same frequency resources simultaneously; network technologies that comprehensively utilize satellites, high-altitude platform stations (HAPS), etc.; improved network architectures for supporting mobile base stations, etc., and achieving network operation optimization and automation, etc.; dynamic spectrum sharing technology via conflict avoidance based on spectrum usage prediction; the use of artificial intelligence (AI) in wireless communication to improve overall network operation by leveraging AI from the design stage of developing 6G and internalizing end-to-end AI support capabilities; and next-generation distributed computing technology that overcomes the limitations of UE computing capabilities through ultra-high-performance communication and computing resources (such as mobile edge computing (MEC), cloud, etc.) accessible on the network. In addition, by designing new protocols for 6G communication systems, developing mechanisms for implementing hardware-based security environments and secure data usage, and developing technologies for maintaining privacy, continuous attempts are being made to strengthen connections between devices, optimize the network, promote network entity softwareization, and increase wireless communication openness.

[0006] Research and development on 6G communication systems in terms of hyper-connectivity (including person to machine (P2M) and machine to machine (M2M)) is expected to enable the next-generation hyper-connectivity experience. In particular, services such as truly immersive extended reality (XR), high-fidelity mobile holography, and digital replicas are expected to be provided through 6G communication systems. In addition, services for security and reliability enhancement, industrial automation, and emergency response (such as remote surgery) will also be provided through 6G communication systems, enabling these technologies to be applied to various fields such as industry, healthcare, automotive, and household appliances.

[0007] A communication system includes a downlink (DL) that transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE), and an uplink (UL) that transmits signals from the UE to a receiving point such as NodeB. The UE (usually also referred to as a terminal or mobile station) can be fixed or mobile and can be a cellular phone, a personal computer device, or an automated device. An eNodeB (eNB), which refers to NodeB in a Long-Term Evolution (LTE) communication system, and a gNodeB (gNB), which refers to NodeB in a New Radio (NR) communication system, can also be referred to as access points or other equivalent terms. Summary of the Invention

[0008] Solution to the problem

[0009] The present disclosure relates to a quasi-5G or 5G communication system with window size adaptation for broadband operation in NR unlicensed.

[0010] In one embodiment, a user equipment (UE) in a wireless communication system is provided. The UE includes a processor configured to: determine the number of bits for a physical uplink shared channel (PUSCH); generate a first set of bits for grant uplink control information (CG-UCI); generate a second set of bits for hybrid automatic repeat request (HARQ) feedback; and multiplex the first set of bits for CG-UCI and the second set of bits for HARQ feedback into the PUSCH if the sum of the first set of bits and the second set of bits does not exceed the determined number of bits for PUSCH feedback, wherein the first set of bits for CG-UCI is multiplexed with a higher priority than the second set of bits for HARQ feedback. The UE further includes a transceiver operatively connected to the processor, the transceiver being configured to transmit, via an uplink channel, a PUSCH including the multiplexed first set of bits and the second set of bits for CG-UCI and HARQ feedback, respectively, to a base station (BS).

[0011] In another embodiment, a base station (BS) in a wireless communication system is provided. The BS includes a transceiver configured to receive, via an uplink channel, a physical uplink shared channel (PUSCH) from a user equipment (UE) including a first set of bits for grant uplink control information (CG-UCI) and a second set of bits for hybrid automatic repeat request (HARQ) feedback, wherein: the first set of bits and the second set of bits are multiplexed into the PUSCH based on a comparison between the sum of the first set of bits and the second set of bits and the number of bits for the PUSCH; and the first set of bits for CG-UCI is multiplexed with a higher priority than the second set of bits for HARQ feedback.

[0012] In yet another embodiment, a method for a user equipment (UE) in a wireless communication system is provided. The method includes: determining the number of bits of a physical uplink shared channel (PUSCH); generating a first set of bits for grant-based uplink control information (CG-UCI); generating a second set of bits for hybrid automatic repeat request (HARQ) feedback; if the sum of the first set of bits and the second set of bits does not exceed the determined number of bits for the PUSCH, multiplexing the first set of bits for CG-UCI and the second set of bits for HARQ feedback into the PUSCH, wherein the first set of bits for CG-UCI is multiplexed with a higher priority than the second set of bits for HARQ feedback; and transmitting, via an uplink channel, the PUSCH including the multiplexed first set of bits and second set of bits for CG-UCI and HARQ feedback, respectively, to a base station (BS).

[0013] Other technical features will be clear to those skilled in the art from the accompanying drawings, description, and claims.

[0014] Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases used in this patent document. The term "couple" and its derivatives refer to any direct or indirect communication between two or more elements, whether or not those elements are in physical contact with each other. The terms "transmit," "receive," and "communicate," and their derivatives, include both direct and indirect communication. The terms "include" and "comprise," and their derivatives, mean including but not limited to. The term "or" is inclusive, meaning and / or. The phrase "associated with," and its derivatives, means including, included within, interconnected with, containing, contained within, connected to or with, coupled to or with, communicable with, cooperating with, interlaced, juxtaposed, proximate to, bound to or with, having, having the attribute of, having a relationship to or with, etc. The term "controller" refers to any device, system, or part 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 functions associated with any particular controller may be centralized or distributed, whether local or remote. When used with a list of items, the phrase "at least one of" means that different combinations of one or more of the listed items may be used and only one item in the list may be required. For example, "at least one of A, B, and C" includes any of the following combinations: A; B; C; A and B; A and C; B and C; and A and B and C.

[0015] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed of computer-readable program code and contained in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, related data, or portions thereof suitable for implementation in appropriate 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 disk drive, compact disc (CD), digital versatile disc (DVD), or any other type of memory. A "non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transitory electrical signals or other signals. Non-transitory computer-readable media include media that can permanently store data and media that can store data and later overwrite it, such as rewritable optical discs or erasable memory devices.

[0016] Definitions for other specific 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 the prior and future use of such defined words and phrases. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] To more fully understand 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:

[0018] Figure 1 An example wireless network according to an embodiment of the present disclosure is shown;

[0019] Figure 2 An example gNB according to an embodiment of the present disclosure is shown;

[0020] Figure 3 An example UE according to an embodiment of the present disclosure is shown;

[0021] Figure 4 An example transmitter structure using OFDM according to an embodiment of the present disclosure is shown;

[0022] Figure 5 An example receiver structure using OFDM according to an embodiment of the present disclosure is shown;

[0023] Figure 6 An example encoding process for DCI format according to an embodiment of the present disclosure is shown;

[0024] Figure 7Shows an example decoding process for DCI format for a UE according to an embodiment of the present disclosure;

[0025] Figure 8 Shows an example channel access process according to an embodiment of the present disclosure;

[0026] Figure 9 Shows an example CWS bandwidth according to an embodiment of the present disclosure;

[0027] Figure 10 Shows another example CWS bandwidth according to an embodiment of the present disclosure;

[0028] Figure 11 Shows yet another example CWS bandwidth according to an embodiment of the present disclosure;

[0029] Figure 12 Shows an example CWS bandwidth and PDSCH according to an embodiment of the present disclosure;

[0030] Figure 13 Shows an example active BWP switch according to an embodiment of the present disclosure;

[0031] Figure 14 Shows an example CWS for BWP according to an embodiment of the present disclosure;

[0032] Figure 15 Shows an example BWP and CBG according to an embodiment of the present disclosure;

[0033] Figure 16 Shows an example BWP according to an embodiment of the present disclosure;

[0034] Figure 17 Shows an example BWP and CBG according to an embodiment of the present disclosure;

[0035] Figure 18 Shows an example UL BWP in carrier BW according to an embodiment of the present disclosure;

[0036] Figure 19 Shows an example PUSCH in carrier BW according to an embodiment of the present disclosure;

[0037] Figure 20 Shows a flowchart of a multiplexing method according to an embodiment of the present disclosure;

[0038] Figure 21 Shows another flowchart of a multiplexing method according to an embodiment of the present disclosure;

[0039] Figure 22 Shows yet another flowchart of a multiplexing method according to an embodiment of the present disclosure;

[0040] Figure 23 Shows an example LBT position according to an embodiment of the present disclosure;

[0041] Figure 24 Shows a flowchart of a method for an adaptive LBT process according to an embodiment of the present disclosure;

[0042] Figure 25 Shows another flowchart of a method for an adaptive LBT process according to an embodiment of the present disclosure;

[0043] Figure 26 Shows a flowchart of a method for LBT type sorting according to an embodiment of the present disclosure;

[0044] Figure 27 Shows another flowchart of a method for LBT type sorting according to an embodiment of the present disclosure; and

[0045] Figure 28 Shows a flowchart of a method for window size adaptation according to an embodiment of the present disclosure. Detailed Description

[0046] The following discussion Figures 1 to 28 , and the various embodiments used in this patent document to describe the principles of the present disclosure are merely exemplary and should not be construed 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.

[0047] The following documents are incorporated by reference into this disclosure as if fully set forth herein: 3GPP TS 38.211 v15.4.0, "NR; Physical channels and modulation (NR; Physical channels and modulation)"; 3GPP TS 38.212 v15.4.0, "NR; Multiplexing and Channel coding (NR; Multiplexing and Channel coding)"; 3GPP TS 38.213 v15.4.0, "NR; Physical Layer Procedures for Control (NR; Physical Layer Procedures for Control)"; 3GPP TS 38.214 v15.4.0, "NR; Physical Layer Procedures for Data (NR; Physical Layer Procedures for Data)"; 3GPP TS 38.331 v15.4.0, "NR; Radio Resource Control (RRC) Protocol Specification (NR; Radio Resource Control Protocol Specification)"; ETSI EN 301 893 V2.1.1, "5GHz RLAN; Harmonized Standard covering the essential requirements of article 3.2 of Directive 2014 / 53 / EU (5GHz RLAN; Harmonized Standard covering the essential requirements of article 3.2 of Directive 2014 / 53 / EU)", 2017; ETSI EN 302 567 V2.1 1, "Multiple-Gigabit / s radio equipment operating in the 60GHz band; Harmonized Standard covering the essential requirements of article 3.2 of Directive 2014 / 53 / EU (Multiple-Gigabit / s radio equipment operating in the 60GHz band; Harmonized Standard covering the essential requirements of article 3.2 of Directive 2014 / 53 / EU), 2017; 3GPP TR 36.889 V13.0.0, "Study on Licensed-Assisted Access to Unlicensed Spectrum (Study on Licensed-Assisted Access to Unlicensed Spectrum)", 2015; and IEEE Standard 802.11 - 2016, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", 2016.

[0048] The following Figures 1 - 3 describes various embodiments implemented using orthogonal frequency division multiplexing (OFDM) or orthogonal frequency division multiple access (OFDMA) communication techniques in a wireless communication system. Figures 1 - 3 The description does not imply physical or architectural limitations on the ways in which different embodiments can be implemented. Different embodiments of the present disclosure can be implemented in any suitably arranged communication system.

[0049] Figure 1 illustrates an example wireless network according to an embodiment of the present disclosure. Figure 1 The illustrated embodiment of the wireless network is for illustrative purposes only. Other embodiments of the wireless network 100 can be used without departing from the scope of the present disclosure.

[0050] As Figure 1 shown, the wireless network includes gNB 101, gNB 102, and gNB 103. gNB 101 communicates with gNB 102 and gNB 103. gNB 101 also communicates with at least one network 130 (such as the Internet, a proprietary Internet Protocol (IP) network, or other data networks).

[0051] gNB 102 provides wireless broadband access to network 130 for a first plurality of user equipment (UE) within the coverage area 120 of gNB 102. The first plurality of UEs includes UE 111, which may be located in a small business; 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, a wireless laptop computer, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within the coverage area 125 of gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNBs 101 - 103 may use 5G, LTE, LTE - A, WiMAX, WiFi, or other wireless communication technologies to communicate with each other and with UEs 111 - 116.

[0052] Depending on the network type, the term "base station" or "BS" can refer to any component (or collection of components) configured to provide wireless access to a network, such as a transmission point (TP), a transmission-reception point (TRP), an enhanced base station (eNodeB or eNB), a 5G base station (gNB), a macro cell, a femto cell, a Wi-Fi access point (AP), or other wireless-enabled devices. The base station can provide wireless access according to one or more wireless communication protocols (e.g., 5G 3GPP New Radio Interface / Access (NR), Long-Term Evolution (LTE), LTE-Advanced (LTE-A), High-Speed Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc.). For convenience, in this patent document, the terms "BS" and "TRP" can be used interchangeably to refer to the network infrastructure components that provide wireless access to remote terminals. Additionally, depending on the network type, the term "user equipment" or "UE" can refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user device". For convenience, in this patent document, the terms "user equipment" and "UE" are used to refer to the remote wireless devices that wirelessly access the BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or a device that is typically considered fixed (such as a desktop computer or a vending machine).

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

[0054] Although Figure 1 an example of a wireless network is shown, various changes can be made to Figure 1 it. For example, the wireless network can include any suitable arrangement of any number of gNBs and any number of UEs. Additionally, gNB 101 can communicate directly with any number of UEs and provide wireless broadband access to network 130 to these UEs. Similarly, each of gNBs 102 - 103 can communicate directly with network 130 and provide direct wireless broadband access to the UEs. Further, gNBs 101, 102, and / or 103 can provide access to other or additional external networks (such as an external telephone network or other types of data networks).

[0055] Figure 2 An example gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The illustrated embodiment of gNB 102 is for illustrative purposes only, Figure 1gNBs 101 and 103 may have the same or similar configurations. However, gNBs have a wide variety of configurations, and Figure 2 does not limit the scope of the present disclosure to any particular implementation of a gNB.

[0056] As Figure 2 shown, gNB 102 includes a plurality of antennas 205a - 205n, a plurality of RF transceivers 210a - 210n, transmit (TX) processing circuitry 215, and receive (RX) processing circuitry 220. gNB 102 also includes a controller / processor 225, a memory 230, and a backhaul or network interface 235.

[0057] RF transceivers 210a - 210n receive incoming RF signals, such as signals transmitted by UEs in network 100, from antennas 205a - 205n. RF transceivers 210a - 210n down-convert the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 220, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 220 sends the processed baseband signal to controller / processor 225 for further processing.

[0058] TX processing circuitry 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from controller / processor 225. TX processing circuitry 215 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate a processed baseband or IF signal. RF transceivers 210a - 210n receive the outgoing processed baseband or IF signal from TX processing circuitry 215 and up-convert the baseband or IF signal to an RF signal transmitted via antennas 205a - 205n.

[0059] Controller / processor 225 may include one or more processors or other processing devices that control the overall operation of gNB 102. For example, controller / processor 225 may control the reception of forward channel signals and the transmission of reverse channel signals by RF transceivers 210a - 210n, RX processing circuitry 220, and TX processing circuitry 215 according to well-known principles. Controller / processor 225 may also support additional functions, such as more advanced wireless communication functions. For example, controller / processor 225 may support beamforming or directional routing operations, in which outgoing signals from a plurality of antennas 205a - 205n are weighted differently to effectively direct the outgoing signals in a desired direction. In gNB 102, controller / processor 225 may support any of a variety of other functions.

[0060] The controller / processor 225 is also capable of executing programs and other processes residing in the memory 230, such as the OS. The controller / processor 225 can move data into or out of the memory 230 as needed for the execution of the processes.

[0061] 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 via a network. The interface 235 can support communication via any suitable wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (such as a system supporting 5G, 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 via a wired or wireless local area network or via a wired or wireless connection to a larger network (such as the Internet). The interface 235 includes any suitable structure that supports communication via a wired or wireless connection, such as an Ethernet or RF transceiver.

[0062] The memory 230 is coupled to the controller / processor 225. A portion of the memory 230 can include RAM, while another portion of the memory 230 can include flash memory or other ROM.

[0063] Although Figure 2 one example of the gNB 102 is shown, various changes can be made to Figure 2 it. For example, the gNB 102 can include any number of Figure 2 each of the components shown. As a specific example, an access point can include multiple interfaces 235, and the controller / processor 225 can support routing functions to route data between different network addresses. As another specific example, although shown as including a single instance of the TX processing circuit 215 and a single instance of the RX processing circuit 220, the gNB 102 can include multiple instances of each component (such as one for each RF transceiver). Additionally, Figure 2 the various components in

[0064] Figure 3 An example UE 116 according to an embodiment of the present disclosure is shown. Figure 3 The embodiment of the UE 116 shown is for illustrative purposes only, Figure 1 and the UEs 111 - 115 can have the same or similar configurations. However, UEs have a wide variety of configurations, and Figure 3 the scope of the present disclosure is not limited to any particular implementation of the UE.

[0065] As shown Figure 3 UE 116 includes antenna 305, radio frequency (RF) transceiver 310, TX processing circuitry 315, microphone 320, and receive (RX) processing circuitry 325. UE 116 also includes speaker 330, processor 340, input / output (I / O) interface 345, touch screen 350, display 355, and memory 360. Memory 360 includes operating system (OS) 361 and one or more applications 362.

[0066] RF transceiver 310 receives incoming RF signals transmitted by gNB of network 100 from antenna 305. RF transceiver 310 down-converts the incoming RF signals to generate IF or baseband signals. The IF or baseband signals are sent to RX processing circuitry 325, which generates processed baseband signals by filtering, decoding, and / or digitizing the baseband or IF signals. RX processing circuitry 325 sends the processed baseband signals to speaker 330 (such as for voice data) or processor 340 for further processing (such as for web browsing data).

[0067] TX processing circuitry 315 receives analog or digital voice data from microphone 320, or other outgoing baseband data (such as web data, e-mail, or interactive video game data) from processor 340. TX processing circuitry 315 encodes, multiplexes, and / or digitizes the outgoing baseband data to generate processed baseband or IF signals. RF transceiver 310 receives the outgoing processed baseband or IF signals from TX processing circuitry 315 and up-converts the baseband or IF signals to RF signals transmitted via antenna 305.

[0068] Processor 340 may include one or more processors or other processing devices, and executes OS 361 stored in memory 360 to control the overall operation of UE 116. For example, processor 340 may control the reception of forward channel signals and the transmission of reverse channel signals by RF transceiver 310, RX processing circuitry 325, and TX processing circuitry 315 according to well-known principles. In some embodiments, processor 340 includes at least one microprocessor or microcontroller.

[0069] The processor 340 is also capable of executing other processes and programs resident in the memory 360, such as processes for beam management. The processor 340 can move data into or out of the memory 360 as needed for executing processes. In some embodiments, the processor 340 is configured to execute the application 362 based on the OS 361 or in response to signals received from the gNB or the operator. The processor 340 is also coupled to an I / O interface 345, which provides the UE 116 with the ability to connect to other devices, such as laptop computers and handheld computers. The I / O interface 345 is a communication path between these accessories and the processor 340.

[0070] The processor 340 is also coupled to a touch screen 350 and a display 355. An operator of the UE 116 can use the touch screen 350 to input data to 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.

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

[0072] Although Figure 3 an example of the UE 116 is shown, various changes can be made. For example, Figure 3 the various components in Figure 3 can be combined, further subdivided, or omitted, and additional components can be added according to specific requirements. As a specific example, the 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). Additionally, although Figure 3 the UE 116 is shown configured as a mobile phone or smartphone, the UE can be configured to operate as other types of mobile or fixed devices.

[0073] This disclosure generally relates to wireless communication systems, and more particularly, to reducing power consumption of a UE communicating with a base station, and to transmitting and receiving a physical downlink control channel (PDCCH) to and from a UE for dual connectivity operation. A communication system includes a downlink (DL) referring to transmissions from a base station or one or more transmission points to a UE and an uplink (UL) referring to transmissions from the UE to a base station or one or more reception points.

[0074] In order to meet the demand for wireless data services that has increased since the self-deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems." The 5G communication system is considered to be implemented in a higher frequency (millimeter wave (mmWave)) band (such as the 60 GHz band) in order to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, technologies such as beamforming, massive multiple-input multiple-output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and massive antennas are discussed in 5G communication systems. In addition, in 5G communication systems, system network improvements are being developed based on advanced small cells, cloud radio access network (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multi-point (CoMP), receiver interference cancellation, etc.

[0075] A time unit used for DL signaling or UL signaling on a cell is called a time slot and may include one or more symbols. A symbol can also be an additional time unit. A frequency (or bandwidth (BW)) unit is called a resource block. One RB includes multiple subcarriers (SCs). For example, a time slot may include 14 symbols, with a duration of 1 millisecond or 0.5 millisecond, and an RB may have a BW of 180 kHz or 360 kHz and include 12 SCs, with the spacing between SCs being 15 kHz or 30 kHz, respectively.

[0076] DL signals include data signals that carry information content, control signals that carry DL control information (DCI) formats, and reference signals (RS) also known as pilot signals. The gNB can transmit data information (e.g., transport blocks) or DCI formats through the corresponding physical DL shared channel (PDSCH) or physical DL control channel (PDCCH). The gNB can send one or more of various types of RS (including channel state information RS (CSI-RS) and demodulation RS (DMRS)). CSI-RS is for the UE to measure channel state information (CSI) or perform other measurements, such as measurements related to mobility support. DMRS can only be transmitted within the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data information or control information.

[0077] The UL signal also includes a data signal for transmitting information content, a control signal for transmitting UL control information (UCI), and RS. The UE transmits data information (e.g., a transport block) or UCI through a corresponding physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). When the UE transmits data information and UCI simultaneously, the UE can multiplex both the data information and UCI in the PUSCH, or transmit the data information and UCI separately in the corresponding PUSCH and PUCCH. The UCI includes hybrid automatic repeat request acknowledgment (HARQ-ACK) information, which indicates whether the UE correctly or incorrectly detects a data transport block (TB), a scheduling request (SR) indicating whether there is data in its buffer, and a CSI report for enabling the gNB to select appropriate parameters to perform PDSCH or PDCCH transmission to the UE for link adaptation.

[0078] The CSI report from the UE may include: a channel quality indicator (CQI), which notifies the gNB of the modulation and coding scheme (MCS) for the UE to detect a data TB with a predetermined block error rate (BLER) (such as a BLER of 10%); a precoding matrix indicator (PMI), which notifies the gNB of how to precode the signaling to the UE; and a rank indicator (RI), which indicates the transmission rank of the PDSCH. The UL RS includes DMRS and sounding reference signal (SRS). The DMRS is transmitted only in the BW of the corresponding PUSCH or PUSCH transmission. The gNB can use the DMRS to demodulate the information in the corresponding PUSCH or PUCCH. The UE transmits the SRS to provide UL CSI to the gNB, and for a TDD or flexible duplex system, also provides a PMI for DL transmission. The UL DMRS or SRS transmission can be based on, for example, the transmission of Zadoff-Chu (ZC) sequences, or generally based on the transmission of CAZAC sequences.

[0079] The DL transmission and UL transmission can be based on an orthogonal frequency division multiplexing (OFDM) waveform, which includes a variant using DFT precoding, called DFT-spread-OFDM.

[0080] Figure 4 An example transmitter structure 400 using OFDM according to an embodiment of the present disclosure is shown. Figure 4 The embodiment of the shown transmitter structure 400 is for illustration only. Figure 4 One or more of the shown components can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0081] Information bits such as DCI bits or data bits 410 are encoded by an encoder 420, rate-matched to the allocated time / frequency resources by a rate matcher 430, and modulated by a modulator 440. Subsequently, the modulated and encoded symbols and DMRS or CSI-RS 450 are mapped to SC 460 by an SC mapping unit 465, an inverse fast Fourier transform (IFFT) is performed by a filter 470, a cyclic prefix (CP) is added by a CP insertion unit, and the resulting signal is filtered by a filter 490 and transmitted by a radio frequency (RF) unit 495.

[0082] Figure 5 An example receiver structure 500 using OFDM according to an embodiment of the present disclosure is shown. Figure 5 The embodiment of the shown receiver structure 500 is for illustration only. Figure 5 One or more of the shown components may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0083] The received signal 510 is filtered by a filter 520, the CP is removed by a CP removal unit 530, a fast Fourier transform (FFT) is applied by a filter 540, the SC selected by a BW selector unit 555 is demapped by an SC demapping unit 550, the received symbols are demodulated by a channel estimator and demodulator unit 560, the rate dematching is restored by a rate dematcher 570, and the decoder 580 decodes the resulting bits to provide information bits 590.

[0084] A UE typically monitors multiple candidate positions of corresponding potential PDCCH transmissions to decode multiple candidate DCI formats in a time slot. Monitoring PDCCH candidates means receiving and decoding PDCCH candidates according to the DCI formats that the UE is configured to receive. The DCI format includes cyclic redundancy check (CRC) bits for the UE to confirm the correct detection of the DCI format. The DCI format type is identified by a radio network temporary identifier (RNTI) that scrambles the CRC bits. For the DCI format that schedules PDSCH or PUSCH for a single UE, the RNTI may be a cell RNTI (C-RNTI) and is used as a UE identifier.

[0085] For the DCI format of the PDSCH that schedules the transmission of system information (SI), the RNTI can be the SI-RNTI. For the DCI format of the PDSCH that schedules the transmission of a random access response (RAR), the RNTI can be the RA-RNTI. For the DCI format of the PDSCH or PUSCH that is scheduled to a single UE before the UE establishes a radio resource control (RRC) connection with the serving gNB, the RNTI can be a temporary C-RNTI (TC-RNTI). For the DCI format that provides a TPC command to a UE group, the RNTI can be the TPC-PUSCH-RNTI or the TPC-PUCCH-RNTI. Each type of RNTI can be configured for the UE via higher layer signaling, such as RRC signaling. The DCI format for scheduling the PDSCH transmission to the UE is also referred to as the DL DCI format or DL assignment, and the DCI format for scheduling the PUSCH transmission from the UE is also referred to as the UL DCI format or UL grant.

[0086] The PDCCH transmission can be within a physical RB (PRB) set. The gNB can configure one or more PRB sets (also referred to as control resource sets) for the UE for PDCCH reception. The PDCCH transmission can be in a control channel element (CCE) included in the control resource set. The UE determines the CCE for PDCCH reception based on a search space, such as a UE-specific search space (USS), for PDCCH candidates of a DCI format with a CRC scrambled by an RNTI, such as the C-RNTI, that is configured for the UE via UE-specific RRC signaling for scheduling PDSCH reception or PUSCH transmission, and a common search space (CSS) for PDCCH candidates of a DCI format with a CRC scrambled by other RNTIs. The set of CCEs that can be used for PDCCH transmission to the UE defines the PDCCH candidate locations. The attribute of the control resource set is the transmission configuration indication (TCI) state that provides quasi-co-location information of the DMRS antenna port for PDCCH reception.

[0087] Figure 6 An example encoding process 600 of a DCI format according to an embodiment of the present disclosure is shown. Figure 6 The embodiment of the encoding process 600 shown is for illustration only. Figure 6 One or more of the components shown can be implemented in a dedicated circuit configured to perform the function, or one or more of the components can be implemented by one or more processors executing instructions to perform the function. Other embodiments are used without departing from the scope of the present disclosure.

[0088] The gNB encodes and transmits each DCI format separately in the corresponding PDCCH. The RNTI masks the CRC of the DCI format codeword so that the UE can identify the DCI format. For example, the CRC and RNTI may include, for example, 16 bits or 24 bits. A CRC calculation unit 620 is used to determine the cyclic redundancy check of the (uncoded) DCI format bits 610, and an exclusive OR (XOR) operation unit 630 is used between the CRC bits and the RNTI bits 640 to mask the CRC. The XOR operation is defined as XOR(0, 0)=0, XOR(0, 1)=1, XOR(1, 0)=1, XOR(1, 1)=0. A CRC attachment unit 650 is used to attach the masked CRC bits to the DCI format information bits. An encoder 660 performs channel coding (such as tail-biting convolutional coding or polar coding), and then a rate matcher 670 rate-matches it to the allocated resources. An interleaving and modulation unit 680 applies interleaving and modulation (such as QPSK), and the output control signal 690 is transmitted.

[0089] Figure 7 An example decoding process 700 for a DCI format for a UE according to an embodiment of the present disclosure is shown. Figure 7 The embodiment of the decoding process 700 shown is for illustration only. Figure 7 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0090] The received control signal 710 is demodulated and deinterleaved by a demodulator and deinterleaver 720. A rate matcher 730 restores the rate matching applied at the gNB transmitter, and a decoder 740 decodes the resulting bits. After decoding, a CRC extractor 750 extracts the CRC bits and provides the DCI format information bits 760. The DCI format information bits are demasked 770 by an XOR operation with the RNTI 780 (when applicable), and a unit 790 performs a CRC check. When the CRC check is successful (the checksum is zero), the DCI format information bits are considered valid. When the CRC check is not successful, the DCI format information bits are considered invalid.

[0091] Figure 8 An example channel access process 800 according to an embodiment of the present disclosure is shown. Figure 8 The embodiment of the channel access process 800 shown is for illustration only. Figure 8 It does not limit the scope of the present disclosure.

[0092] In the 3GPP standard specification, the downlink transmission including the Physical Downlink Shared Channel (PDSCH) on the LAA carrier follows the Category 4 Listen Before Talk (Cat4 LBT) process ( Figure 8 shown in the flowchart). The eNB initially remains in the IDLE state (step 801). Depending on whether there is data traffic (step 811), the gNB transfers to the CONTEND state (step 802) or remains in the IDLE state (step 801) respectively. The eNB first performs an initial Clear Channel Assessment (iCCA), where the eNB senses the channel within the slot duration of the delay duration (step 812). If the channel is detected as idle in the iCCA, the gNB starts transmitting (step 803); otherwise, the gNB generates a Backoff (BO) counter (step 821) and performs an extended Clear Channel Assessment (eCCA). The eNB can start transmitting after the BO counter reaches 0 (step 814), as in step 4), where the BO counter is adjusted by sensing the channel within an additional slot duration according to the following steps: 1) Set the counter to a random number uniformly distributed between 0 and the contention window size (CWS) (step 821), and go to step 4); 2) If the counter is greater than 0 and the eNB chooses to decrement the counter, decrement the counter by 1 (step 822); 3) Sense the channel within the additional slot duration, if the additional slot duration is idle, go to step 4); otherwise, go to step 5); 4) If the counter is 0 (step 814), stop; otherwise, go to step 2); 5) Sense the channel until a busy slot is detected within the additional delay duration, or all slots of the additional delay duration are detected as idle (step 815); 6) If the channel is detected as idle during all slot durations of the additional delay duration, go to step 4); otherwise, go to step 5).

[0093] The eNB can continue transmitting until the maximum channel occupancy is reached (step 818). After the transmission, if the transmission is successful, the contention window size is reset (step 823); otherwise, the contention window size is increased (step 824). If the eNB still has data traffic after the transmission (step 811), the eNB continues to contend for the channel (step 802); otherwise, the eNB transfers to the IDLE state (step 801). If the eNB has not had any iCCA failures before (step 816), the eNB can perform an iCCA (step 812); otherwise, the gNB can generate a BO counter (step 821) and perform an eCCA (step 813).

[0094] In the LTE-LAA standard specification, for transmissions including the Physical Downlink Shared Channel (PDSCH), or the Physical Downlink Control Channel (PDCCH), or the Enhanced Physical Downlink Control Channel (EPDCCH), the channel access mechanism is based on LBE (also known as Category-4 (CAT-4) LBT). Specifically, the LTE-LAA eNB can transmit after sensing the channel idle during the slot duration of the latency duration and after the Backoff (BO) counter is zero in step 4). An example of such a channel access procedure is shown in Figure 8 (e.g., for this type of channel access procedure, this channel access procedure is also known as Cat4 LBT).

[0095] The backoff counter is adjusted by sensing the channel in an additional slot duration according to the following steps: (1) Set the counter to a random number uniformly distributed between 0 and the contention window (CW) value, and go to step 4; (2) If the counter is greater than 0 and the eNB chooses to decrement the counter, decrement the counter by 1; (3) Sense the channel in the additional slot duration, and if the additional slot duration is idle, go to step 4; otherwise, go to step 5; (4) If the counter is 0, stop; otherwise, go to step 2; (5) Sense the channel until a busy slot is detected in the additional latency duration or all slots of the additional latency duration are detected as idle; and (6) If the channel is sensed as idle during all slot durations of the additional latency duration, go to step 4); otherwise, go to step 5.

[0096] In addition to the basic channel access procedure, a CWS adaptation mechanism is also defined in LTE-LAA to mitigate transmission collisions. The CAT-4 LBT process defines 4 different channel access priority levels p, each with a different minimum allowed CWS and maximum allowed CWS, and the corresponding Maximum Channel Occupancy Time (MCOT). If the eNB transmits a transmission associated with the channel access priority level p on the carrier, the eNB maintains the contention window value CW P and adjusts CW P before generating a random backoff counter for the channel access procedure of the next transmission.

[0097] Specifically, the following procedure is used: (Step 1) For each priority level p ∈ {1, 2, 3, 4}, set CW P to the minimum CWS of priority level p; and (Step 2) If at least Z = 80% of the HARQ-ACK values corresponding to the PDSCH transmission in the reference subframe k are determined to be NACK, then for each priority level p ∈ {1, 2, 3, 4}, increase CW Pto the next higher allowed value and stay in Step 2; otherwise, go to Step 1.

[0098] For LTE-LAA, the reference subframe k is the starting subframe of the most recent transmission made by the eNB on the carrier for which at least some HARQ-ACK feedback is expected to be available. If no HARQ-ACK feedback is detected for a PDSCH transmission made by the eNB, or the eNB detects a "DTX", "NACK / DTX", or "any" state, it is counted as a NACK.

[0099] The CAT-4 LBT process similar to the LBT of LTE-LAA can be used as the basic channel access mechanism for NR unlicensed (NR-U), and the NR-U CWS adaptation can also be based on the HARQ-ACK feedback from the UE. However, different from LTE-LAA where the HARQ-ACK feedback timing is fixed by the specification and is 4 ms, NR supports a very flexible timing relationship from the PDSCH transmission to the relevant corresponding HARQ-ACK feedback. In addition, compared with the HARQ-ACK feedback of LTE-LAA which is only based on the transport block (TB), NR also supports the HARQ-ACK feedback based on the codeblock group (CBG).

[0100] In addition, contrary to the 20 MHz carrier bandwidth of LTE-LAA, NR supports broadband operation with each carrier in the sub-7 GHz band being up to 100 MHz. In addition, NR supports bandwidth parts (BWPs), where each UE can be configured with up to 4 DL BWPs and up to 4 UL BWPs, and one active DL BWP and one active UL BWP can be activated at a given time; and the active DL / UL BWP can be switched semi-statically, semi-persistently, or dynamically by higher layer parameters or MAC CE or downlink control information (DCI). Due to the flexibility and new features of NR, the CWS adaptation rules for NR-U can also be much more flexible than the CWS adaptation rules of LTE-LAA.

[0101] To support the broadband operation of NR-U, the LBT for NR-U can be performed in the frequency domain in units of the LBT bandwidth, where the LBT for the broadband transmission of NR-U can be performed in parallel on multiple LBT bandwidths. For example, the LBT bandwidth for FR1 NR-U can be 20 MHz.

[0102] This disclosure focuses on the CWS adjustment rules for the broadband operation of NR-U, including the CWS adjustment rules when the PDSCH / PUSCH spans multiple LBT bandwidths but only partially overlaps with one or more LBT bandwidths; and the CWS adjustment rules when BWP switching occurs for adjacent UL / DL transmissions.

[0103] The present disclosure includes several embodiments, principles, methods, and examples, which can be combined or used in combination with each other, or can be operated independently. The embodiments / principles / methods / examples in the present disclosure can be applied to NR-U based on FBE, NR-U based on LBE, or NR-U based on both FBE and LBE.

[0104] In the remainder of the present disclosure, FR1 NR-U refers to NR-U operating in an unlicensed / shared band in FR1 (such as the 5 GHz unlicensed band or the 6 GHz unlicensed / shared band); while FR2 GHz NR-U refers to NR-U operating in an unlicensed / shared band in FR2 (such as the 60 GHz unlicensed band).

[0105] In one embodiment, when PDSCH / PUSCH overlaps with the LBT bandwidth portion, enhancements to the CWS adjustment rules are provided.

[0106] When the NR-U gNB operates on a broadband carrier, multiple parallel LBT operations can be performed simultaneously on different frequency units, thereby obtaining more channel access opportunities. When performing multiple parallel LBTs, the multi-carrier LBT process of LTE-LAA can be used as a reference and applied to the parallel LBTs on different frequency units of NR-U.

[0107] Specifically, type A LBT is an LBT that independently performs CAT-4 LBT on different frequency units, which has a potential self-delay to align transmissions on multiple frequency units. In addition, type A1 is an LBT that independently generates a backoff counter for each frequency unit; while type A2 is an LBT where the same counter is used for all carriers and is the same as the counter generated according to the carrier with the maximum CWS.

[0108] In addition, type B LBT is an LBT that performs CAT-4 LBT on a reference frequency unit and performs a single LBT with a PIFS duration on other frequency units before the completion of the CAT-4 LBT. In addition, type B1 is an LBT where a single CWS is used for all carriers and the CWS is updated according to the HARQ-ACK on all carriers; while type B2 is an LBT that independently maintains the CWS for each carrier.

[0109] For broadband transmission in NR-U, broadband LBT operations similar to LTE-LAA multi-carrier LBT types A and B can be utilized. An important design consideration for NR-U broadband LBT operations is how the frequency-domain granularity maintains a single CWS. For example, for LTE-LAA multi-carrier types A1, A2, and type B2, the CWS is maintained independently on each carrier; while for LTE-LAA multi-carrier type B1, a single CWS is maintained across all carriers.

[0110] In one example, within the carrier bandwidth, the CWS can be jointly determined and maintained on the basis of each CWS bandwidth, thereby determining and maintaining a single CWS for the CWS bandwidth within the carrier bandwidth, and potentially different CWSs can be maintained for different CWS bandwidths within the carrier bandwidth; that is, the CWS bandwidth is the frequency-domain granularity where a single CWS is maintained for NR-U broadband operations.

[0111] In one example, the CWS bandwidth is an LBT bandwidth such that the CWS for NR-U broadband LBT operations can be maintained on the basis of each LBT bandwidth.

[0112] For broadband transmission in NR-U, broadband LBT operations similar to LTE-LAA multi-carrier LBT types A and B can be utilized. An important design consideration for NR-U broadband LBT operations is how the frequency-domain granularity maintains a single CWS. For example, for LTE-LAA multi-carrier types A1, A2, and type B2, the CWS is maintained independently on each carrier; while for LTE-LAA multi-carrier type B1, a single CWS is maintained across all carriers.

[0113] In one example, within the carrier bandwidth, the CWS can be jointly determined and maintained on the basis of each CWS bandwidth, thereby determining and maintaining a single CWS for the CWS bandwidth within the carrier bandwidth, and potentially different CWSs can be maintained for different CWS bandwidths within the carrier bandwidth; that is, the CWS bandwidth is the frequency-domain granularity where a single CWS is maintained for NR-U broadband operations.

[0114] In one example, the CWS bandwidth is an LBT bandwidth such that the CWS for NR-U broadband LBT operations can be maintained on the basis of each LBT bandwidth.

[0115] In one sub-example, this can be applied to the CWS for downlink transmission, where the LBT bandwidth is the LBT bandwidth included within the carrier bandwidth.

[0116] In another sub-example, this can be applied to the CWS for uplink transmission, where the LBT bandwidth can refer to the LBT bandwidth overlapping with the scheduled PUSCH of the UE.

[0117] In another sub-example, this can be applied to the CWS for uplink transmission, where the LBT bandwidth can refer to the LBT bandwidth that overlaps with the UE's current active uplink BWP.

[0118] In another sub-example, this can be applied to the CWS for uplink transmission, where the LBT bandwidth can refer to the LBT bandwidth that overlaps with the UE's configured uplink BWP.

[0119] In one example, the CWS bandwidth is the carrier bandwidth, such that the CWS for NR-U wideband LBT operation can be maintained on a per-carrier-bandwidth basis.

[0120] In one sub-example, this can be applied to the CWS for downlink transmission.

[0121] In another sub-example, if the UE is capable of supporting the entire range of carrier bandwidths, this can be applied to the CWS for uplink transmission.

[0122] In one example, the CWS bandwidth is the BWP, such that the CWS for NR-U wideband LBT operation can be maintained on a per-BWP basis.

[0123] In one sub-example, this can be applied to the CWS for downlink transmission, where for the scheduled UE associated with the gNB, the BWP can be the active DL BWP.

[0124] In another sub-example, this can be applied to the CWS for uplink transmission, where the BWP is the UE's current active UL BWP.

[0125] In another sub-example, this can be applied to the CWS for uplink transmission, where the BWP is the UE's configured UL BWP. For example, the UE can maintain a CWS for each configured UL BWP associated with the UE.

[0126] In one example, the CWS bandwidth is a set of LBT bandwidths, such that the CWS for NR-U wideband LBT operation can be maintained on a basis of the set of LBT bandwidths, where the set of LBT bandwidths can be a set of continuous or non-continuous LBT bandwidths.

[0127] In one sub-example, this can be applied to the CWS for downlink transmission.

[0128] In another sub-example, this can be applied to the CWS for uplink transmission.

[0129] In one example, when the NR-U gNB / UE starts to perform a new CAT-4 LBT procedure to initialize DL / UL transmission on a CWS bandwidth (e.g., in an NR-U time slot indexed as n), the gNB / UE identifies a set of HARQ-ACK values corresponding to previous DL / UL transmissions in a set of reference time-domain and frequency-domain resources, and the set of HARQ-ACK values corresponding to the set of reference time-domain and frequency-domain resources can be used in the rule for determining whether the gNB / UE increases or resets the CWS value corresponding to the current CWS bandwidth.

[0130] In a sub-example, the reference time-domain and frequency-domain (T / F) resources for CW adjustment of the CWS bandwidth can be a set of determined time slots and / or mini-slots and / or partial time slots of a previous transmission burst determined on the CWS bandwidth, and the details for determining the reference T / F resources and the CWS adjustment rule can refer to the NR specification.

[0131] In one example, the configuration of the CWS bandwidth according to the foregoing examples and / or embodiments can be one of being fixed in this specification, semi-statically configured by a higher-layer parameter (e.g., an RRC parameter), dynamically configured by DCI, or configured by a MAC CE.

[0132] In one example, the CWS bandwidth and the frequency-domain granularity at which the wideband LBT for NR-U performs the LBT procedure may be different.

[0133] For example, the frequency-domain granularity of the LBT procedure for the wideband LBT of NR-U can be the LBT bandwidth, and the CWS bandwidth can be selected according to one of the foregoing examples.

[0134] Figure 9 An example CWS bandwidth 900 according to an embodiment of the present disclosure is shown. Figure 9 The embodiment of the shown CWS bandwidth 900 is for illustration only. Figure 9 One or more of the shown components can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0135] For wideband operation in NR-U, the gNB scheduler has sufficient flexibility such that the scheduled downlink or uplink transmission of NR-U can span multiple CWS bandwidths and can partially overlap with one or more CWS bandwidths. Figure 9An example of this scenario is provided where PDSCH1, PDSCH2, and PDSCH 3 all overlap with at least one CWS BW section. Thus, CWS BW1 includes both a subset of PDSCH 1 and a subset of PDSCH2, while CWS BW2 includes both a subset of PDSCH 2 and a subset of PDSCH3.

[0136] One design consideration is how to utilize the HARQ-ACK feedback corresponding to such partially overlapping PDSCH / PUSCH to adjust the current HARQ-ACK CWS when the CWS BW includes at least one scheduled PDSCH / PUSCH transmission that only partially overlaps with the CWS BW on the reference T / F resources of the CWS BW (i.e., only a subset of the PDSCH / PUSCH is within the CWS BW). In Figure 9 the example of, this refers to how to update the CWS to CWS BW0 to CWS BW3 respectively.

[0137] In one embodiment, as long as the PDSCH / PUSCH overlaps with the CWS BW in the frequency domain, the HARQ-ACK feedback of the PDSCH / PUSCH can be utilized to adjust the CWS corresponding to the CWS BW.

[0138] In one example, the foregoing examples and / or embodiments can be applied regardless of whether the HARQ-ACK feedback is TB-based or CBG-based.

[0139] In one example, the foregoing examples and / or embodiments can be applied only when the HARQ-ACK feedback is TB-based.

[0140] In one example, the foregoing examples and / or embodiments can be applied only when the HARQ-ACK feedback is CBG-based.

[0141] In one example, when adjusting the CWS for different CWS BWs, it is allowed to utilize the same HARQ-ACK bits corresponding to the PDSCH / PUSCH on the reference time and frequency resources more than once.

[0142] In one sub-example, for each CWS BW, when adjusting the CWS for different CWS BWs, the same ACK / NACK bits corresponding to the PDSCH / PUSCH on the reference time and frequency resources can be used at most once.

[0143] As Figure 9As shown, the CWS adjustment decision for CWS BW0 may depend on the HARQ-ACK feedback corresponding to PDSCH1; the CWS adjustment decision for CWS BW1 may depend on the HARQ-ACK feedback corresponding to PDSCH1 and PDSCH2; the CWS adjustment decision for CWS BW2 may depend on the HARQ-ACK feedback corresponding to PDSCH2 and PDSCH3; and the CWS adjustment decision for CWS BW3 may depend on the HARQ-ACK feedback corresponding to PDSCH3.

[0144] In one embodiment, when using CBG-based HARQ-ACK feedback, as long as the CBG overlaps with the CWS BW in the frequency domain, the HARQ-ACK feedback corresponding to the CBG of the PDSCH / PUSCH can be utilized when adjusting the CWS corresponding to the CWS BW.

[0145] In one example, when adjusting the CWS for different CWS BWs, it is allowed to utilize the same HARQ-ACK bits corresponding to the CBG of the PDSCH / PUSCH on the reference time and frequency resources more than once.

[0146] In one sub-example, for each CWS BW, when adjusting the CWS for different CWS BWs, the same ACK / NACK bits corresponding to the CBG of the PDSCH / PUSCH on the reference time and frequency resources can be used at most once.

[0147] Figure 10 Another example CWS bandwidth 1000 according to an embodiment of the present disclosure is shown. Figure 10 The embodiment of the CWS bandwidth 1000 shown is for illustration only. Figure 10 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0148] As Figure 10 As shown, the PDSCH of the TB spans from CWS BW0 to CWS BW3, and there are 6 CBGs in the TB, where each CBG consists of one CB. Since each CBG spans CWS BW0, CWS BW1, CWS BW2, and CWS BW3, the CWS adjustment decisions for CWS BW0, CWS BW1, CWS BW2, and CWS BW3 may depend on the HARQ-ACK feedback bits for each CBG / CB (i.e., HARQ-ACK for CB0, CB1, CB2, CB3, CB4, and CB5).

[0149] Figure 11 Another example CWS bandwidth 1100 according to an embodiment of the present disclosure is shown. Figure 11 The illustrated embodiment of the CWS bandwidth 1100 is for illustrative purposes only. Figure 11 One or more of the illustrated components may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0150] As Figure 11 As shown, the PDSCH of the TB spans from CWS BW0 to CWS BW3, and there are 8 CBGs in the TB, where each CBG consists of one CB. The CWS adjustment decision for CWS BW0 and CWS BW1 may depend on the HARQ-ACK feedback bits corresponding to CGB0 (i.e., CB0), CGB2 (i.e., CB2), CGB4 (i.e., CB4), CGB6 (i.e., CB6); and the CWS adjustment decision for CWS BW2 and CWS BW3 may depend on the HARQ-ACK feedback bits corresponding to CGB1 (i.e., CB1), CGB3 (i.e., CB3), CGB5 (i.e., CB5), CGB7 (i.e., CB7).

[0151] In one embodiment, if the PDSCH / PUSCH is completely contained in the CWS BW in the frequency domain, the HARQ-ACK feedback of the PDSCH / PUSCH may be used to adjust the CWS corresponding to the CWS BW.

[0152] In one example, under this method, the HARQ-ACK feedback of the PDSCH / PUSCH that partially overlaps (but is not completely contained in) the CWS BW in the reference T / F resource may not be used for CWS adjustment.

[0153] In one embodiment, when using CBG-based HARQ-ACK feedback, if the CBG is completely contained in the CWS BW in the frequency domain, the HARQ-ACK feedback corresponding to the CBG of the PDSCH / PUSCH may be used when adjusting the CWS corresponding to the CWS BW.

[0154] In one example, under this method, the HARQ-ACK feedback of the CBG (of the PDSCH / PUSCH in the reference T / F resource) that partially overlaps (but is not completely contained in) the CWS BW may not be used for CWS adjustment.

[0155] In one example, if the fraction of the bandwidth where PDSCH / PUSCH overlaps with the CWS BW is at least a threshold η (0 <= η <= 1) of the bandwidth of the CWS BW, then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback of PDSCH / PUSCH can be utilized.

[0156] In one example, if the fraction of the bandwidth where PDSCH / PUSCH overlaps with the CWS BW is lower than the threshold η (0 <= η <= 1) of the bandwidth of the CWS BW, then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback of PDSCH / PUSCH may not be utilized.

[0157] In one example, regardless of whether the HARQ-ACK feedback is TB-based or CBG-based, the foregoing examples and / or embodiments can be applied.

[0158] In one example, the foregoing examples and / or embodiments can be applied only when the HARQ-ACK feedback is TB-based.

[0159] In one example, the foregoing examples and / or embodiments can be applied only when the HARQ-ACK feedback is CBG-based.

[0160] In one example, the bandwidth of PDSCH / PUSCH refers to the bandwidth of the TB corresponding to PDSCH / PUSCH.

[0161] In one example, the threshold η can be one of those fixed in the specification, configured by a higher layer parameter, or dynamically configured by DCI.

[0162] In the description of the foregoing embodiments and / or examples, for Figure 9 the example in, if η = 50%, then the decision on CWS adjustment for CWS BW0 can depend on the HARQ-ACK feedback corresponding to PDSCH1; the decision on CWS adjustment for CWS BW1 can depend on the HARQ-ACK feedback corresponding only to PDSCH2 (excluding PDSCH1); the decision on CWS adjustment for CWS BW2 can depend on the HARQ-ACK feedback corresponding only to PDSCH3 (excluding PDSCH2); and the decision on CWS adjustment for CWS BW3 can depend on the HARQ-ACK feedback corresponding to PDSCH3.

[0163] In one embodiment, when using CBG-based HARQ-ACK feedback, if the proportion of the bandwidth of the CBG overlapping with the CWS BW in the bandwidth of the CWS BW is at least the threshold η (0 <= η <= 1), then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback corresponding to the CBG of the PDSCH / PUSCH can be utilized.

[0164] In one example, if the proportion of the bandwidth of the CBG overlapping with the CWS BW in the bandwidth of the CWS BW is lower than the threshold η (0 <= η <= 1), then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback corresponding to the CBG of the PDSCH / PUSCH may not be utilized.

[0165] In one example, the threshold η can be one of those fixed in the specification, or configured by a higher layer parameter, or dynamically configured by DCI.

[0166] In the description of the foregoing embodiments and / or examples, in Figure 10 the example, the PDSCH of the TB spans from CWS BW0 to CWS BW3, and there are 6 CBGs in the TB, where each CBG consists of one CB. If the threshold η = 50%, then the decision on the CWS adjustment for CWS BW0 can depend on the HARQ-ACK feedback bits for each CBG / CB #0, #1, #2, #3, and #5; the decision on the CWS adjustment for CWS BW1 can depend on the HARQ-ACK feedback bits for each CBG / CB #0, #1, #2, #4, and #5; the decision on the CWS adjustment for CWS BW2 can depend on the HARQ-ACK feedback bits for each CBG / CB #0, #2, #3, #4, and #5; the decision on the CWS adjustment for CWS BW3 can depend on the HARQ-ACK feedback bits for each CBG / CB #1, #2, #3, #4, and #5.

[0167] In one embodiment, if the proportion of the bandwidth of the PDSCH / PUSCH overlapping with the CWS BW in the bandwidth of the PDSCH / PUSCH is at least the threshold η (0 <= η <= 1), then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback of the PDSCH / PUSCH can be utilized.

[0168] In one embodiment, if the proportion of the bandwidth of the CBG overlapping with the CWS BW in the bandwidth of the CBG is at least the threshold η (0 <= η <= 1), then when adjusting the CWS corresponding to the CWS BW, the HARQ-ACK feedback corresponding to the CBG of the PDSCH / PUSCH can be utilized.

[0169] In one embodiment, for CWS BW, as the ratio of the bandwidth of the TB or CBG of the PDSCH / PUSCH overlapping with the CWS BW to the bandwidth of the CWS BW increases, when adjusting the CWS for the CWS BW, the ACK / NACK bits of the TB or CBG corresponding to the PDSCH / PUSCH transmission of the reference T / F domain resource, which can be used for making the CWS adjustment decision for the current CWS BW, can have a higher weight.

[0170] In one example, the CWS adjustment rule for the CWS BW can be based on the weighted average ratio of the ACK / NACK bits that can be used to adjust the CWS, such that if the weighted average ratio is lower (or higher) than a given threshold, the CWS is reset to the minimum value, and if the ratio is higher (or lower) than the threshold, the CWS is increased to the next allowed value.

[0171] In one example, the weight of the ACK / NACK bits of the TB or CBG corresponding to the PDSCH / PUSCH transmission of the reference T / F domain resource, which can be used for making the CWS adjustment decision for the current CWS BW, can be BW overlap / BW CWS where BW overlap is the BW where the TB or CBG overlaps (i.e., intersects) with the current CWS BW, and BW CWS is the CWS BW.

[0172] Figure 12 FIG. shows an example CWS bandwidth and PDSCH 1200 according to an embodiment of the present disclosure. Figure 12 The embodiment of the CWS bandwidth and PDSCH 1200 shown is for illustration only. Figure 12 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0173] As Figure 12 shown, if the HARQ-ACK feedback of PDSCH1 is ACK, the HARQ-ACK feedback of PDSCH2 is NACK, and and Then, the weighted average ratio of NACK bits corresponding to CWS BW1 is 10%×0 (ACK) + 90%×1 (NACK) = 90%. If the threshold is the same as that of LTE-LAA, which is 80%, the CWS corresponding to CWS BW1 can be increased to the next allowed value. In contrast, if equal weights are used similar to LTE-LAA, the ratio of NACK bits is 50%, and the CWS of CWS BW1 may be reset to the minimum value, which cannot accurately reflect the collision condition on CWS BW1 because 90% of CWS BW1 is negatively acknowledged (NACK).

[0174] In one embodiment, for CWS BW, as the ratio of the bandwidth of the TB or CBG of the PDSCH / PUSCH overlapping with CWS BW to the bandwidth of the TB or CBG increases, when adjusting the CWS for CWS BW, the ACK / NACK bits of the TB or CBG corresponding to the PDSCH / PUSCH transmission of the reference T / F domain resources, which can be used for making CWS adjustment decisions for the current CWS BW, can have higher weights.

[0175] In one embodiment, an enhancement of the CWS adjustment rule through BWP switching is provided.

[0176] In NR, each UE can be configured with up to 4 DL BWPs and up to 4 UL BWPs, where a single active DL BWP and a single active UL BWP are configured each time. The active DL / UL BWP can be switched over time, such as through dynamic BWP switching via DCI or semi-static BWP switching via RRC.

[0177] In one embodiment, at a given time, an NR-U UE can support a single active DL / UL BWP, and the active DL / UL BWP can be switched to another DL / UL BWP configured for the NR-U UE.

[0178] In one example, for NR-U, it can support all or a subset of the methods for active BWP switching according to Rel-15 NR, where the BWP switching methods include semi-static switching via higher layer parameters, semi-persistent switching via MAC CE, or dynamic switching via DCI.

[0179] In NR-U, when an active UL / DL BWP needs to be switched, for transmission on the new active UL / DL BWP, the UE / gNB needs to first determine the CWS corresponding to the new active UL / DL BWP. Based on this, the UE / gNB can generate a random backoff counter for the CAT-4 LBT process. However, as Figure 13As shown, the new active UL / DL BWP and the previous active UL / DL BWP can share different frequency resources.

[0180] Figure 13 Fig. 1300 shows an example active BWP switch according to an embodiment of the present disclosure. Figure 13 The embodiment of the active BWP switch 1300 shown is for illustrative purposes only. Figure 13 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0181] In one embodiment, regarding the relationship between the frequency domain resources of the new active BWP and the previous active BWP when switching BWP, the following situations are possible.

[0182] In an example of Case 1, the frequency domain resources of the new active BWP completely contain the frequency domain resources of the previous active BWP. In Figure 13 the example, Case 1 occurs when the active BWP switches from BWP0 to BWP1.

[0183] In an example of Case 2, the frequency domain resources of the new active BWP are completely contained in the frequency domain resources of the previous active BWP. In Figure 13 the example, Case 2 occurs when the active BWP switches from BWP1 to BWP0.

[0184] In an example of Case 3, the frequency domain resources of the new active BWP and the previous active BWP partially overlap, and after excluding the common frequency resources shared by the two BWPs, both the new active BWP and the previous active BWP have non-empty frequency resources. In Figure 13 the example, Case 3 occurs when the active BWP switches from BWP0 to BWP2.

[0185] In an example of Case 4, the frequency domain resources of the new active BWP and the previous active BWP do not share any overlapping frequency domain resources. In Figure 13 the example, Case 4 occurs when the active BWP switches from BWP2 to BWP3.

[0186] When the UE is configured to switch to a new active UL BWP and before the first transmission on the new active UL BWP, the UE needs to determine the CWS. However, since the most recent UE transmission was on the previous active UL BWP, an important design consideration is how to determine the CWS for the first transmission on the new active UL BWP, or equivalently the CWS adjustment rule when BWP switching occurs.

[0187] In one embodiment, after the active BWP switches from the previous active BWP to the new active BWP, the CWS for the new active BWP can be determined based on all or a subset of the HARQ-ACK feedback corresponding to the transmission on the most recent reference T / F resource of the previous active BWP.

[0188] In one example, the foregoing example and / or embodiment can be applied to all or only a subset of the configuration of the CWS bandwidth (i.e., the frequency domain granularity where a single CWS is maintained for NR-U broadband operation), where according to the foregoing embodiment, the CWS bandwidth can be configured as one of the LBT bandwidth, the carrier bandwidth, the BWP, or a set of LBT bandwidths.

[0189] In a sub-example, this method can be applied when the CWS bandwidth is the carrier bandwidth, such that the HARQ-ACK feedback corresponding to the transmission on the most recent reference T / F resource of the previous active BWP can be used to adjust the CWS that is maintained as a single CWS across the entire carrier bandwidth.

[0190] In one example, the foregoing embodiment and / or example can be applied to all or only a subset of cases 1, 2, 3, and 4 regarding the relationship between the new active BWP and the previous active BWP as defined in the foregoing embodiment and / or example.

[0191] In one embodiment, the above embodiment and / or example can be applied when the HARQ-ACK feedback for the last transmission on the reference T / F resource of the previous active BWP is based on TB or based on CBG, based only on TB, and based only on CBG.

[0192] In one embodiment, the above embodiment and / or example can be applied under all or only a subset of the combination of the following factors, including the CWS bandwidth configuration, the frequency relationship between the new active BWP and the previous active BWP (i.e., cases 1 to 4), and whether the HARQ-ACK feedback for the last transmission on the reference T / F resource of the previous active BWP is based on TB or based on CBG.

[0193] In a sub - example, this method can be applied to Case 2 and the case where the CWS bandwidth is configured as the carrier bandwidth or BWP. For example, when the CWS bandwidth is a BWP, the HARQ - ACK feedback corresponding to the transmission on the nearest reference T / F resource of the previous active BWP can be used to determine the CWS corresponding to the previous active BWP (which includes the new active BWP in Case 2). Therefore, it is reasonable to apply this method in this scenario. Figure 14 An illustration of this example is provided.

[0194] Figure 14 An example CWS 1400 for BWP according to an embodiment of the present disclosure is shown. Figure 14 The embodiment of the CWS 1400 for BWP shown is for illustration only. Figure 14 One or more of the components shown can be implemented in a dedicated circuit configured to perform the function, or one or more of the components can be implemented by one or more processors executing instructions to perform the function. Other embodiments are used without departing from the scope of the present disclosure.

[0195] In another sub - example, when CBG - based HARQ - ACK feedback is used for the last reference T / F resource of the previous active BWP, the foregoing embodiments and / or examples can be applied, such that the CWS for the first transmission on the new active BWP can be determined based on the CBG - based HARQ - ACK feedback on the last reference T / F resource of the CWS bandwidth of the previous active BWP, where such a CBG shares overlapping frequency resources with the new active BWP.

[0196] Figure 15 An example BWP and CBG 1500 according to an embodiment of the present disclosure is shown. Figure 15 The embodiment of the BWP and CBG 1500 shown is for illustration only. Figure 15 One or more of the components shown can be implemented in a dedicated circuit configured to perform the function, or one or more of the components can be implemented by one or more processors executing instructions to perform the function. Other embodiments are used without departing from the scope of the present disclosure.

[0197] In Figure 15 an illustration of this sub - example is provided, where the CWS for the initial transmission on BWP0 can be determined based on the HARQ - ACK feedback corresponding to CBG1 and CBG2 of the last reference T / F resource of BWP1.

[0198] In an embodiment, when the previous active BWP and the new active BWP share the same frequency resources, the foregoing embodiments and / or examples can be applied.

[0199] In one embodiment, after an active BWP switches from a previous active BWP to a new active BWP, a CWS for the new active BWP can be determined based on all or a subset of HARQ-ACK feedback corresponding to transmissions on the most recent reference T / F resource of the current active BWP.

[0200] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of the configuration of the CWS bandwidth (i.e., the frequency domain granularity where a single CWS is maintained for NR-U broadband operation), wherein, according to the foregoing embodiments, the CWS bandwidth can be configured as one of the LBT bandwidth, the carrier bandwidth, the BWP, or a set of LBT bandwidths.

[0201] In one sub-example, this method can be applied regardless of the CWS bandwidth configuration.

[0202] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of cases 1, 2, 3, and 4 regarding the frequency relationship between the new active BWP and the previous active BWP as defined in the foregoing embodiments and / or examples.

[0203] In one sub-example, this method can be applied regardless of the frequency relationship between the new active BWP and the previous active BWP.

[0204] In one example, the foregoing embodiments and / or examples can be applied under all or only a subset of a combination of factors including the CWS bandwidth configuration and the frequency relationship between the new active BWP and the previous active BWP (i.e., cases 1 to 4).

[0205] In one example, if the time gap between the most recent / latest reference T / F resource of the current active BWP and the expected start of the initial transmission on the current active BWP (after the previous active BWP switches to the current active BWP) is within a threshold, this method can be applied; otherwise, one of the other methods of the embodiment can be applied.

[0206] Figure 16 An example BWP 1600 according to an embodiment of the present disclosure is shown. Figure 16 The embodiment of the shown BWP 1600 is for illustration only. Figure 16 One or more of the shown components can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0207] Figure 16Illustrations of the foregoing embodiments and / or examples are provided, where after the active BWP switches from BWP1 to BWP0, the CWS for the initial transmission on BWP0 can be based on the HARQ-ACK feedback of the last reference T / F resource on BWP0.

[0208] In one embodiment, after the active BWP switches from a previous active BWP to a new active BWP, the CWS for the LBT BW on the new active BWP can be determined based on all or a subset of the HARQ-ACK feedback corresponding to the transmission on the nearest reference T / F resource of that LBT BW.

[0209] In one example, when the CWS bandwidth (i.e., the frequency domain granularity where a single CWS is maintained for NR-U broadband operation) is configured as the LBT bandwidth, the foregoing embodiments and / or examples can be applied.

[0210] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of cases 1, 2, 3, and 4 regarding the relationship between the new active BWP and the previous active BWP defined in the foregoing embodiments and / or examples.

[0211] In one example, when the HARQ-ACK feedback for the last transmission on the reference T / F resource on the previous active BWP is based on a TB or based on a CBG, based only on a TB, or based only on a CBG, the foregoing embodiments and / or examples can be applied.

[0212] In one example, the foregoing embodiments and / or examples can be applied under all or only a subset of a combination of factors, the factors including the frequency relationship between the new active BWP and the previous active BWP (i.e., cases 1 to 4) and whether the HARQ-ACK feedback for the last transmission on the reference T / F resource on the previous active BWP is based on a TB or based on a CBG.

[0213] Figure 17 An example BWP and CBG 1700 according to an embodiment of the present disclosure is shown. Figure 17 The embodiments of the shown BWP and CBG 1700 are for illustration only. Figure 17 One or more of the shown components can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0214] As Figure 17As shown, the CWS for the initial transmission on LBT BW1 for BWP0 can be determined based on the HARQ-ACK feedback corresponding to CBG1 of the last reference T / F resource of BWP1; while the CWS for the initial transmission on LBT BW2 for BWP0 can be determined based on the HARQ-ACK feedback corresponding to CBG2 of the last reference T / F resource of BWP1.

[0215] In one embodiment, after the active BWP switches from a previous active BWP to a new active BWP, the CWS for the new active BWP can be determined as the default CWS value corresponding to the corresponding channel access priority level of the expected transmission on the new active BWP.

[0216] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of the configuration of the CWS bandwidth (i.e., the frequency domain granularity for maintaining a single CWS for NR-U broadband operation), wherein, according to the foregoing embodiments, the CWS bandwidth can be configured as one of the LBT bandwidth, the carrier bandwidth, the BWP, or a set of LBT bandwidths.

[0217] In one sub-example, this method can be applied regardless of the CWS bandwidth configuration.

[0218] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of cases 1, 2, 3, and 4 regarding the frequency relationship between the new active BWP and the previous active BWP defined in the foregoing embodiments and / or examples.

[0219] In one sub-example, this method can be applied regardless of the frequency relationship between the new active BWP and the previous active BWP.

[0220] In one example, the above embodiments and / or examples can be applied when the HARQ-ACK feedback for the last transmission on the reference T / F resource on the previous active BWP is based on TB or based on CBG, only based on TB, and only based on CBG.

[0221] In one example, the default CWS value corresponding to the channel access priority level of the expected transmission on the new active BWP can be the minimum contention window size corresponding to the channel access priority level.

[0222] In one example, the default CWS value corresponding to the channel access priority level of the expected transmission on the new active BWP can be selected from one of the allowed contention window sizes corresponding to the channel access priority level.

[0223] In one embodiment, after the active UL / DL BWP switches from a previous active UL / DL BWP to a new active BWP, if the initial transmission on the new active UL / DL BWP overlaps with the frequency resources of the DL / UL COT initiated by the gNB / UE, the initial transmission on the new active UL / DL BWP can be transmitted on the frequency resources that overlap with the frequency resources of the DL / UL COT initiated by the gNB / UE after a successful CAT-2 LBT.

[0224] In one example, the foregoing embodiments and / or examples can be applied to all or only a subset of the configuration of the CWS bandwidth (i.e., the frequency domain granularity where a single CWS is maintained for NR-U broadband operation), where, according to the foregoing embodiments, the CWS bandwidth can be configured as one of the LBT bandwidth, carrier bandwidth, BWP, or set of LBT bandwidths.

[0225] In one example, when the frequency domain granularity of the LBT process is smaller than the frequency resources that overlap between the new active UL / DL BWP and the frequency resources that overlap with the frequency resources of the DL / UL COT initiated by the gNB / UE, multiple CAT-2 LBT processes can be performed in parallel.

[0226] Figure 18 A diagram of this method is provided, where the UE switches from UL BWP0 to UL BWP1, and UL BWP1 is within the gNB COT. Thus, if either of the two parallel CAT-2 LBTs performed on the LBT BW has elapsed, the UE can initiate a transmission on UL BWP1.

[0227] Figure 18 An example UL BWP 1800 in the carrier BW according to an embodiment of the present disclosure is shown. Figure 18 The embodiment of the UL BWP 1800 in the shown carrier BW is for illustration only. Figure 18 One or more of the shown components can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0228] In one embodiment, after the active BWP switches from a previous active BWP to a new active BWP, the foregoing embodiments and / or examples can be used to determine the CWS for the new active BWP, where the selected method can depend on the frequency resources that overlap between the previous active BWP and the new active BWP.

[0229] In one example, if the ratio of the bandwidth of the overlapping frequency resources between the previous active BWP and the new active BWP to the bandwidth of the previous active BWP is higher than a threshold, one of the foregoing embodiments and / or examples may be applied.

[0230] In one example, if the ratio of the bandwidth of the overlapping frequency resources between the previous active BWP and the new active BWP to the bandwidth of the new active BWP is higher than a threshold, the foregoing embodiments and / or examples may be applied.

[0231] In one embodiment, an enhancement to the UL CWS adjustment rule through PUSCH frequency resource switching is provided.

[0232] In NR-U, PUSCH transmission may be based on an interleaved structure to meet the occupied channel bandwidth (OCB) requirements, where the PUSCH may occupy at least 80% of the nominal channel bandwidth of the unlicensed band. Additionally, to support broadband operation in NR-U, the PUSCH frequency resource allocation for NR-U UEs may also support scheduling the PUSCH across different LBT bandwidths (or nominal channel bandwidths), where such LBT bandwidths must either be continuous in the frequency domain or may be continuous or discontinuous in the frequency domain (e.g., Figure 9 PUSCH 3 and PUSCH 4 in

[0233] In one embodiment, since the scheduled PUSCH resources are configured through UL grants, the frequency-domain resource relationship between the newly scheduled PUSCH of the NR-U UE and the previously scheduled PUSCH of the UE may be one of the following cases.

[0234] Figure 19 FIG. 1900 shows an example PUSCH in the carrier BW according to an embodiment of the present disclosure. Figure 19 The embodiment of PUSCH 1900 in the shown carrier BW is for illustration only. Figure 19 One or more of the shown components may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0235] In one example of Case 1, the frequency-domain resources of the newly scheduled PUSCH completely contain the frequency-domain resources of the previously scheduled PUSCH. As Figure 19 shown, Case 1 occurs when the scheduled PUSCH changes from PUSCH 0 to PUSCH 1.

[0236] In an example of Case 2, the frequency-domain resources of the newly scheduled PUSCH are completely included in the frequency-domain resources of the previously scheduled PUSCH. In Figure 19 the example of

[0237] Case 2 occurs when the scheduled PUSCH changes from PUSCH 1 to PUSCH 2. In an example of Case 3, the frequency-domain resources of the newly scheduled PUSCH partially overlap with the frequency-domain resources of the previously scheduled PUSCH, and after excluding the common frequency resources shared by the two PUSCHs, both the newly scheduled PUSCH and the previously scheduled PUSCH have non-empty frequency resources. As Figure 19 shown, Case 3 occurs when the scheduled PUSCH changes from PUSCH 2 to PUSCH 3.

[0238] In an example of Case 4, the frequency-domain resources of the newly scheduled PUSCH and the previously scheduled PUSCH do not share any overlapping frequency-domain resources. As Figure 19 shown, Case 4 occurs when the scheduled PUSCH changes from PUSCH 3 to PUSCH4.

[0239] In an example, Cases 1 to 4 can be applied when the newly scheduled PUSCH and the previously scheduled PUSCH are in the same active UL BWP.

[0240] In an example, Cases 1 to 4 can be applied when the newly scheduled PUSCH and the previously scheduled PUSCH are in different active UL bandwidths (i.e., BWP switching occurs).

[0241] When the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the newly scheduled PUSCH at the UE needs to be transmitted according to CAT-4 LBT, an important design consideration is how to determine the CWS corresponding to CAT-4 LBT to initiate a UE UL burst to transmit the newly scheduled PUSCH.

[0242] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the UE needs to perform a CAT-4 LBT process to initiate a new UL burst to transmit the newly scheduled PUSCH, the CWS for CAT-4 LBT can be determined based on all or a subset of the HARQ-ACK feedback corresponding to the transmission on the nearest reference T / F resource for the previous UE UL transmission.

[0243] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the UE needs to perform the CAT-4 LBT procedure to initiate a new UL burst for transmitting the newly scheduled PUSCH, the CWS for CAT-4 LBT can be determined based on all or a subset of the HARQ-ACK feedback corresponding to the transmission on the nearest reference T / F resource of the active UL BWP (on which the newly scheduled PUSCH is scheduled).

[0244] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the UE needs to perform the CAT-4 LBT procedure to initiate a new UL burst for transmitting the newly scheduled PUSCH, then for the LBT BW containing the newly scheduled PUSCH, the CWS for CAT-4 LBT on this LBT BW can be determined based on all or a subset of the HARQ-ACK feedback corresponding to the transmission on the nearest reference T / F resource of this LBT BW.

[0245] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the UE needs to perform the CAT-4 LBT procedure to initiate a new UL burst for transmitting the newly scheduled PUSCH, the CWS for the newly scheduled PUSCH can be determined as the default CWS value corresponding to the corresponding channel access priority level of the newly scheduled PUSCH.

[0246] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and if the newly scheduled PUSCH overlaps with the frequency resources of the DL COT initiated by the gNB, the newly scheduled PUSCH can be transmitted on the frequency resources overlapping with the frequency resources of the DL COT initiated by the gNB after successful CAT-2 LBT.

[0247] In one embodiment, when the newly scheduled PUSCH shares different frequency resources from the previously scheduled PUSCH and the UE needs to perform the CAT-4 LBT procedure to initiate a new UL burst for transmitting the newly scheduled PUSCH, the CWS for the newly scheduled PUSCH can be determined using the foregoing embodiments and / or examples, where the selected method can depend on the overlapping frequency resources between the newly scheduled PUSCH and the previously scheduled PUSCH.

[0248] The configured grant uplink control information (CG-UCI) includes at least the following information: HARQ process number, new data indicator (NDI), redundancy version (RV), and channel occupancy time (COT) sharing information in the case of operating using shared spectrum channel access. The CG-UCI can be included in each configured grant (CG)-PUSCH transmission.

[0249] For example, the CG-UCI is mapped to the symbols starting after the first DM-RS symbol of the CG-PUSCH transmission. For example, among UCI types, the CG-UCI can have the highest priority for multiplexing in the CG-PUSCH transmission.

[0250] Since it is necessary to multiplex the CG-UCI with the highest priority in the CG-PUSCH transmission, the present disclosure contemplates enhancements for supporting UCI multiplexing of CG-UCI, HARQ-ACK, and channel state information (CSI) on the CG-PUSCH transmission, including relative prioritization of multiplexing of CG-UCI, HARQ-ACK, CSI on the CG-PUSCH, and the corresponding channels that can be used to transmit CG-UCI, HARQ-ACK, and CSI, power prioritization of various channels that a power-constrained UE may have to transmit simultaneously, and selection of the PUSCH for UCI multiplexing, etc.

[0251] The present disclosure includes several embodiments, principles, methods, and examples, which can be combined or used in combination with each other, or can operate independently. The embodiments / principles / methods / examples in the present disclosure can be applied to contention-free transmission on licensed spectrum, applied to transmission of frame-based devices (FBE) using shared spectrum channel access (such as NR-U), applied to transmission of load-based devices (LBE) using shared spectrum channel access, or applied to transmission of both FBE and LBE using shared spectrum channel access.

[0252] In the present disclosure, FR1 refers to operation in an unlicensed / shared / licensed frequency band in FR1 (such as the 5 GHz band or the 6 GHz unlicensed / shared band); and FR2 refers to operation in an unlicensed / shared / licensed frequency band in FR2 (such as the 60 GHz band).

[0253] In one embodiment, multiplexing of CG-UCI, HARQ-ACK, type I subband CSI part 1 and part 2 is provided.

[0254] This embodiment includes the principles, methods, and examples of multiplexing regarding CG-UCI, HARQ-ACK, Type I subband CSI part 1, and Type I subband CSI part 2. In Rel-15 NR, both Type I subband CSI part 1 and part 2 are multiplexed on PUCCH transmissions or PUSCH transmissions on the cells of a cell group (e.g., the primary cell for PUCCH transmissions). When multiplexing CSI reports on PUSCH transmissions, CSI part 2 can be omitted or discarded according to the transmission priority level of CSI part 2 and the number of coded modulation symbols per layer.

[0255] In one embodiment, from the highest priority to the lowest priority, the relative priority order of multiplexing CG-UCI, HARQ-ACK, Type I subband CSI part 1, and part 2 on CG-PUSCH transmissions is: first is CG-UCI, then HARQ-ACK, then Type I subband CSI part 1, and finally Type I subband CSI part 2. Hereinafter, any UCI type other than CG-UCI is referred to as UCI.

[0256] In one example, according to the priority order in the foregoing embodiment, the UE allocates a certain number of coded modulation symbols per layer for each of CG-UCI, HARQ-ACK, Type 1 subband CSI part 1, and part 2 on CG-PUSCH.

[0257] Figure 20 A flowchart of a method 2000 for multiplexing according to an embodiment of the present disclosure is shown. This method can be executed by a UE (e.g., 111-116 as shown in Figure 1 ). Figure 20 The embodiment of the method 2000 shown is for illustrative purposes only. Figure 20 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0258] In one example, when there are not enough resources (resource elements in CG-PUSCH - e.g., as described in REF 2) after allocating coded modulation symbols for a higher-priority UCI on CG-PUSCH, the UE can discard the UCI. This example is shown in Figure 20 2003, 2006, and 2009 of

[0259] In one example, when there are not enough resources on the CG-PUSCH after encoding modulation symbols are allocated for GC-UCI on the CG-PUSCH or other UCI types with higher priority, the UE may multiplex the UCI type on a PUSCH transmission (instead of a CG-PUSCH transmission). This example is shown in Figure 20 2003, 2006, and 2009 of

[0260] In one example, when there are not enough resources on the CG-PUSCH transmission after encoding modulation symbols are allocated for GC-UCI on the CG-PUSCH or UCI types with even higher priority, the UE may multiplex the UCI on a PUCCH transmission. This example is shown in Figure 20 2003, 2006, and 2009 of

[0261] As Figure 20 shown, the method starts at step 2001. In step 2001, the UE multiplexes the CG-UCI on the CG-PUSCH. Subsequently, in step 2002, the UE determines whether there are enough resources on the CG-PUSCH for HARQ-ACK. In step 2002, if not enough, the UE executes step 2003. In step 2003, the UE discards the HARQ-ACK or multiplexes the HARQ-ACK on the PUSCH / PUCH. In step 2002, if enough, the UE executes step 2004. In step 2004, the UE multiplexes the HARQ-ACK on the CG-PUSCH. Subsequently, in step 2005, the UE determines whether there are enough resources on the CG-PUSCH for type 1 subband CSI part 1. In step 2005, if not enough, the UE executes step 2006. In step 2006, the UE discards type 1 subband CSI part 1 or multiplexes type 1 subband CSI part 1 on the PUSCH / PUCCH. In step 2005, if enough, then in step 2007, the UE multiplexes type 1 subband CSI part 1 on the CG-PUSCH. In step 2008, the UE determines whether there are enough resources on the CG-PUSCH for type 1 subband CSI part 2. In step 2008, if not enough, the UE executes step 2009. In step 2009, the UE discards all or part of type 1 subband CSI part 2, or multiplexes all or part of type 1 subband CSI part 2 on the PUSCH / PUCCH. In step 2008, if enough, the UE multiplexes type 1 subband CSI part 2 on the CG-PUSCH in step 2010.

[0262] In one example, for the channels that a UE can use to multiplex CG-UCI, HARQ-ACK, and Type I subband CSI parts 1 and 2, all or a subset of the scenarios in Table 1 can be supported. For a given scenario in Table 1 (i.e., a given row), each entry in Table 1 represents the channel on which the UE can multiplex the corresponding UCI.

[0263] In one example of Scenario 1, the UE can multiplex all of CG-UCI, HARQ-ACK, Type I subband CSI part 1, and Type I subband CSI part 2 on a CG-PUSCH transmission.

[0264] In one example of Scenario 2, according to the foregoing embodiments and / or examples, the UE can multiplex CG-UCI, HARQ-ACK, and Type I subband CSI part 1 on a CG-PUSCH transmission, while the UE can discard all or part of Type I subband CSI part 2 from the CG-PUSCH transmission.

[0265] In one example of Scenario 3, the UE can multiplex CG-UCI, HARQ-ACK, and Type I subband CSI part 1 on a CG-PUSCH transmission, and can multiplex all or part of Type I subband CSI part 2 on another PUSCH or PUCCH transmission.

[0266] In one example of Scenario 4, according to the foregoing examples and / or embodiments, the UE can multiplex CG-UCI and HARQ-ACK on a CG-PUSCH transmission, and can discard all of Type I subband CSI part 1 and Type I subband CSI part 2 from the CG-PUSCH transmission.

[0267] In one example of Scenario 5, the UE can multiplex CG-UCI and HARQ-ACK on a CG-PUSCH transmission, and multiplex all or part of Type I subband CSI part 1 and Type I subband CSI part 2 on another PUSCH transmission (different from the CG-PUSCH transmission).

[0268] In one example of Scenario 6, the UE can multiplex CG-UCI and HARQ-ACK on a CG-PUSCH transmission, and multiplex all or part of Type I subband CSI part 1 and Type I subband CSI part 2 on a PUCCH transmission.

[0269] In one example of Scenario 7, according to the foregoing embodiments and / or examples, the UE can multiplex CG-UCI on a CG-PUSCH transmission, and discard HARQ-ACK, Type I subband CSI part 1, and Type I subband CSI part 2 from the CG-PUSCH transmission.

[0270] In an example of Scenario 8, the UE may multiplex CG-UCI on CG-PUSCH transmission, multiplex HARQ-ACK on another PUSCH transmission (different from the CG-PUSCH transmission) or on PUCCH transmission, and multiplex all or part of Type I subband CSI Part 1 and Type I subband CSI Part 2 on another PUSCH transmission (different from the CG-PUSCH transmission).

[0271] In an example of Scenario 9, the UE may multiplex CG-UCI on CG-PUSCH transmission, multiplex HARQ-ACK on another PUSCH transmission (different from the CG-PUSCH transmission) or on PUCCH transmission, and multiplex all or part of Type I subband CSI Part 1 and Type I subband CSI Part 2 on PUCCH transmission.

[0272] [Table 1]

[0273]

[0274] In one embodiment, multiplexing of CG-UCI, HARQ-ACK, Type II subband CSI Part 1 and Part 2 is provided.

[0275] In one embodiment, methods and examples for multiplexing CG-UCI, HARQ-ACK, Type II subband CSI Part 1 and Type II subband CSI Part 2 are provided.

[0276] In the NR standard specification, the UE may multiplex Type II subband CSI Part 1 and Part 2 on PUCCH or PUSCH transmission, or may multiplex Type II subband CSI Part 1 on PUCCH transmission and may multiplex Type II subband CSI Part 2 on PUSCH transmission. When the CSI report is on PUSCH, the UE may omit / discard Part 2 CSI according to the priority for multiplexing of CSI Part 2 and the number of coded modulation symbols per layer.

[0277] In one embodiment, from the highest priority to the lowest priority, the relative priority order for the UE to multiplex CG-UCI, HARQ-ACK, Type II subband CSI Part 1 and Part 2 on CG-PUSCH transmission is: first CG-UCI, then HARQ-ACK, then Type II subband CSI Part 1, and finally Type II subband CSI Part 2.

[0278] In an example, according to the priority order in the foregoing embodiments and / or examples, the UE allocates a number of coded modulation symbols per layer for CG-UCI, HARQ-ACK, Type II subband CSI Part 1 and Part 2 on CG-PUSCH.

[0279] Figure 21 Another flowchart of method 2100 for multiplexing according to an embodiment of the present disclosure is shown. Figure 21 The embodiment of method 2100 shown is for illustration only. Figure 21 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0280] In one example, when there are not enough resources after encoding and modulation symbols are allocated for UCI with a higher priority on CG-PUSCH transmission, the UE discards / omits the UCI. This example can be provided in Figure 21 steps 2103, 2106, and 2109.

[0281] In one example, when there are not enough resources on CG-PUSCH after encoding and modulation symbols are allocated for UCI with a higher priority on CG-PUSCH, the UE may multiplex the UCI on another PUSCH transmission different from the CG-PUSCH transmission. This example can be provided in Figure 21 steps 2103, 2106, and 2109.

[0282] In one example, when there are not enough resources on CG-PUSCH transmission after encoding and modulation symbols are allocated for UCI with a higher priority on CG-PUSCH transmission, the UE may multiplex the UCI on PUCCH transmission. This example can be provided in Figure 21 steps 2103, 2106, and 2109.

[0283] As Figure 21As shown, method 2100 starts at step 2101. In step 2101, the UE multiplexes CG-UCI on the CG-PUSCH. Subsequently, in step 2102, the UE determines whether there are sufficient resources on the CG-PUSCH for HARQ-ACK. In step 2102, if not, the UE performs step 2103. In step 2103, the UE discards the HARQ-ACK or multiplexes the HARQ-ACK on the PUSCH / PUCCH. In step 2102, if sufficient, the UE performs step 2104. In step 2104, the UE multiplexes the HARQ-ACK on the CG-PUSCH. Subsequently, the UE determines in step 2105 whether there are sufficient resources on the CG-PUSCH for type 2 subband CSI part 1. In step 2105, if not, the UE performs step 2106. In step 2106, the UE discards type 2 subband CSI part 1 or multiplexes type 2 subband CSI part 1 on the PUSCH / PUCCH. In step 2105, if sufficient, the UE multiplexes type 2 subband CSI part 1 on the CG-PUSCH in step 2107. In step 2008, the UE determines whether there are sufficient resources on the CG-PUSCH for type 2 subband CSI part 2. In step 2108, if not, the UE performs step 2109. In step 2109, the UE discards all or part of type 2 subband CSI part 2 or multiplexes all or part of type 2 subband CSI part 2 on the PUSCH / PUCCH. In step 2108, if sufficient, the UE performs step 2110. In step 2110, the UE multiplexes type 2 subband CSI part 2 on the CG-PUSCH.

[0284] In one example, for the channels used by the UE to multiplex CG-UCI, HARQ-ACK, and type II subband CSI parts 1 and 2, all or a subset of the scenarios in Table 2 may be supported. For a given scenario in Table 2 (i.e., a given row), each entry in Table 2 represents the channel on which the UE multiplexes the corresponding UCI. Each scenario is as follows.

[0285] In one example of Scenario 1, the UE may multiplex all of CG-UCI, HARQ-ACK, type II subband CSI part 1, and type II subband CSI part 2 on the CG-PUSCH transmission.

[0286] In one example of Scenario 2, the UE may multiplex CG-UCI, HARQ-ACK, and type II subband CSI part 1 on the CG-PUSCH transmission. According to the foregoing embodiments and / or examples, the UE may discard all or part of type II subband CSI part 2 from the CG-PUSCH transmission.

[0287] In an example of Scenario 3, the UE may multiplex CG-UCI, HARQ-ACK, and Type II subband CSI part 1 on the CG-PUSCH transmission. The UE may multiplex all or part of Type II subband CSI part 2 on another PUSCH transmission (different from the CG-PUSCH transmission) or on the PUCCH transmission.

[0288] In an example of Scenario 4, the UE may multiplex CG-UCI and HARQ-ACK on the CG-PUSCH transmission. According to the foregoing embodiments and / or examples, the UE may discard all of Type II subband CSI part 1 and Type II subband CSI part 2 from the CG-PUSCH transmission.

[0289] In an example of Scenario 5, the UE may multiplex CG-UCI and HARQ-ACK on the CG-PUSCH transmission. The UE may multiplex Type II subband CSI part 1 and all or part of Type II subband CSI part 2 on another PUSCH transmission (different from the CG-PUSCH transmission).

[0290] In an example of Scenario 6, the UE may multiplex CG-UCI and HARQ-ACK on the CG-PUSCH transmission. The UE may multiplex Type II subband CSI part 1 and all or part of Type II subband CSI part 2 on the PUCCH transmission.

[0291] In an example of Scenario 7, the UE may multiplex CG-UCI and HARQ-ACK on the CG-PUSCH transmission. The UE may multiplex Type II subband CSI part 1 on the PUCCH transmission and may multiplex all or part of Type II subband CSI part 2 on another PUSCH transmission (different from the CG-PUSCH transmission).

[0292] In an example of Scenario 8, the UE may multiplex CG-UCI on the CG-PUSCH transmission. According to the foregoing embodiments and / or examples, the UE may discard HARQ-ACK, Type II subband CSI part 1, and Type II subband CSI part 2 from the CG-PUSCH transmission.

[0293] In an example of Scenario 9, the UE may multiplex CG-UCI on the CG-PUSCH transmission, while HARQ-ACK may be multiplexed on another PUSCH transmission (different from the CG-PUSCH transmission) or on the PUCCH transmission, and all or part of Type II subband CSI part 1 and Type II subband CSI part 2 may be multiplexed on another PUSCH transmission (different from the CG-PUSCH transmission).

[0294] In an example of Scenario 10, the UE may multiplex CG-UCI on a CG-PUSCH transmission. The UE may multiplex HARQ-ACK on another PUSCH transmission (different from the CG-PUSCH transmission) or on a PUCCH transmission, and may multiplex all or part of Type II subband CSI Part 1 and Type II subband CSI Part 2 on the PUCCH transmission.

[0295] In an example of Scenario 11, the UE may multiplex CG-UCI on a CG-PUSCH transmission. The UE may multiplex HARQ-ACK on another PUSCH transmission (different from the CG-PUSCH transmission) or on a PUCCH transmission, and multiplex Type II subband CSI Part 1 on the PUCCH transmission and multiplex all or part of Type II subband CSI Part 2 on another PUSCH transmission (different from the CG-PUSCH transmission).

[0296]

Table 2

[0297] Scenario and Signal

[0298]

[0299]

[0300] In one embodiment, multiplexing of CG-UCI, HARQ-ACK, and wideband CSI is provided. This embodiment includes the principles, methods, and examples of the UE multiplexing CG-UCI, HARQ-ACK, and wideband CSI in PUSCH or PUCCH transmissions. In Rel-15 NR, wideband CSI is multiplexed in PUCCH transmissions.

[0301] In one embodiment, from the highest priority to the lowest priority, the relative priority order of multiplexing CG-UCI, HARQ-ACK, and wideband CSI is: first CG-UCI, then HARQ-ACK, and finally wideband CSI.

[0302] In an example, according to Figure 22 the shown priority order, the UE allocates a number of per-layer coded modulation symbols for CG-UCI, HARQ-ACK, and wideband CSI on the CG-PUSCH transmission.

[0303] Figure 22 Another flowchart of method 2200 for multiplexing according to an embodiment of the present disclosure is shown. Figure 22 The embodiment of method 2200 shown is for illustration only. Figure 22One or more of the components shown may be implemented in dedicated circuitry configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0304] In one example, as shown in Figure 22 steps 2203 and 2206 of, when there are not enough resources after encoding modulation symbols are allocated for UCI with higher priority on CG-PUSCH transmission, the UE discards / omits the UCI.

[0305] In one example, when there are not enough resources on CG-PUSCH transmission after encoding modulation symbols are allocated for UCI with higher priority on CG-PUSCH transmission, the UE multiplexes the UCI on a PUSCH transmission different from the CG-PUSCH transmission. Figure 22 This example is shown.

[0306] As Figure 22 shown, method 2200 begins at step 2201. In step 2201, the UE multiplexes CG-UCI on CG-PUSCH. Subsequently, in step 2202, the UE determines whether there are enough resources on CG-PUSCH for HARQ-ACK. In step 2202, if not enough, the UE performs step 2203. In step 2203, the UE discards HARQ-ACK or multiplexes HARQ-ACK on PUSCH / PUCCH. In step 2202, if enough, the UE performs step 2204. In step 2104, the UE multiplexes HARQ-ACK on CG-PUSCH. Subsequently, in step 2205, the UE determines whether there are enough resources on CG-PSCH for wideband CSI. In step 2205, if not enough, the UE performs step 2206. In step 2206, the UE discards wideband CSI or multiplexes wideband CSI on PUSCH / PUCCH. In step 2205, if enough, the UE multiplexes wideband CSI on CG-PUSCH in step 2207.

[0307] In one example, when there are not enough resources on CG-PUSCH transmission after encoding modulation symbols are allocated for UCI with higher priority on CG-PUSCH transmission, the UE multiplexes the UCI on PUCCH transmission. Figure 22 This example is shown.

[0308] In one example, for a channel on which a UE can multiplex CG-UCI, HARQ-ACK, and wideband CSI, all or a subset of the scenarios in Table 3 can be supported. For a given scenario in Table 3 (i.e., a given row), each entry in Table 3 represents a channel on which the UE can multiplex the corresponding UCI. Each scenario is as follows.

[0309] In one example of Scenario 1, the UE multiplexes all of CG-UCI, HARQ-ACK, and wideband CSI on a CG-PUSCH transmission.

[0310] In one example of Scenario 2, the UE multiplexes CG-UCI and HARQ-ACK on a CG-PUSCH transmission and multiplexes wideband CSI on a PUCCH transmission.

[0311] In one example of Scenario 3, the UE multiplexes CG-UCI and HARQ-ACK on a CG-PUSCH transmission and multiplexes wideband CSI on another PUSCH transmission (different from the CG-PUSCH transmission).

[0312] In one example of Scenario 4, the UE multiplexes CG-UCI and HARQ-ACK on a CG-PUSCH transmission and discards wideband CSI.

[0313] In one example of Scenario 5, the UE multiplexes CG-UCI on a CG-PUSCH transmission and multiplexes HARQ-ACK and wideband CSI on a PUCCH transmission.

[0314] In one example of Scenario 6, the UE multiplexes CG-UCI on a CG-PUSCH transmission, multiplexes HARQ-ACK on another PUSCH transmission (different from the CG-PUSCH transmission), and multiplexes wideband CSI on a PUCCH transmission.

[0315] In an example of Scenario 7, the UE multiplexes CG-UCI on a CG-PUSCH transmission and multiplexes HARQ-ACK and wideband CSI on another PUSCH transmission (different from the CG-PUSCH transmission).

[0316]

Table 3

[0317] Scenario and Signal

[0318]

[0319] In one embodiment, a UE procedure for reporting CG-UCI is provided.

[0320] In the NR standard specification, if a UE transmits multiple PUSCHs in a time slot on a corresponding serving cell (including a first PUSCH scheduled by a DCI format and a second PUSCH configured by corresponding higher layer parameters ConfiguredGrantConfig and semiPersistentOnPUSCH), and the UE multiplexes UCI in one of the multiple PUSCHs, and the multiple PUSCHs meet the conditions for UCI multiplexing in the NR specification, then the UE multiplexes the UCI in the PUSCH of the first PUSCH. However, this NR UCI multiplexing process does not directly apply to CG-UCI in CG-PUSCH transmission because CG-UCI has the highest priority in UCI multiplexing and is included in each CG-PUSCH transmission.

[0321] In one embodiment, if a UE transmits multiple PUSCHs in a time slot on a corresponding serving cell (including a first PUSCH scheduled by a DCI format and a second PUSCH configured by a corresponding ConfiguredGrantConfig), and the UE multiplexes UCI including CG-UCI in one of the multiple PUSCHs, and the multiple PUSCHs meet the conditions for UCI multiplexing (such as, for example, the conditions in the NR standard specification), then the UE multiplexes the UCI in the CG-PUSCH of the second PUSCH configured by ConfiguredGrantConfig; otherwise, the UE multiplexes the UCI in the PUSCH transmission scheduled by the DCI format (instead of the PUSCH transmission configured by higher layer signaling).

[0322] In one embodiment, if a UE transmits multiple PUSCHs in a time slot on a corresponding serving cell (including a first PUSCH scheduled by a DCI format and a second PUSCH configured by a corresponding ConfiguredGrantConfig), and the UE multiplexes UCI including CG-UCI in one of the multiple PUSCHs, and the multiple PUSCHs meet the conditions for UCI multiplexing, then the UE multiplexes CG-UCI in the CG-PUSCH of the second PUSCH configured by ConfiguredGrantConfig, and the UE multiplexes UCI other than CG-UCI in the PUSCH of the first PUSCH.

[0323] In one embodiment, if the UE transmits multiple PUSCHs (including the first PUSCH configured by the corresponding ConfiguredGrantConfig) in a time slot on the corresponding serving cell, and the UE will multiplex UCI including CG-UCI in one of the multiple PUSCHs, and the multiple PUSCHs meet the conditions for UCI multiplexing, then the UE multiplexes the UCI in the first PUSCH configured by the ConfiguredGrantConfig.

[0324] In one embodiment, the priority of the transmission power is provided.

[0325] In the NR standard specification, the UE allocates power to PUSCH / PUCCH / PRACH / SRS transmissions according to the following priority order (in descending order) such that the total UE transmission power is less than or equal to the maximum transmission power in each symbol of the transmission occasion: PRACH transmission on the PCell; PUCCH transmission with HARQ-ACK information and / or SR or PUSCH transmission with HARQ-ACK information; PUCCH transmission with CSI or PUSCH transmission with CSI; PUSCH transmission without HARQ-ACK information or CSI; SRS transmission of an aperiodic SRS with a priority higher than that of semi-persistent and / or periodic SRS; or PRACH transmission on a serving cell different from the PCell.

[0326] When the UE transmits a CG-PUSCH transmission with CG-UCI, it is also necessary to define the transmission power priority rule.

[0327] In one embodiment, the UE allocates power to PUSCH / PUCCH / PRACH / SRS / CG-PUSCH according to the following priority order (in descending order): PRACH transmission on the PCell; CG-PUSCH transmission with CG-UCI information; PUCCH transmission with HARQ-ACK information and / or SR or PUSCH transmission with HARQ-ACK information; PUCCH transmission with CSI or PUSCH transmission with CSI; PUSCH transmission without HARQ-ACK information or CSI; SRS transmission of an aperiodic SRS with a priority higher than that of semi-persistent and / or periodic SRS; or PRACH transmission on a serving cell different from the PCell.

[0328] In one embodiment, the UE allocates power to PUSCH / PUCCH / PRACH / SRS / CG-PUSCH according to the following priority order (in descending order): PRACH transmission on the PCell; PUCCH transmission with HARQ-ACK information and / or SR or PUSCH transmission with HARQ-ACK information; PUCCH transmission with CSI or PUSCH transmission with CSI; CG-PUSCH transmission with CG-UCI information; PUSCH transmission without HARQ-ACK information or CSI; SRS transmission of an aperiodic SRS with a priority higher than that of semi-persistent and / or periodic SRS; or PRACH transmission on a serving cell different from the PCell.

[0329] In one embodiment, the UE allocates power to PUSCH / PUCCH / PRACH / SRS / CG-PUSCH according to the following priority order (in descending order): PRACH transmission on the PCell; PUCCH transmission with HARQ-ACK information and / or SR or PUSCH transmission with HARQ-ACK information; CG-PUSCH transmission with CG-UCI information; PUCCH transmission with CSI or PUSCH transmission with CSI; transmission without HARQ-ACK information or CSI; SRS transmission of an aperiodic SRS with a priority higher than that of semi-persistent and / or periodic SRS; or PRACH transmission on a serving cell different from the PCell.

[0330] In one example, the UE may also prioritize the power allocation for transmission depending on the channel access mechanism used for transmission. For example, the UE may prioritize the power allocation for PUSCH or PUCCH transmission on a serving cell operating in licensed spectrum over the power allocation for PUSCH or PUCCH transmission on a serving cell operating in shared spectrum. For example, the UE may prioritize the power of a PUSCH transmission with UCI (such as HARQ-ACK information) on a serving cell operating in licensed spectrum (without a channel access mechanism for transmission) over a CG-PUSCH transmission with CG-UCI.

[0331] In one embodiment, UCI reporting in CG-PUSCH is provided. The UE may be provided with an RRC configuration to configure the multiplexing of CG-UCI and HARQ-ACK on CG-PUSCH; and in the case of PUCCH overlapping with CG-PUSCH within a PUCCH group, CG-UCI and HARQ-ACK are jointly encoded, where CG-UCI is considered the same type as HARQ-ACK.

[0332] HARQ-ACK information offset Configured according to the values of 3GPP specifications. If the UE multiplexes at most 2 HARQ-ACK information bits, more than 2 and at most 11 HARQ-ACK information bits, and more than 11 bits in the PUSCH respectively, then betaOffsetACK-Index1, betaOffsetACK-Index2, and betaOffsetACK-Index3 provide the indices for the UE to use In the remainder of this embodiment, the beta_offset index of HARQ-ACK is given by to represent. In addition, using the mapping defined in the 3GPP specification, the values in the value set are provided to the UE through betaOffsetCG-UCI-r16 value. The UE jointly encodes the HARQ-ACK information and the CG-UCI and determines the corresponding value. This embodiment includes methods and examples for determining the value of the jointly encoded HARQ-ACK and CG-UCI.

[0333] In one embodiment, the UE jointly encodes the HARQ-ACK and the CG-UCI and determines the corresponding value, where is determined by the offset index configured according to the 3GPP specification and to determine.

[0334] In one example,

[0335] In one example,

[0336] In one example,

[0337] In one example,

[0338] In one example,

[0339] In one example,

[0340] In one embodiment, the UE jointly encodes the HARQ-ACK and the CG-UCI and determines the corresponding value, where is determined by the beta_offset value configured according to the 3GPP standard specification and to determine.

[0341] In one example,

[0342] In one example,

[0343] In one example,

[0344] In one example,

[0345] In one example,

[0346] In one example,

[0347] In one embodiment, the UE jointly encodes HARQ-ACK and CG-UCI, and separate offset indices configured according to 3GPP standard specifications and are applied to HARQ-ACK and CG-UCI respectively.

[0348] In one embodiment, the UE jointly encodes HARQ-ACK and CG-UCI, and separate beta_offset values configured according to 3GPP standard specifications and are applied to HARQ-ACK and CG-UCI respectively.

[0349] In the NR unlicensed system (NR-U), the candidate monitoring time slots of the type 0 PDCCH search space set are the PDCCH monitoring time slots associated with the SS / PBCH block (which is quasi-co-located (QCL) with the SS / PBCH block where the CORESET from which the UE determines the type 0 PDCCH CSS set exists). In NR, for multiplexing mode 1, the number of monitoring time slots associated with the SS / PBCH block is 2, and the time slots are determined based on parameters O and M, which were originally designed for licensed frequency bands.

[0350] Depending on the value of M in the configuration of the type 0 PDCCH CSS set, the total duration of the transmission burst varies with the successful LBT position, which poses challenges to the LBT type and / or priority level applicable to such transmissions. Figure 23 A diagram illustrating this problem is shown.

[0351] As Figure 23 shown, assume Q is 4, and the transmissions of SSB and RMSI are in the same half-frame. If M = 1, the total duration of SSB and the associated RMSI changes according to the position of successful LBT, and in terms of determining the applicable LBT type and / or priority level, this may be inappropriately defined for unlicensed operation.

[0352] Figure 23 Shows an example LBT location 2300 according to an embodiment of the present disclosure. Figure 23 The illustrated embodiment of the LBT location 2300 is for illustrative purposes only. Figure 23 One or more of the illustrated components may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0353] As a result, depending on the candidate start position, when the candidate start position varies within the transmission window, the corresponding burst duration can vary dynamically. When the burst duration exceeds the maximum channel occupancy time (MCOT) of the current gNB LBT type, or when the current gNB LBT type is no longer applicable (e.g., CAT-2 LBT), the LBT type needs to be adjusted accordingly by the gNB.

[0354] The present disclosure focuses on enhancing the LBT process such that the LBT type for transmitting NR-U channels / signals can be adjusted dynamically based on the candidate start position and the corresponding burst duration of the channel / signal.

[0355] The present disclosure includes several embodiments, principles, methods, and examples that can be combined or used in combination with each other, or can operate independently. The embodiments / principles / methods / examples in the present disclosure can be applied to contention-free transmission on licensed spectrum, applied to transmission of frame-based devices (FBEs) with shared spectrum channel access (such as NR-U), applied to transmission of load-based devices (LBEs) with shared spectrum channel access, or applied to transmission based on both FBE and LBE with shared spectrum channel access.

[0356] In the present disclosure, FR1 refers to operation in an unlicensed / shared / licensed band in FR1 (such as the 5 GHz band or the 6 GHz unlicensed / shared band); while FR2 refers to operation in an unlicensed / shared / licensed band in FR2 (such as the 60 GHz band).

[0357] In one embodiment, an adaptive LBT process based on the transmission start position is provided. In such an embodiment, principles, methods, and examples of the adaptive LBT process are provided, wherein the LBT type of the NR-U transmission burst including the channel / signal is adjusted based on the potential transmission start position and the determined burst duration associated with that start position.

[0358] In one embodiment, the priority ranking of LBT types that the gNB can use to send DL transmission bursts including channels / signals, from highest to lowest, is: CAT-2 LBT, CAT-4 LBT with a Channel Access Priority Class (CAPC) value of 1, CAT-4 LBT with a CAPC value of 2, CAT-4 LBT with a CAPC value of 3, and CAT-4 LBT with a CAPC value of 4; and if the gNB cannot use the LBT type with the current priority order, then the gNB can dynamically change the LBT engine to the LBT type corresponding to the LBT with the next lower priority.

[0359] Figure 24 FIG. 2400 is a flowchart of a method for an adaptive LBT process according to an embodiment of the present disclosure, which process may be performed by a gNB (e.g., as shown in Figure 1 101-103). Figure 24 The embodiments of the method 2400 shown are for illustrative purposes only. Figure 24 One or more of the components shown may be implemented in a dedicated circuit configured to perform the functions, or one or more of the components may be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0360] As Figure 24 shown, the NR-U channel / signal to be transmitted is a discovery burst.

[0361] As Figure 24As shown, method 2400 starts at step 2402. At step 2402, the gNB determines whether the gNB can use CAT-2 LBT. At step 2402, if not, the gNB performs step 2412. At step 2402, if the gNB can use CAT-2 LBT, the gNB performs step 2404. At step 2404, the gNB determines whether CAT-2 LBT is successful before the candidate location. At step 2404, if successful, at step 2406, the gNB sends DRS. At step 2404, if not successful, at step 2408, the gNB determines the next candidate location and the burst duration. At step 2410, the gNB determines whether CAT-2 LBT can still be used. At step 2410, if so, the gNB performs step 2404. At step 2410, if not, at step 2412, the gNB determines the lowest CAPC value for the current burst duration and switches to CAT-4 LBT. At step 2414, the gNB determines whether the LBT engine of the current CAPC is completed before the candidate location. At step 2414, if so, the gNB sends a discovery burst. At step 2414, if not, the gNB determines the next candidate location and the burst duration. At step 2420, the gNB determines whether the next candidate location is within the discovery burst transmission window. At step 2420, if not, at step 2422, the gNB does not perform transmission in the current discovery burst transmission window. At step 2420, if so, at step 2424, if the burst duration exceeds the MCOT of the current CAPC, the gNB increases the CAPC.

[0362] In one example, the burst duration is determined and associated with the transmission start position of the burst. Once the gNB intends to switch the start position within the transmission window, the gNB can determine the burst duration of that start position.

[0363] In one example, if the transmission burst duration is at most 1 millisecond and the duty cycle is at most 1 / 20, the gNB can use CAT-2 LBT.

[0364] In one example, if the burst duration does not exceed the maximum COT corresponding to the CAPC value, CAT-4 LBT with a given CAPC value can be used.

[0365] In one example, the period for determining the duty cycle is the DRS window period, which can be common and independent of the start position of the DRS transmission burst.

[0366] In one example, the transmission burst duration is the total duration of the actually transmitted SSB and the associated RMSI starting after LBT success.

[0367] In one example, the transmission burst duration is the total duration of the time slots overlapping with the actually transmitted SSB that starts after LBT is successful and the associated RMSI.

[0368] In one embodiment, the priority order of the LBT types that the gNB can use to transmit the current channel / signal, from highest to lowest, is: CAT-2 LBT and CAT-4 LBT with a Channel Access Priority Class (CAPC) value of 4 (i.e., the highest CACP value); if the gNB cannot use CAT-2, the gNB can dynamically change the LBT engine to CAT-4 LBT with the highest CAPC value. As Figure 25 shown, the NR-U channel / signal to be transmitted is the discovery burst.

[0369] Figure 25 Another flowchart of method 2500 for an adaptive LBT process according to an embodiment of the present disclosure is shown, which can be executed by a gNB (e.g., such as Figure 1 shown in 101-103). Figure 25 The embodiment of method 2500 shown is for illustration only. Figure 25 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0370] As Figure 25As shown, method 2500 begins at step 2502. In step 2402, the gNB determines whether the gNB can use CAT-2 LBT. In step 2502, if not, the gNB performs step 2512. In step 2502, if the gNB can use CAT-2 LBT, the gNB performs step 2504. In step 2504, the gNB determines whether CAT-2 LBT is successful before the candidate location. In step 2504, if successful, in step 2506, the gNB sends DRS. In step 2504, if not successful, in step 2508, the gNB determines the next candidate location and the burst duration. In step 2510, the gNB determines whether CAT-2 LBT can still be used. In step 2510, if not, in step 2512, the gNB switches to CAT-4 LBT with the highest CAPC value. In step 2514, the gNB determines whether the LBT engine of the current CAPC is completed before the candidate location. In step 2514, if the LBT engine of the current CAPC is completed before the candidate location, in step 2516, the gNB sends a discovery burst. In step 2514, if not, in step 2518, the gNB determines the next candidate location and the burst duration. In step 2520, the gNB determines whether the next candidate location is within the discovery burst transmission window. In step 2520, if not, in step 2522, the gNB does not perform transmission in the current discovery burst transmission window. In step 2520, if so, the gNB performs step 2514.

[0371] In one example, the gNB can use CAT-2 LBT if the transmission burst duration is at most 1 millisecond and the duty cycle is at most 1 / 20.

[0372] In one example, the period for determining the duty cycle is the DRS window period, which can be common and independent of the start position of the DRS transmission burst.

[0373] In one example, the transmission burst duration is the total duration of the actually sent SSB and the associated RMSI that starts after LBT success.

[0374] In one example, the transmission burst duration is the total duration of the time slots overlapping with the actually sent SSB that starts after LBT success and the associated RMSI.

[0375] In one embodiment, the priority order of the LBT types that the gNB can use to send the current channel / signal from the highest to the lowest is: CAT-4 LBT with a Channel Access Priority Class (CAPC) value of 1, CAT-4 LBT with a CAPC value of 2, CAT-4 LBT with a CAPC value of 3, and CAT-4 LBT with a CAPC value of 4; and if the gNB cannot use the LBT type with the current priority order, then the gNB can dynamically change the LBT engine to the LBT type corresponding to the LBT with the next lower priority. As Figure 26 shown, the NR-U channel / signal to be sent is a discovery burst.

[0376] Figure 26 illustrates a flowchart of a method 2600 for LBT type sorting according to an embodiment of the present disclosure, which can be performed by a gNB (e.g., such as Figure 1 shown in 101-103). Figure 26 The embodiment of the method 2600 shown is for illustrative purposes only. Figure 26 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0377] As Figure 26 shown, the method 2600 starts at step 2602. In step 2602, the gNB determines the lowest CAPC value of the current burst duration and uses CAT-4 LBT. In step 2604, the gNB determines whether the LBT engine of the current CAPC has completed before the candidate position. In step 2604, if so, then in step 2606, the gNB sends a discovery burst. In step 2604, if not, then in step 2608, the gNB determines the next candidate position and burst duration. In step 2610, the gNB determines whether the next candidate position is within the discovery burst transmission window. In step 2610, if not, then in step 2614, the gNB does not perform transmission in the current discovery burst transmission window. In step 2610, if so, then in step 2612, if the burst duration exceeds the MCOT of the current CAPC, the gNB increases the CAPC.

[0378] In one example, if the burst duration does not exceed the maximum COT corresponding to the CAPC value, CAT-4 LBT with a given CAPC value can be used.

[0379] In one example, the period for determining the duty cycle is the DRS window period, which can be common and independent of the start position of the DRS transmission burst.

[0380] In one example, the transmission burst duration is the total duration of the actually transmitted SSB and the associated RMSI that start after LBT is successful.

[0381] In one example, the transmission burst duration is the total duration of the time slots overlapping with the actually transmitted SSB that start after LBT is successful and the associated RMSI.

[0382] In one embodiment, the gNB always uses CAT-4 LBT with a Channel Access Priority Class (CAPC) value of 4 (i.e., the highest CACP value). As Figure 27 shown, the NR-U channel / signal to be transmitted is a discovery burst.

[0383] Figure 27 Another flowchart of method 2700 for LBT type sorting according to an embodiment of the present disclosure is shown, which can be executed by a gNB (e.g., 101-103 as Figure 1 shown). Figure 27 The embodiment of method 2700 shown is for illustration only. Figure 27 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors executing instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0384] As Figure 27 shown, method 2700 starts at step 2702. In step 2702, the gNB uses the highest CAPC value of the current burst duration and uses CAT-4 LBT. In step 2704, the gNB determines whether the LBT engine of the current CAPC finishes before the candidate location. In step 2704, if so, then in step 2706, the gNB transmits the discovery burst. In step 2704, if not, then in step 2708, the gNB determines the next candidate location and burst duration. In step 2710, the gNB determines whether the next candidate location is within the discovery burst transmission window. In step 2710, if not, then in step 2712, the gNB does not perform transmission in the current discovery burst transmission window. In step 2710, if so, the gNB executes step 2704.

[0385] In one example, the transmission burst duration is the total duration of the actually transmitted SSB and the associated RMSI that start after LBT is successful.

[0386] In one example, the transmission burst duration is the total duration of the time slots that overlap with the actually transmitted SSB starting after successful LBT and the associated RMSI.

[0387] In one embodiment, the gNB determines the maximum possible transmission duration of the transmission burst for all possible starting positions within the transmission window and utilizes the corresponding allowed LBT type and / or priority level, regardless of the transmission start position within the transmission window.

[0388] In one embodiment of a method that may be applicable to this embodiment, when M in the configuration is 1 or 2, the method for determining the LBT type and / or priority level is only applicable to discovery burst transmissions.

[0389] In one embodiment of a method that may be applicable to this embodiment, the method for determining the LBT type and / or priority level is only applicable to discovery burst transmissions, where the SS / PBCH block of SIB1 and the associated CORESET / PDSCH are expected to be transmitted in the same burst and share the same channel occupancy.

[0390] Figure 28 A flowchart of a method 2800 for window size adaptation according to an embodiment of the present disclosure is shown, and this method can be executed by a UE (e.g., 111 - 116 as Figure 1 shown). Figure 28 The embodiment of the method 2800 shown is for illustration only. Figure 28 One or more of the components shown can be implemented in a dedicated circuit configured to perform the functions, or one or more of the components can be implemented by one or more processors that execute instructions to perform the functions. Other embodiments are used without departing from the scope of the present disclosure.

[0391] As Figure 28 shown, the method 2800 starts at step 2802. In step 2802, the UE determines the number of bits for the physical uplink shared channel (PUSCH).

[0392] In step 2804, the UE generates a first set of bits for the grant uplink control information (CG-UCI).

[0393] In step 2806, the UE generates a second set of bits for the hybrid automatic repeat request (HARQ) feedback.

[0394] In step 2808, if the sum of the first bit set for CG-UCI and the second bit set for HARQ feedback does not exceed the determined number of bits for PUSCH, the UE multiplexes the first bit set and the second bit set into the PUSCH, where the first bit set for CG-UCI is multiplexed with a higher priority than the second bit set for HARQ feedback.

[0395] In step 2810, the UE transmits, via an uplink channel, the PUSCH including the multiplexed first bit set and second bit set for CG-UCI and HARQ feedback, respectively, to a base station (BS).

[0396] In one embodiment, if the sum of the first bit set for CG-UCI and the second bit set for HARQ feedback exceeds the determined number of bits for PUSCH, the UE does not multiplex the first bit set with the second bit set.

[0397] In one embodiment, when the PUSCH includes the multiplexed first bit set and second bit set for CG-UCI and HARQ feedback, respectively, the UE determines a power offset value for the PUSCH, and the power offset value for the PUSCH is the same as the power offset value for HARQ feedback.

[0398] In one embodiment, the UE generates a third bit set for channel state information (CSI), and if the sum of the first bit set, the second bit set, and the third bit set does not exceed the determined number of bits for PUSCH, the UE multiplexes the third bit set for CSI with the first bit set for CG-UCI and the second bit set for HARQ feedback into the PUSCH. In such an embodiment, the third bit set for CSI is multiplexed with the lowest priority compared to the first bit set and the second bit set for CG-UCI and HARQ, respectively.

[0399] In one embodiment, if the sum of the first bit set, the second bit set, and the third bit set exceeds the determined bit set for PUSCH, the UE does not multiplex at least a part of the third bit set for CSI with the first bit set and the second bit set.

[0400] In one embodiment, the UE receives a discovery burst from the BS according to a transmission window for discovering the burst.

[0401] In one embodiment, the UE identifies the transmission window based on a duty cycle, which is defined as D DB / P DB where D DB is the duration of the discovery burst determined based on the transmission start instance of the discovery burst, and P DBIt is the period for discovering a burst transmission window.

[0402] Although the present disclosure has been described with exemplary embodiments, various changes and modifications can be suggested to those skilled in the art. The present disclosure is intended to cover these changes and modifications that fall within the scope of the appended claims. Any description in this application should not be construed as implying that any particular element, step, or function is an essential element that must be included within the scope of the claims. The scope of the claimed subject matter is defined by the claims.

Claims

1. A user equipment UE in a wireless communication system, the UE comprising: a transceiver, and a processor configured to: multiplex a first set of bits for configured grant - uplink control information CG - UCI on a configured grant - physical uplink shared channel CG - PUSCH, multiplex a second set of bits for hybrid automatic repeat request - acknowledgement HARQ - ACK on the CG - PUSCH when resources are available on the CG - PUSCH for HARQ - ACK, multiplex a third set of bits for CSI part 1 of type 1 sub - band or type 2 sub - band channel state information CSI on the CG - PUSCH when resources are available on the CG - PUSCH for type 1 sub - band or type 2 sub - band CSI part 1, multiplex a fourth set of bits for CSI part 2 on a physical uplink control channel PUCCH when resources are not available on the CG - PUSCH for type 1 sub - band or type 2 sub - band CSI part 2, send the CG - PUSCH to a base station BS via the transceiver, and send the PUCCH to the BS via the transceiver.

2. The UE according to claim 1, wherein, The processor is further configured to receive a discovery burst from the BS via the transceiver based on a transmission window of the discovery burst.

3. A base station BS in a wireless communication system, the BS comprising: a transceiver, and a processor configured to: receive a configured grant - physical uplink shared channel CG - PUSCH from a user equipment UE, receive a physical uplink control channel PUCCH from the UE, and wherein: a first set of bits for configured grant - uplink control information CG - UCI is multiplexed on the CG - PUSCH, a second set of bits for HARQ - ACK and a third set of bits for CSI part 1 are multiplexed on the CG - PUSCH when resources are available on the CG - PUSCH for HARQ - ACK and type 1 sub - band or type 2 sub - band channel state information CSI part 1, and a fourth set of bits for CSI part 2 is multiplexed on the PUCCH when resources are not available on the CG - PUSCH for type 1 sub - band or type 2 sub - band CSI part 2.

4. The BS according to claim 3, wherein The processor is further configured to send the discovery burst to the UE via the transceiver based on a transmission window of the discovery burst.

5. A method for a user equipment UE in a wireless communication system, the method comprising: multiplex a first set of bits for configured grant - uplink control information CG - UCI on a configured grant - physical uplink shared channel CG - PUSCH, multiplex a second set of bits for hybrid automatic repeat request - acknowledgement HARQ - ACK on the CG - PUSCH when resources are available on the CG - PUSCH for HARQ - ACK, multiplex a third set of bits for CSI part 1 of type 1 sub - band or type 2 sub - band channel state information CSI on the CG - PUSCH when resources are available on the CG - PUSCH for type 1 sub - band or type 2 sub - band CSI part 1, In the case where there are no resources available on the CG-PUSCH for the type 1 subband or the type 2 subband CSI part 2, the fourth bit set for CSI part 2 is multiplexed on the physical uplink control channel PUCCH, send the CG-PUSCH to the base station BS, and send the PUCCH to the BS.

6. The method according to claim 5 further comprises: Receive the discovery burst from the BS based on the transmission window of the discovery burst.

7. A method for a base station BS in a wireless communication system, the method comprising: Receive a configured grant - physical uplink shared channel CG-PUSCH from a user equipment UE, Receive a physical uplink control channel PUCCH from the UE, and wherein: A first bit set for configured grant - uplink control information CG-UCI is multiplexed on the CG-PUSCH, In the case where there are resources available on the CG-PUSCH for hybrid automatic repeat request - acknowledgement HARQ-ACK and type 1 subband or type 2 subband channel state information CSI part 1, a second bit set for HARQ-ACK and a third bit set for CSI part 1 are multiplexed on the CG-PUSCH, and In the case where there are no resources available on the CG-PUSCH for the type 1 subband or the type 2 subband CSI part 2, a fourth bit set for CSI part 2 is multiplexed on the PUCCH.

8. The method according to claim 7 further comprises: Send the discovery burst to the UE based on the transmission window of the discovery burst.

Images