Small data communications in a wireless communication network

CROSS REFERENCE TO RELATED APPLICATIONS

0001The present application claims priority to U.S. Provisional Patent Application No. 61/504,054, filed Jul. 1, 2011, the entire specification of which is hereby incorporated by reference in its entirety for all purposes.

FIELD

0002Embodiments of the present disclosure generally relate to the field of wireless communication systems, and more particularly, to techniques and configurations for transmitting small data payloads such as, for example, Machine Type Communication (MTC) data in a wireless communication network.

BACKGROUND

0003Mobile networks that facilitate transfer of information at broadband rates continue to be developed and deployed. Such networks may be colloquially referred to herein as broadband wireless access (BWA) networks. A variety of different device types may be used in broadband wireless technologies. Such devices may include, for example, personal computers, smartphone, laptops, netbooks, ultrabooks, tablets, handheld devices, and other consumer electronics such as music players, digital cameras, etc., that are configured to communicate over the wireless broadband networks.

0004Machine-to-Machine (M2M) may refer to technologies that allow wireless and wired systems to communicate with other devices without any human intervention. M2M may use a device such as, for example, a sensor or meter to collect information, which may be relayed through a network (e.g., wireless, wired, or hybrid) to an application that translates the information into meaningful data. The expansion of BWA networks across the world and accompanying increased speed/bandwidth and reduced power of wireless communication has facilitated growth of M2M communication. Although the amount of data sent by M2M devices is very small, a large number of these devices, in combination, may increase a load on a network. Current techniques for transmitting small data payloads such as machine type communication (MTC) data may be inefficient or incompatible with emerging BWA networks.

BRIEF DESCRIPTION OF THE DRAWINGS

0005Embodiments will be readily understood by the following detailed description in conjunction with the accompanying drawings. To facilitate this description, like reference numerals designate like structural elements. Embodiments are illustrated by way of example and not by way of limitation in the figures of the accompanying drawings.

0006<figref idref="DRAWINGS">FIG. 1</figref> schematically illustrates an example broadband wireless access (BWA) network in accordance with some embodiments.

0007<figref idref="DRAWINGS">FIG. 2</figref> schematically illustrates system architecture for transmitting a small data payload, in accordance with some embodiments.

0008<figref idref="DRAWINGS">FIGS. 3A-3D</figref> schematically illustrate example schemes for transmitting a small data payload, in accordance with some embodiments.

0009<figref idref="DRAWINGS">FIG. 4</figref> schematically illustrates another example scheme for transmitting a small data payload, in accordance with some embodiments.

0010<figref idref="DRAWINGS">FIG. 5</figref> schematically illustrates yet another example scheme for transmitting a small data payload, in accordance with some embodiments.

0011<figref idref="DRAWINGS">FIG. 6</figref> schematically illustrates still yet another example scheme for transmitting a small data payload, in accordance with some embodiments.

0012<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram of a method for sending a small data payload in a BWA network, in accordance with some embodiments.

0013<figref idref="DRAWINGS">FIG. 8</figref> schematically illustrates an example system that may be used to practice various embodiments described herein.

DETAILED DESCRIPTION

0014Embodiments of the present disclosure provide techniques and configurations for transmitting small data payloads such as, for example, Machine Type Communication (MTC) data in a wireless communication network, triggering or monitoring small data communications, and signaling improvements of the same. In the following detailed description, reference is made to the accompanying drawings which form a part hereof, wherein like numerals designate like parts throughout, and in which is shown by way of illustration embodiments in which the subject matter of the present disclosure may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present disclosure. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of embodiments is defined by the appended claims and their equivalents.

0015Various operations are described as multiple discrete operations in turn, in a manner that is most helpful in understanding the claimed subject matter. However, the order of description should not be construed as to imply that these operations are necessarily order dependent. In particular, these operations may not be performed in the order of presentation. Operations described may be performed in a different order than the described embodiment. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.

0016For the purposes of the present disclosure, the phrase “A and/or B” means (A), (B), or (A and B). For the purposes of the present disclosure, the phrase “A, B, and/or C” means (A), (B), (C), (A and B), (A and C), (B and C), or (A, B and C).

0017The description may use the phrases “in an embodiment,” or “in embodiments,” which may each refer to one or more of the same or different embodiments. Furthermore, the terms “comprising,” “including,” “having,” and the like, as used with respect to embodiments of the present disclosure, are synonymous.

0018As used herein, the term “module” may refer to, be part of, or include an Application-Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that execute one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.

0019Example embodiments may be described herein in relation to broadband wireless access (BWA) networks including networks operating in conformance with one or more protocols specified by the 3^rdGeneration Partnership Project (3GPP) and its derivatives, the WiMAX Forum, the Institute for Electrical and Electronic Engineers (IEEE) 802.16 standards (e.g., IEEE 802.16-2005 Amendment), long-term evolution (LTE) project along with any amendments, updates, and/or revisions (e.g., advanced LTE project, ultra mobile broadband (UMB) project (also referred to as “3GPP2”), etc.). IEEE 802.16 compatible BWA networks are generally referred to as WiMAX networks, an acronym that stands for Worldwide Interoperability for Microwave Access, which is a certification mark for products that pass conformity and interoperability tests for the IEEE 802.16 standards. In other embodiments, communication schemes described herein may be compatible with additional/alternative communication standards, specifications, and/or protocols. For example, embodiments of the present disclosure may be applied to other types of wireless networks where similar advantages may be obtained. Such networks may include, but are not limited to, wireless local area networks (WLANs), wireless personal area networks (WPANs) and/or wireless wide area networks (WWANs) such as cellular networks and the like.

0020The following embodiments may be used in a variety of applications including transmitters and receivers of a mobile wireless radio system. Radio systems specifically included within the scope of the embodiments include, but are not limited to, network interface cards (NICs), network adaptors, base stations, access points (APs), relay nodes, enhanced node Bs, gateways, bridges, hubs and satellite radiotelephones. Further, the radio systems within the scope of embodiments may include satellite systems, personal communication systems (PCS), two-way radio systems, global positioning systems (GPS), two-way pagers, personal computers (PCs) and related peripherals, personal digital assistants (PDAs), personal computing accessories and all existing and future arising systems which may be related in nature and to which the principles of the embodiments could be suitably applied.

0021<figref idref="DRAWINGS">FIG. 1</figref> schematically illustrates an example broadband wireless access (BWA) network <b>100</b> in accordance with some embodiments. The BWA network <b>100</b> may include one or more radio access networks (hereinafter “RAN <b>20</b>”) and a core network <b>25</b>.

0022User Equipment (UE) <b>15</b> may access the core network <b>25</b> via a radio link (“link”) with a base station (BS) such as, for example, one of base stations <b>40</b>, <b>42</b>, etc., in the RAN <b>20</b>. The UE <b>15</b> may, for example, be a subscriber station that is configured to communicate with the base stations <b>40</b>, <b>42</b> in conformance with one or more protocols. The following description is provided for an example BWA network <b>100</b> that conforms with 3GPP for ease of discussion, however, subject matter of the present disclosure is not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein. In some embodiments, the base stations <b>40</b>, <b>42</b> may include enhanced Node B (eNB) stations and a UE <b>15</b> that is configured to communicate using a multiple-input and multiple-output (MIMO) communication scheme. One or more antennas of the UE <b>15</b> may be used to concurrently utilize radio resources of multiple respective component carriers (e.g., which may correspond with antennas of eNB stations <b>40</b>, <b>42</b>) of the BWA network <b>100</b>. The UE <b>15</b> may be configured to communicate using Orthogonal Frequency Division Multiple Access (OFDMA) in, e.g., downlink communications, and/or Single-Carrier Frequency Division Multiple Access (SC-FDMA) in, e.g., uplink communications in some embodiments.

0023While <figref idref="DRAWINGS">FIG. 1</figref> generally depicts the UE <b>15</b> as a cellular phone, in various embodiments the UE <b>15</b> may be a personal computer (PC), a notebook, ultrabook, netbook, smartphone, an ultra mobile PC (UMPC), a handheld mobile device, an universal integrated circuit card (UICC), a personal digital assistant (PDA), a Customer Premise Equipment (CPE), a tablet, or other consumer electronics such as MP3 players, digital cameras, and the like. The base stations <b>40</b>, <b>42</b> may include one or more antennas, one or more radio modules to modulate and/or demodulate signals transmitted or received on an air interface, and one or more digital modules to process signals transmitted and received on the air interface.

0024In some embodiments, communication with the UE <b>15</b> via RAN <b>20</b> may be facilitated via one or more nodes <b>45</b>. The one or more nodes <b>45</b> may act as an interface between the core network <b>25</b> and the RAN <b>20</b>. According to various embodiments, the one or more nodes <b>45</b> may include a Mobile Management Entity (MME) (e.g., SGSN/MME <b>58</b> of <figref idref="DRAWINGS">FIG. 2</figref>) that is configured to manage signaling exchanges (e.g., authentication of the UE <b>15</b>) between the base stations <b>40</b>, <b>42</b> and the core network <b>25</b> (e.g., one or more servers <b>50</b>), a Packet Data Network Gateway (PGW) (e.g., GGSN/PGW <b>51</b> of <figref idref="DRAWINGS">FIG. 2</figref>) to provide a gateway router to the Internet <b>65</b>, and/or a Serving Gateway (SGW) to manage user data tunnels or paths between the base stations <b>40</b>, <b>42</b> of the RAN <b>20</b> and the PGW. Other types of nodes may be used in other embodiments.

0025The core network <b>25</b> may include logic (e.g., a module) to provide authentication of the UE <b>15</b> or other actions associated with establishment of a communication link to provide a connected state of the UE <b>15</b> with the BWA network <b>100</b>. For example, the core network <b>25</b> may include one or more servers <b>50</b> that may be communicatively coupled to the base stations <b>40</b>, <b>42</b>. In an embodiment, the one or more servers <b>50</b> may include a Home Subscriber Server (HSS) (e.g., HLR/HSS <b>56</b> of <figref idref="DRAWINGS">FIG. 2</figref>), which may be used to manage user parameters such as a user's International Mobile Subscriber Identity (IMSI), authentication information, and the like. The core network <b>25</b> may include other servers, interfaces, and modules some of which are further described in connection with <figref idref="DRAWINGS">FIG. 2</figref>. The one or more servers <b>50</b> may include over-the-air (OTA) servers in some embodiments. In some embodiments, logic associated with different functionalities of the one or more servers <b>50</b> may be combined to reduce a number of servers, including, for example, being combined in a single machine or module.

0026According to various embodiments, the BWA network <b>100</b> is an Internet Protocol (IP) based network. For example, the core network <b>25</b> may be an IP based network. Interfaces between network nodes (e.g., the one or more nodes <b>45</b>) may be based on IP, including a backhaul connection to the base stations <b>40</b>, <b>42</b>. In some embodiments, the BWA network <b>100</b> includes a Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or Long Term Evolution (LTE) network. In some embodiments, the RAN <b>20</b> may include GSM EDGE Radio Access Network (GERAN) where EDGE stands for Enhanced Data for GSM Evolution, Universal Terrestrial Radio Access Network (UTRAN), or Evolved UTRAN (E-UTRAN. The BWA network <b>100</b> may operate in accordance other network technologies in other embodiments.

0027<figref idref="DRAWINGS">FIG. 2</figref> schematically illustrates system architecture <b>200</b> for transmitting a small data payload, in accordance with some embodiments. The system architecture <b>200</b> may be configured to efficiently perform small data transmissions intended for use with Machine-to-Machine (M2M) communication such as, for example, MTC communication. For example, user equipment (UE) <b>15</b> may include or be communicatively coupled with smart meters or sensors to collect small amounts of information for transmission (e.g., health monitoring devices, vending machines, and the like configured to collect information about temperature, inventory, etc.). In some embodiments, an Application server <b>26</b> may be configured to send a small data payload in a message (e.g., to request MTC information such as sensor or meter measurement, inventory level, etc.). The data payload (e.g., MTC data payload) may be smaller than a preconfigured threshold to define a small data payload in some embodiments. The preconfigured threshold may be set by subscription or network operator policy in some embodiments.

0028According to various embodiments, the small data payload may be sent by the UE <b>15</b> to an MTC server <b>52</b> or Application server <b>26</b> via RAN <b>20</b> and core network <b>25</b> or the small data payload may be sent by the Application server <b>26</b> or MTC server <b>52</b> to the UE <b>15</b> via the core network <b>25</b> and the RAN <b>20</b>. For example, an Application server <b>26</b> may be configured (e.g., by an MTC user) to send or trigger sending of a small data payload to user equipment (UE) <b>15</b>. The Application server <b>26</b> may be communicatively coupled with the core network <b>25</b> using, for example, an Internet connection (e.g., Internet <b>65</b> of <figref idref="DRAWINGS">FIG. 1</figref>). In another example, an MTC application <b>24</b> that is communicatively coupled with the UE <b>15</b> may be configured to send or trigger the sending of a small data payload to the Application server <b>26</b>. In some embodiments, the UE <b>15</b> is an MTC device configured to send or receive small data payloads and/or communicate with the MTC application <b>24</b>. In some embodiments, the UE <b>15</b> may include the MTC application <b>24</b>.

0029The system architecture <b>200</b> includes an MTC server <b>52</b>, which is configured to connect to the core network <b>25</b> to communicate with UEs (e.g., UE <b>15</b>) that are configured for MTC communication. The MTC server <b>52</b> may be further configured to communicate with an Interworking Function (IWF) such as MTC-IWF <b>54</b> to trigger a transmission of a small data payload. In some embodiments, the MTC server <b>52</b> may be referred to as a Services Capability Server (SCS).

0030The MTC-IWF <b>54</b> may terminate an MTCsp reference point or interface (hereinafter “reference point”) between the MTC server <b>52</b> and the MTC-IWF <b>43</b>. The MTC-IWF <b>43</b> may be configured to hide internal public land mobile network (PLMN) topology and relay or translate signaling protocols used over the MTCsp reference point to invoke specific functionality in the PLMN. In some embodiments, the MTC-IWF <b>54</b> may authenticate the MTC server <b>52</b> before communication is established with the core network <b>25</b> and/or control plane requests from the MTC server <b>52</b> are authorized. According to various embodiments, the dashed lines between modules (e.g., <b>54</b>, <b>58</b>) represent a control plane and the solid lines between modules represent a user plane. While a particular plane may be shown between modules, other embodiments may include additional/alternative planes.

0031In one embodiment, the MTC-IWF <b>54</b> may terminate an MTCx reference point between a module including a Mobility Management Entity (MME) and/or a Serving GPRS (General Packet Radio Service) Support Node (SGSN) such as, for example, SGSN/MME <b>58</b>. In some embodiments, a first MTCx1 reference point may terminate on the MME of the SGSN/MME <b>58</b> and a second MTCx2 reference point may terminate on the SGSN of the SGSN/MME <b>58</b>. In another embodiment, the MTC-IWF <b>54</b> may terminate an MTCy reference point between a module including a Home Location Register (HLR) and/or Home Subscriber Server (HSS) such as, for example, HLR/HSS <b>56</b>. In another embodiment, the MTC-IWF <b>54</b> may terminate an MTCz reference point between a module including a Gateway GPRS Support Node (GGSN) and/or Packet Data Network Gateway (PGW) such as, for example, GGSN/PGW <b>51</b>. The MTCx, MTCy, and MTCz reference points are not limited to the example names provided (e.g., MTCx, MTCy, and MTCz) and may be referred to by other names in other embodiments.

0032According to various embodiments, the MTCx reference point may be used to send control packet information to a network (e.g., a 3GPP PLMN) based on an indication from the MTC server <b>52</b>. The MTCy reference point may be used to derive routing information for a downlink small data payload by obtaining a network identifier (e.g., 3GPP internal device identifier such as IMSI or Mobile Station International Subscriber Directory Number (MSISDN)) from an MTC device identifier or MTC application identifier. The MTCz reference point may be used for sending a small data payload over a user plane to GGSN/PGW <b>51</b>. According to various embodiments, the system architecture <b>200</b> may include one or more of the MTCx, MTCy, or MTCz reference points in various combinations. For example, the system architecture <b>200</b> may include only the reference points MTCx and MTCy in one embodiment. In another embodiment, the system architecture <b>200</b> may include only the reference point MTCz. In other embodiments, the system architecture <b>200</b> may include all of the MTCx, MTCy and MTCz reference points. The system architecture <b>200</b> may further include Gr/S6a/S6d reference points between the HLR/HSS <b>56</b> and the SGSN/MME <b>58</b>, reference point MTCi between the MTC server <b>52</b> and the GGSN/PGW <b>51</b>, reference point Application Programming Interface (API) between the Application server <b>26</b> and the MTC server <b>52</b>, reference point S1 between the SGSN/MME <b>58</b> and the RAN <b>20</b>, and reference points Um/Uu/LTE-UU between the RAN <b>20</b> and the UE <b>15</b>.

0033The system architecture <b>200</b> may support transmission of small data payloads with little network impact such as signaling overhead, network resources, or delay for reallocation. In some embodiments, the UE <b>15</b> may be attached (e.g., by an established Radio Resource Control (RRC) connection) or detached from the RAN <b>20</b> before transmission of the small data payload (e.g., when the small data payload transmission is triggered). The UE <b>15</b> may be in connected mode or idle mode when the small data payload transmission is triggered in some embodiments. The system architecture <b>200</b> (e.g., the MTC-IWF <b>54</b>) may be configured with a policy that preferentially sends the small data payload over a user plane data path established between the UE <b>15</b> and the GGSN/PGW <b>51</b> and the MTCz interface when the UE <b>15</b> is in connected mode and over a control plane using one of the MTCx or MTCy reference points when the UE <b>15</b> is in idle mode. In some embodiments, when the UE <b>15</b> is in idle mode, the system architecture <b>200</b> may be configured to preferentially send the small data payload over the MTCx reference point.

0034According to various embodiments, the system architecture <b>200</b> may be configured to send the small data payload over one or more of the MTCx, MTCy, or MTCz reference points in various combinations. For example, the system architecture <b>200</b> may be configured to only send the small data payload over the reference points MTCx and MTCy in one embodiment. In another embodiment, the system architecture may be configured to only send the small data payload over the reference point MTCz. In other embodiments, the system architecture <b>200</b> may be configured to send the small data payload directly over all of the reference points MTCx, MTCy and MTCz. In other embodiments, the system architecture <b>200</b> may be configured to only send the small data payload over the reference points MTCz and only one of MTCx or MTCy. The system architecture <b>200</b> may be configured to send the small data payload over other reference points than described in other embodiments.

0035<figref idref="DRAWINGS">FIG. 3</figref><i>a </i>schematically illustrates an example scheme <b>300</b><i>a </i>for transmitting a small data payload, in accordance with some embodiments. The scheme <b>300</b><i>a </i>depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCx reference point according to a first technique, T1.

0036Referring to <figref idref="DRAWINGS">FIGS. 2 and 3</figref><i>a</i>, at <b>302</b>, the MTC server <b>52</b> may send a message to the MTC-IWF <b>54</b> to trigger transmission of a small data payload. The MTC server <b>52</b> may include an MTC device identification (ID) and/or an MTC application (e.g., MTC application <b>24</b>) ID in the message to indicate a target UE (e.g., UE <b>15</b>) to receive the small data payload. The MTC server <b>52</b> may further include in the message, or otherwise send, the small data payload to the MTC-IWF <b>54</b> in some embodiments. In other embodiments, an Application server <b>26</b> may directly send the small data payload to the MTC-IWF <b>54</b>. In some embodiments, a secure connection may be established between the MTC-IWF <b>54</b> and the MTC server <b>52</b> for transmissions at <b>302</b>.

0037At <b>304</b>, in response to receiving the trigger at <b>302</b>, the MTC-IWF <b>54</b> may Query the HLR/HSS <b>56</b> to obtain routing information to deliver the small data payload to the UE <b>15</b> over the MTCx reference point. In some embodiments, the MTC-IWF <b>54</b> may send the MTC device ID to the HLR/HSS <b>56</b>, which may have the MTC Device ID as part of an MTC subscription. The HLR/HSS <b>56</b> may map the MTC Device ID to an IMSI of the UE <b>15</b> and send the IMSI along with an address for the SGSN/MME <b>58</b> back to the MTC-IWF <b>54</b>. A trust relation may be established between the MTC-IWF <b>54</b> and the HLR/HSS <b>56</b> in some embodiments (e.g., when the MTC-IWF <b>54</b> is outside of a domain of an operator of the core network). In response to receiving the query at <b>304</b> from the MTC-IWF <b>54</b>, the HLR/HSS <b>56</b> may send to the MTC-IWF <b>54</b> IMSI serving node identities and/or other information such as operator policy, authorization information, failure indication with cause value, and the like.

0038At <b>306</b>, the MTC-IWF <b>54</b> may send the small data payload and a request (e.g., Forward Small Data request) to forward the small data payload, to the SGSN/MME <b>58</b> over the MTCx reference point. The MTC-IWF <b>54</b> may use the IMSI to send the request and the small data payload to the SGSN/MME <b>58</b>.

0039In accordance with the first technique T1 of sending the small data payload from the SGSN/MME <b>68</b> to the UE <b>15</b>, the SGSN/MME <b>58</b> may determine that the UE <b>15</b> is in a connected state and, at <b>308</b><i>a</i>, forward the small data payload to the UE <b>15</b> using uplink/downlink (UL/DL) Non-Access Stratum (NAS) signaling. For example, the SGSN/MME <b>58</b> may determine that the UE <b>15</b> is in a connected state by determining that a context (e.g., locally stored) already exists to indicate a location for the UE <b>15</b>. The SGSN/MME <b>58</b> may send the small data payload to the UE <b>15</b> using, for example a downlink Non-Access Stratum (NAS) transport message. An acknowledgement that the small data payload has been sent to the UE <b>15</b> may be received by the SGSN/MME <b>58</b> during communications at <b>308</b><i>a. </i>

0040At <b>316</b>, the SGSN/MME <b>58</b> may forward to the MTC-IWF <b>54</b> the acknowledgement that the small data payload has been sent to the UE <b>15</b>. At <b>318</b>, the MTC-IWF <b>54</b> may send a trigger to the MTC server <b>52</b> to send an acknowledgement that the small data payload has been delivered to the UE <b>15</b>. The MTC server <b>52</b> may, for example, send the acknowledgement to the Application server <b>26</b> in response to the trigger.

0041<figref idref="DRAWINGS">FIG. 3</figref><i>b </i>schematically illustrates an example scheme <b>300</b><i>b </i>for transmitting a small data payload, in accordance with some embodiments. The scheme <b>300</b><i>b </i>depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCx reference point according to a second technique, T2. Actions from <b>302</b> to <b>306</b> and from <b>316</b> to <b>318</b> of scheme <b>300</b><i>b </i>may comport with embodiments described for same numbered actions of scheme <b>300</b><i>a. </i>

0042In accordance with the second technique T2 of sending the small data payload from the SGSN/MME <b>68</b> to the UE <b>15</b>, the SGSN/MME <b>58</b> may determine that the UE <b>15</b> is in an idle state and, at <b>308</b><i>b</i>, may send the small data payload to the RAN <b>20</b> (e.g., base station <b>40</b> or <b>42</b> of <figref idref="DRAWINGS">FIG. 1</figref>) in a paging message. The RAN <b>20</b> may send, at <b>310</b><i>b</i>, the paging message including the small data payload to the UE <b>15</b>. For example, the small data payload may be included in a paging message that is broadcasted in a tracking area of a target UE <b>15</b> that is in idle mode. The SGSN/MME <b>58</b> may be configured to send the paging message including the small data payload over a control plane in some embodiments. In some embodiments, the RAN <b>20</b> may inform the SGSN/MME <b>58</b> that the small data payload was successfully delivered by sending, at <b>314</b><i>b</i>, a small data acknowledgement to the SGSN/MME <b>58</b>, which may be forwarded to the MTC-IWF <b>54</b> at <b>316</b>.

0043<figref idref="DRAWINGS">FIG. 3</figref><i>c </i>schematically illustrates an example scheme <b>300</b><i>c </i>for transmitting a small data payload, in accordance with some embodiments. The scheme <b>300</b><i>c </i>depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCx reference point according to a third technique, T3. Actions from <b>302</b> to <b>306</b> and from <b>316</b> to <b>318</b> of scheme <b>300</b><i>c </i>may comport with embodiments described for same numbered actions of scheme <b>300</b><i>a. </i>

0044In accordance with the third technique T3 of sending the small data payload from the SGSN/MME <b>68</b> to the UE <b>15</b>, the SGSN/MME <b>58</b> may determine that the UE <b>15</b> is in an idle state and, at <b>308</b><i>c</i>, may send a paging message including the small data payload to the RAN <b>20</b> (e.g., base station <b>40</b> or <b>42</b> of <figref idref="DRAWINGS">FIG. 1</figref>). The paging message may further include an optional small data indicator to indicate that the small data payload is at the RAN <b>20</b> (e.g., at base station <b>40</b> or <b>42</b> of <figref idref="DRAWINGS">FIG. 1</figref>). In some embodiments, the SGSN/MME <b>58</b> may send the small data payload over the S1 reference point to RAN <b>20</b>.

0045In some embodiments, the RAN <b>20</b> may retrieve and/or store the small data payload from the paging message and send, at <b>310</b><i>c</i>, a paging message to the UE <b>15</b> without the small data payload. The RAN <b>20</b> may include the small data indicator with the paging message. In some embodiments where the small data payload is at the RAN <b>20</b> prior to the UE <b>15</b> being attached to the RAN <b>20</b> (e.g., by RRC connection), the UE <b>15</b> may receive the paging message sent at <b>310</b><i>c </i>with the small data indicator indicating that the small data payload is at the RAN <b>20</b>.

0046At <b>312</b><i>c</i>, the UE <b>15</b> may begin an attachment process to the RAN <b>20</b> by, e.g., establishment of an RRC connection. For example, the establishment of the RRC connection may be requested by the UE <b>15</b> in an RRC connection request message to the RAN <b>20</b> in response to the paging message at <b>310</b><i>c</i>. The RAN <b>20</b> may deliver the small data payload to the UE <b>15</b> via signals associated with the RRC connection setup procedure. When the UE <b>15</b> receives the small data payload, the UE <b>15</b> may terminate the RRC connection setup procedure and may return to an idle mode if no other data is to be sent or received by the UE <b>15</b>. In some embodiments, the RAN <b>20</b> may inform the SGSN/MME <b>58</b> that the small data payload was successfully delivered by sending, at <b>314</b><i>c</i>, a small data acknowledgement to the SGSN/MME <b>58</b>.

0047<figref idref="DRAWINGS">FIG. 3</figref><i>d </i>schematically illustrates an example scheme <b>300</b><i>d </i>for transmitting a small data payload, in accordance with some embodiments. The scheme <b>300</b><i>d </i>depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCx reference point according to a fourth technique, T4. Actions from <b>302</b> to <b>306</b> and from <b>316</b> to <b>318</b> of scheme <b>300</b><i>d </i>may comport with embodiments described for same numbered actions of scheme <b>300</b><i>a. </i>

0048In accordance with the fourth technique T4 of sending the small data payload from the SGSN/MME <b>68</b> to the UE <b>15</b>, the SGSN/MME <b>58</b> may determine that the UE <b>15</b> is in an idle state and, at <b>308</b><i>d</i>, may send a paging message that may include a small data indicator that indicates a presence of the small data payload at the SGSN/MME <b>58</b> that needs to be delivered or forwarded to the UE <b>15</b>. At <b>310</b><i>d</i>, the RAN <b>20</b> may send the paging message, which may include the small data indicator to the UE <b>15</b> to indicate that the small data payload targeted for the UE <b>15</b> is at the SGSN/MME <b>58</b>. In some embodiments where the small data payload is at the SGSN/MME <b>58</b> prior to the UE <b>15</b> being attached to the RAN <b>20</b> (e.g., by RRC connection), the UE <b>15</b> may receive the paging message sent at <b>310</b><i>d </i>with the small data indicator indicating that the small data payload is at the SGSN/MME <b>58</b>. In response to the paging message at <b>310</b><i>d</i>, the UE <b>15</b>, at <b>312</b><i>d</i>, may begin an attachment process to the RAN <b>20</b> by, e.g., establishment of an RRC connection and, at <b>314</b><i>d</i>, begin an attachment process with the SGSN/MME <b>58</b> by sending a Non-Access Stratum (NAS) message such as an attach/service request message to the RAN <b>20</b>. The RAN <b>20</b> may forward the NAS message to the SGSN/MME <b>58</b>. During the attachment process at <b>314</b><i>d</i>, the SGSN/MME <b>58</b> may send the small data payload to the UE <b>15</b> using Non-Access Stratum (NAS) signaling e.g. attach response, service request response, DL NAS transport message, etc.

0049The content of the NAS message sent by the UE <b>15</b> to begin the attachment process at <b>314</b><i>d </i>may depend on the content of the paging message received by the UE <b>15</b> at <b>310</b><i>d</i>. For example, in a case where the paging message at <b>310</b> contains only the small data indicator indicating that the small data payload is at the SGSN/MME <b>58</b>, the UE <b>15</b> may include an information element including a Key Set Identifier (KSI), which may be associated with cipher and integrity keys, and a sequence number, which may be a counter value for the UE <b>15</b>, in the NAS message. The MME of the SGSN/MME <b>58</b> may use the KSI, the sequence number and a Temporary Mobile Subscriber Identity (TMSI) value such as an S-TMSI, where the S refers to System Architecture Evolution (SAE), to encrypt the small data payload for delivery to the UE <b>15</b>. When the UE <b>15</b> receives the small data payload, the UE <b>15</b> may terminate the attachment process and may be configured to return to an idle mode if no other data is to be sent or received by the UE <b>15</b>.

0050In some embodiments where the paging message sent at <b>310</b><i>d </i>includes the small data payload (e.g., at <b>310</b><i>b </i>of <figref idref="DRAWINGS">FIG. 3</figref><i>b</i>), the UE <b>15</b> may or may not be required by network operator policy to send a response message to the small data payload from the MTC server <b>52</b>. In a case where network operator policy does not require sending of any response, the UE <b>15</b> may be configured to include an information element including an acknowledgement such as an MTC data acknowledgement in the NAS message that is sent to begin the attachment process at <b>314</b><i>d</i>. In a case where network operator policy requires sending of a response, the UE <b>15</b> may include an information element including the KSI and sequence number and an encrypted response payload as a NAS Packet Data Unit (PDU) in a NAS container in the NAS message that is sent to begin the attachment process at <b>314</b><i>d</i>. If the UE <b>15</b> has multiple response messages or more data to fit in the NAS container at <b>314</b><i>d</i>, the UE <b>15</b> may indicate in the NAS container that more data is to follow. After the attach/service request message has been sent by the UE <b>15</b> to begin the attachment process at <b>314</b><i>d</i>, the UE <b>15</b> may include the additional data in a NAS PDU in an uplink information transfer message to the SGSN/MME <b>58</b>. In some embodiments, if the UE <b>15</b> has an uplink small data payload to send to the MTC server <b>52</b>, the UE <b>15</b> may activate Packet Data Protocol (PDP) Context and/or PDP bearers and send uplink data on a user plane (e.g., via GGSN/PGW <b>51</b> of <figref idref="DRAWINGS">FIG. 2</figref>).

0051In embodiments where the NAS message (e.g., of attachment process at <b>314</b><i>d</i>) sent by the UE <b>15</b> to the SGSN/MME <b>58</b> includes only the KSI and the sequence number (e.g., a case where the paging message at <b>310</b><i>d </i>contains only the small data indicator indicating that the small data payload is at the SGSN/MME <b>58</b>), the SGSN/MME <b>58</b> may send the small data payload in an encrypted information element in a NAS message such as, for example, an encrypted information element in a NAS PDU in an S1 downlink NAS transport message to the UE <b>15</b>. The UE <b>15</b> may send a response message or an acknowledgement in response to the NAS message with the small data payload. The acknowledgement may include, for example, an acknowledgement in an encrypted information element in a NAS PDU in an uplink information transfer message. The UE <b>15</b> may further include in the response message or acknowledgement, an information element in the uplink information transfer message to request the release of the RRC connection at <b>312</b><i>d </i>if the UE <b>15</b> does not have further data to send.

0052In some embodiments, if the NAS message (e.g., attach/service request message) that is sent to begin the attachment process at <b>314</b><i>d </i>includes the information element including an acknowledgement such as an MTC data acknowledgement (e.g., a case where network operator policy does not require sending of a response to reception by the UE <b>15</b> of the small data payload), the SGSN/MME <b>58</b> may send or forward the data acknowledgement to the MTC-IWF <b>54</b> at <b>316</b><i>d</i>. If the NAS message (e.g., attach/service request message) that is sent to begin the attachment process at <b>314</b><i>d </i>includes an information element including the KSI and sequence number and an encrypted response payload as a NAS Packet Data Unit (PDU) in a NAS container (e.g., a case where network operator policy requires sending of a response to indicate reception by the UE <b>15</b> of the small data payload), the SGSN/MME <b>58</b> may decrypt the NAS PDU and forward, at <b>316</b><i>d</i>, the response payload to the MTC-IWF <b>54</b>. The SGSN/MME <b>58</b> may also send an acknowledgement in an encrypted information element in a NAS PDU in an S1 downlink NAS transport message to the UE <b>15</b>.

0053In some embodiments, the S1 downlink NAS transport message may include an information element that allows the MME of the SGSN/MME <b>58</b> to request the base station of the RAN <b>20</b> to release the RRC connection at <b>312</b><i>d</i>. The MME may not use this indication if the UE <b>15</b> previously indicated that multiple response messages are to be transferred.

0054<figref idref="DRAWINGS">FIG. 4</figref> schematically illustrates another example scheme <b>400</b> for transmitting a small data payload, in accordance with some embodiments. The scheme <b>400</b> depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCy reference point. The scheme <b>400</b> may comport with embodiments described in connection with schemes <b>300</b><i>a</i>-<i>d </i>of <figref idref="DRAWINGS">FIGS. 3</figref><i>a</i>-<b>3</b><i>d </i>except where otherwise indicated. For example, the small data payload may be sent, at <b>415</b>, from the SGSN/MME <b>58</b> to the UE <b>15</b> according to the first, second, third, or fourth techniques (e.g., T1, T2, T3, or T4) as described in connection with <figref idref="DRAWINGS">FIGS. 3</figref><i>a</i>-<b>3</b><i>d. </i>

0055Referring to <figref idref="DRAWINGS">FIGS. 2 and 4</figref>, at <b>302</b>, the MTC server <b>52</b> may send a message to the MTC-IWF <b>54</b> to trigger transmission of a small data payload. The action at <b>302</b> may comport with embodiments described in connection with <b>302</b> of <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>. At <b>404</b>, the MTC-IWF <b>54</b> may send the small data payload and a request (e.g., Forward Small Data request) to forward the small data payload, to the HLR/HSS <b>56</b> over the MTCy reference point. The MTC-IWF <b>54</b> may use MTC device identification (ID) and/or an MTC application ID (ID of MTC Application <b>24</b>) in the message to indicate a target UE (e.g., UE <b>15</b>) to the HLR/HSS <b>56</b>. A trust relation may be established between the MTC-IWF <b>54</b> and the HLR/HSS <b>56</b> in some embodiments (e.g., when the MTC-IWF <b>54</b> is outside of a domain of an operator of the core network).

0056The HLR/HSS <b>56</b> may have the MTC device ID as part of an MTC subscription. The HLR/HSS <b>56</b> may be configured to map the MTC device ID to an IMSI of the UE <b>15</b> and derive the target SGSN/MME <b>58</b>. At <b>406</b>, the HLR/HSS <b>56</b> may send the small data payload to the SGSN/MME <b>58</b> (e.g., over the reference points Gr/S6a/S6d of <figref idref="DRAWINGS">FIG. 2</figref>). The small data payload may be sent, for example, in a notify request message.

0057At <b>415</b>, the SGSN/MME <b>58</b> may send the small data payload to the UE <b>15</b>. At <b>416</b>, the SGSN/MME <b>58</b> may send or forward a response or acknowledgement as described in connection with <figref idref="DRAWINGS">FIGS. 3</figref><i>a</i>-<b>3</b><i>d </i>to the HLR/HSS <b>56</b>. At <b>418</b>, the HLR/HSS <b>56</b> may forward the response or acknowledgement to the MTC-IWF <b>54</b> over the MTCy reference point.

0058At <b>420</b>, the MTC-IWF <b>54</b> may send a trigger to the MTC server <b>52</b> to send an acknowledgement that the small data payload has been delivered to the UE <b>15</b>. The MTC server <b>52</b> may, for example, send the acknowledgement to the Application server <b>26</b>. According to various embodiments, techniques described in connection with <figref idref="DRAWINGS">FIGS. 3</figref><i>a</i>-<b>3</b><i>d </i>and <figref idref="DRAWINGS">FIG. 4</figref> may be combined. For example, the small data payload may be sent over the MTCx reference point and the acknowledgement may be received over the MTCy reference point or vice versa.

0059<figref idref="DRAWINGS">FIG. 5</figref> schematically illustrates yet another example scheme <b>500</b> for transmitting a small data payload, in accordance with some embodiments. The scheme <b>500</b> depicts a method for sending a small data payload (e.g., downlink) to the UE <b>15</b> over the MTCz reference point. The scheme <b>500</b> is described in connection with a Long Term Evolution/Evolved Packet Core (LTE/EPC) system, however, similar concepts may apply to other systems.

0060The MTC server <b>52</b> may receive a trigger to send a small data payload as described in connection with scheme <b>300</b><i>a </i>of <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>. At <b>502</b>, in response to receiving the trigger, the MTC server <b>52</b> may send the small data payload, at <b>504</b>, to PGW <b>42</b> (e.g., PGW of the GGSN/PGW <b>51</b> of <figref idref="DRAWINGS">FIG. 2</figref>) over the MTCz reference point. At <b>506</b>, the PGW <b>42</b> may send the small data payload to a serving gateway (SGW) over an established default bearer.

0061At <b>508</b>, the SGW <b>44</b> may send a downlink data notification message to the MME <b>59</b> and/or at <b>514</b>, the SGW <b>44</b> may send a downlink notification message to the SGSN <b>57</b>. At <b>512</b> the MME <b>59</b> may respond with a downlink data notification acknowledgement message and/or at <b>516</b>, the SGSN <b>57</b> may respond with a downlink data notification acknowledgement message.

0062At <b>518</b>, the MME may send a paging message to the base station if the UE <b>15</b> is registered in the MME. At <b>520</b>, the SGSN <b>57</b> may send a paging message to a Radio Network Controller/Base Station Controller (RNC/BSC) <b>46</b> if the UE is registered in the SGSN <b>57</b>. At <b>522</b>, the base station <b>40</b> may send a paging message to the UE <b>15</b> and/or at <b>524</b>, the RNC/BSC <b>46</b> may send a paging message to the UE <b>15</b>. The paging messages may indicate to the UE <b>15</b> that a downlink small data payload is to be sent to the UE <b>15</b>.

0063At <b>526</b>, in response to the paging message(s) the UE <b>15</b> may perform an attachment process to establish an RRC connection with the base station <b>40</b> and/or RNC/BSC <b>46</b> (e.g., RAN <b>20</b> of <figref idref="DRAWINGS">FIG. 3</figref><i>a</i>). At <b>528</b>, the UE <b>15</b> may perform an attachment process (e.g., a service request procedure) to establish a connection with the MME <b>59</b>, SGSN <b>57</b> and/or SGW <b>44</b>. The SGW <b>44</b> may transmit the small data payload to the UE <b>15</b> via Radio Access Technology (RAT), which may be the RAT used to perform the attachment process at <b>528</b>. According to various embodiments, the RRC connection at <b>526</b> may comport with embodiments described in connection with action <b>312</b><i>c </i>of <figref idref="DRAWINGS">FIG. 3</figref><i>c </i>and the attachment process at <b>528</b> may comport with embodiments described in connection with action <b>314</b><i>d </i>of <figref idref="DRAWINGS">FIG. 3</figref><i>d. </i>

0064<figref idref="DRAWINGS">FIG. 6</figref> schematically illustrates still yet another example scheme <b>600</b> for transmitting a small data payload, in accordance with some embodiments. The scheme <b>600</b> depicts a method for sending a small data payload (e.g., uplink) from the UE <b>15</b> to the MTC server <b>52</b> over the MTCx or MTCy reference points.

0065Referring to <figref idref="DRAWINGS">FIGS. 2 and 6</figref>, the UE <b>15</b> may be triggered by the MTC application <b>24</b> to send a small data payload to the MTC server <b>52</b>. At <b>602</b>, in response to the trigger, the UE <b>15</b> may send a connection request message to RAN <b>20</b>. The UE <b>15</b> may include a NAS module and an Access Stratum (AS) module. In some embodiments, the NAS module may be configured to request the AS module to establish, for example, an RRC connection including a TMSI (e.g., S-TMSI) of the UE <b>15</b> in the connection request message resulting in the action at <b>602</b>. The UE <b>15</b> may include a value that indicates to a base station of RAN <b>20</b> that a short-lived signaling procedure is in progress. For example, the UE <b>15</b> may set a cause value in the connection request message to “mo-Signaling.” Such action may reduce a likelihood that the MME of SGSN/MME <b>58</b> will download a security context to the base station. Without the security context, handover may not be performed. Radio resources can be saved if the base station does not configure the UE <b>15</b> to perform measurement reporting.

0066At <b>604</b>, the base station of the RAN <b>20</b> may send an RRC connection setup message to indicate establishment of the RRC connection. At <b>606</b>, in response to receiving the RRC connection setup message, the UE <b>15</b> may send the small data payload to the base station as part of an RRC setup complete message. The RRC setup complete message may include, for example, a KSI and sequence number and the small data payload in encrypted form. The small data payload may be sent as a NAS PDU in a NAS container in some embodiments.

0067At <b>608</b>, the base station may forward the encrypted small data payload (e.g., in the NAS container) to the MME of the SGSN/MME <b>58</b> in an S1 Application Protocol (S1-AP) initial context message. The MME may be configured to decrypt the small data payload and add identity information of the UE <b>15</b> to a message that includes the small data payload to the MTC-IWF <b>54</b>.

0068The SGSN/MME <b>58</b> may be configured to forward the small data payload to the MTC/IWF <b>54</b> over the MTCx or MTCy reference points. In one embodiment, at <b>610</b>, the SGSN/MME <b>58</b> may forward the small data payload to the HLR/HSS <b>56</b> (e.g., over Gr/S6a/S6d reference points of) and, at <b>612</b>, the HLR/HSS may forward the small data payload to the MTC-IWF <b>54</b> over the MTCy reference. In another embodiment, at <b>614</b>, the SGSN/MME <b>58</b> may be configured to forward the small data payload to the MTC-IWF <b>54</b> directly over the MTCx reference point.

0069At <b>616</b>, the MTC-IWF <b>54</b> may forward the small data payload to the MTC server <b>52</b> (e.g., over the MTCsp reference point). The MTC server <b>52</b> may further forward the small data payload to an Application server <b>26</b>.

0070At <b>618</b>, the SGSN/MME <b>58</b> may send an acknowledgement that the small data payload has been received by the SGSN/MME <b>58</b> or forwarded to the MTC-IWF <b>54</b>. The acknowledgement may be in a message that includes an MTC data acknowledgement information element in an encrypted NAS PDU to the base station in an S1 downlink NAS transport message. In some embodiments, the message may further include an information element that allows the MME of the SGSN/MME <b>58</b> to request the base station of the RAN <b>20</b> to release the RRC connection.

0071At <b>620</b>, the base station of the RAN <b>20</b> may send the acknowledgement message to the UE <b>15</b> and release the RRC connection in an RRC connection release message. The base station may include an MTC data acknowledgement information element as a NAS PDU within the RRC connection release message.

0072In some embodiments, the UE <b>15</b> may perform NAS signaling instead of actions at <b>602</b>-<b>606</b> such as, for example, a tracking area update, service request, attach request, and the like and include the uplink small data payload to the SGSN/MME <b>58</b> using NAS signaling. In some embodiments, the UE <b>15</b> may perform RRC signaling to include the uplink small data payload to the RAN <b>20</b>, which may forward the small data payload to the SGSN/MME <b>58</b> using S1. S1 may be shared and not on a per UE basis.

0073In other embodiments, the UE <b>15</b> may send an uplink small data payload to the MTC server <b>52</b> over a user plane (e.g., over the MTCz reference point). For example, the UE <b>15</b> may establish a connection (e.g., a User Path (UP) connection) with the MTC server <b>52</b> and send the small data payload on a user plane directly to the MTC server <b>52</b> (e.g., over reference point MTCi).

0074<figref idref="DRAWINGS">FIG. 7</figref> is a flow diagram of a method <b>700</b> for sending a small data payload in a BWA network (e.g., BWA network <b>100</b> of <figref idref="DRAWINGS">FIG. 1</figref>), in accordance with some embodiments. The method <b>700</b> may comport with embodiments already described in connection with <figref idref="DRAWINGS">FIGS. 1-6</figref>.

0075Referring to <figref idref="DRAWINGS">FIGS. 2 and 7</figref>, at <b>702</b>, the method <b>700</b> includes receiving a request to send a small data payload to User Equipment (UE) <b>15</b>. For example, the MTC-IWF <b>54</b> may receive a trigger from the MTC server <b>52</b> to request the sending of the small data payload.

0076At <b>704</b>, the method <b>700</b> may further include determining a route for sending the small data payload to the UE <b>15</b>. A module such as the MTC-IWF <b>54</b> in the core network <b>25</b> may be configured to determine the route by determining whether the UE <b>15</b> is in connected or idle mode. For example, the MTC-IWF <b>54</b> may query the HLR/HSS <b>56</b> or the SGSN/MME <b>58</b> to determine whether a context is present for the UE <b>15</b> to determine whether the UE <b>15</b> is connected with the SGSN/MME <b>58</b> or idle. If the UE <b>15</b> is in idle mode, the MTC-IWF <b>54</b> may be routed over one of the MTCx or MTCy reference points. If the UE <b>15</b> is in connected mode, the MTC-IWF <b>54</b> may be routed over the MTCz reference point.

0077In some embodiments, the MTC-IWF <b>54</b> may query the HLR/HSS <b>56</b> or SGSN/MME <b>58</b> to determine a network operator policy and route the information over the MTCx, MTCy, or MTCz reference points according to the network operator policy.

0078In some embodiments, the MTC-IWF <b>54</b> may determine the route by attempting to send the small data payload over the MTCz reference point. If the attempt to send over the MTCz reference point fails for any reason, the MTC-IWF <b>54</b> may attempt to send the small data payload over the MTCx and/or MTCy reference points. For example, if sending by the MTC-IWF over the MTCz reference point to a Packet Data Network Gateway (PGW) fails, the MTC-IWF <b>54</b> may attempt to send the small data payload over the MTCx reference point. If sending by the MTC-IWF over the MTCx reference point fails, the MTC-IWF <b>54</b> may attempt to send the small data payload over the MTCy reference point.

0079In some embodiments, the MTC-IWF <b>54</b> may determine a route by determining whether a data path is established between the UE <b>15</b> and the PGW of GGSN/PGW <b>51</b>. If it is determined that the data path is established, then the MTC-IWF <b>54</b> may route the small data payload over the MTCz reference point, else, the MTC-IWF <b>54</b> may route the small data payload over one of the MTCx or MTCy reference points. Combinations of these techniques may be used to determine a route for sending the small data payload to the UE <b>15</b>.

0080At <b>706</b>, the method <b>700</b> may further include sending the small data payload to the UE <b>15</b>. The small data payload may be sent, for example, using the techniques described in connection with <figref idref="DRAWINGS">FIGS. 3-5</figref>. At <b>708</b>, the method <b>700</b> may further include receiving an acknowledgement that the small data payload was received by the UE <b>15</b>. The acknowledgement may comport with techniques described in connection with <figref idref="DRAWINGS">FIGS. 3-5</figref>.

0081Embodiments of the present disclosure may be implemented into a system using any suitable hardware and/or software to configure as desired. <figref idref="DRAWINGS">FIG. 8</figref> schematically illustrates an example system <b>800</b> that may be used to practice various embodiments described herein. <figref idref="DRAWINGS">FIG. 8</figref> illustrates, for one embodiment, an example system <b>800</b> having one or more processor(s) <b>804</b>, system control module <b>808</b> coupled to at least one of the processor(s) <b>804</b>, system memory <b>812</b> coupled to system control module <b>808</b>, non-volatile memory (NVM)/storage <b>816</b> coupled to system control module <b>808</b>, and one or more communications interface(s) <b>820</b> coupled to system control module <b>808</b>.

0082In some embodiments, the system <b>800</b> may be capable of functioning as the UE <b>15</b> as described herein. In some embodiments, a system control module <b>808</b> of the UE <b>15</b> may include a NAS module and an AS module as described herein. In other embodiments, the system <b>800</b> may be capable of functioning as the one or more servers <b>50</b> of <figref idref="DRAWINGS">FIG. 1</figref> or otherwise provide logic/module that performs functions as described for a base station <b>40</b>, one or more nodes, MTC Server <b>52</b>, MTC-IWF <b>54</b>, HLR/HSS <b>56</b>, SGSN/MME <b>58</b>, RAN <b>20</b>, PGW <b>42</b>, and other modules described herein. In some embodiments, the system <b>800</b> may include one or more computer-readable media (e.g., system memory or NVM/storage <b>816</b>) having instructions and one or more processors (e.g., processor(s) <b>804</b>) coupled with the one or more computer-readable media and configured to execute the instructions to implement a module (e.g., an interworking function) to perform actions described herein.

0083System control module <b>808</b> for one embodiment may include any suitable interface controllers to provide for any suitable interface to at least one of the processor(s) <b>804</b> and/or to any suitable device or component in communication with system control module <b>808</b>.

0084System control module <b>808</b> may include memory controller module <b>810</b> to provide an interface to system memory <b>812</b>. The memory controller module <b>810</b> may be a hardware module, a software module, and/or a firmware module.

0085System memory <b>812</b> may be used to load and store data and/or instructions, for example, for system <b>800</b>. System memory <b>812</b> for one embodiment may include any suitable volatile memory, such as suitable DRAM, for example. In some embodiments, the system memory <b>812</b> may include double data rate type four synchronous dynamic random-access memory (DDR4 SDRAM).

0086System control module <b>808</b> for one embodiment may include one or more input/output (I/O) controller(s) to provide an interface to NVM/storage <b>816</b> and communications interface(s) <b>820</b>.

0087The NVM/storage <b>816</b> may be used to store data and/or instructions, for example. NVM/storage <b>816</b> may include any suitable non-volatile memory, such as flash memory, for example, and/or may include any suitable non-volatile storage device(s), such as one or more hard disk drive(s) (HDD(s)), one or more compact disc (CD) drive(s), and/or one or more digital versatile disc (DVD) drive(s), for example.

0088The NVM/storage <b>816</b> may include a storage resource physically part of a device on which the system <b>800</b> is installed or it may be accessible by, but not necessarily a part of, the device. For example, the NVM/storage <b>816</b> may be accessed over a network via the communications interface(s) <b>820</b>.

0089Communications interface(s) <b>820</b> may provide an interface for system <b>800</b> to communicate over one or more network(s) and/or with any other suitable device. The system <b>800</b> may wirelessly communicate with the one or more components of the wireless network in accordance with any of one or more wireless network standards and/or protocols.

0090For one embodiment, at least one of the processor(s) <b>804</b> may be packaged together with logic for one or more controller(s) of system control module <b>808</b>, e.g., memory controller module <b>810</b>. For one embodiment, at least one of the processor(s) <b>804</b> may be packaged together with logic for one or more controllers of system control module <b>808</b> to form a System in Package (SiP). For one embodiment, at least one of the processor(s) <b>804</b> may be integrated on the same die with logic for one or more controller(s) of system control module <b>808</b>. For one embodiment, at least one of the processor(s) <b>804</b> may be integrated on the same die with logic for one or more controller(s) of system control module <b>808</b> to form a System on Chip (SoC).

0091In various embodiments, the system <b>800</b> may be, but is not limited to, a server, a workstation, a desktop computing device, or a mobile computing device (e.g., a laptop computing device, a handheld computing device, a tablet, a netbook, etc.). In various embodiments, the system <b>800</b> may have more or less components, and/or different architectures. For example, in some embodiments, the system <b>800</b> includes one or more of a camera, a keyboard, liquid crystal display (LCD) screen (including touch screen displays), non-volatile memory port, multiple antennas, graphics chip, application-specific integrated circuit (ASIC), and speakers.

0092According to various embodiments, the present disclosure describes a system comprising one or more computer-readable media having instructions and one or more processors coupled with the one or more computer-readable media and configured to execute the instructions to implement an interworking function (IWF) to receive, from a machine type communication (MTC) server, a trigger to send a data payload to a user equipment (UE) over a wireless communication network, the data payload being smaller than a preconfigured threshold and send, over a first reference point to a first module including a Mobility Management Entity (MME) or a Serving GPRS (General Packet Radio Service) Support Node (SGSN) or a second reference point to a second module including a Home Location Register (HLR) or a Home Subscriber Server (HSS), the data payload and a request to forward the data payload to the UE. In some embodiments, the IWF is configured to send the data payload and the request to forward the data payload over the first reference point to the first module and in response to receiving the trigger from the MTC server, communicate with the first module to obtain routing information for sending the data payload to the UE over the first reference point.

0093In some embodiments, the IWF is configured to send the data payload and the request to forward the data payload over the second reference point to the second module. In some embodiments, the IWF comprises a machine type communication interworking function (MTC-IWF) that is configured to terminate a reference point to the MTC-IWF from the MTC server. In some embodiments, the MTC-IWF is configured to authenticate the MTC server and authorize control plane requests from the MTC server and to relay or translate signaling protocols received over the reference point to the MTC-IWF from the MTC server. In some embodiments, the first module and the second module are each configured to send the data payload to the UE over a control plane of the wireless communication network. In some embodiments, the IWF is configured to send, over a third reference point to a third module including a Packet Data Network Gateway (PGW), the data payload and the third module is configured to send the data payload to the UE over a user plane of the wireless communication network. In some embodiments, the IWF is configured to send the data payload using the third reference point if the UE is in connected mode and send the data payload using the first reference point or the second reference point if the UE is in idle or connected mode. In some embodiments, the wireless communication network includes a Global System for Mobile Communication (GSM), General Packet Radio Service (GPRS), Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Evolved HSPA (E-HSPA), or Long Term Evolution (LTE) network and the wireless communication network is accessible by a GSM Enhanced Data for GSM Evolution (EDGE) Radio Access Network (GERAN), Universal Terrestrial Radio Access Network (UTRAN) or Evolved UTRAN (E-UTRAN).

0094According to various embodiments, the present disclosure further describes a system comprising an interworking function (IWF) configured to receive, from a machine type communication (MTC) server, a trigger to send an MTC data payload to a user equipment (UE) over a wireless communication network and a module including a Mobility Management Entity (MME) or a Serving GPRS (General Packet Radio Service) Support Node (SGSN) coupled with the IWF over a reference point that terminates at the IWF, wherein the IWF is further configured to send, over the reference point to the module, the MTC data payload and a request to forward the MTC data payload to the UE. In some embodiments, the module is configured to send, to a base station of the wireless communication network, a paging message that includes a small data indicator that indicates a location of the MTC data payload and/or the MTC data payload to be forwarded to the UE.

0095In some embodiments, the module is configured to send a paging message that includes the MTC data payload to the base station and the base station is configured to send the paging message including the MTC data payload to the UE. In some embodiments, the module is configured to send a paging message that includes the small data indicator and the MTC data payload to the base station and the base station is configured to send the paging message including the small data indicator to the UE, the small data indicator indicating that the MTC data payload is at the base station, the base station being further configured to send the MTC data payload over a Radio Resource Control (RRC) connection established between the base station and the UE. In some embodiments, the module is configured to send a paging message that includes the small data indicator to the base station, the small data indicator indicating that the MTC data payload is at the module. In some embodiments, the base station is configured to send the paging message including the small data indicator to the UE. In some embodiments, the module is configured to send, to the UE, the MTC data payload in response to a non-access stratum (NAS) message sent by the UE, the NAS message being sent by the UE in response to the paging message.

0096According to various embodiments, the present disclosure further describes a method comprising receiving, by a machine type communication interworking function (MTC-IWF) from a machine type communication (MTC) server, a trigger to send a data payload, which is smaller than a preconfigured threshold, to a user equipment (UE) over a wireless communication network and sending, by the MTC-IWF over a reference point to a Packet Data Network Gateway (PGW), the data payload. In some embodiments, the PGW is configured to send the data payload to the UE over a user plane of the wireless communication network. In some embodiments, the method further includes sending, by the PGW, the data payload to a serving gateway (SGW) of the wireless communication network.

0097In some embodiments, the method further includes sending, by the SGW, the data payload to the UE over a user plane. In some embodiments, the reference point is a third reference point. In some embodiments, the method further includes, if sending by the MTC-IWF over a reference point to a Packet Data Network Gateway (PGW), the data payload fails, then sending, by the MTC-IWF over a first reference point to a first module including a Mobility Management Entity (MME) or a Serving GPRS (General Packet Radio Service) Support Node (SGSN) or a second reference point to a second module including a Home Location Register (HLR) or a Home Subscriber Server (HSS), the data payload and a request to forward the data payload to the UE. In some embodiments, the first module or the second module is configured to send the data payload to the UE over a control plane of the wireless communication network.

0098According to various embodiments, the present disclosure describes an apparatus comprising an antenna, a processor configured to communicate with a base station of a wireless communication network via the antenna, and a control module configured to establish a wireless connection with the base station of the wireless communication network and send, over the wireless connection, a Machine Type Communication (MTC) data payload to the base station for forwarding of the MTC data payload to a module including a Mobility Management Entity (MME) or a Serving GPRS (General Packet Radio Service) Support Node (SGSN) that is configured to forward the MTC data payload over an interface to a machine type communication interworking function (MTC-IWF), the MTC-IWF being configured to forward the MTC data payload to an MTC server. In some embodiments, the control module further includes a Non-Access Stratum (NAS) module and an Access Stratum (AS) module. In some embodiments, the control module is further configured to establish a connection with the base station by requesting, by the NAS module, the AS module to send a Radio Resource Control (RRC) connection request message with a Temporary Mobile Subscriber Identity (TMSI) to the base station.

0099In some embodiments, the RRC connection request message includes a value that indicates to the base station that a short-lived signaling procedure is in progress. In some embodiments, the control module is further configured to send the MTC data payload to the base station as part of an RRC setup complete message that is sent in response to an RRC connection setup message received from the base station. In some embodiments, the RRC connection setup complete message includes an information element including a Key Set Identifier (KSI) and sequence number and the MTC data payload in encrypted form, the MTC data payload being sent as a NAS Packet Data Unit (PDU) in a NAS container. In some embodiments, the base station is configured to forward the MTC data payload to the module in an S1 Application Protocol (S1-AP) initial context message. In some embodiments, the module is configured to decrypt the MTC data payload and add identity information of the apparatus to a message that includes the MTC data payload to the MTC-IWF.

0100In some embodiments, the control module is further configured to receive an acknowledgement that the MTC data payload has been received by the module. In some embodiments, the wireless connection with the base station is a Radio Resource Control (RRC) connection. In some embodiments, the module is configured to send the acknowledgement to the base station in an encrypted Non-Access Stratum (NAS) Packet Data Unit (PDU) in an S1 downlink NAS transport message. In some embodiments, the base station is configured to forward the acknowledgement to the apparatus in a Non-Access Stratum (NAS) Packet Data Unit (PDU) within a Radio Resource Control (RRC) connection release message that releases the RRC connection between the apparatus and the base station. In some embodiments, the S1 downlink NAS Transport message further includes a request by the module to the base station to release the RRC connection. In some embodiments, the wireless communication network is an Internet Protocol (IP) based network and the apparatus is a user equipment (UE) comprising one of a laptop computing device, a handheld computing device, a tablet, or a netbook. In some embodiments, the apparatus further includes one or more of a camera, a keyboard, a liquid crystal display (LCD) screen, a non-volatile memory port, multiple antennas, a graphics chip, an application-specific integrated circuit (ASIC), or a speaker.

0101Although certain embodiments have been illustrated and described herein for purposes of description, a wide variety of alternate and/or equivalent embodiments or implementations calculated to achieve the same purposes may be substituted for the embodiments shown and described without departing from the scope of the present disclosure. This application is intended to cover any adaptations or variations of the embodiments discussed herein. Therefore, it is manifestly intended that embodiments described herein be limited only by the claims and the equivalents thereof.