Method of Handling Signaling and Data Transmission for Machine-Type Communication

• US 20120257571A1
• Filed: 04/09/2012
• Published: 10/11/2012
• Est. Priority Date: 04/07/2011
• Status: Active Grant

• Current Assignee: HTC Corporation
• Original Assignee: HTC Corporation
• Inventors: Liao, Ching-Yu
• Granted Patent: US 9,113,355 B2
• Time in Patent Office: Days
• US Class Current: 370/328
• CPC Class Codes: H04W 28/0247 based on conditions of the access network or the infrastructure network central resource management H04W28/16
• CPC Class Codes: H04W 28/04 Error control
• CPC Class Codes: H04W 4/70 Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 88/16 Gateway arrangements

Abstract

A method of handling signaling and data transmission for machine-type communication (MTC) for a network node in a mobile communication environment is disclosed. The method comprises receiving a non-access stratum (NAS) request message from a mobile communication device when the network control node is congested; and sending a trigger delivery failure report to a network gateway node in the core network to reject a trigger request message received from the network gateway node for triggering the mobile communication device.

Claims

1. A method of handling signaling and data transmission for machine-type communication (MTC) in a network control node of a core network of a mobile communication system, the method comprising:

receiving a non-access stratum (NAS) request message from a mobile communication device when the network control node is congested; and

sending a trigger delivery failure report to a network gateway node in the core network to reject a trigger request message received from the network gateway node for triggering the mobile communication device.

2. The method of claim 1, further comprising:

sending a NAS reject message with a NAS back-off timer to the mobile communication device; and

storing a back-off status corresponding to the mobile communication device;

wherein the trigger delivery failure report is sent to the network gateway node when the back-off status corresponding to the mobile communication device is active.

3. The method of claim 2, wherein the back-off status is sent with the trigger delivery failure report to the network gateway node.

4. The method of claim 3, wherein the back-off status is a trigger back-off timer corresponding to the NAS back-off timer.

5. A method of handling signaling and data transmission for machine-type communication (MTC) in a network gateway node of a core network of a mobile communication system, the method comprising:

forwarding a first trigger request message received from a MTC server to a network control node of the core network, wherein the first trigger request message is for triggering a mobile communication device;

receiving a first trigger delivery failure report from the network control node; and

sending a second trigger delivery failure report to the MTC server in response to receiving the first trigger delivery failure report.

6. The method of claim 5, wherein the first trigger delivery failure report includes a back-off status corresponding to the mobile communication device, and the method further comprises:

receiving a second trigger request message for triggering the mobile communication device from the MTC server; and

sending a third trigger delivery failure report to the MTC server according to the back-off status.

7. The method of claim 6, wherein the back-off status is sent with the third trigger delivery failure report to the MTC server.

8. A method of handling signaling and data transmission for machine-type communication (MTC) for a core network in a wireless communication system, the method comprising:

selectively performing trigger suppression operation on at least a trigger request from a MTC server according to whether the core network is congested or overloaded.

9. The method of claim 8, wherein the core network comprises at least one of a network control node, a data base and a network gateway node.

10. The method of claim 8, wherein the trigger suppression operation comprises at least one of sending trigger delivery failure report to the MTC server, stopping forwarding stored trigger requests, dropping received trigger requests, and deleting the stored trigger requests.

11. The method of claim 9, wherein the trigger suppression operation is performed according to a trigger suppression setting, wherein the trigger suppression setting comprises at least one of a trigger-suppressing factor, a trigger-suppressing duration, a triggering-suppressing application identifier, a trigger-suppress-identifier, a group of MTC devices with a specific group identifier, a specific priority type, a particular MTC server, a particular MTC server with a specific Transmission Control Protocol (TCP) port or a specific User Datagram Protocol (UDP) port, a MME identifier, a SGSN identifier, a specific access point name (APN), and a MME identifier or a SGSN identifier associated with a specific APN.

12. The method of claim 11 further comprising:

the network gateway node sending a message to the MTC server via X1 interface, wherein the message comprises at least an optional information element (IE) which includes the trigger suppression setting.

13. The method of claim 11 further comprising:

the network control node sending a message to the network gateway node via X2 interface, wherein the message comprises at least an optional information element (IE) which includes the trigger suppression setting.

14. The method of claim 9 further comprising:

the network gateway node rejecting the trigger request with a trigger back-off timer for a mobile communication device or a group of mobile communication devices to the MTC server;

wherein the MTC server does not send any other trigger request to the mobile communication device or the group of mobile communication devices before the trigger back-off timer expires.

15. The method of claim 9 further comprising the network control node sending a message via X2 interface to the network gateway node to start or stop the suppress operation of the network gateway node, according to whether the network control node is congested.

16. The method of claim 15, wherein the message is a trigger delivery failure report corresponding to the trigger request received from the network gateway node.

17. The method of claim 9 further comprising the network gateway node sending a message via X1 interface to the MTC server to start or stop the suppress operation of the MTC server, according to whether the network gateway node is congested.

18. The method of claim 17, wherein the message is a trigger delivery failure report corresponding to the trigger request received from the MTC server.

19. The method of claim 9 further comprising the network gateway node sending the trigger request received from the MTC server to a target mobile communication device via a packet data connection (PDN) gateway node, wherein the target mobile communication device has an IP address available in at least one of the network gateway node and the MTC server.

20. The method of claim 19 further comprising:

the network gateway node receiving from the PDN gateway node via X3 interface a message indicating a trigger-suppression time for a specific access point name (APN) when an overload situation on the specific APN is detected by the PDN gateway node; and

the network gateway node performs the trigger suppression operation according to the received message.

21. The method of claim 20, wherein the message indicates a trigger suppression setting comprising at least one of optional information elements (IEs), wherein the trigger suppression setting comprises at least one of a P-GW identifier, a trigger-suppress-identifier, a group of MTC devices with a specific group identifier, a specific application identifier, a priority type, a particular MTC server, a particular MTC server with a specific TCP port or a specific UDP port, a MTC server-specific-triggering-suppressing application identifier, a MTC-server specific-trigger-suppressing factor, and a MTC server specific-trigger-suppressing delay.

22. The method of claim 19 further comprising:

the network control node receiving from the PDN gateway node a message indicating a back-off time and a trigger suppression setting for a specific access point name (APN) when an overload situation on the specific APN is detected by the PDN gateway node; and

the network control node performs the trigger suppression operation according to the received message;

wherein the trigger suppression setting is included in an optional information element (IE) of the message and comprises at least one of a P-GW identifier, a trigger-suppress-identifier, a group of MTC devices with a specific group identifier, a specific application identifier, a priority type, a particular MTC server, a particular MTC server with a specific TCP port or a specific UDP port, a MTC server-specific-triggering-suppressing application identifier, a MTC-server specific-trigger-suppressing factor, and a MTC server specific-trigger-suppressing delay.