IP Library Granted Patent US 12,395,550
Granted Patent B2
US 12,395,550 · App. 18/513,974 · Granted Aug 19, 2025

Multi-access edge computing based visibility network

Inventors: Shubharanjan Dasgupta (Bangalore, IN); Mythil Raman (San Jose, CA); Prasanna Kumar Acharya (Bangalore, IN); Ram Gopal Singh (Bangalore, IN); Pranesh Kulkarni (Bangalore, IN)
Assignee: Extreme Networks, Inc.
H04L67/10H04L9/0643H04L41/0823H04L43/0888H04L45/745H04L47/24H04L47/32H04L47/36H04L61/5007H04L67/289H04L67/53H04L9/50
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 12,395,550
App. No.
18/513,974
Granted
Aug 19, 2025
Kind
B2
Abstract

Disclosed herein are system, method, and computer program product embodiments for providing traffic visibility in a network. An embodiment operates by a third-party component receiving a copy of a first data packet during a first period of time. The third-party component extracts a first network parameter associated with the first period of time from the copy of the first data packet. The third-party component then predicts a baseline of normalcy for the first network parameter during a second period of time after the first period of time based on data associated with a copy of a second data packet and the first network parameter. Thereafter, the third-party component receives a copy of a third data packet during the second period of time, and extracts a second network parameter from the copy of the third data packet. The third-party component then determines that the second network parameter of the copy of the second data packet is an anomaly based on the baseline of normalcy for the first network parameter.

Claims (42)

1. A method, comprising:

receiving, by a third-party component from a network component, a copy of a first data packet during a first period of time;

extracting, by the third-party component, a first network parameter associated with the first period of time from the copy of the first data packet;

predicting, by the third-party component, a baseline of normalcy for the first network parameter during a second period of time after the first period of time based on data associated with a copy of a second data packet and the first network parameter, the copy of the second data packet received during the second period of time;

receiving, by the third-party component from the network component, a copy of a third data packet during the second period of time, the copy of the third data packet being different from the copy of the second data packet;

extracting, by the third-party component, a second network parameter from the copy of the third data packet; and

determining, by the third-party component, that the second network parameter of the copy of the second data packet is an anomaly based on the baseline of normalcy for the first network parameter.

2. The method of claim 1 , wherein the first network parameter and the second network parameter are associated with one or more of a user device operation, a user device application usage, a user device location behavior, and a network-entity behavior pattern.

3. The method of claim 1 , further comprising:

deriving a network characteristic associated with the first period of time based on the copy of the first data packet and the copy of the second data packet.

4. The method of claim 3 , wherein the network characteristic includes an amount of throughput, a direction of flow, a bandwidth utilization, a latency, or a utilized network service.

5. The method of claim 1 , wherein the baseline of normalcy for the first network parameter is further based on a network provider input corresponding to a key performance indicator relating to the first network parameter.

6. The method of claim 1 , wherein the second period of time includes a first point in time and a second point in time, and a baseline of normalcy for the first point in time is different than a baseline of normalcy for the second point in time.

7. The method of claim 1 , further comprising:

updating the baseline of normalcy for the first network parameter based on the anomaly.

8. The method of claim 1 , wherein determining the second network parameter comprises determining that the second network parameter of the copy of the second data packet is the anomaly when determining that the anomaly exceeds the baseline of normalcy by a predetermined amount set by a network provider.

9. A system, comprising:

a memory; and

a processor coupled to the memory and configured to:

receive a copy of a first data packet during a first period of time;

extract a first network parameter associated with the first period of time from the copy of the first data packet;

predict a baseline of normalcy for the first network parameter during a second period of time after the first period of time based on data associated with a copy of a second data packet and the first network parameter, the copy of the second data packet received during the second period of time;

receive a copy of a third data packet during the second period of time, the copy of the third data packet being different from the copy of the second data packet;

extract a second network parameter from the copy of the third data packet; and

determine that the second network parameter of the copy of the second data packet is an anomaly based on the baseline of normalcy for the first network parameter.

10. The system of claim 9 , wherein the first network parameter and the second network parameter are associated with one or more of a user device operation, a user device application usage, a user device location behavior, and a network-entity behavior pattern.

11. The system of claim 9 , wherein the processor is further configured to derive a network characteristic associated with the first period of time based on the copy of the first data packet and the copy of the second data packet.

12. The system of claim 11 , wherein the network characteristic includes an amount of throughput, a direction of flow, a bandwidth utilization, a latency, or a utilized network service.

13. The system of claim 9 , wherein the baseline of normalcy for the first network parameter is further based on a network provider input corresponding to a key performance indicator relating to the first network parameter.

14. The system of claim 9 , wherein the second period of time includes a first point in time and a second point in time, and a baseline of normalcy for the first point in time is different than a baseline of normalcy for the second point in time.

15. The system of claim 9 , wherein the processor a third party component is further configured to update the baseline of normalcy for the first network parameter based on the anomaly.

16. A non-transitory computer-readable medium (CRM) having instructions stored thereon that, when executed by at least one computing device, cause the at least one computing device to perform operations comprising:

receiving, from a network component, a copy of a first data packet during a first period of time;

extracting a first network parameter associated with the first period of time from the copy of the first data packet;

predicting a baseline of normalcy for the first network parameter during a second period of time after the first period of time based on data associated with a copy of a second data packet and the first network parameter, the copy of the second data packet received during the second period of time;

receiving, from the network component, a copy of a third data packet during the second period of time, the copy of the third data packet being different from the copy of the second data packet;

extracting a second network parameter from the copy of the third data packet; and

determining that the second network parameter of the copy of the second data packet is an anomaly based on the baseline of normalcy for the first network parameter.

17. The non-transitory CRM of claim 16 , wherein the first network parameter and the second network parameter are associated with one or more of a user device operation, a user device application usage, a user device location behavior, and a network-entity behavior pattern.

18. The non-transitory CRM of claim 16 , wherein the operations further comprise deriving a network characteristic associated with the first period of time based on the copy of the first data packet and the copy of the second data packet.

19. The non-transitory CRM of claim 18 , wherein the network characteristic includes an amount of throughput, a direction of flow, a bandwidth utilization, a latency, or a utilized network service.

20. The non-transitory CRM of claim 16 , wherein the baseline of normalcy for the first network parameter is further based on a network provider input corresponding to a key performance indicator relating to the first network parameter.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 31, 2024
From: DASGUPTA, SHUBHARANJAN; KULKARNI, PRANESH; ACHARYA, PRASANNA KUMAR; SINGH, RAM GOPAL; RAMAN, MYTHIL
To: EXTREME NETWORKS, INC.
Reel/Frame 066308/0535 →
Continuity (3)
Continuation 16798210 · Feb 21, 2020
Provisional Application 62809231 · Feb 22, 2019
Related Publication 20240089173A1 · Mar 14, 2024
References Cited (37)
US 9930012B1 · Clemons, Jr. et al. · 2018 [cited by applicant]
US 11323324B2 · Dasgupta et al. · 2022 [cited by applicant]
US 11870649B2 · Dasgupta et al. · 2024 [cited by applicant]
US 20060008063A1 · Harnesk et al. · 2006 [cited by applicant]
US 20060064619A1 · Wen et al. · 2006 [cited by applicant]
US 20080043976A1 · Maximo et al. · 2008 [cited by applicant]
US 20090135794A1 · Su et al. · 2009 [cited by applicant]
US 20100130170A1 · Liu et al. · 2010 [cited by applicant]
US 20130003607A1 · Kini et al. · 2013 [cited by applicant]
US 20130250799A1 · Ishii · 2013 [cited by applicant]
US 20140192776A1 · Lee et al. · 2014 [cited by applicant]
US 20150071292A1 · Tripathi et al. · 2015 [cited by applicant]
US 20150120871A1 · Li · 2015 [cited by applicant]
US 20150244842A1 · Laufer et al. · 2015 [cited by applicant]
US 20150245277A1 · Hassan et al. · 2015 [cited by applicant]
US 20150257159A1 · Speicher et al. · 2015 [cited by applicant]
US 20150358434A1 · Parthasarathy et al. · 2015 [cited by applicant]
US 20160020993A1 · Wu · 2016 [cited by examiner]
US 20160294606A1 · Puri · 2016 [cited by examiner]
US 20160294776A1 · Sun et al. · 2016 [cited by applicant]
US 20170132615A1 · Castinado et al. · 2017 [cited by applicant]
US 20170140408A1 · Wuehler · 2017 [cited by applicant]
US 20170142021A1 · Chen et al. · 2017 [cited by applicant]
US 20170163685A1 · Schwartz et al. · 2017 [cited by applicant]
US 20180053401A1 · Martin · 2018 [cited by examiner]
US 20180152385A1 · Xu et al. · 2018 [cited by applicant]
US 20190043050A1 · Smith et al. · 2019 [cited by applicant]
US 20200065212A1 · Chanda · 2020 [cited by examiner]
US 20200090208A1 · Reichenbach et al. · 2020 [cited by applicant]
US 20200272493A1 · Lecuyer et al. · 2020 [cited by applicant]
US 20200274765A1 · Dasgupta et al. · 2020 [cited by applicant]
US 20210221247A1 · Daniel et al. · 2021 [cited by applicant]
US 20210342836A1 · Cella et al. · 2021 [cited by applicant]
US 20210400595A1 · Sutskover et al. · 2021 [cited by applicant]
US 20220263716A1 · Dasgupta et al. · 2022 [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority directed to related International Patent Application No. PCT/US2020/019318, mailed Jun. 12, 2020; 14 pages. [cited by applicant]
International Search Report and Written Opinion of the International Searching Authority directed to related International Patent Application No. PCT/US2020/019315, mailed Jun. 17, 2020, 11 pages. [cited by applicant]