Design for CSI Report-Based UE Initiative Beam Display

Abstract

A method for providing a User Equipment (UE) Initiated Beam Report (UIBR) to a base station (BS) in a wireless communication system comprises: decoding configuration information from the BS in the UE—the configuration information indicates a plurality of Channel State Information (CSI) reporting locations—; determining in the UE to include or exclude a UIBR in each of the plurality of CSI reporting locations; and, if the UE determines to include a UIBR in one of the plurality of CSI reporting locations, encoding the UIBR in the UE for transmission to the BS from that CSI reporting location.

Description

Technology Field

[0001] Embodiments of the present invention relate to wireless communication comprising devices, systems, and methods for facilitating UE-initiated / event-driven beam management to reduce overhead and latency in wireless communication systems. Background Technology

[0002] The usage of wireless communication systems is increasing rapidly. Over the past few years, wireless devices such as smartphones and tablet computers have become increasingly sophisticated. Many mobile devices now, in addition to supporting phone calls, provide access to the Internet, email, text messaging, and navigation using the Global Positioning System (GPS), and can run sophisticated applications that utilize these capabilities.

[0003] LTE (Long Term Evolution) has been the technology of choice for most wireless network operators worldwide, providing mobile broadband data and high-speed internet access to their subscriber bases. LTE was first proposed in 2004 and first standardized in 2008. Since then, as the use of wireless communication systems has expanded exponentially, there has been an increasing demand from wireless network operators to support higher capacity for higher-density mobile broadband users. In 2015, research on new radio access technology (RAT) began, and in 2017, the first release of Fifth Generation New Radio (5G NR) was standardized.

[0004] 5G-NR, also simply referred to as NR, supports ultra-reliable, massive machine-type communications between devices with lower latency and / or lower battery consumption, while providing higher capacity to higher-density mobile broadband users compared to LTE. Additionally, NR can allow for more flexible scheduling than current LTE. Consequently, efforts to utilize higher throughputs possible at higher frequencies are being made in the ongoing development of NR.

[0005] Wireless communication systems provide mobility through the use of battery-powered user equipment (UE) that communicates with network components such as base stations (BS), which may be referred to as gNBs or gNodeBs.

[0006] The embodiments relate to methods for providing a user equipment (UE)-initiated beam report (UIBR) to a base station (BS) in a wireless communication, more specifically, in a wireless communication system, the method comprising: decoding configuration information from the BS in the UE - the configuration information indicates a plurality of channel state information (CSI) reporting occasions -; determining in the UE to include or exclude a UIBR in each of the plurality of CSI reporting occasions; and if the UE determines to include a UIBR in one of the plurality of CSI reporting occasions, encoding the UIBR in the UE for transmission to the BS from that CSI reporting occasion.

[0007] The embodiments relate to methods of wireless communication, more specifically, wireless communication performed by a base station (BS), the method comprising: encoding configuration information for transmission to a user equipment (UE) at the BS, wherein the configuration information indicates a plurality of channel state information (CSI) reporting locations; monitoring each of the CSI reporting locations at the BS for a UE-initiated beam report (UIBR) from the UE; and decoding the UIBR transmitted by the UE at one of the CSI reporting locations at the BS.

[0008] The embodiments relate to wireless communication, more specifically, methods of wireless communication performed by a user device (UE), the method comprising: decoding configuration information transmitted by a base station (BS) in the UE; determining a set of channel state information (CSI) processing units (CSI processing units, CPUs) occupied in the UE based on the configuration information; and counting CPUs for UIBR regardless of whether the UE transmits a UE-initiated beam report (UIBR) to the BS.

[0009] The techniques described herein may be implemented and / or used with a number of different types of devices, including but not limited to unmanned aerial vehicles (UAVs), unmanned aerial controllers (UACs), base stations, access points, cellular phones, tablet computers, wearable computing devices, portable media players, the Internet of Things (IOT), and various other computing devices.

[0010] The content of the present invention is intended to provide a brief overview of some of the subject matter described herein. Accordingly, it will be understood that the features described above are merely examples and should not be interpreted to limit the scope or technical concept of the subject matter described herein in any way. Other features, embodiments, and advantages of the subject matter described herein will become apparent from the following detailed description, drawings, and claims. Brief explanation of the drawing

[0011] A better understanding of the subject of the invention can be obtained when the following detailed description of various embodiments is considered together with the accompanying drawings. FIG. 1a illustrates an exemplary wireless communication system according to some embodiments. FIG. 1b illustrates an example of a base station and an access point communicating with a user equipment (UE) device according to some embodiments. FIG. 2 illustrates an exemplary block diagram of a base station according to some embodiments. FIG. 3 illustrates an exemplary block diagram of a server according to some embodiments. FIG. 4 illustrates an exemplary block diagram of a UE according to some embodiments. FIG. 5 illustrates an exemplary block diagram of a cellular communication circuit section according to some embodiments. FIG. 6 illustrates an example of a baseband processor architecture for a UE according to some embodiments. FIG. 7 illustrates an exemplary block diagram of an interface of a baseband circuit section according to some embodiments. FIG. 8 illustrates an example of a control plane protocol stack according to some embodiments. FIG. 9 illustrates an example of a user plane protocol stack according to some embodiments. FIG. 10 illustrates an example of a drawing showing legacy CSI reporting between a base station and user equipment according to some embodiments. FIG. 11 illustrates an example of a drawing showing CSI reporting between a base station and user equipment according to some embodiments. FIG. 12 illustrates an example of a drawing showing CSI reporting occupations related to UE initiation / event-driven reports according to some embodiments. FIG. 13 illustrates an example of a channel state report (CSR) according to some embodiments. FIG. 14 illustrates an example of a drawing showing CSI reporting between a base station and user equipment according to some embodiments. FIG. 15 illustrates an example of a drawing showing CSI reporting occupations related to channel status reports according to some embodiments. FIG. 16 illustrates a table showing examples of transmission configuration indicator (TCI) display schemes according to some embodiments. FIG. 17 is an example of an ASN.1 (Abstract Syntax Notation One) code according to some embodiments. FIGS. 18 to 20 each illustrate an exemplary method of UE initiation / event-driven reporting according to some embodiments. While the features described herein may be susceptible to various modifications and alternative forms, specific embodiments thereof are illustrated by way of example in the drawings and described in detail herein. However, it should be understood that the drawings and the detailed description thereof are not intended to limit the invention to the specific form disclosed, but on the contrary, the intention is to cover all modifications, equivalents, and alternatives within the spirit and scope of the subject matter as defined by the appended claims. Specific details for implementing the invention

[0012] Terms

[0013] The following is an explanation of the terms used in this disclosure:

[0014] Memory medium or memory – any of various types of non-transient memory devices or storage devices. The term “memory medium” is intended to include installation media, e.g., CD-ROM, floppy disk, or tape device; computer system memory or random access memory such as DRAM, DDR RAM, SRAM, EDO RAM, Rambus RAM, etc.; non-volatile memory such as flash, magnetic media, e.g., hard drive, or optical storage; registers, or other similar types of memory elements, etc. Memory media may include other types of non-transient memory as well as combinations thereof. Additionally, memory media may be located in a first computer system where programs are executed, or 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 medium” may include two or more memory media residing in different locations, e.g., different computer systems connected via a network. A memory medium can store program instructions that can be executed by one or more processors (e.g., implemented as computer programs).

[0015] Carrier medium - not only memory media as described above, but also physical transmission media such as buses and networks, and / or other physical transmission media that transmit signals such as electrical, electromagnetic, or digital signals.

[0016] Programmable hardware elements—include various hardware devices comprising multiple programmable function blocks connected via programmable interconnects. Examples include Field Programmable Gate Arrays (FPGAs), Programmable Logic Devices (PLDs), Field Programmable Object Arrays (FPOAs), and Complex PLDs (CPLDs). The programmable function blocks can range from fine-grained (combinatorial logic or lookup tables) to coarse-grained (arithmetic logic units or processor cores). Programmable hardware elements may also be referred to as "reconfigurable logic".

[0017] 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 appliances, personal digital assistants (PDAs), television systems, grid computing systems, or other devices or combinations of devices. Generally, the term “computer system” may be broadly defined to encompass any device (or combination of devices) having at least one processor that executes instructions from a memory medium.

[0018] User Equipment (UE) (or “UE Device”) – Any of the various types of computer system devices that are mobile or portable and perform wireless communication. Examples of UE devices include mobile phones or smartphones (e.g., iPhone™, Android™-based phones), portable gaming devices (e.g., Nintendo DS™, PlayStation Portable™, Gameboy Advance™, iPhone™), laptops, wearable devices (e.g., smartwatches, smart glasses), PDAs, portable Internet of Things devices, Internet of Things devices, music players, data storage devices, other handheld devices, unmanned aerial vehicles (UAVs) (e.g., drones), UAV controllers (UAV controllers, UACs), etc. Generally, the term “UE” or “UE Device” may be broadly defined to encompass any electronic, computing, and / or telecommunications device (or combination of devices) that is easily carried by a user and capable of wireless communication.

[0019] Base Station – The term “base station” has the full range of its general meaning, including but not limited to next-generation Node Bs (gNBs or gNodeBs), and includes at least a radio station installed at a fixed location and used to communicate with UEs as part of a wireless telephone system or radio system.

[0020] processing element (or processor)- Refers to various elements or combinations of elements capable of performing functions in devices such as user equipment or cellular network devices. Processing elements may include, for example, processors and associated memory, parts or circuits of individual processor cores, entire processor cores, processor arrays, circuits such as Application Specific Integrated Circuits (ASICs), programmable hardware elements such as Field Programmable Gate Arrays (FPGAs), as well as any of the various combinations of the above.

[0021] Channel - A medium used to transmit information from a transmitter to a receiver. It should be noted that since the characteristics of the term “channel” may vary depending on different wireless protocols, the term “channel” as used herein may be considered to be used in a manner consistent with the standards of the type of device for which this term is referenced. In some standards, channel width may be variable (e.g., depending on device capabilities, band conditions, etc.). For example, LTE may support scalable channel bandwidths of 1.4 MHz to 20 MHz. 5G NR may support scalable channel bandwidths of 5 MHz to 100 MHz in Frequency Range 1 (FR1) and up to 400 MHz in FR2. In other radio access technologies, WLAN channels may be 22 MHz wide, while Bluetooth channels may be 1 MHz wide. Other protocols and standards may include different definitions of a channel. Furthermore, some standards may define and use multiple types of channels, for example, different channels for uplink or downlink and / or different channels for different uses such as data, control information, etc.

[0022] Band - The term "band" has the full range of its general meaning and includes at least a section of the spectrum (e.g., radio frequency (RF) spectrum) where channels are used or set aside for the same purpose.

[0023] Automatically – Refers to an action or operation performed by a computer system (e.g., software executed by a computer system) or a device (e.g., circuits, programmable hardware elements, ASICs, etc.) without user input that directly specifies or performs the action or operation. Therefore, the term "automatically" is contrasted with actions performed or specified manually by a user, where the user provides input to perform the operation directly. While an automatic procedure may be initiated by input provided by a user, subsequent actions performed "automatically" are not specified by the user; that is, they are not performed "manually" by the user specifying each action to be performed. For example, a user filling out an electronic form by selecting each field and providing input that specifies information (e.g., by typing information, selecting checkboxes, radio selections, etc.) constitutes filling out the form manually, even though the computer system will update the form in response to the user actions. A form may be automatically filled out by a computer system, wherein the computer system (e.g., software running on the computer system) analyzes the fields of the form and fills out the form without any user input specifying the responses to the fields. As indicated above, the user may invoke the automatic filling of the form but does not participate in the actual filling out of the form (e.g., the user does not manually specify the responses to the fields, but rather they are completed automatically). This specification provides various examples of actions that are automatically performed in response to actions taken by the user.

[0024] Approximately - refers to a nearly correct or accurate value. For example, "approximately" may refer to a value within 1 to 10 percent of the accurate (or desired) value. However, it should be noted that the actual threshold value (or tolerance) may be application-dependent. For example, in some embodiments, "approximately" may mean within 0.1 percent of some specific or desired value, while in various other embodiments, the threshold may be, for example, 2 percent, 3 percent, 5 percent, etc., as desired or set by a specific application.

[0025] Concurrency – Refers to concurrent execution or performance where tasks, processes, or programs are executed in a manner that involves at least partial nesting. For example, concurrency may be implemented using "strong" or strict concurrency when tasks are executed in parallel (at least partially) with respect to individual computational elements, or using "weak concurrency" when tasks are executed in an interleaving manner, for example, through the time multiplexing of execution threads.

[0026] Information Element (IE) - A group of information that may be included within a signaling message or data flow transmitted through an interface.

[0027] rN – As used herein, rN refers to a UE capable of supporting 3GPP Release N when used with an information element (IE). For example, r18 indicates a UE capable of supporting 3GPP Release 18. A UE capable of supporting a release greater than N may also be capable of supporting 3GPP Release N. A UE that cannot support 3GPP Release N may not be able to support IEs containing rN.

[0028] Various components may be described as being "configured to" perform a task or tasks. In such a context, "configured to" is a broad description generally meaning "having a structure that performs a task or tasks during operation." Thus, a component may be configured to perform a task even when the component is not currently performing the task (e.g., a set of electrical conductors may be configured to electrically connect two modules even when one module is not connected to the other). In some contexts, "configured to" may be a broad description of a structure generally meaning "having a circuit part that performs a task or tasks during operation." Thus, a component may be configured to perform a task even when the component is not currently in an "on" state. Generally, the circuit part forming the structure corresponding to "configured to" may include hardware circuits.

[0029] Various components may be described as performing a single task or a number of tasks for convenience in description. Such descriptions should be interpreted as containing the phrase “configured to perform.” Referring to a component configured to perform one or more tasks is clearly intended not to apply the interpretation of 35 USC § 112(f) to that component.

[0030] Exemplary embodiments may be further understood by referring to the following description and the associated accompanying drawings, wherein like elements are provided with the same reference numerals. The exemplary embodiments relate to devices, systems, and methods for reducing energy consumption by network components, e.g., base stations, within wireless communication systems.

[0031] Exemplary embodiments describe communication between a next-generation node B (gNB) and a user equipment (UE). However, references to the gNB or UE are provided for illustrative purposes only. Exemplary embodiments may be utilized with any electronic component consisting of hardware, software, and / or firmware to establish a connection to a network and to help reduce energy consumption by network components within wireless communication systems. Accordingly, as described herein, the gNB or UE is used to represent any suitable type of electronic component.

[0032] Exemplary embodiments are also described with respect to a 5th generation (5G) New Radio (NR) network that can configure a UE to help reduce energy consumption by network components within wireless communication systems. However, references to 5G NR networks are provided only for exemplary purposes. Exemplary embodiments may be utilized with any suitable type of network.

[0033] Throughout this description, various information elements (IEs) are referred to by specific names. These names are merely examples, and it should be understood that the IEs that return the information referred to throughout this description may be referred to by different names by various entities.

[0034] FIGS. 1A and FIGS. 1B: Communication systems

[0035] FIG. 1a illustrates a simplified exemplary wireless communication system according to some embodiments. It should be noted that the system of FIG. 1a is merely an example of a possible system and that the features of the present disclosure may be implemented in any of the various systems as desired.

[0036] As described, an exemplary wireless communication system includes a base station (102A) that communicates with one or more user devices (106A, 106B, etc. to 106N) through a transmission medium. Each of the user devices may be referred to herein as "User Equipment (UE)". Accordingly, the user devices (106) are referred to as UEs or UE devices.

[0037] The base station (BS) (102A) may be a base transceiver station (BTS) or a cell site ("cellular base station") and may include hardware that enables wireless communication with UEs (106A to 106N).

[0038] The communication area (or coverage area) of a base station may be referred to as a “cell.” The base station (102A) and UEs (106) may be configured to communicate over a transmission medium using any of the various radio access technologies (RATs) also referred to as radio communication standards, such as GSM, UMTS, LTE, LTE-Advanced (LTE-A), 5G New Radio (5G NR), 6G, etc. Note that when the base station (102A) is implemented in the context of LTE, also referred to as the Evolved Universal Terrestrial Radio Access Network (E-UTRAN), it may alternatively be referred to as an ‘eNodeB’ or ‘eNB’. Note that when the base station (102A) is implemented in the context of 5G NR, it may alternatively be referred to as a ‘gNodeB’ or ‘gNB’.

[0039] As described, the base station (102A) may also be equipped to communicate with the network (100) (e.g., among various possibilities, a core network of a cellular service provider, a telecommunications network such as a public switched telephone network (PSTN) and / or the Internet). Thus, the base station (102A) can facilitate communication between user devices and / or between user devices and the network (100). In particular, the cellular base station (102A) can provide various telecommunications capabilities to the UEs (106), such as voice, SMS and / or data services.

[0040] Accordingly, a base station (102A) and other similar base stations (e.g., base stations (102B...102N)) operating according to the same or different cellular communication standards may be provided as a network of cells, and these may provide continuous or nearly continuous overlapping services to UEs (106A to 106N) and similar devices across a geographical area through one or more cellular communication standards.

[0041] Accordingly, while the base station (102A) may serve as a "serving cell" for the UEs (106A to 106N) as exemplified in FIG. 1a, each UE (106) may also receive signals (which may be provided by base stations (102B to 102N) and / or any other base stations) from one or more other cells that may be referred to as "neighbor cells" (and possibly within their communication range). Additionally, such cells may facilitate communication between user devices and / or between user devices and the network (100). Such cells may include "macro" cells, "micro" cells, "pico" cells, and / or cells providing any of various other granularities of service area size. For example, the base station (102A, 102B) exemplified in FIG. 1a may be a macro cell, while the base station (102N) may be a micro cell. Other configurations are also possible.

[0042] In some embodiments, the base station (102A) may be a next-generation base station, e.g., a 5G New Radio (5G NR) base station or a “gNB”. In some embodiments, the gNB may be connected to a legacy Evolved Packet Core (EPC) network and / or an NR Core (NR core, NRC) network. Additionally, the gNB cell may include one or more transition and reception points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0043] Note that the UE (106) may be able to communicate using multiple wireless communication standards. For example, the UE (106) may 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.) in addition to at least one cellular communication protocol (e.g., GSM, UMTS (e.g., associated with WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2 CDMA2000 (e.g., 1xRTT, 1xEV-DO, HRPD, eHRPD), etc.). Also, or alternatively, the UE (106) may be configured to communicate using one or more GNSS (global navigational satellite systems) (e.g., GPS or GLONASS), one or more mobile television broadcasting standards (e.g., ATSC-M / H or DVB-H), and / or, if desired, any other radio communication protocol. Other combinations of radio communication standards (including more than two radio communication standards) are also possible.

[0044] In some embodiments, the base station (102A) may select a paging configuration and a PEI configuration for the UEs (106). The base station (102A) may encode the paging configuration and the PEI configuration and transmit them to the UEs (106) as part of the registration process. Using the paging configuration, the UEs (106) may determine which PO and PF to monitor in a paging cycle. Using the PEI configuration, the UEs (106) may determine the radio frame that carries the relevant PEI.

[0045] FIG. 1b illustrates a user device (106) (e.g., one of devices (106A to 106N)) communicating with a base station (102) and an access point (112) according to some embodiments. The UE (106) may be a device having both cellular communication capabilities and non-cellular communication capabilities (e.g., Bluetooth, Wi-Fi, etc.), such as a mobile phone, a handheld device, a computer or tablet, or virtually any type of wireless device.

[0046] The UE (106) may include a processor configured to execute program instructions stored in memory. The UE (106) may perform any of the method embodiments described herein by executing such stored instructions. Alternatively or additionally, the UE (106) may include a programmable hardware element, such as a field programmable gate array (FPGA), configured to perform any of the method embodiments described herein, or any part of any of the method embodiments described herein.

[0047] The UE (106) may include one or more antennas for communicating using one or more wireless communication protocols or technologies. In some embodiments, the UE (106) may be configured to communicate using, for example, CDMA2000 (1xRTT / 1xEV-DO / HRPD / eHRPD), LTE / LTE-Advanced, or 5G NR using a single shared radio and / or GSM, LTE, LTE-Advanced, or 5G NR using a single shared radio. The shared radio may be coupled to a single antenna or may be coupled to multiple antennas for performing wireless communications (e.g., for MIMO). Generally, the radio may include any combination of a baseband processor, an analog RF signal processing circuitry (e.g., including filters, mixers, oscillators, amplifiers, etc.), or a digital processing circuitry (e.g., for digital modulation as well as other digital processing). Similarly, a radio can implement one or more receiving and transmitting chains using the aforementioned hardware. For example, the UE (106) can share one or more parts of the receiving and / or transmitting chains among a number of wireless communication technologies such as those discussed above.

[0048] In some embodiments, the 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. As an additional possibility, the UE (106) may include one or more radios shared among a number of wireless communication protocols, and one or more radios used exclusively by a single wireless communication protocol. For example, the UE (106) may include a shared radio for communicating using either LTE or 5G NR (or LTE or 1xRTT or LTE or GSM), and separate radios for communicating using Wi-Fi and Bluetooth, respectively. Other configurations are also possible.

[0049] Fig. 2: Block diagram of a base station (gNB)

[0050] FIG. 2 illustrates an exemplary block diagram of a base station (102) according to some embodiments. Note that the base station of FIG. 2 is merely one example of a possible base station. As illustrated, the base station (102) may include processor(s) (204) capable of executing program instructions for the base station (102). The processor(s) (204) may also be coupled to a memory management unit (MMU) (240) or other circuits or devices that may be configured to receive addresses from the processor(s) (204) and convert those addresses into locations within memory (e.g., memory (260) and read-only memory (ROM) (250)).

[0051] The base station (102) may include at least one network port (270). The network port (270) may be coupled to a telephone network and configured to provide access to the telephone network to a plurality of devices, such as UE devices (106), as described in FIGS. 1 and FIGS. 2 above.

[0052] Alternatively, the network port (270) (or additional network port) may be configured to be coupled to a cellular network, for example, a 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 devices (106). In some cases, the network port (270) may be coupled to a telephone network through the core network, and / or the core network may provide a telephone network (e.g., between other UE devices serviced by a cellular service provider).

[0053] In some embodiments, the base station (102) may be a next-generation base station, e.g., a 5G New Radio (5G NR) base station or a “gNB”. In such embodiments, the base station (102) may be connected to a legacy Evolved Packet Core (EPC) network and / or an NR Core (NRC) network. Additionally, the base station (102) may be considered a 5G NR cell and may include one or more Transition and Receive Points (TRPs). Additionally, a UE capable of operating according to 5G NR may be connected to one or more TRPs within one or more gNBs.

[0054] The base station (102) may include at least one antenna (234) and possibly multiple antennas. At least one antenna (234) may be configured to operate as a wireless transceiver and may be further configured to communicate with UE devices (106) via a radio (230). The antenna (234) communicates with the radio (230) via a communication chain (232). The communication chain (232) may be a receiving chain, a transmitting chain, or both. The radio (230) may be configured to communicate via various wireless communication standards, including but not limited to 5G NR, LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

[0055] A base station (102) may be configured to communicate wirelessly using multiple wireless communication standards. In some cases, the base station (102) may include multiple radios that enable the base station (102) to communicate according to multiple wireless communication technologies. For example, as one possibility, the base station (102) may include an LTE radio for communicating according to LTE as well as a 5G NR radio for communicating according to 5G NR. In such a case, the base station (102) may be able to operate as both an LTE base station and a 5G NR base station. As another possibility, the base station (102) may include a multimode radio capable of communicating according to any of the 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.).

[0056] As further subsequently described in this specification, the base station (102) may include hardware and software components for implementing or supporting the implementation of the features described in this specification. The processor (204) of the base station (102) may be configured to implement or support the implementation of some or all of the methods described in this specification by executing program instructions stored, for example, in a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively, the processor (204) may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC), or as a combination thereof. Alternatively (or additionally), the processor (204) of the base station (102) may be configured to implement or support the implementation of some or all of the features described in this specification together with one or more of the other components (230, 232, 234, 240, 250, 260, 270).

[0057] Additionally, as described in this specification, the processor(s) (204) may be composed of one or more processing elements. In other words, one or more processing elements may be included in the processor(s) (204). Accordingly, the processor(s) (204) may include one or more integrated circuits (ICs) configured to perform the functions of the processor(s) (204). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the processor(s) (204).

[0058] Additionally, as described in this specification, the radio (230) may be composed of one or more processing elements. In other words, one or more processing elements may be included in the radio (230). Accordingly, the radio (230) may include one or more integrated circuits (ICs) configured to perform the functions of the radio (230). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the radio (230).

[0059] In some embodiments, the base station or gNB (102), and / or its processors (204) can determine, and may be configured to determine, a paging configuration that reduces energy consumption by network components within wireless communication systems, such as the base station or gNB (102), for user equipment.

[0060] Fig. 3: Server block diagram

[0061] FIG. 3 illustrates an exemplary block diagram of a server (104) according to some embodiments. Note that the server in FIG. 3 is merely an example of a possible server. As illustrated, the server (104) may include processor(s) (344) capable of executing program instructions for the server (104). The processor(s) (344) may also be coupled to a memory management unit (MMU) (374) or other circuits or devices that may be configured to receive addresses from the processor(s) (344) and translate those addresses into locations within memory (e.g., memory (364) and read-only memory (ROM) (354)).

[0062] The server (104) may be configured to provide access to network functions to a plurality of devices, such as a base station (102) and UE devices (106), as further described in this specification.

[0063] In some embodiments, the server (104) may be part of a radio access network, such as a 5G New Radio (5G NR) radio access network. In some embodiments, the server (104) may be connected to a legacy Evolved Packet Core (EPC) network and / or an NR Core (NRC) network.

[0064] As described in this specification, the server (104) may include hardware and software components to implement or support the implementation of the features described in this specification. The processor (344) of the server (104) may be configured to implement or support the implementation of some or all of the methods described in this specification by, for example, executing program instructions stored in a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively, the processor (344) may be configured as a programmable hardware element such as a field programmable gate array (FPGA), as an application-specific integrated circuit (ASIC), or as a combination thereof. Alternatively (or additionally), the processor (344) of the server (104) may be configured to implement or support the implementation of some or all of the features described in this specification together with one or more of the other components (354, 364, and / or 374).

[0065] Additionally, as described in this specification, the processor(s) (344) may be composed of one or more processing elements. In other words, one or more processing elements may be included in the processor(s) (344). Accordingly, the processor(s) (344) may include one or more integrated circuits (ICs) configured to perform the functions of the processor(s) (344). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the processor(s) (344).

[0066] Fig. 4: Block diagram of the User Equipment (UE)

[0067] FIG. 4 illustrates an exemplary simplified block diagram of a communication device (106) according to some embodiments. Note that the block diagram of the communication device in FIG. 4 is merely one example of a possible communication device. According to embodiments, the communication device (106) may be, among other devices, 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, an unmanned aerial vehicle (UAV), a UAV controller (UAC), and / or a combination of devices. As illustrated, the communication device (106) may include a set of components (400) configured to perform core functions. For example, such a set of components may be implemented as a system on chip (SOC), which may include parts for various purposes. Alternatively, such a set of components (400) may be implemented as separate components or groups of components for various purposes. A set of components (400) can be coupled to various other circuits of the communication device (106) (e.g., communicably; directly or indirectly).

[0068] For example, the communication device (106) may include various types of memory (e.g., NAND flash (410)), an input / output interface such as a connector I / F (420) (e.g., for connecting to a computer system; a dock; a charging station; input devices such as a microphone, camera, keyboard; output devices such as a speaker; etc.), a display (460) that may be integrated with or outside the communication device (106), a cellular communication circuit (430) for example 5G NR, LTE, GSM, etc., and a short-to-medium range wireless communication circuit (429) (e.g., Bluetooth™ and WLAN circuit). In some embodiments, the communication device (106) may include a wired communication circuit (not shown), such as a network interface card for example Ethernet.

[0069] The cellular communication circuit (430) may be coupled to one or more antennas, such as antennas (435a-b) and antenna (436) as illustrated in FIG. 4 (e.g., communicably; directly or indirectly). The short-to-medium range wireless communication circuit (429) may also be coupled to one or more antennas, such as antennas (437, 438) as illustrated (e.g., communicably; directly or indirectly). Alternatively, the short-to-medium range wireless communication circuit (429) may be coupled to antennas (435, 436) (e.g., communicably; directly or indirectly) in addition to, or instead of being coupled to, antennas (437, 438). The short-to-medium range wireless communication circuit (429) and / or cellular communication circuit (430) may include a number of receiving chains and / or a number of transmitting chains for receiving and / or transmitting a number of spatial streams in, for example, a multiple-input multiple output (MIMO) configuration.

[0070] In some embodiments, as further described below, the cellular communication circuit (430) may include dedicated receiving chains (e.g., a first receiving chain for LTE and a second receiving chain for 5G NR) for a plurality of RATs (including dedicated processors and / or radios and / or capable of communicating with them; directly or indirectly coupled). Additionally, in some embodiments, the cellular communication circuit (430) may include a single transmitting chain that can be switched between radios dedicated to specific RATs. For example, the first radio may be dedicated to the first RAT, e.g., LTE, and may communicate with a transmitting chain and a dedicated receiving chain shared with an additional radio (e.g., a second radio that may be dedicated to the second RAT (e.g., 5G NR) and may communicate with the dedicated receiving chain and the shared transmitting chain).

[0071] The communication device (106) may also include one or more user interface elements and / or be configured to be used with them. The user interface elements may include any of various elements, such as a display (460) (which may be a touchscreen display), a keyboard (which may be a separate keyboard or implemented as part of a touchscreen display), a mouse, a microphone and / or speakers, one or more cameras, one or more buttons, and / or any of various other elements capable of providing information to the user and / or receiving or interpreting user input.

[0072] The communication device (106) may further include one or more smart cards (445) that include a Subscriber Identity Module (SIM) function, such as one or more Universal Integrated Circuit Card (UICC) cards (445). Note that the term “SIM” or “SIM entity” is intended to include any of the various types of SIM implementations or SIM functions, whether removable or embedded, such as one or more UICC(s) cards (445), one or more eUICCs, one or more eSIMs, 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 a SIM function. Thus, each SIM may be a single smart card that can be embedded, for example, soldered onto a circuit board within the UE (106), or each SIM (410) may be implemented as a removable smart card. Accordingly, the SIM(s) may be one or more removable smart cards (e.g., UICC cards sometimes referred to as "SIM cards"), and / or the SIM(s) (410) may be one or more embedded cards (e.g., embedded UICC(eUICC) sometimes referred to as "eSIMs" or "eSIM cards"). In some embodiments (e.g., where the SIM(s) include an eUICC), one or more of the SIM(s) may implement an embedded SIM(eSIM) function; and in such embodiments, one of the SIM(s) may execute multiple SIM applications. Each of the SIM(s) may include components such as a processor and / or memory; instructions for performing SIM / eSIM functions may be stored in memory and executed by the processor.In some embodiments, the UE (106) may include, as desired, a combination of removable smart cards and fixed / non-removable smart cards (e.g., one or more eUICC cards implementing eSIM functionality). For example, the 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 considered.

[0073] As mentioned above, in some embodiments, the UE (106) may include two or more SIMs. Inclusion of two or more SIMs within the UE (106) may allow the UE (106) to support two different phone numbers and allow the UE (106) to communicate on two or more corresponding respective networks. For example, the first SIM may support a first RAT such as LTE, and the second SIM (410) may support a second RAT such as 5G NR. Other implementations and RATs are, of course, possible. In some embodiments, when the UE (106) includes two SIMs, the UE (106) may support a DSDA (Dual SIM Dual Active) function. The DSDA function can allow the UE (106) to be connected to two networks simultaneously (and to use two different RATs), or to maintain two connections supported by two different SIMs simultaneously using the same or different RATs on the same or different networks. The DSDA function can also allow the UE (106) to receive voice calls or data traffic simultaneously from either phone number. In some embodiments, voice calls may be packet-switched communication. That is, voice calls may be received using VoLTE (voice over LTE) technology and / or VoNR (voice over NR) technology. In some embodiments, the UE (106) may support a DSDS (Dual SIM Dual Standby) function. The DSDS function can allow one of the two SIMs in the UE (106) to be in a standby state waiting for a voice call and / or data connection. In DSDS, when a call / data is established on one SIM, the other SIM is no longer active.In some embodiments, the DSDx function (either the DSDA function or the DSDS function) may be implemented as a single SIM (e.g., eUICC) running multiple SIM applications for different carriers and / or RATs.

[0074] As illustrated, the SOC (400) may include a processor(s) (402) capable of executing program instructions for a communication device (106) and a display circuit (404) capable of performing graphics processing and providing display signals to a display (460). The processor(s) (402) may also be coupled to a memory management unit (MMU) (440) which may be configured to receive addresses from the processor(s) (402) and convert those addresses into locations within memory (e.g., memory (406), read-only memory (ROM) (450), NAND flash memory (410)), and / or other circuits or devices, such as a display circuit (404), a short-to-medium range wireless communication circuit (429), a cellular communication circuit (430), a connector I / F (420), and / or a 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(s) (402).

[0075] As described in this specification, the communication device (106) may include hardware and software components for implementing the above features for the communication device (106) to communicate a scheduling profile for power saving to a network. The processor (402) of the communication device (106) may be configured to implement some or all of the features described in this specification by executing program instructions stored, for example, in a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively (or additionally), the processor (402) may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC). Alternatively (or additionally), the processor (402) of the communication device (106) may be configured to implement some or all of the features described herein together with one or more of the other components (400, 404, 406, 410, 420, 429, 430, 440, 445, 450, 460).

[0076] Additionally, as described in this specification, the processor (402) may include one or more processing elements. Accordingly, the processor (402) may include one or more integrated circuits (ICs) configured to perform the functions of the processor (402). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the processor(s) (402).

[0077] Additionally, as described in this specification, the cellular communication circuit (430) and the short-to-medium range wireless communication circuit (429) may each include one or more processing elements. That is, one or more processing elements may be included within the cellular communication circuit (430), and similarly, one or more processing elements may be included within the short-to-medium range wireless communication circuit (429). Accordingly, the cellular communication circuit (430) may include one or more integrated circuits (ICs) configured to perform the functions of the cellular communication circuit (430). Additionally, each integrated circuit may include a circuit (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). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of a short-range to medium-range wireless communication circuit section (429).

[0078] In some embodiments, the UE (106) and / or its processors (402) may be configured to identify paging configurations that reduce energy consumption in the UE (106) and gNB (102) in the UE (106) and / or may be able to identify.

[0079] Fig. 5: Block diagram of the cellular communication circuit section

[0080] FIG. 5 illustrates an exemplary simplified block diagram of a cellular communication circuit according to some embodiments. Note that the block diagram of the cellular communication circuit in FIG. 5 is merely one example of a possible cellular communication circuit. According to the embodiments, the cellular communication circuit (530), which may be a cellular communication circuit (430), may be included in a communication device such as the communication device (106) described above. As mentioned above, the communication device (106) may be, among other devices, 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, and / or a combination of devices.

[0081] The cellular communication circuit (530) may be coupled (e.g., communicably; directly or indirectly) to one or more antennas, such as antennas (435a-b) and antenna (436) as illustrated in FIG. 4. In some embodiments, the cellular communication circuit (530) may include dedicated receiving chains for a number of RATs (including dedicated processors and / or radios and / or coupled to them communicably; directly or indirectly, e.g., a first receiving chain for LTE and a second receiving chain for 5G NR). For example, as illustrated in FIG. 5, 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, for example, and the modem (520) may be configured for communication according to a second RAT, such as 5G NR, for example.

[0082] As described, the modem (510) may include one or more processors (512) and a memory (516) that communicates with the processors (512). The modem (510) may communicate with a radio frequency (RF) front end (535). The RF front end (535) may include circuitry for transmitting and receiving radio signals. For example, the RF front end (535) may include a receiving circuitry (RX) (532) and a transmitting circuitry (TX) (534). In some embodiments, the receiving circuitry (532) may communicate with a downlink (DL) front end (550) that may include circuitry for receiving radio signals through an antenna (335a).

[0083] Similarly, the modem (520) may include one or more processors (522) and a memory (526) that communicates with the processors (522). The modem (520) may communicate with an RF front end (540). The RF front end (540) may include circuitry for transmitting and receiving radio signals. For example, the RF front end (540) may include a receiving circuitry (542) and a transmitting circuitry (544). In some embodiments, the receiving circuitry (542) may communicate with a DL front end (560) that may include circuitry for receiving radio signals through an antenna (335b).

[0084] In some embodiments, the switch (570) may couple the transmitting circuit (534) to the uplink (UL) front end (572). Additionally, the switch (570) may couple the transmitting circuit (544) to the UL front end (572). The UL front end (572) may include a circuit for transmitting radio signals through an antenna (336). Thus, when the cellular communication circuit (530) receives commands to transmit according to a first RAT (e.g., as supported by the modem (510)), the switch (570) may be switched to a first state that allows the modem (510) to transmit signals according to the first RAT (e.g., through a transmission chain including the transmitting circuit (534) and the UL front end (572). Similarly, when the cellular communication circuit (530) receives commands to transmit according to the second RAT (e.g., as supported by the modem (520)), the switch (570) may be switched to a second state that allows the modem (520) to transmit signals according to the second RAT (e.g., through a transmission chain including the transmission circuit (544) and the UL front end (572).

[0085] As described in this specification, the modem (510) may include hardware and software components for implementing the above features or for time-division multiplexing UL data for NSA NR operations, as well as various other techniques described in this specification. Processors (512) may be configured to implement some or all of the features described in this specification by executing program instructions stored, for example, in a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively (or additionally), the processor (512) may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC). Alternatively (or additionally), the processor (512) may be configured to implement some or all of the features described herein together with one or more of the other components (530, 532, 534, 535, 550, 570, 572, 335a, 335b, 336).

[0086] Additionally, as described in this specification, the processors (512) may include one or more processing elements. Accordingly, the processors (512) may include one or more integrated circuits (ICs) configured to perform the functions of the processors (512). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the processors (512).

[0087] Processors (522) may be configured to implement some or all of the features described herein by executing program instructions stored, for example, in a memory medium (e.g., a non-transient computer-readable memory medium). Alternatively (or additionally), the processor (522) may be configured as a programmable hardware element, such as a field programmable gate array (FPGA), or as an application-specific integrated circuit (ASIC). Alternatively (or additionally), the processor (522) may be configured to implement some or all of the features described herein in combination with one or more of other components (540, 542, 544, 550, 570, 572, 335, 336).

[0088] Additionally, as described in this specification, the processors (522) may include one or more processing elements. Accordingly, the processors (522) may include one or more integrated circuits (ICs) configured to perform the functions of the processors (522). Additionally, each integrated circuit may include a circuit section (e.g., a first circuit section, a second circuit section, etc.) configured to perform the functions of the processors (522).

[0089] In some embodiments, processors (512, 522) may be configured to cluster PFs, POs, and PEIs during paging cycles as further described herein.

[0090] Fig. 6: Block diagram of baseband processor architecture for UE

[0091] FIG. 6 illustrates exemplary components of a device (600) according to some embodiments. It should be noted that the device of FIG. 6 is merely an example of a possible system and that the features of the present disclosure can be implemented in any of the various UEs as desired.

[0092] In some embodiments, the device (600) may include an application circuit (602), a baseband circuit (604), a radio frequency (RF) circuit (606), a front-end module (FEM) circuit (608), one or more antennas (610), and a power management circuitry (PMC) (612) coupled together as illustrated. The components of the illustrated device (600) may be included in a UE (106) or a RAN node (102A). In some embodiments, the device (600) may include fewer elements (e.g., the RAN node may not utilize the application circuit (602) and instead may include a processor / controller for processing IP data received from the EPC). In some embodiments, the device (600) may include additional elements such as, for example, memory / storage, a display, a camera, a sensor, or an input / output (I / O) interface. In other embodiments, the components described below may be included in more than one device (e.g., the circuits may be individually included in more than one device for C-RAN (Cloud-RAN) implementations).

[0093] The application circuit (602) may include one or more application processors. For example, the application circuit (602) may include circuits such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled to or include memory / storage and may be configured to execute instructions stored in memory / storage so that various applications or operating systems can run on the device (600). In some embodiments, the processors of the application circuit (602) may process IP data packets received from the EPC.

[0094] The baseband circuit section (604) may include one or more circuit sections, such as, but not limited to, single-core or multi-core processors. The baseband circuit section (604) may include one or more baseband processors or control logic for processing baseband signals received from the receiving signal path of the RF circuit section (606) and for generating baseband signals for the transmitting signal path of the RF circuit section (606). The baseband processing circuit section (604) may interface with the application circuit section (602) for generating and processing baseband signals and for controlling the operations of the RF circuit section (606). For example, in some embodiments, the baseband circuit (604) may include a 3rd generation (3G) baseband processor (604A), a 4th generation (4G) baseband processor (604B), a 5th generation (5G) baseband processor (604C), or other baseband processor(s) (604D) for other existing generations, generations under development or to be developed in the future (e.g., 2nd generation (2G), 6th generation (6G), etc.). The baseband circuit (604) (e.g., one or more of the baseband processors (604A to 604D)) may process various radio control functions that enable communication with one or more radio networks through the RF circuit (606). In other embodiments, some or all of the functions of the baseband processors (604A to 604D) may be included in modules that are stored in memory (604G) and executed through a Central Processing Unit (CPU) (604E). Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc. In some embodiments, the modulation / demodulation circuit of the baseband circuit (604) may include Fast-Fourier Transform (FFT), precoding, or constellation mapping / demapping functions.In some embodiments, the encoding / decoding circuit of the baseband circuit (604) may include convolution, tail-biting convolution, turbo, Viterbi, or low density parity check (LDPC) encoder / decoder functions. Embodiments of modulation / demodulation and encoder / decoder functions are not limited to these examples and may include other suitable functions in other embodiments.

[0095] In some embodiments, the baseband circuit (604) may include one or more audio digital signal processors (DSPs) (604F). The audio DSPs (604F) may include elements for compression / decompression and echo removal, and in other embodiments, may include other suitable processing elements. The components of the baseband circuit may be suitably combined on a single chip, a single chipset, or, in some embodiments, placed on the same circuit board. In some embodiments, some or all of the components of the baseband circuit (604) and the application circuit (602) may be implemented together, for example, on a system-on-chip (SOC).

[0096] In some embodiments, the baseband circuit (604) may provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit (604) may support communication with an advanced universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), wireless local area networks (WLAN), or wireless personal area networks (WPAN). Embodiments in which the baseband circuit (604) is configured to support radio communications of more than one wireless protocol may be referred to as a multi-mode baseband circuit.

[0097] The RF circuit section (606) can enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuit section (606) may include switches, filters, amplifiers, etc. to facilitate communication with wireless networks. The RF circuit section (606) may include a receiving signal path that may include a circuit section for down-converting RF signals received from the FEM circuit section (608) and providing baseband signals to the baseband circuit section (604). The RF circuit section (606) may also include a transmitting signal path that may include a circuit section for up-converting baseband signals provided by the baseband circuit section (604) and providing RF output signals to the FEM circuit section (608) for transmission.

[0098] In some embodiments, the receiving signal path of the RF circuit (606) may include a mixer circuit (606a), an amplifier circuit (606b), and a filter circuit (606c). In some embodiments, the transmitting signal path of the RF circuit (606) may include a filter circuit (606c) and a mixer circuit (606a). The RF circuit (606) may also include a synthesizer circuit (606d) for synthesizing frequencies for use by the mixer circuit (606a) of the receiving signal path and the transmitting signal path. In some embodiments, the mixer circuit (606a) of the receiving signal path may be configured to downconvert RF signals received from the FEM circuit (608) based on the synthesized frequencies provided by the synthesizer circuit (606d). The amplifier circuit (606b) may be configured to amplify the down-converted signals, and the filter circuit (606c) may be a low-pass filter (LPF) or a band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. The output baseband signals may be provided to the baseband circuit (604) for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, but this is not mandatory. In some embodiments, the mixer circuit (606a) of the receiving signal path may include passive mixers, but the scope of embodiments is not limited in this respect.

[0099] In some embodiments, the mixer circuit (606a) of the transmission signal path may be configured to upconvert input baseband signals based on a synthesized frequency provided by the synthesizer circuit (606d) to generate RF output signals for the FEM circuit (608). The baseband signals may be provided by the baseband circuit (604) and may be filtered by the filter circuit (606c).

[0100] In some embodiments, the mixer circuit section (606a) of the receiving signal path and the mixer circuit section (606a) of the transmitting signal path may include two or more mixers and may be arranged for orthogonal downconversion and upconversion, respectively. In some embodiments, the mixer circuit section (606a) of the receiving signal path and the mixer circuit section (606a) of the transmitting signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuit section (606a) of the receiving signal path and the mixer circuit section (606a) may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuit section (606a) of the receiving signal path and the mixer circuit section (606a) of the transmitting signal path may be configured for super-heterodyne operation.

[0101] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, but the scope of the embodiments is not limited in this respect. In some alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuit (606) may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit (604) may include a digital baseband interface for communicating with the RF circuit (606).

[0102] In some dual-mode embodiments, separate radio IC circuits may be provided to process signals for each spectrum, but the scope of embodiments is not limited in this respect.

[0103] In some embodiments, the synthesizer circuit (606d) may be a fractional-N synthesizer or a fractional N / N+1 synthesizer, but the scope of embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit (606d) may be a synthesizer comprising a delta-sigma synthesizer, a frequency multiplier, or a phase-locked loop having a frequency divider.

[0104] The synthesizer circuit section (606d) may be configured to synthesize an output frequency for use by the mixer circuit section (606a) of the RF circuit section (606) based on frequency input and divider control input. In some embodiments, the synthesizer circuit section (606d) may be a fractional N / N+1 synthesizer.

[0105] In some embodiments, the frequency input may be provided by a voltage-controlled oscillator (VCO), but this is not mandatory. The divider control input may be provided by either the baseband circuit (604) or the application processor (602) depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on a channel indicated by the application processor (602).

[0106] The synthesizer circuit (606d) of the RF circuit (606) may include a divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on carry-out) to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a set of cascaded and tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may be configured to divide the VCO cycle into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[0107] In some embodiments, the synthesizer circuit (606d) may be configured to generate a carrier frequency as an output frequency, whereas in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and may be used in conjunction with an orthogonal generator and a divider circuit to generate multiple signals at the carrier frequency having multiple different phases relative to each other. In some embodiments, the output frequency may be an LO frequency (fLO). In some embodiments, the RF circuit (606) may include an IQ / polar converter.

[0108] The FEM circuit section (608) may include a receiving signal path configured to operate on RF signals received from one or more antennas (610), amplify the received signals, and provide amplified versions of the received signals to the RF circuit section (606) for further processing. The FEM circuit section (608) may also include a transmitting signal path configured to amplify signals for transmission provided by the RF circuit section (606) for transmission by one or more of the one or more antennas (610). In various embodiments, amplification through the transmitting or receiving signal paths may be performed only in the RF circuit section (606), only in the FEM (608), or in both the RF circuit section (606) and the FEM (608).

[0109] In some embodiments, the FEM circuit section (608) may include a TX / RX switch for switching between transmit mode and receive mode operation. The FEM circuit section may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit section may include an LNA for amplifying received RF signals and providing the amplified received RF signals as output (e.g., to the RF circuit section (606)). The transmit signal path of the FEM circuit section (608) may include a power amplifier (PA) for amplifying input RF signals (e.g., provided by the RF circuit section (606)), and one or more filters for generating RF signals for subsequent transmission (e.g., by one or more of the antennas (610)).

[0110] In some embodiments, the PMC (612) can manage the power supplied to the baseband circuit (604). In particular, the PMC (612) can control power selection, voltage scaling, battery charging, or DC-DC conversion. The PMC (612) may often be included when the device (600) can be powered by a battery, for example, when the device is included in a UE. The PMC (612) can increase power conversion efficiency while providing desirable implementation sizes and heat dissipation characteristics.

[0111] FIG. 6 illustrates that the PMC (612) is coupled only to the baseband circuit (604), but in other embodiments, the PMC (612) may additionally or alternatively be coupled to other components such as, but not limited to, the application circuit (602), the RF circuit (606), or the FEM circuit (608) and perform similar power management operations for them.

[0112] In some embodiments, the PMC (612) may control various power saving mechanisms of the device (600) or otherwise be part of them. For example, if the device (600) is in a radio resource control_connected (RRC_Connected) state, which is still connected to a RAN node in anticipation of receiving traffic soon, it may enter a state known as discontinuous reception mode (DRX) after a period of inactivity. During this state, the device (600) may be powered down for short time intervals and thus save power.

[0113] If there is no data traffic activity during an extended period, the device (600) may transition to an RRC_Idle state, in which the device is disconnected from the network and does not perform operations such as channel quality feedback, handover, etc. The device (600) enters an ultra-low power state, and the device performs paging, in which it periodically wakes up to listen to the network again and then at least parts of the device are powered off again. The device (600) may not receive data in this state. To receive data, it will transition back to an RRC_Connected state.

[0114] Additional power saving modes may cause the device to be unavailable to the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this time, the device may be entirely unreachable from the network and completely powered off. Any data transmitted during this time will cause significant delay, and it is assumed that the delay is acceptable.

[0115] The processors of the application circuit (602) and the processors of the baseband circuit (604) may be used to execute elements of one or more instances of the protocol stack. For example, the processors of the baseband circuit (604) may be used, either alone or in combination, to define clusters of PFs, POs, and PEIs during paging cycles. Accordingly, the baseband circuit (604) may be used to encode messages for transmission between the UE and the gNB, or to decode messages received between the UE and the gNB. For example, the baseband circuit (604) may be used to encode paging configurations that define clusters of PFs, POs, and PEIs in the gNB. These examples are not intended to be limited. The baseband circuit may be used as previously described.

[0116] Fig. 7: Block diagram of the interface of the baseband circuit section

[0117] FIG. 7 illustrates exemplary interfaces of a baseband circuit according to some embodiments. It should be noted that the baseband circuit of FIG. 7 is merely one example of a possible circuit, and that the features of the present disclosure can be implemented in any of various systems as desired.

[0118] As discussed above, the baseband circuit (604) of FIG. 6 may include processors (604A to 604E) and a memory (604G) utilized by said processors. Each of the processors (604A to 604E) may each include a memory interface (704A to 704E) to transmit / receive data to / from the memory (604G).

[0119] The baseband circuit section (604) may further include one or more interfaces for communicatingly coupled to other circuit sections / devices, such as a memory interface (712) (e.g., an interface for transmitting / receiving data to / from a memory outside the baseband circuit section (604)), an application circuit section interface (714) (e.g., an interface for transmitting / receiving data to / from the application circuit section (602) of FIG. 6), an RF circuit section interface (716) (e.g., an interface for transmitting / receiving data to / from the RF circuit section (606) of FIG. 6), a wireless hardware connection interface (718) (e.g., an interface for transmitting / receiving data to / from NFC (Near Field Communication) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface (720) (e.g., an interface for transmitting / receiving power or control signals to / from the PMC (612)). there is.

[0120] Fig. 8: Control Plane Protocol Stack

[0121] FIG. 8 is an example of a control plane protocol stack according to some embodiments. In these embodiments, the control plane (800) is illustrated as a communication protocol stack between a UE (106a) (or alternatively, a UE (106b)), a RAN node (102A) (or alternatively, a RAN node (102B)), and a mobility management entity (MME) (621).

[0122] The PHY layer (801) can transmit or receive information used by the MAC layer (802) through one or more air interfaces. The PHY layer (801) can additionally perform link adaptation or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers such as the RRC layer (805). The PHY layer (801) can also additionally perform error detection for transmission channels, forward error correction (FEC) coding / decoding of transmission channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping of physical channels, and multiple input multiple output (MIMO) antenna processing.

[0123] The MAC layer (802) can perform mapping between logical channels and transmission channels, multiplexing MAC service data units (SDUs) from one or more logical channels onto transmission blocks (TBs) to be transmitted to the PHY through transmission channels, demultiplexing MAC SDUs onto one or more logical channels from transmission blocks (TBs) to be transmitted from the PHY through transmission channels, multiplexing MAC SDUs onto TBs, scheduling information reporting, error correction via a hybrid automatic repeat request (HARQ), and logical channel prioritization.

[0124] The RLC layer (803) may operate in a plurality of operating modes, including Transparent Mode (TM), Unacknowledged Mode (UM), and / or Acknowledged Mode (AM). The RLC layer (803) may perform error correction via Automatic Repetition Request (ARQ) for upper layer protocol data units (PDUs) and AM data transmissions, and perform concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transmissions. The RLC layer (803) may also perform re-segmentation of RLC data PDUs for AM data transmissions, reorder RLC data PDUs for UM and AM data transmissions, detect duplicate data for UM and AM data transmissions, discard RLC SDUs for UM and AM data transmissions, detect protocol errors for AM data transmissions, and perform RLC re-establishment.

[0125] The PDCP layer (804) can perform header compression and decompression of IP data, maintain PDCP sequence numbers (SN), perform sequential delivery of upper layer PDUs in lower layer re-establishment, remove duplicates of lower layer SDUs in lower layer re-establishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discarding of data, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0126] The main services and functions of the RRC layer (805) may include broadcasting of system information (e.g., included in Master Information Blocks (MIBs) or System Information Blocks (SIBs) associated with the non-access stratum (NAS)), broadcasting of system information associated with the access stratum (AS), paging, establishment, maintenance, and release of RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), security functions including establishment, configuration, maintenance, and release of point-to-point radio bearers, key management, mobility between radio access technologies (RATs), and measurement configuration for UE measurement reporting. The MIBs and SIBs may include one or more information elements (IEs), each of which may include individual data fields or data structures.

[0127] The UE (601) and RAN node (102A) can utilize a Uu interface (e.g., LTE interface) to exchange control plane data through a protocol stack including a PHY layer (801), a MAC layer (802), an RLC layer (803), a PDCP layer (804) and an RRC layer (805).

[0128] Non-access layer (NAS) protocols (806) form the highest layer of the control plane between the UE (601) and the MME (621). The NAS protocols (806) support the mobility of the UE (601) and session management procedures for establishing and maintaining an IP connection between the UE (601) and the P-GW (623).

[0129] The S1 Application Protocol (S1-AP) layer (815) supports the functions of the S1 interface and may include Elementary Procedures (EPs). An EP is a unit of interaction between a RAN node (102A) and a network (100). S1-AP layer services may include two groups: UE-associated services and non-UE-associated services. These services perform functions including, but not limited to, E-UTRAN Radio Access Bearer (E-RAB) management, UE capability indication, mobility, NAS signaling transmission, RAN Information Management (RIM), and configuration transmission.

[0130] The Stream Control Transmission Protocol (SCTP) layer (alternatively referred to as the SCTP / IP layer) (814) can ensure reliable delivery of signaling messages between the RAN node (102A) and the MME (621) based in part on the IP protocol supported by the IP layer (813). The L2 layer (812) and L1 layer (811) may refer to communication links (e.g., wired or wireless) used by the RAN node and the MME to exchange information.

[0131] The RAN node (102A) and MME (621) can utilize the S1-MME interface to exchange control plane data through a protocol stack including an L1 layer (811), an L2 layer (812), an IP layer (813), an SCTP layer (814), and an S1-AP layer (815).

[0132] Fig. 9: User Plane Protocol Stack

[0133] FIG. 9 is an example of a user plane protocol stack according to some embodiments. In these embodiments, the control plane (900) is illustrated as a communication protocol stack between a UE (106A) (or alternatively, a UE (106B or 106N)), a RAN node (102A) (or alternatively, a RAN node (102B)), an S-GW (622), and a P-GW (623). The user plane (900) may utilize at least some of the same protocol layers as the control plane (800). For example, the UE (601) and the RAN node (102A) may utilize a Uu interface (e.g., an LTE-Uu interface) to exchange user plane data through a protocol stack including a PHY layer (801), a MAC layer (802), an RLC layer (803), and a PDCP layer (804).

[0134] The GTP-U (GPRS (General Packet Radio Service) Tunneling Protocol for the user plane) layer (904) can be used to transmit user data within the GPRS core network and between the radio access network and the core network. The user data transmitted can be packets of any of the formats, for example, IPv4, IPv6, or PPP. The UDP / IP (UDP and IP security) layer (903) can provide checksums for data integrity, port numbers for addressing different functions at the source and destination, and encryption and authentication for selected data streams. The RAN node (102A) and the S-GW (622) can utilize the S1-U interface to exchange user plane data through a protocol stack including the L1 layer (811), L2 layer (812), UDP / IP layer (903), and GTP-U layer (904). The S-GW (622) and P-GW (623) can utilize the S5 / S8a interface to exchange user plane data through a protocol stack including the L1 layer (811), L2 layer (812), UDP / IP layer (903), and GTP-U layer (904). As previously discussed with respect to FIG. 8, NAS protocols support the mobility of the UE (106) and session management procedures to establish and maintain an IP (813) connection between the UE (106) and the P-GW (623).

[0135] For the remainder of the disclosure, references to base station (gNB) and user equipment (UE) are assumed to refer to base station (gNB) (102) and user equipment (UE) (106), respectively, even if specific reference numbers may be omitted.

[0136] Fig. 10: Legacy Beam Management and Reporting (TCI and CSI)

[0137] Beam management is one of the key enabling technologies employed in 5G New Radio (NR) systems. NR beam management includes the following important components: beam presentation, beam measurement and reporting, and beam failure recovery.

[0138] In terms of beam indication, NR can utilize indicators transmitted by the base station to the UE, including Transmit Configuration Indicators (TCIs). A TCI is an indicator used to convey specific transmit configuration parameters from the base station to the UE. A TCI may include parameters such as Quasi-Collocation (QCL) reference resources and power control-related information. The TCI enables the UE to properly decode the transmitted signal by configuring its receiver parameters accordingly. TCIs are often included in control signaling messages exchanged between the base station and user equipment. TCIs are critical for efficient resource allocation, dynamic scheduling, and ensuring compatibility between different devices and network configurations.

[0139] The latest 3GPP releases support the unified TCI (uTCI) framework. Under uTCI, a single set of TCI states is used to indicate beams for multiple channels / signals for both DL and UL in one of two modes. The first mode is "joint TCI," meaning that a single joint TCI can be applied to both UL and DL channels / signals. The second mode is "separated TCI," meaning that a DL TCI is used for DL ​​beam indication and a UL TCI is used for UL beam indication. Table (1600) in FIG. 16 shows uTCI configurations under Scheme 1, Scheme 1 or 2, or Scheme 2.

[0140] Additionally, uTCI supports two schemes of TCI status indication. Scheme 1, common TCI indication for multiple channels / signals: (1) common TCI is always applied to dedicated PDCCH / PDSCH / PUCCH / PUSCH, (2) common TCI may be optionally applied to non-periodic CSI-RS for BM / CSI and SRS for CB / NCB / AS / BM, and (3) whether common TCI is applied to channels / signals is configured by RRC. Scheme 2, dedicated TCI indication for a single channel / RS: (1) this scheme is applied to signals to which common TCI indication (Scheme 1) is not applied, and (2) 3GPP Release 16 signaling is reused to provide TCI indication for such channels / signals. Table (1600) in FIG. 16 illustrates these relationships.

[0141] For the 3GPP Release 17 uTCI framework, for "Joint TCI" mode, up to 128 TCI-States configured in the dl-OrJointTCI-StateList-r17 information element (IE) of PDSCH-Config. For "Detached TCI" mode, for DL ​​uTCI: up to 128 TCI-States configured in the dl-OrJointTCI-StateList-r17 IE of PDSCH-Config, and for UL uTCI: up to 64 TCI-UL-State-r17s configured in the ul-TCI-StateList-r17 IE of BWP-UplinkDedicated.

[0142] Channel State Information (CSI) plays a crucial role in beam management and reporting. The base station can configure the UE to report CSI, including when and how to report CSI, and which CSI parameters the UE measures and reports back to the base station. CSI provides the base station with feedback regarding the characteristics of the beam between the UE and the base station. To assist the UE in calculating CSI parameters, the base station can provide a Channel State Information Reference Signal (CSI-RS). Various configuration options allow the CSI-RS to be transmitted over multiple ports with various scheduling options, such as periodic, semi-permanent, and non-periodic. Using the CSI-RS, the UE determines CSI parameters, which may include the Channel Quality Indicator (CQI), Precoding Matrix Indicator (PMI), and Rank Indicator (RI). The UE transmits these CSI parameters to the base station in the CSI report. The base station utilizes the CSI report to optimize communication with the UE. For example, by using CSI, a base station can adapt its transmission parameters to maximize the quality of the received signal, which leads to improved data rates, reliability, and spectrum efficiency.

[0143] Referring to FIG. 10, a diagram (1000) outlining the CSI reporting framework under a legacy 3GPP release is shown. The base station first configures the UE with a CSI-ReportConfig message. The UE measures CSI parameters such as CQI, PMI, and RI using the Channel State Information Reference Signal (CSI-RS) (alternatively, the UE may use other reference signals, such as demodulation reference signals (DMRS) within the SSB (synchronization signal (SS) physical broadcast channel (PBCH) block), as reference signals for specific measurements). The UE may transmit a CSI-Report message containing the parameters in the CSI reporting occlusion to the base station. Upon receiving the CSI parameters, the base station may schedule downlink data transmissions accordingly using the measurements in the CSI-Report (e.g., modulation scheme, code rate, number of transmission layers, and MIMO precoding).

[0144] Another mechanism under legacy 3GPP is CSI resource counting. As described above, for UEs to perform beam measurements, the base station may transmit reference signals to the UEs. For example, a UE may be configured to receive and report periodic CSI-RS. However, the UE may have a limited number of resources for processing CSI. These processing resources of the UE may be referred to as CSI processing units (CPUs). Conventional scheduling techniques may allow the UE to "count" CPU occupancy to prevent the base station from overconfiguring the UE for CSI. For example, the number of occupied CPUs may be the accumulated (or aggregated) number of CPUs occupied for configured CSI operations. The UE may perform multiple CSI operations based on a determined number of CPUs. For example, the base station may configure the UE to perform that number of CSI operations and may suppress the configuration of additional CSI operations if additional CSI operations require more CPUs than are available to the UE. In other words, the number of CSI operations configured for the UE by the base station can use up to the total number of CPUs in the UE's CPU pool.

[0145] One drawback of the current CSI reporting framework is that the network, for example, the base station, configures the UE to repeatedly report CSIs at defined CSI reporting locations. Due to this configuration, the UE is configured to report as directed by the base station, even if reporting is not required. This is disadvantageous due to the overhead at both the base station and the UE for generating and processing CSI reports. Additionally, the information communicated in the CSI-Report increases the amount of overhead and reduces the amount of data that can be communicated between the UE and the BS. Under the current CSI framework, the UE has no choice but to generate a CSI report for each CSI reporting location as configured by the base station. Another drawback of the current CSI reporting framework is that if the CSI reporting locations configured by the base station are insufficient, the UE may fail to report changes in beam quality in a timely manner. This can lead to increased beam failures and latency issues in data communication between the UE and the BS.

[0146] Therefore, there will be improvements in the technical field regarding a new CSI reporting framework that enable the UE to select to provide beam reporting to each CSI reporting occupancy configured by the base station. That is, there will be improvements to provide a new channel state reporting framework that enables the UE to provide UE-initiated / event-driven beam management information to the base station.

[0147] FIGS. 11 to 17: Novel beam reporting configurations and procedures

[0148] In some embodiments, various approaches to adapt beam measurement and reporting to reduce overhead and latency may be considered. In one embodiment, the present disclosure provides a user equipment initiated / event-driven beam report (UIBR) that is encoded and transmitted from the UE to the base station. The UIBR may display beam parameters of a reference signal as measured by the UE. For example, the UIBR may display one or more parameters of the reference signal, such as Reference Signal Received Power (RSRP) or Signal-to-Interference-plus-Noise Ratio (SINR). In one embodiment, the UIBR may report parameters for multiple beams. In some embodiments, the UE may dynamically select to provide the UIBR based on one or more events or conditions monitored by the UE. That is, the UIBR may be initiated by the UE independently of the base station based on events or conditions monitored by the UE.

[0149] Now, referring to FIG. 11, in one embodiment of the present disclosure, FIG. (1100) illustrates that a base station (gNB) can encode channel state configuration information (CSCI) and transmit it to a UE. In one embodiment, the CSCI of the present disclosure may be identical to or different from the CSI configurations (CSI-ReportConfig) specified in legacy specifications, for example, 3GPP Release 18. However, it will be understood that in some embodiments, the CSCI of the present disclosure may differ from the legacy CSI configurations to accommodate the features described herein.

[0150] CSCI can display a schedule of channel state (CS) reporting locations to the UE. In one embodiment, the CS reporting locations configured by the base station may be periodic, semi-permanent, or non-periodic. In one embodiment, the CS reporting locations may be configured identically to channel state information (CSI) reporting locations (reportConfigType - periodic, semi-permanent, non-periodic) configured under legacy specifications, e.g., 3GPP Release 18. For clarity, in one embodiment, the CS reporting locations according to the present disclosure may be configured identically to or differently from legacy CSI reporting locations.

[0151] The CSCI of the present disclosure may additionally display parameters to be measured in the UE. These parameters may be identical to or different from the parameters (reportQuantity) configured by the legacy CSI configuration. These parameters may include one or more of RSRP or SINR.

[0152] In one embodiment, the CSCI may additionally explicitly indicate a channel measurement resource (CMR) that identifies a resource (e.g., a reference signal (RS)) for which the UE will measure parameters. That is, the CMR refers to specific physical resources allocated to measure channel state information. In one embodiment, the CSCI may indicate one or more of the following as a CMR: a list of uTCI states, a list of SSBs, or a channel state information reference signal (CSI-RS).

[0153] When the CMR is configured as a list of uTCI states, for the “Joint TCI” mode, the list of uTCI states is selected from a list provided by the base station (e.g., dl-OrJointTCI-StateList-r17 IE of PDSCH-Config IE). For the “Separate TCI” mode, the list may be selected from (1) only DL uTCI (e.g., dl-OrJointTCI-StateList-r17 IE of PDSCH-Config IE), (2) DL uTCI or UL uTCI (i.e., ul-TCI-StateList-r17 IE of BWP-UplinkDedicated IE) (but not a mix of DL uTCI and UL integrated TCI), or (3) a mix of DL uTCI and UL uTCI. In one embodiment, the list of uTCI states may be selected from (1) uTCI states where only the medium access control (MAC) control element (CE) (MAC-CE) is enabled, or (2) uTCI states where all radio resource control (RRC) is configured.

[0154] When a CMR is configured as a list of SSBs, the SSBs may be configured with a Physical Cell Identity (PCI) distinct from the serving cell.

[0155] In one embodiment, the CSCI may not explicitly indicate the CMR to the UE. In this case, the CMR is implicitly configured by the UE as one or more of the following: (1) all MAC-CE enabled uTCI states, or (2) all RRC configured uTCI states. For "Joint TCI" mode, the list of uTCI states may be selected from a list provided by the base station (e.g., dl-OrJointTCI-StateList-r17 IE of PDSCH-Config IE). For "separated TCI mode", the list may be selected from (1) only DL uTCI (e.g., dl-OrJointTCI-StateList-r17 IE of PDSCH-Config IE), (2) DL uTCI or UL uTCI (i.e., ul-TCI-StateList-r17 IE of BWP-UplinkDedicated IE) (but not a mix of DL uTCI and UL integrated TCI), or (3) a mix of DL uTCI and UL uTCI.

[0156] In one embodiment, when the uTCI state is used as the CMR and two quasi-coordinated (QCL) sources (QCL-Info) are configured by the TCI-State as shown in the ASN.1 code (1700) illustrated in FIG. 17, two options are available. Under Option 1, only the QCL source (QCL-Info) with qcl-Type "typeD" is used for beam measurement. Under Option 2, both QCL sources are used for beam measurement.

[0157] In one embodiment, the CSCI may additionally explicitly indicate events / conditions monitored by the UE and events or conditions that can trigger the encoding and transmission of the UIBR by the UE. In one embodiment, the UE-monitored events / conditions may determine whether a different uTCI state has a measured quality greater than that of an active TCI state. In one embodiment, the measured quality may need to be greater than a quality threshold. In one embodiment, the UE-monitored events / conditions may determine whether the quality of an active TCI state is below a quality threshold. For both of the aforementioned embodiments, each UE-monitored event / condition may be measured at multiple occupations, that is, the event / condition may need to be satisfied multiple times in succession to trigger the UIBR. In one embodiment, any quality thresholds may be configured by the CSCI or another IE, or pre-configured (hardcoded) in the UE. In one embodiment, quality measurements may consider one or both of the following: Reference Signal Received Power (RSRP) or Signal-to-Interference Plus-Noise Ratio (SINR).

[0158] In one embodiment, the CSCI may additionally explicitly indicate to the UE that group-based beam reporting is allowed. In one embodiment, a pair of beams, i.e., a uTCI status, may be reported in the UIBR. In one embodiment, a pair of beams reported by the UE may be used for simultaneous reception and simultaneous transmission. In one embodiment, the UE may report two pairs of beams, one pair of beams may be used only for simultaneous reception, and the other pair of beams may be used only for simultaneous transmission. In one embodiment, a pair of beams reported by the UE may be used only for simultaneous reception. In one embodiment, a pair of beams reported by the UE may be used only for simultaneous transmission. Alternatively, a single pair of beams may be used, where one beam is used to transmit signals from the UE and the other beam is used to receive signals from the UE.

[0159] In one embodiment, only a single beam or a single pair of beams may be reported in the UIBR. In one embodiment, maximum , for example, A number of beams or pairs of beams may be reported.

[0160] In one embodiment, the CSCI may additionally explicitly indicate to the UE that the CapabilityIndex IE can be reported together in the UIBR with each reported beam. In one embodiment, the CSCI may additionally explicitly indicate to the UE that the CapabilityIndex IE cannot be reported together in the UIBR with each reported beam. In one embodiment, the CapabilityIndex IE indicates the maximum number of SRS ports.

[0161] In one embodiment, the CSCI may additionally explicitly indicate to the UE that beam quality can be reported together with each reported beam. In one embodiment, the CSCI may additionally explicitly indicate to the UE that beam quality cannot be reported together with each reported beam. In one embodiment, beam quality may be used to configure the UE to measure one or both of the following: RSRP or SINR.

[0162] In one embodiment, to eliminate the need for the base station to configure the UE in some or all instances, the UE may be pre-configured (hardcoded) with any of the CSCIs identified above. It will be understood that pre-configuring the UE with a CSCI saves overhead resources and improves latency.

[0163] As illustrated in FIG. 11, once configured by the base station, the UE can independently monitor and detect beam quality-related events and conditions that may need to be reported to the base station. In response to detecting an event / condition, the UE can encode a UE-initiated / event-driven beam report (UIBR) in one of the upcoming CS reporting occupations and transmit it to the base station. In one embodiment, the UIBR may be carried by a Physical Uplink Control Channel (PUCCH) and communicated using Radio Resource Control (RRC) signaling. In one embodiment, the UIBR may also be carried by a Physical Uplink Shared Channel (PUSCH) and enabled / disabled by a Media Access Control-Control Element (MAC-CE). In one embodiment, the UIBR may be carried by a Physical Uplink Shared Channel (PUSCH) and triggered by Downlink Control Information (DCI).

[0164] Referring to FIG. 11 and FIG. 12, a diagram (1200) is shown illustrating a plurality of CS reporting locations that enable a UE to communicate a UIBR to a base station. The base station may configure a plurality of CS reporting locations in which a CSCI is encoded and transmitted to the UE. In one embodiment, the CS reporting locations are one of periodic, semi-permanent, or non-periodic. In one embodiment, the CS reporting locations are one of PUSCH or PUCCH locations. In one embodiment, the UE may choose to provide or not provide a UIBR at each CSI reporting location based on the determination of a UE event / condition. For example, when the UE detects an event or condition that may affect beam management, the UE may encode a UIBR and transmit it to the base station at the next available CS reporting location.

[0165] As described above, in one embodiment, the CSCI may indicate an event / condition monitored by the UE that can trigger the encoding and transmission of the UIBR. In one embodiment, the UE-monitored event / condition may determine whether a different uTCI state has a measured quality greater than that of an active TCI state. In one embodiment, the measured quality may need to be greater than a quality threshold. In one embodiment, the UE-monitored event / condition may determine whether the quality of an active TCI state is below a quality threshold. For both of the aforementioned embodiments, each UE-monitored event / condition may be measured at multiple occupations, that is, the event / condition may need to be satisfied multiple times in succession to trigger the UIBR. In one embodiment, any quality thresholds may be configured by the CSCI or pre-configured (hardcoded) in the UE. In one embodiment, quality measurements may consider one or both of the following: Reference Signal Received Power (RSRP) or Signal to Interference Plus Noise Ratio (SINR). In one embodiment, the event / condition monitored by the UE may be implicitly indicated or pre-configured in the UE.

[0166] Now, referring to FIG. 13, an exemplary block diagram (1300) of a channel status report (CSR) according to one embodiment of the present disclosure is shown. In one embodiment, the CSR may include Part 1 and Part 2. Part 1 indicates whether Part 2 includes a UIBR. For example, Part 1 may include a minimum number of bits to indicate whether the UIBR is included in or excluded from Part 2. In one embodiment, "0" in Part 1 indicates that the UIBR is excluded from Part 2, while "1" indicates that the UIBR is returned from Part 2. Of course, other indicators may be used to indicate the inclusion or exclusion of the UIBR.

[0167] With reference to FIG. 13, and now with reference to FIGS. 14 and 15, Figure (1400) illustrates that once configured by a base station using CSCI, a UE can independently monitor and detect events and conditions related to CMR. In response to detecting an event / condition, the UE can encode a UE-initiated / event-driven beam report (UIBR) as part of a CSR (e.g., within Part 2) in one of the upcoming CS reporting locations and transmit it to the base station, as illustrated in the exemplary block diagram (1500) of FIG. 15. If no event / condition is detected, the base station still encodes and transmits a CSR, but there is no UIBR.

[0168] New CSI resource counting

[0169] As described above, UEs may have a limited number of resources for processing CSI. These processing resources of the UE may be referred to as CSI processing units (CPUs). UEs and base stations may "count" CPU occupancy to prevent the base station from overconfiguring the UE. The number of occupied CPUs may be the accumulated (or aggregated) number of CPUs occupied for configured CSI operations. In one embodiment, CPUs may be estimated based on specific parameters including algorithm complexity, the number of antennas (CSI-RS resources / ports), modulation scheme, UE processing capabilities, and resource allocation (CPU cycles and memory). In one embodiment, the present disclosure may utilize legacy processes and methods to determine CPUs as known in the art.

[0170] The UE can be configured to perform a limited number of CSI operations based on a determined number of CPUs. For example, the base station may configure the UE to perform that number of CSI operations and may suppress the configuration of additional CSI operations if additional CSI operations require more CPUs than are available. In other words, the number of CSI operations required by the base station may utilize up to the total number of CPUs in the UE's CPU pool.

[0171] According to some embodiments, the UE may not report the UIBR at all scheduled CS reporting occupations as described above. Nevertheless, the CPU is counted by the UE for the UIBR, even if it is not provided to the base station. In other embodiments, the CPU is counted only when the UIBR is provided to the base station by the UE.

[0172] When UIBR is counted, various options including the following are available under the present disclosure: (1) the CPU is counted based on an explicit or implicit CMR configuration within the corresponding CSI-ReportConfig (when two QCL sources (QCL-Info) are configured for an integrated TCI state, see FIG. 17 and the preceding related discussion), (2) the CPU count is reported as a UE capability, or (3) the CPU is counted as a fixed value, e.g., 1.

[0173] In terms of counting active CSI-RS resources / ports, various options including the following are available under the present disclosure: (1) CSI-RS resources / ports are counted regardless of whether the UE reports a beam or not, or (2) CSI-RS resources / ports are counted only when the UE reports a beam.

[0174] In terms of CSI-RS resources / ports, various options including the following are available under the present disclosure: (1) CSI-RS resources / ports are counted based on an explicit or implicit CMR configuration within the corresponding CSI-ReportConfig (when two QCL sources (QCL-Info) are configured for an integrated TCI state, see FIG. 17 and the preceding related discussion), (2) CSI-RS resources / ports are reported as UE capabilities, or (3) CSI-RS resources / ports are counted as a fixed value, e.g., 1.

[0175] With respect to CSI-RS resources / ports, various options including the following are available under this disclosure: (1) the CSI-RS resources / ports are counted only in the slots in which they are transmitted, or (2) the CSI-RS resources / ports are counted even in slots in which they are not transmitted. In the case of non-periodic CSI-RS, the CSI-RS resources / ports are counted starting from the end of the PDCCH containing the request and ending at the end of the scheduled PUSCH containing the report associated with this non-periodic CSI-RS. In the case of semi-permanent CSI-RS, the CSI-RS resources / ports are counted starting from the end when the MAC-CE enable command is applied and ending at the end when the MAC-CE disable command is applied. In the case of periodic CSI-RS, the CSI-RS resources / ports are counted starting when the periodic CSI-RS is configured by the RRC and ending when the periodic CSI-RS configuration is released by the RRC.

[0176] In terms of CSI priority, various options including the following are available under the present disclosure: (1) UE initiating / event-driven beam reports have the same priority as CSI reports that return "L1-RSRP" or "L1-SINR", (2) UE initiating / event-driven beam reports have the same priority as CSI reports that do not return "L1-RSRP" or "L1-SINR", or (3) UE initiating / event-driven beam reports have a higher priority than CSI reports that return "L1-RSRP" or "L1-SINR".

[0177] FIGS. 18 to 20: Flowcharts for UE initiation-type / event-driven beam management

[0178] FIG. 18 illustrates a flowchart (1800) of an example of a method for providing a User Equipment (UE) Initiated Beam Report (UIBR) to a Base Station (BS) in a wireless communication system. In step (1802), the UE decodes configuration information from the BS, and the configuration information indicates a plurality of Channel State Information (CSI) reporting locations. In step (1804), the UE decides to include or exclude a UIBR in each of the plurality of CSI reporting locations. In step (1806), if the UE decides to include a UIBR in one of the plurality of CSI reporting locations, it encodes the UIBR from that CSI reporting location for transmission to the BS.

[0179] FIG. 19 illustrates a flowchart (1900) of an example of a method of wireless communication performed by a base station (BS). In step (1902), the base station encodes configuration information for transmission to a user equipment (UE), and the configuration information indicates a plurality of channel state information (CSI) reporting locations. In step (1904), the base station monitors each of the CSI reporting locations for a UE initiated / event driven beam (UIBR) from the UE. In step (1906), the base station decodes the UIBR transmitted by the UE from one of the CSI reporting locations.

[0180] FIG. 20 illustrates a flowchart (2000) of an example of a method of wireless communication performed by a user equipment (UE). In step (2002), the UE decodes configuration information transmitted by a base station (BS). In step (2004), the UE determines a set of occupied channel state information (CSI) processing units (CPUs) based on the configuration information. In step (2006), the UE counts CPUs for the UIBR, regardless of whether or not it transmits a UE-initiated / event-driven beam report (UIBR) to the BS.

[0181] Examples of systems, devices, and methods

[0182] The following embodiments relate to specific technical embodiments and indicate specific features, elements, or actions that may be used or otherwise combined to achieve such embodiments.

[0183] Embodiment 1 relates to a method for providing a User Equipment (UE) Initiated Beam Report (UIBR) to a base station (BS) in a wireless communication system, the method comprising: decoding configuration information from the BS in the UE - the configuration information indicates a plurality of Channel State Information (CSI) reporting locations -; determining in the UE to include or exclude a UIBR in each of the plurality of CSI reporting locations; and if the UE determines to include a UIBR in one of the plurality of CSI reporting locations, encoding the UIBR in the UE for transmission to the BS from that CSI reporting location.

[0184] Example 2 comprises the method of Example 1, wherein the step of encoding the UIBR further comprises, in the UE, encoding a Channel State (CS) report for transmission to the BS from each of a plurality of CSI reporting occupations, wherein the CS report has a first part and a second part, the first part indicates whether the second part includes the UIBR, and the second part optionally includes the UIBR. Example 3 comprises the methods of Example 1 or Example 2, and further comprises the step of generating the UIBR from the UE. Example 4 comprises the methods of Example 1, Example 2, or Example 3, wherein, in the UE, the step of determining whether to include or exclude the UIBR from each of the plurality of CSI reporting occupations further comprises the step of determining whether the quality of the inactive Transmit Configuration Indicator (TCI) state is greater than the quality of the active TCI state for the UE. Example 5 comprises the method of Example 4, wherein the inactive TCI state is an integrated TCI state. Example 6 comprises the method of Example 1, Example 2, or Example 3, wherein, in the UE, the step of determining to include or exclude a UIBR in each of the plurality of CSI reporting occupations further comprises the step of determining whether the quality of the active TCI state for the UE is below a quality threshold. Example 7 comprises the method of Example 4, Example 5, or Example 6, wherein the quality of the active TCI state is determined based on one or both of the Reference Signal Received Power (RSRP) and the Signal-to-Interference Plus-Noise Ratio (SINR). Example 8 comprises the method of any one of Examples 1 to 7, wherein the UIBR reports beam measurements for more than one beam. Example 9 comprises the method of any one of Examples 1 to 8, wherein the plurality of CSI reporting occupations are one of periodic, semi-permanent, or non-periodic.Example 10 comprises the method of any one of Examples 1 through 9, wherein the configuration information additionally explicitly indicates Channel Measurement Resources (CMRs). Example 11 comprises the method of Example 10, wherein the CMR is one or more of a list of Integrated Transmission Configuration Indicator (uTCI) states, a list of SSBs, or a CSI Reference Signal (CSI-RS). Example 12 comprises the method of any one of Examples 1 through 11, wherein the configuration information does not explicitly configure Channel Measurement Resources (CMRs). Example 13 comprises the invention of Example 12, wherein the CMR is implicitly configured in the UE as one or more of all Media Access Control-Control Element (MAC-CE) enabled Integrated Transmission Configuration Indicator (uTCI) states, or all Radio Resource Control (RRC) configured uTCI states. Example 14 comprises the method of any one of Examples 1 through 13, wherein the transmit configuration indicator (uTCI) state is used as a measurement resource, and when two quasi-collective location (QCL) sources (QCL-Info) are configured, only the QCL source (QCL-Info) with QCL-Type "typeD" is used for measurement, or both QCL sources are used for measurement. Example 15 comprises the method of any one of Examples 1 through 14, wherein the UIBR includes single beam reporting or group-based beam reporting. Example 16 comprises the method of Example 15, wherein the group-based beam reporting reports one of a single pair of beams, up to four beams, or two pairs of beams. Example 17 comprises the methods of Example 15 or Example 16, wherein a CapabilityIndex information element (IE) is reported in the UIBR for each reported beam. Example 18 includes the method of any one of Examples 1 to 17, wherein the beam quality is reported for each reported beam in the UIBR.Example 19 includes the method of Example 18, wherein beam quality is based on either or both of the reference signal received power (RSRP) or the signal-to-interference plus noise ratio (SINR).

[0185] Example 20 comprises a method of wireless communication performed by a base station (BS), the method comprising: at the BS, encoding configuration information for transmission to a user equipment (UE) - the configuration information indicates a plurality of channel state information (CSI) reporting locations -; at the BS, monitoring each of the CSI reporting locations for a UE-initiated beam report (UIBR) from the UE; and at the BS, decoding a UIBR transmitted by the UE from one of the CSI reporting locations.

[0186] Example 21 includes the method of Example 20, wherein a plurality of CSI reporting occupations are one of periodic, semi-permanent, or non-periodic. Example 22 includes the method of Example 20, wherein the configuration information explicitly indicates a Channel Measurement Resource (CMR). Example 23 includes the method of Example 22, wherein the CMR is one or more of a Transmit Configuration Indicator (TCI) status, an SSB, or a CSI Reference Signal (CSI-RS). Example 24 includes the method of Example 20, wherein the configuration information does not explicitly indicate Channel Measurement Resources (CMRs). Example 25 includes the method of Example 20, wherein the UIBR includes group-based beam reporting.

[0187] Example 26 includes a method of wireless communication performed by a user device (UE), the method comprising: decoding configuration information transmitted by a base station (BS) in the UE; determining a set of channel state information (CSI) processing units (CPUs) occupied in the UE based on the configuration information; and counting CPUs for UIBR regardless of whether the UE transmits a UE-initiated beam report (UIBR) to the BS.

[0188] Example 27 includes the method of Example 26, wherein the CPU for the beam is counted based on the explicit or implicit Channel Measurement Resource (CMR) configuration within the configuration information. Example 28 includes the method of Example 26, wherein the CSI reference signal resource / port is counted regardless of whether the UE transmits the UIBR to the BS or not. Example 29 includes the method of Example 26, wherein the CSI reference signal resource / port is counted based on the explicit or implicit Channel Measurement Resource (CMR) configuration within the configuration information. Example 30 includes the method of Example 26, wherein the CSI reference signal resource / port is counted only in the slot in which it is transmitted. Example 31 includes the method of Example 26, wherein the UIBR has the same priority as CSI reports returning "L1-RSRP" or "L1-SINR".

[0189] Example 31 includes an apparatus configured to cause a user equipment (UE) to perform any one of the methods of Examples 1 through 19 and Examples 26 through 31. Example 33 includes a baseband processor configured to perform one or more of the methods of Examples 1 through 31. Example 34 includes an apparatus configured to cause a base station (BS) to perform any one of the methods of Examples 20 through 25. Example 35 includes a computer program product comprising computer instructions that perform any one of the operations or methods described herein when executed by one or more processors.

[0190] Embodiments of the present disclosure may be realized in any of various forms. For example, some embodiments may be realized as a computer implementation method, a computer-readable memory medium, or a computer system. Other embodiments may be realized using one or more custom-designed hardware devices, such as an ASIC. Still other embodiments may be realized using one or more programmable hardware elements, such as FPGAs.

[0191] In some embodiments, a non-transient computer-readable memory medium may be configured to store program instructions and / or data, wherein the program instructions, when executed by a computer system, cause the computer system to perform a method, for example, any of the method embodiments described herein, or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets.

[0192] In some embodiments, 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, the processor is configured to read and execute program instructions from the memory medium, and the program instructions are executable to implement any of the various method embodiments described herein (or any combination of the method embodiments described herein, or any subset of any of the method embodiments described herein, or any combination of such subsets). The device may be realized in any of the various forms.

[0193] Any of the methods described herein for operating a user equipment (UE) may be the basis of a corresponding method for operating a base station by interpreting each message / signal X received by the UE in the downlink as a message / signal X transmitted by the base station and each message / signal Y transmitted by the UE in the uplink as a message / signal Y received by the base station.

[0194] Although the above embodiments have been described in considerable detail, once the above disclosure is sufficiently recognized, many variations and modifications will be apparent to those skilled in the art. The following claims are intended to be interpreted as encompassing all such variations and modifications.

Claims

Claim 1 A method for providing a user equipment (UE)-initiated beam report (UIBR) to a base station (BS) in a wireless communication system, In the UE, a step of decoding configuration information from the BS - said configuration information indicates a plurality of channel state information (CSI) reporting occasions -; In the above UE, a step of determining to include or exclude the UIBR in each of the plurality of CSI reporting locations; and A method comprising the step of, when the UE determines to include the UIBR in one of the plurality of CSI reporting locations, encoding the UIBR in the UE for transmission to the BS from the CSI reporting location. Claim 2 The method of claim 1, wherein the step of encoding the UIBR further comprises, in the UE, the step of encoding a channel state (CS) report for transmission to the BS at each of the plurality of CSI reporting occupations, wherein the CS report has a first part and a second part, the first part indicates whether the second part includes the UIBR, and the second part optionally includes the UIBR. Claim 3 A method according to claim 1 or 2, further comprising the step of generating the UIBR in the UE. Claim 4 In claim 1, 2, or 3, the step of determining to include or exclude the UIBR in each of the plurality of CSI reporting locations in the UE is additionally, A method comprising the step of determining whether the quality of an inactive transmission configuration indicator (TCI) state is greater than the quality of an active TCI state for the UE. Claim 5 A method according to paragraph 4, wherein the inactive TCI state is a unified transmission configuration indicator (uTCI) state. Claim 6 In claim 1, 2, or 3, the step of determining to include or exclude the UIBR in each of the plurality of CSI reporting locations in the UE is additionally, A method comprising the step of determining whether the quality of the active TCI state for the UE is below a quality threshold. Claim 7 A method according to claim 4, 5, or 6, wherein the quality of the active TCI state is determined based on one or both of the reference signal received power (RSRP) and the signal-to-interference-plus-noise ratio (SINR). Claim 8 A method according to any one of claims 1 to 7, wherein the UIBR reports beam measurements for more than one beam. Claim 9 A method according to any one of claims 1 to 8, wherein the plurality of CSI reporting occupations are one of periodic, semi-permanent, or non-periodic. Claim 10 A method according to any one of claims 1 to 9, wherein the configuration information additionally explicitly indicates channel measurement resources (CMRs). Claim 11 In paragraph 10, the method wherein the CMR is one or more of a list of integrated transmission configuration indicator (uTCI) states, a list of SSBs (synchronization signal (SS) physical broadcast channel (PBCH) blocks), or a CSI reference signal (CSI-RS). Claim 12 A method according to any one of claims 1 to 11, wherein the configuration information does not explicitly configure channel measurement resources (CMRs). Claim 13 In paragraph 12, the method wherein the CMR is implicitly configured as one or more of all medium access control-control element (MAC-CE) enabled integrated transmit configuration indicator (uTCI) states in the UE, or all radio resource control (RRC) configured uTCI states. Claim 14 A method according to any one of claims 1 through 13, wherein a transmitting configuration indicator (uTCI) state is used as a measurement resource, and when two quasi-co-location (QCL) sources (QCL-Info) are configured, only the QCL source (QCL-Info) whose QCL-Type is "typeD" is used for measurement, or both of the said QCL sources are used for measurement. Claim 15 A method according to any one of claims 1 to 14, wherein the UIBR comprises a single beam report or a group-based beam report. Claim 16 In paragraph 15, the group-based beam reporting method reports one of a single pair of beams, up to four beams, or two pairs of beams. Claim 17 A method according to claim 15 or 16, wherein a CapabilityIndex information element (IE) is reported for each reported beam in the UIBR. Claim 18 A method according to any one of claims 1 to 17, wherein the beam quality is reported for each reported beam in the UIBR. Claim 19 In paragraph 18, the beam quality is based on either or both of the reference signal received power (RSRP) or the signal-to-interference plus noise ratio (SINR). Claim 20 As a method of wireless communication performed by a base station (BS), In the above BS, a step of encoding configuration information for transmission to a user device (UE) - said configuration information indicates a plurality of channel state information (CSI) reporting occupations -; In the above BS, the step of monitoring each of the CSI reporting occupations for a UE-initiated beam report (UIBR) from the UE; and A method comprising the step of decoding the UIBR transmitted by the UE in one of the CSI reporting locations in the above BS. Claim 21 In paragraph 20, the above-mentioned plurality of CSI reporting occupations are one of periodic, semi-permanent, or non-periodic. Claim 22 A method according to paragraph 20, wherein the above configuration information explicitly indicates a channel measurement resource (CMR). Claim 23 In paragraph 22, the method wherein the CMR is one or more of a Transmit Configuration Indicator (TCI) state, an SSB, or a CSI Reference Signal (CSI-RS). Claim 24 In paragraph 20, the above configuration information does not explicitly indicate channel measurement resources (CMRs). Claim 25 In paragraph 20, the above UIBR is a method comprising group-based beam reporting. Claim 26 As a method of wireless communication performed by user equipment (UE), In the above UE, a step of decoding configuration information transmitted by a base station (BS); In the above UE, a step of determining a set of channel state information (CSI) processing units (CSI processing unit, CPU) occupied based on the configuration information; and A method comprising the step of counting the CPU to process the UIBR, regardless of whether the UE transmits the UE-initiated beam report (UIBR) to the BS. Claim 27 In paragraph 26, the CPU for the beam is counted based on the explicit or implicit channel measurement resource (CMR) configuration within the configuration information. Claim 28 In paragraph 26, a method in which CSI reference signal resources / ports are counted. Claim 29 A method according to claim 26, wherein a CSI reference signal resource / port is counted based on an explicit or implicit channel measurement resource (CMR) configuration within the configuration information. Claim 30 In paragraph 26, a method in which the CSI reference signal resource / port is counted only in the slot where it is transmitted. Claim 31 In paragraph 26, the above UIBR has the same priority as CSI reports that return "L1-RSRP" or "L1-SINR". Claim 32 An apparatus configured to enable a user device (UE) to perform any one of the methods of claims 1 through 19 and claims 26 through 31. Claim 33 A baseband processor configured to perform one or more of the methods of claims 1 through 31. Claim 34 A device configured to enable a base station (BS) to perform any one of the methods of paragraphs 20 through 25. Claim 35 A computer program product comprising computer instructions that perform any one of the operations or methods described in this specification when executed by one or more processors.

Images