IP Library › Granted Patent US 10,158,524
Granted Patent B2
US 10,158,524 · App. 15/429,644 · Granted Dec 18, 2018

System and method for enhanced network event monitoring and reporting

Inventors: James Mathison (Warren, NJ); Ye Huang (San Ramon, CA); Sudhakar Reddy Patil (Flower Mound, TX)
Assignee: Verizon Patent and Licensing Inc.
H04L41/0686H04L41/0631H04L43/065H04L43/0811H04W4/14H04W60/00
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,158,524
App. No.
15/429,644
Granted
Dec 18, 2018
Kind
B2
Abstract

A device may detect an event associated with a user device. The event may include at least one of a data reachability event, a loss of connectivity event, or a loss of reachability event. The device may determine, based on detecting the event, event information associated with the event. The event information may include information that identifies a type of a packet data network (PDN) connection when the event includes a data reachability event. The event information may include information that identifies a reason for detachment from a network when the event includes a loss of connectivity event. The event information may include information indicating that one or more PDN connections have been closed when the event includes a loss of reachability event. The device may provide the event information for reporting to one or more devices that are to receive event reports associated with the user device.

Claims (98)

1. A device, comprising:

a memory; and

one or more processors to:

detect an event associated with a user device,

the event including

a loss of reachability event;

determine, based on detecting the event, event information associated with the event,

the event information including information indicating that one or more packet data network (PDN) connections are closed and that one or more other PDN connections remain open, while the one or more PDN connections are closed, when the event includes the loss of reachability event; and

provide the event information for reporting to one or more devices that are to receive event reports associated with the user device,

the event information causing, when the event information includes the information indicating that the one or more PDN connections are closed and that the one or more other PDN connections remain open, while the one or more PDN connections are closed, the one or more devices to determine whether the user device remains reachable.

2. The device of claim 1 ,

where the one or more processors, when detecting the event associated with the user device are to:

detect a loss of connectivity event; and

where the one or more processors, when determining the event information, are to:

determine event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event,

where the event information that identifies the reason for detachment from the network includes a cause code.

3. The device of claim 1 , where the one or more processors, when providing the event information, are to:

provide the event information to a service capability exposure function device.

4. The device of claim 1 , where the one or more processors, when detecting the event associated with the user device, are to:

detect a loss of connectivity event; and

the one or more processors, when determining the event information, are to:

determine event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event.

5. The device of claim 4 , where the one or more processors, when providing the event information for reporting detecting the loss of connectivity event, are to:

provide event information preventing the one or more devices from attempting to communicate with the user device.

6. The device of claim 1 , where the one or more processors, when detecting the event associated with the user device, are to:

detect a data reachability event;

the one or more processors, when determining the event information, are to:

determine event information that identifies a type of a PDN connection and an access point name (APN) associated with the PDN connection when the event includes the data reachability event; and

the one or more processors, when providing the event information, are to:

cause the one or more devices to communicate with the user device based on the type of the PDN connection.

7. The device of claim 6 , where the information that identifies the type of the PDN connection includes information that identifies the PDN connection as an Internet protocol (IP) PDN connection or a non-IP PDN connection, and

where the event information further includes an IP address, associated with the user device, when the information identifies the PDN connection as an IP PDN connection.

8. A non-transitory computer-readable medium storing instructions, the instructions comprising:

one or more instructions that, when executed by one or more processors, cause the one or more processors to:

detect an event associated with a user device,

the event including a loss of reachability event;

determine, based on detecting the event, event information associated with the event,

the event information including information indicating that one or more packet data network (PDN) connections are closed and that one or more other PDN connections remain open, while the one or more PDN connections are closed, when the event includes the loss of reachability event; and

provide the event information for reporting to one or more devices that are to receive event reports associated with the user device,

the event information causing, when the event information includes the information indicating that the one or more PDN connections are closed and that the one or more other PDN connections remain open, while the one or more PDN connections are closed, the one or more devices to determine whether the user device remains reachable.

9. The non-transitory computer-readable medium of claim 8 ,

where the one or more instructions, that cause the one or more processors to detect the event associated with the user device, cause the one or more processors to:

detect a loss of connectivity event; and

where the one or more instructions, that cause the one or more processors to determine the event information, cause the one or more processors to:

determine event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event,

where the event information that identifies the reason for detachment from the network includes a cause code.

10. The non-transitory computer-readable medium of claim 8 , where the one or more instructions, that cause the one or more processors to provide the event information, cause the one or more processors to:

provide the event information to a service capability exposure function device.

11. The non-transitory computer-readable medium of claim 8 ,

where the one or more instructions, that cause the one or more processors to detect the event associated with the user device, cause the one or more processors to:

detect a loss of connectivity event; and

where the one or more instructions, that cause the one or more processors to determine the event information, cause the one or more processors to:

determine event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event.

12. The non-transitory computer-readable medium of claim 11 , where the event information that identifies the reason for detachment includes at least one of:

a tracking area update (TAU) failure,

an expiration of an idle time,

an expected detachment,

a requested detachment, or

a scheduled detachment.

13. The non-transitory computer-readable medium of claim 8 ,

where the one or more instructions, that cause the one or more processors to detect the event associated with the user device, cause the one or more processors to:

detect a data reachability event;

where the one or more instructions, that cause the one or more processors to determine the event information, cause the one or more processors to:

determine event information that identifies a type of a PDN connection and an access point name (APN) associated with the PDN connection when the event includes the data reachability event; and

where the one or more instructions, that cause the one or more processors to provide the event information, cause the one or more processors to:

cause the one or more devices to communicate with the user device based on the type of the PDN connection.

14. The non-transitory computer-readable medium of claim 13 , where the information that identifies the type of the PDN connection includes information that identifies the PDN connection as an Internet protocol (IP) PDN connection or a non-IP PDN connection, and

where the event information further includes an IP address, associated with the user device, when the information identifies the PDN connection as an IP PDN connection.

15. A method, comprising:

detecting, by a device, an event associated with a user device,

the event including a loss of reachability event;

determining, by the device and based on detecting the event, event information associated with the event,

the event information including information indicating that one or more packet data network (PDN) connections are closed and that one or more other PDN connections remain open, while the one or more PDN connections are closed, when the event includes the loss of reachability event; and

providing, by the device, the event information for reporting to one or more devices that are to receive event reports associated with the user device.

16. The method of claim 15 ,

where detecting the event associated with the user device comprises:

detecting a loss of connectivity event; and

where determining the event information comprises:

determining event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event,

where the event information that identifies the reason for detachment from the network includes a cause code.

17. The method of claim 15 ,

where detecting the event associated with the user device comprises:

detecting a loss of connectivity event; and

where determining the event information comprises:

determining event information that identifies a reason for detachment from a network when the event includes the loss of connectivity event.

18. The method of claim 17 , where the event information that identifies the reason for detachment includes at least one of:

a tracking area update (TAU) failure,

an expiration of an idle time,

an expected detachment,

a requested detachment, or

a scheduled detachment.

19. The method of claim 15 ,

where detecting the event associated with the user device comprises:

detecting a data reachability event; and

where determining the event information comprises:

determining event information that identifies a type of a PDN connection and an access point name (APN) associated with the PDN connection when the event includes the data reachability event.

20. The method of claim 19 , where the information that identifies the type of the PDN connection includes information that identifies the PDN connection as an Internet protocol (IP) PDN connection or a non-IP PDN connection, and

where the event information further includes an IP address, associated with the user device, when the information identifies the PDN connection as an IP PDN connection.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 10, 2017
From: MATHISON, JAMES; HUANG, YE; PATIL, SUDHAKAR REDDY
To: VERIZON PATENT AND LICENSING INC.
Reel/Frame 041225/0753 →
Continuity (1)
Related Publication 20180234291A1 · Aug 16, 2018