Methods and apparatuses for storage of user equipment contexts in a radio access network for inactive user equipments

Methods and Apparatuses for Storage of User Equipment Contexts in a Radio Access Network for Inactive User Equipments

Technical Field

The present disclosure relates to a cellular communications network and, in particular, to storage of User Equipment device (UE) contexts in a Radio Access Network (RAN) for inactive UEs.

Background

WO 2016/178605 introduced the concept of storing the User Equipment (UE) Radio Access Network (RAN) context in the UE and in the RAN when the UE is in a not connected state and then re-using the context when the UE returns to connected state.

In a typical wireless, cellular, or radio communications network, wireless devices, also known as mobile stations, terminals, and/or UEs, communicate via a RAN with one or more Core Networks (CNs). The RAN covers a geographical area which is divided into cells, with each cell being served by a base station, e.g. a Radio Base Station (RBS), or network node, which in some networks may also be called, for example, a “Node B” or an “enhanced or evolved Node B (eNB).” A cell is a geographical area where radio coverage is provided by the RBS at a base station site or an antenna site in case the antenna and the RBS are not collocated. One RBS may serve one or more cells.

A Universal Mobile Telecommunications System (UMTS) is a third generation mobile communication system, which evolved from Second Generation (2G) Global System for Mobile Communications (GSM). The UMTS Universal Terrestrial RAN (UTRAN) is essentially a RAN using Wideband Code Division Multiple Access (WCDMA) and/or High-Speed Packet Access (HSPA) to communicate with a UE. In a forum known as the Third Generation Partnership Project (3GPP), telecommunications suppliers propose and agree upon standards for third generation networks and UTRAN specifically, and investigate enhanced data rate and radio capacity. In some versions of the RAN, as e.g. in UMTS, several base stations may be connected, e.g. by landlines or microwave, to a controller node, such as a Radio Network Controller (RNC) or a Base Station Controller (BSC), which supervises and coordinates various activities of the plural base stations connected thereto. The RNCs are typically connected to one or more CNs.

Specifications for the Evolved Packet System (EPS) have been completed within 3GPP and this work continues in the coming 3GPP releases. The EPS comprises the Evolved UTRAN (E-UTRAN), also known as the Long Term Evolution (LTE) radio access, and the Evolved Packet Core (EPC), also known as the System Architecture Evolution (SAE) CN. E-UTRAN/LTE is a variant of a 3GPP radio access technology wherein the RBS nodes are directly connected to the EPC CN rather than to RNCs. In general, in EUTRAN/LTE the functions of an RNC are distributed between the RBS nodes, e.g. eNBs in LTE, and the CN. As such, the RAN of an EPS has an essentially flat architecture comprising RBS nodes without reporting to RNCs.

Figure 1 illustrates the current standard EPC architecture of a wireless communications network. The EPC architecture, including all of its components and interfaces, is further described and defined in 3GPP Technical Specification (TS) 23.401 V12.0.0. The current standard E-UTRAN architecture is further described and defined in, e.g., 3GPP TS 36.300 V12.0.0.

Figure 2 illustrates the radio interface user and control plane protocol for EUTRAN. The E-UTRAN radio interface user and control plane protocol consists of the following protocol layers and main functionalities.

Radio Resource Control (RRC) (Control Plane Only)

The main function for control plane: broadcast of system information for both NonAccess Stratum (NAS) and Access Stratum (AS); paging; RRC connection handling; allocation of temporary identifiers for the UE; configuration of signaling radio bearer(s) for RRC connection; handling of radio bearers; Quality of Service (QoS) management functions; security functions including key management; mobility functions (including UE measurement reporting and control of the reporting, handover, UE cell selection and reselection, and control of cell selection and reselection); and NAS direct message transfer to/from the UE.

Packet Data Convergence Protocol (PDCP)

There exists one PDCP entity for each radio bearer for the UE. PDCP is used for both control plane, i.e. RRC, and for user plane, i.e. user data received via General Packet Radio System (GPRS) Tunneling Protocol User Plane (GTP-U) signaling. The main function for the control plane is ciphering/deciphering and integrity protection. Main functions for the user plane are: ciphering/deciphering; header compression and decompression using Robust Header Compression (ROHC); and in-sequence delivery, duplicate detection, and retransmission.

Radio Link Control (RLC)

The RLC layer provides services for the PDCP layer and there exists one RLC entity for each radio bearer for the UE. Main functions for both the control and user plane are: segmentation/concatenation; retransmission handling; duplicate detection; and insequence delivery to higher layers.

Medium Access Control (MAC)

The MAC provides services to the RLC layer in the form of logical channels and performs mapping between these logical channels and transport channels. Main functions are: uplink and downlink scheduling, scheduling information reporting, Hybrid Automatic Repeat Request (HARQ) retransmissions, and multiplexing/de-multiplexing data across multiple component carriers for carrier aggregation.

Physical Layer (PHY)

The PHY provides services to the MAC layer in the form of transport channels and handles mapping of transport channels to physical channels.

Information relating to one or more of these protocol layers and their functionality is hereinafter referred to as RAN context information. In other words, the configuration of these protocol layers for a particular wireless device would be the RAN context information of this particular wireless device in the wireless communications network. The configuration of these protocol layers are typically done by the RRC layer via RRC configuration messages. One example of configuration specific information is different identifiers on the different protocol layers for the wireless device. However, it should also be noted that the RAN context information may further include additional information, such as, for example, radio access capabilities of the wireless device, previous mobility or traffic history of the wireless device, etc.

For instance, the RAN context information of a wireless device may comprise RRC protocol information of the wireless device. In some embodiments, the RAN context information may comprise one or more identifiers used for the wireless device in the wireless communications network. Examples of such identifiers may comprise a Cell Radio Network Temporary Identifier (C-RNTI), a SAE Temporary Mobile Subscriber Identity (S-TMSI), a Globally Unique Temporary Identity (GUTI), etc. In some embodiments, the RAN context information may comprise configuration parameters of the wireless device for a communications protocol on a lower layer than the RRC protocol layer. Examples of such configuration parameters may comprise RLC configuration parameters, e.g. RLC Acknowledged Mode (RLC-AM) or RLC Unacknowledged Mode (RLC-UM), or mapping parameters between Resource Blocks (RBs) and logical channels. In some embodiments, the RAN context information may comprise radio access capability information of the wireless device. Examples of such radio access capabilities may comprise some or all of the capabilities defined in the standard 3GPP 36.331, “UEEUTRA-Capability,” such as, e.g., which release the wireless device supports, which wireless device category the wireless device belongs to, and which frequency bands and Radio Access Technologies (RATs) the wireless device supports. In some embodiments, the RAN context information may comprise information related to one or more ongoing radio bearers of the wireless device. In some embodiments, the RAN context information may comprise one or more security keys and/or sequence numbers associated with the wireless device. Examples of such security keys may be an eNB Key (KeNB), a KRRCint (i.e., the Security Key used for integrity protection of RRC messages), a KRRCenc (i.e., the Security Key used for encryption of RRC messages), a KUPenc (i.e., the Security Key used for encryption of user plane data), etc. Examples of such sequence numbers may be a PDCP sequence number, a COUNT number, etc.

The above described functionality of the network node (eNB) may be deployed in different ways. In one example, all the protocol layers and related functionality is deployed in the same physical node including the antenna. One example of this is a so-called pico or femto eNB. Another example is a so-called Main-Remote split. In this case, the eNB is divided into a main unit and a remote unit. The main unit may also be referred to as a Digital Unit (DU) and the remote unit may also be referred to as a Remote Radio Unit (RRU). In this case, the main unit comprises all the protocol layers except the lower parts of the PHY that are instead placed in the remote unit. In a further example, the remote unit and the antenna are co-located. This may be referred to as an Antenna Integrated Radio (AIR) system.

Handling of Inactive UEs in the RAN

In the contribution R3-161290 to the 3GPP RAN 3 WG meeting in May 2016 there is a proposal to introduce a RAN controlled inactive state where the CN/RAN connection is maintained as described below. The RAN-controlled inactive state (which is also referred to herein as a RAN-based inactive state) is to be distinguished from the conventional IDLE state in which the UE is only known at the CN level and does not have a context in the RAN. The RAN controlled inactive state is also referred to herein as a RAN based inactive state.

It has been proposed that UEs in the RAN controlled inactive state should incur minimum signaling and resource costs in the RAN/CN making it possible to maximize the number of UEs utilizing, and benefiting from, this state. It has also been proposed that UEs in the RAN controlled inactive state perform mobility within an area without notifying the network. It has also been proposed that the RAN can trigger paging of UEs which are in the RAN controlled inactive state.

If a RAN controlled inactive mode is supported, this means that the transition from inactive to active state in the RAN will be transparent to the CN.

- In the downlink this means, for the default solution, that downlink packets will be sent to the last node where the UE was connected (anchor RAN node). That node will then be responsible for initiated UE paging within the paging area that the UE is allowed to move in without notifying the network.

- In the uplink it means that the UE needs to perform a RAN level procedure to transition to active state to transmit data. In case the UE has moved to a different RAN node this RAN node will most likely need to fetch the UE context from another RAN node, and if needed notify the CN that the UE has moved to a new node.

- If the UE moves outside the paging area it would need to notify the network about the mobility so that the paging area can be updated. This procedure could trigger a RAN node relocation or the RAN node can be kept.

The following RAN functions are envisioned:

- Paging for downlink data

- Context fetch to handle moving UEs (may be similar to an existing LTE procedure)

- Mobility updating (it is possible this could use a similar mechanism as context fetch)

In order for these mechanisms to be enabled, the UE needs to be allocated a RAN identifier uniquely identifying the UE context in the RAN.

In case there is any failure where it is not possible to retrieve the UE RAN context, it is assumed that the RAN context can be rebuilt as it would happen in the case of a new connection setup.

Figures 3 and 4 illustrate the basic principles.

WO2013110543 discloses a network element comprising a signal processor supporting communications between a subscriber unit (UE) and a core network (CN). The signal processor is arranged to: receive a first update request message (location or routing area) from the subscriber unit; forward the first update request message to the core network; receive from the CN a first update accept (or response) message; store at least a part of the accept message content; forward the first update response message to the subscriber unit; receive a second update request from the subscriber unit; create a second update accept (or response) message using the at least part of the stored content; and respond to the subscriber unit second update accept (or response) message direct.

EP 2 876 948 relates to idle mode mobility procedures in a femto architecture wherein a plurality of small cells constitute a preconfigured cluster of small cells. The idle mode mobility procedure comprises HNBAP messaging for UE registering and NAS messaging for location updating procedures. The small size of the cells and the corresponding higher mobility can lead to more frequent HNBAP and NAS signalling procedures. Therefore the application proposes a mechanism whereby the core network location update procedure is supplemented by a local, i.e. femto-cell-based location update procedure, which has potentially a higher frequency than the core network location update procedure. The HNB-gateway forward location update requests from the UE only then to the core network when the core network periodic timer has been expired, the UE moves to the femtocell or the mobile station was turned on.

WO2009139675 discloses a method of determining whether a mobile station (MS) has left a femto cell while in idle mode, and deregistering the MS from a Generic Access Network, GAN, upon making this determination. A Femto Cell Customer Premises Equipment, Femto Cell CPE, may deregister the MS if the MS fails to perform a periodic location update at a time ordered by the Femto Cell CPE. The Femto Cell CPE may also deregister the MS if the MS fails to respond to a paging attempt originated by either the Femto Cell CPE or a GAN Controller, GANC. The Femto Cell CPE may also deregister the MS if the GANC instructs all of the MSs in the femto cell to perform attach and detach procedures, and the MS sends a detach indication toward a core network. In alternative embodiments, the GANC deregisters the MS rather than the Femto Cell CPE.

WO2009135438 discloses a method and equipment of obtaining an information for residence reselecting. The method may include the steps whereby an access network in the 2G or 3G system calculates to gain a residence reselecting information for the mobile terminal according to the subscriber type indication of the mobile terminal sent by a core network, and the residence reselecting information is sent to the mobile terminal. The method may also include the steps of that: the core network calculates to gain a residence reselecting information for the mobile terminal according to the subscriber type indication of the mobile terminal, and the residence reselecting information transparent transmission is sent to the mobile terminal by the access network. The method may also include the steps of: the mobile terminal receives the subscriber type indication from the core network sent by the access network, and the residence reselecting information is obtained by

263067/2 calculating according to the subscriber type indication. Thus, various technical schemes is provided for obtaining the residence reselecting information. The switching information transmission and the switching technical scheme make the residence switching control in the case of the coexistence of the service switching cell and subscriber information clear.

WO2016178605 discloses a method performed by a network node for handling a Radio Access Network, RAN, context information of a wireless device in a cell served by the network node in a wireless communications network. The network node stores the RAN context information of the wireless device when the wireless device is no longer in a connected state in the cell. When the wireless device has returned to a connected state in the cell, the network node receives information indicating a RAN context information from the wireless device. Also, the network node transmits, to the wireless device, information indicating that the wireless device is to use the indicated RAN context information in the cell when the indicated RAN context information is such that it can be reused with the RAN context information of the wireless device previously stored by the network node. Embodiments of the network node are also described. Embodiments herein further relate to a method performed by a wireless device for handling a Radio Access Network, RAN, context information in a cell served by a network node in wireless communications network, and to embodiments of the wireless device.

US 2012/252397 discloses a system of normal service resumption comprising of a UE that is currently behaving as emergency attached after receiving an limited service indication from the network, sends a behaviour change request message when the UE enters a new tracking area with a tracking area identity that is not included in the forbidden list. The network node accepts the behaviour change request when it receives a behaviour change request message from a UE that is currently behaving as emergency attached and sending the behaviour change request message from an area wherein the UE can obtain normal service. Subsequently, the said UE and network node consider the UE to be normally attached after the behaviour change request has been accepted.

US 2013/0208699 relates to reduction of radio connectivity of a bearer service. Upon detection of low data transfer activity within a bearer service, radio connectivity of the bearer service is reduced so as to reduce signaling overhead in an air interface. However, a core network connection of the bearer service is maintained.

US 2016/0105865 discloses systems and methods for small cell idle mode mobility include receiving, at a first small cell of a preconfigured cluster of small cells, a mobility area update request from a user equipment (UE). The method can also include registering location information of the UE with a small cell gateway, and retrieving a core network

7a

263067/1 periodic timer for the UE from a mobility server. If certain conditions are met, the first small cell forwards the mobility area update request to a core network via the small cell gateway. Otherwise, the method can include the first small cell updating the location information of the UE with the mobility server, generating a locally-generated mobility area update accept message, and sending a locally generated mobility area update accept message to the UE along with a local periodic timer instructing the UE to send another mobility area update request when the local periodic timer expires.

US 2015/0009816 discloses a method of uplink shaping and extending UE in RRC Idle Mode. The UE processes a data packet to be sent to the network. The data packet is associated with a traffic type. If the data packet belongs to a normal traffic type, then the UE enters RRC Connected mode and thereby transmitting the data packet to the network. If the data packet belongs to a background traffic type, then the UE buffers the data packet and the UE is prohibited from entering RRC Connected mode until a triggering condition is satisfied for uplink transmission. The proposed mechanism achieves power saving by reducing the activity of uplink transmission. In addition, the proposed mechanism also reduces signaling overhead to enhance network efficiency.

Reference is also made to ERICSSON: “3GPP Draft; R2-163998: Handling of inactive UEs”, vol. RAN WG2, no. Nanjing; 20160523 - 20160527, 13 May 2016 (2016-05-13), pages 1 - 6, XP051089658: http://www.3qpp.org/ftp/tsq ran/WG2 RL2/TSGR2 94/Docs/. This standard proposes a number of assumptions related to handling of inactive UEs in New 5G Radio (NR) aimed at minimizing signaling related to inactive devices by having relaxed requirements on mobility tracking in inactive state, while the state transition can be optimized by keeping and re-using the device context when the device returns. At the same time it is also important to minimize the UE battery consumption both in active and inactive state.

Summary

Systems and methods are disclosed herein that relate configuration of a periodic updating timer for, e.g., a Radio Access Network (RAN) - controlled inactive state. In some embodiments, a method of operation of a RAN node in a cellular communications network comprises configuring a User Equipment (UE) with a timer value T for a periodic updating timer. In this manner, the RAN node is able to configure the UE with a time value T, e.g., for use by the UE for providing periodic update messages while the UE is operating in an inactive state such as, e.g., a RAN-controlled inactive state.

In some embodiments, the timer value T is a function of whether the RAN node can reliably store a RAN context of the UE. In some embodiments, the timer value T is a function of one or more characteristics of the RAN node. In some embodiments, the timer value T is received from another network node. In some embodiments, the periodic updating timer is a timer utilized by the UE for periodic updates when the UE is in a RAN inactive state. In some embodiments, the timer value T is a first value if the RAN node is a macro node and a second value if the RAN node is a Low Power Node (LPN), the second value being less than the first value.

In some embodiments, configuring the UE with the timer value T comprises configuring the UE with the timer value T prior to releasing the UE. In other embodiments, configuring the UE with the timer value T comprises configuring the UE with the timer value T upon releasing the UE.

In some embodiments, configuring the UE with the timer value T comprises sending a release message to the UE, wherein the release message comprises the timer value T.

In some embodiments, the method further comprises releasing a connection with the UE and, after releasing the connection with the UE, receiving an update message from the UE upon expiry of the periodic updating timer.

Embodiments of a RAN node for a cellular communications network are also disclosed. In some embodiments, a RAN node for a cellular communications network is adapted to configure a UE with a timer value T for a periodic updating timer. Further, in some embodiments, the RAN node is further adapted to perform the method of operation of a RAN node according to any one of the embodiments disclosed herein.

In some embodiments, a RAN node for a cellular communications network comprises one or more transmitters, one or more processors, and memory storing instructions executable by the one or more processors whereby the RAN node is operable to configure a UE with a timer value T for a periodic updating timer. Further, in some embodiments, by execution of the instructions by the one or more processors, the RAN node is further operable to perform the method of operation of a RAN node according to any one of the embodiments disclosed herein.

In some embodiments, a RAN node for a cellular communications network comprises a timer configuration module operable to configure a UE with a timer value T for a periodic updating timer.

Embodiments of a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method of operation of a RAN node according to any one of the embodiments disclosed herein. Embodiments of a carrier containing the aforementioned computer program are also disclosed, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

Embodiments of a method of operation of a UE in a cellular communications network are also disclosed. In some embodiments, a method of operation of a UE in a cellular communications network comprises receiving, from a RAN node, a configuration of a timer value T for a periodic updating timer. The method further comprises starting the periodic updating timer once a connection between the UE and the RAN node is released, and sending a periodic update message to the RAN node upon expiry of the periodic updating timer.

In some embodiments, the method further comprises storing a RAN context of the UE at the UE when in the RAN-controlled inactive state. In some embodiments, the method further comprises, upon transitioning from the RAN-controlled inactive state to an active state, rebuilding the RAN context of the UE if needed.

In some embodiments, the timer value T is a function of whether the RAN node can reliably store a RAN context of the UE. In some embodiments, the timer value T is a function of one or more characteristics of the RAN node.

In some embodiments, receiving the configuration of the timer value T for the periodic updating timer comprises receiving the configuration of the timer value T for the periodic updating timer prior to release of the connection between the UE and the RAN node. In some other embodiments, receiving the configuration of the timer value T for the periodic updating timer comprises receiving the configuration of the timer value T for the periodic updating timer upon release of the connection between the UE and the RAN node. In some embodiments, receiving the configuration of the timer value T for the periodic updating timer comprises receiving a release message from the RAN, where the release message comprises the timer value T for the periodic updating timer.

Embodiments of a UE for a cellular communications network are also disclosed. In some embodiments, a UE for a cellular communications network is adapted to receive, from a RAN node, a configuration of a timer value T for a periodic updating timer. The UE is further adapted to start the periodic updating timer once a connection between the UE and the RAN node is released and send a periodic update message to the RAN node upon expiry of the periodic updating timer. In some embodiments, the UE node is further adapted to perform the method of operation of a UE according to any one of the embodiments disclosed herein.

In some embodiments, a UE for a cellular communications network comprises one or more transmitters, one or more receivers, one or more processors, and memory storing instructions executable by the one or more processors whereby the UE is operable to receive, from a RAN node, a configuration of a timer value T for a periodic updating timer, start the periodic updating timer once a connection between the UE and the RAN node is released, and send a periodic update message to the RAN node upon expiry of the periodic updating timer. In some embodiments, by execution of the instructions by the one or more processors, the UE is further operable to perform the method of operation of a UE according to any one of the embodiments disclosed herein.

In some embodiments, a UE for a cellular communications network comprises a receiving module, a timer starting module, and a sending module. The receiving module is operable to receive, from a RAN node, a configuration of a timer value T for a periodic updating timer. The timer starting module is operable to, once a connection between the UE and the RAN node is released, start the periodic updating timer. The sending module is operable to, upon expiry of the periodic updating timer, send a periodic update message to the RAN node.

Embodiments of a computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method of operation of a UE according to any one of the embodiments disclosed herein. Embodiments of a carrier containing the aforementioned computer program are also disclosed, wherein the carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium.

Those skilled in the art will appreciate the scope of the present disclosure and realize additional aspects thereof after reading the following detailed description of the embodiments in association with the accompanying drawing figures.

Brief Description of the Drawings

The accompanying drawing figures incorporated in and forming a part of this specification illustrate several aspects of the disclosure, and together with the description serve to explain the principles of the disclosure.

Figure 1 illustrates the current standard Evolved Packet Core (EPC) architecture of a wireless communications network;

Figure 2 illustrates the radio interface user and control plane protocol for Evolved Universal Terrestrial Radio Access Network (E-UTRAN);

Figures 3 and 4 illustrate the basic principles of handling of inactive User Equipment devices (UEs) in the Radio Access Network (RAN);

Figure 5 illustrates one example of a cellular communications network in which embodiments of the present disclosure may be implemented;

Figure 6 illustrates UE RAN context storing according to some embodiments of the present disclosure;

Figure 7 illustrates RAN configuration of a periodic update timer according to some embodiments of the present disclosure;

Figure 8 illustrates a RAN node making a decision as to whether to retain UE RAN context of a UE according to some embodiments of the present disclosure;

Figures 9 to 11 illustrate example embodiments of a network node; and

Figures 12 and 13 illustrate example embodiments of a UE.

Detailed Description

The embodiments set forth below represent information to enable those skilled in the art to practice the embodiments and illustrate the best mode of practicing the embodiments. Upon reading the following description in light of the accompanying drawing figures, those skilled in the art will understand the concepts of the disclosure and will recognize applications of these concepts not particularly addressed herein. It should be understood that these concepts and applications fall within the scope of the disclosure and the accompanying claims.

Radio Node: As used herein, a “radio node” is either a radio access node or a wireless device.

Radio Access Node: As used herein, a “radio access node” is any node in a Radio Access Network (RAN) of a cellular communications network that operates to wirelessly transmit and/or receive signals. The terms “radio access node” and “RAN node” are used interchangeably herein. Some examples of a radio access node include, but are not limited to, a base station (e.g., an enhanced or evolved Node B (eNB) in a Third Generation Partnership Project (3GPP) Long Term Evolution (LTE) network), a highpower or macro base station, a low-power base station (e.g., a micro base station, a pico base station, a home eNB, or the like), and a relay node.

Macro Node: As used herein, a “macro node” is one type of radio access node. A macro node may also be referred to as a high power node. One example of a macro node is a LTE eNB.

Low Power Node (LPN): As used herein, a “low power node (LPN)” is one type of radio access node and is to be distinguished from a macro node. In general, a LPN has a lower transmit power than a macro node and, as such, has a smaller coverage area than a macro node. Some examples of a LPN include a micro base station, a pico base station, a home eNB, or the like.

Core Network (CN) Node: As used herein, a “core network (CN) node” is any type of node in a CN. Some examples of a CN node include, e.g., a Mobility Management Entity (MME), a Packet Data Network (PDN) Gateway (P-GW), a Service Capability Exposure Function (SCEF), or the like.

Wireless Device: As used herein, a “wireless device” is any type of device that has access to (i.e., is served by) a cellular communications network by wirelessly transmitting and/or receiving signals to a radio access node(s). The terms “wireless device” and “User Equipment (UE)” are used interchangeably herein in that the term “UE” is used in a broad sense to mean any type of wireless device unless otherwise specified (e.g., unless specified as an LTE UE). Some examples of a wireless device include, but are not limited to, an UE in a 3GPP network and a Machine Type Communication (MTC) device.

Network Node: As used herein, a “network node” is any node that is either part of the RAN or the CN of a cellular communications network/system.

Note that the description given herein focuses on a 3GPP cellular communications system and, as such, 3GPP LTE terminology or terminology similar to 3GPP LTE terminology is oftentimes used. However, the concepts disclosed herein are not limited to LTE or a 3GPP system.

Note that, in the description herein, reference may be made to the term “cell;” however, particularly with respect to Fifth Generation (5G) concepts, beams may be used instead of cells and, as such, it is important to note that the concepts described herein are equally applicable to both cells and beams.

Storing the UE RAN context in the RAN for UEs that are not connected or inactive introduces a potential risk that the UE RAN context is lost, e.g., due to restart of the RAN node. A similar problem can also occur if the UE context is stored in the CN, but most likely the risk of losing the UE context is deemed lower in those cases since typically CN nodes are deployed in a secure central environment and use additional redundancy methods. Some RAN nodes on the other hand such as pico or femto base stations may be deployed everywhere in a non-controlled environment including coffee shops, enterprises, shopping malls, etc. These nodes may in some cases also need to be lowcost, meaning additional costly redundancy methods may not be used.

Losing the UE RAN context may lead to the UE not being reachable for incoming data, paging, or services during a time period. The time period depends on the UE’s own activity and on any periodic location updating signaling from the UE. It is assumed that once the UE contacts the network the UE RAN context will be re-built in some way or another.

In a legacy system, the periodic location updating timers, which are used by the core network, are set to longer than one hour in order to have a good tradeoff between the risk of not being able to reach the UE if the context is lost and the amount of the signaling in the network. However, the current solution is not good enough given that UE RAN context may be lost more frequently if it is stored in more unreliable nodes.

One way to minimize the risk of UEs ending up in an unreachable state could be as in the 3GPP Release 13 Radio Resource Control (RRC) suspend/resume solution where CN based paging and registration updating is also supported. In such a solution, if the RAN context is lost, the CN can still page and reach the UE. The drawback with this solution though is that if it is desirable to support RAN paging in order to optimize the paging performance in RAN, the UE would then still need to also monitor CN based paging in case the RAN context is lost. This extra complexity in the UE and network is a fairly high price to pay for something that happens quite rarely.

The present disclosure introduces methods for handling UE context in the RAN in such a way that the risk of the UE ending up in an unreachable state is minimized. The following high level embodiments are envisioned:

- The usage of a configurable periodic updating timer in the UE, used in such a way that RAN nodes which are considered more unreliable (e.g., pico or femto nodes) assign the UE a short periodic updating timer in the inactive state, where RAN nodes which are considered highly reliable use a long timer. In this way the total amount of periodic updating is not affected so much, but the risk of UEs ending up in an unreachable state is minimized.

- The possibility to move the UE context from an unreliable RAN node (e.g., pico or femto nodes) to a more reliable RAN node when the UE is sent to the inactive state by such an unreliable RAN node. This can be done when the RAN decides to order the UE to inactive state. It first transfers the UE RAN context to a more reliable RAN node towards which it has an interface and then provides the UE with a context identifier which is associated with that more reliable RAN node.

- For solutions where the RAN based inactive state (including RAN paging) is only used for UEs which have a context stored in a reliable RAN node, UEs in nonreliable RAN nodes are only supported in a CN based sleep state with CN paging. In this solution the UE would only need to monitor one type of paging.

By using embodiments disclosed herein, it is possible to reduce the risk of UEs ending up in an unreachable state which is beneficial for both the operator and the end user. It also avoids the need for CN paging in addition to RAN paging which introduces a lot of extra complexity.

In this regard, Figure 5 illustrates one example of a cellular communications network 10 in which embodiments of the present disclosure may be implemented. As illustrated, the cellular communications network 10 includes a RAN. The RAN includes, in this example, a macro node 12 that serves a macro cell 14 and a LPN 16 that serves a small cell 18. UEs 20 transmit and receive wireless signals to and from the macro node 12 and/or the LPN 16. In this context of the embodiments described herein, the macro node 12 is one example of a radio access node or base station that is reliable in the sense that a RAN context of a UE 20 may be stored reliably at the macro node 12. Conversely, in this example, the LPN 16 is one example of a radio access node or base station that is unreliable in the sense that a RAN context of a UE 20 may not be reliably stored at the LPN 16. However, this is only an example.

The macro node 12 and the LPN 16 are connected to a core network 22 via corresponding CN interfaces (e.g., S1 interfaces), which may be wired or wireless interfaces. While not illustrated, the macro node 12 and the LPN 16 may be connected to one another via base-station-to-base-station interfaces (e.g., X2 interfaces), which may be wired or wireless interfaces. The core network 22 is connected to a data network 24 via an appropriate interface(s).

Figure 6 illustrates UE RAN context storing according to some embodiments of the present disclosure. In particular, Figure 6 shows how a UE RAN context of a UE (e.g., one of the UEs 20 of Figure 5) is stored in a reliable macro RAN node (e.g., the macro node 12 of Figure 5) designated as RAN_Macro by an unreliable pico RAN node (e.g., the LPN 16 of Figure 5) designated as RAN_Pico according to some embodiments of the present disclosure. Note that while a pico RAN node is used in this example, the process is equally applicable to a more general LPN or even more generally to any other type of radio access node (i.e., any other type of RAN node) that is unable to reliably store UE RAN context information. For example, a RAN node may be unable to reliably store UE RAN context information due to various issues such as, for example, memory shortage.

As illustrated, the process of Figure 6 is as follows:

• Step 100: A data connection is established between the UE and the Data_Network (e.g., the data network 24 of Figure 5) whereby the UE has an active connection with the RAN_Pico.

• Step 102: Due to, e.g., inactivity, the RAN_Pico node decides to release the connection with the UE, e.g. to move it to an inactive state (e.g., a RAN controlled inactive state).

• Step 104: The RAN_Pico node sends, over an interface that supports a UE RAN context storing procedure, a request to the RAN_Macro node for storing of the UE RAN context. The request includes the UE RAN context of the UE.

• Step 106: The RAN_Macro node stores the UE RAN context of the UE and replies with a response message containing a UE RAN context identity allocated to the UE RAN context of the UE on that RAN_Macro node.

• Step 108: The RAN_Pico node releases the connection with the UE, e.g. by moving the UE into an inactive state (e.g., a RAN controlled inactive state). It provides the UE with the UE RAN context identity provided by the RAN_Macro node in step 106.

Figure 7 illustrates RAN configuration of a periodic update timer according to some embodiments of the present disclosure. In particular, Figure 7 shows how the RAN node (in this example RAN_Pico but can also be some other RAN node) configures a timer value T for a periodic updating timer of the UE. Again, here the RAN_Pico may be, e.g., the LPN 16 of Figure 5) and the UE may be one of the UEs 20 of Figure 5. The process is as follows:

• Step 200: A data connection is established between the UE and the Data_Network (e.g., the data network 24 of Figure 5) whereby the UE has an active connection with the RAN_Pico node.

• Step 202: In some embodiments (i.e., in a first alternative), the RAN_Pico node configures the periodic updating timer to a timer value T before connection release. Since in this example the RAN_Pico node is considered unreliable with respect to storing UE RAN context, the timer value T is smaller than a respective timer value T for a reliable RAN node (e.g., the macro node 12). For example, the timer value T configured by the RAN_Pico node may be on the order of seconds or minutes, rather than on the order of hours.

• Step 204: Due to, e.g., inactivity, the RAN_Pico node decides to release the connection with the UE, e.g. to move it to an inactive state (e.g., move it to a RAN controlled inactive state). Note that while the term “release” is used herein, other terms may be used such as, e.g., “suspend,” “putting the UE in the RAN controlled inactive state,” or the like.

• Step 206: The RAN_Pico node releases the connection with the UE, e.g. by moving the UE into an inactive state (e.g., a RAN controlled inactive state). In a second alternative, the RAN_Pico node configures the timer value T when releasing the connection (e.g., the timer value T is included in the release message). Thus, in some embodiments, the timer value T is set in step 202, whereas in other embodiments the timer value T is set in step 206 when releasing the connection.

• Step 208: Once the connection is released (and the UE has therefore entered the RAN-based inactive state), the UE starts the periodic updating timer set to the timer value T. The timer continues to run until it expires. The UE stores the RAN context of the UE while in the RAN-based inactive state. The stored RAN context is used by the UE when transitioning back to the RAN-based active state. In other words, the UE stores the RAN context of the UE when no longer in a (RAN based) connected state in the cell. This means that instead of discarding this information, the UE may save or cache this information in case of returning to the cell.

• Step 210: Upon expiry of the timer (assuming the UE has not performed any other action during the time that requires signaling towards the network), the UE sends a periodic update message.

• Step 212: Optionally, the network (e.g., the RAN_Pico node) may return an acknowledge message.

• Step 214: If the UE has no data to send or receive, the UE resets the timer to the timer value T and re-enters the inactive state until the timer expires again. Once reset, the timer continues to run until it expires.

• Step 216: Upon expiry of the timer (assuming the UE has not performed any other action during the time), the UE sends a periodic update message.

• Step 218: Optionally, the network (e.g., the RAN_Pico node) may return an acknowledge message.

The process continues in this manner.

Note that, in some embodiments, the timer value T is a function of where the RAN node can reliably store RAN context of the UE (e.g., as determined based on one or more characteristics of the RAN node such as, e.g., a type or class of the RAN node, memory usage at the RAN node, or the like or otherwise determined). In some other embodiments, the timer value T is a function of one or more characteristics of the RAN node (e.g., type or class of the RAN node, amount of memory, memory usage, or the like). In some embodiments, the timer value T is determined or set by the RAN node itself. However, in other embodiments, the timer value T is determined or set by, e.g., some other node in the network (e.g., an Operations and Management (OAM) system) and sent to the RAN node.

Figure 8 illustrates a RAN node making a decision as to whether to retain UE RAN context of a UE according to some embodiments of the present disclosure. In particular, Figure 8 shows how the RAN node (e.g., the macro node 12 or the LPN 16 of Figure 5) takes a decision to release a UE to an inactive state. The decision could either be to release the UE to a CN IDLE state with no RAN context stored in the RAN or to a RAN inactive state where the RAN context of the UE is stored and UE kept in a CN CONNECTED state. The decision is based on, among other things, the reliability of the context storage in the RAN node (which could be the reliability of the whole node). The process is as follows:

• Step 300: A data connection is established between the UE and the Data_Network (e.g., the data network 24 of Figure 5) whereby the UE has an active connection with the RAN_Node.

• Step 302: Due to, e.g., inactivity, the RAN_Node decides to release the connection with the UE, e.g. to move it to an inactive state. The RAN_Node decides whether to release the UE to a CN IDLE state with no RAN context stored in the RAN or to a RAN inactive state where the RAN context of the UE is stored and kept in a CN CONNECTED state.

• Steps 304 and 306: If the RAN_Node decides to release the UE to the CN IDLE state, it signals both the UE (step 304) and the Core_Network (step 306) to release the UE to the CN IDLE state. As noted above, the RAN context of the UE is not stored in the RAN in this case.

• Step 308: If the RAN_Node decides to release the UE to RAN inactive state, the RAN_Node signals the UE to release the UE to the RAN inactive state. In this case, the RAN context of the UE is stored in the RAN. The RAN context may be stored at the RAN_Node in the conventional manner or stored at another RAN node (e.g., a more reliable RAN node as described above).

Figure 9 is a schematic block diagram of a network node 26 according to some embodiments of the present disclosure. The network node 26 may be, for example, a RAN node such as the macro node 12 or the LPN 16 of Figure 5. As illustrated, the network node 26 includes a control system 28 that includes processing circuitry that includes one or more processors 30 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like). The control system 28 further includes memory 32, and a network interface 34. In addition, if the network node 26 is a RAN node, then the network node 26 also includes one or more radio units 36 that each includes one or more transmitters 38 and one or more receivers 40 coupled to one or more antennas 42. In some embodiments, the radio unit(s) 36 is external to the control system 28 and connected to the control system 28 via, e.g., a wired connection. However, in some other embodiments, the radio unit(s) 36 and potentially the antenna(s) 42 are integrated together with the control system 28. The one or more processors 30 operate to provide one or more functions of a network node as described herein. In some embodiments, the function(s) are implemented in software that is stored, e.g., in the memory 32 and executed by the one or more processors 30.

Figure 10 is a schematic block diagram that illustrates a virtualized embodiment of the network node 26 according to some embodiments of the present disclosure. This discussion is equally applicable to other types of radio access nodes. Further, other types of network nodes may have similar virtualized architectures.

As used herein, a “virtualized” network node (e.g., a virtualized base station or a virtualized radio access node) is an implementation of the network node in which at least a portion of the functionality of the network is implemented as a virtual component (e.g., via a virtual machine(s) executing on a physical processing node(s) in a network(s)). As illustrated, in this example, the network node 26 includes the control system 28 that includes the one or more processors 30 (e.g., CPUs, ASICs, FPGAs, and/or the like), the memory 32, and the network interface 34 and, depending on the type of network node, the one or more radio units 36 that each includes the one or more transmitters 38 and the one or more receivers 40 coupled to the one or more antennas 42, as described above. The control system 28 is connected to the radio unit(s) 36 via, for example, an optical cable or the like. The control system 28 is connected to one or more processing nodes 44 coupled to or included as part of a network(s) 46 via the network interface 34. Each processing node 44 includes processing circuitry that includes one or more processors 48 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 50, and a network interface 52.

In this example, functions 54 of the network node (e.g., functions of the macro node 12 (RAN_Macro node) or the LPN 16 (e.g., the RAN_Pico node) or the functions of the RAN_Node) described herein are implemented at the one or more processing nodes 44 or distributed across the control system 28 and the one or more processing nodes 44 in any desired manner. The functions 54 may include, e.g., one or more functions 54 performed by the RAN_Pico node described with respect to Figure 6, one or more functions 54 performed by the RAN_Pico node of Figure 7, and/or one or more functions 54 performed by the RAN_Node of Figure 8. In some particular embodiments, some or all of the functions 54 of the network node 26 described herein are implemented as virtual components executed by one or more virtual machines implemented in a virtual environment(s) hosted by the processing node(s) 44. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 44 and the control system 28 is used in order to carry out at least some of the desired functions 54. Notably, in some embodiments, the control system 28 may not be included, in which case the radio unit(s) 36 communicate directly with the processing node(s) 44 via an appropriate network interface(s).

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of a network node or a node (e.g., a processing node 44) implementing one or more of the functions 54 of the network node in a virtual environment according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 11 is a schematic block diagram of the network node 26 according to some other embodiments of the present disclosure. The network node 26 includes one or more modules 56, each of which is implemented in software. The module(s) 56 provide the functionality of the network node 26 described herein. For example, the module(s) 56 may include one or modules that perform the operations of the RAN_Pico node described with respect to Figure 6, one or more modules that perform the operations of the RAN_Pico node of Figure 7, and/or one or more modules that operate to perform the operations of the RAN_Node of Figure 8.

Figure 12 is a schematic block diagram of the UE 20 according to some embodiments of the present disclosure. As illustrated, the UE 20 includes processing circuitry that includes one or more processors 58 (e.g., CPUs, ASICs, FPGAs, and/or the like). The UE 20 further includes memory 60, and one or more transceivers 62 each including one or more transmitters 64 and one or more receivers 66 coupled to one or more antennas 68. In some embodiments, the functionality of the UE 20 described above (e.g., the functionality of the UE 20 described with respect to Figures 6, 7, and/or 8) may be fully or partially implemented in software that is, e.g., stored in the memory 60 and executed by the processor(s) 58.

In some embodiments, a computer program including instructions which, when executed by at least one processor, causes the at least one processor to carry out the functionality of the UE 20 according to any of the embodiments described herein is provided. In some embodiments, a carrier comprising the aforementioned computer program product is provided. The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer readable storage medium (e.g., a non-transitory computer readable medium such as memory).

Figure 13 is a schematic block diagram of the UE 20 according to some other embodiments of the present disclosure. The UE 20 includes one or more modules 70, each of which is implemented in software. The module(s) 70 provide the functionality of the UE 20 described herein. For example, the module(s) 70 may include one or modules that perform the operations of the UE described with respect to Figure 6, one or more modules that perform the operations of the UE of Figure 7, and/or one or more modules that operate to perform the operations of the UE of Figure 8.

While not being limited thereto, some example embodiments of the present disclosure are provided below. In some embodiments, a method of operation of a first RAN node in a cellular communications network comprises storing a RAN context of a UE at a second RAN node, obtaining a RAN context identity of the RAN context of the UE stored at the second RAN node, and providing the RAN context identity to the UE. In some embodiments, providing the RAN context identity to the UE comprises providing the RAN context identity to the UE when releasing a connection of the UE. In some embodiments, the method further comprises making a decision to release the connection of the UE, wherein storing the RAN context of the UE at the second RAN node comprises storing the RAN context of the UE at the second RAN node upon making the decision to release the connection of the UE. In some embodiments, storing the RAN context of the UE at a second RAN node comprises sending a request to store the RAN context of the

UE to the second RAN node, wherein the request comprises the RAN context of the UE, and obtaining the RAN context identity comprises receiving a response from the second RAN node in response to the request, wherein the response comprises the RAN context identity of the RAN context of the UE stored at the second RAN node. In some embodiments, the first RAN node is a LPN, and the second RAN node is a macro node.

In some embodiments, a first RAN node for a cellular communications network is adapted to store a RAN context of a UE at a second RAN node, obtain RAN context identity of the RAN context of the UE stored at the second RAN node, and provide the RAN context identity to the UE. Further, in some embodiments, the RAN node is further adapted to perform the method of operation of the first RAN node described above.

In some embodiments, a first RAN node for a cellular communications network comprises a communication interface, one or more transmitters, one or more processors, and memory storing instructions executable by the one or more processors whereby the first RAN node is operable to store, via the communication interface, a RAN context of a UE at a second RAN node, obtain RAN context identity of the RAN context of the UE stored at the second RAN node, and provide, via the one or more transmitters, the RAN context identity to the UE.

In some embodiments, a first RAN node for a cellular communications network comprises a storing module operable to store a RAN context of a UE at a second RAN node, an obtaining module operable to obtain RAN context identity of the RAN context of the UE stored at the second RAN node, and a providing module operable to provide the RAN context identity to the UE.

In some embodiments, a method of operation of a UE in a cellular communications network comprises receiving, from a first RAN node, a RAN context identity of a RAN context of the UE stored at a second RAN node. Further, in some embodiments, receiving the RAN context identity comprises receiving a connection release from the first RAN node, wherein the connection release comprises the RAN context identity. Further, in some embodiments, the first RAN node is a LPN and the second RAN node is a macro node.

In some embodiments, a UE for a cellular communications network is adapted to receive, from a first RAN node, a RAN context identity of a RAN context of the UE stored at a second RAN node. Further, in some embodiments, the UE is further adapted to operate according to any one of the embodiments of the UE described above.

In some embodiments, a UE for a cellular communications network comprises one or more receivers, one or more processors, and memory storing instructions executable by the one or more processors whereby the UE is operable to receive, from a first RAN node, a RAN context identity of a RAN context of the UE stored at a second RAN node.

In some embodiments, a UE for a cellular communications network comprises a receiving module operable to receive, from a first RAN node, a RAN context identity of a RAN context of the UE stored at a second RAN node.

In some embodiments, a method of operation of a RAN node in a cellular communications network comprises configuring a UE with a timer value T for a periodic updating timer. Further, in some embodiments, the timer value T is a function of whether the RAN node can reliably store a RAN context of the UE. In some embodiments, the timer value T is a function of one or more characteristics of the RAN node. In some embodiments, the timer value T is received from another network node. In some embodiments, the periodic update timer is a timer utilized by the UE for periodic updates when the UE is in a RAN inactive state. In some embodiments, the timer value is a first value if the RAN node is a macro node and a second value if the RAN node is a LPN, the second value being less than the first value. In some embodiments, configuring the UE with the timer value T comprises configuring the UE with the timer value T prior to releasing the UE. In some embodiments, configuring the UE with the timer value T comprises configuring the UE with the timer value T upon releasing the UE. In some embodiments, configuring the UE with the timer value T comprises sending a release message to the UE, wherein the release message comprises the timer value T.

In some embodiments, a RAN node for a cellular communications network is adapted to configure a UE with a timer value T for a periodic updating timer. Further, in some embodiments, the RAN node is further adapted to perform the method of any one of the embodiments of the method of operation of the RAN node describe above.

In some embodiments, a RAN node for a cellular communications network comprises one or more transmitters, one or more processors, and memory storing instructions executable by the one or more processors whereby the RAN node is operable to configure a UE with a timer value T for a periodic updating timer.

In some embodiments, a RAN node for a cellular communications network comprises a timer configuration module operable to configure a UE with a timer value T for a periodic updating timer.

In some embodiments, a method of operation of a RAN node in a cellular communications network comprises making a connection release decision for a UE, wherein the connection release decision is either a decision to release the UE to a CN IDLE state or a RAN inactive state, releasing the UE to the CN IDLE state if the connection release decision is a decision to release the UE to the CN IDLE state, wherein a RAN context of the UE is not stored in the RAN when the UE is in the CN IDLE state, and releasing the UE to the RAN inactive state if the connection release decision is a decision to release the UE to the RAN inactive state, wherein the RAN context of the UE is stored in the RAN when the UE is in the RAN inactive, and thus CN CONNECTED, state. In some embodiments, making the connection release decision comprises making the connection release decision based on an ability of the RAN node to reliably store the RAN context of the UE. In some embodiments, the connection release decision is a decision to release the UE to the CN IDLE state if the RAN node is a LPN.

In some embodiments, a RAN node for a cellular communications network is adapted to make a connection release decision for a UE, wherein the connection release decision is either a decision to release the UE to a CN IDLE state or a RAN inactive state, release the UE to the CN IDLE state if the connection release decision is a decision to release the UE to the CN IDLE state, wherein a RAN context of the UE is not stored in the RAN node when the UE is in the CN IDLE state, and release the UE to the RAN inactive state if the connection release decision is a decision to release the UE to the RAN inactive state, wherein the RAN context of the UE is stored in the RAN node when the UE is in the RAN inactive, and thus CN CONNECTED, state. In some embodiments, the RAN node is further adapted to perform the method of operation of the RAN node in accordance with any one of the embodiments described above.

In some embodiments, a RAN node for a cellular communications network comprises one or more transmitters, one or more processors, and memory storing instructions executable by the one or more processors whereby the first RAN node is operable to make a connection release decision for a UE, wherein the connection release decision is either a decision to release the UE to a CN IDLE state or a RAN inactive state, release the UE to the CN IDLE state if the connection release decision is a decision to release the UE to the CN IDLE state, wherein a RAN context of the UE is not stored in the RAN node when the UE is in the CN IDLE state, and release the UE to the RAN inactive state if the connection release decision is a decision to release the UE to the RAN inactive state, wherein the RAN context of the UE is stored in the RAN node when the UE is in the RAN inactive, and thus CN CONNECTED, state.

In some embodiments, a RAN node for a cellular communications network comprises a decision module operable to make a connection release decision for a UE, wherein the connection release decision is either a decision to release the UE to a CN IDLE state or a RAN inactive state, and a connection release module operable to release the UE to the CN IDLE state if the connection release decision is a decision to release the UE to the CN IDLE state, wherein a RAN context of the UE is not stored in the RAN node when the UE is in the CN IDLE state, and release the UE to the RAN inactive state if the connection release decision is a decision to release the UE to the RAN inactive state, wherein the RAN context of the UE is stored in the RAN node when the UE is in the RAN inactive, and thus CN CONNECTED, state.

The following acronyms are used throughout this disclosure.

<td> • 2G</td><td> Second Generation</td>

<td> • 3GPP</td><td> Third Generation Partnership Project</td>

<td> • 5G</td><td> Fifth Generation</td>

<td> • AIR</td><td> Antenna Integrated Radio</td>

<td> • AS</td><td> Access Stratum</td>

<td> • ASIC</td><td> Application Specific Integrated Circuit</td>

<td> • BSC</td><td> Base Station Controller</td>

<td> • CN</td><td> Core Network</td>

<td> • CPU</td><td> Central Processing Unit</td>

<td> • C-RNTI</td><td> Cell Radio Network Temporary Identifier</td>

<td> • DU</td><td> Digital Unit</td>

<td> • eNB</td><td> Enhanced or Evolved Node B</td>

<td> • EPC</td><td> Evolved Packet Core</td>

<td> • EPS</td><td> Evolved Packet System</td>

<td> • E-UTRAN</td><td> Evolved Universal Terrestrial Radio Access Network</td>

<td> • FPGA</td><td> Field Programmable Gate Array</td>

<td> • GPRS</td><td> General Packet Radio System</td>

<td> • GSM</td><td> Global System for Mobile Communications</td>

<td> • GTP-U</td><td> General Packet Radio System Tunneling Protocol User</td>

<td></td><td> Plane</td>

<td> • GUTI</td><td> Globally Unique Temporary Identity</td>

<td> • HARQ</td><td> Hybrid Automatic Repeat Request</td>

<td> • HSPA</td><td> High-Speed Packet Access</td>

<td> • KeNB</td><td> Enhanced or Evolved Node B Key</td>

<td> • LPN</td><td> Low Power Node</td>

<td> • LTE</td><td> Long Term Evolution</td>

<td> • MAC</td><td> Medium Access Control</td>

<td> • MME</td><td> Mobility Management Entity</td>

<td> • MTC</td><td> Machine Type Communication</td>

<td> • NAS</td><td> Non-Access Stratum</td>

<td> • OAM</td><td> Operations and Management</td>

<td> • PDCP</td><td> Packet Data Convergence Protocol</td>

<td> • PDN</td><td> Packet Data Network</td>

<td> • P-GW</td><td> Packet Data Network Gateway</td>

<td> • PHY</td><td> Physical Layer</td>

<td> • QoS</td><td> Quality of Service</td>

<td> • RAN</td><td> Radio Access Network</td>

<td> • RAT</td><td> Radio Access Technology</td>

<td> • RB</td><td> Resource Block</td>

<td> • RBS</td><td> Radio Base Station</td>

<td> • RLC</td><td> Radio Link Control</td>

<td> • RLC-AM</td><td> Radio Link Control Acknowledged Mode</td>

<td> • RLC-UM</td><td> Radio Link Control Unacknowledged Mode</td>

<td> • RNC</td><td> Radio Network Controller</td>

<td> • ROHC</td><td> Robust Header Compression</td>

<td> • RRC</td><td> Radio Resource Control</td>

<td> • RRU</td><td> Remote Radio Unit</td>

<td> • SAE</td><td> System Architecture Evolution</td>

<td> • SCEF</td><td> Service Capability Exposure Function</td>

<td> • S-TMSI</td><td> System Architecture Evolution Temporary Mobile Subscriber</td>

<td></td><td> Identity</td>

<td> • TS</td><td> Technical Specification</td>

<td> • UE</td><td> User Equipment</td>

<td> • UMTS</td><td> Universal Mobile Telecommunications System</td>

<td> • UTRAN</td><td> Universal Terrestrial Radio Access Network</td>

<td> • WCDMA</td><td> Wideband Code Division Multiple Access</td>

<td> Those skilled in</td><td> the art will recognize improvements and modifications to the</td>

<td colspan="2"> embodiments of the present disclosure. All such improvements and modifications falling</td>

<td colspan="2"> within the scope of the claims are considered within the scope of the concepts disclosed</td>

herein.