Measurement reporting configuration for aiding the sorting of beam/cell level measurements

It was agreed in RAN2 that beam level reporting is supported in NR. Specifically, it was agreed that:

Beam measurements (based on new radio-synchronization signals (NR-SS) and channel state information reference signals (CSI-RS)) can be included in the measurement report and configured by the network (i.e. the network (UE) to report beam identifiers only, to report beam measurements and beam identifiers, or to do no beam reporting).

A quantity of measurements can be set by the network for beam measurement reporting. RAN1 confirms the supported metrics.

For the selection of x Synchronization Signal (SS) blocks to be included in the measurement report for each cell: x can be set independently of N (N is used in cell quality derivation).

The measured quantity to be reported for beam measurements can be the same as both the (cell) trigger quantity or RSRP/RSRQ.

For NR-SS based measurement events, in each cell, the best SS block is reported, up to x-1 next highest measured SS blocks above the absolute threshold. The threshold is the same threshold used for cell quantity derivation.

For CSI-RS-based measurement events, in each cell, the best CSI-RS is reported, up to y-1 next highest measured CSI-RS above the absolute threshold. The threshold is the same threshold used for cell quality derivation.

Network to include beam level information (beam IDS and/or available measurement results for primary cell (PCell)/primary secondary cell (PSCell) and secondary cell (SCell)) in measurement reports. When UEs are configured, their beam level information is included in the measurement report.

Based on these agreements, in event-triggered measurement reports, the UE shall report beam level measurements of PCell, PSCell, SCell and cells in the triggeredCellsList.

Additionally, the beam-related measures to be reported for cells in the triggeredCellsList are beam index only, beam index and beam RSRP, beam index and beam RSRQ, or beam index and beam signal-to-interference-plus-noise ratio (SINR). , can be set (independently of the measurements that will be reported for the cell). For each cell, the best SS block/CSI-RS is always included in the measurement report, up to x-1/y-1 next highest measured SS blocks/CSI-RS are included in the measurement report. included.

In addition, there will be support for period measurement reporting in NR. Specifically, the following was agreed in RAN2.

o if the current beam reporting agreement (the network configures the UE to report beam identifiers only, beam measurements and beam identifiers, or no beam reporting) is considered an event-triggered report; Applies to both periodic reports.

A single periodic measurement configuration may be configured to report SS-based measured results or CSI-RS-based measured results (not both).

- The UE is required to report all applicable cells up to maxCellReport for periodic measurements, where applicable cells are on the relevant frequency, excluding cells in the black cell list. Defined as the neighbor cell detected above.

Based on these agreements, periodic measurement reports will be based on only one RSType set in the corresponding reportConfig. It was also agreed that beam level measurements should be included in the measurement report.

In LTE, the triggerQuantity parameter, part of the reporting configuration (reportConfig), to indicate which quantity shall be used for event-triggered reporting, e.g. either RSRP, RSRQ or SINR. It is not used only for Additionally, the triggerQuantity parameter can also be used for periodic reporting. In addition to this parameter, reportConfig also contains a parameter called reportQuantity which is used to indicate which quantities shall be included in the measurement report. In other words, the network may configure the UE to report a higher amount than what is used to trigger the event.

If triggerQuantity is set as RSRP and reportQuantity is set as sameAsTriggerQuantity, the UE shall report the RSRP value. If triggerQuantity is set as RSRQ and reportQuantity is set as sameAsTriggerQuantity, the UE shall report the RSRQ value. Additionally, the reportQuantity can be set as both, leading to reporting of both RSRP and RSRQ. Release 13 also introduced additional SINR-based reporting.

Currently, there are certain challenges (one or more). Based on the above agreement for NR, the network may provide beam level measurement information (i.e., beam index only or beam index with measurement(s)) for periodic measurement reports as well as event-triggered measurement reports. ) may be configured to include the It has already been agreed that the UE shall include in the measurement report the best beam for each cell up to the X-1 strongest beams per cell above the absolute threshold, where: X is set in reportConfig and thresholds are set in measObject.

In addition, the following was submitted to RAN2#100 in R2-1713427 describing an amendment for the RRM TP discussed to resolve that issue.

The current TP, UE, derives each cell quantity with the best N beams for that quantity as follows.

The UE shall:

1> For each cell metric to be derived based on SS/PBCH blocks, 2> if nroSS-BlocksToAverage in the associated measObject is not set or 2> absThreshSS-BlocksConsolidation in the associated measObject is not set or 2> if the highest beam metric value is below absThreshSS-BlocksConsolidation, then 3> derive each cell metric based on the SS/PBCH block as the highest beam metric value, where each beam metric is is described in TS38.215 [FFS].

2> Otherwise, 3> derive each cell metric based on SS/PBCH blocks as the linear average of the power values of the highest beam metric values above absThreshSS-BlocksConsolidation, where the total number of averaged beams is shall not exceed nroSS-BlocksToAverage.

If multiple cell qualities (eg, RSRQ and RSRQ) are configured to report, the UE may differ between the best N beams for RSRP and the best N beams for RSRQ. , we can have different sets of best N beams for cell derivation.

However, there is only one set of beams in the measurement report and the current TP is that the UE should include the best beam for each quantity and the other beams above the threshold in descending order. , but it is unclear as to how these beams should be classified. If the beams were sorted by different quantities (eg RSRP or RSRQ), the results would be different.

For the beam measurement information to be included in the measurement report, the UE shall:

1> Set rsIndexResults to include up to maxNroRsIndexesToReport beam indices in descending order as follows:

2> If the measurement information to be included is based on an SS/PBCH block, 3> the best beam for that SS/PBCH block amount, and the rest whose amount exceeds the absThreshSS-BlocksConsolidation specified in the VarMeasConfig for the corresponding measObject , in resultsSSBIndexes, and if 3> onlyReportBeamIds is not set, include the SS/PBCH-based measurement results associated with each beam index.

To clarify the beam raking criteria for beam reporting, one possible change is to classify the beams by the amount triggered by the event, but for periodic MR it is not clear how the beams should be classified. It remains unclear as to whether Another option is to quantify beam classification explicitly by the network, in which case additional configuration is required to quantify beam classification in MR.

Proposal 6: The network should indicate the metric for beam classification in the measurement configuration when multiple metrics are set to report.

As can be seen, therefore, the R2-1713427 contribution document mentions a first solution whose "triggerQuantity" can be used as the metric to be used to classify the beam level measurements to be reported. did. As mentioned in the prior art itself, the problem with that solution is that triggerQuantity is specified in the NR RRC specification only for event-triggered types, and therefore how the UE classifies the beams to be included in the measurement report. is ambiguous.

The contributing document then suggests a second solution, in which there is some kind of beam classification reporting parameter where the explicit parameters indicate to the UE how to classify the beams. That solution can solve the problem, but it's not the most efficient.

A problem with the second solution is that additional parameters would have to be defined in the specification and explicitly signaled to the UE. Another problem is that the second solution only covers the case of a single triggering quantity, ie the report is triggered based on a single quantity RSRP, RSRQ or SINR. In NR it was at least suggested that the network should potentially configure multiple trigger quantities, eg RSRP and RSRQ, RSRQ and SINR, RSRP and SINR, RSRP and RSRQ and SINR. It was also proposed that these could be based on multiple RS types, eg SS/PBCH block and CSI-RS.

Yet another issue concerns the following agreements in NR related to beam reporting related to the serving cell. Specifically, in RAN2#99bis Prague, if the network configures the UE to include PCell/PSCell and SCell beam level information (beam ID and/or available measurement results) in the measurement report, their It was agreed that beam level information should be included in the measurement report.

There is still an open question whether the UE always includes the serving cell's beam information in the measurement report, but one of the following options could possibly be supported.

The UE shall include all available beam measurement information for the serving cell(s) in the measurement report.

The UE shall include available beam measurement information for the serving cell(s) in the measurement report according to the reportConfig associated with the report.

In other words, in LTE, the UE shall include RSRP and RSRQ in the measurement report for each configured serving cell. This was also agreed for NR. Therefore, there is no need to solve the classification problem for serving cell measurement reports since there is a single serving cell for each frequency. However, in NR, the network is associated with i) the serving cell (PCell and SCell(s)) and ii) the best neighbor(s) on the serving frequency, as explained above. It was agreed that the UE could be configured to include beam measurements. Therefore, the solution(s) described in the previous contributing documents and agreements ignore that aspect of serving cell measurements, which is yet another limitation.

Yet another issue relates to the following agreements in NR related to beam reporting related to the best neighbor cell(s) on each serving frequency. In RAN2#99bis Prague it was agreed that the network could configure the UE to report the best neighbor cell on the serving frequency. Agreement from the RAN2#99bis conference allows cell-level measurements of the best neighbor cell on the serving frequency to be included. However, the RSType that should be used to perform neighbor cell measurements is still not agreed upon. A separate information element can be configured to control which type of RSType should be used to perform neighbor cell measurements on the serving frequency, but the same RSType used for serving cell measurements. Having an RSType would be sufficient. It has already been agreed that the RSType for serving cell measurements is the same as the RSType configured in reportConfigNR. It is possible that the following could be agreed in NR.

The UE shall use the same RSType(s) as the RSType of the serving cell's measurements on those serving frequencies to measure the best neighbor cells on the serving frequencies.

Quantities to be measured, such as RSType to be used to measure neighbor cell measurements on the serving frequency, may also follow the same principle. It is beneficial to the network to have the same amount to be reported for the best neighbor cell and serving cell on the serving frequency so that the network can compare these measurements and make decisions accordingly. . When RSRP and RSRQ measurements are to always be reported for serving cells, it shall be applicable to the best neighbor cells on their serving frequencies. The SINR reporting described in the previous section can depend on the reported quantity content of the measID that triggered the measurement report. Then, the following may also be agreed in NR.

The UE shall use the same metrics as the serving cell measurements on their serving frequencies to report the cell-level measurements of the best neighbor cells on the serving frequencies.

The beam level information of the best neighbor cell on the serving frequency is not always required. If that beam level information is needed, the network can obtain that beam level information by having a specific event (eg, A6 event) related to that beam level information. However, configuring additional A6 events just for the purpose of obtaining the best neighbor cell beam level information on the serving frequency may lead to an increase in the number of measurements configured for the UE. To overcome this drawback, there can be a trade-off, i.e. the UE is reported to the network only if it is configured with beam level reporting enabled in reportConfig for the measID that triggered the measurement report. , may have the beam level information of the best neighbor cell on the serving frequency. The following may also be agreed for NR.

The UE shall include the beam level measurement of the best neighbor cell on the serving frequency in the measurement report only if beam level reporting is enabled in the reportConfig of the measID that triggered the measurement report.

To further reduce the reporting overhead, the UE may only report the amount configured in the beam level reporting related parameter in reportConfig of the measID that triggered the measurement report.

The UE shall only include the beam level measurements of the best neighbor cell on the serving frequency as configured in the beam level reporting of the reportConfig in the measID that triggered the measurement report.

In summary, beam level measurement information related to the best neighbor(s) on each serving frequency may also be configured by the network to be included by the UE in the measurement report. Therefore, the problem also remains unsolved because it did not exist in LTE or was not addressed by previous proposals.

Certain aspects of the disclosure and their embodiments may provide solutions to these and other challenges. Certain embodiments propose methods for configuring user equipment (UE) to identify the quantity to be chosen for classifying beam level measurements.

According to some embodiments, a method implemented by a wireless device for measurement reporting includes sorting a plurality of measurements for a measurement report based on at least one metric. The method further includes reporting to a network node measurement information selected from the plurality of measurements sorted based on at least one metric.

According to some embodiments, a wireless device for measurement reporting sorts a plurality of measurements for a measurement report based on at least one metric; and reporting measurement information selected from the measurements to a network node.

According to some embodiments, a method implemented by a network node for configuring a wireless device for measurement reporting comprises configuring the wireless device for event-based measurement reporting; receiving a measurement report including measurement information selected from the plurality of measurements based on classification of the plurality of measurements in response to detection of the event.

According to some embodiments, a network node for configuring a wireless device for measurement reporting configures the wireless device for event-based measurement reporting and responds to detection of an event from the wireless device. and receiving a measurement report including measurement information selected from the plurality of measurements based on the classification of the plurality of measurements.

Some embodiments may provide one or more of the following technical advantage(s). For example, some embodiments may provide standardized behavior from the UE for beam classification that enables the network to build sophisticated self-optimizing network (SON) functions.

For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following description in conjunction with the accompanying drawings.

<figref num="1">FIG. 4 illustrates a measurement reporting procedure, according to some embodiments;</figref><figref num="2">1 illustrates an exemplary network, according to some embodiments; FIG.</figref><figref num="3">FIG. 4 illustrates an exemplary network node, in accordance with some embodiments;</figref><figref num="4">1 illustrates an exemplary wireless device, according to some embodiments; FIG.</figref><figref num="5">FIG. 4 illustrates an exemplary embodiment of a UE, according to some embodiments;</figref><figref num="6">FIG. 2 illustrates a virtualized environment in which functionality implemented by some embodiments may be virtualized, according to some embodiments;</figref><figref num="7">1 illustrates a communication network connected to a host computer via an intermediate network, according to some embodiments; FIG.</figref><figref num="8">FIG. 4 illustrates a host computer communicating with user equipment via a base station over a partial wireless connection, according to some embodiments;</figref><figref num="9">1 illustrates an exemplary method implemented in a communication system according to some embodiments; FIG.</figref><figref num="10">FIG. 4 illustrates another example method implemented in a communication system according to some embodiments;</figref><figref num="11">FIG. 4 illustrates another example method implemented in a communication system according to some embodiments;</figref><figref num="12">FIG. 4 illustrates another example method implemented in a communication system according to some embodiments;</figref><figref num="13">1 illustrates an exemplary method in a wireless network, according to some embodiments; FIG.</figref><figref num="14">1 is a schematic block diagram of devices in a wireless network, according to some embodiments; FIG.</figref><figref num="15">FIG. 4 illustrates an exemplary method by a wireless device for measurement reporting, according to some embodiments;</figref><figref num="16">1 is a schematic block diagram of devices in a wireless network, according to some embodiments; FIG.</figref><figref num="17">FIG. 4 illustrates an example method by a network node for configuring a wireless device for measurement reporting, according to some embodiments;</figref><figref num="18">1 is a schematic block diagram of devices in a wireless network, according to some embodiments; FIG.</figref>

In general, all terms used in this specification are defined by their normal meaning in the relevant technical field, unless a different meaning is explicitly given and/or implied from the context in which the term is used. should be interpreted according to their meaning. All references to one (a/an)/the (the) element, device, component, means, step, etc., are the same as that element, device, component, means, unless expressly stated otherwise. should be interpreted openly as referring to at least one instance of steps, etc. No step of any method disclosed herein may be described as following or preceding another step, unless the step is expressly described as following or preceding another step, and/or if the step follows or precedes another step. Where it is implied that must be done, it need not be performed in the strict order disclosed. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment wherever appropriate. Likewise, any advantage of any of the embodiments may be applied to any other embodiment and vice versa. Other objects, features and advantages of the enclosed embodiments will become apparent from the following description.

Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. However, other embodiments are included within the scope of the presently disclosed subject matter, and the disclosed subject matter is to be construed as limited to only the embodiments set forth herein. Rather, these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

The following embodiments are applicable at least for cell and beam level measurement reports in i) periodic measurement reports containing beam measurement information and ii) event-triggered measurement reports containing beam measurement information.

For event-triggered measurement reporting, some embodiments may assume the following cases for the problem of classifying beam measurement information and cells based on these cases.

- A single trigger quantity based on a single RS type.

RSRP, RSRQ or SINR, any of which are based on the SS/PBCH block.

RSRP, RSRQ or SINR, any of which are based on CSI-RS.

- A single trigger quantity based on multiple RS types.

RSRP, RSRQ or SINR. There can be the same trigger quantity measured using different RS types.

o For example, an event may be configured to be triggered based on two RSRP values, one of which is measured based on the SS/PBCH block and the other based on the CSI-RS be done.

o For example, an event may be configured to be triggered based on two RSRQ values, one of which is measured based on the SS/PBCH block and the other based on the CSI-RS be done.

o For example, an event may be set to be triggered based on two SINR values, one of which is measured based on the SS/PBCH block and the other based on the CSI-RS be done.

RSRP, RSRQ or SINR, any of which are based on CSI-RS.

- Multiple trigger amounts based on a single RS type per event.

RSRP and RSRQ, RSRP and SINR, RSRQ and SINR, RSRP and RSRQ and SINR, all based on SS/PBCH blocks.

RSRP and RSRQ, RSRP and SINR, RSRQ and SINR, RSRP and RSRQ and SINR, all based on CSI-RS.

- Multiple trigger amounts based on multiple RS types per event.

RSRP is based on SS/PBCH blocks and RSRQ is based on CSI-RS.

RSRP is based on CSI-RS and RSRQ is based on SS/PBCH blocks.

RSRP is based on SS/PBCH blocks and SINR is based on CSI-RS.

RSRP is based on CSI-RS and SINR is based on SS/PBCH blocks.

RSRQ is based on SS/PBCH blocks and SINR is based on CSI-RS.

RSRQ is based on CSI-RS and SINR is based on SS/PBCH blocks.

- RSRP, RSRQ and SINR based on any combination of RS types. For example, RSRP and RSRQ are based on SS/PBCH blocks and SINR is based on CSI-RS. In another example, RSRP and SINR are based on SS/PBCH blocks and RSRQ is based on CSI-RS.

According to some embodiments, the network may set different beam and cell level measurement information. For example, the network may configure the UE to report the following measurement information based on SS/PBCH block(s).

- measurement results per cell and/or beam per SS/PBCH block, - indices of (one or more) SS/PBCH blocks (i.e. which SS/PBCH blocks are beamformed and configured for measurement). index for each beam).

The network may configure the UE to report the following measurement information based on CSI-RS resources.

- per CSI-RS resource, per cell and/or per beam measurement result; - CSI-RS resource measurement identifier.

According to some embodiments, a single parameter, which may be called triggerQuantity, is defined in reportConfig as a multi-purpose parameter and is defined for multiple event types.

In certain embodiments, for example, a single parameter called triggerQuantity may be defined in reportConfig for event-triggered and periodic report types as a common parameter. The parameter triggerQuantity can be specified in reportConfig and subsequently encoded as triggerQuantity::=ENUMERATED{rsrp,rsrq,sinr}.

Below are some examples of how the common parameters can be coded in ASN.1. For example, triggerQuantity is valid for multiple report types, eg, periodic or eventTriggered, as shown below, and can be coded outside of reportType.

<img file="JP7166340B2_D0001.tif" /><img file="JP7166340B2_D0002.tif" /><img file="JP7166340B2_D0003.tif" />

According to other embodiments, the same multi-purpose parameter triggerQuantity may be encoded within each reportType, which is intended to be used, such as periodic or eventTriggered, as indicated below.

<img file="JP7166340B2_D0004.tif" /><img file="JP7166340B2_D0005.tif" /><img file="JP7166340B2_D0006.tif" />

According to some other embodiments, the parameters for the event-triggered report type within each event are applicable for other events to be introduced in the future, as shown below. , so the parameter is encoded.

<img file="JP7166340B2_D0007.tif" /><img file="JP7166340B2_D0008.tif" /><img file="JP7166340B2_D0009.tif" />

According to some embodiments, the UE action may be taken depending on the parameter value in reportConfig for the measurement identifier (measId), which may be 'rsrp', 'rsrq' or 'sinr'. As an example, the UE shall:

- if an event-triggered report type is configured and beam reporting is configured for that event, or - if a periodic report type is configured and beam reporting is configured for that report type. the UE shall classify the neighbor cell measurements to be included in the measurement report based on the configured value, i.e. if the network configures 'rsrp', the cell measurements and the beam Both of the measurement information are classified based on RSRP measurements (cell RSRP value and L3 filtered beam RSRP value based on either SS/PBCH block or CSI-RS).

- if a periodic report type is configured and if beam reporting is configured for that report type, the UE shall set the configured parameters to the trigger amount for that configured event i.e. RSRP, RSRQ or SINR.

- When the UE is to include beam measurement information for the configured serving cell(s), there can be multiple beams per cell and classification is required. Therefore, the UE shall:

If the beam to be reported has measurements associated with only one RS type, then include the quantity(s) indicated in reportQuantity in the relevant reportConfig, starting with the highest triggerQuantity. ie the best beam associated with the triggerQuantity for the available RS types is included first.

- When the UE should include beam measurement information for the configured best neighbor(s) on each serving frequency, there can be multiple beams per best neighbor cell and classification is required. be done. Therefore, the UE shall:

If the beam to be reported has measurements associated with only one RS type, then include the quantity(s) indicated in reportQuantity in the relevant reportConfig, starting with the highest triggerQuantity. ie the best beam associated with the triggerQuantity for the available RS types is included first.

According to some embodiments, the parameter is the best It is sometimes said to be versatile in that it is also used to indicate an ordering for inclusion of beam measurement information associated with neighbors, i.e. ordered by RSRP, RSRQ or SINR.

In another embodiment, the existing parameter rsType in reportConfig, which can take the values SS/PBCH block or CSI-RS, is also multi-purpose. As specified in the current 38.331 draft specification, the parameter is only used to select which RS type should be used for neighbor measurements associated with that report type. As proposed in this embodiment, the parameters shall also be used for additional UE actions related to classifying the beams associated with the serving cell to be included in the measurement report.

- if an event-triggered report type is set, or - if a periodic report type is set, reportConfig that triggered a report if the beam(s) associated with the configured serving cell to be reported has measurements associated with multiple RS types, e.g., SS/PBCH blocks and CSI-RS set measResult to include the quantity(s) indicated in the reportQuantity in the associated reportConfig in descending order of triggerQuantity associated with the same rsType in the The best beam associated with the triggerQuantity measured on the Suppose we have Then, if the triggerQuantity is rsrp, the classification shall be based on RSRP. However, there can be two RSRP values, one based on SSB and the other based on CSI-RS. If rsType in reportConfig is SSB, then the RSRP value to be used as sorting criterion shall be SSB. Otherwise, if rsType in reportConfig is CSI-RS, then the RSRP value to be used as the classification criterion shall be CSI-RS.

- When the UE should include beam measurement information for the configured best neighbor(s) on each serving frequency, the concept of one or more "best" cells is best RSRQ? best SINR?) and RS type (best follows SSB? best follows CSI-RS?). Therefore, if the UE has multiple of these measurements available and shall include only the K best cells, the UE shall:

Triggered reporting if the best cell on the configured serving frequency(s) to be reported has measurements related to multiple RS types, e.g., SS/PBCH block and CSI-RS Set measResult to include the quantity(s) indicated in the reportQuantity in the related reportConfig in descending order of triggerQuantity associated with the same rsType in the reportConfig, i.e. use the configured rsType The best cell associated with triggerQuantity measured as Suppose we have Then, if the triggerQuantity is rsrp, the classification shall be based on RSRP. However, there can be two RSRP values, one based on SSB and the other based on CSI-RS. If rsType in reportConfig is SSB, then the RSRP value to be used as sorting criterion shall be SSB. Otherwise, if rsType in reportConfig is CSI-RS, then the RSRP value to be used as the classification criterion shall be CSI-RS.

The best beam of the best cell(s) on the configured serving frequency(s) to be reported may be for multiple RS types, e.g., SS/PBCH block and CSI-RS. If it has associated measurements, set measResult to include the quantity(s) indicated in reportQuantity in the associated reportConfig in descending order of triggerQuantity associated with the same rsType in the reportConfig that triggered the report. set, i.e. the best cell associated with the triggerQuantity measured using the set rsType is included first, in other words the available cell measurements (eg, both RSRP and RSRQ). Then, if the triggerQuantity is rsrp, the classification shall be based on RSRP. However, there can be two RSRP values, one based on SSB and the other based on CSI-RS. If rsType in reportConfig is SSB, then the RSRP value to be used as sorting criterion shall be SSB. Otherwise, if rsType in reportConfig is CSI-RS, then the RSRP value to be used as the classification criterion shall be CSI-RS.

If a beam to be reported has measurements associated with multiple RS types, e.g., SS/PBCH blocks and CSI-RS, then in the relevant reportConfig, in descending order of triggerQuantity associated with the same rsType in the reportConfig set measResult to include the quantity(s) indicated in the reportQuantity of , i.e. the best beams associated with the triggerQuantity measured using the set rsType are included first.

FIG. 1 shows a measurement reporting procedure, according to some embodiments. Regarding the measurement reporting procedure, the procedure text can be written for NR RRC specification 38.331 as follows.

The purpose of this procedure is to transfer the measurement results from the UE to the network. The UE shall initiate this procedure only after successful security activation.

For the measId for which the measurement report procedure was triggered, the UE shall set measResults in the MeasurementReport message as follows.

1&gt; Set measId to the measurement identification that triggered the measurement report.

1&gt; Set measResultServingCell in measResultServingFreqList to include all available cell and beam quantities for PCell based on SS/PBCH block and CSI-RS measurements.

1&gt; For each SCell configured, if available according to the performance requirements in TS38.133, servFreqId, if any, and all available cells and Set the measResultServingCell in the measResultServFreqList to include the beam frequency and

1&gt; if the reportConfig associated with the measId that triggered the measurement report contains reportAddNeighMeas, 2&gt; for each serving frequency whose measObjectId is referenced in the measIdList, other than the frequency corresponding to the measId that triggered the measurement report, 3&gt; related Set measResultBestNeighCell in measResultServFreqList to include the physCellId and amount of the best non-serving cell on the serving frequency.

[The details of the information to be reported relating to the best neighbor cell on the serving frequency, e.g., which RS type, what quantity, whether beam reporting is supported, etc., are for future study. be. Furthermore, whether the UE shall include all available beam information of the PCell/SCell in the measurement report or whether the UE shall only include the beam information of the PCell/PSCell indicated in the reportConfig associated with its measId. Whether or not to include it needs future consideration. ]

1&gt; If there is at least one applicable neighbor cell to report, 2&gt; set measResultNeighCells to include the best neighbor cells up to maxReportCells according to:

3&gt; If reportType is set to eventTriggered, 4&gt; Include the cells contained in the cellsTriggeredList defined in VarMeasReportList for this measId.

3&gt; Otherwise, 4&gt; new measurement results, including applicable cells that have been available since the last periodic report or since the measurement was started or reset, 4&gt; if reportQuantityRsIndexes is set, 5.5 .include beam measurement information as described in 5.1;

3&gt; For each cell contained in measResultNeighCells, include a physCellId.

3&gt; If reportType is set to eventTriggered, 4&gt; For each included cell, include the Layer 3 filtered measured results according to the reportConfig for this measId, ordered as follows:

5&gt; If the measObject associated with this measId pertains to NR, 6&gt; If rsType in the associated reportConfig is set to ss, then the Set resultsSSBCell in measResult to include the SS/PBCH block-based quantity(s) indicated in reportQuantityCell, i.e. if the best cell is included first and &gt; reportQuantityRsIndexes is set, Include beam measurement information as described in 5.5.5.1.

6&gt; If rsType in the associated reportConfig is set to csi-rs, 7&gt; the quantity indicated in the triggerQuantity parameter is listed in the reportQuantityCell in the associated reportConfig in descending order (one or multiple) set resultsCSI-RSCell in measResult to include the CSI-RS base quantity, i.e. the best cell is included first and 8&gt; reportQuantityRsIndexes is set, as described in 5.5.5.1. Include beam measurement information as described.

1&gt; increment the numberOfReportsSent specified in the VarMeasReportList for this measId by 1, 1&gt; stop the periodic reporting timer if running, 1&gt; the numberOfReportsSent specified in the VarMeasReportList for this measId is less than the reportAmount specified in the corresponding reportConfig for this measId, 2&gt; start a periodic reporting timer using the value of reportInterval specified in the corresponding reportConfig for this measId .

1&gt; Else, 2&gt; If reportType is set to Periodic, 3&gt; delete the entry in VarMeasReportList for this measId and 3&gt; delete this measId from measIdList in VarMeasConfig.

1&gt; Submit the MeasurementReport message to the lower layers for transmission, then the procedure ends.

5.5.5.1 Reporting beam measurement information For beam measurement information to be included in measurement reports related to neighbors, the UE shall:

1&gt; If the measurement information to be included relates to the serving cell(s) and both SS/PBCH block measurements and CSI-RS measurements are available, beam ordering to rsType configured in reportConfig. 1&gt; the measurement information to be included relates to the best neighbor cell(s) on the serving frequency(s) and the SS/PBCH block measurements; and CSI-RS measurements are available, consider beam ordering to be based on the measurements performed for the rsType configured in reportConfig, indicated in the triggerQuantity parameter, as follows: Set rsIndexResults to include up to maxNroRsIndexesToReport beam indices in descending order.

2&gt; If the measurement information to be included is based on an SS/PBCH block, 3&gt; the best beam for that SS/PBCH block amount, and the rest whose amount exceeds the absThreshSS-BlocksConsolidation specified in the VarMeasConfig for the corresponding measObject , in resultsSSBIndexes, and if 3&gt; onlyReportBeamIds is not set, include the SS/PBCH-based measurement results associated with each beam index.

2&gt; If the beam measurement information to be included is based on CSI-RS, 3&gt; the best beam for that CSI-RS quantity, and the quantity exceeds absThreshCSI-RS-Consolidation specified in VarMeasConfig for the corresponding measObject Include the indices associated with the remaining beams in resultsCSI-RSIndexes, and if 3&gt; onlyReportBeamIds is not set, include the CSI-RS-based measurement results associated with each beam index.

According to some other embodiments, a single parameter called triggerQuantity may be defined in reportConfig for event-triggered report types and periodic report types as a common parameter. The parameter triggerQuantity is defined in reportConfig and can be encoded as:

triggerQuantity::=SEQUENCE{rsrp BOOLEAN,rsrq BOOLEAN,sinr BOOLEAN}. Thus, the previous set of embodiments indicates that if the network sets a single trigger quantity, i.e. only one quantity is selected (i.e. true is set to ) and all remaining quantities are set to false.

Below are some examples of how that common parameter could be coded in ASN.1. For example, triggerQuantity is valid for multiple report types, eg, periodic or eventTriggered, as shown below, and can be coded outside of reportType.

<img file="JP7166340B2_D0010.tif" /><img file="JP7166340B2_D0011.tif" /><img file="JP7166340B2_D0012.tif" />

In another example, the same multi-purpose parameter triggerQuantity may be encoded within each reportType, which is intended to be used, such as periodic or eventTriggered, as shown below.

<img file="JP7166340B2_D0013.tif" /><img file="JP7166340B2_D0014.tif" /><img file="JP7166340B2_D0015.tif" />

In another example, as shown below, parameters for event-triggered report types may not be applicable for other events that may be introduced in the future, so the parameters are , can be encoded within each event.

<img file="JP7166340B2_D0016.tif" /><img file="JP7166340B2_D0017.tif" /><img file="JP7166340B2_D0018.tif" /><img file="JP7166340B2_D0019.tif" />

In still other embodiments, a single parameter called triggerQuantity may be defined in reportConfig for event-triggered and periodic report types as a common parameter. However, the parameter triggerQuantity defined in reportConfig can be encoded as:

triggerQuantity::=SEQUENCE {rsrp BOOLEAN,rsrq BOOLEAN,sinr BOOLEAN}.

And, furthermore, the IE rsType is defined as a sequence to indicate that events can be triggered based on multiple RS types.

rsType::=SEQUENCE{ssb BOOLEAN,csi-rs BOOLEAN}.

According to some other embodiments, the beam level quantity to be used to classify the beam level measurements may be based on the classifier selection method specified in measConfig and further specified in reportConfig. based on triggerQuantity. In this embodiment, the network sets a mapping between the triggerQuantity specified in reportConfig and the quantity used for the classification method to be used by the UE for beam selection. Some of these mappings are given in the table below (the table below is given one way or another in measConfig).

<img file="JP7166340B2_D0020.tif" />

In some other embodiments, the beam level quantity to be used to classify the beam level measurements is based on the classifier selection method (mapping table) specified in measConfig and further specified in reportConfig. Based on reportQuantityRsIndexes provided. In this embodiment, the network sets a mapping between the reportQuantity specified in reportConfig and the quantity used for the classification method to be used by the UE for beam selection. Some of these mappings are given in the table below (the table below is given one way or another in measConfig).

<img file="JP7166340B2_D0021.tif" />In other embodiments where RSRQ and SINR are indicated for beam level reporting, the metric to be used for classification of beam level measurements may be RSRQ.

In another particular embodiment, in case of multiple triggering quantities (eg RSRP and RSRQ), the UE knows which quantity shall be used to classify the cells to be included in the measurement report. , there can be an explicit parameter (cellsSortingQuantity).

In another particular embodiment, in case of multiple triggering quantities (eg RSRP and RSRQ), the UE knows which quantity shall be used to classify the cells to be included in the measurement report. , there can be an explicit parameter (beamsSortingQuantity).

In another specific embodiment, in case of multiple triggering quantities (eg RSRP and RSRQ), the UE knows which quantity shall be used to classify the cells and beams to be included in the measurement report. So there can be an explicit parameter (sortingQuantity).

In another specific embodiment, in the case of multiple RS types (eg, SSB-based RSRP and CSI-RS-based RSRP) as trigger quantities, the UE determines which RS type to classify the cells to include in the measurement report. There can be an explicit parameter (cellsSortingQuantity) to know what should be used.

In another specific embodiment, in case of multiple RS types (eg SSB-based RSRP and CSI-RS-based RSRP) as trigger quantities, how the UE can classify the per-cell beams to be included in the measurement report. There can be an explicit parameter (beamsSortingQuantity) to know what quantity shall be used.

In another specific embodiment, in case of multiple RS types (eg, SSB-based RSRP and CSI-RS-based RSRP) as triggering quantities, which quantity is used by the UE to classify the cells and beams to be included in the measurement report? There can be an explicit parameter (sortingQuantity) to know what shall be used.

FIG. 2 shows a wireless network, according to some embodiments. Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are shown in FIG. A wireless network is described, such as an exemplary wireless network. For simplicity, the wireless network of FIG. 2 only shows network 106, network nodes 160 and 160b, and WDs 110 and 110b. In practice, wireless networks support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, service provider, or any other network node or end device. may further comprise any additional elements suitable for Of the components shown, network node 160 and wireless device (WD) 110 are illustrated with additional detail. A wireless network provides communication and other types of services to one or more wireless devices to provide wireless device access to and/or by or through a wireless network. It can facilitate the use of services.

A wireless network may include and/or interface with any type of communication, communications, data, cellular, and/or wireless network or other similar type system. In some embodiments, a wireless network may be configured to operate according to a particular standard or other type of pre-defined rules or procedures. Accordingly, particular embodiments of wireless networks are Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G communications standards such as standards, wireless local area network (WLAN) standards such as the IEEE 802.11 standard, and/or World Wide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards; Any other suitable wireless communication standard may be implemented.

Network 106 may include one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WAN), local area networks (LAN), wireless local It may include area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks for enabling communication between devices.

Network node 160 and WD 110 include various components that are described in more detail below. These components cooperate to provide network node and/or wireless device functionality, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may include any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and/or whether via wired or wireless connections. but may include any other component or system that may facilitate or participate in communication of data and/or signals.

FIG. 3 shows a network node, according to some embodiments. As used herein, a network node enables and/or provides wireless access to and/or wireless devices and/or performs other functions (e.g., administrative functions) in wireless networks. ) capable, configured, configured, and/or operable to communicate directly or indirectly with other network nodes or devices in a wireless network to implement point to Examples of network nodes include, but are not limited to, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., wireless base stations, Node Bs, evolved Node Bs (eNBs) and NR Node Bs (gNB)). Base stations may be categorized based on the amount of coverage they provide (or, put another way, the transmit power level of the base station), where femto base stations, pico base stations, micro base stations, Or it may be called a macro base station. A base station may be a relay node or a relay donor node that controls a relay. Network nodes also include one or more (or all) parts of distributed radio base stations, such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as remote radio heads (RRHs). obtain. Such remote radio units may or may not be integrated with an antenna as integrated antenna radios. Parts of a distributed radio base station are sometimes called nodes in a distributed antenna system (DAS). Still further examples of network nodes are MSR equipment such as multi-standard radio (MSR) BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes. , multi-cell/multicast coordination entity (MCE), core network Nodes (eg, MSC, MME), O&amp;M nodes, OSS nodes, SON nodes, positioning nodes (eg, E-SMLC), and/or MDTs. As another example, the network nodes may be virtual network nodes, as described in more detail below. More generally, however, a network node is capable of enabling and/or providing access to a wireless network to wireless devices or providing some service to wireless devices that have accessed the wireless network. It may represent any suitable device (or group of devices) configured, configured and/or operable to do so.

In FIG. 3, network node 160 includes processing circuitry 170 , device readable medium 180 , interface 190 , auxiliary equipment 184 , power supply 186 , power circuitry 187 and antenna 162 . Network node 160 shown in the exemplary wireless network of FIG. 2 may represent a device that includes the indicated combination of hardware components, although other embodiments have different combinations of components. It may contain network nodes. It should be understood that a network node includes any suitable combination of hardware and/or software required to perform the tasks, features, functions and methods disclosed herein. Moreover, although the components of network node 160 are illustrated as a single box located within a larger box or as a single box nested within multiple boxes, in reality: A network node may include multiple different physical components that make up a single depicted component (eg, device-readable medium 180 may include multiple separate hard drives as well as multiple RAM modules).

Similarly, network node 160 may be assembled from multiple physically separate components (eg, Node B and RNC components, or BTS and BSC components, etc.), each of which is itself can have each component of In some scenarios where network node 160 includes multiple distinct components (e.g., a BTS component and a BSC component), one or more of the distinct components may be connected between several network nodes. can be shared. For example, a single RNC may control multiple Node Bs. In such scenarios, each unique Node B and RNC pair may in some cases be considered a single distinct 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 (eg, separate device-readable media 180 for different RATs) and some components may be reused (eg, the same antenna 162 may be used by RATs). may be shared by). Network node 160 has multiple sets of components for the various different wireless technologies shown, e.g., GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into network node 160. can also include These wireless technologies may be integrated into the same or different chips or sets of chips and other components within network node 160 .

Processing circuitry 170 is configured to perform any determining, computing, or similar operations described herein as being provided by a network node (eg, some obtaining operations). be. These operations performed by processing circuitry 170 include processing the information obtained by processing circuitry 170, e.g., by transforming the obtained information into other information, obtaining information or converting one or more of comparing the obtained information with information stored in a network node and/or based on the obtained or transformed information and as a result of said processing making a decision may include performing the operations of

Processing circuitry 170 is a microprocessor, controller, operable to provide network node 160 functionality, either alone or in conjunction with other network node 160 components, such as device-readable media 180. A microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, a combination of one or more of the resources, or hardware, software and /or may contain a combination of coded logic. For example, processing circuitry 170 may execute instructions stored on device-readable medium 180 or instructions stored in memory within processing circuitry 170 . Such functionality may include providing any of the various wireless features, functions, or benefits described herein. In some embodiments, processing circuitry 170 may include a system-on-chip (SOC).

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

In some embodiments, some or all of the functionality described herein as provided by a network node, base station, eNB or other such network device may be provided on the device readable medium 180, or It may be implemented by processing circuitry 170 executing instructions stored in memory within processing circuitry 170 . In alternative embodiments, some or all of the functionality may be provided by processing circuitry 170 without executing instructions stored on a separate or separate device-readable medium, such as in a hardwired fashion. In any of those embodiments, whether or not to execute instructions stored on a device-readable storage medium, processing circuitry 170 may be configured to implement the described functionality. The benefits provided by such functionality are not limited to processing circuitry 170 alone or to other components of network node 160, but may be provided by network node 160 as a whole and/or by end users and wireless networks generally. , to be enjoyed.

Device readable media 180 include, but are not limited to, persistent storage, solid state memory, remote mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk ), any form of volatile or non-volatile computer readable memory, including removable storage media (e.g., flash drives, compact discs (CDs) or digital video discs (DVDs)), and/or used by processing circuitry 170. may include any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory device that stores information, data, and/or instructions that may be stored. Device readable media 180 may be executed by applications including one or more of computer programs, software, logic, rules, code, tables, etc., and/or processing circuitry 170 to network node 160. Any suitable instructions, data or information, including other instructions, utilized by the may be stored. Device-readable media 180 may be used to store calculations made by processing circuitry 170 and/or data received via interface 190 . In some embodiments, processing circuitry 170 and device readable medium 180 may be considered integrated.

Interface 190 is used in wired or wireless communication of signaling and/or data between network node 160, network 106, and/or WD 110. FIG. As shown, interface 190 includes port(s)/terminal(s) 194 for sending and receiving data to and from network 106, eg, over a wired connection. . Interface 190 also includes radio front-end circuitry 192 that may be coupled to antenna 162 or, in some embodiments, part of antenna 162 . Radio front end circuitry 192 includes filter 198 and amplifier 196 . Radio front end circuitry 192 may be connected to antenna 162 and processing circuitry 170 . Radio front-end circuitry may be configured to condition signals communicated between antenna 162 and processing circuitry 170 . Wireless front-end circuitry 192 may receive digital data to be sent to other network nodes or WDs over wireless connections. Radio front-end circuitry 192 may convert digital data into radio signals with 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 to digital data by radio front-end circuitry 192 . Digital data may be passed to processing circuitry 170 . In other embodiments, the interface may include different components and/or different combinations of components.

In some alternative embodiments, network node 160 may not include separate radio front-end circuitry 192; instead, processing circuitry 170 may include radio front-end circuitry and separate radio front-end circuitry. It can be connected to antenna 162 without circuitry 192 . Similarly, all or part of RF transceiver circuitry 172 may be considered part of interface 190 in some embodiments. In yet other embodiments, interface 190 includes one or more ports or terminals 194, radio front-end circuitry 192, and RF transceiver circuitry 172 as part of a radio unit (not shown). Additionally, interface 190 may communicate with baseband processing circuitry 174 that is part of a digital unit (not shown).

Antenna 162 may include one or more antennas or antenna arrays configured to transmit and/or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and/or signals. In some embodiments, antenna 162 may include one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals, eg, between 2 GHz and 66 GHz. Omni-directional antennas can be used to transmit/receive wireless signals in any direction, sector antennas can be used to transmit/receive wireless signals from devices within a specific area, and panel antennas can be used to It can be a line-of-sight antenna used for transmitting/receiving radio signals in a relatively straight line. In some instances, the use of two or more antennas may be referred to as MIMO. In some embodiments, antenna 162 may be separate from network node 160 and connectable to network node 160 through an interface or port. Antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any receive operation and/or some acquisition operations described herein 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, antenna 162, interface 190, and/or processing circuitry 170 may be configured to perform any transmission operation described herein 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.

Power circuitry 187 may include or be coupled to power management circuitry to provide power to the components of network node 160 to perform the functionality described herein. is set to Power circuitry 187 may receive power from power supply 186 . Power supply 186 and/or power circuitry 187 may be connected to various components of network node 160 in a form suitable for each component (eg, at voltage and current levels required for each respective component). can be set to provide power to Power supply 186 may either be included within power circuitry 187 and/or network node 160 or external to power circuitry 187 and/or network node 160 . For example, network node 160 may be connectable to an external power source (eg, an electrical outlet) via input circuitry or an interface such as an electrical cable, whereby the external power source provides power to power circuitry 187 . As a further example, power supply 186 may include a power source in the form of a battery or battery pack connected to or integrated within power circuitry 187 . A battery may provide backup power if the external power source fails. Other types of power sources such as photovoltaic devices may also be used.

An alternative embodiment of network node 160 is a network node that includes any of the functionality described herein and/or the functionality necessary to support the subject matter described herein. Additional components other than those shown in FIG. 3 may be included that may be responsible for providing some aspect of functionality. For example, network node 160 may include user interface equipment for enabling information input to network node 160 and for enabling information output from network node 160 . This may allow users to perform diagnostics, maintenance, repairs, and other management functions for network node 160 .

FIG. 4 shows a wireless device (WD) 110, according to some embodiments. WD as used herein refers to a device capable, configured, configured and/or operable to wirelessly communicate with network nodes and/or other wireless devices. . Unless otherwise noted, the term WD may be used interchangeably with user equipment (UE) herein. Communicating wirelessly involves sending and/or receiving radio signals using electromagnetic, radio, infrared, and/or other types of signals suitable for conveying information over the air. obtain. In some embodiments, the WD may be configured to send and/or receive information without direct human interaction. For example, WD can be designed to transmit information to the network on a predetermined schedule when triggered by internal or external events, or in response to requests from the network. Examples of WD include, but are not limited to, smart phones, mobile phones, cell phones, voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage. Devices, Playbacks, Wearable Terminal Devices, Wireless Endpoints, Mobile Stations, Tablets, Laptops, Laptop Embedded Equipment (LEE), Laptop Equipment (LME), Smart Devices, Wireless Customer Premises Equipment (CPE: customer premise equipment), in-vehicle wireless terminal devices, etc. WD supports device-to-device (D2D) communication, for example by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) It may be called a D2D communication device in this case. As yet another specific example, in an Internet of Things (IoT) scenario, WD performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or network node. It may represent a machine or other device that The WD may in this case be a machine-to-machine (M2M) device, which in the 3GPP context is sometimes referred to as an MTC device. As one specific example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g. refrigerators, televisions, etc.), personal wearables (e.g. watches , fitness trackers, etc.). In other scenarios, WD may represent a vehicle or other device that monitors and/or reports on its operational status, or performs other actions associated with its operation. function is possible. A WD as described above may represent an endpoint of a wireless connection, in which case the device is sometimes referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may also be referred to as a mobile device or mobile terminal. equipment), in-vehicle wireless terminal devices, etc. WD supports device-to-device (D2D) communication, for example by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) It may be called a D2D communication device in this case. As yet another specific example, in an Internet of Things (IoT) scenario, WD performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or network node. It may represent a machine or other device that The WD may in this case be a machine-to-machine (M2M) device, which in the 3GPP context is sometimes referred to as an MTC device. As one specific example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g. refrigerators, televisions, etc.), personal wearables (e.g. watches , fitness trackers, etc.). In other scenarios, WD may represent a vehicle or other device that monitors and/or reports on its operational status, or performs other actions associated with its operation. function is possible. A WD as described above may represent an endpoint of a wireless connection, in which case the device is sometimes referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may also be referred to as a mobile device or mobile terminal. equipment), in-vehicle wireless terminal devices, etc. WD supports device-to-device (D2D) communication, for example by implementing 3GPP standards for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) It may be called a D2D communication device in this case. As yet another specific example, in an Internet of Things (IoT) scenario, WD performs monitoring and/or measurements and transmits the results of such monitoring and/or measurements to another WD and/or network node. It may represent a machine or other device that The WD can in this case be a machine-to-machine (M2M) device, which in a 3GPP context is an M Sometimes called a TC device. As one specific example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g. refrigerators, televisions, etc.), personal wearables (e.g. watches , fitness trackers, etc.). In other scenarios, WD may represent a vehicle or other device that monitors and/or reports on its operational status, or performs other actions associated with its operation. function is possible. A WD as described above may represent an endpoint of a wireless connection, in which case the device is sometimes referred to as a wireless terminal. Additionally, the WD described above may be mobile, in which case the device may also be referred to as a mobile device or mobile terminal.

As shown, wireless device 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, ancillary equipment 134, power supply 136, and power circuitry. 137 and including. Of the components shown for the different wireless technologies supported by the WD110 are GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. may include multiple sets of one or more of These wireless technologies may be integrated into the same or different chip or set of chips as other components within WD 110 .

Antenna 111 , which may include one or more antennas or antenna arrays configured to transmit and/or receive radio signals, is connected to interface 114 . In some alternative embodiments, antenna 111 may be separate from WD 110 and connectable to WD 110 through an interface or port. Antenna 111, interface 114, and/or processing circuitry 120 may be configured to perform any receive or transmit operation described herein as being performed by the WD. Any information, data and/or signals may be received from a network node and/or another WD. In some embodiments, radio front-end circuitry and/or antenna 111 may be considered an interface.

As shown, interface 114 includes radio front-end circuitry 112 and antenna 111 . Radio front-end circuitry 112 includes one or more filters 118 and amplifiers 116 . Radio front-end circuitry 112 is connected to antenna 111 and processing circuitry 120 and is configured to condition signals communicated between antenna 111 and processing circuitry 120 . Radio front-end circuitry 112 may be coupled to or part of antenna 111 . In some embodiments, WD 110 may not include separate radio front-end circuitry 112 , rather processing circuitry 120 may include radio front-end circuitry and may be connected to antenna 111 . Similarly, some or all of RF transceiver circuitry 122 may be considered part of interface 114 in some embodiments. Wireless front-end circuitry 112 may receive digital data to be sent to other network nodes or WDs over wireless connections. Radio front-end circuitry 112 may convert digital data into radio signals with appropriate channel and bandwidth parameters using a combination of filters 118 and/or amplifiers 116 . The radio signal can then be transmitted via antenna 111 . Similarly, when receiving data, antenna 111 may collect radio signals, which are then converted to digital data by radio front-end circuitry 112 . Digital data may be passed to processing circuitry 120 . In other embodiments, the interface may include different components and/or different combinations of components.

Processing circuitry 120 is a microprocessor, controller, microcontroller, central processor, operable to provide WD110 functionality, either alone or in conjunction with other WD110 components, such as device-readable media 130. A processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, a combination of one or more of the resources, or hardware, software and/or coding may contain a combination of the logic described. Such functionality may include providing any of the various wireless features or benefits described herein. For example, processing circuitry 120 may execute instructions stored on device-readable medium 130 or instructions stored in memory within processing circuitry 120 to provide the functionality disclosed herein. .

As shown, processing circuitry 120 includes one or more of RF transceiver circuitry 122 , baseband processing circuitry 124 , and application processing circuitry 126 . In other embodiments, the processing circuitry may include different components and/or different combinations of components. In some embodiments, processing circuitry 120 of WD 110 may include a SOC. In some embodiments, RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be on separate chips or sets of chips. In an alternative embodiment, some or all of the baseband processing circuitry 124 and application processing circuitry 126 may be combined into one chip or set of chips, and the RF transceiver circuitry 122 may be on a separate chip or chip. Can be on set. In a further alternative embodiment, some or all of the RF transceiver circuitry 122 and baseband processing circuitry 124 may be on the same chip or set of chips, and the application processing circuitry 126 may be on a separate chip or set of chips. can be In yet other alternative embodiments, some or all of RF transceiver circuitry 122, baseband processing circuitry 124, and application processing circuitry 126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry 122 may be part of interface 114 . RF transceiver circuitry 122 may condition the RF signal for processing circuitry 120 .

In some embodiments, some or all of the functionality described herein as performed by the WD may be provided by processing circuitry 120 executing instructions stored on device-readable medium 130. , the device-readable medium 130 may be a computer-readable storage medium in some embodiments. In alternative embodiments, some or all of the functionality may be provided by processing circuitry 120 without executing instructions stored on a separate or separate device-readable storage medium, such as in a hardwired fashion. In any of those particular embodiments, processing circuitry 120 may be configured to implement the described functionality, whether or not to execute instructions stored on a device-readable storage medium. The benefits provided by such functionality are not limited to processing circuitry 120 alone or other components of WD 110, but are enjoyed by WD 110 as a whole and/or by end users and wireless networks generally. .

Processing circuitry 120 may be configured to perform any determining, computing, or similar operations (e.g., some obtaining operations) described herein as being performed by the WD. . These operations, as performed by processing circuitry 120, include processing the information obtained by processing circuitry 120, for example, by transforming the obtained information into other information; or comparing the transformed information with information stored by WD 110, and/or based on the information obtained or transformed and as a result of said processing making a decision, one or It may involve performing multiple actions.

Device readable medium 130 stores applications including one or more of computer programs, software, logic, rules, code, tables, etc., and/or other instructions capable of being executed by processing circuitry 120. may be operable to Device-readable media 130 may be computer memory (eg, random access memory (RAM) or read-only memory (ROM)), mass storage media (eg, hard disks), removable storage media (eg, compact discs (CDs) or digital video disk (DVD)) and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable that stores information, data, and/or instructions that may be used by the processing circuitry 120 capable memory devices. In some embodiments, processing circuitry 120 and device-readable medium 130 may be considered integrated.

User interface device 132 may provide components that allow a human user to interact with WD 110 . Such interaction can be in many forms, such as visual, auditory, and tactile. User interface device 132 may be operable to produce output to the user and allow the user to provide input to WD 110 . The type of interaction may vary depending on the type of user interface device 132 installed on WD 110 . For example, if the WD110 is a smartphone, the interaction could be via a touchscreen, if the WD110 is a smart meter, the interaction could be a screen providing usage (e.g., number of gallons used), or It may be through a speaker that provides an audible alarm (eg, if smoke is detected). User interface equipment 132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface device 132 is configured to allow input of information to WD 110 and is connected to processing circuitry 120 to allow processing circuitry 120 to process the input information. User interface device 132 may include, for example, a microphone, proximity or other sensor, keys/buttons, touch display, one or more cameras, USB ports, or other input circuitry. User interface device 132 is also configured to enable output of information from WD 110 and processing circuitry 120 to output information from WD 110 . User interface device 132 may include, for example, speakers, displays, vibration circuitry, USB ports, headphone interfaces, or other output circuitry. Using one or more of the input and output interfaces, devices, and circuits of user interface equipment 132, WD 110

Auxiliary equipment 134 is operable to provide more specific functionality that may not generally be implemented by WD. This may include specialized sensors for taking measurements for various purposes, interfaces for additional types of communication such as wired communication, and the like. The inclusion and type of components of ancillary equipment 134 may vary depending on the embodiment and/or scenario.

Power source 136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as external power sources (eg, electrical outlets), photovoltaic devices or batteries. WD 110 includes power circuitry 137 for delivering power to various portions of WD 110 that require power from power supply 136 to perform any functionality described or illustrated herein. can further include Power circuitry 137 may include power management circuitry in some embodiments. Power circuitry 137 may additionally or alternatively be operable to receive power from an external power source, in which case WD 110 may receive power via input circuitry such as a power cable or interface (such as an electrical outlet). It may be connectable to an external power source. Power circuitry 137 may also be operable to deliver power from an external power source to power source 136 in some embodiments. This may be for charging the power supply 136, for example. Power circuitry 137 performs any formatting, transformations, or other modifications to the power from power supply 136 to make it suitable for the respective component of WD 110 to which it is powered. can be implemented.

FIG. 5 illustrates one embodiment of a UE 200, according to various aspects described herein. User equipment or UE as used herein does not necessarily have a user in the sense of a human user who owns and/or operates the associated device. Alternatively, a UE is intended for sale to or operation by a human user, but may not be associated with a particular human user, or may be initially associated with a particular human user. It may represent a device (eg, a smart sprinkler controller) that may not exist. Alternatively, UE represents a device (e.g., smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. obtain. UE200 is NB-IoT It may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. The UE 200 shown in FIG. 5 is configured for communication according to one or more communication standards promulgated by 3GPP, such as the GSM, UMTS, LTE, and/or 5G standards of the 3rd Generation Partnership Project (3GPP). It is an example of the WD that was made. As noted above, the terms WD and UE may be used interchangeably. Thus, although FIG. 5 is a UE, the components described herein are equally applicable to WD and vice versa.

In FIG. 5, UE 200 includes input/output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217 and read only memory (ROM) 219, storage medium 221, and the like. , communication subsystem 231, power supply 213, and/or other components, or any combination thereof. Storage medium 221 includes operating system 223 , application programs 225 and data 227 . In other embodiments, storage medium 221 may contain other similar types of information. Some UEs may utilize all of the components shown in FIG. 5 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, some UEs may include multiple instances of components such as multiple processors, memories, transceivers, transmitters, receivers, and so on.

In FIG. 5, processing circuitry 201 may be configured to process computer instructions and data. Processing circuitry 201 is operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (eg, in discrete logic, FPGA, ASIC, etc.). One or more programmed, general-purpose processors, such as any sequential state machine, programmable logic with appropriate firmware, microprocessors or digital signal processors (DSPs) with appropriate software, or any combination of the above. can be configured to implement For example, processing circuitry 201 may include two central processing units (CPUs). The data may be information in any form suitable for use by a computer.

In the illustrated embodiment, input/output interface 205 may be configured to provide a communication interface to input devices, output devices, or input/output devices. UE 200 may be configured to use output devices 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 to and output from the UE200. The output device can be a speaker, sound card, video card, display, monitor, printer, actuator, emitter, smart card, another output device, or any combination thereof. UE 200 may be configured to use input devices via input/output interface 205 to allow a user to capture information into UE 200 . Input devices include touch- or presence-sensitive displays, cameras (e.g., digital cameras, digital video cameras, webcams, etc.), microphones, sensors, mice, trackballs, directional pads, trackpads, scroll wheels, smart cards, etc. obtain. Presence sensitive displays may include capacitive or resistive touch sensors for sensing input from a user. The sensors can be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, light sensors, proximity sensors, another similar sensor, or any combination thereof. For example, input devices can be accelerometers, magnetometers, digital cameras, microphones, and light sensors.

In FIG. 5, RF interface 209 may be configured to provide a communication interface to RF components such as transmitters, receivers, and antennas. Network connection interface 211 may be configured to provide a communication interface to 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 communications network, another similar network, or any combination thereof. . For example, network 243a may include a Wi-Fi network. Network connection interface 211 is a receiver and transmitter 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, etc. can be configured to include an aircraft interface. Network connection interface 211 may implement receiver and transmitter functionality suitable for communication network links (eg, optical, electrical, etc.). Transmitter and receiver functions may share circuitry, software or firmware, or alternatively may be implemented separately.

RAM 217 is configured to interface with processing circuitry 201 via bus 202 to provide storage or caching of data or computer instructions during execution of software programs such as operating systems, application programs, and device drivers. can be ROM 219 may be configured to provide computer instructions or data to processing circuitry 201 . For example, ROM 219 stores immutable low-level system code or data for basic system functions such as basic input/output (I/O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. can be set to Storage medium 221 may include RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable Can be configured to contain memory, such as a cartridge, or flash drive. In one example, storage medium 221 may be configured to include an operating system 223 , application programs 225 such as a web browser application, widget or gadget engine, or another application, and data files 227 . Storage medium 221 may store any of a wide variety of different operating systems or combinations of operating systems for use by UE 200 .

The storage medium 221 may be a redundant array of independent disks (RAID), floppy disk drives, flash memory, USB flash drives, external hard disk drives, thumb drives, pen drives, key drives, high density digital versatile disc (HD-DVD) optical discs. Drives, Internal Hard Disk Drives, Blu-Ray Optical Disk Drives, Holographic Digital Data Storage (HDDS) Optical Disk Drives, External Mini Dual Inline Memory Modules (DIMMs), Synchronous Dynamic Random Access Memory (SDRAM), External Micro DIMMs It may be configured to include several physical drive units such as SDRAM, smart card memory such as subscriber identity modules or removable user identity (SIM/RUIM) modules, other memory, or any combination thereof. Storage media 221 may allow UE 200 to access computer-executable instructions, application programs, etc., offload data, or upload data stored on temporary or non-transitory memory media. . An article of manufacture, such as an article of manufacture that utilizes a communication system, may be tangibly embodied in storage medium 221, which may include device-readable media.

5, processing circuitry 201 may be configured to communicate with network 243b using communication subsystem 231. In FIG. Network 243a and network 243b may be the same network or networks or different networks or networks. Communication subsystem 231 may be configured to include one or more transceivers used to communicate with network 243b. For example, the communication subsystem 231 communicates with other WDs, UEs, or base stations of the Radio Access Network (RAN) according to one or more communication protocols such as IEEE802.4, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. etc., 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. Each transceiver may include a transmitter 233 and/or receiver 235 for implementing transmitter or receiver functionality appropriate for the RAN link (eg, frequency allocation, etc.), respectively. Additionally, the transmitter 233 and receiver 235 of each transceiver may share circuitry, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem 231 include data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, global positioning system (GPS) for determining location, and so on. ), another similar communication facility, or any combination thereof. For example, communications subsystem 231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. Network 243b 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 communications network, another similar network, or any combination thereof. . For example, network 243b can be a cellular network, a Wi-Fi network, and/or a near-field network. Power supply 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of UE 200 .

Features, benefits and/or functions described herein may be implemented in one of the components of UE 200 or split across multiple components of UE 200 . Furthermore, the features, benefits and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem 231 can be configured to include any of the components described herein. Additionally, processing circuitry 201 may be configured to communicate with any of such components over bus 202 . In another example, any of such components are represented by program instructions stored in memory that, when executed by processing circuitry 201, perform the corresponding functions described herein. can be In another example, the functionality of any such components may be split between processing circuitry 201 and communication subsystem 231 . In another example, non-computation-intensive functions of any such components may be implemented in software or firmware, and computation-intensive functions may be implemented in hardware.

FIG. 6 is a schematic block diagram illustrating a virtualization environment 300 in which functionality implemented by some embodiments may be virtualized. In this context, virtualizing means creating a virtual version of a device or device, which can include virtualizing the hardware platform, storage devices and networking resources. Virtualization, as used herein, refers to a node (e.g., virtualized base station or virtualized radio access node) or device (e.g., UE, wireless device or any other type of communication device). ) or components of that device, where at least a portion of the functionality is (e.g., one or more applications executing on one or more physical processing nodes in one or more networks, configuration Pertaining to implementations implemented as one or more virtual components (via elements, functions, virtual machines or containers).

In some embodiments, some or all of the functionality described herein is implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. or as a virtual component executed by multiple virtual machines. Further, in embodiments where the virtual node is not a radio access node or does not require radio connectivity (eg, core network node), the network node may be fully virtualized.

A facility is operable to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein (alternatively, software instances, virtual , network functions, virtual nodes, virtual network functions, etc.) may be implemented by one or more applications 320 . Application 320 runs in virtualized environment 300, which provides hardware 330, including processing circuitry 360 and memory 390-1. Memory 390-1 includes instructions 395 executable by processing circuitry 360 to enable application 320 to implement one or more of the features, benefits, and/or functions disclosed herein. is operable to provide

The virtualization environment 300 includes a general-purpose or dedicated network hardware device 330 that includes one or more sets of processors or processing circuitry 360, which are commercially available. Off-the-shelf (COTS: commercial off-the-shelf) processor, a dedicated application specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include 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 include one or more network interface controllers (NICs) 370 , also known as network interface cards, which include physical network interfaces 380 . Each hardware device may also include a non-transitory, permanent, machine-readable storage medium 390-2 that stores software 395 and/or instructions executable by processing circuitry 360. Software 395 includes software for instantiating one or more virtualization layers (also called hypervisors) 350, software for running virtual machines 340, and any number of them described herein. It may include any type of software, including software that enables the functions, features and/or benefits described in connection with any embodiment.

A virtual machine 340 includes virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the virtual appliance 320 instance may be implemented on one or more of the virtual machines 340, and may be implemented differently.

In operation, processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, sometimes referred to as a virtual machine monitor (VMM). Virtualization layer 350 may present virtual machine 340 with a virtual operating platform that looks like networking hardware.

As shown in FIG. 6, hardware 330 may be a standalone network node with general or specific components. Hardware 330 may include antenna 3225 and may implement some functions through virtualization. Alternatively, hardware 330 is managed via management and orchestration (MANO) 3100, in which many hardware nodes cooperate and, among other things, oversee lifecycle management of applications 320 (e.g., data center or may be part of a larger cluster of hardware (as in the case of Customer Premises Equipment (CPE)).

Hardware virtualization is called network function virtualization (NFV) in some contexts. NFV can be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that can be located in data centers and customer premises equipment.

In the context of NFV, virtual machine 340 may be a software implementation of a physical machine that runs programs as if those programs were running on a physical, non-virtualized machine. Each of virtual machines 340 and its virtual machines, whether hardware dedicated to that virtual machine and/or shared by that virtual machine with other virtual machines of virtual machines 340 That part of the hardware 330 that executes it forms a separate virtual network element (VNE).

Further, in the context of NFV, a Virtual Network Function (VNF) is responsible for handling specific network functions running in one or more virtual machines 340 on top of the hardware networking infrastructure 330, Corresponds to the application 320.

In some embodiments, one or more wireless units 3200, each including one or more transmitters 3220 and one or more receivers 3210, are coupled to one or more antennas 3225. obtain. The wireless unit 3200 may communicate directly with the hardware node 330 via one or more suitable network interfaces and combine with virtual components to provide a virtual node with wireless capabilities, such as a wireless access node or base station. can be used

In some embodiments, some signaling may be implemented using control system 3230, which may alternatively be used for communication between hardware node 330 and radio unit 3200.

FIG. 7 illustrates a communication network connected to host computers via intermediate networks, according to some embodiments. Referring to FIG. 7, according to one embodiment, a communication system includes a communication network 410, such as a 3GPP type cellular network, including an access network 411, such as a radio access network, and a core network 414. The access network 411 includes multiple base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412 a , 412 b , 412 c is connectable to core network 414 over wired or wireless connection 415 . A first UE 491 located in the coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in the coverage area 413a is wirelessly connectable to the corresponding base station 412a. Although multiple UEs 491, 492 are shown in this example, the disclosed embodiments apply to situations where only one UE is in the coverage area or is connected to the corresponding base station 412. Equally applicable.

The communication network 410 is itself connected to a host computer 430, which can be embodied in hardware and/or software of a stand-alone server, cloud-implemented server, distributed server, or as processing resources in a server farm. . Host computer 430 may be owned or controlled by a service provider or may be operated by or on behalf of a service provider. Connections 421 and 422 between communication network 410 and host computer 430 may extend directly from core network 414 to host computer 430 or may go through optional intermediate network 420 . Intermediate network 420 may be one of a public network, a private network, or a hosted network, or a combination of two or more of them, and intermediate network 420 may be a backbone network or the Internet, if any. Possibly, in particular, intermediate network 420 may include two or more sub-networks (not shown).

The communication system of FIG. 7 as a whole allows connectivity between connected UEs 491 , 492 and host computer 430 . Connectivity can be described as an over-the-top (OTT) connection 450 . Host computer 430 and connected UEs 491, 492 communicate over OTT connection 450 using access network 411, core network 414, optional intermediate network 420, and possible further infrastructure (not shown) as intermediaries. , is configured to communicate data and/or signaling. The OTT connection 450 may be transparent in the sense that the participating communication devices through which the OTT connection 450 passes are unaware of the routing of uplink and downlink communications. For example, base station 412 may or may not be informed of the past routing of incoming downlink communications with data originating from host computer 430 to be forwarded (eg, handed over) to connected UE 491 . no need to Similarly, base station 412 need not be aware of future routing of outgoing uplink communications originating from UE 491 and destined for host computer 430 .

FIG. 8 is a diagram illustrating a host computer communicating with user equipment via a base station over a partial wireless connection, according to some embodiments. An exemplary implementation of the UE, base station and host computer described in the previous paragraph according to one embodiment will now be described with reference to FIG. In communication system 500 , host computer 510 includes hardware 515 , including communication interface 516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of communication system 500 . Host computer 510 further includes processing circuitry 518, which may have storage and/or processing capabilities. In particular, processing circuitry 518 may include one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. Host computer 510 further includes software 511 stored on or accessible by host computer 510 and executable by processing circuitry 518 . Software 511 includes host application 512 . Host application 512 may be operable to serve remote users, such as UE 530 and UE 530 connecting via OTT connection 550 terminating at host computer 510 . In providing services to remote users, host application 512 may provide user data that is transmitted using OTT connection 550 .

Communication system 500 further includes a base station 520 provided in the communication system, which includes hardware 525 that enables base station 520 to communicate with host computer 510 and UE 530 . Hardware 525 includes communication interface 526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of communication system 500, as well as the coverage area served by base station 520 (not shown in FIG. 8). A wireless interface 527 may be included for setting up and maintaining at least a wireless connection 570 with a UE 530 located therein. Communication interface 526 may be configured to facilitate connection 560 to host computer 510 . Connection 560 may be direct, or connection 560 may pass through the core network of the communication system (not shown in FIG. 8) and/or through one or more intermediate networks external to the communication system. In the illustrated embodiment, the hardware 525 of the base station 520 further includes processing circuitry 528, which may be one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or It may include combinations of these (not shown) adapted to execute instructions. Base station 520 further has software 521 stored internally or accessible via an external connection.

Communication system 500 further includes UE 530 already mentioned. Hardware 535 of UE 530 may include a wireless interface 537 configured to set up and maintain a wireless connection 570 with a base station serving the coverage area in which UE 530 is currently located. Hardware 535 of UE 530 further includes processing circuitry 538, which may be one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or adapted to execute instructions. It may also include combinations of these (not shown). UE 530 further includes software 531 stored on or accessible by UE 530 and executable by processing circuitry 538 . Software 531 includes client application 532 . Client application 532 may be operable to provide services to human or non-human users via UE 530 with the support of host computer 510 . At host computer 510 , a running host application 512 may communicate with a running client application 532 over an OTT connection 550 terminating at UE 530 and host computer 510 . In providing services to a user, client application 532 may receive request data from host application 512 and provide user data in response to the request data. OTT connection 550 may transfer both request data and user data. Client application 532 may interact with a user to generate user data that client application 532 provides.

Host computer 510, base station 520 and UE 530 shown in FIG. 8 are similar to host computer 430, one of base stations 412a, 412b, 412c and one of UE 491, 492, respectively, of FIG. or equivalent. That is, the internal workings of these entities may be as shown in FIG. 8, and separately the surrounding network topology may be that of FIG.

In FIG. 8, OTT connection 550 shows communication between host computer 510 and UE 530 via base station 520 without explicit reference to intermediary devices and the precise routing of messages via these devices. It is drawn abstractly for The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 530 or from the service provider operating the host computer 510, or both. While the OTT connection 550 is active, the network infrastructure may also make decisions to dynamically change routing (eg, based on load balancing considerations or reconfiguration of the network).

Wireless connection 570 between UE 530 and base station 520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE 530 using OTT connection 550 with wireless connection 570 forming the last segment. More precisely, the teachings of these embodiments may improve the UE's beam classification behavior to improve its ability to build self-optimizing network functionality.

Measurement procedures may be provided for the purpose of monitoring data rates, latencies and other factors that one or more embodiments improve upon. There can also be optional network functionality to reconfigure the OTT connection 550 between the host computer 510 and the UE 530 in response to changes in the measurement results. Network functionality for reconfiguring the measurement procedure and/or OTT connection 550 may be implemented in software 511 and hardware 515 of host computer 510 or software 531 and hardware 535 of UE 530, or both. In embodiments, a sensor (not shown) may be deployed at or associated with the communication device through which the OTT connection 550 passes, the sensor providing the values of the monitored quantities exemplified above, or The software 511, 531 may participate in the measurement procedure by supplying values of other physical quantities from which the monitored quantity can be calculated or estimated. Reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc. The reconfiguration need not affect the base station 520 and the reconfiguration is unknown to the base station 520. or may be imperceptible. Such procedures and functionality are known in the art and can be implemented. In some embodiments, the measurements may involve proprietary UE signaling that facilitates host computer 510 measurements of throughput, propagation time, latency, and the like. Measurements cause software 511 and 531 to send messages, especially empty or "dummy" messages, using OTT connection 550 while software 511 and 531 monitor propagation times, errors, etc. can be implemented in

FIG. 9 is a flow chart illustrating a method implemented in a communication system, according to some embodiments. The communication system includes host computers, base stations and UEs, which may be as described with reference to FIGS. For simplicity of this disclosure, only drawing reference to FIG. 9 is included in this section. At step 610, the host computer provides user data. In sub-step 611 (which may be optional) of step 610, the host computer provides user data by executing the host application. At step 620, the host computer initiates a transmission that carries user data to the UE. At step 630 (which may be optional), the base station transmits to the UE the user data carried in the host computer-initiated transmission in accordance with the teachings of the embodiments described throughout this disclosure. In step 640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Figure 10 is a flow chart illustrating a method implemented in a communication system, according to some embodiments. The communication system includes host computers, base stations and UEs, which may be as described with reference to FIGS. For simplicity of this disclosure, only drawing reference to FIG. 10 is included in this section. In step 710 of the method, the host computer provides user data. In an optional substep (not shown), the host computer provides user data by executing the host application. At step 720, the host computer initiates a transmission that carries user data to the UE. Transmission may proceed via base stations in accordance with the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives user data carried in the transmission.

Figure 11 is a flow chart illustrating a method implemented in a communication system, according to some embodiments. The communication system includes host computers, base stations and UEs, which may be as described with reference to FIGS. For simplicity of this disclosure, only drawing reference to FIG. 11 is included in this section. At step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application that provides user data in response to the received input data provided by the host computer. In providing user data, the executed client application may further consider user input received from the user. Regardless of the particular manner in which the user data was provided, the UE initiates transmission of the user data to the host computer in sub-step 830 (which may be optional). At method step 840, the host computer receives user data transmitted from the UE in accordance with the teachings of the embodiments described throughout this disclosure.

Figure 12 is a flow chart illustrating a method implemented in a communication system, according to some embodiments. The communication system includes host computers, base stations and UEs, which may be as described with reference to FIGS. For simplicity of this disclosure, only drawing reference to FIG. 12 is included in this section. At step 910 (which may be optional), the base station receives user data from the UE in accordance with the teachings of the embodiments described throughout this disclosure. At step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. At step 930 (which may be optional), the host computer receives user data carried in the transmission initiated by the base station.

Any suitable step, method, feature, function or benefit disclosed herein may be implemented through one or more functional units or modules of one or more virtual devices. Each virtual device may contain several of these functional units. These functional units are implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, etc. can be The processing circuitry may include one or several types of memory, such as read only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, etc. It can be configured to run code. Program code stored in memory comprises program instructions for executing one or more communication and/or data communication protocols and instructions for performing one or more of the techniques described herein. including. In some implementations, processing circuitry may be used to cause respective functional units to perform corresponding functions according to one or more embodiments of the present disclosure.

FIG. 13 illustrates a method in a wireless network, according to some embodiments. The method begins at step 1002 by determining whether event-triggered reporting, periodic reporting, and/or beam reporting are configured. The method continues at step 1004 with sorting the neighbor cell measurements for measurement reports based on the determination. The method continues at step 1006 with reporting the measurement report to the network node based on the determination and classification.

FIG. 14 shows a schematic block diagram of an apparatus 1100 in a wireless network (eg, the wireless network shown in FIG. 2), according to some embodiments. The apparatus may be implemented in a wireless device or network node (eg, wireless device 110 or network node 160 shown in FIG. 2). Apparatus 1100 is operable to perform the exemplary method described with respect to FIG. 13, and possibly any other process or method disclosed herein. Also, it should be understood that the method of FIG. 13 is not necessarily performed by device 1100 alone. At least some acts of the method may be performed by one or more other entities.

Virtual device 1100 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), specialized digital logic, and the like. The processing circuitry executes program code stored in memory, which may include one or several types of memory such as read only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. can be set to The program code stored in memory, in some embodiments, is program instructions for executing one or more communication and/or data communication protocols and one of the techniques described herein. or containing an instruction to do more than one. In some implementations, the processing circuitry provides decision unit 1110, classification unit 1120, and reporting unit 1130, any other suitable unit of apparatus 1100 with the functionality of the present disclosure, such as the functionality described in FIG. It can be used to perform corresponding functionality according to one or more embodiments.

The term unit may have its usual meaning in the field of electronics, electrical devices and/or electronic devices, e.g. May include electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions, etc., for performing/or performing display functions.

FIG. 15 illustrates a method by wireless device 110 for measurement reporting, according to some embodiments. The method begins at step 1210 with wireless device 110 sorting a plurality of measurements for a measurement report based on at least one metric.

In certain embodiments, the metric is a network-configured reporting quantity. In another embodiment, the metric is a triggering quantity from a set of multiple triggering quantities set by the network.

In certain embodiments, the plurality of measurements includes beam level measurements. Additionally or alternatively, the plurality of measurements includes cell level measurements.

In particular embodiments, the plurality of measurements is for the wireless device's serving cell. Additionally or alternatively, the plurality of measurements are for neighboring cells of the wireless device.

In step 1220, wireless device 110 reports to network node 160 a measurement report including measurement information selected from the plurality of measurements based on a classification of the plurality of measurements based on at least one metric.

In certain embodiments, the measurement information includes at least one of multiple measurements. Additionally or alternatively, the measurement information may include beam indices.

In certain embodiments, the measurement report includes beam level information for primary cells (PCell) and secondary cells (SCell).

In particular embodiments, wireless device 110 detects fulfillment of measurement reporting criteria and, in response to detecting fulfillment of measurement reporting criteria, sorts a plurality of measurements for a measurement report. .

In certain embodiments, wireless device 110 is configured for periodic reporting. Wireless device 110 may receive information indicative of at least one metric from a network node.

For example, in certain embodiments, at least one metric indicates that only the beam index is to be reported as part of the beam level report, and wireless device 110 classifies the multiple measurements based on RSRP. .

In another exemplary embodiment, at least one measurement quantity is indicative of RSRP, and wireless device 110 sorts the multiple measurements based on RSRP.

In yet another exemplary embodiment, at least one measurement quantity indicates an RSRQ, and wireless device 110 sorts the multiple measurements based on the RSRQ.

In yet another exemplary embodiment, at least one metric is indicative of SINR, and wireless device 110 sorts the multiple measurements based on the SINR.

In yet another exemplary embodiment, the at least one measurement quantity indicates RSRP and at least one of SINR and RSRQ, and wireless device 110 classifies the plurality of measurements based on RSRP.

In certain embodiments, the wireless device is configured for event-triggered reporting and the at least one measurement quantity includes the trigger quantity.

In certain embodiments, the plurality of measurements includes one or more measurements for neighboring cells of the wireless device, and the wireless device 110 selects at least one best neighbor that does not exceed the maximum number of cells to be reported. To identify a cell, classify one or more measurements for neighboring cells. In certain embodiments, the best measurement of the multiple measurements of the measurement type associated with the triggering quantity may be reported first in the measurement report.

FIG. 16 shows a schematic block diagram of an apparatus 1300 in a wireless network (eg, the wireless network shown in FIG. 2). The apparatus may be implemented in a wireless device or network node (eg, wireless device 110 or network node 160 shown in FIG. 2). Apparatus 1300 is operable to perform the exemplary method described with respect to FIG. 15, and possibly any other process or method disclosed herein. Also, it should be understood that the method of FIG. 15 is not necessarily performed by device 1300 alone. At least some acts of the method may be performed by one or more other entities.

Virtual device 1300 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), specialized digital logic, and the like. The processing circuitry executes program code stored in memory, which may include one or several types of memory such as read only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. can be set to The program code stored in memory, in some embodiments, is program instructions for executing one or more communication and/or data communication protocols and one of the techniques described herein. or containing an instruction to do more than one. In some implementations, processing circuitry provides classification unit 1310, reporting unit 1320, and any other suitable unit of apparatus 1300 with one or more of the features of the present disclosure, such as the functionality described in FIG. may be used to implement corresponding functionality according to embodiments of

For example, sorting unit 1310 may implement the sorting function of device 1300 . In certain embodiments, classification unit 1310 may classify measurements for a measurement report based on at least one metric.

For example, reporting unit 1320 may implement the reporting functionality of device 1300 . In particular embodiments, reporting unit 1320 may report to network node 160 a measurement report including measurement information selected from a plurality of measurements based on a classification of the plurality of measurements based on at least one metric.

The term unit may have its usual meaning in the field of electronics, electrical devices and/or electronic devices, e.g. May include electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions, etc., for performing/or performing display functions.

FIG. 17 illustrates a method by network node 160 for configuring wireless device 110 for measurement reporting, according to some embodiments. The method begins at step 1410 with network node 160 configuring wireless device 110 for event-based measurement reporting.

In certain embodiments, the plurality of measurements includes beam level measurements. Additionally or alternatively, the plurality of measurements includes cell level measurements.

In particular embodiments, the plurality of measurements is for the serving cell of wireless device 110 . Additionally or alternatively, in certain embodiments, the plurality of measurements are for neighboring cells of wireless device 110 .

At step 1420, network node 160 receives from wireless device 110 a measurement report including measurement information selected from the plurality of measurements based on a classification of the plurality of measurements. A classification of the plurality of measurements is responsive to detection of the event.

In certain embodiments, the measurement information includes at least one of multiple measurements. Additionally or alternatively, in certain embodiments, the measurement information includes beam index.

In certain embodiments, the measurement report may include PCell and SCell beam level information.

In certain embodiments, multiple measurements are sorted for a measurement report based on at least one metric.

In certain embodiments, the metric is a network-configured reporting quantity.

In certain embodiments, the metric is a triggering quantity from a set of multiple triggering quantities set by the network.

According to some particular embodiments, network node 160 may transmit information indicative of at least one metric to wireless devices.

In certain exemplary embodiments, at least one metric indicates that only the beam index is to be reported as part of the beam level report, and the multiple measurements are sorted based on RSRP.

In another exemplary embodiment, at least one metric is indicative of RSRP and the plurality of measurements are classified based on RSRP.

In yet another exemplary embodiment, at least one metric is indicative of RSRQ, and the plurality of measurements are categorized based on RSRQ.

In yet another exemplary embodiment, at least one metric is indicative of SINR, and the plurality of measurements are classified based on SINR.

In yet another exemplary embodiment, the at least one metric is indicative of RSRP and at least one of SINR and RSRQ, and the plurality of measurements are classified based on RSRP.

In certain embodiments, configuring wireless device 110 for event-based measurement reporting may include configuring wireless device 110 for event-triggered reporting, wherein at least one measurement quantity includes a triggering quantity. .

In certain embodiments, the best measurement of the multiple measurements of the measurement type associated with the triggering quantity is reported first in the measurement report.

In particular embodiments, network node 160 may configure wireless device 110 for periodic reporting.

In certain embodiments, the plurality of measurements includes one or more measurements for neighboring cells of the wireless device, and the one or more measurements for neighboring cells are used to identify at least one best neighboring cell. being classified. At least one best neighbor does not exceed the maximum number of cells to be reported.

FIG. 18 shows a schematic block diagram of an apparatus 1500 in a wireless network (eg, the wireless network shown in FIG. 2). The apparatus may be implemented in a wireless device or network node (eg, wireless device 110 or network node 160 shown in FIG. 2). Apparatus 1500 is operable to perform the exemplary method described with respect to FIG. 17 and possibly any other process or method disclosed herein. Also, it should be understood that the method of FIG. 17 is not necessarily performed by device 1500 alone. At least some acts of the method may be performed by one or more other entities.

Virtual device 1500 may include processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), specialized digital logic, and the like. The processing circuitry executes program code stored in memory, which may include one or several types of memory such as read only memory (ROM), random access memory, cache memory, flash memory devices, optical storage devices, etc. can be set to The program code stored in memory, in some embodiments, is program instructions for executing one or more communication and/or data communication protocols and one of the techniques described herein. or containing an instruction to do more than one. In some implementations, processing circuitry provides configuration unit 1510, receiving unit 1520, and any other suitable unit of apparatus 1500 with one or more of the present disclosure, such as the functionality described in FIG. may be used to implement corresponding functionality according to embodiments of

For example, configuration unit 1510 may perform configuration functions of device 1500 . In particular embodiments, configuration unit 1510 may configure wireless device 110 for event-based measurement reporting.

For example, receiving unit 1520 may implement the receiving functionality of apparatus 1500 . In particular embodiments, receiving unit 1520 may receive from wireless device 110 a measurement report containing measurement information selected from a plurality of measurements based on classification of the plurality of measurements in response to detection of an event.

The term unit may have its usual meaning in the field of electronics, electrical devices and/or electronic devices, e.g. May include electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions, etc., for performing/or performing display functions.

Exemplary Embodiments According to some exemplary embodiments, a method implemented by a wireless device for measurement reporting includes whether event-triggered reporting is configured for the wireless device, periodic reporting, is configured and/or beam reporting is configured; classifying neighbor cell measurements for a measurement report based on the determination; and classifying the measurement report based on the determination and classification and reporting to a network node. Optionally, the method may further comprise providing user data and forwarding the user data to the host computer via transmission to the base station.

According to some exemplary embodiments, a wireless device for measurement reporting comprises processing circuitry configured to perform any of the steps described in the exemplary embodiments above; and power supply circuitry configured to supply power to the

According to some exemplary embodiments, a UE for measurement reporting is connected to an antenna configured to send and receive radio signals, and to an antenna and processing circuitry, wherein the antenna and processing circuitry radio front-end circuitry configured to condition signals communicated between an input interface connected to the radio front-end circuitry and the processing circuitry and configured to allow information input to the UE to be processed by the processing circuitry; an output interface connected and configured to output information from the UE processed by the processing circuitry; and a battery connected to the processing circuitry and configured to power the UE. .

According to some exemplary embodiments, a communication system including a host computer includes processing circuitry configured to provide user data, and cellular data user equipment (UE) for transmission to user equipment (UE). a communication interface configured to forward to a network, the UE comprising a radio interface and processing circuitry, the UE components performing the steps of any one of the above exemplary embodiments; is set to implement either Optionally, the cellular network further includes a base station configured to communicate with the UE. Optionally, the processing circuitry of the host computer is configured to run a host application and thereby provide user data, and the processing circuitry of the UE is configured to run a client application associated with the host application. A communication system according to the previous two embodiments, wherein:

According to some exemplary embodiments, a method implemented in a communication system including a host computer, a base station, and a user equipment (UE) comprises providing user data at the host computer; In a computer, initiating a transmission carrying user data to a UE over a cellular network including a base station, wherein the UE performs any of the steps described in any one of the above exemplary embodiments. and initiating transmission. Optionally, the method of the previous embodiment further comprises receiving user data from the base station at the UE.

According to some exemplary embodiments, a communication system including a host computer includes a communication interface configured to receive user data generated from transmissions from a UE to a base station, the UE communicating with a radio interface and processing circuitry, wherein the processing circuitry of the UE is configured to perform any of the steps described in any one of the above exemplary embodiments. Optionally, the communication system according to the previous embodiment further comprises a UE. Optionally, the communication system according to the previous embodiment further comprises a base station, the base station configured to communicate with the UE over the air interface and user data carried by transmission from the UE to the base station. to the host computer. Optionally, the processing circuitry of the host computer is configured to run a host application and the processing circuitry of the UE is configured to run a client application associated with the host application thereby providing user data. A communication system as in any preceding embodiment, wherein: Optionally, the processing circuitry of the host computer is configured to execute the host application thereby providing the requested data and the processing circuitry of the UE executes a client application associated with the host application thereby It is configured to provide user data in response to request data.

According to some exemplary embodiments, a method implemented in a communication system includes a host computer, a base station, and a user equipment (UE), wherein the method is performed at the host computer from the UE to the base station. Receiving transmitted user data, wherein the UE performs any of the steps described in any one of the above exemplary embodiments. Optionally, the method further comprises, at the UE, providing user data to the base station. Optionally, the method further comprises executing a client application at the UE, thereby providing user data to be transmitted, and executing a host application associated with the client application at the host computer. . Optionally, the method includes executing a client application in the UE and receiving input data to the client application in the UE, the input data executing a host application associated with the client application. receiving input data provided at the host computer by the client application, wherein the user data to be sent is provided by the client application in response to the input data.

According to some exemplary embodiments, a method implemented in a communication system including a host computer, a base station, and a user equipment (UE) comprises: receiving user data generated from the received transmission, wherein the UE performs any of the steps described in any one of the above exemplary embodiments; . Optionally, the method further includes receiving user data from the UE at the base station. Optionally, the method further comprises initiating, at the base station, transmission of the received user data to the host computer.

Abbreviations At least some of the following abbreviations may be used in this disclosure. If there is a mismatch between abbreviations, preference should be given to how it is used above. When listed multiple times below, the first listing should be preferred over the subsequent listing(s).

1x RTT CDMA2000 1x Radio Transmission Technology 3GPP 3rd Generation Partnership Project 5G 5th Generation ABS Almost Blank Subframe ARQ Automatic Repeat Request AWGN Additive White Gaussian Noise BCCH Broadcast Control Channel BCH Broadcast Channel CA Carrier Aggregation CC Carrier Component CCCH SDU Common Control Channel SDUCDMA Code Division Multiplex Access CGI Cell Global Identifier CIR Channel Impulse Response CP Cyclic Prefix CPICH Common Pilot Channel CPICH Ec/No CPICH received energy per chip divided by power density in band CQI Channel Quality Information C-RNTI Cell RNTCSI Channel State Information DCCH Dedicated Control Channel DL Downlink DM Demodulation DMRS Demodulation Reference Signal DRX Discontinuous Reception DTX Discontinuous Transmission DTCH Dedicated Traffic Channel DUT Device Under Test E-CID Enhanced Cell ID (Positioning Method) E-SMLC Evolved Serving Mobile Location Center ECGI Evolved CGIeNB E-UTRAN Node BePDCCH Enhanced Physical Downlink Control Channel E-SMLC Evolved Serving Mobile Location Center E-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division Duplex FFS Needs Further Study GERAN GSM EDGE Base Station GNSS in Radio Access Network gNB NR Global Navigation Satellite System GSM Global System for Mobile Communications HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Speed Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term EvolutionMAC Medium Access Control MBMS Multimedia Broadcast Multicast Service MBSFN Multimedia Broadcast Multicast Service Single Frequency Network MBSFN ABS MBSFN Almost Blank Subframe MDT Drive Test Minimization MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplex OFDMA Orthogonal Frequency Division Multiple Access OSS Operation Support System OTDOA Observed Time Difference of Arrival O&amp;M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel PCell Primary Cell PCFICH Physical Control Format Indicator Channel PDCCH Physical Downlink Control Channel PDP Profile Delay Profile PDSCH Physical Downlink Shared Channel PGW Packet Gateway PHICH Physical Hybrid Automatic Repeat Request Indicator Channel PLMN Public Land Mobile Network PMI Precoder Matrix Indicator PRACH Physical Random Access Channel PRS Positioning Reference Signal PSS Primary Synchronization Signal PUCCH Physical Uplink Control Channel PUSCH Physical Uplink Shared Channel RACH Random Access Channel QAM Quadrature Amplitude Modulation RAN Radio Access Network RAT Radio Access Technology RLM Radio Link Management RNC Radio Network Controller RNTI Radio Network Temporary Identifier RRC Radio Resource Control RRM Radio Resource Management RS Reference Signal RSCP Received Signal Code Power RSRP Reference Symbol Received Power, or Reference Signal Received Power RSRQ Reference Signal Received Quality, or Reference Symbol Received Quality RSSI Received Signal Strength Indicator RSTD Reference Signal Time Difference SCH Synchronization Channel SCell Secondary Cell SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal-to-Noise Ratio SON Self-Optimizing Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunications System USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMAWLAN wide local area network