BR112021014991B1 - METHOD FOR REPORTING MEASUREMENT, METHOD FOR SETTING MEASUREMENT REPORT, WIRELESS DEVICE AND BASE STATION - Google Patents

Abstract

METHOD FOR MEASUREMENT REPORT, METHOD FOR SETTING MEASUREMENT REPORT, WIRELESS DEVICE AND BASE STATION. A method for measurement reporting performed by a wireless device includes obtaining a beam measurement configuration from a network. Based on the beam measurement configuration, the wireless device performs at least one beam measurement while operating in a dormant state. The wireless device reports a result of at least one beam measurement to the network. The report is made after a transition from the dormant state to a connected state.

Description

TECHNICAL FIELD

[001] The present disclosure concerns, generally, wireless communications and, more particularly, systems and methods for beam information in advance measurements.

BACKGROUND

[002] In Release 10, Carrier Aggregation (CA) was introduced in Long Term Evolution (LTE) to enable user equipment (UE) to transmit and/or receive information via multiple cells, which may be called Secondary Cells (SCells, from multiple carrier frequencies, to the benefit of the existence of non-contiguous and contiguous carriers. In CA terminology, the Primary Cell (PCell) is the cell to which the UE has established the Radio Resource Control connection (RRC) or handover to. In CA, cells are aggregated at the Medium Access Control (MAC) level. The Medium Access Control (MAC) obtains grants for a certain cell and multiplexes data from it. different carriers for a Transport Block being sent in that cell. Furthermore, the MAC controls how this process is done.

[003] FIGURE 1 illustrates multiple Packet Data Convergence Protocols (PDCPs) and Radio Link Controls (RLCs) connected to multiple cells (e.g., Cell1, Cell2 and Cell3) via a MAC layer.

[004] SCells can be added or configured for the UE using RRC signaling, such as, for example, an RRCConnectionReconfiguration message, which occurs on the order of 100s of milliseconds. A cell that is configured for the UE becomes a serving cell for this UE. A SCell can also be associated with a SCell state. When configured/added via RRC, a SCell starts in a disabled state. In LTE Release 15, an eNB can tell the UE to activate on configuration, or change state, at least on RRCReconfiguration.

[005] FIGURE 2 illustrates the possible states for a cell, as discussed in LTE Release 15. Specifically, in LTE Release 15, a new intermediate state between the disabled and active states was introduced for improved uplink operation. This state is the dormant state and has not yet been introduced in Novo Rádio (NR). The action of moving into a dormant state is called hibernation.

[006] A MAC Control Element (MAC CE) can be used to change the state of the SCell between deactivated, activated and dormant states. There are also timers in MAC to move a cell between off, on, and dormant states. These timers are: — sCellHibernationTimer; which moves the SCell from the activated state to the dormant state, — sCellDeactivationTimer; which moves the SCell from the activated state to the deactivated state, — dormantSCellDeactivationTimer; which moves the SCell from the dormant state to the deactivated state.

[007] MAC level SCell activation occurs in the range of 20-30 ms.

[008] Once the network understands the need to configure and/or activate the CA, the question is which cells to configure and/or activate initially, whether they are configured and/or whether a cell/carrier is good enough in terms of of radio quality/coverage such as RSRP and RSRQ. To understand the conditions in SCell(s) or potential SCell(s) on a given available carrier, the network can configure the UE to perform Radio Resource Management (RRM) measurements.

[009] Typically, the network may be assisted by RRM measurements to be reported by a UE. The network can configure the UE with measurement IDs associated with reportConfig with event A1 (serving cell becomes better than threshold) in case it is a configured SCell, or A4 (neighboring cell becomes better than threshold) in case it is a configured SCell, or A4 (neighbor cell becomes better than the threshold) for carriers without a configured SCell. Measurement objects are associated with the carrier the network wants to report on. If the network is aware of the exact cells it wants the UE to measure, a white list of cells can be configured on the measurement object so that the UE is only required to measure those cells on that carrier.

[010] FIGURE 3 illustrates a signaling flow diagram for reconfiguring a UE in RRC_Connected after the Master Node (MN) makes the decision to adjust (set up) the CA and/or Dual Connectivity (DC). Specifically, the MN sends an RRCReconfiguation message, which is a measConfig with, for example, A4. After a period of time equal to the time it takes to obtain the first measurement reports, the UE sends an RRCMeasurementReport to carriers and cells. The MN then makes a decision for SCell addition or SCell activation based on the RRCMeasurementReport and transmits an RRCReconfiguration message to the UE.

[011] With the later introduction of DC in Release 12, it was possible to add what is called a Secondary Cell Group (SCG) configuration to the UE. The main benefit is that the UE can, in principle, add a cell from another eNodeB. In terms of protocol, this would require different MAC entities, one for each group of cells. The UE will have two groups of cells, one associated with a PCell (master node) and another associated with a PSCell (from the secondary eNodeB), where each group can possibly have its own associated SCells.

[012] When it comes to adding SCells, when the UE is in single connectivity, the RRCConnectionReconfiguration message can carry a cell index (so that MAC identifiers are optimized, i.e. shorter), the cell identifier and the carrier frequency, common parameters and status information, later introduced in Release 15 (activated or dormant).

[013] 5G in 3GPP introduces a new core network (5GC) and a new Radio Access Network (NR). The core network, 5GC, however, will also support Radio Access Technologies (RATs) in addition to NR. It was agreed that LTE or Evolved Universal Terrestrial Radio Access (E-UTRA) should also be connected to the 5GC. LTE base stations, such as eNBs, that are connected to 5GC are called ng-eNB and are part of NG-RAN, which also consists of NR base stations called gNBs. FIGURE 4 illustrates the 5GS architecture containing 5GC and NG-RAN. Specifically, FIGURE 4 shows how base stations are connected to each other and to nodes in 5GC.

[014] There are different ways to deploy a 5G network with or without interworking with LTE (also referred to as E-UTRA) and evolved packet core (EPC). FIGURE 5 illustrates LTE and NR interworking options. In principle, NR and LTE can be deployed without any interworking, denoted by NR autonomous operation (SA). That is, the gNB in the NR can be connected to the 5G core network (5GC) and the eNB can be connected to the EPC without interconnection between the two, as shown in Option 1 and Option 2 in FIGURE 5. On the other hand, the first version supported of NR is E-UTRAN-NR Dual Connectivity (EN-DC), which is illustrated as Option 3. In such a deployment, DC between NR and LTE is applied with LTE as the master and NR as the secondary node. The RAN node, which may include a gNB supporting NR, may not have a core network control plane connection (EPC), instead it relies on LTE as the master node (MeNB). This is also called non-autonomous NR. In this case, the functionality of an NR cell is limited and would be used for tethered mode UEs as a diversity leg and/or booster, but an RRC_IDLE UE cannot camp in these NR cells.

[015] With the introduction of 5GC, other options may also be valid. As mentioned above, Option 2 supports standalone NR deployment, where the gNB is connected to 5GC. Similarly, LTE can also be connected to 5GC using Option 5, which is also known as eLTE, E-UTRA/5GC or LTE/5GC, and the node can be referred to as an ng-eNB. In these cases, both NR and LTE are seen as part of NG-RAN, and both ng-eNB and gNB can be referred to as NG-RAN nodes). It should be noted that Option 4 and Option 7 are other DC variants between LTE and NR which will be standardized as part of 5GC-connected NG-RAN, denoted by Multi-Radio Dual Connectivity (MR-DC). Under the umbrella of MR-DC we have: • EN-DC (Option 3): LTE is the master node and NR is the secondary (EPC CN employed) • NE-DC (Option 4): NR is the master node and LTE is the secondary (5GCN employed) • NGEN-DC (Option 7): LTE is the master node and NR is the secondary (5GCN employed) • NR-DC (Option 2 variant): Dual connectivity in which both the master and secondary are NR (5GCN employed).

[016] As migration to these options may differ between different network operators, it is possible to have deployments with multiple options in parallel on the same network. For example, there could be an eNB base station supporting Options 3, 5 and 7 on the same network as an NR base station supporting Options 2 and 4. In combination with DC solutions between LTE and NR, it is also possible to support the CA in each cell group (i.e., MCG and SCG) and dual connectivity between nodes in the same RAT (e.g., NR-NR DC). For LTE cells, a consequence of these different deployments is the coexistence of LTE cells associated with eNBs connected to EPC, 5GC or both EPC/5GC.

[017] A very typical scenario/use case is a UE with some burst traffic that comes and goes. For example, the UE may send or receive some video packets, experience transmit/receive idle periods, and then return to live. To save UE power, the network transitions the UE from connected to idle during these periods. Then the UE comes back again, via paging or requesting the UE to be connected, and accesses the network.

[018] In LTE Release 13, a mechanism was introduced for the UE to be suspended by the network in a suspended state in a similar way to RRC_IDLE, but with the difference that the UE stores the Access Stratum (AS) context or RRC. This makes it possible to reduce signaling when the UE is becoming active again by resuming the RRC connection, rather than a priori establishing the RRC connection from scratch. Reducing signaling can have several benefits: — Reduce latency, for example for smartphones accessing the Internet — Reduced signaling leads to reduced battery consumption for machine-type devices that send very little data.

[019] The Release 13 solution is based on the fact that the UE sends an RRCConnectionResumeRequest message to the network and in response may receive an RRCConnectionResume from the network. The RRCConnectionResume is not encrypted, but its integrity is protected.

[020] The LTE resume procedure can be found in the RRC specifications, such as 3GPP TS 36.331. As the UE performing resumption is in RRC_IDLE (with suspended AS context), this triggers a transition from RRC_IDLE to RRC_CONNECTED. Thus, this is modeled in the specifications in the same subclause that captures RRC connection establishment (subclause 5.3.3 RRC connection establishment).

[021] There are a few relevant things to highlight in SCG configurations and SCell configurations for MCGs in relation to suspend/resume procedures. After suspend, the UE is set to store its used RRC configuration. In other words, if the UE is operating in any DC mode and has an SCG configuration or if the UE has only configured SCells in the MCG, it must store all these configurations. However, upon resumption, at least until Release 15, it is defined that the UE must release the SCG configurations and the SCell configurations.

[022] Therefore, when the UE comes from RRC_IDLE with the context, if the network wants to add SCell(s) to the MCG or add an SCG, it needs to do it from scratch, even if the UE is suspending and resuming in the same cell/ area where all previous PCell and SCell configurations are still valid from the point of view of radio conditions.

[023] As the use case of UEs with burst traffic being constantly suspended and resuming in the same cell is quite common, 3GPP has standardized a solution in LTE to allow the UE to assist the network with measurements performed while the UE is in RRC_IDLE so that the network could accelerate the adjustment of carrier aggregation or dual connectivity. Specifically, in LTE Release 15, it is possible to configure the UE to report so-called early measurements upon transition from the idle state to the connected state. These measurements are measurements that the UE can perform in an idle state and in accordance with a configuration provided by the source cell with the intention of receiving these measurements immediately after the UE is connected and quickly adjusting AC and/or other forms of DC (e.g. , EN-DC, MR-DC, etc.) without the need to first provide a measurement configuration (measConfig) in RRC_CONNECTED, as shown in the previous sections, and wait hundreds of milliseconds until the first samples are collected, monitored and, then the first reports are triggered and transmitted to the network.

[024] A first aspect of the existing solution, as standardized in EUTRA 36.331, is described in 5.6.20 Idle Mode Measurements. The UE can receive these measurement configurations idle in the system information (SIB5) in the MeasIdleConfigSIB-r15 field, indicating up to 8 cells or ranges of cell IDs to perform measurements. Additionally, the UE can be configured by transitioning from RRC_CONNECTED to RRC_IDLE with a dedicated measurement configuration in the RRCConnectionRelease message with MeasIdleDedicated-r15 which overrides the settings broadcast in SIB5.

Carrier information and cell list

[025] The UE is provided with a list of carriers and, optionally, with a list of cells on which the UE is to perform measurements. The s-NonIntraSearch fields in SystemInformationBlockType3 do not affect UE measurement procedures in IDLE mode.

T331 timer

[026] Upon receipt of this measurement configuration, the UE starts a T331 timer with the value provided in measIdleDuration, which can range from 0 to 300 seconds. The timer stops upon receiving RRCConnectionSetup, RRCConnectionResume which indicates a transition to RRC_CONNECTED. This concept exists to limit the amount of time that the UE performs measurements for the purpose of early measurements.

Validity Area

[027] Another concept introduced in the LTE Release 15 solution is a validity area, which comprises a list of PCBs. The intention is to limit the area where AC or DC can be adjusted later when the UE resumes/adjusts the connection, so that early measurements are somehow useful for this purpose. If validityArea is configured and the UE reselects to a serving cell whose PCI does not match any entry in the validityArea for the corresponding carrier frequency, the T331 timer is stopped. Then, the UE stops performing IDLE measurements and releases the configuration (i.e., VarMeasIdleConfig). This does not necessarily imply that the UE releases the idle measurements that were configured in the release message and that were performed. They can still be stored and possibly requested over the network. Furthermore, the UE may continue with IDLE mode measurements according to the broadcast SIB5 configuration after timer T331 has expired or stopped.

Minimum quality threshold

[028] It is also noted that only measurements above a certain threshold should be stored, as candidate cells for AC adjustment need to be within a minimum acceptable threshold. How the UE performs measurements in IDLE mode depends on the implementation of the UE, as long as the RAN4 requirements for measurement reporting defined in 36.133 are met.

Indication of early measurements available upon resumption/adjustment in LTE

[029] Another aspect of the existing solution occurs when the UE attempts to resume or adjust a call from RRC_IDLE without context. If the previous step is performed, such as if the UE is configured to store idle measurements, the network may ask the UE upon resumption/adjustment (after security is enabled) whether the UE has idle measurements available.

[030] In case this UE is adjusting a connection coming from RRC_IDLE without the AS Context, the network is not aware that the UE has available measurements stored. Then, to let the network know this, and possibly ask the UE to report early measurements, the UE can indicate the availability of idle measurements stored in RRCConnectionSetupComplete. Since not all cells would support the feature anyway, the UE only includes this availability information if the cell broadcasts the idleModeMeasurements indication to SIB2.

[031] In the event that this UE is tuning a connection coming from RRC_IDLE, but with a stored AS Context (i.e., resuming from suspend), the network may be aware that the UE may have idle measurements available stored after checking the fetched context of the source node where the UE was suspended. However, it is still not certain that the UE has measurements available, since the UE is only required to perform measurements if the cells are above the configured RSRP/RSRQ thresholds and while performing cell selection/cell reselection within the configured validity area. Then, to let the network know that, and possibly request the UE to report early measurements, the UE can also indicate the availability of idle measurements stored in RRCConnectionResumeComplete. Since not all cells would support the feature anyway, the UE only includes this availability information if the cell broadcasts the idleModeMeasurements indication to SIB2.

[032] FIGURE 6 illustrates the early measurement report after resumption/adjustment in LTE. Once the UE indicates to the target cell upon resumption or adjustment that idle measurements are available, the network can finally request the UE to report these available measurements by including the idleModeMeasurementReq field in the UEInformationRequest message transmitted to the UE. Then, the UE responds with a UEInformationResponse containing these measurements.

[033] There are currently certain challenge(s). For example, unlike LTE, in NR, random access resources are mapped per beam, for example, by SSB and/or by CSI-RS. Before random access selection, the UE needs to perform measurements on the destination cell, which is the cell where the UE performs random access, and select a beam based on these measurements (e.g., an SSB for the destination cell, i.e. , an SSB that encodes the PCI, i.e., PSS/SSS of the target cell). Then, after selecting a beam, the UE knows which random access resources to use, since the RACH configuration contains the mapping between the selected DL beam and the RACH resources to be used (either the dedicated one, if provided, or the common RACH configuration), including for example preamble(s) and time/frequency domain resources. In other words, in NR, random access resource selection needs to be performed within a cell, depending on the measurements performed in SSBs or CSI-RSs.

[034] FIGURE 7 illustrates an exemplary SSB transmission. As depicted, a cell in NR is basically defined by a set of these SSBs that can be transmitted in one (typical implementation for lower frequencies, e.g. below 6 GHz) or multiple downlink beams (typical implementation for lower frequencies , e.g. below 6 GHz). For the same cell, these SSBs carry the same physical cell identifier (PCI) and master information block (MIB). For autonomous operation and to support UEs camped in an NR cell, they also carry in SIB1 the RACH configuration, which comprises a mapping between the detected SSB covering the UE at a given point in time and the PRACH configuration (e.g. time, frequency, preamble, etc.) to be used. To achieve this, each of these beams can transmit its own SSB, which can be distinguished by an SSB index.

[035] The mapping between RACH resources and SSBs (or CSI-RS) is also provided as part of the RACH configuration (in RACH-ConfigCommon). Two parameters are relevant here: — #SSBs per PRACH occasion: 1/8, %, %, 1, 2, 8 or 16, which represents the number of SSBs per RACH occasion; — # CB preambles per SSB for each SS block: within a RACH occasion, how many preambles are allocated.

[036] To give a first example, if the number of SSBs per RACH occasion is 1, and if the UE is under the coverage of a specific SSB, for example SSB index 2, there will be a RACH occasion for that index. SSB 2. If the UE moves and is now under the coverage of another specific SSB, e.g., SSB index 5, there will be another RACH occasion for that SSB index 5, i.e., each SSB detected by a given UE would have your own RACH occasion. Thus, on the network side, upon detecting a preamble on a particular RACH occasion, the network knows exactly which SSB the UE has selected and, consequently, which downlink beam is covering the UE, so that the network can continue transmission downlink, for example, RAR, etc. This factor of 1 is an indication that each SSB has its own RACH resource. that is, a preamble detected there indicates to the network which SSB the UE has selection, that is, which DL beam the network should use to communicate with the UE, such as the one to send the RAR.

[037] FIGURE 8 illustrates the preamble mapping for different RACH occasions, and FIGURE 9 illustrates the preamble mapping for the same RACH occasion. Note that each SS block typically maps to multiple preambles (different cyclic offsets and Zadoff-Chu roots) within a PRACH occasion, so that it is possible to multiplex different UEs on the same RACH occasions, since they can be under the coverage of the same SSB. In a second example, shown below, the number of SSBs per RACH occasion is two. Therefore, a preamble received at that time from RACH indicated to the network that one of the two beams is being selected by the UE. Thus, either the network has means via implementation to distinguish these two beams and/or it must perform a beam scan on the downlink by transmitting the RAR in both beams, simultaneously or, transmitting in one, waiting for a response from the UE, and if absent, transmitting in the other.

[038] The examples above are also applicable for CSI-RS resources.

[039] A UE can be configured for early measurements for quick AC/DC adjustment. While in RRC_CONNECTED, the UE can be configured to perform measurements and trigger measurement reports. This can help the network make decisions such as adding, modifying or removing SCell(s), SCG(s), triggering handovers, etc. In the case of NR, the network may configure the UE to apply L3 filtering on beam measurements and include beam measurement information in RRC measurement reports for the serving cell(s) and trigger cell(s), that is, cells that trigger measurement reports. The configuration for beam reporting is provided as part of ReportConfigNR and MeasObject, both possibly included in a measurement configuration (see MeasConfig IE). One of the purposes of the network configuring the RRC_CONNECTED UE to report beam measurements is to enable the target cell (which may be a target candidate for HO, SCG addition, SCell addition, etc.) to efficiently allocate RACH resources Containment Free (CFRA). Upon receipt of beam measurements from the UE associated with a destination candidate, the source can forward these beam measurements during the preparation phase so that the destination knows which of its beams are best covering the UE (e.g., SSBs and/or CSI-RSs). Therefore, the target may limit the provision of CFRA resources to only these beams, since there is a high probability that when performing beam selection during random access, the UE will select one of these beams.

[040] In the existing solution, as explained above, the UE can be configured to report upon resumption procedure (or rather, at the end of it) of cell measurements, such as, for example, RSRP cell, RSRQ cell, SINR, etc., to help the network make faster decisions to configure SCell(s) for MCG, SCGs (possibly including SCell(s), etc.) rather than waiting for connected mode measurements, which can only be configured in RRC Resume type messages. It would take a few hundred milliseconds before the first reports were received by the network.

[041] If the existing LTE solution were adopted in NR, the network would have problems performing CFRA for SCG addition, SCell addition, as it would require the provision of RACH resources for all possible beams (e.g. SSBs ) covering the cell, which can be quite ineffective. Consequently, the network may not even use such a resource due to this inefficiency.

[042] There may be cells that do not transmit SSBs (PSS, SSS or PBCH) within the synchronization raster. They will not be detected by a UE searching the carrier frequency for cells to camp. These cells are not possible to configure for early measurements if the LTE Release 15 solution is adopted in NR. This would restrict the use of the early metering feature as these cells would be excluded from rapid AC or DC adjustment.

SUMMARY

[043] Certain aspects of this disclosure and its modalities may provide solutions to these or other challenges.

[044] According to certain embodiments, a method for reporting measurement performed by a wireless device includes obtaining a beam measurement configuration from a network. Based on the beam measurement configuration, the wireless device performs at least one beam measurement while operating in a dormant state. The wireless device reports a result of at least one beam measurement to the network. The report is made after a transition from the dormant state to a connected state.

[045] According to certain embodiments, a wireless device is provided for reporting measurement. The wireless device includes processing circuitry configured to obtain a beam measurement configuration from a network. Based on the beam measurement configuration, the processing circuitry is configured to perform at least one beam measurement while operating in a dormant state. The processing circuitry is configured to report a result of the at least one beam measurement to the network. The report is made after a transition from the dormant state to a connected state.

[046] According to certain embodiments, a method performed by a base station to configure the measurement report includes transmitting a beam measurement configuration to a wireless device. The beam measurement configuration configures the wireless device to perform at least one beam measurement while the wireless device is operating in a dormant state. The base station receives, from the wireless device, a report of a result of the at least one beam measurement. The report is received after a wireless device transitions from a dormant state to a connected state.

[047] According to certain embodiments, a base station is provided for configuring the measurement report. The base station includes processing circuitry configured to transmit a beam measurement configuration to a wireless device. The beam measurement configuration configures the wireless device to perform at least one beam measurement while the wireless device is operating in a dormant state. The processing circuitry is configured to receive, from the wireless device, a report of a result of the at least one beam measurement. The report is received after a wireless device transitions from a dormant state to a connected state.

[048] Certain modalities may provide one or more of the following technical advantages. For example, certain embodiments provide the possibility of efficiently accelerating SCG and SCell additions when the UE is performing state transitions from a dormant state to the connected state, reporting beam measurements to the network in advance measurements performed in a dormant state when the UE transitions to connected and allowing the network to allocate CFRA resources to the target SCG(s) and/or SCell(s).

[049] As another example, certain embodiments allow the network to allocate only CFRA resources (or other resources) related to a single DL beam, or a few DL beams, which is/are more likely to be the best beam for the UE in the destination SCG(s) and/or SCell(s), such as the DL beam that the UE will select. This allows, for example, faster addition of SCG and/or SCell in the state transition from a dormant state to the connected state without allocating resources, such as dedicated RACH resources, to many (or even all) beams in the cell(s) to add.

[050] As another example, certain embodiments allow early measurements performed outside the synchronization raster to be performed by a UE in a dormant state, in order to adjust SCG(s) and/or SCell(s) that, for example, do not transmit any SSB in the synchronization raster, i.e. cells in which it is not possible for UEs to camp. As an example, it can be a cell that is only used for UEs in connected state, such as SCells.

[051] Other advantages can be readily perceived by a person skilled in the art. Certain modalities may have none, some or all of the aforementioned advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

[052] For a more complete understanding of the disclosed modalities and their features and advantages, reference will now be made to the following description, taken together with the attached figures, which:

[053] FIGURE 1 illustrates multiple Packet Data Convergence Protocols (PDCPs) and Radio Link Controls (RLCs) connected to multiple cells (e.g., Cell1, Cell2 and Cell3) via a MAC layer;

[054] FIGURE 2 illustrates the possible states for a cell as discussed in LTE Release 15;

[055] FIGURE 3 illustrates a signaling flow diagram for reconfiguring a User Equipment (UE) in RRC_Connected after the Master Node (MN) makes the decision to adjust Carrier Aggregation (CA) and/or Dual Connectivity (A.D);

[056] FIGURE 4 illustrates the preamble mapping for different Radio Access Channel (RACH) occasions;

[057] FIGURE 5 illustrates the preamble mapping for the same RACH occasion;

[058] FIGURE 6 illustrates the report of early measurements upon resumption/configuration in LTE;

[059] FIGURE 7 illustrates an example of Synchronization Signal Block (SSB) transmission;

[060] FIGURE 8 illustrates the preamble mapping for different RACH occasions;

[061] FIGURE 9 illustrates the preamble mapping for the same RACH occasion;

[062] FIGURE 10 illustrates an SSB, according to certain embodiments;

[063] FIGURE 11 illustrates an exemplary wireless network, according to certain embodiments;

[064] FIGURE 12 illustrates an exemplary network node, according to certain embodiments;

[065] FIGURE 13 illustrates an exemplary wireless device, according to certain embodiments;

[066] FIGURE 14 illustrates exemplary user equipment, according to certain embodiments;

[067] FIGURE 15 illustrates a virtualization environment in which functions implemented by some modalities can be virtualized, according to certain modalities;

[068] FIGURE 16 illustrates an exemplary method by a wireless device, according to certain embodiments;

[069] FIGURE 17 illustrates an exemplary virtual computing device, according to certain embodiments;

[070] FIGURE 18 illustrates an exemplary method by a network node, according to certain embodiments; It is

[071] FIGURE 19 illustrates another exemplary virtual computing device 1, according to certain embodiments.

DETAILED DESCRIPTION

[072] Some of the embodiments contemplated in the present invention will now be described more fully with reference to the attached drawings. Other embodiments, however, are contained within the scope of the subject matter disclosed in the present invention, the subject matter disclosed should not be interpreted as limited to only the embodiments set forth herein; rather, these embodiments are provided by way of example to convey the scope of the matter to those skilled in the art.

[073] Generally, all terms used in the present invention should be interpreted in accordance with their common meaning in the relevant technical field, unless a different meaning is clearly given and/or implied in the context in which it is used. All references to an element, apparatus, component, means, stage, etc. shall be openly interpreted as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed in the present invention need not be performed in the exact order disclosed unless a step is explicitly described as following or preceding another step and/or where it is implied that a step must follow or precede another step. Any feature of any of the embodiments disclosed in the present invention can be applied to any other embodiment, whenever appropriate. Likewise, any advantage of any of the modalities can be applied to any other modalities and vice versa. Other objectives, features and advantages of the included modalities will be evident from the following description.

[074] According to certain embodiments, a method performed on a wireless terminal/user equipment (UE) to report advance measurement upon transition from a dormant state (e.g., RRC_IDLE with stored context, RRC_IDLE without stored context, RRC_INACTIVE) for connected includes: — obtaining from the network a configuration for beam measurement information based on beam measurements performed in a dormant state, where reporting is done upon transition from a dormant state to a connected state; and — reporting to the network beam measurement information based on beam measurements performed in a dormant state, where reporting is done upon transition from a dormant state to the connected state.

[075] According to certain embodiments, a method performed by a source network node configuring a user equipment (UE) upon transition from a connected state to a dormant state (e.g., RRC_IDLE with stored context, RRC_IDLE without stored context , RRC_INACTIVE) may include: — configuring a UE going into the dormant state to perform beam measurements per cell (where a list of one or multiple cells may be provided) and/or per carrier frequency (where a list of one or multiple cells can be provided), where measurements are performed according to a measurement configuration.

[076] According to certain embodiments, a method performed by a target network node where a user equipment (UE) is performing a transition from a dormant state (e.g., RRC_IDLE with stored context, RRC_IDLE without stored context, RRC_INACTIVE ) for a connected state includes: — receiving an early measurement report from a UE performing a transition from the dormant state to the connected state, where the report includes measurements with beam measurement information performed in the dormant state; These beam measurements may be provided per cell for at least one carrier frequency; and — configure the UE to perform SCG and/or SCell configuration, such as adding, removing, modifying SCG/SCell, for at least one cell and providing contention-free RACH capabilities for at least one of the beams reported in the previous step.

[077] According to certain embodiments, a method performed by a source network node configuring a user equipment (UE) after transitioning from a connected state to a dormant state (e.g., RRC_IDLE with stored context, RRC_IDLE without context stored, RRC_INACTIVE) includes: — configuring a UE going into the dormant state to perform measurements per beam and/or per cell (where a list of single or multiple cells can be provided) and/or per carrier frequency (where a list of one or multiple cells may be provided), where some or all measurements are performed outside the synchronization raster in accordance with a measurement configuration.

[078] As used in the present invention, the term “beam measurement information” can be interpreted as measurement performed on reference signals (such as SSBs or CSI-RS resources) that can be beamformed by the network. Beam measurement information can be beam measurements such as RSRP, RSRQ, or SINR per beam (e.g. SS-RSRP, for RSRP performed on a specific SSB) or information derived from beam measurements such as a list of beam identifiers where these have been selected based on beam measurements, for example identifying stronger beams or beam above a configurable threshold.

[079] As used in the present invention, beam measurement information may consist of at least one of the following: o Beam identifier of beam(s); If it is an SSB, the SSB identifier. If it is a CSI-RS, a CSI-RS identifier. o Radio conditions of the measured beam(s) (e.g. RSRP, RSRQ or SINR). These radio conditions may be those that the UE used to derive cell quality while the UE is in the dormant state.

[080] In a particular embodiment, the beam identifier is an SSB index. This can be derived based on the information transmitted in the MIB payload and its demodulation reference signals (DM-RS).

[081] In a particular embodiment, the beam identifier is a CSI-RS index. This can be provided by the network via dedicated signaling associated with a specific CSI-RS resource configuration.

[082] The present disclosure describes the reporting of beam measurement information in advance measurements upon transition from a dormant state (e.g., RRC_IDLE without a stored context, RRC_IDLE with a stored context, RRC_INACTIVE). In the context of the present disclosure, a “beam” may be a reference signal that the UE detects and that has an associated identifier. For example, if the present disclosure is applied to the 3GPP NR standard, the reference signal described above may be a PBCH Synchronization and Block Signal (SSB) or a CSI-RS.

[083] FIGURE 10 illustrates an SSB, according to certain embodiments. In the case of an SSB consisting of primary and secondary synchronization signals (PSS, SSS), each occupying 1 symbol and 127 subcarriers, and PBCH comprising 3 OFDM symbols and 240 subcarriers, but in one symbol leaving an unused portion in between for SSS.

[084] The possible time locations of the SSBs in a half-frame are determined by the subcarrier spacing and the periodicity of the half-frames where the SSBs are transmitted is configured by the network. During a half frame, different SSBs can be transmitted in different spatial directions (i.e., using different beams, increasing the coverage area of a cell). Within the frequency range of a carrier, multiple SSBs can be transmitted. The PCBs of SSBs transmitted at different frequency locations do not need to be unique, i.e., different SSBs in the frequency domain can have different PCBs. However, when an SSB is associated with an RMSI, the SSB corresponds to an individual cell, which has a unique NCGI (see subclause 8.2). Such an SSB is referred to as a Cell Definition SSB (CD-SSB). A PCell is always associated with a CD-SSB located in the synchronization raster.

[085] Layer 1 may receive from upper layers a set of SS/PBCH (or CS-RS) block indices and provide the upper layers with a corresponding set of RSRP, RSRQ and/or SINR measurements. These may be called L1 measurement by SSB, L1 measurement by CSI-RS or L1 measurement by beam. These measurements to be recorded and reported as described in this disclosure may be those described in the L1 specifications, as reproduced below (for simplicity, only RSRP definitions have been provided for CSI-RS and SSB): — SS of received signal power (SS-RSRP) o SS reference signal received power (SS-RSRP) is defined as the linear average over the power contributions (in [W]) of the resource elements carrying the signals secondary synchronization settings. The measurement time resource(s) for SS-RSRP are confined within the SS/PBCH Block Measurement Time Configuration (SMTC) window duration. If SS-RSRP is used for L1-RSRP as configured by report settings as defined in 3GPP TS 38.214, the restriction of measurement time resource(s) by the duration of the SMTC window is not applicable. o For the determination of SS-RSRP, demodulation reference signals for physical broadcast channel (PBCH) and, if indicated by higher layers, CSI reference signals, in addition to secondary synchronization signals, can be used. SS-RSRP using demodulation reference signal for PBCH or CSI reference signal shall be measured by linear averaging over the power contributions of the resource elements carrying corresponding reference signals, taking into account the power scaling for the demodulation signals. reference as defined in 3GPP TS 38.213. If SS-RSRP is not used for L1-RSRP, the additional use of CSI reference signals for SS-RSRP determination is not applicable. SS-RSRP shall be measured only between reference signals corresponding to SS/PBCH blocks with the same SS/PBCH block index and the same physical layer cell identity. o If SS-RSRP is not used for L1-RSRP and higher layers indicate certain SS/PBCH blocks to perform SS-RSRP measurements, then SS-RSRP is measured only from the indicated set of SS/PBCH block(s). PBCH. o For frequency band 1, the reference point for SS-RSRP should be the UE antenna connector. For frequency band 2, SS-RSRP shall be measured based on the combined signal of antenna elements corresponding to a given receiving branch. For frequency band 1 and 2, if receiver diversity is in use by the UE, the reported SS-RSRP value must not be less than the corresponding SS-RSRP of any of the individual receiver branches. o NOTE 1: The number of resource elements within the measurement period that are used by the UE to determine SS-RSRP is left to the UE implementation with the limitation that the corresponding measurement accuracy requirements must be met. This information may also be recorded in the RACH report, as a new aspect of this disclosure. o NOTE 2: The power per resource element is determined from the power received during the useful part of the symbol, excluding the CP. — CSI Reference Signal Received Power (CSI-RSRP) o CSI Reference Signal Received Power (CSI-RSRP), is defined as the linear average over the power contributions (in [W]) of the resource elements of the antenna port(s) carrying CSI reference signals configured for RSRP measurements within the measurement frequency bandwidth at the configured CSI-RS occasions. o For the determination of CSI-RSRP, CSI reference signals transmitted on antenna port 3000 in accordance with 3GPP TS 38.211 [4] must be used. If CSI-RSRP is used for L1-RSRP, the CSI reference signals transmitted on antenna ports 3000, 3001 can be used for determining CSI-RSRP. o For intra-frequency CSI-RSRP measurements, if the measurement gap is not configured, the UE is not expected to measure the CSI-RS resource(s) outside the active downlink bandwidth portion. o For frequency band 1, the reference point for the CSI-RSRP must be the UE antenna connector. For frequency band 2, CSI-RSRP shall be measured based on the combined signal of antenna elements corresponding to a given receiving branch. For frequency band 1 and 2, if receiver diversity is in use by the UE, the reported CSI-RSRP value must not be less than the corresponding CSI-RSRP of any of the individual receiver branches. o NOTE 1: The number of resource elements within the considered measurement frequency bandwidth and within the measurement period that are used by the UE to determine CSI-RSRP is left to the UE implementation with the limitation that the requirements corresponding measurement accuracy standards must be met. This information may also be recorded in the RACH report, as a new aspect of this disclosure.

[086] Although this disclosure is primarily focused on NR, the method is not limited to NR. Instead, the methods described in the present invention apply to many different notions of RATs, including: — A RAT in which the UE is in RRC_CONNECTED when suspended; — The RAT at which the UE is configured to perform measurements when suspended; — The RAT in which the UE performs RRC connection resume or RRC connection setup and in which the UE sends initial measurement reports, including beam measurement information.

[087] In the disclosed methods, all different RAT combinations are supported. Some examples are provided below: — The UE in RRC_CONNECTED on NR is suspended or released to the dormant state (e.g., RRC_IDLE or RRC_INACTIVE) and performs beam measurements for a cell on a carrier frequency of NR (this may be a frequency outside the sync raster, i.e. where other UEs are possibly not camping or in the sync raster); This UE resumes or adjusts a connection on the NR; Then, during this transition to connected, these early measurements, including beam measurements, can be reported. — The UE in RRC_CONNECTED in LTE is suspended or released to the dormant state (e.g., RRC_IDLE or RRC_INACTIVE) and performs beam measurements for a cell on a carrier frequency of NR (this may be a frequency outside the synchronization raster, i.e. where other UEs are possibly not camping or in the synchronization raster); This UE resumes or adjusts an LTE connection; Then, during this transition to connected, these early measurements, including beam measurements, can be reported; — The UE in RRC_CONNECTED in NR is suspended or released to the dormant state (e.g., RRC_IDLE or RRC_INACTIVE) and performs beam measurements for a cell on a carrier frequency of NR (this may be a frequency outside the synchronization raster, i.e. where other UEs are possibly not camping or in the synchronization raster); This UE resumes or adjusts an LTE connection; Then, during this transition to connected, these early measurements, including beam measurements, can be reported. — The UE in RRC_CONNECTED in LTE is suspended or released to the dormant state (e.g., RRC_IDLE or RRC_INACTIVE) and performs beam measurements for a cell on a carrier frequency of NR (this may be a frequency outside the synchronization raster, i.e. where other UEs are possibly not camping or in the synchronization raster); This UE resumes or adjusts a connection on the NR; Then, during this transition to connected, these early measurements, including beam measurements, can be reported.

[088] In the methods described in the present invention, the UE can be configured to perform beam measurements at frequencies that are outside the synchronization raster, such as, for example, where a UE may possibly not be camping. As an alternative, the UE can be configured to perform cell-level or carrier-level measurements outside the synchronization raster.

[089] Since a UE can, in some cases, move between different beams quite quickly, the relevance of information about which is the best perceived beam(s) decreases with time from measurement . According to certain embodiments, a method is provided in which the network configures the UE with a threshold for how old beam-level measurements are considered to be useful. The UE can then be configured to only report beam level measurements if the measurements are performed within a configured or defined time period prior to the time of reporting. Alternatively, the UE includes beam level measurements (even if they are old) in the report, but also includes information about how old the measurements are, that is, information about when the reported measurements were performed.

[090] According to certain embodiments, a method performed on a wireless terminal/user equipment (UE) to report early measurement upon transition from a dormant state (e.g., RRC_IDLE with stored context, RRC_IDLE without stored context, RRC_INACTIVE ) for connected, the method includes: — Obtaining from the network a configuration for beam measurement information based on beam measurements performed in a dormant state, where reporting is done upon transition from a dormant state to a connected state .

[091] There may be different alternatives for the UE to obtain the configuration to perform beam measurements while it is in a dormant state.

[092] According to certain embodiments, the UE may receive a dedicated measurement configuration when it is suspended or released into the dormant state. This configuration can be included in an RRC Release message (for example RRCConnectionRelease or RRCRelease). This may contain information currently provided only on measurement objects (such as cell quality derivation parameters such as consolidation thresholds provided by carrier and RS type) and reporting settings such as number of beams to report, measurement quantities for measurements of beam to include, a flag indication that not only beam indices but also measurements should be included, etc.

[093] According to certain embodiments, the beam measurement configuration also has an associated validity timer. This can be the same expiration timer set for cell measurements, also provided as part of the configuration.

[094] According to certain embodiments, the configuration of the beam measurements also has an associated area of validity. This can be the same validity defined for cell measurements, also provided as part of the configuration.

[095] According to certain embodiments, the configuration may contain a list of carriers (e.g., NR carriers, LTE carriers, or both NR and LTE carriers). The UE performs measurements (including beam measurements) for these carriers.

[096] According to certain embodiments, the configuration may contain a list of cells (e.g., for a configured carrier), the UE only performs measurements on the indicated cells.

[097] According to certain embodiments, the configuration may contain a list of beams (e.g., for a configured carrier and/or cell, where the beams may be SSB indices or CSI-RS resource indices), the UE only perform measurements on the indicated beams.

[098] According to certain embodiments, the configuration may contain any parameters as shown above, that is, parameters that would normally be configured only in MeasObjectNR or ReportConfig, and are now being provided in RRCRelease.

[099] According to certain embodiments, this configuration can be defined as highlighted below:

[100] A possible procedural text in the RRC for the proposed method could be as follows: 5.7.6 Idle/Idle Mode Measurements 5.7.6.1 General

[101] This procedure specifies the measurements made by a UE in RRC_IDLE or in RRC_INACTIVE when it has an IDLE/INACTIVE mode measurement configuration and the storage of available measurements by a UE in RRC_IDLE, RRC_INACTIVE and RRC_CONNECTED. 5.7.6.2 Initiation While T331 is being performed, the UE must: 1> perform measurements according to the following: 2> for each entry in measIdleCarrierListNR-r16 within the VarMeasIdleConfig: 3> if the UE supports carrier aggregation and/or or dual connectivity (or any form of MR-DC) between the serving carrier and the carrier frequency indicated by ssbFrequency within the corresponding entry; 4> perform measurements on the carrier frequency and bandwidth indicated by ssbFrequency within the corresponding input; 4> if measCellListNR-r16 is included: 5> consider PCell and cells identified by each entry within measCellListNR-r16 to be applicable for reporting idle/idle measurement; 4> else: 5> consider PCell and up to maxCellMeasIdleNR-r16 identified strongest cells whose RSRP/RSRQ/SINR measurement results are above the value(s) provided in qualityThresholdNR (if any) to be applicable to report idle mode measurement; 4> if reportQuantityRS-Indexes and maxNrofRS- IndexesToReport are included: 5> perform measurements for the measurement quantities indicated in reportQuantityRS-Indexes whose RSRP/RSRQ/SINR measurement results are above the provided value(s)( s) in absThreshSS-BlocksConsolidation or absThreshCSI-RS-Consolidation (if applicable); 4> store measurement results for applicable cells to report idle mode measurement within VarMeasIdleReport; 3>otherwise: 4>do not consider the carrier frequency to be applicable for reporting idle/inactive mode measurement; 2> for each entry in measIdleCarrierListEUTRA within VarMeasIdleConfig: 3> whether the UE supports carrier aggregation between the serving carrier and the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry; 4> perform measurements on the carrier frequency and bandwidth indicated by carrierFreq and allowedMeasBandwidth within the corresponding entry; NOTE: The s-NonIntraSearch fields in SystemInformationBlockType3 do not affect UE measurement procedures in IDLE mode. How the UE performs measurements in IDLE mode depends on the UE implementation, as long as the requirements of TS 36.133 [16] are met for measurement reporting. The UE is not required to perform idle measurements if the idle measurement indication SIB2 is not configured. 4> if measCellList is included: 5> consider PCell and cells identified by each entry within measCellList to be applicable for reporting idle mode measurement; 4> else: 5> consider PCell and up to maxCellMeasIdle strongest identified cells whose RSRP/RSRQ measurement results are above the value(s) provided in qualityThreshold (if any) to be applicable for reporting measurement of idle mode; 4> store measurement results for applicable cells to report idle mode measurement within VarMeasIdleReport; 3>otherwise: 4>do not consider the applicable carrier frequency to report measurement in idle mode; 1> If ValidityArea is configured in VarMeasIdleConfig and UE reselects for a serving cell whose physical cell identity (which can be an NR cell or an LTE cell or a combination of NR and LTE cells) does not match any entry in ValidityArea for the corresponding carrier frequency: 2> stop T331; 5.7.6.3 T331 expires or stops The UE must: 1> if T331 expires or is stopped: 2> release the VarMeasIdleConfig, including beam and cell measurements;

[102] According to other certain embodiments, the UE may obtain configuration for INACTIVE/IDLE measurements for initial reporting upon transition from dormant to connected in the system information of each cell that the UE selects (e.g., upon transition to the state dormant) or reselect again (while the UE moves in the dormant state and performs cell reselection). The UE may obtain indication in the suspend/release procedure (for example, in a configuration in an RRC Release type message), but the UE obtains the measurement configuration in the system information to perform the idle/inactive measurements to be recorded and later possibly reported during the state transition. The UE can obtain the measurement configuration for these idle/inactive measurements in SIB2 and/or SIB4 (in case of inter-frequency measurements).

[103] In a particular embodiment, in SIB2, the UE can obtain common parameters for interfrequency and intrafrequency, while in SIB4, the UE can obtain parameters to perform measurements at a given carrier frequency, where parameters are also provided by frequency.

[104] In a particular embodiment, the UE can also obtain only measurement parameters in SIB4 for the carrier possibly configured in dedicated signaling. For example, in one variant, the UE receives a list of carriers in dedicated signaling but without measurement parameters (e.g. without CQD settings, thresholds, etc.), but obtains these parameters by combining the same carrier by obtaining parameters in SIB4.

[105] SIB2, for example, contains CQD parameters and additional parameters related to beam measurements and beam reports, as shown below: - SIB2

[106] SIB2 contains common cell reselection information for intra-frequency, inter-frequency and/or inter-RAT cell reselection (i.e., applicable for more than one type of cell reselection, but not necessarily all), as well as reselection information of intrafrequency cells that are not related to the neighboring cell. Also contains configuration for idle/idle measurements to possibly be reported during transitions to connected, if requested by the network and if available.

[107] SIB4 contains information relevant only for interfrequency cell reselection, that is, information about other NR frequencies and neighboring interfrequency cells relevant for cell reselection. IE includes common cell reselection parameters for a frequency as well as cell-specific reselection parameters.

[108] According to certain embodiments, a wireless device or UE may be configured to report to the network, beam measurement information based on beam measurements performed in a dormant state, where the report is made upon transition from a state dormant to the connected state.

[109] The reporting of measurement information can be manipulated by including beam measurement information in the UE Information Response type message, for example, upon a network request. The request can be generic, for measurements performed in idle/inactive mode, or specific for beam reporting. For example, the network can request measurements without beam reporting or with beam reporting.

[110] The inclusion of beam measurement information in early measurements upon transition to connected (e.g., to be included in the UE Information Response type message) may be based on configured parameters (e.g., configured in the RRC Release when the EU has been suspended). For example, the UE may include only the best beam and/or best beams above a configurable threshold for a given measurement quantity (e.g., RSRP, RSRQ, SINR, etc.).

[111] An implementation in the RRC specifications is provided below, in which at least one of the parameters provided in the dedicated configuration controls how beam measurement information is included in reports: 5.6.7 UE Information 5.6.7.1 General

[112] The UE information procedure is used by NG-RAN to request the UE to report information (e.g., cell and beam measurements). 5.6.7.2 Initiation

[113] NG-RAN starts the procedure by sending the UEInformationRequest message. The NG-RAN must initiate this procedure only after successful security activation. 5.6.7.3 Receiving the UEInformationRequest message

[114] Upon receipt of the UEInformationRequest message, the UE must, only after successful security activation: ... 1> if the idleModeMeasurementReq is included in the UEInformationRequest and the UE has stored VarMeasIdleReport: 2> adjust the measResultListIdleInactive in the UEInformationResponse message for the value of idleInactiveMeasReport in VarMeasIdleInactiveReport; 2> discard the VarMeasIdleReport after successful delivery of the UEInformationResponse message confirmed by the lower layers; 2> forward the UEInformationResponse message to lower layers for transmission via SRB1; 1> adjust the rsIndexResults to include up to maxNrofRS- IndexesToReport SS/PBCH block indices or CSI-RS indices in descending order of sort quantity as follows: 2> if the measurement information to be included is based on the SS/PBCH: 3> include within the resultsSSB-Indexes the index associated with the best beam for that amount of SS/PBCH block ordering and if absThreshSS-BlocksConsolidation is included in the VarMeasConfig for the measObject associated with the cell for which the beams should be reported, the remaining beams whose ordering quantity is above absThreshSS-BlocksConsolidation; 3> if includeBeamMeasurements is configured, include the SS/PBCH-based measurement results for the quantities in reportQuantityRS-Indexes set to TRUE for each SS/PBCH block index; 2> else if the beam measurement information to be included is based on CSI-RS: 3> include within the resultsCSI-RS-Indexes the index associated with the best beam for that CSI-RS ordering quantity and, if absThreshCSI- RS-Consolidation is included in the VarMeasConfig for the measObject associated with the cell for which beams are to be reported, the remaining beams whose ordering quantity is above absThreshCSI-RS-Consolidation; 3> if includeBeamMeasurements is configured, include the CSI-RS based measurement results for the quantities in reportQuantityRS-Indexes set to TRUE for each CSI-RS index.

[115] FIGURE 11 illustrates an exemplary wireless network according to some embodiments. Although the subject matter described in the present invention can be implemented in any suitable type of system using any suitable components, the embodiments disclosed in the present invention are described with respect to a wireless network, such as the exemplary wireless network illustrated in FIGURE 11. By For simplicity, the wireless network of FIGURE 11 depicts only the network 106, the network nodes 160 and 160b, and the wireless devices 110, 110b and 110c. In practice, a wireless network may additionally include any additional elements suitable to support communication between wireless devices or between a wireless device and another communicating device, such as a landline telephone, a service provider or any other communication node. network or end device. Among the illustrated components, the network node 160 and the wireless device 110 are depicted in additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate access and/or use of the wireless devices to services provided by, or via, the wireless network.

[116] The wireless network can comprise and/or interface with any type of communication, telecommunications, data, cellular and/or radio network or other type of similar system. In some embodiments, the wireless network may be configured to operate in accordance with specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE) and/or other 2G, 3G, 4G, or 5G; wireless local area network (WLAN) standards, such as IEEE 802.11 standards; and/or any other appropriate wireless communications standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

[117] Network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide area networks (WANs), wide area networks local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks to enable communication between devices.

[118] Network node 160 and wireless device 110 comprise various components described in more detail below. Such components work together to provide functionality to the network node and/or wireless device, such as providing wireless connections in a wireless network. In different embodiments, the wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or any other components or systems that may facilitate or participate in communication. of data and/or signals via wired or wireless connections.

[119] FIGURE 12 illustrates an example of network node 160, according to certain embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment on the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) on the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node B, Evolved Node B (eNBs) ) and NR Node B (gNBs)). Base stations can be categorized based on the amount of coverage they provide (or, in other words, their transmit power level) and can also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station can be a relay node or a relay donor node that controls 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 and/or remote radio units (RRUs), sometimes referred to as remote radio heads (RRHs). Such remote radio units may or may not be integrated into an antenna as an antenna-integrated radio. Parts of a distributed base station can also be referred to as nodes in a distributed antenna system (DAS). Still additional examples of network nodes include multistandard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multicell/multicast coordination entities (MCEs), core network nodes (e.g. MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g. E-SMLCs ) and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged and/or operable to enable and/or provide a wireless device with access to the wireless network or provide some service. to a wireless device that has accessed the wireless network.

[120] In FIGURE 12, network node 160 includes processing circuitry 170, device-readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although the Network node 160 illustrated in the exemplary wireless network of FIGURE 12 may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It should be understood that a network node comprises any suitable combination of hardware and/or software necessary to perform tasks, resources, functions and methods disclosed in the present invention. Furthermore, while the components of network node 160 are depicted as single boxes located within a larger box or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., For example, device-readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[121] Similarly, network node 160 may be composed of multiple physically separated components (e.g., a Node B component and an RNC component or a BTS component and a BSC component, etc.), which They can each have their own components. In certain scenarios in which network node 160 comprises multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among multiple network nodes. For example, a single RNC can control multiple NodeBs. In such a scenario, each unique pair of NodeB and RNC can in some cases be considered a single separate network node. In some embodiments, network node 160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable medium 180 for the different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies integrated with network node 160, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or a different chip or chip set and other components in the network node 160.

[122] The processing circuitry 170 is configured to perform any determining, calculating or related operations (e.g., certain obtaining operations) described in the present invention as being provided by a network node. These operations performed by the processing circuitry set 170 may include processing information obtained by the processing circuitry set 170, 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 information obtained or converted and as a result of said processing making a determination.

[123] The processing circuitry 170 may comprise a combination of one or more of microprocessors, controllers, microcontrollers, central processing units, digital signal processors, application-specific integrated circuits, field-programmable gate arrays, or any other Suitable computing device, resource, or combination of hardware, software, and/or coded logic operable to provide, alone or in conjunction with other components of network node 160, such as device-readable medium 180, the functionality of network node 160 For example, the processing circuitry 170 may execute instructions stored on the device-readable medium 180 or in memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed. in the present invention. In some embodiments, the processing circuitry 170 may include a system on a chip (SOC).

[124] In some embodiments, the processing circuitry 170 may include one or more radio frequency (RF) transceiver circuitry sets 172 and baseband processing circuitry sets 174. In some embodiments, the radio frequency (RF) transceiver circuitry sets 174. radio frequency (RF) 172 and baseband processing circuitry sets 174 may be on separate chips (or chip sets), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or set of chips, boards, or units.

[125] In certain embodiments, some or all of the functionality described in the present invention as being provided by a network node, base station, eNB or other network device may be performed by processing circuitry 170 executing instructions stored on the readable medium by device 180 or memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170 without executing instructions stored on a separate or discrete device-readable medium, such as an innate (hard-wired) way. In any of these embodiments, whether executing instructions stored on a device-readable storage medium or not, the processing circuitry 170 may be configured to perform the described functionality. The benefits provided by this functionality are not limited to the processing circuitry 170 individually or other components of network node 160, but are enjoyed by the network node 160 as a whole and/or by end users and the wireless network in general.

[126] Device-readable medium 180 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, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., a hard drive), removable storage media (e.g., a flash drive, a Compact Disc (CD), or a Digital Video Disk (DVD)) and/or any other computer executable and/or device readable non-transient, volatile or non-volatile memory devices that store information, data and/or instructions that can be used by the processing circuitry 170. Device-readable medium 180 may store any suitable instructions, data or information, including a computer program, software, an application that includes one or more logic, rules, code, tables, etc. and/or other instructions capable of being executed by the processing circuitry 170 and used by the network node 160. The device-readable medium 180 may be used to store any calculations made by the processing circuitry 170 and/or any data received via interface 190. In some embodiments, the processing circuitry 170 and the device-readable medium 180 may be considered as integrated.

[127] Interface 190 is used in wired or wireless signaling and/or data communication between network node 160, network 106, and/or wireless devices 110. As illustrated, interface 190 comprises port(s) /terminal(s) 194 to send and receive data, for example, to and from network 106 via a wired connection. Interface 190 also includes radio front end circuitry 192 that may be coupled to, or, in certain embodiments, be a part of, antenna 162. Radio front end circuitry 192 comprises filters 198 and amplifiers 196. of radio front end circuitry 192 may be connected to an antenna 162 and a set of processing circuitry 170. The set of radio front end circuitry may be configured to condition signals communicated between the antenna 162 and the set of processing circuitry. processing 170. Radio front end circuitry 192 may receive digital data that is to be sent to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 192 can convert the digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of filters 198 and/or amplifiers 196. The radio signal can then be transmitted via antenna 162. Similarly, when receiving data, antenna 162 may collect radio signals which are then converted into digital data by radio front end circuitry 192. The digital data may be passed to the radio front end circuitry. processing 170. In other embodiments, the interface may comprise different components and/or different combinations of components.

[128] In certain alternative embodiments, network node 160 may not include separate radio front end circuitry 192, rather, processing circuitry 170 may comprise radio front end circuitry and may be connected to antenna 162 without separate radio front end circuitry 192 . Similarly, in some embodiments, all or some of the RF transceiver circuitry 172 may be considered a part of the interface 190. In still other embodiments, the interface 190 may include one or more ports or terminals 194, front circuitry set. radio end 192 and RF transceiver circuitry 172 as part of a radio unit (not illustrated) and interface 190 may communicate with baseband processing circuitry 174, which is part of a digital unit (not illustrated).

[129] Antenna 162 may include one or more antennas or antenna arrays configured to send and/or receive wireless signals. The antenna 162 may be coupled to the radio front end circuitry 192 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, the antenna 162 may comprise one or more omnidirectional, sector, or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omnidirectional antenna may be used to transmit/receive radio signals. radio in any direction, a sector antenna can be used to transmit receive radio signals to and from devices within a specific area and a panel antenna can be a line-of-sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be termed as MIMO. In certain embodiments, the antenna 162 may be separate from the network node 160 and may be connectable to the network node 160 through an interface or port.

[130] The antenna 162, the interface 190 and/or the processing circuitry 170 may be configured to perform any receive operations and/or certain obtain operations described in the present invention as being performed by a network node. Any information, data and/or signals may be received from a wireless device, another network node and/or any other network equipment. Similarly, the antenna 162, the interface 190, and/or the processing circuitry 170 may be configured to perform any transmission operations described in the present invention as being performed by a network node. Any information, data and/or signals may be transmitted to a wireless device, another network node and/or any other network equipment.

[131] The power circuitry 187 may comprise or be coupled to a power management circuitry and is configured to supply components of the network node 160 with power to perform the functionality described in the present invention. The power circuitry 187 may receive power from the power source 186. The power source 186 and/or the power circuitry 187 may be configured to provide power to the various components of the network node 160 in an appropriate manner. for the respective components (e.g. at the voltage and current level required for each respective component). The power source 186 may be included in or external to a power circuitry 187 and/or network node 160. For example, the network node 160 may be connectable to an external power source (e.g., an electrical outlet). of electricity) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to the power circuitry 187. As a further example, the power source 186 may comprise a power source in the form of a battery or battery pack connected or integrated into the power circuitry 187. The battery can provide backup power if the external power source fails. Other types of power sources can also be used, such as photovoltaic devices.

[132] Alternative embodiments of the network node 160 may include additional components beyond those shown in FIGURE 12, which may be responsible for providing certain aspects of the functionality of the network node, including any of the functionality described in the present invention and/or any functionality necessary to support the matter described in the present invention. For example, network node 160 may include user interface equipment to allow information to be input to network node 160 and to allow information to be output from network node 160. This may allow the user to perform diagnostics, maintenance, repair and other administrative functions for network node 160.

[133] FIGURE 13 illustrates an example of wireless device 110, according to certain embodiments. As used in the present invention, wireless device refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise indicated, the term wireless device may be used in the present invention interchangeably with user equipment (UE). Wireless mode communication may involve the transmission and/or reception of wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for carrying information through the air. In some embodiments, a wireless device may be configured to transmit and/or receive information without direct human interaction. For example, a wireless device may be designed to transmit information to a network at a predetermined schedule when triggered by an internal or external event or in response to requests from the network. Examples of a wireless device include, but are not limited to, a smartphone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless camera, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless terminal point, a mobile station, a tablet, a laptop, a laptop embedded equipment (LEE), a laptop mounted equipment (LME), a smart device, a wireless customer premises equipment (CPE), a vehicle mounted wireless terminal device, etc. A wireless device can support device-to-device (D2D) communication, for example, by implementing a 3GPP standard for sidelink, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) communication, and can in this case be referred to as a D2D communication device. As another specific example, in an Internet of Things (IoT) scenario, a wireless device 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 wireless device. and/or a network node. The wireless device may in this case be a machine-to-machine (M2M) device which, in a 3GPP context, may be referred to as an MTC device. As a particular example, the wireless device may be a UE implementing the 3GPP narrowband internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, measuring devices such as power meters, industrial machines or household or personal appliances (e.g. refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.) . In other scenarios, a wireless device may represent a vehicle or other equipment that is capable of monitoring and/or reporting its operational status or other functions associated with its operation. A wireless device as described above may represent the terminal point of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a wireless device as described above may be mobile; in this case it may also be referred to as a mobile device or a mobile terminal.

[134] As illustrated, the wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and circuitry assembly of power 137. The wireless device 110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by the wireless device 110, such as, for example, GSM, WCDMA, LTE, NR, WiFi, wireless technologies. WiMAX or Bluetooth, to name just a few. These wireless technologies may be integrated into the same or different chips or chip sets as the other components within the wireless device 110.

[135] Antenna 111 may include one or more antennas or antenna arrays configured to send and/or receive wireless signals and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from wireless device 110 and be connectable to the wireless device through an interface or port. The antenna 111, the interface 114 and/or the processing circuitry 120 may be configured to perform any reception or transmission operation described in the present invention as being performed by a wireless device. Any information, data and/or signals may be received from a network node and/or other wireless device. In some embodiments, the radio front end circuitry and/or the antenna 111 may be considered as an interface.

[136] As illustrated, interface 114 comprises radio front end circuitry 112 and antenna 111. Radio front end circuitry 112 comprises one or more filters 118 and amplifiers 116. Radio front end circuitry 112 is connected to the antenna 111 and the processing circuitry 120 and is configured to condition signals communicated between the antenna 111 and the processing circuitry 120. The radio front end circuitry 112 may be coupled to, or be a part of the antenna 111. In certain embodiments, the wireless device 110 may not include separate radio front end circuitry sets 112; instead, the processing circuitry 120 may comprise a radio front end circuitry and may be connected to the antenna 111. Similarly, in some embodiments, part or all of the RF transceiver circuitry 122 may be considered as a part of interface 114. Radio front end circuitry 112 can receive digital data that is to be sent to other network nodes or wireless devices via a wireless connection. Radio front end circuitry 112 may convert the digital data into a radio signal with the appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116. The radio signal may then be transmitted via antenna 111. Similarly, when receiving data, antenna 111 may collect radio signals which are then converted into digital data by radio front end circuitry 112. The digital data may be passed to the radio front end circuitry. processing 120. In other embodiments, the interface may comprise different components and/or different combinations of components.

[137] The processing circuitry 120 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field-programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or coded logic operable to provide, alone or in conjunction with other components of wireless device 110, such as device-readable medium 130, wireless device functionality 110. Such functionality may include providing any of the various wireless features or benefits discussed in the present invention. For example, the processing circuitry 120 may execute instructions stored on the device-readable medium 130 or in memory within the processing circuitry 120 to provide the functionality disclosed in the present invention.

[138] As illustrated, processing circuitry 120 includes one or more RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126. In other embodiments, the set of of processing circuits may comprise different components and/or different combinations of components. In certain embodiments, the processing circuitry 120 of wireless device 110 may comprise a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or chip sets. In alternative embodiments, all or part of the baseband processing circuitry set 124 and the application processing circuitry set 126 may be combined on a chip or chip set and the RF transceiver circuitry set 122 may be on a chip or separate chip set. In still alternative embodiments, part or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or chipset, and the application processing circuitry 126 may be in a separate chip or chip set. In still other alternative embodiments, part or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined on the same chip or chip set. In some embodiments, the RF transceiver circuitry 122 may be a part of the interface 114. The RF transceiver circuitry 122 may condition RF signals to the processing circuitry 120.

[139] In certain embodiments, some or all of the functionality described in the present invention as being performed by a wireless device may be provided by the processing circuitry 120 executing instructions stored on the device-readable medium 130, which, in certain embodiments , may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 120 without executing instructions stored on a separate or discrete device-readable storage medium, such as in an innate manner. In any of these particular embodiments, whether executing instructions stored on a device-readable storage medium or not, the processing circuitry 120 may be configured to perform the described functionality. The benefits provided by this functionality are not limited to the processing circuitry 120 individually or other components of the wireless device 110, but are enjoyed by the wireless device 110 as a whole and/or by end users and the wireless network in general.

[140] The processing circuitry 120 may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described in the present invention as being performed by a wireless device. These operations, as performed by the processing circuitry set 120 may include processing information obtained by the processing circuitry set 120, for example, converting the obtained information into other information, comparing the obtained information or converted information with information stored by the device without wire 110 and/or performing one or more operations based on the information obtained or converted and as a result of said processing making a determination.

[141] The device-readable medium 130 may be operable to store a computer program, software, an application that includes one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry 120. Device-readable medium 130 may include computer memory (e.g., Random Access Memory (RAM) or Read-Only Memory (ROM)), media mass storage media (e.g., a hard drive), removable storage media (e.g., a Compact Disc (CD) or a Digital Video Disc (DVD)), and/or any other computer-executable memory devices and/or or non-transient, non-volatile or device-readable media that store information, data and/or instructions that can be used by the processing circuitry sets 120. In some embodiments, the processing circuitry set 120 and the device-readable medium 130 can be considered as integrated.

[142] The user interface equipment 132 may provide components that allow a human user to interact with the wireless device 110. Such interaction may take various forms, such as visual, auditory, tactile, etc. The user interface equipment 132 may be operable to produce output to the user and allow the user to provide input to the wireless device 110. The type of interaction may vary depending on the type of user interface equipment 132 installed on the wireless device. wire 110. For example, if the wireless device 110 is a smartphone, the interaction may occur via a touch screen; If the wireless device 110 is a smart meter, the interaction may be through a display that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if a smoke). User interface equipment 132 may include input interfaces, devices, and circuits and output interfaces, devices, and circuits. The user interface equipment 132 is configured to allow information to be input to the wireless device 110 and is connected to the processing circuitry 120 to allow the processing circuitry 120 to process the input information. User interface equipment 132 may include, for example, a microphone, a proximity sensor or the like, keys/buttons, a touch display, one or more cameras, a USB port, or other set of input circuitry. The user interface equipment 132 is also configured to allow the output of information from the wireless device 110 and to allow the processing circuitry 120 to output information from the wireless device 110. The user interface equipment 132 may include, for example, a speaker, a display, a set of vibrating circuitry, a USB port, a headphone interface, or other set of output circuitry. Using one or more interfaces, devices, and input and output circuitry of user interface equipment 132, wireless device 110 may communicate with end users and/or the wireless network and allow them to benefit from the functionality described herein. invention.

[143] Ancillary equipment 134 is operable to provide more specific functionalities, which generally cannot be performed by wireless devices. This may comprise specialized sensors to take measurements for various purposes, interfaces for additional types of communication such as wired communications, etc. The inclusion and type of auxiliary equipment components 134 may vary depending on the embodiment and/or scenario.

[144] The power source 136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g. an electrical outlet), photovoltaic devices or power cells, can also be used. The wireless device 110 may further comprise power circuitry 137 for delivering power from the power source 136 to the various parts of the wireless device 110 that require power from the power source 136 to perform any functionality described or indicated in present invention. The power circuitry assemblies 137 may, in certain embodiments, comprise power management circuitry assemblies. The power circuitry 137 may additionally or alternatively be operable to receive power from an external power source; In which case, the wireless device 110 may be connectable to the external power source (such as an electrical outlet) via input circuitry or an interface such as an electrical power cable. The power circuitry 137 may also, in certain embodiments, be operable to deliver power from an external power source to the power source 136. This may be, for example, to charge the power source 136. Power circuitry 137 may perform any formatting, conversion, or other modification to the power of the power source 136 to make it suitable for the respective components of the wireless device 110 to which the power is supplied.

[145] FIGURE 14 illustrates an embodiment of a UE in accordance with various aspects described in the present invention. As used in the present invention, a user equipment or 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 or operation by a human user, but which may be, or may not be, initially 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 or operation by an end user, but that may be associated with or operated for the benefit of a user (e.g., a smart power meter). The UE 2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine-type communication (MTC) UE, and/or an enhanced MTC UE (eMTC). The UE 200, as illustrated in FIGURE 14, is an example of a wireless device configured to communicate in accordance with one or more communication standards promulgated by the 3rd Generation Partnership Project (3GPP), such as the GSM, UMTS , LTE and/or 5G from 3GPP. As mentioned previously, the term wireless device and UE can be used interchangeably. Accordingly, although FIGURE 14 is a UE, the components discussed in the present invention are equally applicable to a wireless device and vice versa.

[146] In FIGURE 14, the UE 200 includes set of processing circuits 201 that are operatively coupled to the input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including access memory random memory (RAM) 217, read-only memory (ROM) 219 and storage medium 221 or the like, communication subsystem 231, power source 213 and/or any other component, or any combination thereof. Storage medium 221 includes operating system 223, application program 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Certain UEs may utilize all of the components shown in FIGURE 14, or only a subset of the components. The level of integration between components may vary from one UE to another UE. Additionally, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[147] In FIGURE 14, the set of processing circuits 201 can be configured to process data and computer instructions. The processing circuitry 201 may be configured to implement any sequential state machine operation to execute machine instructions stored as machine-readable computer programs in memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with the appropriate firmware; one or more stored 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, processing circuitry 201 may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

[148] In the depicted embodiment, the input/output interface 205 may be configured to provide a communication interface to an input device, output device, or input and output device. The UE 200 may be configured to use an output device via input/output interface 205. An output device may use the same type of interface port as an input device. For example, a USB port may be used to provide input and output from the UE 200. The output device may be 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. The UE 200 may be configured to use an input device via input/output interface 205 to allow a user to capture information on the UE 200. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g. example, a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a control ball, 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 detect input from a user. A sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another similar sensor or any combination thereof. For example, the input device can be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

[149] In FIGURE 14, the RF interface 209 can be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. Network connection interface 211 may be configured to provide a communication interface for network 243a. Network 243a may encompass wired and/or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a telecommunications network, another similar network or any combination thereof. For example, network 243a may comprise a Wi-Fi network. Network connection interface 211 may be configured to include a receiver and a transmit interface used to communicate with one or more other devices over a communication network. according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM or the like. Network connection interface 211 may implement appropriate receiver and transmitter functionality for communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuitry, software, or firmware components, or alternatively, they may be implemented separately.

[150] The RAM 217 may be configured to interface via the bus 202 to the processing circuitry 201 to provide storage or caching of data or computer instructions during the execution of software programs, such as the operating system, programs application and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuitry 201. For example, ROM 219 may be configured to store low-level invariant system code or data for basic system functions, such as input and basic output (I/O), initialization, or reception of keystrokes from a keyboard that are stored in non-volatile memory. The storage medium 221 may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), programmable erasable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical discs, floppy disks, hard drives, removable cartridges or flash drives. In one example, the storage medium 221 may be configured to include the operating system 223, the application program 225, such as a web browser application, a widget or gadget engine, or other application, and data file 227. The medium storage space 221 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[151] The storage medium 221 may be configured to include a series of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, thumb drive, etc. drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, digital holographic data storage optical disc drive ( HDDS), external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external microDIMM SDRAM, smartcard memory, such as a subscriber identity module or a removable user identity module ( YES/BAD), other memory or any combination thereof. The storage medium 221 may allow the UE 200 to access computer-executable instructions, application programs, or the like, stored in transient or non-transitory memory media, to off-load or upload data. An article of manufacture, such as one utilizing a communication system, may be tangibly incorporated into the storage medium 221, which may comprise a device-readable medium.

[152] In FIGURE 14, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. Network 243a and network 243b may be the same network or networks or a network or networks many different. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another wireless device, UE, or base station of a network. radio access system (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax or the like. Each transceiver may include transmitter 233 and/or receiver 235 to implement transmitter or receiver functionality, respectively, appropriate for the RAN links (e.g., frequency allocations and the like). Additionally, the transmitter 233 and receiver 235 of each transceiver may share circuitry, software, or firmware components or, alternatively, may be implemented separately.

[153] In the illustrated embodiment, the communication functions of the communication subsystem 231 may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, field proximity communication, location-based communication such as use of the global positioning system (GPS) to determine a location, other related communication function, or any combination thereof. For example, communication subsystem 231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network 243b may encompass wired and/or wireless networks, such as a local area network (LAN), a geographically distributed network (WAN), a computer network, a wireless network, a telecommunications network, another related network, or any combination thereof. For example, network 243b may be a cellular network, a Wi-Fi network, and/or a near-field network. The power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to components of the UE 200.

[154] The features, benefits and/or functions described in the present invention can be implemented in one of the components of the UE 200 or partitioned across multiple components of the UE 200. Furthermore, the features, benefits and/or functions described in the present invention can be implemented in any combination of hardware, software or firmware. In one example, communications subsystem 231 may be configured to include any of the components described in the present invention. Additionally, processing circuitry 201 may be configured to communicate with any of such components via bus 202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the set of processing circuits 201, perform the corresponding functions described in the present invention. In another example, the functionality of any of these components may be partitioned between the processing circuitry 201 and the communications subsystem 231. In another example, the non-computationally intensive functions of any of these components may be implemented in software or firmware. and computationally intensive functions can be implemented in hardware.

[155] FIGURE 15 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualization means creating virtual versions of appliances or devices which may include virtualization hardware platforms, storage devices and network resources. As used in the present invention, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or components thereof and refers to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., through one or more applications, components, functions, virtual machines or containers running one or more physical processing nodes on one or more networks).

[156] In some embodiments, some or all of the functions described in the present invention may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. Additionally , in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), the network node may then be fully virtualized.

[157] The functions may be implemented by one or more applications 320 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions and/or benefits of some of the embodiments disclosed in the present invention. Applications 320 are performed in virtualization environment 300, which provides hardware 330 comprising processing circuitry 360 and memory 390. Memory 390 contains instructions 395 executable by processing circuitry 360, whereby application 320 is operative to provide one or more of the features, benefits and/or functions disclosed in the present invention.

[158] Virtualization environment 300 comprises general-purpose or special-purpose networking hardware devices 330 comprising a set of one or more processors or sets of processing circuits 360, which may be commercial off-the-shelf (COTS) processors, circuits Dedicated Application Specific Integrated ASICs (ASICs), or any other type of processing circuitry, including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory 390-1, which may be non-persistent memory for temporarily storing instructions 395 or software executed by processing circuitry 360. Each hardware device may comprise one or more network interface controllers. (NICs) 370, also known as network interface cards, which include physical network interface 380. Each hardware device may also include non-transitory, persistent, machine-readable storage media 390-2 having software 395 stored thereon. and/or instructions executable by processing circuitry 360. Software 395 may include any type of software, including software for instantiating one or more virtualization layers 350 (also referred to as hypervisors), software for running virtual machines 340, as well as software that allows you to perform functions, features and/or benefits described in connection with some embodiments described in the present invention.

[159] Virtual machines 340 comprise virtual processing, virtual memory, virtual networking or interface, and virtual storage and may be realized by a virtualization layer 350 or corresponding hypervisor. Different embodiments of the virtual appliance instance 320 can be deployed to one or more of the virtual machines 340 and the deployments can be done in different ways.

[160] During operation, the processing circuitry 360 runs software 395 to instantiate the hypervisor or virtualization layer 350, which may sometimes be referred to as a virtual machine monitor (VMM). The virtualization layer 350 may present a virtual operating platform that appears as networking hardware for the virtual machine 340.

[161] As shown in FIGURE 15, hardware 330 may be a stand-alone network node with generic or specific components. Hardware 330 may comprise antenna 3225 and may implement some functions via virtualization. Alternatively, the hardware 330 may be part of a larger hardware cluster (e.g., such as in a data center or customer on-premises equipment (CPE)), where many hardware nodes work together and are managed via management and orchestration ( MANO) 3100, which, among others, oversee the lifecycle management of 320 applications.

[162] Hardware virtualization is, in some contexts, known as network function virtualization (NFV). NFV can be used to consolidate many types of networking equipment into industry-standard high-volume server hardware, physical switches, and physical storage, which can be located in data centers and equipment within customer premises.

[163] In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that performs programs as if they were on a non-virtualized physical machine. Each of the virtual machines 340 and that portion of the hardware 330 that runs that virtual machine, whether hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with other of the virtual machines 340, forms separate virtual network elements (VNE). .

[164] Still in the context of NFV, the Virtual Network Function (VNF) is responsible for handling specific network functions that are performed in one or more virtual machines 340 on top of the hardware network 330 and corresponds to the application 320 in FIGURE 15 .

[165] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with hardware nodes 330 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 radio access node or a base station.

[166] In some embodiments, some signaling may be effected using control system 3230 which may alternatively be used for communication between hardware nodes 330 and radio units 3200.

[167] Any appropriate steps, methods, features, functions or benefits disclosed in the present invention can be performed through one or more functional units or modules of one or more virtual appliances. Each virtual appliance can comprise several of these functional units. These functional units may be implemented via a processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, devices flash memory, optical storage devices, etc. The program code stored in memory includes program instructions for executing one or more telecommunications and/or data communication protocols, as well as instructions for carrying out one or more of the techniques described in the present invention. In some implementations, the processing circuitry may be used to cause the respective functional unit to perform corresponding functions in accordance with one or more embodiments of the present disclosure.

[168] FIGURE 16 illustrates an exemplary method 400 for reporting measurement performed by a wireless device 110, in accordance with certain embodiments. The method begins at step 402 when the wireless device 110 obtains a beam measurement configuration from a network. In step 404, based on the beam measurement configuration, the wireless device 110 performs at least one beam measurement while operating in a dormant state. In step 406, the wireless device 110 reports a result of the at least one beam measurement to the network. The report is made after a transition from the dormant state to a connected state.

[169] In a particular embodiment, the dormant state includes one of, an RRC_IDLE with stored context, RRC_IDLE without stored context state, or RRC_INACTIVE state.

[170] In a particular embodiment, the at least one beam measurement includes at least one measurement performed on at least one reference signal that is beamformed by the network. The at least one reference signal includes at least one SSB and one CSI-RS resource.

[171] In a particular embodiment, the at least one beam measurement comprises at least one: RSRP, RSRQ or SINR.

[172] In a particular embodiment, the result of at least one beam measurement is reported in a RadioResourceControlResumeComplete message.

[173] In a particular embodiment, the result of at least one beam measurement is reported in a UEInformationResponse message.

[174] In a particular embodiment, obtaining the beam measurement configuration includes receiving a message comprising the beam measurement configuration. The message indicates that the wireless device must transition to the dormant state.

[175] In a particular embodiment, performing at least one beam measurement during dormant state operation includes performing at least one beam measurement at a per-cell and/or per-carrier frequency while in the dormant state.

[176] In a particular embodiment, performing the at least one beam measurement while operating in the dormant state includes performing at least one beam measurement on at least one cell or carrier having SSBs outside a synchronization raster while in the dormant state. Put another way, beam measurements are performed outside of the synchronization raster.

[177] In a particular embodiment, the beam measurement configuration is obtained from a source network node and the report of the result of the at least one beam measurement is transmitted to a destination network node that is different from a source node.

[178] In a particular embodiment, the beam measurement configuration is obtained from a network node and the report of the result of the at least one beam measurement is transmitted to the network node. In this scenario, the network node is a source network node.

[179] In certain embodiments, the method for reporting measurement, as described above, may be performed by a virtual computing device. FIGURE 17 illustrates an exemplary virtual computing device 500 for reporting measurement, in accordance with certain embodiments. In certain embodiments, the virtual computing device 500 may include modules for performing steps similar to those described above with respect to the method illustrated and described in FIGURE 16. For example, the virtual computing device 500 may include an obtainment module 502, a performance module 504, a reporting module 506, and any other modules suitable for measurement reporting. In some embodiments, one or more of the modules may be implemented using the processing circuitry 120 of FIGURE 13. In certain embodiments, the functions of two or more of the various modules may be combined into a single module.

[180] The acquisition module 502 may perform the functions of obtaining the virtual computing device 500. For example, in a particular embodiment, the acquisition module 502 may obtain a beam measurement configuration from a network.

[181] The performance module 504 may perform the performance functions of the virtual computing device 500. For example, in a particular embodiment, based on the beam measurement configuration, the performance module 504 may perform at least one beam measurement. beam while operating in a dormant state.

[182] The reporting module 506 may perform the reporting functions of the virtual computing device 500. For example, in a particular embodiment, the reporting module 506 may report a result of the at least one beam measurement to the network. The report is made after a transition from the dormant state to a connected state.

[183] Other embodiments of the virtual computing device 500 may include additional components beyond those shown in FIGURE 17, which may be responsible for providing certain aspects of functionality of the wireless device, including any of the functionality described above and/or any additional functionality (including any functionality required to support the solutions described above). The various different types of wireless devices 110 may include components having the same physical hardware, but configured (e.g., via programming) to support different radio access technologies, or may represent partially or entirely different physical components.

[184] FIGURE 18 illustrates an exemplary method 600 by a network node 115, such as a base station, for configuring the measurement report, according to certain embodiments. The method begins at step 602 when the base station transmits a beam measurement configuration to a wireless device. The beam measurement configuration configures the wireless device to perform at least one beam measurement while the wireless device operates in a dormant state. In step 604, the base station receives, from the wireless device, a report of a result of the at least one beam measurement. The report is received after a wireless device transitions from a dormant state to a connected state.

[185] In a particular embodiment, the dormant state comprises one of: An RRC_IDLE with stored context state, an RRC_IDLE with no stored context state, or an RRC_INACTIVE state.

[186] In a particular embodiment, the at least one beam measurement includes at least one measurement performed on at least one reference signal that is beamformed by the network. The at least one reference signal includes at least one SSB and one CSI-RS resource.

[187] In a particular embodiment, the at least one beam measurement includes at least one RSRP, RSRQ and SINR.

[188] In a particular embodiment, the result of the at least one beam measurement is received in a RRCResumeComplete message.

[189] In a particular embodiment, the result of at least one beam measurement is reported in a UEInformationResponse message.

[190] In a particular embodiment, the beam measurement configuration message indicates that the wireless device should transition to the dormant state.

[191] In a particular embodiment, the beam measurement configuration message configures the wireless device 110 to perform at least one beam measurement per cell and/or per carrier frequency, while in the dormant state.

[192] In a particular embodiment, the beam measurement configuration message configures the wireless device 110 to perform at least one beam measurement on at least one cell or carrier having SSB outside of a synchronization raster while in the dormant state. . Stated another way, the beam measurement configuration message configures the wireless device 110 to perform beam measurements outside of the synchronization raster.

[193] In a particular embodiment, the base station transmits, to the wireless device 110, contention-free Radio Access Channel, RACH, resources for at least one beam included in the report of the result of the at least one beam measurement. .

[194] In certain embodiments, the method for configuring the measurement report, as described above, may be performed by a virtual computing device. FIGURE 19 illustrates an exemplary virtual computing device 700 for configuring measurement reporting, in accordance with certain embodiments. In certain embodiments, the virtual computing device 700 may include modules for performing steps similar to those described above with respect to the method illustrated and described in FIGURE 18. For example, the virtual computing device 700 may include at least one transmission module 702, a receive module 704 and any other suitable modules for configuring the measurement report. In some embodiments, one or more of the modules may be implemented using the processing circuitry 170 of FIGURE 12. In certain embodiments, the functions of two or more of the various modules may be combined into a single module.

[195] The transmission module 702 may perform the transmission functions of the virtual computing device 700. For example, in a particular embodiment, the transmission module 702 may transmit a beam measurement configuration to a wireless device 110. beam measurement configuration configures the wireless device 110 to perform at least one beam measurement while the wireless device 110 operates in a dormant state.

[196] The receiving module 704 may perform the receiving functions of the virtual computing device 700. For example, in a particular embodiment, the receiving module 704 may receive, from the wireless device 110, a report of a result gives at least one beam measurement. The report is received upon a transition of the wireless device 110 from the dormant state to a connected state.

[197] Other embodiments of the virtual computing device 700 may include additional components beyond those shown in FIGURE 12, which may be responsible for providing certain aspects of network node functionality, including any of the functionality described above and/or any additional functionality (including any functionality required to support the solutions described above). The various different types of wireless devices 115 may include components having the same physical hardware, but configured (e.g., via programming) to support different radio access technologies, or may represent partially or entirely different physical components.

Claims (34)

1. Method (400) for reporting measurement performed by a wireless device (110), the method characterized by the fact that it comprises: obtaining (402), from a network, a message indicating that the wireless device (110) must transition from a connected state to a Radio Resource Control Inactive state, RRC_INACTIVE, the message comprising a beam measurement configuration to perform at least one beam measurement while the wireless device (110) is in the state RRC_INACTIVE, where the beam measurement configuration comprises: a maximum number of beam indices to include in a beam measurement report; an indication as to whether or not to include beam measurements for the beam indices in the beam measurement report; and an indication of what beam index measurement information is to be included in the beam measurement report; based on the beam measurement configuration, performing (404) the at least one beam measurement while operating in an RRC_INACTIVE state, wherein performing (404) the at least one beam measurement while operating in the RRC_INACTIVE state comprises performing the at least a beam measurement on at least one cell or carrier having synchronization signal blocks (SSBs) outside a synchronization raster while in the RRC_INACTIVE state; and reporting (406), in the beam measurement report, a result of the at least one beam measurement to the network, wherein the report is made after a transition from the RRC_INACTIVE state to a connected state; wherein the beam measurement configuration is obtained from the originating base station and the result report of the at least one beam measurement is transmitted to a destination base station that is different from the originating base station. 2. Method according to claim 1, characterized by the fact that the at least one beam measurement comprises at least one measurement performed on at least one reference signal that is beamformed by the network, the at least one signal signal reference comprising at least one of: a Synchronization Signal Block, SSB, and a Channel State Information Reference Signal, CSI-RS resource. 3. Method according to claim 1, characterized by the fact that the at least one beam measurement comprises at least one of: Reference Signal Received Power, RSRP; Reference Signal Received Quality, RSRQ; and Signal-to-Interference plus Noise Ratio, SINR. 4. Method according to claim 1, characterized by the fact that the result of the at least one beam measurement is reported in an RRCResumeComplete message. 5. The method of claim 1, wherein the result of the at least one beam measurement is reported in a UEInformationResponse message. 6. The method of claim 1, wherein the message comprising the beam measurement configuration comprises an RRCRelease message. 7. Method according to claim 1, characterized by the fact that performing at least one beam measurement while operating in the RRC_INACTIVE state comprises performing at least one beam measurement per cell and/or per carrier frequency while in the state RRC_INACTIVE. 8. Method according to claim 1, characterized by the fact that the beam measurement configuration additionally comprises a threshold for consolidation of L1 measurements. 9. The method of claim 1, wherein the beam measurement configuration further comprises a carrier frequency to be used for the at least one beam measurement. 10. Method according to claim 1, characterized by the fact that the beam measurement configuration additionally comprises a duration for performing at least one beam measurement. 11. The method of claim 1, wherein the beam measurement configuration further comprises a list of cells for performing at least one beam measurement. 12. Wireless device (110) characterized by the fact that it comprises: a set of processing circuits (120) configured to: obtain (402), from a network, a message indicating that the wireless device (110) should perform transition from a connected state to a Radio Resource Control Inactive state, RRC_INACTIVE, the message comprising a beam measurement configuration to perform at least one beam measurement while the wireless device (110) is in the RRC_INACTIVE state, wherein the beam measurement configuration comprises: a maximum number of beam indices to include in a beam measurement report; an indication as to whether or not to include beam measurements for the beam indices in the beam measurement report; and an indication of what beam index measurement information is to be included in the beam measurement report; based on the beam measurement configuration, performing (404) the at least one beam measurement while operating in an RRC_INACTIVE state, wherein performing (404) the at least one beam measurement while operating in the RRC_INACTIVE state comprises performing the at least a beam measurement on at least one cell or carrier having synchronization signal blocks (SSBs) outside a synchronization raster while in the RRC_INACTIVE state; and reporting (406), in the beam measurement report, a result of the at least one beam measurement to the network, wherein the report is made after a transition from the RRC_INACTIVE state to a connected state; wherein the beam measurement configuration is obtained from the originating base station and the result report of the at least one beam measurement is transmitted to a destination base station that is different from the originating base station. 13. Wireless device (110), according to claim 12, characterized by the fact that the at least one beam measurement comprises at least one measurement performed on at least one reference signal that is beamformed by the network, the at least one reference signal comprising at least one of: a Synchronization Signal Block, SSB, and a Channel State Information Reference Signal, CSI-RS resource. 14. Wireless device (110), according to claim 12, characterized by the fact that the at least one beam measurement comprises at least one of: Reference Signal Received Power, RSRP; Reference Signal Received Quality, RSRQ; and Signal-to-Interference plus Noise Ratio, SINR. 15. Wireless device (110), according to claim 12, characterized by the fact that the result of the at least one beam measurement is reported in an RRCResumeComplete message or in a UEInformationResponse message. 16. Wireless device (110), according to claim 12, characterized by the fact that the message comprising the beam measurement configuration comprises an RRCRelease message. 17. Wireless device (110), according to claim 12, characterized by the fact that when performing at least one beam measurement while operating in the RRC_INACTIVE state, the processing circuitry (120) causes the device wireless (110) perform at least one beam measurement per cell and/or per carrier frequency while in the RRC_INACTIVE state. 18. Wireless device (110), according to claim 12, characterized by the fact that the beam measurement configuration additionally comprises a threshold for consolidation of L1 measurements. 19. Wireless device (110), according to claim 12, characterized by the fact that the beam measurement configuration additionally comprises a carrier frequency to be used for the at least one beam measurement. 20. Wireless device (110), according to claim 12, characterized by the fact that the beam measurement configuration additionally comprises a duration for performing at least one beam measurement. 21. Wireless device (110), according to claim 12, characterized by the fact that the beam measurement configuration additionally comprises a list of cells for performing the at least one beam measurement. 22. Method (600), performed by a base station, to configure measurement report, the method characterized by the fact that it comprises: transmitting (602) to a wireless device (110), a message indicating that the wireless device ( 110) must transition from a connected state to a Radio Resource Control Inactive state, RRC_INACTIVE, the message comprising a beam measurement configuration configuring the wireless device (110) to perform at least one beam measurement while the wireless device (110) is operating in the RRC_INACTIVE state, wherein the beam measurement configuration comprises: a maximum number of beam indices to include in a beam measurement report; an indication as to whether or not to include beam measurements for the beam indices in the beam measurement report; and an indication of what beam index measurement information is to be included in the beam measurement report; and receiving (604), from the wireless device (110), a result of the at least one beam measurement in the beam measurement report, wherein the report is received after a transition of the wireless device (110) from from the RRC_INACTIVE state to a connected state; wherein the transmit step is performed by a source base station and the receive step is performed by a destination base station, the source base station being different from the destination base station; and wherein the beam measurement configuration configures the wireless device (110) to perform the at least one beam measurement on at least one cell or carrier having synchronization signal blocks (SSBs) outside of a synchronization raster while in the state RRC_INACTIVE. 23. Base station characterized by the fact that it comprises: a set of processing circuits (170) configured to: transmit (602) to a wireless device (110), a message indicating that the wireless device (110) should transition to from a connected state to a Radio Resource Control Inactive state, RRC_INACTIVE, the message comprising a beam measurement configuration configuring the wireless device (110) to perform at least one beam measurement while the wireless device (110 ) is operating in the RRC_INACTIVE state, where the beam measurement configuration comprises: a maximum number of beam indices to include in a beam measurement report; an indication as to whether or not to include beam measurements for the beam indices in the beam measurement report; and an indication of what beam index measurement information is to be included in the beam measurement report; and receiving (604), from the wireless device (110), a result of the at least one beam measurement in the beam measurement report, wherein the report is received after a transition of the wireless device (110) from from the RRC_INACTIVE state to a connected state; wherein the transmit step is performed by a source base station and the receive step is performed by a destination base station, the source base station being different from the destination base station; and wherein the beam measurement configuration configures the wireless device (110) to perform the at least one beam measurement on at least one cell or carrier having synchronization signal blocks (SSBs) outside of a synchronization raster while in the state RRC_INACTIVE. 24. The base station of claim 23, wherein the at least one beam measurement comprises at least one measurement performed on at least one reference signal that is beamformed by the network, the at least one signal reference comprising at least one of: a Synchronization Signal Block, SSB; and a Channel State Information Reference Signal, CSI-RS, feature. 25. Base station according to claim 23, characterized by the fact that the at least one beam measurement comprises at least one of: Reference Signal Received Power, RSRP; Reference Signal Received Quality, RSRQ; and Signal-to-Interference plus Noise Ratio, SINR. 26. The base station of claim 23, wherein the result of the at least one beam measurement is received in an RRCResumeComplete message. 27. The base station of claim 23, wherein the result of the at least one beam measurement is reported in a UEInformationResponse. 28. The base station of claim 23, wherein the message comprises an RRCRelease message. 29. Base station according to claim 23, characterized by the fact that it further comprises transmitting, to the wireless device (110), contention-free Radio Access Channel, RACH, resources for at least one beam included in the report the result of at least one beam measurement. 30. The base station of claim 23, wherein the beam measurement configuration configures the wireless device (110) to perform at least one beam measurement per cell and/or per carrier frequency while in the RRC_INACTIVE state. 31. The base station of claim 23, wherein the beam measurement configuration further comprises a threshold for consolidating L1 measurements. 32. The base station of claim 23, wherein the beam measurement configuration further comprises a carrier frequency to be used for the at least one beam measurement. 33. The base station of claim 23, wherein the beam measurement configuration further comprises a duration for performing at least one beam measurement. 34. The base station of claim 23, wherein the beam measurement configuration further comprises a list of cells for performing the at least one beam measurement.