Method and apparatus for binding indication - Patents.com

Abstract

A method for binding indication is provided. The method is performed by a first network function in a communication network. The method may include generating first binding information for a first notification endpoint in the network function, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint. The method may further include transmitting the first binding information to a second network function.

Description

[Technical field]

[0001] The present disclosure relates generally to communication networks, and more particularly, to a method and apparatus for binding indication. [Background technology]

[0002] Bindings may be used to indicate appropriate target Network Function (NF) producer instance(s) for NF service instance selection, reselection and routing of subsequent requests related to a particular NF producer resource (context) and NF service. This allows an NF producer to indicate that an NF consumer for a particular context should be bound to an NF service instance, NF instance, NF service set or NF set depending on local policies and other criteria (e.g., taking into account at what point in time it is in the middle of a particular procedure, performance aspects, etc.).

[0003] Bindings can also be used by NF consumers for reselection of notification target instances and routing of subsequent notification requests related to a particular notification subscription, and to provide binding indications of the service(s) that the NF consumer generates for the same data context and the services that the NF service producer may subsequently invoke.

[0004] For 5GC from Rel-16, a new binding indication is defined. This indication allows a network function producer (NFp) to indicate the preferred binding level and the binding for reselection (e.g. on failure or load balancing). The binding level indicates the resiliency model that may be used for subsequent requests (NF (service) set, NF instance, etc.).

[0005] Binding indications are defined to be included in requests and responses with different intents.

[0006] A binding indication provided as part of an explicit or implicit subscription applies to the corresponding notification.

[0007] In 3GPP TS29.500, clause 5.2.3.2.6, an example is given: Example 6: Subscription request from one NF on behalf of another NF, with two binding indications: 3gpp-Sbi-Binding: bl= nf-set; nfset=set1.udmset.5gc.mnc012.mcc345; servname=nudm-ee;scope=subscription-events 3gpp-Sbi-Binding: bl= nf-set; nfset=set1.nefset.5gc.mnc012.mcc345; servname=nnef-event-exposure Summary of the Invention

[0008] The solution disclosed herein aims to enable direct notification between network functions.

[0009] This solution proposes to complement the binding indication with an identification of the target user (notification sender) and the resource owner to which the binding applies. Alternatively, this information can be included in the application payload if it needs to be stored in a Unified Data Repository (UDR).

[0010] Additionally, this disclosure provides a mechanism to associate a binding resource with subscription information (including a notification Uniform Resource Identifier (URI), or similar callback URI) when multiple bindings are included in a request.

[0011] According to a first aspect of the present disclosure there is provided a method implemented by a first network function in a communications network, the method comprising: sending first binding information for a first notification endpoint among the network function consumers to a second network function, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; the first target user is a network function producer; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; The first binding information is included in a 3gpp-sbi-binding header.

[0012] The first binding information may be included in a binding indication sent to the second network function.

[0013] The first binding information may be sent to the second network function in addition to a binding indication.

[0014] The first binding information may be transmitted in a subscription request for a subscription event.

[0015] The first binding information may be transmitted in a subscription request for a subscription event on behalf of a third network function.

[0016] The first binding information may include a first target user identifier for the first target user and a first owner identifier for the first resource owner.

[0017] The first binding information may include correlation information used to correlate the first binding information with subscription information.

[0018] The correlation information may include an event identifier of a subscription event in the subscription information.

[0019] The correlation information may include information that allows identification of a notification recipient.

[0020] The correlation information may be an authority portion of a notification uniform resource identifier (URI) for a subscription event in the subscription information.

[0021] and sending second binding information for a second notification endpoint to the second network function, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network function producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; The second binding information is included in a 3gpp-sbi-binding header.

[0022] The first network function may be the network function consumer, the third network function and / or the second network function consumer.

[0023] The second network function may be the network function producer and / or the second network function producer.

[0024] According to a second aspect of the present disclosure, there is provided a method implemented by a second network function in a communications network, the method comprising: receiving, from a first network function, first binding information for a first notification endpoint among the network function consumers, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; the first target user is a network function producer; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; The first binding information is included in a 3gpp-sbi-binding header.

[0025] The first binding information may be included in a binding indication received by the second network function.

[0026] The first binding information may be received by the second network function in addition to a binding indication.

[0027] The first binding information may be received in a subscription request for a subscription event.

[0028] The first binding information may be received in a subscription request for a subscription event on behalf of a third network function.

[0029] The first binding information may include a first target user identifier for the first target user and a first owner identifier for the first owner.

[0030] The first binding information may include correlation information used to correlate the first binding information with subscription information.

[0031] The correlation information may include an event identifier of a subscription event in the subscription information.

[0032] The correlation information may include information that allows identification of a notification recipient.

[0033] The notification recipient information may be an authority portion of a notification uniform resource identifier (URI) for a subscription event in the subscription information.

[0034] using the first binding information to identify the first target user and the first resource owner; the first target user is the second network function; Sending a notification directly from the first target user to the first resource owner based on the first binding information; It may further include.

[0035] receiving, at the second network function, second binding information for a second notification endpoint, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network function producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; the second binding information is included in a 3gpp-sbi-binding header; using the second binding information to identify the second target user and the second resource owner; the second target user is the second network function; sending a notification directly from the second target user to the second resource owner based on the second binding information; It may further include.

[0036] The first network function may be the network function consumer, the third network function and / or the second network function consumer.

[0037] The second network function may be the network function producer and / or the second network function producer.

[0038] According to a third aspect of the present disclosure, there is provided a network device in a communication network, the network device may include a processor and a memory communicatively coupled to the processor, the memory may be adapted to store instructions that, when executed by the processor, cause the network device to perform steps of the method according to the first aspect above.

[0039] According to a fourth aspect of the present disclosure, there is provided a non-transitory machine-readable medium having stored thereon a computer program which, when executed by a set of one or more processors of a network device, causes said network device to perform the steps of the method according to the first aspect above.

[0040] According to a fifth aspect of the present disclosure, there is provided a network device in a communication network, the network device may include a processor and a memory communicatively coupled to the processor, the memory may be adapted to store instructions that, when executed by the processor, cause the network device to perform steps of the method according to the second aspect above.

[0041] According to a sixth aspect of the present disclosure, there is provided a non-transitory machine-readable medium having stored thereon a computer program which, when executed by a set of one or more processors of a network device, causes said network device to perform the steps of the method according to the second aspect above.

[0042] Advantageously, the solution disclosed herein enables sending of notifications directly from network capability producers to network capability consumers, thus reducing the signaling load in communication networks.

[0043] Further advantageously, the solution disclosed herein allows for the propagation of the above direct notification configuration through a chain of network functions that are not network function producers or network function consumers, thus allowing for the configuration of direct notifications in any message of any procedure executed by any NF.

[0044] Further advantageously, the solution disclosed herein enables the utilization of an integral part of the 5G architecture, the SBI header, to carry configuration information.

[0045] Other objects, features and advantages will become apparent from the following detailed disclosure, the appended dependent claims, and the drawings. [Brief description of the drawings]

[0046] The present disclosure may best be understood, by way of example, by referring to the following description and accompanying drawings, which are used to illustrate embodiments of the disclosure. In the drawings:

[0047] [Figure 1] FIG. 11 is a diagram illustrating a first example in which a network exposure function (NEF) cannot provide binding information for a notification sent from a session management function (SMF). [Diagram 2]FIG. 2 illustrates a method for binding indication according to a first embodiment, which solves the problem in the first example illustrated in FIG. 1. [Diagram 3] FIG. 13 illustrates a method for binding indication according to a second embodiment of the present disclosure. [Figure 4] FIG. 11 illustrates a third example in which a notification sender (NF producer) may receive multiple event subscriptions, each with its own different notification callback URI and binding indication in the 3gpp-Sbi-Binding header. [Diagram 5] 1 is an example flow diagram of a method of binding indication according to one or more embodiments of the present disclosure. [Figure 6] 1 is an example flow diagram of a method of binding indication according to one or more embodiments of the present disclosure. [Figure 7] FIG. 2 is a block diagram illustrating a network device according to some embodiments of the present disclosure. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0048] In the following detailed description, a method and apparatus for binding indication are described. In the following detailed description, numerous specific details are set forth, such as logic implementation, types and interrelationships of system components, in order to provide a more thorough understanding of the present disclosure. However, it should be understood by those skilled in the art that the present disclosure can be practiced without such specific details. In other instances, control structures, circuits and instruction sequences are not shown in detail in order not to obscure the present disclosure. Those skilled in the art will be able to implement the appropriate functions with the included description without undue experimentation.

[0049] As used herein, terms such as "first", "second", etc. refer to different elements. The singular forms "a", "an", and "the" are intended to include the plural unless the context clearly indicates otherwise. As used herein, the terms "comprise", "comprising", "has", "having", "includes" and / or "including" specify the presence of stated features, elements, and / or components, etc., but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof. The term "according to" is to be read as "at least in part according to". The terms "an embodiment" and "one embodiment" are to be read as "at least one embodiment". The term "another embodiment" is to be read as "at least one other embodiment".

[0050] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood. It will be further understood that terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and related art, and should not be interpreted in an idealized or overly formal sense unless expressly defined as such in this specification.

[0051] Bracketed text and blocks with dashed borders (e.g., big dashes, small dashes, dot dashes, and dots) may be used herein to illustrate optional operations that add additional features to embodiments of the present disclosure. However, such notations should not be taken to imply that these are the only options or optional operations and / or that blocks with solid borders are not optional in certain embodiments of the present disclosure.

[0052] Electronic devices use machine-readable media (also called computer-readable media), such as machine-readable storage media (e.g., magnetic disks, optical disks, read-only memories (ROMs), flash memory devices, phase-change memories) and machine-readable transmission media (also called carriers) (e.g., electrical, optical, radio, acoustic or other forms of propagated signals-carrier waves, infrared signals, etc.) to store and transmit code (comprised of software instructions, also called computer program code or computer programs) and / or data (internally and / or to and from other electronic devices over a network). Thus, an electronic device (e.g., a computer) includes hardware and software, such as a set of one or more processors coupled to one or more machine-readable storage media for storing code for execution on the set of processors and / or for storing data. For example, an electronic device may include a non-volatile memory containing code, such that non-volatile memory can persist code / data even when the electronic device is turned off (power is removed), and portions of the code to be executed by the processor(s) of the electronic device while the electronic device is turned on are copied from the typically slower non-volatile memory into the volatile memory of the electronic device (e.g., dynamic random access memory (DRAM) or static random access memory (SRAM)). A typical electronic device also includes a set or one or more physical network interfaces for establishing network connections with other electronic devices (sending and / or receiving code and / or data using propagating signals). One or more portions of the embodiments of the present disclosure may be implemented using different combinations of software, firmware, and / or hardware.

[0053] Bindings can be used to indicate the target NF producer instance(s) suitable for NF service instance selection, reselection and routing of subsequent requests related to a particular NF producer resource (context) and NF service. This allows an NF producer to indicate that an NF consumer for a particular context should be bound to an NF service instance, NF instance, NF service set or NF set depending on local policies and other criteria (e.g., at what point in time are they in the middle of a particular procedure, taking into account performance aspects, etc.).

[0054] Bindings can also be used by NF consumers for reselection of notification target instances and routing of subsequent notification requests related to a particular notification subscription, and to provide binding indications for service(s) that the NF consumer may generate for the same data context and that the NF service producer may subsequently invoke.

[0055] An NF service producer may provide a binding indication to an NF service consumer as part of a direct or indirect communication procedure to be used in subsequent related service requests. The level of binding indication that an NF service producer provides to an NF consumer indicates whether a resource in the NF service producer is bound to an NF service instance, an NF instance, an NF service set or an NF set. The binding indication may include an NF service set ID, an NF set ID, an NF instance ID or an NF service instance ID for the NF consumer or SCP to use for (re)selection of the NF service producer. When a resource is created at an NF service producer, the NF service producer provides resource information including the NF service producer's endpoint address. For indirect communication, the NF service consumer copies the binding indication to the routing binding indication of the request or subscribe message.

[0056] During an explicit or implicit notification subscription, a binding indication may be provided by an NF service consumer to an NF service producer, where the NF service consumer will also provide a notification endpoint. An NF service consumer may also provide a binding indication in response to a notification request. The level of binding indication provided by an NF service consumer to an NF service provider indicates whether the notification endpoint is bound to an NF service instance, an NF instance, an NF service set or an NF set as specified in Table 6.3.1.0-1. The binding indication must include at least one of an NF set ID, an NF instance ID, an NF service set ID and / or an NF service instance ID, and may also include a service name. The NF service set ID, NF service instance ID and service name are associated with the service of the NF service consumer that processes the notification.

[0057] As used herein, a "binding resource" refers to a resource of an NF service producer when a binding indication is provided from an NF producer to an NF consumer, and refers to a notification endpoint when a binding indication is provided from an NF consumer to an NF producer.

[0058] The solution disclosed herein aims to enable direct notification between network functions.

[0059] The solution proposes to complement the binding indication with an identification of the target user (notification sender) and the resource owner to which the binding applies. Alternatively, this information may be included in the application payload if it needs to be stored in a Uniform Data Repository (UDR).

[0060] Additionally, this disclosure provides a mechanism to associate a binding resource with subscription information (including a notification uniform resource identifier (URI), or similar callback URI) when multiple bindings are included in a request.

[0061] According to a first aspect of the present disclosure there is provided a method implemented by a first network function in a communications network, the method comprising: sending first binding information for a first notification endpoint among the network function consumers to a second network function, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; the first target user is a network function producer; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; The first binding information is included in a 3gpp-sbi-binding header.

[0062] The first binding information may be included in a binding indication sent to the second network function.

[0063] The first binding information may be sent to the second network function in addition to a binding indication.

[0064] The first binding information may be transmitted in a subscription request for a subscription event.

[0065] The first binding information may be transmitted in a subscription request for a subscription event on behalf of a third network function.

[0066] The first binding information may include a first target user identifier for the first target user and a first owner identifier for the first resource owner.

[0067] The first binding information may include correlation information used to correlate the first binding information with subscription information.

[0068] The correlation information may include an event identifier of a subscription event in the subscription information.

[0069] The correlation information may include information that allows identification of a notification recipient.

[0070] The correlation information may be an authority portion of a notification uniform resource identifier (URI) for a subscription event in the subscription information.

[0071] and sending second binding information for a second notification endpoint to the second network function, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network function producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; The second binding information is included in a 3gpp-sbi-binding header.

[0072] The first network function may be the network function consumer, the third network function and / or the second network function consumer.

[0073] The second network function may be the network function producer and / or the second network function producer.

[0074] According to a second aspect of the present disclosure, there is provided a method implemented by a second network function in a communications network, the method comprising: receiving, from a first network function, first binding information for a first notification endpoint among the network function consumers, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; the first target user is a network function producer; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; The first binding information is included in a 3gpp-sbi-binding header.

[0075] The first binding information may be included in a binding indication received by the second network function.

[0076] The first binding information may be received by the second network function in addition to a binding indication.

[0077] The first binding information may be received in a subscription request for a subscription event.

[0078] The first binding information may be received in a subscription request for a subscription event on behalf of a third network function.

[0079] The first binding information may include a first target user identifier for the first target user and a first owner identifier for the first owner.

[0080] The first binding information may include correlation information used to correlate the first binding information with subscription information.

[0081] The correlation information may include an event identifier of a subscription event in the subscription information.

[0082] The correlation information may include information that allows identification of a notification recipient.

[0083] The notification recipient information may be an authority portion of a notification uniform resource identifier (URI) for a subscription event in the subscription information.

[0084] using the first binding information to identify the first target user and the first resource owner; the first target user is the second network function; Sending a notification directly from the first target user to the first resource owner based on the first binding information; It may further include.

[0085] receiving, at the second network function, second binding information for a second notification endpoint, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network function producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; the second binding information is included in a 3gpp-sbi-binding header; using the second binding information to identify the second target user and the second resource owner; the second target user is the second network function; sending a notification directly from the second target user to the second resource owner based on the second binding information; It may further include.

[0086] The first network function may be the network function consumer, the third network function and / or the second network function consumer.

[0087] The second network function may be the network function producer and / or the second network function producer.

[0088] According to a third aspect of the present disclosure, there is provided a network device in a communication network, the network device may include a processor and a memory communicatively coupled to the processor, the memory may be adapted to store instructions that, when executed by the processor, cause the network device to perform steps of the method according to the first aspect above.

[0089] According to a fourth aspect of the present disclosure, there is provided a non-transitory machine-readable medium having stored thereon a computer program which, when executed by a set of one or more processors of a network device, causes said network device to perform the steps of the method according to the first aspect above.

[0090] According to a fifth aspect of the present disclosure, there is provided a network device in a communication network, the network device may include a processor and a memory communicatively coupled to the processor, the memory may be adapted to store instructions that, when executed by the processor, cause the network device to perform steps of the method according to the second aspect above.

[0091] According to a sixth aspect of the present disclosure, there is provided a non-transitory machine-readable medium having stored thereon a computer program which, when executed by a set of one or more processors of a network device, causes said network device to perform the steps of the method according to the second aspect above.

[0092] Advantageously, the solution disclosed herein enables sending of notifications directly from network capability producers to network capability consumers, thus reducing the signaling load in communication networks.

[0093] Further advantageously, the solution disclosed herein allows for the propagation of the above direct notification configuration through a chain of network functions that are not network function producers or network function consumers, thus allowing for the configuration of direct notifications in any message of any procedure executed by any NF.

[0094] Further advantageously, the solution disclosed herein enables the utilization of an integral part of the 5G architecture, the SBI header, to carry configuration information.

[0095] Other objects, features and advantages will become apparent from the following detailed disclosure, the appended dependent claims, and the drawings.

[0096] FIG. 1 is a diagram illustrating a first example in which a network exposure function (NEF) cannot provide binding information for a notification sent from a session management function (SMF).

[0097] Step 0. The PCF subscribes to receive updates of application data and / or influence data.

[0098] Step 1. The SMF sends a Nsmf_SMPolicyControl_Create to the PCF for a new PDU session. In the response, the PCF may include a binding indication for the resources created by the request.

[0099] Step 2. The AF sends an Nnef_TrafficInfluence_Create to the NEF. This operation contains an implicit subscription to the UP_PATH_CHANGE event identified by the SMF.

[0100] Step 3. The NEF stores the application data / impact data in the UDR, including information from the NEF subscription to SMF notifications.

[0101] Step 4. The UDR notifies subscribed consumers (which in this case apply to the PCF) of the updated application data / impact data.

[0102] Step 5. The PCF checks the information received in the notification, including the subscription to UP_PATH_CHANGE.

[0103] Step 6. Upon receiving the updated data, the PCF notifies the SMF for the affected ongoing PDU session(s) by Nsmf_SMPolicyControl_UpdateNotify. This notification includes the subscription to the previously received UP_PATH_CHANGE.

[0104] Step 7. Although the subscription information received today includes a notification callback URI, no means are defined for conveying other information that would allow SMF to find an alternative endpoint if the notification callback URI fails.

[0105] In this first example, the subscription information is stored in the UDR for use in subsequent notifications.

[0106] As proposed in this disclosure, a binding indication is complemented with information identifying who is the intended user of the binding information (notification sender) and the resource owner of the binding resource to which the binding applies (notification recipient), so that the binding indication can ultimately be used by its intended users and received by the corresponding owner, even across different NFs.

[0107] FIG. 2 illustrates a binding indication method according to a first embodiment, which solves the problem in the first example illustrated in FIG.

[0108] The steps are similar to those described for Figure 1, with the following modifications:

[0109] Step 3: The binding indication is included with additional information identifying the target user (notification sender) and the resource owner (notification receiver) to which the binding applies. In this example, the target user is the SMF and the resource owner is the NEF.

[0110] The "resource owner (notification receiver)" is identified by the binding information itself, except for the "notification URI", which is overlooked. This is explained in more detail in the third example below. In this first example, the target user is one that the involved NFs know about, since this particular interaction is only defined for the NEF (notification receiver) and the SMF (notification sender). The "target user" would be needed in case there could be multiple notification receivers for the same type of subscription.

[0111] In one embodiment, the binding indication is complemented with the target user and / or owner of the resource information and conveyed in a header (eg, 3gpp-Sbi-Binding header).

[0112] 3gpp-Sbi-Binding = "3gpp-Sbi-Binding" ":" #(OWS "bl=" blvalue 1*( OWS ";" parameter) OWS ";" recoverytime; OWS ";" user; OWS ";" owner) blvalue = "nf-instance" / "nf-set" / "nfservice-instance" / "nfservice-set" parameter = parametername "=" token parametername = "nfinst" / "nfset" / "nfservinst" / "nfserviceset" / "servname" / "scope" scope = "other-service" / "callback" / "subscription-events" recoverytime = "recoverytime=" OWS date-time

[0113] The 'user' field may contain the following information to help the intermediate NF identify the target user of the binding indication (which is the SMF in this example): nf-type, nf-instance, nf-set, nfservice-instance, and nfservice-set.

[0114] The 'owner' field may contain the following information to help intermediate NFs and / or intended users of the binding indication to identify the resource owner to which the binding applies: nf-type, nf-instance, nf-set, nfservice-instance, nfservice-set.

[0115] In another embodiment, the binding indication is complemented with the target user and / or owner of the resource information and conveyed in an application payload in the message body, e.g., TrafficInfluData, which is stored in the UDR by the NEF via the Nudr_DataRepository API. This makes sense if the binding is for notifications that are valid for future interactions, not just subsequent notifications. In the second and third examples of the problem statement, this embodiment may not be applicable, since there may be no point in storing the data in the UDR.

[0116] [Table 1]

[0117] [Table 2]

[0118] Step 4. The UDR sends a binding indication containing additional information to the PCF.

[0119] Step 7. If the notification callback URI is not reachable, the SMF MUST be able to use the binding information received in step 6 to identify an alternative NEF recipient for the required notification.

[0120] The messages discussed herein are merely examples for the purposes of this disclosure and do not limit the scope of this disclosure. Those skilled in the art may employ different types of messages to perform the method without departing from the spirit and scope of the disclosure. As will be apparent to those skilled in the art, many different ways of performing the method are possible. For example, the order of steps may be changed or some steps may be performed in parallel. Furthermore, other method steps may be inserted between steps. The inserted steps may represent improvements to the method as described herein or may be unrelated to the method. For example, steps may be performed at least partially in parallel. A given step may not be completely completed before the next step is initiated. Furthermore, fewer steps than all steps illustrated may be required to implement the illustrated methodology. Steps may be combined or separated into multiple sub-steps. Furthermore, additional or alternative methodologies may employ additional steps not illustrated.

[0121] FIG. 3 illustrates a method for binding indication according to a second embodiment of the present disclosure.

[0122] In the second example, the NF / NF service status subscribe / notification traverses the PLMN. However, in this case, it is not explained how the NRF of the H-PLMN obtains the necessary binding information to use in step 4 (sending notification). Figure 3 provides a way to solve the problem in the second example.

[0123] Step 1: The NFc contains the normal binding indication used by the receiver (the NRF of the serving PLMN).

[0124] Step 2: The subscription request contains the usual binding indications (i.e., those that the NRF needs to receive notifications directly from the NRF of the home PLMN, but targeted to itself). The subscription request contains another binding indication that applies to the NFc as the recipient of the notifications. The target user and resource owner are included as described for the other first and third examples.

[0125] Step 3: When a notification from the NRF of the serving PLMN is required to be sent to the NFc, the NFc uses the received binding.

[0126] Step 4: If the NRF of the home PLMN needs to notify the NFc directly, it must use the newly added binding indication (which contains the additional information shown above).

[0127] Figure 4 shows a third example where a notification sender (NF producer) can receive multiple event subscriptions, each with a different notification callback URI and binding indication in the 3gpp-Sbi-Binding header, but it is not standard how the notification sender can distinguish which binding indication is associated with (owned by) which subscription(s).

[0128] Step 1. The AF sends a Nnef_TrafficInfluence_Create to the NEF to influence the traffic of an ongoing PDU session. This operation includes an implicit subscription to the UP_PATH_CHANGE event identified by the SMF.

[0129] Step 2. The NEF calls Npcf_PolicyAuthorization_Create for the serving PCF of the PDU session. For simplicity, how the NEF discovers the serving PCF (through NRF and BSF queries) is not visible in the call flow. The Npcf_PolicyAuthorization_Create operation includes the subscription information from the NEF on the SMF for the traffic-impacting UP_PATH_CHANGE event. Meanwhile, based on local policy, the NEF may also include another subscription for the QOS_MONITORING event on the SMF. The NEF may add two different binding indications for these two subscriptions, respectively. This may happen for traffic separation or load balancing purposes.

[0130] Step 3. The PCF updates the serving SMF of the PDU session with the policy change via Npcf_SMPolicyControl_UpdateNotify. This operation contains information about the subscriptions from the NEF to the SMF for the UP_PATH_CHANGE and QOS_MONITORING events, and the corresponding binding indications. However, the standard does not define how the SMF can associate the subscriptions with the binding indications (in steps 4 and 5) that are used in case the original notification callback URI is not reachable. In fact, it does not describe how the notification URI is conveyed specifically in case the NF sends a subscription on behalf of another person.

[0131] For the third example of the problem description, the same solution would be applied: the binding indications in steps 2 and 3 of Fig. 3 would be complemented with additional information (user and / or owner) as commented for the first and second examples.

[0132] But more importantly, in this case there is also a need to specify which subscription (including notification URI, i.e. callback) is associated with each binding indication.

[0133] In the first embodiment, the owner field may also include other information (e.g., an event ID) to help the intermediate NF and / or the intended user of the binding indication associate a subscription with the binding indication.

[0134] In another embodiment, the binding indication is complemented with correlation information and conveyed in a header, for example the 3gpp-Sbi-Binding header (reference [2]). The correlation information is used to correlate the binding indication with the subscription(s) information. If necessary, user and owner information can be derived implicitly from the subscription information pointed to by the correlation information.

[0135] 3gpp-Sbi-Binding = "3gpp-Sbi-Binding" ":" #(OWS "bl=" blvalue 1*( OWS ";" parameter) OWS ";" recoverytime; OWS ";" correlation) blvalue = "nf-instance" / "nf-set" / "nfservice-instance" / "nfservice-set" parameter = parametername "=" token parametername = "nfinst" / "nfset" / "nfservinst" / "nfserviceset" / "servname" / "scope" scope = "other-service" / "callback" / "subscription-events" recoverytime = "recoverytime=" OWS date-time

[0136] In one implementation, the correlation information may be a JSON pointer to the resource attribute that contains the notification callback URI, or to any parent attribute that contains one or more notification callback URIs with the same binding indication.

[0137] Example: Traffic impact 3gpp-Sbi-Binding: bl=nf-instance; nfinst=54804518-4191-46b3-955c-ac631f953ed9; nfset=set1.nefset.5gc.mnc012.mcc345; servname=nnef-afi; correlation= / pccRules / id3 / refTcData

[0138] Example: QoS monitoring 3gpp-Sbi-Binding: bl=nf-instance; nfinst=64804518-4191-46b3-955c-ac631f953ed9; nfset=set1.nefset.5gc.mnc012.mcc345; servname=nnef-qos; correlation= / pccRules / id3 / refQoSMon

[0139] In another embodiment, the correlation information may be conveyed in an application payload within the message body, such as TrafficInfluData, which is stored in the UDR by the NEF via the Nudr_DataRepository API, as described above for the first example.

[0140] FIG. 5 illustrates an example flow diagram 500 for a method of binding indication according to one or more embodiments of the present disclosure.

[0141] 5, in step 501, first binding information may be generated for a first binding resource in a network function. The first binding information may indicate a first target user of the first binding information and a first resource owner of the first binding resource. In step 502, the first binding information is sent to a second network device.

[0142] In a further embodiment, the first binding information may be included in a binding indication sent to the second network function.

[0143] In another further embodiment, the first binding information may be transmitted to the second network device in addition to the binding indication.

[0144] In one example, the method 500 may include generating a subscription request for the subscription event and sending the first binding information in the subscription request to the second network device.

[0145] In another example, the method may include generating a subscription request for the subscription event on behalf of a third network device and sending the first binding information in the subscription request to the second network device.

[0146] In one embodiment, the first binding information may include a first target user identifier for the first target user and a first owner identifier for the first resource owner.

[0147] In another embodiment, the first binding information includes correlation information used to correlate the first binding information and the subscription information.

[0148] As one example, the correlation information may include an event identifier of the subscription event in the subscription information. As another example, the correlation information may include information to enable identification of a notification recipient. As a further example, the correlation information may be an authority portion of a notification uniform resource identifier URI of the subscription event in the subscription information. As yet another example, the correlation information may be a JavaScript Object Notation (JSON) pointer to a payload attribute that encodes a notification recipient of the subscription event in the subscription information.

[0149] In one embodiment, the first binding information may be included in a header for transmission to the second network device.

[0150] In another embodiment, the first binding information may be included in an application body in a message for sending to the second network device.

[0151] In another embodiment, the first binding information may be used by the second network device to send a notification directly to the third network device.

[0152] As one embodiment, the method 500 may further include generating second binding information for the second binding resource created by the network function producer, the second binding information indicating a second target user of the second binding information and a second resource owner of the second binding resource, and sending the second binding information to the second network device.

[0153] FIG. 6 illustrates an example flow diagram 600 for a method of binding indication according to one or more embodiments of the present disclosure.

[0154] 6, in step 601, first binding information may be received for a first binding resource in a network function. The first binding information may indicate a first target user of the first binding information and a first resource owner of the first binding resource. In step 602, the first binding information may be used to identify the first target user and the first resource owner.

[0155] In a further embodiment, the first binding information may be included in a binding indication received by the second network device.

[0156] In another further embodiment, the first binding information may be received by the second network device in addition to the binding indication.

[0157] In one example, the first binding information may be received in a subscription request for a subscription event for the first network device.

[0158] In another example, the first binding information may be received in a subscription request for a subscription event from a first network device on behalf of a third network device.

[0159] In one embodiment, the first binding information may include a first target user identifier for the first target user and a first owner identifier for the first owner.

[0160] In another embodiment, the first binding information may include correlation information used to correlate the first binding information with the subscription information.

[0161] As one example, the correlation information may include an event identifier of a subscription event in the subscription information. As another example, the correlation information may include information to enable identification of a notification recipient. As a further example, the correlation information may be an authority portion of a notification uniform resource identifier URI of a subscription event in the subscription information. As yet another example, the correlation information may be a JavaScript Object Notation (JSON) pointer to a payload attribute that encodes a notification recipient of a subscription event in the subscription information.

[0162] In one embodiment, the first binding information may be included in a header received by the second network device.

[0163] In another embodiment, the first binding information may be included in an application body in the message received by the second network device.

[0164] In another embodiment, the first binding information may be used by the second network device to send a notification directly to the third network device.

[0165] In another embodiment, the first binding information may be used by the second network device to send a direct notification to the first network device.

[0166] As one embodiment, the method 600 may further include receiving second binding information for a second binding resource at the network function, the second binding information indicating a second target user of the second binding information and a second resource owner of the second binding resource; and using the second binding information to identify the second target user and the second resource owner.

[0167] 7 is a block diagram illustrating a network device 700 according to some embodiments of the present disclosure. It should be understood that the network device 700 may be implemented using components other than those illustrated in FIG.

[0168] 7, the network device 700 may include at least a processor 701, a memory 702, an interface, and a communication medium. The processor 701, the memory 702, and the interface are communicatively coupled to each other via the communication medium.

[0169] Processor 701 includes one or more processing units. A processing unit may be a physical device or article of manufacture including one or more integrated circuits that read data and instructions from a computer-readable medium, such as memory 702, and selectively execute the instructions. In various embodiments, processor 701 is implemented in various ways. As one example, processor 702 may be implemented as one or more processing cores. As another example, processor 701 may be comprised of one or more separate microprocessors. As yet another example, processor 702 may be comprised of an application specific integrated circuit (ASIC) that provides specific functions. In yet another example, processor 701 provides specific functionality by using an ASIC and executing computer-executable instructions.

[0170] The memory 702 includes one or more computer usable or computer readable storage media capable of storing data and / or computer executable instructions. It should be understood that the storage media is preferably a non-transitory storage medium.

[0171] The communication medium facilitates communication between the processor 701, the memory 702, and the interface. The communication medium can be implemented in various ways. For example, the communication medium can be a PCI (Peripheral Component Interconnect) bus, a PCI Express bus, an AGP (Accelerated Graphics Port) bus, an ATA (Serial Advanced Technology Attachment) interconnect, a Parallel ATA interconnect, a Fibre Channel interconnect, a USB bus, a SCSI (Small Computer System Interface) interface, or other types of communication media. The interface can be coupled to the processor. Information and data such as those described above in connection with the method can be transmitted over the interface.

[0172] In the example of FIG. 7, instructions stored in memory 702 may include those that, when executed by processor 701, cause network device 700 to perform the methods described with respect to FIGS.

[0173] Some portions of the preceding detailed description have been presented in terms of algorithms and symbolic representations of transactions on data bits within a computer memory. These algorithmic descriptions and representations are the methods used by those skilled in the data processing arts to most effectively convey the substance of their work to others skilled in the art. An algorithm is herein generally conceived to be a self-consistent sequence of transactions leading to a desired result. The transactions are those requiring physical manipulations of physical quantities. Usually, though not necessarily, these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to these signals as bits, values, elements, symbols, characters, terms, numbers, or the like.

[0174] It should be understood, however, that all of these and similar terms are to be associated with the appropriate physical quantities and are merely convenient labels applied to these quantities. As is apparent from the above discussion, unless specifically stated otherwise, discussions utilizing terms such as "processing" or "computing" or "calculating" or "determining" or "displaying" throughout this specification are understood to refer to operations and processes of a computer system or similar electronic computing device that manipulate and transform data represented as physical (electronic) quantities in the computer system's registers and memory into other data that are similarly represented as physical quantities in the computer system's memory or registers or other such information storage, transmission or display device.

[0175] The algorithms and displays presented herein are not inherently related to any particular computer or other apparatus. Various general-purpose systems may be used with programs in accordance with the teachings herein, or it may prove convenient to construct more specialized apparatus to perform the required method transactions. The required structure for a variety of these systems will appear from the description above. Further, embodiments of the present disclosure have not been described with reference to any particular programming language. It will be understood that a variety of programming languages ​​may be used to implement the teachings of the embodiments of the present disclosure described herein.

[0176] An embodiment of the present disclosure may be an article of manufacture in which a non-transitory machine-readable medium (such as a microelectronic memory) stores instructions (e.g., computer code) that program one or more data processing components (generally referred to herein as "processors") to perform the operations described above. In other embodiments, some of these operations may be performed by specific hardware components that include hardwired logic (e.g., dedicated digital filter blocks and state machines). The operations may alternatively be performed by any combination of programmed data processing components and fixed hardwired circuitry components.

[0177] In the foregoing detailed description, embodiments of the present disclosure have been described with reference to specific exemplary embodiments thereof. It will be apparent that various modifications may be made thereto without departing from the spirit and scope of the present disclosure as defined in the following claims. The specification and drawings are therefore to be regarded in an illustrative rather than a restrictive sense.

[0178] Throughout the description, some embodiments of the present disclosure are presented through flow diagrams. It should be understood that the transactions and order of transactions depicted in these flow diagrams are for illustrative purposes only and are not intended as limitations of the present disclosure. Those skilled in the art will recognize that variations can be made to the flow diagrams without departing from the spirit and scope of the present disclosure, as defined in the following claims.

Claims

1. 1. A method implemented by a first network function in a communications network, the method comprising: sending first binding information for a first notification endpoint among the network function consumers to a second network function, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; the first target user is a network function producer; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; the first binding information is included in a 3gpp-sbi-binding header; The first binding information is transmitted in a subscription request for a subscription event on behalf of a third network function. method.

2. The first binding information is included in a binding indication sent to the second network function. The method of claim 1.

3. The first binding information is sent to the second network function in addition to a binding indication. The method of claim 1.

4. The first binding information includes a first target user identifier for the first target user and a first owner identifier for the first resource owner. The method of claim 1.

5. The first binding information includes correlation information used to correlate the first binding information with subscription information.

5. The method according to any one of claims 1 to 4.

6. The correlation information includes an event identifier of a subscription event in the subscription information. The method according to claim 5.

7. sending second binding information for a second notification endpoint to the second network function, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network capability producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; The second binding information is included in a 3gpp-sbi-binding header.

7. The method according to any one of claims 1 to 6.

8. A method implemented by a second network function in a communications network, the method comprising: receiving, from a first network function, first binding information for a first notification endpoint among the network function consumers, the first binding information indicating a first target user of the first binding information and a first resource owner of the first notification endpoint; using the first binding information to identify the first target user and the first resource owner; Including, the first target user is a network function producer and the second network function; the first resource owner is the network function consumer; the first binding information indicates sending a notification directly from the first target user to the first resource owner; the first binding information is included in a 3gpp-sbi-binding header; The first binding information is received in a subscription request for a subscription event on behalf of a third network function. method.

9. The first binding information is included in a binding indication received by the second network function. The method according to claim 8.

10. The first binding information is received by the second network function in addition to a binding indication. The method according to claim 8.

11. The first binding information includes a first target user identifier for the first target user and a first owner identifier for the first resource owner. The method according to claim 8.

12. The first binding information includes correlation information used to correlate the first binding information with subscription information.

12. The method according to any one of claims 8 to 11.

13. The correlation information includes an event identifier of a subscription event in the subscription information. The method of claim 12.

14. Sending a notification directly from the first target user to the first resource owner based on the first binding information; and Also includes 14. A method according to any one of claims 8 to 13.

15. receiving, at the second network function, second binding information for a second notification endpoint, the second binding information indicating a second target user of the second binding information and a second resource owner of the second notification endpoint; the second target user is a second network capability producer; the second resource owner is a second network function consumer; the second binding information indicates sending a notification directly from the second target user to the second resource owner; the second binding information is included in a 3gpp-sbi-binding header; using the second binding information to identify the second target user and the second resource owner; the second target user is the second network function; sending a notification directly from the second target user to the second resource owner based on the second binding information; Also includes 15. A method according to any one of claims 8 to 14.

16. 1. A network function in a communications network, comprising: A processor; A memory communicatively coupled to said processor and adapted to store instructions which, when executed by said processor, cause said network function to perform the steps of the method of any one of claims 1 to 7; Networking capabilities, including

17. 1. A network function in a communications network, comprising: A processor; a memory communicatively coupled to said processor and adapted to store instructions which, when executed by said processor, cause said network function to perform the steps of the method of any one of claims 8 to 15; Networking capabilities, including

Images