Technical Field

[0001] The present disclosure relates to a wireless network and, in particular, to infrequent small data for battery saving wireless communication devices.

Background

[0002] Third Generation Partnership Project (3GPP) Technical Report (TR) 23.799 has captured Key Issue 4 on session management.

[0003] This key issue addresses the scenario for users sending infrequent small user data with minimal signalling.

[0004] Requirements under Key Issue 4 addresses "transfer infrequent small user data." The requirements are stated:

- How to efficiently transmit and receive infrequent small amounts of data through the Next Generation (NG) system, including studying whether sessions need to be established to enable such services.

- The solutions should allow for unidirectional transmission (i.e., uplink or downlink only transmission), efficient security mechanisms depending on user and/or operator needs, different options for addressing, charging, policing, and inter-operator interworking.

Summary

[0005] Systems and methods relating to, e.g., infrequent small data for battery saving wireless devices are disclosed. In some embodiments, a method of operation of one or more core network nodes in a Core Network (CN) of a wireless communications system comprises receiving data destined for a wireless device, where the wireless device is unreachable via a Radio Access Network (RAN). In some embodiments, the wireless device is unreachable while operating in a Power Savings Mode (PSM) or extended idle mode Discontinuous Reception (eDRX) or similar. The method further comprises buffering the data in the CN until the wireless device is indicated as being reachable via the RAN and, upon the wireless device being indicated as being reachable, forwarding the data to the wireless device via the RAN. Brief Description of the Drawings

[0006] 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.

[0007] Figure 1 illustrates one example of a wireless communication system in which embodiments of the present disclosure may be implemented;

[0008] Figure 2 illustrates one example of a downlink Packet Data Unit (PDU) flow;

[0009] Figure 3 illustrates one example of a downlink PDU flow for a wireless device operating in a power savings mode according to some embodiments of the present disclosure;

[0010] Figures 4 and 5 illustrate example embodiments of a wireless device; and

[0011] Figures 6 through 8 illustrate example embodiments of a network node.

Detailed Description

[0012] 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.

[0013] Radio Node: As used herein, a "radio node" is either a radio access node or a wireless device. [0014] 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, preferably within a cell, preferably covering a limited geographical area. 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 high-power 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. A radio access node may also be referred to herein as a RAN node or an Access Network (AN) node. In future RANs and/or ANs, a cell may correspond to one or more beams within which a RAN node transmits and/or receives radio signals.

[0015] Core Network Node: As used herein, a "core network node" is any type of node in a Core Network (CN). Some examples of a core network 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. In future CNs, the CN nodes may be virtual or functional entities, e.g. the CN node may be a function, i.e. a function implemented by the CN.

[0016] 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). Some examples of a wireless device include, but are not limited to, a User Equipment device (UE) in a 3GPP network and a Machine Type Communication (MTC) device. A wireless device is also referred to herein as a wireless communication device.

[0017] Network Node: As used herein, a "network node" is any node that is either part of the radio access network or the CN of a cellular communications network/system.

[0018] 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.

[0019] Note that, in the description herein, reference may be made to the term "cell;" however, particularly with respect to Fifth Generation (5G) or Next

Generation (NG) 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.

[0020] 3GPP Technical Report (TR) 23.799 V1 .1 .0 is a study on an

architecture for a NG wireless communication system. 3GPP TR 23.799 presents a number of "Key Issues" and a number of "solutions." One of the key issues, which is referred to in 3GPP TR 23.799 as "Key Issue 4," addresses the scenario for infrequent small user data transmission with minimal signalling. As stated in 3GPP TR 23.799, Section 5.4.1 , requirements listed in 3GPP TR 23.799 for Key Issue 4 include:

· How to efficiently transmit and receive infrequent small amounts of data through the NG system, including studying whether sessions need to be established to enable such services.

• The solutions should allow for unidirectional transmission (i.e., uplink or downlink only transmission), efficient security mechanisms depending on user and/or operator needs, different options for addressing, charging, policing, and inter-operator interworking.

[0021] 3GPP TR 23.799 includes a solution, referred to as "Solution 4.18" and is described in Section 6.4.18 of 3GPP TR 23.799, for infrequency small data. The requirements for infrequent small data mentioned in Key Issue 4 were considered. Solution 4.18 is based on reusing the Inactive 'state' which is expected to be defined by the RAN and also applicable for small data transfers. In this way, a unified handling of sessions is reached.

[0022] In the Release 13 3GPP specification, the requirements for battery savings in context of MTC have been put forward as requiring battery lifetimes of up to 10 years. These extreme battery lifetimes may be required for some wireless devices installed in remote places. Special adaptations in Release 13 to such wireless devices include the solutions based on extended idle mode Discontinuous Reception (eDRX) or Power Saving Mode (PSM). These solutions include devices being unreachable for long times. The expectation of infrequent small data may be that the wireless device is prone to battery savings due to the infrequent nature of the applications. This may apply to both uplink and downlink. In general, it may be expected that the Mobile Terminating (MT) data is even less frequent as stated in 3GPP Technical Specification (TS) 22.368 stage 1 requirement for Infrequent MT data.

[0023] Furthermore, wireless devices may be more or less mobile, ranging from stationary wireless devices such as, e.g., the smart home with wireless devices attached to refrigerators to highly moving wireless devices in vehicles. The combination of high mobility and infrequent data with battery saving requirements may need further considerations.

[0024] Solution 4.18 for infrequent small data uses the method of INACTIVE state in the AN. From the CN point of view, the wireless device (e.g., UE) will be in CONNECTED mode. Therefore, the CN will forward any received packets towards the AN immediately. It is then the responsibility of the AN, if the wireless device is in INACTIVE state, to store the packet, to page the wireless device if needed, and deliver the packet to the wireless device when reachable.

[0025] It is proposed to amend solution 4.18 for infrequent small data to use the method on INACTIVE state in the AN except for battery saving wireless devices.

[0026] Assumptions:

• the network learns the wireless device's mobility pattern and power saving functionality and adapts accordingly;

• for battery saving wireless devices, the packet is stored in the CN until there is an indication that the wireless device is reachable. A CN Control Plane (CP) function uses messages similar to Release 13

suspend/resume as well as Discontinuous Reception (DRX) parameters to identify when the wireless device becomes reachable. [0027] Embodiments of this proposed solution are described below. In particular, it proposed to amend solution 4.18 of 3GPP TR 23.799 for infrequent small data.

[0028] Before describing some embodiments of the present disclosure, a brief discussion of one example of a wireless communications system 10, which is illustrated in Figure 1 , is beneficial. As illustrated, the wireless communications system 10, which may also be referred to herein as a cellular communications system, includes a RAN 12 or AN or similar that includes a number of radio access nodes 14 providing radio access to wireless devices 16 (e.g., UEs). The radio access nodes 14 may also be referred to herein as RAN nodes or AN nodes 14. The radio access nodes 14 are connected to a CN 18 that includes a number of CN nodes 20 or functions (e.g., MMEs, Serving Gateways (S-GWs), P-GWs, CP functions, UP functions, MMF, SMF, and/or the like). As discussed below, a number of CP and User Plane (UP) functionality entities are

implemented on the one or more CN nodes 20. In some particular embodiments, the wireless communications system 10 is a 3GPP NG or 5G system, wherein the RAN 12 is a NG (R)AN and the CN 18 is a NG CN.

[0029] With the 5G (also referred to as NG) architecture of the CN 18, there are a number of basic assumptions made for infrequent small data delivery:

- The Packet Data Unit (PDU) may be Internet Protocol (IP) based or non- IP based.

- The method is based on using the methods in RAN developed for 5G, specifically the "RRC Inactive Connected/Active Connected" states and potential optimizations thereof. The solution thus assumes that the AN does not release the wireless device, or UE, context. In case the AN releases the UE context, the solution falls back to regular CN IDLE state handling.

- CN CP wireless device, or UE, contexts are established at attach or

session setup.

- CN CP preserves UE PDU session contexts as long as the PDU session is maintained. - CN UP can refrain from preserving wireless device, or UE, state

information during inactive periods for the wireless device 16. In this case, CN UP context and connectivity is established when wireless device, or UE, originated or terminated packets need to be forwarded in the UP. After a packet is forwarded to/from the wireless device 16, a UE context is held for a short time in the CN UP to facilitate the server to send, e.g., Acknowledgements (ACKs) to/from the wireless device 16. Removing UE context from CN UP during inactivity periods and maintaining UE state only for a small fraction of the time allows the CN UP to multiplex its resources over a larger number of wireless devices 16.

- The solution is also based on:

o Notifications similar to Release 13 suspend/resume functionality taking the length of the DRX cycle into account.

o AN sending notifications similar to suspend/resume to the CN 18. o For wireless devices 16 where the CN/AN interface is suspended, the downlink PDUs are stored in the CN 18 until an indication is received that the wireless device 16 is reachable or the paging occasion occurs.

o To be able to transfer data to the AN in a way that it coincides with the wireless device's 16 paging occasion, it is required that CN CP function is to certain extent synchronized with the AN.

[0030] Figure 2 illustrates how a downlink PDU is transferred from a data network 28 (e.g., from an Application Server (AS) in the data network) to the wireless device 16, where the wireless device 16 is a device that sends data infrequently. Notably, Figure 2 is a reproduction (at least to a large extent) of Figure 6.4.18.2.3-1 of 3GPP TR 23.700. Note that while a number of "steps" are illustrated, these "steps" are actions that can be performed in any desired order unless otherwise stated or required. Further, Figure 2 illustrates a number of CN functions that are implemented in the CN 18 via one or more of the CN nodes 20. In particular, Figure 2 illustrates a CP function 22, an UP function 24, and a policy function 26. [0031] It is assumed for the procedure of Figure 2 that the wireless device 16 is attached to the RAN 12 and that a PDU session is established, the wireless device 16 is in Radio Resource Control (RRC) inactive connected state, and no UE context is currently established in the UP functions 24.

[0032] Step 100: An application server in a data network 28 transfers a mobile terminated PDU towards the UP function 24. In case of IP, the

destination address is the IP address of the wireless device 16. Note that this solution relies on the regular PDU session concept and any solution for non-IP PDU types thus applies also for this solution, i.e. no separate solution for non-IP is needed.

[0033] Step 102: The UP function 24 receives the downlink PDU and, as the UE context does not exist, the UP function 24 obtains the UE context from the proper CP function 22. In case of IP, the IP address is used to derive the proper Session Management (SM) function (i.e., the control function (separated from the UP function)). In case a UE context already exists in the UP function 24, this step is omitted.

[0034] Step 104: The UP function 24 encapsulates the PDU into a tunnel protocol header and forwards the PDU to the AN, and more specifically the radio access node 14 identified by the AN tunnel identifier part of the UE context. The UP function 24 may enforce, e.g., Quality of Service (QoS) marking, rate limiting, charging, etc.

[0035] Step 106: When the radio access node 14 receives the PDU, the wireless device 16 and the radio access node 14 transition to RRC active state.

[0036] Step 108: The radio access node 14 forwards the PDU to the wireless device 16.

[0037] Step 1 10: After the radio access node 14 has forwarded the PDU, the radio access node 14 initiates the transition to RRC inactive state with the wireless device 16, e.g. due to wireless device 16 inactivity during a time period. The wireless device 16 is moved to RRC inactive connected state.

[0038] Step 1 12: The UP function 24 may remove the UE context due to, e.g., inactivity. [0039] In case the UP function 24 is accessible from the Internet, the UE context may need to be kept in the UP function 24 for longer times to avoid unnecessary signaling between UP and CP in step 102 (e.g., due to Denial-of- Service (DoS) attacks in which case the signaling should not be allowed to propagate into the network). In this case, the CP function 22 can instruct the UP function 24 to not release UE context or instruct the UP function 24 to use a longer inactivity timer.

[0040] Figure 3 illustrates how a downlink PDU is transferred from the data network 28 to a battery saving wireless device 16 that sends data infrequently according to some embodiments of the present disclosure. Note that while a number of "steps" are illustrated, these "steps" are actions that can be performed in any desired order unless otherwise stated or required. Further, Figure 3 illustrates a number of CN functions that are implemented in the CN 18 via one or more of the CN nodes 20. In particular, Figure 3 illustrates a CP function 22, a UP function 24, and a policy function 26.

[0041] It is assumed for this procedure that the wireless device 16 is attached to the RAN 12 and that a PDU session is established.

[0042] Step 200: The wireless device 16 (e.g., UE) enters RRC Idle. In this example, prior to entering RRC Idle, the wireless device 16 was connected to a source radio access node 14-1 .

[0043] Step 202: The state change is notified to the CN 18 (i.e., to the CP function 22) as in Release 13 in the S1AP suspend procedure. NG Mobility Management (MM) enters Idle. In this example, the source radio access node 14-1 communicates with the CP function 22 to notify the CN 18 of this state change (i.e., notify the CN 18, or more specifically the CP function 22, that the wireless device 16 is now unreachable).

[0044] Step 204: An application server in the data network 28 transfers a MT PDU towards the UP function(s) 24. In case of IP, the destination address is the IP address of the wireless device 16.

[0045] Step 206: If the UE context does not exist, the UP function(s) 24 obtains the UE context for the wireless device 16 from the proper CP function(s) 22. In case of IP, the IP address is used to derive the proper SM function. In the case of non-IP, some other device or user identifier received in the packet is used to derive the proper SM function. In case a UE context already exists in the UP function(s) 24, this step is omitted.

[0046] Step 208: In case the wireless device 16 is subject to functionality similar to Release 13 PSM, the downlink PDU is buffered in the CN 18, the CN 18 waiting for the AN to indicate the wireless device 16 is reachable, e.g., by means of a Release 13 S1AP resume procedure, before proceeding to forward the PDU to the AN. For example, the CP function(s) 22 and/or the UP function(s) 24, either together or alone, buffer the PDU, e.g., in a respective CN node 20. The CN 18 buffers the PDU until the CN 18 receives an indication that the wireless device 16 is reachable. For example, the wireless device 16 may be considered "reachable" when the wireless device 16 wakes up from PSM to check for (i.e., to listen for) paging, e.g., according to a configured DRX cycle.

[0047] Step 210: For long DRX, the CP function 22 will be able to calculate the paging occasions assuming the CN CP function 22 is to some extent synchronized with the AN. The CP function 22 pages the wireless device 16. This paging may be performed in the conventional manner. For example, the CP function 22 may initiate the transmission of a paging message to the wireless device 16 by, e.g., the radio access nodes 14 in a tracking area in which the wireless device 16 is located. In this example, the wireless device 16 is located within a tracking area that includes at least a target radio access node 14-2. Note that the target radio access node 14-2 may be the same as the source radio access node 14-1 or different than the source radio access node 14-1 depending on, e.g., the mobility of the wireless device 16.

[0048] Step 212: In response to the paging, the wireless device 16 transmits a notification to, in this example, the target radio access node 14-2 that the wireless device 16 is now reachable. For example, the wireless device 16 may transmit a paging response that indicates to the target radio access node 14-2 that the wireless device 16 is now reachable. The target radio access node 14-2 provides a notification to the CN 18, and more specifically to the CP function 22 in this example, that the wireless device 16 is reachable. In other words, the AN indicates to the CN 18 that the wireless device 16 is reachable, e.g. using the Release 13 S1AP resume procedure.

[0049] Step 214: The UP path between the AN and the UP function(s) 24 (specifically between the target radio access node 14-2 and the UP function(s) 24) is set up. The UP function(s) 24 is updated with the AN tunnel identifier for the PDU session.

[0050] Step 216: The PDU is forwarded to the AN (specifically to the radio access node 14, which in this example is the target radio access node 14-2) identified by the AN tunnel identifier part of the UE context. The UP function 24 may enforce, e.g., QoS marking, rate limiting, charging, etc.

[0051] Figure 4 is a schematic block diagram of the wireless device 16 according to some embodiments of the present disclosure. As illustrated, the wireless device 16 includes circuitry 22 comprising one or more processors 24 (e.g., Central Processing Units (CPUs), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), and/or the like) and memory 26. The wireless device 16 also includes one or more transceivers 28 each including one or more transmitters 30 and one or more receivers 32 coupled to one or more antennas 34. In some embodiments, the functionality of the wireless device 16 described above may be fully or partially implemented in software that is, e.g., stored in the memory 26 and executed by the processor(s) 24.

[0052] 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 wireless device 16 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing 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). [0053] Figure 5 is a schematic block diagram of the wireless device 16 according to some other embodiments of the present disclosure. The wireless device 16 includes one or more modules 36, each of which is implemented in software. The module(s) 36 provide the functionality of the wireless device 16 described herein.

[0054] Figure 6 is a schematic block diagram of a network node 38 (e.g., a radio access node 14 or a CN node 20) according to some embodiments of the present disclosure. As illustrated, the network node 38 includes a control system 40 that includes circuitry comprising one or more processors 42 (e.g., CPUs, ASICs, FPGAs, and/or the like) and memory 44. The control system 40 also includes a network interface 46. In embodiments in which the network node 38 is a radio access node 14, the network node 38 also includes one or more radio units 48 that each include one or more transmitters 50 and one or more receivers 52 coupled to one or more antennas 54. In some embodiments, the functionality of the network node 38 (e.g., the functionality of the radio access node 14 or the functionality of a CN node 20 implementing, e.g., the CP function 22 and/or the UP function 24) described above may be fully or partially implemented in software that is, e.g., stored in the memory 44 and executed by the processor(s) 42.

[0055] Figure 7 is a schematic block diagram that illustrates a virtualized embodiment of the network node 38 (e.g., the radio access node 14 or a CN node 20 implementing the CP function 22 and/or the UP function 24) according to some embodiments of the present disclosure. As used herein, a "virtualized" network node 38 is a network node 38 in which at least a portion of the functionality of the network node 38 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, the network node 38 optionally includes the control system 40, as described with respect to Figure 6. In addition, if the network node 38 is a radio access node 14, the network node 38 also includes the one or more radio units 48, as described with respect to Figure 6. The control system 40 (if present) is connected to one or more processing nodes 56 coupled to or included as part of a network(s) 58 via the network interface 46. Alternatively, if the control system 40 is not present, the one or more radio units 48 (if present) are connected to the one or more processing nodes 56 via a network interface(s). Alternatively, all of the functionality of the network node 38 described herein may be implemented in the processing nodes 56 (i.e., the network node 38 does not include the control system 40 or the radio unit(s) 48). Each processing node 56 includes one or more processors 60 (e.g., CPUs, ASICs, FPGAs, and/or the like), memory 62, and a network interface 64.

[0056] In this example, functions 66 of the network node 38 described herein are implemented at the one or more processing nodes 56 or distributed across the control system 40 (if present) and the one or more processing nodes 56 in any desired manner. In some particular embodiments, some or all of the functions 66 of the network node 38 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) 56. As will be appreciated by one of ordinary skill in the art, additional signaling or communication between the processing node(s) 56 and the control system 40 (if present) or alternatively the radio unit(s) 48 (if present) is used in order to carry out at least some of the desired functions. Notably, in some embodiments, the control system 40 may not be included, in which case the radio unit(s) 48 (if present) communicates directly with the processing node(s) 56 via an appropriate network interface(s).

[0057] 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 network node 38 or a processing node 56 according to any of the embodiments described herein is provided. In some embodiments, a carrier containing 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).

[0058] Figure 8 is a schematic block diagram of the network node 38 (e.g., the radio access node 14 or a CN node 20 implementing the CP function 22 and/or the UP function 24) according to some other embodiments of the present disclosure. The network node 38 includes one or more modules 68, each of which is implemented in software. The module(s) 68 provide the functionality of the network node 38 described herein.

Example Embodiments

[0059] While not being limited thereto, some example embodiments of the present disclosure are provided below. 1 . A method of operation of one or more core network nodes (20) in a core network (18) of a wireless communications system (10), comprising:

receiving (204) data destined for a wireless device (16), the wireless device (16) being unreachable via a radio access network (12);

buffering (208) the data in the core network (18) until the wireless device (16) is indicated as being reachable via the radio access network (12); and

upon the wireless device (16) being indicated as being reachable, forwarding (216) the data to the wireless device (16) via the radio access network (12). 2. The method of embodiment 1 further comprising, prior to receiving (204) the data, receiving (202) from the radio access network (12), an indication that the wireless device (16) is unreachable via the radio access network (12).

3. The method of embodiment 1 or 2 wherein the wireless device (16) is indicated as unreachable while the wireless device (16) is operating in a power savings mode.

4. The method of any one of embodiments 1 to 3 further comprising, upon buffering the data, paging (210) the wireless device (16). 5. The method of embodiment 4 wherein paging (210) the wireless device (16) comprises paging (210) the wireless device 16 during a paging occasion configured for the wireless device (16). 6. The method of embodiment 5 wherein the wireless device (16) is indicated as unreachable while the wireless device (16) is operating in a power savings mode, and the paging occasion is a paging occasion configured for the wireless device (16) during a period of time in which the wireless device (16) wakes up from power savings mode to check for paging.

7. The method of any one of embodiments 1 to 6 further comprising, in response to paging (210) the wireless device (16), receiving (212), from a radio access node (14), an indication that the wireless device (16) is reachable via the radio access network (12).

8. The method of any one of embodiments 1 to 7 further comprising, upon receiving (212) the indication that the wireless device (16) is reachable, performing (214) setup of a user plane path between the radio access node (14) and a user plane function (24) of the core network (18).

9. The method of any one of embodiments 1 to 8 further comprising, upon receiving (204) the data, performing (206) user plane setup for the wireless device (16) by obtaining a wireless device (16) context for the wireless device (16).

10. A core network node (20) in a core network (18) of a wireless

communications system (10), the core network node (20) adapted to perform the method of any one of embodiments 1 to 9. 1 1 . A core network (18) of a wireless communications system (10), the core network (18) adapted to perform the method of any one of embodiments 1 to 9. 12. A core network node (20) in a core network (18) of a wireless

communications system (10), the core network node (20) comprising one or more modules (68) operable to perform the method of any one of embodiments 1 to 9.

[0060] The following acronyms are used throughout this disclosure.

• 3GPP Third Generation Partnership Project

• 5G Fifth Generation

• ACK Acknowledgement

• AN Access Network

• AS Application Server

• ASIC Application Specific Integrated Circuit

• CN Core Network

• CP Control Plane

• CPU Central Processing Unit

• DoS Denial-of-Service

• DRX Discontinuous Reception

• eDRX Extended Discontinuous Reception

• eNB Enhanced or Evolved Node B

• FPGA Field Programmable Gate Array

• IP Internet Protocol

• LTE Long Term Evolution

• MM Mobility Management

• MME Mobility Management Entity

• MT Mobile Terminating

• MTC Machine Type Communication

• NG Next Generation

• PDN Packet Data Network

• PDU Packet Data Unit P-GW Packet Data Network Gateway

PSM Power Saving Mode

QoS Quality of Service

RAN Radio Access Network

RRC Radio Resource Control

SCEF Service Capability Exposure Function

S-GW Serving Gateway

SM Session Management

TR Technical Report

TS Technical Specification

UE User Equipment

UP User Plane

[0061] Those skilled in the art will recognize improvements and modifications to the embodiments of the present disclosure. All such improvements and modifications are considered within the scope of the concepts disclosed herein.