# US 2015/0189491 A1 · Network monitoring of user equipment events

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2015/0189491 A1
- Document ID: US20150189491A1
- Status: Published application
- Kind: A1
- Application number: 14/656,013
- Filed: 2015-03-12
- Published: 2015-07-02
- Earliest claimed: 2012-11-09
- Assignees: Alcatel Lucent
- Applicants: Alcatel Lucent
- Inventors: Deborah L. Barclay; Bruno Landais; Laurent Thiebaut
- Web page: https://patentgrep.com/patent/US20150189491A1

## CPC

- G06F 9/4881: {Scheduling strategies for dispatcher, e.g. round robin, multi-level priority queues}
- H04W 4/70: Services for machine-to-machine communication [M2M] or machine type communication [MTC]
- H04W 8/04: Registration at HLR or HSS [Home Subscriber Server]
- H04W 16/18: Network planning tools
- H04W 24/00: Supervisory, monitoring or testing arrangements
- H04W 24/08: Testing, {supervising or monitoring} using real traffic
- Y02D 30/70: in wireless communication networks
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- Y02D: CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE

## Abstract

Embodiments of the claimed subject matter provide a method for supporting network monitoring of user equipment events. Some embodiments of the method include receiving, at a home subscriber server (HSS) in a public land mobile network (PLMN), a request to monitor one or more events associated with one or more users. The request is used to configure, activate, or deactivate delivery of reports from one or more entities in the PLMN to a monitor collection entity in response to the event(s). Some embodiments of the method also include configuring one or more profiles in the HSS associated with the user(s) based on the request and providing the request to monitor the event(s) associated with the user(s) to one or more serving nodes for user equipment associated with the user(s).

## Claims

### Claim at position 1

1-29. (canceled)

### Claim 30

A home subscriber server (HSS) for deployment in a public land mobile network (PLMN), the HSS comprising:
a memory; and
a computer system configured to:
receive a request to monitor at least one event associated with at least one user, wherein the request includes information for controlling delivery of reports from at least one entity in the PLMN to a monitor collection entity in response to said at least one event, wherein the request indicates at least one action to be taken by said at least one entity in response to said at least one event;
configure at least one profile associated with said at least one user based on the request, wherein the at least one profile is stored in the memory; and
provide the request to monitor said at least one event associated with said at least one user to at least one serving node associated with said at least one user.

### Claim 31 (depends on 30)

The HSS of claim 30, wherein the request to monitor said at least one event associated with said at least one user is received from an element management system (EMS) within the PLMN.

### Claim 32 (depends on 30)

The HSS of claim 30, wherein the request to monitor said at least one event associated with said at least one user is from an external entity and validated by an interworking function that supports and controls an interface between the PLMN and non PLMN entities.

### Claim 33 (depends on 30)

The HSS of claim 30, wherein the computer system is configured to provide monitoring information indicative of said at least one event associated with said at least one user to said at least one entity in the PLMN or at least one entity in another network.

### Claim 34 (depends on 30)

The HSS of claim 30, wherein said at least one user is associated with user equipment that supports at least one machine type communication (MTC) application, and wherein the computer system is configured to receive a request to monitor at least one event associated with the at least one MTC application.

### Claim 35 (depends on 34)

The HSS of claim 34, wherein the computer system is configured to receive a request to monitor an event indicating at least one of behavior that is not aligned with an activated MTC feature associated with the at least one MTC application, a change in an association between the user equipment and a smart card, loss of connectivity, a communication failure, a change in geographical position of the user equipment, or a change in a point of attachment of the user equipment.

### Claim 36

An apparatus, comprising:
a computer system configured to:
receive, from a home subscriber server (HSS), a request to monitor at least one event associated with at least one user, wherein the request indicates at least one action to be taken by the apparatus in response to said at least one event; and
configure, based on the request, delivery of reports from the apparatus to a monitor collection entity in response to said at least one event.

### Claim 37 (depends on 36)

The apparatus of claim 36, wherein the computer system is configured to activate or deactivate delivery of the reports from the apparatus based on information provided to the apparatus by the HSS.

### Claim 38 (depends on 36)

The apparatus of claim 36, wherein said at least one user is associated with user equipment that supports at least one machine type communication (MTC) application, and wherein the computer system is configured to receive a request to monitor at least one event associated with the at least one MTC application.

### Claim 39 (depends on 38)

The apparatus of claim 38, wherein the computer system is configured to receive a request to monitor an event indicating at least one of a behavior that is not aligned with an activated MTC feature associated with the at least one MTC application, a change in an association between the user equipment and a smart card, loss of connectivity, a communication failure, a change in geographical position of the user equipment, or a change in a point of attachment of the user equipment.

### Claim 40 (depends on 36)

The apparatus of claim 36, wherein the computer system is configured to provide a report to the monitor collection entity in response to detecting said at least one event associated with the said at least one user.

### Claim 41 (depends on 36)

The apparatus of claim 36, wherein the computer system is configured to take the at least one action in response to detecting said at least one event associated with user equipment.

### Claim 42 (depends on 36)

The apparatus of claim 36, wherein the computer system is configured to forward a request to monitor said at least one event to at least one network entity in a public land mobile network (PLMN) that serves user equipment associated with at least one user.

### Claim 43

A node for deployment in a public land mobile network (PLMN) that serves user equipment associated with at least one user, comprising:
a computer system configured to:
receive, from a home subscriber server (HSS), a request to monitor one or more events associated with at least one subscription associated with said at least one user, wherein the request indicates at least one action to be taken by at least one of the node or at least one other node in response to said at least one event; and
propagate the request toward said at least one other node participating in PLMN service delivery to said at least one user for monitoring said one or more events of said at least one event associated with said at least one subscription on the basis of the request received from the node.

### Claim 44 (depends on 43)

The node of claim 43, wherein the computer system is configured to propagate the request towards at least one of a radio access network, a serving gateway, a packet data node gateway, or a gateway general packet radio service (GPRS) support node (GGSN).

### Claim 45 (depends on 43)

The node of claim 43, wherein the request comprises an address indicating a monitor collection entity that can be used to configure delivery of reports to the monitor collection entity in response to said at least one event.

### Claim 46 (depends on 43)

The node of claim 43, wherein the computer system is configured to provide a report to the monitor collection entity in response to detecting said at least one event associated with said at least one subscription.

### Claim 47 (depends on 43)

The node of claim 43, wherein the computer system is configured to take said at least one action in response to at least one of the node or said at least one other node detecting a first event of said at least one event associated with said at least one subscription.

### Claim 48 (depends on 43)

The node of claim 43, wherein said at least one user is associated with user equipment that supports at least one machine type communication (MTC) application, and wherein the computer system is configured to receive a request to monitor at least one event associated with the at least one MTC application.

### Claim 49 (depends on 48)

The node of claim 48, wherein the computer system is configured to receive a request to monitor an event indicating at least one of behavior that is not aligned with an activated MTC feature associated with the at least one MTC application, a change in an association between the user equipment and a smart card, loss of connectivity, a communication failure, a change in geographical position of the user equipment, or a change in a point of attachment of the user equipment.
