WO2013105976A1

WO2013105976A1 - Native short message service for long term evolution

Info

Publication number: WO2013105976A1
Application number: PCT/US2012/021288
Authority: WO
Inventors: Devaki Chandramouli; Rainer Liebhart
Original assignee: Nokia Siemens Networks Oy
Priority date: 2012-01-13
Filing date: 2012-01-13
Publication date: 2013-07-18

Abstract

One embodiment is directed to a method and apparatus for supporting short message service (SMS) functionality. The method includes receiving a short message service (SMS) message at a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF). The method further includes creating and adding, by the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF), at least one header to the short message service (SMS) message. The method may also include forwarding the short message service (SMS) message to a mobility management entity (MME). The mobility management entity (MME) may then transfer the short message service message to a user equipment.

Description

NATIVE SHORT MESSAGE SERVICE FOR LONG TERM EVOLUTION

BACKGROUND:

Field:

[0001] Embodiments of the invention relate to wireless communications networks, such as the Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) Long Term Evolution (LTE) and Evolved UTRAN (E-UTRAN).

Description of the Related Art:

[0002] Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN) refers to a communications network including base stations, or Node-Bs, and radio network controllers (RNC). UTRAN allows for connectivity between the user equipment (UE) and the core network. The RNC provides control functionalities for one or more Node Bs. The RNC and its corresponding Node Bs are called the Radio Network Subsystem (RNS).

[0003] Long Term Evolution (LTE) refers to improvements of the UMTS through improved efficiency and services, lower costs, and use of new spectrum opportunities. In particular, LTE is a 3rd Generation Partnership Project (3GPP) standard that provides for uplink peak rates of at least 50 megabits per second (Mbps) and downlink peak rates of at least 100 Mbps. LTE supports scalable carrier bandwidths from 20 MHz down to 1.4 MHz and supports both Frequency Division Duplexing (FDD) and Time Division Duplexing (TDD).

[0004] As mentioned above, LTE improves spectral efficiency in communication networks, allowing carriers to provide more data and voice services over a given bandwidth. Therefore, LTE is designed to fulfill future needs for high-speed data and media transport in addition to high- capacity voice support. Advantages of LTE include high throughput, low latency, FDD and TDD support in the same platform, an improved end-user experience, and a simple architecture resulting in low operating costs. In addition, LTE is an all internet protocol (IP) based network, supporting both IPv4 and IPv6.

[0005] The Evolved 3 GPP Packet Switched Domain, which is also known as the Evolved Packet System (EPS), provides IP connectivity using the E- UTPvAN.

SUMMARY:

[0006] One embodiment is directed to a method for supporting short message service (SMS) functionality. The method includes receiving a short message service (SMS) message at a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF). The method further includes creating and adding, by the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF), at least one header to the short message service (SMS) message. The method may also include forwarding the short message service (SMS) message to a mobility management entity (MME). The mobility management entity (MME) may then transfer the short message service message to a user equipment.

[0007] Another embodiment is directed to an apparatus including at least one processor and at least one memory including computer program code. The at least one memory and the computer program code are configured, with the at least one processor, to cause the apparatus at least to receive a short message service (SMS) message, create and add at least one header to the short message service (SMS) message, and forward the short message service (SMS) message to a mobility management entity (MME). The mobility management entity (MME) transfers the short message service message to a user equipment. In one embodiment, the apparatus is a short message service center (SMSC). In another embodiment, the apparatus is a machine type communication interworking function (MTC-IWF).

[0008] Another embodiment is directed to an apparatus including means for receiving a short message service (SMS) message at a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF). The apparatus further includes means for creating and adding, by the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF), at least one header to the short message service (SMS) message. The apparatus may also include means for forwarding the short message service (SMS) message to a mobility management entity (MME). The mobility management entity (MME) may then transfer the short message service message to a user equipment.

[0009] Another embodiment includes a computer program embodied on a non-transitory computer readable medium. The computer program is configured to control a processor to perform a process that includes receiving a short message service (SMS) message at a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF). The process further includes creating and adding, by the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF), at least one header to the short message service (SMS) message. The process may also include forwarding the short message service (SMS) message to a mobility management entity (MME). The mobility management entity (MME) may then transfer the short message service message to a user equipment. BRIEF DESCRIPTION OF THE DRAWINGS:

[0010] For proper understanding of the invention, reference should be made to the accompanying drawings, wherein:

[0011] Fig. 1 illustrates a system according to one embodiment of the invention;

[0012] Fig. 2 illustrates a system according to another embodiment;

[0013] Fig. 3 illustrates a signaling diagram according to an embodiment;

[0014] Fig. 4 illustrates a system according to another embodiment;

[0015] Fig. 5 illustrates a signaling diagram according to another embodiment;

[0016] Fig. 6 illustrates an apparatus according to one embodiment;

[0017] Fig. 7 illustrates a flow diagram of a method according to one embodiment;

[0018] Fig. 8 illustrates a flow diagram of a method according to another embodiment;

[0019] Fig. 9 illustrates a signaling diagram according to another embodiment; and

[0020] Fig. 10 illustrates a signaling diagram according to another embodiment.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT(S):

[0021] The evolved packet system (EPS) is the evolution of the general packet radio system (GPRS). EPS provides a new radio interface and new evolved packet core (EPC) network functions for broadband wireless data access. Fig. 1 illustrates an example of the EPS core network 100, according to an embodiment. As illustrated in Fig. 1 , the EPS core network 100 may include the Mobility Management Entity (MME) 1 10, Packet Data Network Gateway (PGW) 125, and Serving Gateway (SGW) 120. MME 110 may be connected to SGW 120 via the SI interface, and the SGW 120 in turn may be connected to PGW 125 via the S5 interface.

[0022] A common packet domain core network, such as EPS core network 100, can be used to provide core network functionality to the base station controller (BSC) 103 of the GSM/Edge radio access network (GERAN), the radio network controller (RNC) 102 of the UTRAN, and the eNodeB (eNB) 101 of the E-UTRAN.

[0023] MME 1 10 may be considered the main control node for the core network 100. Some features handled by MME 1 10 include: bearer activation/de-activation, idle mode UE tracking, choice of SGW for a UE 104, intra-LTE handover involving core network node location, interacting with the home location register (HLR) / home subscriber server (HSS) 130 to authenticate user on attachment, and providing temporary identities for UEs 104.

[0024] HLR/HSS 130 is a central database that contains user-related and subscription-related information. Functions of the HLR/HSS 130 may include mobility management, call and session establishment support, user authentication and access authorization.

[0025] SGW 120 is a data plane element within the core network 100. SGW 120 manages user plane mobility and acts as the main interface between the radio access network(s) and the core network. SGW 120 can also maintain the data path between the eNBs 101 and PGW 125. As a result, SGW 120 may form an interface for the data packet network at the E- UTRAN. SGW 120 may also be in communication with home public land mobile network (HPLMN) gateway 135 which may store the home user's 140 subscription data. PGW 125 provides connectivity for the UE to external packet data networks (PDNs). A UE 104 may have connectivity with more than one PGW 125 for accessing multiple PDNs 150.

[0026] A serving GPRS support node (SGSN) 105 may be provided in the core network 100 to transfer information to and from the GERAN and UTRAN via an Iu interface, for example. SGSN 105 may communicate with SGW 120 via the S4 interface. SGSN 105 may store location information for a UE, such as current cell, and may also store user profiles, such as international mobile subscriber identity (IMSI).

[0027] The packet switched (PS) only ("PS-only") device triggering requirement has resulted in the need for PS-only short message service (SMS) requirement in LTE. Currently, circuit switched (CS) infrastructure or support for IMS is required to support voice and especially SMS services in EPS. For operators who do not support GSM CS infrastructure or who want to de-invest from CS in the future, IMS deployment is needed in order to be able to provide SMS services.

[0028] For SMS over IMS, devices are required to support IMS/SIP client which could make the device expensive in terms of SW deployment and maintenance. This is not suitable when the device does not need voice support, but only needs support for SMS. Examples of such devices include data cards or machine-type-devices. In the future, it is likely that machine type devices with support for "LTE only" but without support for IMS/SIP client will be deployed in some networks. Furthermore, when in-bound roamers, such as GSM/LTE devices with no IMS/SIP client, come into these networks, they will be unable to support SMS services. Also, when subscribers from these networks roam into other networks, they may not receive SMS services unless they have a CS subscription. These factors have resulted in the need for PS-only SMS or so-called "native SMS" in LTE.

[0029] In view of the above, embodiments of the invention are able to reuse the functionalities of the short message service center (SMSC) including the store and forward functionality that allows for the storage and subsequent delivery of messages when the UE is available. At the same time, embodiments of the invention avoid impacts to the MME without the assumption of a MSC being available in the network.

[0030] Embodiments provide a simple and a scalable solution for native SMS with little or no impact to the MME and at the same time retain the existing rich SMS features, such as the store and forward functionality. In one embodiment, the SMS related functionality, which is also referred to as SMS over SGs interface (SMSoSGs, see 3 GPP TS 23.272), can be provided by the SMSC. As a result, a MSC is not required in the network to provide the SMS related functionality. In another embodiment, the SMS related functionality (e.g., SMSoSGs) can be provided by the machine-type communication interworking function (MTC-IWF). MTC-IWF is a functional entity that was introduced for improvements for machine-type- communication (see, for example, 3GPP TS 23.682 and TR 23.888). MTC- IWF has interfaces to MME and SMSC. MTC-IWF also may act as an interworking function between the machine-type communication (MTC) Server and the 3 GPP core network. These architectures, according to embodiments of the invention, also address the device triggering requirement with "PS only" infrastructure and without the need for mobile station international subscriber directory number (MSISDN).

[0031] According to certain embodiments, the SMSoSGs functionality that may be provided by the SMSC and/or MTC-IWF includes looking at the source/destination headers of a message, such as a SMS message, and creating and adding headers to the message. The SMSC and/or MTC-IWF may also run a SMS state machine to monitor acknowledgements from the UE and report to the service center or application server for submit upon delivery. Further, in some embodiments, the SMSoSGs functionality provided by the SMSC and/or MTC-IWF can include generating missed call log(s), processing short message (SM) prepaid and postpaid charging related functionalities including interaction with a service control point (SCP), message waiting functionalities such as registering with the HSS for UE reachability notification, SMS specific barring functionalities, performing overload control, and generating SMS related O&M statistics including service reports, trace, SMS measurements, and Traffica.

[0032] Additionally, according to certain embodiments, MTC-IWF may implement direct SM delivery. For example, in the case of a UE-to-UE SMS scenario, if the destination UE is within the coverage area and is known, the SMS can be directly forwarded to the target UE bypassing the SMSC to enable efficient delivery.

[0033] In some embodiments, the SMSC and/or MTC-IWF may implement SM traffic filtering functionality, for example, to block mobile viruses and/or when mobile originated short message (MO-SM) traffic is unwanted and needs to be blocked as early as possible. The SMSC and/or MTC-IWF may maintain a blacklist in order to accomplish the blocking.

[0034] Fig. 2 illustrates a diagram of a system according to one embodiment of the invention. In this embodiment, SMS service layer 170 is configured to perform the SMS related functionality. SMS service layer 170 may include the SMSC, SMS-GMSC, SMS-IWMSC, or SMS router. SMS service layer 170 is in communication with HSS 130 and with MME 110. MME 1 10 can forward and receive message from UE 104 via eNB 101 , for example.

[0035] Fig. 3 illustrates an example of a signaling diagram showing the call flow for device triggering where the SMSC 170 is configured to perform the SMSoSGs related functionality in a PS-only environment, for example. As illustrated in Fig. 3, a domain name system (DNS) query 1 is performed between MTC server 205 and DNS server 210. At 2, an MTC trigger submit request is sent from MTC server 205 to MTC-IWF 200. At 3, MTC-IWF 200 performs authentication and load control and send a routing information request for the short message to the HSS 130. Then, at 5, HSS 130, may perform access authorization and send the routing information back to MTC-IWF at 6. MTC-IWF 200 then submits the SMS message to the SMSC 170 at 8. Upon receiving the SMS message, SMSC 170 sends a submit confirm message to MTC-IWF 200 at 9.

[0036] SMSC 170 performs call detail record (CDR) generation at 11. According to certain embodiments, SMSC 170 may further create a SMS payload, and create and add one or more headers to the SMS message. Depending on the charging model, SMSC 170 may need to interface with the SCP or the online charging system (OCS) for prepaid charging and decide whether SMS transmission should be allowed or denied, or perform postpaid charging related functionality (e.g., create and forward charging records). SMSC 170 may then forward the SMS message to MME 110 at 12. MME 110 transfers the message to UE 104 at 13, for example, using a downlink (DL) non-access-stratum (NAS) transport message or another NAS message. UE 104 may acknowledge the SMS by sending an uplink (UL) NAS transport message or another NAS message to MME 110. The message from UE 104 is transparently forwarded by MME 110, at 14, to SMSC 170, for example in an uplink unit data or DIAMETER message. SMSC 170 decodes the message and recognizes it as a delivery report. The delivery report may include an acknowledgement packet and confirms that the SMS message was delivered to UE 104. Upon receipt of the delivery report, SMSC 170 may then send, at 15, a message delivery report to MTC- IWF 200.

[0037] If the delivery of the SMS has failed, SMSC 170 may also register with HSS 130 for UE reachability notification to retain store-and- forward functionality. It may also include the generation of missed log due to an absent subscriber and call forwarding. SMSC 170 may also support notifying MME 1 10 that no more messages from SMSC 170 need to be tunneled. At 16, a MTC trigger delivery report may be provided from MTC-IWF 200 to MTC server 205.

[0038] As a result, in this embodiment, SMSC 170 supports all the functionalities of MTC-IWF 200 as listed in 3 GPP TS 23.682 for SIMTC and 3GPP TS 23.040 for SMS services. Additionally, in this embodiment, SMSC 170 supports necessary SMSoSGs functionality as defined in 3GPP TS 23.272 for MSC/VLR in a PS-only environment. SMSC 170 may also support "UE reachability notification" with HSS 130 in order to be able to support the store and forward functionality.

[0039] Fig. 4 illustrates a diagram of a system according to one embodiment of the invention. In this embodiment, MTC-IWF 200 is configured to perform the SMS related functionality. According to this embodiment, MTC-IWF 200 may communicate with MTC server 205, HSS 130, and MME 1 10. MME 1 10 can forward and receive message from UE 104 via eNB 101, for example.

[0040] Fig. 5 illustrates an example of a signaling diagram showing the call flow for device triggering where the MTC-IWF 200 is configured to perform the SMSoSGs related functionality in a PS-only environment. Steps 1 to 11 of the flow of Fig. 5 are similar to that of Fig. 3 described above. However, in the embodiment of Fig. 5, after creating the SMS payload, SMSC 170 forwards the message to MTC-IWF 200, at 12, to perform the SMS related functionality. MTC-IWF 200 may then create and add one or more headers to the SMS message. Depending on the charging model, MTC-IWF 200 may need to interface with the SCP or the OCS for prepaid charging and decide whether SMS transmission should be allowed or denied, or perform postpaid charging related functionality (e.g., create and forward charging records). At 13, MTC-IWF 200 may send the SMS message to MME 1 10 in a DL unit data or DIAMETER message, for example. MME 110 transfers the message to UE 104 at 13. MME 110 may then send a delivery report, at 14, directly to the SMSC 170. The delivery report may include an acknowledgement packet and confirms that the SMS message was delivered to UE 104.

[0041] If the delivery of the SMS has failed, MTC-IWF 200 may also register with HSS 130 for UE reachability notification to retain store-and- forward functionality. It may also include the generation of missed log due to an absent subscriber and call forwarding. MTC-IWF 200 may also support notifying MME 110 that no more messages from MTC-IWF 200 need to be tunneled. Upon receipt of the delivery report, at 16, a MTC trigger delivery report may be provided from MTC-IWF 200 to MTC server 205.

[0042] In this embodiment, MTC-IWF 200 acts as an interworking function, for example a SMS interworking function, in a PS-only environment such that it supports SMSoSGs functionality as defined in 3 GPP TS 23.272 for MSC/VLR. MTC-IWF 200 can also support MAP - DIAMETER interworking functionality to work with legacy network elements and in roaming scenarios. Additionally, in this embodiment, MTC-IWF 200 may also support "UE reachability notification" with HSS 130 in order to be able to support the store and forward functionality. [0043] Fig. 9 illustrates an example of a signaling diagram showing the call flow for mobile originated SMS (MO-SMS) SMSoSGS functionality implemented in SMSC 170, according to an embodiment. As illustrated in Fig. 9, at 1, the combined EPS/IMSI attach procedure or EPS attach procedure has been performed. At 2, a mobile originating SMS is triggered and UE 104 is in idle mode. UE 104 initiates the UE triggered service request procedure, which is defined in 3 GPP TS 23.401. UE 104 indicates its S-TMSI in the RRC signaling. UE 104 builds the SMS message to be sent as defined in 3 GPP TS 23.040 (i.e., the SMS message includes CP- DATA/RP-DATA/TPDU/SMS-SUBMIT parts). Following the activation of the radio bearers, the SMS message is encapsulated in a NAS message and sent to MME 1 10 at 3. MME 1 10 forwards the SMS message to SMSC 170 in an UL unit data message or DIAMETER message, for example, at 4. In order to permit the SMSC 170 to create an accurate charging record, MME 110 adds the IMEISV, the local time zone, the mobile station classmark 2, and the UE's current TAI and E-CGI to the message. At 4a, SMSC 170 acknowledges receipt of the SMS to UE 104. At 6, the SMS message is forwarded to the service center (SC) 220 and SC 220 returns a delivery report message at 7. At 8 and 9, SMSC 170 forwards the received delivery report to MME 1 10 associated with UE 104 in a DL unit data message. MME 1 10 encapsulates the received delivery report in a NAS message and sends the message to UE 104 at 10. At 1 1 and 12, UE 104 acknowledges receipt of the delivery report to SMSC 170. At 13, SMSC 170 may indicate to MME 110 that no more messages from SMSC 170 need to be tunneled.

[0044] Fig. 10 illustrates an example of a signaling diagram showing the call flow for mobile originated SMS (MO-SMS) SMSoSGs functionality implemented in MTC-IWF 200, according to an embodiment. Steps 1-3 of Fig. 10 are similar to those of Fig. 9 above. However, in this embodiment, MME 110 forwards the SMS message to MTC-IWF 200, at 4, in an uplink unit data or DIAMETER message, for example. At 4a, MTC-IWF 200 acknowledges receipt of the SMS to UE 104. Steps 5-8 are again similar to those of Fig. 9 discussed above. At 9, MTC-IWF 200 forwards the received delivery report to MME 1 10 associated with UE 104 in a DL unit data message. As outlined above, at 10, MME 110 encapsulates the received delivery report in a NAS message and sends the message to UE 104. At 1 1 and 12, UE 104 acknowledges receipt of the delivery report to MTC-IWF 200. At 13, MTC-IWF 200 may indicate to MME 1 10 that no more messages from MTC-IWF 200 need to be tunneled

[0045] Fig. 6 illustrates an apparatus 10 according to one embodiment. In an embodiment, apparatus 10 may be the SMSC 170 illustrated in Fig. 2. In another embodiment, apparatus 10 may be the MTC-IWF 200 illustrated in Fig. 4. Apparatus 10 includes a processor 22 for processing information and executing instructions or operations. Processor 22 may be any type of general or specific purpose processor. While a single processor 22 is shown in Fig. 6, multiple processors may be utilized according to other embodiments. In fact, processor 22 may include one or more of general- purpose computers, special purpose computers, microprocessors, digital signal processors ("DSPs"), field-programmable gate arrays ("FPGAs"), application-specific integrated circuits ("ASICs"), and processors based on a multi-core processor architecture, as examples.

[0046] Apparatus 10 further includes a memory 14, coupled to processor 22, for storing information and instructions that may be executed by processor 22. Memory 14 may be one or more memories and of any type suitable to the local application environment, and may be implemented using any suitable volatile or nonvolatile data storage technology such as a semiconductor-based memory device, a magnetic memory device and system, an optical memory device and system, fixed memory, and removable memory. For example, memory 14 can be comprised of any combination of random access memory ("RAM"), read only memory ("ROM"), static storage such as a magnetic or optical disk, or any other type of non-transitory machine or computer readable media. The instructions stored in memory 14 may include program instructions or computer program code that, when executed by processor 22, enable the apparatus 10 to perform tasks as described herein.

[0047] Apparatus 10 may further include a transmitter 28 for transmitting information, such as data and/or control signals. Apparatus 10 may also include a receiver 24 for receiving information including data and/or control signals. In some examples, the receiver and transmitter functionality may be implemented in a single transceiver unit.

[0048] In an embodiment, memory 14 stores software modules that provide functionality when executed by processor 22. The modules may include an operating system 15 that provides operating system functionality for apparatus 10. The memory may also store one or more functional modules 18, such as an application or program, to provide additional functionality for apparatus 10. The components of apparatus 10 may be implemented in hardware, or as any suitable combination of hardware and software.

[0049] In one embodiment, memory 14 and the computer program code stored thereon may be configured, with processor 22, to cause the apparatus 10 to receive a SMS message for routing. In some embodiments, memory 14 and the computer program code may be further configured, with processor 22, to cause the apparatus 10 to create a SMS payload for the SMS message. Apparatus 10 may then be controlled to create and add one or more headers to the SMS message. According to some embodiments, apparatus 10 is then controlled to forward the SMS message to MME 110 for routing to UE 104.

[0050] In certain embodiments, apparatus 10 is also controlled to receive a delivery report from MME 1 10 confirming that the SMS message was delivered. Apparatus 10 may then be controlled to provide a message delivery report to a MTC network entity, such as MTC server 210.

[0051] Fig. 7 illustrates a flow diagram of a method according to one embodiment. In some embodiments, the method of Fig. 7 may be performed by SMSC 170 discussed above. The method includes, at 700, receiving a SMS message at SMSC 170. At 710, the method includes creating a SMS payload for the SMS message. The method then includes, at 720, creating and adding one or more SMS headers to the SMS message. At 730, the SMS message is forwarded from SMSC 170 to MME 110. Then, at 740, the method includes receiving a delivery report from MME 1 10 confirming delivery of the SMS message to UE 104. The method may further include sending a message delivery report from SMSC 170 to MTC-IWF 200.

[0052] Fig. 8 illustrates a flow diagram of a method according to another embodiment. In some embodiments, the method of Fig. 8 may be performed by MTC-IWF 200 discussed above. The method includes, at 800, receiving a SMS message from SMSC 170. At 810, the method includes creating and adding one or more SMS headers to the SMS message. Then, at 820, the SMS message is forwarded from MTC-IWF 200 directly to MME 110. At 830, the method includes receiving a delivery report from MME 1 10 confirming delivery of the SMS message to UE 104. The method may further include sending a message delivery report from MTC-IWF 200 to MTC server 205.

[0053] In some embodiments, the methods of Figs. 7 and/or 8 may further include processing SM prepaid/postpaid charging related functionalities, which includes the decision to allow or deny the transmission of SMS and interaction with the service control point (SCP). In addition, the methods of Figs. 7 and/or 8 may also include generating missed call log(s), registration for UE reachability, SMS specific barring functionality, and performing overload control.

[0054] According to certain embodiments, the functionality of the flow diagram of Figs. 7 and 8, or that of any other method described herein, may be implemented by a software stored in memory or other computer readable or tangible media, and executed by a processor. In other embodiments, the functionality may be performed by hardware, for example through the use of an application specific integrated circuit (ASIC), a programmable gate array (PGA), a field programmable gate array (FPGA), or any other combination of hardware and software.

[0055] Embodiments of the invention provide several distinct advantages. These advantages include, but are not limited to, providing a native SMS solution and a device triggering solution as needed in 3GPP release 11. Further, embodiments preserve current SMSC deployment and retaining all the existing functionalities of SMSC. Embodiments of the invention are also able to support the store and forward functionality, and able to fulfill the requirements for PS-only SMS and MSISDN-less infrastructure. Embodiments do not require a LTE-MSC in the MME. Additionally, embodiments may make use of DIAMETER available at MME/SGSN and the DIAMETER routing function.

[0056] The computer readable media mentioned above may be at least partially embodied by a transmission line, a compact disk, digital -video disk, a magnetic disk, holographic disk or tape, flash memory, magnetoresistive memory, integrated circuits, or any other digital processing apparatus memory device. [0057] The described features, advantages, and characteristics of the invention may be combined in any suitable manner in one or more embodiments. One skilled in the relevant art will recognize that the invention may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the invention.

[0058] One having ordinary skill in the art will readily understand that the invention as discussed above may be practiced with steps in a different order, and/or with hardware elements in configurations which are different than those which are disclosed. Therefore, although the invention has been described based upon these preferred embodiments, it would be apparent to those of skill in the art that certain modifications, variations, and alternative constructions would be apparent, while remaining within the spirit and scope of the invention. In order to determine the metes and bounds of the invention, therefore, reference should be made to the appended claims.

Claims

WE CLAIM:

1. A method, comprising:

receiving a short message service (SMS) message at a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF);

creating and adding, by the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF), at least one header to the short message service (SMS) message; and

forwarding the short message service (SMS) message to a mobility management entity (MME), wherein the mobility management entity (MME) transfers the short message service message to a user equipment.

2. The method according to claim 1, further comprising:

creating, at the short message service center (SMSC), a short message service payload for the short message service (SMS) message.

3. The method according to claims 1 or 2, wherein the receiving comprises receiving an uplink unit data or DIAMETER message, wherein the uplink unit data or DIAMETER message comprises the short message service (SMS) message.

4. The method according to any of claims 1-3, further comprising:

receiving an uplink unit data or DIAMETER message;

decoding the message; and

recognizing the message as a delivery report confirming that the short message service (SMS) message was delivered to the user equipment.

5. The method according to any of claims 1-3, further comprising sending the delivery report to an originator of the short message service (SMS) request.

6. The method according to any of claims 1-5, wherein the forwarding comprises forwarding the short message service (SMS) message from the machine type communication interworking function (MTC-IWF) to the mobility management entity (MME) in a downlink unit data or DIAMETER message.

7. The method according to any of claims 1-6, further comprising:

sending, from the machine type communication interworking function (MTC-IWF), a machine type communication trigger delivery report to a machine type communication server or short message service center (SMSC).

8. The method according to any of claims 1-7, further comprising indicating to the mobility management entity (MME) that no more messages from the short message service center (SMSC) or the machine type communication interworking function (MTC-IWF) need to be tunneled.

9. The method according to any of claims 1-8, further comprising:

generating missed call log(s);

processing short message (SM) prepaid and postpaid charging related functionalities including interaction with a service control point (SCP); performing message waiting functionalities including registering with a home subscriber server (HSS) for user equipment (UE) reachability notification;

performing short message service (SMS) specific barring

functionalities;

performing overload control; and

generating short message service (SMS) related operation and maintenance (O&M) statistics including service reports, trace, short message service (SMS) measurements, and traffica.

10. The method according to any of claims 1-9, further comprising:

implementing, by the machine-type communication interworking function (MTC-IWF), direct short message (SM) delivery,

wherein the direct short message (SM) delivery comprises, in the case of a UE-to-UE short message service (SMS) scenario where a destination UE is within the coverage area and is known, the short message service (SMS) message is directly forwarded to the destination UE bypassing the short message service center (SMSC).

11. The method according to any of claims 1-10, further comprising:

implementing short message (SM) traffic filtering functionality to block mobile viruses and/or when mobile originated short message (MO- SM) traffic is unwanted and needs to be blocked as early as possible.

12. An apparatus, comprising:

at least one processor; and

at least one memory including computer program code,

the at least one memory and the computer program code configured, with the at least one processor, to cause the apparatus at least to

receive a short message service (SMS) message;

create and add at least one header to the short message service (SMS) message; and

forward the short message service (SMS) message to a mobility management entity (MME), wherein the mobility management entity (MME) transfers the short message service message to a user equipment,

wherein the apparatus comprises one of a short message service center (SMSC) or a machine type communication interworking function (MTC-IWF).

13. The apparatus according to claim 12, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to create, at the short message service center (SMSC), a short message service payload for the short message service (SMS) message.

14. The apparatus according to claims 12 or 13, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to receive an uplink unit data or DIAMETER message, wherein the uplink unit data or DIAMETER message comprises the short message service (SMS) message.

15. The apparatus according to any of claims 12-14, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to receive an uplink unit data or DIAMETER message, decode the message, and recognize the message as a delivery report confirming that the short message service (SMS) message was delivered to the user equipment.

16. The apparatus according to any of claims 12-15, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to forward the short message service (SMS) message from the machine type communication interworking function (MTC-IWF) to the mobility management entity (MME) in a downlink unit data or DIAMETER message.

17. The apparatus according to any of claims 12-16, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to send a machine type communication trigger delivery report to a machine type communication server.

18. The apparatus according to any of claims 12-17, wherein the at least one memory and the computer program code are further configured, with the at least one processor, to cause the apparatus at least to indicate to the mobility management entity (MME) that no more messages from the apparatus need to be tunneled.

19. A computer program embodied on a non-transitory computer readable medium, the computer program configured to control a processor to perform a process, the process comprising:

20. The computer program to claim 19, further comprising:

21. The computer program according to claims 19 or 20, wherein the receiving comprises receiving an uplink unit data or DIAMETER message, wherein the uplink unit data or DIAMETER message comprises the short message service (SMS) message.

22. The computer program according to any of claims 19-21, further comprising:

receiving an uplink unit data or DIAMETER message;

decoding the message; and

recognizing the message as a delivery report confirming that the short message service (SMS) message was delivered to the user equipment..

23. The computer program according to any of claims 19-22, wherein the forwarding comprises forwarding the short message service (SMS) message from the machine type communication interworking function (MTC-IWF) to the mobility management entity (MME) in a downlink unit data or DIAMETER message.

24. The computer program according to any of claims 19-23, further comprising:

sending, from the machine type communication interworking function (MTC-IWF), a machine type communication trigger delivery report to a machine type communication server.