IP Library › Granted Patent US 12,010,553
Granted Patent B2
US 12,010,553 · App. 17/491,795 · Granted Jun 11, 2024

Cloud-based 5G security network architectures with intelligent steering

Inventors: Nathan Howe (Frankfurt, DE); Kenneth B. Urquhart (Rancho Mirage, CA)
Assignee: Zscaler, Inc.
H04W28/0925H04L63/0227H04L63/029H04L63/1425H04W28/12
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,010,553
App. No.
17/491,795
Filed
Oct 1, 2021
Granted
Jun 11, 2024
Kind
B2
Art Unit
2467
USPC
709/224
Abstract

Cloud-based 5G security, implemented in a Multi-Access Edge Compute (MEC) system, includes steps of receiving a request for a workload from User Equipment (UE); determining a type of traffic for the workflow and querying a machine learning engine based on the traffic type; informing the UE of how the workflow should be accessed; and receiving an updated request for the workflow and steering the traffic based on how the workflow should be steered. The steps can include receiving policy updates from a cloud-based system, related to how workloads should be steered.

Claims (39)

1. A method of cloud-based 5G security, implemented in a Multi-Access Edge Compute (MEC) system, comprising:

receiving a request for a workload from User Equipment (UE);

determining a type of traffic for the workflow and querying a machine learning engine based on the traffic type;

informing the UE of how the workflow should be accessed; and

receiving an updated request for the workflow and steering the traffic based on how the workflow should be steered.

2. The method of claim 1 , further comprising

receiving policy updates from a cloud-based system, related to how workloads should be steered.

3. The method of claim 1 , further comprising

receiving updates for the machine learning engine based on monitoring in a cloud-based system.

4. The method of claim 1 , wherein the MEC is a first MEC in a Radio Access Network (RAN).

5. The method of claim 1 , wherein the traffic is encrypted and the steering includes decrypting the traffic for inspection at another MEC closer to a destination.

6. The method of claim 1 , wherein the method is implemented in a decision front end that is processed in the MEC and that is part of a cloud-based system including nodes external to the MEC.

7. The method of claim 1 , wherein the steering includes decisions about how and where to send traffic based on a topology of data paths through the MEC and other edge compute resources.

8. A Multi-Access Edge Compute (MEC) system comprising:

one or more servers each including at least one processor and memory storing instructions that, when executed, cause the at least one processor to

receive a request for a workload from User Equipment (UE),

determine a type of traffic for the workflow and querying a machine learning engine based on the traffic type,

inform the UE of how the workflow should be accessed, and

receive an updated request for the workflow and steer the traffic based on how the workflow should be steered.

9. The MEC system of claim 8 , wherein the instructions, when executed, cause the at least one processor to

receive policy updates from a cloud-based system, related to how workloads should be steered.

10. The MEC system of claim 8 , wherein the instructions, when executed, cause the at least one processor to

receive updates for the machine learning engine based on monitoring in a cloud-based system.

11. The MEC system of claim 8 , wherein the MEC is a first MEC in a Radio Access Network (RAN).

12. The MEC system of claim 8 , wherein the traffic is encrypted and the steering includes decrypting the traffic for inspection at another MEC closer to a destination.

13. The MEC system of claim 8 , wherein the steering includes decisions about how and where to send traffic based on a topology of data paths through the MEC and other edge compute resources.

14. A non-transitory computer-readable storage medium having computer-readable code stored thereon for programming a Multi-Access Edge Compute (MEC) system to perform steps of:

receiving a request for a workload from User Equipment (UE);

determining a type of traffic for the workflow and querying a machine learning engine based on the traffic type;

informing the UE of how the workflow should be accessed; and

receiving an updated request for the workflow and steering the traffic based on how the workflow should be steered.

15. The non-transitory computer-readable storage medium of claim 14 , wherein the steps further include

receiving policy updates from a cloud-based system, related to how workloads should be steered.

16. The non-transitory computer-readable storage medium of claim 14 , wherein the steps further include

receiving updates for the machine learning engine based on monitoring in a cloud-based system.

17. The non-transitory computer-readable storage medium of claim 14 , wherein the MEC is a first MEC in a Radio Access Network (RAN).

18. The non-transitory computer-readable storage medium of claim 14 , wherein the traffic is encrypted and the steering includes decrypting the traffic for inspection at another MEC closer to a destination.

19. The non-transitory computer-readable storage medium of claim 14 , wherein the method is implemented in a decision front end that is processed in the MEC and that is part of a cloud-based system including nodes external to the MEC.

20. The non-transitory computer-readable storage medium of claim 14 , wherein the steering includes decisions about how and where to send traffic based on a topology of data paths through the MEC and other edge compute resources.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2021
From: HOWE, NATHAN; URQUHART, KENNETH B.
To: ZSCALER, INC.
Reel/Frame 057668/0114 →
Continuity (3)
Continuation In Part 17371408 · Jul 9, 2021
Continuation In Part 17194568 · Mar 8, 2021
Related Publication 20220286911A1 · Sep 8, 2022
Cited By (1)
US 12,706,957