Method for idle channel access power signaling for channel occupancy time
By reporting EIRPs by UEs and dynamically adjusting EIRPs, the CCA power signaling problem during COT sharing in 5G NR systems was resolved, improving resource allocation efficiency and channel access flexibility, and reducing interference.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- APPLE INC
- Filing Date
- 2021-04-06
- Publication Date
- 2026-04-14
AI Technical Summary
In 5G NR systems, existing technologies struggle to effectively manage idle channel access (CCA) power signaling during Channel Occupied Time (COT) sharing, leading to uneven resource allocation and interference issues in wireless communication systems.
User equipment (UE) is configured to report the maximum peak average equivalent isotropic radiated power (EIRP) and the actual EIRP to the base station, and dynamically adjust the EIRP of transmission bursts through directed listen-before-speak (LBT) and closed-loop power control to achieve COT sharing.
It improves the resource allocation efficiency of wireless communication systems, reduces interference, and enhances the flexibility and reliability of channel access.
Smart Images

Figure CN115443673B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for idle channel access (CCA) power signaling during channel occupancy time (COT) sharing, for example in 5G NR systems and later versions.
[0002] Description of related technologies
[0003] The use of wireless communication systems is growing rapidly. In recent years, wireless devices such as smartphones and tablets have become increasingly sophisticated. In addition to supporting phone calls, many mobile devices now offer access to the internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can operate complex applications that utilize these capabilities.
[0004] Long Term Evolution (LTE) is currently the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their user base. LTE was first proposed in 2004 and first standardized in 2008. Since then, with the exponential growth in the use of wireless communication systems, the demand for wireless network operators has increased to support higher capacity for a higher density of mobile broadband users. Therefore, research into new radio access technologies began in 2015, and in 2017, the first version of 5G New Radio (5G NR) was standardized.
[0005] Compared to LTE, 5G-NR (also known as NR) offers higher capacity for higher density mobile broadband users, while also supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and / or lower battery consumption. Furthermore, NR allows for more flexible UE scheduling compared to current LTE. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR. Summary of the Invention
[0006] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for idle channel access (CCA) power signaling during channel occupancy time (COT) sharing, for example in 5G NR systems and higher.
[0007] For example, in some implementations, a User Equipment (UE) (such as UE 106) may be configured to report the maximum peak average equivalent isotropic radiated power (EIRP) for COT sharing to a base station (such as base station 102). The maximum EIRP for COT sharing may be reported as a UE capability and / or via a UE capability. This UE capability may be a parameter, such as peakEIRP-v17, and may be reported for a frequency range between 52.6 GHz and 71 GHz. Furthermore, the UE may be configured to receive a Pout value from the base station for CCA. The Pout value may specify the EIRP used for the transmission burst and may be based at least in part on the UE capability. Additionally, the UE may be configured to report the actual EIRP for CCA to the base station to obtain COT.
[0008] As another example, in some implementations, a UE (such as UE 106) may be configured to perform directed listen-before-speak (LBT) using a specific EIRP and beam detection for transmission bursts. The UE may be further configured to report a Pout value for COT sharing to a base station (such as base station 102). This Pout value may be at least partially based on directed LBT, and the Pout value may specify an EIRP for the transmission burst. As an example, the Pout value may be reported via a CG uplink control indication (UCI), which may include the Pout value, transmission control information (TCI) status, COT duration and / or COT offset, and other parameters.
[0009] As another example, in some implementations, the UE (such as UE 106) may be configured to detect that the EIRP exceeds a threshold, where the threshold may be at least partially based on a closed-loop power control setting. Additionally, the UE may be configured to report a Pout value for COT sharing to a base station (such as base station 102) via a Media Access Control (MAC) control element, where the Pout value may specify the EIRP used for transmission bursts. It should be noted that when the UE does not report a Pout value, the base station may use a power value associated with uplink power control as the Pout value.
[0010] The techniques described herein can be implemented in and / or used with a variety of different types of devices, including but not limited to any one of the following computing devices: unmanned aerial vehicles (UAVs), unmanned controllers (UACs), UTM servers, base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, and various other computing devices.
[0011] The present invention is intended to provide a brief overview of some of the subjects described in this document. Therefore, it should be understood that the above features are merely illustrative and should not be construed as narrowing the scope or substance of the subjects described herein in any way. Other features, aspects, and advantages of the subjects described herein will become apparent from the following detailed description, drawings, and claims. Attached Figure Description
[0012] A better understanding of the subject matter can be obtained by considering the following detailed description of the various embodiments in conjunction with the accompanying drawings, in which:
[0013] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.
[0014] Figure 1B Examples of base stations and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.
[0015] Figure 2 An exemplary block diagram of a base station according to some implementation schemes is shown.
[0016] Figure 3 An exemplary block diagram of a server according to some implementation schemes is shown.
[0017] Figure 4 An exemplary block diagram of a UE according to some implementation schemes is shown.
[0018] Figure 5 An exemplary block diagram of a cellular communication circuit according to some implementation schemes is shown.
[0019] Figure 6A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to 5G CN.
[0020] Figure 6B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to 5G CN as well as non-3GPP access.
[0021] Figure 7 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.
[0022] Figure 8 An example of a method for idle channel access (CCA) power signaling during channel occupancy time (COT) sharing, according to some implementation schemes, is shown.
[0023] Figure 9An example of a method for configuring authorized (CG) uplink COT sharing according to some implementation schemes is shown.
[0024] Figure 10 Examples of methods for dynamic authorization (DG) uplink COT sharing according to some implementation schemes are shown.
[0025] Although the features described herein may be subject to various modifications and alternatives, specific embodiments thereof are shown by way of example in the accompanying drawings and described in detail herein. However, it should be understood that the drawings and the detailed description thereof are not intended to limit this document to the specific forms disclosed, but rather are intended to cover all modifications, equivalents and alternatives falling within the substance and scope of the subject matter as defined by the appended claims. Detailed Implementation
[0026] acronym
[0027] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:
[0028] 3GPP: Third Generation Partnership Project
[0029] UE: User Equipment
[0030] RF: Radio Frequency
[0031] ·BS: Base Station
[0032] DL: Downlink
[0033] ·UL: Uplink
[0034] LTE: Long Term Evolution
[0035] NR: New Radio
[0036] ·5GS: 5G system
[0037] ·5GMM: 5GS Mobility Management
[0038] ·5GC / 5GCN: 5G Core Network
[0039] ·IE: Information Elements
[0040] ·CE: Control element
[0041] MAC: Media Access Control
[0042] •SSB: Synchronization Signal Block
[0043] • CSI-RS: Channel State Information Reference Signal
[0044] • PDCCH: Physical Downlink Control Channel
[0045] • PDSCH: Physical Downlink Shared Channel
[0046] •RRC: Radio Resource Control
[0047] • RRM: Radio Resource Management
[0048] • CORESET: Control Resource Set
[0049] •TCI: Transport Configuration Indicator
[0050] • DCI: Downlink Control Indicator
[0051] the term
[0052] The following is a glossary of terms used in this disclosure:
[0053] Memory media – any device of any type of nontransitory memory device or storage device. The term “memory media” is intended to include mounting media such as CD-ROMs, floppy disks, or magnetic tape devices; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash memory, magnetic media, e.g., hard disk drives or optical storage devices; registers or other similar types of memory elements, etc. Memory media may also include other types of nontransitory memory or combinations thereof. Furthermore, memory media may reside in a first computer system executing a program, or may reside in a different second computer system connected to the first computer system via a network such as the Internet. In the latter case, the second computer system may provide program instructions to the first computer for execution. The term “memory media” may include two or more memory media that may reside in different locations on different computer systems, for example, connected via a network. Memory media may store program instructions (e.g., representing a computer program) that can be executed by one or more processors.
[0054] Carrier medium - storage media as described above and physical transmission media, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).
[0055] Programmable hardware elements encompass a variety of hardware devices that include multiple programmable functional blocks connected via programmable interconnects. Examples include FPGAs (Field-Programmable Gate Arrays), PLDs (Programmable Logic Devices), FPOAs (Field-Programmable Object Arrays), and CPLDs (Complex PLDs). Programmable functional blocks can vary from fine-grained (combinatorial logic units or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "configurable logic units."
[0056] Computer system (or computer) – any of various types of computing or processing systems, including personal computer systems (PCs), mainframe computer systems, workstations, network appliances, internet-connected appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations thereof. In general, the term "computer system" can be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.
[0057] User equipment (UE) (or “UE device”) – any device in a variety of types of computer system equipment that is mobile or portable and performs wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). TM Based on Android TM Telephones), portable gaming devices (e.g., Nintendo DS) TM PlayStation Portable TM Gameboy Advance TM iPhone TM Laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly defined as encompassing any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by the user and capable of wireless communication.
[0058] Base station - The term "base station" has the full range of its common meaning and includes at least a wireless communication station that is installed in a fixed location and used for communication as part of a wireless telephone system or radio system.
[0059] A processing element (or processor) refers to a variety of elements or combinations of elements capable of performing the functions of a device such as user equipment or cellular network equipment. A processing element may include, for example: a processor and associated memory, portions or circuitry of individual processor cores, an entire processor core, a processor array, circuitry such as an ASIC (Application-Specific Integrated Circuit), programmable hardware elements such as a Field-Programmable Gate Array (FPGA), and any combination thereof.
[0060] A channel is a medium used to transmit information from a transmitter to a receiver. It should be noted that because the characteristics of the term "channel" can vary depending on different wireless protocols, the term "channel" as used herein can be considered to be used in a standard manner consistent with the type of device to which the term is referenced. In some standards, the channel width can be variable (e.g., depending on device capabilities, frequency band conditions, etc.). For example, LTE can support scalable channel bandwidths from 1.4 MHz to 20 MHz. In contrast, WLAN channels can be 22 MHz wide, while Bluetooth channels can be 1 MHz wide. Other protocols and standards may include different definitions of channels. Furthermore, some standards may define and use multiple types of channels, such as different channels for uplink or downlink and / or different channels for different purposes such as data, control information, etc.
[0061] Frequency band – The term “frequency band” has the full range of its general meaning and includes at least a segment of spectrum (e.g., radio frequency spectrum) in which channels are used or reserved for the same purpose.
[0062] The term "Wi-Fi" (or WiFi) encompasses the full range of its common meaning and includes at least wireless communication networks, or RATs, which are provided by and through wireless LAN (WLAN) access points to provide connectivity to the Internet. Most modern Wi-Fi networks (or WLAN networks) are based on the IEEE 802.11 standard and marketed under the name "Wi-Fi." Wi-Fi (WLAN) networks are distinct from cellular networks.
[0063] 3GPP access refers to access technologies (e.g., radio access technologies) specified by 3GPP standards. These access technologies include, but are not limited to, GSM / GPRS, LTE, LTE-A, and / or 5G NR. Generally speaking, 3GPP access refers to various types of cellular access technologies.
[0064] Non-3GPP access refers to any access technology (e.g., radio access technologies) not specified by 3GPP standards. These accesses include, but are not limited to, WiMAX, CDMA2000, Wi-Fi, WLAN, and / or fixed networks. Non-3GPP access can be categorized into two types: "trusted" and "untrusted." Trusted non-3GPP access can interact directly with the Evolved Packet Core (EPC) and / or 5G Core (5GC), while untrusted non-3GPP access interoperates with the EPC / 5GC via network entities such as Evolved Packet Data Gateways and / or 5G NR Gateways. Generally speaking, non-3GPP access refers to various types of non-cellular access technologies.
[0065] Automatic – refers to the action or operation performed by a computer system (e.g., software executed by the computer system) or device (e.g., circuits, programmable hardware elements, ASICs, etc.) without requiring direct specification or execution of the action or operation through user input. Therefore, the term "automatically" is the opposite of an operation performed or specified manually by a user, where the user provides input to directly perform the operation. An automatic process can be initiated by user-provided input, but the subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually," where the user specifies each action to be performed. For example, a user filling out a form by selecting each field and providing input specifying information (e.g., by typing information, selecting a checkbox, radio selection, etc.) is considered manually filling out the form, even though the computer system must update the form in response to the user's actions. The form can be automatically filled out by a computer system (e.g., software executed on the computer system) which analyzes the fields of the form and fills it out without any user input specifying answers for the fields. As indicated above, the user can invoke the automatic filling of the form but does not participate in the actual filling of the form (e.g., the user does not manually specify answers for the fields, but they are completed automatically). This manual provides various examples of operations that are automatically performed in response to actions taken by the user.
[0066] Approximately – refers to a value close to the correct or precise value. For example, approximately can mean a value within 1% to 10% of the precise (or expected) value. However, it should be noted that the actual threshold (or tolerance) can vary depending on the application. For example, in some implementations, “approximately” may mean within 0.1% of some specified or expected value, while in various other implementations, the threshold may be, for example, 2%, 3%, 5%, etc., depending on the expectations or requirements of the specific application.
[0067] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that at least partially overlaps. For example, concurrency can be achieved using “strong” or strict parallelism, where tasks are executed in parallel (at least partially) on corresponding computing elements; or using “weak parallelism,” where tasks are executed in an interleaved manner (e.g., by time multiplexing of execution threads).
[0068] Various components can be described as being “configured to” perform one or more tasks. In such contexts, “configured to” is a broad expression generally meaning “to have” a “structure” that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently performing one (e.g., a set of electrical conductors can be configured to electrically connect one module to another, even when the two modules are not connected). In some contexts, “configured to” can be a broad expression generally meaning a structure that “has” a “circuit” that performs one or more tasks during operation. Thus, a component can be configured to perform a task even when it is not currently switched on. Typically, the circuit forming the structure corresponding to “configured to” can include hardware circuitry. For ease of description, various components can be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to”. The description of a component configured to perform one or more tasks is explicitly intended not to invoke the interpretation of 35 U.S.SC §112(f) for that component.
[0069] Figure 1A and Figure 1B Communication system
[0070] Figure 1A A simplified exemplary wireless communication system according to some implementation schemes is shown. It should be noted that... Figure 1A The system described herein is merely one example of a possible system, and the features of this disclosure can be implemented in any of a variety of systems as needed.
[0071] like Figure 1A As shown, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N, etc., via a transmission medium. Each user equipment may be referred to herein as a "user equipment" (UE). Therefore, user equipment 106 is referred to as a UE or UE device.
[0072] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware for enabling wireless communication with UEs 106A to 106N.
[0073] The communication area (or coverage area) of a base station can be referred to as a "cell". Base station 102A and UE 106 can be configured to communicate via a transmission medium using any of a variety of Radio Access Technologies (RATs), also known as wireless communication technologies or telecommunications standards, such as GSM, UMTS (associated with air interfaces such as WCDMA or TD-SCDMA), LTE, LTE-A Advanced, 5G New Radio (5G NR), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc. Note that if base station 102A is implemented in an LTE environment, its alternative location can be referred to as an "eNodeB" or "eNB". Note that if base station 102A is implemented in a 5G NR environment, its alternative location can be referred to as a "gNodeB" or "gNB".
[0074] like Figure 1A As shown, base station 102A can also be configured to communicate with network 100 (e.g., in various possibilities, the core network of a cellular service provider, telecommunications networks such as the Public Switched Telephone Network (PSTN), and / or the Internet). Therefore, base station 102A can facilitate communication between user equipments and / or between user equipments and network 100. Specifically, cellular base station 102A can provide a UE 106 with various communication capabilities such as voice, SMS, and / or data services.
[0075] Base station 102A and other similar base stations (such as base stations 102B...102N) operating according to the same or different cellular communication standards can therefore be provided as a network of cells that can provide continuous or nearly continuous overlapping services to UE 106A-N and similar devices over a geographical area via one or more cellular communication standards.
[0076] Therefore, although base station 102A can act as such Figure 1A The diagram shows the "serving cell" of UEs 106A-N, but each UE 106 may also be able to receive signals (and possibly within its communication range) from one or more other cells (which may be provided by base stations 102B-N and / or any other base stations), which may be referred to as "neighboring cells". Such cells may also facilitate communication between user equipments and / or between user equipments and network 100. These cells may include "macro" cells, "micro" cells, "pecimen" cells, and / or any other cells of various other granularities providing service area size. For example, in Figure 1A Base stations 102A-B shown can be macro cells, while base station 102N can be a micro cell. Other configurations are also possible.
[0077] In some implementations, base station 102A may be a next-generation base station, such as a 5G New Radio (5G NR) base station or a "gNB". In some implementations, the gNB may be connected to a legacy evolved packet core (EPC) network and / or to a new radio communication core (NRC) network. Furthermore, the gNB cell may include one or more transition and receive points (TRPs). Additionally, a UE capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.
[0078] It should be noted that UE 106 can communicate using multiple wireless communication standards. For example, in addition to at least one cellular communication protocol (e.g., GSM, UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD, etc.), UE 106 can be configured to communicate using wireless networking (e.g., Wi-Fi) and / or peer-to-peer wireless communication protocols (e.g., Bluetooth, Wi-Fi peer-to-peer, etc.). If desired, UE 106 can also or alternatively be configured to communicate using one or more Global Navigation Satellite Systems (GNSS, such as GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or any other wireless communication protocol. Other combinations of wireless communication standards (including more than two wireless communication standards) are also possible.
[0079] Figure 1B User equipment 106 (e.g., one of devices 106A to 106N) communicating with base station 102 and access point 112 according to some embodiments is shown. UE 106 can be a device with cellular and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, handheld device, computer or tablet, or virtually any type of wireless device.
[0080] UE 106 may include a processor configured to execute program instructions stored in memory. UE 106 may execute any of the method embodiments of the present invention by executing such stored instructions. Alternatively or additionally, UE 106 may include programmable hardware elements, such as a field-programmable gate array (FPGA) configured to execute any of the method embodiments of the present invention or any portion thereof.
[0081] UE 106 may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, UE 106 may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / Advanced LTE, or 5G NR and / or GSM, LTE, Advanced LTE, or 5G NR using a single shared radio component. The shared radio may be coupled to a single antenna or to multiple antennas (e.g., for MIMO) for performing wireless communication. Typically, the radio component may include any combination of baseband processor, analog radio frequency (RF) signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.) or digital processing circuitry (e.g., for digital modulation and other digital processing). Similarly, the radio component may use the aforementioned hardware to implement one or more receive chains and transmit chains. For example, UE 106 may share one or more portions of the receive chain and / or transmit chain among various wireless communication technologies such as those discussed above.
[0082] In some implementations, UE 106 may include separate transmit and / or receive chains (e.g., including separate antennas and other radio components) for each wireless communication protocol configured to communicate therewith. As another possibility, UE 106 may include one or more radio components shared among multiple wireless communication protocols, as well as one or more radio components uniquely used by a single wireless communication protocol. For example, UE 106 may include shared radio components for communication using either LTE or 5G NR (or LTE or 1xRTT, or LTE or GSM), and separate radio components for communication using each of Wi-Fi and Bluetooth. Other configurations are also possible.
[0083] Figure 2 Block diagram of a base station
[0084] Figure 2 An exemplary block diagram of a base station 102 according to some embodiments is shown. It should be noted that... Figure 3 The base station shown is merely one example of a possible base station. For example... Figure 2 As shown, base station 102 may include processor 204 capable of executing program instructions for base station 102. Processor 204 may also be coupled to memory management unit (MMU) 240 or other circuitry or devices, which may be configured to receive addresses from processor 204 and translate those addresses into locations in memory (e.g., memory 260 and read-only memory (ROM) 250).
[0085] Base station 102 may include at least one network port 270. Network port 270 may be configured to be coupled to a telephone network and provide access rights as described above. Figure 1A and Figure 1B and Figure 2 The telephone network as described herein includes multiple devices (such as UE device 106).
[0086] Network port 270 (or an additional network port) may also be configured, or alternatively configured, to be coupled to a cellular network, such as the core network of a cellular service provider. The core network may provide mobility-related services and / or other services to multiple devices, such as UE device 106. In some cases, network port 270 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., in other UE devices served by the cellular service provider).
[0087] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or a “gNB”. In such implementations, base station 102 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network. Furthermore, base station 102 may be considered a 5G NR cell and may include one or more transition and receive points (TRPs). Additionally, UEs capable of operating according to 5G NR may connect to one or more TRPs within one or more gNBs.
[0088] Base station 102 may include at least one antenna 234 and possibly multiple antennas. The at least one antenna 234 may be configured to function as a wireless transceiver and may be further configured to communicate with UE device 106 via radio component 230. Antenna 234 communicates with radio component 230 via communication link 232. Communication link 232 may be a receive link, a transmit link, or both. Radio component 230 may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.
[0089] Base station 102 can be configured to perform wireless communication using multiple wireless communication standards. In some cases, base station 102 may include multiple radios that enable base station 102 to communicate according to multiple wireless communication technologies. For example, as one possibility, base station 102 may include an LTE radio component for performing communication according to LTE and a 5G NR radio component for performing communication according to 5G NR. In this case, base station 102 may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, base station 102 may include a multimode radio component capable of performing communication according to any of multiple wireless communication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTE and UMTS, LTE and CDMA2000, UMTS and GSM, etc.).
[0090] As further described herein, base station 102 may include hardware and software components for implementing or supporting embodiments of the features described herein. The processor 204 of base station 102 may be configured to implement or support some or all of the methods described herein, for example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable memory medium). Alternatively, processor 204 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array), or as an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 230, 232, 234, 240, 250, 260, 270, the processor 204 of base station 102 may be configured to implement or support some or all of the features described herein.
[0091] Furthermore, as described herein, processor 204 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 204. Therefore, processor 204 may include one or more integrated circuits (ICs) configured to perform the functions of processor 204. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of one or more processors 204.
[0092] Additionally, as described herein, the radio component 230 may comprise one or more processing elements. In other words, one or more processing elements may be included in the radio component 230. Therefore, the radio component 230 may include one or more integrated circuits (ICs) configured to perform the functions of the radio component 230. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the radio component 230.
[0093] Figure 3 Server block diagram
[0094] Figure 3 An exemplary block diagram of server 104 according to some implementation schemes is shown. It should be noted that... Figure 3 The server mentioned is merely one example of possible servers. For example... Figure 3 As shown, server 104 may include processor 344 capable of executing program instructions for server 104. Processor 344 may also be coupled to memory management unit (MMU) 374, which may be configured to receive addresses from processor 344 and translate those addresses into locations in memory (e.g., memory 364 and read-only memory (ROM) 354) or to other circuitry or devices.
[0095] Server 104 can be configured to provide network access functionality to multiple devices, such as base station 102, UE device 106, and / or UTM 108, for example, as further described herein.
[0096] In some implementations, server 104 may be part of a radio access network, such as a 5G New Radio (5G NR) access network. In some implementations, server 104 may be connected to a legacy evolved packet core (EPC) network and / or to an NR core (NRC) network.
[0097] As further described herein, server 104 may include hardware and software components for implementing or supporting the implementation of the features described herein. Processor 344 of server 104 may be configured, for example, to implement or support some or all of the methods described herein by executing program instructions stored on a storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 344 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or configured as an ASIC (Application-Specific Integrated Circuit) or a combination thereof. Alternatively (or in addition), in conjunction with one or more of other components 354, 364, and / or 374, processor 344 of server 104 may be configured to implement or support some or all of the features described herein.
[0098] Furthermore, as described herein, processor 344 may comprise one or more processing elements. In other words, one or more processing elements may be included in processor 344. Therefore, processor 344 may include one or more integrated circuits (ICs) configured to perform the functions of processor 344. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 344.
[0099] Figure 4 : UE block diagram
[0100] Figure 4 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 4 The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices, as well as other devices. Figure 4 As shown, the communication device 106 may include a set of components 400 configured to perform core functions. For example, this set of components may be implemented as a system-on-a-chip (SOC), which may include portions for various purposes. Alternatively, the set of components 400 may be implemented as individual components or groups of components for various purposes. This set of components 400 may be (e.g., communicatively; directly or indirectly) coupled to various other circuitry of the communication device 106.
[0101] For example, communication device 106 may include various types of memory (e.g., including NAND flash memory 410), input / output interfaces such as connector I / F 420 (e.g., for connection to a computer system; docking station; charging station; input devices such as microphone, camera, keyboard; output devices such as speaker; etc.), a display 460 that may be integrated with or external to communication device 106, and cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). TM (and WLAN circuitry). In some embodiments, the communication device 106 may include wired communication circuitry (not shown), such as, for example, a network interface card for Ethernet.
[0102] Cellular communication circuit 430 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as Figure 4 Antennas 435 and 436 are shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively; directly or indirectly) to one or more antennas, such as... Figure 4 Antennas 437 and 438 are shown. Alternatively, short-range to mid-range wireless communication circuitry 429 may be coupled to antennas 435 and 436, in addition to (e.g., communicatively grounded; directly or indirectly) being coupled to antennas 437 and 438, or as an alternative (e.g., communicatively grounded; directly or indirectly). Short-range to mid-range wireless communication circuitry 429 and / or cellular communication circuitry 430 may include multiple receive chains and / or multiple transmit chains for receiving and / or transmitting multiple spatial streams, such as in a multiple-input multiple-output (MIMO) configuration.
[0103] In some embodiments, as further described below, the cellular communication circuit 430 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). Furthermore, in some embodiments, the cellular communication circuit 430 may include a single transmit chain that can be switched between radio components dedicated to a particular RAT. For example, a first radio component may be dedicated to a first RAT, such as LTE, and can communicate with a dedicated receive chain and a transmit chain shared with additional radio components, such as a second radio component that may be dedicated to a second RAT (e.g., 5G NR) and can communicate with a dedicated receive chain and a shared transmit chain.
[0104] The communication device 106 may also include one or more user interface elements and / or be configured to be used with one or more user interface elements. User interface elements may include any of a variety of components such as a display 460 (which may be a touch screen display), a keyboard (which may be a separate keyboard or may be implemented as part of the touch screen display), a mouse, a microphone and / or a speaker, one or more cameras, one or more buttons, and / or any of a variety of other components capable of providing information to the user and / or receiving or interpreting user input.
[0105] The communication device 106 may also include one or more smart cards 445 with SIM (Subscriber Identity Module) functionality, such as one or more UICC cards (one or more general-purpose integrated circuit cards) 445. It should be noted that the term "SIM" or "SIM entity" is intended to include any of various types of SIM implementations or SIM functions, such as one or more UICC cards 445, one or more eUICCs, one or more eSIMs, removable or embedded, etc. In some embodiments, the UE 106 may include at least two SIMs. Each SIM may execute one or more SIM applications and / or otherwise implement SIM functionality. Thus, each SIM may be a single smart card that can be embedded, for example, soldered to a circuit board in the UE 106, or each SIM 410 may be implemented as a removable smart card. Therefore, a SIM may be one or more removable smart cards (such as UICC cards, sometimes referred to as "SIM cards"), and / or SIM 410 may be one or more embedded cards (such as embedded UICCs (eUICCs), sometimes referred to as "eSIMs" or "eSIM cards"). In some implementations (such as when the SIM includes an eUICC), one or more SIMs within the SIM can implement embedded SIM (eSIM) functionality; in such implementations, a single SIM within the SIM can execute multiple SIM applications. Each SIM may include components such as a processor and / or memory; instructions for performing SIM / eSIM functionality may be stored in memory and executed by the processor. In some implementations, UE 106 may include, as needed, a combination of removable smart cards and fixed / non-removable smart cards (such as one or more eUICC cards implementing eSIM functionality). For example, UE 106 may include two embedded SIMs, two removable SIMs, or a combination of one embedded SIM and one removable SIM. Various other SIM configurations are also envisioned.
[0106] As described above, in some implementations, UE 106 may include two or more SIMs. Including two or more SIMs in UE 106 allows UE 106 to support two different phone numbers and allows UE 106 to communicate on two or more corresponding networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM 106 may support a second RAT such as 5G NR. Other implementations and RATs are also possible. In some implementations, when UE 106 includes two SIMs, UE 106 may support Dual SIM Dual Standby (DSDA) functionality. DSDA functionality allows UE 106 to connect to two networks simultaneously (and use two different RATs), or allows two connections supported by two different SIMs using the same or different RATs to be maintained simultaneously on the same or different networks. DSDA functionality also allows UE 106 to receive voice calls or data traffic simultaneously on either phone number. In some implementations, voice calls may be packet-switched communications. In other words, voice calls can be received using LTE-based Voice (VoLTE) technology and / or NR-based Voice (VoNR) technology. In some implementations, UE 106 may support Dual SIM Dual Standby (DSDS) functionality. DSDS functionality allows either of the two SIMs in UE 106 to remain in standby while awaiting a voice call and / or data connection. In DSDS, when a call / data connection is established on one SIM, the other SIM is no longer active. In some implementations, DSDx functionality (DSDA or DSDS functionality) can be implemented using a single SIM (e.g., eUICC) that performs multiple SIM applications for different carriers and / or RATs.
[0107] like Figure 4 As shown, the SOC 400 may include a processor 402 and a display circuit 404. The processor executes program instructions for the communication device 106, and the display circuit performs graphics processing and provides display signals to the display 460. The processor 402 may also be coupled to a memory management unit (MMU) 440 (which may be configured to receive addresses from the processor 402 and translate those addresses into locations in memory (e.g., memory 406, read-only memory (ROM) 450, NAND flash memory 410)) and / or coupled to other circuitry or devices (such as the display circuit 404, short-to-medium range wireless communication circuitry 429, cellular communication circuitry 430, connector I / F 420, and / or display 460). The MMU 440 may be configured to perform memory protection and page table translation or setup. In some embodiments, the MMU 440 may be included as part of the processor 402.
[0108] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuits. Communication device 106 can be configured to perform methods for CCA power signaling during COT sharing as further described herein, for example, in 5G NR systems and later.
[0109] As described herein, communication device 106 may include hardware and software components for implementing the features described above in communication device 106 to transmit a scheduling profile for power saving to a network. For example, by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium), processor 402 of communication device 106 may be configured to implement some or all of the features described herein. Alternatively (or otherwise), processor 402 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array) or an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), in conjunction with one or more other components 400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460, processor 402 of communication device 106 may be configured to implement some or all of the features described herein. Furthermore, as described herein, processor 402 may include one or more processing elements. Therefore, processor 402 may include one or more integrated circuits (ICs) configured to perform the functions of processor 402. In addition, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.
[0110] Furthermore, as described herein, the cellular communication circuit 430 and the short-to-medium-range wireless communication circuit 429 may each include one or more processing elements. In other words, one or more processing elements may be included in the cellular communication circuit 430, and similarly, one or more processing elements may be included in the short-to-medium-range wireless communication circuit 429. Therefore, the cellular communication circuit 430 may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit 430. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the cellular communication circuit 430. Similarly, the short-to-medium-range wireless communication circuit 429 may include one or more ICs configured to perform the functions of the short-to-medium-range wireless communication circuit 429. Furthermore, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of the short-to-medium-range wireless communication circuit 429.
[0111] Figure 5 Block diagram of cellular communication circuit
[0112] Figure 5An exemplary simplified block diagram of a cellular communication circuit according to some embodiments is shown. It should be noted that... Figure 5 The block diagram of the cellular communication circuit is merely one example of a possible cellular communication circuit. According to the implementation, the cellular communication circuit 530 (which may be the cellular communication circuit 430) may be included in a communication device such as the communication device 106 described above. As mentioned above, among other devices, the communication device 106 may be a user equipment (UE) device, a mobile device or mobile station, a wireless device or wireless station, a desktop computer or computing device, a mobile computing device (e.g., a laptop, notebook, or portable computing device), a tablet computer, and / or a combination of these devices.
[0113] Cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a to 435b and 436 are shown in the diagram. In some embodiments, the cellular communication circuitry 530 may include dedicated receive chains for multiple RATs (including and / or coupled to (e.g., communication ground; directly or indirectly) dedicated processors and / or radio components) (e.g., a first receive chain for LTE and a second receive chain for 5G-NR). For example, as... Figure 5 As shown, the cellular communication circuit 530 may include a modem 510 and a modem 520. The modem 510 may be configured for communication according to a first RAT, such as LTE or LTE-A, and the modem 520 may be configured for communication according to a second RAT, such as 5G NR.
[0114] like Figure 5 As shown, modem 510 may include one or more processors 512 and memory 516 communicating with processors 512. Modem 510 may communicate with radio frequency (RF) front end 530. RF front end 530 may include circuitry for transmitting and receiving radio signals. For example, RF front end 530 may include receiver circuitry (RX) 532 and transmitter circuitry (TX) 534. In some embodiments, receiver circuitry 532 may communicate with downlink (DL) front end 550, which may include circuitry for receiving radio signals via antenna 335a.
[0115] Similarly, modem 520 may include one or more processors 522 and memory 526 communicating with processor 522. Modem 520 may communicate with RF front end 540. RF front end 540 may include circuitry for transmitting and receiving radio signals. For example, RF front end 540 may include receiving circuitry 542 and transmitting circuitry 544. In some embodiments, receiving circuitry 542 may communicate with DL front end 560, which may include circuitry for receiving radio signals via antenna 335b.
[0116] In some implementations, switch 570 may couple transmitting circuitry 534 to uplink (UL) front-end 572. Additionally, switch 570 may couple transmitting circuitry 544 to UL front-end 572. UL front-end 572 may include circuitry for transmitting radio signals via antenna 336. Therefore, when cellular communication circuitry 530 receives an instruction to transmit according to a first RAT (e.g., supported by modem 510), switch 570 may be switched to a first state allowing modem 510 to transmit signals according to the first RAT (e.g., via a transmission chain including transmitting circuitry 534 and UL front-end 572). Similarly, when cellular communication circuitry 530 receives an instruction to transmit according to a second RAT (e.g., supported by modem 520), switch 570 may be switched to a second state allowing modem 520 to transmit signals according to the second RAT (e.g., via a transmission chain including transmitting circuitry 544 and UL front-end 572).
[0117] In some implementations, the cellular communication circuit 530 may be configured to perform methods for CCA power signaling during COT sharing as further described herein, for example in 5G NR systems and later.
[0118] As described herein, modem 510 may include hardware and software components for implementing the features described above or for UL data used in time-division multiplexing NSA NR operation, as well as various other techniques described herein. For example, processor 512 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 512 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or otherwise), processor 512 may be configured to implement some or all of the features described herein by combining with one or more of other components 530, 532, 534, 550, 570, 572, 335, and 336.
[0119] Furthermore, as described herein, processor 512 may include one or more processing elements. Therefore, processor 512 may include one or more integrated circuits (ICs) configured to perform the functions of processor 512. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 512.
[0120] As described herein, modem 520 may include hardware and software components designed to implement the aforementioned features for transmitting power-saving scheduling profiles to the network, as well as various other technologies described herein. For example, processor 522 may be configured to implement some or all of the features described herein by executing program instructions stored on a memory medium (e.g., a non-transitory computer-readable storage medium). Alternatively (or otherwise), processor 522 may be configured as a programmable hardware element such as a FPGA (Field-Programmable Gate Array) or as an ASIC (Application-Specific Integrated Circuit). Alternatively (or additionally), processor 522 may be configured to implement some or all of the features described herein by combining one or more of other components 540, 542, 544, 550, 570, 572, 335, and 336.
[0121] Furthermore, as described herein, processor 522 may include one or more processing elements. Therefore, processor 522 may include one or more integrated circuits (ICs) configured to perform the functions of processor 522. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 522.
[0122] Figure 6A , Figure 6B and Figure 7 5G Core Network Architecture—Interoperability with Wi-Fi
[0123] In some implementations, access to the 5G core network (CN) can be made via (or through) cellular connections / interfaces (e.g., via 3GPP communication architectures / protocols) and non-cellular connections / interfaces (e.g., non-3GPP access architectures / protocols such as Wi-Fi connections). Figure 6A Examples of 5G network architectures according to some implementation schemes are shown, which combine 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. Figure 6AAs shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to a non-3GPP Interoperability Function (N3IWF) 603 network entity. N3IWF may include a connection to the 5G CN's core access and mobility management function (AMF) 605. AMF 605 may include an instance of 5G mobility management (5G MM) functions associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register for access simultaneously via gNB 604 and AP 612. As shown in 6A, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 620, Short Message Service Function (SMSF) 622, Application Function (AF) 624, Unified Data Management (UDM) 626, Policy Control Function (PCF) 628, and / or Authentication Server Function (AUSF) 630). It should be noted that these functional entities may also be supported by the 5G CN's Session Management Functions (SMF) 606a and SMF 606b. AMF 605 may connect to (or communicate with) SMF 606a. Furthermore, gNB 604 may communicate with (or connect to) User Plane Function (UPF) 608a, which may also communicate with SMF 606a. Similarly, N3IWF 603 may communicate with UPF 608b, which may also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and the Internet Protocol (IP) Multimedia Subsystem / IP Multimedia Core Network Subsystem (IMS) Core Network 610.
[0124] Figure 6B Examples of 5G network architectures according to some implementation schemes are shown, which combine dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN with non-3GPP access. Figure 6BAs shown, a user equipment device (e.g., such as UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB 604 or eNB 602, which may be base station 102) and an access point (such as AP 612). AP 612 may include a connection to the Internet 600 and a connection to the N3IWF 603 network entity. N3IWF may include a connection to the AMF 605 of the 5G CN. AMF 605 may include an instance of 5G MM functionality associated with UE 106. Additionally, the RAN (e.g., gNB 604) may also have a connection to AMF 605. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register for access simultaneously via gNB 604 and AP 612. Furthermore, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via eNB 602) and a 5G network (e.g., via gNB 604). Figure 6B As shown, eNB 602 may have connections to Mobility Management Entity (MME) 642 and Service Gateway (SGW) 644. MME 642 may have connections to both SGW 644 and AMF 605. Additionally, SGW 644 may have connections to both SMF 606a and UPF 608a. Figure 6B As shown, AMF 605 may include one or more functional entities associated with the 5G CN (e.g., NSSF 620, SMSF 622, AF 624, UDM 626, PCF 628, and / or AUSF 630). It should be noted that UDM 626 may also include Home Subscriber Server (HSS) functionality, and PCF may also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities may also be supported by SMF 606a and SMF 606b of the 5G CN. AMF 606 may connect to (or communicate with) SMF 606a. Furthermore, gNB 604 may communicate with (or connect to) UPF 608a, which may also communicate with SMF 606a. Similarly, N3IWF 603 may communicate with UPF 608b, which may also communicate with SMF 606b. Both UPFs can communicate with data networks (e.g., DN 610a and 610b) and / or the Internet 600 and IMS core network 610.
[0125] It should be noted that, in various implementations, one or more of the network entities described above may be configured to perform methods for improving security checks in 5G NR networks, including mechanisms such as those for CCA power signaling during COT sharing, as further described herein, for example, in 5G NR systems and later versions.
[0126] Figure 7 An example of a baseband processor architecture for a UE (e.g., such as UE 106) according to some implementation schemes is shown. Figure 7 The baseband processor architecture 700 described herein can be implemented on one or more radio components as described above (e.g., radio components 429 and / or 430 described above) or modems (e.g., modems 510 and / or 520). Figure 7 As shown, the Non-Access Stratum (NAS) 710 may include a 5G NAS 720 and a traditional NAS 750. The traditional NAS 750 may include communication connections with the traditional Access Stratum (AS) 770. The 5G NAS 720 may include communication connections with a 5G AS 740, a non-3GPP AS 730, and a Wi-Fi AS 732. The 5G NAS 720 may include functional entities associated with both access strata. Therefore, the 5G NAS 720 may include multiple 5G MM entities 726 and 728, and 5G Session Management (SM) entities 722 and 724. The traditional NAS 750 may include functional entities such as Short Message Service (SMS) entity 752, Evolved Packet System (EPS) Session Management (ESM) entity 754, Session Management (SM) entity 756, EPS Mobility Management (EMM) entity 758, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 760. In addition, the traditional AS 770 may include functional entities such as LTE AS 772, UMTS AS 774 and / or GSM / GPRS AS776.
[0127] Therefore, the 700 baseband processor architecture allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access). It should be noted that... Figure 7 As shown, 5G MM can maintain separate connection management and registration management state machines for each connection. Additionally, a device (e.g., UE 106) can register to a single PLMN (e.g., 5GCN) using both 5G cellular and non-cellular access. Furthermore, a device can be in a connected state in one access and an idle state in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.
[0128] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS may be configured to perform methods, such as those for CCA power signaling during COT sharing as further described herein, for example, in 5G NR systems and later.
[0129] CCA power signaling during COT sharing
[0130] In current implementations, for example as defined in EN 302 567, adaptability (media access protocol) is a mechanism designed to facilitate spectrum sharing between devices in a wireless network. This mechanism requires a listen-before-speak (LBT) process to facilitate spectrum sharing. The LBT process requires the device initiating a transmission to perform an idle channel assessment (CCA) check on the working channel before any transmission or transmission burst on the working channel. It should be noted that when a device detects that the working channel is occupied, it may not transmit on that channel, and may also prevent other devices from transmitting on that channel. It should be further noted that when the CCA check determines that the channel is no longer occupied and transmission is delayed within several empty time slots defined by the CCA check, the device can resume transmission and / or enable other devices to transmit on the channel. Additionally, the LBT process specifies that the device initiating the transmission will use an energy detection mechanism to perform the CCA check, and if the energy level in the working channel exceeds a threshold corresponding to a power level as defined in EN 302 567, the working channel will be considered occupied for a time slot of five microseconds. In addition, the device will observe the working channel over the duration of the CCA observation time, which is measured through multiple time slots.
[0131] EN 302 567 further defines that a CCA check is initiated at the end of the occupied time slot of the working channel, and a transmission delay occurs when the working channel is observed to be unoccupied for at least eight microseconds, wherein the transmission delay lasts for at least a random number (from 0 to a maximum number) of empty time slot periods. Note that the maximum number cannot be less than 3.
[0132] EN 302 567 also defines the total time a device using the working channel to initiate a transmission as the Channel Occupied Time (COT). This (COT) must be less than five milliseconds, after which a new CCA check will be required. It should be noted that after correctly receiving a packet intended for use by the device, the device may skip the CCA check and immediately continue transmission in response to the received frame. However, the device's continuous transmission sequence cannot exceed five milliseconds of COT without a new CCA check.
[0133] Furthermore, EN 302 567 defines the energy detection threshold for CCA inspection as -80dBm + 10 × log10 (operating channel bandwidth (in MHz)) + 10 × log10 (Pmax / Pout). Pout is the RF output power (e.g., the average equivalent isotropic radiated power (EIRP) of the device during a transmission burst), and Pmax is the RF output power limit, where Pout is less than or equal to Pmax.
[0134] In 3GPP 5th Generation (5G) New Radio (NR) Release 17, EN 302 567 is assumed to be the benchmark for developing channel access mechanisms that assume beam-based operation in order to comply with regulatory requirements for unlicensed spectrum applicable to frequencies between 52.6 GHz and 71 GHz (this unlicensed spectrum may be considered as part of 5G NR Frequency Range 2 (FR2), or as an increase to FR2 (FR2x) and / or 5G NR Frequency Range 3 (FR3)). As mentioned above, the benchmark energy detection (ED) threshold can be calculated as -80 dBm + 10 × log10 (operating channel bandwidth (in MHz)) + 10 × log10 (Pmax / Pout). However, it is not defined whether Pout is the device's maximum output EIRP or the instantaneous output EIRP. Furthermore, the operating channel bandwidth is not defined, nor is the ED threshold defined when the COT has time-varying transmission beams and varying EIRPs.
[0135] Additionally, in 3GPP 5G NR, the UE can initiate COT sharing. Different mechanisms are defined depending on whether the base station has configured an ED threshold for COT sharing. For example, if an ED threshold is configured, the UE can provide a row index in the Radio Resource Control (RRC) configuration table, where duration, offset, and CAPC are jointly encoded, and the RRC parameter cg-COT-SharingList-r16 (e.g., the table) has a value range of 1709. As another example, if an ED threshold is not configured, a single Information Element (IE) can indicate whether slot / symbol X is suitable for COT sharing, where X is configured by RRC signaling in symbols from the end of the slot transmitting CG-UCI.
[0136] It should be noted that 3GPP TS 38.101 6.2.1.3 defines the maximum output power radiated by a User Equipment (UE) within FR2 for any transmission bandwidth within the channel bandwidth of a non-carrier aggregation configuration. Furthermore, unlike in Frequency Range 1 (FR1), the maximum EIRP of the UE has a wider range in FR2.
[0137] The implementations described herein provide systems, methods, and mechanisms for supporting UE CCA power signaling during COT sharing, including systems, methods, and mechanisms for UEs to report the maximum average equivalent isotropic radiated power (EIRP) for COT sharing thresholds, the network-configured COT sharing thresholds, the Pout for COT sharing, and the CCA bandwidth for CCA sharing. In some implementations, the UE may report the maximum peak EIRP to the base station. It should be noted that the maximum EIRP may be UE-specific and based on individual UE designs.
[0138] In some implementations, the report format may be a UE capability and / or parameter, such as a modification and / or addition to a UE capability defined in 3GPP TS 38.306 4.2.7.2, for example, a BandNR capability. In some implementations, the report may be on top of and / or added to a power class report. For example, parameters such as ue-peakEIRP-v17 may be reported for the frequency range of 52.6 GHz to 71 GHz (e.g., as part of FR2, FR2x, and / or FR3). It should be noted that the UE may support and / or report peak EIRP in the corresponding power class, for example, via parameters such as the peakEIRP-v17 parameter added to and / or included in the BandNR capability, as defined in 3GPP TS 38.306 4.2.7.2. As another example, the report may be part of the SharedSpectrumChAccessParamsPerBand capability, for example, as defined in 3GPP TS 38.0306 4.2.7.2a. Therefore, parameters such as ue-peakEIRP-v17 can be reported for the frequency range of 52.6 GHz to 71 GHz. It should be noted that the UE can support and / or report the UE's maximum peak EIRP for ul-DL-COT-Sharing-r17, for example, via parameters such as the peakEIRP-v17 parameter added to and / or included in the SharedSpectrumChAccessParamsPerBand capability, as defined in 3GPP TS 38.306 4.2.7.2a.
[0139] In some implementations, the base station (such as base station 102) can configure a COT sharing threshold. For example, for dynamic uplink granting or configured uplink granting, the base station can use one of the RRC signaling in UE-specific Radio Resource Control (RRC) signaling to configure the Pout value for idle channel assessment (CCA), or use cell-specific signaling to configure the Pout for all UEs served by the base station. It should be noted that when using UE-specific RRC signaling, the Pout value may be reported at least partially based on the UE's maximum EIRP. In some cases, the Pout value may be equal to and / or less than the UE's maximum EIRP, for example, as reported to the base station via parameters (such as peakEIRP-v17), as described above. It should be noted that when using cell-specific signaling, Pout may be greater than the UE's maximum EIRP. For example, Pout may be based at least partially on the base station's maximum EIRP. It should be further noted that for COT acquired by the UL, this may result in a tightened Energy Detection Threshold (EDT), and / or for COT acquired by the UE, may reduce the probability of contention success. As an alternative, the base station may not configure the Pout value used in CCA, but instead use default values, such as a specific maximum EIRP reported by the UE. It should be noted that base station sharing of COT may be limited to the Common Transmission Control Information (TCI) state and the same Pout.
[0140] In some implementations, for configuration-granted uplink COT sharing, the UE may utilize specific EIRP and beam detection for transmission bursts to perform directed listen-before-speak (LBT). Pout can then be reported as feedback in the configuration-granted (CG) uplink control information (UCI) for COT sharing. In some implementations, the CG-UCI may include parameters related to COT sharing, such as Pout and TCI states, as well as COT duration and offset. The CG-UCI may also include other parameters, such as the Hybrid Automatic Repeat Request (HARQ) identifier (ID), New Data Indicator (NDI), and / or Redundancy Version (RV). The base station may share the UE-shared COT for PDCCH / PDSCH transmissions within, for example, the TCI states and Pout limits reported by the UE in the CG-UCI.
[0141] In some implementations, for dynamically authorized uplink COT sharing, the base station may know the UE power and EIRP with UL power control. In such cases, the UE may not need to report the Pout for COT sharing. In other cases, the UE may report the Pout for COT sharing based on one or more events via a Media Access Control (MAC) control element (CE). The MAC CE may indicate the Pout for COT sharing, and may be sent if and / or when the EIRP exceeds a threshold compared to the closed-loop power control setting. Note that the threshold may be configured via RRC signaling. Additionally, if and / or when the UE does not report the Pout for COT sharing, the base station may use the power value in the uplink power control.
[0142] In some implementations, CCA bandwidth may be based on channel bandwidth and / or bandwidth portion (BWP) bandwidth. However, in some implementations, the UE may indicate to the base station whether COT is acquired based on channel bandwidth or BWP bandwidth, for example via CG-UCI. The CG-UCI may include parameters related to COT sharing, such as a bit indicating channel bandwidth or CG Physical Uplink Shared Channel (PUSCH) transmission bandwidth, Pout and TCI states, and COT duration and offset. The CG-UCI may also include other parameters such as HARQ ID, NDI, and / or RV. It should be noted that for base station COT sharing, when using CG PUSCH transmission bandwidth to acquire COT, base station transmission may be limited to PUSCH transmission bandwidth, including Physical Downlink Control Channel (PDCCH) and Physical Downlink Shared Channel (PDSCH). It should be noted that limiting the base station to PUSCH transmission bandwidth (including PDCCH and PDSCH) may adversely and / or undesirably limit the PDCCH control resource set. (CoreSet) configuration. Therefore, in some cases, base station transmission may be limited to PUSCH transmission bandwidth, but at least in part based on CoreSet configuration, PDCCH may be larger.
[0143] Figure 8 A block diagram illustrating an example of a method for idle channel access (CCA) power signaling during channel occupancy time (COT) sharing, according to some implementation schemes, is shown. Among other things, Figure 8 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be performed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be performed as needed. Figure 8 As shown, this method can be operated as follows.
[0144] At 802, a UE (such as UE 106) may report the maximum peak average equivalent isotropic radiated power (EIRP) for COT sharing to a base station (such as base station 102). The maximum EIRP for COT sharing may be reported as a UE capability and / or via a UE capability. UE capabilities may be parameters such as peakEIRP-v17. The maximum EIRP may be reported for a frequency range between 52.6 GHz and 71 GHz. The maximum EIRP may be included in a power class report and / or may be specific to a power class. The maximum EIRP may be included in the SharedSpectrumChAccessParamsPerBand parameter / capability and / or the BandNR parameter / capability.
[0145] At 804, the UE may receive a Pout value from the base station for CCA. The Pout value may specify the EIRP used for transmission burst. This Pout value may be at least partially based on UE capabilities. In some embodiments, the Pout value may be less than or equal to the maximum EIRP for COT sharing reported via UE capabilities. In some embodiments, the Pout value may be received via radio resource control signaling and / or via cell-specific signaling. In some embodiments, for example, when the Pout value is received via cell-specific signaling, the Pout value may be greater than or equal to the maximum EIRP for COT sharing reported via UE capabilities. In such embodiments, the Pout value may also be at least partially based on the base station's maximum EIRP. The Pout value may be represented by any, any combination of, and / or all of the following (e.g., at least one of the following and / or one or more of the following): Type 1 or Type 2 Configuration Grant (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Activated Downlink Control Information (DCI) information scrambled with Configuration Scheduling (CS) Radio Network Temporary Identifier- (RNTI) for Type 2 Configuration Grant (CG); and / or DCI format 0-1 or 0-2 for Dynamic Physical Uplink Shared Channel (PUSCH) grant.
[0146] At 806, the UE can report the actual EIRP used for CCA to the base station to obtain COT.
[0147] In some implementations, the CCA bandwidth may be based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
[0148] In some implementations, the UE may indicate to the base station whether COT is acquired based on channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth. In such implementations, indicating to the base station whether COT is acquired based on channel bandwidth or BWP bandwidth may include transmitting a Configuration Grant (CG) Uplink Control Indicator (UCI) to the base station. The CG UCI may include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a bit indicating the channel bandwidth or CG Physical Uplink Shared Channel (PUSCH) transmission bandwidth, a Pout value, Transmission Control Information (TCI) status, COT duration, and / or COT offset. In some implementations, the CG UCI may also include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a hybrid Automatic Repeat Request (HARQ) identifier (ID), a New Data Indicator (NDI), and / or Redundancy Version (RV).
[0149] In some implementations, the UE may indicate to the base station the actual Pout and beam direction (e.g., TCI status) used to acquire COT. To indicate the actual Pout, the UE may transmit a Configuration Grant (CG) Uplink Control Indicator (UCI) to the base station. The CG UCI may include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a bit indicating the channel bandwidth or the CG Physical Uplink Shared Channel (PUSCH) transmission bandwidth, the actual Pout value, the Transmission Control Information (TCI) status, the COT duration, and / or the COT offset. In some implementations, the CG UCI may also include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a hybrid Automatic Repeat Request (HARQ) identifier (ID), a New Data Indicator (NDI), and / or a Redundancy Version (RV).
[0150] In some implementations, the UE can detect that the equivalent isotropic radiated power (EIRP) exceeds a threshold and report a Pout value for channel occupancy time (COT) sharing to the base station. The Pout value can specify the EIRP used for transmission bursts. The Pout value can be reported via a Media Access Control (MAC) control element (CE). Furthermore, the threshold can be based at least in part on closed-loop power control settings. Additionally, the threshold can be configured via Radio Resource Control (RRC) signaling.
[0151] Figure 9 A block diagram illustrating an example of a method for configuring licensed (CG) uplink channel occupancy time (COT) sharing according to some implementation schemes is shown. Among other things, Figure 9The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. Figure 9 As shown, this method can be operated as follows.
[0152] At 902, a UE (such as UE 106) can perform directed listen-before-speak (LBT) by utilizing a specific peak-average equivalent isotropic radiated power (EIRP) and beam detection for transmitting bursts.
[0153] At 904, the UE may report a Pout value for COT sharing to a base station (such as base station 102). This Pout value may be at least partially based on a directional LBT. The Pout value may specify the EIRP used for the transmission burst. In some embodiments, the Pout value may be reported for a frequency range between 52.6 GHz and 71 GHz. In some embodiments, the Pout value may be reported via a CG Uplink Control Indicator (UCI). The CG UCI may include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): Pout value, Transmission Control Information (TCI) status, COT duration, and / or COT offset. In some embodiments, the CG UCI may also include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a hybrid Automatic Repeat Request (HARQ) identifier (ID), a New Data Indicator (NDI), and / or a Redundancy Version (RV). In some implementations, the base station may share the COT for transmission of the Physical Downlink Control Channel (PDCCH) and / or Physical Downlink Shared Channel (PDSCH) within the Transmission Control Information (TCI) status and Pout limits reported by the UE in the CG-UCI.
[0154] In some implementations, the CCA bandwidth may be based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
[0155] In some implementations, the UE may indicate to the base station whether COT is acquired based on channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth. In such implementations, indicating to the base station whether COT is acquired based on channel bandwidth or BWP bandwidth may include transmitting a Configuration Grant (CG) Uplink Control Indicator (UCI) to the base station. The CG UCI may include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a bit indicating the channel bandwidth or CG Physical Uplink Shared Channel (PUSCH) transmission bandwidth, a Pout value, Transmission Control Information (TCI) status, COT duration, and / or COT offset. In some implementations, the CG UCI may also include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a hybrid Automatic Repeat Request (HARQ) identifier (ID), a New Data Indicator (NDI), and / or Redundancy Version (RV).
[0156] In some implementations, the UE may receive a Pout value from the base station for Clear Channel Assessment (CCA), wherein the Pout value for CCA is at least partially based on the reported Pout value. The Pout value may be represented via any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a Type 1 or Type 2 Configuration Grant (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Active Downlink Control Information (DCI) scrambled with a Configuration Scheduling (CS) Radio Network Temporary Identifier- (RNTI) for Type 2 Configuration Grant (CG); and / or DCI format 0-1 or 0-2 for Dynamic Physical Uplink Shared Channel (PUSCH) grant.
[0157] Figure 9 A block diagram illustrating an example of a method for sharing Dynamic Grant (DG) uplink Channel Occupancy Time (COT) according to some implementation schemes is shown. Among other things, Figure 9 The method shown can also be used with any of the systems, methods, or devices shown in the figures. In various embodiments, some of the method elements shown may be executed concurrently in a different order than that shown, or may be omitted. Additional method elements may also be executed as needed. Figure 10 As shown, this method can be operated as follows.
[0158] At point 1002, the UE (such as UE 106) can detect that the equivalent isotropic radiated power (EIRP) exceeds a threshold. This threshold may be based at least in part on a closed-loop power control setting. In some implementations, this threshold may be configured via radio resource control (RRC) signaling.
[0159] At location 1004, the UE can report a Pout value for COT sharing to a base station (such as base station 102). The Pout value can specify the EIRP used for transmission bursts. In some implementations, the Pout value can be reported for a frequency range between 52.6 GHz and 71 GHz. In some implementations, the Pout value can be reported via a Media Access Control (MAC) control element.
[0160] In some implementations, when the UE does not report the Pout value, the base station can use the power value associated with uplink power control as the Pout value.
[0161] In some implementations, the CCA bandwidth may be based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
[0162] In some implementations, the UE may indicate to the base station whether COT is acquired based on channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth. In such implementations, indicating to the base station whether COT is acquired based on channel bandwidth or BWP bandwidth may include transmitting a Configuration Grant (CG) Uplink Control Indicator (UCI) to the base station. The CG UCI may include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a bit indicating the channel bandwidth or CG Physical Uplink Shared Channel (PUSCH) transmission bandwidth, a Pout value, Transmission Control Information (TCI) status, COT duration, and / or COT offset. In some implementations, the CG UCI may also include any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a hybrid Automatic Repeat Request (HARQ) identifier (ID), a New Data Indicator (NDI), and / or Redundancy Version (RV).
[0163] In some implementations, the UE may receive a Pout value from the base station for Clear Channel Assessment (CCA), wherein the Pout value for CCA is at least partially based on the reported Pout value. The Pout value may be represented via any, any combination of, and / or all of the following (e.g., at least one and / or one or more of the following): a Type 1 or Type 2 Configuration Grant (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Active Downlink Control Information (DCI) scrambled with a Configuration Scheduling (CS) Radio Network Temporary Identifier- (RNTI) for Type 2 Configuration Grant (CG); and / or DCI format 0-1 or 0-2 for Dynamic Physical Uplink Shared Channel (PUSCH) grant.
[0164] As is widely recognized, the use of personally identifiable information should comply with privacy policies and practices that are generally accepted to meet or exceed industry or governmental requirements for protecting user privacy. Specifically, personally identifiable information data should be managed and processed to minimize the risk of unintentional or unauthorized access or use, and the nature of authorized use should be clearly explained to users.
[0165] Embodiments of this disclosure may be implemented in any of a variety of forms. For example, some embodiments may be implemented as computer-implemented methods, computer-readable storage media, or computer systems. Other embodiments may be implemented using one or more custom-designed hardware devices such as ASICs. Other embodiments may be implemented using one or more programmable hardware elements such as FPGAs.
[0166] In some embodiments, a non-transitory computer-readable storage medium may be configured to store program instructions and / or data, wherein if the program instructions are executed by a computer system, the computer system performs a method, such as any method embodiment of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset or combination of any such subset of any method embodiments described herein.
[0167] In some implementations, the device (e.g., UE 106) may be configured to include a processor (or a set of processors) and a memory medium, wherein the memory medium stores program instructions, and the processor is configured to read from and execute the program instructions from the memory medium, wherein the program instructions are executable to implement any of the various method implementations described herein (or any combination of method implementations described herein, or any subset of any method implementations described herein, or any combination of such subsets). The device may be implemented in any of a variety of forms.
[0168] By interpreting each message / signal X received by the user equipment (UE) in the downlink as a message / signal X transmitted by the base station, and interpreting each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station, any method described herein for operating the UE can serve as the basis for a corresponding method for operating the base station.
[0169] Although the above embodiments have been described in considerable detail, many variations and modifications will become apparent to those skilled in the art once the disclosure is fully understood. This disclosure is intended to render the following claims as encompassing all such variations and modifications.
Claims
1. A user equipment (UE) comprising: At least one antenna; At least one radio component, wherein the at least one radio component is configured to perform cellular communication using at least one radio access technology (RAT); One or more processors, said one or more processors being coupled to said at least one radio component, wherein said one or more processors and said at least one radio component are configured to perform communication; The one or more processors are configured such that the UE: The UE can report the maximum peak average equivalent isotropic radiated power (EIRP) used for channel occupancy time (COT) sharing to the base station via its capability. Receive a Pout value for idle channel assessment (CCA) from the base station, wherein the Pout value specifies the EIRP for transmission burst, and wherein the Pout value is based at least in part on at least one of the maximum EIRP reported via the UE capability or the maximum EIRP of the base station. as well as The base station reports the actual Pout and beam direction for CCA used to obtain the COT, as well as the indication of whether the COT is obtained based on channel bandwidth, bandwidth portion BWP bandwidth, or allocated transmission burst bandwidth.
2. The UE according to claim 1, The maximum EIRP is reported for the frequency range between 52.6 GHz and 71 GHz.
3. The UE according to claim 1, The maximum EIRP is included in the power level report, and the maximum EIRP is specific to the power level.
4. The UE according to claim 1, The Pout value is less than or equal to the maximum EIRP for COT sharing reported via the UE capability.
5. The UE according to claim 1, The Pout value is received via cell-specific signaling, and the Pout value is further based at least in part on the maximum EIRP of the base station.
6. The UE according to claim 1, The Pout value is emitted by a signal via at least one of the following: Type 1 or Type 2 Configuration Authorization (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Activated downlink control information (DCI) scrambled with the configuration scheduling (CS) radio network temporary identifier (RNTI) for type 2 configuration authorization (CG); or DCI format 0-1 or 0-2 for dynamic physical uplink shared channel (PUSCH) licensing.
7. The UE according to claim 1, The CCA bandwidth is based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
8. The UE according to claim 1, in: The indication is based on channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth to obtain the COT, including the UE transmitting Configuration Grant (CG) Uplink Control Indication (UCI) to the base station.
9. The UE according to claim 8, The CG UCI mentioned therein includes one or more of the following: A bit indicating the channel bandwidth or the transmission bandwidth of the Physical Uplink Shared Channel (PUSCH) in the CG. The Pout value; Transmission Control Information (TCI) status; COT duration; or COT offset.
10. The UE according to claim 1, in: The report is used to obtain the actual Pout and beam direction of the COT, including the UE transmitting a Configuration Authorization (CG) Uplink Control Indicator (UCI) to the base station.
11. The UE according to claim 10, The CG UCI mentioned therein includes one or more of the following: A bit indicating the channel bandwidth or the transmission bandwidth of the Physical Uplink Shared Channel (PUSCH) in the CG. The actual Pout value; Transmission Control Information (TCI) status; COT duration; or COT offset.
12. The UE according to claim 1, The one or more processors are further configured such that the UE: The detected equivalent isotropic radiated power (EIRP) exceeds the threshold.
13. The UE according to claim 1, The Pout value is reported via a Media Access Control (MAC) control element (CE).
14. The UE according to claim 12, The threshold is at least partially based on the closed-loop power control setting.
15. The UE according to claim 12, The threshold is configured via Radio Resource Control (RRC) signaling.
16. An apparatus for wireless communication, comprising: Memory; as well as At least one processor, which communicates with the memory, wherein the at least one processor is configured to: Directional Listen-Before-Speak (LBT) is performed using specific peak-average equivalent isotropic radiated power (EIRP) and beam detection for transmitting bursts; and The Pout value for Channel Occupied Time (COT) sharing is reported to the base station at least in part based on the directional LBT, wherein the Pout value specifies the EIRP for transmission bursts. The at least one processor is configured to: Receive a Pout value for idle channel assessment (CCA) from the base station, wherein the Pout value for CCA is at least partially based on a reported Pout value; as well as The base station is instructed to obtain the COT based on channel bandwidth, bandwidth portion BWP bandwidth, or allocated transmission burst bandwidth.
17. The apparatus according to claim 16, The Pout value is reported via Configuration Grant (CG) Uplink Control Indication (UCI).
18. The apparatus according to claim 17, The CG UCI mentioned therein includes one or more of the following: Pout value; Transmission Control Information (TCI) status; COT duration; or COT offset.
19. The apparatus according to claim 16, The base stations share the COT for transmission of the Physical Downlink Control Channel (PDCCH) and / or Physical Downlink Shared Channel (PDSCH) within the Transmission Control Information (TCI) status and Pout limits reported by the device.
20. The apparatus according to claim 16, The Pout value used for CCA is signaled via at least one of the following: Type 1 or Type 2 Configuration Authorization (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Activated downlink control information (DCI) scrambled with the configuration scheduling (CS) radio network temporary identifier (RNTI) for type 2 configuration authorization (CG); or DCI format 0-1 or 0-2 for dynamic physical uplink shared channel (PUSCH) licensing.
21. The apparatus according to claim 16, The CCA bandwidth is based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
22. A non-transitory computer-readable storage medium storing program instructions executable by processing circuitry to cause a user equipment (UE) to: The detected equivalent isotropic radiated power (EIRP) exceeds the threshold; as well as The Pout value for Channel Occupancy Time (COT) sharing is reported to the base station, wherein the Pout value specifies the EIRP used for transmission bursts. The program instructions can be further executed by the processing circuitry to enable the user equipment (UE) to: Receive a Pout value for idle channel assessment (CCA) from the base station, wherein the Pout value for CCA is at least partially based on a reported Pout value; as well as The base station is instructed to obtain the COT based on channel bandwidth, bandwidth portion BWP bandwidth, or allocated transmission burst bandwidth.
23. The non-transitory computer-readable storage medium according to claim 22, The Pout value is reported via a Media Access Control (MAC) control element (CE).
24. The non-transitory computer-readable storage medium according to claim 22, The threshold is at least partially based on the closed-loop power control setting.
25. The non-transitory computer-readable storage medium according to claim 22, The threshold is configured via Radio Resource Control (RRC) signaling.
26. The non-transitory computer-readable storage medium according to claim 22, When the UE does not report the Pout value, the base station uses the power value associated with uplink power control as the Pout value.
27. The non-transitory computer-readable storage medium according to claim 22, The CCA bandwidth is based on at least one of the channel bandwidth, bandwidth portion (BWP) bandwidth, or allocated transmission burst bandwidth.
28. The non-transitory computer-readable storage medium according to claim 22, The Pout value used for CCA is represented by at least one of the following: Type 1 or Type 2 Configuration Authorization (CG) Radio Resource Control (RRC) Configuration Information Element (IE); Activated downlink control information (DCI) scrambled with the configuration scheduling (CS) radio network temporary identifier (RNTI) for type 2 configuration authorization (CG); or DCI format 0-1 or 0-2 for dynamic physical uplink shared channel (PUSCH) licensing.
Citation Information
Patent Citations
Improvements in or relating to bathing tents or screens
GB302567A
Method for transmitting physical uplink shared channel of terminal in unlicensed band and device using same method
CN112335315A
User equipment initiated channel occupancy time (COT) sharing between multiple user equipments
WO2020162804A1