APPARATUS AND METHOD TO EFFICIENTLY SEND DEVICE TRIGGER MESSAGES

• US 20150249958A1
• Filed: 03/23/2015
• Published: 09/03/2015
• Est. Priority Date: 07/02/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet, Rao, Varun, Shan, Chang Hong, Venkatachalam, Muthaiah
• Granted Patent: US 9,432,150 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 1/0025 Transmission of mode-switching indication
• CPC Class Codes: H04L 1/0026 Transmission of channel quality indication
• CPC Class Codes: H04L 1/1628 List acknowledgements, i.e. the acknowledgement message consisting of a list of identifiers, e.g. of sequence numbers H04L1/1614 takes precedence
• CPC Class Codes: H04L 1/1812 Hybrid protocols; Hybrid automatic repeat request [HARQ]
• CPC Class Codes: H04L 1/1854 Scheduling and prioritising arrangements
• CPC Class Codes: H04L 1/1861 Physical mapping arrangements for ACK signaling see also H04L5/0053
• CPC Class Codes: H04L 1/1887 Scheduling and prioritising arrangements
• CPC Class Codes: H04L 5/0048 Allocation of pilot signals, i.e. of signals known to the receiver
• CPC Class Codes: H04L 5/0053 Allocation of signaling, i.e. of overhead other than pilot signals
• CPC Class Codes: H04L 5/0055 Physical resource allocation for ACK/NACK for physical mapping arrangements in ARQ protocols H04L1/1861
• CPC Class Codes: H04L 5/0064 Rate requirement of the data, e.g. scalable bandwidth, data priority
• CPC Class Codes: H04L 5/0073 Allocation arrangements that take into account other cell interferences for intercell interference mitigation or co-ordination in orthogonal multiplex systems H04J11/005
• CPC Class Codes: H04L 5/14 Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1033 Signalling gateways
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04W 12/08 Access security
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/0205 at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/08 : Load balancing or load distribution transferring a connection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 48/12 : using downlink control channel
• CPC Class Codes: H04W 52/0206 : in access points, e.g. base stations access point devices per se H04W88/08
• CPC Class Codes: H04W 52/0209 : in terminal devices terminal devices per se H04W88/02
• CPC Class Codes: H04W 52/0212 : managed by the network, e.g. network or access point is master and terminal is slave
• CPC Class Codes: H04W 52/0245 : according to signal strength
• CPC Class Codes: H04W 52/383 : power control in peer-to-peer links
• CPC Class Codes: H04W 68/00 : User notification, e.g. alerting and paging, for incoming communication, change of service or the like
• CPC Class Codes: H04W 72/0446 : Resources in time domain, e.g. slots or frames
• CPC Class Codes: H04W 72/046 : the resource being in the space domain, e.g. beams
• CPC Class Codes: H04W 72/21 : in the uplink direction of a wireless link, i.e. towards the network
• CPC Class Codes: H04W 72/23 : in the downlink direction of a wireless link, i.e. towards a terminal
• CPC Class Codes: H04W 72/30 : Resource management for broadcast services
• CPC Class Codes: H04W 72/569 : of the traffic information
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 92/02 : Inter-networking arrangements
• CPC Class Codes: Y02D 30/70 : in wireless communication networks
• CPC Class Codes: Y02E 40/60 : Superconducting electric elements or equipment; Power systems integrating superconducting elements or equipment

Abstract

With the proliferation of Machine-Type Communication (MTC), an excessive use of device trigger messages in a Long Term Evolution (LTE) network can have negative effects on user equipment (UE). These effect can include a shortening of UE battery life and/or excessive signalling caused by the frequent changing from an idle mode to an active mode. An MTC Interworking Function (MTC-IWF) can be configured to determine the status of a UE to which a device trigger message is intended. If the device trigger message is low priority and the UE is in an idle state, the MTC-IWF or Mobile Management Entity (MME)/Serving GPRS Support Node (SGSN)/Mobile Switching Center (MSC) can buffer the device trigger message.

Claims

1. (canceled)

2. A user equipment (UE) comprising:

transceiver circuitry configured to;

receive triggering information that includes an Application Port ID; and

processor circuitry in the UE to;

route a trigger to a triggering function using the Application Port ID, wherein the message further includes a standardized identifier, and wherein the circuitry is further arranged to distinguish messages carrying device triggering information based on the standardized identifier identify an Application Port ID based on a message.

3. The UE of claim 2, wherein the UE is configured to perform machine-type communications (MTC).

4. The UE of claim 2, further including:

two or more antennas.

5. The UE of claim 2, further including:

file storage memory.

6. A Machine Type Communication Interworking Function (MTC-IWF) comprising:

processing circuitry to

receive a device trigger request, from a Services Capability Server (SCS), that includes an Application Port ID; and

forward a standardized identifier to the UE to allow the UE to distinguish machine-type messages carrying device triggering information.

7. The MTC-IWF of claim 6, wherein a trigger payload corresponding to the device trigger request includes a priority value to indicate priority of the trigger request.

8. The MTC-IWF of claim 7, wherein the MTC-IWF is further arranged to,

when the priority of the device trigger request is low,

send the device trigger message when the UE is in a connected state;

and

buffer the device trigger message when the UE is in an idle state.

9. A computer-readable medium including instructions that, when executed on a machine, cause the machine to:

receive a message including a device trigger request that includes an Application Port ID; and

forward a standardized identifier to the UE to allow the UE to distinguish machine-type messages carrying device triggering information.

10. The computer-readable medium of claim 9, wherein a trigger payload corresponding to the device trigger request includes a priority value to indicate priority of the trigger request.

11. The computer-readable medium of claim 10, wherein the instructions further cause the machine to, when the priority of the device trigger request is low,

send the device trigger message when the UE is in a connected state;

and

buffer the device trigger message when the UE is in an idle state.

12. The computer-readable medium of claim 9, wherein the machine includes a Machine Type Communications Interworking Function (MTC-IWF), and wherein the request is received from a Services Capability Server (SCS).

13. The computer-readable medium of claim 9 wherein the machine is a mobile management entity (MME).

14. A non-transitory computer-readable medium including instructions that, when executed on a user equipment (UE), cause the UE to:

identify an Application Port ID; and

route a trigger to a triggering function, within the UE, indicated by the Application Port ID.

15. The non-transitory computer-readable medium of claim 14, wherein triggering information is received via IP-SM-GW.

16. The non-transitory computer-readable medium of claim 14, wherein triggering information further includes a standardized identifier, and wherein the instructions further cause the UE to distinguish messages carrying device triggering information based on the standardized identifier.

17. An apparatus comprising:

circuitry configured to identify an Application Port ID based on a message from a 3rd Generation Partnership Project (3GPP) network; and

route a trigger to a triggering function using the Application Port ID, wherein the message further includes a standardized identifier, and wherein the circuitry is further arranged to distinguish messages carrying device triggering information based on the standardized identifier.

18. The apparatus of claim 17, wherein triggering information is received via IP Short Message Gateway (IP-SM-GW).

19. The apparatus of claim 17, wherein the circuitry is included in a device is configured to perform machine-type communications (MTC).