Methods, systems, and computer readable media for optimizing network bandwidth utilization through intelligent updating of network function (NF) profiles with NF repository function

1. A method for optimizing network bandwidth utilization through intelligent updating of network function (NF) profiles, the method comprising:

at an NF repository function (NRF):

receiving, from a georedundant mate NRF and over a data replication channel between the NRF and the georedundant mate NRF, an NF profile update for a first NF that successfully updated its NF profile with the georedundant mate NRF;

after failure of the georedundant mate NRF:

receiving, from the first NF that previously communicated with the geo-redundant mate NRF as primary, an NF heart-beat request message;

receiving, from a second NF that previously communicated with the geo-redundant mate NRF as primary and that successfully updated its NF profile with the geo-redundant mate NRF but whose updated NF profile was not communicated to the NRF over the data replication channel, an NF heart-beat request message;

locating an NF profile for the first NF in an NF profiles database maintained by the NRF, computing a first NF profile data modification detection value for the NF profile, and transmitting the first NF profile data modification detection value to the first NF;

locating an NF profile for the second NF in the NF profiles database maintained by the NRF, computing a second NF profile data modification detection value for the NF profile for the second NF, and transmitting the second NF profile data modification detection value to the second NF; and

receiving, from the second NF, an NF update message containing a full NF profile of the second NF.

2. The method of claim 1 comprising:

at the first NF:

receiving the first NF profile data modification detection value;

computing an NF profile data modification detection value for an NF profile of the first NF stored locally by the first NF;

comparing the first NF profile data modification detection value received from the NRF with the NF profile data modification detection value computed for the NF profile stored locally by the first NF;

determining that the first NF profile data modification detection value received from the NRF matches the NF profile data modification detection value computed for the NF profile stored locally by the first NF; and

in response to determining that the first NF profile data modification detection value received from the NRF matches the NF profile data modification detection value computed for the NF profile stored locally by the first NF, refraining from sending an NF profile update to the NRF.

3. The method of claim 1 wherein locating the NF profile for the first NF includes performing a lookup in the NF profiles database maintained by the NRF using an NF instance ID received in the NF heart-beat request message from the first NF.

4. The method of claim 1 wherein computing the first NF profile data modification detection value for the NF profile of the first NF located in the NF profiles database maintained by the NRF includes computing a checksum of the NF profile of the first NF located in the NF profiles database maintained by the NRF.

5. The method of claim 1 wherein transmitting the first NF profile data modification detection value to the first NF includes transmitting the first NF profile data modification detection value to the first NF in a 204 No Content message.

6. The method of claim 1 comprising:

at the second NF:

receiving the second NF profile data modification detection value computed for the NF profile of the second NF;

computing an NF profile data modification detection value for an NF profile of the second NF stored locally by the second NF;

comparing the second NF profile data modification detection value received from the NRF with the NF profile data modification detection value computed for the NF profile of the second NF stored locally by the second NF;

determining that the second NF profile data modification detection value computed by the NRF for the second NF does not match the NF profile data modification detection value computed for the NF profile stored locally by the second NF; and

in response to determining that the second NF profile data modification detection value computed for the NF profile of the second NF and received from the NRF does not match the NF profile data modification detection value computed for the NF profile stored locally by the second NF, sending the NF update message containing the full NF profile of the second NF to the NRF.

7. The method of claim 6 wherein sending the NF update message to the NRF includes sending an NF update request message to the NRF.

8. The method of claim 1 comprising, at the NRF, maintaining an intelligent NF profile update feature support database indicating whether NFs support intelligent NF profile updating.

9. The method of claim 8 comprising, at the NRF, prior to computing the first NF profile data modification detection value, accessing the intelligent NF profile update feature support database and determining that the first NF supports intelligent NF profile updating.

10. A system for optimizing network bandwidth utilization through intelligent updating of network function (NF) profiles, the system comprising:

an NF repository function (NRF) including at least one processor; and

an NF profiles update manager implemented by the at least one processor for receiving, from a georedundant mate NRF and over a data replication channel between the NRF and the georedundant mate NRF, an NF profile update for a first NF that successfully updated its NF profile with the georedundant mate NRF;

after failure of the georedundant mate NRF:

receiving, from a first NF, which previously communicated with the geo-redundant mate NRF as primary, an NF heart-beat request message;

receiving, from a second NF that previously communicated with the geo-redundant mate NRF as primary and that successfully updated its NF profile with the geo-redundant mate NRF but whose updated NF profile was not communicated to the NRF over the data replication channel, an NF heart-beat request message;

locating an NF profile for the first NF in an NF profiles database maintained by the NRF, computing a first NF profile data modification detection value for the NF profile, and transmitting the first NF profile data modification detection value to the first NF;

locating an NF profile for the second NF in the NF profiles database maintained by the NRF, computing a second NF profile data modification detection value for the NF profile for the second NF, and transmitting the second NF profile data modification detection value to the second NF; and

receiving, from the second NF, an NF update message containing a full NF profile of the second NF.

11. The system of claim 10 comprising an NF profile update controller implemented by the first NF for receiving the first NF profile data modification detection value, computing an NF profile data modification detection value for an NF profile of the first NF stored locally by the first NF, comparing the first NF profile data modification detection value received from the NRF with the NF profile data modification detection value computed for the NF profile stored locally by the first NF, determining that the first NF profile data modification detection value received from the NRF matches NF profile data modification detection value computed for the NF profile stored locally by the first NF, and, in response to determining that the first NF profile data modification detection value received from the NRF matches the NF profile data modification detection value computed for the NF profile stored locally by the first NF, refraining from sending an NF profile update to the NRF.

12. The system of claim 10 wherein the NF profiles update manager is configured to locate the NF profile for the first NF by performing a lookup in the NF profiles database maintained by the NRF using an NF instance ID received in the NF heart-beat request message from the first NF.

13. The system of claim 10 wherein the NF profile data modification detection value includes a checksum of the NF profile of the first NF located in the NF profiles database maintained by the NRF.

14. The system of claim 10 wherein the NF profiles update manager is configured to transmit the first NF profile data modification detection value to the first NF in a 204 No Content message.

15. The system of claim 10 wherein the second NF is configured to:

receive the second NF profile data modification detection value computed for the NF profile of the second NF;

compute an NF profile data modification detection value for an NF profile of the second NF stored locally by the second NF;

compare the second NF profile data modification detection value received from the NRF with the NF profile data modification detection value computed for the NF profile of the second NF stored locally by the second NF;

determine that the second NF profile data modification detection value computed for the second NF and received from the NRF does not match the NF profile data modification detection value computed for the NF profile stored locally by the second NF; and

in response to determining that the second NF profile data modification detection value computed for the NF profile of the second NF and received from the NRF does not match the NF profile data modification detection value computed for the NF profile stored locally by the second NF, send the NF update message to the NRF, wherein sending the NF update message to the NRF includes sending an NF update request message to the NRF.

16. The system of claim 10 comprising an intelligent NF profile update feature support database maintained by the NRF indicating whether NFs support intelligent NF profile updating.

17. The system of claim 16 wherein the NF profiles update manager is configured to, prior to computing the first NF profile data modification detection value, access the intelligent NF profile update feature support database and determine that the first NF supports intelligent NF profile updating.

18. A non-transitory computer readable media having stored thereon executable instructions that when executed by a processor of a computer control the computer to perform steps comprising:

at a network function (NF) repository function (NRF):

receiving, from a georedundant mate NRF and over a data replication channel between the NRF and the georedundant mate NRF, an NF profile update for a first NF that successfully updated its NF profile with the georedundant mate NRF;

after failure of the georedundant mate NRF:

receiving, from the first NF that previously communicated with the geo-redundant mate NRF as primary, an NF heart-beat request message;

receiving, from a second NF that previously communicated with the geo-redundant mate NRF as primary and that successfully updated its NF profile with the geo-redundant mate NRF but whose updated NF profile was not communicated to the NRF over the data replication channel, an NF heart-beat request message;

locating an NF profile for the first NF in an NF profiles database maintained by the NRF, computing an NF profile data modification detection value for the NF profile, and transmitting the NF profile data modification detection value to the first NF; and

locating an NF profile for the second NF in the NF profiles database maintained by the NRF, computing a second NF profile data modification detection value for the NF profile for the second NF, and transmitting the second NF profile data modification detection value to the second NF; and

receiving, from the second NF, an NF update message containing a full NF profile of the second NF.