Network function redundancy using binding header enhancements
AssigneeVerizon Patent and Licensing Inc.
InventorsSudhakar Reddy Patil, James Mathison
Life of this patent
Estimating the term…
Abstract
A first network function (NF) instance sends a request for a session to a second NF instance. The first NF instance receives a response, from the second NF instance, that includes a binding header that includes a failover mode identifier, a designated number of retry attempts, and a retry mode. The first NF instance sends a second request for the session to the second NF instance. The first NF instance determines if an error or a timed out response has occurred subsequent to sending the second request to the second NF instance, and re-sends, in response to the error or timed out response, the second request based on the failover mode identifier, the designated number of retry attempts and the retry mode from the binding header.
Claims20
A method, comprising:
- sending, from a first network function (NF) instance, a first request for a session to a second NF instance;
- receiving a response, at the first NF instance from the second NF instance, that includes a binding header, wherein the binding header comprises a failover mode identifier, a designated number of retry attempts, and a retry mode;
- sending, from the first NF instance, a second request for the session to the second NF instance;
- determining, by the first NF instance, if an error or a timed out response has occurred subsequent to sending the second request;
- and
- re-sending, in response to the error or timed out response, the second request based on the failover mode identifier, the designated number of retry attempts, and the retry mode from the binding header.
A device implementing a first network function (NF) instance, comprising:
- a communication interface coupled to a network to:
- send, by the first NF instance, a first request for a session to a second NF instance;
- receive a response, from the second NF instance, that includes a binding header, wherein the binding header comprises a failover mode identifier, a designated number of retry attempts, and a retry mode;
- send, by the first NF instance, a second request for the session to the second NF instance;
- and
- a processor or logic configured to:
- determine if an error or a timed out response has occurred subsequent to sending the second request or the command to the second NF instance;
- and
- re-send, via the communication interface in response to the error or timed out response, the second request based on the failover mode identifier, the designated number of retry attempts and the retry mode from the binding header.
A non-transitory storage medium storing instructions executable by a device implementing a first network function (NF) instance, wherein the instructions comprise instructions to cause the device to:
- send, from the first NF instance, a first request for a session to a second NF instance;
- receive a response, from the second NF instance, that includes a binding header, wherein the binding header comprises a failover mode identifier, a designated number of retry attempts, and a retry mode;
- send, from the first NF instance, a second request for the session to the second NF instance;
- determine, by the first NF instance, if an error or a timed out response has occurred subsequent to sending the second request;
- and
- re-send, in response to the error or timed out response, the second request based on the failover mode identifier, the designated number of retry attempts and the retry mode from the binding header.
Dependencies are inferred from the claim text.