Short message server, terminal trigger method of server thereof, trigger request delivery server, trigger request deliver method of server thereof

• US 9,900,269 B2
• Filed: 10/05/2012
• Issued: 02/20/2018
• Est. Priority Date: 10/10/2011
• Status: Active Grant

• Current Assignee: Golden Eye Technologies LLC (Harfang IP Investment Corp)
• Original Assignee: KT Corporation
• Inventors: Cho, Soo Hyun, Hong, Sung Pyo, Lee, Sung Hoon, Lee, Hyun Song
• Primary Examiner(s): Anyan, Barbara B
• Application Number:
  US14/350,743
• Publication Number:
  US 20140258434A1
• Time in Patent Office: 1,964 Days
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 2101/654 International mobile subscriber identity [IMSI] numbers
• CPC Class Codes: H04L 51/04 Real-time or near real-time messaging, e.g. instant messaging [IM]
• CPC Class Codes: H04L 61/103 across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
• CPC Class Codes: H04L 61/4588 containing mobile subscriber information, e.g. home subscriber server [HSS]
• CPC Class Codes: H04L 61/5053 Lease time; Renewal aspects
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/18 using different networks or channels, e.g. using out of band channels cryptographic mechanisms or cryptographic arrangements for key distribution involving distinctive intermediate devices or communication paths H04L9/0827; cryptographic mechanisms or cryptographic arrangements for authentication using a plurality of channels H04L9/3215
• CPC Class Codes: H04W 4/12 Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/14 Short messaging services, e.g. short message services [SMS] or unstructured supplementary service data [USSD]
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]

Abstract

The present application relates to a control function related to a trigger in a communication network for machine-type communication. A method for triggering a terminal comprises the steps of: receiving a trigger request message from a trigger request transmission server which transmits trigger requests from external servers; and transmitting the trigger request message to a terminal using a received short message, wherein transmission parameters of the short message indicates that the received short message is a short message for triggering a machine-type communication (MTC) apparatus.

Claims

1. A trigger request delivery server comprising at least one hardware processor that executes:

an interface module of a server side configured to receive a trigger request for triggering a terminal from a machine type communication (MTC) external server, wherein the trigger request includes (i) an identifier of the terminal to be triggered and (ii) a validity time to store the trigger request in a network when the trigger request is not delivered to the terminal;

a terminal identifier mapping module configured to;

determine whether the identifier of the terminal included in the trigger request is a mobile subscriber ISDN number (MSISDN) or a non-MSISDN identifier, wherein the non-MSISDN identifier includes at least one of a fully qualified domain name (FQDN), a network access identifier (NAI), a session initiation protocol uniform resource identifier (SIP URI), and an Internet protocol (IP) address; and

map the identifier of the terminal to an IMSI (International Mobile Subscriber Identity), capable of identifying in a mobile network, of the terminal when the identifier of the terminal is the non-MSISDN identifier; and

an interface module of a short message server side configured to;

generate a first short message using the trigger request and the IMSI of the terminal according to a short message service (SMS) protocol when the identifier of the terminal is the non-MSISDN identifier, wherein the first short message is generated to include the IMSI of the terminal such that the IMSI is used as information identifying the terminal in the mobile network,

generate a second short message using the trigger request and the MSISDN of the terminal according to the SMS protocol when the identifier of the terminal is the MSISDN, wherein the second short message is generated to include the MSISDN of the terminal such that the MSISDN is used as information identifying the terminal in the mobile network, and

transmit the generated first short message or the generated second short message to a short message server such that the first short message or the second short message is delivered by the short message server to the terminal through the mobile network.

2. The trigger request delivery server of claim 1, wherein the terminal identifier mapping module interrogates a HLR/HSS (Home Location Register/Home Subscriber Server) in order to map the identifier of the terminal to the IMSI (International Mobile Subscriber Identity) of the terminal.

3. The trigger request delivery server of claim 1, wherein the validity time is included in a parameter of at least one of the first short message and the second short message.

4. The trigger request delivery server of claim 1, wherein the trigger request comprises at least one of an identifier of the MTC external server, the identifier of the terminal, an identifier of an application operated on the terminal and a priority.

5. The trigger request delivery server of claim 1, further comprising an overload determining module configured to determine an overload by managing a number of trigger requests transmitted from a specific MTC external server or a total number of trigger requests transmitted from all MTC external servers.

6. The trigger request delivery server of claim 5, wherein the trigger request comprises information on a priority.

7. The trigger request delivery server of claim 1, wherein the interface module of the short message server side receives a report with success or failure of delivery of at least one of the first short message and the second short message from the short message server.

8. A short message server comprising at least one hardware processor that executes:

an interface module of a server side configured to receive a trigger request message for triggering a terminal, delivered from a trigger request delivery server configured to deliver a trigger request from a machine type communication (MTC) external server, wherein the trigger request includes (i) an identifier of the terminal to be triggered and (ii) a validity time to store the trigger request in a network when the trigger request is not delivered to the terminal, and

an interface module of a terminal side configured to deliver the trigger request message to the terminal, through a mobile network, using a mobile terminated short message,

wherein a short message transfer layer parameter represents that the mobile terminated short message is a short message for a MTC device triggering;

wherein the mobile terminated short message includes an IMSI (International Mobile Subscriber Identity) of the terminal mapped to the identifier of the terminal such that the IMSI is used as information identifying the terminal in the mobile network;

wherein the mapping of the identifier of the terminal and the IMSI includes determining whether the identifier of the terminal is a mobile subscriber ISDN number (MSISDN) or a non-MSISDN identifier, and mapping the identifier of the terminal to the IMSI, capable of identifying in the mobile network, of the terminal when the identifier of the terminal is the non-MSISDN identifier;

wherein the non-MSISDN identifier includes at least one of a fully qualified domain name (FQDN), a network access identifier (NAI), a session initiation protocol uniform resource identifier (SIP URI), and an Internet protocol (IP) address; and

wherein when the identifier of the terminal is the MSISDN, the mobile terminated short message includes the MSISDN of the terminal such that the MSISDN is used as information identifying the terminal in the mobile network.

9. The short message server of claim 8, wherein at least a portion of the trigger request message is mapped to a SMS application layer protocol parameter, a SMS transfer layer protocol parameter, or SMS relay layer protocol parameter.

10. The short message server of claim 8, wherein an application identifier included in the trigger request message is in a TP-UD (Transfer Protocol-User Data) which is a SMS transfer layer protocol parameter.

11. A method for delivering a trigger request in a short message delivery server delivering the trigger request from a machine type communication (MTC) external server to a terminal, the method comprising:

receiving the trigger request for triggering the terminal from the MTC external server, wherein the trigger request includes (i) an identifier of the terminal to be triggered and (ii) a validity time to store the trigger request in a network when the trigger request is not delivered to the terminal;

determining whether the identifier of the terminal included in the trigger request is a mobile subscriber ISDN number (MSISDN) or a non-MSISDN identifier, wherein the non-MSISDN identifier includes at least one of a fully qualified domain name (FQDN), a network access identifier (NAI), a session initiation protocol uniform resource identifier (SIP URI), and an Internet protocol (IP) address;

mapping the identifier of the terminal to an IMSI (International Mobile Subscriber Identity), capable of identifying in a mobile network, of the terminal when the identifier of the terminal is the non-MSISDN identifier;

generating a first short message using the trigger request and the IMSI of the terminal according to a short message service (SMS) protocol when the identifier of the terminal is the non-MSISDN identifier, wherein the first short message is generated to include the IMSI of the terminal such that the IMSI is used as information identifying the terminal in the mobile network;

generating a second short message using the trigger request and the MSISDN of the terminal according to the SMS protocol when the identifier of the terminal is the MSISDN, wherein the second short message is generated to include MSISDN of the terminal such that the MSISDN is used as information identifying the terminal in the mobile network; and

transmitting the generated first short message or the generated second short message to a short message server such that the first short message or the second short message is delivered by the short message server to the terminal through the mobile network.

12. The method of claim 11, wherein the mapping comprises interrogating a HLR/HSS (Home Location Register/Home Subscriber Server) and so mapping the identifier of the terminal to the IMSI (International Mobile Subscriber Identity) of the terminal.

13. The method of claim 11, wherein the validity time is included in a parameter of at least one of the first short message and the second short message.

14. The method of claim 11, wherein the trigger request comprises at least one of an identifier of the MTC external server, the identifier of the terminal, an identifier of an application operated on the terminal, and a priority.

15. The method of claim 11, further comprising:

determining an overload state by managing at least one of a number of trigger requests transmitted from a specific MTC external server and a total number of trigger requests transmitted from all MTC external servers.

16. The method of claim 15, wherein the trigger request comprises information on a priority.

17. The method of claim 11, further comprising:

receiving a report on a success or a failure of the delivery of at least one of the first short message and the second short message from the short message server.