TW201735673A - Cellular internet of things data transfer via a mobility management entity - Google Patents

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 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 PDN connection associated with the EPS bearer ID and forward the user data based on the EPS bearer ID.

Description

Honeycomb IoT data transfer technology via mobility management entity

The present disclosure relates to a cellular Internet of Things data transfer technology via a mobility management entity.

BACKGROUND OF THE INVENTION Wireless mobile communication technologies use various standards and protocols to transfer data between a node (e.g., a transmitting station such as an eNodeB) and a wireless device (e.g., a mobile device). Some wireless devices use orthogonal frequency division multiple access (OFDMA) in one downlink (DL) transmission and single carrier frequency division multiple access (SC-FDMA) in one uplink (UL) transmission. communication. Standards and protocols for signal transmission using orthogonal frequency division multiplexing (OFDM) include 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE), an international motor commonly referred to by the industry as WiMAX (Worldwide Interoperability for Microwave Access) The Institute of Electrical Engineers (IEEE) 802.16 standards (eg, 802.16e, 802.16m), and the IEEE 802.11 standard, which is commonly referred to by the industry as Wi-Fi. In a 3GPP Radio Access Network (RAN) LTE system, the node may be an Evolved Universal Terrestrial Radio Access Network (E-UTRAN), which is carried out with the wireless device known as a User Equipment (UE). communication. The downlink (DL) transmission may be a communication from the node to the wireless device (e.g., UE), and the uplink (UL) transmission may be a communication from the wireless device to the node.

Honeycomb networks are gradually being adjusted to make it easy to use machine-to-machine (M2M) type devices. Machine-to-machine (M2M) and Machine Type Communication (MTC) terms are used to describe use cases and to describe the various features of machine type communication services. M2M and MTC devices can be designed to operate within a wireless network to implement an "Internet of Things."

According to an embodiment of the present invention, a device for enabling a user equipment (UE) for transmitting user data via a control plane, which comprises a cellular Internet of Things (CIoT) function, comprises: one or more a processor configured to: incorporate user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for use by the control plane The data is transmitted to a mobility management entity (MME); an EPS bearer identification associated with the user profile is included in the ESM data transmission message; and the ESM data transmission message is encoded for transmission to the control plane The MME, such that the MME can identify a packet data network (PDN) connection and forward the user profile based on the EPS carrying ID; and a memory interface coupled to the one or more processors to enable A memory can store the user data.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Before the present technology is disclosed and described, it should be understood that the present invention is not limited to the specific structures, processes, or materials disclosed herein, but may be extended to Those skilled in the relevant art will understand the equivalents. It is also understood that the terminology used herein is for the purpose of the description The same reference numbers in the different drawings denote the same elements. The figures are provided in the flowcharts and the process for the purpose of clearly illustrating the acts and operations and do not necessarily represent a particular order or order. Example embodiment

A preliminary overview of the technical embodiments is provided below, and then specific technical embodiments will be described in more detail later. This preliminary summary is intended to assist the reader in understanding the present technology, but is not intended to identify key features or essential features of the technology, and is not intended to limit the scope of the claimed subject matter.

Machine Type Communication (MTC) is an important growth opportunity for the 3rd Generation Partnership Project (3GPP) next generation wireless communication system. In order to support an Internet of Things (IoT), the 3GPP system is limited to use the use of power efficient IoT devices (eg, with years of battery life) and can be deployed in challenging coverage conditions ( For example, outdoor, indoor, building, basement, etc.). In addition, IoT devices for 3GPP communications can be inexpensive so that they can be deployed on a large scale when used for one-time use.

Therefore, the present technology provides efficient processing support for frequent and infrequent small data transfer while minimizing the computational overhead for system signaling without affecting security, and supports power optimization and paging optimization. Chemical. In addition, the present technology can provide support for improving mobility and meeting management efficiency.

In one aspect, the present technology provides cellular Internet of Things (CIoT) data transfer via a Mobility Management Entity (MME) within a wireless communication network. In order to send user data to an MME via a control plane, a user equipment (UE) can process a control plane service request message having an evolved packet system (EPS) session management (ESM) message container. An information element (IE) containing an ESM data transmission message including the user profile. The ESM data transmission message may enable the MME to identify an EPS carrying identification (ID) associated with the material.

In one aspect, the present technology provides a data transfer procedure via a Mobility Management Entity (MME). A unique ID can be used to distinguish the connection between the UE and the MME in order to deliver the data correctly, especially since there may be multiple connections (UE Service Capability Exposure Architecture "UE-SCEF" Connection and Packet Data Network) Road "PDN" connections) coexist. In one aspect, the unique ID can be an Evolution Packet System (EPS) carrying ID.

The PDU used to transmit material via an MME can be embedded and encrypted. However, if the EPS-carrying ID is used as one of the input parameters in the security operation, the EPS-carrying ID should not be encrypted to allow the EPS-carrying ID to be used as being in the security. An input in a sexual operation. In one aspect, the transmitted material can be embedded in a non-access layer (NAS) message.

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 restricted to include a Key Set Identifier (KSI) for use in an EPS security environment in relation to the UE and in the network. The UE can be processed and the network is not synchronized (eg, the UE and the network have become "out of sync").

Additionally, an additional message information element (IE) can be used with a one-tuple containing the EPS-carrying ID and the key set identification code (KSI) in the NAS message. The security-protected NAS message type can be modified and a security header type can be implemented to protect the EPS-carrying ID and KSI.

In one aspect, an enhanced ESM message containing the EPS carried ID can be used. Under the assumption that the division/combination of user data can be performed by the MME and the lower layer of the UE (eg, a 1600-byte packet can be divided into 8×200 bytes), a substance A NAS message container with a maximum length of 250 bytes would be sufficient. In one aspect, the maximum length can be 65 kilobytes (KB) under the assumption that the user profile can be up to 1500 bytes and can be transmitted without splitting.

In one aspect, a Control Plane Service Request NAS message with an Evolution Packet System (EPS) Talk 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 may include an ESM data transmission message including user data. In one example, the ESM data transmission message can be encapsulated or included in a NAS message and sent from the UE to the MME. The ESM data transmission message may enable the MME to identify an EPS carrier identification (ID) associated with the user profile.

Accordingly, the present technology provides a NAS program and/or message to support cellular Internet of Things (CIoT) data transfer via the MME. The present technology provides a modification of the protocol specification of 3GPP TS 24.301 version 13.4.0 and an update of the related EPS mobility management and EPS conference management service request procedure for providing data transmission in a NAS PDU via the MME. The mechanism, while considering the security aspects for 3GPP devices. The service request procedure is enhanced to process UE initiated and network initiated user data transmissions via a control plane procedure. A control plane service request message is defined to enable the UE to transmit data in an EPS mobility management (EMM)-idle mode; and when it is paged by the network, for example, to transmit data, it may be back call. A new service acceptance message is defined to terminate the service request procedure for a particular use case. Therefore, CIoT data transfer can occur via a control plane.

1 illustrates a mobile communication network within a cell 100 having an evolved Node B (eNB or eNodeB) accompanying a mobile device. Figure 1 illustrates an eNB 104 that can be associated with an anchor cell, a giant cell, or a primary cell. Moreover, the cell 100 can include a mobile device such as, for example, a user equipment (UE) 108 that can communicate with the eNB 104. The eNB 104 may be a station that communicates with the UE 108 and may 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 transmit power eNB, such as a giant eNB, for coverage and connectivity. The eNB 104 may be responsible for mobility and may also be responsible for Radio Resource Control (RRC) signaling. The UE or UEs 108 may be supported by the jumbo eNB 104. The eNB 104 can provide communication coverage for a particular geographic area. In 3GPP, the term "cell" may refer to a particular geographic coverage area of an eNB and/or serve an eNB subsystem of the coverage area with an associated carrier frequency and a frequency bandwidth, depending on the term Context.

2 is a schematic diagram showing a protocol architecture for supporting one of the EPS services or a mobile station (MS) according to an example. That is, Figure 2 depicts three sublayers for an EPS Packet Exchange (PS) domain service. The Access Layer (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) includes the MM sublayer and the CM sublayer. The MM sublayer further includes an EPS Mobility Management (EMM) entity. The CM sublayer may include one or more Evolution Packet System (EPS) Talk Management (ESM) entities. The ESM entity may provide services to the bearer control (BC) entity and use the services of the MM sublayer. The BC entity can hide these concepts of radios that can be established/released when an EPS carries environmental activity. If the uplink data in the terminal is to be transmitted and the radio bearer has been released, the BC entity can trigger a service request procedure in the EMM. In addition, one or more Packet Data Convergence Protocol (PDCP) Service Access Points (SAP) (eg, PDCP 1-SAP, PDCP 2-SAP, and PDCP 3-SAP), other SAPs (eg, RBMAS-SAP, ESMREG) - SAP, EMMREG-SAP, and EMMAS-SAP) and parameters for use via a SAP multiplex (eg, EBI, PD) are depicted.

In one aspect, upon receiving a request to transmit user data, an application (not shown) can be assumed to be located above the "modulation demodulator" (or "mobile terminal"), ie In an upper layer higher than the protocol layers shown in FIG. 2, one of the radio bearers (eg, RB1) may be delivered via an RB Service Access Point (SAP) (eg, RB1-SAP). User data package. If the BC entity determines that the UE is in EMM idle mode (ie, no RRC connection and no radio bearer has been established), the BC entity may send a request to the NAS to initiate a service request procedure and via the control plane That is, the user profile is transmitted via a signaling radio. Accordingly, the present technology provides an improvement over the state of the art in which the request is directed to the EMM, and the EMM initiates the procedure to establish all radio bearers, ie, data radio bearers and signaling radios. give away.

In one aspect, the BC entity can determine that the user profile can be sent via the control plane (rather than via the user plane). The BC entity may forward the user profile to the ESM with a request to send the data to the network. The ESM may encapsulate the user data packet in a transport message, such as an ESM DATA TRANSPORT message, and forward the message to the EMM in response to a request to send the data to the network. The EMM may 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 establishment of the RRC connection, the UE may transmit the CONTROL PLANE SERVICE REQUEST message to the eNB.

As used herein, the term package refers to the modular data process that is transmitted using a predetermined delivery protocol. The data is typically encapsulated in a physical data unit (PDU). Header information, sometimes footnote or footer information, can be added, including control information used to transmit and decode the packaged data. As used herein, the term encapsulation may refer to both the data processed in the PDU and the header and/or trailer information.

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

In one aspect, the BC may decide not to forward the user profile itself, but instead forward an indicator to the user profile. In another aspect, an application itself can determine that the user profile is transmitted via the control plane and can communicate the user profile directly to the ESM via a new service access point. It should be noted that the UE internal communication may refer to a request from the "upper layer", wherein the upper layer may be the application itself, an operating system of the application processor on which the application runs, A Transmission Control Protocol/Internet Protocol (TCP/IP) socket on the application processor, and so on. Thus, a request to transmit user data may be the delivery of the user data packet, or the request may contain additional information such as information for the BC, which may also be used as a decision to transmit data via the control plane. a standard. Moreover, an application, or more generally, the upper layer can initiate the request to transmit the user profile.

Referring now to Figures 3A-3B, in an Operational Origin (MO) data transmission in control plane CIoT EPS optimization with P-GW connections and in control plane CIoT EPS optimization with P-GW connections An action termination (MT) data transfer is depicted.

However, for purposes of the present technology, operations 0-2 and 11-12 of Figure 3A and operations 5-6 and 13-16 of Figure 3B are most relevant. While each of these additional operations of Figures 3A-3B may be implemented and may be applicable, it is not necessary for the purposes of the present technology. For example, in FIG. 3A, the relevant portions of 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 may send an integrity-protected NAS PDU as part of it. The NAS PDU can carry the EPS carrying ID and the encrypted uplink data. For example, the NAS PDU may be a control plane service request message, which may include an encrypted ESM data transmission message including one of the uplink user data. The UE may also indicate in a release assistance information in the NAS PDU whether downlink data transmission (eg, acknowledgement or response to uplink data) after the uplink data transmission is expected. If the NAS PDU is a control plane service request message including an ESM data transmission message, the release assistance information may also be included in the ESM data transmission message. In operation (2), the NAS PDU transmitted in operation 1 is relayed to the MME by the eNodeB using an S1-AP initial UE message. In order to assist the MME in any NAS PDU retransmission policy, the eNB may indicate the coverage level of the UE to the MME.

In one aspect, the following items can also be performed in Figure 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 may decompress the IP header if header compression is applied to the packet data network (PDN) connection. The MME can execute (and the UE can respond to) any security related procedures. Operations 4 through 9 can be parallel to this, but operations 10 and 11 can wait for the completion of all security related programs. In operation 4, if the S11-U connection is not established, the MME may send a modified bearer request message (MME address, MME TEID DL, delayed downlink packet notification request, radio access technology (RAT) type ) to the service gateway (GW).

In operation 5, if the RAT type has changed compared to the most recently reported RAT type, or if the UE's location and/or information IE and/or UE time zone and service network id appear in operation 4, Then the service GW may send the modified bearer request message (RAT type) to the PDN GW. In operation 6, the PDN GW may send the modified bearer response to the serving GW. In operation 7, if a modify bearer request message is sent in operation 4, the serving GW may return a modified bearer response (service GW address and tunneling endpoint identifier for uplink traffic). (TEID)) The MME is given a response to a modified bearer request message. In operation 8, the MME may send uplink information to the P-GW via the S-GW. The P-GW can forward the uplink data to an application server in a packet data network (PDN) (not shown). If the P-GW receives downlink data from the PDN, for example, an acknowledgment or response to the uplink data from the application server (not shown), then operations 9-14 may be performed. . That is, for a UE in EMM connected mode, operations 9-14 exhibit an example of a mobile terminated (MT) data transmission in control plane CIoT EPS optimization with P-GW connectivity. In operation 9, the P-GW may send downlink data to the MME via the S-GW. In operation 10, the MME may perform encryption and integrity protection on the downlink data. In operation 11, the downlink data is encapsulated in a NAS PDU and sent to the eNB with an S1-AP downlink message. For example, the NAS PDU may be an encrypted ESM data transmission message including one of the downlink user data. In operation 12, the eNB may send an RRC downlink information message including the downlink data encapsulated in the NAS PDU. In operation 11, after the S1-AP message with the NAS DATA PDU is followed by an S1 UE environment release command, after the downlink data of the NAS PDU is transmitted to the UE, the operation 14 is performed. It is done quickly 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 reconstruct the Internet Protocol (IP) header. In operation 13, the eNB may initiate an S1 release in operation 14 if there is no NAS PDU activity for a period of time. In operation 14, an S1 release procedure can be performed.

As shown in FIG. 3B, such related operations for MT data transmission in the NAS PDU may be in operations 5-6 and 13-14. That is, in operation 5-6, the UE is in an ECM idle state. Upon receiving a paging indication, the UE may send a UE-triggered service request NAS message through an RRC connection request and the S1-AP initial message. When the C-IoT control plane is optimized for use, the service request NAS message does not trigger the data radio bearer setup by the MME, and the MME can immediately send the received downlink data to the eNodeB using a NAS PDU. . The MME can monitor the paging procedure with a timer. If the MME does not receive a response to the paging request message from the UE, it may repeat the paging according to any applicable paging policy described in operation 3.

If the MME does not receive a response from the UE after the repeat paging procedure, the MME may use the downlink material notification rejection message to notify the serving GW that the paging failure has occurred (or equivalently, if The buffer is in the MME, and the MME can simply discard the data for the UE locally) unless the MME knows that an MM program that prevents the UE from responding is in progress, that is, the MME receives the indication The UE performs an environment request message of another MME's Tracking Area Update (TAU). When receiving the downlink data notification rejection message, the service GW may delete the (etc.) buffered packet. If the UE is in the ECM idle state and the PDN GW has enabled the "PDN Charging Suspend" function, the serving GW may invoke the P-GW to suspend the charging procedure. If the buffer is in the MME, the suspended charging is triggered by the MME, and the request includes a "radio link abnormal release" cause, which is released via a release access to the S-GW. The S11-U.

Thus, in Figures 3A-3B, the present technology provides a particular structure for a NAS data PDU that includes an ESM message encapsulated or contained in an EMM message, as shown in Figure 3A, where the same The ESM message can be used for the NAS profile PDU in operations 15-16 of Figure 3B, for the network initiated scenario illustrated in operations 13-14 of Figure 3B, and for operation 11-12 in Figure 3A. in. That is, because the transmission of the user profile is associated with a particular EPS delivery - characterized by a particular EPS-carrying identification - the ESM layer can be involved in the UE-initiated scenario also used in Figure 3A. In transit. On the other hand, since the UE should only send 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 profile in the EMM message. This will be more fully described in these continuing paragraphs. Transfer user data in the NAS PDU via the MME program

In one aspect, in an evolved packet system (EPS) attachment procedure, a network can initiate a predetermined EPS carrier environment (ie, if the UE requests a packet data network "PDN" in the attach request Connectivity). In addition, a network can initiate one or several dedicated EPS carrying environments in parallel for an IP PDN type PDN connection. To this end, an EPS conference management message for a preset EPS delivery environment initiation may be transmitted in an information element of the EPS mobility management messages. In this case, the UE and the network can execute the attach procedure, the preset EPS carrying environment launching program, and the dedicated EPS carrying environment launching program in parallel. The UE and the network may complete a combined preset EPS carrying environment launching procedure and the attaching procedure before the dedicated EPS carrying environment launching procedure is completed. The success of the attachment procedure depends on the success of the preset EPS delivery environment launcher. If the attachment fails, the ESM programs will also fail.

A UE using an EPS service optimized with a control plane CIoT EPS can initiate transmission of user data via a control plane. Control plane CIoT EPS optimization may include signaling optimization for efficient transmission of user data (IP, non-IP or SMS) over the control plane via the MME, including selective header compression of IP data . To this end, a UE in an Evolution Packet System (EPS) Mobility Management (EMM)-Idle mode can initiate the service request procedure and transmit an ESM data transmission message in an information element of the control plane service request message. . In addition to the attach procedure and the service request procedure, the MME may suspend the transmission of the ESM message during the EMM procedure. The MME may suspend the sending of ESM messages during the service request procedure. In addition to the attach procedure for the user data transmission initiated by the UE of the control plane and the service request procedure, the UE may suspend the transmission of the ESM message during the EMM procedure.

In one aspect, transmission of the UE-initiated user profile can be performed in a NAS PDU via the MME. It should be noted that one of the purposes of transmitting user data in a NAS PDU via an MME procedure is carried on the control plane between the UE and the MME and between the MME and the UE. User data in the NAS message. The program can be initiated by the UE or the network.

Upon receiving a request to transmit user profile via the MME, if the UE is in the EMM idle mode, the EMM entity in the UE may initiate the procedure by sending a control plane service request (which is also It may be referred to as a "data service request" or, equivalently, a "control plane service request" message, the message including an ESM container message IE containing the information to be sent in the ESM data transmission message data. The data service type of the control plane service request message may indicate an "action origination request" for the UE initiator.

Upon receiving the ESM data transmission message, the MME may identify the carrier (eg, the service capability exposure function "SCEF" connection), based on the EPS carrier identification included in the ESM data transmission message, on a core network The user data is transmitted by the road, and then the contents of the user data container IE are transferred accordingly.

The UE may 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 may indicate "integrity protected and encrypted initial NAS message" as shown in FIG. The UE may provide an indication in an IE, such as the "Additional Information" IE or the "Release Auxiliary Indication" IE in the control plane service request message, indicating whether subsequent transmission of the uplink data is expected Downlink data. In one aspect, the additional information or "release assistance indication" may be an information element included in the ESM data transmission message and not in the control plane service request. As used herein, "Additional Information" and "Release Auxiliary Instructions" may be used interchangeably.

Upon receiving a request from one or more upper layers associated with the UE (eg, an application layer within the UE) to transmit user profiles via the control plane, if the UE is in the EMM-CONNECTED In the mode, the ESM entity in the UE can initiate the procedure by sending a separate ESM DATA TRANSPORT message. Network-initiated user data transmission in the NAS PDU via the MME

Upon receiving a paging message indicating that "user data is transmitted via the control plane", the UE may respond with a control plane service request message. The data service type of the control plane service request message may indicate an "action termination request". The UE may 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 may indicate "initial protected and encrypted initial NAS messages" (see Figure 12).

Upon receiving the control plane service request message with the type of data service indicating the "action termination request", the network may send an ESM DATA TRANSPORT message. When receiving the ESM data transmission message, the UE may forward the content of the user data container IE to an upper layer, and use the EPS to carry the identification. CONTROL PLANE SERVICE REQUEST ( message definition)

A control plane service request message (e.g., a data service request message) can be sent by the UE to the network to carry an ESM message in an encapsulated format, as shown in table 400 of FIG. (It should be noted that the "Data Service Request Message" and "Control Plan Service Request Message" used in this document can be used interchangeably. The control plane service request message type is a CONTROL PLANE SERVICE REQUEST. The control plane service request The meaning of the message is bidirectional, and the direction can be from the UE to the network. The content of the control plane service request message can include the information element, the type/reference, the appearance, the format, and the length. As depicted in the text, "Note 1" indicates that in a variation of the present technique, additional information may be defined in a TLV format of 3 bytes in length. Further, the spare nibble may include the NAS KSI. Device properties

If the UE is configured for the NAS signaling low priority level, the UE may include a device feature information element IE. Additional information

In one aspect, if an uplink data transmission (eg, an acknowledgment or response) is expected after the uplink data transmission, the UE may include an additional information IE or a "release assistance indication" IE. It should be noted that the "Additional Information" IE can be used interchangeably with the term "Release Auxiliary Instruction". ESM message container

The UE may include an ESM Message Container IE during an action originated control plane service request. Security-protected initial NAS message ( message definition)

In one aspect, a security-protected initial NAS message can be transmitted by the UE to transmit an initial NAS message along with the sequence number and the message authentication code that protects the message, as shown in table 500 of FIG. The security-protected initial NAS message type may be a security-protected initial NAS message. The security-protected initial NAS message is bidirectional, and the direction can be from the UE to the network. NAS messages with enhanced security protection ( message definition)

In one aspect, an enhanced security protected NAS message can be transmitted by the UE or the network to transmit a security-protected NAS message along with the sequence number and the message authentication code that protects the message, as shown in the figure. Table 600 of 6 shows. The enhanced security protected NAS message type can be an enhanced security protected NAS message. The enhanced security protected NAS message may be bidirectional, and the direction may be from the UE to the network or from the network to the UE. ESM DATA TRANSPORT ( message definition)

In one aspect, an ESM data transmission message can be transmitted by the UE or the network to perform (transmit) user data in an encapsulated format, as shown in table 700 of FIG. The ESM data transmission message type may be an ESM data transmission message. The meaning of the ESM data transmission message can be bidirectional, and the direction can be from the UE to the network or vice versa. Release auxiliary instructions or "additional information"

In one aspect, a UE may include one or more Release Assistance Information IEs if a downlink data transmission (eg, an acknowledgment or response) is expected after the uplink data transmission.

For example, using one or more of the protocols, procedures, and/or embodiments as described herein, each message other than a SERVICE REQUEST message may be one as defined in 3GPP TS 24.007, v 13.0.0. L3 message. Therefore, the release of the auxiliary information message may include one or more of the following: 1) if the message is a normal NAS message: a) the protocol discriminator; b) the EPS carrying identification or security header type; c) the program Transaction recognition; d) message type; e) other information elements. 2) If the message is a security-protected NAS message: a) the protocol discriminator; b) the security header type; c) the message authentication code; d) the sequence number; e) the normal 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) Alternate nibble [or: stream identification]; g) M-TMSI; h) normal NAS message, as defined in 1. In one aspect, the UE may include only the control plane service request message in the normal NAS message field.

In one aspect, the organization of a generic NAS message is illustrated in the table 800 of FIG. That is, FIG. 8 illustrates a table 800 for an organizational structure of a non-access stratum (NAS) message. Table 8 includes an EPS-carrying identification or security header type, protocol discriminator, program transaction identification, message type, and/or other information elements. Figure 9 illustrates a table 900 for one of the security-protected non-access stratum (NAS) messages. Table 9 includes a security header type, protocol discriminator, message authentication code, sequence number, and/or a NAS message. Figure 10 illustrates a table 1000 for one of the organization structures for security protection of initial non-access stratum (NAS) messages. Table 1000 includes the security header type, protocol discriminator, message authentication code, sequence number, NAS key set identifier, alternate nibble, a mobile action user identification "M-TMSI", and/or NAS message. .

It should be noted that it is possible to include a globally unique temporary identification (ID) "GUTI" instead of an M-TMSI. The security-protected initial NAS message can then also be used when the UE is transmitting a first message in a new tracking area. If an individual NAS message stream with a different "stream identification code" is used, another security header type can be used, such as shown in FIG.

For example, a first-class identifier = 0 (binary "0000") can be used for NAS messages that are not used to transmit user data (these are, for example, all NAS messages specified in 3GPP TS 23.401 Rel-12 and earlier). ), and the stream identifier = 1 (binary "0001") is used for the NAS message used to transmit the user data (for example, the ESM data transmission message, or the control plane service request message if it includes an ESM data transmission message) if).

This organization of an enhanced security protected NAS message is shown in the table 1100 of FIG. That is, FIG. 11 illustrates an organizational structure table 1100 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 Figure 10, a spare nibble in byte 7 can be a first-class identification - indicating the respective Which NAS message stream belongs to, and therefore which serial number (and an overflow counter) and which carrier ID can be used for the decryption of the NAS message. In one aspect, the unique NAS message allowed to be included in the security-protected initial NAS message is the control plane service request message and allowed to be included in the enhanced security protection NAS message or the control plane service request The only NAS message in the message is the ESM data transmission message.

In one aspect, the EPS payload identification and the program transaction identification are only used in messages having a protocol discriminator EPS talk management. A byte 1a (see Fig. 8) having a program change identification can only be included in a message having a protocol discriminator EPS talk management. In one aspect, a particular information element can only appear once in a given message.

In one aspect, when a field of a message extends beyond a byte, the value of that location of a bit gradually decreases as the number of bytes increases. The least significant bit of the field is represented by the lowest numbered bit of the highest numbered byte of the field. Security header type

Referring now to Figure 12, a table 1200 illustrates a security header type information element (IE). In one aspect, bits 5 through 8 of the first byte of each EPS mobility management (EMM) message contain a security header type IE. The security header type IE may include control information related to the security protection of a NAS message. The overall size of the security header type IE can be at least 4 bits. The security header type IE can take the values shown in the table 1200. It should be noted that 1) Note 1 indicates that the code point may only apply to a SECURITY MODE COMMAND message, 2) Note 2 indicates that the code point may only apply to a SECURITY MODE COMPLETE message, and 3) Note 3 indicates when the bit is specified When 7 and 8 are set to '11', bits 5 and 6 can be used for future expansion of the SERVICE REQUEST message.

In one aspect, an EMM message can be encoded with a security header type that can be encoded as "0000" and can be treated as a non-security-protected, normal NAS message. A protocol entity that sends a non-secure protected EMM message can send the message as a normal NAS message and encode the security header type to "0000". Message type

In one aspect, the message type IE and its use can be defined in 3GPP TS 24.007, V 13.0.0. Referring now to Figures 13 and 14, Figure 13 illustrates a table 1300 for various message types for Evolution Packet System (EPS) mobility management and Figure 14 illustrates an Evolution Packet System (EPS) session management. Table 1400 of various message types. Figures 13-14 define this portion of the value of the message type IE used in the EPS Mobility Management Agreement and EPS Talk Management Agreement. Data service type

In one aspect, the purpose of the data service type information element is to specify the purpose of the control plane service request procedure. Referring now to Figures 15-19, Figure 15 illustrates a table 1500 of a data service type information element (IE), and Figure 16 illustrates an additional table 1600 of a data service type information element (IE) with additional information. Figure 17 illustrates a table 1700 of additional information elements (IEs), Figure 18 illustrates a table 1800 for an alternative to an additional information element (IE), and Figure 19 illustrates an additional A table 1900 of a third alternative to information elements (IE).

In one aspect, bit 4 in Figure 16 can be used for an alternate purpose, such as for use as an "active" flag indication. In addition, as shown in FIG. 17, the purpose of the additional information information element (or "release assistance indication") is to specify whether downlink (DL) data is expected or expected after the uplink data transmission (eg, Confirmation or response to uplink "UL" information). The additional informational element is encoded as shown in FIG. The additional information can be a type 1 information element. In one aspect, FIG. 18 depicts an alternative 2 additional information element and FIG. 19 depicts an alternative 3 additional information element, which can be a type 4 information element. It should be noted that the encoding and bits used in this Figure 15-19 for this encoding are only depicted as examples. It should be noted that the encoding of Figures 15-19 may have one or more of a variety of different encodings and bits for the release assistance indication. User data container

In one aspect, the user profile container information element can be used to encapsulate the transferred material between the UE and the MME. The user profile container information element can be encoded as shown in table 2000 of FIG. In one aspect, the material via the MME container can be a type 6 information element.

Accordingly, as described herein, the present technology provides a User Equipment (UE) device that enhances and optimizes features and functions related to a cellular Internet of Things (CIoT) for connection to An EPS network that is also enhanced with its CIoT characteristics. The EPS network may include entities such as eNB, MME, SGW, PGW, SCEF (Service Capability Exposure Function), and the like.

The UE may transmit the action originated data to the MME via the control plane and the network may transmit action termination (MT) information to the UE via the control plane. If the UE is in the EMM-IDLE mode, the EMM entity in the UE may initiate the data transfer procedure via the control plane by sending a CONTROL PLANE SERVICE REQUEST message. The CONTROL PLANE SERVICE REQUEST message includes an ESM Container Message IE containing the material to be sent in the ESM DATA TRANSPORT message. The data service type of the CONTROL PLANE SERVICE REQUEST message indicates "action origination request". In one aspect, if the UE is in the EMM-IDLE mode, the UE can reuse the extended service request message to carry the ESM DATA TRANSPORT message. The UE may send the CONTROL PLANE SERVICE REQUEST message as part of a security-protected initial NAS message. The security header type that securely protects the initial NAS message can indicate "initial NAS messages that are integrity protected and encrypted." If the UE is in the EMM-CONNECTED mode, the user data received from the one or more upper layers associated with the UE, such as an application layer within the UE, is to be transmitted via the control plane. Upon request, the ESM entity in the UE can initiate the data transfer procedure by sending a separate ESM DATA TRANSPORT message. Upon receiving the ESM DATA TRANSPORT message, the technology can identify the bearer (eg, the SCEF connection), and transmit the user within the core network based on the EPS bearer identification included in the ESM DATA TRANSPORT message. The data is then forwarded accordingly to the content of the user profile container IE.

If the termination of action (MT) data is available to the UE, a network can page the UE. In one aspect, the network can indicate whether to "transmit the data via the control plane" or "transmit the data via the user plane" based on UE preferences and capabilities. Upon receiving a paging message indicating that "user data is transmitted via the control plane", the UE may respond with a CONTROL PLANE SERVICE REQUEST message. The data service type of the CONTROL PLANE SERVICE REQUEST message may indicate an "action termination request". The UE may send the CONTROL PLANE SERVICE REQUEST message as part of a security-protected initial NAS message. The security header type that securely protects the initial NAS message will indicate "initial protected and encrypted initial NAS messages." Once the CONTROL PLANE SERVICE REQUEST with the type of data service indicating the "action termination request" is received, the network can send an ESM DATA TRANSPORT message. Upon receiving the ESM DATA TRANSPORT message, the UE may use the EPS bearer identification to forward the content of the user profile container IE to the upper layer.

Referring now to Figure 21, an example provides a User Equipment (UE) function 2100 for communicating with a wireless communication network using a scheduled request transmission of a cmWave system, as in the flow chart of Figure 21 Show. The function 2100 can be implemented as a method or a function can be executed as instructions on a machine, wherein the instructions are included in one or more computer readable media or one or more non-transitory machine readable Take the storage media. The UE may include one or more processors. In one embodiment, the one or more processors may include a baseband processor and/or an application processor. The one or more processors may be configured to process a service request message having an evolved packet system for transmitting user data to a mobility management entity (MME) via a control plane (EPS) An Information Element (IE) of the Interview Management (ESM) data transmission message, which includes user data, wherein the ESM data transmission message includes an EPS carrying identification (ID) associated with the user data. The MME is enabled to identify a packet data network (PDN) connection, as at block 2110. The UE may include one or more processors, the one or more processors being configured to process user data transfer between the UE and the MME via the control plane, as in block 2120 .

More specifically, in order to transmit user data to a mobility management entity (MME) via a control plane, the UE can process a control plane service request message having the ESM message container containing an ESM data transmission message. An information element (IE), which includes user data, wherein the data ESM transmission message enables the MME to identify an EPS carrier identification (ID) associated with the material.

Referring now to FIG. 22, an example provides a User Equipment (UE) function 2200 for communicating with a wireless communication network using a schedule request transmission of a cmWave system, as in the flow chart of FIG. Show. The function 2200 can be implemented as a method or a function can be executed as instructions on a machine, wherein the instructions are included in one or more computer readable media or one or more non-transitory machine readable Take the storage media. The UE may include one or more processors that are configured to: assemble a transceiver of the UE when operating in an Evolution Packet System (EPS) mobility management ( EMM) - When in idle mode, a paging message can be received from a network, as in 2210. The UE may include one or more processors that are configured to process a service request message, such as in 2220, for transmission to a Mobility Management Entity (MME). The UE may include one or more processors, the one or more processors being configured to: a transceiver that assembles the UE to receive an evolved packet system (EPS) conference management from the MME ( ESM) Information Element (IE) for data transmission messages, including user data, as in 2230. The UE may include one or more processors, and the one or more processors are configured to: when receiving the ESM data transmission request message from a network, between the UE and the MME The control plane processes the user profile for transmission to one or more upper layers associated with the UE, as in block 2240.

In addition, the UE can be configured with a transceiver of the UE to receive a paging message from the eNodeB. A control plane service request message can be processed for transmission to a Mobility Management Entity (MME). A transceiver of the UE can be configured to receive an evolved packet system (EPS) message management (ESM) message container information element (IE) containing an ESM data transmission message from the eNodeB, including the data. The user profile can be forwarded to the upper layer of the UE using an EPS bearer identification (ID) associated with the profile via the control plane between the UE and the MME.

Another example provides a function 2300 of an eNodeB operable to communicate with a user equipment (UE) using one of a cmWave system scheduling requests within a wireless communication network, as in the flow chart of FIG. Show. The function 2300 can be implemented as a method or the function can be executed as instructions on a machine, wherein the instructions are included in one or more computer readable media or one or more non-transitory machine readable Take the storage media. The eNodeB can include one or more processors that are configured to: when operating in an Evolution Packet System (EPS) Mobility Management (EMM)-Idle mode, for transmission To the UE, a page message received from a network is processed, as in block 2310. The eNodeB may include one or more processors, the one or more processors being configured to: a transceiver assembling the eNodeB to receive a service request message from the UE via the control plane, An information element (IE), the IE includes an evolved packet system (EPS) conference management (ESM) data transmission message including the user data, for transmitting the service request message to a mobility management entity (MME), As in block 2320. The eNodeB can include one or more processors and memory, the processors and memory being configured to: receive for transmission to the MME via the control plane processing between the UE and the MME The user data obtained is as in block 2330.

Referring now to FIG. 24, an example provides a User Equipment (UE) function 2400 for enabling a cellular Internet of Things (CIoT) function for transmitting user data via a control plane for movement within a wireless communication network. The Attribute Management Entity (MME) communicates as shown in the flow chart of FIG. The function 2400 can be implemented as a method or a function can be executed as instructions on a machine, wherein the instructions are included in one or more computer readable media or one or more non-transitory machine readable Take the storage media. The UE may include one or more processors, the one or more processors being configured to: incorporate user data in an information element (IE) into an Evolution Packet System (EPS) conference management ( The ESM) data transfer message is used to transmit the user profile to a Mobility Management Entity (MME) via the control plane, as in block 2410. The UE may include one or more processors, and the one or more processors are configured to: include an EPS bearer identification associated with the user profile in the ESM data transmission message, such as In block 2420. The UE may include one or more processors, the one or more processors being configured to: encode the ESM data transmission message for transmission to the MME via the control plane, such that the MME can identify a A packet data network (PDN) connection and forwarding the user profile based on the EPS delivery ID, as in block 2430. The UE can further include a memory device that is 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 carrying ID.

Referring now to FIG. 25, an example provides a functionality of a Mobile Management Entity (MME) that enables a cellular Internet of Things (CIoT) function 2500 for transmitting user data via a control plane for use with a user within a wireless communication network. The device (UE) communicates as shown in the flow chart of FIG. The function 2500 can be implemented as a method or a function can be executed as instructions on a machine, wherein the instructions are included in one or more computer readable media or one or more non-transitory machine readable Take the storage media. The MME may include one or more processors, the one or more processors being configured to: incorporate user data in an information element (IE) into an Evolution Packet System (EPS) conference management ( The ESM) data transmission message is used to transmit the user profile to a UE via the control plane, as in block 2510. The MME may include one or more processors, the one or more processors being configured to: include an EPS bearer identification associated with the user profile in the ESM data transmission message, such as In block 2520. The MME may include one or more processors, the one or more processors being configured to: encode the ESM data transmission message for transmission to the UE via the control plane, wherein the EPS carries identification such that The UE can forward the user profile to one or more upper layers of the UE based on the EPS Carry ID, as in block 2530. The MME can further include a memory device that is 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 carrying ID.

Figure 26 illustrates a schematic diagram of a wireless device (e.g., a UE), according to an example. 26 provides an example illustration of the wireless device, such as a user equipment (UE) UE, a mobile station (MS), a type of mobile wireless device, a mobile communication device, a tablet computer, a handheld device, or other Type of wireless device. In one aspect, the wireless device can include an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, and a non-powered device. At least one of a sexual memory, and a combination thereof.

The wireless device can include one or more antennas that are configured to communicate with a node or a transmitting station, such as a base station (BS), an evolved Node B (eNB), a baseband unit (BBU), and a Remote radio head (RRH), a remote radio (RRE), a relay (RS), a radio (RE), a remote radio unit (RRU), a central processing module (CPM), or Other types of wireless wide area network (WWAN) access points. The wireless device can be configured to communicate using at least one of 3GPP LTE, WiMAX, High Speed Packet Access (HSPA), Bluetooth, and Wi-Fi. The wireless device can communicate using a separate antenna for each wireless communication standard or a shared antenna 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 in communication with the application processor, the graphics processor, the display, the non-volatile memory, and/or internal memory. In one aspect, the application processor and graphics processor are storage media.

Figure 27 illustrates an example component of a device in accordance with some embodiments. In some embodiments, the apparatus 2700 can include an application circuit 2702, a baseband circuit 2704, a radio frequency (RF) circuit 2706, a front end module (FEM) circuit 2708, and one or more antennas 2710, at least as shown Ground coupled together. The components of the illustrated device 2700 can be included in a UE or a RAN node. In some embodiments, the device 2700 can include fewer components (eg, a RAN node can not use the application circuit 2702, but includes a processor/controller to process IP data received from an EPC). . In some embodiments, the device 2700 can include additional components such as, for example, a memory/storage device, a display, a camera, a sensor, and/or an input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (eg, the circuits may be separately included in one of the cloud-RAN (C-RAN) implementations) In the above device).

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

The baseband circuit 2704 can include circuitry such as, but not limited to, one or more single core or multi-core processors. The baseband circuit 2704 can include one or more baseband processors and/or control logic for processing a baseband signal received from a signal path received by one of the RF circuits 2706 and generating a signal for the RF circuit 2706. A baseband signal that transmits a signal path. The baseband processing circuit 2704 can interface the application circuit 2702 for the generation and processing of the baseband signals and for controlling the operation of the RF circuitry 2706. For example, in some embodiments, the baseband circuit 2704 can include a second generation (2G) baseband processor 2704a, a third generation (3G) baseband processor 2704b, and a fourth generation (4G) baseband processor. 2704c, and/or other baseband processors 2704d are used in other generations, in development, or in future generations (eg, fifth generation (5G), 6G, etc.). The baseband circuitry 2704 (e.g., one or more of the baseband processors 2704a-d) can process 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 functions of the baseband processors 2704a-d may be included in a module stored in the memory 2704g and executed via a central processing unit (CPU) 2704e. Such radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, and the like. In some embodiments, the modulation/demodulation circuitry of the baseband circuit 2704 can include Fast Fourier Transform (FFT), precoding, and/or constellation mapping/demapping functionality. In some embodiments, the encoding/decoding circuitry of the baseband circuit 2704 can include convolution, cyclic convolution, turbo, Viterbi, and/or low density parity check (LDPC) encoder/decoder functionality. Embodiments of the functions of modulation/demodulation and encoding/decoder are not limited to these examples, and may include other suitable functions in other embodiments.

In some embodiments, the baseband circuit can include one or more audio digital signal processors (DSPs) 2704f. The (equal) audio DSP 2704f may include compression/decompression and echo cancellation components, and may include other suitable processing elements in other embodiments. The components of the baseband circuit can be suitably combined in a single wafer, in a single wafer set, or in some embodiments on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 2704 and the application circuit 2702 can be implemented together, such as, for example, on a system single chip (SOC).

In some embodiments, the baseband circuit 2704 can provide communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuit 2704 can support an evolved universal terrestrial radio access network (EUTRAN) and/or other wireless metro network (WMAN), a wireless local area network (WLAN), a Wireless Personal Area Network (WPAN) communicates. In some embodiments, the radio communication in the baseband circuit 2704 that is configured to support more than one wireless protocol may be referred to as a multi-mode baseband processing circuit.

The RF circuit 2706 can enable communication with the wireless network via modulated non-solid media using modulated electromagnetic radiation. In various examples, the RF circuit 2706 can include switches, filters, amplifiers, and the like to facilitate communication with the wireless network. The RF circuit 2706 can include a receive signal path that can include circuitry to downconvert the RF signal received from the FEM circuit 2708 and provide a baseband signal to the baseband circuit 2704. The RF circuit 2706 can also include a transmit signal path that can include circuitry to upconvert the baseband signal provided by the baseband circuit 2704 and provide an RF output signal to the FEM circuit 2708 for transmission.

In some examples, the RF circuit 2706 can include a receive signal path and a transmit signal path. The receive signal path of the RF circuit 2706 can include a mixer circuit 2706a, an amplifier circuit 2706b, and a filter circuit 2706c. The transmit signal path of the RF circuit 2706 can include a filter circuit 2706c and a mixer circuit 2706a. The RF circuit 2706 can also include a frequency synthesizer circuit 2706d to synthesize a frequency from the receive signal path and the mixer circuit 2706a of the transmit signal path. In some embodiments, the mixer circuit 2706a of the receive signal path can be configured to downconvert the RF signal received from the FEM circuit 2708 based on the synthesized frequency provided by the synthesizer circuit 2706d. The amplifier circuit 2706b can be configured to amplify the downconverted signals and the filter circuit 2706c can be configured to remove unwanted signals from the downconverted signals to produce an output baseband signal A low pass filter (LPF) or band pass filter (BPF). The output baseband signal can be provided to the baseband circuit 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, the mixer circuit 2706a of the receive signal path can include a passive mixer, although the scope of the embodiments is not limited in this respect.

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

In some embodiments, the mixer circuit 2706a of the receive signal path and the mixer circuit 2706a of the transmit signal path may comprise two or more mixers and may be respectively arranged for orthogonal downwards Frequency conversion and / or up conversion. In some embodiments, the mixer circuit 2706a of the receive signal path and the mixer circuit 2706a of the transmit signal path may include two or more mixers and may be arranged for image rejection (eg, , Hartley image suppression). In some embodiments, the mixer circuit 2706a and the mixer circuit 2706a of the receive signal path can be arranged to be directly downconverted and/or directly upconverted, respectively. In some embodiments, the mixer circuit 2706a of the receive signal path and the mixer circuit 2706a of the transmit signal path can be configured for superheterodyne operation.

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 alternative embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternative embodiments, the RF circuit 2706 can include an analog to digital converter (ADC) and a digital to analog converter (DAC) circuit and the baseband circuit 2704 can include a digital baseband interface to interface with the RF circuit 2706 for communication.

In some dual mode embodiments, a separate radio IC circuit can be provided for processing the signals for each of the spectra, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuit 2706d can be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect, as other types of frequencies Synthesizers may be suitable. For example, synthesizer circuit 2706d can be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer including a phase-locked loop with one of the frequency dividers.

Based on a frequency input and a divider control input, the synthesizer circuit 2706d can be configured to synthesize an output frequency for use by the mixer circuit 2706a of the RF circuit 2706. In some embodiments, the synthesizer circuit 2706d can be a fractional N/N+1 synthesizer.

In some embodiments, the frequency input can be provided by a voltage controlled oscillator (VCO), although that is not a requirement. The divider control input can be provided by either the baseband circuit 2704 or by the application processor 2702, depending on the desired output frequency. In some embodiments, a divide control input (e.g., N) can be determined from a lookup table based on one of the channels indicated by the application processor 2702.

The synthesis circuit 2706d of the RF circuit 2706 can include a frequency divider, a delay locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the divider can be a dual analog frequency divider (DMD) and the phase accumulator can be a digital phase accumulator (DPA). In some embodiments, the DMD can be configured to divide the input signal by N or N+1 (eg, based on a carry output) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascade tunable delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements can be configured to break up a VCO period into Nd equal phase packets, where Nd is the number of delay elements in the delay line. In this manner, the DLL provides negative feedback to help ensure that the total delay through the delay line is a VCO period.

In some embodiments, synthesizer circuit 2706d can be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency can be a multiple of the carrier frequency (eg, the carrier frequency Twice, four times the carrier frequency) and used with quadrature generator and divider circuits to generate multiple signals at the carrier frequency and have multiple different phases with respect to each other. In some embodiments, the output frequency can be an LO frequency (fLO). In some embodiments, the RF circuit 2706 can include an IQ/polarity converter.

FEM circuit 2708 can include a receive signal path that can include circuitry configured to operate on an RF signal received from one or more antennas 2710, amplify the received signal and provide an amplified version of the received signal to The RF circuit 2706 is used for further processing. The FEM circuit 2708 can also include a transmit signal path that can include circuitry that is configured to amplify signals provided by the RF circuit 2706 for transmission for transmission by one or more of the one or more antennas 2710. .

In some embodiments, the FEM circuit 2708 can include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuit can include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit can include a low noise amplifier (LNA) to amplify the received RF signal and provide the amplified received RF signal as an output (e.g., to the RF circuit 2706). The transmit signal path of the FEM circuit 2708 can include a power amplifier (PA) to amplify the input RF signal (eg, provided by the RF circuit 2706) and one or more filters to generate the RF signal for subsequent transmission (eg, One or more of the one or more antennas 2710.

In some embodiments, the device 2700 includes a plurality of power saving mechanisms. If the device 2700 is in an RRC_Connected state in which it is still connected to the RAN node because it expects to receive traffic soon, it may enter a discontinuous reception mode (DRX) after a period of inactivity. a state of one. During this state, the device can be powered down for a short time interval and thus save power.

If there is no data traffic activity for an extended period of time, the device 2700 can transition to an RRC_idle state where it will disconnect from the network and not perform operations such as channel quality feedback, handover, and the like. . The device 2700 enters a very low power state and performs paging where it periodically wakes up again to listen to the network and then power down again. The device cannot receive data in this state, and in order to receive the data, it can transition back to the RRC_Connected state.

An additional power save mode allows the network to be unable to use a device for a period of time greater than one paging interval (from seconds to hours). During this time, the device is completely unable to connect to the network and can be completely powered down. Any information sent during this time will incur a large delay and is assumed to be acceptable.

The processor of the application circuit 2702 and the processor of the baseband circuit 2704 can be used to perform elements of one or more instances of a protocol stack. For example, the processor of the baseband circuit 2704, alone or in combination, can be used to perform the functions of Layer 3, Layer 2, and/or Layer 1, and the processor of the application circuit 2704 can utilize the receiving Data from these layers (eg, packet data) and further implementation of Layer 4 functions (eg, Transport Protocol (TCP) and User Datagram Protocol (UDP) layers). As mentioned herein, Layer 3 may include a Radio Resource Control (RRC) layer, which is described in further detail below. As mentioned herein, Layer 2 may include a Media Access Control (MAC) layer, a Radio Link Control (RLC) layer, and a Packet Data Convergence Protocol (PDCP) layer, which will be Further details are described. As mentioned herein, layer 1 may include a physical (PHY) layer of a UE/RAN node, which will be described in further detail below.

Figure 28 illustrates an example interface of a baseband circuit in accordance with some embodiments. As discussed above, the baseband circuit 2704 of FIG. 27 can include processors 2704A-2704E and a memory 2704G used by the processors. Each of the processors 2704A-2704E can include a memory interface 2804A-2804E for transmitting data to and receiving data from the memory 2704G.

The baseband circuit 2704 can further include one or more interfaces for communicatively coupling to other circuits/devices, such as a memory interface 2812 (eg, an interface for transmitting data to external memory of the baseband circuit 2704) Or receiving data from it, an application circuit interface 2814 (eg, an interface for transmitting data to or receiving data from the application circuit 2702 of FIG. 27), an RF circuit interface 2816 (eg, an interface) To transmit data to or receive data from the RF circuit 2706 of FIG. 27, and a wireless hardware connection interface 2818 (eg, an interface for transmitting data to near field communication (NFC) components, Bluetooth components (eg, Bluetooth low) Energy), Wi-Fi® components, and other communication components to receive data from).

29 shows a schematic diagram 2900 of a node 2910 (e.g., an eNB and/or a base station) and a wireless device (e.g., a UE), according to an example. The node may include a base station (BS), a Node B (NB), an evolved Node B (eNB), a baseband unit (BBU), a remote radio head (RRH), and a remote radio ( 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 assembled to implement the described techniques. 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 to form a circuit 2918 for the node 2910. In one aspect, the transceiver module 2916 and the processing module 2914 can form a circuit 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.

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 described techniques. The node 2910 and the wireless device 2920 can also include one or more storage media, such as transceiver modules 2916, 2924, and/or the processing modules 2914, 2922. In one aspect, the components of the transceiver module 2916 described herein can be included in one or more separate devices that can be used in a cloud-RAN (C-RAN) environment. Instance

The following examples are directed to specific embodiments and are intended to be used in combination or in other ways to implement the specific features, elements, or operations of the embodiments.

Example 1 includes a device for enabling a cellular Internet Protocol (CIoT) enabled user equipment (UE) for transmitting user data via a control plane, the device comprising: one or more processors, the one Or a plurality of processors are configured to: incorporate user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for use by the control plane The data is transmitted to a mobility management entity (MME); an EPS bearer identification associated with the user profile is included in the ESM data transmission message; and the ESM data transmission message is encoded for transmission via the control plane The MME is given to enable the MME to identify a Packet Data Network (PDN) connection and forward the user profile based on the EPS Carry ID.

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

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 transmission message.

Example 4 includes the apparatus of example 2, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

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

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) in the service request message to request the service request message Recognized as a request originated by an action.

Example 7 includes the apparatus of example 1 or 5, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, the use The profile is in the user data container IE, and a release assistance indicator IE.

Example 8 includes the apparatus of example 1, wherein the one or more processors are further configured to encode the ESM data including the user profile when the UE is in an EPS mobility management (EMM) connection mode The transmission message is for transmission to the MME via the control plane.

Example 9 includes the apparatus of example 1, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification.

The example 10 includes the device of example 1, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, At least one of a non-electrical memory cartridge, and a combination thereof.

Example 11 includes a device for enabling a cellular Internet of Things (CIoT) enabled Mobile Management Entity (MME) for transmitting user profiles via a control plane, the device comprising: one or more processors, the Or a plurality of processors are configured to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for using the control plane Transmitting the user profile to a UE; identifying an EPS payload associated with the user profile in the ESM data transmission message; and encoding the ESM data transmission message for transmission to the UE via the control plane, The EPS bearer identification enables the UE to forward the user profile to one or more upper layers of the UE based on the EPS bearer ID.

Embodiment 12 includes the apparatus of example 11, wherein the one or more processors are further configured to: decode a service request message received from the UE, wherein the service request message includes identifying the service request message as A data service type information element (IE) that terminates the request.

The embodiment 13 includes the apparatus of example 11, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, and the user data. The IE in a user profile container, and a release assistance indicator IE.

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

The example 15 includes the apparatus of example 14, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

Example 16 includes the apparatus of example 11, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification.

Example 17 includes at least one machine readable storage medium having instructions embodied thereon for a device enabled for a cellular Internet of Things (CIoT) enabled user equipment (UE) for user access via a control plane The transmission of data, when executed, causes the UE to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for The control plane transmits the user profile to a mobility management entity (MME); an EPS carrying identification associated with the user profile is included in the ESM data transmission message; and encoding the ESM data transmission message And transmitting to the MME via the control plane, so that the MME can identify a packet data network (PDN) connection and forward the user profile based on the EPS carrying ID.

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

Example 19 includes the at least one machine readable storage medium of example 18, wherein the user data container information element includes a user data container content length and the user data is stored as a user data container content in a byte group .

Example 20 includes the at least one machine readable storage medium of example 17, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to: The UE is in an EPS mobility management (EMM)-idle mode, including the ESM data transmission message in a service request message; and encoding the data service request message for transmission from the UE to the MME via the control plane .

Example 21 includes at least one machine readable storage medium of example 19 or 20, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to: A data service type information element (IE) is encapsulated into the service request message to identify the service request message as an action origination request.

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

Example 23 includes at least one machine readable storage medium of the embodiment 17 or 21, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, and an ESM data transmission. The message identification IE, the user profile in the user data container IE, and a release assistance indicator IE.

The example 24 includes the at least one machine readable storage medium of the example 17, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, and a baseband processor. At least one of an internal memory, a non-electrical memory, and a combination thereof.

Example 25 includes a device for enabling a cellular Internet of Things (CIoT) enabled user equipment (UE) for transmitting user profiles via a control plane, the device comprising: one or more processors, the one or more The plurality of processors are configured to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message, to use the control plane to Transmitting user data to a mobility management entity (MME); including an EPS bearer identification associated with the user profile in the ESM data transmission message; encoding the ESM data transmission message for transmission via the control plane Giving the MME such that the MME can identify a packet data network (PDN) connection and forward the user profile based on the EPS carrier ID; and a memory interface coupled to the one or more processors for Enables a memory to store the user profile.

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

The embodiment 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 transmission message.

The example 28 includes the apparatus of example 27, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

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

The 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) in the service request message to request the service request message Recognized as a request originated by an action.

The example 31 includes the apparatus of example 29, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, and the user data. The IE in a user profile container, and a release assistance indicator IE.

Example 32 includes the apparatus of example 25, wherein the one or more processors are further configured to encode the ESM data including the user profile when the UE is in an EPS mobility management (EMM) connection mode The transmission message is for transmission to the MME via the control plane.

Example 33 includes the apparatus of example 25, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification.

Example 34 includes the apparatus of example 25, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, At least one of a non-electrical memory cartridge, and a combination thereof.

Example 35 includes a device for enabling a cellular Internet of Things (CIoT) enabled Mobile Management Entity (MME) for transmitting user profiles via a control plane, the device comprising: one or more processors, Or a plurality of processors are configured to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for using the control plane Transmitting the user profile to a UE; identifying an EPS payload associated with the user profile in the ESM data transmission message; encoding the ESM data transmission message for transmission to the MME via the control plane, Enabling the MME to identify a packet data network (PDN) connection and forwarding the user profile based on the EPS carrier ID; and a memory interface coupled to the one or more processors to enable a memory Save the user profile.

Embodiment 36 includes the apparatus of example 35, wherein the one or more processors are further configured to: decode a service request message received from the UE, wherein the service request message includes identifying the service request message as A data service type information element (IE) that terminates the request.

The example 37 includes the apparatus of example 35, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, and a user profile. The user profile IE in the container, and a release assistance indicator IE.

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

The example 39 includes the apparatus of example 38, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

The example 40 includes the apparatus of example 35, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification.

Example 41 includes at least one machine readable storage medium having instructions embodied thereon for a cellular enabled Internet of Things (CIoT) enabled user equipment (UE) for user data via a control plane Transmitting, when the instructions are executed, causing the UE to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for The control plane transmits the user profile to a mobility management entity (MME); an EPS bearer identification associated with the user profile is included in the ESM data transmission message; and the ESM data transmission message is encoded for Transmitting the control plane to the MME such that the MME can identify a packet data network (PDN) connection and forward the user profile based on the EPS carried ID; and a memory coupled to the one or more processors The body interface is used to enable a memory to store the user profile.

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

The example 43 includes the at least one machine readable storage medium of the example 42, wherein the user data container information element includes a user data container content length and the user data is stored as a user data container content in a byte group. .

Example 44 includes the at least one machine readable storage medium of example 41, further comprising instructions that, when executed, cause the UE to be executable, wherein the one or more processors are further configured to: when the UE The ESM data transmission message is included in a service request message when in an EPS mobility management (EMM)-idle mode; and the data service request message is encoded for transmission from the UE to the MME via the control plane.

Example 45 includes the at least one machine readable storage medium of example 44, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to: A data service type information element (IE) is encapsulated into the service request message to identify the service request message as an action origination request.

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

The example 47 includes the at least one machine readable storage medium of the example 46, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, and an ESM data transmission message. The IE is identified, the user profile is in the user data container IE, and a release assistance indicator IE.

The example 48 includes the at least one machine readable storage medium of the example 41, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, and a baseband processing At least one of a device, an internal memory, a non-electric memory, and a combination thereof.

Example 49 includes a device for enabling a cellular Internet of Things (CIoT) enabled user equipment (UE) for transmitting user data via a control plane, the device comprising: one or more processors, the Or a plurality of processors are configured to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for using the control plane Transmitting the user profile to a mobility management entity (MME); including an EPS bearer identification associated with the user profile in the ESM data transmission message; and encoding the ESM data transmission message for use via the control The plane is transmitted to the MME such that the MME can identify a packet data network (PDN) connection and forward the user profile based on the EPS carried ID.

The example 50 includes the apparatus of example 49, wherein the information element is a user data container information element.

The example 51 includes the apparatus of example 49 or 50, wherein the one or more processors are further configured to: encapsulate the user profile container information element in the ESM data transfer message, wherein the user profile The container information element includes a user data container content length and the user data is stored as a user data container content in a byte.

In Example 52, the technical subject matter of any of the examples 49 or any of the examples described herein can further include, wherein the one or more processors are further configured to: when the UE is in a EPS mobility management (EMM)-idle mode, in an ESM data transmission message in a service request message; encoding the data service request message for transmission from the UE to the MME via the control plane; and The data service type information element (IE) includes a request to identify the service request message as an action origination to the service request message, wherein the ESM data transmission message includes a protocol authentication information element (IE), the EPS Send identification IE, a program transaction identification IE, an ESM data transmission message identification IE, the user data in a user data container IE, and a release assistance indication IE.

In Example 53, the technical subject matter of any of the examples 49 or any of the examples described herein can further include wherein the one or more processors are further configured to be in an EPS mobility when the UE is in an In the management (EMM) connection mode, the ESM data transmission message including the user profile is encoded for transmission to the MME via the control plane.

In Example 54, the technical subject matter of any of the examples 49 or any of the examples described herein can further include, further comprising a memory that is configured to interface with one or more processors and to store the user The data or the EPS carries one or more of the identified, wherein the UE includes an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, and a At least one of internal memory, a non-electrical memory, and a combination thereof.

Example 55 includes a device for enabling a cellular Internet of Things (CIoT) enabled Mobile Management Entity (MME) for transmitting user profiles via a control plane, the device comprising: one or more processors, Or a plurality of processors are configured to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for using the control plane Transmitting the user profile to a UE; identifying an EPS payload associated with the user profile in the ESM data transmission message; and encoding the ESM data transmission message for transmission to the UE via the control plane, The EPS bearer identification enables the UE to forward the user profile to one or more upper layers of the UE based on the EPS bearer ID.

The example 56 includes the apparatus of example 55, wherein the one or more processors are further configured to: decode a service request message received from the UE, wherein the service request message includes identifying the service request message as A data service type information element (IE) for an action termination request, wherein the ESM data transmission message includes a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, and an ESM data transmission message identification IE, the user data is in a user data container IE, and a release assistance indicator IE, wherein the information element is a user data container information element.

The example 57 includes the apparatus of example 55 or 56, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

In Example 58, the technical subject matter of any of the examples 55 or any of the examples described herein can further include, further comprising a memory that is configured to interface with one or more processors and to store the user The data or the EPS carries one or more of the identified ones.

Example 59 includes at least one machine readable storage medium having instructions embodied thereon for a cellular enabled Internet of Things (CIoT) enabled user equipment (UE) to communicate user data via a control plane When the instructions are executed, the UE may be caused to: include user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for control Transmitting the user profile to a mobility management entity (MME); including an EPS bearer identification associated with the user profile in the ESM data transmission message; and encoding the ESM data transmission message for The control plane transmits to the MME to enable the MME to identify a packet data network (PDN) connection and forward the user profile based on the EPS carried ID.

The example 60 includes the at least one machine readable storage medium of the request item 59, wherein the information element is a user data container information element, and wherein the user data container information element includes a user data container content length and the use The data is stored as a user data container in a byte.

Example 61 includes the at least one machine readable storage medium of claim 59 or 60, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to Transmitting the ESM data transmission message into a service request message when the UE is in an EPS mobility management (EMM)-idle mode; encoding the data service request message for transmitting from the UE to the MME via the control plane Transmitting a data service type information element (IE) into the service request message to identify the service request message as an action origination request; or when the UE is in an EPS mobility management (EMM) In the connected mode, a request to transmit user data from one or more upper layers of the UE via the control plane is received.

In Example 62, the technical subject of any one of the examples 59 or the examples described herein may further include wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, A program transaction identification IE, an ESM data transmission message identification IE, the user data in a user data container IE, and a release assistance indication IE.

In Example 63, the technical subject of any one of the examples 59 or the examples described herein may further include wherein the UE includes an antenna, a touch sensitive display screen, a speaker, a microphone, and a graphics processor. At least one of an application processor, a baseband processor, an internal memory, a non-electric memory, and a combination thereof.

The example 64 includes a device for enabling a cellular Internet Protocol (CIoT) enabled user equipment (UE) for transmitting user data via a control plane, the device comprising: means for including user data in an information An element (IE) is included in an Evolution Packet System (EPS) Talk Management (ESM) data transmission message for transmitting the user profile to a mobility management entity (MME) via the control plane; An EPS carrying identification associated with the user profile is included in the ESM data transmission message; and means for encoding the ESM data transmission message for transmission to the MME via the control plane to enable the MME to identify a A packet data network (PDN) connection and forwarding the user profile based on the EPS carrying ID.

Example 65 includes the apparatus of example 64, wherein the information element is a user data container information element.

The example 66 includes the apparatus of example 64, wherein the user profile container information element includes a user profile container content length and the user profile is stored as a user profile container content in a byte group.

Example 67 includes the apparatus of example 64, further comprising means for: including the ESM data transmission message in a service request message when the UE is in an EPS mobility management (EMM)-idle mode; and encoding the data The service request message is for transmission from the UE to the MME via the control plane.

The example 68 includes the apparatus 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 an action origination request.

Example 69 includes the apparatus of example 64 or 68, further comprising means for receiving, when the UE is in an EPS mobility management (EMM)-connected mode, receiving an attempt to transmit from one or more upper layers of the UE via a control plane A request for user profile.

The example 69 includes the apparatus of the example 64 or 68, further comprising means for: wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, and an ESM data transmission. The message identification IE, the user profile in the user data container IE, and a release assistance indicator IE.

The example 70 includes the device of example 64, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, At least one of a non-electrical memory cartridge, and a combination thereof.

As used herein, the term "circuitry" may be used to include an application-specific integrated circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, Dedicated, or group, or a portion of the above, that executes 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 one or more software or firmware modules, or the functionality associated with the circuitry can be implemented by one or more software or firmware modules. In some aspects, the circuitry can include logic that is at least partially operable in hardware.

Various techniques, or some aspects or portions thereof, may be embodied in tangible media in the form of code (ie, instructions), such as floppy disks, CD-ROMs, hard disks, Non-transitory computer readable storage medium, or any other machine readable storage medium, wherein when the code is loaded into and executed by a machine such as a computer, the machine becomes a practice Devices of these various technologies. The circuitry can include hardware, firmware, 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 a signal. In the case where the code is executed on a planable computer, the computing device can include a processor that can read the storage medium (including the electrical and non-electrical memory and/or the storage component). ) at least one input device and at least one output device. The electrically and non-electrical memory and/or storage component can be a random access memory (RAM), an erasable programmable read only memory (EPROM), a flash memory disk, a compact disk, Magnetic hard disk, solid state hard disk, or other media used to store electronic materials. The node and the wireless device may further include a transceiver module (ie, a transceiver), a counter module (ie, a counter), a processing module (ie, a processor), and/or a clock module (ie, , clock) or timer module (ie, timer). An application interface (API), reusable controls, and the like can be implemented or utilized with one or more of the various techniques described herein. Such a program can be implemented in a high-level procedural or object-oriented programming language for communicating with a computer system. However, the program can be implemented in a combined language or machine language, if desired. In any case, the language can be a compiled or literal language and combined with a hardware implementation.

As used herein, the term processor may include a general purpose processor; a special purpose processor such as a VLSI, FPGA, or other type of dedicated processor; and used in a transceiver for transmitting, receiving, and processing wireless communications. The baseband processor.

It should be understood that many of the functional units described in this specification have been labeled as a module to more specifically emphasize the independence of their implementation. For example, a module can be implemented as a hardware circuit that includes custom ultra-large integrated body (VLSI) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module can also be implemented in a programmable hardware device such as a field programmable gate array, programmable array logic, programmable logic devices, and the like.

Modules can also be implemented in software to be executed by different types of processors. For example, a module identified by one of the executable code can contain one or more entities or logical blocks of computer instructions, for example, which can be organized into an object, program, or function. However, the executable code of the identified module may not be physically placed together, but may include different instructions stored in different locations. When they are logically combined, they form the module. Group and implement the stated purpose of the module.

In fact, a module of executable code can be a single instruction, or many instructions, and can even be spread across several different code segments, different programs, and across multiple memory devices. Similarly, operational data can be identified and illustrated within the module, and can be embodied in any suitable form and organized into any suitable type of data structure. The operational data may be collected as a single data set or may be distributed at different locations including different storage devices, and may at least partially exist as electronic signals on a system or network. The module can be passive, including agents that are operable to perform the desired function.

References to "an example" or "an exemplary" in this specification 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. Therefore, the appearances of the terms "a" or "an"

As used herein, a plurality of items, structural elements, component elements, and/or materials may be presented in a common list for convenience. However, these lists should be interpreted as if each member of the list was individually identified as an independent and unique member. Thus, individual members of such a list should not be interpreted as being the de facto equivalent of any other member of the same list based solely on the fact that they appear in a common group without indicating their dissimilarity. Moreover, various embodiments and examples of the techniques mentioned herein may be substituted for such various components. It is to be understood that such embodiments, examples, and alternatives are not to be construed as being

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 instances, and so forth, to provide a thorough understanding of embodiments of the present technology. However, it will be appreciated by those skilled in the art that the present invention can be practiced without one or more specific details or other methods, components, arrangements, and so forth. In other instances, well-known structures, materials, or operations are not shown or described in detail to avoid obscuring various aspects of the technology.

Although the foregoing examples are described in the context of one or more specific applications, it will be apparent to those skilled in the art that In the case of these principles and concepts, numerous modifications are made to the form, use, and details of the implementation. Therefore, the present technology is not intended to be limiting, except as set forth in the claims below.

100‧‧‧ cell 104‧‧‧eNB 108‧‧‧UE 300, 325‧‧‧ data transmission 400, 500, 600, 700, 800, 900, 1000, 1100, 1200, 1300, 1400, 1500, 1600, 1700, 1800, 1900, 2000‧‧ 2100, 2200, 2300, 2400, 2500‧‧‧ functions 2110~2120, 2210~2240, 2310~2330, 2410~2430, 2510~2530‧‧‧ 2600‧‧‧Wireless devices 2700‧‧‧ device 2702‧‧‧Application Circuit 2704‧‧‧Base frequency circuit 2704a‧‧2G BB 2704b‧‧3G BB 2704c‧‧4G BB 2704d‧‧‧Other baseband processors 2704e‧‧‧CPU 2704f‧‧‧Audio DSP 2704g‧‧‧ memory 2706‧‧‧RF circuit 2706a‧‧‧Mixer circuit 2706b‧‧‧Amplifier Circuit 2706c‧‧‧Filter circuit 2706d‧‧‧Synthesizer circuit 2708‧‧‧FEM 2710‧‧‧Antenna 2804a~2804e, 2812‧‧‧ memory interface 2814‧‧‧Application Circuit Interface 2816‧‧‧RF circuit interface 2818‧‧‧Wireless hardware connection interface 2900‧‧‧ Schematic 2910‧‧‧ nodes 2912‧‧‧node device 2914, 2922‧‧‧Processing Module 2916, 2924‧‧‧ transceiver module 2918‧‧‧ Circuitry 2920‧‧‧Wireless devices

The features and advantages of the present disclosure will become more apparent from the description of the appended claims.

Figure 1 illustrates a mobile communication network within a cell according to an example;

2 is a diagram showing a protocol architecture for an MS supporting an EPS service, according to an example;

3A illustrates an action originating (MO) data transfer diagram in a control plane CIoT EPS optimization connected by a P-GW, according to an example;

3B illustrates a mobile termination (MT) data transmission diagram in a control plane CIoT EPS optimization with P-GW connections, according to an example;

4 shows, according to an example, a data service request message table having a non-access stratum (NAS) key set identification code (KSI) included in a spare nibble;

FIG. 5 illustrates a security-protected initial non-access stratum (NAS) message table, according to an example;

6 illustrates an enhanced security protection non-access stratum (NAS) message table, according to an example;

FIG. 7 illustrates an Evolution Packet System (EPS) Talk Management (ESM) data transmission message table according to an example diagram;

Figure 8 illustrates an organizational structure table for a common non-access stratum (NAS) message, according to an example;

FIG. 9 illustrates an organizational structure table for security-protected non-access stratum (NAS) messages, according to an example;

Figure 10 illustrates an organizational structure table for security-protected initial non-access stratum (NAS) messages, according to an example;

11 illustrates an organizational structure table for a non-access stratum (NAS) message for enhanced security protection, according to an example;

FIG. 12 illustrates a security header type information element (IE) table according to an example diagram;

Figure 13 illustrates various message type tables for Evolution Packet System (EPS) mobility management, according to an example;

Figure 14 illustrates various message type tables for Evolution Packet System (EPS) conference management, according to an example;

Figure 15 illustrates a data service type information element (IE) table according to an example;

16 is an illustration of an additional table of data service type information elements (IEs) with additional information, according to an example;

17 shows an additional information element (IE) table according to an example diagram;

Figure 18 illustrates an alternative scheme for an additional information element (IE), according to an example;

Figure 19 illustrates a third-party alternative scheme for an additional information element (IE), according to an example;

20 is a diagram showing a user data container information element table according to an example;

21 depicts the functionality of a User Equipment (UE) that communicates with a wireless communication network using a scheduling request transmission for a cmWave system, according to an example;

22 depicts, in accordance with an example, an additional function of a user equipment (UE) for communicating within a wireless communication network for a scheduled request transmission using a cmWave system;

23 depicts the functionality of an eNodeB that is operable to communicate with a User Equipment (UE) using a scheduling request transmission for a cmWave system, according to an example;

24 depicts, in accordance with an example, an additional functionality of a cellular enabled Internet of Things (CIoT) enabled user equipment (UE) in communication with a Mobility Management Entity (MME) within a wireless communication network for control via a control Flat user data transfer;

25 depicts, in accordance with an example, an additional functionality of a Mobility Internet of Things (CIoT) enabled Mobility Management Entity (MME) to communicate with a User Equipment (UE) within a wireless communication network for use via a control plane User data transfer;

26 is a schematic diagram showing an example component of a wireless device (eg, user equipment "UE"), according to an example;

27 is a schematic diagram showing an example component of a user equipment (UE) device, according to an example;

28 is a schematic diagram showing an example interface of a baseband circuit according to an example;

29 is a diagram showing a node (e.g., an eNB) and a wireless device (e.g., a UE), according to an example.

Reference will now be made to the exemplary embodiments shown and the specific language will be used. However, it should be understood that there is no intention to limit the scope of the technology.

300‧‧‧ data transmission

Claims (24)

A device for enabling a user equipment (UE) for transmitting user data via a control plane, enabling a cellular Internet of Things (CIoT) function, the device comprising: one or more processors configured to: Incorporating user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message to transmit the user profile to a mobility management entity (MME) via the control plane And an EPS carrying identification associated with the user profile is included in the ESM data transmission message; encoding the ESM data transmission message for transmission to the MME via the control plane, so that the MME can identify a packet A data network (PDN) connection and forwarding the user profile based on the EPS carrier ID; and a memory interface coupled to the one or more processors to enable a memory to store the user profile. The device of claim 1, wherein the information element is a user data container information element. The device of claim 2, wherein the one or more processors are further configured to encapsulate the user data container information element in the ESM data transmission message. The device of claim 3, wherein the user data container information element comprises a user data container content length and the user data is stored as a user data container content in a byte group. The device of claim 1, wherein the one or more processors are further configured to: when the UE is in an EPS mobility management (EMM)-idle mode, one of a service request message The ESM data transmission message; and encoding the data service request message for transmission from the UE to the MME via the control plane. The device of claim 5, wherein the one or more processors are further configured to: include a data service type information element (IE) in the service request message to identify the service request message as an action Originating request. The device of claim 5, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, and the user data in a The IE in the user profile container, and a release assistance indicator IE. The device of claim 1, wherein the one or more processors are further configured to encode the ESM data transmission message including the user profile when the UE is in an EPS mobility management (EMM) connection mode For transmission to the MME via the control plane. The device of claim 1, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification. The device of claim 1, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, a baseband processor, an internal memory, and a non- At least one of an electrical memory cartridge and a combination thereof. A device for enabling a Mobile Management Entity (MME) for transmitting user data via a control plane, enabling a cellular Internet of Things (CIoT) function, the device comprising: one or more processors configured to: Incorporating user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message to transmit the user data to a UE via the control plane; An EPS carrying identification associated with the data is included in the ESM data transmission message; encoding the ESM data transmission message for transmission to the MME via the control plane, so that the MME can identify a packet data network (PDN) connection And forwarding the user profile based on the EPS carrying ID; and a memory interface coupled to the one or more processors for enabling a memory to store the user profile. The device of claim 11, wherein the one or more processors are configured to: decode a service request message received from the UE, wherein the service request message includes identifying the service request message as an action termination request A data service type information element (IE). The device of claim 11, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, an ESM data transmission message identification IE, and the user data in a The IE in the user profile container, and a release assistance indication. The device of claim 13, wherein the information element is a user data container information element. The device of claim 14, wherein the user data container information element comprises a user data container content length and the user data is stored as a user data container content in a byte. The device of claim 11, further comprising a memory that is configured to interface with one or more processors and to store one or more of the user profile or the EPS-carrying identification. At least one machine readable storage medium having instructions embodied thereon for a user equipment (UE) that enables a cellular Internet of Things (CIoT) function to transmit user data via a control plane when When the instruction is executed, the UE: includes user data in an information element (IE) into an Evolution Packet System (EPS) Talk Management (ESM) data transmission message to transmit the user data to the control plane via the control plane a mobility management entity (MME); an EPS bearer identification associated with the user profile is included in the ESM data transmission message; encoding the ESM data transmission message for transmission to the MME via the control plane, Having the MME identify a packet data network (PDN) connection and forward the user profile based on the EPS carrier ID; and a memory interface coupled to the one or more processors to enable a memory to be stored The user profile. The at least one machine readable storage medium of claim 17 wherein the information element is a user data container information element. The at least one machine readable storage medium of claim 18, wherein the user data container information element comprises a user data container content length and the user data is stored as a user data container content in a byte. The at least one machine readable storage medium of claim 17, further comprising instructions that, when executed, enable the UE to be executable, wherein the one or more processors are further configured to: The ESM data transmission message is included in a service request message when in an EPS mobility management (EMM)-idle mode; and the data service request message is encoded for transmission from the UE to the MME via the control plane. The at least one machine readable storage medium of claim 20, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to: A service type information element (IE) is encapsulated into the service request message to identify the service request message as an action origination request. The at least one machine readable storage medium of claim 17, further comprising instructions that, when executed, cause the UE to: wherein the one or more processors are further configured to: When in an EPS mobility management (EMM)-connected mode, a request to transmit user data from one or more upper layers of the UE via the control plane is received. The at least one machine readable storage medium of claim 21, wherein the ESM data transmission message comprises a protocol authentication information element (IE), the EPS delivery identification IE, a program transaction identification IE, and an ESM data transmission message identification. IE, the user profile in the user data container IE, and a release assistance indication. The at least one machine readable storage medium of claim 17, wherein the UE comprises an antenna, a touch sensitive display screen, a speaker, a microphone, a graphics processor, an application processor, and a baseband processor. At least one of an internal memory, a non-electrical memory, and a combination thereof.