# US 2026/0095768 A1 · Multi-operator core sase for 5g sase

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

- Number: US 2026/0095768 A1
- Document ID: US20260095768A1
- Status: Published application
- Kind: A1
- Application number: 19/217,567
- Filed: 2025-05-23
- Published: 2026-04-02
- Earliest claimed: 2024-04-15
- Applicants: Palo Alto Networks, Inc.
- Inventors: Yogesh Vijay Ranade; Anand Oswal
- Web page: https://patentgrep.com/patent/US20260095768A1

## CPC

- H04L 63/0227: {Filtering policies (mail message filtering H04L51/212)}
- H04W 12/088: using filters or firewalls
- H04L 63/0236: {Filtering by address, protocol, port number or service, e.g. IP-address or URL}
- H04L 63/0263: {Rule management}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/145: {the attack involving the propagation of malware through the network, e.g. viruses, trojans or worms}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04W 12/037: of the control plane, e.g. signalling traffic
- H04W 12/069: using certificates or pre-shared keys
- H04W 12/102: Route integrity, e.g. using trusted paths
- H04W 12/121: Wireless intrusion detection systems [WIDS]; Wireless intrusion prevention systems [WIPS]
- H04W 12/122: Counter-measures against attacks; Protection against rogue devices
- H04W 12/37: Managing security policies for mobile devices or for controlling mobile applications
- H04W 12/72: Subscriber identity
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

Techniques for providing multi-operator core SASE solutions (e.g., for 5G SASE) are disclosed. In some embodiments, a system, a process, and/or a computer program product for providing multi-operator core SASE solutions for 5G SASE includes receiving mobile network traffic, at a Secure Access Service Edge (SASE) cloud network, via a service provider interconnect between a plurality of mobile service provider networks and the SASE cloud network; monitoring the mobile network traffic at the SASE cloud network from the plurality of mobile service provider networks for a tenant of the SASE cloud network provider; enforcing a security policy based on one or more parameters associated with the mobile network traffic, wherein the security policy is associated with the tenant of the SASE cloud network provider; and forwarding the secured data plane traffic from the SASE cloud network to its original destination if allowed by the security policy, and block or drop the data plane traffic from the SASE cloud network if not allowed by the security policy.

## Claims

### Claim 1

A system, comprising:
a processor configured to:
receive mobile network traffic, at a Secure Access Service Edge (SASE) cloud network, via a service provider interconnect between a plurality of mobile service provider networks and the SASE cloud network;
monitor the mobile network traffic at the SASE cloud network from the plurality of mobile service provider networks for a tenant of a SASE cloud network provider;
enforce a security policy based on one or more parameters associated with the mobile network traffic, wherein the security policy is associated with the tenant of the SASE cloud network provider; and
forward secured data plane traffic from the SASE cloud network to its original destination if allowed by the security policy, and block or drop the secured data plane traffic from the SASE cloud network if not allowed by the security policy; and
a memory coupled to the processor and configured to provide the processor with instructions.

### Claim 2 (depends on 1)

The system recited in claim 1, wherein the service provider interconnect between the plurality of mobile service provider networks and the SASE cloud network is provided using a roaming network provider.

### Claim 3 (depends on 1)

The system recited in claim 1, wherein the SASE cloud network includes a firewall as a service (FWaaS) that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity and an application identifier, and wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI).

### Claim 4 (depends on 1)

The system recited in claim 1, wherein the SASE cloud network includes a firewall as a service (FWaaS) that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity, a unique device identifier, and an application identifier, wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI) and/or Mobile Station International Subscriber Directory Number (MSISDN), and wherein the unique device identifier includes an International Mobile Equipment Identifier (IMEI).

### Claim 5 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein the security policy is enforced on the data plane traffic associated with a UE based on contextual information associated with the UE to provide secured data plane traffic using the security policy configured per user group and/or per user associated with the tenant of the SASE cloud network provider.

### Claim 6 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein the plurality of mobile service provider networks includes a 4G mobile core network, a 5G mobile core network, and/or 6G mobile core network, and wherein the data plane traffic from the plurality of mobile service provider networks is secured from and to 4G, 5G, and/or 6G UE devices.

### Claim 7 (depends on 1)

The system recited in claim 1, wherein Internet access is secured from and to 4G, 5G, and/or 6G UE devices, and wherein enterprise data center access is secured from and to 4G, 5G, and/or 6G UE devices.

### Claim 8 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein selection and the enforcement of the security policy is based on contextual information associated with a UE and the data plane traffic is correlated with the UE based on a UE Internet Protocol (IP) address.

### Claim 9 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein a firewall as a service (FWaaS) associated with the SASE cloud network is configured to perform Uniform Resource Link (URL) filtering for the data plane traffic.

### Claim 10 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein a firewall as a service (FWaaS) associated with the SASE cloud network is configured to perform application Denial of Service (DoS) detection for the data plane traffic.

### Claim 11 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein a firewall as a service (FWaaS) associated with the SASE cloud network is configured to perform application Denial of Service (DoS) prevention for the data plane traffic.

### Claim 12 (depends on 1)

The system recited in claim 1, wherein each of a plurality of security policies is distinctly selected and enforced for each mobile service provider (MSP) enterprise tenant at the SASE cloud network, wherein per tenant security policy configuration and enforcement are provided by the SASE cloud network.

### Claim 13 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein the data plane traffic is encapsulated with meta information, including a subscriber identity and/or a unique device identifier.

### Claim 14 (depends on 1)

The system recited in claim 1, wherein the mobile network traffic includes data plane traffic, and wherein the processor is further configured to:
determine the security policy to apply at the SASE cloud network to the data plane traffic based on a subscriber identity and/or a unique device identifier.

### Claim 15

A method, comprising:
receiving mobile network traffic, at a Secure Access Service Edge (SASE) cloud network, via a service provider interconnect between a plurality of mobile service provider networks and the SASE cloud network;
monitoring the mobile network traffic at the SASE cloud network from the plurality of mobile service provider networks for a tenant of a SASE cloud network provider;
enforcing a security policy based on one or more parameters associated with the mobile network traffic, wherein the security policy is associated with the tenant of the SASE cloud network provider; and
forwarding secured data plane traffic from the SASE cloud network to its original destination if allowed by the security policy, and block or drop the secured data plane traffic from the SASE cloud network if not allowed by the security policy.

### Claim 16 (depends on 15)

The method of claim 15, wherein the SASE cloud network includes a firewall as a service that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity and an application identifier, and wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI).

### Claim 17 (depends on 15)

The method of claim 15, wherein the SASE cloud network includes a firewall as a service (FWaaS) that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity, a unique device identifier, and an application identifier, wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI) and/or Mobile Station International Subscriber Directory Number (MSISDN), and wherein the unique device identifier includes an International Mobile Equipment Identifier (IMEI).

### Claim 18

A computer program product, the computer program product being embodied in a tangible computer readable storage medium and comprising computer instructions for:
receiving mobile network traffic, at a Secure Access Service Edge (SASE) cloud network, via a service provider interconnect between a plurality of mobile service provider networks and the SASE cloud network;
monitoring the mobile network traffic at the SASE cloud network from the plurality of mobile service provider networks for a tenant of a SASE cloud network provider;
enforcing a security policy based on one or more parameters associated with the mobile network traffic, wherein the security policy is associated with the tenant of the SASE cloud network provider; and
forwarding secured data plane traffic from the SASE cloud network to its original destination if allowed by the security policy, and block or drop the secured data plane traffic from the SASE cloud network if not allowed by the security policy.

### Claim 19 (depends on 18)

The computer program product recited in claim 18, wherein the SASE cloud network includes a firewall as a service that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity and an application identifier, and wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI).

### Claim 20 (depends on 18)

The computer program product recited in claim 18, wherein the SASE cloud network includes a firewall as a service that is configured with distinct security policies for each of a plurality of tenants of the SASE cloud network provider, and wherein the security policy is selected based on a subscriber identity, a unique device identifier, and an application identifier, wherein the subscriber identity includes an International Mobile Subscriber Identity (IMSI) and/or Mobile Station International Subscriber Directory Number (MSISDN), and wherein the unique device identifier includes an International Mobile Equipment Identifier (IMEI).

### Claim 21

A system, comprising:
a processor configured to:
receive, at an SD-WAN device, Wi-Fi traffic for an enterprise network;
route the Wi-Fi traffic to one or more of a plurality of mobile service provider networks based on an enterprise SD-WAN policy;
receive, at a Secure Access Service Edge (SASE) cloud network, mobile network traffic from the plurality of mobile service provider networks via a service provider interconnect;
monitor the mobile network traffic, at the SASE cloud network from the plurality of mobile service provider networks, for a tenant of a SASE cloud network provider;
enforce a security policy based on one or more parameters associated with the mobile network traffic, wherein the security policy is associated with the tenant of the SASE cloud network provider, and wherein the enterprise network is associated with the tenant of the SASE cloud network provider; and
forward secured data plane traffic from the SASE cloud network to its original destination if allowed by the security policy, and block or drop the secured data plane traffic from the SASE cloud network if not allowed by the security policy; and
a memory coupled to the processor and configured to provide the processor with instructions.
