IP Library › Granted Patent US 12,632,344
Granted Patent B2
US 12,632,344 · App. 18/032,392 · Granted May 19, 2026

Network nodes and methods therein for providing backup network function

Inventors: Yunjie Lu (Shanghai, CN); Yong Yang (Kållered, SE); Gang Ren (Shanghai, CN); Xiao Li (Shanghai, CN)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
G06F11/1464G06F11/1451
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,632,344
App. No.
18/032,392
Granted
May 19, 2026
Kind
B2
Abstract

The present disclosure provides a method in a network node implementing a Network Function, NF. The method includes: transmitting, to another NF, information indicating an identifier, ID, of each of one or more backup entities for one or more contexts in the NF. The information is included in a binding indication or a separate indication from the binding indication. The one or more backup entities are one or more backup NF instances or one or more backup NF service instances.

Claims (106)

1 . A method in a network node implementing a Network Function, NF, comprising:

receiving, from another NF, information indicating an identifier, ID, of each of one or more backup entities for one or more contexts in the other NF,

wherein the information is included in a binding indication or a separate indication from the binding indication,

wherein the one or more backup entities are one or more backup NF instances or one or more backup NF service instances,

wherein the binding indication contains a binding level set to NF service instance, NF service set, NF instance, or NF set, and one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises, when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, when the NF service set ID is contained in the binding indication and the ID of each of the one or more backup NF instances is contained in the information, or selecting an equivalent NF service instance in one of the one or more backup NF instances, when the ID of each of the one or more backup NF instances is contained in the information,

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the binding indication, and/or

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the binding indication; and/or

selecting one of the one or more backup NF service instances when the ID of each of the one or more backup NF service instances is contained in the information, with a higher priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the binding indication,

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the binding indication,

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the binding indication; or

wherein the one or more backup entities correspond to a binding level indicated in the binding indication, and wherein the binding level is set to NF service instance and the one or more backup entities are one or more backup service instances, the binding level is set to NF service set and the one or more backup entities are one or more backup NF service sets, the binding level is set to NF instance and the one or more backup entities are one or more backup NF instances, or the binding level is set to NF set and the one or more backup entities are one or more backup NF sets, wherein the binding indication contains one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises: when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities,

selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets,

wherein the selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the binding indication; and/or

wherein the selecting of the one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the binding indication.

2 . The method of claim 1 , wherein the information is carried in a 3gpp-sbi-binding header in a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response.

3 . The method of claim 1 , further comprising:

transmitting the information to a Service Communication Proxy, SCP,

wherein the information is included in a routing binding indication or a separate indication from the routing binding indication, or

wherein the information is carried in a 3gpp-sbi-routing-binding header in a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response destined to the other NF.

4 . A method in a network node implementing a Service Communication Proxy, SCP, comprising:

receiving, from a Network Function, NF, information indicating an identifier, ID, of each of one or more backup entities for one or more contexts in another NF,

wherein the information is included in a routing binding indication or a separate indication from the routing binding indication, and

wherein the one or more backup entities are one or more backup NF instances or one or more backup NF service instances;

wherein the routing binding indication contains a binding level set to NF service instance, NF service set, NF instance, or NF set, and one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises, when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, when the NF service set ID is contained in the routing binding indication and the ID of each of the one or more backup NF instances is contained in the information, or selecting an equivalent NF service instance in one of the one or more backup NF instances, when the ID of each of the one or more backup NF instances is contained in the routing binding indication,

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication, and/or

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication; and/or

selecting one of the one or more backup NF service instances when the ID of each of the one or more backup NF service instances is contained in the information, with a higher priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication,

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication,

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication

wherein the one or more backup entities correspond to a binding level indicated in the routing binding indication, and wherein the binding level is set to NF service instance and the one or more backup entities are one or more backup service instances, the binding level is set to NF service set and the one or more backup entities are one or more backup NF service sets, the binding level is set to NF instance and the one or more backup entities are one or more backup NF instances, or the binding level is set to NF set and the one or more backup entities are one or more backup NF sets, and wherein the routing binding indication contains one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises: when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets,

wherein the selecting of the one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication; and/or

wherein the selecting of the one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication.

5 . The method of claim 4 , wherein the information is carried in a 3gpp-sbi-routing-binding header in a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response destined to the other NF.

6 . A network node, comprising a communication interface, a processor and a memory, the memory comprising instructions executable by the processor whereby the network node is operative to:

when implementing a Network Function, NF, perform following steps:

receiving, from another NF, information indicating an identifier, ID, of each of one or more backup entities for one or more contexts in the other NF,

wherein the information is included in a binding indication or a separate indication from the binding indication,

wherein the one or more backup entities are one or more backup NF instances or one or more backup NF service instances,

wherein the routing binding indication contains a binding level set to NF service instance, NF service set, NF instance, or NF set, and one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises, when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, when the NF service set ID is contained in the routing binding indication and the ID of each of the one or more backup NF instances is contained in the information, or selecting an equivalent NF service instance in one of the one or more backup NF instances, when the ID of each of the one or more backup NF instances is contained in the routing binding indication,

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication, and/or

wherein the selecting the NF service instance in the equivalent NF service set of one of the one or more backup NF instances or the selecting an equivalent NF service instance in one of the one or more backup NF instances is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication; and/or selecting one of the one or more backup NF service instances when the ID of each of the one or more backup NF service instances is contained in the information, with a higher priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication,

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication,

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication

wherein the one or more backup entities correspond to a binding level indicated in the routing binding indication, and wherein the binding level is set to NF service instance and the one or more backup entities are one or more backup service instances, the binding level is set to NF service set and the one or more backup entities are one or more backup NF service sets, the binding level is set to NF instance and the one or more backup entities are one or more backup NF instances, or the binding level is set to NF set and the one or more backup entities are one or more backup NF sets, and wherein the routing binding indication contains one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises: when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets,

wherein the selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication; and/or

wherein the selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication, or

when implementing a Service Communication Proxy, SCP, function, perform following steps:

receiving, from a Network Function, NF, information indicating an identifier, ID, of each of one or more backup entities for one or more contexts in another NF,

wherein the information is included in a routing binding indication or a separate indication from the routing binding indication, and

wherein the one or more backup entities are one or more backup NF instances or one or more backup NF service instances;

wherein the routing binding indication contains a binding level set to NF service instance, NF service set, NF instance, or NF set, and one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises, when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, when the NF service set ID is contained in the routing binding indication and the ID of each of the one or more backup NF instances is contained in the information, or selecting an equivalent NF service instance in one of the one or more backup NF instances, when the ID of each of the one or more backup NF instances is contained in the routing binding indication,

wherein the selecting the NF service instance in the equivalent NF service set or the selecting an equivalent NF instance in one of the one or more backup NF instances is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication, and/or

wherein the selecting the NF service instance in the equivalent NF service set or the selecting an equivalent NF instance in one of the one or more backup NF instances is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication; and/or

selecting one of the one or more backup NF service instances when the ID of each of the one or more backup NF service instances is contained in the information, with a higher priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication,

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication,

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication

wherein the one or more backup entities correspond to a binding level indicated in the routing binding indication, and wherein the binding level is set to NF service instance and the one or more backup entities are one or more backup service instances, the binding level is set to NF service set and the one or more backup entities are one or more backup NF service sets, the binding level is set to NF instance and the one or more backup entities are one or more backup NF instances, or the binding level is set to NF set and the one or more backup entities are one or more backup NF sets, and wherein the routing binding indication contains one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, and the method further comprises: when the other NF is not available at a time subsequent to the receiving information indicating the ID of each of the one or more backup entities:

selecting of one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets,

wherein the selecting the one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a lower priority than:

selecting an NF service instance in an NF service set indicated by the NF service set ID, when the NF service set ID is contained in the routing binding indication, and/or

selecting an equivalent NF service instance in an NF instance indicated by the NF instance ID, when the NF instance ID is contained in the routing binding indication; and/or

wherein the selecting the one of the one or more backup service instances, the NF service instance in one of the one or more backup NF service sets, the equivalent NF service instance in one of the one or more backup NF instances, or the equivalent NF service instance in one of the one or more backup NF sets is performed with a higher priority than:

selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, when the NF service set ID and the NF set ID are contained in the routing binding indication, and/or

selecting an equivalent NF service instance in another NF instance of the NF set, when the NF set ID is contained in the routing binding indication.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 18, 2023
From: LU, YUNJIE; YANG, YONG; REN, GANG; LI, XIAO
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 063355/0786 →
Priority Claims (1)
WO PCT/CN2020/123350 · Oct 23, 2020 · international
Continuity (1)
Related Publication 20230385161A1 · Nov 30, 2023
References Cited (36)
US 11129215B2 · Bharatia · 2021 [cited by examiner]
US 12004059B2 · S Bykampadi · 2024 [cited by examiner]
US 20200028920A1 · Livanos · 2020 [cited by examiner]
US 20210105196A1 · Dao · 2021 [cited by examiner]
US 20210168215A1 · Zong · 2021 [cited by examiner]
US 20210258406A1 · Ali · 2021 [cited by examiner]
US 20210297935A1 · Belling · 2021 [cited by examiner]
US 20210306875A1 · Zhang · 2021 [cited by examiner]
US 20210306907A1 · Landais · 2021 [cited by examiner]
US 20220015023A1 · De-Gregorio-Rodriguez · 2022 [cited by examiner]
US 20220053372A1 · Shekhar · 2022 [cited by examiner]
US 20220086734A1 · Aggarwal · 2022 [cited by examiner]
US 20220210060A1 · Wang · 2022 [cited by examiner]
US 20220232460A1 · Fu · 2022 [cited by examiner]
US 20220247827A1 · Das · 2022 [cited by examiner]
US 20220303793A1 · Patil · 2022 [cited by examiner]
CN 11083543A · 2020 [cited by applicant]
WO 2019223855A1 · 2019 [cited by applicant]
WO WO2020002507A1 · 2020 [cited by examiner]
WO WO2020202043A1 · 2020 [cited by examiner]
WO WO2020254925A1 · 2020 [cited by examiner]
WO WO2022035695A1 · 2022 [cited by examiner]
T. Taleb, A. Ksentini and B. Sericola, “On Service Resilience in Cloud-Native 5G Mobile Systems,” in IEEE Journal on Selected Areas in Communications, vol. 34, No. 3, pp. 483-496, Mar. 2016. [cited by examiner]
R. Ahmed et al., “Service naming in large-scale and multi-domain networks,” in IEEE Communications Surveys & Tutorials, vol. 7, No. 3, pp. 38-54, Third Quarter 2005. [cited by examiner]
Dominic Duggan, “Service-Oriented Architecture,” in Enterprise Software Architecture and Design: Entities, Services, and Resources , IEEE, 2012, pp. 207-358. [cited by examiner]
Author Unknown, “Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS): Stage 2 (Release 16),” Technical Specification 23.501, Version 16.6.0, Sep. 2020, 3GPP Organizatio… [cited by applicant]
Author Unknown, “Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 17),” Technical Specification 29.500, Version 17.0.0, Sep. 2020… [cited by applicant]
Notice of Reasons for Rejection for Japanese Patent Application No. 2023-524870, mailed Jun. 11, 2024, 6 pages. [cited by applicant]
Author Unknown, “Technical Specification Group Services and System Aspects; System architecture for the 5G System (5GS): Stage 2 (Release 16),” Technical Specification 23.501, Version 16.4.0, Mar. 2020, 3GPP Organizatio… [cited by applicant]
Author Unknown, “Technical Specification Group Core Network and Terminals; 5G System; Technical Realization of Service Based Architecture; Stage 3 (Release 16),” Technical Specification 29.500, Version 16.3.0, Mar. 2020… [cited by applicant]
Nokia, et al., “S2-187460: Peer NF association of GUAMI with a given UE,” 3GPP SA WG2 Meeting #128, Jul. 2-6, 2018, Vilnius, Lithuania, 5 pages. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/CN2021/119676, mailed Nov. 25, 2021, 9 pages. [cited by applicant]
International Preliminary Report on Patentability for International Patent Application No. PCT/CN2021/119676, mailed Feb. 15, 2023, 25 pages. [cited by applicant]
Ericsson, “C4-205355: Binding Indication for Backup AMF,” 3GPP TSG-CT WG4 Meeting #101e, Nov. 3-13, 2020, Electronic Meeting, 7 pages. [cited by applicant]
Extended European Search Report for European Patent Application No. 21881804.5, mailed Aug. 6, 2024, 10 pages. [cited by applicant]
Notice of Reasons for Refusal for Japanese Patent Application No. 2023-524870, mailed Nov. 12, 2024, 8 pages. [cited by applicant]