Machine type communication monitoring framework for 3GPP systems

• US 9,025,445 B2
• Filed: 06/27/2013
• Issued: 05/05/2015
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel Corporation
• Inventors: Jain, Puneet K., Rao, Varun N., Venkatachalam, Muthaiah
• Primary Examiner(s): Phan, Tri H
• Application Number:
  US13/928,628
• Publication Number:
  US 20140092808A1
• Time in Patent Office: 677 Days
• Field of Search: 370229-238, 370/252, 370254-258, 370310-350, 370400-408, 370437-439, 455431-466
• US Class Current: 370/229
• CPC Class Codes: H04B 17/318 Received signal strength
• CPC Class Codes: H04J 11/00 Orthogonal multiplex systems, e.g. using WALSH codesH04J13/00 takes precedence
• CPC Class Codes: H04J 11/0086 Search parameters, e.g. search strategy, accumulation length, range of search, thresholds code acquisition in DSSS H04B1/7075
• CPC Class Codes: H04J 3/1694 Allocation of channels in TDM/TDMA networks, e.g. distributed multiplexers Passive Optical Networks H04Q11/0062
• CPC Class Codes: H04L 1/1812 Hybrid protocols; Hybrid automatic repeat request [HARQ]
• CPC Class Codes: H04L 1/1861 Physical mapping arrangements for ACK signaling see also H04L5/0053
• CPC Class Codes: H04L 1/1864 ARQ related signaling H04L1/1607 takes precedence
• CPC Class Codes: H04L 1/1893 Physical mapping arrangements physical resource mapping in general H04L5/00
• CPC Class Codes: H04L 41/069 using logs of notifications; Post-processing of notifications
• CPC Class Codes: H04L 41/5032 Generating service level reports
• CPC Class Codes: H04L 43/16 Threshold monitoring
• CPC Class Codes: H04L 5/001 the frequencies being arranged in component carriers
• CPC Class Codes: H04L 5/0035 Resource allocation in a cooperative multipoint environment
• 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/0057 Physical resource allocation for CQI
• 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/0091 Signaling for the administration of the divided path
• CPC Class Codes: H04L 5/14 Two-way operation using the same type of signal, i.e. duplex
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 65/612 for unicast
• CPC Class Codes: H04L 65/65 : Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]
• CPC Class Codes: H04L 65/762 : at the source reformatting of additional data in video distribution servers H04N21/2355
• CPC Class Codes: H04L 67/10 : in which an application is distributed across nodes in the network software deployment G06F8/60; multiprogramming arrangements G06F9/46
• CPC Class Codes: H04W 24/02 : Arrangements for optimising operational condition
• CPC Class Codes: H04W 24/08 : Testing, supervising or monitoring using real traffic
• 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/0215 : based on user or device properties, e.g. MTC-capable devices services for machine-to-machine communication [M2M] or machine type communication [MTC] H04W4/70; wireless resource selection or allocation plan definition based on terminal or device properties H04W72/51
• CPC Class Codes: H04W 28/0221 : power availability or consumption
• CPC Class Codes: H04W 28/0252 : per individual bearer or channel dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/0268 : using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 28/16 : Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
• CPC Class Codes: H04W 36/0061 : of neighbour cell information
• CPC Class Codes: H04W 36/0066 : of control information between different types of networks in order to establish a new radio link in the target network
• CPC Class Codes: H04W 36/0083 : Determination of parameters used for hand-off, e.g. generation or modification of neighbour cell lists
• CPC Class Codes: H04W 36/0085 : Hand-off measurements
• CPC Class Codes: H04W 36/0088 : Scheduling hand-off measurements
• CPC Class Codes: H04W 36/08 : Reselecting an access point
• CPC Class Codes: H04W 36/14 : Reselecting a network or an air interface
• CPC Class Codes: H04W 36/22 : for handling the traffic
• CPC Class Codes: H04W 4/70 : Services for machine-to-machine communication [M2M] or machine type communication [MTC]
• CPC Class Codes: H04W 40/005 : Routing actions in the presence of nodes in sleep or doze mode
• CPC Class Codes: H04W 40/246 : Connectivity information discovery
• CPC Class Codes: H04W 48/14 : using user query or user detection
• CPC Class Codes: H04W 48/16 : Discovering, processing access restriction or access information
• CPC Class Codes: H04W 48/18 : Selecting a network or a communication service
• CPC Class Codes: H04W 48/20 : Selecting an access point
• 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/0225 : using monitoring of external events, e.g. the presence of a signal
• CPC Class Codes: H04W 52/0235 : where the received signal is a power saving command
• CPC Class Codes: H04W 52/0258 : controlling an operation mode according to history or models of usage information, e.g. activity schedule or time of day
• CPC Class Codes: H04W 52/0261 : managing power supply demand, e.g. depending on battery level
• CPC Class Codes: H04W 52/04 : TPC
• CPC Class Codes: H04W 52/14 : Separate analysis of uplink or downlink
• CPC Class Codes: H04W 72/02 : Selection of wireless resources by user or terminal
• CPC Class Codes: H04W 72/044 : based on the type of the allocated resource
• CPC Class Codes: H04W 72/0453 : Resources in frequency domain, e.g. a carrier in FDMA
• CPC Class Codes: H04W 72/20 : Control channels or signalling for resource management
• 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/52 : based on load
• CPC Class Codes: H04W 72/541 : using the level of interference
• CPC Class Codes: H04W 74/002 : Transmission of channel access control information
• CPC Class Codes: H04W 74/004 : in the uplink, i.e. towards network
• CPC Class Codes: H04W 76/12 : Setup of transport tunnels
• CPC Class Codes: H04W 76/15 : Setup of multiple wireless link connections
• CPC Class Codes: H04W 76/16 : Involving different core network technologies, e.g. a packet-switched [PS] bearer in combination with a circuit-switched [CS] bearer
• CPC Class Codes: H04W 76/23 : Manipulation of direct-mode connections
• CPC Class Codes: H04W 76/27 : Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/28 : Discontinuous transmission [DTX]; Discontinuous reception [DRX]
• CPC Class Codes: H04W 76/30 : Connection release
• CPC Class Codes: H04W 8/08 : Mobility data transfer
• CPC Class Codes: H04W 80/10 : adapted for application session management, e.g. SIP [Session Initiation Protocol] connection management H04W76/00; arrangements for session management H04L67/14
• CPC Class Codes: H04W 84/042 : Public Land Mobile systems, e.g. cellular systems
• CPC Class Codes: H04W 84/12 : WLAN [Wireless Local Area Networks]
• CPC Class Codes: H04W 88/02 : Terminal devices
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: H04W 88/08 : Access point devices
• CPC Class Codes: H04W 88/12 : Access point controller devices
• CPC Class Codes: H04W 88/14 : Backbone network devices
• CPC Class Codes: H04W 88/16 : Gateway arrangements
• CPC Class Codes: H04W 88/18 : Service support devices; Network management devices
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

A 3GPP monitoring architecture framework provides monitoring event configuration, detection, and reporting for machine-type and other mobile data applications using a machine type communication interworking function (MTC-IWF) that communicates monitoring event configuration, detection, and reporting messages through existing interfaces, such as Tsp, T4, and T5 interfaces.

Claims

1. A user equipment (UE) for communication in a wireless network supporting machine-type communication (MTC) monitoring, the UE comprising:

a receiver configured to receive from a network entity terminating a T4 or T5 reference point, monitoring event data specified by a service capability server (SCS), a home subscriber service (HSS), or a home location register (HLR);

a processor configured to, in response to receiving the monitoring event data, configure the UE to monitor an event specified by the monitoring event data; and

a transmitter configured to transmit, to the network entity, a response to the monitoring event data, the response including delivery status information indicating whether the monitoring event data was successfully delivered to and configured on the UE.

2. The UE of claim 1, in which the network entity comprises an mobile switching center (MSC), a serving general packet radio service node (SGSN), or a mobility management entity (MME).

3. The UE of claim 1, in which the monitoring event data is included in a transferred device trigger.

4. The UE of claim 1, in which the monitoring event data is received in response to an MTC interworking function (MTC-IWF) sending a submit-request message over a T5 interface to a mobility management entity (MME), the submit-request message including the monitoring event data specified by the SCS.

5. The UE of claim 1, in which the monitoring event data is received in response to an MTC interworking function (MTC-IWF) sending a submit-trigger message over a T4 interface to a short message service—

service center (SMS-SC) that forwards the message to the network entity, the submit-trigger message including the monitoring event data specified by the SCS.

6. The UE of claim 1, in which the response includes information for an MTC interworking function (MTC-IWF) to deliver to the SCS in the form of a request-status or a monitoring-configuration-answer attribute value pair indicating the delivery status information.

7. The UE of claim 1, in which the monitoring event data is specified by the HSS in network subscription information associated with the UE.

8. The UE of claim 1, in which the monitoring event data includes information that specifies an action to be taken in response to an occurrence of the event specified by the monitoring event data.

9. The UE of claim 1, in which the monitoring event data includes information that specifies whether the event specified by the monitoring event data is to be monitored continuously or intermittently.

10. A method of configuring a machine-type communication (MTC) monitoring event using messages communicated by an MTC interworking function (MTC-IWF) over third-generation partnership project (3GPP) network system interfaces, the method comprising:

receiving from a services capability server (SCS) a diameter-protocol-based message including attribute value pairs (AVPs) defining monitoring event data including a request to establish, activate, deactivate, or trigger report delivery of a monitoring event on a 3GPP destination node;

sending to a home subscriber service (HSS) or home location register (HLR) over an S6m interface, a subscriber-information-request message requesting authorization for configuring the monitoring event on a 3GPP network element corresponding to the 3GPP destination node;

receiving from the HSS/HLR a subscriber-information-answer message authorizing the MTC-IWF to configure the monitoring event on the 3GPP network element corresponding to the 3GPP destination node; and

determining, based on the monitoring event data, the 3GPP network element that corresponds to the 3GPP destination node.

11. The method of claim 10, in which the diameter-protocol-based message comprises a monitoring-action-request message or a device-action-request message including an event identification AVP to identify the event to be monitored and an event action AVP to specify whether the event is to be monitored continuously or monitored at time intervals.

12. The method of claim 10, further comprising:

in response to receiving the diameter-protocol-based message, determining whether the SCS is authorized to send monitoring requests, whether the SCS has exceeded its quota of monitoring requests, and whether the SCS has exceeded its rate of submitting monitoring requests; and

in response to the determination, sending a monitoring-action-answer message or a device-action-answer message indicating a status of the request.

13. The method of claim 12, in which the monitoring-action-answer message includes information indicating a cause of an unsuccessful request.

14. The method of claim 10, further comprising:

sending to the 3GPP network element over a third interface, an indication to configure the monitoring event.

15. The method of claim 14, in which the third interface comprises a T5 interface, the method further comprising:

sending to the 3GPP network element over the T5 interface, the indication to configure the monitoring event.

16. The method of claim 14, in which the 3GPP network element comprises a mobility management entity (MME), in which the indication comprises a submit-request message including a destination-node AVP indicating the 3GPP destination node of the monitoring event data, and in which the step of sending the indication to configure the monitoring event further comprises:

initiating the MME to determine whether it corresponds to the 3GPP destination node of the monitoring event data.

17. The method of claim 16, further comprising:

initiating the MME to transfer to a UE a trigger message that provides the UE with information corresponding to the monitoring event data; and

receiving from the MME a delivery-report message indicating whether the trigger message was successfully delivered.

18. The method of claim 10, in which the 3GPP destination node comprises a serving general packet radio service node (SGSN) or a mobile switching center (MSC).

19. The method of claim 10, in which the 3GPP destination node comprises a packet data network gateway (P-GW) or an Enhanced Node B (eNB), the method further comprising:

sending to a mobility management entity (MME) a submit-request message including a destination-node AVP indicating the 3GPP destination node.

20. A node in a third generation partnership project (3GPP) network, the node comprising processing circuitry configured to:

receive machine-type communication (MTC) monitoring event data conveyed by an MTC interworking function (MTC-IWF) for a services capability server (SCS) and an application server (AS), the monitoring event data including information to configure the node for a monitoring event and to specify an action to be taken by the node in response to the monitoring event;

configure the node for reporting the monitoring event; and

generate a report of the monitoring event for the SCS.

21. The node of claim 20, in which the processing circuitry is further configured to:

detect an occurrence of the monitoring event; and

generate the report in response to detecting an occurrence of the monitoring event.

22. The node of claim 20, in which the node comprises a serving general packet radio service (SGSN), a mobility management entity (MME), a gateway general packet radio service support node (GGSN), or a packet data network gateway (P-GW).

23. The node of claim 20, in which the MTC-IWF comprises a default MTC-IWF defined in a monitoring subscription account of a user equipment (UE).

24. The node of claim 20, in which the MTC-IWF comprises a dynamically selectable MTC-IWF available in a 3GPP network visited by a user equipment (UE) configured to monitor the monitoring event.