Methods, apparatuses, and media for improved receiver assisted access mechanisms in new radio unlicensed spectrum

Abstract

The present disclosure relates to improved receiver assisted access mechanisms in new radio unlicensed spectrum. A user equipment (UE) can receive a measurement reporting capability request from a base station, and in response to the request, further transmit an indication of a measurement reporting capability of the UE. The UE can also receive signaling from the base station including a channel state information (CSI) request trigger. In response to receiving the CSI request trigger, the UE can transmit a measurement report to the base station, where the measurement report can include at least one received signal strength indicator (RSSI) measurement.

Description

Technical Field

[0001] This invention relates to wireless communication, and more particularly to apparatus, systems, and methods for improved receiver-assisted access mechanisms in unlicensed New Radio (NR) spectrum. Background Technology

[0002] 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. Furthermore, many different wireless communication technologies and standards exist. Some examples of wireless communication standards include GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A (Advanced LTE), HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), IEEE 802.11 (WLAN or Wi-Fi), and BLUETOOTH. ™ wait.

[0003] The increasing number of features and functionalities introduced into wireless communication devices has also created a continuous demand for improvements in wireless communication and devices themselves. In addition to the communication standards mentioned above, more wireless communication technologies are being developed to increase coverage and better serve the growing needs and intended applications of wireless communication.

[0004] The next telecommunications standard proposed to surpass the current International Mobile Telecommunications Advanced (IMT-Advanced) standard is called 5G mobile network or 5G radio system, or simply 5G (also known as 5G-NR for 5G New Radio, or simply NR). Compared to the current LTE standard, 5G-NR offers higher capacity for higher density mobile broadband users, while supporting ultra-reliable and massive machine-type communication between devices, as well as lower latency and lower battery consumption. Furthermore, the 5G-NR standard allows for less restrictive UE scheduling compared to the current LTE standard. Therefore, efforts are underway to leverage the potentially higher throughput at higher frequencies in the ongoing development of 5G-NR.

[0005] Furthermore, wireless communication technologies have evolved from voice communication alone to include the transmission of data such as the internet and multimedia content. Additionally, interference, collisions, and conflicts between transmissions of one or more Radio Access Technologies (RATs) are increasingly likely (e.g., in unlicensed spectrum). For example, conflicts can occur between transmissions (e.g., between 5G / cellular transmissions and / or wireless local area network (WLAN) transmissions). Interference, collisions, and conflicts can degrade the wireless ecosystem and negatively impact users of one or more RATs. Therefore, there is a need to improve the areas supporting such development and design. Summary of the Invention

[0006] The implementation scheme relates to wireless communication, and more specifically to apparatus, systems, and methods for improved receiver-assisted access mechanisms in unlicensed spectrum of New Radio (NR).

[0007] In some implementations, the user equipment (UE) may receive a measurement reporting capability request from the base station and, in response to the request, further transmit an indication of the UE's measurement reporting capability. The UE may also receive signaling from the base station including a Channel State Information (CSI) request trigger. In response to receiving a CSI request trigger, the UE may transmit a measurement report to the base station, wherein the measurement report may include at least one Received Signal Strength Indicator (RSSI) measurement.

[0008] According to some implementations, the measurement report may be an aperiodic channel state information (AP-CSI) report, and at least one RSSI measurement may be a Layer 1 (L1) RSSI measurement. In some implementations, for RSSI measurements, the UE may reuse an existing processing timeline or existing priority rules corresponding to the Reference Signal Received Power (RSRP) measurement.

[0009] According to some implementation schemes, the UE can be configured to perform RSSI measurements in the time domain. Additionally or alternatively, the measurement time of the RSSI measurement in the time domain may correspond to one orthogonal frequency division multiplexing (OFDM) symbol for a 120 kHz subcarrier spacing (SCS), three OFDM symbols for a 480 kHz SCS, and five OFDM symbols for a 960 kHz SCS.

[0010] In some implementations, the receive beam associated with the active transmission configuration indicator (TCI) of the signaling can be used to perform RSSI measurements in the time domain.

[0011] According to some implementation schemes, the zero-power channel state information reference signal (ZP-CSI-RS) can be characterized for RSSI measurements in the time domain. Additionally or alternatively, RSSI measurements can be performed based on one or more symbols within or across time slots.

[0012] 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), base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, automobiles and / or motor vehicles, and various other computing devices.

[0013] 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

[0014] 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:

[0015] Figure 1A An exemplary wireless communication system according to some implementation schemes is shown.

[0016] Figure 1B Examples of base stations (BS) and access points communicating with user equipment (UE) devices according to some implementation schemes are shown.

[0017] Figure 2 An exemplary simplified block diagram of a WLAN access point (AP) according to some implementation schemes is shown.

[0018] Figure 3A Example block diagrams of a BS according to some implementation schemes are shown.

[0019] Figure 3B An example block diagram of a server according to some implementation schemes is shown.

[0020] Figure 4 An exemplary block diagram of a UE according to some implementation schemes is shown.

[0021] Figure 5 An example block diagram of a cellular communication circuit according to some implementation schemes is shown.

[0022] Figure 6A An example of the connection between the EPC network, LTE base station (eNB), and 5G NR base station (gNB) is shown.

[0023] Figure 6B An example of the protocol stack used for eNB and gNB is shown.

[0024] Figure 7A 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.

[0025] Figure 7B 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.

[0026] Figure 8 An example of a baseband processor architecture for a UE according to some implementation schemes is shown.

[0027] Figure 9 This is a flowchart illustrating an exemplary method of including measurements as part of an enhanced report, according to some implementation schemes.

[0028] Figure 10 An exemplary communication flow is shown, according to some implementation schemes, incorporating L1-RSSI measurements as part of an AP-CSI report.

[0029] Figure 11 Exemplary processing timelines and priority features, which include measurements as part of an enhanced report, are shown according to some implementation schemes.

[0030] Figure 12 This is a flowchart illustrating an exemplary method of including a measurement report as part of a free channel assessment (CCA) process, according to some implementation schemes.

[0031] Figure 13A and Figure 13B Examples of explicit and implicit indications for triggering measurement reports as part of the CCA process are shown according to some implementation schemes.

[0032] While 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 their detailed description 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 characterized by the appended claims. Detailed Implementation

[0033] acronym

[0034] Various acronyms are used throughout this disclosure. The definitions of the most prominent acronyms that may appear throughout this disclosure are as follows:

[0035] • 3GPP: Third Generation Partnership Project

[0036] •TS: Technical Specifications

[0037] •RAN: Radio Access Network

[0038] •RAT: Radio Access Technology

[0039] •UE: User Equipment

[0040] •RF: Radio Frequency

[0041] •BS: Base Station

[0042] •DL: Downlink

[0043] •UL: Uplink

[0044] •LTE: Long Term Evolution

[0045] •NR: New Radio

[0046] •5GS: 5G system

[0047] • 5GMM: 5GS Mobility Management

[0048] •5GC: 5G Core Network

[0049] •ITS: Intelligent Transportation Systems

[0050] •BM: Broadcast Multicast

[0051] •LBT: Listen before you speak

[0052] •SSB: Synchronization Signal Block

[0053] •RRM: Radio Resource Management

[0054] •RSSI: Received Signal Strength Indicator

[0055] •RSRP: Reference Signal Received Power

[0056] •SCS: Subcarrier Spacing

[0057] •ACK: Confirmation

[0058] • NACK: Negative Acknowledgment

[0059] •TX: Transmission

[0060] •RX: Receive

[0061] •L1: Level 1

[0062] •PDCCH: Physical Downlink Control Channel

[0063] •PUCCH: Physical Uplink Control Channel

[0064] •PDSCH: Physical Downlink Shared Channel

[0065] •PUSCH: Physical Uplink Shared Channel

[0066] •EDT: Energy Detection Threshold

[0067] •CAT2: Category 2

[0068] •ZP-CSI-RS: Zero Power Channel State Information Reference Signal

[0069] •AP-CSI: Aperiodic Channel State Information

[0070] •CCA: Clear Channel Assessment

[0071] •eCCA: Extended Free Channel Assessment

[0072] •HARQ-ACK: Hybrid Automatic Repeat Request Acknowledgment

[0073] • HARQ-ID: Hybrid Automatic Repeat Request Identifier

[0074] •DCI: Downlink Control Information

[0075] •UCI: Uplink Control Information

[0076] •OFDM: Orthogonal Frequency Division Multiplexing

[0077] •TCI: Transport Configuration Indicator

[0078] •RE: Resource Element

[0079] •RB: Resource Block

[0080] •TDRA: Time Domain Resource Allocation

[0081] •RRC: Radio Resource Control

[0082] •MAC-CE: Media Access Control - Control Element

[0083] the term

[0084] The following is a glossary of terms used in this disclosure:

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

[0086] Carrier medium—the memory medium as described above, and physical transmission medium, such as buses, networks and / or other physical transmission media for transmitting signals (such as electrical signals, electromagnetic signals or digital signals).

[0087] Programmable hardware elements—including a variety of hardware devices comprising 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."

[0088] Computer system (or computer) — any of the 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 characterized to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0089] User equipment (UE) (or “UE device”) — any of a variety of computer system devices that are mobile or portable and perform wireless communications. Examples of UE devices include mobile phones or smartphones (e.g., iPhone). ™ Based on Android™ Telephones), portable gaming devices (e.g., Nintendo DS) ™ PlayStation Portable ™ Gameboy Advance ™ iPhone ™ This includes laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable internet devices, music players, data storage devices, other handheld devices, automobiles and / or motor vehicles, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UACs), etc. Generally speaking, the term "UE" or "UE device" can be broadly characterized to encompass any electronic, computing, and / or telecommunications equipment (or combination of equipment) that is easily transportable by (or with) a user and capable of wireless communication.

[0090] 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 is used for communication as part of a wireless telephone system or radio system.

[0091] A processing element (or processor) is a component or combination of components 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 components such as a Field-Programmable Gate Array (FPGA), and any combination thereof.

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

[0093] 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 a channel is used or reserved for the same purpose.

[0094] Wi-Fi—The term “Wi-Fi” 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 are marketed under the name “Wi-Fi.” Wi-Fi (WLAN) networks are distinct from cellular networks.

[0095] Automatic—means an 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 user input to specify or perform that action or operation. Therefore, the term "automatic" contrasts with an action performed or specified manually by a user, where the user provides input to perform that action directly. 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 to specify 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.

[0096] Approximately—means a value close to the correct or precise value. For example, approximately can refer to 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.

[0097] Concurrency refers to the parallel execution or implementation of tasks, processes, or programs in a manner that overlaps at least partially. 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).

[0098] Various components can be described as being "configured" to perform one or more tasks. In such contexts, "configured" is a broad expression generally meaning "having" 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" can also 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" can include hardware circuitry.

[0099] For ease of description, various components may be described as performing one or more tasks. Such descriptions should be interpreted as including the phrase “configured to”. Statements describing a component as configured to perform one or more tasks are explicitly intended not to invoke the interpretation of 35 USC § 112(f) for that component.

[0100] Figure 1A and Figure 1B Communication system

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

[0102] As shown in the figure, the exemplary wireless communication system includes a base station 102A, which communicates with one or more user equipments 106A, 106B to 106N 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.

[0103] Base station (BS) 102A may be a transceiver base station (BTS) or a cell site (“cellular base station”), and may include hardware that enables wireless communication with UE 106A to UE 106N.

[0104] 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".

[0105] As shown in the figure, 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 UE 106 with various communication capabilities such as voice, SMS, and / or data services.

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

[0107] Therefore, although base station 102A can act as the "serving cell" for UEs 106A-N as shown in Figure 1, 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-102N and / or any other base station), 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. Such cells may include "macro" cells, "micro" cells, "pecimen" cells and / or any other cells of various other granularities providing service area size. For example, base stations 102A to 102B shown in Figure 1 may be macro cells, while base station 102N may be a pico cell. Other configurations are also possible.

[0108] 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 an NR core (NRC) network. Furthermore, a gNB cell may include one or more transport 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.

[0109] 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, 3GPP2 CDMA2000 (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.

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

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

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

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

[0114] Figure 2 Access point diagram

[0115] Figure 2 An exemplary block diagram of access point (AP) 112 is shown. Note that... Figure 2 The block diagram of the AP is only one example of a possible system. As shown, AP 112 may include a processor 204 capable of executing program instructions for AP 112. Processor 204 may also be (directly or indirectly) coupled to a memory management unit (MMU) 240 or other circuitry or device, 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).

[0116] AP 112 may include at least one network port 270. Network port 270 may be configured to couple to a wired network and provide access to the Internet to multiple devices such as UE 106. For example, network port 270 (or additional network ports) may be configured to couple to a local network, such as a home network or a corporate network. For example, port 270 may be an Ethernet port. The local network may provide connectivity to additional networks such as the Internet.

[0117] AP 112 may include at least one antenna 234, which may be configured to function as a wireless transceiver and may be further configured to communicate with UE 106 via wireless communication circuitry 230. Antenna 234 communicates with wireless communication circuitry 230 via communication link 232. Communication link 232 may include one or more receive links, one or more transmit links, or both. Wireless communication circuitry 230 may be configured to communicate via Wi-Fi or WLAN (e.g., 802.11). For example, in the case of a small cell where the AP coexists with a base station, or in other situations where it may be desirable for AP 112 to communicate via various different wireless communication technologies, wireless communication circuitry 230 may also or alternatively be configured to communicate via various other wireless communication technologies, including, but not limited to, 5G NR, LTE, LTE-A Advanced, GSM, WCDMA, CDMA2000, etc.

[0118] In some implementations, as further described below, AP 112 can be configured to perform overhead reduction methods for multi-carrier beam selection and power control as further described herein.

[0119] Figure 3A Block diagram of a base station

[0120] Figure 3A An example block diagram of a base station 102 according to some implementation schemes is shown. It should be noted that... Figure 3A The base station shown is merely one example of a possible base station. As illustrated, base station 102 may include processor 304, which executes program instructions for base station 102. Processor 304 may also be coupled to memory management unit (MMU) 340, which may be configured to receive addresses from processor 304 and translate these addresses into locations in memory (e.g., memory 360 and read-only memory (ROM) 350), or into other circuitry or devices.

[0121] Base station 102 may include at least one network port 370. Network port 370 may be configured to be coupled to a telephone network and provide access to the telephone network to multiple devices (e.g., UE device 106), as shown above in Figure 1 and... Figure 2As described in [the text].

[0122] Network port 370 (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 370 may be coupled to a telephone network via the core network, and / or the core network may provide a telephone network (e.g., between other UE devices served by a cellular service provider).

[0123] In some implementations, base station 102 may be a next-generation base station, such as a 5G New Radio (5G NR) base station, or "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.

[0124] Base station 102 may include at least one antenna 334, and may include multiple antennas. At least one antenna 334 may be configured to operate as a wireless transceiver, and may also be configured to communicate with UE device 106 via radio component 330. Antenna 334 communicates with radio component 330 via communication link 332. Communication link 332 may be a receive link, a transmit link, or both. Radio component 330 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.

[0125] 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.).

[0126] 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 304 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 storage medium (e.g., a non-transitory computer-readable storage medium). Alternatively, processor 304 may be configured as a programmable hardware element, such as an FPGA (Field-Programmable Gate Array), or an ASIC (Application-Specific Integrated Circuit), or a combination thereof. Optionally (or additionally), the processor 304 of BS 102, together with one or more other components 330, 332, 334, 340, 350, 360, 370, may be configured to implement or support some or all of the features described herein.

[0127] Furthermore, as described herein, processor 304 may include one or more processing elements. In other words, one or more processing elements may be included in processor 304. Therefore, processor 304 may include one or more integrated circuits (ICs) configured to perform the functions of processor 304. In addition, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 304.

[0128] Furthermore, as described herein, radio component 330 may include one or more processing elements. In other words, radio component 330 may include one or more processing elements. Therefore, radio component 330 may include one or more integrated circuits (ICs) configured to perform the functions of radio component 330. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of radio component 330.

[0129] Figure 3B Server block diagram

[0130] Figure 3B An example block diagram of server 104 according to some implementation schemes is shown. Note that... Figure 3B The server described is merely one example of a possible server. 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.

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

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

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

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

[0135] Figure 4 : UE block diagram

[0136] Figure 4 An exemplary simplified block diagram of a communication device 106 according to some embodiments is shown. It should be noted that... Figure 4The block diagram of the communication device is merely one example of possible communication devices. According to the implementation, 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. As shown, 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 circuits of communication device 106.

[0137] 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 connecting 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, cellular communication circuitry 430 such as for 5G NR, LTE, GSM, etc., and short- to medium-range wireless communication circuitry 429 (e.g., Bluetooth). ™ (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.

[0138] Cellular communication circuitry 430 may be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 435 and 436 shown. Short-to-medium-range wireless communication circuitry 429 may also be coupled (e.g., communicatively grounded; directly or indirectly) to one or more antennas, such as antennas 437 and 438 shown. Alternatively, short-to-medium-range wireless communication circuitry 429 may be coupled (e.g., communicatively grounded; directly or indirectly) to antennas 437 and 438, or as an alternative, to antennas 435 and 436. Short-to-medium-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.

[0139] 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 may 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 may communicate with a dedicated receive chain and a shared transmit chain.

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

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

[0142] 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, for example, a first RAT for LTE, while the second SIM supports, for example, a second RAT for 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 Active (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.

[0143] As shown, the SOC 400 may include a processor 402 and display circuitry 404. The processor executes program instructions for the communication device 106, and the display circuitry 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 display circuitry 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.

[0144] As described above, communication device 106 can be configured to communicate using wireless and / or wired communication circuitry. Communication device 106 can be configured to perform methods for beam fault recovery based on a unified TCI framework (e.g., in 5G NR systems and higher), as further described herein.

[0145] As described herein, communication device 106 may include hardware and software components for implementing the features described above 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 in addition), 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 in addition), 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.

[0146] Furthermore, as described in this invention, 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. Additionally, each integrated circuit may include circuitry (e.g., a first circuit, a second circuit, etc.) configured to perform the functions of processor 402.

[0147] Further, 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.

[0148] Figure 5 Block diagram of cellular communication circuit

[0149] Figure 5 An 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.

[0150] Cellular communication circuit 530 may (e.g., communicatively; directly or indirectly) be coupled to one or more antennas, such as ( Figure 4 Antennas 435a-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 shown... 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.

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

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

[0153] 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).

[0154] In some implementations, the cellular communication circuit 530 may be configured to perform beam fault recovery methods based on a unified TCI framework (e.g., in 5G NR systems and higher), as further described herein.

[0155] 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 technologies 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.

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

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

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

[0159] Figure 6A and Figure 6B 5G NR architecture with LTE

[0160] In some specific implementations, fifth-generation (5G) wireless communication will initially be deployed concurrently with current wireless communication standards (e.g., LTE). For example, dual connectivity between LTE and 5G New Radio (5G NR or NR) has been designated as part of the initial NR deployment. Therefore, as... Figures 6A to 6B As shown, the Evolved Packet Core (EPC) network 600 can continue to communicate with the current LTE base station (e.g., eNB 602). Furthermore, eNB 602 can communicate with the 5G NR base station (e.g., gNB 604) and can transfer data between the core network 600 and gNB 604. Therefore, the EPC network 600 can be used (or reused), and gNB 604 can serve as additional capacity for user equipment, for example, to provide increased downlink throughput for the UE. In other words, LTE can be used for control plane signaling, and NR can be used for user plane signaling. Therefore, LTE can be used to establish connections to the network, and NR can be used for data services.

[0161] Figure 6BThe proposed protocol stack for eNB 602 and gNB 604 is illustrated. As shown, eNB 602 may include a Media Access Control (MAC) layer 632 that interfacing with Radio Link Control (RLC) layers 622a-622b. RLC layer 622a may also interfacing with Packet Data Convergence Protocol (PDCP) layer 612a, and RLC layer 622b may interfacing with PDCP layer 612b. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 612a may interfacing with EPC network 600 via Primary Cell Group (MCG) bearer, while PDCP layer 612b may interfacing with EPC network 600 via decoupling bearer.

[0162] Additionally, as shown in the figure, gNB 604 may include a MAC layer 634 that interfacing with RLC layers 624a-624b. RLC layer 624a may interfacing with the PDCP layer 612b of eNB 602 via the X2 interface for information exchange and / or coordination (e.g., UE scheduling) between eNB 602 and gNB 604. Furthermore, RLC layer 624b may interfacing with PDCP layer 614. Similar to the dual connectivity specified in Advanced LTE Release 12, PDCP layer 614 may interfacing with EPC network 600 via a secondary cell group (SCG) bearer. Therefore, eNB 602 can be considered the primary node (MeNB), and gNB 604 can be considered the secondary node (SgNB). In some cases, it may be required that the UE maintain connectivity with both the MeNB and the SgNB. In such cases, the MeNB can be used to maintain the Radio Resource Control (RRC) connection with the EPC, while the SgNB can be used for capacity (e.g., additional downlink and / or uplink throughput).

[0163] Figure 7A and Figure 7B 5G Core Network Architecture - Interoperability with Wi-Fi

[0164] 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 7AAn example of a 5G network architecture according to some implementation schemes is shown, which combines 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access to the 5G CN. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, e.g., gNB or base station 604) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to a non-3GPP Interoperability Function (N3IWF) 702 network entity. N3IWF may include a connection to the core access and mobility management function (AMF) 704 of the 5G CN. AMF 704 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 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. As shown, AMF 704 may include one or more functional entities associated with the 5G CN (e.g., Network Slice Selection Function (NSSF) 720, Short Message Service Function (SMSF) 722, Application Function (AF) 724, Unified Data Management (UDM) 726, Policy Control Function (PCF) 728, and / or Authentication Server Function (AUSF) 730). It should be noted that these functional entities may also be supported by the 5G CN's Session Management Functions (SMF) 706a and SMF 706b. AMF 706 may connect to (or communicate with) SMF 706a. In some implementations, such functional entities may reside on, and / or be performed by, or supported by, one or more servers 104 located within the RAN and / or core network. Furthermore, gNB 604 may communicate with (or connect to) the User Plane Function (UPF) 708a, which may also communicate with SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which in turn can communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0165] Figure 7BAn example of a 5G network architecture according to some implementation schemes is shown, which combines dual 3GPP (e.g., LTE and 5G NR) access to the 5G CN as well as non-3GPP access. As shown, a user equipment device (e.g., UE 106) can access the 5G CN via both a radio access network (RAN, such as gNB or base station 604 or eNB or base station 602) and an access point such as AP 112. AP 112 may include a connection to the Internet 700 and a connection to the N3IWF 702 network entity. The N3IWF may include a connection to the AMF 704 of the 5G CN. AMF 704 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 704. Therefore, the 5G CN can support unified authentication on both connections and allow UE 106 to register access simultaneously via gNB 604 and AP 112. Additionally, the 5G CN can support dual registration of the UE on both a legacy network (e.g., LTE via base station 602) and a 5G network (e.g., via base station 604). As shown, base station 602 can have connections to both the Mobility Management Entity (MME) 742 and the Service Gateway (SGW) 744. MME 742 can have connections to both SGW 744 and AMF 704. Furthermore, SGW 744 can have connections to both SMF 706a and UPF 708a. As shown, AMF 704 can include one or more functional entities associated with the 5G CN (e.g., NSSF 720, SMSF 722, AF 724, UDM 726, PCF 728, and / or AUSF 730). Note that UDM 726 can also include Home Subscriber Server (HSS) functionality, and PCF can also include Policy and Charging Rules (PCRF) functionality. It should also be noted that these functional entities can also be supported by the 5G CN's SMF 706a and SMF 706b. The AMF 706 can connect to (or communicate with) the SMF 706a. In some implementations, such functional entities may reside on, and / or be performed by, or supported by, one or more servers 104 located within the RAN and / or core network. Furthermore, the gNB 604 can communicate with (or connect to) the UPF 708a, which can also communicate with the SMF 706a. Similarly, the N3IWF 702 can communicate with the UPF 708b, which can also communicate with the SMF 706b. Both UPFs can communicate with data networks (e.g., DN 710a and 710b) and / or the Internet 700 and the IMS core network 710.

[0166] It should be noted that, in various implementation schemes, one or more of the aforementioned network entities may be configured to perform methods for implementing mechanisms to extend the measurement period, for example, as further described herein.

[0167] Figure 8 Baseband processor architecture

[0168] Figure 8 An example of a baseband processor architecture for a UE (e.g., UE 106) according to some implementation schemes is shown. As described above, Figure 8 The baseband processor architecture 800 described herein can be implemented on one or more radio components (e.g., radio components 329 and / or 330) or modems (e.g., modems 510 and / or 520) as described above. As shown, the non-access stratum 810 may include a 5G NAS 820 and a traditional NAS 850. The traditional NAS 850 may include a communication connection with a traditional access stratum (AS) 870. The 5G NAS 820 may include communication connections with a 5G AS 840 and a non-3GPP AS 830, as well as a Wi-Fi AS 832. The 5G NAS 820 may include functional entities associated with both access strata. Therefore, the 5G NAS 820 may include multiple 5G MM entities 826 and 828 and 5G session management (SM) entities 822 and 824. The traditional NAS 850 may include functional entities such as Short Message Service (SMS) entity 852, Evolved Packet System (EPS) Session Management (ESM) entity 854, Session Management (SM) entity 856, EPS Mobility Management (EMM) entity 858, and Mobility Management (MM) / GPRS Mobility Management (GMM) entity 860. Furthermore, the traditional AS 870 may include functional entities such as LTE AS 872, UMTS AS 874, and / or GSM / GPRS 876.

[0169] Therefore, the baseband processor architecture 800 allows for a common 5G-NAS for both 5G cellular and non-cellular (e.g., non-3GPP access) networks. It's important to note that, as shown in the figure, the 5G MM can maintain separate connection management and registration management state machines for each connection. Furthermore, a device (e.g., UE 106) can register to a single PLMN (e.g., a 5G CN) using both 5G cellular and non-cellular access. Additionally, a device can be connected in one access and idle in another, or vice versa. Finally, there may be common 5G-MM procedures (e.g., registration, deregistration, identification, authentication, etc.) for both accesses.

[0170] It should be noted that, in various implementations, one or more of the aforementioned functional entities of the 5G NAS and / or 5G AS can be configured to perform methods for reducing overhead for multi-carrier beam selection and power control, for example, as further described herein.

[0171] Improved Receiver Assisted Access Mechanism in Unlicensed NR Spectrum

[0172] In recent developments in wireless standards, receive (Rx) assisted access has been investigated to provide enhanced communications. For the assisted receiver (e.g., UE), channel sensing and reporting can be performed by the UE to assess the characteristics (e.g., power measurements) of one or more wireless channels and accordingly inform the network of these characteristics. In some implementations, the UE can perform channel sensing using Received Signal Strength Indicator (RSSI) measurements and reporting. For example, in some implementations, RSSI measurements can be compared to an Energy Detection Threshold (EDT). In some implementations, the UE can perform beam-specific RSSI measurements and reporting and / or RSSI measurements based on the Zero Power Channel State Information Reference Signal (ZP-CSI-RS). Additionally or alternatively, the UE can provide Layer 1 (L1) RSSI reports in the form of specific CSI reports.

[0173] In some implementations, the UE may utilize enhanced aperiodic channel state information reporting (AP-CSI), but other specific reporting methods (e.g., CSI reporting) are also envisioned. For example, if the UE is configured with aperiodic CSI reporting, the UE may report CSI when CSI interference measurement (CSI-IM) and zero-power channel state information reference signal (NZP-CSI-RS) resources are configured as periodic, semi-persistent, or aperiodic. Furthermore, the time and frequency resources that the UE may use to report CSI may be controlled by the base station (e.g., gNB). Additionally, CSI may include a channel quality indicator (CQI), a precoding matrix indicator (PMI), a CSI-RS resource indicator (CRI), an SS / PBCH block resource indicator (SSBRI), a layer indicator (LI), a rank indicator (RI), L1-RSRP, L1-RSSI, and / or a Layer 1 signal-to-noise-interference ratio (L1-SINR). Additionally or alternatively, the UE may perform aperiodic CSI reporting on the serving cell using the PUSCH after successfully decoding DCI format 0-1 or DCI format 0-2, which may further trigger an aperiodic CSI trigger state. In some implementations, the UE may perform semi-persistent CSI reporting on the PUSCH after successfully decoding DCI format 0-1 or DCI format 0-2, which may activate a semi-persistent CSI trigger state.

[0174] As another form of receiver-assisted access, the UE can also act as a receiver to perform Listen-Before-Speak (LBT) operations. LBT can also be characterized by the UE performing an Empty Channel Assessment (CCA) before attempting to access a channel. For example, the UE can perform a CCA procedure to listen to or monitor the duration of the CCA observation for an appropriate channel. If the energy level in the channel exceeds a certain threshold, the channel is considered occupied. Therefore, if the UE determines that a channel is occupied (e.g., the measured energy level exceeds the threshold), the UE can delay further attempts to access the channel.

[0175] Furthermore, in some implementations, the UE may perform extended idle channel assessment (eCCA) to assess the occupancy characteristics or state of one or more channels. For example, the UE may perform an eCCA procedure to listen to or monitor energy levels in the channel using a flexible CCA observation duration. Additionally or alternatively, the UE may perform Category 2 (Cat2) LBT, which may correspond to performing a “single-trigger” LBT or an LBT without random backoff, and may also have a defined CCA period or duration. In other words, Cat2 LBT may correspond to a fixed sensing period within a frame or subframe, and may also exclude a backoff period corresponding to a portion of the frame or subframe preceding the sensing period. In some implementations, the backoff period may be generated based on random values ​​to facilitate the interval between channel time or contention for resources and potentially reduce resource conflicts. In contrast, LBT Category 3 (Cat3) and Category 4 (Cat4) may utilize variable sensing periods and additionally include a random backoff period. These other categories of LBT can be used in the various implementations described herein.

[0176] In some existing implementations, the Talk-Before (LBT) mechanism can be used to access shared media (e.g., unlicensed frequency bands commonly used for Wi-Fi, Bluetooth, and other short- to mid-range communications (e.g., non-3GGP access)) to avoid collisions (transmissions from two or more wireless devices attempting to access the shared media) and improve media utilization efficiency. However, the LBT mechanism is not collision-free. In other words, the LBT mechanism cannot guarantee collision-free transmission.

[0177] For example, in the case of unicast transmission, the transmitter can easily detect transmission collisions based on the receiver's acknowledgment / negative acknowledgment (ACK / NACK) feedback. However, in the case of multicast transmission, the transmitter may not easily detect collisions based on the receiver's ACK / NACK, at least in part due to the heavy traffic associated with ACK / NACK from multiple receivers and the transmitter's inability to distinguish (or isolate) transmission collisions from channel quality issues based on received ACK / NACK. In other words, since receivers in multicast transmission may be located at different locations with different channel qualities, the transmitter cannot determine the cause of the NACK (e.g., transmission collision versus poor channel quality). Furthermore, in the case of broadcast transmission, feedback from the receiver is known to be infeasible, therefore, the transmitter is unaware of the collision. Additionally, in some implementations, the transmitter may reserve periodic slots for communication within a reserved time period. In such implementations, if a collision occurs, the collision may persist for at least a portion of the reserved time period (and, in the worst case, the duration of the reserved time period) if the transmitter does not detect (or cannot detect) the collision.

[0178] In the current implementation of 3GPP 5G NR, research on extending current NR operation to 71 GHz is related to UE measurements involving physical layer procedures. For example, some studies have addressed timing associated with beam-based operation for new subcarrier spacings (e.g., 480 kHz and / or 960 kHz) in enhanced and shared spectrum operations. Additionally, other studies have addressed channel access mechanisms using beam-based operation that comply with regulatory requirements associated with unlicensed spectrum between 52.6 GHz and 71 GHz. Furthermore, some studies have attempted to specify receiver-assisted LBT and non-LBT procedures regarding omnidirectional listen-before-speak (LBT), directional LBT, enhanced energy detection thresholds, and channel access (without specifying additional sensing mechanisms). Moreover, in addition to defining uplink (UL) and downlink (DL) operation within the frequency band and excluding Intelligent Transportation Systems (ITS) spectrum within the stated frequency range, some core specifications regarding the new frequency band in the 52.6 GHz to 71 GHz frequency range have been discussed. In addition, the core requirements for gNB (e.g., base station), UE radio frequency (RF), radio resource management (RRM), radio link monitoring (RLM), and broadcast multicast (BM) in the frequency range of 52.6 GHz to 71 GHz were investigated.

[0179] Furthermore, when a UE performs cell-specific measurements during LBT procedures in an NR environment, the UE may be susceptible to or experience LBT failures. These LBT failures may involve the UE performing beam measurements in higher, unlicensed spectrum in the 52.6 GHz to 71 GHz frequency range.

[0180] While the embodiments described below discuss L1-RSSI and various specific CSI reports, any of a variety of messages, measurements, reports, etc., can be used. According to some embodiments, one example of receiver-assisted access technology may involve transmitting measurements (e.g., L1-RSSI measurements) as part of an enhanced report (e.g., an AP-CSI report). Additionally or alternatively, measurements based on L1-RSSI and / or ZP-CSI-RS, beam-specific RSSI measurements and reports, the content of L1-RSSI reports (e.g., RSSI measurement values ​​and / or comparison results with EDT), and receiver-assisted measurement timelines, report configurations, triggering, measurement configurations, and resources based on CCA / eCCA may also be used as part of receiver-assisted access technology.

[0181] In some implementations, measurements (e.g., L1-RSSI) may be included as enhancements to reports (e.g., AP-CSI reports), which involve enhanced or altered parameters relating to triggering on the PUSCH, report configuration (e.g., ReportConfig), timeline, priority, measurement, and report format. Additionally or alternatively, according to some implementations, the UE may provide receive-assisted access via LBT in the Rx. For example, the base station may trigger the measurement to be reported by using downlink DCI (downlink control information) transmissions. Furthermore, PDSCH transmissions from the base station may further depend on the measurement (which may be quantized) and be reported in the PUCCH or PUSCH.

[0182] Figure 9 - Methods of including measurements as part of enhanced reporting

[0183] Figure 9 This is a flowchart illustrating an exemplary method of including measurements as part of an enhanced report, according to some implementation schemes.

[0184] Figure 9Aspects of the method may be implemented by a wireless device such as one or more UEs 106, which communicate with one or more base stations (e.g., BS 102) as shown in the figures and as described with respect to the figures, or more generally, in conjunction with any of the computer systems or devices shown in the figures, as well as other circuits, systems, devices, elements or components and other devices shown in the figures, as needed. For example, one or more processors (or processing elements) of the UE (e.g., one or more processors 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) may cause the UE to perform some or all of the illustrated method elements. It should be noted that although at least some elements of the method have been described in a manner involving the use of communication technologies and / or features associated with 3GPP specification documents, this description is not intended to limit the disclosure, and aspects of the method may be used in any suitable wireless communication system as needed. In various embodiments, some elements of the illustrated method may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.

[0185] In 902, the UE may receive a measurement reporting capability request from the base station. More specifically, the base station may request the UE from the base station an indication of the UE's ability to report measurements (e.g., L1-RSSI) as part of an enhanced report (e.g., AP-CSI report). For example, some UEs may not support this capability due to hardware or software configurations implemented in older UEs. However, newer UEs may have hardware and / or software specifications or configurations to support the ability to include measurements as part of an enhanced report.

[0186] In 904, the UE may transmit an indication of its measurement reporting capability to the base station in response to a measurement reporting capability request from the base station. For example, the UE may respond to the BS by indicating whether it supports or does not support L1-RSSI measurement reporting as part of the AP-CSI reporting configuration. Furthermore, the UE may use certain bit parameter allocations in the response transmission to indicate whether it has or lacks the aforementioned capability. In some embodiments, the allocated bits may correspond to binary "true" or "false" parameters corresponding to "1" or "0" values, respectively. According to some embodiments, parameters such as rssi-csi-dynamicChannelAccess-r17 may be used to indicate whether the UE supports L1-RSSI measurement reporting as part of the AP-CSI enhancement.

[0187] In 906, a UE, already indicated in 904 as capable of including certain measurements (e.g., L1-RSSI) as part of an enhanced report (e.g., AP-CSI report), can receive or decode a Physical Downlink Control Channel (PDCCH) transmission from a base station, which may further include a CSIrequest trigger. For example, the PDCCH transmission may include a CSIrequest field, which can be set or assigned specific parameters to trigger a measurement report. In some implementations, the base station may utilize DCI formats 0-1 and 0-2 with the CSIrequest field to indicate measurement report triggering. Furthermore, according to some implementations, the CSI request parameters may include 0-6 bits, which may be further determined by higher-level parameters such as reportTriggerSize. Additionally, enhanced report (e.g., AP-CSI report) configuration may require including measurements (e.g., L1-RSSI). An exemplary code block for the aforementioned parameters is shown below.

[0188] CSI-ReportConfig ::= SEQUENCE {

[0189] reportConfigId CSI-ReportConfigId,

[0190] carrier ServCellIndex OPTIONAL, --

[0191] … …

[0192] reportQuantity CHOICE {

[0193] none NULL,

[0194] cri-RI-PMI-CQI NULL,

[0195] cri-RI-i1 NULL,

[0196] cri-RI-i1-CQI SEQUENCE {

[0197] pdsch-BundleSizeForCSI ENUMERATED {n2, n4} OPTIONAL -- Need S

[0198] },

[0199] cri-RI-CQI NULL,

[0200] cri-RSRP NULL,

[0201] ssb-Index-RSRP NULL,

[0202] cri-RI-LI-PMI-CQI NULL

[0203] RSSI NULL

[0204] },

[0205] ...

[0206] }

[0207] In 908, the UE may, in response to receiving a PDCCH transmission from the base station, transmit a measurement (e.g., a quantized L1-RSSI) as part of an enhancement report (e.g., an AP-CSI report) via a PUSCH transmission. More specifically, the PDCCH transmission from the base station may include a trigger that, in turn, causes the UE to transmit the measurement as part of the enhancement report. Thus, the UE may perform appropriate channel measurements or sensing to generate the measurement. Furthermore, according to some embodiments, the measurement may be quantized (e.g., including bit fields in the data transmission) such that the measurement indicates a measured value (e.g., an L1-RSSI value). Additionally or alternatively, the measurement may be quantized based on a comparison with an energy detection threshold (EDT) value.

[0208] In 910, the UE can receive or decode the DCI (Distributed Control Channel Information) regarding the scheduling of PDSCH transmissions from the base station. For example, based on feedback received from the UE, the BS (Base Station) can transmit scheduling information regarding PDSCH transmissions. According to some implementations, if the UE previously indicated that the channel was noise-free (e.g., low interference level) via a measurement (L1-RSSI) in an enhancement report (e.g., AP-CSI report), the base station can continue to transmit the DCI for scheduled transmission via PDSCH. Additionally or alternatively, if the UE's quantization measurement (e.g., L1-RSSI) indicates a noisy channel (e.g., high interference level), the base station can optionally or automatically cancel PDSCH transmission and therefore not transmit the DCI scheduling information. In some implementations, the base station (e.g., gNB) can transmit PDSCH signaling at a higher Control Channel Element (CCE) aggregation level. Additionally or alternatively, if the L1-RSSI indicates a noisy channel but the interference level still allows for low-rate transmission, the DCI can schedule PDSCHs with a lower Mission Critical Service (MCS) index. In other words, the base station (e.g., gNB) can adjust the PDCCH and PDSCH transmission to the UE based on the quantization feedback (e.g., L1-RSSI) it receives in 908.

[0209] In 912, the UE can receive PDSCH transmissions from the base station. Therefore, as a result of quantization measurements, the UE can receive the PDSCH to indicate to the base station that the measured channel has a low interference level and is free of noise.

[0210] In 914, the UE can transmit an acknowledgment (ACK) or a negative acknowledgment (NACK) to the base station. Therefore, the base station can use this ACK or NACK to determine whether a previously transmitted PDSCH transmission was successfully received or failed. Thus, if the BS receives a NACK from the UE, the BS can optionally stop further attempts to communicate with the UE, or alternatively, it can attempt to restart the measurement reporting process at 902.

[0211] Figure 10 - Incorporate L1-RSSI measurements into the communication flow as part of the AP-CSI report.

[0212] Figure 10 An exemplary communication flow between the UE and a base station (e.g., gNB) is shown according to some implementation schemes when L1-RSSI measurements are included as part of the AP-CSI report.

[0213] As mentioned above Figure 9 As briefly discussed, the UE may first receive a capability request from the base station and respond to the base station with an indication of having (or lacking) its capability in order to include the quantified L1-RSSI measurement as part of the AP-CSI report.

[0214] Therefore, the UE can receive or decode PDCCH transmissions from the base station, including those triggered by CSI requests. More specifically, according to some implementations, if the UE has indicated its support for including L1-RSSI measurements as part of the AP-CSI report, the base station can respond with an L1-RSSI-triggered PDCCH transmission. Furthermore, the base station can schedule PDCCH transmissions such that they correspond to an offset value K1' (K1 prime).

[0215] Next, in response to receiving the PDCCH, the UE may transmit a quantized L1-RSSI to the base station via the PUSCH (as part of the AP-CSI report). More specifically, during offset value K1', the UE may decode the DCI associated with the PDCCH transmission triggered by the CSI request, perform RSSI measurement, and accordingly transmit a quantized L1-RSSI report via the PUSCH as part of the AP-CSI report.

[0216] In response to the L1-RSSI indicating a low-noise or low-interference channel, the UE can receive or decode from the base station the scheduling of PDSCH transmissions and the DCI associated with the offset period K0. More specifically, K0 may correspond to the offset between the DL time slot for receiving the PDCCH (e.g., DCI) for downlink scheduling and the DL time slot for scheduling the PDSCH.

[0217] Therefore, the UE can receive PDSCH transmissions from the base station and, upon successfully receiving the PDSCH transmissions, further transmit an ACK response to the base station. Furthermore, the ACK response can correspond to an offset period K1, which can be characterized as the offset between the DL time slot for scheduling data on the PDSCH and the UL time slot where the ACK / NACK feedback for the scheduled PDSCH data will be transmitted.

[0218] Figure 11 - Used to include measurements in a timeline and priority as part of an enhanced report.

[0219] Figure 11 An exemplary implementation of a processing timeline and priorities is shown, which are associated with including measurements as part of an enhanced report.

[0220] For example, such as Figure 11 As shown, the UE can decode the DCI, which corresponds to the PDCCH received from the base station with a CSIrequest triggered. Furthermore, the PDCCH can be configured by the base station (e.g., gNB) to allow sufficient time for the base station to process the DCI measurement (e.g., L1-RSSI) before the PDSCH transmission at K0. In other words, the base station may need to wait, receive, and process the measurement (corresponding to K1'). During this period, the UE can perform the measurement (e.g., L1-RSSI) and further transmit the quantized measurement via the PUSCH.

[0221] In some implementations, including measurements (e.g., L1-RSSI) as part of an enhanced report (e.g., AP-CSI) may further include utilizing a processing timeline (e.g., a CSI processing timeline). For example, according to some implementations, L1-RSSI may be able to reuse the Layer 1 Reference Signal Received Power (L1-RSRP) processing timeline, which may involve a 480 kHz subcarrier spacing (SCS) and a 960 kHz SCS. Additionally or alternatively, the L1-RSSI processing timeline and / or measurements may occur faster than the L1-RSRP processing timeline because L1-RSSI is based on energy sensing in the time domain and may not require frequency domain processing. Furthermore, according to some implementations, L1-RSSI measurements may use zero or at most one CSI processing unit (CPU).

[0222] In some implementations, L1-RSSI may utilize the priority rules of CSI reports. For example, if the associated priority value (e.g., k) of a first report is lower than the associated priority value of a second report, the first CSI report may have a higher priority than the second CSI report. In one example, according to some implementations, L1-RSSI may be able to reuse the L1-RSRP priority rule (e.g., k=0). Additionally or alternatively, L1-RSSI may be associated with a priority lower than CSI (e.g., k=1). However, if the time occupancy of the physical channel scheduled to carry the CSI report overlaps in at least one OFDM symbol and is transmitted on the same carrier, a conflict may occur between the two CSI reports.

[0223] According to some implementations, RSSI measurements can be used to sense the overall environment in unlicensed frequency bands (which may include certain 802.11ad and 802.11ay technologies / standards). Furthermore, L1-RSSI measurements (as part of the AP-CSI report) may also include RSSI measurement configurations in the time domain.

[0224] For example, in some implementations, the measurement time for L1-RSSI measurements may be greater than or equal to the 5-microsecond CCA time slot time corresponding to the minimum timing time slot. More specifically, for a 120 kHz SCS, the L1-RSSI measurement time may correspond to one orthogonal frequency division multiplexing (OFDM) symbol, and for 480 kHz and 960 kHz SCS, the L1-RSSI measurement time may correspond to three and five OFDM symbols, respectively.

[0225] Additionally or alternatively, ZP-CSI-RS can be characterized for L1-RSSI measurements. For example, according to some implementations, ZP-CSI-RS can be characterized with a new measurement resource configuration (instead of the traditional zero-power configuration corresponding to resource block / resource element estimation), such that the new pattern occupies the full amount of OFDM symbols. Additionally or alternatively, parameters such as CSI-reportConfigID for L1-RSSI can be directly linked to empty OFDM symbols. These alternative configurations allow the UE to perform RSSI measurements of its surrounding environment (e.g., channel) using certain gaps or intervals when not transmitting.

[0226] In some implementations, L1-RSSI can be measured based on symbols within a time slot. Additionally or alternatively, L1-RSSI can be measured based on symbols spanning multiple time slots. For example, the L1-RSSI measurement time corresponding to three and five OFDM symbols (for 480 kHz and 960 kHz SCS) can be extended across time slot boundaries.

[0227] According to some implementations, the time-domain measurement limit of L1-RSSI may not be configurable, and therefore the UE may utilize “single-trigger” measurements corresponding to LBT category 2.

[0228] In some implementations, the UE may utilize directional L1-RSSI. For example, the UE may use the Rx beam associated with the active TCI state that triggered the PDCCH to measure L1-RSSI. Alternatively or additionally, if the triggering PDCCH does not carry the active TCI state, the UE may use the Rx beam based on the default PDSCH beam to measure L1-RSSI.

[0229] According to some implementations, L1-RSSI can reuse the L3-RSSI reporting range. For example, an information element (IE) such as the RSSI range can specify the range of values ​​used in RSSI measurements and the threshold for operations with shared spectrum channel access (e.g., New Radio (NR)). More specifically, the L1-RSSI reporting range can be characterized as "RSSI-Range-r16 ::=INTEGER(0..76)", where the reporting range of the measurement can be defined from -100 dBm to -25 dBm with a resolution of 1 dBm. For example, according to some implementations, the RSSI reporting value "RSSI 00" can correspond to an RSSI measurement value less than -100 dBm, the RSSI reporting value "RSSI 01" can correspond to an RSSI measurement value greater than or equal to -100 dBm and less than -99 dBm, and the RSSI reporting value "RSSI 02" can correspond to an RSSI measurement value greater than or equal to -99 dBm and less than -98 dBm. Furthermore, this characterization can continue for the L1-RSSI reporting range, such that the RSSI reporting value "RSSI 75" can correspond to an RSSI measurement value greater than or equal to -26 dBm and less than -25 dBm, and the RSSI reporting value "RSSI 76" can correspond to an RSSI measurement value greater than or equal to -25 dBm.

[0230] As a supplement to or alternative to the time-domain measurement configuration, L1-RSSI measurements (as part of the AP-CSI report) may also include a frequency-domain RSSI measurement configuration, depending on some implementations.

[0231] In some implementations, the UE may be configured to reuse an existing ZP-CSI-RS configuration for L1-RSSI measurements. Additionally or alternatively, the UE may be configured to define a new ZP-CSI-RS configuration pattern that further enables continuous RE (e.g., RB-based) estimation. According to some implementations, frequency-domain RSSI measurements may not capture, characterize, or sense interference from 802.11ad sources, as well as time-domain based RSSI measurements.

[0232] Figure 12 - Methods of incorporating measurement as part of the CCA process

[0233] Figure 12 Exemplary techniques are shown for performing exemplary methods of incorporating measurements as part of a CCA process, according to some implementation schemes.

[0234] Figure 12 Aspects of the method may be implemented by a wireless device such as UE 106, which communicates with one or more base stations (e.g., BS 102) as shown in the accompanying drawings and as described with respect to the drawings, or more generally, in conjunction with any of the computer systems or devices shown in the drawings, as well as other circuits, systems, devices, elements or components and other devices shown in the drawings, as needed. For example, one or more processors (or processing elements) of the UE (e.g., one or more processors 402, one or more baseband processors, one or more processors associated with communication circuitry, etc.) may cause the UE to perform some or all of the illustrated method elements. It should be noted that although at least some elements of the method have been described in a manner involving the use of communication technologies and / or features associated with 3GPP specification documents, this description is not intended to limit the present disclosure, and aspects of the method may be used in any suitable wireless communication system as needed. In various embodiments, some elements of the illustrated method may be performed simultaneously in a different order than shown, may be replaced by other method elements, or may be omitted. Additional method elements may also be performed as needed. As shown, the method may operate as follows.

[0235] In step 1202, the base station may transmit a measurement reporting capability request to the UE. More specifically, the base station may request an indication from the UE regarding the UE's ability to report measurements (e.g., L1-RSSI) as part of an enhancement process (e.g., CCA or eCCA process).

[0236] In 1204, the base station can receive an indication of the UE's measurement reporting capability from the UE. More specifically, this indication can tell the base station whether the UE supports measurement reporting as part of the enhanced CCA process. This capability can be indicated using certain bit parameter allocations in the UE's response transmission.

[0237] In 1206, the base station may transmit downlink DCI triggering L1-RSSI along with PDSCH scheduling. For example, the base station may transmit the Physical Downlink Control Channel (PDCCH) to the UE, which may further include CSIrequest triggering. Additionally, the PDCCH transmission may include a CSIrequest field, which may be set or assigned specific parameters to trigger measurement (e.g., L1-RSSI) reporting. In some embodiments, the base station may use DCI formats 1-1 and 1-2 with the CSIrequest field to indicate measurement report triggering. Additionally or alternatively, transmissions from the base station may include DCI scheduling regarding PDSCH transmission.

[0238] In 1208, the base station may transmit measurements received from the UE (e.g., quantized L1-RSSI) via PUSCH or PUCCH. For example, the UE may indicate that the channel is noise-free (e.g., low interference level) via a measurement report. Alternatively, the UE's quantized L1-RSSI report may also indicate a noisy channel (e.g., high interference level).

[0239] In 1210, the base station may, in response to receiving a measurement (e.g., a quantized L1-RSSI), transmit a PDSCH to the UE as part of subsequent communication. For example, if the UE's measurement indicates a low interference level, the base station may continue its scheduled PDSCH transmission due to the included DCI scheduling information in the request trigger. Alternatively, if the UE's measurement indicates a noisy channel, the base station may optionally or automatically cancel the PDSCH transmission.

[0240] In 1212, the base station can receive an acknowledgment (ACK) transmission from the UE indicating that the UE has successfully received the PDSCH transmission. Alternatively, if the PDSCH transmission fails, the base station can receive a negative acknowledgment (NACK) transmission from the UE.

[0241] Figures 13A to 13B - Explicit and implicit indications used to trigger measurement reports as part of the CCA process

[0242] Figure 13A Explicit indications for triggering L1-RSSI reporting are shown, according to some implementation schemes, as part of a method for including measurements as part of the CCA process.

[0243] For example, in some implementations, the base station may transmit the DL scheduling DCI trigger L1-RSSI along with the PDSCH scheduling. Furthermore, as part of an explicit indication, the base station may utilize a 1-bit L1-RSSI trigger field in DCI format 1-1 or 1-2. Therefore, the L1-RSSI can be quantized and compared with the EDT. In some implementations, if the L1-RSSI is higher than the EDT, the 1-bit L1-RSSI trigger field may be set to 0. Alternatively or additionally, if the L1-RSSI is lower than the EDT, the 1-bit L1-RSSI trigger may be set to 1. In some implementations, the base station may utilize two or more bits of linear quantization with the L1-RSSI.

[0244] In some implementations, the additional bit field can be used to indicate the K1' value for L1-RSSI transmissions used for quantization on the PUCCH. Additionally or alternatively, K1' can be configured via Radio Resource Control (RRC) signaling corresponding to each Time Domain Resource Allocation (TDRA) entry in the DCI.

[0245] According to some implementations, the base station (e.g., gNB) can perform transmission scheduling to ensure that K1' is less than K0, so as to ensure that the base station has sufficient time to process the L1-RSSI of the DCI before transmitting the PDSCH at K0. In other words, the base station may need to wait, receive, and process the L1-RSSI (corresponding to K1'). Therefore, the base station can configure K0 or K1' to be greater than K1', so as to transmit the PDSCH after receiving and processing the L1-RSSI. However, if K0 is less than K1', the feedback provided by the L1-RSSI may not be available to the base station for subsequent PDSCH transmissions. Furthermore, according to some implementations, the PDSCH can be transmitted only when the L1-RSSI is lower than the EDT. In other words, if the UE reports strong interference in the corresponding channel with the quantized L1-RSSI (which can indicate adverse conditions that the base station should pass through its transmission), the base station may be able to adjust accordingly and may "automatically" cancel the PDSCH transmission. According to another implementation, the PDSCH can be canceled if the L1-RSSI is higher than the EDT.

[0246] In some implementations, the base station may facilitate the scheduling of transmissions such that K1' is higher than a threshold reported by the UE, so that the UE has sufficient time to decode the PDCCH and identify the correct Rx beam for L1-RSSI measurements.

[0247] Figure 13B Implicit indications for triggering L1-RSSI reporting are shown as part of a method for including measurement (e.g., L1-RSSI) reports as part of a CCA process, according to some implementations.

[0248] In some implementations, the base station may transmit the DL scheduling DCI-triggered L1-RSSI along with the PDSCH scheduling, and may further utilize implicit indications. For example, according to some implementations, the base station may reuse DCI format 1-1 and DCI format 1-2. Additionally or alternatively, the base station may utilize RRC configuration or MAC CE signaling to implement the UE's L1-RSSI feedback. Thus, the UE may send or transmit a quantized L1-RSSI corresponding to the timing offset K1 from the DCI in response to this signaling. Additionally, the K1 slot may be configured such that it is less than the subsequent K0 timing offset. For example, as discussed above, the base station may configure K1 to be less than K0 to ensure that the base station has sufficient time to process the DCI's L1-RSSI before PDSCH transmission at K0. In some implementations, if the L1-RSSI is below the EDT, the base station may transmit the PDSCH, and the UE may transmit an acknowledgment (ACK) after the K1 slot from the PDSCH. Additionally or alternatively, if the L1-RSSI is above the EDT, the PDSCH may be cancelled.

[0249] According to some implementations, the UE may be configured by a higher layer (e.g., RRC or MAC-CE) to perform periodic CSI reporting via PUCCH transmission. Periodic CSI reporting may also correspond to CSI reporting settings and associated CSI resource settings, which can also be configured via a higher layer. In addition to including L1-RSSI reporting as part of the CCA procedure, L1-RSSI quantization may also correspond to a 1-bit quantization comparison with the EDT. In some implementations, this 1-bit quantization comparison may be used to minimize the PUCCH payload size. Additionally or alternatively, according to some implementations, the PUCCH resources used for reporting quantized L1-RSSI may also include a PUCCH resource index configured by higher-layer signaling (such as RRC or MAC-CE signaling). Additionally or alternatively, a new field may be introduced for the PUCCH resource index indication. In some implementations, the PUCCH resources may be determined by the indicated PUCCH resources used for HARQ-ACK reporting. Furthermore, according to some implementation schemes, for uplink (e.g., UCI) collision handling, the priority of L1-RSSI on PUCCH may be equal to or higher / lower than the priority of L1-RSRP on PUCCH.

[0250] In some implementations, the UE may perform CCA sensing after receiving the PDCCH to determine whether the medium (e.g., the channel) is busy. According to some implementations, the UE may be configured for a one-time sensing event of 8 or 5 microseconds. Additionally or alternatively, the UE may be configured to perform an eCCA procedure in which the UE utilizes an 8-microsecond sensing event, followed by 0-3 consecutive 5-microsecond time-slot sensing events.

[0251] In some implementations, the quantized L1-RSSI may utilize the same HARQ ID as the PDSCH scheduler used for the UCI mapping procedure. For example, according to some implementations, the quantized L1-RSSI may be multiplexed with an ACK used for another HARQ procedure based on the corresponding HARQ codebook. Additionally or alternatively, the quantized L1-RSSI may be reported independently (e.g., not based on the corresponding HARQ codebook). Therefore, in some implementations, the UE may need to discard the HARQ-ACK upon detecting a collision.

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

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

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

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

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

[0257] 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 method for wireless communication, the method comprising: Request the ability to receive measurement reports from the base station (BS); Transmit an indication of the measurement reporting capability of the user equipment (UE) to the BS; The BS receives signaling including a Channel State Information (CSI) request trigger, wherein the CSI request trigger is implicitly indicated by the BS through the reuse of one or more bits of downlink control information DCI format 1-1 or DCI format 1-2. In response to receiving the CSI request, a measurement report is transmitted to the base station, wherein the measurement report includes at least one Received Signal Strength Indicator (RSSI) measurement.

2. The method according to claim 1, wherein, The measurement report is an aperiodic channel state information (AP-CSI) report, and the at least one RSSI measurement is a Layer 1 (L1) RSSI measurement.

3. The method according to claim 1, further comprising: For the at least one RSSI measurement, at least one of the existing processing timeline and existing priority rules corresponding to the reference signal received power RSRP measurement is reused.

4. The method according to claim 1, further comprising: Perform the at least one RSSI measurement in the time domain.

5. The method according to claim 4, wherein, The measurement time of the at least one RSSI measurement in the time domain corresponds to one orthogonal frequency division multiplexing (OFDM) symbol of a 120 kHz subcarrier spacing (SCS), three OFDM symbols of a 480 kHz SCS, or five OFDM symbols of a 960 kHz SCS.

6. The method according to claim 4, wherein, The at least one RSSI measurement in the time domain is performed using a receive beam associated with the active transport configuration indicator (TCI) of the signaling.

7. The method according to claim 4, wherein, The zero-power channel state information reference signal ZP-CSI-RS is characterized for the at least one RSSI measurement in the time domain.

8. The method according to claim 1, wherein, The at least one RSSI measurement is performed based on one or more symbols within or across time slots.

9. A method for wireless communication, the method comprising: Request the ability to transmit measurement report to the user equipment (UE); Indication of the UE's ability to receive measurement reports from the UE. In response to the indication received regarding the UE's measurement reporting capability, signaling is transmitted to the UE, wherein the signaling includes a request trigger and downlink control information (DCI), the DCI including scheduling information for subsequent transmissions; One or more bits of the DCI format 1-1 or DCI format 1-2 are reused as part of an implicit indication of the triggering of the request. as well as The UE receives a measurement report, wherein the measurement report includes at least one Received Signal Strength Indicator (RSSI) measurement.

10. The method according to claim 9, wherein, The measurement report is an aperiodic channel state information (AP-CSI) report, and the at least one RSSI measurement is a Layer 1 (L1) RSSI measurement.

11. The method of claim 9, wherein the at least one RSSI measurement is in the time domain.

12. The method according to claim 11, wherein, The measurement time of the at least one RSSI measurement in the time domain corresponds to one orthogonal frequency division multiplexing (OFDM) symbol of a 120 kHz subcarrier spacing (SCS), three OFDM symbols of a 480 kHz SCS, or five OFDM symbols of a 960 kHz SCS.

13. The method according to claim 11, wherein, The at least one RSSI measurement in the time domain is performed using a receive beam associated with the active transport configuration indicator (TCI) of the signaling.

14. The method according to claim 11, wherein, The zero-power channel state information reference signal ZP-CSI-RS is characterized for the at least one RSSI measurement in the time domain.

15. The method according to claim 9, wherein, The at least one RSSI measurement is performed based on one or more symbols within or across time slots.

16. An apparatus for wireless communication, comprising: A processor configured to perform the method according to any one of claims 1-8 when executing instructions stored in memory.

17. The apparatus of claim 16, further comprising: A radio component, which is operatively coupled to the processor.

18. An apparatus for wireless communication, comprising: A processor configured to perform the method according to any one of claims 9-15 when executing instructions stored in memory.

19. A non-transitory computer-readable storage medium storing program instructions executable by one or more processors to cause a base station (BS) to perform the method according to any one of claims 9-15.

20. A non-transitory computer-readable storage medium storing program instructions executable by one or more processors to cause a user equipment (UE) to perform the method according to any one of claims 1-8.

Images