MACHINE TYPE COMMUNICATION MONITORING FRAMEWORK FOR 3GPP SYSTEMS

• US 20200137613A1
• Filed: 12/30/2019
• Published: 04/30/2020
• Est. Priority Date: 09/28/2012
• Status: Active Grant

• Current Assignee: Muthaiah Venkatachalam, Puneet K. Jain, Varun N. Rao
• Original Assignee: Muthaiah Venkatachalam, Puneet K. Jain, Varun N. Rao
• Inventors: Jain, Puneet K., Rao, Varun N., Venkatachalam, Muthaiah
• Granted Patent: US 11,089,500 B2
• Time in Patent Office: Days
• 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 by configuring monitoring on a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node through existing interfaces, such as Tsp, T4, and T5 interfaces.

Claims

1. A method for a network element, the method comprising:

receiving a monitoring request message to configure a monitoring event on the network element comprising a mobility management entity (MME) or a serving general packet radio service support node (SGSN) for monitoring events associated with a user equipment (UE) configured to provide machine type communications (MTC) in a cellular network, the monitoring request message indicating a monitoring type and originates from a services capability server (SCS) or an application server (AS) configured to receive the MTC;

in response to the monitoring request message, enabling the monitoring event based on the monitoring type; and

providing a monitoring response message to acknowledge the monitoring request message.

2. The method of claim 1, wherein the monitoring request message indicates a recipient of a monitoring indication message to be provided by the network element.

3. The method of claim 1, wherein the monitoring request message includes a parameter to associate a monitoring event report to a specific monitoring request or an original source of the monitoring request message.

4. The method of claim 1, wherein the monitoring request message includes a parameter that indicates a status of the monitoring request message.

5. The method of claim 1, wherein the monitoring request message includes a parameter to deactivate event reporting or includes information indicating a condition for which monitoring expires.

6. The method of claim 1, wherein the monitoring request message includes a parameter that makes a monitoring request a continuous monitoring request or that indicates that a monitoring request should generate a single monitoring report.

7. The method of claim 1, further comprising:

detecting an occurrence of the monitoring event; and

generating a report in response to detecting the occurrence of the monitoring event.

8. The method of claim 1, wherein the monitoring request message comprises subscriber data provided by a home subscriber service (HSS), and wherein the method further comprises determining, based on an operator configuration, whether the network element can accept a monitoring request.

9. The of claim 1, further comprising deleting a monitoring configuration.

10. A method comprising:

receiving from a node in a cellular network a monitoring request for monitoring event configuration of a monitoring event associated with a user equipment (UE) configured to provide machine type communications (MTC) in the cellular network;

determining whether the monitoring request may be used for configuring the monitoring event on one or more of a mobility management entity (MME), a serving general packet radio service support node (SGSN), or a home subscriber service (HSS) node; and

sending to the node a monitoring response message to acknowledge acceptance or failure of the monitoring request.

11. The method of claim 10, further comprising:

determining whether the monitoring request would exceed a quota or rate of submitting monitoring requests; and

providing to the node a cause value indicating an error in response to determining the monitoring request has failed.

12. The method of claim 10, further comprising:

determining whether a services capability server (SCS) or application server (AS) are authorized to make the monitoring request; and

providing to the node a cause value indicating an error in response to determining the monitoring request has failed.

13. The method of claim 10, wherein the node is a services capability server (SCS), an application server (AS), or an MTC interworking function (MTC-IWF).

14. The method of claim 10, wherein the monitoring request comprises a first monitoring request message, and the method further comprises:

preparing a second monitoring request message based on the first monitoring request message; and

sending the second monitoring request message to the HSS.

15. The method of claim 10, wherein the monitoring request includes a parameter to associate a monitoring event report to a specific monitoring request or includes an identification to associate a corresponding monitoring report with the node.

16. The method of claim 10, wherein the monitoring request includes a parameter that indicates a time at which a related monitoring request is considered to expire.

17. The method of claim 10, wherein the monitoring request includes a parameter that indicates a maximum number of event reports to be generated by the node until an associated monitoring event is considered to expire.

18. The method of claim 10, wherein the monitoring request includes a parameter that makes a monitoring request a continuous monitoring request or that indicates that a monitoring request should generate a single monitoring report.

19. The method of claim 10, wherein the monitoring request includes a monitoring type, and wherein the method further comprises providing a message including the monitoring type to the MME/SGSN.

20. The method of claim 10, further comprising receiving the monitoring request from an MTC interworking function (MTC-IWF) through an S6m interface.