USER EQUIPMENT AND A METHOD PERFORMED THEREIN

TECHNICAL FIELD

Embodiments herein relate to a user equipment (UE) and method performed therein regarding wireless communication. Furthermore, a computer program and a carrier are also provided herein. Especially, embodiments herein relate to handling or enabling communication, e.g. handling communication at radio resource control (RRC) idle mode in a wireless communication network.

BACKGROUND

In a typical wireless communication network, UEs, also known as wireless communication devices, mobile stations, stations (STA) and/or wireless devices, communicate via a Radio access Network (RAN) to one or more core networks (CN).

3GPP Dual Connectivity

In 3GPP the Dual-Connectivity (DC), solution has been specified, both for Long Term Evolution (LTE) and between LTE and New Radio (NR). In DC, two nodes are involved, a master node (MN or MeNB) and a Secondary Node (SN, or SeNB). Multi-Connectivity (MC) is the case when there are more than 2 nodes involved. Also, it has been proposed in 3GPP that DC is used in the Ultra Reliable Low Latency Communications (URLLC) cases in order to enhance the robustness and to avoid connection interruptions.

There are different ways to deploy 5G network with or without interworking with LTE, also referred to as Evolved Universal Terrestrial Radio Access (E-UTRA), and Evolved Packet Core (EPC), as depicted in Fig. 1. In principle, NR and LTE can be deployed without any interworking, denoted by NR stand-alone (SA) operation. That is gNodeB (gNB) in NR may be connected to 5G core network (5GC) and evolved NodeB (eNB) may be connected to EPC with no interconnection between the two, illustrated as Option 1 and Option 2 in Fig. 1. On the other hand, the first supported version of NR is the so-called E-UTRAN-NR Dual Connectivity (EN-DC ), illustrated by Option 3 in Fig. 1. In such a deployment, dual connectivity between NR and LTE is applied with LTE as the master node (MN) and NR as the secondary node (SN). The radio access network (RAN) node such as a gNB supporting NR may not have a control plane (CP) connection to the core network such as the EPC. Instead, it relies on the LTE as a master node such as a master nNB (MeNB). This is also called as “Non-standalone NR". Notice that in this case, the functionality of an NR cell is limited and may be used for connected mode UEs as a booster and/or diversity leg, but an RRCJDLE UE cannot camp on these NR cells.

With introduction of 5GC, other options may be also valid. As mentioned above, option 2 supports stand-alone NR deployment where the gNB is connected to 5GC. Similarly, LTE may also be connected to 5GC using option 5, also known as eLTE, E- UTRA/5GC, or LTE/5GC, and the node may be referred to as an ng-eNB. In these cases, both NR and LTE are seen as part of the NG-RAN, and both the ng-eNB and the gNB may be referred to as NG-RAN nodes. It is worth noting that option 4 and option 7 are other variants of dual connectivity between LTE and NR which will be standardized as part of NG- RAN connected to 5GC, denoted by Multi-Radio Dual Connectivity (MR-DC). Under the MR-DC umbrella, there are:

• EN-DC (Option 3): LTE is the master node and NR is the secondary (EPC CN employed)

• NE-DC (Option 4): NR is the master node and LTE is the secondary (5GCN employed)

• NGEN-DC (Option 7): LTE is the master node and NR is the secondary (5GCN employed)

• NR-DC (variant of Option 2): Dual connectivity where both the master and secondary are NR (5GCN employed).

Fig. 1 shows 3GPP scenarios such as LTE and NR interworking options.

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

As described above, DC is standardized for both LTE and E-UTRA -NR DC (EN-DC).

LTE DC and EN-DC are designed differently when it comes to which nodes control what. Basically, there are two options:

1. Centralized solution (like LTE-DC),

2. Decentralized solution (like EN-DC). Fig. 2 shows the schematic control plane architecture for LTE DC and EN-DC. The main difference here is that in EN-DC, the SN has a separate RRC entity (NR RRC). This means that the SN may also control the UE, sometimes without the knowledge of the MN, but often the SN needs to coordinate with the MN. In LTE-DC, the RRC decisions are always coming from the MN (MN to UE). Note however that the SN still decides the configuration of the SN, since it is only the SN itself that has knowledge of what kind of resources, capabilities, etc. it has.

Fig. 2 shows a Control Plane architecture for Dual Connectivity in LTE DC and EN- DC.

For EN-DC, the major changes compared to LTE DC are:

• The introduction of split bearer from the SN, known as SCG split bearer

• The introduction of split bearer for RRC

• The introduction of a direct RRC from the SN, also referred to as SCG signalling radio bearer (SRB).

Fig. 3 and Fig. 4 show the user plane (UP) and Control Plane (CP) architectures for EN-DC.

Fig. 3 shows Network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC (EN-DC).

Fig. 4 shows a Network architecture for control plane in EN-DC.

The SN is sometimes referred to as secondary gNB (SgNB), where gNB is an NR base station, and the MN as MeNB in case the LTE is the master node and NR is the secondary node. In the other case, where NR is the master and LTE is the secondary node, the corresponding terms are SeNB and MgNB.

Split RRC messages are mainly used for creating diversity, and the sender may decide to either choose one of the links for scheduling the RRC messages, or it may duplicate the message over both links. In the downlink, the path switching between the MCG or SCG legs or duplication on both is left to network implementation. On the other hand, for the uplink (UL), the network configures the UE to use the MCG, SCG or both legs. The terms “leg”, “path”, and “radio link control (RLC) bearer” are used interchangeably throughout this document.

5G Status Indicator (5G icon)

In 3GPP there was a stepwise introduction of support for 5G/NR, where the first step comprised support for EN-DC, i.e. where the UE is configured with an LTE MCG and an NR SCG. In this case, NR was only used as a secondary cell group when the UE was in RRC_Connected. It was therefore also known as Non Standalone (NSA), since it could only be used together with LTE. In the next step, support for NR Standalone was introduced, where the UE can be camping in NR and set up a connection in NR, as primary cell (PCell)ZMCG.

Since a UE thus could be configured with NR (5G) also if establishing a connection in LTE (through EN-DC), there was a need to introduce some indication for the UE to determine whether it can consider itself to be in 5G coverage or not. Indications were therefore introduced in the LTE system information for a UE to determine whether it is in 5G coverage while camping in LTE, based on whether the UE can be configured with EN-DC or not in that cell.

When the UE determines, on an Access Stratum (AS) level, as described in e.g. the 3GPP RRC specification TS 36.331 , based on e.g. the indication in LTE system information, that it is in NR (5G) coverage, it will indicate this to the upper layers in the UE. It may then be used there to indicate to the end user whether the UE is in 5G coverage or not, by setting the 5G status indicator (5G icon), e.g., on the screen of the UE.

In a first release, an indication about the NR (5G) coverage was introduced through an upperLayerlndicator'^ SystemlnformationBlockType2 (SIB2) in LTE. This upperLayerlndicator could then be configured per Public Land Mobile Network (PLMN) in case of a shared cell. This upperLayerlndicator was then sent to upper layers in order to set the 5G status indicator (5G icon) for the end user accordingly. Later on, the requirements for the upperLayerlndicator were updated to also take into account whether the UE supports any of the NR frequencies, which are available for EN-DC configuration (per PLMN) in the LTE cell. This information is included in SystemlnformationBlockType26a (SIB26a). If SIB26a is present in the cell, the UE then checks whether it supports EN-DC configuration with the serving cell, i.e., where it is camping, and any of the NR frequencies that are indicated for the selected PLMN in SIB26a. If so, the UE (AS layer) forwards upperLayerlndication, as if received from SIB2, to upper layers. Otherwise, the UE (AS layer) indicates absence of upperLayerlndication to upper layers. If SIB26a is not present, the UE (AS layer) instead forwards the upperLayerlndication from SIB2, if present, to upper layers or indicates to upper layers that it is absent (if not present).

From 3GPP TS 36.331 v16.2.1, the actions at reception of SIB2: ************************************************************ *

5.2.2.9 Actions upon reception of SystemlnformationBlockType2 Upon receiving SystemlnformationBlockType2, the UE shall:

1> apply the configuration included in the radioResourceConfigCommon',

1> if in RRC INACTIVE:

2> apply the shortest of the ran-PagingCycle (if configured), the (UE specific) paging cycle (if indicated by upper layers), and the defaultPagingCycle included in the radioResourceConfigCommorr,

1> else if upper layers indicate that a (UE specific) paging cycle is configured:

2> apply the shortest of the (UE specific) paging cycle and the defaultPagingCycle included in the radioResourceConfigCommon',

1> if the mbsfn-SubframeConfigList is included:

2> consider that DL assignments may occur in the MBSFN subframes indicated in the mbsfri- SubframeConfigList under the conditions specified in TS 36.213 [23], clause 7.1;

1> apply the specified PCCH configuration defined in 9.1.1.3 ;

1> not apply the timeAlignmentTimerCommon',

1> if in RRC CONNECTED and UE is configured with RLF timers and constants values received within rlf-TimersAndConstants'.

2> not update its values of the timers and constants in ue-TimersAndConstants except for the value of timer T300;

1> if in RRC CONNECTED while T311 is not running; and the UE supports multi-band cells as defined by bit 31 in featureGroupIndicators or multipleNS-Pmax'.

2> disregard the additionalSpectrumEmission and ul-CarrierFreq, if received, while in RRC CONNECTED;

1> if attachWithoutPDN-Connectivity is received for the selected PLMN:

2> forward attachWithoutPDN-Connectivity to upper layers;

1> else:

2> indicate to upper layers that attachWithoutPDN-Connectivity is not present;

1> if cp-CIoT-EPS-Optimisation is received for the selected PLMN:

2> forward cp-CIoT-EPS-Optimisation to upper layers;

1> else:

2> indicate to upper layers that cp-CIoT-EPS-Optimisation is not present;

1> if up-CIoT-EPS-Optimisation is received for the selected PLMN:

2> forward up-CIoT-EPS-Optimisation to upper layers;

1> else:

2> indicate to upper layers that up-CIoT-EPS-Optimisation is not present;

1> if SystemInformationBlockType26a is not present:

2> to upper layers either forward upperLayerlndication, if present for the selected PLMN, or otherwise indicate absence of this field; NOTE: upperLayerlndication is an indication to upper layers that the UE has entered a coverage area that offers 5G capabilities.

1> to upper layers either forward rlos-Enabled, if present, or otherwise indicate absence of this field;

Upon receiving SystemlnformationBlockType2-NB, the UE shall:

1> apply the configuration included in the radioResourceConfigCommon’,

1> if upper layers indicate that a (UE specific) paging cycle is configured and ue-SpecificDRX- CycleMin is included in the radioResourceConfigCommon’.

2> apply the shortest of max ((UE specific) paging cycle, ue-SpecificDRX-CycleMin) and the defaultPagingCycle included in the radioResourceConfigCommorr,

1> else:

2> apply the defaultPagingCycle included in the radioResourceConfigCommon’,

1> if SystemInformationBlockType22-NB is scheduled:

2> read and act on information sent in SystemInformationBlockType22-NB’,

1> apply the specified PCCH configuration defined in 9.1.1.3.

1> if in RRC CONNECTED and UE is configured with RLF timers and constants values received within rlf-TimersAndConstants’.

2> not update its values of the timers and constants in ue-TimersAndConstants except for the value of timer T300;

Upon receiving SystemlnformationBlockType2 (SystemlnformationBlockType2-NB in

NB-loT), the UE shall:

1> if up-PUR-5GC is not included and the UE connected to 5GC in RRC IDLE with a suspended RRC connection is configured with pur-C nfig’. or

1> if up-PUR-EPC is not included and the UE connected to EPC in RRC IDLE with a suspended RRC connection is configured with pur-Config’, or

1> if cp-PUR-5GC is not included and the UE connected to 5GC in RRC IDLE without a suspended RRC connection is configured with pur-Config’, or

1> if cp-PUR-EPC is not included and the UE connected to EPC in RRC IDLE without a suspended RRC connection is configured with pur-Config’.

2> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur- TimeAlignmentTimer is released;

2> release pur-Config’,

2> discard previously stored pur-Config.

From 3GPP TS 36.331 v16.2.1, the actions at reception of SIB26a:

********************************************************* ****

5.2.2.33a Actions upon reception of SystemlnformationBlockType26a 1> if nrBandList is included for the selected PLMN and the UE supports to operate in EN- DC using the serving cell and at least one of NR bands in nrBandList:

2> forward upperLayerlndication, as if the UE receives this field from SIB2, to upper layers;

1> else:

2> _ indicate upper layers absence of upperLayerlndication',

Also a separate handling in case the UE enters RRC_CONNECTED has been introduced, where the UE then only should indicate that it is in NR (5G) coverage if it is actually configured with EN-DC. If the UE thus is in RRC_CONNECTED but with no NR SCG, it should then not indicate to the end user that it is in NR (5G) coverage. This has been implemented in the procedures for RRC Resume and RRC Reconfiguration.

From 3GPP TS 36.331 v16.2.1 , the actions at reception of the RRCConnectionResume message: ************************************************************ *

5.3.3.4a Reception of the RRCConnectionResume by the UE

The UE shall:

1> stop timer T300;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> stop T380 if running;

1> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for EDT or for transmission using PUR:

2> discard the stored UE AS context and resumeidentity,

2> if the RRCConnectionResume is received in response to an RRCConnectionResumeRequest for transmission using PUR:

3> instruct the associated MAC entity to start timeAlignmentTimer',

1> else:

2> if resuming an RRC connection from a suspended RRC connection in EPC; or

2> for NB-IoT, if resuming an RRC connection from a suspended RRC connection in 5GC and fullConfig is not present in the RRCConnectionResume message:

3> restore the PDCP state and re-establish PDCP entities for SRB2, if configured with E- UTRA PDCP, and for all DRBs that are configured with E-UTRA PDCP;

3> if drb-ContinueROHC is included: 4> indicate to lower layers that stored UE AS context is used and that drb- ContinueROHC is configured;

4> continue the header compression protocol context for the DRBs configured with the header compression protocol;

3> else:

4> indicate to lower layers that stored UE AS context is used;

4> reset the header compression protocol context for the DRBs configured with the header compression protocol;

3> if restoreMCG-SCells is included:

4> restore the MCG SCell(s) configuration, if stored;

3> else:

4> release the MCG SCell(s) from the UE AS context, if stored;

3> if restoreSCG is included:

4> restore nr-SecondaryCellGroupConfig, if stored;

3> else if the UE was configured with EN-DC:

4> perform MR-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

3> discard the stored UE AS context and resumeidentity,

3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

2> else if the RRCConnectionResume message includes the fullConfig (i.e., for resuming an RRC connection from RRC INACTIVE or for resuming a suspended RRC connection in 5GC):

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> else if resuming an RRC connection from RRC INACTIVE:

3> restore the following from the stored UE Inactive AS context:

- MCG physical layer configuration,

- MCG MAC configuration,

- MCG RLC configuration,

- PDCP configuration;

3> if restoreMCG-SCells is included:

4> restore the MCG SCell(s) configuration, if stored;

3> else:

4> release the MCG SCell(s) from the UE AS context, if stored;

3> if restoreSCG is included:

4> restore nr-SecondaryCellGroupConfig, if stored; 3> else if the UE was configured with NGEN-DC:

4> perform MR-DC release, as specified in TS 38.331 [82], clause 5.3.5.10;

3> discard the stored UE Inactive AS context;

3> configure lower layers to consider the restored MCG and SCG SCell(s) (if any) to be in deactivated state;

3> release the rrc-InactiveConfig, except ran-NotificationArealnfo',

2> else (i.e., except for NB-IoT for resuming a suspended RRC connection in 5GC):

3> restore the physical layer configuration, the MAC configuration, the RLC configuration and the PDCP configuration from the stored UE AS context;

3> discard the stored UE AS context and resumeidentity,

1> perform the radio resource configuration procedure in accordance with the received radioResourceConfigDedicated and as specified in 5.3.10;

NOTE 1 : When performing the radio resource configuration procedure, for the physical layer configuration and the MAC Main configuration, the restored RRC configuration from the stored UE AS context is used as basis for the reconfiguration.

1> if the YQCQYVQ& RRCConnectionResume includes the sCellToReleaseList

2> perform SCell release as specified in 5.3.10.3a;

1> if the YQCQYVQ& RRCConnectionResume includes the sCellToAddModList

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> if the received RRCConnectionResume includes the sCellGroupToReleaseList.

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionResume includes the sCellGroupToAddModList

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionResume message includes the nr-SecondaryCellGroupConfig'.

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionResume message includes the sk-Counter

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.8;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfigl'.

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionResume message includes the nr-RadioBearerConfig2'.

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

[...some parts skipped...]

1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerlndication to upper layers as if the UE has received this field from SIB2, otherwise indicate to upper layers the absence of this field; 1> submit the RRCConnectionResumeComplete message to lower layers for transmission;

1> the procedure ends.

********************************************************* ****

From 3GPP TS 36.331 v16.2.1 , the actions at reception of the RRCConnectionReconfiguration message (without or with mobilityControlInfo):

********************************************************* ****

5.3.5.3 Reception of an RRCConnectionReconfiguration not including the mobilityControlInfo by the UE

If the RRCConnectionReconfiguration message does not include the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if the received RRCConnectionReconfiguration includes the daps-SourceRelease'.

2> reset source MCG MAC and release the source MCG MAC configuration;

2> for each DAPS bearer:

3> re-establish the RLC entity or entities for the source PCell;

3> release the RLC entity or entities and the associated DTCH logical channel for the source PCell;

3> reconfigure the PDCP entity to release DAPS, as specified in TS 36.323 [8];

2> for each SRB:

3> release the PDCP entity for the source PCell;

3> release the RLC entity and the associated DCCH logical channel for the source PCell;

2> release the physical channel configuration for the source PCell;

1> if this is the first RRCConnectionReconfiguration message after successful completion of the RRC connection re-establishment procedure:

2> re-establish PDCP for SRB2 configured with E-UTRA PDCP entity and for all DRBs that are established and configured with E-UTRA PDCP, if any;

2> re-establish RLC for SRB2 and for all DRBs that are established and configured with E- UTRA RLC, if any;

2> if the RRCConnectionReconfiguration message includes the fullConfig'.

3> perform the radio configuration procedure as specified in 5.3.5.8;

2> if the RRCConnectionReconfiguration message includes the radioResourceConfigDedicated.

3> perform the radio resource configuration procedure as specified in 5.3.10;

NOTE 1: Void NOTE 2: Void

1> else:

2> if the RRCConnectionReconfiguration message includes the radioResourceCon figDedi cated.

3> perform the radio resource configuration procedure as specified in 5.3.10;

NOTE 3 : If the RRCConnectionReconfiguration message includes the establishment of radio bearers other than SRB1, the UE may start using these radio bearers immediately, i.e. there is no need to wait for an outstanding acknowledgment of the SecurityModeComplete message.

1> if the received RRCConnectionReconfiguration includes the sCellToReleaseList.

2> perform SCell release as specified in 5.3.10.3a;

1> if the received RRCConnectionReconfiguration includes the sCellToAddModList

2> perform SCell addition or modification as specified in 5.3.10.3b;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToReleaseList'.

2> perform SCell group release as specified in 5.3.10.3d;

1> if the received RRCConnectionReconfiguration includes the sCellGroupToAddModList'.

2> perform SCell group addition or modification as specified in 5.3.10.3e;

1> if the received RRCConnectionReconfiguration includes the scg-Configuration or

1> if the current UE configuration includes one or more split DRBs configured with pdcp-Config and the received RRCConnectionReconfiguration includes radioResourceConfigDedicated including drb-ToAddModList

2> perform SCG reconfiguration as specified in 5.3.10.10;

1> if the received RRCConnectionReconfiguration includes the nr-Config and it is set to release'. or

1> if the received RRCConnectionReconfiguration includes endc-ReleaseAndAdd and it is set to TRUE'.

2> perform MR-DC release as specified in TS 38.331 [82], clause 5.3.5.10;

1> if the received RRCConnectionReconfiguration includes the sk-Counter.

2> perform key update procedure as specified in TS 38.331 [82], clause 5.3.5.7;

1> if the received RRCConnectionReconfiguration includes the nr-SecondaryCellGroupConfig'.

2> perform NR RRC Reconfiguration as specified in TS 38.331 [82], clause 5.3.5.3;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfigl'.

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

1> if the received RRCConnectionReconfiguration includes the nr-RadioBearerConfig2'.

2> perform radio bearer configuration as specified in TS 38.331 [82], clause 5.3.5.6;

[...some parts skipped...] 1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerlndication, as if the UE receives this field from SIB2, to upper layers, otherwise indicate upper layers absence of this field;

1> if the UE is configured with NE-DC:

2> transfer the RRCConnectionReconfigurationComplete message via SRB 1 embedded in NR RRC message RRCReconfigurationComplete as specified in TS 38.331 [82];

1> else:

2> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission using the new configuration, upon which the procedure ends;

5.3.5.4 Reception of an RRCConnectionReconfiguration including the mobilityControlinfo by the UE (handover)

If the RRCConnectionReconfiguration message includes the mobilityControlinfo and the UE is able to comply with the configuration included in this message, the UE shall:

1> if daps-HO is not configured for any DRB:

2> stop timer T310, if running;

2> stop timer T312, if running;

2> if timer T316 is running:

3> stop timer T316;

3> clear the information included in VarRLF -Report, if any;

2> resume MCG transmission, if suspended;

1> start timer T304 with the timer value set to t304, as included in the mobilityControlinfo',

1> stop timer T370, if running;

1> if the carrierFreq is included:

2> consider the target PCell to be one on the frequency indicated by the carrierFreq with a physical cell identity indicated by the targetPhysCellld',

1> else:

2> consider the target PCell to be one on the frequency of the source PCell with a physical cell identity indicated by the targetPhysCellld',

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> start synchronising to the DL of the target PCell;

NOTE 1 : The UE should perform the handover as soon as possible following the reception of the RRC message triggering the handover, which could be before confirming successful reception (HARQ and ARQ) of this message. [...some parts skipped...]

1> if the UE is configured to operate in EN-DC as result of this procedure, forward upperLayerlndication, as if the UE receives this field from SIB2, to upper layers, otherwise indicate upper layers absence of this field;

1> set the content of RRCConnectionReconfigurationComplete message as follows:

2> if the UE has radio link failure or handover failure information available in VarRLF-Report and if the RPLMN is included in plmn-IdentityList stored in VarRLF-Report.

3> include rlf-InfoAvailable',

2> if the UE has MBSFN logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport and if T330 is not running:

3> include logMeasAvailableMBSFN',

2> else if the UE has logged measurements available for E-UTRA and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport.

3> include the logMeasAvailable',

2> if the UE has Bluetooth logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport.

3> include logMeasAvailableBT,

2> if the UE has WLAN logged measurements available and if the RPLMN is included in plmn-IdentityList stored in VarLogMeasReport.

3> include logMeasAvailableWLAN',

2> if the UE has connection establishment failure information available in VarConnEstFailReport and if the RPLMN is equal to plmn-Identity stored in VarConnEstFailReport.

3> include connEstFaillnfoAvailable',

2> if the RRCConnectionReconfiguration message includes perCC-GapIndicationRequest.

3> include perCC-GapIndicationList wA numFreqEffective

2> if the frequencies are configured for reduced measurement performance:

3> include numFreqEffectiveReduced,

2> if the UE has flight path information available:

3> include flightPathlnfoAvailable',

2> if the received RRCConnectionReconfiguration message included nr- SecondaryCellGroupConfig'.

3> include scg-ConfigResponseNR in accordance with TS 38.331 [82], clause 5.3.5.3;

1> submit the RRCConnectionReconfigurationComplete message to lower layers for transmission;

[...some parts skipped...]

********************************************************* **** System information validity and acquisition.

In LTE, the UE considers stored system information to be invalid after 3 hours from the moment it was successfully confirmed as valid. There is a systemlnfoValueTag in the SystemlnformationBlockTypel (SIB1) message that indicates the current valid version of the system information in the cell. In case the UE has stored system information from the current cell with the same systemlnfoValueTag as the one that is currently indicated by systemlnfoValueTag in SystemlnformationBlockTypel , the UE then does not have to reacquire the system information until 3 hours has passed since it was received.

In case there is a change of the system information in the cell in the LTE, the network changes the systemlnfoValueTag value in SystemlnformationBlockTypel and then includes an indication (systemlnfoModificatior) in the Paging message. The UE then acquires SystemlnformationBlockTypel to check the value of the systemlnfoValueTag to determine whether it needs to reacquire the system information, i.e. the other SIBs that are scheduled through the SystemlnformationBlockTypel message (e.g. SIB2 and SIB26a).

There currently exist certain challenges. For example, when a UE is in RRC_CONNECTED in LTE and gets an RRCConnectionReconfiguration message, the UE will send an indication to the upper layers that depends on whether it is configured with EN- DC, i.e. whether the UE is configured with an NR SCG in addition to the LTE MCG, as a result of the RRCConnectionReconfiguration message. If the UE thus is configured with EN- DC, the AS layer will forward upperLayerlndication, as if the UE received the field from SIB2, to the upper layers, so that it is indicated to the end user that the UE is in coverage of NR (5G). If the UE is not configured with EN-DC, i.e. it has an LTE connection without NR SCG, the UE AS layer will instead indicate absence of the upperLayerlndication field to the upper layers, thereby indicating to the end user that the UE is not in coverage of NR (5G).

If the UE thereafter gets released from RRC_CONNECTED to RRCJDLE (or RRC NACTIVE) in LTE, no update of presence of upperLayerlndication is sent to the upper layers. An indication about a relevant upperLayerlndication field in SIB2 or SIB26a will only be sent to the upper layers when the SIB2 and/or SIB26a is reacquired, when the corresponding procedures specified in 3GPP TS 36.331 clauses 5.2.2.9 and 5.2.2.33a, respectively, are performed. Stored SIBs are valid up to 3 hours in case there is no change in the content, which means it may be a very long time until the broadcasted indication is sent to upper layers in the UE, and thus indicated to the end user.

An example scenario would be that a UE is camping in an LTE cell in an area with NR coverage, for possible EN-DC configuration for the UE, where upperLayerlndication is set in SIB2, and possibly also in SIB26a. The UE indicates this to upper layers and thereby indicates to the end user that the UE is in coverage of NR (5G). If the UE then enters RRC_CONNECTED without entering EN-DC, e.g. the NR SCG may not be needed or suitable for the specific connection, the II E AS layer will instead indicate absence of the upperLayerlndication field to the upper layers, thereby indicating to the end user that the UE is not in coverage of NR (5G). This will be indicated to the end user even though the UE is still in an area where it would be possible to configure it with EN-DC. When the UE then is released to RRCJDLE (or RRCJNACTIVE), the UE AS layer will not send any new indication to upper layers until it reacquires SIB2 and/or SIB26a the next time, or until it enters RRC_CONNECTED the next time, and then is configured with EN-DC, through an RRCConnectionReconfiguration message. This leads to that the UE thereby will (incorrectly) indicate to the end user that the UE is not in coverage of NR (5G) for a time of up to 3 hours, in case the UE remains in the same LTE cell.

SUMMARY

An object of embodiments herein is to provide a mechanism to improve UE operation in an efficient manner.

According to an aspect the object is achieved by providing a method performed by a UE within a cell in a communications network, the method comprising, in response to leaving a connected mode, acquiring system information related to 5G capabilities of said cell.

According to another aspect the object is achieved by providing a UE in a cell in a communications network, wherein the UE is configured to, in response to leaving a connected mode, acquire system information related to 5G capabilities of said cell.

According to yet another aspect a computer program is provided comprising instructions, which when executed by a processor, causes the processor to perform actions according to the methods herein.

According to still another aspect a carrier comprising the computer program is provided, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

According to embodiments of the present disclosure, in case the UE is released from RRC_CONNECTED to RRCJDLE/RRCJNACTIVE in LTE, the UE may check the settings for coverage of NR ((NG)EN-DC) in system information for the cell, or for the selected PLMN. In other words, during the RRC connection release procedure it is added that the UE may check, for the selected PLMN, whether it supports any of the NR frequencies that are indicated in SIB26a, if present, for (NG)EN-DC configuration with the current serving cell. If SIB26a is not present, the UE may instead check the setting of the upperLayerlndication in SIB2 for the selected PLMN. The corresponding upperLayerlndication (or absence of it) may then be forwarded or sent to upper layers as a result of, or during, e.g. as a response to, the RRC connection release procedure, so that the 5G status indicator (e.g. 5G icon) can be set according to the broadcasted information when the UE is in RRC_IDLE/RRC_INACTIVE. Thus, the operation of the UE is improved.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments will now be described in more detail in relation to the enclosed drawings, in which:

Fig. 1 shows different ways to deploy a 5G network in accordance with 3GPP, with or without interworking with LTE.

Fig. 2 shows a control plane architecture for Dual Connectivity in LTE DC and EN-DC. Fig. 3 shows network side protocol termination options for MCG, SCG and split bearers in MR-DC with EPC.

Fig. 4 shows a network architecture for control plane in EN-DC.

Fig. 5 is a flowchart illustrating a UE behaviour according to a previously described process.

Fig. 6a is a flowchart illustrating a method performed by a UE within a cell in a communications network, in accordance with some embodiments.

Fig. 6b is another flowchart illustrating a method performed by a UE within a cell in a communications network, in accordance with some embodiments.

Fig. 7 is a flowchart illustrating a method performed by a UE for handling an indicator relating to 5G coverage within a cell, in accordance with some embodiments.

Figs. 8a and 8b are diagrams illustrating a UE in accordance with some embodiments.

Fig. 9 is a diagram illustrating a wireless network in accordance with some embodiments.

Fig. 10 is diagram illustrating a UE in accordance with some embodiments.

Fig. 11 is a diagram illustrating a virtualization environment in accordance with some embodiments.

Fig. 12 is a diagram illustrating a telecommunication network connected via an intermediate network to a host computer, in accordance with some embodiments. Fig. 13 is a diagram illustrating a host computer communicating via a base station with a user equipment over a partially wireless connection, in accordance with some embodiments.

Figs. 14, 15, 16, and 17 are flowcharts illustrating methods implemented in a communication system including a host computer, a base station and a user equipment, in accordance with some embodiments.

Fig. 18 is a block diagram illustrating a virtualization apparatus in accordance with some embodiments.

DETAILED DESCRIPTION

In some aspects, a method performed by a UE within a cell in a communications network is provided. The method comprises, in response to leaving a connected mode, acquiring system information related to 5G capabilities of said cell.

In some aspect, the object is achieved by providing a UE in a cell in a communications network, wherein the UE is configured to, in response to leaving a connected mode, acquire system information related to 5G capabilities of said cell.

Generally, all terms used herein are to be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and/or is implied from the context in which it is used. All references to a/an/the element, apparatus, component, means, step, etc. are to be interpreted openly as referring to at least one instance of the element, apparatus, component, means, step, etc., unless explicitly stated otherwise. The steps of any methods disclosed herein do not have to be performed in the exact order disclosed, unless a step is explicitly described as following or preceding another step and/or where it is implicit that a step must follow or precede another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, wherever appropriate. Likewise, any advantage of any of the embodiments may apply to any other embodiments, and vice versa. Other objectives, features and advantages of the enclosed embodiments will be apparent from the following description.

Fig. 5 shows a UE behaviour according to an approach wherein the UE may end up incorrectly indicating to an end user that the UE is not in coverage of 5G capability.

Action 510. The UE is in the connected mode.

Action 520. The UE determines whether to show a 5G icon based on connected mode procedures, e.g., determines to show the 5G icon if 5G-operation is enabled.

Action 530. The UE exits CONNECTED mode and goes to IDLE or INACTIVE mode. Action 540. The UE acquires system information related 5G icon due to legacy procedures, e.g. periodically, due to cell changes, etc.

Action 550. The UE determines whether to show the 5G icon based on acquired system information.

In Fig. 5, the second-to-last action, step 540, i.e. “UE acquires system information....”, may be performed a significant amount of time after the UE has exited CONNECTED mode, during which period the UE may incorrectly indicate to the end user that the UE is not in coverage of 5G.

The method actions performed by a UE 800, see Figs. 8a and 8b, within a cell in a communications network according to embodiments will now be described with reference to a flowchart depicted in Fig. 6a. The actions do not have to be taken in the order stated below, but may be taken in any suitable order. Actions performed in some embodiments are marked with dashed boxes.

Action 601. In response to leaving a connected mode, the UE 800 acquires system information related to 5G capabilities of said cell. The UE 800 may acquire the system information by reacquiring system information in response to a RRC connection release procedure. The acquired system information may be for a selected Public Land Mobile Network (PLMN) of said cell. The UE 800 may acquire the system information by receiving the system information broadcasted in said cell. The system information may be acquired during a radio resource control connection release procedure. Thus, according to embodiments herein the system information is acquired rapidly when leaving connected mode and the UE 800 will correctly indicate whether 5G capabilities are present or not.

Action 602. The UE 800 may determine, based on said acquired system information, whether 5G capabilities are provided in said cell. The UE 800 may determine whether the 5G capabilities are provided by determining whether system information stored within the UE is still valid based on the acquired system information, wherein said acquired system information comprises system information block one (SIB1). If it is determined that the system information is valid, the stored system information may be used to determine whether the 5G capabilities are provided. In some embodiments, the UE 800 may determine whether the 5G capabilities are provided by determining whether any of the NR frequencies that are indicated in SIB26a is supported for E-UTRAN-NR Dual Connectivity (EN-DC) configuration with the cell. In some embodiments, the UE 800 may determine whether the 5G capabilities are provided by determining whether an indication for 5G capabilities is present in SIB2 for the cell. Action 603. If it is determined that the system information is not valid, the UE 800 may reacquire system information, wherein the system information comprises SIB26a and/or SIB2.

Action 604. The UE 800 may indicate, to upper layers, whether the UE is within a cell that offers 5G capabilities. The UE 800 may indicate this to the upper layers by providing an indication that the UE is within a cell that offers 5G capabilities, wherein the indication is, in some embodiments, an upperLayerlndication. The indication may be provided at a certain time after that the UE has left the connected mode and only if the UE at that time still is not in the connected mode. In some embodiments, the indication may be provided only if there is a change whether the UE is within a cell that offers 5G capabilities compared to a latest indication transmitted to the upper layers. It may be indicated at a display of the UE whether the UE is in coverage of 5G.

Thus, according to a first aspect, there is provided a method implemented, or performed, by a UE within a cell in a communications network. The cell may be a serving cell.

The method comprises acquiring system information related to 5G (NR) coverage, or 5G capabilities, in said cell in response to leaving, or exiting, a connected mode.

In some embodiments, acquiring system information related to 5G capabilities of said cell in response to leaving a connected mode comprises reacquiring system information in response to a RRC connection release procedure.

In some embodiments, acquiring system information related to 5G capabilities of said cell may comprise acquiring system information related to 5G capabilities for a selected PLMN of said cell.

In some embodiments, acquiring system information related to 5G capabilities may comprise receiving system information broadcasted in said cell.

In some embodiments, the method further comprises determining, based on said acquired system information, whether 5G capabilities are provided in said cell.

In some embodiments, determining whether 5G capabilities are provided comprises determining whether system information stored within the UE is still valid based on the acquired system information, wherein said acquired system information comprises SIB1. If it is determined that the system information is valid, the method may further comprise using the stored system information to determine whether 5G capabilities are provided. If it is determined that the system information is not valid, the method may further comprise reacquiring system information, wherein the system information comprises SIB26a and/or SIB2. In some embodiments, determining whether 5G capabilities are provided comprises determining whether any of the NR frequencies that are indicated in SIB26a is supported for E-UTRAN-NR Dual Connectivity, EN-DC, configuration with the cell.

In some embodiments, determining whether 5G capabilities are provided comprises determining whether an indication for 5G capabilities is present in SIB2 for the cell.

In some embodiments, the method further comprises indicating, to upper layers, whether the UE is within a cell that offers 5G capabilities. The step of indicating, to upper layers, whether the UE is within a coverage area that offers 5G capabilities may comprise providing an indication that the UE is within a cell that offers 5G capabilities. The indication may be, for example, an upperLayerlndication.

In some embodiments, the indication is provided a certain time after that the UE has left the connected mode and only if the UE at that time still is not in a connected mode.

In some embodiments, the indication is provided only if there is a change of the indication compared to the latest indication transmitted to the upper layers.

In some embodiments, it is indicated at a display of the UE whether the UE is in coverage of 5G. A 5G status indicator may indicate whether the UE is in coverage of 5G.

In some embodiments, the connected mode is RRC_CONNECTED.

In some embodiments, the cell in the communications network is an LTE cell.

In some embodiments, leaving the connected mode comprises receiving a RRCConnectionRelease message.

Fig 6b shows an embodiment according to the present disclosure. As shown in Fig. 6b, the second-to-last action, action 640, is different compared to action 540 in the process illustrated in Fig. 5. The new behaviour described herein will result in that the UE 800 acquires system information in response to exiting CONNECTED mode and hence, the time from that the UE 800 exits from CONNECTED until that the UE 800 determines whether or not to show the 5G icon is shortened, which results in a shorter time when the UE may display (or not display) the 5G icon inaccurately.

Action 610. The UE 800 may be in connected mode.

Action 620. The UE 800 may determine whether to show a 5G icon based on connected mode procedures, e.g., the UE 800 may show the icon if 5G-operation is enabled.

Action 630. The UE 800 exits CONNECTED and goes to IDLE/INACTIVE mode.

Action 640. The UE 800 acquires system information related 5G icon in response to exiting CONNECTED, for example, during connection release procedure.. Action 650. The UE 800 may determine whether to show 5G icon based on acquired system information.

There are, proposed herein, various embodiments which address one or more of the issues disclosed herein.

Certain embodiments may provide the following technical advantage. Embodiments herein ensure that the UE 100, for example, camping in LTE and supporting EN-DC, which is in an area where there is NR (5G) coverage for such EN-DC configuration, will be able to indicate this to the end user directly after leaving an RRC connection without EN-DC configuration, i.e. during which the UE should not indicate that it is in NR (5G) coverage. Otherwise, a UE, which had an RRC connection without an NR SCG at the end, i.e. not configured as EN-DC when releasing the UE to RRC_IDLE/RRC_INACTIVE, may indicate that it is not in NR (5G) coverage, and thus not set the 5G status indication for the end user up to 3 hours, even if it is actually in an area where it may be configured with EN-DC and it is indicated so in system information.

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.

Terminology.

Any two or more embodiments described in this document may be combined in any way with each other. The described embodiments are not limited to LTE, but can be adapted in other RATs too, e.g., NR, UTRA, LTE-Advanced, 5G, NX, NB-loT, WiFi, BlueTooth, or any new radio systems wherein indications about coverage of other RATs, frequency bands or cells are provided.

In some embodiments, a non-limiting term User Equipment, or “UE”, is used. The UE herein can be any type of wireless device capable of communicating with network node or another UE over radio signals. The UE may also be radio communication device, target device, device to device (D2D) UE, machine type UE or UE capable of machine to machine communication (M2M), a sensor equipped with UE, iPAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME), USB dongles, Customer Premises Equipment (CPE), etc. Also, in some embodiments, generic terminology “network node” is used. It can be any kind of network node which may comprise of a radio network node such as base station, radio base station, base transceiver station, base station controller, network controller, gNB, NR BS, evolved Node B (eNB), Node B, Multi-cel l/multicast Coordination Entity (MCE), relay node, access point, radio access point, Remote Radio Unit (RRU) Remote Radio Head (RRH), a multi-standard BS (a.k.a. MSR BS), a core network node (e.g., MME, SON node, a coordinating node, positioning node, MDT node, etc.), or even an external node (e.g., 3rd party node, a node external to the current network), etc. The network node may also comprise a test equipment.

It should be noted that it will herein be described how the AS layer in the UE 800 sends presence or absence of an upperLayerlndication to higher layers in the UE. As previously described, the “5G status indicator” is modelled in the standard specification as a flag which can be present, to indicate that 5G is available, or absent, to indicate that 5G is not available. However, this is just an example of an implementation used in the standard specification. It may, in a certain implementation, be possible to model the 5G status indicator in different ways, e.g. that the UE 800 always indicates a particular indication to higher layers, but the indication may take different values or representations; one value or representation which indicates that 5G is available and another value or representation which indicates that 5G is not available. There may be many other modelling approaches a certain implementation may take in order to achieve the behaviour described by the model in the standard specification, and it should be clear to the person skilled in the art to understand how to translate the behaviour of the embodiments described herein to the corresponding behaviour for that other model used in an actual implementation.

According to a first aspect of the present disclosure, there is provided a method implemented, or performed, by the UE 800 within the cell in the communications network. The cell may be a serving cell. According to another aspect of the present disclosure there is provided the UE 800 performing the method according to the first aspect. An embodiment of the present disclosure is now going to be described with reference to Fig. 7, illustrated herein below.

According to one embodiment, the method 700 comprises action 740 of acquiring system information related to 5G (NR) capabilities, or 5G coverage, in said cell. This is performed as a response to the UE 800 leaving, or exiting, the connected mode. The connected mode may correspond to RRC_CONNECTED, and leaving this mode may mean that the UE enters RRCJNACTIVE or RRCJDLE modes. Steps 710-730 are optional steps and correspond to steps 510-530 of Fig. 5 previously described. Action 710. The UE 800 may be in a connected mode.

Action 720. The UE 800 may determine whether to show a 5G icon.

Action 730. The UE 800 leaves CONNECTED and enter IDLE/INACTIVE mode.

Action 740. The UE 800 acquires system information related 5G capabilities within said cell.

Action 750. The UE 800 may determine whether 5G capabilities are provided based on acquired system information.

Action 760. The UE 800 may indicate the 5G capabilities.

Some embodiments according to the present disclosure is now going to be described more in detail.

Forwarding upperLayerlndication to upper layers at RRC connection release procedure.

In one embodiment, the UE 800 , or from AS layer of the UE 800, sends the upperLayerlndication, or absence of thereof, to upper layers when it leaves RRC_CONNECTED state and enters RRCJDLE state or RRC_IN ACTIVE state. The UE 800 may then e.g. forward an upperLayerlndication, or indicate absence of the upperLayerlndication, based on the UE capabilities and the information in SIB26a, if present in the serving cell. Otherwise, if SIB26a is not present, the UE 800 may then e.g. forward an upperLayerlndication, or indicate absence of the upperLayerlndication, based on the presence of upperLayerlndication in SIB2 for the cell where the UE 800 is camping after entering RRCJDLE or RRCJNACTIVE. The UE 800 may then perform these actions even if the UE 800 does not reacquire/receive the system information, e.g. SIB2 and/or SIB26a, when entering RRC DLE/RRC N ACTIVE. The UE 800 may thus update the “5G status indicator” to be based on the information that is being broadcasted in the cell, even if the UE 800 camps in a cell where it has already stored the system information that is valid in the cell. This may, e.g., be the case if the UE 800, when entering RRCJDLE or RRCJNACTIVE, remains in the same cell as where it was in RRC_CONNECTED and the indicated valid version of the system information in the cell is the same as the one that the UE 800 has stored.

Accordingly, in one embodiment, the action 740 of acquiring system information related to 5G capabilities of said cell in response to leaving a connected mode may comprise reacquiring system information in response to a RRC connection release procedure. Acquiring system information related to 5G capabilities of said cell may comprise acquiring system information related to 5G capabilities for a selected PLMN of said cell. Acquiring system information related to 5G capabilities may further comprise receiving system information broadcasted in said cell.

Thereafter, in some embodiments, the method 700 may further comprise action 750 of determining, based on said acquired system information, whether 5G capabilities, or 5G coverage, are provided in said cell. Determining whether the 5G capabilities are provided may comprise determining whether any of the NR frequencies that are indicated in SIB26a is supported for EN-DC configuration with the cell. Alternatively, determining whether the 5G capabilities are provided may comprise determining whether an indication for the 5G capabilities is present in SIB2 for the cell.

In some embodiments, the method 700 may further comprise action 760 of indicating, to upper layers, whether the UE 800 is within a cell that offers 5G capabilities. This may comprise providing an indication that the UE 800 is within a cell that offers 5G capabilities, i.e. that 5G coverage is provided. The indication may be, for example, an upperLayerlndication. In one embodiment, the UE may send the upperLayerl indication, or absence of thereof, to upper layers when it has received the RRCConnectionRelease message from the network. In such embodiments, it may be indicated at a display of the UE 800 whether the UE 800 is in coverage of 5G. A 5G status indicator may indicate whether the UE 800 is in coverage of 5G. This makes it possible for an end-user to view whether the UE 800 is located within a cell that provides 5G coverage. The method 700 according to these embodiments relates to handling of upperLayerlndication at transition to RRCJDLE. Thus, according to some embodiments, the method 700 may be a method 700 for handling an indicator relating to 5G coverage within a cell.

In another embodiment, the UE 800 may send the upperLayerlndication, or absence of thereof, to the upper layers when it enters RRC DLE or RRC NACTIVE from RRC_CONNECTED due to other reasons than reception of an RRCConnectionRelease message. As an example, if the UE 800 enters RRCJDLE due to that there is a failure in the connection. The UE 800 may then also update the “5G status indicator” to be based on the information that is being broadcasted in the cell, even if it camps in a cell where it has already stored the system information that is valid in the cell.

In yet another embodiment, the UE 800 may send the upperLayerlndication, or absence of thereof, to upper layers only some time after the UE 800 has entered RRCJDLE/RRCJNACTIVE. Thus, the indication may be provided a certain time after that the UE 800 has left the connected mode and only if the UE 800 at that time, i.e. after that certain time has passed, still is not in a connected mode. In this way a “too frequent” change of the “5G status indicator” may be avoided in case the UE 800, e.g. soon afterwards, may enter RRC_CONNECTED again.

In another embodiment, the UE 800 may only send the upperLayerlndication, or absence thereof, to upper layers, e.g. during or after the RRC connection release procedure, or when entering RRCJDLE/RRCJNACTIVE, if there is a change compared to the latest indication that was sent to the upper layers. Thus, the indication may be provided only if there is a change of the indication compared to the latest indication transmitted to the upper layers. If, for example, the UE 800 would forward the upperLayerlndication to upper layers based on the content of system information, and possibly the UE capabilities, and the last indication sent by the UE 800 to upper layers also comprised forwarding the upperLayerlndication, e.g. since the last configuration the UE 800 had in RRC_CONNECTED was EN-DC, then the UE 800 will not forward the upperLayerlndication during the RRC connection release procedure, even if, based on the procedures to determine whether or not to forward the indication would suggest that the UE 800 should forward the upperLayerlndication. If there instead is a difference compared to the latest indication transmitted to the upper layers, the UE 800, from the AS layer, will send new information to the upper layers, i.e., presence or absence of the upperLayerlndication.

In some alternatives of the above embodiments, the UE 800 may reacquire system information, e.g. SIB1, SIB2 and/or SIB26a, in response to (e.g. during or after) entering RRCJDLE or RRCJNACTIVE state, e.g. due to an RRC connection release procedure. The UE 800 may then forward the upperLayerlndication, or indicate absence thereof, based on the information in the newly acquired system information (SIB26a or SIB2). In one embodiment, the UE 800 may reacquire SIB1 during (or after) the RRC connection release procedure to check whether the stored system information (for e.g. SIB2 and/or SIB26a) is still valid, based on e.g. the systemlnfoValueTag value. Thus, step 750 of determining whether 5G capabilities are provided may comprise determining whether stored system information is still valid based on the acquired system information. The acquired system information may then comprise SIB1. If the stored system information is still valid, the UE 800 may then use the information in the stored system information to determine whether to forward the upperLayerlndication to upper layers or whether to indicate absence thereof. The UE 800 may then perform the actions that are performed upon reception of SIB2 and/or SIB26a, as specified in 3GPP TS 36.331 clauses 5.2.2.9 and 5.2.2.33a respectively, even if the corresponding SIB is not reacquired/received at this point in time. Thus, if it is determined that the system information is valid, the method 700 may further comprise using the stored system information to determine whether 5G capabilities, or 5G coverage, are provided. If the stored system information instead is not valid according to the systemlnfoValueTag value in SIB1, the UE 800 may first reacquire the system information, e.g. SIB26a and/or SIB2. Thus, if it is determined that the system information is not valid, the method may further comprise reacquiring system information, wherein the system information comprises SIB26a and/or SIB2.

Possible RRC implementation.

Below are some example implementations of the above embodiments into 3GPP TS 36.331 (v16.2.1), where one or several of these could be implemented, see changes underlined and bold:

5.3.8.3 Reception of the RRCConnectionRelease by the UE

The UE shall:

1> except for NB-IoT, BL UEs or UEs in CE, delay the following actions defined in this subclause 60 ms from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

1> for BL UEs or UEs in CE, delay the following actions defined in this subclause 1.25 seconds from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier;

1> for NB-IoT, delay the following actions defined in this subclause 10 seconds from the moment the RRCConnectionRelease message was received or optionally when lower layers indicate that the receipt of the RRCConnectionRelease message has been successfully acknowledged, whichever is earlier.

NOTE 0: For BL UEs, UEs in CE and NB-IoT, when STATUS reporting, as defined in TS 36.322 [7], has not been triggered and the UE has sent positive HARQ feedback (ACK), as defined in TS 36.321 [6], the lower layers can be considered to have indicated that the receipt of the RRCConnectionRelease message has been successfully acknowledged.

1> stop T380, if running;

1> for NB-IoT:

2> if the UE has reported anr-InfoAvailable, clear VarANR-MeasConfig-NB and VarANR-MeasReport- NB-

2> if the UE has reported rlf-InfoAvailable, clear VarRLF-Report-NB',

1> if the RRCConnectionRelease message is received in response to an RRCConnectionResumeRequest for EDT or for UP transmission using PUR:

2> indicate to upper layers that the suspended RRC connection has been resumed;

2> discard the stored UE AS context and resumeidentity,

2> stop timer T300;

2> stop timer T302, if running;

2> stop timer T303, if running; 2> stop timer T305, if running;

2> stop timer T306, if running;

2> stop timer T308, if running;

2> perform the actions as specified in 5.3.3.7;

2> if timer T316 is running:

3> stop timer T316;

3> clear the information included in VarRLF -Report, if any;

2> stop timer T320, if running;

2> stop timer T322, if running;

2> stop timer T323, if running;

1> except for UEs using the Control Plane CIoT 5GS optimisation, if AS security is not activated and if UE is connected to 5GC:

2> ignore any field included in RRCConnectionRelease message except waitTimc,

2> perform the actions upon leaving RRC CONNECTED or RRC IN ACTIVE as specified in 5.3.12 with the release cause 'other' upon which the procedure ends;

1> if the RRCConnectionRelease message includes redirectedCarrierlnfo indicating redirection to gerarr, or

1> if the RRCConnectionRelease message includes idleModeMobilityControlInfo including freqPriorityListGERAN'.

2> if AS security has not been activated; and

2> if upper layers indicate that redirect to GERAN without AS security is not allowed:

3> ignore the content of the RRCConnectionRelease',

3> perform the actions upon leaving RRC CONNECTED or RRC IN ACTIVE as specified in

5.3.12, with release cause 'other', upon which the procedure ends;

1> if AS security has not been activated:

2> ignore the content of redirectedCarrierlnfo, if included and indicating redirection to nr;

2> ignore the content of idleModeMobilityControlInfo, if included and including freqPriorityListNR',

2> ignore the altFreqPriorities and T323, if included;

2> if the UE ignores the content of redirectedCarrierlnfo or of idleModeMobilityControlInfo, or of altFreqPriorities and T323 :

3> perform the actions upon leaving RRC CONNECTED as specified in 5.3.12, with release cause 'other', upon which the procedure ends;

1> if the RRCConnectionRelease message includes redirectedCarrierlnfo indicating redirection to eutra and if UE is connected to 5GC:

2> if cn-Type is included:

3> after the cell selection, indicate the available CN Type(s) and the received cn-Type to upper layers; NOTE 1 : Handling the case if the E-UTRA cell selected after the redirection does not support the core network type specified by the cn-Type, is up to UE implementation.

1> if the RRCConnectionRelease message includes the idleModeMobilityControlInfo:

2> store the cell reselection priority information provided by the idleModeMobilityControlInfo',

2> if the 1320 is included:

3> start timer T320, with the timer value set according to the value of 1320:

1> else if the RRCConnectionRelease message includes the altFreqPriorities'.

2> store the received altFreqPriorities',

2> for E-UTRA frequency, apply the alternative cell reselection priority information broadcast in the system information if available, otherwise apply the cell reselection priority broadcast in the system information;

2> for inter-RAT frequency, apply the cell reselection priority broadcast in the system information;

2> if the 1323 is included:

3> start timer T323, with the timer value set according to the value of 1323:

1> else:

2> apply the cell reselection priority information broadcast in the system information;

1> if the RRCConnectionRelease message includes the releaseMeasIdleConfig'.

2> if timer T331 is running:

3> stop timer T331;

3> perform the actions as specified in 5.6.20.3;

1> if the RRCConnectionRelease message includes the measIdleConfig'.

2> clear VarMeasIdleConfig and VarMeasIdleReport',

2> store the received measIdleDuration in VarMeasIdleConfig',

2> start or restart T331 with the value of measIdleDuration',

2> if the measIdleConfig contains measIdleCarrierListEUTRA'.

3> store the received measIdleCarrierListEUTRA in VarMeasIdleConfig',

2> if the measIdleConfig contains measIdleCarrierListNR'.

3> store the received measIdleCarrierListNR in VarMeasIdleConfig',

2> if the measIdleConfig contains validityAreaList'.

3> store the received validityAreaList in VarMeasIdleConfig',

NOTE 2: If the measIdleConfig contains neither measIdleCarrierListEUTRA nor measIdleCarrierListNR, UE may receive measIdleCarrierListEUTRA and/or measIdleCarrierListNR as specified in 5.6.20.1a.

1> for NB-IoT, if the RRCConnectionRelease message includes the anr-MeasConfig'.

2> clear VarANR-MeasConfig-NB and VarANR-MeasReport-NB', 2> store the received anr-QualityThreshold in VarANR-MeasConfig-NB',

2> if the anr-MeasConfig contains anr-CarrierList'.

3> store the received anr-CarrierList in VarANR-MeasConfig-NB',

2> set plmn-IdentityList in VarANR-MeasReport-NB to include the list of EPLMNs stored by the UE (i.e. includes the RPLMN);

2> set servCellldentity in VarANR-MeasReport-NB to the global cell identity of the Pcell;

2> start performing ANR measurements as specified in 5.6.24;

1> if the RRCConnectionRelease message includes the pur-Config'.

2> if pur-Config is set to setup'.

3> store or replace the PUR configuration provided by the pur-Config',

3> if pur-TimeAlignmentTimer is included in the received pur-Config'.

4> configure lower layers in accordance with pur-TimeAlignmentTimer',

3> else:

4> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur- TimeAlignmentTimer is released;

3> start maintenance of PUR occasions as specified in 5.3.3.20;

2> else:

3> if pur-TimeAlignmentTimer is configured, indicate to lower layers that pur-TimeAlignmentTimer is released;

3> release pur-Config, if configured;

3> discard previously stored pur-Config',

1> for NB-IoT, if the RRCConnectionRelease message includes the redirectedCarrierlnfo'.

2> if the redirectedCarrierOffsetDedicated is included in the redirectedCarrierlnfo'.

3> store the dedicated offset for the frequency in redirectedCarrierlnfo',

3> start timer T322, with the timer value set according to the value of 7322 in redirectedCarrierlnfo',

1> if the releaseCause received in the RRCConnectionRelease message indicates loadBalancingTA URequired'.

2> perform the actions upon leaving RRC CONNECTED as specified in 5.3.12, with release cause 'load balancing T AU required';

1> else if the releaseCause received in the RRCConnectionRelease message indicates cs- FallbackHighPriori ty :

2> perform the actions upon leaving RRC CONNECTED as specified in 5.3.12, with release cause 'CS Fallback High Priority';

1> else:

2> if the extendedWaitTime is present; and 2> if the UE supports delay tolerant access or the UE is a NB-IoT UE:

3> forward the extendedWaitTime to upper layers;

2> if the extendedWaitTime-CPdata is present and the NB-IoT UE only supports the Control Plane CIoT EPS optimisation:

3> forward the extendedWaitTime-CPdata to upper layers;

2> if SystemInformationBlockType26a is present:

3> perform the actions as specified in 5.2.2.33a;

2> else:

3> if upperLayerlndication is present for the selected PLMN in SystemInformationBlockType2‘.

4> forward upperLayerlndication to upper layers;

3> else:

4> indicate absence of upperLayerlndication to upper layers;

2> if the releaseCause received in the RRCConnectionRelease message indicates rrc-Suspend:

3> perform the actions upon leaving RRC CONNECTED as specified in 5.3.12, with release cause 'RRC suspension';

2> else if rrc-InactiveConfig is included:

3> perform the actions upon entering RRC NACTIVE as specified in 5.3.8.7;

2> else:

3> perform the actions upon leaving RRC CONNECTED or RRCJNACTIVE as specified in

5.3.12, with release cause 'other';

5.3.8. 7 UE actions upon entering RRCJNACTIVE

Upon entering RRCJNACTIVE, the UE shall:

1> reset MAC and release the default MAC configuration if any;

1> stop all timers that are running except T302, T309, T320, T323 and T325;

1> re-establish RLC entities for all SRBs and DRBs;

1> if the RRCConnectionRelease message is including the aitTime

2> start timer T302, with the timer value set according to the waitTime',

2> inform the upper layer that access barring is applicable for all access categories except categories 'O' and '2';

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> apply the received rrc-InactiveConfig',

1> if the RRCConnectionRelease message was received in response to an RRCConnectionResumeRe quest. 2> in the stored UE Inactive AS context:

3> replace the I< _C NB and K^cint keys with the current I< _C NB and KRRCint keys;

3> replace the C-RNTI with the temporary C-RNTI which the UE has used to receive the RRCConnectionRelease message;

3> replace the cellidentity with the cellidentity of the PCell at the time the UE has received the RRCConnectionRelease message;

3> replace the previously stored physical cell identity with the physical cell identity of the PCell at the time the UE has received the RRCConnectionRelease message;

1> else:

2> store in the UE Inactive AS Context, the current I< _C NB and KRRCint keys, the ROHC state, the stored QoS flow to DRB mapping rules, the C-RNTI used in the source PCell, the cellidentity and the physical cell identity of the source PCell, the spCellConfigCommon y/iAdyiReconfigurationWithSync of the PSCell (if configured), and all other parameters configured;

1> if the periodic-RNA U-timer is included:

2> start timer T380, with the timer value set to the periodic-RNA U-timer',

1> suspend all SRB(s) and DRB(s), except SRBO;

1> indicate PDCP suspend to lower layers of all DRBs;

1> indicate the suspension of the RRC connection to upper layers;

1> if SystemInformationBlockType26a is present:

2> perform the actions as specified in 5.2.2.33a;

1> else:

2> if upperLayerlndication is present for the selected PLMN in SystemInformationBlockType2'

3> forward upperLayerlndication to upper layers;

2> else:

3> indicate absence of upperLayerlndication to upper layers;

1> enter RRC INACTIVE and perform procedures as specified in TS 36.304 [4], clause 5.2.7;

Upon selecting to an inter-RAT cell or switching to another CN type, the UE shall:

1> perform the actions upon leaving RRC INACTIVE as specified in 5.3.12, with release cause 'other';

5.3.12 UE actions upon leaving RRC_CONNECTED or RRCJNACTIVE

Upon leaving RRC_CONNECTED or RRCJNACTIVE, the UE shall:

1> reset MAC;

1> if leaving RRC INACTIVE was not triggered by the reception of RRCConnectionRelease including idleModeMobilityControlInfo or altFreqPriorities'.

2> stop the timer T320 and T323, if miming;

2> if stored, discard the cell reselection priority information provided by the idleModeMobilityControlInfo', 2> if stored, discard the altFreqPriorities provided by the RRCConnectionRelease',

1> if entering RRC IDLE was triggered by reception of the RRCConnectionRelease message including a waitTime.'

2> start timer T302, with the timer value set according to the w aiiTi ie'.

2> inform the upper layer that access barring is applicable for all access categories except categories 'O' and '2';

1> else if T302 is running:

2> stop timer T302;

2> if the UE is connected to 5GC:

3> perform the actions as specified in 5.3.16.4;

1> if T309 is running:

2> stop timer T309 for all access categories;

2> perform the actions as specified in 5.3.16.4.

1> stop all timers that are running except T302, T320, T322, T323, T325, T330, T331;

1> release crs-ChEstMPDCCH-ConfigDedicated, if configured;

1> if leaving RRC CONNECTED was triggered by suspension of the RRC:

2> re-establish RLC entities for all SRBs and DRBs, including RBs configured with NR PDCP;

2> store the UE AS Context including the current RRC configuration, the current security context, the PDCP state including ROHC state, C-RNTI used in the source PCell, the cellldentity and the physical cell identity of the source PCell, and the spCellConfigCommon within ReconfigurationWithSync of the PSCell (if configured);

2> store the following information provided by E-UTRAN:

3> if the UE connected to 5GC is a BL UE or UE in CE:

4> the fullI-RNTI, if present;

4> the shortl-RNTI, if present;

3> else:

4> the resumeidentity,

3> the nextHopChainingCount, if present. Otherwise discard any stored nextH opChainingCount that does not correspond to stored key KRRCmt;

3> the drb-ContinueROHC, if present. Otherwise discard any stored drb-ContinueROHC',

2> suspend all SRB(s) and DRB(s), including RBs configured with NR PDCP, except SRBO;

2> if the UE connected to 5GC is a BL UE or UE in CE, indicate PDCP suspend to lower layers of all DRBs;

2> if the UE is connected to 5GC:

3> indicate the idle suspension of the RRC connection to upper layers;

2> else: 3> indicate the suspension of the RRC connection to upper layers;

2> configure lower layers to suspend integrity protection and ciphering;

NOTE 1 : Except when resuming an RRC connection after early security reactivation in accordance with conditions in 5.3.3.18, ciphering is not applied for the subsequent RRCConnectionResume message used to resume the connection and an integrity check is performed by lower layers, but merely upon request from RRC.

1> else:

2> upon leaving RRC IN ACTIVE:

3> discard the UE Inactive AS context;

3> discard the K _e NB, the Kpacenc key, the KRRCim and the Kupenc key;

2> release rrc-InactiveConfig, if configured;

2> remove all entries within VarConditionalReconfiguration, if any;

2> for each measld, that is part of the current UE configuration in VarMeasConfig, if the associated reportConfig has condReconfigurationTriggerEUTRA configured:

3> remove the entry with the matching reportConfigld from the reportConfigList within the VarMeasConfig',

3> if the associated measObjectld is only associated with condReconfigurationTriggerEUTRA'.

4> remove the entry with the matching measObjectld from the measObjectList within the VarMeasConfig',

3> remove the entry with the matching measld from the measIdList within the VarMeasConfig',

2> release all radio resources, including release of the MAC configuration, the RLC entity and the associated PDCP entity and SDAP (if any) for all established RBs, except for the following:

- pur-Config, if stored;

2> indicate the release of the RRC connection to upper layers together with the release cause;

1> if leaving RRC CONNECTED was triggered neither by reception of the MobilityFromEUTRACommand message nor by selecting an inter-RAT cell while T311 was running; or

1> if leaving RRC INACTIVE was not triggered by the inter-RAT cell reselection:

2> if timer T350 is configured:

3> start timer T350;

3> apply rclwi-Configuration if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN included in SystemlnformationBlockTypel 7;

2> else:

3> release the wlan-OffloadConfigDedicated, if received;

3> if the wlan-OffloadConfigCommon corresponding to the RPLMN is broadcast by the cell:

4> apply the wlan-OffloadConfigCommon corresponding to the RPLMN included in SystemlnformationBlockTypel 7;

4> apply steerToWLAN if configured, otherwise apply the wlan-Id-List corresponding to the RPLMN included in SystemlnformationBlockTypel 7; 2> if SystemInformationBlockType26a is present:

3> perform the actions as specified in 5.2.2.33a;

2> else:

3> if upperLayerlndication is present for the selected PLMN in SystemInformationBlockType2‘.

4> forward upperLayerlndication to upper layers;

3> else:

4> indicate absence of upperLayerlndication to upper layers;

2> enter RRC IDLE and perform procedures as specified in TS 36.304 [4], clause 5.2.7; 1> else:

2> release the wlan-OffloadConfigDedicated, if received;

NOTE 2: BL UEs or UEs in CE verifies validity of SI when released to RRC IDLE. 1> release the LWA configuration, if configured, as described in 5.6.14.3; 1> release the LWIP configuration, if configured, as described in 5.6.17.3;

According to another aspect of the present disclosure, there is provided the UE 800 implementing the method according to the first aspect. Example embodiments are illustrated in Figs. 8a and 8b.

Embodiments herein relate to the UE 800 in the cell in the communications network, wherein the UE 800 is configured to, in response to leaving the connected mode, acquire system information related to 5G capabilities of said cell. The UE 800 may be configured to acquire the system information by reacquiring system information in response to a Radio Resource Control (RRC) connection release procedure. The acquired system information may be for a selected PLMN of said cell. The UE 800 may be configured to acquire the system information by receiving the system information broadcasted in said cell. The UE 800 may further be configured to determine, based on said acquired system information, whether 5G capabilities are provided in said cell. The UE 800 may be configured to determine whether 5G capabilities are provided by determining whether system information stored within the UE is still valid based on the acquired system information, wherein said acquired system information comprises SIB1. If it is determined that the system information is valid, the UE 800 may be configured to use the stored system information to determine whether 5G capabilities are provided. If it is determined that the system information is not valid, the UE 800 may be configured to reacquire system information, wherein the system information comprises SIB26a and/or SIB2. The UE 800 may be configured to determine whether 5G capabilities are provided by determining whether any of the NR frequencies that are indicated in SIB26a is supported for EN-DC configuration with the cell. The UE 800 may be configured to determine whether 5G capabilities are provided by determining whether an indication for 5G capabilities is present in SIB2 for the cell. The UE 800 may be configured to indicate, to upper layers, whether the UE is within a cell that offers 5G capabilities. The UE 800 may be configured to indicate to the upper layers, whether the UE is within the coverage area that offers 5G capabilities by providing an indication that the UE is within a cell that offers 5G capabilities, wherein the indication is an upperLayerlndication. The indication may be provided at a certain time after that the UE has left the connected mode and only if the UE at that time still is not in the connected mode. The indication may be provided only if there is a change whether the UE is within a cell that offers 5G capabilities compared to a latest indication transmitted to the upper layers. Whether the UE is in coverage of 5G may be indicated at a display of the UE. The UE 800 may be configured to acquire the system information during a radio resource control connection release procedure.

According to some embodiments, the UE 800 may comprise a determining unit 81, an acquiring unit 82, a transmitting unit 83, and a receiving unit 84 configured to perform the method 700. According to various embodiments, the UE 800 may comprise a processor 86 and a memory 87, as shown in Fig. 8b. The memory 87 may store computer program code which, when run in the processor 86 may cause the UE 800 to perform the method 700 according to the previously presented aspect.

Thus, the UE 800 is configured to acquire system information related to 5G capabilities in the cell which it is located within. The UE 800 is configured to perform this in response to leaving a connected mode.

In some embodiments, the UE 800 may further be configured to determine, based on said acquired system information, whether 5G capabilities are provided in said cell.

In some embodiments, the UE 800 may further be configured to indicate, to upper layers, whether the UE 800 is within a cell that offers 5G capabilities.

The present disclosure ensures that a 5G status indicator for an end user is set accurately. A UE camping in an LTE cell supporting EN-DC will be able to indicate, to the end user, that there is NR (5G) coverage directly, or at least soon, after leaving an RRC connection without EN-DC configuration, i.e. during which the UE should not indicate that it is in NR (5G) coverage. As the UE, in response to leaving a connected mode, will acquire system information related to the 5G coverage within the cell, the UE may determine more quickly whether an 5G status indicator should be shown to an end user or not. Without the present disclosure, the UE, which had an RRC connection without an NR SCG at the end, i.e. not configured as EN-DC when releasing the UE to RRC_IDLE/RRC_INACTIVE, would indicate that it is not in NR (5G) coverage, and thus not set the 5G status indicator for the end user up to 3 hours later. This even if the UE actually is in an area where it may be configured with EN-DC and it is indicated so in system information.

Thus, according to a second aspect, there is herein provided a UE in a cell in a communications network, wherein the UE is configured to perform the method according to the first aspect.

The UE is configured to acquire system information related to 5G (NR) coverage, or capabilities, in said cell in response to leaving, or exiting, a connected mode.

In some embodiments, the UE is configured to acquire system information related to 5G capabilities of said cell in response to leaving a connected mode by reacquiring system information in response to a Radio Resource Control (RRC) connection release procedure.

In some embodiments, the UE is configured to acquire system information related to 5G capabilities of said cell in response to leaving a connected mode by acquiring system information related to 5G capabilities for a selected Public Land Mobile Network (PLMN) of said cell.

In some embodiments, the UE is configured to acquire system information related to 5G capabilities by receiving system information broadcasted in said cell.

In some embodiments, the UE is configured to determine, based on said acquired system information, whether 5G capabilities are provided in said cell.

In some embodiments, the UE is configured to determine whether 5G capabilities are provided by determining whether system information stored within the UE is still valid based on the acquired system information, wherein said acquired system information comprises SIB1. If it is determined that the system information is valid, the UE may be configured to use the stored system information to determine whether 5G capabilities are provided. If it is determined that the system information is not valid, the UE may be configured to reacquire system information, wherein the system information comprises SIB26a and/or SIB2.

In some embodiments, the UE is configured to determine whether 5G capabilities are provided by determining whether any of the NR frequencies that are indicated in SIB26a is supported for E-UTRAN-NR Dual Connectivity, EN-DC, configuration with the cell.

In some embodiments, the UE is configured to determine whether 5G capabilities are provided by determining whether an indication for 5G capabilities is present in SIB2 for the cell.

In some embodiments, the UE is further configured to indicate, to upper layers, whether the UE is within a cell that offers 5G capabilities. To indicate, to upper layers, whether the UE is within a coverage area that offers 5G capabilities may comprise providing an indication that the UE is within a cell that offers 5G capabilities. The indication may be, for example, an upperLayerlndication.

In some embodiments, the indication is provided a certain time after that the UE has left the connected mode and only if the UE at that time still is not in a connected mode.

In some embodiments, the indication is provided only if there is a change of the indication compared to the latest indication transmitted to the upper layers.

In some embodiments, it is indicated at a display of the UE whether the UE is in coverage of 5G. A 5G status indicator may indicate whether the UE is in coverage of 5G.

In some embodiments, the connected mode is RRC_CONNECTED.

In some embodiments, the cell in the communications network is an LTE cell.

In some embodiments, leaving the connected mode comprises receiving a RRCConnectionRelease message.

According to a third aspect of the present disclosure, there is provided a computer program comprising instructions, which, when executed by a processor, causes the processor to perform actions according to the method according to the first aspect.

According to a fourth aspect of the present disclosure, the object is achieved by a carrier comprising the computer program of the third aspect, wherein the carrier is one of an electronic signal, an optical signal, an electromagnetic signal, a magnetic signal, an electric signal, a radio signal, a microwave signal, or a computer-readable storage medium.

Fig. 9 illustrates a wireless network in accordance with some embodiments.

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 in Fig. 9. For simplicity, the wireless network of Fig. 9 only depicts network QQ106, network nodes QQ160 and QQ160b, and wireless devices (WDs) QQ110, QQ110b, and QQ110c. 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 node QQ160 and wireless device (WD) QQ110 are 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 network nodes QQ160 and QQ160b may be configured to perform the method of the network node according to the present disclosure. The wireless devices QQ110, QQ110b and QQ110c may be configured to perform the method as illustrated in Fig. 6.

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 standards, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave and/or ZigBee standards.

Network QQ106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTNs), packet data networks, optical networks, wide-area networks (WANs), 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 node QQ160 and WD QQ110 comprise 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-cel l/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.

In Fig. 9, network node QQ160 includes processing circuitry QQ170, device readable medium QQ180, interface QQ190, auxiliary equipment QQ184, power source QQ186, power circuitry QQ187, and antenna QQ162. Although network node QQ160 illustrated in the example wireless network of Fig. 9 may 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 node QQ160 are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, a network node may comprise multiple different physical components that make up a single illustrated component (e.g., device readable medium QQ180 may comprise multiple separate hard drives as well as multiple RAM modules).

Similarly, network node QQ160 may 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 node QQ160 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple 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 node QQ160 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device readable medium QQ180 for the different RATs) and some components may be reused (e.g., the same antenna QQ162 may be shared by the RATs). Network node QQ160 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ160, 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 node QQ160.

Processing circuitry QQ170 is 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 circuitry QQ170 may include processing information obtained by processing circuitry QQ170 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and/or performing one or more operations based on the obtained information or converted information, and as a result of said processing making a determination.

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

In some embodiments, processing circuitry QQ170 may include one or more of radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174. In some embodiments, radio frequency (RF) transceiver circuitry QQ172 and baseband processing circuitry QQ174 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry QQ172 and baseband processing circuitry QQ174 may 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 circuitry QQ170 executing instructions stored on device readable medium QQ180 or memory within processing circuitry QQ170. In alternative embodiments, some or all of the functionality may be provided by processing circuitry QQ170 without 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 circuitry QQ170 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ170 alone or to other components of network node QQ160, but are enjoyed by network node QQ160 as a whole, and/or by end users and the wireless network generally.

Device readable medium QQ180 may comprise any form of volatile or non-volatile computer readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (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 circuitry QQ170. Device readable medium QQ180 may 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 circuitry QQ170 and, utilized by network node QQ160. Device readable medium QQ180 may be used to store any calculations made by processing circuitry QQ170 and/or any data received via interface QQ190. In some embodiments, processing circuitry QQ170 and device readable medium QQ180 may be considered to be integrated.

Interface QQ190 is used in the wired or wireless communication of signalling and/or data between network node QQ160, network QQ106, and/or WDs QQ110. As illustrated, interface QQ190 comprises port(s)/terminal(s) QQ194 to send and receive data, for example to and from network QQ106 over a wired connection. Interface QQ190 also includes radio front end circuitry QQ192 that may be coupled to, or in certain embodiments a part of, antenna QQ162. Radio front end circuitry QQ192 comprises filters QQ198 and amplifiers QQ196. Radio front end circuitry QQ192 may be connected to antenna QQ162 and processing circuitry QQ170. Radio front end circuitry may be configured to condition signals communicated between antenna QQ162 and processing circuitry QQ170. Radio front end circuitry QQ192 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ192 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ198 and/or amplifiers QQ196. The radio signal may then be transmitted via antenna QQ162. Similarly, when receiving data, antenna QQ162 may collect radio signals which are then converted into digital data by radio front end circuitry QQ192. The digital data may be passed to processing circuitry QQ170. In other embodiments, the interface may comprise different components and/or different combinations of components.

In certain alternative embodiments, network node QQ160 may not include separate radio front end circuitry QQ192, instead, processing circuitry QQ170 may comprise radio front end circuitry and may be connected to antenna QQ162 without separate radio front end circuitry QQ192. Similarly, in some embodiments, all or some of RF transceiver circuitry QQ172 may be considered a part of interface QQ190. In still other embodiments, interface QQ190 may include one or more ports or terminals QQ194, radio front end circuitry QQ192, and RF transceiver circuitry QQ172, as part of a radio unit (not shown), and interface QQ190 may communicate with baseband processing circuitry QQ174, which is part of a digital unit (not shown).

Antenna QQ162 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. Antenna QQ162 may be coupled to radio front end circuitry QQ190 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In some embodiments, antenna QQ162 may 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, antenna QQ162 may be separate from network node QQ160 and may be connectable to network node QQ160 through an interface or port.

Antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may 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, antenna QQ162, interface QQ190, and/or processing circuitry QQ170 may 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 circuitry QQ187 may comprise, or be coupled to, power management circuitry and is configured to supply the components of network node QQ160 with power for performing the functionality described herein. Power circuitry QQ187 may receive power from power source QQ186. Power source QQ186 and/or power circuitry QQ187 may be configured to provide power to the various components of network node QQ160 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). Power source QQ186 may either be included in, or external to, power circuitry QQ187 and/or network node QQ160. For example, network node QQ160 may 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 circuitry QQ187. As a further example, power source QQ186 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry QQ187. 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 node QQ160 may include additional components beyond those shown in Fig. 9 that 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 node QQ160 may include user interface equipment to allow input of information into network node QQ160 and to allow output of information from network node QQ160. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for network node QQ160.

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 customerpremise 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 (loT) 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-loT) 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 device QQ110 includes antenna QQ111 , interface QQ114, processing circuitry QQ120, device readable medium QQ130, user interface equipment QQ132, auxiliary equipment QQ134, power source QQ136 and power circuitry QQ137. WD QQ110 may include multiple sets of one or more of the illustrated components for different wireless technologies supported by WD QQ110, 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 WD QQ110. Antenna QQ111 may include one or more antennas or antenna arrays, configured to send and/or receive wireless signals, and is connected to interface QQ114. In certain alternative embodiments, antenna QQ111 may be separate from WD QQ110 and be connectable to WD QQ110 through an interface or port. Antenna QQ111 , interface QQ114, and/or processing circuitry QQ120 may 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 antenna QQ111 may be considered an interface.

As illustrated, interface QQ114 comprises radio front end circuitry QQ112 and antenna QQ111. Radio front end circuitry QQ112 comprise one or more filters QQ118 and amplifiers QQ116. Radio front end circuitry QQ114 is connected to antenna QQ111 and processing circuitry QQ120, and is configured to condition signals communicated between antenna QQ111 and processing circuitry QQ120. Radio front end circuitry QQ112 may be coupled to or a part of antenna QQ111. In some embodiments, WD QQ110 may not include separate radio front end circuitry QQ112; rather, processing circuitry QQ120 may comprise radio front end circuitry and may be connected to antenna QQ111. Similarly, in some embodiments, some or all of RF transceiver circuitry QQ122 may be considered a part of interface QQ114. Radio front end circuitry QQ112 may receive digital data that is to be sent out to other network nodes or WDs via a wireless connection. Radio front end circuitry QQ112 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ118 and/or amplifiers QQ116. The radio signal may then be transmitted via antenna QQ111. Similarly, when receiving data, antenna QQ111 may collect radio signals which are then converted into digital data by radio front end circuitry QQ112. The digital data may be passed to processing circuitry QQ120. In other embodiments, the interface may comprise different components and/or different combinations of components.

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

As illustrated, processing circuitry QQ120 includes one or more of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126. In other embodiments, the processing circuitry may comprise different components and/or different combinations of components. In certain embodiments processing circuitry QQ120 of WD QQ110 may comprise a SOC. In some embodiments, RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be on separate chips or sets of chips. In alternative embodiments, part or all of baseband processing circuitry QQ124 and application processing circuitry QQ126 may be combined into one chip or set of chips, and RF transceiver circuitry QQ122 may be on a separate chip or set of chips. In still alternative embodiments, part or all of RF transceiver circuitry QQ122 and baseband processing circuitry QQ124 may be on the same chip or set of chips, and application processing circuitry QQ126 may be on a separate chip or set of chips. In yet other alternative embodiments, part or all of RF transceiver circuitry QQ122, baseband processing circuitry QQ124, and application processing circuitry QQ126 may be combined in the same chip or set of chips. In some embodiments, RF transceiver circuitry QQ122 may be a part of interface QQ114. RF transceiver circuitry QQ122 may condition RF signals for processing circuitry QQ120.

In certain embodiments, some or all of the functionality described herein as being performed by a WD may be provided by processing circuitry QQ120 executing instructions stored on device readable medium QQ130, 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 circuitry QQ120 without 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 circuitry QQ120 can be configured to perform the described functionality. The benefits provided by such functionality are not limited to processing circuitry QQ120 alone or to other components of WD QQ110, but are enjoyed by WD QQ110 as a whole, and/or by end users and the wireless network generally.

Processing circuitry QQ120 may 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 circuitry QQ120, may include processing information obtained by processing circuitry QQ120 by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored by WD QQ110, 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 medium QQ130 may 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 circuitry QQ120. Device readable medium QQ130 may 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 circuitry QQ120. In some embodiments, processing circuitry QQ120 and device readable medium QQ130 may be considered to be integrated.

User interface equipment QQ132 may provide components that allow for a human user to interact with WD QQ110. Such interaction may be of many forms, such as visual, audial, tactile, etc. User interface equipment QQ132 may be operable to produce output to the user and to allow the user to provide input to WD QQ110. The type of interaction may vary depending on the type of user interface equipment QQ132 installed in WD QQ110. For example, if WD QQ110 is a smart phone, the interaction may be via a touch screen; if WD QQ110 is 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 equipment QQ132 may include input interfaces, devices and circuits, and output interfaces, devices and circuits. User interface equipment QQ132 is configured to allow input of information into WD QQ110, and is connected to processing circuitry QQ120 to allow processing circuitry QQ120 to process the input information. User interface equipment QQ132 may 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 equipment QQ132 is also configured to allow output of information from WD QQ110, and to allow processing circuitry QQ120 to output information from WD QQ110. User interface equipment QQ132 may 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 equipment QQ132, WD QQ110 may communicate with end users and/or the wireless network, and allow them to benefit from the functionality described herein. Auxiliary equipment QQ134 is 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 equipment QQ134 may vary depending on the embodiment and/or scenario.

Power source QQ136 may, in some embodiments, be in the form of a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic devices or power cells, may also be used. WD QQ110 may further comprise power circuitry QQ137 for delivering power from power source QQ136 to the various parts of WD QQ110 which need power from power source QQ136 to carry out any functionality described or indicated herein. Power circuitry QQ137 may in certain embodiments comprise power management circuitry. Power circuitry QQ137 may additionally or alternatively be operable to receive power from an external power source; in which case WD QQ110 may 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 circuitry QQ137 may also in certain embodiments be operable to deliver power from an external power source to power source QQ136. This may be, for example, for the charging of power source QQ136. Power circuitry QQ137 may perform any formatting, converting, or other modification to the power from power source QQ136 to make the power suitable for the respective components of WD QQ110 to which power is supplied.

Fig. 10 illustrates 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). UE QQ200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including a NB-loT UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. UE QQ200, as illustrated in Fig. 10, is one example of a WD configured for communication in accordance with one or more communication standards promulgated by the 3rd Generation 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, although Fig. 10 shows a UE, the components discussed herein are equally applicable to a WD, and vice- versa.

In Fig. 10, UE QQ200 includes processing circuitry QQ201 that is operatively coupled to input/output interface QQ205, radio frequency (RF) interface QQ209, network connection interface QQ211, memory QQ215 including random access memory (RAM) QQ217, readonly memory (ROM) QQ219, and storage medium QQ221 or the like, communication subsystem QQ231 , power source QQ233, and/or any other component, or any combination thereof. Storage medium QQ221 includes operating system QQ223, application program QQ225, and data QQ227. In other embodiments, storage medium QQ221 may include other similar types of information. Certain UEs may utilize all of the components shown in Fig. 10, 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.

In Fig. 10, processing circuitry QQ201 may be configured to process computer instructions and data. Processing circuitry QQ201 may 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 circuitry QQ201 may 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 interface QQ205 may be configured to provide a communication interface to an input device, output device, or input and output device. UE QQ200 may be configured to use an output device via input/output interface QQ205. 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 UE QQ200. 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. UE QQ200 may be configured to use an input device via input/output interface QQ205 to allow a user to capture information into UE QQ200. 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.

In Fig. 10, RF interface QQ209 may be configured to provide a communication interface to RF components such as a transmitter, a receiver, and an antenna. Network connection interface QQ211 may be configured to provide a communication interface to network QQ243a. Network QQ243a may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243a may comprise a Wi-Fi network. Network connection interface QQ211 may 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 interface QQ211 may 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.

RAM QQ217 may be configured to interface via bus QQ202 to processing circuitry QQ201 to 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. ROM QQ219 may be configured to provide computer instructions or data to processing circuitry QQ201. For example, ROM QQ219 may 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 nonvolatile memory. Storage medium QQ221 may 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 medium QQ221 may be configured to include operating system QQ223, application program QQ225 such as a web browser application, a widget or gadget engine or another application, and data file QQ227. Storage medium QQ221 may store, for use by UE QQ200, any of a variety of various operating systems or combinations of operating systems.

Storage medium QQ221 may 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 minidual 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 medium QQ221 may allow UE QQ200 to access computerexecutable 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 medium QQ221 , which may comprise a device readable medium.

In Fig. 10, processing circuitry QQ201 may be configured to communicate with network QQ243b using communication subsystem QQ231. Network QQ243a and network QQ243b may be the same network or networks or different network or networks. Communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with network QQ243b. For example, communication subsystem QQ231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication such as another 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 transmitter QQ233 and/or receiver QQ235 to implement transmitter or receiver functionality, respectively, appropriate to the RAN links (e.g., frequency allocations and the like). Further, transmitter QQ233 and receiver QQ235 of each transceiver may share circuit components, software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions of communication subsystem QQ231 may 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 subsystem QQ231 may include cellular communication, Wi-Fi communication, Bluetooth communication, and GPS communication. Network QQ243b may encompass wired and/or wireless networks such as a local-area network (LAN), a wide-area network (WAN), a computer network, a wireless network, a telecommunications network, another like network or any combination thereof. For example, network QQ243b may be a cellular network, a Wi-Fi network, and/or a near-field network. Power source QQ213 may be configured to provide alternating current (AC) or direct current (DC) power to components of UE QQ200.

The features, benefits and/or functions described herein may be implemented in one of the components of UE QQ200 or partitioned across multiple components of UE QQ200. Further, the features, benefits, and/or functions described herein may be implemented in any combination of hardware, software or firmware. In one example, communication subsystem QQ231 may be configured to include any of the components described herein. Further, processing circuitry QQ201 may be configured to communicate with any of such components over bus QQ202. In another example, any of such components may be represented by program instructions stored in memory that when executed by processing circuitry QQ201 perform the corresponding functions described herein. In another example, the functionality of any of such components may be partitioned between processing circuitry QQ201 and communication subsystem QQ231. 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. 11 is a schematic block diagram illustrating a virtualization environment QQ300 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to 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 environments QQ300 hosted by one or more of hardware nodes QQ330. 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 applications QQ320 (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. Applications QQ320 are run in virtualization environment QQ300 which provides hardware QQ330 comprising processing circuitry QQ360 and memory QQ390. Memory QQ390 contains instructions QQ395 executable by processing circuitry QQ360 whereby application QQ320 is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

Virtualization environment QQ300, comprises general-purpose or special-purpose network hardware devices QQ330 comprising a set of one or more processors or processing circuitry QQ360, 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 memory QQ390-1 which may be non-persistent memory for temporarily storing instructions QQ395 or software executed by processing circuitry QQ360. Each hardware device may comprise one or more network interface controllers (NICs) QQ370, also known as network interface cards, which include physical network interface QQ380. Each hardware device may also include non-transitory, persistent, machine-readable storage media QQ390-2 having stored therein software QQ395 and/or instructions executable by processing circuitry QQ360. Software QQ395 may include any type of software including software for instantiating one or more virtualization layers QQ350 (also referred to as hypervisors), software to execute virtual machines QQ340 as well as software allowing it to execute functions, features and/or benefits described in relation with some embodiments described herein.

Virtual machines QQ340, comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ350 or hypervisor. Different embodiments of the instance of virtual appliance QQ320 may be implemented on one or more of virtual machines QQ340, and the implementations may be made in different ways.

During operation, processing circuitry QQ360 executes software QQ395 to instantiate the hypervisor or virtualization layer QQ350, which may sometimes be referred to as a virtual machine monitor (VMM). Virtualization layer QQ350 may present a virtual operating platform that appears like networking hardware to virtual machine QQ340.

As shown in Fig. 11 , hardware QQ330 may be a standalone network node with generic or specific components. Hardware QQ330 may comprise antenna QQ3225 and may implement some functions via virtualization. Alternatively, hardware QQ330 may 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) QQ3100, which, among others, oversees lifecycle management of applications QQ320.

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 machine QQ340 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, nonvirtualized machine. Each of virtual machines QQ340, and that part of hardware QQ330 that 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 machines QQ340, 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 machines QQ340 on top of hardware networking infrastructure QQ330 and corresponds to application QQ320 in Fig. 11.

In some embodiments, one or more radio units QQ3200 that each include one or more transmitters QQ3220 and one or more receivers QQ3210 may be coupled to one or more antennas QQ3225. Radio units QQ3200 may communicate directly with hardware nodes QQ330 via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station.

In some embodiments, some signalling can be effected with the use of control system QQ3230 which may alternatively be used for communication between the hardware nodes QQ330 and radio units QQ3200.

Fig. 12 illustrates a telecommunication network connected via an intermediate network to a host computer in accordance with some embodiments. With reference to Fig. 12, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ411 , such as a radio access network, and core network QQ414. Access network QQ411 comprises a plurality of base stations QQ412a, QQ412b, QQ412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area QQ413a, QQ413b, QQ413c. Each base station QQ412a, QQ412b, QQ412c is connectable to core network QQ414 over a wired or wireless connection QQ415. A first UE QQ491 located in coverage area QQ413c is configured to wirelessly connect to, or be paged by, the corresponding base station QQ412c. A second UE QQ492 in coverage area QQ413a is wirelessly connectable to the corresponding base station QQ412a. While a plurality of UEs QQ491, QQ492 are 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 station QQ412.

Telecommunication network QQ410 is itself connected to host computer QQ430, 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 computer QQ430 may 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. Connections QQ421 and QQ422 between telecommunication network QQ410 and host computer QQ430 may extend directly from core network QQ414 to host computer QQ430 or may go via an optional intermediate network QQ420. Intermediate network QQ420 may be one of, or a combination of more than one of, a public, private or hosted network; intermediate network QQ420, if any, may be a backbone network or the Internet; in particular, intermediate network QQ420 may comprise two or more sub-networks (not shown).

The communication system of Fig. 12 as a whole enables connectivity between the connected UEs QQ491 , QQ492 and host computer QQ430. The connectivity may be described as an over-the-top (OTT) connection QQ450. Host computer QQ430 and the connected UEs QQ491 , QQ492 are configured to communicate data and/or signaling via OTT connection QQ450, using access network QQ411 , core network QQ414, any intermediate network QQ420 and possible further infrastructure (not shown) as intermediaries. OTT connection QQ450 may be transparent in the sense that the participating communication devices through which OTT connection QQ450 passes are unaware of routing of uplink and downlink communications. For example, base station QQ412 may not or need not be informed about the past routing of an incoming downlink communication with data originating from host computer QQ430 to be forwarded (e.g., handed over) to a connected UE QQ491. Similarly, base station QQ412 need not be aware of the future routing of an outgoing uplink communication originating from the UE QQ491 towards the host computer QQ430.

Fig. 13 shows a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments

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 to Fig. 13. In communication system QQ500, host computer QQ510 comprises hardware QQ515 including communication interface QQ516 configured to set up and maintain a wired or wireless connection with an interface of a different communication device of communication system QQ500. Host computer QQ510 further comprises processing circuitry QQ518, which may have storage and/or processing capabilities. In particular, processing circuitry QQ518 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. Host computer QQ510 further comprises software QQ511, which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ511 includes host application QQ512. Host application QQ512 may be operable to provide a service to a remote user, such as UE QQ530 connecting via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the remote user, host application QQ512 may provide user data which is transmitted using OTT connection QQ550.

Communication system QQ500 further includes base station QQ520 provided in a telecommunication system and comprising hardware QQ525 enabling it to communicate with host computer QQ510 and with UE QQ530. Hardware QQ525 may include communication interface QQ526 for setting up and maintaining a wired or wireless connection with an interface of a different communication device of communication system QQ500, as well as radio interface QQ527 for setting up and maintaining at least wireless connection QQ570 with UE QQ530 located in a coverage area (not shown in Fig. 13) served by base station QQ520. Communication interface QQ526 may be configured to facilitate connection QQ560 to host computer QQ510. Connection QQ560 may be direct or it may pass through a core network (not shown in Fig. 13) of the telecommunication system and/or through one or more intermediate networks outside the telecommunication system. In the embodiment shown, hardware QQ525 of base station QQ520 further includes processing circuitry QQ528, 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 station QQ520 further has software QQ521 stored internally or accessible via an external connection.

Communication system QQ500 further includes UE QQ530 already referred to. Its hardware QQ535 may include radio interface QQ537 configured to set up and maintain wireless connection QQ570 with a base station serving a coverage area in which UE QQ530 is currently located. Hardware QQ535 of UE QQ530 further includes processing circuitry QQ538, which may comprise one or more programmable processors, applicationspecific integrated circuits, field programmable gate arrays or combinations of these (not shown) adapted to execute instructions. UE QQ530 further comprises software QQ531, which is stored in or accessible by UE QQ530 and executable by processing circuitry QQ538. Software QQ531 includes client application QQ532. Client application QQ532 may be operable to provide a service to a human or non-human user via UE QQ530, with the support of host computer QQ510. In host computer QQ510, an executing host application QQ512 may communicate with the executing client application QQ532 via OTT connection QQ550 terminating at UE QQ530 and host computer QQ510. In providing the service to the user, client application QQ532 may receive request data from host application QQ512 and provide user data in response to the request data. OTT connection QQ550 may transfer both the request data and the user data. Client application QQ532 may interact with the user to generate the user data that it provides.

It is noted that host computer QQ510, base station QQ520 and UE QQ530 illustrated in Fig. 13 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Fig. 12, respectively. This is to say, the inner workings of these entities may be as shown in Fig. 13 and independently, the surrounding network topology may be that of Fig. 12.

In Fig. 13, OTT connection QQ550 has been drawn abstractly to illustrate the communication between host computer QQ510 and UE QQ530 via base station QQ520, 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 UE QQ530 or from the service provider operating host computer QQ510, or both. While OTT connection QQ550 is 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 connection QQ570 between UE QQ530 and base station QQ520 is 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 UE QQ530 using OTT connection QQ550, in which wireless connection QQ570 forms the last segment. More precisely, the teachings of these embodiments may improve time to acquire the 5G capability indication and thereby provide benefits such as reduced user waiting time, better responsiveness and thus improved 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 connection QQ550 between host computer QQ510 and UE QQ530, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring OTT connection QQ550 may be implemented in software QQ511 and hardware QQ515 of host computer QQ510 or in software QQ531 and hardware QQ535 of UE QQ530, or both. In embodiments, sensors (not shown) may be deployed in or in association with communication devices through which OTT connection QQ550 passes; 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 software QQ511, QQ531 may compute or estimate the monitored quantities. The reconfiguring of OTT connection QQ550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not affect base station QQ520, and it may be unknown or imperceptible to base station QQ520. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling facilitating host computer QQ510’s measurements of throughput, propagation times, latency and the like. The measurements may be implemented in that software QQ511 and QQ531 causes messages to be transmitted, in particular empty or ‘dummy’ messages, using OTT connection QQ550 while it monitors propagation times, errors etc.

Fig. 14 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment, 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 to Figs. 12 and 13. For simplicity of the present disclosure, only drawing references to Fig. 14 will be included in this section. In step QQ610, the host computer provides user data. In substep QQ611 (which may be optional) of step QQ610, the host computer provides the user data by executing a host application. In step QQ620, the host computer initiates a transmission carrying the user data to the UE. In step QQ630 (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 step QQ640 (which may also be optional), the UE executes a client application associated with the host application executed by the host computer.

Fig. 15 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment, 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 to Figs. 12 and 13. For simplicity of the present disclosure, only drawing references to Fig. 15 will be included in this section. In step QQ710 of 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 step QQ720, 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 step QQ730 (which may be optional), the UE receives the user data carried in the transmission.

Fig. 16 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment, 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 to Figs. 12 and 13. For simplicity of the present disclosure, only drawing references to Fig. 16 will be included in this section. In step QQ810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step QQ820, the UE provides user data. In substep QQ821 (which may be optional) of step QQ820, the UE provides the user data by executing a client application. In substep QQ811 (which may be optional) of step QQ810, 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 substep QQ830 (which may be optional), transmission of the user data to the host computer. In step QQ840 of 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. 17 is a flowchart illustrating a method implemented in a communication system including a host computer, a base station and a user equipment, 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 to Figs. 12 and 13. For simplicity of the present disclosure, only drawing references to Fig. 17 will be included in this section. In step QQ910 (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 step QQ920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step QQ930 (which may be optional), the host computer receives the user data carried in the transmission initiated by the base station.

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), randomaccess 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.

Fig. 18 illustrates a virtualization apparatus in accordance with some embodiments. Fig. 18 illustrates a schematic block diagram of an apparatus 1800 in a wireless network (for example, the wireless network shown in Fig. 9). The apparatus may be implemented in a wireless device (e.g., wireless device QQ110 shown in Fig. 9). Apparatus 1800 is operable to carry out the example method described with reference to Figs. 6a, 6b and 7, and possibly any other processes or methods disclosed herein. It is also to be understood that the methods of Figs. 6a, 6b and 7 are not necessarily carried out solely by apparatus 1800. At least some operations of the method can be performed by one or more other entities.

Virtual Apparatus 1800 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), randomaccess 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 receiving unit 1802, determining unit 1804, and transmitting unit 1806 and any other suitable units of apparatus 1800 to perform corresponding functions according one or more embodiments of the present disclosure.

As illustrated in Fig. 18, apparatus 1800 includes receiving unit 1802 configured to receive, or acquire, system information related to 5G (NR) coverage, or capabilities, in said cell in response to leaving, or exiting, a connected mode. Apparatus 1800 further comprises determining unit 1804 configured to determine, based on said acquired system information, whether 5G capabilities are provided in said cell. Apparatus 1800 further comprises transmitting, or indicating, unit 1806 configured to indicate, to upper layers, whether the UE is within a cell that offers 5G capabilities.

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

Group A Embodiments

1. A method performed by a User Equipment, UE, within a cell in a communications network, the method comprising: acquiring system information related to 5G capabilities of said cell in response to leaving a connected mode.

2. The method of embodiment 1, wherein acquiring system information related to 5G capabilities of said cell in response to leaving a connected mode comprises: reacquiring system information in response to a Radio Resource Control, RRC, connection release procedure.

3. The method of any of embodiments 1 and 2, wherein acquiring system information related to 5G capabilities of said cell comprises: acquiring system information related to 5G capabilities for a selected Public Land Mobile Network, PLMN, of said cell.

4. The method of any of the previous embodiments, wherein acquiring system information related to 5G capabilities comprises: receiving system information broadcasted in said cell.

5. The method of any of the previous embodiments, wherein the method further comprises: determining, based on said acquired system information, whether 5G capabilities are provided in said cell.

6. The method of embodiment 5, wherein determining whether 5G capabilities are provided comprises: determining whether system information stored within the UE is still valid based on the acquired system information, wherein said acquired system information comprises SIB1.

7. The method of embodiment 6, wherein if it is determined that the system information is valid, the method further comprises: using the stored system information to determine whether 5G capabilities are provided.

8. The method of embodiment 6, wherein if it is determined that the system information is not valid, the method further comprises: reacquiring system information, wherein the system information comprises SIB26a and/or SIB2.

9. The method of any of embodiments 5 to 8, wherein determining whether 5G capabilities are provided comprises: determining whether any of the NR frequencies that are indicated in SIB26a is supported for E-UTRAN-NR Dual Connectivity, EN-DC, configuration with the cell.

10. The method of any of embodiments 5 to 9, wherein determining whether 5G capabilities are provided comprises: determining whether an indication for 5G capabilities is present in SIB2 for the cell.

11. The method of any of embodiments 5 to 10, wherein the method further comprises: indicating, to upper layers, whether the UE is within a cell that offers 5G capabilities.

12. The method according to embodiment 11 , wherein the step of indicating, to upper layers, whether the UE is within a coverage area that offers 5G capabilities comprises: providing an indication that the UE is within a cell that offers 5G capabilities.

13. The method according to embodiment 12, wherein the indication is an upperLayerlndication.

14. The method according to any of embodiments 12 and 13, wherein the indication is provided a certain time after that the UE has left the connected mode and only if the UE at that time still is not in a connected mode.

15. The method according to any of embodiments 12 to 14, wherein the indication is provided only if there is a change of the indication compared to the latest indication transmitted to the upper layers.

16. The method according to any of embodiments 11 to 15, wherein it is indicated at a display of the UE whether the UE is in coverage of 5G. 17. The method according to any of embodiments 11 to 16, wherein a 5G status indicator indicates whether the UE is in coverage of 5G.

18. The method of any of the previous embodiments, wherein the connected mode is RRC_CONNECTED.

19. The method of any of the previous embodiments, wherein the cell in the communications network is an LTE cell.

20. The method of any of the previous embodiments, wherein leaving the connected mode comprises: receiving a RRCConnectionRelease message.

Group B Embodiments

1. A method performed by a base station for communicating with a user equipment within a cell served by the base station, the method comprising: transmitting and/or receiving messages from the user equipment.

Group C Embodiments

1. A User Equipment, UE, in a serving cell in a communications network, the UE comprising: processing circuitry configured to perform any of the steps of any of the Group

A embodiments; and power supply circuitry configured to supply power to the wireless device.

2. A base station for communicating with a User Equipment operating in a serving cell served by the base station, 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.

2. A user equipment (UE) in a serving cell in a communications network, 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; and a battery connected to the processing circuitry and configured to supply power to the UE.

3. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a 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.

4. The communication system of the previous embodiment further including the base station.

5. The communication system of the previous 2 embodiments, further including the UE, wherein the UE is configured to communicate with the base station.

6. 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; and the UE comprises processing circuitry configured to execute a client application associated with the host application.

7. 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; and at 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.

8. The method of the previous embodiment, further comprising, at the base station, transmitting the user data.

9. 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.

10. A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to performs the of the previous 3 embodiments.

11. A communication system including a host computer comprising: processing circuitry configured to provide user data; and a 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.

12. The communication system of the previous embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

13. 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; and the UE’s processing circuitry is configured to execute a client application associated with the host application.

14. 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; and at 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.

15. The method of the previous embodiment, further comprising at the UE, receiving the user data from the base station.

16. 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.

17. The communication system of the previous embodiment, further including the UE.

18. 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.

19. The communication system of the previous 3 embodiments, wherein: the processing circuitry of the host computer is configured to execute a host application; and the UE’s processing circuitry is configured to execute a client application associated with the host application, thereby providing the user data.

20. 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; and the 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. 21. 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.

22. The method of the previous embodiment, further comprising, at the UE, providing the user data to the base station.

23. The method of the previous 2 embodiments, further comprising: at the UE, executing a client application, thereby providing the user data to be transmitted; and at the host computer, executing a host application associated with the client application.

24. The method of the previous 3 embodiments, further comprising: at the UE, executing a client application; and at 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.

25. 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.

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; 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.

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, 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.

30. The method of the previous embodiment, further comprising at the base station, receiving the user data from the UE. 31. 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).

Abbreviation Explanation

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ARQ Automatic Repeat Request

BCCH Broadcast Control Channel

BCH Broadcast Channel

CA Carrier Aggregation

CC Carrier Component

CCCH SDU Common Control Channel SDU

CDMA Code Division Multiplexing Access

CGI Cell Global Identifier

CIR Channel Impulse Response

CP Cyclic Prefix

CPICH Common Pilot Channel

CPICH Ec/No CPICH Received energy per chip divided by the power density in the band

CQI Channel Quality information

C-RNTI Cell RNTI

CSI Channel State Information

DCCH Dedicated Control Channel

DL Downlink

DM Demodulation

DMRS Demodulation Reference Signal

DRX Discontinuous Reception

DTX Discontinuous Transmission

DTCH Dedicated Traffic Channel

E-CID Enhanced Cell-ID (positioning method) E-SMLC Evolved-Serving Mobile Location Centre ECGI Evolved CGI eNB E-UTRAN NodeB ePDCCH enhanced Physical Downlink Control Channel E-SMLC evolved Serving Mobile Location Center E-UTRA Evolved UTRA

E-UTRAN Evolved UTRAN FDD Frequency Division Duplex FFS For Further Study GERAN GSM EDGE Radio Access Network gNB Base station in NR GSM Global System for Mobile communication HARQ Hybrid Automatic Repeat Request HO Handover HSPA High Speed Packet Access HRPD High Rate Packet Data LOS Line of Sight LPP LTE Positioning Protocol LTE Long-Term Evolution MAC Medium Access Control MBMS Multimedia Broadcast Multicast Services MBSFN Multimedia Broadcast multicast service Single Frequency Network MDT Minimization of Drive Tests MIB Master Information Block MME Mobility Management Entity MSC Mobile Switching Center NPDCCH Narrowband Physical Downlink Control Channel NR New Radio OCNG OFDMA Channel Noise Generator OFDM Orthogonal Frequency Division Multiplexing OFDMA Orthogonal Frequency Division Multiple Access OSS Operations Support System OTDOA Observed Time Difference of Arrival O&M Operation and Maintenance PBCH Physical Broadcast Channel P-CCPCH Primary Common Control Physical Channel

PCell Primary Cell

PCFICH Physical Control Format Indicator Channel

PDCCH Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCH Physical Downlink Shared Channel

PGW Packet Gateway

PHICH Physical Hybrid-ARQ Indicator Channel

PLMN Public Land Mobile Network

PMI Precoder Matrix Indicator

PRACH Physical Random Access Channel

PRS Positioning Reference Signal

PSS Primary Synchronization Signal

PLICCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR Reference Signal Received Power

RSRQ Reference Signal Received Quality OR Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit SFN System Frame Number SGW Serving Gateway SI System Information SIB System Information Block SNR Signal to Noise Ratio SON Self Optimized Network SS Synchronization Signal SSS Secondary Synchronization Signal TDD Time Division Duplex TDOA Time Difference of Arrival TOA Time of Arrival TSS Tertiary Synchronization Signal TTI Transmission Time Interval UE User Equipment UL Uplink UMTS Universal Mobile Telecommunication System

USIM Universal Subscriber Identity Module UTDOA Uplink Time Difference of Arrival UTRA Universal Terrestrial Radio Access UTRAN Universal Terrestrial Radio Access Network WCDMA Wide CDMA WLAN Wide Local Area Network elCIC Enhanced Inter-Cell Interference Coordination eNB Evolved Node B eMBB Enhanced Make-Before-Break E-UTRAN Evolved Universal Terrestrial Access Network EPC Evolved Packet Core network gNB 5G Node B HARQ Hybrid Automatic Repeat Request HO Handover ICIC Inter-Cell Interference Coordination LTE Long-term Evolution MAC Medium Access Control MBB Make- Before- Break MME Mobility Management Entity NCC Next Hop Chaining Counter

NG The interface/reference point between the RAN and the CN in

5G/NR.

NG-C The control plane part of NG (between a gNB and an AMF).

NG-U The user plane part of NG (between a gNB and a UPF).

NG-RAN Next Generation Radio Access Network

NR New Radio

PDCP Packet Data Convergence Protocol

PDU Protocol Data Unit

PHY Physical layer

QoS Quality of Service

RA Random Access

RACH Random Access Channel

RAN Radio Access Network

RAR Random Access Response

RLC Radio Link Control

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

Rx Receive

S1 The interface/reference point between the RAN and the CN in LTE.

S1-C The control plane part of S1 (between an eNB and a MME).

S1-LI The user plane part of S1 (between an eNB and a SGW).

SDU Service Data Unit

SGW Serving Gateway

SN Sequence Number

TS Technical Specification

Tx Transmit

UE User Equipment

UL Uplink

UPF User Plane Function

URLLC Ultra-Reliable Low-Latency Communication

X2 The interface/reference point between two eNBs.

X2AP X2 Application Protocol

Xn The interface/reference point between two gNBs.

XnAP Xn Application Protocol