Enhanced trigger conditions for Rx beam pair change indication

Abstract

A user equipment (UE) configured to decode configuration information related to simultaneous reception of signals from a plurality of transmit and receive points (TRPs) from signaling received from a base station, in which a signal from a first TRP is received using a first Rx beam in a receive (Rx) beam pair, and receiving a signal from a second TRP using a second Rx beam in the Rx beam pair; determining that an event associated with the Rx beam pair has occurred; and configuring the transceiver circuitry to transmit an indication of the event to the base station, wherein the indication includes (i) an indication that a transmit (Tx) beam pair is invalid, (ii) an indication that an Rx beam pair is invalid, or (iii) an indication that one or more resource set group-based beam reports (GBBRs) are to be configured for the UE.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of wireless technology, and in particular to enhanced triggering conditions for Rx beam pair change indication. BACKGROUND

[0002] The use of wireless communication systems is rapidly increasing. In recent years, wireless devices such as smart phones and tablet computers have become increasingly sophisticated. In addition to supporting telephone calls, many mobile devices (i.e., user equipment devices or UEs) now provide access to the Internet, email, text messaging, and navigation using the global positioning system (GPS), and can operate sophisticated applications that utilize these functionalities. The current telecommunication standard beyond previous standards is referred to as 5th Generation Mobile Networks or 5th Generation Wireless Systems, referred to as 3GPP NR (otherwise referred to as 5G-NR or NR-5G for 5G New Radio, also simply referred to as NR). NR provides higher capacity for higher density of mobile broadband users, while supporting device-to-device, ultra-reliable, and massive machine communications, as well as lower latency and lower battery consumption than the LTE standard.

[0003] In some cases, multiple receive (multi-Rx) chain downlink (DL) reception at a UE can be beneficial. In some cases, such multi-Rx chain DL reception mechanisms can be used in frequency range 2 (FR2) (e.g., 24.25 GHz to 52.6 GHz and / or 52.6 GHz to 71 GHz (or higher) frequency bands). In such cases, it can be beneficial to introduce mechanisms for simultaneous DL reception from different directions with different quasi co-location (QCL) type-D reference signals (RS) on a single component carrier (e.g., which can be used with an enhanced FR2-1 UE or other UEs).

[0004] In some instances, it can be beneficial to specify one or more of the following: a layer 1 (L1) reference signal received power (RSRP) (L1-RSRP) measurement delay; a layer 3 (L3) measurement delay (e.g., cell detection delay and / or measurement period), where the starting point can be an enhancement related to L1-RSRP measurement enhancement; radio link monitoring (RLM), bidirectional forward detection (BFD), and / or candidate beam detection (CBD) requirements; scheduling and / or measurement restrictions; transmission configuration indicator (TCI) state switching delay with dual TCI; and / or reception (Rx) timing difference between different directions (e.g., different QCL type-D RS). SUMMARY

[0005] Some example embodiments relate to an apparatus of a user equipment (UE) having processing circuitry configured to: decode, from signaling received from a base station, configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein a first receive (Rx) beam of a pair of Rx beams is used to receive signals from a first TRP and a second Rx beam of the pair of Rx beams is used to receive signals from a second TRP; determine that an event related to the pair of Rx beams has occurred; and configure transceiver circuitry to transmit, to the base station, an indication of the event, wherein the indication comprises: (i) an indication that a pair of transmit (Tx) beams is ineffective, (ii) an indication that the pair of Rx beams is ineffective, or (iii) an indication that one or more resource set group-based beam reports (GBBRs) are to be configured for the UE.

[0006] Other example embodiments relate to a processor configured to: decode, from signaling received from a base station, configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein a first receive (Rx) beam of a pair of Rx beams is used to receive signals from a first TRP and a second Rx beam of the pair of Rx beams is used to receive signals from a second TRP; determine that an event related to the pair of Rx beams has occurred; and configure transceiver circuitry to transmit, to the base station, an indication of the event, wherein the indication comprises: (i) an indication that a pair of transmit (Tx) beams is ineffective, (ii) an indication that the pair of Rx beams is ineffective, or (iii) an indication that one or more resource set group-based beam reports (GBBRs) are to be configured for the UE.

[0007] Still other example embodiments relate to an apparatus of a base station having processing circuitry configured to: configure transceiver circuitry to transmit, to a user equipment (UE), configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein the configuration information includes an identification that a first receive (Rx) beam of a pair of Rx beams is used by the UE to receive signals from a first TRP and a second Rx beam of the pair of Rx beams is used by the UE to receive signals from a second TRP; monitor, from the UE, feedback signals related to the UE receiving the signals from the first TRP using the first Rx beam and receiving the signals from the second TRP using the second Rx beam; and configure transceiver circuitry to transmit, to the UE, updated configuration information.

[0008] Additional example embodiments relate to a processor configured to: configure transceiver circuitry to transmit, to a user equipment (UE), configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein the configuration information includes an identification that a first reception (Rx) beam of a Rx beam pair is used by the UE to receive signals from a first TRP and a second Rx beam of the Rx beam pair is used by the UE to receive signals from a second TRP; monitor, from the UE, feedback signals related to the UE using the first Rx beam to receive the signals from the first TRP and using the second Rx beam to receive signals from the second TRP; and configure transceiver circuitry to transmit, to the UE, updated configuration information. BRIEF DESCRIPTION OF DRAWINGS

[0009] To easily identify discussions of any particular element or act, one or more of the highest three digits in a figure reference number are often dropped and the figure is given a three -digit number. For example, figure 10-15 is a reference to figure 15 in figure 10.

[0010] Figure 1 An example network arrangement is shown in accordance with various example embodiments.

[0011] Figure 2 An example user equipment (UE) is shown in accordance with various example embodiments.

[0012] Figure 3 An example base station is shown in accordance with various example embodiments.

[0013] Figure 4 A diagram showing an example UE in accordance with embodiments herein is illustrated.

[0014] Figure 5 An example situation in which an example UE can perform simultaneous reception from multiple transmission and reception points (TRPs) before rotation of the example UE but not after rotation of the example UE is illustrated in accordance with embodiments herein.

[0015] Figure 6 An example call flow in which a UE is configured for event triggered reporting is shown in accordance with various example embodiments.

[0016] Figure 7 An example call flow in which a UE is configured for sensor based trigger reporting is shown in accordance with various example embodiments.

[0017] Figure 8Exemplary call flows are shown in which a network reconfigures a UE based on feedback or lack of feedback from the UE, in accordance with various example embodiments.

[0018] Figure 9 Exemplary call flows are shown in which a UE is configured to report beam pair failure when there is no beam failure or link failure at the UE for individual beam identifications, in accordance with various example embodiments.

[0019] Figure 10 Exemplary call flows are shown in which a UE 110 is configured for measurement and reporting based on body proximity sensing (BPS), in accordance with various example embodiments. DETAILED DESCRIPTION

[0020] Exemplary embodiments can be further understood with reference to the following description and the related drawings in which like elements are provided with the same reference numbers. The exemplary embodiments relate to initiating beam pair updates or indicating beam pair problems from multiple transmission and reception points (TRPs) that are simultaneously received in relation to a user equipment (UE) movement (e.g., rotation). As used herein, simultaneously received can refer to receiving signals simultaneously or in a substantially simultaneous manner.

[0021] Exemplary embodiments are described with reference to a user equipment (UE). However, references to a UE are provided for illustrative purposes only. Exemplary embodiments can be utilized with any electronic component that can establish a connection to a network and is configured with hardware, software, and / or firmware for exchanging information and data with the network. Thus, a UE as described herein is used to represent any appropriate type of electronic component.

[0022] Exemplary embodiments are also described with reference to a fifth generation (5G) New Radio (NR) network and a next generation NodeB (gNB). However, references to a 5G NR network and a gNB are provided for illustrative purposes only. Exemplary embodiments can be utilized with any appropriate type of network (e.g., 5G advanced, 6g, etc.) and base station.

[0023] When a UE is performing simultaneous reception from multiple transmission and reception points (TRPs), there can be scenarios (e.g., UE rotation) in which the UE can no longer be able to perform simultaneous reception from multiple TRPs. When this occurs, the UE will waste time finding a new beam pair and will also waste throughput until the next beam reporting interval (e.g., a report that allows the network to select a new beam pair) because the network is unaware that the beam pair is no longer valid at the UE.

[0024] Exemplary embodiments describe operations for a user equipment (UE) to perform enhanced triggering of beam pair change information (beam part update) when using simultaneous reception. In exemplary embodiments, the UE initiates a beam pair update as quickly as possible and / or indicates a beam pair problem to the network.

[0025] Figure 1 An exemplary network arrangement 100 is shown in accordance with various exemplary embodiments. The exemplary network arrangement 100 includes a UE 110. Those skilled in the art will appreciate that the UE 110 can be any type of electronic component configured to communicate via a network, such as a mobile phone, a tablet computer, a desktop computer, a smart phone, a phablet, an embedded device, a wearable device, an Internet of Things (IoT) device, etc. It should also be appreciated that a practical network arrangement can include any number of UEs used by any number of users. Thus, the example of a single UE 110 is provided for illustrative purposes only.

[0026] The UE 110 can be configured to communicate with one or more networks. In the example of the network arrangement 100, the network with which the UE 110 can wirelessly communicate is a 5G NR Radio Access Network (RAN) 120. However, the UE 110 can also communicate with other types of networks (e.g., a sixth generation (6G) RAN, a 5G cloud RAN, a next generation RAN (NG-RAN), a Long Term Evolution (LTE) RAN, a legacy cellular network, a wireless local area network (WLAN), etc.), and the UE 110 can also communicate with networks through a wired connection. With reference to exemplary embodiments, the UE 110 can establish a connection with the 5G NR RAN 120. Thus, the UE 110 can have at least a 5G NR chipset to communicate with the 5G NR RAN 120.

[0027] The 5G NR RAN 120 can be part of a cellular network that can be deployed by a network operator (e.g., Verizon, AT&T, T-Mobile, etc.). The 5G NR RAN 120 can include a base station or access node (NodeB, eNodeB, HeNB, eNB, gNB, gNodeB, macrocell, microcell, small cell, femtocell, etc.) configured to transmit and receive traffic from UEs equipped with the appropriate cellular chipset.

[0028] In network arrangement 100, 5G NR RAN 120 deploys a gNB 120A. gNB 120A can be configured with multiple transmission and reception points (TRPs). Throughout the specification, a TRP generally refers to a set of components configured to transmit and / or receive a beam. In some embodiments, multiple TRPs can be deployed locally at gNB 120A. In other embodiments, multiple TRPs can be distributed at different locations and connected to gNB 120A via a backhaul connection. For example, multiple small cells can be deployed at different locations and connected to gNB 120A. However, these examples are provided for illustrative purposes only. Those skilled in the art will appreciate that a TRP is configured to be adaptable to a variety of different conditions and deployment scenarios. Thus, any reference to a TRP as a particular network component or to multiple TRPs deployed in a particular arrangement is for illustrative purposes only. The TRPs described herein can represent any type of network component configured to transmit and / or receive a beam.

[0029] Those skilled in the art will appreciate that any relevant procedures can be performed for UE 110 to connect to 5G NR RAN 120. For example, as discussed above, 5G NR RAN 120 can be associated with a particular cellular provider at which UE 110 and / or its user has agreement and credential information (e.g., stored on a SIM card). Upon detecting the presence of 5G NR RAN 120, UE 110 can transmit corresponding credential information in order to associate with 5G NR RAN 120. More specifically, UE 110 can associate with a particular base station (e.g., gNB 120A).

[0030] Network arrangement 100 also includes a cellular core network 130, the Internet 140, an IP Multimedia Subsystem (IMS) 150, and a network services backbone 160. Cellular core network 130 can refer to an interconnected set of components that manage the operation and traffic of a cellular network. It can include an Evolved Packet Core (EPC) and / or a 5G Core (5GC). Cellular core network 130 also manages traffic that flows between the cellular network and the Internet 140. IMS 150 can generally be described as an architecture for delivering multimedia services to UE 110 using IP protocols. IMS 150 can communicate with cellular core network 130 and the Internet 140 to provide multimedia services to UE 110. Network services backbone 160 communicates with the Internet 140 and cellular core network 130, either directly or indirectly. Network services backbone 160 can generally be described as a collection of components (e.g., servers, network storage arrangements, etc.) that implement a suite of services that can be used to extend the functionality of UE 110 in communicating with various networks.

[0031] Figure 2An example UE 110 is shown in accordance with various example embodiments. The UE 110 will be described with reference to the network arrangement 100. Figure 1 The UE 110 can include a processor 205, a memory arrangement 210, a display device 215, an input / output (I / O) device 220, a transceiver 225, and other components 230. The other components 230 can include, for example, an audio input device, an audio output device, a power source, a data acquisition device, a port for electrically connecting the UE 110 to other electronic devices, etc.

[0032] The processor 205 can be configured to execute a number of engines of the UE 110. For example, the engines can include a UE capability engine 235. The UE capability engine 235 can perform various operations related to the capabilities of the UE 110. To provide some general examples, the UE capability engine 235 can perform operations such as, but not limited to, determining operational capabilities of the UE 110, determining when the capabilities of the UE 110 should change, informing the network of the capabilities of the UE 110, etc.

[0033] The processor 205 can be configured to execute a number of engines of the UE 110. For example, the engines can also include an mTRP engine 240. The mTRP engine 240 can perform various operations related to mTRP operations. To provide some general examples, the mTRP engine 240 can perform operations such as, but not limited to, dynamically switching between mTRP mode and sTRP mode, updating CC groups for mTRP operations, and determining default downlink beams / TCI states for mTRP PDSCH reception.

[0034] The number of engines of the UE 110 can also include an L1 measurement reporting engine 245. The L1 measurement reporting engine 245 can perform operations including determining whether L1 measurements conflict with L3 measurements. When such a conflict is determined, some measurement results for RSs in a set of resources can not be synchronized with measurement results for other RSs in the set of resources. The L1 measurement reporting engine 245 can implement operations such as omitting certain measurement results from a measurement report, or informing the network whether some or all of the measurement results included in a measurement report are current or were determined in a previous measurement occasion.

[0035] The number of engines of the UE 110 can also include an enhanced 5G NR mobility engine 255. The enhanced 5G NR mobility engine 255 can perform various operations related to implementing the example mobility framework described herein. These operations can include, but are not limited to, receiving configuration information, performing measurements, sending measurement reports, receiving DCI, receiving MAC CEs, etc.

[0036] The engines 235, 240, 245, and 255 referenced above are each provided for illustrative purposes as an application (e.g., program) executed by the processor 205. The functionality associated with each of the engines 235, 240, 245, and 255 can also be represented as a separate bound component of the UE 110, or can be a modular component coupled to the UE 110, such as an integrated circuit with or without firmware. For example, the integrated circuit can include input circuitry to receive signals and processing circuitry to process the signals and other information. The engines can also be embodied as one application or multiple separate applications. Moreover, in some UEs, the functionality described with respect to the processor 205 is split between two or more processors, such as a baseband processor and an application processor. In particular, in some examples, when the UE 110 is operating in a low power mode, the capabilities of the UE 110 that are typically handled by the baseband processor can be reduced. The example embodiments can be implemented in any of these or other configurations of the UE.

[0037] The memory arrangement 210 can be a hardware component configured to store data related to operations performed by the UE 110. The display device 215 can be a hardware component configured to display data to a user, while the I / O device 220 can be a hardware component that enables a user to enter input. The display device 215 and the I / O device 220 can be separate components or can be integrated together, such as a touchscreen. The transceiver 225 can be a hardware component configured to establish a connection with the 5G NR-RAN 120, an LTE-RAN (not shown in the figure), a legacy RAN (not shown in the figure), a WLAN (not shown in the figure), and the like. Thus, the transceiver 225 can operate on a variety of different frequencies or channels (e.g., a contiguous set of frequencies).

[0038] The transceiver 225 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals can be encoded with information implementing any of the methods described herein. The processor 205 can be operatively coupled to the transceiver 225 and configured to receive signals from and / or transmit signals to the transceiver 225. The processor 205 can be configured to encode and / or decode signals (e.g., signaling from a base station of a network) for implementing any of the methods described herein.

[0039] Figure 3 An example base station 300 is shown in accordance with various example embodiments. The base station 300 can represent a gNB 120A or any other type of access node with which a UE 110 can establish a connection and manage network operations.

[0040] The base station 300 can include a processor 305, a memory arrangement 310, input / output (I / O) devices 315, a transceiver 320, other components 325, and one or more transmission and reception points (TRPs) 330. The other components 325 can include, for example, an audio input device, an audio output device, a battery, a data acquisition device, a port for electrically connecting the base station 300 to other electronic devices and / or a power source, a TxRU, a transceiver chain, an antenna element, an antenna panel, etc.

[0041] The processor 305 can be configured to execute a number of engines of the base station 300. For example, the engines can include a UE capability engine 335. The UE capability engine 335 can perform various operations related to the capabilities of the UE 110 for the base station 300. To provide some general examples, the UE capability engine 335 can perform operations such as, but not limited to, transmitting a signal to inquire about the capabilities of the UE 110, triggering the UE 110 to dynamically switch to a different set of capabilities, transmitting configuration information to the UE 110 to perform operations based on the current capabilities of the UE 110, etc.

[0042] The processor 305 can be configured to execute a number of engines of the base station 300. For example, the engines can include an mTRP engine 340. The mTRP engine 340 can perform various operations related to mTRP operations. To provide some general examples, the mTRP engine 340 can perform operations such as, but not limited to, transmitting a signal to trigger the UE 110 to dynamically switch between mTRP mode and sTRP mode, transmitting information to update a CC group for mTRP operations, and indicating a default downlink beam / TCI state for mTRP PDSCH reception.

[0043] The number of engines of the base station 300 can also include an L1 measurement processing engine 345. The L1 measurement reporting engine 345 can perform operations including receiving and processing measurement reports from the UE and performing beam management in reliance thereon.

[0044] The number of engines can include an enhanced 5G NR mobility engine 355. The enhanced 5G NR mobility engine 355 can perform various operations related to the example mobility framework described herein. These operations can include, but are not limited to, transmitting a handover preparation request to another gNB, receiving capability information, transmitting configuration information, receiving measurement data, allocating resources, transmitting a reference signal, transmitting DCI, transmitting a MAC CE, etc.

[0045] The engines 335, 340, 345, and 355 identified above as being executed by the processor 305 are each exemplary only. The functionality associated with the engines 335, 340, 345, and 355 can also be represented as separate combined components of the base station 300, or can be modular components coupled to the base station 300, such as integrated circuits with or without firmware. For example, the integrated circuits can include input circuitry for receiving signals and processing circuitry for processing signals and other information. Further, in some base stations, the functionality described with respect to the processor 305 is split among multiple processors (e.g., a baseband processor, an application processor, etc.). In particular, in some examples, operations for communicating with the UE 110 that are typically handled by a baseband processor can be reduced when the UE 110 is operating in a low power mode. The exemplary embodiments can be implemented in any of these or other configurations of the base station.

[0046] The memory 310 can be a hardware component that is configured to store data related to operations performed by the base station 300. The I / O device 315 can be a hardware component or port that enables a user to interact with the base station 300. The transceiver 320 can be a hardware component that is configured to exchange data with the UE 110 and any other UEs in the network arrangement 100. The transceiver 320 can operate on a variety of different frequencies or channels (e.g., a set of contiguous frequencies). Thus, the transceiver 320 can include one or more components to enable data exchange with various networks and UEs.

[0047] The transceiver 320 includes circuitry configured to transmit and / or receive signals (e.g., control signals, data signals). Such signals can be encoded with information implementing any of the methods described herein. The processor 305 can be operatively coupled to the transceiver 320 and configured to receive and / or transmit signals from / to the transceiver 320. The processor 305 can be configured to encode and / or decode signals (e.g., signaling from a UE) for implementing any of the methods described herein.

[0048] Figure 4An illustration 400 showing a UE 410 according to the example embodiments herein is illustrated. The UE 410 can be capable of simultaneously receiving two beams used by the network using two antenna panels of the UE (with one antenna panel used to receive a corresponding one of the two beams from the network). The illustration 400 illustrates a first scan range and gain 402 of a first antenna panel of the UE 410 and a second scan range and gain 404 of a second antenna panel of the UE 102 (which can for example differ from the first scan range and gain 404) corresponding to this functionality. In such cases, it will be appreciated that as illustrated, a first beam can arrive at the first antenna panel at a first angle of arrival 406, while a second beam can arrive at the second antenna panel at a second angle of arrival 408. It is noted that it is contemplated that in some embodiments, this arrangement can be used to successfully receive multiple beams used by the network on the same component carrier (CC), while in other embodiments, the multiple beams can belong to different CCs (e.g., carrier aggregation (CA) can be used).

[0049] In some cases, the first and second antenna panels are separate physical panels of the UE. However, it is noted that as used herein, an antenna panel can also be understood to refer to a logical antenna panel concept. Thus, it will be appreciated that cases described herein, e.g., of a first and second antenna panel, also encompass cases where a single physical antenna panel module is used, with the first panel corresponding to a first weight on that antenna panel module, and the second panel corresponding to a second weight on that antenna panel module.

[0050] A beam reporting mechanism can allow a UE to report to the network a pair of beams that the UE is capable of using according to a multiple-reception (multi-Rx) chain downlink (DL) reception functionality.

[0051] Two example beam reporting mechanisms are described that can be used in a wireless communication system that allow a UE to support simultaneous reception of multiple beams from different directions corresponding to different QCL-TypeD RSs (e.g., on the same CC or on different CCs). A first such mechanism can use group-based beam reporting (GBBR), and the UE can report a pair of beams that it is capable of simultaneously receiving. In a second such mechanism, GBBR can be used, and the UE can be capable of reporting up to four pairs of beams.

[0052] In any case, it can be possible for the UE to report, for each of the beam pair(s) reported by the UE in a beam report message to the network, a Ll-RSRP value for each beam in the pair. For example, if a beam pair comprising beams B1 and B2 is to be reported by the UE in a beam report message, the UE also reports B1 and B2the associated L1-RSRP of each of

[0053] In this document, according to convention used in the present disclosure, the L1-RSRP of each of B1 and B2 may be referred to as RSRP_ B1 , RSRP_ B2 , respectively. Similar convention can be followed herein with respect to other characteristics of beams. For example, according to convention used in the present disclosure, B1 and B2 the L1-SINR of each of B1 , SINR_ B2 . As a further example, B1 and B2 the angle of arrival (AoA) of each of B1 and AoA_ B2 .

[0054] To improve performance, the following aspects can be considered. First, it has been identified that it is useful to define the use of one or more UE reporting criteria for beam pair reporting. That is, it can be useful to establish criteria for determining at a UE whether a beam pair has properties such that simultaneous DL communication to the UE (e.g., on the same CC or on different CCs) is desired, such that the UE selects to report the beam pair to the network. A beam pair determined by a UE to have properties according to such criteria such that, for example, simultaneous DL communication to the UE is desired can be referred to herein as a “qualified beam pair.”

[0055] Second, it has been identified that it is useful to establish particular ways in which reported beam pairs are updated. For example, in existing wireless communication systems, there can be no mechanism for determining whether a previously reported beam pair remains valid / useful at a UE, and / or how such information should be updated from / by a UE to a network when the relevant environment changes.

[0056] Embodiments of beam pair reporting criteria Embodiments related to the use of beam pair reporting criteria are now discussed. Such embodiments can involve, for example, a determination at a UE as to whether a first beam and a second beam receivable at the UE together constitute a qualified beam pair that should be reported to a network for use by the network (potentially) for simultaneous communication with the UE. In this document, the first beam for such consideration can be referred to as B1 , and the second beam for such consideration can be referred to as B2 .

[0057] Consistent with the description herein, B1 and B2one or more characteristics of each of B1 and B2 may be applied, along with one or more conditions, in order to determine B1 and / or B2 an RSRP (e.g., Ll-RSRP) value of each of B1 and / or B2 an AoA at the UE of each of B1 and / or B2 a signal-to-interference-and-noise ratio (SINR) of each of

[0058] In some cases in which such conditions are used, the RSRP B1 and the RSRP B2 may be applied relative to a relevant threshold.

[0059] For example, a first condition can use an RSRP threshold that applies to each of the RSRP B1 and the RSRP B2 . The first condition can require that each of the RSRP B1 and the RSRP B2 be greater than or equal to (or greater than) the RSRP threshold in order to identify B1 and B2 as a qualified beam pair. Thus, the UE can compare each of the RSRP B1 and the RSRP B2 to the RSRP threshold and identify B1 and B2 as a qualified beam pair if each is greater than or equal to (or greater than) the RSRP threshold.

[0060] As another example, a second condition can use an RSRP difference threshold. The second condition can require that a difference between the RSRP B1 and the RSRP B2 be greater than or equal to (or greater than) the RSRP difference threshold in order to identify B1 and B2 as a qualified beam pair. Thus, the UE can calculate a difference between the RSRP B1 and the RSRP B2 , compare the difference to the RSRP difference threshold, and identify B1 and B2 as a qualified beam pair if the difference is greater than or equal to (or greater than) the RSRP difference threshold.

[0061] In some cases in which such conditions are used, the AoA B1and AoA B2 .

[0062] For example, the third condition can use an AoA offset threshold. The third condition can require that the offset (e.g., the angular difference) between the AoA B1 and the AoA B2 is greater than or equal to (or greater than) the AoA offset threshold in order to identify B1 and B2 as a qualified beam pair. Thus, the UE can calculate the offset between the AoA B1 and the AoA B2 , compare the offset to the AoA offset threshold, and identify B1 and B2 as a qualified beam pair if the offset is greater than or equal to (or greater than) the AoA offset threshold.

[0063] In some cases using such conditions, the SINR B1 and the SINR B2 may be applied relative to a relevant threshold.

[0064] For example, the fourth condition can use a SINR threshold that applies to each of the SINR B1 and the SINR B2 . The fourth condition can require that each of the SINR B1 and the SINR B2 is greater than or equal to (or greater than) the SINR threshold in order to identify B1 and B2 as a qualified beam pair. Thus, the UE can compare each of the SINR B1 and the SINR B2 to the SINR threshold and identify B1 and B2 as a qualified beam pair if each is greater than or equal to (or greater than) the SINR threshold.

[0065] As another example, the fifth condition can use a SINR difference threshold. The fifth condition can require that the difference between the SINR B1 and the SINR B2 is greater than or equal to (or greater than) the SINR difference threshold in order to identify B1 and B2 as a qualified beam pair. Thus, the UE can calculate the difference between the SINR B1 and the SINR B2 , compare the difference to the SINR difference threshold, and identify B1 and B2identified as a qualified beam pair.

[0066] Note that the specific examples of conditions discussed herein are given by way of example and not by way of limitation.

[0067] Further, it is contemplated that, in some embodiments, when evaluating whether a beam pair B1 and B2 is a qualified beam pair, multiple conditions can be used. For example, two (or more) of the conditions described herein can need to be satisfied in the manner described before the UE identifies B1 and B2 as a qualified beam pair.

[0068] Note also that it has been recognized that, in some cases, a beam report message identifying qualified beam pairs B1 and B2 may include more than, for example, RSRP_ B1 and RSRP_ B2 For example, in some cases, SINR_ B1 and SINR_ B2 may be (e.g., also) reported in a beam report message identifying B1 and B2 as a qualified pair. Note that using SINR values in a beam report message in this manner can correspond to the UE identifying B1 and B2 as a qualified beam pair using one or more SINR-related conditions, as described herein.

[0069] The potential sources of the relevant thresholds corresponding to the conditions used are now discussed. In some cases, the threshold used can be a single predefined value at the UE for the corresponding condition.

[0070] In other cases, the threshold used can be one of a predefined range of values at the UE for the corresponding condition. In some such cases, when a group-based beam report is configured to the UE, one of the predefined values for the condition used at the UE can be signaled to the UE by the network. In other such cases, one of the predefined values for the condition used at the UE can be signaled to the network by the UE in a UE capability message corresponding to the UE’s capabilities.

[0071] In cases where the UE tests more than two beams, it can be possible for the UE to identify multiple qualified beam pairs by using one or more conditions as described herein. In cases where multiple qualified beam pairs are identified, the UE can report them together in a single beam report message. Prior to transmitting such a beam report message, the UE can order the qualified beam pairs within the beam report message.

[0072] Now discuss mechanisms for ordering multiple qualified beam pairs. In some cases, the UE can order a set of qualified pairs each having a beam B1 and B2 based on a sum of their respective RSRP B1 and RSRP B2 values. In this case, the qualified beam pair with the largest sum can be ranked first, the qualified beam pair with the second largest sum can be ranked second, and so on. Note that the sum of these RSRP values can be performed in linear domain or in logarithmic domain.

[0073] In some cases, the UE can order a set of qualified beam pairs each having a beam B1 and B2 based on a minimum between their respective RSRP B1 and RSRP B2 values, which can be denoted as min(RSRP B1 , RSRP B2 ) for that beam pair. In this case, the qualified beam pair with the largest min(RSRP B1 , RSRP B2 ) can be ranked first, the qualified beam pair with the second largest min(RSRP B1 , RSRP B2 ) can be ranked second, and so on.

[0074] In some cases, the UE can order a set of qualified beam pairs each having a beam B1 and B2 based on a maximum between their respective RSRP B1 and RSRP B2 values, which can be denoted as max(RSRP B1 , RSRP B2 ) for that beam pair. In this case, the qualified beam pair with the largest max(RSRP B1 , RSRP B2 ) can be ranked first, the qualified beam pair with the second largest max(RSRP B1 , RSRP B2 ) can be ranked second, and so on.

[0075] In some cases, the UE can order a set of qualified pairs each having a beam B1 and B2 based on a sum of their respective SINR B1 and SINR B2 values. In this case, the qualified beam pair with the largest sum can be ranked first, the qualified beam pair with the second largest sum can be ranked second, and so on.The set of qualified beam pairs is sorted. In this case, the qualified beam pair with the largest sum can be ranked first, the qualified beam pair with the second largest sum can be ranked second, and so on.

[0076] In some cases, the UE can be based on beam. B1 and B2 The sum of the corresponding effective channel capabilities is used to determine the beam size of each component. B1 and B2 Sort the set of qualified pairs, where SINR_ is used respectively. B1 and SINR_ B2 To calculate and B1 and B2 The effective channel capability corresponding to each of them. For example, it can be... B1 The effective channel capability is calculated as log(1+SINR_ B1 ), and can B2 The effective channel capability is calculated as log(1+SINR_B2). Once the sum of these two values ​​has been calculated for each eligible beam pair, the eligible beam pair with the largest such sum is ranked first, the eligible beam pair with the second largest such sum is ranked second, and so on.

[0077] In some cases, the UE can base its configuration on the SINR of each beam pair. B1 and SINR_ B2 The minimum value between (which can be expressed as min(SINR_) of the beam pair) B1 SINR_ B2 Each has its own beam B1 and B2 The set of qualified beam pairs is sorted. In this case, the one with the maximum min(SINR_ B1 SINR_ B2 The qualified beam pair can be ranked first, with the second largest min(SINR_ B1 SINR_ B2 The qualified beam pairs of (SINR_) can be ranked second, and so on. Note that the maximum min(SINR_) B1 SINR_ B2 This can be correlated with the minimum data rate supported at each beam, so ranking based on this can help the network make determinations related to Quality of Service (QoS).

[0078] In some cases, the UE can base its configuration on the SINR of each beam pair. B1 and SINR_ B2 The maximum value between (which can be expressed as max(SINR_) of the beam pair) B1 SINR_B2 ) pairs of beams B1 and B2 are sorted. In this case, the pair of beams with the largest max(SINR_ B1 , SINR_ B2 ) can be ranked first, the pair of beams with the second largest max(SINR_ B1 , SINR_ B2 ) can be ranked second, and so on.

[0079] Note that the particular examples of the ranking mechanisms discussed herein are given by way of example and not by way of limitation.

[0080] It is contemplated that the UE can apply multiple ranking mechanisms corresponding to multiple orders of ranking. For example, a first order of ranking can use a first ranking mechanism, and a second order of ranking (e.g., to break any ties that arise based on the first order of ranking) can use a different ranking mechanism, and so on.

[0081] In some embodiments, the network (e.g., base station) can further configure / limit the beam pairs that can be reported by the UE. This can be useful in cases where it is desirable to incorporate the effects of the AoA and / or angle of departure (AoD) corresponding to the beams into the analysis and it cannot be assumed that the UE is able to generate this information independently based on its reception of the beams (e.g., because the UE is only able to use a relatively wide Rx beam over its antenna panel).

[0082] Various options regarding network-side considerations of the validity of beam pairs are now discussed. In a first option, for a valid beam pair reported by the UE, the network starts a beam pair validity timer corresponding to the valid beam pair. When the timer expires, the network considers the beam pair to no longer be valid / available. In some embodiments, the network is provided with a starting value for the beam pair validity timer by the UE in a beam report message indicating the valid beam pair.

[0083] The starting value for the beam pair validity timer can be predefined (e.g., per specification of the wireless communication system). The predefinition can be a single starting value. Alternatively, the predefinition can be a range of such starting values.

[0084] In some cases, the network can configure two active transmission configuration indicator (TCI) states to the UE, one corresponding to each beam in the reported beam pair. In such cases, if the network receives a hybrid automatic repeat request acknowledgement (HARQ-ACK) corresponding to each of the first and second TCI states from the UE, the beam pair validity timer for the beam pair can be reset.

[0085] In some embodiments, upon expiration of the beam pair validity timer, the network can initiate another group-based beam report procedure with the UE (e.g., in order to establish a new qualified beam pair for communication with the UE).

[0086] In some embodiments, if the UE determines that the beam pair is (e.g., still) valid, the UE can send a coverage message to the network to cover the beam pair validity timer. In various embodiments, the coverage message can be conveyed to the network via any of a radio resource control (RRC) message, a medium access control control element (MAC-CE), and / or uplink control information (UCI). In response to the coverage message, the network can reset the beam pair validity timer (e.g., to an original value and / or to a value specified by the UE in the coverage message).

[0087] A second option for network-side considerations regarding validity of a beam pair at the network can be as follows. When using periodic / semi-periodic group-based reporting, periodic / semi-periodic beam report messages can be accordingly received at the network from the UE. In such cases, the network can understand that the most recently reported beam pair covers the previously reported beam pair. Moreover, if a beam pair validity timer is also used in such cases (e.g., as described herein), the beam pair validity timer can be reset upon receipt of each periodic / semi-periodic beam report message.

[0088] In some cases, the UE can initiate a beam pair update by conveying a beam pair update message to the network. The beam pair update message can indicate, for example, one or both of one or two replacement beams for one or both of the beams B1 、 B2 that make up the current qualified beam pair as interpreted by the network. Upon receipt of the beam pair update message, the network can replace the beams B1 and / or B2 with the corresponding replacement beams from the beam pair update message.

[0089] In some such cases, the beam pair update message can be treated / sent by the UE as UCI. In a first such alternative, the beam pair update message can be treated as special channel state information (CSI) feedback from the UE to the network. Under this alternative, the beam pair update message can have the same priority as existing CSI in use, e.g., the same priority as Ll-RSRP CSI feedback or Ll-SINR CSI feedback.

[0090] In a second such alternative where the beam pair update message is UCI, the beam pair update message can be handled / transmitted as a new type of UCI (e.g., in addition to existing UCI such as scheduling request (SR) / HARQ-ACK / CSI / configured grant uplink control information (CG-UCI), etc., which can be used in a wireless communication system). In this alternative, the beam pair update message can be independently encoded using polar codes. Alternatively, the beam pair update message can be jointly encoded with other types of UCI using polar codes.

[0091] In other cases of beam pair update messages (e.g., in addition to the beam pair update message as UCI just discussed), the beam pair update message can be transmitted in a MAC-CE. In such cases, if the UE already has an uplink (UL) grant for a physical uplink control channel (PUSCH) transmission, the UE can use the existing UL grant to transmit the MAC-CE.

[0092] However, in some cases, the mechanisms discussed above for a UE to indicate a beam pair update can have issues. For example, referring to Figure 5 If the UE rotates, the UE can no longer be able to perform simultaneous reception from multiple TRPs. In Figure 5 On the left, UE 110 receives beams from both TRP1 and TRP2 simultaneously, e.g., UE 110 receives RX beam 1 from TRP1 on panel 1 and also receives RX beam 2 from TRP2 on panel 2. In this way, UE 110 is able to receive simultaneous reception from TRP1 and TRP2 by receiving RX beam 1 and RX beam 2 on separate panels. However, if UE 110 rotates, as seen on the right, Figure 5 panel 1 rotates away from TRP1 and TRP2, panel 1 of UE 110 can no longer receive beams from TRP1 or TRP2. After rotation, UE 110 is not able to perform simultaneous reception from TRP1 and TRP2 by using RX beam 1 and RX beam 2 because the AoA from both TRPs results in two RX beams on the same panel. In this case, panel 1 does not receive any beams. In this case, if this rotation occurs during a periodic beam report, UE 110 is not able to perform a beam update and can not be able to identify a suitable beam pair.

[0093] In the traditional case where the UE has only one RX beam for reception, there is no issue caused by UE rotation. The UE will have a beam measurement procedure of Type D with a specific RS QCL after the active TCI for PDCCH / PDSCH reception, e.g., the UE will not do GBBR. Before and after UE rotation, the active TCI for PDCCH or PDSCH can always find the best RX beam according to the parallel beam measurement procedure, e.g., when using a single beam measurement procedure, UE rotation does not affect beam measurement. But for paired Rx beams, after UE rotation, even if the UE has such beam measurement, the UE can not be able to find a new beam pair to support simultaneous reception from TRP1 and TRP2, as shown above Figure 5 .

[0094] When the UE is doing group-based beam reporting (GBBR) and the conditions of the UE change such that the UE cannot find a suitable beam pair (such as rotation of the UE), the UE will waste time to find a new beam pair and also will waste throughput until the next GBBR measurement. GBBR measurement is configured by the network, and thus between two GBBR reporting occasions, the network cannot know whether the beam pair at the UE side is valid and cannot change the network scheduling scheme in time in response to the change of the beam pair.

[0095] Example embodiments provide various ways to solve this problem. Generally, the UE will initiate a beam pair update and / or will indicate to the network that there is a problem trying to find a suitable beam pair at the receiver side as fast as possible. There are several examples that can be used by the UE to initiate and / or indicate the configuration change. These example embodiments will be described in more detail below.

[0096] In a first example embodiment, event-triggered reporting is configured by the network for the UE to report the problem to the network in time. The first example embodiment will be described with reference to the call flow of Figure 6 .

[0097] Figure 6 An example call flow 600 is shown in accordance with various example embodiments in which a UE 110 is configured for event-triggered reporting. In the example of Figure 6 , the call flow 600 is performed between the UE 110 and a network (e.g., gNB 120A).

[0098] In 610, the network (e.g., gNB 120A) configures the UE 110 with periodic RS for beam pair measurement and event-triggered reporting. In the example of Figure 6 , the configuration of the beam pair measurement and event-triggered reporting is shown as being communicated in the same message. However, this is just an example and multiple messages can be used.

[0099] The network can configure various events for event triggered reporting. In one option, the event can be that a Rx beam pair is invalid. A first example of UE 110 determining that an event has occurred can be that UE 110 is unable to find a reliable Rx beam pair to support simultaneous reception of physical downlink control channel (PDCCH) and / or physical downlink shared channel (PDSCH) from multiple TRPs. A second example of UE 110 determining that an event has occurred can be that the signal to interference plus noise ratio (SINR) and / or reference signal received power (RSRP) of any Rx beam is below a threshold. In a third example, the combined SINR / RSRP of a Rx beam pair is below a threshold, where the combined mean is the sum, or the most efficient SINR / RSRP pair based on capability, or the minimum SINR / RSRP of the Rx beam pair.

[0100] In a second option, the event can be a beam failure or radio link failure identified by UE 110 on any beam of a beam pair. In a third option, the event can be a case where the SINR or RSRP of any beam of a beam pair changes by more than a threshold. These events are examples only, and other events can also be configured by the network.

[0101] Thus, in 620, UE 110 will monitor for the configured event. It should be understood that UE 110 will also perform the configured beam pair measurements. In Figure 6 In the example of FIG. 6, UE 110 can determine that a configured event has occurred.

[0102] In 630, UE 110 will report to the network that the event has occurred. UE 110 can report that the event has occurred using a L1 report (e.g., uplink control information (UCI)), a MAC-CE report, a RRC report, or perform a random access channel (RACH) procedure on the failed link (if one link has a beam failure or link failure). The report can indicate that a Tx beam pair is invalid, a Rx beam pair is invalid, and / or that a new GBBR resource set needs to be measured.

[0103] Thus, a first example provides a way for UE 110 to timely report a Rx beam pair invalid based on RS measurements performed by UE 110.

[0104] In a second example implementation, a sensor based trigger is configured by the network for UE to timely report issues to the network. The second example implementation will be described with reference to Figure 7 the call flow of FIG. 7.

[0105] Figure 7An example call flow 700 in which a UE 110 is configured for sensor-based trigger reporting is shown, in accordance with various example embodiments. Figure 7 In examples, the call flow 700 is performed between the UE 110 and a network (e.g., gNB 120A).

[0106] In 710, the UE 110 can indicate to the network a capability to use a sensor to detect a rotation or beam change. As will be described in greater detail below, the UE 110 capability to detect a rotation or beam change can be based on, for example, a gyroscope-based UE pose or an accelerometer.

[0107] In 720, the network (e.g., gNB 120A) configures the UE 110 for beam pair measurements and periodic RS for sensor-based trigger reporting based on the UE 110 reporting the capability in 710. In Figure 7 In examples, the configuration of the beam pair measurements and event-triggered reporting is shown as being communicated in the same message. However, this is merely an example, and multiple messages can be used.

[0108] The network can configure various sensor measurements for sensor-triggered reporting based on the capability of the UE 110. In a first option, the sensor measurement can be a gyroscope measurement indicating that the pose change of the UE 110 is above a threshold. In a second option, the sensor measurement can be an accelerometer measurement indicating that the UE position change is above a threshold. These measurements are merely examples, and other measurements can also be configured by the network.

[0109] Accordingly, in 730, the UE 110 will perform the sensor measurement and monitor the measurement to indicate that a rotation or beam change has occurred. It should be understood that the UE 110 will also perform the configured beam pair measurements. In Figure 7 In examples, the UE 110 can determine that a rotation or beam change has occurred based on the sensor measurement.

[0110] In 740, the UE 110 will report to the network that a rotation or beam change has occurred. The report can be the actual sensor measurement, or that the event indicated by the sensor measurement value has occurred (e.g., a rotation or beam change). The UE 110 can report the event (or sensor measurement) using a L1 report (e.g., uplink control information (UCI)), a MAC-CE report, a RRC report, or perform a random access channel (RACH) procedure on a failed link if one link has a beam failure or link failure. The report can also indicate that a Tx beam pair is invalid, a Rx beam pair is invalid, and / or that a new GBBR resource set needs to be measured.

[0111] Accordingly, the second example provides ways for the UE 110 to timely report a beam pair invalidation based on sensor measurements performed by the UE 110.

[0112] In a third example, the beam pair used for simultaneous PDCCH / PDSCH reception from a TRP can have a high block error rate (BLER), decoding errors, or reception failures, but the separate BFD and RLM on these links with the TRP are still good (e.g., there is no separate beam failure or link failure). This can occur because the Rx beam pair used for simultaneous PDCCH / PDSCH reception from a TRP can be different beams from the separate best beams toward the TRP, e.g., Rx beam 1 and Rx beam 2 are used in order to support simultaneous PDCCH / PDSCH reception from a TRP because they have the least interference. However, the separate Rx beam used for receiving PDCCH / PDSCH from only one TRP can be different from Rx beam 1 or Rx beam 2. When this scenario occurs, the third example can include a network-side based solution or a UE-side based solution. The network-side based solution will be described with reference to Figure 8 The network-side based solution is described, and will be described with reference to Figure 9 The UE-side based solution is described.

[0113] Figure 8 An example call flow 800 is shown in which the network reconfigures the UE 110 based on feedback or lack of feedback from the UE 110, in accordance with various example embodiments. In this example, the call flow 800 is performed between the UE 110 and the network (e.g., gNB 120A). Figure 8 The call flow 800 is performed between the UE 110 and the network (e.g., gNB 120A).

[0114] In 810, the network (e.g., gNB 120A) configures the UE 110 with periodic RS for beam pair measurements.

[0115] In 820, the network monitors for feedback from the UE 110. For example, when the network has scheduled simultaneous PDCCH / PDSCH to the UE, the network can receive continuous negative acknowledgement (NACK) or no acknowledgement (ACK) feedback from the UE 110 on one or both links (based on the corresponding beams). However, the network has not received a beam failure or link failure report / indication from the UE 110.

[0116] When this occurs, in 830, the network can configure the UE 110 to perform GBBR reporting, or configure the UE 110 with a new set of resources to measure and perform GBBR reporting.

[0117] Figure 9An example call flow 900 in which a UE 110 is configured to report beam pair failure when there is no individual beam or link failure at the UE 110 is shown, in accordance with various example embodiments. Figure 9 In an example, the call flow 900 is performed between the UE 110 and a network (e.g., gNB 120A).

[0118] In 910, the network (e.g., gNB 120A) configures the UE 110 with periodic RS for beam pair measurement.

[0119] In 920, the UE 110 identifies a condition based on the configured measurement. As described above, the condition can be when the network schedules simultaneous PDCCH / PDSCH to the UE 110, the UE has high BLER, decoding error, or reception failure on one or both links (based on corresponding beams), but no beam or link failure is identified at the UE 110.

[0120] In 930, the UE 110 will report to the network that the condition has occurred. The UE 110 can report that the condition has occurred using a LI report (e.g., uplink control information (UCI)), a MAC-CE report, a RRC report, or perform a random access channel (RACH) procedure on the failed link (if one link has beam or link failure). The report can indicate Tx beam pair invalid, Rx beam pair invalid, and / or a new GBBR resource set is needed for measurement.

[0121] In a fourth example, which can also be used with one or more of the other examples, body proximity sensing (BPS) based measurement and reporting can be used. The second example embodiment will be described with reference to the call flow of Figure 10

[0122] Figure 10 An example call flow 1000 in which a UE 110 is configured for body proximity sensing (BPS) based measurement and reporting is shown, in accordance with various example embodiments. In Figure 10 In an example, the call flow 1000 is performed between the UE 110 and a network (e.g., gNB 120A).

[0123] In 1010, the UE 110 can indicate to the network a capability to perform BPS to detect rotation or beam change. The BPS capability allows the UE 110 to determine whether a biological entity, a biological presence (e.g., a human entity / presence) is located within a certain distance of the UE 110. This BPS capability can be used to detect rotation or beam change of the UE 110.

[0124] ​In 1020, the network (e.g., gNB 120A) configures the UE 110 with periodic RS for beam pair measurements and BPS based trigger reporting based on the UE 110 reporting the capability in 1010. In Figure 10 In examples, the configuration of beam pair measurements and BPS triggered reporting is shown as being communicated in the same message. However, this is just an example, and multiple messages can be used.

[0125] In 1030, the UE 110 will perform BPS measurements to determine if a rotation or beam change has occurred. It should be understood that the UE 110 will also perform the configured beam pair measurements. In Figure 10 In examples, the UE 110 can determine that a rotation or beam change has occurred based on the BPS measurements.

[0126] In 1040, the UE 110 will report to the network that a rotation or beam change has occurred. The report can be the actual BPS measurements, or that the event indicated by the BPS measurements has occurred (e.g., a rotation or beam change). The UE 110 can report the event (or sensor measurements) using a Ll report (e.g., uplink control information (UCI)), a MAC-CE report, a RRC report, or perform a random access channel (RACH) procedure on a failed link (if one link has a beam or link failure). The report can also indicate that a Tx beam pair is invalid, a Rx beam pair is invalid, and / or that a new GBBR resource set needs to be measured.

[0127] Embodiments In a first embodiment, a method is performed by a user equipment (UE), the method comprising: decoding, from signaling received from a base station, configuration information related to simultaneous reception of signals from a plurality of transmission and reception points (TRPs), wherein a signal from a first TRP is received using a first receive (Rx) beam of an Rx beam pair and a signal from a second TRP is received using a second Rx beam of the Rx beam pair; determining that an event related to the Rx beam pair has occurred; and configuring transceiver circuitry to transmit, to the base station, an indication of the event, wherein the indication comprises: (i) an indication that a transmit (Tx) beam pair is invalid, (ii) an indication that the Rx beam pair is invalid, or (iii) an indication that one or more resource sets group-based beam reporting (GBBR) are to be configured for the UE.

[0128] In a second embodiment, the method of the first embodiment, wherein the indication is transmitted using uplink control information (UCI) signaling, medium access control control element (MAC-CE) signaling, or radio resource control (RRC) signaling.

[0129] In a third embodiment, the method of the first embodiment, wherein the configuration information comprises a periodic reference signal (RS) for measuring the pair of Rx beams, and the event relates to a measurement performed by the UE on the periodic RS.

[0130] In a fourth embodiment, the method of the third embodiment, wherein the event comprises that the pair of Rx beams is invalid based on: (i) the UE failing to find the pair of Rx beams to support simultaneous reception of physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH) from the first TRP and the second TRP, (ii) a signal to interference plus noise ratio (SINR) of the first Rx beam or the second Rx beam being below a threshold, (iii) a reference signal received power (RSRP) of the first Rx beam or the second Rx beam being below a threshold, (iv) a combined SINR of the first Rx beam and the second Rx beam being below a threshold, or (v) a combined RSRP of the first Rx beam and the second Rx beam being below a threshold.

[0131] In a fifth embodiment, the method of the third embodiment, wherein the event comprises a beam failure or a radio link failure of the first Rx beam or the second Rx beam.

[0132] In a sixth embodiment, the method of the fifth embodiment, wherein the indication comprises a random access channel (RACH) procedure transmission of the first Rx beam or the second Rx beam.

[0133] In a seventh embodiment, the method of the third embodiment, wherein the event comprises a change in a signal to interference plus noise ratio (SINR) of the first Rx beam or the second Rx beam being above a threshold, or a change in a reference signal received power (RSRP) of the first Rx beam or the second Rx beam being above a threshold.

[0134] In an eighth embodiment, the method of the first embodiment, wherein a sensor of the UE detects the event.

[0135] In a ninth embodiment, the method of the eighth embodiment, further comprising configuring transceiver circuitry to transmit, to the base station, a capability related to the sensor.

[0136] In a tenth embodiment, the method of the eighth embodiment, wherein the sensor is a gyroscope, and the event is a change in an attitude of the UE above a threshold.

[0137] In an eleventh embodiment, the method of the eighth embodiment, wherein the sensor is an accelerometer, and the event is a change in a position of the UE above a threshold.

[0138] In a twelfth embodiment, the method according to the first embodiment, wherein the event comprises a block error rate (BLER), a decoding error, or a reception error for one of the first Rx beam or the second Rx beam that is above a threshold value without a beam failure or a link failure of the one of the first Rx beam or the second Rx beam.

[0139] In a thirteenth embodiment, the method according to the first embodiment, the method further comprising one or more sensors configured to perform body proximity sensing (BPS), wherein the event is based on a detection of a body by the BPS.

[0140] In a fourteenth embodiment, the method according to the thirteenth embodiment, the method further comprising configuring the transceiver circuitry to transmit, to the base station, a capability related to the BPS.

[0141] In a fifteenth embodiment, a processor configured to perform any of the methods according to the first through fourteenth embodiments.

[0142] In a sixteenth embodiment, a user equipment (UE) comprising a transceiver configured to communicate with a network; and a processor communicatively coupled to the transceiver and configured to perform any of the methods according to the first through fourteenth embodiments.

[0143] In a seventeenth embodiment, a method performed by a base station, the method comprising configuring transceiver circuitry to transmit, to a user equipment (UE), configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein the configuration information comprises identifying reception, by the UE, of a signal from a first TRP using a first receive (Rx) beam of a Rx beam pair and reception, by the UE, of a signal from a second TRP using a second Rx beam of the Rx beam pair; monitoring, from the UE, a feedback signal related to reception, by the UE, of the signal from the first TRP using the first Rx beam and reception, by the UE, of the signal from the second TRP using the second Rx beam; and configuring the transceiver circuitry to transmit, to the UE, updated configuration information.

[0144] In an eighteenth embodiment, the method according to the seventeenth embodiment, wherein the feedback signal comprises consecutive negative acknowledgement (NACK) signals for the first Rx beam or the second Rx beam.

[0145] In a nineteenth embodiment, the method of the seventeenth embodiment, wherein, while the apparatus monitors the feedback signal, the apparatus does not receive an acknowledgement (ACK) signal for one of the first Rx beam or the second Rx beam, and does not receive a beam failure or link failure indication for the one of the first Rx beam or the second Rx beam.

[0146] In a twentieth embodiment, the method of the seventeenth embodiment, wherein the updated configuration information comprises instructions for the UE to perform group-based beam reporting (GBBR) measurements and reporting using a previously configured set of resources.

[0147] In a twenty-first embodiment, the method of the seventeenth embodiment, wherein the updated configuration information comprises instructions for the UE to perform group-based beam reporting (GBBR) measurements and reporting using a newly configured set of resources.

[0148] In a twenty-second embodiment, a processor configured to perform any of the methods of the seventeenth through twenty-first embodiments.

[0149] In a twenty-third embodiment, a base station comprising: a transceiver configured to communicate with a user equipment (UE); and a processor communicatively coupled to the transceiver and configured to perform any of the methods of the seventeenth through twenty-first embodiments.

[0150] Those skilled in the art will understand that the exemplary embodiments described above can be implemented in any suitable software configuration or hardware configuration, or a combination thereof. Exemplary hardware platforms for implementing the exemplary embodiments can include, for example, Intel x86-based platforms with compatible operating systems, Windows OS, Mac platforms and MAC OS, mobile devices with operating systems such as iOS, Android, and the like. The above exemplary embodiments can be embodied as a program including code lines stored on a non-transitory computer-readable storage medium, which, when compiled, can be executed on a processor or microprocessor.

[0151] In some embodiments, a non-transitory computer-readable storage medium (e.g., a non-transitory memory element) can be configured to have stored thereon program instructions and / or data, which, if executed by a computer system, cause the computer system to perform a method, such as 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.

[0152] In some embodiments, a device (e.g., a UE) can be configured to include a processor (or a set of processors) and a memory medium (or memory element), where the memory medium stores program instructions, where the processor is configured to read and execute the program instructions from the memory medium, where the program instructions are executable to implement any of the various method embodiments (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) described herein. The device can be implemented in any of various forms.

[0153] Embodiments of the application can be implemented in any of various forms. For example, in some embodiments, the application can be implemented as a computer-implemented method, a computer-readable memory medium, or a computer system. In other embodiments, the application can be implemented using one or more custom-designed hardware devices such as ASICs. In other embodiments, the application can be implemented using one or more programmable hardware elements such as FPGAs.

[0154] While the present application describes various embodiments each having different features in various combinations, those skilled in the art will understand that any feature of one embodiment can be combined with features of another embodiment, in any manner not expressly and implicitly excluded by the principles and spirit of the application.

[0155] It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled in a way to minimize plant or unauthorized access, modification or disclosure thereof. Additionally, users should be informed about how their personal identifiable information data is being used by a website or platform who collects such data.

[0156] As will be apparent to those of ordinary skill in the art, various modifications can be made to the present disclosure without departing from the scope or spirit of the disclosure. Therefore, it is to be understood that the disclosure is intended to cover all modifications and alternative methods falling within the scope of the claims and their equivalents.

Claims

1. An apparatus of a user equipment (UE), the apparatus comprising processing circuitry configured to: decode, from signaling received from a base station, configuration information related to simultaneous reception of signals from a plurality of transmission and reception points (TRPs), wherein a first receive (Rx) beam of a pair of Rx beams is used to receive signals from a first TRP and a second Rx beam of the pair of Rx beams is used to receive signals from a second TRP; determine that an event related to the pair of Rx beams has occurred; and configure transceiver circuitry to transmit, to the base station, an indication of the event, wherein the indication comprises: (i) an indication that a pair of transmit (Tx) beams is invalid, (ii) an indication that the pair of Rx beams is invalid, or (iii) an indication that one or more resource set based group beam reporting (GBBR) is to be configured for the UE.

2. The apparatus of claim 1, wherein the indication is transmitted using uplink control information (UCI) signaling, medium access control control element (MAC-CE) signaling, or radio resource control (RRC) signaling.

3. The apparatus of claim 1, wherein the configuration information comprises a periodic reference signal (RS) used to measure the pair of Rx beams, and the event relates to measurements performed by the UE on the periodic RS. the pair of Rx beams is invalid based on: (i) the UE failing to find the pair of Rx beams to support simultaneous reception of physical downlink control channel (PDCCH) or physical downlink shared channel (PDSCH) from the first TRP and the second TRP, (ii) a signal to interference and noise ratio (SINR) of the first Rx beam or the second Rx beam being below a threshold, (iii) a reference signal received power (RSRP) of the first Rx beam or the second Rx beam being below a threshold, (iv) a combined SINR of the first Rx beam and the second Rx beam being below a threshold, or (v) a combined RSRP of the first Rx beam and the second Rx beam being below a threshold.

5. The apparatus of claim 3, wherein the event comprises a beam failure or a radio link failure of the first Rx beam or the second Rx beam.

6. The apparatus of claim 5, wherein the indication comprises a random access channel (RACH) procedure transmission of the first Rx beam or the second Rx beam. a change in a signal to interference and noise ratio (SINR) of the first Rx beam or the second Rx beam is above a threshold, or a change in a reference signal received power (RSRP) of the first Rx beam or the second Rx beam is above a threshold.

4. The apparatus of claim 3, wherein the event comprises:

8. The apparatus of claim 1, further comprising a sensor configured to detect the event.

9. The apparatus of claim 8, wherein the processing circuitry is further configured to: configure the transceiver circuitry to transmit, to the base station, a capability related to the sensor. ​ 7. The apparatus of claim 3, wherein the event comprises: ​ ​ ​ ​ 10. The apparatus of claim 8, wherein the sensor is a gyroscope and the event is a change in attitude of the UE that is above a threshold.

11. The apparatus of claim 8, wherein the sensor is an accelerometer and the event is a change in position of the UE that is above a threshold.

12. The apparatus of claim 1, wherein the event comprises: a block error rate (BLER), a decoding error, or a reception error for the one of the first Rx beam or the second Rx beam that is above a threshold without a beam failure or a link failure of the one of the first Rx beam or the second Rx beam.

13. The apparatus of claim 1, the apparatus further comprising one or more sensors configured to perform body proximity sensing (BPS), wherein the event is a detection of a body based on the BPS.

14. The apparatus of claim 13, wherein the processing circuitry is further configured to: configure transceiver circuitry to transmit, to the base station, a capability related to the BPS.

15. A processor configured to: decode, from signaling received from a base station, configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein a first receive (Rx) beam of a pair of Rx beams is used to receive a signal from a first TRP and a second Rx beam of the pair of Rx beams is used to receive a signal from a second TRP; determine that an event related to the pair of Rx beams has occurred; and configure transceiver circuitry to transmit, to the base station, an indication of the event, wherein the indication comprises: (i) an indication of a pair of transmit (Tx) beams invalid, (ii) an indication of the pair of Rx beams invalid, or (iii) an indication that one or more resource set based group beam reporting (GBBR) is to be configured for the UE.

16. An apparatus of a base station, the apparatus comprising processing circuitry configured to: configure transceiver circuitry to transmit, to a user equipment (UE), configuration information related to simultaneous reception of signals from multiple transmission and reception points (TRPs), wherein the configuration information comprises an identification of: reception (Rx) of a signal from a first TRP by the UE using a first Rx beam of a pair of Rx beams and reception of a signal from a second TRP by the UE using a second Rx beam of the pair of Rx beams; monitor for a feedback signal from the UE related to reception of the signal from the first TRP by the UE using the first Rx beam and reception of the signal from the second TRP by the UE using the second Rx beam; and configure transceiver circuitry to transmit, to the UE, updated configuration information.

17. The apparatus of claim 16, wherein the feedback signal comprises a consecutive negative acknowledgement (NACK) signal for the first Rx beam or the second Rx beam.

18. The apparatus of claim 16, wherein, When the apparatus monitors the feedback signal, the apparatus does not receive an acknowledgement (ACK) signal for one of the first Rx beam or the second Rx beam, and does not receive a beam failure or link failure indication for the one of the first Rx beam or the second Rx beam.

19. The apparatus of claim 16, wherein the updated configuration information comprises instructions for the UE to perform group-based beam reporting (GBBR) measurements and reporting using a previously configured set of resources.

20. The apparatus of claim 16, wherein the updated configuration information comprises instructions for the UE to perform group-based beam reporting (GBBR) measurements and reporting using a newly configured set of resources.

Images