Systems and methods for user plane function (“UPF”) offload at configurable routing fabric
A system described herein may provide for the separation of functions associated with a User Plane Function (“UPF”) in a wireless network (e.g., a Fifth Generation (“5G”) network), such that routing devices associated with the wireless network may perform functionality that would otherwise be performed by virtualized hosts or other configurable resources. For example, routing components which form a backhaul or other portion of the network may process traffic according to a suitable set of policies (e.g., Quality of Service (“QoS”) policies, content filtering policies, queueing policies, and/or other policies) instead of transmitting such traffic to a UPF associated with the network core for processing.
1. A device, comprising:
one or more processors configured to:
receive traffic associated with a first destination device, wherein the first destination device includes a User Plane Function (“UPF”) of a core network;
determine whether the traffic is associated with an existing traffic flow;
when the traffic is not associated with an existing traffic flow:
forward the traffic to the first destination device, and
establish a traffic flow associated with the traffic; and
when the traffic is associated with an existing traffic flow:
identify one or more policies associated with the traffic,
process the traffic by implementing the one or more policies associated with the traffic without forwarding the traffic to the first destination device, and
forward the processed traffic to a second destination device associated with the traffic.
2. The device of claim 1 , wherein determining whether the traffic is associated with an existing traffic flow includes:
identifying flow identifying information associated with the traffic; and
determining whether policy information, associated with the flow identifying information, has been previously received,
wherein the traffic is associated with an existing traffic flow when policy information associated with the flow identifying information has been previously received.
3. The device of claim 2 , wherein the flow identifying information includes information included in header information of the received traffic.
4. The device of claim 1 , wherein the traffic includes an encapsulated packet that indicates the second destination device, wherein processing the traffic includes identifying the second destination device based on header information of the encapsulated packet.
5. The device of claim 1 , wherein processing the traffic includes identifying a tunnel endpoint toward which the traffic is to be forwarded, wherein forwarding the processed traffic to the second destination device includes forwarding the processed traffic toward the tunnel endpoint.
6. The device of claim 1 , wherein implementing the one or more policies includes performing Quality of Service (“QoS”) treatment to the traffic.
7. The device of claim 1 , wherein identifying the one or more policies associated with the traffic includes receiving the one or more policies from a Session Management Function (“SMF”) of the core network.
8. A system, comprising:
one or more network devices configured to:
receive traffic associated with a first destination device, wherein the first destination device includes a User Plane Function (“UPF”) of a core network;
determine whether the traffic is associated with an existing traffic flow;
when the traffic is not associated with an existing traffic flow:
forward the traffic to the first destination device, and
establish a traffic flow associated with the traffic; and
when the traffic is associated with an existing traffic flow:
identify one or more policies associated with the traffic,
process the traffic by implementing the one or more policies associated with the traffic without forwarding the traffic to the first destination device, and
forward the processed traffic to a second destination device associated with the traffic.
9. The system of claim 8 , wherein determining whether the traffic is associated with an existing traffic flow includes:
identifying flow identifying information associated with the traffic; and
determining whether policy information, associated with the flow identifying information, has been previously received,
wherein the traffic is associated with an existing traffic flow when policy information associated with the flow identifying information has been previously received.
10. The system of claim 9 , wherein the flow identifying information includes information included in header information of the received traffic.
11. The system of claim 8 , wherein the traffic includes an encapsulated packet that indicates the second destination device, wherein processing the traffic includes identifying the second destination device based on header information of the encapsulated packet.
12. The system of claim 8 , wherein processing the traffic includes identifying a tunnel endpoint toward which the traffic is to be forwarded, wherein forwarding the processed traffic to the second destination device includes forwarding the processed traffic toward the tunnel endpoint.
13. The system of claim 8 , wherein implementing the one or more policies includes performing Quality of Service (“QoS”) treatment to the traffic.
14. The system of claim 8 , wherein identifying the one or more policies associated with the traffic includes receiving the one or more policies from a Session Management Function (“SMF”) of the core network.
15. A method, comprising:
receiving traffic associated with a first destination device, wherein the first destination device includes a User Plane Function (“UPF”) of a core network;
determining whether the traffic is associated with an existing traffic flow;
when the traffic is not associated with an existing traffic flow:
forwarding the traffic to the first destination device, and
establishing a traffic flow associated with the traffic; and
when the traffic is associated with an existing traffic flow:
identifying one or more policies associated with the traffic,
processing the traffic by implementing the one or more policies associated with the traffic without forwarding the traffic to the first destination device, and
forwarding the processed traffic to a second destination device associated with the traffic.
16. The method of claim 15 , wherein determining whether the traffic is associated with an existing traffic flow includes:
identifying header information associated with the traffic; and
determining whether policy information, associated with the identified header information, has been previously received,
wherein the traffic is associated with an existing traffic flow when policy information associated with the header information has been previously received.
17. The method of claim 15 , wherein the traffic includes an encapsulated packet that indicates the second destination device, wherein processing the traffic includes identifying the second destination device based on header information of the encapsulated packet.
18. The method of claim 15 , wherein processing the traffic includes identifying a tunnel endpoint toward which the traffic is to be forwarded, wherein forwarding the processed traffic to the second destination device includes forwarding the processed traffic toward the tunnel endpoint.
19. The method of claim 15 , wherein implementing the one or more policies includes performing Quality of Service (“QoS”) treatment to the traffic.
20. The method of claim 15 , wherein identifying the one or more policies associated with the traffic includes receiving the one or more policies from a Session Management Function (“SMF”) of the core network.