Abstract: Systems and methods are provided for providing differential treatment to user traffic involving optimized reporting of start and stop traffic. The systems and method can include detecting, at a user plane function, an initiation of a type of traffic being performed at the user plane function, providing, by the user plane function, a start event trigger of the type of traffic detected by the user plane function to a session management function, and receiving, at the user plane function, a policy associated with the type of traffic from the session management function, the policy including instructions preventing submissions of subsequent event triggers to the session management function until an end of the type of traffic, the subsequent event triggers being associated with the type of traffic detected by the user plane function.

Abstract: Systems and methods are provided for providing differential treatment to user traffic involving optimized reporting of start and stop traffic. The systems and method can include detecting, at a user plane function, an initiation of a type of traffic being performed at the user plane function, providing, by the user plane function, a start event trigger of the type of traffic detected by the user plane function to a session management function, and receiving, at the user plane function, a policy associated with the type of traffic from the session management function, the policy including instructions preventing submissions of subsequent event triggers to the session management function until an end of the type of traffic, the subsequent event triggers being associated with the type of traffic detected by the user plane function.

Abstract: Systems and methods are provided for providing differential treatment to user traffic involving optimized reporting of start and stop traffic. The systems and method can include detecting, at a user plane function, an initiation of a type of traffic being performed at the user plane function, providing, by the user plane function, a start event trigger of the type of traffic detected by the user plane function to a session management function, and receiving, at the user plane function, a policy associated with the type of traffic from the session management function, the policy including instructions preventing submissions of subsequent event triggers to the session management function until an end of the type of traffic, the subsequent event triggers being associated with the type of traffic detected by the user plane function.

Abstract: A method of configuring a user plane function node in, e.g., a fifth generation mobile core architecture to process user plane traffic without reliance on control messages over the Sx/N4 or Gx/N7 interfaces. The method includes detecting a type of user traffic at a user plane function node in, e.g., a fifth generation mobile core architecture, selecting, on the user plane function node and based on the type of user traffic, a rule to be applied to the user traffic, and activating the rule to be applied to the user traffic. The approach reduces or eliminates north-south control traffic in CUPS architecture or 5G mobile core architecture.

Abstract: A Session Management Function (SMF) provides session and service continuity for a User Equipment (UE) transitioning between User Plane Functions (UPFs). The SMF establishes a first session between the first UPF and the UE using a first network address. The SMF determines that the UE transitions to the second UPF and establishes a second session between the second UPF and the UE using a second network address for new flows on the second session. The SMF queries the first UPF to determine any ongoing flows in the first session. The first UPF forwards packets in the ongoing flow(s) to the UE via the second UPF. The second UPF forwards packets in the ongoing flow(s) to the first UPF with the first network address. The SMF directs the second UPF to replace the first network address with the second network address in packets of a new flow for the UE.

Abstract: Techniques that provide for the preservation of policy and charging for a subscriber following a user-plane element failover are described herein. In one embodiment, a method includes receiving, by a user-plane element, at least one data packet of a packet flow associated with a subscriber, wherein the at least one data packet is are received after the user-plane element has recovered from a failure; determining, by the user-plane element, whether restoration information associated with the packet flow is stored at the user-plane element; and applying one or more policies to the packet flow based on a determination that the restoration information associated with the packet flow is stored at the user-plane element, wherein the restoration information comprises a rule associated with the packet flow.

Abstract: A method is performed by a mobility management entity (MME) in a network. Responsive to a session request from user equipment (UE), the MME initiates a session request procedure that includes: selecting a control plane serving gateway (SGW) and a user plane packet data network gateway (PGW) to establish a session for the UE; and receiving from the control plane SGW a session response to the session request, the session response including an identifier of the user plane PGW. After the session is established, responsive to a relocation request from the UE, the MME initiates a relocation procedure that includes: selecting a new control plane SGW; and sending to the new control plane SGW a new session request with the identifier of the user plane PGW, to cause the new control plane SGW to perform selecting the user plane PGW for the session in the relocation procedure.

Abstract: A method is performed by a mobility management entity (MME) in a network. Responsive to a session request from user equipment (UE), the MME initiates a session request procedure that includes: selecting a control plane serving gateway (SGW) and a user plane packet data network gateway (PGW) to establish a session for the UE; and receiving from the control plane SGW a session response to the session request, the session response including an identifier of the user plane PGW. After the session is established, responsive to a relocation request from the UE, the MME initiates a relocation procedure that includes: selecting a new control plane SGW; and sending to the new control plane SGW a new session request with the identifier of the user plane PGW, to cause the new control plane SGW to perform selecting the user plane PGW for the session in the relocation procedure.

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 for the preservation of policy and charging for a subscriber following a user-plane element failover are described herein. In one embodiment, a method includes receiving, by a user-plane element, at least one data packet of a packet flow associated with a subscriber, wherein the at least one data packet is are received after the user-plane element has recovered from a failure; determining, by the user-plane element, whether restoration information associated with the packet flow is stored at the user-plane element; and applying one or more policies to the packet flow based on a determination that the restoration information associated with the packet flow is stored at the user-plane element, wherein the restoration information comprises a rule associated with the packet flow.

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: Techniques that provide for the preservation of policy and charging for a subscriber following a user-plane element failover are described herein. In one embodiment, a method includes receiving, by a user-plane element, at least one data packet of a packet flow associated with a subscriber, wherein the at least one data packet is are received after the user-plane element has recovered from a failure; determining, by the user-plane element, whether restoration information associated with the packet flow is stored at the user-plane element; and applying one or more policies to the packet flow based on a determination that the restoration information associated with the packet flow is stored at the user-plane element, wherein the restoration information comprises a rule associated with the packet flow.