Abstract: Methods and system for providing network connectivity are disclosed. In an example, a method for providing network connectivity involves receiving from an Internet Service Provider (ISP) Internet Protocol (IP) address pool-to-tier mappings, generating an IP address-to-tier mapping at a Secure Access Service Edge (SASE) domain from the IP address pool-to-tier mappings, and forwarding traffic received at the SASE domain from a Broadband Network Gateway (BNG) of the ISP according to the IP address-to-tier mapping, wherein the traffic is received at the SASE domain from the BNG of the ISP only after access to the ISP is granted using an access ID.

Abstract: Methods and system for providing network connectivity are disclosed. In an example, a method for providing network connectivity involves receiving from an Internet Service Provider (ISP) an access ID and an IP address at a SASE domain, wherein the access ID and the IP address correspond to a subscriber of the ISP, generating an IP address-to-tenant mapping at the SASE domain by applying the access ID and the IP address to an access ID-to-tenant mapping, and forwarding traffic received at the SASE domain from a Broadband Network Gateway (BNG) of the ISP according to the IP address-to-tenant mapping.

Abstract: Methods and systems for providing network connectivity are disclosed. In an embodiment, a method for providing network connectivity involves receiving from a Mobile Network Operator (MNO) an access ID, an IP address, and an Access Point Name (APN) at a SASE domain, wherein the access ID, the IP address, and the APN correspond to a wireless device, updating IP address-to-tenant mappings at the SASE domain in response to the access ID, the IP address, and the APN, and forwarding traffic received at the SASE domain from the wireless device via the MNO according to the updated IP address-to-tenant mappings.

Abstract: Methods and system for providing network connectivity are disclosed. In an example, a method for providing network connectivity involves receiving from an Internet Service Provider (ISP) an access ID and an IP address at a SASE domain, wherein the access ID and the IP address correspond to a subscriber of the ISP, generating an IP address-to-tenant mapping at the SASE domain by applying the access ID and the IP address to an access ID-to-tenant mapping, and forwarding traffic received at the SASE domain from a Broadband Network Gateway (BNG) of the ISP according to the IP address-to-tenant mapping.

Abstract: Methods and system for providing network connectivity are disclosed. In an example, a method for providing network connectivity involves receiving from an Internet Service Provider (ISP) Internet Protocol (IP) address pool-to-tier mappings, generating an IP address-to-tier mapping at a Secure Access Service Edge (SASE) domain from the IP address pool-to-tier mappings, and forwarding traffic received at the SASE domain from a Broadband Network Gateway (BNG) of the ISP according to the IP address-to-tier mapping, wherein the traffic is received at the SASE domain from the BNG of the ISP only after access to the ISP is granted using an access ID.

Abstract: Methods and system for providing network connectivity are disclosed. In an embodiment, a method for providing network connectivity involves receiving from a Mobile Network Operator (MNO) an access ID and an IP address at a SASE domain, wherein the access ID and the IP address correspond to a wireless device, generating an IP address-to-tenant mapping at the SASE domain by applying the access ID and the IP address to an access ID-to-tenant mapping, and forwarding traffic received at the SASE domain from the wireless device via the MNO according to the IP address-to-tenant mapping.

Abstract: Method and systems for transitioning a wireless device between client-less connectivity and client-based connectivity are disclosed. In an embodiment, a method for transitioning a wireless device between client-less connectivity and client-based connectivity involves forwarding traffic from a wireless device through a SASE domain, receiving a request for information related to a SASE gateway in the SASE domain from the wireless device, transmitting information related to the SASE gateway from the SASE domain to the wireless device in response to the request, and transitioning the wireless device between client-less connectivity to the SASE gateway and client-based connectivity to the SASE gateway.

Abstract: Method and systems for transitioning a wireless device between client-less connectivity and client-based connectivity are disclosed. In an embodiment, a method for transitioning a wireless device between client-less connectivity and client-based connectivity involves forwarding traffic from a wireless device through a SASE domain, receiving a request for information related to a SASE gateway in the SASE domain from the wireless device, transmitting information related to the SASE gateway from the SASE domain to the wireless device in response to the request, and transitioning the wireless device between client-less connectivity to the SASE gateway and client-based connectivity to the SASE gateway.

Abstract: Methods and system for providing network connectivity are disclosed. In an embodiment, a method for providing network connectivity involves receiving from a Mobile Network Operator (MNO) an access ID and an IP address at a SASE domain, wherein the access ID and the IP address correspond to a wireless device, generating an IP address-to-tenant mapping at the SASE domain by applying the access ID and the IP address to an access ID-to-tenant mapping, and forwarding traffic received at the SASE domain from the wireless device via the MNO according to the IP address-to-tenant mapping.

Abstract: An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.

Abstract: The present disclosure is directed at systems, methods and media for providing bearer call-back services for bearers that have been rejected or pre-empted by a network apparatus in a core network. In some embodiments, if a network apparatus enters a state in which it becomes necessary to reject or pre-empt a bearer associated with a user equipment (UE) (e.g., due to load conditions in a radio access network, the core network, or an application server), the network apparatus can send to the UE a call-back message when the network apparatus exits the state that precipitated the bearer rejection or pre-emption. By sending a call-back message, the network apparatus can save the UE from multiple unsuccessful attempts to establish a bearer, or from waiting an unnecessarily long time before establishing a bearer.

Abstract: An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.

Abstract: An example method is provided in one example embodiment and may include receiving a session request for a user equipment (UE) at a node, wherein the session request includes a timestamp for the UE and a retry count; determining if the session request is a stray session request; and maintaining session information for an existing session for the UE at the node if the session request is a stray session request. The method can include identifying the received session request as a stray request if the timestamp received in the request is less than a timestamp stored for an existing session for the UE. The method can also include identifying the received request as a stray request if the timestamp received is equal to the timestamp stored for the existing session and if the retry count received is less than or equal to a retry count stored for the session.

Abstract: The present disclosure is directed at systems, methods and media for providing bearer call-back services for bearers that have been rejected or pre-empted by a network apparatus in a core network. In some embodiments, if a network apparatus enters a state in which it becomes necessary to reject or pre-empt a bearer associated with a user equipment (UE) (e.g., due to load conditions in a radio access network, the core network, or an application server), the network apparatus can send to the UE a call-back message when the network apparatus exits the state that precipitated the bearer rejection or pre-emption. By sending a call-back message, the network apparatus can save the UE from multiple unsuccessful attempts to establish a bearer, or from waiting an unnecessarily long time before establishing a bearer.