Method and apparatus for uplink transmission in frame-based device NR license-free

By in the 5G NR-U system, the terminal device recognizes the time gap and performs channel sensing after receiving the downlink, the problem of low transmission efficiency of FBE NR-U is solved, and more efficient channel utilization and Channel sensing success rate.

CN113287337BActive Publication Date: 2024-11-01SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080008626.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2020-08-04
Filing Date
2020-09-11
Publication Date
2024-11-01
Estimated Expiration
2040-09-11

AI Technical Summary

Technical Problem

In 5G communication systems, frame-based devices (FBEs) are difficult to effectively realize uplink transmission in an NR license-free (NR-U) environment, especially in channel sensing and time-consuming management.

Method used

By in the shared spectrum channel, the terminal device identifies the time gap after receiving downlink transmission and performs channel sensing within the channel occupation time to determine whether uplink transmission can be safely performed, ensuring that the channel sensing is successful and the corresponding Uplink transmission is performed within time.

Benefits of technology

The uplink transmission efficiency and channel sensing success rate of the Rel-15 NR system for FBE NR-U is improved, and the RACH timing verification rules of FBE NR-U are met, and the spectrum utilization of the system is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113287337B_ABST
    Figure CN113287337B_ABST
Patent Text Reader

Abstract

The present disclosure relates to a communication method and system for integrating a fifth generation (5G) communication system supporting a higher data rate than a fourth generation (4G) system with an Internet of Things (IoT) technology. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, safety and security services. A method performed by a terminal operating in a shared spectrum channel is provided. The method includes: receiving a downlink (DL) transmission from a base station in a channel occupancy time (COT); identifying a time gap between a DL transmission and an uplink (UL) transmission; identifying whether to perform channel sensing before UL transmission based on the time gap; and sending UL transmission to a base station within the COT.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates generally to wireless communication systems, and more particularly to frame-based uplink transmission in device NR license-free. Background Art

[0002] In order to meet the increasing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, large-scale multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technology 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 networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoints (CoMP), receiving-end interference elimination, etc. In 5G systems, hybrid FSK with QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, which is a human-centered connectivity network where people generate and consume information, is now evolving into the Internet of Things (IoT), where distributed entities (such as things) exchange and process information without human intervention. An Internet of Everything (IoE) technology has emerged that combines big data processing technology with IoT technology by connecting to cloud servers, etc. As IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have been studied recently. Such IoT environments can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to multiple fields including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services through the fusion and combination between existing information technology (IT) and various industrial applications.

[0004] In line with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the fusion between 5G technology and IoT technology.

[0005] The communication system includes a downlink (DL) and an uplink (UL), the downlink (DL) transmits signals from a transmission point such as a base station (BS) or NodeB to a user equipment (UE), and the uplink (UL) transmits signals from the UE to a receiving point such as a NodeB. A UE (also commonly referred to as a terminal or mobile station) may be fixed or mobile and may be a cellular phone, a personal computer device, or an automation device. An eNodeB (eNB) (referred to as a NodeB in a long term evolution (LTE) communication system) and a gNodeB (gNB) (referred to as a NodeB in a new radio (NR) communication system) may also be referred to as an access point or other equivalent terms. Summary of the invention

[0006] Technical issues

[0007] Frame-based equipment or FBE is a channel access mechanism in which the transmit / receive structure has a periodic timing, whose periodicity is called the Fixed Frame Period (FFP); and the initiating device shall perform a Listen Before Talk (LBT) during the observation slot before starting transmission on the operating channel at the start of the FFP. The FFP is within 1ms to 10ms, and the observation slot is at least 9 microseconds. If LBT fails on an operating channel, the initiating device shall not transmit on that channel unless a short control signaling transmission meets certain requirements. The channel occupation time (COT) associated with a successful LBT check for FBE operation shall not be greater than 95% of the FFP and shall be followed by an idle period until the next FFP starts, such that the idle period is at least max(5% of the channel occupation time, 100 microseconds).

[0008] In addition to the load-based equipment (LBE) operation mode, NR-U can also support FBE operation mode for various application scenarios. Examples can include the presence of a single NR-U operator in the operating channel and the exclusion of other Wi-Fi networks (e.g., by deployment); and two or more NR-U operators coexisting in the operating channel, potentially coordinating between operators; and one or more NR-U operators coexisting with Wi-Fi networks based on FBE operation; etc.

[0009] Solution

[0010] The present disclosure relates to a quasi-5G or 5G communication system to be provided for uplink transmission in frame-based device NR license-free.

[0011] In one embodiment, a method performed by a terminal operating in a shared spectrum channel is provided. The method includes: receiving a downlink (DL) transmission from a base station in a channel occupation time (COT); identifying a time gap between the DL transmission and an uplink (UL) transmission; identifying whether to perform channel sensing before the UL transmission based on the time gap; and sending the UL transmission to the base station within the COT.

[0012] In another embodiment, a terminal operating in a shared spectrum channel is provided. The terminal includes: a transceiver; and a controller configured to: receive a downlink (DL) transmission from a base station in a channel occupation time (COT), identify a time gap between the DL transmission and an uplink (UL) transmission, identify whether to perform channel sensing before the UL transmission based on the time gap, and send the UL transmission to the base station within the COT.

[0013] In yet another embodiment, a method performed by a base station operating in a shared spectrum channel is provided. The method includes: sending a downlink (DL) transmission to a terminal in a channel occupation time (COT); and receiving an uplink (UL) transmission from the terminal within the COT, wherein the terminal identifies whether to perform channel sensing before the UL transmission based on a time gap between the DL transmission and the UL transmission.

[0014] In yet another embodiment, a base station operating in a shared spectrum channel is provided. The base station includes: a transceiver; and a controller configured to: send a downlink (DL) transmission to a terminal in a channel occupation time (COT), and receive an uplink (UL) transmission from the terminal within the COT, wherein the terminal identifies whether to perform channel sensing before the UL transmission based on a time gap between the DL transmission and the UL transmission.

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

[0016] Beneficial Effects

[0017] The present disclosure provides methods and apparatus for enhancing Rel-15 NR to support uplink transmission and corresponding LBT requirements for FBE NR-U and RACH opportunity verification rules for FBE NR-U. Such requirements and rules are not available in LTE-LAA. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] For a more complete understanding of the present disclosure and its advantages, reference is now made to the following description taken in conjunction with the accompanying drawings, in which like reference numerals represent like parts:

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

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

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

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

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

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

[0025] Figure 7 An example decoding process of a DCI format for a UE according to an embodiment of the present disclosure is shown;

[0026] Figure 8 shows example timing for FBE operation according to an embodiment of the present disclosure;

[0027] Fig. 9 An example LBT type for scheduled UL transmission in FBE NR-U according to an embodiment of the present disclosure is shown;

[0028] Fig.10 Another example LBT type for scheduled UL transmission in FBE NR-U according to an embodiment of the present disclosure is shown;

[0029] Fig.11 Another example LBT type for scheduled UL transmission in FBE NR-U according to an embodiment of the present disclosure is shown;

[0030] Fig.12 Another example LBT type for scheduled UL transmission in FBE NR-U according to an embodiment of the present disclosure is shown;

[0031] Fig.13 Another example LBT type for scheduled UL transmission in FBE NR-U according to an embodiment of the present disclosure is shown;

[0032] Fig.14An example CG-PUSCH for a FBE UE according to an embodiment of the present disclosure is shown;

[0033] Fig.15 Another example CG-PUSCH for FBE UE according to an embodiment of the present disclosure is shown;

[0034] Fig.16 Another example CG-PUSCH for FBE UE according to an embodiment of the present disclosure is shown;

[0035] Fig.17 Another example CG-PUSCH for FBE UE according to an embodiment of the present disclosure is shown;

[0036] Fig.18 Another example CG-PUSCH for FBE UE according to an embodiment of the present disclosure is shown;

[0037] Fig.19 shows an example RO for a FBE UE according to an embodiment of the present disclosure; and

[0038] Fig. 20 A flowchart of a method for uplink transmission in frame-based device NR license-free according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0039] Before proceeding to the following detailed description, it may be advantageous to set forth the definitions of certain words and phrases used throughout this patent document. The term "coupling" 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 "send", "receive" and "communication" and their derivatives include both direct and indirect communication. The terms "include" and "comprise" and their derivatives refer to including without limitation. The term "or" is inclusive, meaning and / or. The phrase "associated with..." and its derivatives mean including, included in, interconnected with, included in, connected to, or connected with, coupled to, or coupled with, can communicate with, collaborate with, interweave, juxtapose, be adjacent to, engage with, have, have the nature of, have a relationship with, etc. The term "controller" means any device, system, or part thereof that controls at least one operation. Such controllers can be implemented with hardware or a combination of hardware and software and / or firmware. The functionality associated with any particular controller can 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.

[0040] In addition, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by a 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, processes, functions, objects, classes, instances, related data or parts thereof suitable for implementation in a suitable computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as a read-only memory (ROM), a random access memory (RAM), a hard drive, a compact disc (CD), a digital video disc (DVD) or any other type of memory. "Non-transitory" computer-readable media does not include wired, wireless, optical or other communication links that transmit temporary electrical signals or other signals. Non-transitory computer-readable media include media in which data can be permanently stored and media in which data can be stored and then rewritten, such as rewritable optical discs or erasable memory devices.

[0041] 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 prior, as well as future uses of such defined words and phrases.

[0042] The following discusses Figures 1 to 20 The various embodiments used to describe the principles of the present disclosure in this patent document are merely exemplary and should not be interpreted in any way to limit 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.

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

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

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

[0046] like Figure 1 As 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 network.

[0047] gNB 102 provides wireless broadband access to network 130 for a first plurality of user devices (UEs) within coverage area 120 of gNB 102. The first plurality of UEs includes: UE 111, which may be located in a small business (SB); UE 112, which may be located in an enterprise (E); UE 113, which may be located in a WiFi hotspot (HS); UE 114, which may be located in a first residence (R); UE 115, which may be located in a second residence (R); and UE 116, which may be a mobile device (M), such as a cellular phone, a wireless laptop computer, a wireless PDA, etc. gNB 103 provides wireless broadband access to network 130 for a second plurality of UEs within coverage area 125 of gNB 103. The second plurality of UEs includes UE 115 and UE 116. In some embodiments, one or more of gNB 101 to gNB 103 may communicate with each other and with UE 111 to UE 116 using 5G, LTE, LTE-A, WiMAX, WiFi, or other wireless communication technologies.

[0048] Depending on the network type, the term "base station" or "BS" may refer to any component (or set 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 WiFi access point (AP), or other wireless enabling devices. A base station may provide wireless access according to one or more wireless communication protocols, for example, 5G 3GPP New Radio Interface / Access (NR), Long Term Evolution (LTE), Advanced LTE (LTE-A), High Speed ​​Packet Access (HSPA), Wi-Fi 802.11a / b / g / n / ac, etc. For convenience, the terms "BS" and "TRP" are used interchangeably in this patent document to indicate a network infrastructure component that provides wireless access to a remote terminal. In addition, depending on the network type, the term "user device" or "UE" may refer to any component, such as a "mobile station", "subscriber station", "remote terminal", "wireless terminal", "reception point", or "user device". For convenience, the term "user equipment" or "UE" is used in this patent document to refer to a remote wireless device that wirelessly accesses a BS, whether the UE is a mobile device (such as a mobile phone or smartphone) or is generally considered a fixed device (e.g., a desktop computer or vending machine).

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

[0050] As described in more detail below, one or more of UEs 111-116 include circuitry, programming, or a combination thereof for uplink transmission in frame-based device NR license-free. In certain embodiments, one or more of gNBs 101-103 include circuitry, programming, or a combination thereof for efficient uplink transmission in frame-based device NR license-free.

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

[0052] Figure 2 An exemplary gNB 102 according to an embodiment of the present disclosure is shown. Figure 2 The illustrated embodiment of gNB 102 is for illustration only, and Figure 1 gNB 101 and gNB 103 may have the same or similar configuration. However, gNBs have various configurations, and Figure 2 The scope of the present disclosure is not limited to any particular implementation of the gNB.

[0053] like Figure 2 As shown, gNB 102 includes multiple antennas 205a to 205n, multiple RF transceivers 210a to 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.

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

[0055] The TX processing circuit 215 receives analog or digital data (such as voice data, web data, email, or interactive video game data) from the controller / processor 225. The TX processing circuit 215 encodes, multiplexes, and / or digitizes the output baseband data to produce a processed baseband or IF signal. The RF transceivers 210a to 210n receive the output processed baseband or IF signals from the TX processing circuit 215 and up-convert the baseband or IF signals into RF signals that are transmitted via the antennas 205a to 205n.

[0056] The controller / processor 225 may include one or more processors or other processing devices that control the overall operation of the gNB 102. For example, the controller / processor 225 may control the RF transceivers 210a to 210n, the RX processing circuit 220, and the TX processing circuit 215 to receive forward channel signals and transmit reverse channel signals according to well-known principles. The controller / processor 225 may also support additional functions, such as more advanced wireless communication functions.

[0057] For example, the controller / processor 225 may support beamforming or directional routing operations to weight signals output from the plurality of antennas 205a to 205n differently to efficiently steer the output signals in a desired direction. Any of a variety of other functions may be supported in the gNB 102 by the controller / processor 225.

[0058] Controller / processor 225 is also capable of executing programs and other processes, such as an OS, that reside in memory 230. Controller / processor 225 may move data into or out of memory 230 as needed to execute a process.

[0059] The controller / processor 225 is also connected 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 appropriate wired or wireless connection. For example, when the gNB 102 is implemented as part of a cellular communication system (e.g., a system supporting 5G, 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 with a larger network (such as the Internet) via a wired or wireless local area network or via a wired or wireless connection. The interface 235 includes any appropriate structure that supports communication via a wired or wireless connection (such as an Ethernet or RF transceiver).

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

[0061] although Figure 2 An example of a gNB 102 is shown, but the Figure 2 For example, gNB 102 may include Figure 2Any number of each component shown. As a specific example, the access point can include multiple interfaces 235, and the controller / processor 225 can support routing functions for routing data between different network addresses. As another specific example, although shown as including a single TX processing circuit 215 example and a single RX processing circuit 220 example, the gNB 102 can include multiple TX processing circuit 215 examples and multiple RX processing circuit 220 examples (such as one example for each RF transceiver). In addition, Figure 2 The various components in may be combined, further subdivided, or omitted, and additional components may be added according to specific needs.

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

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

[0064] RF transceiver 310 receives an incoming RF signal from antenna 305 transmitted by a gNB of network 100. RF transceiver 310 down-converts the incoming RF signal to produce an intermediate frequency (IF) or baseband signal. The IF or baseband signal is sent to RX processing circuitry 325, which generates a processed baseband signal by filtering, decoding, and / or digitizing the baseband or IF signal. RX processing circuitry 325 sends the processed baseband signal to speaker 330 (e.g., for voice data) or processor 340 for further processing (such as for web browsing data).

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

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

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

[0068] Processor 340 is also coupled to touch screen 350 and display 355. An operator of UE 116 may input data into UE 116 using touch screen 350. Display 355 may be a liquid crystal display, light emitting diode display, or other display capable of presenting text (such as from a website) and / or at least limited graphics.

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

[0070] although Figure 3 An example of UE 116 is shown, but the Figure 3 Make various changes. For example, Figure 3The various components in the embodiment may be combined, further subdivided, or omitted, and additional components may be added as required. As a specific example, processor 340 may be divided into multiple processors, such as one or more central processing units (CPUs) and one or more graphics processing units (GPUs). In addition, although Figure 3 The UE 116 is shown configured as a mobile phone or smart phone, but the UE may be configured to operate as other types of mobile or stationary devices.

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

[0072] In order to meet the increasing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or quasi-5G communication systems. Therefore, 5G or quasi-5G communication systems are also referred to as "beyond 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, large-scale multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large-scale antenna technology 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 networks (RANs), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoints (CoMP), receiving-end interference elimination, etc.

[0073] The time unit for DL ​​signaling or for UL signaling on a cell is called a time slot and may include one or more symbols. A symbol may also serve as an additional time unit. A frequency (or bandwidth (BW)) unit is called a resource block (RB). An RB includes multiple subcarriers (SC). For example, a time slot may include 14 symbols with a duration of 1 millisecond or 0.5 milliseconds, and an RB may have a bandwidth of 180kHz or 360kHz and include 12 SCs with an interval of 15kHz or 30kHz between SCs, respectively.

[0074] DL signals include data signals that transmit information content, control signals that transmit DL control information (DCI) formats, and reference signals (RS) also called pilot signals. The gNB can send 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 multiple 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 be sent only in the BW of the corresponding PDCCH or PDSCH, and the UE can use DMRS to demodulate data or control information.

[0075] UL signals also include data signals that transmit information content, control signals that transmit UL control information (UCI), and RS. The UE sends data information (e.g., transport blocks) or UCI through the corresponding physical UL shared channel (PUSCH) or physical UL control channel (PUCCH). When the UE sends data information and UCI at the same time, the UE can multiplex both in the PUSCH or send them separately in the corresponding PUSCH and PUCCH. UCI includes: hybrid automatic repeat request acknowledgement (HARQ-ACK) information, which indicates the UE's correct or incorrect detection of a data transmission block (TB); scheduling request (SR), which indicates whether the UE has data in the UE's buffer; and CSI report, which enables the gNB to select appropriate parameters to perform link adaptation for PDSCH or PDCCH transmission to the UE.

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

[0077] DL and UL transmissions may be based on an Orthogonal Frequency Division Multiplexing (OFDM) waveform, including a variation that uses DFT precoding, referred to as DFT-spread-OFDM.

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

[0079] 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, an SC mapping unit 460 maps the modulated coded symbols and DMRS or CSI-RS 450 to an SC 465, a filter 470 performs an inverse fast Fourier transform (IFFT), a cyclic prefix (CP) insertion unit adds the CP, and a filter 480 filters the resulting signal and a radio frequency (RF) unit 490 transmits it.

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

[0081] The filter 520 filters the received signal 510, the CP removal unit removes the CP 530, the filter 540 applies a fast Fourier transform (FFT), the SC demapping unit 550 demaps the SC selected by the BW selector unit 555, the channel estimator and demodulator unit 560 demodulates the received symbols, the rate dematcher 570 restores rate matching, and the decoder 580 decodes the resulting bits to provide information bits 590.

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

[0083] For a DCI format that schedules a PDSCH that transmits system information (SI), the RNTI may be an SI-RNTI. For a DCI format that schedules a PDSCH that provides a random access response (RAR), the RNTI may be an RA-RNTI. For a DCI format that schedules a PDSCH or PUSCH to a single UE before the UE establishes a radio resource control (RRC) connection with the serving gNB, the RNTI may be a temporary C-RNTI (TC-RNTI). For a DCI format that provides TPC commands to a group of UEs, the RNTI may be a TPC-PUSCH-RNTI or a TPC-PUCCH-RNTI. Each RNTI type may be configured to the UE via higher layer signaling, such as RRC signaling. A DCI format that schedules PDSCH transmissions to a UE is also referred to as a DL DCI format or DL ​​allocation, while a DCI format that schedules PUSCH transmissions from a UE is also referred to as a UL DCI format or UL grant.

[0084] PDCCH transmissions may be performed within a set of physical RBs (PRBs). The gNB may configure a UE with one or more sets of PRBs (also referred to as control resource sets) for PDCCH reception. PDCCH transmissions may be performed in control channel elements (CCEs) contained in a control resource set. The UE determines CCEs for PDCCH reception based on search spaces, such as UE-specific search spaces (USSs) for PDCCH candidates in DCI format with CRC scrambled by an RNTI (such as C-RNTI) that is configured to the UE via UE-specific RRC signaling for scheduling PDSCH reception or PUSCH transmission, and common search spaces (CSSs) such as PDCCH candidates in DCI format with CRC scrambled by other RNTIs. A set of CCEs that may be used for PDCCH transmissions to the UE defines the PDCCH candidate locations. An attribute of a control resource set is a transmission configuration indication (TCI) state that provides quasi-co-location information of DMRS antenna ports for PDCCH reception.

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

[0086] The gNB encodes and transmits each DCI format in the corresponding PDCCH respectively. The RNTI masks the CRC of the DCI format codeword to enable the UE to identify the DCI format. For example, the CRC and RNTI may include (for example) 16 bits or 24 bits. The CRC of the (uncoded) DCI format bits 610 is determined using a CRC calculation unit 620, and the CRC is masked using an exclusive OR (XOR) operation unit 630 between the CRC bits and the RNTI bits 640. The XOR operation is defined as XOR (0,0) = 0, XOR (0,1) = 1, XOR (1,0) = 1, XOR (1,1) = 0. The masked CRC bits are appended to the DCI format information bits using a CRC append unit 650. The encoder 660 performs channel coding (such as tail-biting convolutional coding or polar coding), followed by rate matching of the allocated resources by a rate matcher 670. The interleaving and modulation unit 680 applies interleaving and modulation, such as QPSK, and the output control signal 690 is transmitted.

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

[0088] The demodulator and deinterleaver 720 demodulates and deinterleaves the received control signal 710. The rate matcher 730 recovers the rate matching applied at the gNB transmitter and the decoder 740 decodes the resulting bits. After decoding, the CRC extractor 750 extracts the CRC bits and provides 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 CRC check is performed by unit 790. When the CRC check succeeds (checksum is zero), the DCI format information bits are considered valid. When the CRC check does not succeed, the DCI format information bits are considered invalid.

[0089] Frame-based equipment (FBE) is a channel access mechanism in which the transmit / receive structure has periodic timing, whose periodicity is called the fixed frame period (FFP); and the initiating device can perform listen before talk (LBT) during the observation time slot before starting transmission on the operating channel at the beginning of the FFP. The FFP is within 1ms to 10ms, and the observation time slot is at least 9 microseconds. If LBT fails on an operating channel, the initiating device shall not transmit on that channel unless a short control signaling transmission meets certain requirements. The channel occupation time (COT) associated with a successful LBT check for FBE operation may be no greater than 95% of the FFP and may be followed by an idle period until the next FFP begins, such that the idle period is at least max(5% of the channel occupation time, 100 microseconds).

[0090] Figure 8 Example timing for FBE operation 800 is shown according to an embodiment of the disclosure. Figure 8 The illustrated embodiment of timing for FBE operation 800 is for illustration only. Figure 8 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0091] In this disclosure, an observation time slot refers to a duration during which an FBE device performs LBT, and an NR-U time slot refers to a time slot of 14 OFDM symbols of the NR-U system.

[0092] In addition to the load-based equipment (LBE) operation mode, NR-Unlicensed (NR-U) can also support the above-mentioned FBE operation mode for various application scenarios. Examples may include the presence of a single NR-U operator in the operating channel and the exclusion of other Wi-Fi networks (e.g., by deployment); and two or more NR-U operators coexisting in the operating channel, potentially with coordination between operators; and one or more NR-U operators coexisting with Wi-Fi networks based on FBE operation; etc. Compared with the LBE operation mode, the FBE operation mode may have higher spectrum utilization in such cases, assuming that the LBT process in FBE operation is much simpler than the LBT process in LBE operation.

[0093] The present disclosure focuses on enhancements to Rel-15 NR to support uplink transmission of FBE NR-U, including enhancements to scheduled UL transmission of FBE NR-U, enhancements to configured granted UL transmission of FBE NR-U, and enhancements to PRACH transmission of FBE NR-U.

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

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

[0096] The present disclosure focuses on enhancements to Rel-15 NR to support uplink transmission of FBE NR-U, including enhancements to scheduled UL transmission of FBE NR-U, enhancements to configured granted UL transmission of FBE NR-U, and enhancements to PRACH transmission of FBE NR-U.

[0097] In one embodiment, signaling and indication methods are provided to support PUSCH transmissions scheduled by UL grant for FBE NR-U.

[0098] In one embodiment, the general LBT types for granting UL transmission of NR-U may include: CAT-4 LBT, where each CAT-4 LBT type may have a corresponding LBT priority value. For example, there may be a total of 4 LBT priority values, and the lower the priority value, the higher the channel access priority. CAT-4 LBT can be used by the UE to obtain a UE-initiated COT; CAT-2 LBT with a duration of Tμs, where 16<=T<=25. This option can be used when the gap from the start of the UL transmission to the end of the previous transmission is at least 16μs, and the CAT-2 LBT is successful if the energy detected on the operating channel during a single observation slot or two observation slots within the Tμs duration is lower than the energy detection threshold; and CAT-1 LBT for immediate transmission. This option can be used when the gap from the start of the UL transmission to the end of the previous transmission is less than 16μs.

[0099] In one embodiment, the LBT types used for UL transmission in FBE NR-U may include CAT-2 LBT and CAT-1 LBT, but not CAT-4 LBT.

[0100] In one example, CAT-2 LBT for UL transmission in FBE NR-U may include only 1 type. In one sub-example, a successful CAT-2 LBT may be referenced to the operating channel during a single observation slot within a 25 μs duration immediately following the UL transmission starting below the energy detection threshold. In another sub-example, a successful CAT-2 LBT may be referenced to the operating channel during both observation slots within a 25 μs duration immediately following the UL transmission starting below the energy detection threshold.

[0101] In one example, CAT-2 LBT for UL transmission in FBE NR-U may include 2 types, one of which is CAT-2 LBT with a duration of 16 μs and the other is CAT-2 LBT with a duration of 25 μs. In one sub-example, a successful CAT-2 LBT of 16 μs may be referenced to an operating channel during a single observation slot or two observation slots within a 16 μs duration immediately following the UL transmission starting below an energy detection threshold. In another sub-example, a successful CAT-2 LBT of 25 μs may be referenced to an operating channel during a single observation slot or two observation slots within a 25 μs duration immediately following the UL transmission starting below an energy detection threshold.

[0102] In one example, for UL transmission in FBE NR-U, there is no need to indicate CAT-4 LBT and the corresponding LBT priority level value for CAT-4 LBT.

[0103] In one example, the LBT type for a scheduled UL transmission in FBE NR-U may be explicitly indicated by a UL grant of the scheduled UL transmission.

[0104] In one example, the UL grant may have an LBT type field to indicate one of CAT-1LBT or CAT-2LBT. In one sub-example, the number of bits of the LBT type field in the UL grant needs to be 1 bit. In another sub-example, as in the embodiments and / or examples mentioned, CAT-2LBT may refer to a CAT-2LBT type. In another sub-example, CAT-2LBT may refer to one of 16μs CAT-2LBT or 25μs CAT-2LBT, where a higher layer parameter (e.g., RRC parameter) may configure one of 16μs CAT-2LBT or 25μs CAT-2LBT to be indicated by the UL grant. In yet another sub-example, CAT-2LBT may refer to one of 16μs CAT-2LBT or 25μs CAT-2LBT, which may be fixed in the specification. In yet another sub-example, CAT-1 LBT may be scheduled by the gNB if the end of the previous transmission within a fixed frame period (FFP) and the start of the scheduled UL transmission is at most 16 μs.

[0105] In one example, the UL grant may have an LBT type field to indicate one of CAT-1 LBT, CAT-2 LBT of 16 μs, and CAT-2 LBT of 25 μs. In one sub-example, the number of bits of the LBT type field in the UL grant requires 2 bits. In another sub-example, as in the embodiments and / or examples mentioned, CAT-2 LBT of 16 μs and CAT-2 LBT of 25 μs may refer to CAT-2 LBT type.

[0106] In one example, a start and length indicator value (SLIV) indicated in a UL grant for a scheduled UL transmission may be interpreted as a start symbol for an LBT operation prior to the scheduled UL transmission, and the UL transmission may begin after the LBT operation is completed. In a sub-example, the UL transmission may be interrupted in the first symbol after the LBT operation.

[0107] In one example, a start and length indicator value (SLIV) indicated in a UL grant for a scheduled UL transmission may be interpreted as a start symbol for the scheduled UL transmission, and an LBT operation may be performed prior to the indicated start of the scheduled UL transmission.

[0108] Fig. 9An example LBT type for scheduled UL transmission in FBE NR-U 900 according to an embodiment of the present disclosure is shown. Fig. 9 The illustrated embodiment of LBT type for scheduled UL transmissions in FBE NR-U 900 is for illustration only. Fig. 9 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0109] like Fig. 9 As shown, the LBT type used for the scheduled UL transmission is indicated by the corresponding UL grant.

[0110] In one embodiment, the LBT type and / or LBT parameters for UL transmission may be semi-statically configured via higher layer parameters.

[0111] In one example, the higher layer parameters may configure CAT-2 LBT as the default LBT type. In a sub-example, as in the mentioned embodiments and / or examples, CAT-2 LBT may refer to a CAT-2 LBT type.

[0112] In one example, when CAT-2 LBT is used, the higher layer parameters may configure the default CAT-2 LBT type to be one of 16 μs CAT-2 LBT and 25 μs CAT-2 LBT. In a sub-example, this example may be applied in conjunction with the embodiments and / or examples mentioned, where the DCI may configure CAT-2 LBT as the LBT type, and 16 μs CAT-2 LBT or 25 μs CAT-2 LBT may be configured by the higher layer parameters.

[0113] In one example, higher layer parameters may configure CAT-1 LBT as the default LBT type.

[0114] In one example, the LBT type configured by a higher layer parameter (e.g., an RRC parameter) may be overwritten by the configured LBT type dynamically indicated by the UL grant.

[0115] In one embodiment, the LBT type and / or LBT parameters for UL transmission may be fixed by specification.

[0116] In one example, the fixed configuration of the LBT type may be one of CAT-1 LBT and CAT-2 LBT.

[0117] In one example, a fixed configuration of the LBT type made by the specification may be overridden by a semi-static configuration by higher layer parameters or a dynamic configuration by UL grant.

[0118] In one embodiment, the LBT type may be determined by the UE through implicit indication, where the UE may implicitly determine the LBT type through DCI (i.e., there is no explicit LBT type field in the DCI) and / or configuration of higher layer parameters.

[0119] In one example, the configuration by DCI and / or higher layer parameters that can facilitate the UE to implicitly derive the LBT type may include a COT duration and a COT start position, or a COT end position corresponding to a COT in which the UE receives an UL grant. In a sub-example, the COT start position and the COT duration, or the COT end position, may be indicated by one or more of a GC-PDCCH, a UE-specific PDCCH, a DM-RS, or a higher layer parameter. In another sub-example, based on the gNB COT duration and / or the gNB COT end position, the UE may determine whether the start position of the UL transmission scheduled by the UL grant is within the current gNB COT, and if the start position of the scheduled UL transmission is within the gNB COT, CAT-1 LBT or CAT-2 LBT may be used, where a specific LBT type (CAT-1 LBT, 16μs CAT-2 LBT, or 25μs CAT-2 LBT) may be explicitly indicated by the DCI or implicitly derived by the UE. For example, if the gap between the start of a UL transmission and the end of the previous transmission within the COT is within 16 μs, CAT-1 LBT may be used, otherwise CAT-2 LBT may be used.

[0120] In one example, configuration by DCI and / or higher layer parameters that may facilitate the UE to implicitly derive the LBT type may include a gNB COT structure that configures a slot format for each slot within a gNB initiated COT that includes an UL grant. In one sub-example, the COT structure may be obtained by the UE via a group common (GC)-PDCCH. In another sub-example, the COT structure may be indicated by a slot format indication (SFI) for each slot within the COT, wherein the SFI may indicate whether a symbol within a slot of the COT is DL, UL, or flexible. In another sub-example, the UE may determine a gap duration from the end of a previous DL transmission within the COT to the start of a scheduled UL transmission based on the last DL symbol position before the start position of the scheduled UL transmission (which may be obtained via the gNB COT structure and via the start position of the scheduled UL transmission and / or UL TA value configured by DCI and / or higher layer parameters). For example, if the gap between the start of a UL transmission and the end of the previous transmission within the COT is within 16 μs, CAT-1 LBT may be used, otherwise CAT-2 LBT may be used.

[0121] In one example, if the UE's scheduled UL transmission can share the gNB-initiated COT containing the UL grant, the LBT type (e.g., 16 / 25μs CAT-2LBT, CAT-1LBT) can be determined based on the UE implementation. In a sub-example, the UE can always use 25μs as the baseline CAT-2LBT option.

[0122] Fig.10 Another example LBT type for scheduled UL transmission in FBE NR-U 1000 according to an embodiment of the present disclosure is shown. Fig.10 The illustrated embodiment of LBT type for scheduled UL transmissions in the FBE NR-U 1000 is for illustration only. Fig.10 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0123] like Fig.10 As shown, the UE can determine that the UL transmission is within the current COT after detecting the GC-PDCCH, and the UE can select the corresponding UL LBT type according to the COT structure indicated in the GC-PDCCH.

[0124] In one embodiment, scheduled UL transmissions for FBE NR-U may be constrained to be contained within the same channel occupancy time of a fixed frame period containing the UL grants for the scheduled UL transmissions.

[0125] In one example, if the UE has received a UL grant, the UE may always assume that the serving gNB has successfully obtained the COT in the LBT, and therefore the UE may send the scheduled UL transmission subject to a successful LBT, which may be determined according to one of the mentioned embodiments and / or examples.

[0126] In one example, this approach may be implemented by the gNB only selecting values ​​in the pusch-TimeDomainAllocationList that ensure that the UL transmission is included in the UL grant in the current COT.

[0127] In one example, if a scheduled UL transmission starts outside of the current COT containing the UL grant, the UE may drop the UL transmission.

[0128] In one example, if the scheduled UL transmission is not completely contained in the current COT containing the UL grant (eg, partially contained in an idle period), the scheduled PUSCH falling outside the current COT may be interrupted.

[0129] In one embodiment, it may be allowed to schedule UL transmissions for FBE NR-U outside of the same channel occupancy time of a fixed frame period containing UL grants for scheduled UL transmissions.

[0130] In one example, if the UE has received an UL grant, the UE may start the scheduled UL transmission if the scheduled UL transmission is within the COT obtained by the gNB and the UE has successfully performed LBT according to the LBT type determined from one of the mentioned embodiments and / or examples. In a sub-example, the UE may determine whether the scheduled UL transmission is within the COT obtained by the gNB based on detecting whether the serving gNB has sent a common PDCCH (GC-PDCCH) to inform UEs associated with the gNB of subsequent transmissions on the COT (which implicitly indicates that the gNB has passed LBT when obtaining the COT), or equivalently, whether the serving gNB has successfully performed LBT to obtain the COT of the FFP in which the scheduled UL transmission occurs.

[0131] Fig.11 Yet another example LBT type for scheduled UL transmission in FBE NR-U 1100 according to an embodiment of the present disclosure is shown. Fig.11The illustrated embodiment of LBT type for scheduled UL transmissions in the FBE NR-U 1100 is for illustration only. Fig.11 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0132] like Fig.11 As shown, the UL grant schedules UL transmission in the next FFP (i.e., FFP1) following the COT / FFP (i.e., FFP0) containing the UL grant; and the gNB has passed the CAT-2 LBT for FFP1 and has correspondingly sent the GC-PDCCH, which has been detected by the UE. Therefore, the UE can send the scheduled PUSCH after the UE has passed the LBT of the type indicated by the UL grant or determined by the UE.

[0133] In one example, if the scheduled UL transmission is within the FFP for which the gNB fails to obtain the corresponding LBT through LBT, the UE may discard the scheduled UL transmission.

[0134] Fig.12 Yet another example LBT type for scheduled UL transmission in FBE NR-U 1200 according to an embodiment of the present disclosure is shown. Fig.12 The illustrated embodiment of LBT type for scheduled UL transmissions in the FBE NR-U 1200 is for illustration only. Fig.12 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0135] like Fig.12 As shown, the gNB fails to obtain the FFP following the FFP containing the UL grant through CAT-2 LBT, so the UE can discard the scheduled UL transmission scheduled within the FFP where the gNB failed to pass the LBT.

[0136] In one example, if the scheduled UL transmission is within the FFP in which the gNB fails to obtain the corresponding LBT through LBT, the UE may send the UL transmission if CAT-2 LBT is performed immediately before the scheduled UL transmission. In one sub-example, this example may be applied regardless of the relative time position of the scheduled UL transmission. In another sub-example, this example may be applied when the FBE NR-U UE may be an initiating device for initiating COT, where the FFP may be configured for the UE and the UL transmission may be scheduled to be at the beginning of the UE-associated FFP.

[0137] In one instance, the UE-associated FFP may be applied together with the gNB FFP. In another instance, the UE-associated FFP may be different from the gNB-associated FFP. In another instance, the scheduled UL transmission may start only at the beginning of the UE-associated FFP, so that the start position for the scheduled PUSCH transmission has the granularity of one UE-associated FFP. For example, the gNB may select an appropriate UL grant for PUSCH delay to ensure this. In another example, the UE may initiate UL transmission in the earliest UE-associated FFP that is no earlier than the start position scheduled by the UL grant. In another instance, the UL grant for PUSCH delay (i.e., K2) may be interpreted with the time domain granularity of the UE-associated FFP. For example, K2=1 indicates that the scheduled PUSCH starts at the beginning of the next UE-associated FFP and the UE needs to pass the CAT-2 LBT before the start of the UE-associated FFP to send the scheduled PUSCH.

[0138] In another sub-example, this example may be applied when the FBE NR-U UE may be the initiating device for initiating COT, where the FFP may be configured for the UE and the scheduled UL transmission may be in the middle of the UE-associated FFP and following other UE UL transmissions (e.g., CG-PUSCH or RACH) starting at the start of the UE-initiated COT. In one instance, the gap between the scheduled UL transmission and other UE UL transmissions starting at the start of the UE-initiated COT may be at most 16 μs. In another example, the gap between the scheduled UL transmission and other UE UL transmissions starting at the start of the UE-initiated COT may be greater than 16 μs, and the UE may need to pass CAT-2 LBT before the scheduled UL transmission to send the scheduled UL transmission.

[0139] In one example, if the scheduled UL transmission is not completely contained within the current COT containing the UL grant (eg, partially contained in an idle period), the scheduled PUSCH falling outside the current COT may be interrupted.

[0140] In one embodiment, enhancements to FBE NR-U UE detection of a gNB-obtained COT are provided. In such embodiments, a FBE NR-U UE is provided to detect whether an uplink transmission (whether dynamically scheduled, semi-statically configured, or semi-persistently configured) is within a gNB-initiated COT.

[0141] In one embodiment, the FBE NR-U UE can determine whether the serving gNB has obtained the COT of the current FFP by monitoring and detecting the GC-PDCCH.

[0142] In one example, the GC-PDCCH can be the same as the Rel-15 NR GC-PDCCH, which refers to the type 3-PDCCH common search space (CSS) set configured by SearchSpace in PDCCH-Config, where searchSpaceType = Common for DCI formats with CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI or TPC-SRS-RNTI (and only for primary cell, C-RNTI, MCS-C-RNTI or CS-RNTI).

[0143] In one example, the GC-PDCCH can be enhanced from the Rel-15 NR GC-PDCCH, which can further indicate information such as COT duration / end time, effective LBT bandwidth that has passed the LBT, etc.; and the GC-PDCCH can use a DCI format with a CRC scrambled by one of the existing RNTIs for GC-PDCCH from the NR standard specification or a DCI format with a CRC scrambled by a new RNTI for GC-PDCCH introduced for NR-U.

[0144] In one example, if the UE has detected the GC-PDCCH from the gNB, the UE can determine that the serving gNB has obtained the COT of the current FFP.

[0145] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0146] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0147] In one embodiment, the FBE NR-U UE may determine whether the serving gNB has obtained the COT of the current FFP by monitoring and detecting the UE-specific UL grant.

[0148] In one example, if the UE has detected a UE-specific UL grant with a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI, the UE may determine that the serving gNB has obtained the COT for the current FFP.

[0149] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0150] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0151] In one embodiment, the FBE NR-U UE may determine whether the serving gNB has obtained the COT of the current FFP by monitoring and detecting the PDCCH CSS set configured by the MIB or by the higher layer parameter PDCCH-ConfigCommon in SIB1 / RMSI.

[0152] In one example, if the UE has detected a cell-specific PDCCH with a DCI format scrambled by SI-RNTI from the serving gNB, the UE can determine that the serving gNB has obtained the COT for the current FFP.

[0153] In one example, if the UE has detected a cell-specific PDCCH with a DCI format scrambled by the P-RNTI from the serving gNB, the UE can determine that the serving gNB has obtained the COT for the current FFP.

[0154] In one example, if the UE has detected a UE-specific UL grant with a CRC scrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI, the UE may determine that the serving gNB has obtained the COT for the current FFP.

[0155] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0156] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0157] In one example, the mentioned examples and / or embodiments may be applied to an RRC_IDLE FBE NR-U UE.

[0158] In one embodiment, the FBE NR-U UE may determine whether the serving gNB has obtained the COT for the current FFP by monitoring and detecting the presence of the SS / PBCH and / or Discovery Reference Signature (DRS) from the serving gNB.

[0159] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0160] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0161] In one example, the mentioned examples and / or embodiments may be applied to an RRC_IDLE FBE NR-U UE.

[0162] In one embodiment, the UE FBE NR-U may determine whether the serving gNB has obtained the COT of the current FFP by monitoring and detecting the presence of SIB1 and / or other system information (OSI) from the serving gNB.

[0163] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0164] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0165] In one example, the mentioned examples and / or embodiments may be applied to an RRC_IDLE FBE NR-U UE.

[0166] In one embodiment, the FBE NR-U UE can determine whether the serving gNB has obtained the COT of the current FFP by monitoring and detecting paging messages, where the paging messages are scheduled by a PDCCH with a CSS set corresponding to the UE's serving gNB and the PDCCH is used for a DCI format with a CRC scrambled by the P-RNTI.

[0167] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0168] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0169] In one example, the examples and / or embodiments mentioned may be applied to an RRC_IDLE FBE NR-U UE. For example, this may be applied to an IDLE UE attempting a PRACH transmission.

[0170] In one embodiment, the FBE NR-U UE may determine whether the serving gNB has obtained the COT for the current FFP by monitoring and detecting short messages transmitted on the PDCCH using P-RTNI with or without an associated paging message using the short message field in DCI format 1_0.

[0171] In one example, the mentioned examples and / or embodiments may be applied to a RRC_CONNECTED FBE NR-U UE.

[0172] In one example, the mentioned examples and / or embodiments may be applied to a RRC_INACTIVE FBE NR-U UE.

[0173] In one example, the examples and / or embodiments mentioned may be applied to an RRC_IDLE FBE NR-U UE. For example, this may be applied to an IDLE UE attempting a PRACH transmission.

[0174] In one example, the short message may include a cell ID, based on which the UE may determine that the short message corresponds to the serving gNB. In one sub-example, the short message field may be increased from 8 bits to 10 bits for indicating the cell ID.

[0175] In one embodiment, the FBE NR-U UE may determine the FFP duration and start position of each FFP associated with the serving gNB from the corresponding configuration of the RMSI.

[0176] In one embodiment, enhancements are provided for supporting configured granted UL transmission for FBE NR-U. In such embodiments, signaling and indication methods are provided to support configured granted UL transmission for FBE NR-U.

[0177] In one embodiment, FBE NR-U may support configured granted uplink transmissions.

[0178] In one example, both type 1 configured grants (i.e., semi-statically configured by higher layer parameters) and type 2 configured grants (i.e., semi-persistently scheduled by UL grants in valid activation / deactivation DCI) uplink transmissions can be supported by FBE NR-U.

[0179] In another example, only type 1 configured grants (i.e., semi-statically configured by higher layer parameters) uplink transmissions can be supported by FBE NR-U.

[0180] In yet another example, only type 2 configured grants (i.e., semi-persistently scheduled by UL grants in valid activation / deactivation DCI) uplink transmissions may be supported by FBE NR-U.

[0181] In one embodiment, the FBE NR-U UE may be an initiating device for initiating transmission.

[0182] In one example, explicit signaling from higher layer parameters (e.g., RRC parameters) can be used to enable / disable the FBE UE as an initiator of transmission. In one sub-example, if the higher layer parameters disable the FBE UE as an initiator, the FBE UE cannot be an initiator of FBE transmission.

[0183] In another sub-example, a FBE UE may act as an initiating device for FBE transmission only if higher layer parameters enable the FBE UE to act as an initiating device.

[0184] In one example, explicit L1 signaling (e.g., from DCI) can be used to dynamically enable / disable the FBE UE as an initiator of transmission. In one sub-example, if the L1 signaling disables the FBE UE as an initiator, the FBE UE cannot be an initiator of FBE transmission. In another sub-example, the FBE UE can be an initiator of FBE transmission only if the L1 signaling enables the FBE UE as an initiator.

[0185] In another example, the MAC CE may be used to enable / disable the FBE UE as an initiator of transmission. In one sub-example, if the MAC CE disables the FBE UE as an initiator, the FBE UE cannot be an initiator of FBE transmission. In another sub-example, the FBE UE can be an initiator of FBE transmission only if the MAC CE enables the FBE UE as an initiator.

[0186] In one example, the FBE NR-U UE may act as an initiator of transmission only if the FBE NR-U UE determines that the serving gNB has not yet acquired the COT associated with the current FFP of the gNB. In a sub-example, the FBE NR-U UE may determine whether the serving gNB has already acquired the COT.

[0187] In one example, the FBE NR-U UE may act as an initiator of a transmission only if the FBE NR-U UE has unscheduled UL transmissions configured to be sent within the current FFP. In one sub-example, the unscheduled UL transmissions may be all or a subset of the configured granted PUSCH, PRACH, SRS. In another sub-example, the current FFP may refer to the FFP associated with the gNB. In another sub-example, the current FFP may refer to the FFP associated with the UE.

[0188] In one example, the FBE NR-U UE may act as an initiator of a transmission only if the FBE NR-U UE has a scheduled UL transmission configured to be sent within the current FFP. In one sub-example, the current FFP may refer to the FFP associated with the gNB. In another sub-example, the current FFP may refer to the FFP associated with the UE.

[0189] In one example, the FBE NR-U UE can be used as the initiator of transmission only if and only if one or more of the examples and / or embodiments mentioned are met. In a sub-example, the FBE NR-U UE can be used as the initiator if and only if the examples and / or embodiments mentioned are met.

[0190] In one example, when the UE is the initiator of the FBE transmission, the COT duration and / or FFP duration associated with the UE may be configured by one of semi-static configuration through higher layer parameters and / or dynamic indication through layer 1 (L1) signaling and activation / deactivation of a MAC CE, depending on the regulations. In one sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be explicitly configured with dedicated higher layer parameters and / or MAC CE and / or DCI format and / or DCI field. In another sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be implicitly configured or implicitly inferred from other existing higher layer parameters and / or MAC CE and / or DCI format and / or DCI field. For example, the COT duration and / or FFP duration associated with the NR-U UE may be the same as that associated with the same gNB.

[0191] In one example, when the UE is an initiator of FBE transmission, the starting position of the FFP associated with the FBE NR-U UE may be configured by semi-static configuration through higher layer parameters and / or by dynamic indication through layer 1 (L1) signaling and by one of activation / deactivation of MAC CE. In one sub-example, the starting position of the FFP associated with the FBE NR-U UE may be explicitly configured with dedicated higher layer parameters and / or MAC CE and / or DCI format and / or DCI field. In another sub-example, the starting position of the FFP associated with the FBE NR-U UE may be implicitly configured or implicitly inferred from other existing higher layer parameters and / or MAC CE and / or DCI format and / or DCI field.

[0192] In one embodiment, the FBE NR-U UE may transmit only in configured Granted (CG) PUSCH opportunities by sharing a valid gNB-initiated COT, where the UE may determine or may be informed that the serving gNB has obtained a COT containing the configured CG PUSCH opportunities and the UE has passed the LBT corresponding to the CG PUSCH opportunities.

[0193] In one example, the FBE NR-U may determine whether the CGPUSCH opportunity is within the gNB initiated COT by following one of the examples and / or embodiments.

[0194] In one example, the LBT type may be fixed as CAT-2 LBT.

[0195] In one example, the LBT type may be implicitly determined by the UE based on the mentioned examples and / or embodiments.

[0196] In one example, the LBT type of a CG PUSCH opportunity with a type 2 CG-PUSCH may be indicated by a PDCCH for activating / deactivating a type 2 CG. In a sub-example, an additional field for indicating the LBT type may be introduced for the corresponding DCI format for activating / deactivating a type 2 configured UL grant, which may be implemented according to the examples and / or embodiments mentioned.

[0197] Fig.13 Yet another example LBT type for scheduled UL transmission in FBE NR-U 1300 according to an embodiment of the present disclosure is shown. Fig.13 The illustrated embodiment of LBT type for scheduled UL transmissions in the FBE NR-U 1300 is for illustration only. Fig.13One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0198] like Fig.13 As shown, the UE can determine that the CG-PUSCH opportunity is within the COT initiated by the gNB by detecting the GC-PDCCH, and the UE can utilize the CG-PUSCH opportunity when the LBT for the CG-PUSCH has passed.

[0199] In one embodiment, the FBE NR-U UE may be an initiating device and have an associated COT and / or FFP such that the FBE NR-U UE transmits in a configured granted (CG) PUSCH opportunity if the UE has passed the LBT corresponding to the FFP associated with the UE that includes a CG-PUSCH opportunity.

[0200] In one example, the COT duration and / or FFP duration associated with the UE may be configured by one of semi-static configuration through higher layer parameters and / or dynamic indication through layer 1 (L1) signaling and activation / deactivation of a MAC CE, depending on the regulations allowing. In a sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be explicitly configured with dedicated higher layer parameters and / or MAC CE and / or DCI format and / or DCI field.

[0201] In another sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be implicitly configured or implicitly inferred from other existing higher layer parameters and / or MAC CE and / or DCI format and / or DCI fields. For example, the FFP duration may be the minimum of the configured grant type 1 or type 2 periodicity and the specified maximum allowed FFP duration (e.g., 10 ms).

[0202] In one example, the CG-PUSCH may be at the beginning of an FFP associated with the UE such that the CG-PUSCH may be sent once the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured.

[0203] In one example, a CG-PUSCH may be in the middle of an FFP associated with a UE, and such CG-PUSCH may be sent if the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured; and: if there is a gap duration greater than 16 μs relative to the end of the previous transmission in the COT before the configured CG-PUSCH, then the UE has passed the CAT-2 LBT before the CG-PUSCH in the middle of the FFP, such as Fig.14 shown. Fig.14 An example CG-PUSCH for a FBE UE 1400 is shown according to an embodiment of the present disclosure. Fig.14 The illustrated embodiment of CG-PUSCH for FBE UE 1400 is for illustration only. Fig.14 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0204] like Fig.15 As shown, if the gap duration before the configured CG-PUSCH is at most 16 μs relative to the end of the previous transmission in the COT, the UE can send the CG-PUSCH directly in the middle of the FFP.

[0205] Fig.15 Another example CG-PUSCH for a FBE UE 1500 according to an embodiment of the present disclosure is shown. Fig.15 The illustrated embodiment of CG-PUSCH for FBE UE 1500 is for illustration only. Fig.15 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0206] In one example, the FFP duration and / or COT duration associated with the UE may be fixed in the specification.

[0207] In one example, the FFP duration and / or COT duration associated with the UE may be the same as the configured periodicity of the grant transmissions. In a sub-example, the CG-PUSCH may be at the beginning of the FFP associated with the UE such that the CG-PUSCH may be transmitted once the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured.

[0208] Fig.16 Yet another example CG-PUSCH for a FBE UE 1600 according to an embodiment of the present disclosure is shown. Fig.16 The illustrated embodiment of CG-PUSCH for FBE UE 1600 is for illustration only. Fig.16 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0209] like Fig.16 As shown, the configured authorization type 1 is used.

[0210] Fig.17 Yet another example CG-PUSCH for a FBE UE 1700 according to an embodiment of the present disclosure is shown. Fig.17 The illustrated embodiment of CG-PUSCH for FBE UE 1700 is for illustration only. Fig.17 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0211] like Fig.17 As shown, using the configured grant type 2, and if CG-PUSCH is activated in FFP and the UE has passed LBT, the UE can transmit in CG-PUSCH; and if CG-PUSCH is deactivated in FFP, the UE does not need to perform LBT.

[0212] In one example, the periodicity of the configured grant transmissions may be an integer multiple of the FFP duration and / or COT duration associated with the UE. In a sub-example, the CG-PUSCH may be at the beginning of the FFP associated with the UE such that the CG-PUSCH may be sent once the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured.

[0213] like Fig.17 As shown, if CG-PUSCH is activated in FFP and the UE has passed LBT, the UE can transmit in CG-PUSCH; and if CG-PUSCH is deactivated in FFP or FFP does not contain CG-PUSCH, the UE does not need to perform LBT.

[0214] In one example, the FFP duration and / or COT duration associated with the UE may be an integer multiple of the configured periodicity of the granted transmissions. In one sub-example, the CG-PUSCH may be at the beginning of the FFP associated with the UE, and such CG-PUSCH at the beginning of the FFP may be sent once the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured. In another sub-example, the CG-PUSCH may be in the middle of the FFP associated with the UE, and such CG-PUSCH may be sent if the UE has passed the LBT corresponding to the FFP / COT in which the CG-PUSCH is configured; and if there is a gap duration greater than 16 μs relative to the CG-PUSCH at the beginning of the FFP, the UE has passed the CAT-2 LBT before the CG-PUSCH in the middle of the FFP, as Fig.18 shown.

[0215] Fig.18 Yet another example CG-PUSCH for a FBE UE 1800 according to an embodiment of the present disclosure is shown. Fig.18 The illustrated embodiment of CG-PUSCH for FBE UE 1800 is for illustration only. Fig.18 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0216] In one example, the FFP duration and / or COT duration associated with a UE need not start with a CG-PUSCH at the beginning of the FFP duration and / or COT duration. In one sub-example, this may occur when (periodicity of CG-PUSCH / FFP=m / n) m and n are both integer values. In another sub-example, this may apply when different FBE UEs are using synchronized FFP.

[0217] In one example, the mentioned examples and / or embodiments may be used only in the case where the gNB fails to obtain the COT associated with the gNB containing the CG-PUSCH through LBT; or the mentioned embodiments and / or examples may always be used by the UE to send the CG-PUSCH regardless of whether the gNB has obtained the COT.

[0218] In one example, the mentioned embodiments and / or examples may be applied to other periodic uplink transmissions besides CG-PUSCH, such as periodic sounding reference signal (SRS) for FBE NR-U.

[0219] In one embodiment, enhancements are provided to support PRACH transmissions for FBE NR-U. In such embodiments, enhancements are provided for FBE NR-U to support PRACH transmissions.

[0220] In one embodiment, FBE NR-U can support PRACH transmission of UE.

[0221] In one example, an IDLE UE may send a PRACH configured by higher layer parameters.

[0222] In one example, the UE may also send a PRACH scheduled by a PDCCH command or a DCI.

[0223] In one example, the UE may also send a PRACH following the DRS.

[0224] In one embodiment, a FBE NR-U UE may send PRACH only by sharing a valid gNB-initiated COT, where the UE may determine or may be informed that the serving gNB has obtained a COT containing a UE-associated RACH opportunity (RO) and the UE has passed the LBT corresponding to the RO.

[0225] In one example, by following one of the examples and / or embodiments, the FBE NR-U may determine whether the CG PUSCH opportunity is within the gNB initiated COT.

[0226] In one example, the LBT type may be fixed as CAT-2 LBT.

[0227] In one example, according to the mentioned embodiments and / or examples, the LBT type can be implicitly determined by the UE.

[0228] In one example, the LBT type may be explicitly indicated to the UE via a PDCCH command or other DCI format.

[0229] In one embodiment, the FBE NR-U UE may be an initiating device and have an associated COT and / or FFP such that the FBE NR-U UE transmits in a configured valid RACH opportunity if the UE has passed the LBT corresponding to the FFP associated with the UE that contains the RACH opportunity.

[0230] In one example, the COT duration and / or FFP duration associated with the UE may be configured by semi-static configuration through higher layer parameters and / or by dynamic indication through Layer 1 (L1) signaling and by one of activation / deactivation of a MAC CE, depending on what regulations allow.

[0231] In one sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be explicitly configured with dedicated higher layer parameters and / or MAC CE and / or DCI format and / or DCI fields.

[0232] In another sub-example, the COT duration and / or FFP duration associated with the FBE NR-U UE may be implicitly configured or implicitly inferred from other existing higher layer parameters and / or MAC CE and / or DCI format and / or DCI fields. For example, the FFP duration may be the minimum of the PRACH configuration period and the maximum FFP duration allowed by the specification (e.g., 10 ms).

[0233] In one example, the FFP duration and / or COT duration associated with the UE may be fixed in the specification. For example, since the PRACH configuration period is an integer multiple of 10 ms, the FFP duration may be set to 10 ms.

[0234] In one example, the RO may be at the beginning of the FFP associated with the UE such that the PRACH may be sent once the UE has passed the LBT corresponding to the FFP / COT in which the RO is configured.

[0235] In one example, the RO may be in the middle of the COT / FFP associated with the UE, and if the UE has passed the LBT corresponding to the FFP / COT in which the RO is configured, the UE may send PRACH; and: if there is a gap duration greater than 16 μs relative to the end of the previous transmission in the COT before the configured RO, and the UE has passed the CAT-2 LBT before the RO; or if there is a gap duration of up to 16 μs relative to the end of the previous transmission in the COT before the configured RO, the UE may send PRACH directly in the configured RO.

[0236] In one example, the FFP duration and / or COT duration associated with the UE may be the same as the PRACH configuration period. In one sub-example, this occurs when both the PRACH configuration period and the UE FFP are 10 ms.

[0237] Fig.19 An example RO for a FBE UE 1900 according to an embodiment of the present disclosure is shown. Fig.19 The embodiment of the RO for the FBEUE 1900 shown is for illustration only. Fig.19One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0238] like Fig.19 As shown, two ROs are configured for FBE UE within FFP (non-uniformly distributed within COT / FFP), where FFP has the same configuration period as PRACH.

[0239] In one example, the RO position configured by the UE may be repeated in a periodic pattern, where the pattern periodicity may be an integer multiple of the FFP duration associated with the UE. In a sub-example, such a periodic pattern may have a periodicity of a PRACH configuration period or an association period between SSB and RO or an association pattern period between SSB and RO.

[0240] In one embodiment, the RACH opportunity validation rules may be enhanced from Rel-15 NR such that ROs overlapping with idle periods of the FBE fixed frame period may be considered invalid.

[0241] In one example, the FBE FFP may be an FFP associated with the FBE NR-U gNB. In a sub-example, when using the mentioned embodiments and / or examples, this may be applied so that the UE may send a RO by sharing only the COT initiated by the gNB.

[0242] In one example, the FBE FFP may be an FFP associated with a FBE NR-U UE. In one sub-example, this may be applied when the UE is capable of sending PRACH via a UE-initiated COT, where the UE is the initiating device.

[0243] In one example, FBE NR-U has the following PRACH validation rules: if TDD-UL-DL-ConfigurationCommon is provided to the UE, then the PRACH opportunity in the PRACH slot is valid provided that the RO does not overlap with the idle period of the FFP of the initiating device sending the PRACH, and: the PRACH opportunity is within the UL symbol, or the PRACH opportunity is not before the SS / PBCH block in the PRACH slot, and the PRACH opportunity starts at least N symbols after the last downlink symbol and at least N symbols after the last SS / PBCH block transmission symbol, where the gap N is fixed in the specification or configured by higher layer parameters or DCI.

[0244] Fig. 20A flowchart of a method 2000 for uplink transmission in a frame-based device NR license-free mode according to an embodiment of the present disclosure is shown. The method may be performed by a user equipment (eg, 111 to 116, such as Figure 1 as shown) to execute. Fig. 20 The illustrated embodiment of method 2000 is for illustration only. Fig. 20 One or more of the components shown may be implemented in dedicated circuits configured to perform the functions described, or one or more components may be implemented by one or more processors executing instructions to perform the functions described.Other embodiments may be used without departing from the scope of the present disclosure.

[0245] like Fig. 20 As shown, method 2000 starts at step 2002. In step 2002, a UE in a wireless communication system supporting shared spectrum channel access receives first downlink control information (DCI) including a channel occupation time (COT) of a base station (BS) via a shared spectrum channel.

[0246] Then, in step 2004, the UE determines a first portion of the COT for downlink transmission from the BS and a second portion of the COT for uplink transmission to the BS, wherein the COT includes a gap between the first portion and the second portion of the COT.

[0247] Then, in step 2006, the UE performs a channel access procedure based on the duration of the gap.

[0248] In one embodiment, the channel access procedure does not include a duration for sensing the shared spectrum channel, and the duration of the gap does not exceed 16 microseconds.

[0249] In one embodiment, the channel access procedure includes a duration of 16 microseconds for sensing the shared spectrum channel, and the duration of the gap is longer than 16 microseconds.

[0250] Next, in step 2008, the UE receives a downlink transmission from the BS via the shared spectrum channel in the first part of the COT.

[0251] Finally, in step 2010, the UE sends an uplink transmission to the BS via the shared spectrum channel in the second part of the COT based on a sensed state of the shared spectrum channel, which is sensed as an idle state during the channel access procedure in the duration of the gap.

[0252] In one embodiment, the UE identifies the operation mode of the BS, and based on identifying that the operation mode of the BS is the semi-static mode, further identifies that there is a period in which transmission is not allowed before starting the COT.

[0253] In one embodiment, the UE determines that a physical random access channel (PRACH) opportunity is valid, wherein the PRACH opportunity does not overlap with a period in which no transmission is allowed before starting the COT.

[0254] In one embodiment, the UE determines the second DCI from the downlink transmission included in the first part of the COT.

[0255] In such an embodiment, the second DCI includes a channel access operation type for uplink transmissions included in the second part of the COT; and the channel access operation type is one of: a channel access procedure type that does not include a duration for sensing a shared spectrum channel, or a channel access procedure type that includes a duration of 16 microseconds for sensing a shared spectrum channel.

[0256] Although the present disclosure has been described with exemplary embodiments, various variations and modifications may be conceived by those skilled in the art. The present disclosure is intended to include such variations 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 patent subject matter is defined by the claims.

Claims

1. A method performed by a terminal operating in a shared spectrum channel, the method include: receiving a downlink DL transmission from a base station in a channel occupancy time COT; identifying a time gap between the DL transmission and an uplink UL transmission; identifying whether to perform channel sensing before the UL transmission according to the value of the time gap; and transmitting the UL transmission to the base station within the COT, where the maximum COT is identified based on period information configured by higher layer parameters, and Wherein, based on the fact that the physical random access channel PRACH opportunity does not overlap with the time period before the start of the next COT, the PRACH opportunity is valid. 2 . The method of claim 1 , wherein the channel occupancy associated with the COT is initiated by the base station. 3 . The method of claim 1 , wherein in a case where the value of the time gap is at most 16 μs, the UL transmission is transmitted within the COT without performing the channel sensing.

4. The method of claim 1 , wherein the UL transmission is transmitted within the COT after the channel sensing if the value of the time gap is greater than 16 μs and the channel is identified as idle for a sensing time slot duration within a 25 μs interval prior to the UL transmission. The method according to claim 4 , wherein the sensing time slot duration is equal to 9 μs. The method of claim 1 , wherein the time period is associated with a duration of the COT.

7. A terminal operating in a shared spectrum channel, the terminal include: Transceiver; as well as A controller configured to: Receiving downlink DL transmission from the base station during the channel occupancy time COT, identifying a time gap between the DL transmission and the uplink UL transmission, identifying whether to perform channel sensing before the UL transmission according to the value of the time gap, and transmitting the UL transmission to the base station within the COT, where the maximum COT is identified based on period information configured by higher layer parameters, and Wherein, based on the fact that the physical random access channel PRACH opportunity does not overlap with the time period before the start of the next COT, the PRACH opportunity is valid. The terminal according to claim 7 , wherein the channel occupancy associated with the COT is initiated by the base station. 9 . The terminal of claim 7 , wherein in a case where the value of the time gap is at most 16 μs, the UL transmission is transmitted within the COT without performing the channel sensing.

10. The terminal of claim 7, wherein in the case where the value of the time gap is greater than 16 μs and the channel is identified as idle for a sensing time slot duration within a 25 μs interval before the UL transmission, the UL transmission is transmitted within the COT after the channel sensing, and The duration of the sensing time slot is equal to 9 μs. The terminal according to claim 7 , wherein the time period is associated with a duration of the COT.

12. A method performed by a base station operating in a shared spectrum channel, the method include: Transmitting downlink DL transmission to the terminal during the channel occupation time COT; as well as receiving an uplink (UL) transmission from the terminal within the COT, wherein whether to perform channel sensing before the UL transmission is identified according to a value of a time gap between the DL transmission and the UL transmission, and where the maximum COT is identified based on period information configured by higher layer parameters, and Wherein, based on the fact that the physical random access channel PRACH opportunity does not overlap with the time period before the start of the next COT, the PRACH opportunity is valid.

13. A base station operating in a shared spectrum channel, the base station include: Transceiver; as well as A controller configured to: transmitting a downlink DL transmission to the terminal during the channel occupancy time COT, and receiving an uplink (UL) transmission from the terminal within the COT, wherein whether to perform channel sensing before the UL transmission is identified according to a value of a time gap between the DL transmission and the UL transmission, and where the maximum COT is identified based on period information configured by higher layer parameters, and Wherein, based on the fact that the physical random access channel PRACH opportunity does not overlap with the time period before the start of the next COT, the PRACH opportunity is valid.