Sharing resource redundancy information about network function service instances using binding indications between network functions

Abstract

Embodiments herein relate to populating information related to redundancy. In some embodiments, a method (400) performed by a first network function (201) is presented. The method (400) may comprise the step of sending (S401) a first message to a second network function (202), the first message comprising a first parameter indicating no redundancy to indicate that a first context is uniquely bound to a particular network function (NF) service instance within the first network function (201). The particular NF service instance may be identified in a binding indication included in the first message. Embodiments herein may allow an NF service instance to indicate that a resource is uniquely bound to the NF service instance without redundancy for related resources.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to PCT application serial number PCT / CN2022 / 106496 filed on July 19, 2022 and titled “POPULATING THE INFORMATION RELATED TO REDUNDANCY”, the entire contents of which are incorporated herein by reference. Technical Field

[0003] Embodiments herein generally relate to the field of mobile communications, and more particularly, embodiments herein relate to filling in redundancy-related information. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) defines the concept of Network Function (NF) Sets starting from Release 16 (Rel-16) to allow service continuity between NF instances within the same NF Set. To ensure optimized data replication management, NF producers can indicate the preferred scope of data replication to peer NFs through binding indications.

[0005] 3GPP TS29.500 section 6.12.1 states that "Binding Indication shall not be used if a specific resource can only be served by a specific NF service instance of a NF instance, i.e., if NF service instances of the same NF service cannot share resources within a NF instance. Resources for which no Binding Indication or Route Binding Indication is sent shall be considered to be uniquely bound to a certain NF service instance, unless the NF service resource owner instance is part of a 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 a NF instance (see 3GPP TS23.527

[38] section 6.5)". Summary of the invention

[0006] As specified in TS29.500, there is no way to use a binding indication to indicate, for example, that a resource is uniquely bound to a specific NF service instance, which may be a problem for some use cases.

[0007] Embodiments herein propose methods, network functions, computer-readable media, and computer program products for filling without redundancy.

[0008] In some embodiments, a method performed by a first network function is proposed. The method may include the following steps: sending a first message to a second network function, the first message including a first parameter indicating no redundancy to indicate that a first context is uniquely bound to a specific NF service instance within the first network function. The specific service instance may be identified by a binding indication included in the first message.

[0009] In one embodiment, the first message may further include a second parameter indicating a valid timer. The valid timer may indicate a valid period of the redundancy-free state.

[0010] In one embodiment, the validity timer may be included in the binding indication or another Hypertext Transfer Protocol (HTTP) header.

[0011] In one embodiment, the first network function may be a NF service producer, and the second network function may be a NF service consumer. In addition, the first context may be a resource context; and the first message may be a response message or a notification message.

[0012] In one embodiment, the first network function may be a NF service consumer, and the second network function may be a NF service producer. In addition, the first context may be a session context or a resource context; and the first message may be a request message or a subscription message.

[0013] In one embodiment, the first network function may act as a home session management function (SMF) for a home-routed packet data unit (PDU) session, and a visit SMF corresponding to the home-routed PDU session does not support redundancy.

[0014] In one embodiment, due to service software upgrade, downgrade or maintenance, the first network function may be removed from a group of NFs.

[0015] In one embodiment, a first network function may temporarily lose connectivity to an unstructured data storage function (UDSF) shared by a group of NFs.

[0016] In one embodiment, the method may further include the step of receiving a second message including a third parameter from the second network function, the third parameter indicating no redundancy to indicate that the second context is uniquely bound to a specific NF service instance within the second network function. In addition, the method may further include the step of deleting the second context if the second network function is unavailable.

[0017] In some embodiments, a method performed by a second network function is proposed. The method may include the step of receiving a first message from a first network function, the first message including a first parameter indicating no redundancy to indicate that a first context is uniquely bound to a specific NF service instance within the first network function. The specific NF service instance may be identified by a binding indication included in the first message.

[0018] In one embodiment, the first message may further include a second parameter indicating a valid timer. The valid timer may indicate a valid period without redundancy.

[0019] In one embodiment, the method may further include the following step: if the first network function is unavailable, deleting the first context.

[0020] In one embodiment, the method may further include the following step: when the validity timer indicates that the redundancy is not within the validity period, if the first network function is unavailable, deleting the first context.

[0021] In one embodiment, a validity timer may be included in the binding indication or another HTTP header.

[0022] In one embodiment, the first network function may be a NF service producer, and the second network function may be a NF service consumer. In addition, the first context may be a resource context; and the first message may be a response message or a notification message.

[0023] In one embodiment, the first network function may be a NF service consumer, and the second network function may be a NF service producer. In addition, the first context may be a session context or a resource context; and the first message may be a request message or a subscription message.

[0024] In one embodiment, the first network function may serve as a home SMF for a home-routed PDU session, and the access SMF corresponding to the home-routed PDU session does not support redundancy.

[0025] In one embodiment, the first network function may be removed from a group of NFs due to service software upgrade, downgrade or maintenance.

[0026] In one embodiment, the first network function may temporarily lose connectivity with an unstructured data storage function UDSF shared by a group of NFs.

[0027] In some embodiments, a network function is provided. In one embodiment, the network function may include at least one processor; and a non-transitory computer-readable medium coupled to the at least one processor. The non-transitory computer-readable medium may store instructions executable by the at least one processor, so that the at least one processor may be configured to perform any of the above methods. In one embodiment, the network function may be configured as a first network function or a second network function.

[0028] In some embodiments, a computer-readable medium including computer-readable code is provided, which, when executed on a device, can cause the device to perform any of the above methods.

[0029] In some embodiments, a computer program product including computer readable code is provided, which, when the computer program product is run on a device, can cause the device to perform any of the above methods.

[0030] This embodiment allows the NF service instance indication resource to be specifically bound to the NF service instance, and there is no redundancy in the related resources when using 3gpp-Sbi-Binding-Indication. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] The accompanying drawings are incorporated herein and constitute a part of the specification, and illustrate various embodiments of the present disclosure, and together with the specification, are further used to explain the principles of the present disclosure and enable those skilled in the relevant art to make and use the embodiments disclosed herein. In the accompanying drawings, similar reference numerals represent the same or functionally similar elements, wherein:

[0032] Figure 1 is a schematic block diagram of an example 5G network architecture in a non-roaming scenario;

[0033] Figure 2 is a schematic block diagram of an example wireless communication system architecture, used to indicate additional redundant information;

[0034] Figure 3 is a schematic signaling diagram showing a message in an example process according to an embodiment of the present invention, for indicating additional redundant information;

[0035] Figure 4 is a schematic flow chart illustrating an example method in a first network function according to an embodiment of the present invention;

[0036] Figure 5 is a schematic flow chart of an example method in a second network function according to an embodiment of the present invention;

[0037] Figure 6 is a schematic block diagram illustrating an example first network function according to an embodiment of the present invention;

[0038] Figure 7 is a schematic block diagram of an example second network function according to an embodiment of the present invention;

[0039] Figure 8 is a schematic block diagram of an example computer-implemented apparatus according to embodiments herein. DETAILED DESCRIPTION

[0040] The embodiments of the present invention are described in detail with reference to the accompanying drawings, in which the embodiments are shown. However, these embodiments of the present invention may be implemented in many different forms and should not be construed as being limited to the embodiments described herein. The elements in the drawings do not necessarily correspond to each other to scale.

[0041] Reference to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, the phrases "in an embodiment" appearing in various places in the specification are not necessarily all referring to the same embodiment.

[0042] As used herein, the term "A, B or C" means "A" or "B" or "C"; the term "A, B and C" as used herein means "A" and "B" and "C"; the term "A, B and / or C" as used herein means "A", "B", "C", "A and B", "A and C", "B and C" or "A, B and C".

[0043] It should also be understood that a network node (e.g. Figure 1 The AMF 101 or SMF 102 in the network, also known as a network function, can be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on an appropriate platform (e.g., a cloud infrastructure).

[0044] In one embodiment, the communication system 100 can be configured in an Over The Top (OTT) scenario. The OTT connection can be transparent because the devices participating in the communication through which the OTT connection passes are unaware of the routing of uplink and downlink communications. For example, the base station may not or need to be informed of the past routing of incoming downlink communications, where the data originates from a network function in the core network (e.g., AMF 101 or SMF 102) and will be forwarded (e.g., switched) to a connected user equipment (UE). Similarly, the base station does not need to know the future routing of outgoing uplink communications from the UE to a network function in the core network (e.g., AMF 101 or SMF 102).

[0045] Figure 1 1 is a schematic block diagram of an example architecture 100 showing a 5G network architecture in a non-roaming scenario. In a 5G core network, the service-based architecture describes several interaction modes, such as a request / response mode, or a subscription / notification mode.

[0046] The subscription / notification model assumes that a network function (NF) service consumer (e.g., AMF 101) issues a request message (e.g., a "subscribe" operation) to a NF service producer (e.g., SMF 102). Then, when something happens to the NF service producer, it issues a subsequent request (i.e., a "notify" operation) to the NF service consumer.

[0047] To ensure optimized data replication management, an NF producer or NF consumer may indicate the preferred scope of data replication by using a binding indication in a "Subscribe", "Request", "Notify" or "Response" message.

[0048] Binding indication is information included by the NF Service Producer in a response or notification to the NF Service Consumer to convey the scope of possible execution of selection / reselection of the target NF / NF Service, or information included by the NF Service Consumer in a request or subscription to convey the scope of possible execution of selection / reselection of the notification target or selection of other services generated by the NF Consumer for the same data context.

[0049] In the binding indication, the context owner (NF producer or NF consumer) can define the binding level to define the preferred scope of NF reselection. Example binding levels for binding, selection and reselection are shown in Table 1 below.

[0050] Table 1: Binding, selection, and reselection

[0051]

[0052] When the peer NF receives the binding instruction and detects that the original NF is unavailable, it will first select candidates within the preferred range (binding level). Only when all candidates within the binding level are unavailable will the peer NF reselect candidates outside the binding level.

[0053] 3GPP TS29.500 has this requirement, probably due to protocol limitations; the binding indication may include a preferred binding entity corresponding to the binding level, and another binding entity for reselection. When the binding level is NF service instance, the NF service instance ID (as the preferred binding entity) must be included, but the NF service instance ID is not globally unique and must be provided together with the NF instance ID or NF service set ID, which makes it unclear whether this NF instance ID / NF service set ID indication is used to identify the NF service instance or to describe the binding entity for reselection.

[0054] However, in several use cases, in addition to the existing binding indication, the NF may want to indicate additional redundant information for selecting / reselecting a NF service instance or entity, e.g., the NF may want to indicate that a resource is uniquely bound to a specific NF service instance.

[0055] Use case 1. Recovery process for PDU sessions supporting Home-Routed or PDU sessions with I-SMF

[0056] When the Visitor / Intermediate Session Management Function (V / I-SMF) does not support the PSETR function specified in 3GPP TS29.502 (i.e., when the H-SMF supports the DLSET function defined in 3GPPTS29.502 (i.e., the (H-)SMF is deployed in the (H-)SMF set), when the V / I-SMF detects that the (H-)SMF fails (is unreachable), the V / I-SMF cannot reselect an alternative (home) SMF (i.e., the (H-)SMF)), so when the (H-)SMF fails, the V / I-SMF will delete the PDU session, while the PDU session resources are still retained in the shared memory, such as the UDSF, the NF behind the (H)-SMF, such as the Policy Control Function / Unified Data Management (Policy Control Function / Unified Data) in the home Public Land Mobile Network (PLMN) The Home PLMN (for example, in the Home PLMN) is not aware that the PDU Session cannot be recovered (because it was deleted in the Visited PLMN). Therefore a method is needed to delete the resources that are suspended in the PCF / UDM (for example in the Home PLMN). One of the solutions could be that a replacement H-SMF in the same SMF set as the failed SMF is somehow aware of the failure of the (H-)SMF and knows that the PDU Session cannot be recovered (because it was deleted by the V / I-SMF) and then triggers the deletion. This alternative requires a complex mechanism with the SMF set to enable the SMFs in the set to track the status of each SMF in the set.

[0057] Use case 2. NF is removed from the SMF set in the following scenario:

[0058] In a service software upgrade, that is, upgrading to a certain software version so that the newly created resources cannot be shared by other NF service instances in the set that have not been upgraded;

[0059] Downgrade similar;

[0060] ·maintain.

[0061] For example:

[0062] Assume there are 5 NFs in the set (1, 2, 3, 4, and 5), and NF1 is being upgraded:

[0063] For any existing resources handled by NF1:

[0064] Preferably, other NFs in the same NF may be informed by notifying the preferred binding entity in the request to change the binding indication, either for a resource or, if supported, for a resource group; or

[0065] Use 3xx redirects when receiving a service request for an existing resource that was created before being moved out of the collection.

[0066] And for any new request, especially those requiring new upgraded functionality, NF1 should accept the request since NF1 is the first upgraded NF in the set and there is no redundancy. This must be indicated to the NF service consumer.

[0067] When NF2 is later also upgraded, the binding indication will be further updated, because NF1 and NF2 can form a new set. At some point, existing resources (created before NF1 was upgraded) will be handled by the new set.

[0068] Use case 3. A NF (service) set is deployed to use UDSF as a centralized database to store resource information, so any NF in the same (service) set can obtain resource information and thus be able to process requests related to that resource.

[0069] However, if the NF temporarily loses connection with the UDSF, any resources created or updated by the NF cannot be synchronized and stored in the UDSF, that is, the newly created or updated resources cannot be served by other NFs in the same set, that is, they are uniquely bound to a specific NF service instance.

[0070] In view of the above shortcomings, the embodiments of this document propose a mechanism that enables the NF service instance to indicate that the resource is uniquely bound to the NF service instance and there is no redundancy in the related resources.

[0071] Figure 2 A schematic block diagram is shown to illustrate an example architecture of a wireless communication system 200 for indicating additional redundancy information (eg, indicating no redundancy).

[0072] In one embodiment, the wireless communication system 200 may include but is not limited to a first NF 201 and a second NF 202. In one embodiment, the first NF 201 and the second NF 202 may be configured as Figure 1 Any two of the NFs shown.

[0073] In one embodiment, the first NF 201 may be a NF service consumer, the second NF 202 may be a NF service producer, and the message may be a request message or a subscription message. As an example, the first NF 201 may be Figure 1In the AMF 101, the second NF 202 can be Figure 1 SMF 102 in.

[0074] In another embodiment, the first NF 201 may be a NF service producer, the second NF 202 may be a NF service consumer, and the message may be a response message or a notification message.

[0075] In one embodiment, the first NF 201 may be configured to transmit a message to the second NF 202. In one embodiment, the first NF 201 may include a binding indication in the message.

[0076] In addition to the Binding Indication, the first NF 201 may also include additional redundant information in the message. Such "additional redundant information" may be included in the Binding Indication, in another HTTP header, or in a new HTTP customer header.

[0077] As an example, the additional redundant information may include the following parameters in Table 2 below.

[0078] Table 2: Definition of AdditionalRedundancyInfo type

[0079]

[0080] In one embodiment, the timer may indicate the validity period of the redundancy level, that is, the additional redundancy information is valid until the timer expires.

[0081] In one embodiment, the redundancy level can be defined as a Boolean value. When the redundancy level is set to true, it can indicate that no redundancy is available. That is, the context can be uniquely bound to a specific NF service instance within the first network function.

[0082] In one embodiment, the redundancy level may be defined as an enumeration value, i.e., "no-redundancy" or "nfservinst", "nfservset", "nfinst"; this indicates to the recipient the current redundancy level of the resource or session context, regardless of the binding level in the binding indication. When the redundancy level is set to "no-redundancy" or "nfservinst", it indicates that the resource is uniquely bound to this NF service instance.

[0083] As an example, the enumeration redundancy level may include the following information in Table 3 below. In Table 3, the enumeration RedundancyLevel indicates the current redundancy level.

[0084] Table 3: Enumeration redundancy level (RedundancyLevel)

[0085]

[0086] The redundancy level may have a finer level than the binding entity indicated in the binding indication for reselection. For example, if the binding indication indicates that the binding level is NF instance, the preferred binding entity is NF instance and the other binding entity (for reselection) is NF set. The redundancy level may be set to NF instance, so it instructs the receiver to respect the additional redundancy information, i.e. in case of failure, the receiver can only select an alternative NF service instance within the NF instance and not within the NF set until the validity period expires. When the timer expires, the receiver shall directly start using the binding indication as resilience information for the relevant resources or session context.

[0087] The binding indication may also include a binding entity corresponding to the redundancy level:

[0088] When the redundancy level is "NO_REDUNDANCY" or "NF_SERVICE_INSTANCE", the NF service instance ID may appear in the binding indication, for example, nfservinst=xyz may appear.

[0089] When the redundancy level is "NF_SERVICE_SET", the NF service set ID may exist in the binding indication (e.g., nfservset=setxyz.snnsmf-pdusession.nfi54804518-4191-46b3-955c-ac631f953ed8.5gc.mnc012.mcc345).

[0090] When the redundancy level is "NF_INSATNCE", the NF instance ID (e.g., nfinst=54804518-4191-46b3-955c-ac631f953ed8) may appear in the binding indication.

[0091] As shown above, in certain use cases, the NF wishes to indicate that resources have no redundancy, i.e., resources are uniquely bound to a specific NF service instance, even if the NF is or was part of a NF (service) set.

[0092] Embodiments are intended to address the problem / use case when a NF wishes to indicate that a resource is uniquely bound to a specific NF service instance.

[0093] In an embodiment, a new data type "redundancy-info" is proposed, which includes "redundancy-level", which includes "no-redundancy" as an enumeration value. Specifically, the embodiment allows the NF service instance to use 3gpp-Sbi-Binding-Indication to indicate that the resource is uniquely bound to the NF service instance and the related resources have no redundancy.

[0094] Figure 3 is a schematic signaling diagram illustrating messages in an example process for indicating additional redundancy information (eg, indicating no redundancy) according to embodiments herein.

[0095] Figure 3 It shows how one NF indicates to its peer NF that the resources or session context allocated in the NF producer or NF consumer are uniquely bound to a specific NF service use case, whether the NF is a NF service consumer (e.g. AMF101) or a NF service producer (e.g. SMF 102). In this example, the binding indication can be used to convey this additional redundant information. For simplicity, it is assumed that one NF instance (AMF 101 or SMF 102) contains only one NF service instance. For example, AMF1 has one NF service instance abc; and SMF1 has one NF instance xyz.

[0096] In one embodiment, a process for indicating additional redundant information (e.g., indicating no redundancy) may include the following messages or steps:

[0097] Step 1a. In order to establish the PDU session of UE1, AMF1 sends a request message to SMF1 to create an SmContext resource for the PDU session in SMF1. In the request message, AMF1 may include a 3gpp-Sbi-Binding for callback (i.e., the session context of the PDU session corresponding to the SmContext resource in SMF1).

[0098] For example, an example of 3gpp-Sbi-Binding can be 3gpp-Sbi-Binding: bl=nf-instance; nfinst=54804518-4191-46b3-955c-ac631f953ed7(AMF1); nfset=set1.region48.amfset.5gc.mnc012.mcc345; scope=callback.

[0099] That is, the binding indication of the NF consumer may include the binding level of the NF instance and the identifier of the NF instance (AMF1).

[0100] Step 1b. SMF1 may send a Create Response message which may include a Location header containing a resource Uniform Resource Identifier (URI) which AMF1 will use in subsequent signaling related to this resource. SMF1 may include 3gpp-Sbi-Binding: bl=nf-instance; nfinst=64804518-4191-46b3-955c-ac631f953ed8(SMF1); nfset=set1.smfset.5gc.mnc012.mcc345.

[0101] That is, the binding indication of the NF producer may indicate that, for the resource, the binding level may be set to the NF instance level. In addition, the binding indication of the NF producer may also include an identifier (SMF1) of the NF instance.

[0102] Step 2a. To establish the PDU session for UE2, AMF1 can perform the same operations and provide the same 3gpp-Sbi-Binding as in step 1a.

[0103] Step 2b. SMF1 may perform the same operations and provide the same 3gpp-Sbi-Binding as in step 1b.

[0104] Step 3. SMF1 may leave the SMF set for some reasons (such as upgrade), where the newly created resource context cannot be shared by other SMFs or other SMF service instances in the SMF set.

[0105] Step 4a. To establish the PDU session of UE3, AMF1 can perform the same operations and provide the same 3gpp-Sbi-Binding as in step 1a.

[0106] Step 4b.SMF1 may send a Create Response message which may include a Location header containing the resource URI which AMF1 will use in subsequent signaling related to this resource.SMF1 may include 3gpp-Sbi-Binding:bl=nfserviceinstance;nfservinst=xyz;nfinst=64804518-4191-46b3-955c-ac631f953ed8;no-redundancy=true.

[0107] That is, the binding indication of the NF producer may indicate that, for the resource, the binding level may be set to the NF service instance level. In addition, the binding indication of the NF producer may also include an identifier (xyz) of the NF service instance.

[0108] In this example, the binding indication of the NF producer may also include additional redundancy information (eg, "no-redundancy = true") to indicate that there is no redundancy for the resource.

[0109] The parameter "no-redundancy" in this example is a Boolean value and can be set to "true" or "false". The parameter "no-redundancy" can be used to indicate whether the resource is uniquely bound to the NF service instance identified in the binding indication. The "nfservset" or "nfinst" contained in the binding indication is only used to identify the NF service instance and is not used as a binding entity for reselection.

[0110] Step 5. AMF1 may leave the AMF set for some reasons (e.g. upgrade), where for the newly created resource context, the corresponding session context in the consumer cannot be shared by other AMFs in the AMF set.

[0111] Step 6a. In order to establish the PDU session of UE4, AMF1 can provide a binding indication, such as 3gpp-Sbi-Binding: bl=nfserviceinstance; nfsercinst=abc; nfinst=54804518-4191-46b3-955c-ac631f953ed7; no-redundancy=true.

[0112] That is, the binding indication of the NF consumer may indicate that, for the resource, the binding level may be set to the NF service instance level. In addition, the binding indication of the NF consumer may also include an identifier (abc) of the NF service instance.

[0113] In this example, the binding indication of the NF consumer may also include additional redundancy information (eg, "no-redundancy=true") to indicate that there is no redundancy for the resource.

[0114] Step 6b. SMF1 may send a create response message as in step 4b.

[0115] By referring to e.g. Figure 4 and Figure 5 The flowcharts further explain the embodiments of the present disclosure. Figure 4 is a schematic flow chart illustrating an example method 400 in a first network function 201 (NF consumer or NF producer) according to embodiments of the present invention.

[0116] The method 400 may start from step S401, where the first network function 201 may send a first message to the second network function 202, the first message including a first parameter indicating no redundancy to indicate that the first context is uniquely bound to a specific NF service instance within the first network function 201. The specific NF service instance may be identified in a binding indication included in the first message.

[0117] In one embodiment, the message may further include a second parameter indicating a valid timer. The valid timer may indicate a valid period without redundancy.

[0118] In one embodiment, the validity timer may be included in a binding directive or another HTTP header.

[0119] In one embodiment, the first network function 201 may be a NF service producer (e.g., SMF 102), and the second network function 202 may be a NF service consumer (e.g., AMF 101). In addition, the first context may be a resource context; and the first message may be a response message or a notification message.

[0120] In one embodiment, the first network function 201 may be a NF service consumer (e.g., AMF 101), and the second network function 202 may be a NF service producer (e.g., SMF 102). In addition, the first context may be a session context or a resource context; the first message may be a request message or a subscription message.

[0121] In one embodiment, the first network function 201 may serve as a home SMF for a Home-Routed PDU session, and a corresponding visit SMF for the Home-Routed PDU session does not support redundancy.

[0122] In one embodiment, the first network function 201 may be removed from a group of NFs due to service software upgrade, downgrade or maintenance.

[0123] In one embodiment, the first network function 201 may temporarily lose connectivity with a UDSF shared by a group of NFs.

[0124] Then, the method 400 may proceed to step S402 , where the first network function 201 may receive a second message including a third parameter from the second network function 202 , the third parameter indicating no redundancy, to indicate that the second context is uniquely bound to a specific NF service instance within the second network function 202 .

[0125] Then, the method 400 may proceed to step S403 , where if the second network function 202 is not available, the first network function 201 may delete the second context.

[0126] The above steps are only examples. The first network function 201 may perform Figure 2-3 Any actions described to allow the NF to fill in redundancy related information (e.g., indicating no redundancy) and perform corresponding processing.

[0127] Figure 5 4 is a schematic flow chart of an example method 500 in the second network function 202 (NF producer or NF consumer) according to an embodiment of the present invention.

[0128] Method 500 may start from step S501, where the second network function 202 may receive a first message from the first network function 201, the first message including a first parameter indicating no redundancy to indicate that the first context is uniquely bound to a specific NF service instance within the first network function 201, and the specific NF service instance may be identified in a binding indication included in the first message.

[0129] In one embodiment, the message may further include a second parameter indicating a valid timer. The valid timer may indicate a valid period without redundancy.

[0130] In one embodiment, the validity timer may be included in a binding directive or another HTTP header.

[0131] In one embodiment, the first network function 201 may be a NF service producer (e.g., SMF 102), and the second network function 202 may be a NF service consumer (e.g., AMF 101). In addition, the first context may be a resource context; and the first message may be a response message or a notification message.

[0132] In one embodiment, the first network function 201 may be a NF service consumer (e.g., AMF 101), and the second network function 202 may be a NF service producer (e.g., SMF 102). In addition, the first context may be a session context or a resource context; the first message may be a request message or a subscription message.

[0133] In one embodiment, the first network function 201 may serve as a home SMF for a Home-Routed PDU session, and the corresponding visit SMF for the Home-Routed PDU session does not support redundancy.

[0134] In one embodiment, the first network function 201 may be removed from a group of NFs due to service software upgrade, downgrade or maintenance.

[0135] In one embodiment, the first network function 201 may temporarily lose connectivity with a UDSF shared by a group of NFs.

[0136] Then, the method 500 may proceed to step S502, where if the first network function 201 is unavailable, the second network function 202 may delete the first context. Alternatively, when the validity timer indicates that there is no redundancy within the validity period, if the first network function 201 is unavailable, the second network function 202 may delete the first context.

[0137] The above steps are only examples. The second network function 202 may perform Figure 2-3 Any actions described to allow the NF to fill in redundancy related information (e.g., indicating no redundancy) and perform corresponding processing.

[0138] Figure 6 is a schematic block diagram illustrating an example first network function 201 according to embodiments herein.

[0139] In one embodiment, the first network function 201 may include at least one processor 601; and a non-transitory computer-readable medium 602 coupled to the at least one processor 601. The non-transitory computer-readable medium 602 may store instructions executable by the at least one processor 601, so that the at least one processor 601 may be configured to perform the following steps: Figure 4 The steps in the exemplary method 400 are shown in the schematic flowchart of FIG. 4 ; they will not be repeated here.

[0140] It should be noted that the first network function 201 can be implemented as hardware, software, firmware, and any combination thereof. For example, the first network function 201 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of the example method 400 or one or more steps related to the first NF 201 (AMF 101 or SMF 102).

[0141] It should be understood that the first network function 201 may be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on an appropriate platform (eg, a cloud infrastructure).

[0142] Figure 7 is a schematic block diagram illustrating an example second network function 202 according to embodiments herein.

[0143] In one embodiment, the second network function 202 may include at least one processor 701; and a non-transitory computer-readable medium 702 coupled to the at least one processor 701. The non-transitory computer-readable medium 702 may store instructions executable by the at least one processor 701, so that the at least one processor 701 may be configured to perform the following steps: Figure 5 The steps in the exemplary method 500 are shown in the schematic flowchart of FIG. 5 ; they will not be repeated here.

[0144] It should be noted that the second network function 202 can be implemented as hardware, software, firmware, and any combination thereof. For example, the second network function 202 may include multiple units, circuits, modules, etc., each of which may be used to perform one or more steps of the example method 500 or one or more steps related to the second NF 202 (SMF 102 or AMF 101).

[0145] It should be understood that the second network function 202 may be implemented as a network element on dedicated hardware, a software instance running on dedicated hardware, or a virtualized function instantiated on a suitable platform (eg, a cloud infrastructure).

[0146] Figure 8 8 is a schematic block diagram of an exemplary computer-implemented apparatus 800 according to an embodiment of the present invention. In one embodiment, the apparatus 800 may be configured as the above-mentioned apparatus, such as AMF 101, SMF 102, first NF 201 or second NF 202.

[0147] In one embodiment, the apparatus 800 may include but is not limited to at least one processor, such as a central processing unit (CPU) 801, a computer readable medium 802, and a memory 803. The memory 803 may include a volatile memory (e.g., a random access memory RAM) and / or a non-volatile memory (e.g., a hard disk or a flash memory). In one embodiment, the computer readable medium 802 may be configured to store a computer program and / or instructions, and when the processor 801 executes the computer program and / or instructions, the computer program and / or instructions cause the processor 801 to perform any of the above methods.

[0148] In one embodiment, computer readable medium 802 (e.g., non-transitory computer readable medium) may be stored in memory 803. In another embodiment, the computer program may be stored in a remote location, such as a computer program product 804 (also embodied as a computer readable medium), and accessible by processor 801 via, for example, carrier 805.

[0149] The computer-readable medium 802 and / or the computer program product 804 can be distributed and / or stored on a removable computer-readable medium, such as a floppy disk, a CD (Compact Disk), a DVD (Digital Video Disk), a flash memory or similar removable storage medium (such as compact flash, SD (secure digital), memory stick, mini SD card, MMC multimedia card, smart media), HD-DVD (High Definition DVD) or Blu-ray DVD, USB (Universal Serial Bus) based removable storage medium, magnetic tape media, optical storage media, magneto-optical media, bubble memory, or distributed as a propagation signal through a network (such as Ethernet, ATM, ISDN, PSTN, X.25, the Internet, a local area network (LAN) or a similar network capable of transmitting data packets to infrastructure nodes).

[0150] In addition, the following amendments are proposed to revise the current 3GPP technical specification 3GPP TS29.500V17.7.0.

[0151] Title: Binding indication of resources bound to a specific NF service instance

[0152] Reason for change:

[0153] According to TS29.500, a binding indication cannot be used to indicate that a resource is uniquely bound to a specific NF service instance:

[0154] If a specific resource can only be served by a specific NF service instance of a NF instance, i.e., if NF service instances of the same NF service cannot share resources within a NF instance, then the binding indication shall not be used. A resource for which no binding indication or route binding indication is sent shall be considered to be uniquely bound to one NF service instance, unless the NF service resource owner instance is part of a 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 a NF instance (see clause 6.5 of 3GPP TS 23.527

[38] ).

[0155] The requirements highlighted in italics force the receiving NF (consumer or producer) to perform a service discovery procedure with the NRF to determine if the resource is actually bound to a specific NF service instance, as the producer may not support binding indication.

[0156] Additionally, there are several use cases where an NF may wish to indicate that a resource is uniquely bound to a specific NF service instance:

[0157] 1. Support the recovery process of home-routed PDU sessions or PDU sessions with I-SMF

[0158] When the V / I-SMF does not support the PSETR function (i.e., when the H-SMF supports the DLSET function (i.e., the (H-)SMF is deployed in the (H-)SMF set), the V / I-SMF cannot reselect an alternative (H-)SMF when it detects that the (H-)SMF fails (is unreachable), so when the (H-)SMF fails, the V / I-SMF will delete the PDU session, while the PDU session resources in the HPLMN are still saved in the shared memory, such as the UDSF, and the NFs behind the (H)-SMF, such as the PCF / UDM in the home PLMN, do not know that the PDU session cannot be restored because it has been deleted in the visited PLMN. Therefore, we need a way to delete the resources suspended by the PCF / UDM (e.g., in the HPLMN). One of the solutions may be that the alternative H-SMF in the same SMF set as the failed SMF somehow knows that the (H-)SMF has failed and cannot restore the PDU session (because the V / I-SMF has deleted the PDU session), and then triggers the deletion. This alternative requires a complex mechanism with SMF sets to enable the SMFs in a set to track the state of each SMF in the set.

[0159] 2. When the NF service instance is removed from the set in the following scenarios:

[0160] In a service software upgrade, that is, upgrading to a certain software version so that the newly created resources cannot be shared by other non-upgraded NF service instances in the collection;

[0161] Downgrade is similar.

[0162] ·maintain.

[0163] For example:

[0164] Assume there are 5 NFs in the set (1, 2, 3, 4 and 5) and NF1 is being upgraded:

[0165] For any existing resources handled by NF1:

[0166] Preferably, other NFs in the same NF set should do the same, which can be done by notifying the preferred binding entity in the request change binding indication, which can be changed per resource or per resource group (if supported); or

[0167] Before NF1 is removed from the collection, when a service request is received addressing an existing resource that is being created, a 3xx redirect is used.

[0168] And for any new request, especially those requiring new upgraded functionality, NF1 should accept the request since NF1 is the first upgraded NF in the set and there is no redundancy. This must be made clear to the NF service consumer.

[0169] 3. Deployment of NF (service) sets uses UDSF as a centralized database to store resource information, so any NF in the same (service) set can obtain resource information and thus be able to process requests related to that resource.

[0170] However, when an NF temporarily loses connection with the UDSF, any resources created or updated by the NF in this case cannot be synchronized and stored in the UDSF, that is, these newly created or updated resources cannot be served by other NFs in the same set, that is, they can only be uniquely bound to a specific NF service instance.

[0171] Therefore, it is proposed to introduce a new parameter “no-redundancy” as a boolean value to indicate whether the resource / session context is uniquely bound to a specific NF service instance in the 3gpp-Sbi-Binding.

[0172] Summary of changes:

[0173] A new parameter "no-redundancy" is introduced in 3gpp-Sbi-Binding. This parameter is used as a Boolean value to indicate whether the resource / session context is uniquely bound to a specific NF service instance, and the relevant description of this parameter is introduced.

[0174] Consequences of non-approval:

[0175] The use case where some NFs want to indicate that a resource is uniquely bound to a specific resource is not supported.

[0176] Suggested changes:

[0177] ***Change 1*** (underlined text indicates content to be added to the 3GPP technical specification)

[0178] 6.1.6.1 General provisions

[0179] This clause specifies the application data model supported by the API.

[0180] 5.2.3.2.6 3gpp-Sbi-Binding

[0181] This header contains a comma-separated list of binding directives from the HTTP server, for storage and subsequent use by the HTTP client (see Section 6.12).

[0182] The encoding of the header follows the ABNF defined in IETF RFC 7230

[12] .

[0183] 3gpp-Sbi-Binding = "3gpp-Sbi-Binding": 1#(OWS "bl" = blvalue 1*(";" OWS parameter) [";" OWS recoverytime] [";" OWS notif-receiver] [";" OWS "group" = groupvalue] [1*(";" OWS groupparameter)])

[0184] blvalue = "nf-instance" / "nf-set" / "nfservice-instance" / "nfservice-set"

[0185] parameter = parametername "=" token

[0186] parametername = "nfinst" / "nfset" / "nfservinst" / "nfserviceset" / "servname" / "scope" / "backupamfinst" / "backupnf"

[0187] recoverytime = "recoverytime = " OWSDQUOTE date-time DQUOTE

[0188] notif-receiver = "nr = " URI; URI production rule from IETF RFC 3986

[14] , Appendix A

[0189] groupvalue = "true" / "false"

[0190] groupparameter = groupparametername "=" token

[0191] groupparametername = "oldgroupid" / "groupid" / "uribase" / "oldnfinst / " oldservset " / " oldservinst " / " guami

[0192] no-redundancy="true" / "false"

[0193] Define the following parameters:

[0194] -scope: Indicates the applicability of the binding indication in service requests other than notification requests, or in notification or callback responses. This parameter can take one of the following values:

[0195] - "other-service": the binding information applies to other services that the NF service consumer may later provide as a NF service producer (see clause 6.12.3);

[0196] - "subscription-events": the binding information applies to subscription change event notifications (see Section 6.12.4);

[0197] - "callback": The binding information applies to a notification or callback request (see clauses 6.12.4 and 6.12.5).

[0198] A service request other than a notification request, or the absence of this parameter in a notification or callback response SHOULD be interpreted as "callback".

[0199] If the binding information applies to notification / callback requests and other services, two scope parameters may be included in the binding indication.

[0200] - Service name (servname): indicates the name of the service, which is defined in 3GPP TS29.510[8], or a custom service, that is:

[0201] - the name of the service that handles the notification or callback request appears in the subscription or callback binding directive, i.e. the scope parameter is not present or is set to "callback"; or

[0202] -When the name of the other service to which the binding applies appears in the binding indication and the binding indication is included in a service request for other services that the NF Service Consumer may subsequently provide as an NF Service Producer, the scope parameter is set to "other-service". Multiple service name (servname) parameters may be present to represent multiple such services. If this parameter is absent from a binding indication with the scope parameter set to "other-service", it should be interpreted as the binding information applying to all services that the NF Service Consumer may subsequently provide as an NF Service Producer.

[0203] - Recovery time: The recovery timestamp of the entity corresponding to the highest level of resilience supported by the resource, i.e., the higher level binding entity indicated in the binding indication. See Table 6.3.1.0-1 of 3GPP TS 23.501 [3] and Section 6.1 of 3GPP TS 23.527

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

[37] and Section 7.1.1.1 of IETF RFC 7231

[11] .

[0204] -nr: indicates the URI of the notification endpoint when this binding information is applicable; it applies to callback requests (see clause 6.12.4); if the notification URI does not contain a correlationID in the path (i.e., it is a common notification URI for multiple subscriptions), the correlationID SHOULD be added to the end of the URI as the fragment component of the URI (i.e., following the "#" character).

[0205] — See Section 5.2.3.2.5 for the definition and encoding of BLVALUE, NFINST, BACKUPAMFINST, NFSET, NFSERVINST, and NFSERVICESET.

[0206] - Backup NF (backupnf): represents the backup NF service instance identifier and / or backup NF identifier, as defined in clause 5.2.2.2.2 or in 3GPP TS 29.510 [8], which shall be used when the preferred binding entity is unreachable (if supported).

[0207] - group: It is a Boolean value indicating whether the binding indication is for a group of resource / session contexts.

[0208] - Group ID (groupid): represents the group identifier assigned to an NF (service) instance. One or more resource / session contexts share the same groupid. The groupid is optional and can be assigned when a resource / session context is created and then updated. The groupid is globally unique and can be encoded using the same mechanism as NfInstanceId defined in 3GPP TS29.571

[13] .

[0209] - OldGroupID: indicates the group identifier previously assigned by the NF (service) instance and will be replaced by groupid, so it should only exist when updating the binding indication of multiple contexts. When oldgroupid exists, groupid should also exist to indicate the new groupid assigned.

[0210] -uribase: Identifies the apiroot and path segment portions of a resource URI or notification / callback URI that are common to multiple contexts. This parameter may only be present when updating a binding indication for multiple contexts and "group" is set to "true". When included, the parameter indicates that all resources or notification contexts with this uribase will subsequently use the updated binding indication. Multiple uribases may be present.

[0211] -oldnfinst: indicates the NF instance ID of the NF instance currently serving the resource / session context group (i.e., the binding indication previously allocated for the resource / session context group contains information of this NF instance), as defined in clause 5.2.2.2.2 of 3GPP TS 29.510 [8]. When included, it indicates that all resource / session contexts served by this NF instance will subsequently use this updated binding indication.

[0212] -oldservset: indicates the NF service set ID of the NF service set currently serving the resource / session context group (i.e., the binding indication previously allocated for the resource / session context group includes information of this NF service set), as defined in clause 5.2.2.2.2 of 3GPP TS 29.510 [8]. When included, it indicates that all resource / session contexts served by this NF service set will subsequently use this updated binding indication.

[0213] -oldservinst: indicates the NF service instance ID of the NF service instance currently serving the resource / session context group (i.e., the binding indication previously allocated for the resource / session context group includes information of this NF service instance), as defined in clause 5.2.2.2.2 of 3GPP TS 29.510 [8]. When included, it indicates that all resource / session contexts served by this NF service instance will subsequently use this updated binding indication.

[0214] -guami (GUAMI): Indicates the GUAMI of the AMF currently serving the UE context, as defined in clause 5.3.4.1 of 3GPP TS 29.571

[13] . When included, indicates that all UE contexts associated with the GUMAI will subsequently use this updated binding indication.

[0215] -no-redundancy: This parameter is of Boolean type and indicates whether the resource is uniquely bound to the identifier in the binding indication. When set to true, the nfservset or nfinst included in the bind indication shall only be used to identify the NF service instance. service instance and should not be considered as a binding entity to be re-elected.

[0216] Examples 1 to 5: Same as Examples 1 to 5 defined in clause 5.2.3.2.5, but the header name is "3gpp-Sbi-Binding" instead of "3gpp-Sbi-Routing-Binding".

[0217] Example 6: A subscription request sent by one NF on behalf of another NF contains two binding indications:

[0218] 3gpp-Sbi-Binding:bl=nf-set; nfset=set1.udmset.5gc.mnc012.mcc345; servname=nudm-ee; scope=subscription-events

[0219] 3gpp-Sbi-Binding:bl=nf-set;nfset=set1.nefset.5gc.mnc012.mcc345;servname=nnef-event-exposure

[0220] Example 7: Service request with 2 binding indications for callback request and other services that the NF Service Consumer may subsequently provide as a NF Service Producer:

[0221] 3gpp-Sbi-Binding:bl=nf-instance;nfinst=54804518-4191-46b3-955c-ac631f953ed8;nfset=set1.smfset.5gc.mnc012.mcc345;servname=nsmf-pdusession

[0222] 3gpp-Sbi-Binding:bl=nf-instance;nfinst=54804518-4191-46b3-955c-ac631f953ed8;nfset=set1.smfset.5gc.mnc012.mcc345;scope=other-service;servname=nsmf-event-exposure

[0223] Example 8: Service request with one binding indication for notification / callback request and for any other services that the NF Service Consumer may subsequently provide as a NF Service Producer:

[0224] 3gpp-Sbi-Binding: bl=nf-set; nfset=set1.region48.amfset.5gc.mnc012.mcc345; scope=callback; scope=other-service

[0225] Example 9: A service request with a binding indication that it is applicable to a notification / callback request, carrying in the binding indication a recovery timestamp associated with a NF set and a binding level set to "nfset":

[0226] 3gpp-Sbi-Binding:bl=nfset; nfset=set1.region48.amfset.5gc.mnc012.mcc345; scope=callback; recoverytime="Tue,04Feb 202008:49:37GMT"

[0227] Example 10: A service response with one binding indication and applied to a session context carries the recovery timestamp associated with the NF set indicated by "nfset" in the binding indication and the binding level set to "nfinstance":

[0228] 3gpp-Sbi-Binding:bl=nfinstance;nfinst=54804518-4191-46b3-955c-ac631f953ed8;nfset=set1.smfset.5gc.mnc012.mcc345;recoverytime="Tue,04Feb2020 08:49:37GMT"

[0229] Example 11: A service response with one binding indication and applied to a session context carries a recovery timestamp associated with the NF instance included in the binding indication and a binding level set to nfserviceinstance:

[0230] 3gpp-Sbi-Binding:bl=nfserviceinstance;nfservinst=xyz;nfinst=54804518-4191-46b3-955c-ac631f953ed8;recoverytime="Tue,04Feb 202008:49:37GMT"

[0231] Example 12: Service response with one binding indication applied to a resource context belonging to the group identified by "54804518-4191-46b3-955c-ac631f953ed1" with backup NF:

[0232] 3gpp-Sbi-Binding:bl=nfinstance;nfinst=54804518-4191-46b3-955c-ac631f953ed0;nfset=set1.smfset.5gc.mnc012.mcc345;

[0233] groupid=54804518-4191-46b3-955c-ac631f953ed1;

[0234] backupnf=54804519-4191-46b3-955c-ac631f953ed2

[0235] Example 13: A notification request message with one binding indication and applicable to resource contexts that have the old group identifier "54804518-4191-46b3-955c-ac631f953ed1", where the preferred binding entity is changed to "nfinst=54804519-4191-46b3-955c-ac631f953ed0" and has a new group identifier "54804519-4191-46b3-955c-ac631f953ed3".

[0236] 3gpp-Sbi-Binding:bl=nfinstance;nfinst=54804519-4191-46b3-955c-ac631f953ed0;nfset=set1 .smfset.5gc.mnc012.mcc345; group=true; oldgroupid=54804518-4191-46b3-955c-ac631f953ed1;

[0237] groupid=54804519-4191-46b3-955c-ac631f953ed3

[0238] Example 14: A Notification Request message with one binding indication, applied to the resource context identified by uribase, where the preferred binding entity is changed to "nfinst=54804519-4191-46b3-955c-ac631f953ed0":

[0239] 3gpp-Sbi-Binding:bl=nfinstance;nfinst=54804519-4191-46b3-955c-ac631f953ed0;nfset=se t1.smfset.5gc.mnc012.mcc345; group=true; uribase=http%3A%2F%2F10.10.10.10%2Fstringxyz

[0240] Example 15: A notification request message with one binding indication, applicable to the resource context served by the NF instance identified by "64804518-4191-46b3-955c-ac631f953ed8", where the preferred binding entity is changed to "nfinst=74804519-4191-46b3-955c-ac631f953ed0".

[0241] 3gpp-Sbi-Binding:bl=nfinstance;nfinst=74804519-4191-46b3-955c-ac631f953ed0;nfset=set 1.smfset.5gc.mnc012.mcc345; group=true; oldnfinst=64804518-4191-46b3-955c-ac631f953ed8

[0242] Example 16: Service request message with updated binding indication, applied to GUAMI"<mnc(012)><mcc(345)><AmfId("abcd12")> The UE context where backupamfinst has changed.

[0243] 3gpp-Sbi-Binding:bl=nf-instance; nfinst=54804518-4191-46b3-955c-ac631f953ed7;

[0244] backupamfinst=54804520-4191-46b3-955c-ac631f953ed8;scope=other-service;group=true;guami={"plmnId":{"mnc":"012","mcc":"345"},"amfId":"abcd12"}

[0245] Example X: A service response with a binding indication applies to a resource context that is uniquely bound to a specific NF service instance. arts.

[0246] 3gpp-Sbi-Binding:bl=nfserviceinstance;nfservinst=xyz;nfinst= 54804518-4191-46b3-955c-ac631f953ed8;no-redundancy=true

[0247] Note: Examples 6 and 7 have two different headers (which improves readability), but they could also have the format of a single header carrying two binding indicator values ​​separated by commas.

[0248] ***Change No. 2*** (underline indicates content to be added in 3GPP technical specifications)

[0249] 6.12.1 General Provisions

[0250] A binding indication for an NF service resource may be provided to the NF service consumer of the resource as part of a direct or indirect communication process for subsequent related service requests. This allows the NF service resource owner to indicate to the NF service consumer that a particular resource should be bound to one NF service instance, NF instance, NF service set or NF set. See clause 6.3.1.0 of 3GPP TS 23.501 [3] and clause 4.17.12 of 3GPP TS 23.502 [4].

[0251] Bindings can be established or updated as part of the following operations:

[0252] 1) A service response that creates or modifies a resource, which is used for subsequent requests for that resource (see 3GPP TS 23.502 [4], section 4.17.12.2), and is applicable to any API that defines a resource;

[0253] 2) Service request, if the NF service consumer can also act as an NF service producer and conduct subsequent communications with the contacted NF service producer, it is used for subsequent service requests initiated by the contacted NF service producer (see 3GPP TS 23.502 [4] Section 4.17.12.3);

[0254] 3) Create or modify an explicit or implicitly subscribed service request, or as part of a notification response for a subsequent notification request initiated by the NF service producer (see 3GPP TS 23.502 [4] clause 4.17.12.3);

[0255] 4) Create an implicit or explicit subscription or update a subscription or a service response as part of a notification request for subsequent operations on the subscription (see section 4.17.12.4 of 3GPP TS 23.502 [4]);

[0256] 5) Create callback (other than notification) resources (e.g. callback URI of V-SMF or I-SMF sent to H-SMF or SMF) or service request as part of callback response for subsequent callback request initiated by NF Service Producer (e.g. PDU Session Modification initiated by H-SMF or SMF);

[0257] 6) The callback request sent from the NF service producer is used to update the binding of the resource context for the NF service consumer to use for subsequent processing of the resource context service request.

[0258] Two types of binding information are defined to manage the binding between NF service consumers and NF service resources:

[0259] 1) The binding indication conveys the binding information of the resource, which must be stored by the consumer (client) of the resource and used by the client to direct future requests to the resource. When the binding information is included in the service request, the binding information is associated with the resource of the current transaction owned by the NF service consumer. When the binding information is included in the service response, the binding information is associated with the resource of the current transaction owned by the NF service producer.

[0260] 2) Route binding instructions convey binding information to direct requests from clients to servers with context. Route binding instructions can only be included in HTTP requests.

[0261] The same service request can pass more than one binding indication, for example:

[0262] - Provides bindings for notifications or callbacks (i.e., item 3 or 5), and bindings for other services that the NF Service Consumer can subsequently provide as an NF Service Producer (i.e., item 2); or

[0263] - When creating a subscription on behalf of another NF, provide binding information for different event notifications (see clause 6.12.4).

[0264] The scope parameter in the binding indication in the service request (or notification or callback response) identifies the applicability (ie, the relevant scenario) of the binding information.

[0265] A service request may use the 3gpp-Sbi-Binding header to convey one or more binding indications as described above and / or include binding routing indications to affect the routing of the request, such as routing to an appropriate set of NF service producers or a service set of a suitable NF service producer using the 3gpp-Sbi-Routing-Binding header. A service response may use the 3gpp-Sbi-Binding header to convey binding indications for resources.

[0266] NOTE 1: The HTTP request may contain, for example, a 3gpp-Sbi-Binding header containing two binding indications for other services and callbacks, and a 3gpp-Sbi-Routing-Binding header to convey a routing binding indication.

[0267] Once a Binding Indication for a specific resource or scope has been received, the absence of a Binding Indication for the same resource or scope in a subsequent request / response message shall be interpreted as meaning that the previously received Binding Indication for that resource or scope has not changed, unless otherwise specified in the rest of this specification (see below for scenarios where the NF service producer or consumer changes, and clause 6.12.4 for inter-AMF mobility scenarios).

[0268] In case of a change in NF service producer (e.g. change of V-SMF or I-SMF), the NF service consumer (e.g. AMF) shall delete any previous binding indication received from the old NF service producer (e.g. old V-SMF / I-SMF) for the producer's resources (e.g. SM context resources) and replace it with any new binding indication that may be received from the new NF service producer (e.g. new V-SMF / I-SMF).

[0269] In case of a change in NF Service Consumer (e.g. inter-AMF mobility), the NF Service Producer (e.g. SMF) shall delete any previous Binding Indication received from the old NF Service Consumer (e.g. Binding Indication for a Callback Request received from the old AMF) and replace it with any new Binding Indication that may have been received from the new NF Service Consumer (e.g. new AMF).

[0270] If the SCP receives a route binding indication in a service or notification request and decides to forward the request to the next-hop SCP, it shall include the route binding indication in the forwarded request. If the SCP forwards the request to the target NF, the SCP shall remove the route binding indication.

[0271] The binding indication and route binding indication shall include the binding level and one or more binding entity IDs, representing all NF service instances that can provide services for service requests for resources, i.e., share the same resource context.

[0272] The binding level indicates the preferred binding to a NF instance, NF set, NF service instance or NF service set.

[0273] When sending a request for a resource context in a NF Service Producer or a session context in a NF Service Consumer, the "3gpp-Sbi-Target-apiRoot" header or the target URI shall first be set using the resource URI or the notification / callback URI (if available) received in the location header; as an exception, if the previously received binding indication for the target resource context or session context indicates a binding level of "NF Service Set", "NF Instance" or "NF Set", and alternative NF Service Instances within the preferred binding entity corresponding to the binding level are available, the request may be sent to one of these alternative NF Service Instances instead. When the URI or notification / callback URI received in the location header is unreachable or when a change in the NF Service Producer or Consumer is recognized (as described in clauses 6.5.3.2 and 6.5.3.3, item 3), 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 unreachable, the request shall be sent to any other binding entity indicated in the binding indication or route binding indication in the following decreasing order of priority:

[0274] - if a backup NF service instance and / or a backup NF instance is indicated in the binding indication or the route binding indication, selecting an available NF service instance in the backup NF instance;

[0275] - If the NF service set ID is indicated in the binding indication or the route binding indication, a NF service instance in the same NF service set is selected;

[0276] - If the NF instance ID is indicated in the binding indication or route binding indication, an equivalent NF service instance is selected in the same NF instance;

[0277] - If the NF Service Set ID and the backup AMF Instance ID are indicated in the Binding Indication or the Route Binding Indication, select a NF Service Instance in the equivalent NF Service Set of the backup AMF Instance;

[0278] - If a backup AMF instance ID is indicated in the binding indication or route binding indication, select an equivalent NF service instance in the backup AMF instance;

[0279] - if the NF Service Set ID and the NF Set ID are indicated in the Binding Indication or the Route Binding Indication, then select the NF Service Instance in the equivalent NF Service Set of another NF Instance of the NF Set;

[0280] - If the NF set ID is indicated in the binding indication or the route binding indication, an equivalent NF service instance is selected in another NF instance of the NF set.

[0281] NOTE 2: NF service instances in different NF instances are equivalent NF service instances if they share the same MCC, MNC, NID (for SNPN), ServiceName, API version and, if applicable, NF service set ID (see 3GPP TS 23.003

[15] clause 28.13).

[0282] If a specific resource can only be served by a specific NF service instance of a NF instance, i.e., if NF service instances of the same NF service cannot share resources within a NF instance, then the binding indication shall not be used, Unless the recipient of the binding instruction has indicated A non-redundant indication in the binding directive in the SupportFeatures property that indicates support for a particular API. Resources that do not indicate a Binding Indication or a Route Binding Indication shall be considered to be uniquely 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 TS 23.527

[38] ).

[0283] NF Service Producers supporting different sets of NF Service Instances (e.g. serving different network slices) shall include the NF Service Set ID in the Binding Indication to be able to reselect (when needed) an alternative NF Service Instance from the same or equivalent NF Service Set. See also clause 6.10.3.2 for the requirement to include the "3gpp-Sbi-Discovery-*" headers in the Service Request for an existing Resource Context in the NF Service Producer.

[0284] Binding indications can be shared by multiple resource / session contexts, i.e. these resource contexts (in NF service producers) or session contexts (in NF service consumers) share the same resilience information. Binding indications for multiple contexts have the same semantics as a single resource / session context, but with the following additions. When this functionality is supported as indicated in the supported capabilities of a specific service API:

[0285] - Both NF Service Consumer and NF Service Producer can indicate whether the Binding Indication is for multiple contexts; if the Binding Indication is for multiple contexts, the "group" parameter in the Binding Indication shall be set to "true";

[0286] - When creating a resource / session context, a group ID may be included in the binding indication to indicate that the group to which the resource / session context belongs shares the same binding indication;

[0287] - When a callback URI is provided by the NF service consumer, such as when the NF changes, by including oldgroupid, oldnfinst, oldservset, oldservinst or uribase in the binding indication of a set of contexts to handle the contexts applicable to the binding indication update, if the binding indication is provided in the 3gpp-Sbi-Consumer-Info header, the binding indication may be updated for each resource URI with a different apiRoot part (representing different peer NF (service) instances) or each notification URI with a different authority part, or each notification URI with the same authority part but different callback-uri-prefix (see clause 5.2.3.3.7). When oldgroupid is present, groupid shall also be present to indicate the newly allocated new group ID. In addition, the binding indication may be updated for a set of UE contexts by including gumai to handle the UE contexts applicable to the updated binding indication.

[0288] ***END OF CHANGES***

[0289] Example embodiments are described herein with reference to block diagrams and / or flowchart illustrations of computer-implemented methods, apparatus (systems and / or devices), and / or non-temporary computer program products. It is understood that the blocks in the block diagrams and / or flowchart illustrations and the combination of blocks in the block diagrams and / or flowchart illustrations can be implemented by computer program instructions executed by one or more computer circuits. These computer program instructions can be provided to processor circuits of general-purpose computer circuits, special-purpose computer circuits, and / or other programmable data processing circuits to produce a machine so that instructions executed by the processor of the computer and / or other programmable data processing devices convert and control transistors, values ​​stored in memory locations, and other hardware components within such circuits to implement the functions / actions specified in the block diagrams and / or flowchart blocks, thereby creating means (functions) and / or structures for implementing the functions / actions specified in the block diagrams and / or flowchart blocks.

[0290] These computer program instructions may also be stored in a tangible computer-readable medium that can instruct a computer or other programmable data processing device to operate in a specific manner so that the instructions stored in the computer-readable medium produce an article of manufacture, including instructions that implement the functions / actions specified in the block diagram and / or flowchart block. Therefore, embodiments of the inventive concept may be embodied in hardware and / or software (including firmware, resident software, microcode, etc.) running on a processor (e.g., a digital signal processor), which may be collectively referred to as a "circuit," "module," or variations thereof.

[0291] It should also be noted that in some alternative embodiments, the function / action indicated in the square frame may not occur in the order indicated in the flow chart. For example, two consecutively displayed square frames may actually be performed substantially simultaneously, or may sometimes be performed in reverse order, depending on the function / action involved. In addition, the function of a given square frame of a flow chart and / or block diagram may be divided into a plurality of square frames and / or the function of two or more square frames of a flow chart and / or block diagram may be integrated at least in part. Finally, other square frames may be added / inserted between the square frames shown, and / or square frames / operations may be omitted without departing from the scope of the inventive concept. In addition, although some figures include arrows on the communication path to show the main direction of communication, it should be understood that communication may occur in the direction opposite to the arrows shown.

[0292] Without departing from the principles of the inventive concept, many changes and modifications may be made to the embodiments. All of these changes and modifications are intended to be included within the scope of the inventive concept. Therefore, the above disclosed subject matter should be considered illustrative, rather than restrictive, and the attached embodiment examples are intended to cover all such modifications, enhancements, and other embodiments, which all belong to the spirit and scope of the inventive concept. Therefore, to the maximum extent permitted by law, the scope of the inventive concept should be determined by the most widely permitted interpretation of the present disclosure, including the following embodiment examples and their equivalents, and should not be limited or restricted by the foregoing detailed description.

[0293] abbreviation

[0294] 3GPP 3rd Generation Partnership Project

[0295] 5G fifth generation of mobile communication technology

[0296] AMF Access and Mobility Management Function

[0297] HTTP Hyper Text Transfer Protocol

[0298] NF Network Function

[0299] OTT is Over The Top

[0300] PCF Policy Control Function

[0301] PDU Packet Data Unit

[0302] PLMN Public Land Mobile Network

[0303] SMF Session Management Function

[0304] UDM Unified Data Management

[0305] UDSF Unstructured Data Storage Function

[0306] UE User Equipment

[0307] URI Uniform Resource Identifier

Claims

1. A method (400) performed by a first network function (201), comprising: - sending a first message to a second network function (202), the first message comprising a first parameter indicating no redundancy to indicate that the first context is uniquely bound to a specific network function (NF) service instance within the first network function (201); and The specific NF service instance is identified by a binding indication included in the first message.

2. The method (400) of claim 1, wherein: The first message further includes a second parameter indicating a valid timer, and the valid timer indicates a valid period of the redundancy-free state.

3. The method (400) of claim 2, wherein the validity timer is contained in the binding indication or in another Hypertext Transfer Protocol (HTTP) header.

4. The method (400) according to any one of claims 1 to 3, wherein: The first network function (201) is a NF service producer (102), and the second network function (202) is a NF service consumer (101); wherein the first context is a resource context; and The first message is a response message or a notification message.

5. The method (400) according to any one of claims 1 to 3, wherein: The first network function (201) is a NF service consumer (101), and the second network function (202) is a NF service producer (102); wherein the first context is a session context or a resource context; and The first message is a request message or a subscription message.

6. The method (400) according to any one of claims 1 to 5, in, The first network function (201) acts as a home session management function (SMF) for a home-routed packet data unit (PDU) session, and the access SMF corresponding to the home-routed PDU session does not support redundancy; wherein the first network function (201) is removed from a group of NFs due to a service software upgrade, downgrade or maintenance; or The first network function (201) temporarily loses connection with an unstructured data storage function (UDSF) shared by a group of NFs.

7. The method (400) according to any one of claims 1 to 6, further comprising: receiving (S402) a second message from the second network function (202), the second message comprising a third parameter indicating no redundancy to indicate that the second context is uniquely bound to a specific NF service instance within the second network function (202); and If the second network function (202) is not available, the second context is deleted (S403).

8. A method (500) performed by a second network function (202), comprising: Receiving (S501) a first message from a first network function (201), the first message comprising a first parameter indicating no redundancy to indicate that a first context is uniquely bound to a specific network function (NF) service instance within the first network function (201); The specific NF service instance is identified by a binding indication included in the first message.

9. The method (500) of claim 8, wherein: The first message further includes a second parameter indicating a valid timer, and the valid timer indicates a valid period without redundancy.

10. The method (500) according to claim 8 or 9, further comprising: If the first network function (201) is not available, the first context is deleted (S502).

11. The method (500) of claim 9, further comprising: When the validity timer indicates that the non-redundancy is within the validity period, if the first network function (201) is not available, the first context is deleted (S502).

12. The method (500) of claim 9 or 11, wherein a validity timer is included in the binding indication or in another Hypertext Transfer Protocol (HTTP) header.

13. The method (500) according to any one of claims 8 to 12, wherein: The first network function (201) is a NF service producer (102), and the second network function (202) is a NF service consumer (101); wherein the first context is a resource context; and The first message is a response message or a notification message.

14. The method (500) according to any one of claims 8 to 12, wherein: The first network function (201) is a NF service consumer (101), and the second network function (202) is a NF service producer (102); Wherein, the first context is a session context or a resource context; The first message is a request message or a subscription message.

15. The method (500) according to any one of claims 8 to 14, in, The first network function (201) acts as a home session management function (SMF) for a home-routed packet data unit (PDU) session, and the access SMF corresponding to the home-routed PDU session does not support redundancy; Wherein, the first network function (201) is removed from a group of NFs due to service software upgrade, downgrade or maintenance; or The first network function (201) temporarily loses connection with an unstructured data storage function (UDSF) shared by a group of NFs.

16. A first network function (201), comprising: at least one processor (601); as well as A non-transitory computer-readable medium (602) coupled to the at least one processor (601), the non-transitory computer-readable medium (602) containing instructions executable by the at least one processor (601), whereby the at least one processor (601) is configured to perform the method (400) according to any one of claims 1-7.

17. A second network function (202), comprising: at least one processor (701); as well as A non-transitory computer-readable medium (702) coupled to the at least one processor (701), the non-transitory computer-readable medium (702) containing instructions executable by the at least one processor (701), whereby the at least one processor (701) is configured to perform the method (500) according to any one of claims 8-15.

18. A computer-readable medium (602, 702, 802), comprising a computer-readable code, which, when executed on a device (101, 102, 201, 202, 800), causes the device (101, 102, 201, 202, 800) to perform the method (400, 500) according to any one of claims 1 to 15.

19. A computer program product (804), comprising a computer readable code, which, when executed on a device (101, 102, 201, 202, 800), causes the device (101, 102, 201, 202, 800) to perform the method (500) according to any one of claims 1 to 15.

Images