Abstract: A network node selectively encrypts messages between a user plane node and a control plane node in a network system. The user plane node and the control plane node negotiate a connection and indicate an encryption level for the connection. The encryption level is selected from an Information Element (IE) level, a message level, or a feature level. The user plane node and the control plane node selectively encrypt at least a portion of the messages between the user plane node and the control plane node based on the encryption level for the connection.

Abstract: Technologies for systems, methods and computer-readable storage media for solving complex distributed congestion in a 5G network by using traffic engineering data to redirect sessions. Specifically, involving anchoring a network node to a User Plane (UP) entity based on traffic engineering data and subscribing to traffic engineering data associated with requested parameters to push particular policies and/or select alternate application functions to correct congestion.

Abstract: Technologies for systems, methods and computer-readable storage media for solving complex distributed congestion in a 5G network by using traffic engineering data to redirect sessions. Specifically, involving anchoring a network node to a User Plane (UP) entity based on traffic engineering data and subscribing to traffic engineering data associated with requested parameters to push particular policies and/or select alternate application functions to correct congestion.

Abstract: Presented herein are embodiments that provide mobile edge computing (MEC) with low latency traffic segregation within a packet data network (PDN) using dedicated bearers. Techniques are provided that are performed at an edge user plane entity and a control plane entity to coordinate the directing of low latency traffic over a dedicated bearer broken out at the edge, and to communicate normal latency traffic over a default bearer that is centrally broken out.

Abstract: Presented herein are embodiments that provide mobile edge computing (MEC) with low latency traffic segregation within a packet data network (PDN) using dedicated bearers. Techniques are provided that are performed at an edge user plane entity and a control plane entity to coordinate the directing of low latency traffic over a dedicated bearer broken out at the edge, and to communicate normal latency traffic over a default bearer that is centrally broken out.

Abstract: A network node selectively encrypts messages between a user plane node and a control plane node in a network system. The user plane node and the control plane node negotiate a connection and indicate an encryption level for the connection. The encryption level is selected from an Information Element (IE) level, a message level, or a feature level. The user plane node and the control plane node selectively encrypt at least a portion of the messages between the user plane node and the control plane node based on the encryption level for the connection.

Abstract: Techniques that provide low latency traffic segregation to ensure an edge user plane (UP) is not overloaded are described herein in at least one embodiment. In at least one embodiment, a method may include determining offload of low latency traffic of a user equipment (UE) at a mobile network edge, wherein the UE has non-low latency traffic associated with a first packet data network session for an access point name; notifying the UE to request creation of a second packet data network session for the access point name; selecting an edge UP element to handle the low latency traffic for the second packet data network session; creating the second packet data network session at the selected edge UP element; and notifying the UE that second packet data network session is created.

Abstract: Technologies for systems, methods and computer-readable storage media for solving complex distributed congestion in a 5G network by using traffic engineering data to redirect sessions. Specifically, involving anchoring a network node to a User Plane (UP) entity based on traffic engineering data and subscribing to traffic engineering data associated with requested parameters to push particular policies and/or select alternate application functions to correct congestion.

Abstract: Various embodiments disclosed herein provide a method for grouping user planes in 4G/5G packet cores to simplify user plane discovery and registration. In some embodiments the method includes detecting a plurality of User Planes (UPs), grouping a first subset of the UPs into a first UP group, in which each UP in the first UP group is associated with a first set of features, and allocating the first UP group to a first network service based on the first set of features associated with the first UP group and a first set of requirements of the first network service. The method further includes grouping a second subset of the plurality of UPs into a second UP group, in which each of the second UP group is associated with a second set of features and allocating the second UP group to a second network service of a plurality of network services.

Abstract: In one embodiment, a method is performed. A first user plane entity may be associated with a user plane group comprising a plurality of user plane entities. The first user plane entity may be associated with a second user plane entity. A failure of the second user plane entity may be detected. In response to detecting the failure of the second user plane entity, the first user plane entity may be activated.

Abstract: Techniques that provide low latency traffic segregation to ensure an edge user plane (UP) is not overloaded are described herein in at least one embodiment. In at least one embodiment, a method may include determining offload of low latency traffic of a user equipment (UE) at a mobile network edge, wherein the UE has non-low latency traffic associated with a first packet data network session for an access point name; notifying the UE to request creation of a second packet data network session for the access point name; selecting an edge UP element to handle the low latency traffic for the second packet data network session; creating the second packet data network session at the selected edge UP element; and notifying the UE that second packet data network session is created.

Abstract: Techniques that provide low latency traffic segregation to ensure an edge user plane (UP) is not overloaded are described herein in at least one embodiment. In at least one embodiment, a method may include determining offload of low latency traffic of a user equipment (UE) at a mobile network edge, wherein the UE has non-low latency traffic associated with a first packet data network session for an access point name; notifying the UE to request creation of a second packet data network session for the access point name; selecting an edge UP element to handle the low latency traffic for the second packet data network session; creating the second packet data network session at the selected edge UP element; and notifying the UE that second packet data network session is created.

Abstract: Presented herein are embodiments that provide mobile edge computing (MEC) with low latency traffic segregation within a packet data network (PDN) using dedicated bearers. Techniques are provided that are performed at an edge user plane entity and a control plane entity to coordinate the directing of low latency traffic over a dedicated bearer broken out at the edge, and to communicate normal latency traffic over a default bearer that is centrally broken out.

Abstract: In one embodiment, a method is performed. A first user plane entity may be associated with a user plane group comprising a plurality of user plane entities. The first user plane entity may be associated with a second user plane entity. A failure of the second user plane entity may be detected. In response to detecting the failure of the second user plane entity, the first user plane entity may be activated.

Abstract: Various embodiments disclosed herein provide a method for grouping user planes in 4G/5G packet cores to simplify user plane discovery and registration. In some embodiments the method includes detecting a plurality of User Planes (UPs), grouping a first subset of the UPs into a first UP group, in which each UP in the first UP group is associated with a first set of features, and allocating the first UP group to a first network service based on the first set of features associated with the first UP group and a first set of requirements of the first network service. The method further includes grouping a second subset of the plurality of UPs into a second UP group, in which each of the second UP group is associated with a second set of features and allocating the second UP group to a second network service of a plurality of network services.

Abstract: An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.

Abstract: An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.

Abstract: An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.

Abstract: An example method is provided in one example embodiment and may include receiving an indication of a radio access technology (RAT) change for a user equipment (UE); determining availability of a preferred RAT type for a policy related rule associated with the UE, wherein the policy related rule includes, at least in part, the preferred RAT type for one or more service data flows for the UE; and configuring the one or more service data flows for the UE based, at least in part, on a change in availability of the preferred RAT type following the RAT change. In at least one case, the method can include routing downlink packets to the UE using the one or more service data flows for the preferred RAT type if the preferred RAT type is available.