EP3424262A1

EP3424262A1 - Cellular internet of things data transfer via a mobility management entity

Info

Publication number: EP3424262A1
Application number: EP17710643.2A
Authority: EP
Inventors: Robert Zaus; Vivek Gupta; Puneet Jain
Original assignee: Intel IP Corp
Current assignee: Intel Corp
Priority date: 2016-03-03
Filing date: 2017-02-24
Publication date: 2019-01-09
Also published as: WO2017151437A1; TWI721119B; TW201735673A

Abstract

Technology for Internet of Things (CIoT) data transfer via a mobility management entity within a wireless communication network is disclosed. A user equipment (UE) can include processors configured to encapsulate user data in an information element into an evolved packet system (EPS) session management (ESM) data 5 transport message to transfer the user data via the control plane to a mobility management entity (MME). An EPS bearer identity associated with the user data in the ESM data transport message can be included with the ESM data transport message. The ESM data transport message can be encoded for transmission to the MME via the control plane. The MME can identify a 10 PDN connection associated with the EPS bearer ID and forward the user data based on the EPS bearer ID.

Description

CELLULAR INTERNET OF THINGS DATA TRANSFER VIA A MOBILITY

MANAGEMENT ENTITY

BACKGROUND

[0001] Wireless mobile communication technology uses various standards and protocols to transmit data between a node (e.g., a transmission station such as an eNodeB) and a wireless device (e.g., a mobile device). Some wireless devices communicate using orthogonal frequency-division multiple access (OFDMA) in a downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in an uplink (UL) transmission. Standards and protocols that use orthogonal frequency-division multiplexing (OFDM) for signal transmission include the third generation partnership project (3GPP) long term evolution (LTE), the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard (e.g., 802.16e, 802.16m), which is commonly known to industry groups as WiMAX (Worldwide interoperability for Microwave Access), and the IEEE 802.11 standard, which is commonly known to industry groups as Wi-Fi. In

3GPP radio access network (RAN) LTE systems, the node can be a an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) which communicates with the wireless device, known as a user equipment (UE). The downlink (DL) transmission can be a communication from the node to the wireless device (e.g., UE), and the uplink (UL) transmission can be a communication from the wireless device to the node.

[0002] Increasingly, cellular networks are being adapted to facilitate their use by Machine-to-Machine (M2M) type devices. The terms Machine-to-Machine (M2M) and Machine-Type Communications (MTC) are used to describe use cases and illustrate the diverse characteristics of machine type communication services. M2M and MTC devices can be designed to work within wireless networks to enable an "internet of things".

BRIEF DESCRIPTION OF THE DRAWINGS

[0003] Features and advantages of the disclosure will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the disclosure; and, wherein: [0004] FIG. 1 illustrates a mobile communication network within a cell in accordance with an example;

[0005] FIG. 2 illustrates a diagram of protocol architecture for a MS supporting EPS services in accordance with an example;

[0006] FIG. 3 A illustrates a diagram of Mobile Originated (MO) Data Transport in Control Plane CIoT EPS optimization with P-GW connectivity in accordance with an example;

[0007] FIG. 3B illustrates a diagram of Mobile Terminated (MT) Data Transport in Control Plane CIoT EPS optimization with P-GW connectivity in accordance with an example;

[0008] FIG. 4 illustrates a table of a data service request message with an non-access stratum (NAS) key set identifier (KSI) included in a spare half octet in accordance with an example;

[0009] FIG. 5 illustrates a table of a security protected initial non-access stratum (NAS) message in accordance with an example;

[0010] FIG. 6 illustrates a table of an enhanced security protected non-access stratum (NAS) message in accordance with an example;

[0011] FIG. 7 illustrates a table of an evolved packet system (EPS) session management (ESM) data transport message in accordance with an example;

[0012] FIG. 8 illustrates a table of an organization structure for a plain non-access stratum (NAS) message in accordance with an example;

[0013] FIG. 9 illustrates a table of an organization structure for a security protected non- access stratum (NAS) message in accordance with an example;

[0014] FIG10 illustrates a table of an organization structure for a security protected initial non-access stratum (NAS) message in accordance with an example;

[0015] FIG.11 illustrates a table of an organization structure for an enhanced security protected non-access stratum (NAS) message in accordance with an example;

[0016] FIG.12 illustrates a table of a security header type information element (IE) in accordance with an example; [0017] FIG.13 illustrates a table of various message types for evolved packet system (EPS) mobility management in accordance with an example;

[0018] FIG.14 illustrates a table of various message types for evolved packet system (EPS) session management in accordance with an example;

[0019] FIG.15 illustrates a table of a data service type information element (IE) in accordance with an example;

[0020] FIG.16 illustrates a additional table of a data service type information element (IE) with additional information in accordance with an example;

[0021] FIG.17 illustrates a table of an additional information element (IE) in accordance with an example;

[0022] FIG.18 illustrates a table of an alternative for an additional information element (IE) in accordance with an example;

[0023] FIG.19 illustrates a table of a third alternative for an additional information element (IE) in accordance with an example;

[0024] FIG.20 illustrates a table of a user data container information element in accordance with an example;

[0025] FIG. 21 depicts functionality of a user equipment (UE) operable to communicate with a wireless communication network, using a scheduling request transmission for a cmWave system in accordance with an example;

[0026] FIG. 22 depicts additional functionality of a user equipment (UE) to

communicate within a wireless communication network, for using a scheduling request transmission for a cmWave system in accordance with an example;

[0027] FIG. 23 depicts functionality of an eNodeB operable to communicate with a user equipment (UE), using a scheduling request transmission for a cmWave system in accordance with an example;

[0028] FIG. 24 depicts additional functionality of a Cellular Internet of Things (CIoT) enabled user equipment (UE) to communicate with a mobility management entity (MME) within a wireless communication network, for transfer of user data via a control plane in accordance with an example; [0029] FIG. 25 depicts additional functionality of Cellular Internet of Things (CIoT) enabled mobile management entity (MME) to communicate with user equipment (UE) within a wireless communication network, for transfer of user data via a control plane in accordance with an example;

[0030] FIG. 26 illustrates a diagram of example components of a wireless device (e.g. User Equipment "UE") in accordance with an example;

[0031] FIG. 27 illustrates a diagram of example components of a User Equipment (UE) device in accordance with an example;

[0032] FIG. 28 illustrates a diagram of example interfaces of baseband circuitry in accordance with an example; and

[0033] FIG. 29 illustrates a diagram of a node (e.g., eNB) and wireless device (e.g., UE) in accordance with an example.

[0034] Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended.

DETAILED DESCRIPTION

[0035] Before the present technology is disclosed and described, it is to be understood that this technology is not limited to the particular structures, process actions, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular examples only and is not intended to be limiting. The same reference numerals in different drawings represent the same element. Numbers provided in flow charts and processes are provided for clarity in illustrating actions and operations and do not necessarily indicate a particular order or sequence.

EXAMPLE EMBODIMENTS

[0036] An initial overview of technology embodiments is provided below and then specific technology embodiments are described in further detail later. This initial summary is intended to aid readers in understanding the technology more quickly but is not intended to identify key features or essential features of the technology nor is it intended to limit the scope of the claimed subject matter.

[0037] Machine type communication (MTC) represents a significant growth opportunity for third generation partnership project (3GPP) next generation wireless communication systems. To support an Internet of Things (IoT), 3GPP systems are constrained to address usage scenarios with IoT devices that are power efficient (e.g., having battery life of several years) and can be employed in challenging coverage conditions (e.g., outdoors, indoors, buildings, basements, etc.). Also, IoT devices for 3GPP communications can be inexpensive in order to be deployed on a mass scale while being disposable.

[0038] Accordingly, the present technology provides support of efficient handling of frequent and infrequent small data transmissions with minimized computing overhead for system signalling without compromising security, supporting power consumption optimization and paging optimizations. Also, the present technology can provide support for increasing efficiency of mobility and session management procedures.

[0039] In one aspect, the present technology provides for Cellular Internet of Things (CIoT) data transfer via a mobility management entity (MME) within a wireless communication network. A user equipment (UE) can process, for transmission of user data to an MME via a control plane, a control plane service request message having an evolved packet system (EPS) session management (ESM) message container Information element (IE) containing an ESM data transport message, that includes the user data. The ESM data transport message can enable the MME to identify an EPS bearer Identification (ID) that is associated with the data.

[0040] In one aspect, the present technology provides for a data transfer procedure via a mobility management entity (MME). A unique ID may be employed to distinguish connections between the UE and the MME in order to correctly deliver data, particularly since multiple connections (UE-service capability exposure framework 'UE-SCEF" connections and packet data network "PDN" connections) can co-exist. In one aspect, the unique ID can be an evolved packet system (EPS) bearer ID.

[0041] The PDU used to transfer data via an MME may be embedded and may be encrypted. However, if the EPS bearer ID is used as one of the input parameters in security operations, the EPS bearer ID should not be encrypted to allow the EPS bearer ID to be used as an input in the security operations. In one aspect, the data transferred may be embedded in a non-access stratum (NAS) message.

[0042] In one aspect, the NAS message carrying the embedded data can be similar to an initial NAS message. This means that the message header of the NAS message carrying the embedded data can be constrained to contain a key set identifier (KSI) in order to handle a situation where the UE and a network are not synchronized (e.g., the UE and the network have become "out-of-sync") regarding the EPS security context available in the UE and in the network.

[0043] Moreover, an additional message information element (IE) can be used with an octet containing the EPS bearer ID and the key set identifier (KSI) in the NAS message. A security protected NAS message type can be modified and a security header type can be implemented to protect the EPS bearer ID and KSI.

[0044] In one aspect, an enhanced ESM message containing the EPS bearer ID can be used. ANAS message container having a maximum length of substantially 250 Octets can be sufficient under an assumption that a segmentation/assembly of user data can be performed by the MME and the UE lower layer (e.g., a packet of 1600 Octets can be divided into 8x200octets). In one aspect, the maximum length can be 65 kilobytes (KB), with an assumption that user data packets can be up to 1500 octets and can be sent without segmentation.

[0045] In one aspect, a control plane service request NAS message having an evolved packet system (EPS) session management (ESM) message container Information element (IE) can be processed, for transmission to a mobility management entity (MME) via the eNodeB. The control plane service request message can contain an ESM data transport message that includes user data. In one example, the ESM data transport message can be encapsulated or included in a NAS message and sent from the UE to the MME. The ESM data transport message can enable the MME to identify an EPS bearer Identification (ID) that is associated with the user data.

[0046] Accordingly, the present technology provides for a NAS procedure and/or message in support of cellular Internet of Things (CIoT) data transfer via the MME. The present technology provides a modification of the protocol specification 3GPP TS 24.301 Release 13.4.0 and updates to relevant EPS mobility management and EPS session management service request procedures to provide a mechanism for data transfer in a NAS PDU via the MME, while considering the security aspects for 3GPP devices. The Service Request procedure is enhanced to handle UE initiated and Network initiated transport of user data via a control plane procedure. A control plane service request message is defined to enable the UE to transfer data in an EPS Mobility Management (EMM)-IDLE mode and to respond to paging when paged by the network, e.g., for the delivery of data. A new Service Accept message is defined to terminate the Service Request procedure for certain use cases. As such, CIoT data delivery can occur via a control plane.

[0047] FIG. 1 illustrates a mobile communication network within a cell 100 having an evolved node B (eNB or eNodeB) with a mobile device. FIG. 1 illustrates an eNB 104 that can be associated with an anchor cell, macro cell or primary cell. Also, the cell 100 can include a mobile device, such as, for example, a User Equipment (UE or UEs) 108 that can be in communication with the eNB 104. The eNB 104 can be a station that communicates with the UE 108 and can also be referred to as a base station, a node B, an access point, and the like. In one example, the eNB 104 can be a high transmission power eNB, such as a macro eNB, for coverage and connectivity. The eNB 104 can be responsible for mobility and can also be responsible for radio resource control (RRC) signaling. The UE or UEs 108 can be supported by the macro eNB 104. The eNB 104 can provide communication coverage for a particular geographic area. In 3GPP, the term "cell" can refer to a particular geographic coverage area of eNB and/or an eNB subsystem serving the coverage area with an associated carrier frequency and a frequency bandwidth, depending on the context in which the term is used.

[0048] FIG. 2 illustrates a diagram of a protocol architecture for a UE or a mobile station (MS) supporting EPS services in accordance with an example. That is, FIG. 2 depicts three sublayers for EPS packet switched (PS) domain services. The Access Stratum (AS) sublayer provides services to the mobility management (MM) sublayer. The MM sublayer provides services to the entities of the Connection Management (CM) sublayer. The non-access stratum (NAS) comprises the MM sublayer and the CM sublayer. The MM sublayer further includes one EPS mobility management (EMM) entity. The CM sublayer can include one or more evolved packet system (EPS) session management (ESM) entities. The ESM entity can provide services to the Bearer Control (BC) entity and use services of the MM sublayer. The BC entity can hide the concepts of radio bearers that can be established/released while an EPS bearer context is active. If uplink data in the terminal is to be sent, and radio bearers have been released, the BC entity can trigger a service request procedure in EMM. Also, one or more packet data convergence protocol (PDCP) service access points (SAP) (e.g., PDCP 1-SAP, PDCP 2- SAP, and PDCP 3-SAP), other SAPs (e.g., RBMAS-SAP, ESMREG-SAP, EMMREG- SAP, and EMMAS-SAP) and parameters used to multiplex transactions via a SAP (e.g., EBI, PD) are depicted.

[0049] In one aspect, upon receipt of a request to transfer user data, an application (not shown) which can be assumed to be located above the "modem" (or "mobile

termination"), i.e. in upper layers that are above the protocol layers shown in FIG. 2, can deliver a user data packet destined to a radio bearer (e.g., RBI) via a RB service access point (SAP) (e.g.,RBl-SAP). If the BC entity determines that the UE is in EMM-Idle mode (i.e. no RRC connection and no radio bearers have been established), the BC entity can send a request to the NAS to initiate a Service Request procedure and transfer the user data via the Control Plane, i.e., via signaling radio bearer. Thus, the present technology provides improvement over the current state of the art where the request was directed towards the EMM, and the EMM initiated the procedure to establish all radio bearers, i.e., data radio bearers and signaling radio bearers.

[0050] In one aspect, the BC entity can decide that the user data can be sent via the Control Plane (instead of via User Plane). The BC entity can forward the user data to the ESM with a request to send the data to the network. The ESM can encapsulate the user data packet in a transport message, such as an ESM DATA TRANSPORT message, and forward the message to the EMM with a request to send the data to the network. The EMM can encapsulate or include the ESM DATA TRANSPORT message in a CONTROL PLANE SERVICE REQUEST message and request the RRC to establish an RRC connection. During the RRC connection establishment, the UE can transfer the

CONTROL PLANE SERVICE REQUEST message to the eNB.

[0051] As used herein the term encapsulate refers to the process of modularizing data for transmission using a predetermined transmission protocol. Data is typically encapsulated in a physical data unit (PDU). Header, and sometimes footer or trailer, information can be added that contains control information used to transmit and decode the encapsulated data. The term encapsulate, as used herein, can refer to both the data in the PDU, as well as the header and/or trailer information.

[0052] In one aspect, the CONTROL PLANE SERVICE REQUEST message can be sent in a connected mode to request establishment of user plane bearers, or it can include an SMS message instead of an ESM message.

[0053] In one aspect, the BC can determine not to forward the user data itself, but rather a pointer to the user data. In an additional aspect, an application itself can decide that the user data is to be delivered via the Control Plane and can deliver the user data via a new service access point directly to the ESM. It should be noted that UE-internal

communication can refer to a request from "upper layers" where upper layers can be the application itself, an operating system of the application processor on which the application is running, a transmission control protocol/internet protocol (TCP/IP) socket on the application processor, etc. As such, a request to transfer user data can be the delivery of the user data packet, or the request can which may contain additional information such as information for the BC, which can also be used as a criterion to decide to transfer the data via Control Plane.. Also, an application, or more generally, the upper layers may initiate the request to transfer the user data.

[0054] Turning now to FIG. 's 3A-3B, where Mobile Originated (MO) Data Transport in Control Plane CIoT EPS optimization with P-GW connectivity and Mobile Terminated (MT) Data Transport in Control Plane CIoT EPS optimization with P-GW connectivity is depicted.

[0055] However, for purposes of the present technology, operations 0-2 and 11-12 of FIG. 3 A, and operations 5-6 and 13-16 of FIG. 3B are most relevant. Each of the additional operations of FIG. 's 3 A-3B can be implemented and may be applicable but not essential for purposes of the present technology. For example, in FIG. 3A, the relevant portions for the present technology can begin at 0 where the UE can be in an EPS Connection Management (ECM)-IDLE state (which can also be referred to as "EMM-Idle mode"). In operation (1), the UE establishes an RRC connection and can send as part of it as an integrity protected NAS PDU. The NAS PDU can carry the EPS Bearer ID and encrypted Uplink Data. E.g. the NAS PDU may be a control plane service request message which can contain an encrypted ESM data transport message that includes the uplink user data. The UE may also indicate in a Release Assistance Information in the NAS PDU whether Downlink data transmission (e.g. Acknowledgement or response to Uplink data) subsequent to the Uplink Data transmission is expected or not. If the NAS PDU is a control plane service request message containing an ESM data transport message, the Release Assistance Information may also be included in the ESM data transport message. In operation (2), the NAS PDU sent in operation 1 is relayed to the MME by the eNodeB using a Sl-AP Initial UE message. To assist the MME in any NAS PDU retransmission strategies, the eNB can indicate the UE's Coverage Level to the MME.

[0056] In one aspect, each of the following can also be performed in FIG. 3A. After operation 2, at operation 3, the MME can check the integrity of the incoming NAS PDU and decrypt the data it contains. The MME can decompress the IP header if header compression applies to the packet data network (PDN) connection. The MME can perform (and the UE can respond to) any security related procedures. Operations 4 to 9 can continue in parallel to this, however, operations 10 and 11 can await completion of all security related procedures. In operation 4, if the Sl l-U connection is not established, the MME can send a Modify Bearer Request message (MME address, MME TEID DL,

Delay Downlink Packet Notification Request, radio access technology (RAT) Type) to the Serving gateway (GW).

[0057] In operation 5, if the RAT Type has changed compared to the last reported RAT Type or if the UE's Location and/or Info IEs and/or UE Time Zone and Serving Network id are present in operation 4, the Serving GW can send the Modify Bearer Request message (RAT Type) to the PDN GW. In operation 6, the PDN GW can send the Modify Bearer Response to the Serving GW. In operation 7, if a Modify Bearer Request message was sent at operation 4, the Serving GW can return a Modify Bearer Response (Serving GW address and tunneling endpoint identifier (TEID) for uplink traffic) to the MME as a response to a Modify Bearer Request message. In operation 8, the MME can send Uplink data to the P-GW via the S-GW. The P-GW can forward the Uplink data to an application server in a packed data network (PDN) (not shown). Operations 9-14 may be performed if the P-GW receives Downlink data from the PDN, e.g., an Acknowledgement or response to the Uplink data from the application server (not shown). I.e. operations 9-14 show an example of a Mobile Terminated (MT) Data Transport in Control Plane CIoT EPS optimization with P-GW connectivity for a UE which is in EMM-Connected mode. In operation 9, the P-GW can send downlink data to the MME via the S-GW. In operation 10, the MME can encrypt and integrity protect the Downlink data. In operation 11, downlink data are encapsulated in a NAS PDU and sent to the eNB in an Sl-AP

Downlink Message. E.g. the NAS PDU may be an encrypted ESM data transport message that includes the downlink user data. In operation 12, the eNB can send an RRC

Downlink data message including the downlink data encapsulated in the NAS PDU. If, in operation, 11 the Sl-AP message with the NAS DATA PDU is followed by a SI UE Context Release Command, then operation 14 can be completed promptly after the Downlink Data transmission of the NAS PDU to the UE is complete at the eNB, and the eNB does not have to perform operation 13. If header compression is applied to the PDN, the UE can perform header decompression to rebuild the internet protocol (IP) header. In operation 13, if no NAS PDU activity exists for a while, the eNB can start an SI release in operation 14. In operation 14, an S I release procedure may be performed.

[0058] As depicted in FIG. 3B, the relevant operations for MT data transport in NAS PDUs can be in operations 5-6 and 13-14. That is, in operations 5-6, the UE is in the ECM-IDLE state. Upon reception of a paging indication, the UE can send a UE triggered Service Request NAS message over an RRC Connection request and the Sl-AP initial message. The Service Request NAS message, when C-IoT Control Plane optimization applies, does not trigger Data radio bearer establishment by the MME and the MME can immediately send Downlink Data it receives using a NAS PDU to the eNodeB. The MME can supervise the paging procedure with a timer. If the MME receives no response from the UE to the Paging Request message, it may repeat the paging according to any applicable paging strategy described in operation 3.

[0059] If the MME receives no response from the UE after this paging repetition procedure, the MME can use the Downlink Data Notification Reject message to notify the Serving GW about the paging failure (or, equivalently, if the buffering is in the MME, the MME can simply discard data for the UE locally), unless the MME is aware of an ongoing MM procedure that prevents the UE from responding, i.e. the MME received a Context Request message indicating that the UE performs a tracking area update (TAU) with another MME. When a Downlink Data Notification Reject message is received, the Serving GW can delete the buffered packet(s). The Serving GW may invoke the procedure P-GW Pause of Charging if the UE is in ECM IDLE and the PDN GW has enabled the "PDN charging pause" feature. If buffering is in the MME, Pause Charging is triggered by the MME via a Release Access Bearer Request to the S-GW including an "Abnormal Release of Radio Link" cause, which releases the S l l-U.

[0060] Thus, in FIG. 's 3A-3B, the present technology provides a specific structure for a NAS Data PDU, comprising an ESM message encapsulated or included in an EMM message, as shown in FIG. 3 A, where the same ESM message can be used as for the NAS Data PDU in FIG. 3B, operations 15-16, and as for the network initiated case illustrated in FIG. 3B, operations 13-14, and in FIG. 3A, operations 11-12. That is, as the transfer of the user data is related to a certain EPS bearer - characterized by a certain EPS bearer identity - the ESM layer can be involved in the transfer also for the UE initiated scenario of FIG. 3 A. On the other hand, since the UE is supposed to send only a single NAS message and the first NAS message is usually an EMM message, the present technology encapsulates or includes the ESM message carrying the user data in the EMM message. This will be described more fully in the proceeding paragraphs.

Transport of user data in NAS PDU via MME procedure

[0061] In one aspect, during an evolved packet system (EPS) attach procedure, a network can activate a default EPS bearer context (i.e. if the UE requests packet data network "PDN" connectivity in the attach request). Additionally, a network can activate one or several dedicated EPS bearer contexts in parallel for PDN connections of an IP PDN type. To this purpose, EPS session management messages for a default EPS bearer context activation can be transmitted in an information element in the EPS mobility management messages. In this case, the UE and the network can execute the attach procedure, the default EPS bearer context activation procedure, and the dedicated EPS bearer context activation procedure in parallel. The UE and network can complete a combined default EPS bearer context activation procedure and the attach procedure before the dedicated EPS bearer context activation procedure is completed. The success of the attach procedure is dependent on the success of the default EPS bearer context activation procedure. If the attach procedure fails, then the ESM procedures also fail.

[0062] A UE using EPS services with a control plane CIoT EPS optimization can initiate transport of user data via a control plane. Control plane CIoT EPS optimization can comprise signaling optimizations to enable efficient transport of user data (IP, non-IP or SMS) over the control plane via the MME, including optional header compression of IP data. For this purpose, a UE in an evolved packet system (EPS) mobility management (EMM)-IDLE mode can initiate the service request procedure and transmit an ESM data transport message in an information element in the control plane service request message. Except for the attach procedure and the service request procedure, during EMM procedures the MME can suspend the transmission of ESM messages. During the service request procedure, the MME may suspend the transmission of ESM messages. Except for the attach procedure and the service request procedure for UE initiated transport of user data via the control plane, during EMM procedures the UE can suspend the transmission of ESM messages.

[0063] In one aspect, the UE initiated transport of user data can be performed in an

NAS PDU via the MME. It should be noted that one of the purposes of transporting user data in a NAS PDU via an MME procedure is to carry user data encapsulated in NAS messages between the UE and the MME and the MME and UE on the control plane. The procedure may be initiated by the UE or the network.

[0064] Upon receipt of a request to transfer user data via the MME, if the UE is in EMM-IDLE mode, the EMM entity in the UE can initiate the procedure by sending a control plane service request (which can also be referred to as a "data service request" or, equivalently, a "control plane service request") message including an ESM container message IE which contains the data to be sent in the ESM data transport message. The data service type of the control plane service request message can indicate "mobile originating request" for UE initiated procedures.

[0065] When receiving the ESM data transport message, the MME can identify the bearer (e.g., the service capability exposure function "SCEF" connection) on which to transfer the user data inside a core network based on the EPS bearer identity included in ESM data transport message and then forward the contents of the user data container IE accordingly. [0066] The UE can send the control plane service request message as part of a Security protected initial NAS message. The security header type of the Security protected initial NAS message can indicate "Integrity protected and ciphered initial NAS message", as indicated in FIG. 12. The UE can provide an indication in an IE, such as the "Additional Information" IE or the "Release Assistance Indication" IE in the Control plane service request message indicating whether downlink data subsequent to the Uplink Data Transmission is expected or not. In one aspect, the additional information or "release assistance indication" can be an information element included in the ESM data transport message rather than the control plane service request. As used herein, "additional information" and "release assistance indication" can be used interchangeably.

[0067] Upon receipt of a request from one or more upper layers associated with the UE (e.g. an application layer within the UE) to transfer user data via the control plane, if the UE is in the EMM-CONNECTED mode, the ESM entity in the UE can initiate the procedure by sending a stand-alone ESM DATA TRANSPORT message.

Network initiated transport of user data in NAS PDU via MME

[0068] Upon receipt of a paging message indicating a "transfer user data via the control plane", the UE can respond with a Control plane service request message. The data service type of the Control plane service request message can indicate a "mobile terminating request". The UE can send the Control plane service request message as part of a Security protected initial NAS message. The security header type of the Security protected initial NAS message can indicate "Integrity protected and ciphered initial NAS message" (see table FIG. 12).

[0069] Upon receipt of the Control plane service request message with a data service type indicating "mobile terminating request", the network can send an ESM DATA TRANSPORT message. When receiving the ESM data transport message, the UE can forward the contents of the User data container IE to an upper layer, using the EPS bearer identity.

CONTROL PLANE SERVICE REQUEST (Message definition)

[0070] A control plane service request message (e.g., data service request message) can be sent by the UE to the network in order to carry an ESM message in an encapsulated format, as indicated the table 400 of FIG. 4. (It should be noted that as used herein "data service request message" and "control plane service request message" can be used interchangeably. The control plane service request message type is a CONTROL PLANE SERVICE REQUEST. The control plane service request message significance is dual, and the direction, can be from the UE to network. The content of the control plane service request message can include the information element, the type/reference, the presence, format, and the length. As depicted in FIG. 4, "Note 1" indicates that in a variant of the present technology, additional information can be defined in format TLV with a length of 3 octets. Moreover, spare half octet can include the NAS KSI.

Device properties

[0071] The UE can include a device properties information element IE if the UE is configured for NAS signaling low priority.

Additional info

[0072] In one aspect, the UE can include an additional information IE or "Release Assistance Indication" IE if a downlink data transmission (e.g. acknowledgement or response) subsequent to the uplink data transmission is expected. It should be noted that "Additional Information" IE can be used interchangeably with the term "Release Assistance Indication" IE.

ESM message container

[0073] The UE may include an ESM message container IE during a mobile originated control plane service request.

Security protected initial NAS message (Message definition)

[0074] In one aspect, a security protected initial NAS message can be sent by the UE to transfer an initial NAS message together with the sequence number and the message authentication code protecting the message, as depicted in table 500 of FIG. 5. The security protected initial NAS message type can be security protected initial NAS message. The security protected initial NAS message significance is dual, and the direction, can be from the UE to the network.

Enhanced security protected NAS message (Message definition)

[0075] In one aspect, an enhanced security protected NAS message can be sent by the UE or the network to transfer a security protected NAS message together with the sequence number and the message authentication code protecting the message, as depicted in table 600 of FIG. 6. The enhanced security protected NAS message type can be an enhanced security protected NAS message. The enhanced security protected NAS message significance can be dual, and the direction, can be from the UE to the network or from the network to the UE.

ESM DATA TRANSPORT (Message definition)

[0076] In one aspect, an ESM data transport message can be sent by the UE or the network in order to carry (transport) user data in an encapsulated format, as depicted in table 700 of FIG. 7. The ESM data transport message type can be an ESM data transport message. The ESM data transport message significance can be dual, and the direction, can be from the UE to the network or vice versa.

Release assistance Indication or "additional information"

[0077] In one aspect, a UE can include one or more release assistance information IEs if a downlink data transmission (e.g. acknowledgement or response) subsequent to the uplink data transmission is expected.

[0078] For example, with one or more protocols, procedures, and/or embodiments as described herein, each message, except a SERVICE REQUEST message, can be an L3 message as defined in 3GPP TS 24.007, v 13.0.0. Thus, a release assistance information message can include one or more of the following:

1) if the message is a plain NAS message:

a) protocol discriminator;

b) EPS bearer identity or security header type;

c) procedure transaction identity;

d) message type;

e) other information elements.

2) if the message is a security protected NAS message:

a) protocol discriminator;

b) security header type;

c) message authentication code; d) sequence number;

e) plain NAS message, as defined in 1.

3) If the message is a security protected initial NAS message:

a) protocol discriminator; b) security header type; c) message authentication code; d) sequence number; e) NAS key set identifier; f) Spare half octet [or: Flow identity]; g) M-TMSI; h) plain NAS message, as defined in 1. In one aspect, the UE can include only the Control plane service request message in the plain NAS message field.

[0079] In one aspect, the organization of a plain NAS message is depicted in table 800 of FIG. 8. That is, FIG. 8 illustrates table 800 of an organization structure for a non- access stratum (NAS) message. Table 8 includes an EPS bearer identity or security header type, protocol discriminator, procedure transaction identity, message type, and/or other information elements. FIG. 9 illustrates the table 900 of an organization structure for a security protected non-access stratum (NAS) message. Table 9 includes a security header type, protocol discriminator, message authentication code, sequence number, and/or a NAS message. FIG. 10 illustrates the table 1000 of an organization structure for a security protected initial non-access stratum (NAS) message. Table 1000 includes the security header type, protocol discriminator, message authentication code, sequence number, NAS key set identifier, spare half octet, a mobile-temporary mobile subscriber identity "M- TMSI", and/or NAS message.

[0080] It should be noted that it is possible to include a global unique temporary identification (ID) "GUTI" rather than an M-TMSI. Then the security protected initial NAS message may also be used for the case when the UE is sending a first message in a new tracking area. If separate NAS message flows with different 'flow identifiers' are used, then another security header type can be used, such as indicated in FIG. 12. [0081] For example, a flow identifier = 0 (binary "0000") can be used for NAS messages not used to transport user data (these are e.g. all the NAS message specified in 3 GPP TS 23.401 Rel-12 and earlier), and flow identifier = 1 (binary "0001") for NAS messages used to transport user data (e.g. the ESM Data Transport message, or the Control Plane Service Request message, if it includes an ESM Data Transport message).

[0082] The organization of an enhanced security protected NAS message is illustrated in the example shown in table 1100 of FIG. 11. That is, FIG.11 illustrates table 1100 of an organization structure for an enhanced security protected non-access stratum (NAS) message. For both the enhanced security protected NAS message and the security protected initial NAS message of FIG. 10, a spare half octet in octet 7 can become a flow identity - indicating to which NAS message flow the respective message belongs, and thus which sequence number (and an overflow counter) and which bearer ID can be used for the deciphering of the NAS message. In one aspect, the only NAS message allowed to be included in the security protected initial NAS message is the Control plane service request message, and the only NAS message allowed to be included in the enhanced security protected NAS message or the Control plane service request message is the ESM data transport message.

[0083] In one aspect, the EPS bearer identity and the procedure transaction identity are only used in messages with a protocol discriminator EPS session management. Octet la (see FIG. 8) with a procedure transaction identity can only be included in messages with a protocol discriminator EPS session management. In one aspect, a particular information element can only be present one time in a given message.

[0084] In one aspect, when a field of a message extends over more than one octet, the place value of a bit progressively decreases as the octet number increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered octet of the field.

Security header type

[0085] Turning now to FIG.12, table 1200 depicts a security header type information element (IE). In one aspect, bits 5 to 8 of the first octet of every EPS Mobility

Management (EMM) message contain a Security header type IE. The Security header type IE can include control information related to the security protection of a NAS message. The total size of the Security header type IE can be at least 4 bits. The Security header type IE can take the values shown in table 1200. It should be noted that 1) NOTE 1 indicates the codepoint may be used only for a SECURITY MODE

COMMAND message, 2) NOTE 2 indicates the codepoint may be used only for a SECURITY MODE COMPLETE message, and 3) NOTE 3 indicates when bits 7 and 8 are set to Ί Γ, bits 5 and 6 can be used for future extensions of the SERVICE REQUEST message.

[0086] In one aspect, an EMM message can be received with the security header type encoded as "0000" and can be treated as a non security protected, plain NAS message. A protocol entity sending a non security protected EMM message can send the message as plain NAS message and encode the security header type as "0000".

Message type

[0087] In one aspect, the message type IE and its use can be defined in

3 GPP TS 24.007, v 13.0.0. Tuming now to FIG.13 and FIG. 14, FIG. 13 illustrates a table 1300 of various message types for evolved packet system (EPS) mobility management and FIG. 14 illustrates a table 1400 of various message types for evolved packet system (EPS) session management. FIGs. 13-14 define the value part of the message type IE used in the EPS mobility management protocol and EPS session management protocol.

Data service type

[0088] In one aspect, the purpose of the Data service type information element is to specify the purpose of the control plane service request procedure. Turning now to FIG's 15-19, FIG.15 illustrates a table 1500 of a data service type information element (IE), FIG. 16 illustrates an additional table 1600 of a data service type information element (IE) with additional information, FIG.17 illustrates a table 1700 of additional information element (IE), FIG.18 illustrates table 1800 of an alternative for an additional information element (IE), and FIG.19 illustrates table 1900 of a third alternative for an additional information element (IE).

[0089] In one aspect, bit 4 in FIG. 16 can be used for an alternative purpose, such as for being used as an "active" flag indication. Also, as depicted in FIG. 17, the purpose of the Additional Info information element (or "Release Assistance indication") is to specify whether downlink (DL) data (e.g. Acknowledgement or response to Uplink "UL" data) subsequent to the Uplink Data Transmission is expected or not expected. The Additional Info information element is coded as shown FIG. 17. The Additional information can be a type 1 information element. In one aspect, FIG. 18 depicts alternative 2 additional information element and FIG. 19 depicts alternative 3 additional information element, which can be a type 4 information element. It should be noted that the coding and bits used for the coding depicted in FIG. 's 15-19 are depicted as examples only. It should be noted that the coding of FIG. 's 15-19 can have one or more various different coding and bits for the release assistance indication.

User data container

[0090] In one aspect, the user data container information element can be used to encapsulate the data transferred between the UE and the MME. The User data container information element can be coded as shown in table 2000 of FIG. 20. In one aspect, the data via MME container can be a type 6 information element.

[0091] Thus, as described herein, the present technology provides for a user equipment (UE) device that has enhancements and optimizations for features and capabilities relating to Cellular Internet of Things (CIoT) for connecting to an EPS network that is also enhanced for CIoT features. The EPS network may include entities such as eNB, MME, SGW, PGW, SCEF (Service Capability Exposure Function), etc.

[0092] The UE can transfer Mobile Originated data via control plane to MME and the network can transfer Mobile Terminated (MT) data via control plane to the UE. If the UE is in EMM-IDLE mode, the EMM entity in the UE can initiate the data transfer procedure via control plane by sending a CONTROL PLANE SERVICE REQUEST message. The CONTROL PLANE SERVICE REQUEST message includes an ESM container message IE which contains the data to be sent in the ESM DATA TRANSPORT message. The data service type of the CONTROL PLANE SERVICE REQUEST message indicates "mobile originating request". In one aspect, if the UE is in EMM-IDLE mode, the UE can re-use the Extended Service Request message to carry the ESM DATA TRANSPORT message. The UE can send the CONTROL PLANE SERVICE REQUEST message as part of a Security protected initial NAS message. The security header type of the Security protected initial NAS message can indicate "Integrity protected and ciphered initial NAS message". If the UE is in EMM-CONNECTED mode, then upon receipt of a request from one or more upper layers associated with the UE, such as an application layer within the UE to transfer user data via the control plane, the ESM entity in the UE initiates the data transfer procedure by sending a stand-alone ESM DATA TRANSPORT message. When receiving the ESM DATA TRANSPORT message, the present technology can identify the bearer (e.g., the SCEF connection) on which to transfer the user data inside the core network based on the EPS bearer identity included in ESM DATA TRANSPORT message and then forward the contents of the User data container IE accordingly.

[0093] A network can page the UE if mobile terminated (MT) data is available for the UE. In one aspect, the network may indicate as to "transfer the data via control plane" or "transfer the data via user plane" based on UE preferences and capabilities. Upon receipt of a paging message indicating a "transfer user data via the control plane", the UE can respond with a CONTROL PLANE SERVICE REQUEST message. The data service type of the CONTROL PLANE SERVICE REQUEST message can indicate "mobile terminating request". The UE can send the CONTROL PLANE SERVICE REQUEST message as part of a Security protected initial NAS message. The security header type of the Security protected initial NAS message shall indicate "Integrity protected and ciphered initial NAS message". Upon receipt of the CONTROL PLANE SERVICE REQUEST message with data service type indicating "mobile terminating request", the network can send an ESM DATA TRANSPORT message. Upon receiving the ESM DATA TRANSPORT message, the UE can forward the contents of the User data container IE to the upper layer, using the EPS bearer identity.

[0094] Turning now to FIG. 21, an example provides functionality 2100 of a User Equipment (UE) to communicate with a wireless communication network, for using a scheduling request transmission for a cmWave system, as shown in the flow chart in FIG. 21. The functionality 2100 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable media or one or more non-transitory machine readable storage media. The UE can comprise one or more processors. In one embodiment, the one or more processors can comprise a baseband processor and/or an application processor. The one or more processors can be configured to: process, for transmission of user data to a mobility management entity (MME) via a control plane, a service request message having an Information element (IE) containing an evolved packet system (EPS) session management (ESM) data transport message, which includes the user data, wherein the ESM data transport message includes an EPS bearer Identity (ID) that is associated with the user data to enable the MME to identify a packet data network (PDN) connection, as in block 2110. The UE can comprise one or more processors configured to: process, for transmission, the user data via the control plane between the UE and the MME, as in block 2120.

[0095] More specifically, the UE can process, for transmission of user data to a mobility management entity (MME) via a control plane, a control plane service request message having the ESM message container Information element (IE) containing an ESM data transport message, that includes the user data, wherein the ESM data transport message enables the MME to identify an EPS bearer Identification (ID) that is associated with the data.

[0096] Turning now to FIG. 22, an example provides functionality 2200 of a User Equipment (UE) to communicate with a wireless communication network, for using a scheduling request transmission for a cmWave system, as shown in the flow chart in FIG. 22. The functionality 2200 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable media or one or more non-transitory machine readable storage media. The UE can comprise one or more processors configured to: configure a transceiver of the UE, operating in an evolved packet system (EPS) Mobility Management (EMM)-idle mode, to receive a paging message from a network, as in 2210. The UE can comprise one or more processors configured to: process, for transmission to a mobility management entity (MME), a service request message, as in 2220. The UE can comprise one or more processors configured to: configure a transceiver of the UE to receive, from the MME, an Information element (IE) containing an evolved packet system (EPS) session

management (ESM) data transport message that includes user data, as in 2230. The UE can comprise one or more processors configured to: process, for transmission to one or more upper layers associated with the UE, the user data via the control plane between the UE and the MME upon receiving the ESM data transport request message from a network, as in block 2240.

[0097] Additionally, the UE may configure a transceiver of the UE to receive a paging message from the eNodeB. A control plane service request message may be processed for transmission to a mobility management entity (MME). A transceiver of the UE can be configured to receive, from the eNodeB, an evolved packet system (EPS) session management (ESM) message container Information element (IE) containing an ESM data transport message, that includes the data. The user data via the control plane between the UE and the MME can be forwarded to upper layers of the UE using an EPS bearer Identification (ID) that is associated with the data.

[0098] Another example provides functionality 2300 of an eNodeB operable to communicate with a User Equipment (UE), within a wireless communication network, using a scheduling request transmission for a cmWave system, as shown in the flow chart in FIG. 23. The functionality 2300 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable media or one or more non-transitory machine readable storage media. The eNodeB can comprise one or more processors and memory configured to: process, for transmission to the UE, operating in an evolved packet system (EPS)

Mobility Management (EMM)-idle mode, a paging message received from a network, as in block 2310. The eNodeB can comprise one or more processors and memory configured to: configure a transceiver of the eNodeB to receive from the UE via the control plane a service request message, having an Information element (IE) containing an evolved packet system (EPS) session management (ESM) data transport message that includes the user data, for transmission of the service request message to a mobility management entity (MME), as in block 2320. The eNodeB can comprise one or more processors and memory configured to: process, for transmission to the MME, user data received via the control plane between the UE and the MME, as in block 2330.

[0099] Turning now to FIG. 24, an example provides functionality 2400 of a Cellular Internet of Things (CIoT) enabled user equipment (UE) to communicate with a mobility management entity (MME) within a wireless communication network, for transfer of user data via a control plane, as shown in the flow chart in FIG. 24. The functionality 2400 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable media or one or more non-transitory machine readable storage media. The UE can comprise one or more processors configured to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME), as in block 2410. The UE can comprise one or more processors configured to: include an EPS bearer identity associated with the user data in the ESM data transport message, as in block 2420. The UE can comprise one or more processors configured to: encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID, as in block 2430. The UE can further comprise a memory device configured to interface with the one or more processors. The memory device can be configured to store information, including the user information and/or the EPS bearer ID.

[00100] Turning now to FIG. 25, an example provides functionality 2500 of Cellular Internet of Things (CIoT) enabled mobile management entity (MME) to communicate with user equipment (UE) within a wireless communication network, for transfer of user data via a control plane, as shown in the flow chart in FIG. 25. The functionality 2500 can be implemented as a method or the functionality can be executed as instructions on a machine, where the instructions are included in one or more computer readable media or one or more transitory or non-transitory machine readable storage media. The MME can comprise one or more processors configured to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a UE, as in block 2510. The MME can comprise one or more processors configured to: include an EPS bearer identity associated with the user data in the ESM data transport message, as in block 2520. The MME can comprise one or more processors configured to: encode the ESM data transport message for transmission to the UE via the control plane, wherein the EPS bearer identity enables the UE to forward the user data to one or more upper layers of the UE based on the EPS bearer ID, as in block 2530. The MME can further comprise a memory device configured to interface with the one or more processors. The memory device can be configured to store information, including the user information and/or the EPS bearer ID.

[00101] FIG. 26 illustrates a diagram of a wireless device (e.g., UE) in accordance with an example. FIG. 26 provides an example illustration of the wireless device, such as a user equipment (UE) UE, a mobile station (MS), a mobile wireless device, a mobile communication device, a tablet, a handset, or other type of wireless device. In one aspect, the wireless device can include at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, a baseband processor, an application processor, internal memory, a non-volatile memory port, and combinations thereof.

[00102] The wireless device can include one or more antennas configured to

communicate with a node or transmission station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a relay station (RS), a radio equipment (RE), a remote radio unit

(RRU), a central processing module (CPM), or other type of wireless wide area network (WWAN) access point. The wireless device can be configured to communicate using at least one wireless communication standard including 3 GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi. The wireless device can communicate using separate antennas for each wireless communication standard or shared antennas for multiple wireless communication standards. The wireless device can communicate in a wireless local area network (WLAN), a wireless personal area network (WPAN), and/or a WWAN. The mobile device can include a storage medium. In one aspect, the storage medium can be associated with and/or communicate with the application processor, the graphics processor, the display, the non-volatile memory port, and/or internal memory. In one aspect, the application processor and graphics processor are storage mediums.

[00103] FIG. 27 illustrates example components of a device in accordance with some embodiments. In some embodiments, the device 2700 may include application circuitry 2702, baseband circuitry 2704, Radio Frequency (RF) circuitry 2706, front-end module (FEM) circuitry 2708, and one or more antennas 2710, coupled together at least as shown. The components of the illustrated device 2700 may be included a UE or a RAN node. In some embodiments, the device 2700 may include less elements (e.g., a RAN node may not utilize application circuitry 2702, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 2700 may include additional elements such as, for example, memory /storage, display, camera, sensor, and/or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

[00104] The application circuitry 2702 may include one or more application processors. For example, the application circuitry 2702 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with and/or may include memory /storage and may be configured to execute instructions stored in the memory /storage to enable various applications and/or operating systems to run on the system. In some embodiments, processors of application circuitry 2702 may process IP data packets received from an EPC.

[00105] The baseband circuitry 2704 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 2704 may include one or more baseband processors and/or control logic to process baseband signals received from a receive signal path of the RF circuitry 2706 and to generate baseband signals for a transmit signal path of the RF circuitry 2706. Baseband processing circuity 2704 may interface with the application circuitry 2702 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 2706. For example, in some embodiments, the baseband circuitry 2704 may include a second generation (2G) baseband processor 2704a, third generation (3G) baseband processor 2704b, fourth generation (4G) baseband processor 2704c, and/or other baseband processor(s) 2704d for other existing generations, generations in development or to be developed in the future (e.g., fifth generation (5G), 6G, etc.). The baseband circuitry 2704 (e.g., one or more of baseband processors 2704a-d) may handle various radio control functions that enable communication with one or more radio networks via the RF circuitry 2706. In other embodiments, some or all of the functionality of baseband processors 2704a-d may be included in modules stored in the memory 2704g and executed via a Central Processing Unit (CPU) 2704e. The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 2704 may include Fast-Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments,

encoding/decoding circuitry of the baseband circuitry 2704 may include convolution, tail- biting convolution, turbo, Viterbi, and/or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

[00106] In some embodiments, the baseband circuitry may include one or more audio digital signal processor(s) (DSP) 2704f. The audio DSP(s) 2704f may be include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 2704 and the application circuitry 2702 may be implemented together such as, for example, on a system on a chip (SOC).

[00107] In some embodiments, the baseband circuitry 2704 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 2704 may support communication with an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 2704 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

[00108] RF circuitry 2706 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RF circuitry 2706 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. RF circuitry 2706 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 2708 and provide baseband signals to the baseband circuitry 2704. RF circuitry 2706 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 2704 and provide RF output signals to the FEM circuitry 2708 for transmission.

[00109] In some embodiments, the RF circuitry 2706 may include a receive signal path and a transmit signal path. The receive signal path of the RF circuitry 2706 may include mixer circuitry 2706a, amplifier circuitry 2706b and filter circuitry 2706c. The transmit signal path of the RF circuitry 2706 may include filter circuitry 2706c and mixer circuitry 2706a. RF circuitry 2706 may also include synthesizer circuitry 2706d for synthesizing a frequency for use by the mixer circuitry 2706a of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 2706a of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 2708 based on the synthesized frequency provided by synthesizer circuitry 2706d. The amplifier circuitry 2706b may be configured to amplify the down-converted signals and the filter circuitry 2706c may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 2704 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, mixer circuitry 2706a of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

[00110] In some embodiments, the mixer circuitry 2706a of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 2706d to generate RF output signals for the FEM circuitry 2708. The baseband signals may be provided by the baseband circuitry 2704 and may be filtered by filter circuitry 2706c. The filter circuitry 2706c may include a low-pass filter (LPF), although the scope of the embodiments is not limited in this respect.

[00111] In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and/or upconversion respectively. In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a may be arranged for direct downconversion and/or direct upconversion, respectively. In some embodiments, the mixer circuitry 2706a of the receive signal path and the mixer circuitry 2706a of the transmit signal path may be configured for super-heterodyne operation. [00112] In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 2706 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 2704 may include a digital baseband interface to communicate with the RF circuitry 2706.

[00113] In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

[00114] In some embodiments, the synthesizer circuitry 2706d may be a fractional-N synthesizer or a fractional N/N+l synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 2706d may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

[00115] The synthesizer circuitry 2706d may be configured to synthesize an output frequency for use by the mixer circuitry 2706a of the RF circuitry 2706 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 2706d may be a fractional N/N+l synthesizer.

[00116] In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 2704 or the applications processor 2702 depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the applications processor 2702.

[00117] Synthesizer circuitry 2706d of the RF circuitry 2706 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+l (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

[00118] In some embodiments, synthesizer circuitry 2706d may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 2706 may include an IQ/polar converter.

[00119] FEM circuitry 2708 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 2710, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 2706 for further processing. FEM circuitry 2708 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RF circuitry 2706 for transmission by one or more of the one or more antennas 2710.

[00120] In some embodiments, the FEM circuitry 2708 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry may include a low-noise amplifier (LNA) to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry

2706). The transmit signal path of the FEM circuitry 2708 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by RF circuitry 2706), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 2710.

[00121] In some embodiments, the device 2700 comprises a plurality of power saving mechanisms. If the device 2700 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device may power down for brief intervals of time and thus save power.

[00122] If there is no data traffic activity for an extended period of time, then the device 2700 may transition off to an RRC Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 2700 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device cannot receive data in this state, in order to receive data, it can transition back to RRC Connected state.

[00123] An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

[00124] Processors of the application circuitry 2702 and processors of the baseband circuitry 2704 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 2704, alone or in combination, may be used execute Layer 3, Layer 2, and/or Layer 1 functionality, while processors of the application circuitry 2704 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

[00125] FIG. 28 illustrates example interfaces of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 2704 of FIG. 27 may comprise processors 2704A-2704E and a memory 2704G utilized by said processors. Each of the processors 2704A-2704E may include a memory interface, 2804A-2804E, respectively, to send/receive data to/from the memory 2704G. [00126] The baseband circuitry 2704 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 2812 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 2704), an application circuitry interface 2814 (e.g., an interface to send/receive data to/from the application circuitry 2702 of FIG. 27), an RF circuitry interface 2816 (e.g., an interface to send/receive data to/from RF circuitry 2706 of FIG. 27), and a wireless hardware connectivity interface 2818 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components).

[00127] FIG. 29 illustrates a diagram 2900 of a node 2910 (e.g., eNB and/or a base station) and wireless device (e.g., UE) in accordance with an example. The node can include a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), a remote radio equipment (RRE), a remote radio unit (RRU), or a central processing module (CPM). In one aspect, the node can be a Serving GPRS Support Node. The node 2910 can include a node device 2912. The node device 2912 or the node 2910 can be configured to communicate with the wireless device 2920. The node device 2912 can be configured to implement the technology described. The node device 2912 can include a processing module 2914 and a transceiver module 2916. In one aspect, the node device 2912 can include the transceiver module 2916 and the processing module 2914 forming a circuitry 2918 for the node 2910. In one aspect, the transceiver module 2916 and the processing module 2914 can form a circuitry of the node device 2912. The processing module 2914 can include one or more processors and memory. In one embodiment, the processing module 2922 can include one or more application processors. The transceiver module 2916 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 2916 can include a baseband processor.

[00128] The wireless device 2920 can include a transceiver module 2924 and a processing module 2922. The processing module 2922 can include one or more processors and memory. In one embodiment, the processing module 2922 can include one or more application processors. The transceiver module 2924 can include a transceiver and one or more processors and memory. In one embodiment, the transceiver module 2924 can include a baseband processor. The wireless device 2920 can be configured to implement the technology described. The node 2910 and the wireless devices 2920 can also include one or more storage mediums, such as the transceiver module 2916, 2924 and/or the processing module 2914, 2922. In one aspect, the components described herein of the transceiver module 2916 can be included in one or more separate devices that can be used in a cloud-RAN (C-RAN) environment.

Examples

[00129] The following examples pertain to specific embodiments and point out specific features, elements, or operations that can be used or otherwise combined in achieving such embodiments.

[00130] Example 1 includes an apparatus of a Cellular Internet of Things (CIoT) enabled user equipment (UE) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to: include user data in an information element (IE) into an evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID.

[00131] Example 2 includes the apparatus of example 1, wherein the information element is a user data container information element.

[00132] Example 3 includes the apparatus of example 2, wherein the one or more processors are further configured to encapsulate the user data container information element in the ESM data transport message.

[00133] Example 4 includes the apparatus of example 2, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00134] Example 5 includes the apparatus of example 1, wherein the one or more processors are further configured to: in the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and encode the data service request message for transmission from the UE to the MME via the control plane.

[00135] Example 6 includes the apparatus of example 5, wherein the one or more processors are further configured to: include a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

[00136] Example 7 includes the apparatus of example 1 or 5, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication IE.

[00137] Example 8 includes the apparatus of example 1, wherein the one or more processors are further configured to encode the ESM data transport message including the user data for transmission to the MME via the control plane when the UE is in an EPS Mobility Management (EMM) connected mode.

[00138] Example 9 includes the apparatus of example 1, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

[00139] Example 10 includes the apparatus of example 1, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00140] Example 11 includes an apparatus of a Cellular Internet of Things (CIoT) enabled mobile management entity (MME) for transfer of user data via a control plane, the apparatus comprising :one or more processors configured to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a UE; include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the UE via the control plane, wherein the EPS bearer identity enables the UE to forward the user data to one or more upper layers of the UE based on the EPS bearer ID.

[00141] Example 12 includes the apparatus of example 11, wherein the one or more processers are configured to: decode a service request message received from the UE, wherein the service request message includes a data service type information element (IE) that identifies the service request message as a mobile terminating request.

[00142] Example 13 includes the apparatus of example 11, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00143] Example 14 includes the apparatus of example 12 or 13, wherein the information element is a user data container information element.

[00144] Example 15 includes the apparatus of example 14, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00145] Example 16 includes the apparatus of example 11, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

[00146] Example 17 includes at least one machine readable storage medium having instructions embodied thereon for a Cellular Internet of Things (CIoT) enabled user equipment (UE) to transfer user data via a control plane, the instructions when executed cause the UE to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID.

[00147] Example 18 at least one machine readable storage medium of example 17, wherein the information element is a user data container information element. [00148] Example 19 includes the at least one machine readable storage medium of example 0, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00149] Example 20 includes at least one machine readable storage medium of example 17, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: include the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)- idle mode; and encode the data service request message for transmission from the UE to the MME via the control plane.

[00150] Example 21 includes at least one machine readable storage medium of example 19 or 20, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: encapsulate a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

[00151] Example 22 includes at least one machine readable storage medium of example 17, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: receive a request to transfer user data via the control plane from one or more upper layers of the UE when the UE is in an EPS Mobility Management (EMM)-connected mode.

[00152] Example 23 includes at least one machine readable storage medium of example 17 or 21, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00153] Example 24 includes at least one machine readable storage medium of example 17, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00154] Example 25 includes an apparatus of a Cellular Internet of Things (CIoT) enabled user equipment (UE) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to: include user data in an information element (IE) into an evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID; and a memory interface coupled to the one or more processors to enable a memory to store the user data.

[00155] Example 26 includes the apparatus of example 25, wherein the information element is a user data container information element.

[00156] Example 27 includes the apparatus of example 26, wherein the one or more processors are further configured to encapsulate the user data container information element in the ESM data transport message.

[00157] Example 28 includes the apparatus of example 27, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00158] Example 29 includes the apparatus of example 25, wherein the one or more processors are further configured to: in the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and encode the data service request message for transmission from the UE to the MME via the control plane.

[00159] Example 30 includes the apparatus of example 29, wherein the one or more processors are further configured to: include a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

[00160] Example 31 includes the apparatus of example 29, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication IE. [00161] Example 32 includes the apparatus of example 25, wherein the one or more processors are further configured to encode the ESM data transport message including the user data for transmission to the MME via the control plane when the UE is in an EPS Mobility Management (EMM) connected mode.

[00162] Example 33 includes the apparatus of example 25, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

[00163] Example 34 includes the apparatus of example 25, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00164] Example 35 includes an apparatus of a Cellular Internet of Things (CIoT) enabled mobile management entity (MME) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a UE; include an EPS bearer identity associated with the user data in the ESM data transport message; encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID; and a memory interface coupled to the one or more processors to enable a memory to store the user data.

[00165] Example 36 includes the apparatus of example 35, wherein the one or more processers are configured to: decode a service request message received from the UE, wherein the service request message includes a data service type information element (IE) that identifies the service request message as a mobile terminating request.

[00166] Example 37 includes the apparatus of example 35, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00167] Example 38 includes the apparatus of example 37, wherein the information element is a user data container information element.

[00168] Example 39 includes the apparatus of example 38, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00169] Example 40 includes the apparatus of example 35, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

[00170] Example 41 includes at least one machine readable storage medium having instructions embodied thereon for a Cellular Internet of Things (CIoT) enabled user equipment (UE) to transfer user data via a control plane, the instructions when executed cause the UE to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID; a memory interface coupled to the one or more processors to enable a memory to store the user data.

[00171] Example 42 includes the at least one machine readable storage medium of example 41, wherein the information element is a user data container information element.

[00172] Example 43 includes the at least one machine readable storage medium of example 42, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00173] Example 44 includes the at least one machine readable storage medium of example 41, further comprising instructions which when executed cause the UE to, wherein the one or more processors are further configured to: include the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and encode the data service request message for transmission from the UE to the MME via the control plane. [00174] Example 45 includes the at least one machine readable storage medium of example 44, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: encapsulate a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

[00175] Example 46 includes the at least one machine readable storage medium of example 41, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: receive a request to transfer user data via the control plane from one or more upper layers of the UE when the UE is in an EPS Mobility Management (EMM)-connected mode.

[00176] Example 47 includes the at least one machine readable storage medium of example 46, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00177] Example 48 includes the at least one machine readable storage medium of example 41, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00178] Example 49 includes an apparatus of a Cellular Internet of Things (CIoT) enabled user equipment (UE) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to: include user data in an information element (IE) into an evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID.

[00179] Example 50 includes the apparatus of example 49, wherein the information element is a user data container information element. [00180] Example 51 includes the apparatus of example 49 or 50, wherein the one or more processors are further configured to: encapsulate the user data container information element in the ESM data transport message, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00181] In Example 52, the subject matter of Example 49 or any of the Examples described herein may further include, wherein the one or more processors are further configured to: in the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; encode the data service request message for transmission from the UE to the MME via the control plane; and include a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication IE.

[00182] In Example 53, the subject matter of Example 49 or any of the Examples described herein may further include, wherein the one or more processors are further configured to encode the ESM data transport message including the user data for transmission to the MME via the control plane when the UE is in an EPS Mobility Management (EMM) connected mode.

[00183] In Example 54, the subject matter of Example 49 or any of the Examples described herein may further include, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00184] Example 55 includes an apparatus of a Cellular Internet of Things (CIoT) enabled mobile management entity (MME) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a UE; include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the UE via the control plane, wherein the EPS bearer identity enables the UE to forward the user data to one or more upper layers of the UE based on the EPS bearer ID.

[00185] Example 56 includes the apparatus of example 55, wherein the one or more processers are configured to: decode a service request message received from the UE, wherein the service request message includes a data service type information element (IE) that identifies the service request message as a mobile terminating request, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication, wherein the information element is a user data container information element.

[00186] Example 57 includes the apparatus of example 55 or 56, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00187] In Example 58, the subject matter of Example 55 or any of the Examples described herein may further include, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

[00188] Example 59 includes at least one machine readable storage medium having instructions embodied thereon for a Cellular Internet of Things (CIoT) enabled user equipment (UE) to transfer user data via a control plane, the instructions when executed cause the UE to: include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID. [00189] Example 60 includes the at least one machine readable storage medium of claim 59, wherein the information element is a user data container information element, and wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00190] Example 61 includes the at least one machine readable storage medium of claim 59 or 60, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to: include the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; encode the data service request message for transmission from the UE to the MME via the control plane; encapsulate a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request; or receive a request to transfer user data via the control plane from one or more upper layers of the UE when the UE is in an EPS Mobility Management (EMM)-connected mode.

[00191] In Example 62, the subject matter of Example 59 or any of the Examples described herein may further include, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00192] In Example 63, the subject matter of Example 59 or any of the Examples described herein may further include, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

[00193] Example 64 includes a device of a Cellular Internet of Things (CIoT) enabled user equipment (UE) to transfer user data via a control plane, the device comprising: means for including user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); means for including an EPS bearer identity associated with the user data in the ESM data transport message; and means for encoding the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID.

[00194] Example 65 includes the device of example 64, wherein the information element is a user data container information element.

[00195] Example 66 includes the device of example 64, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

[00196] Example 67 includes the device of example 64, further comprising means for: including the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and encoding the data service request message for transmission from the UE to the MME via the control plane.

[00197] Example 68 includes the device of example 64 or 67, further comprising means for: encapsulating a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

[00198] Example 69 includes the device of example 64 or 68, further comprising means for: receiving a request to transfer user data via the control plane from one or more upper layers of the UE when the UE is in an EPS Mobility Management (EMM)-connected mode.

[00199] Example 69 includes the device of example 64 or 68, further comprising means for, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

[00200] Example 70 includes the device of example 64, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a nonvolatile memory port, and combinations thereof.

[00201] As used herein, the term "circuitry" can refer to, be part of, or include an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group), and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable hardware components that provide the described functionality. In some aspects, the circuitry can be implemented in, or functions associated with the circuitry can be implemented by, one or more software or firmware modules. In some aspects, circuitry can include logic, at least partially operable in hardware.

[00202] Various techniques, or certain aspects or portions thereof, may take the form of program code (i.e., instructions) embodied in tangible media, such as floppy diskettes, compact disc-read-only memory (CD-ROMs), hard drives, non-transitory computer readable storage medium, or any other machine-readable storage medium wherein, when the program code is loaded into and executed by a machine, such as a computer, the machine becomes an apparatus for practicing the various techniques. Circuitry can include hardware, firmware, program code, executable code, computer instructions, and/or software. A non-transitory computer readable storage medium can be a computer readable storage medium that does not include signal. In the case of program code execution on programmable computers, the computing device may include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and at least one output device. The volatile and non-volatile memory and/or storage elements may be a random-access memory (RAM), erasable programmable read only memory (EPROM), flash drive, optical drive, magnetic hard drive, solid state drive, or other medium for storing electronic data. The node and wireless device may also include a transceiver module (i.e., transceiver), a counter module (i.e., counter), a processing module (i.e., processor), and/or a clock module (i.e., clock) or timer module (i.e., timer). One or more programs that may implement or utilize the various techniques described herein may use an application programming interface (API), reusable controls, and the like. Such programs may be implemented in a high level procedural or object oriented programming language to communicate with a computer system. However, the program(s) may be implemented in assembly or machine language, if desired. In any case, the language may be a compiled or interpreted language, and combined with hardware implementations.

[00203] As used herein, the term processor can include general purpose processors, specialized processors such as VLSI, FPGAs, or other types of specialized processors, as well as base band processors used in transceivers to send, receive, and process wireless communications.

[00204] It should be understood that many of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. For example, a module may be implemented as a hardware circuit comprising custom very-large-scale integration (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.

[00205] Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more physical or logical blocks of computer instructions, which may, for instance, be organized as an object, procedure, or function. Nevertheless, the executables of an identified module may not be physically located together, but may comprise disparate instructions stored in different locations which, when joined logically together, comprise the module and achieve the stated purpose for the module.

[00206] Indeed, a module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices, and may exist, at least partially, merely as electronic signals on a system or network. The modules may be passive or active, including agents operable to perform desired functions.

[00207] Reference throughout this specification to "an example" or "exemplary" means that a particular feature, structure, or characteristic described in connection with the example is included in at least one embodiment of the present technology. Thus, appearances of the phrases "in an example" or the word "exemplary" in various places throughout this specification are not necessarily all referring to the same embodiment.

[00208] As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary. In addition, various embodiments and example of the present technology may be referred to herein along with alternatives for the various components thereof. It is understood that such embodiments, examples, and alternatives are not to be construed as defacto equivalents of one another, but are to be considered as separate and autonomous representations of the present technology.

[00209] Furthermore, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided, such as examples of layouts, distances, network examples, etc., to provide a thorough understanding of embodiments of the technology. One skilled in the relevant art will recognize, however, that the technology can be practiced without one or more of the specific details, or with other methods, components, layouts, etc. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring aspects of the technology.

[00210] While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.

Claims

What is claimed is:

An apparatus of a Cellular Internet of Things (CIoT) enabled user equipment (UE) for transfer of user data via a control plane, the apparatus comprising: one or more processors configured to:

include user data in an information element (IE) into an evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and

encode the ESM data transport message for transmission to the MME via the control plane, to enable the MME to identify a packet data network (PDN) connection and forward the user data based on the EPS bearer ID.

The apparatus of claim 1, wherein the information element is a user data container information element.

The apparatus of claim 2, wherein the one or more processors are further configured to encapsulate the user data container information element in the ESM data transport message.

The apparatus of claim 2, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

The apparatus of claim 1, wherein the one or more processors are further configured to: in the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and

encode the data service request message for transmission from the UE to the MME via the control plane.

6. The apparatus of claim 5, wherein the one or more processors are further configured to:

include a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

7. The apparatus of claim 1 or 5, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication IE.

8. The apparatus of claim 1, wherein the one or more processors are further configured to encode the ESM data transport message including the user data for transmission to the MME via the control plane when the UE is in an EPS Mobility Management (EMM) connected mode.

9. The apparatus of claim 1, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

10. The apparatus of claim 1, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, a non-volatile memory port, and combinations thereof.

11. An apparatus of a Cellular Internet of Things (CIoT) enabled mobile

management entity (MME) for transfer of user data via a control plane, the apparatus comprising:

one or more processors configured to:

include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a UE;

include an EPS bearer identity associated with the user data in the ESM data transport message; and

encode the ESM data transport message for transmission to the UE via the control plane, wherein the EPS bearer identity enables the UE to forward the user data to one or more upper layers of the UE based on the EPS bearer ID.

12. The apparatus of claim 11, wherein the one or more processers are configured to:

decode a service request message received from the UE, wherein the service request message includes a data service type information element (IE) that identifies the service request message as a mobile terminating request.

13. The apparatus of claim 11, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

14. The apparatus of claim 12 or 13, wherein the information element is a user data container information element.

15. The apparatus of claim 14, wherein the user data container information

element includes a length of user data container contents and the user data stored in octets as user data container contents.

16. The apparatus of claim 11, further comprising memory configured to interface with the one or more processors and store one or more of the user data or the EPS bearer identity.

17. At least one machine readable storage medium having instructions embodied thereon for a Cellular Internet of Things (CIoT) enabled user equipment (UE) to transfer user data via a control plane, the instructions when executed cause the UE to:

include user data in an information element (IE) into a evolved packet system (EPS) session management (ESM) data transport message to transfer the user data via the control plane to a mobility management entity (MME); include an EPS bearer identity associated with the user data in the ESM data transport message; and

18. The at least one machine readable storage medium of claim 17, wherein the information element is a user data container information element.

19. The at least one machine readable storage medium of claim 0, wherein the user data container information element includes a length of user data container contents and the user data stored in octets as user data container contents.

20. The at least one machine readable storage medium of claim 17, further

comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to:

include the ESM data transport message in a service request message when the UE is in an EPS Mobility Management (EMM)-idle mode; and encode the data service request message for transmission from the UE to the MME via the control plane.

21. The at least one machine readable storage medium of claim 19 or 20, further comprising instructions which when executed cause the UE to:, wherein the one or more processors are further configured to:

encapsulate a data service type information element (IE) into the service request message to identify the service request message as a mobile originating request.

22. The at least one machine readable storage medium of claim 17, further

receive a request to transfer user data via the control plane from one or more upper layers of the UE when the UE is in an EPS Mobility Management (EMM)-connected mode.

23. The at least one machine readable storage medium of claim 17 or 21, wherein the ESM data transport message includes a protocol discriminator information element (IE), the EPS bearer identity IE, a procedure transaction identity IE, an ESM data transport message identity IE, the user data in a user data container IE, and a release assistance indication.

24. The at least one machine readable storage medium of claim 17, wherein the UE includes at least one of an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an intemal memory, a non-volatile memory port, and combinations thereof.