Patent ID: 12256256

DETAILED DESCRIPTION

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

It should be appreciated that most of the description below refers to LTE messages and procedures. However, the methods are also applicable to future releases of New Radio (NR) (e.g. Rel-17), if further enhancements of the early measurement reporting are implemented that create some incompatibility between the Rel-16 and Rel-17 measurement configurations/results.

In parts of the description below, the term “IDLE mode measurement” is used to refer to measurements performed either in RRC_IDLE or RRC_INACTIVE mode. This is due to historical reasons that the Rel-15 LTE RRC specifications (36.331) used that terminology.

In parts of the description and examples the terminologies “Rel-15 eNB” and “Rel-16 eNB” are used. “Rel-15 eNB” refers to an eNB that is configured to operate according to the 3GPP Release 15 standards. “Rel-16 eNB” refers to an eNB that is configured to operate according to the 3GPP Release 16 standards. It should also be noted that a “Rel-15 eNB” in the case of the present disclosure can also refer to a “Rel-16 eNB” that has implemented only the Rel-15 features of early measurements (e.g. the eNB supports only LTE measurement results).

As noted above this disclosure provides mechanisms to handle early measurement reporting in a scenario where there is a mismatch (e.g. in terms of release of the standard supported or a particular feature of a release that is implemented) between the wireless device (UE) and the network (eNB). Several methods/mechanisms/modifications are proposed and can be used individually or in any suitable combination.

NETWORK EMBODIMENTS

This section discusses various methods/mechanisms/modifications for use in the network, e.g. in or by an eNB, such as a Rel-15 eNB, or a Rel-16 eNB.

Embodiment 1: Extend SIB2 with Rel-16 indication—In an embodiment, a new indication is introduced in system information, i.e. in a system information block, SIB (e.g. SIB2) for indicating the support of the Rel-16 early measurement reporting (i.e. eNB can process early measurement reports that contain measurements of NR cells).

SystemInformationBlockType2 information element-- ASN1STARTSystemInformationBlockType2 ::=SEQUENCE {ac-BarringInfoSEQUENCE {ac-BarringForEmergencyBOOLEAN,ac-BarringForMO-SignallingAC-BarringConfigOPTIONAL,-- Need OPac-BarringForMO-DataAC-BarringConfigOPTIONAL-- Need OP}OPTIONAL,-- Need OPradioResourceConfigCommonRadioResourceConfigCommonSIB,ue-TimersAndConstantsUE-TimersAndConstants,freqInfoSEQUENCE {ul-CarrierFreqARFCN-ValueEUTRAOPTIONAL,-- Need OPul-BandwidthENUMERATED {n6, n15, n25, n50, n75, n100}OPTIONAL,-- Need OPadditionalSpectrumEmissionAdditionalSpectrumEmission},mbsfn-SubframeConfigListMBSFN-SubframeConfigListOPTIONAL,-- NeedORtimeAlignmentTimerCommonTimeAlignmentTimer,...,lateNonCriticalExtensionOCTET STRING (CONTAININGSystemInformationBlockType2-v8h0-IEs)OPTIONAL,<<omitted parts>>,[[cp-EDT-r15ENUMERATED {true} OPTIONAL,-- Need ORup-EDT-r15ENUMERATED true}  OPTIONAL,-- Need ORidleModeMeasurements-r15ENUMERATED {true} OPTIONAL,-- Need ORreducedCP-LatencyEnabled-r15ENUMERATED {true} OPTIONAL-- Need OR]],[[idleModeMeasurements-r16ENUMERATED {true} OPTIONAL,-- Need OR]]}

SystemInformationBlockType2 field descriptionsidleModeMeasurementsThis field indicates that the eNB can process indication of IDLE modemeasurements from UE.If SIB2 includes idleModeMeasurement-r15, it is an indication that theeNB can process IDLE mode measurements that contain LTE results fromthe UE. If SIB2 includes idleModeMeasurement-r16, it is an indicationthat the eNB can process IDLE mode measurements that contain both LTEand NR results from the UE.

Embodiment 2: Extend UEInformationRequest with Rel-16 Indication

Embodiment 2a: Indication is used to request both LTE and NR measurements—In another or further embodiment, a separate indicator can be introduced or included in a Rel-16 UEInformationRequest (e.g. support idleModeMeasurementReq-r16) to indicate that the network wants the UE to send early measurement reports that contain both LTE and NR results. This could be implemented as, e.g.:

UEInformationRequest message-- ASN1STARTUEInformationRequest-r9 ::=SEQUENCE {rrc-TransactionIdentifierRRC-TransactionIdentifier,criticalExtensionsCHOICE {c1CHOICE {ueInformationRequest-r9UEInformationRequest-r9-IEs,spare3 NULL, spare2 NULL, spare1 NULL},criticalExtensionsFutureSEQUENCE { }}}UEInformationRequest-r9-IEs ::=SEQUENCE {rach-ReportReq-r9BOOLEAN,rlf-ReportReq-r9BOOLEAN,nonCriticalExtensionUEInformationRequest-v930-IEsOPTIONAL}UEInformationRequest-v930-IEs ::= SEQUENCE {lateNonCriticalExtensionOCTET STRINGOPTIONAL,nonCriticalExtensionUEInformationRequest-v1020-IEsOPTIONAL}UEInformationRequest-v1020-IEs ::=SEQUENCE {logMeasReportReq-r10ENUMERATED {true}OPTIONAL,-- Need ONnonCriticalExtensionUEInformationRequest-v1130-IEsOPTIONAL}UEInformationRequest-v1130-IEs ::= SEQUENCE {connEstFailReportReq-r11ENUMERATED {true}OPTIONAL,-- Need ONnonCriticalExtensionUEInformationRequest-v1250-IEsOPTIONAL}UEInformationRequest-v1250-IEs :: = SEQUENCE {mobilityHistoryReportReq-r12ENUMERATED {true}OPTIONAL,-- Need ONnonCriticalExtensionUEInformationRequest-v1530-IEsOPTIONAL}UEInformationRequest-v1530-IEs ::= SEQUENCE {idleModeMeasurementReq-r15ENUMERATED {true}OPTIONAL,-- Need ONflightPathInfoReq-r15FlightPathInfoReportConfig-r15OPTIONAL,-- Need ONnonCriticalExtensionUEInformationRequest-v16xx-IEsOPTIONAL}UEInformationRequest-v16xx-IEs ::= SEQUENCE {idleModeMeasurementReq-r16ENUMERATED {true}OPTIONAL,-- Need ONnonCriticalExtensionSEQUENCE { }OPTIONAL}-- ASN1STOP

UEInformationRequest field descriptionsrach-ReportReqThis field is used to indicate whether the UE shall report information aboutthe random access procedure.idleModeMeasurementReqThis field is used to indicate that the UE shall report available idle modemeasurements in UEInformationResponseIf idleModeMeasurementReq-r15 is included, it is an indication that theUE shall report IDLE mode measurements that contain only LTE results.If idleModeMeasurementReq-r16 is included, it is an indication that theUE can report IDLE mode measurements that contain both LTE and NRresults.

Embodiment 2b: Indication is used to request only NR measurements—In another embodiment, a separate indicator can be introduced or included in a rel-16 UEInformationRequest (e.g. support idleModeMeasurementReq-r16) to indicate that the network wants the UE to send early measurement reports that contain only NR results. If LTE results should be included, the legacy indication can be used (i.e. the network includes both indicators if it wants both LTE and NR results). This could be implemented as e.g. (the ASN.1 structure of the UEInformationRequest message can be the same as embodiment 2a above, but in this case both idleModeMeasurementReq-r15 and idleModeMeasurementReq-r16 can be included in the same UEInformationRequest message):

UEInformationRequest field descriptionsrach-ReportRegThis field is used to indicate whether the UE shall report information aboutthe random access procedure.idleModeMeasurementReqThis field is used to indicate that the UE shall report available idle modemeasurements in UEInformationResponseIf idleModeMeasurementReq-r15 is included, it is an indication that theUE shall report IDLE mode measurements that contain LTE results.If idleModeMeasurementReq-r16 is included, it is an indication that theUE can report IDLE mode measurements that contain NR results.

UE Embodiments

This section discusses various methods/mechanisms/modifications for use in or by a User Equipment, UE. The UE can be referred to as a “Rel-16 UE”, i.e. a UE that is configured to operate according to the 3GPP Release 16 standards, and specifically that is able to provide early measurement reporting of LTE and NR cells.

Embodiment 3: Extend Msg.3 with Rel-16 Indication

Embodiment 3a: Rel-16 Msg.3 indication indicates availability of both LTE and NR measurement results—In another or further embodiment, a separate indicator in a Rel-16 RRCConnectionSetupComplete or RRCConnectionResumeComplete (e.g. idleMeasAvailable-r16) can be introduced to indicate to the network that the UE has early measurements that contain both LTE and NR measurement results.

The following provides exemplary embodiments or implementations for when a separate indicator is included in a Rel-16 RRCConnectionSetupComplete:

RRCConnectionSetupComplete message-- ASN1STARTRRCConnectionSetupComplete ::=SEQUENCE {rrc-TransactionIdentifierRRC-TransactionIdentifier,criticalExtensionsCHOICE {c1CHOICE{rrcConnectionSetupComplete-r8RRCConnectionSetupComplete-r8-IEs,spare3 NULL, spare2 NULL, spare1 NULL},criticalExtensionsFutureSEQUENCE { }}}<<omitted parts>>RRCConnectionSetupComplete-v1530-IEs ::= SEQUENCE {logMeasAvailableBT-r15ENUMERATED {true}OPTIONAL,logMeasAvailableWLAN-r15ENUMERATED {true}OPTIONAL,idleMeasAvailable-r15ENUMERATED {true}OPTIONAL,flightPathInfoAvailable-r15ENUMERATED {true}OPTIONAL,connectTo5GC-r15ENUMERATED {true}OPTIONAL,registeredAMF-r15RegisteredAMF-r15OPTIONAL,s-NSSAI-list-r15SEQUENCE(SIZE (1..maxNrofS-NSSAI-r15)) OF S-NSSAI-r15 OPTIONAL,ng-5G-S-TMSI-Bits-r15CHOICE {ng-5G-S-TMSI-r15NG-5G-S-TMSI-r15,ng-5G-S-TMSI-Part2-r15BIT STRING (SIZE (8))}OPTIONAL,nonCriticalExtensionRRCConnectionSetupComplete-v1540-IEsOPTIONAL}RRCConnectionSetupComplete-v1540-IEs ::= SEQUENCE {gummei-Type-v1540ENUMERATED {mappedFrom5G}OPTIONAL,guami-Type-r15ENUMERATED {native, mapped}OPTIONAL,nonCriticalExtensionRRCConnectionSetupComplete-v16xx-IEsOPTIONAL}RRCConnectionSetupComplete-v16xx-IEs ::= SEQUENCE {idleMeasAvailable-r16ENUMERATED {true}OPTIONAL,nonCriticalExtensionRRCConnectionSetupComplete-v1540-IEsOPTIONAL}-- ASN1STOP

RRCConnection SetupComplete field descriptionsidleMeasAvailableIndication that the UE has idle mode measurement report available.If idleMeasAvailable-r15 is included, it is an indication that the UE hasIDLE mode measurements that contain only LTE results.If idleMeasAvailable-r16 is included, it is an indication that the UE hasIDLE mode measurements that contain both LTE and NR results.

If a single indication is used in SIB2, the procedures could be updated to e.g.:

1> set the content of RRCConnectionSetupComplete message as follows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements4>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;4> else if the UE has IDLE mode measurement informationavailable in VarMeasIdleReport-r16:5> include the idleMeasAvailable-r16;

If a new indication is introduced in SIB2 (as in network embodiment 1), the procedures could be updated to e.g.:

1> set the content of RRCConnectionSetupComplete message as follows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements-r15:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport(i.e. VarMeasIdleReport-r15 or VarMeasIdleReport-r16) :5> include the idleMeasAvailable-r15;3> else if the SIB2 contains idleModeMeasurements-r164>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r155> include the idleMeasAvailable-r15;4>else if the UE has IDLE mode measurement informationavailable in VarMeasIdleReport-r165> include the idleMeasAvailable-r16;
The following provides exemplary embodiments or implementations for when a separate indicator is included in a Rel-16 RRCConnectionResumeComplete:

RRCConnectionResumeComplete message-- ASN1 STARTRRCConnectionResumeComplete-r13 ::= SEQUENCE {rrc-TransactionIdentifierRRC-TransactionIdentifier,criticalExtensionsCHOICE {rrcConnectionResumeComplete-r13RRCConnectionResumeComplete-r13-IEs,criticalExtensionsFutureSEQUENCE { }}}<<Omitted parts>>}RRCConnectionResumeComplete-v1530-IEs ::= SEQUENCE {logMeasAvailableBT-r15ENUMERATED {true}OPTIONAL,logMeasAvailableWLAN-r15ENUMERATED {true}OPTIONAL,idleMeasAvailable-r15ENUMERATED {true}OPTIONAL,flightPathInfoAvailable-r15ENUMERATED {true}OPTIONAL,nonCriticalExtensionRRCConnectionResumeComplete-v16xx-IEsOPTIONAL}RRCConnectionResumeComplete-v16xx-IEs ::= SEQUENCE {idleMeasAvailable-r16ENUMERATED {true}OPTIONAL,nonCriticalExtensionSEQUENCE { }OPTIONAL}-- ASN1STOP

RRCConnectionResumeComplete field descriptionsidleMeasAvailableIndication that the UE has idle mode measurement report available.If idleMeasAvailable-r15 is included, it is an indication that the UE hasIDLE mode measurements that contain only LTE results.If idleMeasAvailable-r16 is included, it is an indication that the UE hasIDLE mode measurements that contain both LTE and NR results.

If a single indication is used in SIB, the procedures could be implemented as e.g.:

1> set the content of RRCConnectionResumeComplete message asfollows:<<skipped part>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements4>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;4> else if the UE has IDLE mode measurement informationavailable in VarMeasIdleReport-r16:5> include the idleMeasAvailable-r16;

If a separate indication is used in SIB for the Rel-16 results, the procedures could be implemented as e.g.:

1> set the content of RRCConnectionResumeComplete message asfollows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements-r154> if the UE has IDLE mode measurement information available inVarMeasIdleReport(i.e. VarMeasIdleReport-r15 or VarMeasIdleReport-r16):5> include the idleMeasAvailable-r15;3> else if the SIB2 contains idleModeMeasurements-r164>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r155> include the idleMeasAvailable-r15;4>else if the UE has IDLE mode measurement informationavailable in VarMeasIdleReport-r165> include the idleMeasAvailable-r16;

Embodiment 3b: Rel-16 Msg.3 indication indicates availability of only NR measurement results—In another or further embodiment, a separate indicator in a Rel-16 RRCConnectionSetupComplete or RRCConnectionResumeComplete (e.g. idleMeasAvailable-r16) can be introduced or included to indicate to the network that the UE has early measurements that contain NR results. If LTE results are available, the UE can use the existing legacy indication (i.e. both indicators included).

The following provides exemplary embodiments or implementations for when a separate indicator is included in a Rel-16 RRCConnectionSetupComplete:

The ASN.1 for these embodiments can be the same as embodiment 3a above, but in these embodiments both idleMeasurementAvailable-r15 and idleMeasurementAvailable-r16 can be included in the same RRCConnectionSetupComplete message:

RRCConnectionSetupComplete field descriptionsidleMeasAvailableIndication that the UE has idle mode measurement report available.If idleMeasAvailable-r15 is included, it is an indication that the UE hasIDLE mode measurements that contain LTE results.If idleMeasAvailable-r16 is included, it is an indication that the UE hasIDLE mode measurements that contain NR results.

If a single indication is used in SIB2, the procedures could be updated to e.g.:

1> set the content of RRCConnectionSetupComplete message as follows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements4>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r16:5> include the idleMeasAvailable-r16;

The above means that if UE has both LTE and NR measurements, it will include both indications.

If a new indication is introduced in SIB2 (as in network embodiment 1), the procedures could be updated to e.g.:

1> set the content of RRCConnectionSetupComplete message as follows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>3> if the SIB2 contains idleModeMeasurements-r15:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;3> if the SIB2 contains idleModeMeasurements-r164> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r165> include the idleMeasAvailable-r16;

In the above example, it has been assumed that the SIB can include both idleModeMeasurements-r15 and idleModeMeasurements-r16 to indicate that it wants the UE to report the LTE and NR results, respectively. Another possibility is for the SIB to indicate idleModeMeasurements-r15 when it wants the UE to report only LTE results, and indicate idleModeMeasurements-r16 when it wants the UE to report both LTE and NR results. In such a case, the procedure can be as follows:

1> set the content of RRCConnectionSetupComplete message as follows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements-r15:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;3> else if the SIB2 contains idleModeMeasurements-r164> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r155> include the idleMeasAvailable-r15;4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r165> include the idleMeasAvailable-r16;

The following provides exemplary embodiments or implementations for when a separate indicator is included in a Rel-16 RRCConnectionResumeComplete.

The ASN.1 for this case can be the same as embodiment 3a above, but in this case both idleMeasurementAvailable-r15 and idleMeasurementAvailable-r16 can be included in the same RRCConnectionResumeComplete message:

RRCConnectionResumeComplete field descriptionsidleMeasAvailableIndication that the UE has idle mode measurement report available.If idleMeasAvailable-r15 is included, it is an indication that the UE hasIDLE mode measurements that contain LTE results.If idleMeasAvailable-r16 is included, it is an indication that the UE hasIDLE mode measurements that contain NR results.

If a single indication is used in SIB, the procedures could be implemented as e.g.:

1> set the content of RRCConnectionResumeComplete message asfollows:<<skipped part>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements4>if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r16:5> include the idleMeasAvailable-r16;

If a new indication is used in SIB2 (as in network embodiment 1), the procedures could be implemented as e.g.:

1> set the content of RRCConnectionResumeComplete message asfollows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements-r15:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport:5> include the idleMeasAvailable-r15;3> if the SIB2 contains idleModeMeasurements-r16:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r16:5> include the idleMeasAvailable-r16;

In the above example, it has been assumed that the SIB can include both idleModeMeasurements-r15 and idleModeMeasurements-r16 to indicate that it wants the UE to report the LTE and NR results, respectively. Another possibility is for the SIB to indicate idleModeMeasurements-r15 when it wants the UE to report only LTE results, and idleModeMeasurements-r16 when it wants the UE to report both LTE and NR results. In such a case, the procedure can be as follows:

1> set the content of RRCConnectionResumeComplete message asfollows:<<skipped parts>>2> except for NB-IoT:<<skipped parts>>3> if the SIB2 contains idleModeMeasurements-r15:4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r15:5> include the idleMeasAvailable-r15;3> else if the SIB2 contains idleModeMeasurements-r164> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r155> include the idleMeasAvailable-r15;4> if the UE has IDLE mode measurement information available inVarMeasIdleReport-r165> include the idleMeasAvailable-r16;

Embodiment 4: Introduce New UE Variable that Will Contain the Idle Mode Measurement Results for Both LTE and NR

In another or further embodiment, the UE can have one Rel-16 variable (e.g. VarMeasIdleReport-r16) that can use to store both the LTE and NR measurement results. If the UE has been configured with a Rel-16 early measurement configuration and has Rel-16 early measurement results that contain both LTE and NR results, while the eNB that the UE is resuming or establishing the connection to supports only Rel-15 early measurements (as indicated either the SIB or in the received UEInformationRequest), the UE can either:Include only the LTE results in the early measurement report; orNot send any early measurement report.

Since the current procedures instruct the UE to include the entire VarMeasIdleReport in the UEInformationResponse, the procedures need to be updated to distinguish between the NR and LTE results.

Embodiment 4a: Rel-16 indication in UEInformationRequest requests both LTE and NR measurements—This could be implemented as follows (assuming the network implements two separate indicators for Rel-15 and Rel-16 measurements in the UEInformationRequest as discussed in network embodiment 2a):

5.6.5.3 Reception of the UEInformationRequest messageUpon receiving the UEInformationRequest message, the UE shall, only after successful security activation:<<skipped parts>>1> if the idleModeMeasurementReq-r15 is included in the UEInformationRequest:2> if the UE has stored VarMeasIdleReport-r15:3> set the measResultListIdle in the UEInformationResponse message to the value ofmeasReportIdle in the VarMeasIdleReport-r15;2> else if the UE has stored VarMeasIdleReport-r16:3> set the measResultListIdle in the UEInformationResponse message to the value ofmeasReportIdleEUTRA in the VarMeasIdleReport-r16; <<Here only themeasReportIdle EUTRA is put into the result>>1> else if the idleModeMeasurementReq-r16 is included in the UEInformationRequest:2> if the UE has stored VarMeasIdleReport-r15:3> set the measResultListIdleEUTRA in the UEInformationResponse message to the valueof measReportIdleEUTRA in the VarMeasIdleReport-r15; <<Here only the EUTRApart of UEInformationResponse is populated>>2> else if the UE has stored VarMeasIdleReport-r16:3> set the measResultListIdleEUTRA in the UEInformationResponse message to the valueof measReportIdleEUTRA in the VarMeasIdleReport-r16;3> set the measResultListIdleNR in the UEInformationResponse message to the value ofmeasReportIdleNR in the VarMeasIdleReport-r16; <<Here both the EUTRA and NRpart of UEInformationResponse are populated>>

Embodiment 4b: Rel-16 indication in UEInformationRequest requests only NR measurements—In another or further embodiment, the network can indicate in UEInformationRequest using two indicators, idleModeMeasurementReq-r15 for the LTE measurements, and idleModeMeasurementReq-r16 for the NR measurements (i.e. based on network embodiment 2b). This could be implemented e.g. as:

5.6.5.3 Reception of the UEInformationRequest messageUpon receiving the UEInformationRequest message, the UE shall, only after successful security activation:<<skipped parts>>1> if the idleModeMeasurementReq-r15 is included in the UEInformationRequest:2> if the UE has stored VarMeasIdleReport-r15:3> set the measResultListIdleEUTRA in the UEInformationResponse message to the valueof measReportIdle in the VarMeasIdleReport-r15;2> else if the UE has stored VarMeasIdleReport-r16:3> set the measResultListIdleEUTRA in the UEInformationResponse message to the valueof measReportIdleEUTRA in the VarMeasIdleReport-r16;1> if the idleModeMeasurementReq-r16 is included in the UEInformationRequest:2> if the UE has stored VarMeasIdleReport-r16:3> set the measResultListIdleNR in the UEInformationResponse message to the value ofmeasReportIdleNR in the VarMeasIdleReport-r16;

Embodiment 5: Introduce New UE Variable which Contains Only NR Measurement Results, while Reusing Existing UE Variable for LTE Measurement Results

In another or further embodiment, the Rel-16 early measurement results may only contain NR results. In that case the UE would use the Rel-15 UE variable (VarMeasIdleReport-r15) to store the LTE measurement results and a separate Rel-16 UE variable (e.g. VarMeasIdleReport-r16) to store the NR measurement results.

If the UE has been configured with Rel-16 early measurement configuration and has Rel-16 early measurement results that contain both LTE and NR results while the eNB that the UE is resuming or establishing the connection to supports only Rel-15 early measurements (as indicated either the SIB or in the received UEInformationRequest), the UE may only include the VarMeasIdleReport-r15 in the early measurement report. If the target eNB supports Rel-16 early measurements, the UE can include both VarMeasIdleReport-r15 and VarMeasIdleReport-r16 in the early measurement report.

Embodiment 5a: Rel-16 indication requests both LTE and NR measurements—This could be implemented as follows (assuming the network implements two separate indicators for Rel-15 and Rel-16 measurements in the UEInformationRequest as discussed in network embodiment 2a):

5.6.5.3 Reception of the UEInformationRequest messageUpon receiving the UEInformationRequest message, the UE shall, only after successful security activation:<<skipped parts>>1> if the UE has stored VarMeasIdleReport-r15:2> if idleModeMeasurementReq-r15 or idleModeMeasurementReq-r16 is included in theUEInformationRequest:3>set the measResultListIdle-r15 in the UEInformationResponse message to the value ofmeasReportIdle-r15 in the VarMeasIdleReport-r15;3>discard the VarMeasIdleReport-r15 upon successful delivery of theUEInformationResponse message confirmed by lower layers;1> else if the UE has stored VarMeasIdleReport-r16:2>set the measResultListIdle-r15 in the UEInformationResponse message to the value ofmeasReportIdle-r15 in the VarMeasIdleReport-r15; <<This applies for both the Rel-15and Rel-16 eNB>>2> if idleModeMeasurementReq-r16 is included in the UEInformationRequest:3> set the measResultListIdle-r16 in the UEInformationResponse message to the value ofmeasReportIdle-r16 in the VarMeasIdleReport-r16;2>discard the VarMeasIdleReport-r15 and VarMeasIdleReport-r16 upon successful delivery ofthe UEInformationResponse message confirmed by lower layers;

Embodiment 5b: Rel-16 indication requests only NR measurements—This could be implemented as follows (assuming the network implements two separate indicators for Rel-15 and Rel-16 measurements in the UEInformationRequest as discussed in network embodiment 2b):

5.6.5.3 Reception of the UEInformationRequest messageUpon receiving the UEInformationRequest message, the UE shall, only after successful security activation:<<skipped parts>>1> if the UE has stored VarMeasIdleReport-r15:2> if idleModeMeasurementReq-r15 is included in the UEInformationRequest:3>set the measResultListIdle-r15 in the UEInformationResponse message to the value ofmeasReportIdle-r15 in the VarMeasIdleReport-r15;1> if the UE has stored VarMeasIdleReport-r16:2> if idleModeMeasurementReq-r16 is included in the UEInformationRequest:3> set the measResultListIdle-r16 in the UEInformationResponse message to the value ofmeasReportIdle-r16 in the VarMeasIdleReport-r16;1>discard the stored VarMeasIdleReport-r15 and VarMeasIdleReport-r16, if any, upon successfuldelivery of the UEInformationResponse message confirmed by lower layers;

Thus, the various embodiments set out above may enable inter-operability between a Rel-15/Rel-16 UE and a Rel-15/Rel-16 eNB with regard to early measurement reporting. Without the methods proposed, a Rel-16 UE may end up sending early measurement reports that contain NR results and as such may not be understood/compiled by a Rel-15 eNB. This could effectively render the early measurement enhancement feature useless for some of the UEs in deployments that contain a mix of Rel-15 and Rel-16 eNBs, resulting in a degraded end user performance, as faster CA/DC setup will not be possible.

Although the subject matter described herein may be implemented in any appropriate type of system using any suitable components, the embodiments disclosed herein are described in relation to a wireless network, such as the example wireless network illustrated inFIG.6. For simplicity, the wireless network ofFIG.6only depicts network606, network nodes660and660b, and WDs610,610b, and610c. In practice, a wireless network may further include any additional elements suitable to support communication between wireless devices or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, network node660and wireless device (WD)610are depicted with additional detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices' access to and/or use of the services provided by, or via, the wireless network.

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

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

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

As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a wireless device and/or with other network nodes or equipment in the wireless network to enable and/or provide wireless access to the wireless device and/or to perform other functions (e.g., administration) in the wireless network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and may then also be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS). Yet further examples of network nodes include multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

InFIG.6, network node660includes processing circuitry670, device readable medium680, interface690, auxiliary equipment684, power source686, power circuitry687, and antenna662. Although network node660illustrated in the example wireless network ofFIG.6may represent a device that includes the illustrated combination of hardware components, other embodiments may comprise network nodes with different combinations of components. It is to be understood that a network node comprises any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein. Moreover, while the components of network node660are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium680may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node660may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which network node660comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeB's. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, network node660may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium680for the different RATs) and some components may be reused (e.g., the same antenna662may be shared by the RATs). Network node660may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node660, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node660.

Processing circuitry670is configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being provided by a network node. These operations performed by processing circuitry670may include processing information obtained by processing circuitry670by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Processing circuitry670may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and/or encoded logic operable to provide, either alone or in conjunction with other network node660components, such as device readable medium680, network node660functionality. For example, processing circuitry670may execute instructions stored in device readable medium680or in memory within processing circuitry670. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, processing circuitry670may include a system on a chip (SOC).

In some embodiments, processing circuitry670may include one or more of radio frequency (RF) transceiver circuitry672and baseband processing circuitry674. In some embodiments, radio frequency (RF) transceiver circuitry672and baseband processing circuitry674may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry672and baseband processing circuitry674may be on the same chip or set of chips, boards, or units

In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB or other such network device may be performed by processing circuitry670executing instructions stored on device readable medium680or memory within processing circuitry670. In alternative embodiments, some or all of the functionality may be provided by processing circuitry670without executing instructions stored on a separate or discrete device readable medium, such as in a hard-wired manner. In any of those embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry670can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry670alone or to other components of network node660, but are enjoyed by network node660as a whole, and/or by end users and the wireless network generally.

Device readable medium680may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by processing circuitry670. Device readable medium680may store any suitable instructions, data or information, including a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry670and, utilized by network node660. Device readable medium680may be used to store any calculations made by processing circuitry670and/or any data received via interface690. In some embodiments, processing circuitry670and device readable medium680may be considered to be integrated.

Interface690is used in the wired or wireless communication of signalling and/or data between network node660, network606, and/or WDs610. As illustrated, interface690comprises port(s)/terminal(s)694to send and receive data, for example to and from network606over a wired connection. Interface690also includes radio front end circuitry692that may be coupled to, or in certain embodiments a part of, antenna662. Radio front end circuitry692comprises filters698and amplifiers696. Radio front end circuitry692may be connected to antenna662and processing circuitry670. Radio front end circuitry may be configured to condition signals communicated between antenna662and processing circuitry670. Radio front end circuitry692may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry692may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters698and/or amplifiers696. The radio signal may then be transmitted via antenna662. Similarly, when receiving data, antenna662may collect radio signals which are then converted into digital data by radio front end circuitry692. The digital data may be passed to processing circuitry670. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node660may not include separate radio front end circuitry692, instead, processing circuitry670may comprise radio front end circuitry and may be connected to antenna662without separate radio front end circuitry692. Similarly, in some embodiments, all or some of RF transceiver circuitry672may be considered a part of interface690. In still other embodiments, interface690may include one or more ports or terminals694, radio front end circuitry692, and RF transceiver circuitry672, as part of a radio unit (not shown), and interface690may communicate with baseband processing circuitry674, which is part of a digital unit (not shown).

Antenna662may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna662may be coupled to radio front end circuitry690and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna662may comprise one or more omni-directional, sector or panel antennas operable to transmit/receive radio signals between, for example, 2 GHz and 66 GHz. An omni-directional antenna may be used to transmit/receive radio signals in any direction, a sector antenna may be used to transmit/receive radio signals from devices within a particular area, and a panel antenna may be a line of sight antenna used to transmit/receive radio signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna662may be separate from network node660and may be connectable to network node660through an interface or port.

Antenna662, interface690, and/or processing circuitry670may be configured to perform any receiving operations and/or certain obtaining 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, antenna662, interface690, and/or processing circuitry670may be configured to perform any transmitting operations 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 circuitry687may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node660with power for performing the functionality described herein. Power circuitry687may receive power from power source686. Power source686and/or power circuitry687may be configured to provide power to the various components of network node660in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source686may either be included in, or external to, power circuitry687and/or network node660. For example, network node660may be connectable to an external power source (e.g., an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry687. As a further example, power source686may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry687. The battery may provide backup power should the external power source fail. Other types of power sources, such as photovoltaic devices, may also be used.

Alternative embodiments of network node660may include additional components beyond those shown inFIG.6that may be responsible for providing certain aspects of the network node's functionality, including any of the functionality described herein and/or any functionality necessary to support the subject matter described herein. For example, network node660may include user interface equipment to allow input of information into network node660and to allow output of information from network node660. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node660.

As used herein, wireless device (WD) refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other wireless devices. Unless otherwise noted, the term WD may be used interchangeably herein with user equipment (UE). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE). a vehicle-mounted wireless terminal device, etc. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and/or measurements, and transmits the results of such monitoring and/or measurements to another WD and/or a network node. The WD may in this case be a machine-to-machine (M2M) device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the WD may be a UE implementing the 3GPP narrow band internet of things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or home or personal appliances (e.g. refrigerators, televisions, etc.) personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, a WD may represent a vehicle or other equipment that is capable of monitoring and/or reporting on its operational status or other functions associated with its operation. A WD as described above may represent the endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, a WD as described above may be mobile, in which case it may also be referred to as a mobile device or a mobile terminal.

As illustrated, wireless device610includes antenna611, interface614, processing circuitry620, device readable medium630, user interface equipment632, auxiliary equipment634, power source636and power circuitry637. WD610may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD610, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to mention a few. These wireless technologies may be integrated into the same or different chips or set of chips as other components within WD610.

Antenna611may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface614. In certain alternative embodiments, antenna611may be separate from WD610and be connectable to WD610through an interface or port. Antenna611, interface614, and/or processing circuitry620may be configured to perform any receiving or transmitting operations described herein as being performed by a 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 antenna611may be considered an interface.

As illustrated, interface614comprises radio front end circuitry612and antenna611. Radio front end circuitry612comprise one or more filters618and amplifiers616. Radio front end circuitry614is connected to antenna611and processing circuitry620, and is configured to condition signals communicated between antenna611and processing circuitry620. Radio front end circuitry612may be coupled to or a part of antenna611. In some embodiments, WD610may not include separate radio front end circuitry612; rather, processing circuitry620may comprise radio front end circuitry and may be connected to antenna611. Similarly, in some embodiments, some or all of RF transceiver circuitry622may be considered a part of interface614. Radio front end circuitry612may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry612may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters618and/or amplifiers616. The radio signal may then be transmitted via antenna611. Similarly, when receiving data, antenna611may collect radio signals which are then converted into digital data by radio front end circuitry612. The digital data may be passed to processing circuitry620. In other embodiments, the interface may comprise different components and/or different combinations of components.

Processing circuitry620may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and/or encoded logic operable to provide, either alone or in conjunction with other WD610components, such as device readable medium630, WD610functionality. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry620may execute instructions stored in device readable medium630or in memory within processing circuitry620to provide the functionality disclosed herein.

As illustrated, processing circuitry620includes one or more of RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry620of WD610may comprise a SOC. In some embodiments, RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry624and application processing circuitry626may be combined into one chip or set of chips, and RF transceiver circuitry622may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry622and baseband processing circuitry624may be on the same chip or set of chips, and application processing circuitry626may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry622, baseband processing circuitry624, and application processing circuitry626may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry622may be a part of interface614. RF transceiver circuitry622may condition RF signals for processing circuitry620.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry620executing instructions stored on device readable medium630, which in certain embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by processing circuitry620without executing instructions stored on a separate or discrete device readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a device readable storage medium or not, processing circuitry620can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry620alone or to other components of WD610, but are enjoyed by WD610as a whole, and/or by end users and the wireless network generally.

Processing circuitry620may be configured to perform any determining, calculating, or similar operations (e.g., certain obtaining operations) described herein as being performed by a WD. These operations, as performed by processing circuitry620, may include processing information obtained by processing circuitry620by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD610, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

Device readable medium630may be operable to store a computer program, software, an application including one or more of logic, rules, code, tables, etc. and/or other instructions capable of being executed by processing circuitry620. Device readable medium630may include computer memory (e.g., Random Access Memory (RAM) or Read Only Memory (ROM)), mass storage media (e.g., a hard disk), removable storage media (e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device readable and/or computer executable memory devices that store information, data, and/or instructions that may be used by processing circuitry620. In some embodiments, processing circuitry620and device readable medium630may be considered to be integrated.

User interface equipment632may provide components that allow for a human user to interact with WD610. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment632may be operable to produce output to the user and to allow the user to provide input to WD610. The type of interaction may vary depending on the type of user interface equipment632installed in WD610. For example, if WD610is a smart phone, the interaction may be via a touch screen; if WD610is a smart meter, the interaction may be through a screen that provides usage (e.g., the number of gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). User interface equipment632may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment632is configured to allow input of information into WD610, and is connected to processing circuitry620to allow processing circuitry620to process the input information. User interface equipment632may include, for example, a microphone, a proximity or other sensor, keys/buttons, a touch display, one or more cameras, a USB port, or other input circuitry. User interface equipment632is also configured to allow output of information from WD610, and to allow processing circuitry620to output information from WD610. User interface equipment632may include, for example, a speaker, a display, vibrating circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits, of user interface equipment632, WD610may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein.

Auxiliary equipment634is operable to provide more specific functionality which may not be generally performed by WDs. This may comprise specialized sensors for doing measurements for various purposes, interfaces for additional types of communication such as wired communications etc. The inclusion and type of components of auxiliary equipment634may vary depending on the embodiment and/or scenario.

Power source636may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD610may further comprise power circuitry637for delivering power from power source636to the various parts of WD610which need power from power source636to carry out any functionality described or indicated herein. Power circuitry637may in certain embodiments comprise power management circuitry. Power circuitry637may additionally or alternatively be operable to receive power from an external power source; in which case WD610may be connectable to the external power source (such as an electricity outlet) via input circuitry or an interface such as an electrical power cable. Power circuitry637may also in certain embodiments be operable to deliver power from an external power source to power source636. This may be, for example, for the charging of power source636. Power circuitry637may perform any formatting, converting, or other modification to the power from power source636to make the power suitable for the respective components of WD610to which power is supplied.

FIG.7illustrates one embodiment of a UE in accordance with various aspects described herein. As used herein, a user equipment or UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). UE700may be any UE identified by the 3rdGeneration Partnership Project (3GPP), including a NB-IoT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE700, as illustrated inFIG.7, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rdGeneration Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and/or 5G standards. As mentioned previously, the term WD and UE may be used interchangeable. Accordingly, althoughFIG.7is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

InFIG.7, UE700includes processing circuitry701that is operatively coupled to input/output interface705, radio frequency (RF) interface709, network connection interface711, memory715including random access memory (RAM)717, read-only memory (ROM)719, and storage medium721or the like, communication subsystem731, power source733, and/or any other component, or any combination thereof. Storage medium721includes operating system723, application program725, and data727. In other embodiments, storage medium721may include other similar types of information. Certain UEs may utilize all of the components shown inFIG.7, or only a subset of the components. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

InFIG.7, processing circuitry701may be configured to process computer instructions and data. Processing circuitry701may be configured to implement any sequential state machine operative to execute machine instructions stored as machine-readable computer programs in the memory, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logic together with appropriate firmware; one or more stored program, general-purpose processors, such as a microprocessor or Digital Signal Processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry701may include two central processing units (CPUs). Data may be information in a form suitable for use by a computer.

In the depicted embodiment, input/output interface705may be configured to provide a communication interface to an input device, output device, or input and output device. UE700may be configured to use an output device via input/output interface705. 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 UE700. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. UE700may be configured to use an input device via input/output interface705to allow a user to capture information into UE700. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and an optical sensor.

InFIG.7, RF interface709may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface711may be configured to provide a communication interface to network743a. Network743amay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network743amay comprise a Wi-Fi network. Network connection interface711may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP/IP, SONET, ATM, or the like. Network connection interface711may implement receiver and transmitter functionality appropriate to the communication network links (e.g., optical, electrical, and the like). The transmitter and receiver functions may share circuit components, software or firmware, or alternatively may be implemented separately.

RAM717may be configured to interface via bus702to processing circuitry701to provide storage or caching of data or computer instructions during the execution of software programs such as the operating system, application programs, and device drivers. ROM719may be configured to provide computer instructions or data to processing circuitry701. For example, ROM719may be configured to store invariant low-level system code or data for basic system functions such as basic input and output (I/O), startup, or reception of keystrokes from a keyboard that are stored in a non-volatile memory. Storage medium721may be configured to include memory such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, floppy disks, hard disks, removable cartridges, or flash drives. In one example, storage medium721may be configured to include operating system723, application program725such as a web browser application, a widget or gadget engine or another application, and data file727. Storage medium721may store, for use by UE700, any of a variety of various operating systems or combinations of operating systems.

Storage medium721may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium721may allow UE700to access computer-executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium721, which may comprise a device readable medium.

InFIG.7, processing circuitry701may be configured to communicate with network743busing communication subsystem731. Network743aand network743bmay be the same network or networks or different network or networks. Communication subsystem731may be configured to include one or more transceivers used to communicate with network743b. For example, communication subsystem731may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another WD, UE, or base station of a radio access network (RAN) according to one or more communication protocols, such as IEEE 802.11, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver may include transmitter733and/or receiver735to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter733and receiver735of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem731may include data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. For example, communication subsystem731may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network743bmay encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network743bmay be a cellular network, a Wi-Fi network, and/or a near-field network. Power source713may be configured to provide alternating current (AC) or direct current (DC) power to components of UE700.

The features, benefits and/or functions described herein may be implemented in one of the components of UE700or partitioned across multiple components of UE700. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem731may be configured to include any of the components described herein. Further, processing circuitry701may be configured to communicate with any of such components over bus702. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry701perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry701and communication subsystem731. In another example, the non-computationally intensive functions of any of such components may be implemented in software or firmware and the computationally intensive functions may be implemented in hardware.

FIG.8is a schematic block diagram illustrating a virtualization environment800in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to a node (e.g., a virtualized base station or a virtualized radio access node) or to a device (e.g., a UE, a wireless device or any other type of communication device) or components thereof and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines or containers executing on one or more physical processing nodes in one or more networks).

In some embodiments, some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments800hosted by one or more of hardware nodes830. Further, in embodiments in which the virtual node is not a radio access node or does not require radio connectivity (e.g., a core network node), then the network node may be entirely virtualized.

The functions may be implemented by one or more applications820(which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operative to implement some of the features, functions, and/or benefits of some of the embodiments disclosed herein. Applications820are run in virtualization environment800which provides hardware830comprising processing circuitry860and memory890. Memory890contains instructions895executable by processing circuitry860whereby application820is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment800, comprises general-purpose or special-purpose network hardware devices830comprising a set of one or more processors or processing circuitry860, which may be commercial off-the-shelf (COTS) processors, dedicated Application Specific Integrated Circuits (ASICs), or any other type of processing circuitry including digital or analog hardware components or special purpose processors. Each hardware device may comprise memory890-1which may be non-persistent memory for temporarily storing instructions895or software executed by processing circuitry860. Each hardware device may comprise one or more network interface controllers (NICs)870, also known as network interface cards, which include physical network interface880. Each hardware device may also include non-transitory, persistent, machine-readable storage media890-2having stored therein software895and/or instructions executable by processing circuitry860. Software895may include any type of software including software for instantiating one or more virtualization layers850(also referred to as hypervisors), software to execute virtual machines840as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines840, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer850or hypervisor. Different embodiments of the instance of virtual appliance820may be implemented on one or more of virtual machines840, and the implementations may be made in different ways.

During operation, processing circuitry860executes software895to instantiate the hypervisor or virtualization layer850, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer850may present a virtual operating platform that appears like networking hardware to virtual machine840.

As shown inFIG.8, hardware830may be a standalone network node with generic or specific components. Hardware830may comprise antenna8225and may implement some functions via virtualization. Alternatively, hardware830may be part of a larger cluster of hardware (e.g. such as in a data center or customer premise equipment (CPE)) where many hardware nodes work together and are managed via management and orchestration (MANO)8100, which, among others, oversees lifecycle management of applications820.

Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

In the context of NFV, virtual machine840may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of virtual machines840, and that part of hardware830that executes that virtual machine, be it hardware dedicated to that virtual machine and/or hardware shared by that virtual machine with others of the virtual machines840, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) is responsible for handling specific network functions that run in one or more virtual machines840on top of hardware networking infrastructure830and corresponds to application820inFIG.8.

In some embodiments, one or more radio units8200that each include one or more transmitters8220and one or more receivers8210may be coupled to one or more antennas8225. Radio units8200may communicate directly with hardware nodes830via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system8230which may alternatively be used for communication between the hardware nodes830and radio units8200.

With reference toFIG.9, in accordance with an embodiment, a communication system includes telecommunication network910, such as a 3GPP-type cellular network, which comprises access network911, such as a radio access network, and core network914. Access network911comprises a plurality of base stations912a,912b,912c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area913a,913b,913c. Each base station912a,912b,912cis connectable to core network914over a wired or wireless connection915. A first UE991located in coverage area913cis configured to wirelessly connect to, or be paged by, the corresponding base station912c. A second UE992in coverage area913ais wirelessly connectable to the corresponding base station912a. While a plurality of UEs991,992are illustrated in this example, the disclosed embodiments are equally applicable to a situation where a sole UE is in the coverage area or where a sole UE is connecting to the corresponding base station912.

Telecommunication network910is itself connected to host computer930, which may be embodied in the hardware and/or software of a standalone server, a cloud-implemented server, a distributed server or as processing resources in a server farm. Host computer930may be under the ownership or control of a service provider, or may be operated by the service provider or on behalf of the service provider. Connections921and922between telecommunication network910and host computer930may extend directly from core network914to host computer930or may go via an optional intermediate network920. Intermediate network920may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network920, if any, may be a backbone network or the Internet; in particular, intermediate network920may comprise two or more sub-networks (not shown).

The communication system ofFIG.9as a whole enables connectivity between the connected UEs991,992and host computer930. The connectivity may be described as an over-the-top (OTT) connection950. Host computer930and the connected UEs991,992are configured to communicate data and/or signalling via OTT connection950, using access network911, core network914, any intermediate network920and possible further infrastructure (not shown) as intermediaries. OTT connection950may be transparent in the sense that the participating communication devices through which OTT connection950passes are unaware of routing of uplink and downlink communications. For example, base station912may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer930to be forwarded (e.g., handed over) to a connected UE991. Similarly, base station912need not be aware of the future routing of an outgoing uplink communication originating from the UE991towards the host computer930.

Example implementations, in accordance with an embodiment, of the UE, base station and host computer discussed in the preceding paragraphs will now be described with reference toFIG.10. In communication system1000, host computer1010comprises hardware1015including communication interface1016configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system1000. Host computer1010further comprises processing circuitry1018, which may have storage and/or processing capabilities. In particular, processing circuitry1018may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Host computer1010further comprises software1011, which is stored in or accessible by host computer1010and executable by processing circuitry1018. Software1011includes host application1012. Host application1012may be operable to provide a service to a remote user, such as UE1030connecting via OTT connection1050terminating at UE1030and host computer1010. In providing the service to the remote user, host application1012may provide user data which is transmitted using OTT connection1050.

Communication system1000further includes base station1020provided in a telecommunication system and comprising hardware1025enabling it to communicate with host computer1010and with UE1030. Hardware1025may include communication interface1026for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system1000, as well as radio interface1027for setting up and maintaining at least wireless connection1070with UE1030located in a coverage area (not shown inFIG.10) served by base station1020. Communication interface1026may be configured to facilitate connection1060to host computer1010. Connection1060may be direct or it may pass through a core network (not shown inFIG.10) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware1025of base station1020further includes processing circuitry1028, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. Base station1020further has software1021stored internally or accessible via an external connection.

Communication system1000further includes UE1030already referred to. Its hardware1035may include radio interface1037configured to set up and maintain wireless connection1070with a base station serving a coverage area in which UE1030is currently located. Hardware1035of UE1030further includes processing circuitry1038, which may comprise one or more programmable processors, application-specific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE1030further comprises software1031, which is stored in or accessible by UE1030and executable by processing circuitry1038. Software1031includes client application1032. Client application1032may be operable to provide a service to a human or non-human user via UE1030, with the support of host computer1010. In host computer1010, an executing host application1012may communicate with the executing client application1032via OTT connection1050terminating at UE1030and host computer1010. In providing the service to the user, client application1032may receive request data from host application1012and provide user data in response to the request data. OTT connection1050may transfer both the request data and the user data. Client application1032may interact with the user to generate the user data that it provides.

It is noted that host computer1010, base station1020and UE1030illustrated inFIG.10may be similar or identical to host computer930, one of base stations912a,912b,912cand one of UEs991,992ofFIG.9, respectively. This is to say, the inner workings of these entities may be as shown inFIG.10and independently, the surrounding network topology may be that ofFIG.9.

InFIG.10, OTT connection1050has been drawn abstractly to illustrate the communication between host computer1010and UE1030via base station1020, without explicit reference to any intermediary devices and the precise routing of messages via these devices. Network infrastructure may determine the routing, which it may be configured to hide from UE1030or from the service provider operating host computer1010, or both. While OTT connection1050is active, the network infrastructure may further take decisions by which it dynamically changes the routing (e.g., on the basis of load balancing consideration or reconfiguration of the network).

Wireless connection1070between UE1030and base station1020is in accordance with the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of OTT services provided to UE1030using OTT connection1050, in which wireless connection1070forms the last segment. More precisely, the teachings of these embodiments may improve the utility of the early measurement enhancements for Rel-16 (and subsequent releases) for UEs in deployments that contain a mix of Rel-15 and Rel-16 eNBs, thereby enabling faster CA/DC setup, and thereby provide benefits such as an improved end user experience.

A measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring OTT connection1050between host computer1010and UE1030, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection1050may be implemented in software1011and hardware1015of host computer1010or in software1031and hardware1035of UE1030, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection1050passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software1011,1031may compute or estimate the monitored quantities. The reconfiguring of OTT connection1050may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station1020, and it may be unknown or imperceptible to base station1020. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signalling facilitating host computer1010's measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software1011and1031causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection1050while it monitors propagation times, errors etc.

FIG.11is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.11will be included in this section. In step1110, the host computer provides user data. In substep1111(which may be optional) of step1110, the host computer provides the user data by executing a host application. In step1120, the host computer initiates a transmission carrying the user data to the UE. In step1130(which may be optional), the base station transmits to the UE the user data which was carried in the transmission that the host computer initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step1140(which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

FIG.12is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.12will be included in this section. In step1210of the method, the host computer provides user data. In an optional substep (not shown) the host computer provides the user data by executing a host application. In step1220, the host computer initiates a transmission carrying the user data to the UE. The transmission may pass via the base station, in accordance with the teachings of the embodiments described throughout this disclosure. In step1230(which may be optional), the UE receives the user data carried in the transmission.

FIG.13is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.13will be included in this section. In step1310(which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step1320, the UE provides user data. In substep1321(which may be optional) of step1320, the UE provides the user data by executing a client application. In substep1311(which may be optional) of step1310, the UE executes a client application which provides the user data in reaction to the received input data provided by the host computer. In providing the user data, the executed client application may further consider user input received from the user. Regardless of the specific manner in which the user data was provided, the UE initiates, in substep1330(which may be optional), transmission of the user data to the host computer. In step1340of the method, the host computer receives the user data transmitted from the UE, in accordance with the teachings of the embodiments described throughout this disclosure.

FIG.14is a flowchart illustrating a method implemented in a communication system, in accordance with one embodiment. The communication system includes a host computer, a base station and a UE which may be those described with reference toFIGS.9and10. For simplicity of the present disclosure, only drawing references toFIG.14will be included in this section. In step1410(which may be optional), in accordance with the teachings of the embodiments described throughout this disclosure, the base station receives user data from the UE. In step1420(which may be optional), the base station initiates transmission of the received user data to the host computer. In step1430(which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

The flow chart inFIG.15illustrates a method performed by a wireless device according to various embodiments. The method can be performed by the user equipment shown inFIG.7orFIG.17. The method relates to the handling of early measurement reporting to a network node, such as a base station, or eNB.

In step1501the method comprises the wireless device receiving a first indication from the network node. The first indication indicates a capability of the network node to receive early measurement reports for cells operating according to NR. That is, the first indication indicates whether or not the network node can receive early measurement reports for cells operating according to NR. In some embodiments, the first indication indicates that the network node is capable of receiving early measurement reports for cells operating according to NR.

Where the network node operates according to Release 15, the network node is only capable of receiving early measurement reports for cells operating to according LTE. In this case, the first indication indicates that the network node is not capable of receiving early measurement reports for cells operating to according NR. In some embodiments, the first indication that the network node is not capable of receiving early measurement reports for cells operating to NR can be the absence of a positive indication that NR cell measurements can be received.

In some embodiments, the first indication is received from the network node in or as system information (SI), a system information block, SIB, SIB2, an information request IE, an IE in a UEInformationRequest message, or an idleModeMeasurementReq IE.

In some embodiments, the first indication is a separate indication to a second indication from the network node. The second indication indicates a capability of the network node to receive early measurement reports for cells operating according to LTE. That is, the wireless device can also receive a second indication indicating whether or not the network node can receive early measurement reports for cells operating according to LTE. In some embodiments the first indication and the second indication are received from the network node in SIB2.

In some embodiments, the method further comprises the wireless device performing one or more radio signal measurements of a serving cell and/or one or more neighbouring cells while the wireless device is in an idle state, an idle mode or an inactive state. Any of the serving cell and/or one or more neighbouring cells can be configured to operate according to one or both of 3GPP Release 15 and 3GPP Release 16, LTE and NR or early measurement reporting requirements according to 3GPP Release 15 or 3GPP Release 16. As such, depending on the configuration of the network, the wireless device may only measure cells operating according to Release 15/LTE, only measure cells operating according to Release 16/NR, or measure some cells operating according to Release 15/LTE and some cells operating according to Release 16/NR.

The method can further comprise storing the one or more radio signal measurements of the serving cell and/or one or more neighbouring cells. In these embodiments, the radio signal measurements of LTE cells and NR cells (if measured) can be stored separately. The LTE cell measurements and NR cell measurements can be respectively stored in a 3GPP Release 15 variable/IE and a 3GPP Release 16 variable/IE.

In some embodiments, the method further comprises the wireless device sending the one or more radio signal measurements to the network node. In these embodiments, radio signal measurements of LTE cells and NR cells (if measured) can be sent in separate variables in an early measurement report.

In some embodiments, the wireless device sends a third indication to the network node. The third indication indicates early measurements that the wireless device has available to send to the network node. The wireless device selects the third indication to send to the network node based on the received first indication of the capability of the network node to receive early measurement reports for cells operating according to NR. The third indication can be sent to the network node in or as any one or more of a Radio Resource Control, RRC, message, an IE in a RRC message, an idleMeasAvailable IE, a RRC connection set up complete message, a RRCConnectionSetupComplete message, a RRC connection resume complete message, and a RRCConnectionResumeComplete message.

In some embodiments, if the received first indication indicates that the network node cannot receive early measurement reports for neighbouring cells operating according to NR and the wireless device only has early measurement results available for neighbouring cells operating according to NR (i.e. the wireless device does not have LTE measurements available), the wireless device does not indicate availability of early measurements to the network node (e.g. the wireless device does not send the third indication).

The flow chart inFIG.16illustrates a method performed by a base station (e.g. an eNB) according to various embodiments. The method can be performed by the network node shown inFIG.18. The method relates to the handling of early measurement reporting from a wireless device, such as a UE.

In step1601the method comprises the base station sending a first indication to the wireless device. The first indication indicates a capability of the base station to receive early measurement reports for cells operating according to NR. That is, the first indication indicates whether or not the base station can receive early measurement reports for cells operating according to NR. In some embodiments, the first indication indicates that the base station is capable of receiving early measurement reports for cells operating according to NR.

Where the base station operates according to Release 15, the base station is only capable of receiving early measurement reports for cells operating to according LTE. In this case, the first indication indicates that the base station is not capable of receiving early measurement reports for cells operating to according NR. In some embodiments, the first indication that the base station is not capable of receiving early measurement reports for cells operating to NR can be the absence of a positive indication that NR cell measurements can be received.

In some embodiments, the first indication is sent by the base station in or as SI, a SIB, SIB2, an information request IE, an IE in a UEInformationRequest message, or an idleModeMeasurementReq IE.

In some embodiments, the first indication is a separate indication to a second indication from the base station. The second indication indicates a capability of the base station to receive early measurement reports for cells operating according to LTE. That is, the base station can also send a second indication to the wireless device indicating whether or not the base station can receive early measurement reports for cells operating according to LTE. In some embodiments the first indication and the second indication are sent by the base station in SIB2.

In some embodiments, the method further comprises receiving one or more radio signal measurements from the wireless device. In these embodiments, radio signal measurements of LTE cells and NR cells (if present) can be received from the wireless device in separate variables in an early measurement report.

In some embodiments, the base station can receive a third indication from the wireless device. The third indication indicates early measurements that the wireless device has available to send to the base station. The third indication sent by the wireless device is selected based on the first indication of the capability of the base station to receive early measurement reports for cells operating according to NR. The third indication can be received by the base station in or as any one or more of a RRC message, an IE in a RRC message, an idleMeasAvailable IE, a RRC connection set up complete message, a RRCConnectionSetupComplete message, a RRC connection resume complete message, and a RRCConnectionResumeComplete message.

FIG.17is a block diagram of a wireless device1700that can be used to implement any of the wireless device or UE methods described herein. It will be appreciated that the wireless device1700may comprise one or more virtual machines running different software and/or processes. The wireless device1700may therefore comprise one or more servers, switches and/or storage devices and/or may comprise cloud computing infrastructure that runs the software and/or processes.

The wireless device1700comprises processing circuitry1701that controls the operation of the wireless device1700and can implement the methods described herein. The processing circuitry1701can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the wireless device1700in the manner described herein. In particular implementations, the processing circuitry1701can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of any of the methods described herein.

In some embodiments, the wireless device1700may optionally comprise a communications interface1702. The communications interface1702can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface1702can be configured to transmit to and/or receive from other nodes, network nodes or base stations requests, resources, information, data, signals, or similar. The processing circuitry1701may be configured to control the communications interface1702of the wireless device1700to transmit to and/or receive from other nodes, network nodes, or base stations requests, resources, information, data, signals, or similar.

Optionally, the wireless device1700may comprise a memory1703. In some embodiments, the memory1703can be configured to store program code that can be executed by the processing circuitry1701to perform any of the methods described herein. Alternatively or in addition, the memory1703can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry1701may be configured to control the memory1703to store any requests, resources, information, data, signals, or similar that are described herein.

FIG.18is a block diagram of a network node/base station1800that can be used to implement any of the network node, base station or eNB methods described herein. It will be appreciated that the base station1800may comprise one or more virtual machines running different software and/or processes. The base station1800may therefore comprise one or more servers, switches and/or storage devices and/or may comprise cloud computing infrastructure that runs the software and/or processes.

The base station1800comprises processing circuitry1801that controls the operation of the base station1800and can implement the methods described herein. The processing circuitry1801can comprise one or more processors, processing units, multi-core processors or modules that are configured or programmed to control the base station1800in the manner described herein. In particular implementations, the processing circuitry1801can comprise a plurality of software and/or hardware modules that are each configured to perform, or are for performing, individual or multiple steps of any of the methods described herein.

In some embodiments, the base station1800may optionally comprise a communications interface1802. The communications interface1802can be for use in communicating with other nodes, such as other virtual nodes. For example, the communications interface1802can be configured to transmit to and/or receive from other nodes, network nodes, base stations, wireless devices, UEs requests, resources, information, data, signals, or similar. The processing circuitry1801may be configured to control the communications interface1802of the base station1800to transmit to and/or receive from other nodes, network nodes, base stations, wireless devices or UEs requests, resources, information, data, signals, or similar.

Optionally, the base station1800may comprise a memory1803. In some embodiments, the memory1803can be configured to store program code that can be executed by the processing circuitry1801to perform any of the methods described herein. Alternatively or in addition, the memory1803can be configured to store any requests, resources, information, data, signals, or similar that are described herein. The processing circuitry1801may be configured to control the memory1803to store any requests, resources, information, data, signals, or similar that are described herein.

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

As noted above, any or all of the aspects or embodiments described herein can be performed by an apparatus in a wireless network (for example, the wireless network shown inFIG.6). The apparatus may be implemented in a wireless device or network node (e.g., wireless device610or network node660shown inFIG.6). The apparatus may be implemented as a Virtual Apparatus which may comprise processing circuitry, which may include one or more microprocessor or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), special-purpose digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory such as read-only memory (ROM), random-access memory, cache memory, flash memory devices, optical storage devices, etc. Program code stored in memory includes program instructions for executing one or more telecommunications and/or data communications protocols as well as instructions for carrying out one or more of the techniques described herein, in several embodiments. In some implementations, the processing circuitry may be used to cause one or more units of the Virtual Apparatus to perform corresponding functions according one or more embodiments of the present disclosure.

The term unit may have conventional meaning in the field of electronics, electrical devices and/or electronic devices and may include, for example, electrical and/or electronic circuitry, devices, modules, processors, memories, logic solid state and/or discrete devices, computer programs or instructions for carrying out respective tasks, procedures, computations, outputs, and/or displaying functions, and so on, as such as those that are described herein.

EMBODIMENTS

Example embodiments can include, but are not limited to, the following enumerated examples:

Group A Embodiments

1. A method performed by a wireless device for handling early measurement reporting to a network node, the method comprising any one or more of the following steps:receiving a first indication from the network node, the first indication indicating a capability of the network node to receive early measurement reports; andsending a second indication to the network node, the second indication indicating early measurements that the wireless device has available to send to the network node.2. The method of embodiment 1, wherein the first indication is received from the network node in or as any one or more of:system information;a system information block, SIB;SIB2;an information request information element, IE;an IE in a UEInformationRequest message; andan idleModeMeasurementReq IE.3. The method of embodiment 1 or 2, wherein the second indication is sent to the network node in or as any one or more of:a Radio Resource Control, RRC, message;an information element, IE, in a RRC message;an idleMeasAvailable IE;a RRC connection set up complete message;a RRCConnectionSetupComplete message;a RRC connection resume complete message; anda RRCConnectionResumeComplete message.4. The method of any of embodiments 1-3, wherein the capability of the network node to receive early measurement reports is any one or more of:capability to receive early measurement reports for cells operating according to 3GPP Release 15;capability to receive early measurement reports for cells operating according to 3GPP Release 16;capability to receive early measurement reports for cells operating according to 3GPP Release 15 and 3GPP Release 16;capability to receive early measurement reports for cells operating according to Long Term Evolution, LTE;capability to receive early measurement reports for cells operating according to New Radio, NR;capability to receive early measurement reports for cells operating according to LTE and NR;capability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15;capability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 16; andcapability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15 and 3GPP Release 16.5. The method of any of embodiments 1-4, wherein the second indication indicating early measurements that the wireless device has available to send to the network node is any one or more of:an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 15;an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 16;an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 15 and 3GPP Release 16;an indication that the wireless device has early measurement reports for cells operating according to Long Term Evolution, LTE;an indication that the wireless device has early measurement reports for cells operating according to New Radio, NR;an indication that the wireless device has early measurement reports for cells operating according to LTE and NR;an indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15;an indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 16; andan indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15 and 3GPP Release 16.6. The method of any of embodiments 1-5, wherein the method further comprises the step of:performing one or more radio signal measurements of a serving cell and/or one or more neighbouring cells while the wireless device is in an idle mode or inactive state.7. The method of embodiment 6, wherein the method further comprises the step of:storing the one or more radio signal measurements of the serving cell and/or one or more neighbouring cells.8. The method of embodiment 7, wherein the step of storing comprises any of:storing radio signal measurements of 3GPP Release 15 cells and 3GPP Release 16 cells separately;storing radio signal measurements of 3GPP Release 15 cells and 3GPP Release 16 cells together;storing radio signal measurements of Long Term Evolution, LTE, cells and New Radio, NR, cells separately; andstoring radio signal measurements of LTE cells and NR cells together.9. The method of embodiment 6, 7 or 8, wherein the method further comprises the step of:sending one or more of the one or more radio signal measurements to the network node according to the capability of the network node to receive early measurement reports.10. The method of any of embodiments 6-9, wherein each of the serving cell and/or one or more neighbouring cells are configured to operate according to one or both of:3GPP Release 15 and 3GPP Release 16;Long Term Evolution, LTE, and New Radio, NR;early measurement reporting requirements according to 3GPP Release 15 or 3GPP Release 16.11. The method of any of embodiments 1-10, wherein the wireless device selects the second indication to send to the network node based on the received first indication of the capability of the network node to receive early measurement reports.12. The method of any of the previous embodiments, further comprising:providing user data; andforwarding the user data to a host computer via the transmission to the base station.

Group B Embodiments

13. A method performed by a base station for handling early measurement reporting from a wireless device, the method comprising any one or more of the following steps:sending a first indication from the wireless device, the first indication indicating a capability of the base station to receive early measurement reports; andreceiving a second indication from the wireless device, the second indication indicating early measurements that the wireless device has available to send to the base station.14. The method of embodiment 13, wherein the first indication is sent by the base station in or as any one or more of:system information;a system information block, SIB;SIB2;an information request information element, IE;an IE in a UEInformationRequest message; andan idleModeMeasurementReq IE.15. The method of embodiment 13 or 14, wherein the second indication is received from the wireless device in or as any one or more of:a Radio Resource Control, RRC, message;an information element, IE, in a RRC message;an idleMeasAvailable IE;a RRC connection set up complete message;a RRCConnectionSetupComplete message;a RRC connection resume complete message; anda RRCConnectionResumeComplete message.16. The method of any of embodiments 13-15, wherein the capability of the network node to receive early measurement reports is any one or more of:capability to receive early measurement reports for cells operating according to 3GPP Release 15;capability to receive early measurement reports for cells operating according to 3GPP Release 16;capability to receive early measurement reports for cells operating according to 3GPP Release 15 and 3GPP Release 16;capability to receive early measurement reports for cells operating according to Long Term Evolution, LTE;capability to receive early measurement reports for cells operating according to New Radio, NR;capability to receive early measurement reports for cells operating according to LTE and NR;capability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15;capability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 16; andcapability to receive early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15 and 3GPP Release 16.17. The method of any of embodiments 13-16, wherein the second indication indicating early measurements that the wireless device has available to send to the base station is any one or more of:an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 15;an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 16;an indication that the wireless device has early measurement reports for cells operating according to 3GPP Release 15 and 3GPP Release 16;an indication that the wireless device has early measurement reports for cells operating according to Long Term Evolution, LTE;an indication that the wireless device has early measurement reports for cells operating according to New Radio, NR;an indication that the wireless device has early measurement reports for cells operating according to LTE and NR;an indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15;an indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 16; andan indication that the wireless device has early measurement reports for cells operating according to early measurement reporting requirements defined in 3GPP Release 15 and 3GPP Release 16.18. The method of any of embodiments 13-17, wherein the method further comprises the step of:receiving one or more radio signal measurements from the wireless device.19. The method of any of embodiments 13-17, wherein the method further comprises the step of:receiving one or more radio signal measurements from the wireless device according to the capability of the network node to receive early measurement reports.20. The method of any of embodiments 13-19, wherein the base station is operating according to:3GPP Release 15 and/or 3GPP Release 16;Long Term Evolution, LTE, and/or New Radio, NR;early measurement reporting requirements according to 3GPP Release 15 and/or 3GPP Release 16.21. The method of any of embodiments 13-20, further comprising:obtaining user data; andforwarding the user data to a host computer or a wireless device.

Group C Embodiments

22. A wireless device for handling early measurement reporting to a network node, the wireless device comprising:processing circuitry configured to perform any of the steps of any of the Group A embodiments; andpower supply circuitry configured to supply power to the wireless device.23. A base station for handling early measurement reporting from a wireless device, the base station comprising:processing circuitry configured to perform any of the steps of any of the Group B embodiments;power supply circuitry configured to supply power to the base station.24. A user equipment (UE) for handling early measurement reporting to a network node, the UE comprising:an antenna configured to send and receive wireless signals;radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry;the processing circuitry being configured to perform any of the steps of any of the Group A embodiments;an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry;an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; anda battery connected to the processing circuitry and configured to supply power to the UE.25. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward the user data to a cellular network for transmission to a user equipment (UE),wherein the cellular network comprises a base station having a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.26. The communication system of the previous embodiment further including the base station.27. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.28. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE comprises processing circuitry configured to execute a client application associated with the host application.29. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the base station performs any of the steps of any of the Group B embodiments.30. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.31. The method of the previous 2 embodiments, wherein the user data is provided at the host computer by executing a host application, the method further comprising, at the UE, executing a client application associated with the host application.32. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs any of the previous 3 embodiments.33. A communication system including a host computer comprising:processing circuitry configured to provide user data; anda communication interface configured to forward user data to a cellular network for transmission to a user equipment (UE),wherein the UE comprises a radio interface and processing circuitry, the UE's components configured to perform any of the steps of any of the Group A embodiments.34. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.35. The communication system of the previous 2 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; andthe UE's processing circuitry is configured to execute a client application associated with the host application.36. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, providing user data; andat the host computer, initiating a transmission carrying the user data to the UE via a cellular network comprising the base station, wherein the UE performs any of the steps of any of the Group A embodiments.37. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.38. A communication system including a host computer comprising:communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station,wherein the UE comprises a radio interface and processing circuitry, the UE's processing circuitry configured to perform any of the steps of any of the Group A embodiments.39. The communication system of the previous embodiment, further including the UE.40. The communication system of the previous 2 embodiments, further including the base station, wherein the base station comprises a radio interface configured to communicate with the UE and a communication interface configured to forward to the host computer the user data carried by a transmission from the UE to the base station.41. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.42. The communication system of the previous 4 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application, thereby providing request data; andthe UE's processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data in response to the request data.43. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving user data transmitted to the base station from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.44. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.45. The method of the previous 2 embodiments, further comprising:at the UE, executing a client application, thereby providing the user data to be transmitted; andat the host computer, executing a host application associated with the client application.46. The method of the previous 3 embodiments, further comprising:at the UE, executing a client application; andat the UE, receiving input data to the client application, the input data being provided at the host computer by executing a host application associated with the client application,wherein the user data to be transmitted is provided by the client application in response to the input data.47. A communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station's processing circuitry configured to perform any of the steps of any of the Group B embodiments.48. The communication system of the previous embodiment further including the base station.49. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.50. The communication system of the previous 3 embodiments, wherein:the processing circuitry of the host computer is configured to execute a host application;the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.51. A method implemented in a communication system including a host computer, a base station and a user equipment (UE), the method comprising:at the host computer, receiving, from the base station, user data originating from a transmission which the base station has received from the UE, wherein the UE performs any of the steps of any of the Group A embodiments.52. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE.53. The method of the previous 2 embodiments, further comprising at the base station, initiating a 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 an inconsistency between abbreviations, preference should be given to how it is used above. If listed multiple times below, the first listing should be preferred over any subsequent listing(s).DC Dual ConnectivityEN-DC E-UTRA NR Dual ConnectivityLTE-DC LTE Dual ConnectivityMCG Master Cell GroupMN Master NodeMR-DC Multi-Radio Dual ConnectivityNR-DC NR-NR Dual ConnectivityNE-DC NR-E-UTRA Dual ConnectivitySCG Secondary Cell GroupSN Secondary NodeSRB Signalling Radio Bearer1×RTT CDMA2000 1× Radio Transmission Technology3GPP 3rd Generation Partnership Project5G 5th GenerationABS Almost Blank SubframeARQ Automatic Repeat RequestAWGN Additive White Gaussian NoiseBCCH Broadcast Control ChannelBCH Broadcast ChannelCA Carrier AggregationCC Carrier ComponentCCCH SDU Common Control Channel SDUCDMA Code Division Multiplexing AccessCGI Cell Global IdentifierCIR Channel Impulse ResponseCP Cyclic PrefixCPICH Common Pilot ChannelCPICH Ec/No CPICH Received energy per chip divided by the power density in the bandCQI Channel Quality informationC-RNTI Cell RNTICSI Channel State InformationDCCH Dedicated Control ChannelDL DownlinkDM DemodulationDMRS Demodulation Reference SignalDRX Discontinuous ReceptionDTX Discontinuous TransmissionDTCH Dedicated Traffic ChannelDUT Device Under TestE-CID Enhanced Cell-ID (positioning method)E-SMLC Evolved-Serving Mobile Location CentreECGI Evolved CGIeNB E-UTRAN NodeBePDCCH enhanced Physical Downlink Control ChannelE-SMLC evolved Serving Mobile Location CenterE-UTRA Evolved UTRAE-UTRAN Evolved UTRANFDD Frequency Division DuplexFFS For Further StudyGERAN GSM EDGE Radio Access NetworkgNB Base station in NRGNSS Global Navigation Satellite SystemGSM Global System for Mobile communicationHARQ Hybrid Automatic Repeat RequestHO HandoverHSPA High Speed Packet AccessHRPD High Rate Packet DataLOS Line of SightLPP LTE Positioning ProtocolLTE Long-Term EvolutionMAC Medium Access ControlMBMS Multimedia Broadcast Multicast ServicesMBSFN Multimedia Broadcast multicast service Single Frequency NetworkMBSFN ABS MBSFN Almost Blank SubframeMDT Minimization of Drive TestsMIB Master Information BlockMME Mobility Management EntityMSC Mobile Switching CenterNPDCCH Narrowband Physical Downlink Control ChannelNR New RadioOCNG OFDMA Channel Noise GeneratorOFDM Orthogonal Frequency Division MultiplexingOFDMA Orthogonal Frequency Division Multiple AccessOSS Operations Support SystemOTDOA Observed Time Difference of ArrivalO&M Operation and MaintenancePBCH Physical Broadcast ChannelP-CCPCH Primary Common Control Physical ChannelPCell Primary CellPCFICH Physical Control Format Indicator ChannelPDCCH Physical Downlink Control ChannelPDP Profile Delay ProfilePDSCH Physical Downlink Shared ChannelPGW Packet GatewayPHICH Physical Hybrid-ARQ Indicator ChannelPLMN Public Land Mobile NetworkPMI Precoder Matrix IndicatorPRACH Physical Random Access ChannelPRS Positioning Reference SignalPSS Primary Synchronization SignalPUCCH Physical Uplink Control ChannelPUSCH Physical Uplink Shared ChannelRACH Random Access ChannelQAM Quadrature Amplitude ModulationRAN Radio Access NetworkRAT Radio Access TechnologyRLM Radio Link ManagementRNC Radio Network ControllerRNTI Radio Network Temporary IdentifierRRC Radio Resource ControlRRM Radio Resource ManagementRS Reference SignalRSCP Received Signal Code PowerRSRP Reference Symbol Received Power OR Reference Signal Received PowerRSRQ Reference Signal Received Quality OR Reference Symbol Received QualityRSSI Received Signal Strength IndicatorRSTD Reference Signal Time DifferenceSCH Synchronization ChannelSCell Secondary CellSDU Service Data UnitSFN System Frame NumberSGW Serving GatewaySI System InformationSIB System Information BlockSNR Signal to Noise RatioSON Self Optimized NetworkSS Synchronization SignalSSS Secondary Synchronization SignalTDD Time Division DuplexTDOA Time Difference of ArrivalTOA Time of ArrivalTSS Tertiary Synchronization SignalTTI Transmission Time IntervalUE User EquipmentUL UplinkUMTS Universal Mobile Telecommunication SystemUSIM Universal Subscriber Identity ModuleUTDOA Uplink Time Difference of ArrivalUTRA Universal Terrestrial Radio AccessUTRAN Universal Terrestrial Radio Access NetworkWCDMA Wide CDMAWLAN Wide Local Area Network