For larger deployments, where multiple level of Network Function (NF) Repository Functions (NRFs) are deployed, the slightest misconfiguration could lead to an indefinite query loop between NRFs. The indefinite loop in the NRF query would mean repeated timeouts and/or failure of a service discovery request that a consumer had initiated to find a suitable producer. This could lead to signaling failure between a set of consumers and producers, which in turn can lead to Quality of Service (QoS) and Service Level Agreement (SLA) violations. A new Hypertext Transfer Protocol Version 2 (HTTP/2) header, Network Function (NF)-route-record, is proposed, which should be added by an intermediate NRF (relay or proxy) before forwarding any request. The NF-route-record should contain the identity of the peer from which the request was received. The receiving NRF checks the NF-route-record before further forwarding or serving the request. If the NF-route-record matches its own identity, then the receiving NRF would detect the loop. The same can be used in the reverse direction when sending the response from a server (producer) to a client (consumer).

Creative Commons License

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 License.