UE initiated beam report for updating TCI state list

Abstract

A method performed by a user equipment for beam management is provided. The method includes receiving, from a network node, a configuration of a measurement report generated in response to a trigger condition. The configuration including information of a first set of one or more reference signals and a second set of one or more reference signals, and the trigger condition. The trigger condition using measurements of one or more of the first reference signals and one or more of the second set of reference signals. The method may also include in response to the trigger condition being fulfilled, sending a notification signal to the network node.

Description

UE INITIATED BEAM REPORT FOR UPDATING TCI STATE LISTCROSS REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 555,351 filed on February 19, 2024, titled “UE INITIATED BEAM REPORT FOR UPDATING TCI STATE LIST.”TECHNICAL FIELD

[0002] The present disclosure relates to a wireless (e.g., cellular) communications system and, more particularly, to beam management and beam reporting in a wireless communications system.BACKGROUND

[0003] Generally, in wireless network, Channel State Information (CSI) measurement configurations may be used for beam management (BM). In 5G New Radio (NR), to support beam management operation, a user equipment (UE) is configured by the network with a Channel State Information (CSI) measurement configuration e.g. IE CSI-MeasConfig received within a Radio Resource Control (RRC) Reconfiguration message. That is configured per Serving Cell (within ServingCellConfig, e.g., of a Cell), to associate a serving cell in which CSI reports are to be transmitted, e.g., Uplink (UL) channels of that serving cell. The signaling is defined in TS 38.331.

[0004] For each type of CSI report the UE needs to transmit, the network indicates an explicit list of CSI resources (also called CSI resource configuration(s)), that include a list of reference signals to be measured, such as CSI-reference signal (RS)s sets (nzp-CSI-RS- ResourceSetList, information element (IE) SEQUENCE (SIZE (l..maxNrofNZP-CSI-RS- ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetld) and / or Synchronization and signal block (SSB) sets (csi-SSB-ResourceSetList, IE SEQUENCE (SIZE (E.maxNrofCSI-SSB- ResourceSetsPerConfig)) OF CSI-SSB-ResourceSetld) for a given serving cell the UE is configured with e.g. the special cell (SpCell) of a cell group, or an secondary cell (SCell). Notice that the UE may measure CSI resources of a first serving cell and report in another serving cell.

[0005] The IE in which the CSI resource configuration(s) is provided to the UE is shown below:CSI-ResourceConfig information element- ASN1 START- TAG-CSLRESOURCECONFIG-STARTCSI-ResourceConfig ::= SEQUENCE { csi-ResourceConfigld CSI-ResourceConfigld, csi-RS-ResourceSetList CHOICE { nzp-CSI-RS-SSB SEQUENCE { nzp-CSI-RS-ResourceSetList SEQUENCE (SIZE (L.maxNrofNZP-CSLRS- ResourceSetsPerConfig)) OF NZP-CSI-RS-ResourceSetldOPTIONAL, - Need R csi-SSB-ResourceSetList SEQUENCE (SIZE (L.maxNrofCSI-SSB-ResourceSetsPerConfig)) OF CSLSSB-ResourceSetld OPTIONAL — Need R}, csi-IM-ResourceSetList SEQUENCE (SIZE (L.maxNrofCSLIM-ResourceSetsPerConfig)) OF CSLIM-ResourceSetld}, bwp-Id BWP-Id, resourceType ENUMERATED { aperiodic, semiPersi stent, periodic },}- TAG-CSI-RESOURCECONFIG-STOP- ASN1STOP

[0006] CSI resources to be measured (or resource set with one or more RSs, indicated by SSB indexes and / or CSLRS resource identifiers) are associated in the configuration to a CSI reporting configuration (CSI-ReportConfig), which configures an instance of a CSI report. A CSI report from the UE assists the network to perform beam management operations, such as the activation (and / or deactivation) of a beam to transmit data and / or control channels to the UE (or a beam switching). In 5G NR terminology, the activation of a beam may be referred as the activation of a Transmission Configuration Indication (TCI) state, which is associated to a Quasi-Co-Location (QCL) source, corresponding to a Reference Signal (RS) such as an SSB and / or CSLRS, transmitted in a spatial direction (beam) correlated to the same spatial direction (beam) in which the network may transmit a control channel (e.g., Physical Downlink Control Channel (PDCCH) and / or data channel (e.g., Physical Downlink Shared Channel (PDSCH)).

[0007] The CSI reporting configuration is used to configure a periodic or semi-persistent report sent on Physical Uplink Control Channel (PUCCH) on the serving cell in which the CSI- ReportConfig is included, or to configure a semi-persistent or aperiodic report sent on Physical Uplink Shared Channel (PUSCH) triggered by a CSI request field in Downlink Control Indication (DCI) received on the cell in which the CSI-ReportConfig is included (in this case, the cell on which the report is sent is determined by the received DCI). An example CSL ReportConfig information element may include:- ASN1 START- TAG-CSLREPORTCONFIG-STARTCSI-ReportConfig : := SEQUENCE { reportConfigld CSI-ReportConfigld, carrier ServCelllndex OPTIONAL, — Need S resourcesF orChannelMeasurement C SI-ResourceConfigld, csi-IM-ResourcesForlnterference CSI-ResourceConfigld OPTIONAL, — NeedR nzp-CSI-RS-ResourcesForlnterference CSI-ResourceConfigld OPTIONAL, —Need R reportConfigType CHOICE { periodic SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-C SLResourceLi st SEQUENCE (SIZE (L.maxNrofflWPs)) OFPUCCH-CSLResource}, semiPer si stentOnPU C CH SEQUENCE { reportSlotConfig CSI-ReportPeriodicityAndOffset, pucch-C SLResourceLi st SEQUENCE (SIZE (L.maxNrofflWPs)) OFPUCCH-CSLResource}, semiPer si stentOnPU S CH SEQUENCE { reportSlotConfig ENUMERATED {sl5, si 10, sl20, sl40, sl80, si 160,S1320}, reportSlotOffsetList SEQUENCE (SIZE (L. maxNrofUL-Allocations)) OFINTEGER(0..32), pOalpha PO-PUSCH-AlphaSetld}, aperiodic SEQUENCE { reportSlotOffsetList SEQUENCE (SIZE (L.maxNrofUL- Allocations)) OFINTEGER(0..32) reportQuantity CHOICE { none NULL, cri-RI-PMLCQI NULL, cri-RI-il NULL, cri-RI-il-CQI SEQUENCE { pdsch-Bundle SizeF orC SI ENUMERATED {n2, n4}OPTIONAL - Need S}, cri-RI-CQI NULL, cri-RSRP NULL, ssb-Index-RSRP NULL, cri-RI-LI-PMI-CQI NULL},[...] groupBasedBeamReporting CHOICE { enabled NULL, disabled SEQUENCE { nrofReportedRS ENUMERATED {nl, n2, n3, n4{OPTIONAL - Need S}},[...] csi-ReportMode-rl7 ENUMERATED {model, mode2}OPTIONAL, - Need R numberOfSingleTRP-C Si-Mode 1 -r 17 ENUMERATED {nO, nl, n2}OPTIONAL, — Need R }- TAG-CSLREPORTCONFIG-STOP- ASN1STOP

[0001] As shown above, the field reportConfigType within CSI-ReportConfig indicates to the UE the UL channel to transmit the report and the time domain behavior for reporting the CSI measurements, which may also be called beam reporting in case it includes measurements used for beam management. The configuration indicates whether the report is periodic, aperiodic or semi-persistent, and associated configurations such as periodicity.

[0002] For aperiodic CSI reporting, a UE is also configured with a list of aperiodic CSI trigger states, each associated to one or more CSI report configurations. Part of the CSI- AperiodicTriggerStateList information element defined in 3gpp TS 38.331 is shown below. If multiple reference signal (Non-zero Power Channel State Information Reference Signal (NZP CSI-RS) or SSB) resource sets are configured in a CSI resource configuration in an associated CSI report configuration, one set is selected in the corresponding trigger state. An example, CSI-AperiodicTriggerStateList information element may include:- ASN1 START- TAG-CSI-APERIODICTRIGGERSTATELIST-STARTCSI-AperiodicTriggerStateList : := SEQUENCE (SIZE (1..maxNrOfCSI-AperiodicTriggers)) OF CSI-AperiodicTriggerStateCSI-AperiodicTriggerState ::= SEQUENCE { associatedReportConfiglnfoList SEQUENCE(SIZE(1..maxNrofReportConfigPerAperiodicTrigger)) OF CSI-AssociatedReportConfiglnfo,[[ ap-CSI-MultiplexingMode-rl7 ENUMERATED {enabled} OPTIONAL - Need R]],[[ ltm-AssociatedReportConfigInfo-rl8 LTM-CSI-ReportConfigId-rl8 OPTIONAL — NeedR]]}CSI-AssociatedReportConfiglnfo ::= SEQUENCE { reportConfigld CSI-ReportConfigld, resourcesForChannel CHOICE {nzp-CSI-RS SEQUENCE { resourceSet INTEGER (1..maxNrofNZP-CSLRS-ResourceSetsPerConfig), qcl-info SEQUENCE (SIZE(1..maxNrofAP-CSI-RS-ResourcesPerSet))OF TCLStateld OPTIONAL - Cond Aperiodic}, csi-SSB-ResourceSet INTEGER (1..maxNrofCSI-SSB-ResourceSetsPerConfig)},

[0003] An aperiodic CSI report is triggered when the CSI request field in DCI indicating an aperiodic trigger state associated to the corresponding aperiodic CSI report configuration.

[0004] A Transmission Configuration Indication (TCI) state contains Quasi Co-location (QCL) information between two antenna ports. Two antenna ports are said to be QCL if certain channel parameters associated with one of the two antenna ports can be inferred from the other antenna port. An antenna port is defined by a reference signal (RS). Therefore, a TCI state is used in NR to indicate the QCL relation between a source RS and a target RS. The source RS can be one of a Non-zero Power Channel State Information Reference Signal (NZP CSLRS), tracking RS (TRS), and a Synchronization Signal Block (SSB), while the target RS can be a Demodulation Reference Signal (DMRS) for PDCCH or PDSCH, or a CSLRS.

[0005] The supported QCL information types in NR include:• 'QCL-TypeA': {Doppler shift, Doppler spread, average delay, delay spread}• 'QCL-TypeB': {Doppler shift, Doppler spread}• 'QCL-TypeC: {Doppler shift, average delay}• 'QCL-TypeD': {Spatial Rx parameter}

[0006] A list of TCI states can be RRC configured in a higher layer parameter PDSCH- Config information element (IE). For example, see 3gpp TS 38.331 section 6.3.2 for details regarding the list of TCI states. In some circumstances, up to 8 TCI states from the list can be activated with a Message Authentication Code Control Element (MAC CE). These TCI states that are activated is also called as active TCI state list.

[0007] In NR Rel-15, one TCI state is activated by a MAC CE for each TCI codepoint of a TCI field in DCI, where up to 8 TCI codepoints can be supported (see 3gpp TS 38.321 section 6.1.3.14 for details). In NR Rel-16, up to two TCI states can be activated by a MAC CE for each TCI codepoint (see 3gpp TS38.321 section 6.1.3.24). For dynamically scheduled PDSCH, one of the TCI codepoints is indicated in the TCI field of the DCI (DCI format 1 1 or DCI format 1 2) scheduling the PDSCH for PDSCH reception. For example, if a SSB or CSLRS is configured as the QCL-TypeD source RS in an activated TCI state indicated to a PDSCH, thesame receive beam (or spatial filter) for receiving the SSB or CSI-RS would be used by a UE to receive the PDSCH.

[0008] For each control resource set (CORESET), a list of TCI states can be RRC configured, one of the TCI states is activated by a MAC CE. For example, if a SSB is configured as the QCL-typeD source RS in an activated TCI state for a CORESET, the same receive beam for receiving the SSB can be used by a UE to receive PDCCHs transmitted in the CORESET.

[0009] In NR, downlink beam management is performed by conveying spatial QCL (‘Type D’) assumptions to the UE through TCI states.

[0010] In Rel-17, a unified TCI state-based beam indication framework was introduced to simplify beam management in frequency range 2 (FR2), in which a common beam represented by a TCI state may be activated / indicated to a UE and the common beam is applicable for multiple channel s / signals such as PDCCH and PDSCH. The common beam framework is also referred to a unified TCI state framework.

[0011] The new framework can be RRC configured in one of two modes of operation, i.e.,“Joint DL / UL TCI” or “Separate DL / UL TCI”. For “Joint DL / UL TCI”, one common Joint TCI state is used for both DL and UL signals / channels. For “Separate DL / UL TCI”, one common DL-only TCI state is used for DL channel s / signals and one common UL-only TCI state is used for UL signals / channels. A TCI state configured under the newly introduced Rel- 17 framework will henceforth be referred to as a unified TCI state.

[0012] A unified TCI state for DL or joint DL and UL comprises identifiers of two QCL source reference signals as shown below, where the first RS is a QCL source RS for one of {typeA, typeB, typeC} QCL types, while the second RS is a QCL source RS for QCL typeD. The second RS is used to indicate a spatial beam or filter associated with the unified TCI state.DLorJoint-TCIState-rl7 ::= SEQUENCE { tci- StateUnifiedld-r 17 DLorJoint-TCIState-Id-rl7, tci-StateType-rl7 ENUMERATED {DLOnly, JointULDL}, qcl-Typel-rl7 QCL-Info, qcl-Type2-rl7 QCL-Info OPTIONAL - Need R}QCL-Info ::= SEQUENCE { cell ServCelllndex OPTIONAL, - Need R bwp-Id BWP-Id OPTIONAL, - Cond CSLRS-Indicated referencesignal CHOICE { csi-rs NZP-CSI-RS-Resourceld, ssb SSB -Index},qcl-Type ENUMERATED {typeA, typeB, typeC, typeD},

[0013] A unified TCI state can be updated with one of two alternatives:• Two-stage: RRC signaling is used to configure a number of unified TCI states in higher layer parameter PDSCH-config, and a MAC-CE is used to activate one of the configured unified TCI states.• Three-stage: RRC signaling is used to configure a number of unified TCI states in PDSCH- config, a MAC-CE is used to activate up to 8 unified TCI states, and a 3 -bit TCI state bitfield in DCI is used to indicate one of the activate unified TCI states.

[0014] The one activated or indicated unified TCI state may be used in subsequent PDCCH, PDSCH, and NZP CSI-RS transmissions until a new unified TCI state is activated or indicated.

[0015] The existing DCI formats 1 1 and 1 2 are reused for beam indication (i.e., TCI state indication / update), both with and without DL assignment.

[0016] For DCI-based beam indication, the first slot to apply the indicated TCI is at least Y symbols after the last symbol of the acknowledgment of the joint or separate DL / UL beam indication. The Y symbols are configured by the gNB based on UE capability, which is also reported in units of symbols.

[0017] The gNB can use DCI format 1 1 or 1 2 to indicate to the UE that it may use one of the activated TCI states for the subsequent PDSCH reception. The field being used in the DCI is Transmission configuration indication, which is 3 bits if tci-PresentlnDCI is “enabled” or tci-PresentForDCI-Formatl-2-rl6 is present respectively for DCI format 1 1 and DCI 1 2 by higher layer. One example of such a DCI indication may include have eightslots, each with a different TCI state. The DCI indication may include a number that indicates a slot. For example, DCI code point 0 indicates the first TCI state index in the list of TCI states, DCI code point 1 indicates the second TCI state index in the list, and so on.

[0018] The subject matter claimed in the present disclosure is not limited to embodiments that solve any disadvantages or that operate only in environments such as those described above. Rather, this background is only provided to illustrate one example technology area where some embodiments described in the present disclosure may be practiced.SUMMARY

[0019] This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential characteristics of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.

[0020] Various computer-implemented systems, methods, and articles of manufacture for beam management and beam reporting in a wireless communications system are described herein.

[0021] In some embodiments, a method performed by a user equipment for beam management is provided. The method includes receiving, from a network node, a configuration of a measurement report generated in response to a trigger condition. The configuration including information of a first set of one or more reference signals and a second set of one or more reference signals, and the trigger condition. The trigger condition using measurements of one or more of the first reference signals and one or more of the second set of reference signals. The method may also include in response to the trigger condition being fulfilled, sending a notification signal to the network node.

[0022] In some embodiments, a method performed by a network node for beam management is provided. The method includes sending, to a user equipment, a configuration of a measurement report generated in response to a trigger condition. The configuration including information of a first set of one or more reference signals and a second set of one or more reference signals, and the trigger condition. The trigger condition using measurements of one or more of the first reference signals and one or more of the second set of reference signals. The method also includes in response to the trigger condition being fulfilled, receiving, from the user equipment, a notification signal

[0023] The object and advantages of the embodiments will be realized and achieved at least by the elements, features, and combinations particularly pointed out in the claims. Both the foregoing general description and the following detailed description are exemplary and explanatory and are not restrictive.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

[0025] Figure 1 is a flow chart that illustrates a process performed by a User Equipment (UE) for beam management, in accordance with one embodiment of the present disclosure;

[0026] Figure 2 is a flow chart that illustrates a process performed by a network node for beam management, in accordance with one embodiment of the present disclosure;

[0027] Figure 3 shows an example of a communication system in accordance with some embodiments of the present disclosure;

[0028] Figure 4 shows a UE in accordance with some embodiments of the present disclosure;

[0029] Figure 5 shows a network node in accordance with some embodiments of the present disclosure; and

[0030] Figure 6 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments of the present disclosure may be virtualized.DETAILED DESCRIPTION

[0031] The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure.

[0032] Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise:

[0033] The phrase “In some embodiment” as used herein does not necessarily refer to the same embodiment, though it may. Thus, as described below, various embodiments of the invention may be readily combined, without departing from the scope of the invention.

[0034] As used herein, the term “or” is an inclusive “or” operator and is equivalent to the term “and / or,” unless the context clearly dictates otherwise.

[0035] The term “based on” is not exclusive and allows for being based on additional factors not described unless the context clearly dictates otherwise.

[0036] As used herein, and unless the context dictates otherwise, the term “coupled to” is intended to include both direct coupling (in which two elements that are coupled to each other contact each other) and indirect coupling (in which at least one additional element is located between the two elements). Therefore, the terms “coupled to” and “coupled with” are usedsynonymously. Within the context of a networked environment where two or more components or devices are able to exchange data, the terms “coupled to” and “coupled with” are also used to mean “communicatively coupled with”, possibly via one or more intermediary devices.

[0037] In addition, throughout the specification, the meaning of “a”, “an”, and “the” includes plural references, and the meaning of “in” includes “in” and “on”.

[0038] Although some of the various embodiments presented herein constitute a single combination of inventive elements, it should be appreciated that the inventive subject matter is considered to include all possible combinations of the disclosed elements. As such, if one embodiment comprises elements A, B, and C, and another embodiment comprises elements B and D, then the inventive subject matter is also considered to include other remaining combinations of A, B, C, or D, even if not explicitly discussed herein. Further, the transitional term “comprising” means to have as parts or members, or to be those parts or members. As used herein, the transitional term “comprising” is inclusive or open-ended and does not exclude additional, unrecited elements or method steps.

[0039] It is noted that description herein is not intended as an extensive overview, and as such, concepts may be simplified in the interests of clarity and brevity. Any process or method or corresponding steps of any process or method described in this application may be performed in any order and may omit any of the steps in the process. Processes or methods may also be combined with other processes or steps of other processes, in part or in whole. Parts of processes or methods, or corresponding steps may be combined with other parts of processes or methods, or corresponding steps.

[0040] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0041] Previously, the CSVbeam reporting is always network (NW)-initiated. The NW explicitly requests a certain report from the UE, by including a pointer to a certain CSI- ReportConfig in DCI. In the 3GPP Release 19 Work Item Description (WID) for MIMO (Multiple Input Multiple Output), the following objective is included: Specify enhancement to facilitate UE-initiated / event-driven beam management for reducing overhead and / or latency, assuming the unified TCI while leveraging (as much as possible) legacy CSI measurement and reporting configuration frameworks, targeting FR2 and sTRP with intra- and inter-cell beam management: a. UL signaling content(s) (and procedure(s) as required) for UE-initiated / event- driven beam reporting facilitating fast beam switching.b. UL signaling medium / container considering the UE-initiated / event-driven nature of the UL transmission, designed primarily for the purpose of beam reporting.

[0042] This objective would imply that it is the UE that initiates the event-driven beam reporting. However, there currently exist certain challenge(s). In a NW, the beam with which UE is connected to the NW is controlled by the NW node and the beam selection at the NW may depend on the CSI reports from the UE. Currently, the type of CSI reports supported in network nodes are periodic, semi-persistent or aperiodic report. In a multi-beam scenario, unless periodic / semi-persistent reporting is configured, NW may not know the best beam in timely manner. However, periodic, or semi-persistent CSI report may come with high UL reporting overhead. Aperiodic reports may result in the network having to request the report in a proper timing to prevent beam failures and possibly a Radio Link Failure and reduce UL reporting overhead and UE energy consumption.

[0043] In a multi-beam scenario, a mechanism is needed to reduce the UL signaling overhead without compromising beam management performance such as beam switching in a timely manner and updating the active TCI state list so that a NW can trigger the beam switch among the activated TCI states in a timely manner.

[0044] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. The disclosure is directed to a method at a UE, in which the UE triggers the transmission of a CSI report upon fulfillment of a triggering condition. When evaluating the triggering condition, the UE takes the activation status of the TCI states (e.g. being or not being in the active TCI state list and / or having the “indicated” TCI state among active TCI states) into account to determine which beam(s) or RS in a resource configuration are to be used as input to the evaluation of the triggering condition of the event and the report.

[0045] In some embodiments, the UE triggers the report when the measurements (e.g., beam level reference signal received power (LI- RSRP)) of at least one beam (or RS) which are configured for CSI measurements (e.g. in resource configuration) but are not associated with the active TCI state list become offset better than at least one beam (or RS) that are associated with the active TCI state list.

[0046] In some embodiments, the UE triggers the report when the measurements (e.g., Ll- RSRP) of at least one beam (or RS) which are configured for CSI measurements (e.g., in resource configuration) and are in the activate TCI list becomes offset better than serving beam (i.e., the beam or RS in the active TCI list which is indicated to be activated TCI state of the serving cell). In one example, both beams which are being compared are in the active TCI state list.

[0047] In some embodiments, the disclosure provides a method performed by a UE that is configured with more than one RS for CSI measurement, the method may include triggering the transmission of a UE initiated or event driven CSI measurement report upon fulfillment of a triggering condition. The triggering condition may include a measurement (e.g., Ll-RSRP) of one or more beams, which are configured for CSI measurement but are not in the activated TCI state list, becoming offset better than beams in the active TCI state list. The method may also include transmitting the UE initiated or event driven CSI measurement report. In some embodiments, the method may further include in response to sending the CSI report, receiving a command indicating the switching of the TCI state or update of the active TCI state list.

[0048] Certain embodiments may provide one or more of the following technical advantage(s). For example, one advantage of the method may include savings in terms of UE power consumption and UL resources on the network side because unnecessary transmissions, as in periodic reports, would not be performed based on the UE only transmitting the CSI report when the condition is fulfilled and not at some predefined interval. Thus, the concepts provided in this disclosure may improve power consumption and network resources.

[0049] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0050] The disclosure describes methods in the UE to trigger the transmission of UE initiated or event triggered CSI report. The reporting will be used to perform beam management. Beam management involves performing activation of a set of TCI states, and subsequently indicating one of the activated TCI states to the UE. The activated TCI states are sometimes called active TCI states. The active TCI states are collected in an active TCI state list. A beam is linked / associated to a TCI state or a RS. In the context of this disclosure beam, RS, and TCI state may be used interchangeably.

[0051] The NW activates TCI states by sending a TCI state activation command to the UE.After the reception of the TCI state activation command, the UE activates the TCI states. Sometimes, the TCI state activation command is sent using a MAC CE, e.g., the Unified TCI States Activation / Deactivation MAC CE. Sometimes, the TCI state activation command is sent using a DCI.

[0052] The NW may subsequently indicate one of the activated TCI states, by sending an TCI state indication to the UE. After the TCI state indication has been processed by the UE, the NW can communicate with the UE using the properties, e.g., the beam, associated with the TCI state. Sometimes, the indicated TCI state will be referred to as the serving beam. In otherwords, the UE assumes that signals received using the indicated TCI state are transmitted by the serving beam.

[0053] Sometimes, TCI state activation (e.g., active TCI state list) and indication are performed at the same time. For example, if the active TCI state list only contains a single TCI state, that TCI state is immediately indicated. In the context of this disclosure, active TCI list and activated TCI state list are used interchangeably. In the context of this disclosure, indicated TCI state, activated TCI state, serving beam, and active TCI state are used interchangeably.

[0054] The disclosure describes a method at a UE in which the UE triggers the transmission of UE initiated or event triggered CSI report upon fulfillment of a triggering condition, wherein the triggering condition includes measurement (e.g., Ll-RSRP) of beams which are configured for CSI measurement but are not in the active TCI state list and at least one of the beams that are not in the active TCI state list becomes offset better than one or more of the beams in the active TCI state list. The method may further include one or more of following steps: sending an indication to a NW node indicating that an event or trigger condition mentioned above is met, receiving a request for transmission of measurement report / Receiving UL grant for transmission of measurement report, and transmitting a UE initiated or event triggered CSI report.

[0055] In response to the UE initiated or event triggered CSI report, the UE may receive a command indicating a TCI state switching or UE receives a MAC CE command to update TCI states (e.g., addition or modification or deletion of TCI states in the activated TCI state list) based on the report.

[0056] In some embodiments, the UE evaluates the triggering conditions per serving cell. For example, in a resource configuration associated to the reporting configuration in which the report is configured, the UE is configured with one or more beam(s) / RSs of one or more serving cell(s) (e.g., serving cell here may refer to physical cell identifier (ID) in the context of multiinput multi-output (MIMO) multi-TRP). However, the event compares beams / RSs of the same serving cell (PCI).

[0057] In some embodiments, the UE evaluates the triggering conditions comparing beams of different serving cells. For example, in a resource configuration associated to the reporting configuration in which the report is configured, the UE is configured with one or more beam(s) / RSs of one or more serving cell(s) e.g., serving cell here may refer to physical cell ID in the context of MIMO multi-target rating point (TRP)) so that the comparison of beam(s) / RSs can be for different cells (e.g., Physical cell ID).

[0058] In some embodiments, the UE triggers UE initiated or event triggered CSI report when, for a serving cell, the quality of at least one RS or beam (e.g., SSB or CSI-RS) configured for CSI report but are not in the active TCI state list becomes offset better than the quality of at least one beam or RS that are configured for CSI report and are in the active TCI state list indicated to the UE. For example, the event is triggered when the beam or RS (e.g., SSB or CSI-RS) of the serving cell with the strongest measurement (e.g. strongest LI RSRP), configured for CSI report (e.g. in a resource configuration associated to the reporting configuration in which the report is configured) but are not in the active TCI state list, becomes an offset better than any beam or RS that are configured for CSI report and are in the active TCI state list indicated to the UE.

[0059] In some embodiments, the RS or beams in the activated / active TCI state list are not configured in the CSI report.

[0060] When the event is triggered, the UE transmits a CSI report and includes in the report information about the one or more beams which have triggered the event or report (i.e., the associated L1-RSRP / L1-SINR are offset better than at least one beam’s associated Ll- RSRP in the activated TCI state list), such as information about at least one beam which is not in the active TCI state list (which has triggered the report) and information about at least one beam which is in the active TCI state list (which has triggered the report).

[0061] The quality of a beam or RS is determined by a measurement on the RS. The measurement quantity can be, e.g., Ll-RSRP, Ll-SINR.

[0062] The report aims to indicate to the network, for example, that there is a beam or RS of the serving cell, which is currently not part of the active TCI state list and has better quality than one or more beams or RSs that are currently in the active TCI state list. This would serve as an indication to the NW to update the active TCI state list by including the reported beam or RS. For the beams corresponding to the active TCI state list, UE is supposed to perform beam switching in short time (e.g., within beamAppTime) as UE is supposed to track and maintain the relevant parameters such as QCL and spatial domain parameters for the faster TCI state switching.

[0063] If multiple beams of the serving cell are reported and their associated L 1 -RSRP / L 1 -SINR are offset better than a beam in the activated TCI state list, the beam can be removed / deleted from the list and one or more of the multiple beams can be added / activated to the list. For this purpose, information of LI -RSRP / L 1 -SINR for the multiple beams is also included in the report. If a beam of the serving cell is reported and its associated LI -RSRP / L 1- SINR is offset better than multiple beams in the activated TCI state list, the beam can beadded / activated to the list and one or more of the multiple beams can be removed / deleted from the list. For this purpose, information of L1-RSRP / L1-SINR for the multiple beams is also included in the report.

[0064] In some embodiments, if the NW node configures UE with 8 beams (e.g., SSBO, SSB1, ..SSB7 of a serving cell in CSI resource configuration) for the CSI measurement report, based on the initial measurement reports, NW may indicate 4 beams or RS or TCI states (e.g., SSB 0, SSB 1, SSB2, SSB3) to the UE in the form of activeTCI state list and among the 4 TCI states in the active TCI state list, NW may indicate the TCI state (e.g., SSBO) for the DL / UL data reception / transmission. After some time if the UE observes other TCI states that are not in the active TCI state list (e.g., SSB4, SSB5) becomes offset better than the threshold, then UE may send the CSI report at least including the beam measurement results of SSB4, SSB5. Based on the CSI report, NW may update the active TCI state list by adding another TCI state to the active TCI state list (e.g., new active TCI state list is SSB 0, SSB1, SSB 2, SSB3, SSB4) or modify the TCI state list by adding one or more of TCI state and remove one or more of TCI state (e.g., SSB1, SSB2, SSb3, SSB4).

[0065] In some embodiments, the UE triggers UE initiated, or event triggered CSI report when, for a serving cell, the quality of the serving beam or RS (e.g., SSB or CSI-RS) becomes offset worse than one or more beams or RSs associated with the active TCI state list. The serving beam may also be called the indicated TCI state and / or the beam associated to the indicated TCI state from the list. In response to the report, the UE may receive (from the network) a command which indicates a change of the indicated TCI state or serving beam or the active TCI state. This may be received since the quality of the serving beam or RSs is now worse than one of the beams or RSs in the active TCI state list.

[0066] When the event is triggered, the UE transmits a CSI report and includes in the report information about the one or more beams which have triggered the report, such as information about at least one beam which is in the active TCI state list, but it is not the serving beam or “indicated TCI state” and / or information about at least one beam which is in the active TCI state list and is the serving beam or “indicated TCI state”. The so called “indicated TCI state” in this context, is the TCI state in the active TCI state list which is indicated to be activated (i.e. associated with the serving beam).

[0067] In some embodiments, the UE may receive an RRC message for configuring one or more parameter associated to the event defined as above. The RRC message (e.g. RRC Reconfiguration) may include a reporting configuration (e.g. CSI-ReportConfig) and an associated resource configuration (e.g. CSI-ResourceConfig).

[0068] The reporting configuration may indicate an identifier (e.g., event ID, reportConfigID) so that when the UE receives the configuration the UE determines that the configuration is for the event whose triggering condition is defined in the above set of embodiments.

[0069] The reporting configuration may indicate an identifier of a resource configuration (e.g., CSI-ReportConfigld, included in the reporting configuration), which indicates one or more SSB(s) or CSI-RS to be considered as input for the condition associated to the event. Thus, the UE determines the SSB(s) or CSI-RS within the resource configuration to be considered as input to the event(s).

[0070] In some embodiments the reporting configuration may indicate two different set of beams to be considered as input to the event. One set of beams may be mentioned in the reporting configuration of the event (e.g., RRC config) and other set of beams may be mentioned in the configuration or UE determines based on the event description or type.

[0071] Few examples of such configuration are mentioned below.

[0072] Example 1:Event Name{Offset value of the offsetResource setl C Si-Configuration IDResource set2 active TCI state list}

[0073] In this example 1, UE compares the beams in Resource setl with beams in Resource set2 and when Resource setl becomes offset better than beams in Resource set2, UE triggers the UE initiated beam report.

[0074] Example 2:Event Name{Offset value of the offsetResource setl C Si-Configuration ID}

[0075] In this example 2, UE compares the beams in Resource setl with beams in the active TCI state list and when beams in Resource setl becomes offset better than beams in active TCI state list, UE triggers the UE initiated beam report.

[0076] Example 3:Event Name{Offset value of the offset}

[0077] In this example, UE compares all the beams configured for CSI report with beams in the active TCI state list and when any beam configured for a CSI report becomes offset better than beams in active TCI state list, UE triggers the UE initiated beam report.UE initiated CSI report associated with an Event.

[0078] In some embodiments, the UE transmits a CSI report when a triggering condition is fulfilled i.e. above said condition is met. In these and other embodiments, the UE includes one or more of the following in the UE initiated CSI report.

[0079] Information about an SSBs or CSI-RSs which has triggered the event (e.g. so-called triggered SSB) such as:• Measurement quantities, e.g., Ll-RSRP or Ll-SINR• Differential measurement quantity, e.g., differential LI RSRP or differential Ll-SINR. (e.g. relative to a reference value• An SSB identifier e.g. SS / PBCH Block Resource indicator (SSBRI)• A CSLRS identifier, e.g., CSI-RS resource indicator (CRI),

[0080] Information about other measurements the UE performed, i.e., measurements on SSB or CSI-RS that did not trigger the event. This information may include:• Measurement quantities, e.g., Ll-RSRP or Ll-SINR• Differential measurement quantity, e.g., differential LI RSRP or differential Ll-SINR. (e.g. relative to a reference value• An SSB identifier e.g. SS / PBCH Block Resource indicator (SSBRI)• A CSI-RS identifier, e.g., CSI-RS resource indicator (CRI), Report config ID

[0081] In these and other embodiments, the UE transmits the UE initiated CSI report e.g., by transmitting a MAC Control Element, and / or a report over PUSCH and / or PUCCH.

[0082] In various embodiments, it is described that a measurement becomes an offset better than another measurement.

[0083] In that context, a measurement may be associated to a measurement quantity, such as one of the following:• LI Reference Signal Received Power (Ll-RSRP)• LI Reference Signal Received Quality (Ll-RSRQ)• LI Signal-to-noise and Interference Ratio (Ll-SINR)

[0084] The measurement quantity may be associated to a parameter in the reporting configuration, which configures the event.

[0085] In some embodiments, the measurement is LI filtered. For example, in the case the measurement is an RSRP, this may be a LI filtered RSRP (Ll-RSRP) which is used as input to the event. In some examples, the filtering may be a linear averaging over a last N samples. In some examples it may be a weighted averaging with filter coefficients configured.

[0086] In the context of this disclosure, a first measurement becoming an offset better than a second measurement may be expressed as follows: First measurement > Second measurement + Offset

[0087] The variables in the formula are defined as follows: First measurement is the measurement result of the beam / RS configured for CSI report, not taking into account any offsets. Second measurement is the measurement result of the beam / RS configured for CSI report, not taking into account any offsets. Offset is the offset parameter for this event (e.g. defined within the reporting configuration for UE initiated beam reporting). The First measurement and the second measurement are expressed in dBm in case of RSRP, or in dB in case of RSRQ and RS-SINR.

[0088] One example of the filter is given below. In the below example, measl is a first measurement and meas2 is a second measurement.

[0089] N value may be configured by NW or fixed in the specification, measl (n) refers to measurement taken at measurement occasion n and measl (n-1) refers to measurement taken at measurement occasion n-1, and so on.

[0090] Another example of the filter is given below. In the below example, measl is first measurement and meas2 is second measurement. measl (n)= fil * measl (n) + / ?2 * measl (n — 1) meas2 (n)= ?1 * meas2 (n) + ?2 * meas2 (n — 1)

[0091] Where pi and P2 may be configured by NW explicitly or implicitly. In some examples pi is derived from P2 or vice-versa and pi is configured by the NW or specified in the spec as a fixed value.

[0092] FIG. 1 illustrates a flowchart of an example method 100 for beam management. The method 100 may be arranged in accordance with at least one embodiment described in the present disclosure. One or more operations of the method 100 may be implemented by a UE such as the UE 312A or 312B of Figure 3, or the UE 400 of Figure 4. In these and other embodiments, the method 100 may be performed based on the execution of instructions stored on one or more non-transitory computer-readable media. Although illustrated as discrete blocks, various blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation.

[0093] The method 100 may begin at block 102 and includes receiving, from a network node, a configuration of a measurement report generated in response to a trigger condition. The configuration includes information of: a first set of reference signals and a second set of signals, and the trigger condition. The trigger condition being evaluated using measurements of the first set of reference signals and the second set of reference signals. In some embodiments, each of the first set of reference signals and the second set of reference signals includes one or more reference signals.

[0094] In some embodiments, each of the first set of reference signals and each of the second set of reference signals represents a different beam and are each associated with a transmission configuration indication (TCI) state. In these and other embodiments, each TCI state includes information of an associated reference signal from the first set of reference signals and the second set of reference signals.

[0095] In some embodiments, the first set of reference signals are associated with a set of inactive TCI states or beams. In these and other embodiments, each of the second set of reference signals are associated with an activated TCI state or activated beam and each of the activated TCI states is configured to be dynamically indicated by the network node for communication between the network node and the user equipment. For example, each of the activated TCI states can be dynamically indicated by the network node for communication between the network node and the user equipment.

[0096] In these and other embodiments, one of the second set of reference signals is associated with an indicated TCI state or a current beam. In these and other embodiments, the indicated TCI state is one of the activated TCI states currently indicated by the network node for communication between the network node and the user equipment.

[0097] In some embodiments, the measurement of the first set of reference signals and the second set of reference signals includes computing, for each of the measured signals, a received signal quality. In some embodiments, the received signal quality may be a reference signalreceived power (RSRP) in dBm, a signal -to-noise and interference ratio ( SINR) in dB, a Layer 1 Reference Signal Received Power, LI -RSRP, in dBm or Layer 1 Signal -to-Interference-plus- Noise Ratio, Ll-SINR in dB.

[0098] At block 104, in response to the trigger condition being fulfilled, sending a notification signal to the network node. In some embodiments, sending the notification signal is determined by the user equipment based on the trigger condition. In these and other embodiments, the notification signal is not sent in response to a command from the network node to the user equipment to send the notification signal. In some embodiments, the notification signal indicates that the trigger condition is fulfilled.

[0099] In some embodiments, the trigger condition is fulfilled in response to a difference between a measurement of a first reference signal in the first set of reference signals and a measurement of a second reference signal in the second set of reference signals satisfying a threshold value. For example, the measurement of the first reference signal may be x, the measurement of the second reference signal may be y, and the threshold value may be z, such that the threshold is satisfied when x - y > z, where z is a positive value in dB. In these and other embodiments, the second reference signal is associated with a current beam or an indicated TCI state.

[0100] At block 106, in response to sending the notification signal, receiving, from the network node, a request for the measurement report. In some embodiments, the network node may generate the measurement report. In these and other embodiments, the measurement report includes information of the one or more of the first reference signals and the one or more of the second set of reference signals. In these and other embodiments, the information includes a received signal power or signal quality of the one or more of the first reference signals and the one or more of the second set of reference signals. In some embodiments, the request is a CSI request signaled in a DCI format.

[0101] At block 108, sending the measurement report to the network node. In some embodiments, the measurement report includes information of at least the first reference signal and the second reference signal. Alternately or additionally, the information further includes a received signal quality of the first reference signal and a received signal quality of the second reference signal.

[0102] At block 110, in response to sending the measurement report, receiving, from the network node, a TCI activation command indicating new activated TCI states. In some embodiments, the TCI activation command results in an activated TCI state associated with thesecond reference signal being deactivated and a non-activated TCI state associated with the first reference signal being activated.

[0103] It is understood that, for this and other processes, operations, and methods disclosed herein, the functions and / or operations performed may be implemented in differing order. Furthermore, the outlined functions and operations are only provided as examples, and some of the functions and operations may be optional, combined into fewer functions and operations, or expanded into additional functions and operations without detracting from the essence of the disclosed embodiments.

[0001] Figure 2 illustrates an example method 200 that may be performed by a network node for beam management, in accordance with one or more embodiments of the present disclosure. One or more operations of the method 200 may be implemented by a network node such as the network nodes 310A or 310B of Figure 3, or the network node 500 of Figure 5. In these and other embodiments, the method 200 may be performed based on the execution of instructions stored on one or more non-transitory computer-readable media. Although illustrated as discrete blocks, various blocks may be divided into additional blocks, combined into fewer blocks, or eliminated, depending on the desired implementation.

[0002] Furthermore, note that this process is complementary to the process performed by the UE described above, e.g., with respect to Figure 1. As such, details above provided in relation to Figures 1 are equally applicable to Figure 2.

[0104] The method 200 may begin at block 202 and include sending, to a user equipment, a configuration of a measurement report generated in response to a trigger condition, the configuration including information of a first set of reference signals, a second set of reference signals, and the trigger condition. In some embodiments, the trigger condition is evaluated using measurements of the first set of reference signals and the second set of reference signals. In some embodiments, each of the first set of reference signals and each of the second set of reference signals represents a different beam and are each associated with a transmission configuration indication (TCI) state. In some embodiments, each TCI state includes information of an associated reference signal from the first set of reference signals and the second set of reference signals. In some embodiments, each of the first set of reference signals and the second set of reference signals includes one or more reference signals.

[0105] In some embodiments, the first set of reference signals are associated with a set of inactive TCI states or beams. In these and other embodiments, each of the second set of reference signals are associated with an activated TCI state or activated beam and each of the activated TCI states is configured to be dynamically indicated by the network node forcommunication between the network node and the user equipment. For example, each of the activated TCI states can be dynamically indicated by the network node for communication between the network node and the user equipment.

[0106] In these and other embodiments, one of the second set of reference signals is associated with an indicated TCI state or a current beam, where the indicated TCI state is one of the activated TCI states currently indicated by the network node for communication between the network node and the user equipment.

[0107] In some embodiments, the measurement of the first set of reference signals and the second set of reference signals includes computing, for each of the measured signals, a received signal quality. In some embodiments, the received signal quality may be a reference signal received power (RSRP) in dBm, a signal -to-noise and interference ratio ( SINR) in dB, a Layer 1 Reference Signal Received Power, LI -RSRP, in dBm, or a Layer 1 Signal -to-Interference- plus-Noise Ratio, LI -SINR in dB.

[0108]

[0109] At block 204, in response to the trigger condition being fulfilled, receiving, from the user equipment, a notification signal. In some embodiments, the notification signal is sent by the user equipment to the network node as determined by the user equipment in response to the trigger condition. In these and other embodiments, the network node does not request the notification signal from the user equipment.

[0110] In some embodiments, the trigger condition is fulfilled in response to a difference between a measurement of a first reference signal in the first set of reference signals and a measurement of a second reference signal in the second set of reference signals satisfying a threshold value. For example, the measurement of the first reference signal may be x, the measurement of the second reference signal may be y, and the threshold value may be z, such that the threshold is satisfied when x - y > z, where z is a positive value in dB. In some embodiments, the second reference signal is associated with a current beam or an indicated TCI state. At block 206, after receiving the notification signal, sending, to the user equipment, a request for the measurement report. In some embodiments, the request is a CSI request signaled in a DCI format.[OHl] At block 208, receiving, from the user equipment, the measurement report. In some embodiments, the measurement report includes information of the first reference signal and the second reference signal. In some embodiments, the information includes a signal quality of the first reference signal and the second reference signal.

[0112] At block 210, in response to receiving the measurement report, sending, to the user equipment, a TCI activation command indicating new activated TCI states. In some embodiments, the TCI activation command results in an activated TCI state associated with one of the second set of reference signals being deactivated and a non-activated TCI state associated with one of the first set of reference signals being activated.

[0113] Figure 3 shows an example of a communication system 300 in which embodiments of the present disclosure may be implemented. In the example, the communication system 300 includes a telecommunication network 302 that includes an access network 304, such as a Radio Access Network (RAN), and a core network 306, which includes one or more core network nodes 308. The access network 304 includes one or more access network nodes, such as network nodes 310A and 310B (one or more of which may be generally referred to as network nodes 310), or any other similar Third Generation Partnership Project (3GPP) access nodes or non-3GPP Access Points (APs). Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 302 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 302 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 302, including one or more network nodes 310 and / or core network nodes 308.

[0114] Examples of an ORAN network node include an Open Radio Unit (O-RU), an Open Distributed Unit (O-DU), an Open Central Unit (O-CU), including an O-CU Control Plane (O-CU-CP) or an O-CU User Plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or morenetwork functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 310 facilitate direct or indirect connection of User Equipment (UE), such as by connecting UEs 312A, 312B, 312C, and 312D (one or more of which may be generally referred to as UEs 312) to the core network 306 over one or more wireless connections.

[0115] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 300 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 300 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0116] The UEs 312 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 310 and other communication devices. Similarly, the network nodes 310 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 312 and / or with other network nodes or equipment in the telecommunication network 302 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 302.

[0117] Note that the functionality of the network node or gNB described above (e.g., with respect to Figures 9-14) may be implemented in any one of the network nodes 310, and the functionality of the UE described above (e.g., with respect to Figures 9-14) may be implemented in any one of the UEs 312. In this regard, the network node 310 may be a rnulti- TRP network node (e.g., a gNB having multiple TRPs).

[0118] In the depicted example, the core network 306 connects the network nodes 310 to one or more hosts, such as host 316. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 306 includes one more core network nodes (e.g., core network node 308) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to thecorresponding components of the core network node 308. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-Concealing Function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0119] The host 316 may be under the ownership or control of a service provider other than an operator or provider of the access network 304 and / or the telecommunication network 302, and may be operated by the service provider or on behalf of the service provider. The host 316 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0120] As a whole, the communication system 300 of Figure 3 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system 300 may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable Second, Third, Fourth, or Fifth Generation (2G, 3G, 4G, or 5G) standards, or any applicable future generation standard (e.g., Sixth Generation (6G)); Wireless Local Area Network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any Low Power Wide Area Network (LPWAN) standards such as LoRa and Sigfox.

[0121] In some examples, the telecommunication network 302 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunication network 302 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 302. For example, the telecommunication network 302 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing enhanced Mobile Broadband (eMBB) services to other UEs, and / ormassive Machine Type Communication (mMTC) / massive Internet of Things (loT) services to yet further UEs.

[0122] In some examples, the UEs 312 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 304 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 304. Additionally, a UE may be configured for operating in single- or multi -Radio Access Technology (RAT) or multi-standard mode. For example, a UE may operate with any one or combination of WiFi, New Radio (NR), and LTE, i.e. being configured for Multi -Radio Dual Connectivity (MR- DC), such as Evolved UMTS Terrestrial RAN (E-UTRAN) NR - Dual Connectivity (EN-DC).

[0123] In the example, a hub 314 communicates with the access network 304 to facilitate indirect communication between one or more UEs (e.g., UE 312C and / or 312D) and network nodes (e.g., network node 310B). In some examples, the hub 314 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 314 may be a broadband router enabling access to the core network 306 for the UEs. As another example, the hub 314 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 310, or by executable code, script, process, or other instructions in the hub 314. As another example, the hub 314 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 314 may be a content source. For example, for a UE that is a Virtual Reality (VR) headset, display, loudspeaker or other media delivery device, the hub 314 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 314 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 314 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0124] The hub 314 may have a constant / persistent or intermittent connection to the network node 310B. The hub 314 may also allow for a different communication scheme and / or schedule between the hub 314 and UEs (e.g., UE 312C and / or 312D), and between the hub 314 and the core network 306. In other examples, the hub 314 is connected to the core network 306 and / or one or more UEs via a wired connection. Moreover, the hub 314 may be configured to connect to a Machine-to-Machine (M2M) service provider over the access network 304 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wirelessconnection with the network nodes 310 while still connected via the hub 314 via a wired or wireless connection. In some embodiments, the hub 314 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 310B. In other embodiments, the hub 314 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and the network node 310B, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0125] Figure 4 shows a UE 400 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged, and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, Voice over Internet Protocol (VoIP) phone, wireless local loop phone, desktop computer, Personal Digital Assistant (PDA), wireless camera, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, Laptop Embedded Equipment (LEE), Laptop Mounted Equipment (LME), smart device, wireless Customer Premise Equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3 GPP, including a Narrowband Internet of Things (NB-IoT) UE, a Machine Type Communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0126] A UE may support Device-to-Device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), Vehicle-to-Vehicle (V2V), Vehicle-to-Infrastructure (V2I), or Vehicle-to-Everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0127] The UE 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input / output interface 406, a power source 408, memory 410, a communication interface 412, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 4. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may containmultiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0128] The processing circuitry 402 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 410. The processing circuitry 402 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, Field Programmable Gate Arrays (FPGAs), Application Specific Integrated Circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 402 may include multiple Central Processing Units (CPUs).

[0129] In the example, the input / output interface 406 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 400. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0130] In some embodiments, the power source 408 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 408 may further include power circuitry for delivering power from the power source 408 itself, and / or an external power source, to the various parts of the UE 400 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 408. Power circuitry may perform any formatting, converting, or othermodification to the power from the power source 408 to make the power suitable for the respective components of the UE 400 to which power is supplied.

[0131] The memory 410 may be or be configured to include memory such as Random Access Memory (RAM), Read Only Memory (ROM), Programmable ROM (PROM), Erasable PROM (EPROM), Electrically EPROM (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 410 includes one or more application programs 414, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 416. The memory 410 may store, for use by the UE 400, any of a variety of various operating systems or combinations of operating systems.

[0132] The memory 410 may be configured to include a number of physical drive units, such as Redundant Array of Independent Disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, High Density Digital Versatile Disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, Holographic Digital Data Storage (HDDS) optical disc drive, external mini Dual In-line Memory Module (DIMM), Synchronous Dynamic RAM (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a tamper resistant module in the form of a Universal Integrated Circuit Card (UICC) including one or more Subscriber Identity Modules (SIMs), such as a Universal SIM (USIM) and / or Internet Protocol Multimedia Services Identity Module (ISIM), other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as a ‘SIM card.’ The memory 410 may allow the UE 400 to access instructions, application programs, and the like stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly embodied as or in the memory 410, which may be or comprise a device-readable storage medium.

[0133] The processing circuitry 402 may be configured to communicate with an access network or other network using the communication interface 412. The communication interface 412 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 422. The communication interface 412 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 418 and / or a receiver 420 appropriate to provide network communications (e.g., optical, electrical,frequency allocations, and so forth). Moreover, the transmitter 418 and receiver 420 may be coupled to one or more antennas (e.g., the antenna 422) and may share circuit components, software, or firmware, or alternatively be implemented separately.

[0134] In the illustrated embodiment, communication functions of the communication interface 412 may include cellular communication, WiFi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, NFC, location-based communication such as the use of the Global Positioning System (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband CDMA (WCDMA), GSM, LTE, NR, UMTS, WiMax, Ethernet, Transmission Control Protocol / Internet Protocol (TCP / IP), Synchronous Optical Networking (SONET), Asynchronous Transfer Mode (ATM), Quick User Datagram Protocol Internet Connection (QUIC), Hypertext Transfer Protocol (HTTP), and so forth.

[0135] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 412, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0136] As another example, a UE comprises an actuator, a motor, or a switch related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0137] A UE, when in the form of an loT device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application, and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a television, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlledsmart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, a surveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or VR, a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 400 shown in Figure 4.

[0138] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3 GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship, an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0139] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator and handle communication of data for both the speed sensor and the actuators.

[0140] Figure 5 shows a network node 500 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment in a telecommunication network. Examples of network nodes include, but are not limited to, APs (e.g., radio APs), Base Stations (BSs) (e.g., radio BSs, Node Bs, evolved Node Bs (eNBs), NR Node Bs (gNBs)), and 0-RAN nodes or components of an 0-RAN node (e.g., O-RU, O- DU, O-CU).

[0141] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node), and / or Remote Radio Units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such RRUs may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a Distributed Antenna System (DAS).

[0142] Other examples of network nodes include multiple Transmission Point (multi- TRP) 5G access nodes, Multi -Standard Radio (MSR) equipment such as MSR BSs, network controllers such as Radio Network Controllers (RNCs) or BS Controllers (BSCs), Base Transceiver Stations (BTSs), transmission points, transmission nodes, Multi-Cell / Multicast Coordination Entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0143] The network node 500 includes processing circuitry 502, memory 504, a communication interface 506, and a power source 508. The network node 500 may be composed of multiple physically separate components (e.g., a NodeB component and an RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 500 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair may in some instances be considered a single separate network node. In some embodiments, the network node 500 may be configured to support multiple RATs. In such embodiments, some components may be duplicated (e.g., separate memory 504 for different RATs) and some components may be reused (e.g., a same antenna 510 may be shared by different RATs). The network node 500 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 500, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, Long Range Wide Area Network (LoRaWAN), Radio Frequency Identification (RFID), or Bluetooth wireless technologies. These wirelesstechnologies may be integrated into the same or different chip or set of chips and other components within the network node 500.

[0144] The processing circuitry 502 may comprise a combination of one or more of a microprocessor, controller, microcontroller, CPU, DSP, ASIC, FPGA, or any other suitable computing device, resource, or combination of hardware, software, and / or encoded logic operable to provide, either alone or in conjunction with other network node 500 components, such as the memory 504, to provide network node 500 functionality.

[0145] In some embodiments, the processing circuitry 502 includes a System on a Chip (SOC). In some embodiments, the processing circuitry 502 includes one or more of Radio Frequency (RF) transceiver circuitry 512 and baseband processing circuitry 514. In some embodiments, the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 512 and the baseband processing circuitry 514 may be on the same chip or set of chips, boards, or units.

[0146] The memory 504 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, RAM, ROM, mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD), or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non- transitory device-readable, and / or computer-executable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 502. The memory 504 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 502 and utilized by the network node 500. The memory 504 may be used to store any calculations made by the processing circuitry 502 and / or any data received via the communication interface 506. In some embodiments, the processing circuitry 502 and the memory 504 are integrated.

[0147] The communication interface 506 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 506 comprises port(s) / terminal(s) 516 to send and receive data, for example to and from a network over a wired connection. The communication interface 506 also includes radio front-end circuitry 518 that may be coupled to, or in certain embodiments a part of, the antenna 510. The radio front-end circuitry 518 comprises filters 520 and amplifiers 522. The radio front-end circuitry 518 may be connected to the antenna 510 and the processingcircuitry 502. The radio front-end circuitry 518 may be configured to condition signals communicated between the antenna 510 and the processing circuitry 502. The radio front-end circuitry 518 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 518 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of the filters 520 and / or the amplifiers 522. The radio signal may then be transmitted via the antenna 510. Similarly, when receiving data, the antenna 510 may collect radio signals which are then converted into digital data by the radio front-end circuitry 518. The digital data may be passed to the processing circuitry 502. In other embodiments, the communication interface 506 may comprise different components and / or different combinations of components.

[0148] In certain alternative embodiments, the network node 500 does not include separate radio front-end circuitry 518; instead, the processing circuitry 502 includes radio front-end circuitry and is connected to the antenna 510. Similarly, in some embodiments, all or some of the RF transceiver circuitry 512 is part of the communication interface 506. In still other embodiments, the communication interface 506 includes the one or more ports or terminals 516, the radio front-end circuitry 518, and the RF transceiver circuitry 512 as part of a radio unit (not shown), and the communication interface 506 communicates with the baseband processing circuitry 514, which is part of a digital unit (not shown).

[0149] The antenna 510 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 510 may be coupled to the radio front-end circuitry 518 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 510 is separate from the network node 500 and connectable to the network node 500 through an interface or port.

[0150] The antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node 500. Any information, data, and / or signals may be received from a UE, another network node, and / or any other network equipment. Similarly, the antenna 510, the communication interface 506, and / or the processing circuitry 502 may be configured to perform any transmitting operations described herein as being performed by the network node 500. Any information, data, and / or signals may be transmitted to a UE, another network node, and / or any other network equipment.

[0151] The power source 508 provides power to the various components of the network node 500 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 508 may further comprise, or becoupled to, power management circuitry to supply the components of the network node 500 with power for performing the functionality described herein. For example, the network node 500 may be connectable to an external power source (e.g., the power grid or an electricity outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 508. As a further example, the power source 508 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0152] Embodiments of the network node 500 may include additional components beyond those shown in Figure 5 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 500 may include user interface equipment to allow input of information into the network node 500 and to allow output of information from the network node 500. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 500.

[0153] Figure 6 is a block diagram illustrating a virtualization environment 600 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices, and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more Virtual Machines (VMs) implemented in one or more virtual environments 600 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 600 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0154] Applications 602 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment 600 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0155] Hardware 604 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 606 (also referred to as hypervisors or VM Monitors (VMMs)), provide VMs 608A and 608B (one or more of which may be generally referred to as VMs 608), and / or perform any of the functions, features, and / or benefits described in relation with some embodiments described herein. The virtualization layer 606 may present a virtual operating platform that appears like networking hardware to the VMs 608.

[0156] The VMs 608 comprise virtual processing, virtual memory, virtual networking, or interface and virtual storage, and may be run by a corresponding virtualization layer 606. Different embodiments of the instance of a virtual application 602 may be implemented on one or more of the VMs 608, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as Network Function Virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers and customer premise equipment.

[0157] In the context of NFV, a VM 608 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 608, and that part of the hardware 604 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs 608, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 608 on top of the hardware 604 and corresponds to the application 602.

[0158] The hardware 604 may be implemented in a standalone network node with generic or specific components. The hardware 604 may implement some functions via virtualization. Alternatively, the hardware 604 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 610, which, among others, oversees lifecycle management of the applications 602. In some embodiments, the hardware 604 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a RAN or a base station.In some embodiments, some signaling can be provided with the use of a control system 612 which may alternatively be used for communication between hardware nodes and radio units.

[0159] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions, and methods disclosed herein. Determining, calculating, obtaining, or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination. Moreover, while components are depicted as single boxes located within a larger box or nested within multiple boxes, in practice computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0160] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hardwired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole and / or by end users and a wireless network generally.

[0161] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.

Claims

CLAIMSWhat is claimed is:

1. A method performed by a user equipment for beam management, the method comprising: receiving, from a network node, a configuration of a measurement report generated in response to a trigger condition, the configuration including information of: a first set of reference signals, a second set of reference signals, and the trigger condition, wherein the trigger condition is evaluated using measurements of the first set of reference signals and the second set of reference signals; and in response to the trigger condition being fulfilled, sending a notification signal to the network node.

2. The method of claim 1, wherein each of the first set of reference signals and each of the second set of reference signals represents a different beam and are each associated with a transmission configuration indication (TCI) state, wherein each TCI state includes information of an associated reference signal from the first set of reference signals or the second set of reference signals.

3. The method of any of the previous claims, wherein the sending the notification signal is determined by the user equipment based on the trigger condition.

4. The method of any of the previous claims, wherein the first set of reference signals are associated with a set of inactive TCI states or beams.

5. The method of any of the previous claims, wherein each of the second set of reference signals are associated with an activated TCI state or activated beam and each of the activated TCI states is dynamically indicatable by the network node for communication between the network node and the user equipment.

6. The method of claim 5, wherein one of the second set of reference signals is associated with an indicated TCI state or a current beam, where the indicated TCI state is one of the activated TCI states currently indicated by the network node for communication between the network node and the user equipment.

7. The method of any of the previous claims, wherein the measurement of the first reference signals and the second set of reference signals includes computing, for each of the measured reference signals, a received signal quality, wherein the received signal quality is a reference signal received power (RSRP) in dBm or a signal-to-noise and interference ratio ( SINR) in dB.

8. The method of any of the claims 1-6, wherein the measurement of the first reference signals and the second set of reference signals includes computing, for each of the measured reference signals, a received signal quality, wherein the received signal quality is a Layer 1 Reference Signal Received Power (Ll-RSRP) in dBm or Layer 1 Signal-to-Interference-plus- Noise Ratio (Ll-SINR) in dB.

9. The method of any of the previous claims, wherein the trigger condition is fulfilled when a difference between a received signal quality, x, of a first reference signal in the first set of reference signals and a received signal quality, y, of a second reference signal in the second set of reference signals satisfying a threshold value, z, such that x - y > z, where z is a positive value in dB.

10. The method of claim 9, wherein the second reference signal is associated with a current beam or an indicated TCI state.

11. The method of any of the previous claims, further comprising after sending the notification signal, receiving, from the network node, a request for sending the measurement report.

12. The method of any of the previous claims, wherein the request is a channel state information (CSI) request signaled in a downlink control information (DCI) format.

13. The method of any of the claims 1-12, further comprising in response to sending the notification signal, receiving an uplink grant for transmission of the measurement report.

14. The method of any of the claims 12 and 13, further comprising sending, to the network node, the measurement report.

15. The method of any of the claims 1-11, wherein the notification signal includes themeasurement report.

16. The method of any of the previous claims, wherein the measurement report includes information of at least the first reference signal and the second reference signal.

17. The method of claim 16, wherein the information further includes a received signal quality of the first reference signal and a received signal quality of the second reference signal.

18. The method of any of the previous claims, further comprising in response to sending the measurement report, receiving, from the network node, a TCI activation command indicating new activated TCI states.

19. The method of claim 18, wherein the TCI activation command results in an activated TCI state associated with the second reference signal being deactivated and a non-activated TCI state associated with the first reference signal being activated.

20. The method of any of the previous claims, wherein the notification signal indicates that the trigger condition is fulfilled.

21. A method performed by a network node for beam management, the method comprising: sending, to a user equipment, a configuration of a measurement report generated in response to a trigger condition, the configuration including information of: a first set of reference signals, a second set of reference signals, and the trigger condition, wherein the trigger condition is evaluated using measurements of the first set of reference signals and the second set of reference signals; and in response to the trigger condition being fulfilled, receiving, from the user equipment, a notification signal.

22. The method of claim 21, wherein each of the first set of reference signals and each of the second set of reference signals represents a different beam and are each associated with a transmission configuration indication (TCI) state, wherein each TCI state includes information of an associated reference signal from the first set of reference signals and the second set of reference signals.

23. The method of any of the claims 21 -22, wherein the notification signal is sent by the userequipment to the network node as determined by the user equipment in response to the trigger condition.

24. The method of any of the claims 21-23, wherein the first set of reference signals are associated with a set of inactive TCI states or beams.

25. The method of any of the claims 21-24, wherein each of the second set of reference signals are associated with an activated TCI state or activated beam and each of the activated TCI states is dynamically indicatable by the network node for communication between the network node and the user equipment.

26. The method of claim 25, wherein one of the second set of reference signals is associated with an indicated TCI state or a current beam, where the indicated TCI state is one of the activated TCI states currently indicated by the network node for communication between the network node and the user equipment.

27. The method of any of the of the claims 21-26, wherein the measurement of the first reference signals and the second set of reference signals includes computing, for each of the measured reference signals, a received signal quality, wherein the received signal quality is a reference signal received power (RSRP) in dBm or a signal-to-noise and interference ratio ( SINR) in dB.

28. The method of any of the of the claims 21-26, wherein the measurement of the first reference signals and of the second set of reference signals includes computing, for each of the measured reference signals, a received signal quality, wherein the received signal quality is a Layer 1 Reference Signal Received Power (LI -RSRP) in dBm or Layer 1 Signal -to- Interference-plus-Noise Ratio (Ll-SINR) in dB.

29. The method of any of the of the claims 21-28, wherein the trigger condition is fulfilled when a difference between a received signal quality, x, of a first reference signal in the first set of reference signals and a received signal quality, y, of a second reference signal in the second set of reference signals satisfying a threshold value, z, such that x - y > z, where z is a positive value in dB.

30. The method of claim 29, wherein the second reference signal is associated with a current beam or an indicated TCI state.

31. The method of any of the claims 21-30, further comprising after receiving the notification signal, sending, to the user equipment, a request for sending the measurement report.

32. The method of any of the claims 21-32, wherein the request is a channel state information (CSI) request signaled in a downlink control information (DCI) format.

33. The method of any of the claims 21-30, further comprising after receiving the notification signal, sending, to the user equipment, an uplink grant for transmission of the measurement report.

34. The method of any of the claims 31 and 33, further comprising receiving, from the user equipment, the measurement report.

35. The method of any of the claims 21-30, wherein the notification signal includes the measurement report.

36. The method of any of the claims 21-35, wherein the measurement report includes information of at least the first reference signals and the second reference signals.

37. The method of claim 36, wherein the information further includes a received signal quality of the first reference signals and the second reference signals.

38. The method of any of the claims 21-37, further comprising in response to receiving the measurement report, sending, to the user equipment, a TCI activation command indicating new activated TCI states.

39. The method of claim 38, wherein the TCI activation command results in an activated TCI state associated with the second reference signal being deactivated and a non-activated TCI state associated with the first reference signal being activated.

40. The method of any of the claims 21-39, wherein the notification signal indicates that thetrigger condition is fulfilled.

41. A user equipment for beam management, comprising: processing circuitry configured to perform any of the steps of any of the claims 1-20; and power supply circuitry configured to supply power to the processing circuitry.

42. A network node for beam management, the network node comprising: processing circuitry configured to perform any of the steps of any of the claims 21-40; power supply circuitry configured to supply power to the processing circuitry.

Images