Method and Apparatus to handle Partial Data Path Failure at User Plane
A telecommunications system and method for identifying when a next hop is down by sending a first series of pings from a User Plane (UP) computer to the next hop, for incrementing a Key Performance Indicator (KPI) to count a time for when the next hop is down, and for communicating from the UP computer to a Control Plane (CP) computer that a next hop is down. The system facilitating identification of when the next hop transitions to up by sending a second series of pings from the UP computer to the next hop, for incrementing the KPI at the time when the next hop is up, and for communicating from the UP computer to the CP computer that the next hop is up.
1 . A telecommunications system for determining a status of a next hop in a Radio Access Networks (RAN) where User Equipment (UE) is wirelessly coupled to radio equipment, the system comprising:
a User Plane (UP) computer coupled to the radio equipment;
a Control Plane (CP) computer, said CP computer coupled to said UP computer; and
a plurality of next hops selectable by said UP computer for transmitting of data to and from the UE;
said UP computer transmitting a first series of pings from said UP computer to one of the plurality of next hops;
said UP computer determining from the first series of pings whether the next hop the first series of pings was sent to is down;
wherein when said UP computer determines the next hop is down, said UP computer increments a Key Performance Indicator (KPI) to count a time period for when the next hop is down;
said UP computer notifying said CP computer that the next hop is down.
2 . The telecommunications system according to claim 1 , wherein the first series of pings is continuous for a first period of time.
3 . The telecommunications system according to claim 2 , wherein the first period of time is configurable.
4 . The telecommunications system according to claim 1 , wherein said UP computer notifies said CP computer that next hop is down via a Packet Forwarding Control Protocol (PFCP) mechanism.
5 . The telecommunications system according to claim 1 , further comprising:
a Network Repository Function (NRF) coupled to said UP computer;
wherein said UP computer updates said NRF that the next hop is down.
6 . The telecommunications system according to claim 5 , wherein said UP computer updates said NRF via HTTP, HTTPS or HTTP2 POST/PUT.
7 . The telecommunications system according to claim 1 , wherein the one of the plurality of next hops is selected from the group consisting of:
an enterprise Data Network Name (DNN) or Access Point Name (APN);
an IP multimedia subsystem DNN or APN; or
an internet DNN or APN.
8 . The telecommunications system according to claim 1 , wherein when said UP computer identifies that the one of the plurality of next hops is down, said UP computer identifies all sessions that are latched onto the next hop that is down and notifies said CP computer about a usage count for each of the identified sessions.
9 . The telecommunications system according to claim 8 , wherein said UP computer identifies failed sessions that are not able to send data due to non-availability of the next hop that is down and counts a usage for each session not able to route packets.
10 . The telecommunications system according to claim 9 , wherein said UP computer reports the usage count of a given session to the CP computer until it has a routable SGi/N6 LAN interface.
11 . The telecommunications system according to claim 1 , wherein,
said UP computer transmits a second series of pings from said UP computer to the next hop that was previously determined to be down;
said UP computer determining from the second series of pings whether the next hop that was down is now up;
wherein when said UP computer determines the next hop is up, said UP computer increments the KPI to count a time period at which the next hop is now up;
said UP computer notifying said CP computer that the next hop is up.
12 . The telecommunications system according to claim 11 , wherein said UP computer notifies said CP computer that the next hop is up via a Packet Forwarding Control Protocol (PFCP) mechanism.
13 . The telecommunications system according to claim 11 , further comprising:
a Network Repository Function (NRF) coupled to said UP computer;
wherein said UP computer updates said NRF that the next hop is up.
14 . The telecommunications system according to claim 11 , wherein the second series of pings is continuous for a second period of time.
15 . The telecommunications system according to claim 14 , wherein the second period of time is configurable.