WO2019158772A1

WO2019158772A1 - Amf selection for user equipment behind customer premises equipment

Info

Publication number: WO2019158772A1
Application number: PCT/EP2019/054071
Authority: WO
Inventors: Daniel Nilsson; Ralf Keller; Qian Chen; Jan Backman
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2018-02-19
Filing date: 2019-02-19
Publication date: 2019-08-22

Abstract

Embodiments herein relate to wireless communication systems and more particularly to communication of subscriber identifiers during registration. Further, embodiments herein relate to methods of operating a first network function, a first network node, and a User Equipment. Still further, embodiments herein relate to a corresponding network function, a corresponding first network node, as well as a corresponding User Equipment.

Description

AMF SELECTION FOR USER EQUIPMENT BEHIND CUSTOMER PREMISES

EQUIPMENT

TECHNICAL FIELD

The present disclosure is related to wireless communication systems and more particularly to how subscriber identifiers are communicated during registration.

BACKGROUND

The ongoing development of the fifth generation (5G) mobile communication technology continues to be a cornerstone for applying information and

communication technology. The Third Generation Partnership Project (3GPP) has and is currently identifying main functions and entities of the 5G network. Some current 3GPP solutions provide that a home router, which may include premises equipment such as customer premises equipment (CPE) and/or residential gateway (RG) may use a fixed wireline access to access a core network, such as a 5G long term evolution (LTE) network.

Current 3GPP may only support untrusted non-3GPP and 3GPP cellular access at the same time and define how to select Access and Mobility

Management Function (AMF) in such cases. Currently, the same AMF may be used for a User Equipment (UE) for both 3GPP cellular access and untrusted non-3GPP (N3GPP) access if both accesses are within the same PLMN. This has been available because any AMF can be used for an untrusted N3GPP. Then, the 3GPP AMF selection can take precedence and determine which AMF will be used for the UE. The same AMF may then be used for N3GPP.

In future releases a UE can be registered in more accesses at the same time. For instance, the UE can be attached via a Customer Premises Equipment (CPE) acting as Fixed Wireless Terminal (FWT) that is using 3GPP access as backhaul (the UE is using the CPE as relay). While the CPE may be registered in one AMF, the problem may be to determine AMF selection for the UE. One challenge may be that the RAN that does the AMF selection may not see the N1 traffic of the UE that is connected by the CPE. For example, the UE N1 messages could be carried by the CPE N1 messages and may end up in the AMF that is used by the CPE.

Referring to Figure 1 , which is a block diagram illustrating a 5G architecture, a home router called CPE/RG (another name is 5RG if it is N1 capable) may use the wireline access network to access the 5G core (5GC) network. The RG can also support wireless access via a radio access network (RAN), such as the next generation (NG) RAN to the 5G core network 5GC.

Furthermore, another supported scenario is that a 3GPP UE connected to the RG via WLAN to access the 5GC. The RG may support relaying of the 3GPP UE via the wireline access network or the NG RAN to the 5GC. By using this functionality, the 3GPP UE may be able to send and receive N1 messages transparently with an AMF in the 5GC. Since there may be a N1 connection established for the 3GPP UE, the UE can register to the network and maintain protocol data unit (PDU) sessions (mobility management (MM) and session management (SM) procedures can be supported for 3GPP UE via RG access). Also, the UE may be able to do handover of PDU sessions between 3GPP access and the RG access. In this regard, selecting the AMF for UE that is behind premises equipment may be advantageous.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings, which are incorporated herein and form part of the specification, illustrate various embodiments.

FIG. 1 is a block diagram illustrating a 5G architecture.

FIG. 2 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN) and fixed access (AGF) technologies.

FIG. 3 is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network according to some embodiments.

FIG. 4 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected. FIG. 5 is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network including the operations according to some embodiments.

FIG. 6 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected according to some embodiments.

FIG. 7 is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network including the operations corresponding to some embodiments.

FIG. 8 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected according to some embodiments.

FIG. 9 is a flowchart of operations that may be performed by a first network node according to embodiments.

FIG. 10 is a flowchart of operations that may be performed by a first

communication node according to some embodiments.

FIG. 1 1 is a flowchart of operations that may be performed by a first network function according to some embodiments.

FIG 12 is a flowchart of operations that may be performed by a first network node according to some embodiments.

FIG 13 is a block diagram illustrating elements of a UE configured to operate according to embodiments.

FIG 14 is a block diagram illustrating elements of a network node according to one or more embodiments.

FIG 15 illustrates an example wireless network.

FIG 16 illustrates one embodiment of a UE in accordance with various aspects described herein.

FIG 17 is a schematic block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized.

FIG 18, shows a communication system in accordance with an embodiment. FIG 19 illustrates example implementations in accordance with an embodiment, of the UE, base station and host computer.

DESCRIPTION OF EMBODIMENTS

Reference is now made to Figure 2, which is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN) and fixed access (AGF) technologies at a state in which a UE begins interfacing with the CPE. As illustrated, the CPE is only using one AMF for both access technologies. Embodiments herein may provide the manner in which the UE should attach via the CPE. Before the UE attaches via the CPE, the CPE has two N1 and N2 associations for CPE to AMF. This state is the starting point of the embodiments described below. The end state may be different for different embodiments disclosed herein.

Reference is now made to Figure 3, which is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network including the operations corresponding to some embodiments herein. As several of the operations defined in Figure 3 may be known, discussion thereof may be omitted for conciseness.

As illustrated, the UE sends a registration request to the new AMF via the RAN. The old AMF refers to the AMF having the UE registration prior to attaching to the CPE. The New AMF performs the AMF selection (operation 2) and the end-state will be that UE is single registered in the same AMF (New AMF) as the CPE. If UE is already registered in an AMF in the same PLMN, the UE context may be moved from the Old AMF to the New AMF. For example, in operation 4 the New AMF may send a request to the Old AMF to send UE context data and in operation 5 the Old AMF may respond to the request by sending the UE context data to the New AMF. In some embodiments, UE NAS messages can be sent inside CPE NAS connection to the New AMF.

Reference is now made to Figure 4, which is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected. As discussed herein, the New AMF corresponds to the AMF illustrated in Figure 4 and is the AMF that the CPE is registered with. As illustrated, selecting the New AMF for the UE results in an N1 connection from the UE to the New AMF via RAN1 and an N1 connection to the New AMF via RAN2. Additionally, an N2 connection is provided between the New AMF and RAN2.

Some embodiments provide that the CPE N1 connection is a transport for the UE N1. In such embodiments, when a message from the UE is received by the New AMF, the New AMF will perform the registration request as a registration request from the UE. In some embodiments, coordination with the CPE data may be provided, such as that the 3GPP location of the UE and the CPE will be the same.

The New AMF provides that there may be multiple registrations via a single N1 connection. In some embodiments, the new AMF may provide a separate state for each registration. Some embodiments provide that each message via an N1 connection contains information to which registration this message belongs to. Some embodiments provide that each N1 message relates either to the CPE or to the UE that is behind the CPE.

In some embodiments, RAN1 may communicate may the UE registration NAS messages as any other CPE NAS messages and forward them to the New AMF. The NAS messages in operations 2 and 3 of Figure 3 may be relayed by AGF between UE and New-AMF.

In operations 19b and 19c of Figure 3, if the UE is in CM_CONNECTED state on 3GPP access, then the N2 connection between RAN 2 and the Old AMF may be updated to point from the RAN2 node toward the new AMF instead. In some embodiments, all AMFs may be connected to all RAN nodes in the region. In the case where there is no connectivity between New AMF and RAN2, double registration may be provided. For example, access via CPE may be provided by another RAT than 3GPP.

Some embodiments provide that the AMF may decide to modify the NGAP UE-TNLA-binding toward RAN1 if the AMF is changed and Old AMF includes existing NGAP UE-TNLA-bindings toward RAN2 for the UE.

Some embodiments provide that the UE and CPE are registered in the same AMF and all coordination between the UE and CPE contexts can be handled locally in the AMF. The UE may only be registered in one AMF at the same time, however in some cases/deployments this may not be possible. Such cases include when the UE is registered for 3GPP access (not via CPE) via one AMF which is different than the CPE AMF and the CPE-AMF can’t serve the RAN where the UE is connected.

Some embodiments provide for a single AMF registration for UE in which the UE will not be registered in another AMF in the same PLMN after the registration procedure via CPE is completed and that the UE uses the same AMF as CPE AMF. This will have an impact on UE AMF selection in case UE is also connected via N3GPP or 3GPP access. A change of AMF might be triggered if UE is already registered in another AMF when it registers at/via CPE AMF.

Solution is to update the UE RAN node (gNB) where the UE is connected.

In such embodiments, since the New AMF performs the AMF selection, the RAN does not require any additional or specific logic.

Figure 5 is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network including the operations corresponding to some embodiments herein. Figure 6 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected according to some embodiments herein.

Referring to Figures 5 and 6, the CPE is already registered in CPE AMF and a UE is registering via the CPE. Some embodiments provide that the end-state will be that UE is single registered in a different AMF (UE AMF) than the CPE AMF. If UE is already registered in an AMF in the same PLMN, then the RAN node where CPE is connected may perform the AMF selection for the UE and create a new N2 connection to UE AMF. Some embodiments provide that the radio resource control (RRC) is provided between the UE and RAN2. In Figure 4 “New AMF” refer to the AMF where the UE is already registered. In case UE is not registered in any AMF, the CPE-RAN (RAN1 ) may select CPE-AMF.

In some embodiments, the RAN1 is aware that a UE is registering via the CPE and even though the NAS register request is received via N1 from the CPE, the RAN1 must do AMF selection for the UE. If UE is using a 5G-Global Unique Temporal Identifier (GUTI) assigned by an AMF where the UE is registered, the RAN1 node may select that AMF. Some embodiments provide that the UE provides the 5G-GUTI and an indication from UE or CPE that this is a new device connecting via the CPE.

Some embodiments provide that a new N2 connection may be established. The UE and CPE may be seen as two different devices from an AMF perspective. In some embodiments, the same connection between CPE and RAN may be used by the UE. Some embodiments provide that since RAN1 includes the logic for selecting the UE MAF, the UE may signal to RAN1 that a new UE is

registering and that AMF selection is needed. The RAN1 may differentiate N1 signalling by the UE from N1 signalling from the CPE. In some embodiments, the RAN1 node may establish multiple N2 connections for both CPE and UE when the CPE is transitioning between a connected and idle mode.

In some embodiments, the UE is only single registered in one AMF which could be different than CPE-AMF. Such embodiments may provide that there is no need for double registration support for a UE. Some embodiments provide for single AMF registration for UE in which the UE can use different AMF than CPE AMF. In some embodiments, the AGF and RAN may de-multiplex NAS signals to the correct AMF. In some embodiments, a change in RAN/AGF may be provided since the nodes must be aware of the UE registering via a CPE.

In such embodiments, since the RAN1 performs the AMF selection, the AMF does not require any additional or specific logic.

Figure 7 is data flow diagram illustrating a schematic view of a registration of a UE with a 5G core network including the operations corresponding to some embodiments herein. Figure 8 is a block diagram illustrating a schematic view of a CPE registered in an AMF via both 3GPP (RAN1 ) and fixed access (AGF) technologies at an end state after the AMF for the UE is selected according to some embodiments herein.

Referring to Figures 7 and 8, the CPE is already registered in CPE AMF and a UE is registering via the CPE. Some embodiments provide that the end-state will be that UE is single registered in a different AMF (UE AMF) than the CPE AMF. If UE is already registered in an UE-AMF in the same PLMN, the CPE- AMF, may forward NAS messages to the UE-AMF. In case UE is not registered in any AMF prior registration via CPE, the UE can register in CPE-AMF. As illustrated in Figure 7, operation 3 provides that the CPE-AMF will forward the UE NAS messages to UE-AMF. There will be a new connection between the AMFs, which may be a fixed N2 connection from UE-AMF point-of-view or a new type of connection between two AMF’s.

Some embodiments provide that the CPE-AMF be involved even though the UE is registered in another AMF. There may be complexity in coordination between UE AMF and CPE AMF. Such coordination complexities include determining the status of the connection between the AMFs when CPE goes to CMJDLE mode in CPE-AMF. In some embodiments, the UE may be logically in CM_CONNECTED mode at all time in UE AMF for the UE-behind-CPE access.

Reference is now made to Figure 9, which is a flowchart of operations that may be performed by a first network node according to some embodiments herein. Operations include receiving an initial registration request message from a user equipment (UE) that is registered with a second network function via a premises equipment that is registered with the first network function (block 900). Embodiments may include determining that the UE is registered with the second network function that is different from the first network function (block 902). In some embodiments, determining that the UE is registered with the second network function that is different from the first network function includes receiving an identification of the second network function via a message that is received from the UE via the premises equipment and determining that the received identification is different than an identification of the first network function.

Some embodiments provide that determining that the UE is registered with the second network function that is different from the first network function includes receiving a message that includes data and/or data types corresponding to the UE that are different from data and/or data types that correspond to the premises equipment.

In some embodiments, the first network function includes a first Access and Mobility Management Function (AMF) operational function and the second network function includes a second AMF operational function that is different from the first AMF operational function. Some embodiments provide that the premises equipment is a customer premises equipment (CPE) and/or a residential gateway (RG).

Operations may include, responsive to determining that the UE is registered with the second network function, registering the UE with the first network function that includes registration of the premises equipment (block 904). Some embodiments provide that, responsive to the UE being registered with the first network function, the UE and the premises equipment are both registered to the first network function.

In some embodiments, registering the UE with the first network function that includes registration of the premises equipment includes receiving context data corresponding to the UE from the second network function. In some

embodiments, operations may further include providing network communication service to the UE using the first network function to manage network traffic among a wireline access network and a mobile communication network.

Some embodiments provide that registering the UE with the first network function that includes registration of the premises equipment includes sending a network registration request message to a radio access node that is identified by the second network function as corresponding to the UE.

Some embodiments are directed to a first communication node that is adapted to perform any of the operations described herein.

Reference is now made to Figure 10, which is a flowchart of operations that may be performed by a first communication node according to some

embodiments herein. Operations may include receiving a registration request message from a User Equipment (UE) that is registered with a first Access and Mobility Management Function (AMF) operational function via a premises equipment that is registered with a second Access and Mobility Management Function (AMF) operational function (block 1000). Operations may further include sending a registration request message to the first AMF operational function to provide a network connection between the second AMF operational function and a second communication node that is provided in the registration of the UE with the first AMF operational function (block 1002). In some embodiments, the premises equipment includes a customer premises equipment (CPE) and/or a residential gateway (RG).

Some embodiments provide that the first communication node includes a first radio access node and the second communication node includes a second radio access node. In some embodiments, the first communication node includes AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the UE.

Reference is now made to Figure 11 , which is a flowchart of operations that may be performed by a first network function according to some embodiments herein. Operations may include receiving an initial registration request message from a user equipment (UE) that is registered with a second network function via a premises equipment that is connected via a first radio access node and that is registered with the first network function (block 1100). Operations may include determining that the UE is registered with the second network function that is different from the first network function (block 1102). Responsive to determining that the UE is registered with the second network function, a network connection may be generated between the first network function and the second network function (block 1104). In some embodiments, the first network function is a first Access and Mobility Management Function (AMF) operational function and the second network function is a second AMF operational function that is different from the first AMF operational function.

In some embodiments, the first network function includes AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the UE. Some embodiments provide that the UE is registered with the second AMF operational function via a second radio access node that is different from the first radio access node and the first network function is configured to forward UE messages to the second network function.

Reference is now made to Figure 12, which is a flowchart of operations that may be performed by a first network node according to some embodiments herein. Operations may include sending a registration request message, via a premises equipment and a first radio access node, to a first Access and Mobility Management Function (AMF) operational function that includes AMF selection logic (block 1200). In some embodiments, the AMF selection logic is operable to determine that the UE is registered with a second AMF operational function. In such embodiments, the premises equipment is registered with the first AMF operational function. Operations may include registering with the first AMF operational function to perform communications via the first radio access node and a second radio access node (block 1202).

EXAMPLE ELEMENTS OF UE AND NETWORK NODE:

Figure 13 is a block diagram illustrating elements of a UE 1300 (also referred to as a wireless terminal, a mobile equipment (ME), a wireless communication device, a wireless communication terminal, user equipment, a user equipment node/terminal/device, etc.) configured to operate according to embodiments disclosed herein. As shown, the UE 1300 may include at least one antenna 1307 (also referred to as antenna), and at least one transceiver circuit 1301 (also referred to as transceiver) including a transmitter and a receiver configured to provide uplink and downlink radio communications with a base station or other radio transceiver element of a radio access network. The UE 1300 may also include at least one processor circuit 1303 (also referred to as processor) coupled to the transceiver 1301 , and at least one memory circuit 1305 (also referred to as memory) coupled to the processor 1303. The memory 1305 may include computer readable program code that when executed by the processor 1303 causes the processor 1303 to perform operations according to embodiments disclosed herein for a UE. According to other embodiments, processor 1303 may be defined to include memory so that a separate memory circuit is not required. The UE 1300 may also include an interface (such as a user interface) coupled with processor 1303.

As discussed herein, operations of the UE 1300 may be performed by processor 1303 and/or transceiver 1301. Alternatively, or additionally, the UE 1300 may include modules, e.g., software and/or circuitry, that performs respective operations (e.g., operations discussed herein with respect to example embodiments of UEs). Figure 14 is a block diagram illustrating elements of a network node 1400 according to one or more embodiments disclosed herein. As shown, the network node 1400 may include at least one network interface circuit 1407 (also referred to as a network interface) configured to provide communications with other network nodes, such as one or more nodes of a access network, a core network, and/or another system node. The network node 1400 may also include at least one processor circuit 1403 (also referred to as a processor) coupled to the network interface 1407, and at least one memory circuit 1405 (also referred to as memory) coupled to the processor 1403. The memory 1405 may include computer readable program code that when executed by the processor 1403 causes the processor 1403 to perform operations according to embodiments disclosed herein for a network node. According to other embodiments, processor 1403 may be defined to include memory so that a separate memory circuit is not required.

As discussed herein, operations of the network node 1400 may be performed by processor 1403 and/or network interface 1407. For example, processor 1403 may control network interface 1407 to send communications through network interface 1407 to one or more other network nodes and/or other system nodes, and/or to receive communications through network interface 1407 from one or more other network nodes and/or other system nodes. Alternatively, or additionally, the network node 1400 may include modules, e.g., circuitry, that performs respective operations (e.g., operations discussed herein with respect to example embodiments of network nodes).

In some embodiments, some or all of the operations described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments hosted by one or more of network nodes. 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. As used herein, the term node may refer to one or more physical nodes corresponding to one or more machines, devices and/or apparatus and/or one or more virtual nodes corresponding to one or more virtual machines, devices and/or apparatus that may be partially and/or entirely virtualized.

The operations may be implemented by one or more applications (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 are run in a virtualization environment which provides hardware comprising processing circuitry and memory. Memory contains instructions executable by processing circuitry whereby application is operative to provide one or more of the features, benefits, and/or functions disclosed herein.

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

1x RTT CDMA2000 1x Radio Transmission Technology

3GPP 3rd Generation Partnership Project

5G 5th Generation

ABS Almost Blank Subframe

AKA Authentication and Key Agreement protocol

AMF Access and Mobility Management Function

AN Access Network

ARQ Automatic Repeat Request

AUSF Authentication Server Function

AWGN Additive White Gaussian Noise

BCCFI Broadcast Control Channel

BCFI 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

CN Core Network

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

CRS Cell-specific Reference Signal

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

DUT Device Under Test

EAP Extensible Authentication Protocol

E-CID Enhanced Cell-ID (positioning method)

ECIES Elliptic Curve Integrated Encryption Scheme

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 GNSS Global Navigation Satellite System

GSM Global System for Mobile communication

HARQ Hybrid Automatic Repeat Request

HO Handover

HPLMN Home PLMN

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

MBSFN ABS MBSFN Almost Blank Subframe

MDT Minimization of Drive Tests

MIB Master Information Block

MITM Man In The Middle

MME Mobility Management Entity

MSC Mobile Switching Center

NAS Non-Access Stratum

NPDCCH Narrowband Physical Downlink Control Channel

NPBCH Narrowband Physical Broadcast CHannel

NPDSCH Narrowband Physical Downlink Shared CHannel

NPRACH Narrowband Physical Random Access CHannel

NPUSCH Narrowband Physical Uplink Shared 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

PDCCFI Physical Downlink Control Channel

PDP Profile Delay Profile

PDSCFI Physical Downlink Shared Channel

PGW Packet Gateway

PH ICH Physical Flybrid-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

PUCCH Physical Uplink Control Channel

PUSCH Physical Uplink Shared Channel

RACH Random Access Channel

QAM Quadrature Amplitude Modulation

RAN Radio Access Network

RAT Radio Access Technology

RLM Radio Link Management

RNC Radio Network Controller

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RSCP Received Signal Code Power

RSRP Reference Symbol Received Power OR

Reference Signal Received Power

RSRQ Reference Signal Received Quality OR

Reference Symbol Received Quality

RSSI Received Signal Strength Indicator

RSTD Reference Signal Time Difference

SCH Synchronization Channel

SCell Secondary Cell

SDU Service Data Unit SEAF Security Anchor Function

SFN System Frame Number

SGW Serving Gateway

SI System Information

SIB System Information Block

SMC Security Mode Command

SNR Signal to Noise Ratio

SON Self Optimized Network

SPDCCH Short Physical Downlink Control Channel

SPDSCH Short Physical Downlink Shared Channel

SPUCCH Short Physical Uplink Control Channel

SPUSCH Short Physical Uplink Shared Channel

SS Synchronization Signal

SSS Secondary Synchronization Signal

SUCI Subscription Concealed Identifier

SUPI Subscription Permanent Identifier

TDD Time Division Duplex

TDOA Time Difference of Arrival

TOA Time of Arrival

TSS Tertiary Synchronization Signal

TTI Transmission Time Interval

UE User Equipment

UICC Universal Integrated Circuit Card

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

VPLMN Visited PLMN

WCDMA Wide CDMA

WLAN Wide Local Area Network FURTHER DEFINITIONS AND EMBODIMENTS

In this disclosure a receiving node and a transmitting node is referred to. In the embodiments in one example the transmitting node can be a UE and the receiving node can be a network node. In another example the transmitting node can be a network node and the receiving node can be a UE. In yet another example the transmitting and receiving node can be involved in direct device to device communication, that is both can be considered UEs. Examples of device to device communication are proximity service (ProSe), ProSe direct discovery, ProSe direct communication, V2X (where X can denote V, I or P e.g. V2V, V2I, V2P etc) etc.

A network node is a more general term and can correspond to any type of radio network node or any network node, which communicates with a UE and/or with another network node. Examples of network nodes are NodeB, base station (BS), multi-standard radio (MSR) radio node such as MSR BS, eNodeB, gNodeB. MeNB, SeNB, network controller, radio network controller (RNC), base station controller (BSC), road side unit (RSU), relay, donor node controlling relay, base transceiver station (BTS), access point (AP), transmission points, transmission nodes, RRU, RRH, nodes in distributed antenna system (DAS), core network node (e.g. MSC, MME etc), O&M, OSS, SON, positioning node (e.g. E-SMLC) etc.

Another example of a node could be user equipment, this is a non-limiting term user equipment (UE) and it refers to any type of wireless device

communicating with a network node and/or with another UE in a cellular or mobile communication system. Examples of UE are target device, device to device (D2D) UE, V2X UE, ProSe UE, machine type UE or UE capable of machine to machine (M2M) communication, PDA, iPAD, Tablet, mobile terminals, smart phone, laptop embedded equipped (LEE), laptop mounted equipment (LME),

USB dongles etc.

The term radio access technology, or RAT, may refer to any RAT e.g.

UTRA, E-UTRA, narrow band internet of things (NB-loT), WiFi, Bluetooth, next generation RAT (NR), 4G, 5G, etc. Any of the first and the second nodes may be capable of supporting a single or multiple RATs. The term signal used herein can be any physical signal or physical channel. Examples of downlink physical signals are reference signal such as PSS, SSS, CRS, PRS, CSI-RS, DMRS, NRS, NPSS, NSSS, SS, MBSFN RS etc. Examples of uplink physical signals are reference signal such as SRS, DMRS etc. The term physical channel (e.g., in the context of channel reception) used herein is also called as‘channel. The physical channel carries higher layer information (e.g. RRC, logical control channel etc). Examples of downlink physical channels are PBCH, NPBCH, PDCCH, PDSCH, sPDSCH, MPDCCH, NPDCCH, NPDSCH, E- PDCCH etc. Examples of uplink physical channels are sPUCCH. sPUSCH, PUSCH, PUCCH, NPUSCH, PRACH, NPRACH etc.

The term time resource used herein may correspond to any type of physical resource or radio resource expressed in terms of length of time and/or frequency. Signals are transmitted or received by a radio node over a time resource.

Examples of time resources are: symbol, time slot, subframe, radio frame, TTI, interleaving time, etc.

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 Figure 15. For simplicity, the wireless network of Figure 15 only depicts network QQ106, network nodes QQ160 and QQ160b, and WDs QQ1 10, QQ1 10b, and QQ1 10c. 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) QQ1 10 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 wireless network may comprise and/or interface with any type of communication, telecommunication, data, cellular, and/or radio network or other similar type of system. In some embodiments, the wireless network may be configured to operate according to specific standards or other types of predefined rules or procedures. Thus, particular embodiments of the wireless network may implement communication standards, such as Global System for Mobile

Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless local area network (WLAN) standards, such as the IEEE 802.11 standards; and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z- Wave and/or ZigBee standards.

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-cell/multicast coordination entities (MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SON nodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As another example, a network node may be a virtual network node as described in more detail below. More generally, however, network nodes may represent any suitable device (or group of devices) capable, configured, arranged, and/or operable to enable and/or provide a wireless device with access to the wireless network or to provide some service to a wireless device that has accessed the wireless network.

In Figure QQ1 , 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 Figure QQ1 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 00170. 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 GFIz and 66 GFIz. 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 Figure QQ1 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) and mobile equipment (ME). Communicating wirelessly may involve transmitting and/or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and/or other types of signals suitable for conveying information through air. In some embodiments, a WD may be configured to transmit and/or receive information without direct human interaction. For instance, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the network. Examples of a WD include, but are not limited to, a smart phone, a mobile phone, a cell phone, a voice over IP (VoIP) phone, a wireless local loop phone, a desktop computer, a personal digital assistant (PDA), a wireless cameras, a gaming console or device, a music storage device, a playback appliance, a wearable terminal device, a wireless endpoint, a mobile station, a tablet, a laptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment (LME), a smart device, a wireless customer-premise equipment (CPE) a vehicle-mounted wireless terminal device, etc.. A WD may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, vehicle-to-vehicle (V2V), vehicle-to- infrastructure (V2I), vehicle-to-everything (V2X) and may in this case be referred to as a D2D communication device. As yet another specific example, in an Internet of Things (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 QQ1 18 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 QQ1 10 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.

Figure QQ2 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 QQ2200 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 Figure QQ2, 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 Figure QQ2 is a UE, the components discussed herein are equally applicable to a WD, and vice-versa.

In Figure QQ2, 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, read-only 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 Figure QQ2, 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 Figure QQ2, 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 Figure QQ2, 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 non- volatile 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 (FID-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as a subscriber identity module or a removable user identity (SIM/RUIM) module, other memory, or any combination thereof. Storage medium QQ221 may allow UE QQ200 to access computer- executable instructions, application programs or the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied in storage medium QQ221 , which may comprise a device readable medium.

In Figure 16, 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. QQ2, 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.

Figure 17 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 Figure 17, 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, non-virtualized 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 Figure 17.

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.

With reference to Figure 18, in accordance with an embodiment, a communication system includes telecommunication network QQ410, such as a 3GPP-type cellular network, which comprises access network QQ41 1 , such as a radio access network, and core network QQ414. Access network QQ41 1 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 Figure 18 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 QQ41 1 , 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.

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 Figure 19. 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 QQ51 1 , which is stored in or accessible by host computer QQ510 and executable by processing circuitry QQ518. Software QQ51 1 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 Figure 19) 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 Figure 19) 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, application-specific 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 Figure 19 may be similar or identical to host computer QQ430, one of base stations QQ412a, QQ412b, QQ412c and one of UEs QQ491 , QQ492 of Figure 18, respectively. This is to say, the inner workings of these entities may be as shown in Figure 19 and independently, the surrounding network topology may be that of Figure 18.

In Figure 19, 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).

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.

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.

LISTING OF EXAMPLE EMBODIMENTS

1. A method of operating a first network function or function instance, the method comprising;

receiving an initial registration request message from a user equipment (UE) that is registered with a second network function via a premises equipment that is registered with the first network function;

determining that the UE is registered with the second network function that is different from the first network function; and

responsive to determining that the UE is registered with the second network function, registering the UE with the first network function that includes registration of the premises equipment,

wherein, responsive to the UE being registered with the first network function, the UE and the premises equipment are registered to the first network function.

2. The method of Embodiment 1 ,

wherein the first network function comprises a first Access and Mobility Management Function (AMF) operational function, and

wherein the second network function comprises a second AMF operational function that is different from the first AMF operational function.

3. The method of any of Embodiments 1 or 2, wherein the premises equipment comprises a customer premises equipment (CPE) and/or a residential gateway (RG). 4. The method of any of Embodiments 1 to 3, wherein determining that the UE is registered with the second network function that is different from the first network function comprises:

receiving an identification of the second network function via a message that is received from the UE via the premises equipment; and

determining that the received identification is different than an identification of the first network function.

5. The method of any of Embodiments 1 to 4, wherein registering the UE with the first network function that includes registration of the premises equipment comprises receiving context data corresponding to the UE from the second network function, further comprising providing network communication service to the UE using the first network function to manage network traffic among a wireline access network and a mobile communication network.

6. The method of any of embodiments 1 to 5, wherein registering the UE with the first network function that includes registration of the premises equipment comprises sending a network registration request message to a radio access node that is identified by the second network function as corresponding to the UE.

7. The method of any of Embodiments 1 to 6, wherein determining that the UE is registered with the second network function that is different from the first network function comprises receiving a message that includes data and/or data types corresponding to the UE that are different from data and/or data types that correspond to the premises equipment.

8. A first communication node, wherein the first communication node is adapted to perform according to any of Embodiments 1 -7. 9. A first communication node comprising:

a network interface configured to communicate with a second network function and a user equipment, UE, via an access network; and

a processor coupled to the network interface and configured to perform operations comprising:

10. The first communication node of Embodiment 9, wherein the processor is adapted to perform operations according to any of Embodiments 2- 7.

11. A first communication node, wherein the first communication node includes respective modules adapted to perform according to any of

Embodiments 1 -7.

12. A method of operating a first communication node, the method comprising: receiving a registration request message from a User Equipment (UE) that is registered with a first Access and Mobility Management Function (AMF) operational function via a premises equipment that is registered with a second Access and Mobility Management Function (AMF) operational function; and

sending a registration request message to the first AMF operational function to provide a network connection between the second AMF operational function and a second communication node that is provided in the registration of the UE with the first AMF operational function.

13. The method of Embodiment 12, wherein the premises equipment comprises a customer premises equipment (CPE) and/or a residential gateway (RG).

14. The method of any of Embodiments 12 to 13, wherein the first communication node comprises a first radio access node and the second communication node comprises a second radio access node.

15. The method of any of Embodiments 12-14, wherein the first

communication node comprises AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the

UE.

16. A first communication node comprising:

receiving a registration request message from the UE that is registered with a first Access and Mobility Management Function (AMF) operational function via a premises equipment that is registered with a second Access and Mobility Management Function (AMF) operational function; and sending a registration request message to the first AMF operational function to provide a network connection between the second AMF operational function and a second communication node that is provided in the registration of the UE with the first AMF operational function.

17. The first communication node of Embodiment 18, wherein the processor is adapted to perform operations according to any of Embodiments 13- 15.

18. A first communication node, wherein the first communication node includes respective modules adapted to perform according to any of

Embodiments 13-15.

19. A method of operating a first network function, the method comprising;

receiving an initial registration request message from a user equipment (UE) that is registered with a second network function via a premises equipment that is connected via a first radio access node and that is registered with the first network function; determining that the UE is registered with the second network function that is different from the first network function; and responsive to determining that the UE is registered with the second network function, generating a network connection between the first network function and the second network function, wherein the first network function comprises a first Access and Mobility Management Function (AMF) operational function, and wherein the second network function comprises a second AMF operational function that is different from the first AMF operational function.

20. The method of Embodiment 19, wherein the first network function comprises AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the UE.

21. The method of any of Embodiments 19-20, wherein the UE is registered with the second AMF operational function via a second radio access node that is different from the first radio access node, and

wherein the first network function is configured to forward UE messages to the second network function.

22. A first communication node comprising:

a network interface configured to communicate with a second network function and a user equipment, UE, via an access network; and a processor coupled to the network interface and configured to perform operations comprising:

receiving an initial registration request message from a user equipment (UE) that is registered with a second network function via a premises equipment that is connected via a first radio access node and that is registered with the first network function;

determining that the UE is registered with the second network function that is different from the first network function; and responsive to determining that the UE is registered with the second network function, generating a network connection between the first network function and the second network function,

wherein the first network function comprises a first Access and Mobility Management Function (AMF) operational function, and wherein the second network function comprises a second AMF operational function that is different from the first AMF operational function.

23. The first communication node of Embodiment 22, wherein the processor is adapted to perform operations according to any of Embodiments 19- 21 .

24. A first communication node, wherein the first communication node includes respective modules adapted to perform according to any of

Embodiments 19-21.

25. A method of operating a user equipment, UE, the method comprising: sending a registration request message, via a premises equipment and a first radio access node, to a first Access and Mobility Management Function (AMF) operational function that includes AMF selection logic that determines that the UE is registered with a second AMF operational function, the premises equipment being registered with the first AMF operational function; and

registering with the first AMF operational function to perform

communications via the first radio access node and a second radio access node.

26. A user equipment, UE, adapted to perform according to Embodiment 25.

27. A user equipment, UE, comprising:

a transceiver configured to communicate with a first network function via a radio access network; and

a processor coupled to the transceiver and configured to perform

operations comprising: sending a registration request message, via a premises equipment and a first radio access node, to a first Access and Mobility Management Function (AMF) operational function that includes AMF selection logic that determines that the UE is registered with a second AMF operational function, the premises equipment being registered with the first AMF operational function; and

registering with the first AMF operational function to perform communications via the first radio access node and a second radio access node.

28. The UE of Embodiment 27, wherein the processor is adapted to perform operations according to Embodiment 25.

29. A user equipment, UE, including respective modules adapted to perform operations according to Embodiment 25.

In the specification, there have been disclosed embodiments of the inventive concepts and, although specific terms are employed, they are used in a generic and descriptive sense only and not for purposes of limitation. The following claim is provided to ensure that the present application meets all statutory requirements as a priority application in all jurisdictions and shall not be construed as setting forth the scope of the present inventive concepts.

1 . Systems/Methods/Apparatus substantially as described herein.

Claims

1. A method of operating a first network function or function instance (1400), the method comprising;

receiving (900) an initial registration request message from a user equipment (1300), UE, that is registered with a second network function via a premises equipment that is registered with the first network function;

determining (902) that the UE (1300) is registered with the second network function that is different from the first network function; and

responsive to determining that the UE (1300) is registered with the second network function, registering (904) the UE (1300) with the first network function that includes registration of the premises equipment,

wherein, responsive to the UE (1300) being registered with the first network function, the UE (1300) and the premises equipment are registered to the first network function.

2. The method of Claim 1 , wherein the first network function comprises a first Access and Mobility Management Function, AMF, operational function, and wherein the second network function comprises a second AMF operational function that is different from the first AMF operational function.

3. The method of any of Claims 1 or 2, wherein the premises equipment comprises a customer premises equipment, CPE, and/or a residential gateway, RG.

4. The method of any of Claims 1 to 3, wherein determining that the UE is registered with the second network function that is different from the first network function comprises: receiving an identification of the second network function via a message that is received from the UE via the premises equipment; and

5. The method of any of Claims 1 to 4, wherein registering the UE with the first network function that includes registration of the premises equipment comprises receiving context data corresponding to the UE from the second network function, further comprising providing network communication service to the UE using the first network function to manage network traffic among a wireline access network and a mobile communication network.

6. The method of any of claims 1 to 5, wherein registering the UE with the first network function that includes registration of the premises equipment comprises sending a network registration request message to a radio access node that is identified by the second network function as corresponding to the UE.

7. The method of any of Claims 1 to 6, wherein determining that the UE is registered with the second network function that is different from the first network function comprises receiving a message that includes data and/or data types corresponding to the UE that are different from data and/or data types that correspond to the premises equipment.

8. A first communication node (1400), wherein the first communication node is adapted to perform the method according to any of Claims 1 -7.

9. A first communication node (1400) comprising: a network interface (1407) configured to communicate with a second network function and a user equipment (1300), UE, via an access network; and a processor (1403) coupled to the network interface (1407) and configured to perform operations comprising:

receiving (900) an initial registration request message from a UE (1300) that is registered with a second network function via a premises equipment that is registered with the first network function;

responsive to determining that the UE (1300) is registered with the second network function, registering (904) the UE (1300) with the first network function that includes registration of the premises equipment, wherein, responsive to the UE (1300) being registered with the first network function, the UE (1300) and the premises equipment are registered to the first network function.

10. The first communication node of Claim 9, wherein the processor is adapted to perform the method according to any of Claims 2-7.

11. A first communication node, wherein the first communication node includes respective modules adapted to perform according to any of Claims 1 -7.

12. A method of operating a first communication node (1400), the method comprising:

receiving (1000) a registration request message from a User Equipment

(1300), UE, that is registered with a first Access and Mobility Management Function, AMF, operational function via a premises equipment that is registered with a second AMF operational function; and sending (1002) a registration request message to the first AMF operational function to provide a network connection between the second AMF operational function and a second communication node that is provided in the registration of the UE with the first AMF operational function.

13. The method of Claim 12, wherein the premises equipment comprises a customer premises equipment, CPE, and/or a residential gateway, RG.

14. The method of any of Claims 12 to 13, wherein the first communication node comprises a first radio access node and the second communication node comprises a second radio access node.

15. The method of any of Claims 12-14, wherein the first communication node comprises AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the UE.

16. A first communication node (1400) comprising:

a network interface configured to communicate with a second network function and a user equipment (1300), UE, via an access network; and

a processor (1403) coupled to the network interface (1407) and configured to perform operations comprising:

receiving (1000) a registration request message from the UE that is registered with a first Access and Mobility Management Function, AMF, operational function via a premises equipment that is registered with a second AMF operational function; and

sending (1002) a registration request message to the first AMF operational function to provide a network connection between the second AMF operational function and a second communication node that is provided in the registration of the UE with the first AMF operational function.

17. The first communication node of Claim 16, wherein the processor is adapted to perform the method according to any of Claims 13-15.

18. A first communication node, wherein the first communication node includes respective modules adapted to perform the method according to any of Claims 12-15.

19. A method of operating a first network function, the method comprising; receiving (1100) an initial registration request message from a user equipment, UE, that is registered with a second network function via a premises equipment that is connected via a first radio access node and that is registered with the first network function;

determining (1102) that the UE is registered with the second network function that is different from the first network function; and

responsive to determining that the UE is registered with the second network function, generating (1104) a network connection between the first network function and the second network function,

wherein the first network function comprises a first Access and Mobility Management Function, AMF, operational function, and wherein the second network function comprises a second AMF operational function that is different from the first AMF operational function.

20. The method of Claim 19, wherein the first network function comprises AMF operational function selection logic that selects which of the first and the second AMF operational functions registers the UE.

21. The method of any of Claims 19-20, wherein the UE is registered with the second AMF operational function via a second radio access node that is different from the first radio access node, and

22. A first communication node (1400) comprising:

a network interface (1407) configured to communicate with a second network function and a user equipment (1300), UE, via an access network; and a processor (1403) coupled to the network interface (1407) and configured to perform operations comprising:

receiving (1100) an initial registration request message from a UE (1300) that is registered with a second network function via a premises equipment that is connected via a first radio access node and that is registered with the first network function;

determining (1102) that the UE (1300) is registered with the second network function that is different from the first network function; and

responsive to determining that the UE (1300) is registered with the second network function, generating (1104) a network connection between the first network function and the second network function,

wherein the first network function comprises a first Access and Mobility Management Function, AMF, operational function, and

23. The first communication node of Claim 22, wherein the processor is adapted to perform the method according to any of Claims 19-21.

24. A first communication node, wherein the first communication node includes respective modules adapted to perform the method according to any of Claims 19-21.

25. A method of operating a user equipment (1300), UE, the method comprising:

sending (1200) a registration request message, via a premises equipment and a first radio access node, to a first Access and Mobility Management

Function, AMF, operational function that includes AMF selection logic that determines that the UE is registered with a second AMF operational function, the premises equipment being registered with the first AMF operational function; and registering (1202) with the first AMF operational function to perform communications via the first radio access node and a second radio access node.

26. A user equipment (1300), UE, adapted to perform the method according to Claim 25.

27. A user equipment (1300), UE, comprising:

a transceiver (1301 ) configured to communicate with a first network function via a radio access network; and

a processor (1303) coupled to the transceiver and configured to perform operations comprising:

28. The UE (1300) of Claim 27, wherein the processor (1303) is adapted rm the method according to Claim 25.

29. A user equipment (1300), UE, including respective modules adapted rm the method according to Claim 25.