Network Node for Providing Backup Network Function and Method in Network Node

Abstract

The present disclosure provides a method (100) in a network node implementing a network function (NF). The method (100) includes transmitting (110) 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 an indication separate 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.

Description

Technical Field

[0001] The present disclosure relates to communication technologies, and more particularly, to network nodes for providing backup network functions (NFs) and methods in network nodes.

Background Art

[0002] In Release 16 (Rel-16), the 3rd Generation Partnership Project (3GPP) further expanded the use of the network function (NF) set concept to be applicable to all types of NFs in the 5th Generation (5G) core.

[0003] 3GPP Technical Specification (TS) 23.501, V16.4.0, which is hereby incorporated by reference in its entirety, provides a list of specifications regarding NF services, NF service sets, NFs, and NF sets, namely, NF instance: A distinguishable instance of an NF, NF service: A function that is exposed by an NF through a service-based interface and consumed by other permitted NFs, NF service instance: A distinguishable instance of an NF service, NF service operation: The basic unit that constitutes an NF service, NF service set: A group of interchangeable NF service instances of the same service type within an NF instance (NF service instances in the same NF service set have access to the same context data), and NF set: A group of interchangeable NF instances of the same type that support the same service and (one or more) the same network slices (NF instances in the same NF set are geographically dispersed but may have access to the same context data) is provided.

[0004] As specified in Section 5.21.3.1 of TS23.501, several NF instances can be deployed within an NF set as a set of NF instances to jointly provide distribution, redundancy, and scalability. In this case, the NF can be replaced with an alternative NF within the same NF set in case of failure, load distribution, or load re-balancing. This applies to both service operation and notification delivery.

[0005] In case of failure of an NF (service) instance or to perform load re-balancing, a so-called "binding indication" is used to select an alternative NF (service) instance.

[0006] As specified in Section 6.3.1.0 of TS23.501, the binding can be used to indicate one or more suitable target NF producer instances for NF service instance selection, re-selection, and routing of subsequent requests related to a specific NF producer resource (context) and NF service. This enables an NF service producer (or NF producer for short) to indicate that an NF service consumer (or NF consumer for short) should be bound to an NF service instance, NF instance, NF service set, or NF set according to local policies and other criteria (e.g., at which point in time it is during a certain procedure, considering performance aspects, etc.) for a specific context. The binding can also be used by an NF consumer to indicate one or more suitable NF consumer instances for notification target instance re-selection and routing of subsequent notification requests related to a specific notification subscription, and to provide a binding indication for one or more services that an NF consumer creates for the same data context and that an NF service producer may then call.

[0007] The binding indication is information included by the NF service producer in a request response or notification to the NF service consumer to convey the scope within which selection / reselection of the target NF / NF service can be performed, or information included by the NF service consumer in a request or subscription to convey the scope within which selection / reselection of the notification target, or selection of one or more other services created by the NF consumer for the same data context, can be performed.

[0008] Table 6.3.1.0-1 in TS 23.501, which is reproduced below as Table 1, specifies the selection and reselection behavior of the NF service consumer and the service communication proxy (SCP) that depends on the binding indication provided by the NF service producer. TIFF0007684394000001.tif160170

[0009] The binding indication may be included in the Hypertext Transfer Protocol (HTTP) header, 3gpp-Sbi-Binding, as defined in 3GPP TS 29.500, V16.3.0, which is hereby incorporated by reference in its entirety. This header contains a comma-separated list of binding indications from the HTTP server for storage and subsequent use by the HTTP client. The encoding of the header follows the Augmented Backus-Naur Form (ABNF) as defined in Internet Engineering Task Force (IETF) Request for Comments (RFC) 7230, June 2014. TIFF0007684394000002.tif37170

[0010] The following parameters are specified. - bl (Binding Level): Indicates the binding to either an NF instance, NF set, NF service instance, or NF service set. - nfinst (NF Instance): Indicates the NF instance ID. - nfset (NF Set): Indicates the NF set ID. - nfservinst (NF Service Instance): Indicates the NF service instance ID. - nfserviceset (NF Service Set): Indicates the NF service set ID. - scope: Indicates the applicability of the binding indication in a service request. This can take one of the following values. - “other-service”: The binding information applies to one or more other services that an NF service consumer may later provide as an NF service producer. - “subscription-events”: The binding information applies to subscription change event notifications. - “callback”: The binding information applies to notifications or callback requests.

[0011] The absence of this parameter in a binding indication in a service request shall be interpreted as “callback”.

[0012] When the binding information applies to both notification / callback requests and other services, two scope parameters may be present in the binding indication. - servname (Service Name): The name of the service or custom service, i.e., - the name of the service handling the notification or callback request when present in a binding indication for a subscription or callback, i.e., when the scope parameter is absent or set to “callback”, or - The name(s) of the other service(s) to which the binding applies when present in a binding instruction in a service request for other services that an NF service consumer may later provide as an NF service producer, i.e., when the scope parameter is set to "other-service" is / are indicated. Two or more servname parameters may exist to represent multiple such services. The absence of this parameter in a binding instruction where the scope parameter is set to "other-service" shall be interpreted as binding information applicable to all services that an NF service consumer may later provide as an NF service producer. - It is assumed that the specification and encoding of blvalue and other parameters are those specified for 3gpp-Sbi-Routing-Binding.

[0013] In Rel-16, as part of the network function service framework, "indirect communication" is defined in section 7.1.1 of TS 23.501. NF services can communicate directly between an NF service consumer and an NF service producer, or indirectly via a service communication proxy (SCP). Whether the NF service consumer uses direct communication or indirect communication by using the SCP is based on the settings of the NF service consumer. In direct communication, the NF service consumer discovers the target NF service producer either through local settings or via the NF repository function (NRF). The NF service consumer communicates directly with the target NF service producer. In indirect communication, the NF service consumer communicates with the target NF service producer via the SCP. The NF service consumer can be configured to directly discover the target NF service producer or delegate the discovery of the target NF service producer to the SCP used for indirect communication. In the latter case, the SCP uses the parameters provided by the NF service consumer to perform the discovery and / or selection of the target NF service producer. The SCP address can be set locally in the NF service consumer.

[0014] According to section 6.3.1.0 of TS 23.501, the binding indication contains the information in Table 1. The routing binding indication can be included in a request, subscribe, or notify message. The routing binding indication can be used to route messages in the case of indirect communication by the SCP. The routing binding indication is a copy of the information in the binding indication and also contains the information in Table 1.

Summary of the Invention

[0015] An object of the present disclosure is to provide a network node for providing a backup NF and a method in the network node.

[0016] According to a first aspect of the present disclosure, a method in a network node implementing an NF is provided. The method includes transmitting, to another NF, information indicating an 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 in an indication separate 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.

[0017] In one embodiment, the one or more backup entities may correspond to a binding level indicated in a binding indication.

[0018] In one embodiment, the binding level may be set to an NF service instance, and the one or more backup entities may be one or more backup service instances; the binding level may be set to an NF service set, and the one or more backup entities may be one or more backup NF service sets; the binding level may be set to an NF instance, and the one or more backup entities may be one or more backup NF instances; or the binding level may be set to an NF set, and the one or more backup entities may be one or more backup NF sets.

[0019] In one embodiment, the information may be 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.

[0020] In one embodiment, a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response may be sent directly or via an SCP to another NF.

[0021] In one embodiment, each of one or more backup entities may be provided with one or more contexts.

[0022] According to a second aspect of the present disclosure, a method in a network node implementing an NF is provided. The method includes receiving, from another NF, information indicating the ID of each of one or more backup entities for one or more contexts in the other NF. The information is included in a binding indication or an indication separate 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.

[0023] In one embodiment, the binding indication may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The method may further include selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or selecting an equivalent NF service instance in one of the one or more backup NF instances, when the NF service set ID is included in the binding indication and the ID of each of the one or more backup NF instances is included in the information when the other NF is not available.

[0024] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of one or more backup NF instances, may be performed with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, and / or than selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction.

[0025] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of one or more backup NF instances, may be 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 and / or than selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the binding instruction.

[0026] In one embodiment, the method may further include selecting one of one or more backup NF service instances when the ID of each of the one or more backup NF service instances is included in the information when other NFs are not available.

[0027] In one embodiment, the binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The operation of selecting one of the one or more backup NF service instances may be to select an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, to select an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction, to select 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 included in the binding instruction, and / or to select an equivalent NF service instance in another NF instance of the NF set with a higher priority than when the NF set ID is included in the binding instruction.

[0028] In one embodiment, one or more backup entities may correspond to the binding level indicated in the binding instruction.

[0029] In one embodiment, the binding level can be set to an NF service instance, and one or more backup entities can be one or more backup service instances; the binding level can be set to an NF service set, and one or more backup entities can be one or more backup NF service sets; the binding level can be set to an NF instance, and one or more backup entities can be one or more backup NF instances; or the binding level can be set to an NF set, and one or more backup entities can be one or more backup NF sets.

[0030] In one embodiment, the method may further include selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets when other NFs are not available.

[0031] In one embodiment, the binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. The operation of selecting one of one or more backup service instances, one of the NF service instances in one of one or more backup NF service sets, one of the equivalent NF service instances in one of one or more backup NF instances, or one of the equivalent NF service instances in one of one or more backup NF sets may be performed with lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction.

[0032] In one embodiment, the operation of selecting one of one or more backup service instances, one of the NF service instances in one of one or more backup NF service sets, one of the equivalent NF service instances in one of one or more backup NF instances, or one of the equivalent NF service instances in one of one or more backup NF sets may be performed with higher priority than selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the binding instruction.

[0033] In one embodiment, the information may be carried in the 3gpp-sbi-binding header in a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response.

[0034] In one embodiment, the method may further include sending information to the SCP.

[0035] In one embodiment, the information may be included in a routing binding instruction or in an instruction separate from the routing binding instruction.

[0036] In one embodiment, the information may be carried in a 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0037] In one embodiment, each of the one or more backup entities may be provided with one or more contexts.

[0038] According to a third aspect of the present disclosure, a method in a network node implementing an SCP. The method includes receiving, from an NF, information indicating identifiers of each of one or more backup entities for one or more contexts in another NF. The information is included in a routing binding instruction or in an instruction separate from the routing binding instruction. The one or more backup entities are one or more backup NF instances or one or more backup NF service instances.

[0039] In one embodiment, the routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The method includes, when other NFs are not available, the NF service set ID being included in the routing binding instruction, and when the ID of each of one or more backup NF instances is included in the information, selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or, when the ID of each of one or more backup NF instances is included in the routing binding instruction, selecting an equivalent NF service instance in one of the one or more backup NF instances.

[0040] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of the one or more backup NF instances, may be performed with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction, and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction.

[0041] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of one or more backup NF instances, may be 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 and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the routing binding instruction.

[0042] In one embodiment, the method may further include selecting one of one or more backup NF service instances when the ID of each of the one or more backup NF service instances is included in the information when other NFs are not available.

[0043] In one embodiment, the routing binding indication may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The operation of selecting one of the one or more backup NF service instances may be performed with a higher priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding indication, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included 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 included 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 included in the routing binding indication.

[0044] In one embodiment, the one or more backup entities may correspond to the binding level indicated in the routing binding indication.

[0045] In one embodiment, the binding level can be set for an NF service instance, and one or more backup entities can be one or more backup service instances; the binding level can be set for an NF service set, and one or more backup entities can be one or more backup NF service sets; the binding level can be set for an NF instance, and one or more backup entities can be one or more backup NF instances; or the binding level can be set for an NF set, and one or more backup entities can be one or more backup NF sets.

[0046] In one embodiment, the method can further include selecting one of one or more backup service instances, an NF service instance within one of one or more backup NF service sets, an equivalent NF service instance within one of one or more backup NF instances, or an equivalent NF service instance within one of one or more backup NF sets when other NFs are not available.

[0047] In one embodiment, the routing binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. The operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be performed with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction.

[0048] In one embodiment, the operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be 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 and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the routing binding instruction and when the NF set ID is included in the routing binding instruction.

[0049] In one embodiment, the information may be carried in a 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0050] In one embodiment, each of one or more backup entities may be provided with one or more contexts.

[0051] According to a fourth aspect of the present disclosure, a network node is provided. The network node includes a communication interface, a processor, and a memory. The memory includes instructions executable by the processor, whereby the network node is operable to perform the method according to the first or second aspect above when implementing an NF, or to perform the method according to the third aspect above when implementing an SCP function.

[0052] According to a fifth aspect of the present disclosure, a computer-readable storage medium is provided. The computer-readable storage medium stores computer-readable instructions that, when executed by a processor of a network node, configure the network node to perform the method according to the first or second aspect above when implementing an NF, or to perform the method according to the third aspect above when implementing an SCP function.

[0053] In an embodiment of the present disclosure, an NF may send information indicating the ID of each of one or more backup entities for one or more contexts in the NF to another NF (e.g., a peer NF). In this way, the peer NF is enabled to select a backup entity designated by the NF when the NF is unavailable.

[0054] The above and other objects, features and advantages will become more apparent from the following description of embodiments with reference to the drawings.

Brief Description of the Drawings

[0055]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

DETAILED DESCRIPTION OF THE INVENTION

[0056] In the present disclosure, a network function, or NF, may be implemented either as a network element on dedicated hardware, as a software instance running on dedicated hardware, or as a virtualized function instantiated on a suitable platform, for example, on a cloud infrastructure.

[0057] References in this specification to "one embodiment", "an embodiment", "exemplary embodiments", etc., indicate that the embodiments described may include a particular feature, structure, or characteristic, but not every embodiment necessarily includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated within the knowledge of one of ordinary skill in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0058] The terms "first", "second", etc. may be used herein to describe various elements, but it should be understood that these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the exemplary embodiments, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element. The term "and / or" as used herein includes any and all combinations of one or more of the associated listed terms.

[0059] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of exemplary embodiments. As used herein, the singular forms "a", "an" and "the" are to be construed to include the plural forms as well, unless the context clearly dictates otherwise. The terms "comprises", "comprising", "has", "having", "includes" and / or "including" as used herein specify the presence of stated features, elements, and / or components, etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0060] In the following description and claims, unless otherwise specified, all technical and scientific terms used herein shall have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure pertains.

[0061] Since Release 15, the Access and Mobility Management Function (AMF) may specify a backup AMF for each specific global unique AMF ID (GUMAI). The 5G system supports the establishment of an association between the AMF and the 5G Access (AN) node. A new AMF may be added to the AMF set, and the association between the AMF and the GUAMI may be created and / or updated as follows. The AMF shall be able to dynamically update the NRF with the new or updated (one or more) GUAMIs in order to provide a mapping between the (one or more) GUAMIs and the AMF information. The association between the (one or more) GUAMIs and the AMF is issued to the NRF. Furthermore, to handle planned maintenance and failures, the AMF may optionally provide backup AMF information, i.e., the AMF shall act as a backup AMF if the AMF associated with the indicated GUAMI is unavailable. The backup AMF and the original AMF are assumed to be in the same AMF set since they have access to the same user equipment (UE) context. Based on that information, one GUAMI is associated with an AMF and optionally with a backup AMF used for planned deletion and / or another (same or different) backup AMF used for failures.

[0062] In Release 16, the binding indication may be used by the AMF to indicate a redundant scope of the UE context. For example, the AMF may provide a binding indication of the UE context to a certain NF (e.g., the Session Management Function (SMF) during Protocol Data Unit (PDU) session establishment), but the backup AMF information may not be properly indicated. As a result, when the AMF fails and the NF needs to reselect an alternative AMF to perform a certain service operation (e.g., N1 / N2 message transfer), the NF may select another AMF within a different AMF set than the designated backup AMF. This behavior is not desired.

[0063] In addition to the above backup AMF, other backup NFs can be deployed. For example, to support geographical redundancy with n nodes as active nodes and m nodes as backup nodes, when an active node fails, the backup node can take over and become active, where n and m are positive integers, for example, n = m in a 1:1 geographical redundancy scenario. As another example, a redundancy model with a memory database or a dynamic hash table creates one or more local backup NFs within the same site while synchronizing data with other NFs in the same set, although in other sites, a persistent database solution (usually with appropriate latency) can be used. In this case, when an NF fails, it is desirable to restore service operations on the local backup NF rather than on the NF in another site.

[0064] Figure 1 is a flowchart showing method 100 according to an embodiment of the present disclosure. Method 100 can be implemented in an NF or a network node implementing the NF.

[0065] In block 110, information, hereinafter referred to as "backup information", indicating the ID of each of one or more backup entities for one or more contexts in the NF, is sent to other NFs. For example, a set of one or more contexts in the NF can correspond to one or more backup entities. In one example, each of the one or more backup entities can be provided with one or more contexts, i.e., the contexts can be made available on each backup entity.

[0066] Here, the backup information is included in the binding instruction or in an instruction separate from the binding instruction. For example, the backup information can be carried in the 3gpp-sbi-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response. Here, the service request, service response, subscription request, subscription response, notification request, or notification response can be sent to other NFs directly or via the SCP.

[0067] Here, one or more backup entities are one or more backup NF instances or one or more backup NF service instances. For example, a new parameter for carrying one or more backup NF instance IDs, for example, "backupnfinst", can be defined in the binding instruction (in the 3gpp-sbi-binding header), and / or a new parameter for carrying one or more backup NF service instance IDs, for example, "backupnfservice", can be defined in the binding instruction (in the 3gpp-sbi-binding header). For example, in the 3gpp-sbi-binding header, TIFF0007684394000003.tif15170

[0068] As a non-limiting example, the backup NF service instance can be in the same NF instance as the current NF service instance for the (one or more) contexts. The backup NF instance can function independently of the NF set, that is, the backup NF instance can be in the same NF set as the current NF instance for the (one or more) contexts, or in a different set, or there may be no NF set at all.

[0069] In another example, one or more backup entities may correspond to the binding level indicated in the binding instruction. For example, the binding level may be set to an NF service instance, and one or more backup entities may be one or more backup service instances; the binding level may be set to an NF service set, and one or more backup entities may be one or more backup NF service sets; the binding level may be set to an NF instance, and one or more backup entities may be one or more backup NF instances; or the binding level may be set to an NF set, and one or more backup entities may be one or more backup NF sets. The (one or more) backup entities can provide redundancy to the binding entity at the binding level. For example, when the binding entity at the binding level is unavailable or unreachable, a backup entity can be selected.

[0070] In particular, Table 1 above can be extended to include a "binding entity" and a binding entity ID (e.g., a (one or more) backup NF service instance ID, a (one or more) backup NF service set ID, a (one or more) backup NF instance ID, or a (one or more) backup NF set ID) as shown in Table 2 below. TIFF0007684394000004.tif206170

[0071] FIG. 2 is a flowchart showing a method 200 according to an embodiment of the present disclosure. The method 200 may be implemented in an NF or a network node implementing the NF.

[0072] In block 210, information hereinafter referred to as "backup information", which indicates the ID of each of one or more backup entities for one or more contexts in other NFs, is received from other NFs. For example, a set of one or more contexts in an NF may correspond to one or more backup entities. In one example, each of the one or more backup entities may be provided with one or more contexts, that is, the contexts may be made available on each backup entity.

[0073] Here, the backup information is included in a binding indication or an indication separate from the binding indication. For example, the backup information may be carried in the 3gpp-sbi-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response.

[0074] Here, the one or more backup entities are one or more backup NF instances or one or more backup NF service instances. For example, new parameters for carrying one or more backup NF instance IDs, such as "backupnfinst", may be defined in the binding indication (in the 3gpp-sbi-binding header), and / or new parameters for carrying one or more backup NF service instance IDs, such as "backupnfservice", may be defined in the binding indication (in the 3gpp-sbi-binding header). For example, in the 3gpp-sbi-binding header, TIFF0007684394000005.tif15170

[0075] The binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. When other NFs are not available, if the NF service set ID is included in the binding instruction and the ID of each of one or more backup NF instances is included in the backup information, the NF may select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or, if the ID of each of one or more backup NF instances is included in the backup information, the NF may select an equivalent NF service instance in one of the one or more backup NF instances.

[0076] For example, when other NFs are not available, the NF may (re)select NF service instances in the following order of decreasing priority. - When the NF service set ID is included in the binding instruction, select an NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the binding instruction, select an equivalent NF service instance in the NF instance indicated by the NF instance ID. - When the NF service set ID is included in the binding instruction and the ID of each of one or more backup NF instances is included in the backup information, select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances. - When the ID of each of one or more backup NF instances is included in the backup information, select an equivalent NF service instance in one of the one or more backup NF instances. - When the NF service set ID and the NF set ID are included in the binding instruction, select an NF service instance in the equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the binding instruction, select an equivalent NF service instance in another NF instance of the NF set.

[0077] Alternatively, when other NFs are not available, the NF may select one of one or more backup NF service instances when the ID of each of the one or more backup NF service instances is included in the backup information. For example, when other NFs are not available, the NF may (re)select NF service instances in the following order of decreasing priority. - When the ID of each of one or more backup NF service instances is included in the backup information, select one of the one or more backup NF service instances. - When the NF service set ID is included in the binding instruction, select an NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the binding instruction, select an equivalent NF service instance in the NF instance indicated by the NF instance ID. - When the NF service set ID and the NF set ID are included in the binding instruction, select an NF service instance in the equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the binding instruction, select an equivalent NF service instance in another NF instance of the NF set.

[0078] In another example, one or more backup entities may correspond to the binding level indicated in the binding instruction. For example, as shown in Table 2 above, the binding level may be set to the NF service instance, and one or more backup entities may be one or more backup service instances; the binding level may be set to the NF service set, and one or more backup entities may be one or more backup NF service sets; the binding level may be set to the NF instance, and one or more backup entities may be one or more backup NF instances; or the binding level may be set to the NF set, and one or more backup entities may be one or more backup NF sets.

[0079] When other NFs are not available, an NF may select one of one or more backup service instances, an NF service instance within one of one or more backup NF service sets, an equivalent NF service instance within one of one or more backup NF instances, or an equivalent NF service instance within one of one or more backup NF sets.

[0080] The binding instruction may include a binding level set to an NF service instance, an NF service set, an NF instance, or an 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. In the re-selection process, when other NFs are not available, the third column in Table 2, i.e., "backup entity", may be selected with a lower priority than the second column but a higher priority than the fourth column. For example, when other NFs are not available, an NF may (re)-select NF service instances in the following order of decreasing priority. - When the NF service set ID is included in the binding instruction, select the NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the binding instruction, select the equivalent NF service instance in the NF instance indicated by the NF instance ID. - Select one of the NF service instances in one of one or more backup service instances, one or more backup NF service sets, the equivalent NF service instances in one of one or more backup NF instances, or the equivalent NF service instances in one of one or more backup NF sets. - When the NF service set ID and the NF set ID are included in the binding instruction, select the NF service instance in the equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the binding instruction, select the equivalent NF service instance in another NF instance of the NF set.

[0081] In one example, the backup information can be sent to the SCP, for example, in a routing binding instruction or in an instruction separate from the routing binding instruction. For example, the backup information can be carried in the 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF. Here, the 3gpp-sbi-routing-binding header can be a copy of the 3gpp-sbi-binding header and may also include backup information.

[0082] Figure 3 is a flowchart showing method 300 according to an embodiment of the present disclosure. Method 300 can be implemented at the SCP or a network node implementing the SCP.

[0083] In block 310, information hereinafter referred to as "backup information", which indicates the ID of each of one or more backup entities for one or more contexts in other NFs, is received from the NF. For example, a set of one or more contexts in the NF may correspond to one or more backup entities. In one example, each of the one or more backup entities may be provided with one or more contexts, that is, the contexts may be made available on each backup entity.

[0084] Here, the backup information is included in a routing binding instruction or an instruction separate from the routing binding instruction. For example, the backup information may be carried in the 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0085] Here, the one or more backup entities are one or more backup NF instances or one or more backup NF service instances. For example, new parameters for carrying one or more backup NF instance IDs, for example, "backupnfinst", may be defined in the routing binding instruction (in the 3gpp-sbi-routing-binding header), and / or new parameters for carrying one or more backup NF service instance IDs, for example, "backupnfservice", may be defined in the routing binding instruction (in the 3gpp-sbi-binding header). For example, in the 3gpp-Sbi-Routing-Binding header. TIFF0007684394000006.tif15170

[0086] A routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. When other NFs are not available, the SCP may select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or may select 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 included in the backup information, if the NF service set ID is included in the routing binding instruction.

[0087] For example, when other NFs are not available, the SCP may (re)select NF service instances in the following order of priority, from highest to lowest. - When the NF service set ID is included in the routing binding instruction, select an NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the routing binding instruction, select an equivalent NF service instance in the NF instance indicated by the NF instance ID. - When the NF service set ID is included in the routing binding instruction and the ID of each of the one or more backup NF instances is included in the backup information, select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances. - When the ID of each of one or more backup NF instances is included in the backup information, select an equivalent NF service instance in one of the one or more backup NF instances. - When the NF service set ID and the NF set ID are included in the routing binding instruction, select an NF service instance in an equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the routing binding instruction, select an equivalent NF service instance in another NF instance of the NF set.

[0088] Alternatively, when other NFs are not available, the SCP may select 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 included in the backup information. For example, when other NFs are not available, the SCP may (re)select NF service instances in descending order of priority as follows. - When the ID of each of one or more backup NF service instances is included in the backup information, select one of the one or more backup NF service instances. - When the NF service set ID is included in the routing binding instruction, select an NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the routing binding instruction, select an equivalent NF service instance in the NF instance indicated by the NF instance ID. - When the NF service set ID and the NF set ID are included in the routing binding instruction, select an NF service instance in an equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the routing binding instruction, select an equivalent NF service instance in another NF instance of the NF set.

[0089] In another example, one or more backup entities may correspond to the binding level indicated in the routing binding instruction. For example, as shown in Table 2 above, the binding level may be set to the NF service instance, and one or more backup entities may be one or more backup service instances; the binding level may be set to the NF service set, and one or more backup entities may be one or more backup NF service sets; the binding level may be set to the NF instance, and one or more backup entities may be one or more backup NF instances; or the binding level may be set to the NF set, and one or more backup entities may be one or more backup NF sets.

[0090] When other NFs are not available, the SCP may select an NF service instance in one of one or more backup service instances, one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets.

[0091] The routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. In the reselection process, when other NFs are not available, the third column in Table 2, i.e., the "backup entity", can be selected with a lower priority than the second column but a higher priority than the fourth column. For example, when other NFs are not available, the SCP may (re)select NF service instances in the following order of decreasing priority. - When the NF service set ID is included in the routing binding instruction, select an NF service instance in the NF service set indicated by the NF service set ID. - When the NF instance ID is included in the routing binding instruction, select an equivalent NF service instance in the NF instance indicated by the NF instance ID. - Select one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets. - When the NF service set ID and the NF set ID are included in the routing binding instruction, select an NF service instance in an equivalent NF service set of another NF instance of the NF set. - When the NF set ID is included in the routing binding instruction, select an equivalent NF service instance in another NF instance of the NF set.

[0092] In the following, the above methods 100 to 300 will be further described with reference to the exemplary examples shown in FIGS. 4 to 5.

[0093] Figure 4 is a sequence diagram showing an exemplary process for providing a backup entity ID according to an embodiment of the present disclosure.

[0094] In 4.1, NF B sends a service request for resource creation or modification to NF A. In 4.2, NF A sends a service response to NF B that includes a binding instruction, i.e., a 3gpp-Sbi-Binding header with bl=nf-set, nfset=NF-Set1-ID, backupnfinst=NF1-Instance-ID, where NF-Set1-ID is the NF set ID of the NF set (in this case, NF set 1), NF1-Instance-ID is the NF instance ID of the backup NF instance (in this case, NF 1), and NF A and NF 1 belong to NF set 1. In 4.3, NF B sends a subsequent service request to NF A, but it is found that NF A is not available. In this case, in 4.4, NF B reselects an NF service instance (NF 1) in the equivalent NF service set of the backup NF instance. In 4.5, NF B sends the service request to NF 1, and in 4.6, the resource is recovered at NF 1. In 4.7, NF 1 sends a service response to NF B that includes a binding instruction, i.e., a 3gpp-Sbi-Binding header with bl=nf-set, nfset=NF-Set1-ID, backupnfinst=NF2-Instance-ID, where NF2-Instance-ID is the NF instance ID of the backup NF instance (in this case, NF 2), and NF 2 belongs to NF set 1.

[0095] Figure 5 is a sequence diagram showing an exemplary process for providing a backup entity ID according to an embodiment of the present disclosure.

[0096] In 5.1, NF B sends a service request for resource creation or modification to NF A via SCP. In 5.2, NF A sends a service response to NF B via SCP, which contains a binding instruction, i.e., a 3gpp-Sbi-Binding header with bl=nf-set, nfset=NF-Set1-ID, backupnfinst=NF1-Instance-ID, where NF-Set1-ID is the NF set ID of the NF set (in this case, NF set 1), NF1-Instance-ID is the NF instance ID of the backup NF instance (in this case, NF 1), and NF A and NF 1 belong to NF set 1. In 5.3, NF B sends a subsequent service request to SCP for forwarding to NF A, and the service request contains a routing binding instruction, i.e., a 3gpp-Sbi-Routing-Binding header with bl=nf-set, nfset=NF-Set1-ID, backupnfinst=NF1-Instance-ID, but SCP finds that NF A is not available. In this case, in 5.4, SCP reselects an NF service instance (NF 1) in the equivalent NF service set of the backup NF instance. In 5.5, SCP sends the service request to NF 1, and in 5.6, the resource is restored at NF 1. In 5.7, NF 1 sends a service response to NF B via SCP, which contains a binding instruction, i.e., a 3gpp-Sbi-Binding header with bl=nf-set, nfset=NF-Set1-ID, backupnfinst=NF2-Instance-ID, where NF2-Instance-ID is the NF instance ID of the backup NF instance (in this case, NF 2), and NF 2 belongs to NF set 1.

[0097] Corresponding to method 100 described above, a network node is provided. FIG. 6 is a block diagram of a network node 600 according to an embodiment of the present disclosure. The network node 600 can be configured to implement an NF.

[0098] As shown in FIG. 6, the network node 600 includes a transmission unit 610 configured to transmit, to other NFs, information indicating the 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 an indication separate 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.

[0099] In one embodiment, the one or more backup entities may correspond to a binding level indicated in the binding indication.

[0100] In one embodiment, the binding level may be set to an NF service instance, and the one or more backup entities may be one or more backup service instances; the binding level may be set to an NF service set, and the one or more backup entities may be one or more backup NF service sets; the binding level may be set to an NF instance, and the one or more backup entities may be one or more backup NF instances; or the binding level may be set to an NF set, and the one or more backup entities may be one or more backup NF sets.

[0101] In one embodiment, the information may be 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.

[0102] In one embodiment, the service request, the service response, the subscription request, the subscription response, the notification request, or the notification response may be transmitted to other NFs directly or via an SCP.

[0103] In one embodiment, each of one or more backup entities may provide one or more contexts.

[0104] Unit 610 can be implemented as a pure hardware solution or as a combination of software and hardware, for example, a processor or microprocessor and sufficient software, and memory for software storage, a programmable logic device (PLD), or one or more of the other electronic components or processing circuits described above and configured to perform actions, for example, as shown in FIG. 1.

[0105] Corresponding to the method 200 described above, a network node is provided. FIG. 7 is a block diagram of a network node 700 according to one embodiment of the present disclosure. The network node 700 can be configured to implement an NF.

[0106] As shown in FIG. 7, the network node 700 includes a receiving unit 710 configured to receive from other NFs information indicating the ID of each of one or more backup entities for one or more contexts in the other NFs. The information is included in a binding indication or an indication separate 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.

[0107] In one embodiment, the binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The network node 700 may further include a selection unit configured to select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or select an equivalent NF service instance in one of the one or more backup NF instances, when the NF service set ID is included in the binding instruction and the ID of each of the one or more backup NF instances is included in the information, when other NFs are not available.

[0108] In one embodiment, the selection unit may be configured to select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or select an equivalent NF service instance in one of the one or more backup NF instances, with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction.

[0109] In one embodiment, the selection unit may be configured to select an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or an equivalent NF service instance in one of the one or more backup NF instances, with a higher priority than selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set or an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the binding instruction.

[0110] In one embodiment, the network node 700 may further include a selection unit configured to select one of the one or more backup NF service instances when other NFs are not available and when the ID of each of the one or more backup NF service instances is included in the information.

[0111] In one embodiment, the binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. When the NF service set ID is included in the binding instruction, the selection unit selects one of the one or more backup NF service instances, selects an NF service instance in the NF service set indicated by the NF service set ID, when the NF instance ID is included in the binding instruction, selects an equivalent NF service instance in the NF instance indicated by the NF instance ID, when the NF service set ID and the NF set ID are included in the binding instruction, selects an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or, when the NF set ID is included in the binding instruction, may be set to perform with a higher priority than selecting an equivalent NF service instance in another NF instance of the NF set.

[0112] In one embodiment, one or more backup entities may correspond to the binding level indicated in the binding instruction.

[0113] In one embodiment, the binding level can be set for an NF service instance, and the one or more backup entities can be one or more backup service instances; the binding level can be set for an NF service set, and the one or more backup entities can be one or more backup NF service sets; the binding level can be set for an NF instance, and the one or more backup entities can be one or more backup NF instances; or the binding level can be set for an NF set, and the one or more backup entities can be one or more backup NF sets.

[0114] In one embodiment, the network node 700 may further include a selection unit configured to select one of the one or more backup service instances, an NF service instance in one of the one or more backup NF service sets, an equivalent NF service instance in one of the one or more backup NF instances, or an equivalent NF service instance in one of the one or more backup NF sets when other NFs are not available.

[0115] In one embodiment, the binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. When the NF service set ID is included in the binding instruction, the selection unit selects one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets, and / or when the NF instance ID is included in the binding instruction, the selection unit selects an equivalent NF service instance in the NF instance indicated by the NF instance ID with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID.

[0116] In one embodiment, when the NF service set ID and the NF set ID are included in the binding instruction, the selection unit selects one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets, and / or when the NF set ID is included in the binding instruction, the selection unit selects an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or selects an equivalent NF service instance in another NF instance of the NF set with a higher priority than selecting an equivalent NF service instance in another NF instance of the NF set.

[0117] In one embodiment, the information may be carried in a 3gpp-sbi-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response.

[0118] In one embodiment, the network node 700 may further include a transmission unit configured to transmit information to the SCP.

[0119] In one embodiment, the information may be included in a routing binding instruction, or an instruction separate from the routing binding instruction.

[0120] In one embodiment, the information may be carried in a 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0121] In one embodiment, each of the one or more backup entities may be provided with one or more contexts.

[0122] Unit 710 may be implemented as a pure hardware solution, or as a combination of software and hardware, for example, a processor or microprocessor and sufficient software, and memory for software storage, a programmable logic device (PLD), or one or more of the other electronic components or processing circuits described above and configured to perform actions, for example, as shown in FIG. 2.

[0123] Corresponding to the method 300 described above, a network node is provided. FIG. 8 is a block diagram of a network node 800 according to an embodiment of the present disclosure. The network node 800 may be configured to implement the SCP.

[0124] As shown in FIG. 8, the network node 800 includes a receiving unit 810 configured to receive from an NF information indicating identifiers of each of one or more backup entities for one or more contexts in other NFs. The information is included in a routing binding instruction or an instruction separate from the routing binding instruction. The one or more backup entities are one or more backup NF instances or one or more backup NF service instances.

[0125] In one embodiment, the routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. When other NFs are not available, the network node 800 may further include a selection unit configured to select 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 included in the routing binding instruction and the ID of each of the one or more backup NF instances is included in the information, or to select 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 included in the routing binding instruction.

[0126] In one embodiment, when the NF service set ID is included in the routing binding instruction, the selection unit selects an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or selects an equivalent NF service instance in one of the one or more backup NF instances, and / or when the NF instance ID is included in the routing binding instruction, the selection unit is set to perform the selection of an equivalent NF service instance in the NF instance indicated by the NF instance ID with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID.

[0127] In one embodiment, when the NF service set ID and the NF set ID are included in the routing binding instruction, the selection unit selects an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or when the NF set ID is included in the routing binding instruction, the selection unit is set to perform the selection of an equivalent NF service instance in another NF instance of the NF set with a higher priority than selecting an equivalent NF service instance in one of the one or more backup NF instances, or selecting an equivalent NF service instance in one of the one or more backup NF instances.

[0128] In one embodiment, when other NFs are not available, the network node 800 may further include a selection unit configured to select 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 included in the information.

[0129] In one embodiment, the routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The selection unit selects one of one or more backup NF service instances, selects an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction, selects an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction, selects 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 included in the routing binding instruction, and / or may be set to perform with a higher priority than selecting an equivalent NF service instance in another NF instance of the NF set when the NF set ID is included in the routing binding instruction.

[0130] In one embodiment, one or more backup entities may correspond to the binding level indicated in the routing binding instruction.

[0131] In one embodiment, the binding level can be set for an NF service instance, and one or more backup entities can be one or more backup service instances; the binding level can be set for an NF service set, and one or more backup entities can be one or more backup NF service sets; the binding level can be set for an NF instance, and one or more backup entities can be one or more backup NF instances; or the binding level can be set for an NF set, and one or more backup entities can be one or more backup NF sets.

[0132] In one embodiment, the network node 800 may further include a selection unit configured to select one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets when other NFs are not available.

[0133] In one embodiment, the routing binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. When the NF service set ID is included in the routing binding instruction, the selection unit selects one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets, selects an NF service instance in the NF service set indicated by the NF service set ID, and / or when the NF instance ID is included in the routing binding instruction, is set to perform with a lower priority than selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID.

[0134] In one embodiment, when the NF service set ID and the NF set ID are included in the routing binding instruction, the selection unit selects one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets, selects an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or when the NF set ID is included in the routing binding instruction, is set to perform with a higher priority than selecting an equivalent NF service instance in another NF instance of the NF set.

[0135] In one embodiment, the information may be carried in the 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0136] In one embodiment, each of one or more backup entities may be provided with one or more contexts.

[0137] Unit 810 may be implemented as a pure hardware solution or as a combination of software and hardware, for example, a processor or microprocessor and sufficient software, and memory for software storage, a programmable logic device (PLD), or one or more of the other electronic components or processing circuits described above and configured to perform actions, for example, as shown in FIG. 3.

[0138] FIG. 9 is a block diagram of a network node 900 according to another embodiment of the present disclosure.

[0139] Network node 900 includes a communication interface 910, a processor 920, and a memory 930.

[0140] Memory 930 may contain instructions executable by processor 920, whereby network node 900 is operable to perform actions of the procedures previously described together with FIG. 1 when implementing an NF. Specifically, memory 930 may contain instructions executable by processor 920, whereby network node 900 is operable to send to other NFs information indicating the ID of each of one or more backup entities for one or more contexts in the NF when implementing the NF. The information is included in a binding indication or in an indication separate 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.

[0141] In one embodiment, the one or more backup entities may correspond to the binding level indicated in the binding indication.

[0142] In one embodiment, the binding level may be set to an NF service instance, and the one or more backup entities may be one or more backup service instances; the binding level may be set to an NF service set, and the one or more backup entities may be one or more backup NF service sets; the binding level may be set to an NF instance, and the one or more backup entities may be one or more backup NF instances; or the binding level may be set to an NF set, and the one or more backup entities may be one or more backup NF sets.

[0143] In one embodiment, the information may be carried in the 3gpp-sbi-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response.

[0144] In one embodiment, a service request, service response, subscription request, subscription response, notification request, or notification response can be sent directly or via an SCP to another NF.

[0145] In one embodiment, each of one or more backup entities can provide one or more contexts.

[0146] Alternatively, memory 930 may contain instructions executable by processor 920, whereby network node 900 is operable to perform actions of the procedures previously described, for example, with FIG. 2, when implementing an NF. Specifically, memory 930 may contain instructions executable by processor 920, whereby network node 900 is operable to receive, from another NF, information indicating the ID of each of one or more backup entities for one or more contexts in the other NF when implementing an NF. The information is included in a binding indication or an indication separate 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.

[0147] In one embodiment, the binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The memory 930 may further include instructions executable by the processor 920, whereby the network node 900, when other NFs are not available, selects 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 included in the binding instruction and the ID of each of the one or more backup NF instances is included in the information, or selects 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 included in the information, and is operable to perform such operations.

[0148] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of the one or more backup NF instances, may be performed with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction.

[0149] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of the one or more backup NF instances, may be 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 and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the binding instruction.

[0150] In one embodiment, memory 930 may further include instructions executable by processor 920, whereby network node 900 is operable to select 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 included in the information when other NFs are not available.

[0151] In one embodiment, the binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The operation of selecting one of the one or more backup NF service instances may be to select an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, to select an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction, to select 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 included in the binding instruction, and / or to select an equivalent NF service instance in another NF instance of the NF set with a higher priority than when the NF set ID is included in the binding instruction.

[0152] In one embodiment, one or more backup entities may correspond to the binding level indicated in the binding instruction.

[0153] In one embodiment, the binding level may be set to an NF service instance, and one or more backup entities may be one or more backup service instances; the binding level may be set to an NF service set, and one or more backup entities may be one or more backup NF service sets; the binding level may be set to an NF instance, and one or more backup entities may be one or more backup NF instances; or the binding level may be set to an NF set, and one or more backup entities may be one or more backup NF sets.

[0154] In one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900 is operative to select one of one or more backup service instances, an NF service instance within one of one or more backup NF service sets, an equivalent NF service instance within one of one or more backup NF instances, or an equivalent NF service instance within one of one or more backup NF sets when other NFs are not available.

[0155] In one embodiment, the binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. The operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be performed with lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the binding instruction, and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the binding instruction.

[0156] In one embodiment, the operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be performed with higher priority than selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the binding instruction.

[0157] In one embodiment, the information may be carried in the 3gpp-sbi-binding header in a service request, a service response, a subscription request, a subscription response, a notification request, or a notification response.

[0158] In one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900 is operable to send information to the SCP.

[0159] In one embodiment, the information may be included in a routing binding instruction, or in an instruction separate from the routing binding instruction.

[0160] In one embodiment, the information may be carried in a 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0161] In one embodiment, each of the one or more backup entities may be provided with one or more contexts.

[0162] Alternatively, the memory 930 may include instructions executable by the processor 920, whereby the network node 900 is operable to perform the actions of the procedure previously described with FIG. 3, for example, when implementing the SCP. Specifically, the memory 930 may include instructions executable by the processor 920, whereby the network node 900 is operable to receive, from an NF, information indicating identifiers of each of the one or more backup entities for one or more contexts in another NF when implementing the SCP. The information is included in a routing binding instruction, or in an instruction separate from the routing binding instruction. The one or more backup entities are one or more backup NF instances or one or more backup NF service instances.

[0163] In one embodiment, the routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. Memory 930 may further include instructions executable by processor 920, whereby network node 900, when other NFs are not available, selects 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 included in the routing binding instruction and the ID of each of the one or more backup NF instances is included in the information, or selects 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 included in the routing binding instruction, and is operable to do so.

[0164] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of the one or more backup NF instances, may be performed with a lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction.

[0165] In one embodiment, the operation of selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or the operation of selecting an equivalent NF service instance in one of the one or more backup NF instances, may be 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 and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the routing binding instruction.

[0166] In one embodiment, the memory 930 may further include instructions executable by the processor 920, whereby the network node 900 is operable to select 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 included in the information when other NFs are not available.

[0167] In one embodiment, the routing binding instruction may include a binding level set for an NF service instance, an NF service set, an NF instance, or an 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. The operation of selecting one of the one or more backup NF service instances may be to select an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction, to select an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction, to select 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 included in the routing binding instruction, and / or may be performed with a higher priority than selecting an equivalent NF service instance in another NF instance of the NF set when the NF set ID is included in the routing binding instruction.

[0168] In one embodiment, the one or more backup entities may correspond to the binding level indicated in the routing binding instruction.

[0169] In one embodiment, the binding level can be set for an NF service instance, and the one or more backup entities can be one or more backup service instances; the binding level can be set for an NF service set, and the one or more backup entities can be one or more backup NF service sets; the binding level can be set for an NF instance, and the one or more backup entities can be one or more backup NF instances; or the binding level can be set for an NF set, and the one or more backup entities can be one or more backup NF sets.

[0170] In one embodiment, memory 930 may further include instructions executable by processor 920, whereby network node 900 is operative to select one of the one or more backup service instances, an NF service instance in one of the one or more backup NF service sets, an equivalent NF service instance in one of the one or more backup NF instances, or an equivalent NF service instance in one of the one or more backup NF sets when other NFs are not available.

[0171] In one embodiment, the routing binding instruction may include one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. The operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be performed with lower priority than selecting an NF service instance in the NF service set indicated by the NF service set ID when the NF service set ID is included in the routing binding instruction and / or selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID when the NF instance ID is included in the routing binding instruction.

[0172] In one embodiment, the operation of selecting one of one or more backup service instances, an NF service instance in one of one or more backup NF service sets, an equivalent NF service instance in one of one or more backup NF instances, or an equivalent NF service instance in one of one or more backup NF sets may be performed with higher priority than selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set and / or selecting an equivalent NF service instance in another NF instance of the NF set when the NF service set ID and the NF set ID are included in the routing binding instruction and when the NF set ID is included in the routing binding instruction.

[0173] In one embodiment, the information may be carried in the 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to another NF.

[0174] In one embodiment, each of the one or more backup entities may be provided with one or more contexts.

[0175] The present disclosure also provides at least one computer program product in the form of a non-volatile or volatile memory, such as a non-transitory computer-readable storage medium, an electrically erasable programmable read-only memory (EEPROM), a flash memory, and a hard drive. The computer program product includes a computer program. The computer program includes code / computer-readable instructions that, when executed by a processor 920, cause the network node 900 to perform the actions of the procedures described previously, for example, with FIGS. 1, 2, or 3.

[0176] The computer program product may be set as computer program code structured in computer program modules. The computer program modules can essentially perform the actions of the flows shown in FIGS. 1, 2, or 3.

[0177] The processor can be a single CPU (Central Processing Unit), but can also include two or more processing units. For example, the processor can include a general-purpose microprocessor, an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor such as an application-specific integrated circuit (ASIC). The processor can also include board memory for caching purposes. The computer program can be carried in a computer program product connected to the processor. The computer program product can include a non-transitory computer-readable storage medium in which the computer program is stored. For example, the computer program product can be a flash memory, a random access memory (RAM), a read-only memory (ROM), or an EEPROM, and in alternative embodiments, the computer program modules described above can be distributed over different computer program products in the form of memory.

[0178] The present disclosure has been described above with reference to embodiments of the present disclosure. It should be understood that various modifications, alternations, and additions can be made by those skilled in the art without departing from the spirit and scope of the present disclosure. Accordingly, the scope of the present disclosure is not limited to the specific embodiments described above, but is defined only by the appended claims.

[0179] The present disclosure further includes the following embodiments based on 3GPP TS29.500.

[0180] 5.2.3.2.5 3gpp-Sbi-Routing-Binding This header includes a routing binding instruction used to direct a service request with a target NF service resource context to an HTTP server (see Section 6.12). The encoding of the header follows the ABNF defined in IETF RFC7230

[12] . The following parameters are defined for TIFF0007684394000007.tif35170. - bl (Binding Level): The value of this parameter (blvalue) indicates the preferred binding to a binding entity, i.e., any of an NF instance, NF set, NF service instance, or NF service set. When the binding level is set to an NF service instance (nfservice-instance), either the NF service set ID or the NF instance ID shall also be present to uniquely identify the NF service instance. - nfinst (NF Instance): Indicates the NF instance ID defined in section 5.2.2.2.2 of 3GPP TS 29.510 [8]. This parameter shall be present when the binding level is set to "nf-instance" or when the binding level is set to "nfservice-instance", and the nfserviceset parameter shall not be included. - nfset (NF Set): Indicates the NF set ID defined in section 28.12 of 3GPP TS 23.003

[15] . This parameter shall be present when the binding level is set to "nf-set". This parameter may be present in other cases (see section 6.12.1). - nfservinst (NF Service Instance): Indicates the NF service instance ID. This parameter shall be present when the binding level is set to "nfservice-instance". - nfserviceset (NF Service Set): Indicates the NF service set ID defined in section 28.13 of 3GPP TS 23.003

[15] . This parameter shall be present when the binding level is set to "nfservice-set". This parameter may be present when the binding level is set to "nfservice-instance" (see section 6.12.1). - servname (Service Name): The name of the service defined in 3GPP TS29.510 [8], or indicates a custom service that handles notifications or callback requests. It may be present in the routing binding indication in a notification or callback request. - backupnfinst (Backup NF Instance): Indicates the NF instance ID (as defined in section 5.2.2.2.2 of 3GPP TS29.510 [8]) of a backup NF (e.g., the backup AMF specified in 3GPP TS23.501 [3]). For the "token" type specification, refer to section 3.2.6 of IETF RFC7230

[12] . The value of the token is a string that contains the binding entity ID or service name. Example 1: Binding to SMF set 1 with MCC345 and MNC012. TIFF0007684394000008.tif9170 Example 2: Binding to an SMF instance within the SMF set of Example 1. TIFF0007684394000009.tif13170 Example 3: Binding to the SMF service set "xyz" within the SMF instance within the SMF set of Example 1. TIFF0007684394000010.tif19170 Example 4: Binding to AMF set 1 within AMF area 48 (hexadecimal). TIFF0007684394000011.tif9170 Example 5: Subscription (i.e., notification request) to AMF set 1 within AMF area 48 (hexadecimal) and binding for the Namf_Communication service. TIFF0007684394000012.tif12170 Example 6: Binding to AMF set 1 within AMF area 48 (hexadecimal) with a backup AMF. TIFF0007684394000013.tif12170

[0181] 5.2.3.2.6 3gpp-Sbi-Binding This header contains a comma-separated list of binding instructions from the HTTP server for storage by the HTTP client and subsequent use (see clause 6.12). The encoding of the header follows the ABNF defined in IETF RFC7230

[12] . The following parameters are defined for TIFF0007684394000014.tif40170 and below. - scope: Indicates the applicability of the binding instruction in the service request. This can take one of the following values. - “other-service”: The binding information applies to (one or more) other services that the NF service consumer may later provide as an NF service producer (see clause 6.12.3). - “subscription-events”: The binding information applies to subscription change event notifications (see clause 6.12.4). - “callback”: The binding information applies to notifications or callback requests (see clause 6.12.4 and clause 6.12.5). The absence of this parameter in the binding instruction in the service request shall be interpreted as “callback”. When the binding information applies to notification / callback requests and to other services, two scope parameters may be present in the binding instruction. - servname (service name): The name of the service defined in 3GPP TS29.510 [8], or a custom service, i.e., - the name of the service handling the notification or callback request when present in the binding instruction for the subscription or callback, i.e., when the scope parameter is absent or set to “callback”, or - Indicates the name(s) of the other service(s) to which the binding applies when present in the binding instruction in the service request for other services that the NF service consumer may later provide as an NF service producer, i.e., when the scope parameter is set to "other-service". More than one servname parameter may exist to represent multiple such services. Absence of this parameter in the binding instruction where the scope parameter is set to "other-service" shall be interpreted as binding information applicable to all services that the NF service consumer may later provide as an NF service producer. - recoverytime: Indicates the recovery timestamp of the entity corresponding to the highest level of resilience supported for the resource, i.e., the binding entity at a higher level than that indicated in the binding instruction. See Table 6.3.1.0-1 of 3GPP TS23.501 [3] and section 6.1 of 3GPP TS23.527

[38] . The date-time type is specified in IETF RFC5322

[37] and section 7.1.1.1 of IETF RFC7231

[11] . - See section 5.2.3.2.5 for the definition and encoding of blvalue, nfinst, backupnfinst, nfset, nfservinst, and nfserviceset. Examples 1 to 5: Same as Examples 1 to 5 defined in section 5.2.3.2.5, with the header name "3gpp-Sbi-Binding" instead of "3gpp-Sbi-Routing-Binding". Example 6: A subscription request from one NF for another NF with two binding instructions. TIFF0007684394000015.tifExample 7: A service request with two binding instructions regarding a callback request and other services that an NF service consumer may later provide as an NF service producer. TIFF0007684394000016.tifExample 8: A service request with one binding instruction applied to a notification / callback request and any other service that an NF service consumer may later provide as an NF service producer. TIFF0007684394000017.tifExample 9: A service request with one binding instruction applied to a notification / callback request along with a restoration timestamp related to the NF set indicated in the binding instruction, and with the binding level set to "nfset". TIFF0007684394000018.tifExample 10: A service response with one binding instruction applied to a session context, accompanied by a restoration timestamp related to the NF set indicated in "nfset" in the binding instruction, and with the binding level set to "nfinstance". TIFF0007684394000019.tifExample 11: A service response with one binding instruction applied to a session context, accompanied by a restoration timestamp related to the NF instance included in the binding instruction, and with the binding level set to nfserviceinstance. TIFF0007684394000020.tifNote: Examples 6 and 7 are formatted as two separate headers (this improves readability), but Examples 6 and 7 can also be formatted as a single header with two binding instruction values separated by commas. 6.12 Binding between an NF service consumer and an NF service resource 6.12.1 Overview Binding instructions for NF service resources can be provided to the NF service consumer of the resources as part of a direct or indirect communication procedure so that they can be used in subsequent related service requests. This enables the NF service resource owner to instruct the NF service consumer on which NF service instance, NF instance, NF service set, or NF set the NF service consumer should be bound to for a particular resource. See section 6.3.1.0 of 3GPP TS23.501 [3] and section 4.17.12 of 3GPP TS23.502 [4]. The binding can be established or updated as part of the following. 1) For any API that defines a resource, a service response that creates or modifies this resource (see section 4.17.12.2 of 3GPP TS23.502 [4]) that should be used for subsequent requests targeting the resource. 2) If the NF service consumer can also act as an NF service producer for subsequent communication from the contacted NF service producer, a service request (see section 4.17.12.3 of 3GPP TS23.502 [4]) that should be used for subsequent service requests initiated by the contacted NF service producer. 3) A service request that creates or modifies an explicit or implicit subscription, or is part of a notification response, that should be used for subsequent notification requests initiated by the NF service producer (see section 4.17.12.3 of 3GPP TS23.502 [4]). 4) A service response that creates an implicit or explicit subscription, or updates a subscription, or is part of a notification request, that should be used for subsequent operations on the subscription (see section 4.17.12.4 of 3GPP TS23.502 [4]). Callback resources (e.g., V-SMF or I-SMF callback URIs sent to H-SMF or SMF) other than notifications should be created for subsequent callback requests (e.g., H-SMF or SMF initiated PDU session modification) to be used by the NF service producer, or service requests as part of the callback response. Two types of binding information are defined to manage the binding between the NF service consumer and the NF service resource. 1) The binding indication conveys binding information about a resource, which must be stored by the consumer (client) of that resource and used by the client to direct future requests to that resource. When included in a service request, the binding information relates to a resource owned by the NF service consumer for the current transaction. When included in a service response, the binding information relates to a resource owned by the NF service producer for the current transaction. 2) The routing binding indication conveys binding information for directing requests with context from the client to the server. The routing binding indication shall be included only in HTTP requests. The same service request can, for example, - Provide bindings for notifications or callbacks (i.e., bullet 3 or 5) and for other services that the NF service consumer may later provide as an NF service producer (i.e., bullet 2), or - Provide binding information for different event notifications when creating a subscription for another NF by transmitting two or more binding indications (see clause 6.12.4). The scope parameter in the binding indication during service request identifies the applicability of the binding information (i.e., the scenario related to the binding information). The service request may use the 3gpp-Sbi-Binding header to convey one or more binding indications as described above and / or, for example, use the 3gpp-Sbi-Routing-Binding header to include a binding routing indication for routing the request to an appropriate set of NF service producers or to an appropriate service set of NF service producers. The service response may use the 3gpp-sbi-Binding header to convey a binding indication about the resource. Note 1: An HTTP request may include, for example, one 3gpp-Sbi-Binding header containing two binding indications for other services and for callbacks, and one 3gpp-Sbi-Routing-Binding header for conveying a routing binding indication. If the SCP receives a routing binding indication in a service or notification request and decides to forward that request to the next-hop SCP, the SCP shall include the routing binding indication in the request being forwarded. The SCP shall remove the routing binding indication if the SCP forwards that request to the target NF. The binding indication and the routing binding indication shall include the binding level and one or more binding entity IDs representing all NF service instances that are capable of serving the service request targeting the resource, i.e., sharing the same resource context. The binding level indicates the preferred binding to either an NF instance, NF set, NF service instance, or NF service set. When sending a request to target a resource, the binding entity corresponding to the binding level shall be selected whenever possible. If this is not possible, for example, because the preferred binding entity is not reachable, the request shall be sent to the other binding entities signaled in the binding indication or routing binding indication, in the following order of precedence: - If the NF service set ID is signaled in the binding indication or routing binding indication, select an NF service instance in the same NF service set. - If the NF instance ID is signaled in the binding indication or routing binding indication, select an equivalent NF service instance in the same NF instance. - If the NF service set ID and backup NF instance ID are signaled in the binding indication or routing binding indication, select an NF service instance in the equivalent NF service set of the backup NF instance. - If the backup NF instance ID is signaled in the binding indication or routing binding indication, select an equivalent NF service instance in the backup NF instance. - If the NF service set ID and NF set ID are signaled in the binding indication or routing binding indication, select an NF service instance in the equivalent NF service set of another NF instance of the NF set. - If the NF set ID is signaled in the binding indication or routing binding indication, select an equivalent NF service instance in another NF instance of the NF set. Note 2: NF service instances from different NF instances are equivalent NF service instances if the NF service instances from different NF instances share the same MCC, MNC, (in the case of SNPN) NID, ServiceName, API version, and, if applicable, NF service set ID (see clause 28.13 of 3GPP TS23.003

[15] ). The binding indication shall not be used if a particular resource can only be served by a particular NF service instance of an NF instance, i.e., if NF service instances of the same NF service cannot share resources within the NF instance. Resources for which no binding indication or routing binding indication is signaled shall be considered to be exclusively bound to one NF service instance, unless the NF service resource owner instance is part of an NF set (or AMF set) or NF service set, or unless its NF profile in the NRF indicates that it supports NF service persistence within the NF instance (see clause 6.5 of 3GPP TS23.527

[38] ).

Claims

1. A method (200) 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 an indication separate 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 includes a binding level set for an NF service instance, an NF service set, an NF instance, or an 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; wherein the method, when the other NF is unavailable, selects, with a lower priority than and / or, - when the NF service set ID is included in the binding indication, an NF service instance in the NF service set indicated by the NF service set ID, and / or - when the NF instance ID is included in the binding indication, an equivalent NF service instance in the NF instance indicated by the NF instance ID; and / or selects, with a higher priority than, - when the NF service set ID and the NF set ID are included in the binding indication, an NF service instance in an equivalent NF service set of other NF instances of the NF set, and / or - when the NF set ID is included in the binding indication, an equivalent NF service instance in other NF instances of the NF set; one of the following (1) or (2), that is, (1) when the NF service set ID is included in the binding indication and the ID of each of the one or more backup NF instances is included in the information, selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or ​ When the ID of each of the one or more backup NF instances is included in the information, selecting an equivalent NF service instance in one of the one or more backup NF instances performing, and / or - when the NF service set ID is included in the binding instruction, selecting an NF service instance in the NF service set indicated by the NF service set ID, when the NF instance ID is included in the binding instruction, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID, when the NF service set ID and the NF set ID are included in the binding instruction, selecting an NF service instance in an equivalent NF service set of other NF instances of the NF set, and / or when the NF set ID is included in the binding instruction, selecting an equivalent NF service instance in other NF instances of the NF set with a higher priority than (3)When the ID of each of the one or more backup NF service instances is included in the information, selecting one of the one or more backup NF service instances further comprising or the one or more backup entities correspond to the binding level indicated in the binding instruction, the binding level is set for an NF service instance, and the one or more backup entities are one or more backup service instances, the binding level is set for an NF service set, and the one or more backup entities are one or more backup NF service sets, the binding level is set for an NF instance, and the one or more backup entities are one or more backup NF instances, or the binding level is set for an NF set, and the one or more backup entities are one or more backup NF sets, The binding instruction includes one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID, The method is when the other NF is not available, - When the NF service set ID is included in the binding instruction, selecting an NF service instance in the NF service set indicated by the NF service set ID, and / or When the NF instance ID is included in the binding instruction, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID With a lower priority, and / or - When the NF service set ID and the NF set ID are included in the binding instruction, selecting an NF service instance in an equivalent NF service set of other NF instances of the NF set, and / or When the NF set ID is included in the binding instruction, selecting an equivalent NF service instance in other NF instances of the NF set With a higher priority, (4) Selecting 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 Further including, Method (200).

2. The method (200) according to 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. Further including transmitting the information to a service communication proxy (SCP), wherein the information is included in a routing binding instruction, or an instruction separate from the routing binding instruction, or ​ The information is carried in a 3gpp-sbi-routing-binding header in a service request, service response, subscription request, subscription response, notification request, or notification response addressed to the other NF. The method (200) according to claim 1 or 2.

4. A method (300) in a network node implementing a service communication proxy (SCP), comprising: Receiving (310) 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. Including The information is included in a routing binding instruction or an instruction separate from the routing binding instruction. The one or more backup entities are one or more backup NF instances or one or more backup NF service instances. The routing binding instruction includes one or more of an NF service instance ID, an NF service set ID, an NF instance ID, or an NF set ID. The method is when the other NF is not available, - When the NF service set ID is included in the routing binding instruction, selecting an NF service instance in the NF service set indicated by the NF service set ID, and / or When the NF instance ID is included in the routing binding instruction, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID With a lower priority and / or - When the NF service set ID and the NF set ID are included in the routing binding instruction, selecting an NF service instance in an equivalent NF service set of other NF instances of the NF set, and / or When the NF set ID is included in the routing binding instruction, selecting an equivalent NF service instance in other NF instances of the NF set With a higher priority, the following (1) or (2), that is, When the NF service set ID is included in the routing binding instruction and the ID of each of the one or more backup NF instances is included in the information, selecting an NF service instance in an equivalent NF service set of one of the one or more backup NF instances, or When the ID of each of the one or more backup NF instances is included in the information, selecting an equivalent NF service instance in one of the one or more backup NF instances performing, and / or - When the NF service set ID is included in the routing binding instruction, selecting an NF service instance in the NF service set indicated by the NF service set ID, When the NF instance ID is included in the routing binding instruction, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID, When the NF service set ID and the NF set ID are included in the routing binding instruction, selecting an NF service instance in an equivalent NF service set of another NF instance of the NF set, and / or When the NF set ID is included in the routing binding instruction, selecting an equivalent NF service instance in another NF instance of the NF set with a higher priority than (3) When the ID of each of the one or more backup NF service instances is included in the information, selecting one of the one or more backup NF service instances further comprising, or the one or more backup entities correspond to the binding level indicated in the routing binding instruction, the binding level is set to an NF service instance, and the one or more backup entities are one or more backup service instances The binding level is set to an NF service set, and the one or more backup entities are one or more backup NF service sets, the binding level is set to an NF instance, and the one or more backup entities are one or more backup NF instances, or, the binding level is set to an NF set, and the one or more backup entities are one or more backup NF sets, the routing binding instruction includes a binding level set to an NF service instance, an NF service set, an NF instance, or an 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, the method is when the other NF is not available, - when the NF service set ID is included in the routing binding instruction, selecting an NF service instance in the NF service set indicated by the NF service set ID, and / or, when the NF instance ID is included in the routing binding instruction, selecting an equivalent NF service instance in the NF instance indicated by the NF instance ID with a lower priority and / or, - when the NF service set ID and the NF set ID are included in the routing binding instruction, selecting an NF service instance in an equivalent NF service set of other NF instances of the NF set, and / or, when the NF set ID is included in the routing binding instruction, selecting an equivalent NF service instance in other NF instances of the NF set with a higher priority, selecting one of the one or more backup service instances, the NF service instance among one of the one or more backup NF service sets, the equivalent NF service instance among one of the one or more backup NF instances, or the equivalent NF service instance among one of the one or more backup NF sets further comprising method (300).

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

6. A network node (900) comprising a communication interface (910), a processor (920), and a memory (930), wherein the memory (930) comprises instructions executable by the processor (920), whereby the network node (900) is operable to perform the method according to any one of claims 1 to 3 when implementing a network function (NF), or to perform the method according to claim 4 or 5 when implementing a service communication proxy (SCP) function.

7. A computer-readable storage medium storing computer-readable instructions, which when executed by a processor of a network node, configure the network node to perform the method according to any one of claims 1 to 3 when implementing a network function (NF), or to perform the method according to claim 4 or 5 when implementing a service communication proxy (SCP) function.

Images