Priority of U.S. provisional patent application No.61/504054, filed 7/1/2011, the entire specification of which is hereby incorporated by reference in its entirety for all purposes.
Detailed Description
Embodiments of the present disclosure provide techniques and configurations for transmitting small data payloads such as, for example, Machine Type Communication (MTC) data, triggering or monitoring small data communications in a wireless communication network, and signaling improvements thereof. 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 the embodiments is defined by the appended claims and their equivalents.
Various operations will be 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. The operations described may be performed in a different order than the described embodiments. Various additional operations may be performed and/or described operations may be omitted in additional embodiments.
For the purposes of this disclosure, the phrase "a and/or B" means (a), (B), or (a and B). For the purposes of this 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).
The description may use the phrases "in one embodiment" or "in an embodiment," 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.
The term "module" as used herein may mean to include or be part of: an Application Specific Integrated Circuit (ASIC), an electronic circuit, a processor (shared, dedicated, or group) and/or memory (shared, dedicated, or group) that executes one or more software or firmware programs, a combinational logic circuit, and/or other suitable components that provide the described functionality.
Example embodiments may be described herein with respect to Broadband Wireless Access (BWA) networks, including networks operating in accordance with one or more protocols specified by the third generation partnership project (3GPP) and its derivatives, WiMAX forum, the Institute of Electrical and Electronics Engineers (IEEE)802.16 standards (e.g., the IEEE 802.16-2005 amendment), the Long Term Evolution (LTE) project, along with any amendments, updates, and/or revisions (e.g., the LTE advanced project, the Ultra Mobile Broadband (UMB) project (also referred to as "3 GPP 2"), etc.). IEEE 802.16 compliant BWA networks are commonly referred to as WiMAX networks-an acronym that stands for worldwide interoperability for microwave access, which is a certification mark for products that pass conformance and interoperability tests of the IEEE 802.16 standard. In other embodiments, the 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 applicable 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, among others.
The following embodiments may be used in a variety of applications, including transmitters and receivers of a mobile radio system. Radio systems specifically included within the scope of embodiments include, but are not limited to, Network Interface Cards (NICs), network adapters, base stations, Access Points (APs), relay nodes, enhanced node bs, gateways, bridges, hubs, and satellite radiotelephones. Moreover, the radio systems within the scope of the embodiments may include satellite systems, Personal Communication Systems (PCS), two-way radio systems, Global Positioning Systems (GPS), two-way pagers, Personal Computers (PC) and related peripherals, Personal Digital Assistants (PDA), 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.
Fig. 1 schematically illustrates an example Broadband Wireless Access (BWA) network 100 in accordance with some embodiments. BWA network 100 may include one or more radio access networks (hereinafter "RAN 20") and a core network 25.
A User Equipment (UE)15 may access the core network 25 via a radio link ("link") with a Base Station (BS), such as, for example, one of the base stations 40, 42 in the RAN 20. The UE15 may be, for example, a subscriber station configured to communicate with the base stations 40, 42 in accordance with one or more protocols. For ease of discussion, the following description is provided for an example BWA network 100 that is compliant with 3GPP, however, the subject matter of the present disclosure is not limited in this respect and the embodiments may be applied to other networks that benefit from the principles described herein. In some embodiments, the base stations 40, 42 may include enhanced node b (enb) stations and UEs 15 configured to communicate using a multiple-input multiple-output (MIMO) communication scheme. One or more antennas of UE15 may be used to simultaneously utilize radio resources of multiple respective component carriers (e.g., which may correspond to antennas of eNB stations 40, 42) of BWA network 100. In some embodiments, the UE15 may be configured to communicate using Orthogonal Frequency Division Multiple Access (OFDMA), for example, in downlink communications, and/or single carrier frequency division multiple access (SC-FDMA), for example, in uplink communications.
Although fig. 1 generally depicts the UE15 as a cellular telephone, in various embodiments, the UE15 may be a Personal Computer (PC), notebook, ultrabook, netbook, smartphone, ultra mobile PC (umpc), handheld mobile device, Universal Integrated Circuit Card (UICC), Personal Digital Assistant (PDA), Customer Premises Equipment (CPE), tablet, or other consumer electronics such as MP3 player, digital camera, or the like. The base stations 40, 42 may include: one or more antennas; one or more radio modules that modulate and/or demodulate signals transmitted or received over an air interface; and one or more digital modules that process signals transmitted and received over the air interface.
In some embodiments, communication with UE15 via RAN20 may be facilitated via one or more nodes 45. One or more nodes 45 may act as an interface between core network 25 and RAN 20. According to various embodiments, one or more nodes 45 may include: a Mobility Management Entity (MME) (e.g., SGSN/MME58 of fig. 2) configured to manage signaling exchanges (e.g., authentication of UE 15) between base stations 40, 42 and a core network 25 (e.g., one or more servers 50); a packet data network gateway (PGW) (e.g., GGSN/PGW51 of fig. 2) providing a gateway router to the internet 65; and/or at a Serving Gateway (SGW), manages user data tunnels or paths between the base stations 40, 42 of the RAN20 and the PGW. Other types of nodes may be used in other embodiments.
The core network 25 may include logic (e.g., modules) to provide authentication of the UE15 or other actions associated with establishment of a communication link to provide a connected state of the UE15 with the BWA network 100. For example, the core network 25 may include one or more servers 50 that may be communicatively coupled to the base stations 40, 42. In one embodiment, the one or more servers 50 may include a Home Subscriber Server (HSS) (e.g., HLR/HSS56 of fig. 2), which may be used to manage user parameters, such as the user's International Mobile Subscriber Identity (IMSI), authentication information, and the like. The core network 25 may include other servers, interfaces, and modules, some of which are further described in conjunction with fig. 2. In some embodiments, the one or more servers 50 may comprise over-the-air (OTA) servers. In some embodiments, logic associated with different functionality of one or more servers 50 may be combined to reduce the number of servers, including for example in a single machine or module.
According to various embodiments, BWA network 100 is an Internet Protocol (IP) based network. For example, the core network 25 may be an IP-based network. The interface between network nodes (e.g., one or more nodes 45) may be IP-based, including backhaul connections to the base stations 40, 42. In some embodiments, BWA network 100 includes a global system for mobile communications (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 RAN20 may comprise a GSM EDGE Radio Access Network (GERAN), where EDGE denotes enhanced data for GSM evolution, Universal Terrestrial Radio Access Network (UTRAN), or evolved UTRAN (E-UTRAN). In other embodiments, BWA network 100 may operate in accordance with other network technologies.
Fig. 2 schematically illustrates a system architecture 200 for communicating small data payloads, in accordance with some embodiments. System architecture 200 may be configured to efficiently perform small data transfers designed for use with machine-to-machine (M2M) communications, such as MTC communications, for example. For example, User Equipment (UE)15 may include or be communicatively coupled with smart meters or sensors in order to collect small amounts of information for transmission (e.g., health monitoring devices, vending machines, etc. configured to collect information related to temperature, inventory, etc.). In some embodiments, application server 26 may be configured to send a small data payload in a message (e.g., requesting MTC information such as sensor or meter measurements, inventory levels, etc.). In some embodiments, the data payload (e.g., MTC data payload) may be less than a preconfigured threshold defining a small data payload. In some embodiments, the preconfigured threshold may be set by subscription or network operator policy.
According to various embodiments, a small data payload may be sent by the UE15 to the MTC server 52 or the application server 26 via the RAN20 and the core network 25, or a small data payload may be sent by the application server 26 or the MTC server 52 to the UE15 via the core network 25 and the RAN 20. For example, the application server 26 may be configured (e.g., by an MTC user) to send or trigger sending of a small data payload to the User Equipment (UE) 15. The application server 26 may be communicatively coupled with the core network 25 using, for example, an internet connection (e.g., the internet 65 of fig. 1). In another example, an MTC application 24 communicatively coupled with the UE15 may be configured to send or trigger sending of a small data payload to the application server 26. In some embodiments, the UE15 is an MTC device configured to send or receive a small data payload and/or communicate with the MTC application 24. In some embodiments, UE15 may include MTC application 24.
The system architecture 200 includes an MTC server 52, the MTC server 52 configured to connect to the core network 25 to communicate with a UE (e.g., UE 15) configured for MTC communications. The MTC server 52 may be further configured to communicate with an interworking function (IWF), such as the MTC-IWF54, to trigger the transmission of a small data payload. In some embodiments, the MTC server 52 may be referred to as a Service Capability Server (SCS).
The MTC-IWF54 may terminate an MTCSP reference point or interface (hereinafter "reference point") between the MTC server 52 and the MTC-IWF 43. The MTC-IWF 43 may be configured to hide the internal Public Land Mobile Network (PLMN) topology and relay or translate the signaling protocol used over the MTCsp reference point to invoke particular functionality in the PLMN. In some embodiments, the MTC-IWF54 may authenticate the MTC server 52 prior to establishing communication with the core network 25, and/or control plane requests from the MTC server 52 are authorized. According to various embodiments, dashed lines between modules (e.g., 54, 58) represent the control plane, and solid lines between modules represent the user plane. Although particular planes between modules may be shown, other embodiments may include additional/alternative planes.
In one embodiment, the MTC-IWF54 may terminate the MTCx reference point between modules (such as, for example, SGSN/MME 58) including a Mobility Management Entity (MME) and/or a serving GPRS (general packet radio service) support node (SGSN). In some embodiments, the first MTCx1 reference point may terminate at the MME of the SGSN/MME58 and the second MTCx2 reference point may terminate at the SGSN of the SGSN/MME 58. In another embodiment, the MTC-IWF54 may terminate the MTCy reference point between modules including a Home Location Register (HLR) and/or a Home Subscriber Server (HSS), such as, for example, the HLR/HSS 56. In another embodiment, the MTC-IWF54 may terminate the MTCz reference point between modules (such as, for example, GGSN/PGW 51) including a Gateway GPRS Support Node (GGSN) and/or a packet data network gateway (PGW). The MTCx, MTCy, and MTCz reference points are not limited to the example names provided (e.g., MTCx, MTCy, and MTCz), but may be represented by other names in other embodiments.
According to various embodiments, the MTCx reference point may be used to send control packet information to the network (e.g., 3GPP PLMN) based on an indication from the MTC server 52. The MTCy reference point may be used to derive routing information for the downlink small data payload by deriving a network identifier (e.g., a 3GPP internal device identifier such as an IMSI or a Mobile Station International Subscriber Directory Number (MSISDN)) from an MTC device identifier or an MTC application identifier. The MTCz reference point may be used to send a small data payload to the GGSN/PGW51 over the user plane.
According to various embodiments, the system architecture 200 may include one or more of the MTCx, MTCy, or MTCz reference points in various combinations. For example, in one embodiment, system architecture 200 may only include reference points MTCx and MTCy. In another embodiment, the system architecture 200 may only include the reference point MTCz. In other embodiments, the system architecture 200 may include all of the MTCx, MTCy, and MTCz reference points. The system architecture 200 may also include a Gr/S6a/S6d reference point between the HLR/HSS56 and the SGSN/MME58, a reference point MTCi between the MTC server 52 and the GGSN/PGW51, a reference point Application Programming Interface (API) between the application server 26 and the MTC server 52, a reference point S1 between the SGSN/MME58 and the RAN20, and a reference point Um/Uu/LTE-Uu between the RAN20 and the UE 15.
The system architecture 200 may support the transmission of small data payloads with little network impact, such as signaling overhead, network resources, or delay for reallocation. In some embodiments, the UE15 may attach or detach from the RAN20 (e.g., over an established Radio Resource Control (RRC) connection) prior to transmission of the small data payload (e.g., when the small data payload transmission is triggered). In some embodiments, the UE15 may be in a connected mode or an idle mode when a small data payload transmission is triggered. The system architecture 200 (e.g., MTC-IWF54) may be configured with policies-preferably sending small data payloads over the MTCz interface and user plane data path established between the UE15 and the GGSN/PGW51 when the UE is in connected mode, and over the control plane using one of MTCx or MTCy reference points when the UE15 is in idle mode. In some embodiments, when the UE15 is in idle mode, the system architecture 200 may be configured to send a small data payload, preferably over an MTCx reference point.
According to various embodiments, the system architecture 200 may be configured to transmit a small data payload over one or more of the MTCx, MTCy, or MTCz reference points in various combinations. For example, in one embodiment, the system architecture 200 may be configured to send only a small data payload over the reference points MTCx and MTCy. In another embodiment, the system architecture may be configured to send only a small data payload over the reference point MTCz. In other embodiments, the system architecture 200 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 200 may be configured to send the small data payload over only one of the reference point MTCz and MTCx or MTCy. In other embodiments, the system architecture 200 may be configured to send the small data payload over other reference points than those described.
Fig. 3a schematically illustrates an example scheme 300a for transmitting small data payloads, in accordance with some embodiments. Scheme 300a illustrates a method of transmitting a small data payload (e.g., downlink) to the UE15 over an MTCx reference point in accordance with the first technique T1.
Referring to fig. 2 and 3a, at 302, the MTC server 52 may send a message to the MTC-IWF54 to trigger the transmission of a small data payload. MTC server 52 may include an MTC device Identification (ID) and/or an MTC application (e.g., MTC application 24) ID in the message to indicate a target UE (e.g., UE 15) to receive the small data payload. In some embodiments, the MTC server 52 may also include or otherwise send a small data payload in a message to the MTC-IWF 54. In other embodiments, the application server 26 may send the small data payload directly to the MTC-IWF 54. In some embodiments, a secure connection may be established between the MTC-IWF54 and the MTC server 52 for transmission at 302.
At 304, in response to receiving the trigger at 302, the MTC-IWF54 may query the HLR/HSS56 for routing information in order to deliver a small data payload to the UE15 over the MTCx reference point. In some embodiments, the MTC-IWF54 may send the MTC device ID to the HLR/HSS56, and the HLR/HSS56 may use the MTC device ID as part of the MTC subscription. The HLR/HSS56 may map the MTC device ID to the IMSI for UE15 and send the IMSI back to the MTC-IWF54 along with the address of the SGSN/MME 58. In some embodiments, a trust relationship may be established between the MTC-IWF54 and the HLR/HSS56 (e.g., when the MTC-IWF54 is outside of the operator domain of the core network). In response to receiving the query from the MTC-IWF54 at 304, the HLR/HSS56 may send the IMSI serving node identity and/or other information, such as operator policy, authorization information, a failure indication with a cause value, etc., to the MTC-IWF 54.
At 306, the MTC-IWF54 may send the small data payload and a request to forward the small data payload (e.g., a "forward small data" request) to the SGSN/MME58 over the MTCx reference point. MTC-IWF54 may send the request and small data payload to SGSN/MME58 using IMSI.
In accordance with a first technique T1 of sending a small data payload from the SGSN/MME 68 to the UE15, the SGSN/MME58 may determine that the UE15 is in a connected state and, at 308a, forward the small data payload to the UE15 using uplink/downlink (UL/DL) non-access stratum (NAS) signaling. For example, the SGSN/MME58 may determine that the UE15 is in the connected state by determining that a context (e.g., locally stored) already exists to indicate the location of the UE 15. The SGSN/MME58 may send a small data payload to the UE15 using, for example, a downlink non-access stratum (NAS) transport message. At 308a, during the communication, an acknowledgement may be received by the SGSN/MME58 that a small data payload has been sent to the UE 15.
At 316, the SGSN/MME58 may forward an acknowledgement to the MTC-IWF54 that the small data payload has been sent to the UE 15. At 318, the MTC-IWF54 may send a trigger to the MTC server 52 to send an acknowledgement that a small data payload has been delivered to the UE 15. The MTC server 52 may send an acknowledgement to the application server 26, for example, in response to a trigger.
Fig. 3b schematically illustrates an example scheme 300b for transmitting small data payloads, in accordance with some embodiments. Scheme 300b illustrates a method of transmitting a small data payload (e.g., downlink) to the UE15 over an MTCx reference point in accordance with the second technique T2. The acts from 302 to 306 and from 316 to 318 in scheme 300b may be consistent with the embodiments described for the same numbered acts of scheme 300 a.
According to a second technique T2 of sending a small data payload from the SGSN/MME 68 to the UE15, the SGSN/MME58 may determine that the UE15 is in an idle state and may send the small data payload in a paging message to the RAN20 (e.g., the base station 40 or 42 of fig. 1) at 308 b. The RAN20 may send a paging message including a small data payload to the UE15 at 310 b. For example, the small data payload may be included in a paging message that is broadcast in the tracking area of the target UE15 in idle mode. In some embodiments, the SGSN/MME58 may be configured to send paging messages including small data payloads over the control plane. In some embodiments, the RAN20 may inform the SGSN/MME58 of the successful delivery of the small data payload by sending a small data acknowledgement to the SGSN/MME58 at 314b (which may be forwarded to the MTC-IWF54 at 316).
Fig. 3c schematically illustrates an example scheme 300c for transmitting small data payloads, in accordance with some embodiments. Scheme 300c illustrates a method of transmitting a small data payload (e.g., downlink) to the UE15 over an MTCx reference point in accordance with the third technique T3. The acts from 302 to 306 and from 316 to 318 in scheme 300c may be consistent with the embodiments described for the same numbered acts of scheme 300 a.
According to a third technique T3 of sending a small data payload from the SGSN/MME 68 to the UE15, the SGSN/MME58 may determine that the UE15 is in an idle state and, at 308c, may send a paging message including the small data payload to the RAN20 (e.g., the base station 40 or 42 of fig. 1). The paging message may also include an optional small data indicator to indicate that a small data payload is at the RAN20 (e.g., at base station 40 or 42 of fig. 1). In some embodiments, the SGSN/MME58 may send a small data payload to the RAN20 over the S1 reference point.
In some embodiments, the RAN20 may retrieve and/or store the small data payload in the paging message and send the paging message without the small data payload to the UE15 at 310 c. RAN20 may include the small data indicator in the paging message. In some embodiments in which the small data payload is in the RAN20 prior to the UE15 attaching to the RAN20 (e.g., through an RRC connection), the UE15 may receive the paging message sent at 310c with a small data indicator indicating that the small data payload is in the RAN 20.
At 312c, the UE15 may begin an attach procedure to the RAN20, e.g., by establishing an RRC connection. For example, establishment of the RRC connection may be requested by the UE15 in an RRC connection request message to the RAN20 in response to the paging message at 310 c. The RAN20 may communicate the small data payload to the UE15 via signals associated with the RRC connection establishment procedure. When the UE15 receives a small data payload, the UE15 may terminate the RRC connection establishment procedure and may return to idle mode if no further data is to be sent or received by the UE 15. In some embodiments, the RAN20 may notify the SGSN/MME58 of the successful delivery of the small data payload by sending a small data acknowledgement to the SGSN/MME58 at 314 c.
Fig. 3d schematically illustrates an example scheme 300d for transmitting a small data payload, in accordance with some embodiments. Scheme 300d illustrates a method of transmitting a small data payload (e.g., downlink) to the UE15 over an MTCx reference point in accordance with the fourth technique T4. The acts from 302 to 306 and from 316 to 318 in scheme 300d may be consistent with the embodiments described for the same numbered acts of scheme 300 a.
According to a fourth technique T4 of sending a small data payload from the SGSN/MME 68 to the UE15, the SGSN/MME58 may determine that the UE15 is in an idle state and, at 308d, may send a paging message, which may include a small data indicator indicating that there is a small data payload at the SGSN/MME58 that needs to be delivered or forwarded to the UE 15. At 310d, the RAN20 may send a paging message to the UE15, which may include a small data indicator to indicate that a small data payload targeted for the UE15 is at the SGSN/MME 58. In some embodiments in which the small data payload is at the SGSN/MME58 prior to the UE15 attaching to the RAN20 (e.g., through an RRC connection), the UE15 may receive the paging message sent at 310d with a small data indicator indicating that the small data payload is at the SGSN/MME 58. In response to the paging message at 310d, the UE15 may begin an attach procedure to the RAN20 at 312d by, for example, establishing an RRC connection, and begin an attach procedure with the SGSN/MME58 at 314d by sending a non-access stratum (NAS) message, such as an attach/service request message, to the RAN 20. The RAN20 may forward the NAS message to the SGSN/MME 58. During the attach procedure at 314d, the SGSN/MME58 may send a small data payload to the UE15 using non-access stratum (NAS) signaling, e.g., attach response, service request response, DL NAS transport message, etc.
The content of the NAS message sent by the UE15 at 314d to start the attach procedure may depend on the content of the paging message received by the UE15 at 310 d. For example, in the case where the paging message of 310 only contains a small data indicator (indicating that a small data payload is at the SGSN/MME 58), the UE15 may include in the NAS message an information element that includes a Key Set Identifier (KSI) (which may be associated with a cipher and integrity key) and a sequence number (which may be a count value for the UE 15). The MME of SGSN/MME58 may use the KSI, sequence number, and Temporary Mobile Subscriber Identity (TMSI) values, e.g., S-TMSI, where S denotes System Architecture Evolution (SAE), to cipher the small data payload for transmission to UE 15. The UE15 may terminate the attach procedure when the UE15 receives a small data payload, and may be configured to return to idle mode when no other data is to be sent or received by the UE 15.
In some embodiments where the paging message sent at 310d includes a small data payload (e.g., at 310b of fig. 3 b), the network operator policy may or may not require the UE15 to send a response message for the small data payload from the MTC server 52. In the event that the network operator policy does not require any response to be sent, the UE15 may be configured to include an information element including an acknowledgement (e.g., MTC data acknowledgement) in the NAS message (which is sent to start the attach procedure at 314 d). In the case where network operator policy requires the response to be sent, UE15 may include in the NAS message (which is sent at 314d to start the attach procedure) an informational element including the KSI and sequence number and the ciphered response payload as a NAS Packet Data Unit (PDU) in the NAS container. If the UE15 has multiple response messages or more data is to be loaded in the NAS container at 314d, the UE15 may indicate in the NAS container that there will be more data behind. After the attach/service request message is sent by the UE15 at 314d to start the attach procedure, the UE15 may include the additional data in the NAS PDU in an uplink information transfer message to the SGSN/MME 58. In some embodiments, if the UE15 has an uplink small data payload to send to the MTC server 52, the UE15 may activate a Packet Data Protocol (PDP) context and/or a PDP bearer and send uplink data on the user plane (e.g., via the GGSN/PGW51 of fig. 2).
In embodiments where the NAS message sent by the UE15 to the SGSN/MME58 (e.g., of the attach procedure at 314 d) includes only the KSI and the sequence number (e.g., where the paging message at 310d contains only a small data indicator indicating that a small data payload is at the SGSN/MME 58), the SGSN/MME58 may send the small data payload to the UE15 in a ciphering information element in the NAS message, such as, for example, the ciphering information element in the NAS PDU in the S1 downlink NAS transport message. The UE15 may send a response message or acknowledgement in response to the NAS message having a small data payload. The acknowledgement may comprise, for example, an acknowledgement in a ciphering information element in a NAS PDU in an uplink information transfer message. The UE15 may also include an information element in the uplink information transfer message in a response message or acknowledgement to request release of the RRC connection at 312d when the UE15 has no further data to send.
In some embodiments, if the NAS message (e.g., attach/service request message) sent to begin the attach procedure at 314d includes an information element containing an acknowledgement such as an MTC data acknowledgement (e.g., where the network operator policy does not require the UE15 to send a response to receipt of a small data payload), the SGSN/MME58 may send or forward the data acknowledgement to the MTC-IWF54 at 316 d. If the NAS message (e.g., attach/service request message) sent to start the attach procedure at 314d includes an information element that includes the KSI and sequence number and an encrypted response payload that is a NAS Packet Data Unit (PDU) in the NAS container (e.g., where network operator policy requires UE15 to send a response to indicate receipt of a small data payload), SGSN/MME58 may decrypt the NAS PDU and forward the response payload to MTC-IWF54 at 316 d. The SGSN/MME58 may also send an acknowledgement to the UE15 in the ciphered information element in the NAS PDU in the S1 downlink NAS transport message.
In some embodiments, the S1 downlink NAS transport message may include an information element that allows the MME of SGSN/MME58 to request the base station of RAN20 to release the RRC connection at 312 d. The MME may not use this indication if the UE15 previously indicated that multiple response messages are to be delivered.
Fig. 4 schematically illustrates another example scheme 400 for transmitting small data payloads, in accordance with some embodiments. Scheme 400 illustrates a method for transmitting a small data payload (e.g., downlink) to a UE15 over an MTCy reference point. Scheme 400 may be consistent with the embodiments described in connection with schemes 300a-d of fig. 3a-3d, unless otherwise noted. For example, as described in connection with fig. 3a-3d, a small data payload may be sent 415 from the SGSN/MME58 to the UE15 in accordance with the first, second, third, or fourth technique (e.g., T1, T2, T3, or T4).
Referring to fig. 2 and 4, at 302, the MTC server 52 may send a message to the MTC-IWF54 to trigger the transmission of a small data payload. The acts at 302 may be consistent with the embodiments described in connection with 302 of fig. 3 a. At 404, the MTC-IWF54 may send the small data payload and a request to forward the small data payload (e.g., a "forward small data" request) to the HLR/HSS56 over the MTCy reference point. MTC-IWF54 may indicate the target UE (e.g., UE 15) to HLR/HSS56 using the MTC device Identification (ID) and/or MTC application ID (e.g., ID of MTC application 24) in the message. In some embodiments, a trust relationship may be established between the MTC-IWF54 and the HLR/HSS56 (e.g., when the MTC-IWF54 is outside of the operator domain of the core network).
The HLR/HSS56 may take the MTC device ID as part of the MTC subscription. The HLR/HSS56 may be configured to map the MTC device ID to the IMSI for the UE15 and derive the target SGSN/MME 58. At 406, the HLR/HSS56 may send a small data payload to the SGSN/MME58 (e.g., via reference point Gr/S6a/S6d of FIG. 2). The small data payload may be sent, for example, in a notification request message.
At 415, the SGSN/MME58 may send the small data payload to the UE 15. At 416, SGSN/MME58 may send or forward a response or acknowledgement to HLR/HSS56, as described in connection with fig. 3a-3 d. At 418, the HLR/HSS56 may forward the response or acknowledgement to the MTC-IWF54 over the MTCy reference point.
At 420, the MTC-IWF54 may send a trigger to the MTC server 52 to send an acknowledgement that a small data payload has been delivered to the UE 15. The MTC server 52 may send an acknowledgement to the application server 26, for example. The techniques described in connection with fig. 3a-3d and fig. 4 may be combined, according to various embodiments. For example, a small data payload may be sent over the MTCx reference point and an acknowledgement may be received over the MTCy reference point, or vice versa.
Fig. 5 schematically illustrates yet another example scheme 500 for transmitting small data payloads, in accordance with some embodiments. Scheme 500 illustrates a method for transmitting a small data payload (e.g., downlink) to a UE15 over an MTCz reference point. Scheme 500 is described in connection with a long term evolution/evolved packet core (LTE/EPC) system, but similar concepts may be applied to other systems.
The MTC server 52 may receive a trigger to send a small data payload as described in connection with scheme 300a of fig. 3 a. At 502, in response to receiving the trigger, the MTC server 52 may send a small data payload to the PGW 42 (e.g., the PGW of GGSN/PGW51 of fig. 2) over the MTCz reference point at 504. At 506, PGW 42 may send a small data payload to a Serving Gateway (SGW) over the established default bearer.
The SGW 44 may send a downlink data notification message to the MME 59 at 508, and/or the SGW 44 may send a downlink notification message to the SGSN57 at 514. The MME 59 may respond with a downlink data notification acknowledge message at 512 and/or the SGSN57 may respond with a downlink data notification acknowledge message at 516.
At 518, if the UE15 is registered in the MME, the MME may send a paging message to the base station. At 520, if the UE is registered in SGSN57, SGSN57 may send a paging message to radio network controller/base station controller (RNC/BSC) 46. The base station 40 may send a paging message to the UE15 at 522, and/or the RNC/BSC 46 may send a paging message to the UE15 at 524. The paging message may indicate to the UE15 that a downlink small data payload is to be sent to the UE 15.
At 526, in response to the paging message(s), the UE15 may perform an attach procedure to establish an RRC connection with the base station 40 and/or the RNC/BSC 46 (e.g., RAN20 of fig. 3 a). At 528, the UE15 may perform an attach procedure (e.g., a service request procedure) to establish a connection with the MME 59, SGSN57, and/or SGW 44. The SGW 44 may transmit the small data payload to the UE15 via a Radio Access Technology (RAT), which may be the RAT used to perform the attach procedure at 528. According to various embodiments, the RRC connection at 526 may be consistent with the embodiments described in connection with act 312c of fig. 3c, and the attach procedure at 528 may be consistent with the embodiments described in connection with act 314d of fig. 3 d.
Fig. 6 schematically illustrates yet another example scheme 600 for transmitting small data payloads, in accordance with some embodiments. Scheme 600 illustrates a method for transmitting a small data payload (e.g., uplink) from a UE15 to an MTC server 52 over an MTCx or MTCy reference point.
Referring to fig. 2 and 6, the UE15 may be triggered by the MTC application 24 to send a small data payload to the MTC server 52. At 602, in response to the trigger, UE15 may send a connection request message to RAN 20. The UE15 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, with the TMSI (e.g., S-TMSI) of the UE15 included in the connection request message, causing the action at 602. UE15 may include some value that indicates to the base station of RAN20 that a short-term signaling procedure is in progress. For example, the UE15 may set the cause value in the connection request message to "mo-Signaling". Such action may reduce the likelihood that the MME of SGSN/MME58 will download the security context to the base station. Without a security context, a handover may not be performed. Radio resources can be saved if the base station does not configure the UE15 to perform measurement reporting.
At 604, the base station of the RAN20 may send an RRC connection setup message to indicate establishment of the RRC connection. At 606, in response to receiving the RRC connection setup message, the UE15 may send a small data payload to the base station as part of an RRC setup complete message. The RRC setup complete message may include, for example, KSI and sequence number and a small data payload in encrypted form. In some embodiments, the small data payload may be sent as a NAS PDU in a NAS container.
At 608, the base station may forward the encrypted small data payload (e.g., in a NAS container) to the MME of the SGSN/MME58 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 UE15 to the message including the small data payload directed to the MTC-IWF 54.
The SGSN/MME58 may be configured to forward the small data payload to the MTC/IWF 54 over the MTCx or MTCy reference point. In one embodiment, the SGSN/MME58 may forward the small data payload to the HLR/HSS56 at 610 (e.g., over the Gr/S6a/S6d reference point), and the HLR/HSS may forward the small data payload to the MTC-IWF54 over the MTCy reference at 612. In another embodiment, the SGSN/MME58 may be configured to forward the small data payload directly to the MTC-IWF54 at 614 over the MTCx reference point.
At 616, the MTC-IWF54 may forward the small data payload (e.g., over the MTCsp reference point) to the MTC server 52. MTC server 52 may further forward the small data payload to application server 26.
At 618, the SGSN/MME58 may send an acknowledgement that a small data payload has been received by the SGSN/MME58 or forwarded to the MTC-IWF 54. The acknowledgement may be in a message that includes the MTC data acknowledgement information element in the ciphered NAS PDU addressed to the base station in the S1 downlink NAS transport message. In some embodiments, the message may also include an information element that allows the MME of SGSN/MME58 to request that the base station of RAN20 release the RRC connection.
At 620, the base station of RAN20 may send an acknowledgement message to UE15 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.
In some embodiments, the UE15 may perform NAS signaling instead of the actions at 602 and 606, such as, for example, tracking area updates, service requests, attach requests, etc., and include an uplink small data payload to the SGSN/MME58 using NAS signaling. In some embodiments, the UE15 may perform RRC signaling to include an uplink small data payload directed to the RAN20, which the RAN20 may forward to the SGSN/MME58 using S1. S1 may be shared instead of on a per UE basis.
In other embodiments, the UE15 may send the uplink small data payload to the MTC server 52 over the user plane (e.g., over the MTCz reference point). For example, the UE15 may establish a connection (e.g., a User Path (UP) connection) with the MTC server 52 and send the small data payload directly to the MTC server 52 (e.g., over the reference point MTCi) on the user plane.
Fig. 7 is a flow diagram of a method 700 for transmitting a small data payload in a BWA network (e.g., BWA network 100 of fig. 1), according to some embodiments. The method 700 may be consistent with the embodiments already described in connection with fig. 1-6.
Referring to fig. 2 and 7, at 702, method 700 includes receiving a request to transmit a small data payload to a User Equipment (UE) 15. For example, the MTC-IWF54 may receive a trigger from the MTC server 52 requesting the transmission of a small data payload.
At 704, method 700 may also include determining a route for sending the small data payload to the UE 15. A module such as the MTC-IWF54 in the core network 25 may be configured to determine routing by determining whether the UE15 is in connected mode or idle mode. For example, the MTC-IWF54 may query the HLR/HSS56 or SGSN/MME58 to determine whether context exists for the UE15 to determine whether the UE15 is connected or idle with the SGSN/MME 58. If the UE15 is in idle mode, the MTC-IWF54 may be routed over one of the MTCx or MTCy reference points. If the UE15 is in connected mode, the MTC-IWF54 may be routed over the MTCz reference point. In some embodiments, the MTC-IWF54 may query the HLR/HSS56 or SGSN/MME58 to determine network operator policies and route information over MTCx, MTCy, or MTCz reference points in accordance with the network operator policies.
In some embodiments, the MTC-IWF54 may determine the route by attempting to send a small data payload over the MTCz reference point. If the attempt to transmit over the MTCz reference point fails for any reason, the MTC-IWF54 may attempt to transmit a small data payload over the MTCx and/or MTCy reference points. For example, if transmission by the MTC-IWF to a packet data network gateway (PGW) over an MTCz reference point fails, the MTC-IWF54 may attempt to transmit a small data payload over an MTCx reference point. If the transmission over the MTCx reference point by the MTC-IWF fails, the MTC-IWF54 may attempt to transmit a small data payload over the MTCy reference point.
In some embodiments, the MTC-IWF54 may determine the route by determining whether a data path is established between the UE15 and the PGW of the GGSN/PGW 51. The MTC-IWF54 may route the small data payload over the MTCz reference point if it is determined that the data path is established, otherwise, the MTC-IWF54 may route the small data payload over one of the MTCx or MTCy reference points. A combination of these techniques may be used to determine a route for sending a small data payload to the UE 15.
At 706, the method 700 may also include transmitting the small data payload to the UE 15. The small data payload may be transmitted, for example, using the techniques described in connection with fig. 3-5.
At 708, method 700 may also include receiving an acknowledgement that the small data payload was received by UE 15. Validation may be consistent with the techniques described in connection with fig. 3-5.
Embodiments of the present disclosure may be implemented into a system using any suitable hardware and/or software configured as desired. Fig. 8 schematically illustrates an example system 800 that can be used to implement various embodiments described herein. FIG. 8 illustrates, for one embodiment, an example system 800, the system 800 having one or more processors 804, a system control module 808 coupled to at least one of the processors 804, system memory 812 coupled to the system control module 808, non-volatile memory (NVM)/storage 816 coupled to the system control module 808, and one or more communication interfaces 820 coupled to the system control module 808.
In some embodiments, system 800 may be capable of functioning as a UE15 as described herein. In some embodiments, the system control module 808 of the UE15 may include a NAS module and an AS module AS described herein. In other embodiments, system 800 may be capable of functioning as one or more servers 50 of fig. 1, or otherwise provide logic/modules that perform the functions as described for base station 40, one or more nodes, MTC server 52, MTC-IWF54, HLR/HSS56, SGSN/MME58, RAN20, PGW 42, and other modules described herein. In some embodiments, system 800 may include: one or more computer-readable media having instructions (e.g., system memory or NVM/storage 816); and one or more processors (e.g., processor 804) coupled with one or more computer-readable media and configured to execute instructions to implement modules (e.g., interworking functions) that perform the actions described herein.
System control module 808 for one embodiment may include any suitable interface controller to provide any suitable interface to at least one of processors 804 and/or to any suitable device or component in communication with system control module 808.
The system control module 808 may include a memory controller module 810 to provide an interface to system memory 812. The storage controller module 810 may be a hardware module, a software module, and/or a firmware module.
System memory 812 may be used to load and store data and/or instructions, for example, for system 800. System memory 812 for one embodiment may include, for example, any suitable volatile memory, such as suitable DRAM. In some embodiments, system memory 812 may include double data rate type 4 synchronous dynamic random access memory (DDR4 SDRAM).
System control module 808 for one embodiment may include one or more input/output (I/O) controllers to provide an interface to NVM/storage 816 and communication interface 820.
NVM/storage 816 may be used to store data and/or instructions, for example. NVM/storage 816 may include, for example, any suitable non-volatile memory, such as flash memory, and/or may include, for example, any suitable non-volatile storage, such as one or more Hard Disk Drives (HDDs), one or more Compact Disk (CD) drives, and/or one or more Digital Versatile Disk (DVD) drives.
The NVM/storage 816 may include storage resources that are physically part of a device on which the system 800 is installed, or it may be accessible by, but not necessarily part of, the device. For example, NVM/storage 816 may be accessed over a network via communication interface 820.
Communication interface 820 may provide an interface for system 800 to communicate over one or more networks and/or with any other suitable device. System 800 may communicate wirelessly with one or more components of a wireless network in accordance with any of one or more wireless network standards and/or protocols.
For one embodiment, at least one of the processors 804 may be packaged together with logic for one or more controllers in a system control module 808, such as a memory controller module 810. For one embodiment, at least one of the processors 804 may be packaged together with logic for one or more controllers in a system control module 808 to form a System In Package (SiP). For one embodiment, at least one of the processors 804 may be integrated on the same die with logic for one or more controllers in the system control module 808. For one embodiment, at least one of the processors 804 may be integrated on the same die with logic for one or more controllers of the system control module 808, forming a system on a chip (SoC).
In various embodiments, system 800 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, system 800 may have more or fewer components and/or different architectures. For example, in some embodiments, system 800 includes one or more of a camera, a keyboard, a Liquid Crystal Display (LCD) screen (including a touch screen display), a non-volatile memory port, multiple antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), and a speaker.
According 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 instructions to implement an interworking function (IWF) to: receiving, from a Machine Type Communication (MTC) server, a trigger to send a data payload to a User Equipment (UE) through a wireless communication network, the data payload being less than a preconfigured threshold; and a request to send the data payload to a first module comprising a Mobility Management Entity (MME) or a serving GPRS (general packet radio service) support node (SGSN) over a first reference point, or to a second module comprising a Home Location Register (HLR) or a Home Subscriber Server (HSS) over a second reference point and to forward the data payload to the UE. In some embodiments, the IWF is configured to send the data payload and a request to forward the data payload to the first module over the first reference point, and in response to receiving a 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.
In some embodiments, the IWF is configured to send the data payload and a request to forward the data payload to the second module over the second reference point. In some embodiments, the IWF includes a machine type communication interworking function (MTC-IWF) configured to terminate a reference point from the MTC server to the MTC-IWF. In some embodiments, the MTC-IWF is configured to authenticate the MTC server and authorize control plane requests from the MTC server and relay or convert a signaling protocol received over a reference point from the MTC server to the MTC-IWF. In some embodiments, the first module and the second module are each configured to transmit a data payload to the UE over a control plane of the wireless communication network. In some embodiments, the IWF is configured to send the data payload to a third module comprising a packet data network gateway (PGW) over a third reference point, 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 when the UE is in connected mode and to send the data payload using the first reference point or the second reference point when the UE is in idle or connected mode. In some embodiments, the wireless communication network comprises a global system for mobile communications (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).
The present disclosure also describes, in accordance with various embodiments, a system comprising: an interworking function (IWF) configured to receive a trigger from a Machine Type Communication (MTC) server to send an MTC data payload to a User Equipment (UE) over a wireless communication network; and a module comprising a Mobility Management Entity (MME) or a serving GPRS (general packet radio service) support node (SGSN), the module being coupled with the IWF by a reference point terminating at the IWF, wherein the IWF is further configured to send the MTC data payload to the module over the reference point and to forward a request for the MTC data payload to the UE. In some embodiments, the module is configured to send a paging message to a base station of the wireless communication network including a small data indicator indicating a location of the MTC data payload and/or the MTC data payload to be forwarded to the UE.
In some embodiments, the module is configured to send a paging message including an 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 (which includes a small data indicator and an MTC data payload) to the base station, and the base station is configured to send a paging message (which includes a small data indicator) to the UE, the small data indicator indicating that the MTC data payload is at the base station, the base station 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 (which includes a small data indicator) to the base station, the small data indicator indicating that an MTC data payload is at the module. In some embodiments, the base station is configured to send a paging message (which includes a small data indicator) to the UE. In some embodiments, the module is configured to send the MTC data payload to the UE in response to a non-access stratum (NAS) message sent by the UE, the NAS message sent by the UE in response to the paging message.
The present disclosure also describes, in accordance with various embodiments, a method comprising: receiving, by a machine type communication interworking function (MTC-IWF), a trigger from a Machine Type Communication (MTC) server to send a data payload (which is less than a preconfigured threshold) to a User Equipment (UE) over a wireless communication network; and transmitting, by the MTC-IWF, the data payload to a packet data network gateway (PGW) through the reference point. 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 comprises transmitting, by the PGW, the data payload to a Serving Gateway (SGW) of the wireless communication network.
In some embodiments, the method further comprises sending, by the SGW, the data payload to the UE over the user plane. In some embodiments, the reference point is a third reference point. In some embodiments, the method further comprises: if sending the data payload to a packet data network gateway (PGW) by the MTC-IWF over the reference point fails, sending the data payload by the MTC-IWF over a first reference point to a first module comprising a Mobility Management Entity (MME) or a serving GPRS (general packet radio service) support node (SGSN) or over a second reference point to a second module comprising a Home Location Register (HLR) or a Home Subscriber Server (HSS) and a request to forward the data payload to the UE. In some embodiments, the first module or the second module is configured to transmit the data payload to the UE over a control plane of the wireless communication network.
According 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 an antenna; and a control module configured to establish a wireless connection with a base station of a wireless communication network and to send a Machine Type Communication (MTC) data payload to the base station over the wireless connection for forwarding the MTC data payload to a module comprising a Mobility Management Entity (MME) or a serving GPRS (general packet radio service) support node (SGSN), the module configured to forward the MTC data payload to a machine type communication interworking function (MTC-IWF) over an interface, the MTC-IWF configured to forward the MTC data payload to an MTC server. In some embodiments, the control module further comprises a non-access stratum (NAS) module and an Access Stratum (AS) module. In some embodiments, the control module is further configured to establish the 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.
In some embodiments, the RRC connection request message includes a certain value indicating to the base station that a short-term 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 (which is sent in response to the 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 a sequence number and an 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 device to a message that includes the MTC data payload directed to the MTC-IWF.
In 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 an acknowledgement to the base station in a ciphered non-access stratum (NAS) Packet Data Unit (PDU) in the S1 downlink NAS transport message. In some embodiments, the base station is configured to forward the acknowledgement to the device 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 device 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 device further comprises one or more of a camera, a keyboard, a Liquid Crystal Display (LCD) screen, a non-volatile memory port, a plurality of antennas, a graphics chip, an Application Specific Integrated Circuit (ASIC), or a speaker.
Although 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 the embodiments described herein be limited only by the claims and the equivalents thereof.